Skip to content

Conversation

@bertllll
Copy link
Contributor

@bertllll bertllll commented Oct 9, 2025

Note

Delays and refines retry-payables scheduling, renames/cleans up pending-failure handling with richer logs, fixes inclusive block-range/new-start logic and nonce retrieval, and improves batch error handling; updates tests and CI macOS target.

  • Accountant/Scanners:
    • Rename unproven to suspected failures across pending-payables, with clearer cache handling and logs.
    • Add detailed debug/info logs throughout scans (acknowledge errors, composing reports, confirmations/reclaims, totals, etc.).
    • Change retry-payables to be scheduled via notify_later with configurable retry_payable_scan_interval; reset_scan_timer(&logger) signature.
    • Update RetryTxTemplates::new/RetryTxTemplate::new (accept logger and set amount to latest payable balance, not additive).
    • Minor string/format improvements and panic messages.
  • BlockchainBridge/Web3:
    • Prevent duplicate ScanError by consolidating success/error message emission in then.
    • Add warning on batch submit failure; propagate failed txs without extra ScanError.
    • Calculate end block inclusively (start + range - 1); adjust new-start logic and logs.
    • Low-level get_transaction_id uses default (no Pending) and higher-level logs latest nonce.
  • Tests/CI:
    • Update expectations for logs/messages ("suspected failures", scan summaries, inclusive ranges).
    • Extend integration/unit tests accordingly; add extra RPC endpoints; switch CI to macos-latest.

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

}

pub fn acknowledge_scan_error(&mut self, error: &ScanError, logger: &Logger) {
debug!(logger, "Acknowledging a scan that couldn't finish");
Copy link
Collaborator

Choose a reason for hiding this comment

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

Perhaps you could add more details to this log, using the contents of the error.

utkarshg6 and others added 11 commits October 16, 2025 15:02
* Fixed the AddRouteResultMessage panic problem too

* Preemptive review issues

* Formatting

* example.com -> www.example.com

* Formatting

* Added some debug logging to track RRI

* Formatting

* Clippy

* Made RRI logs more consistent and increased straggler timeout to 30s

* Typo corrections

* Interim commit

* Tests pass

* Unit tests pass

* Interim commit: a real mess

* Proxy Server tests passing; some cleanup yet to do

* Unit tests are all passing

* Unit and multinode tests pass

* All the tests pass now

* Tests passing except one in proxy_client

* RRIDs are completely gone; hostnames are mandatory.

* MOre review issues

* Review issues

* Test is passing now, and code is cleaner

* Cleaned up some code

* More review issues

* Formatting

* Added packet describers

* Error message change.

* log messages enhanced of StreamKey

---------

Co-authored-by: czarte <czarte@gmail.com>
)

Revert "Breaking change to remove RRID from CORES packages (#740)"
This reverts commit a151e96.
* update ci-matrix to test new runners

* Revert Windows runner in CI matrix

Moving windows runner back to 2022, so we can allow macos-latest to fully run through Actions
* Refine regex for max block count extraction and add test

Updated regex to capture maximum block count from error messages more accurately - namely update to Nodies provider. Added a new test case for extracting this specific error response.

* Fix inclusive range calculation for block scanning in BlockchainInterfaceWeb3
Adjusted the end block marker calculation to correctly account for inclusive ranges by subtracting 1 from the scan range. T

* Fix block marker calculations in tests for blockchain bridge and interface. Adjusted expected new start block values to ensure accurate transaction retrieval and logging.
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.

This PR is being reviewed by Cursor Bugbot

Details

Your team is on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle for each member of your team.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

}

pub fn acknowledge_scan_error(&mut self, error: &ScanError, logger: &Logger) {
debug!(logger, "Acknowledging a scan that couldn't finish");
Copy link

Choose a reason for hiding this comment

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

Bug: Insufficient logging detail in scan error handler (Bugbot Rules)

The debug log in acknowledge_scan_error logs a generic message without including error details. The PR reviewer explicitly requested adding more details using the contents of the error parameter, which contains scan_type, response_skeleton_opt, and msg fields that would aid debugging. The commit adds the log but doesn't incorporate the error's contents as requested.

Fix in Cursor Fix in Web

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.

6 participants