Skip to content

Conversation

@lev-starkware
Copy link
Contributor

@lev-starkware lev-starkware commented Feb 10, 2026

Note

Medium Risk
New operational scripts execute gcloud subprocesses and implement non-trivial log parsing/correlation; mistakes or missing config (e.g., expected env_map.yaml) could lead to incomplete/incorrect reports or runtime failures, but production code paths are unaffected.

Overview
Adds a new generate_consensus_report_v1_2.py script that parses GCP Logs JSON exports for a given block height and emits a canonical plain-text consensus report, including per-round timing/metadata, per-node vote extraction, validation failures with evidence, and resource/weights lookup correlated by namespace and timestamps.

Adds a companion generate_logs_and_report.py CLI that builds gcloud logging read queries (with optional auto/near/custom time windows), downloads the relevant logs for a height, and optionally invokes the report generator to produce a .txt report (including temp-file handling when no JSON output path is provided).

Written by Cursor Bugbot for commit 2232394. This will update automatically on new commits. Configure here.

@reviewable-StarkWare
Copy link

This change is Reviewable

Copy link
Contributor Author

This stack of pull requests is managed by Graphite. Learn more about stacking.

@lev-starkware lev-starkware marked this pull request as ready for review February 10, 2026 14:14
@lev-starkware lev-starkware force-pushed the 02-10-consensus_report_script_to_get_logs_and_create_consensus_reports_for_specific_height branch from 51596c3 to 3ccc69c Compare February 10, 2026 14:57
@lev-starkware lev-starkware changed the title consensus_report: script to get logs and create consensus reports for specific height scripts: adding scripts to get logs and create consensus reports for specific height Feb 10, 2026
@lev-starkware lev-starkware force-pushed the 02-10-consensus_report_script_to_get_logs_and_create_consensus_reports_for_specific_height branch 2 times, most recently from 44a6c72 to 203e3f3 Compare February 10, 2026 17:56
Copy link
Contributor Author

@lev-starkware lev-starkware left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@lev-starkware resolved 2 discussions.
Reviewable status: 0 of 2 files reviewed, all discussions resolved (waiting on @TzahiTaub).

@lev-starkware lev-starkware force-pushed the 02-10-consensus_report_script_to_get_logs_and_create_consensus_reports_for_specific_height branch from 203e3f3 to aba265d Compare February 11, 2026 14:31
Copy link
Contributor Author

@lev-starkware lev-starkware left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@lev-starkware resolved 1 discussion.
Reviewable status: 0 of 2 files reviewed, all discussions resolved (waiting on @TzahiTaub).

Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 2 potential issues.

@lev-starkware lev-starkware force-pushed the 02-10-consensus_report_script_to_get_logs_and_create_consensus_reports_for_specific_height branch from aba265d to 2232394 Compare February 11, 2026 21:04
Copy link
Contributor Author

@lev-starkware lev-starkware left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@lev-starkware resolved 2 discussions.
Reviewable status: 0 of 2 files reviewed, all discussions resolved (waiting on @TzahiTaub).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants