007 resilience e2e#362
Conversation
- Introduced and types for managing transaction attempts. - Implemented for creating, saving, and retrieving transaction attempts. - Updated and to include necessary dependencies. - Added tests for transaction attempt functionality to ensure correct behavior and persistence.
- Added support for recording transaction attempt updates, including transaction hashes and receipts. - Updated the trait and its implementations to accommodate new fields. - Integrated transaction attempt recording into order and settlement handlers. - Introduced end-to-end tests for transaction attempt delivery to ensure proper functionality and persistence. - Added dependency for async trait support.
…vice - Added TransactionAttemptStore to RecoveryService for enhanced transaction recovery. - Implemented methods for retrieving and resolving transaction attempts during recovery. - Updated the storage interface to support atomic compare-and-swap operations with index refresh. - Enhanced tests to cover new transaction attempt functionalities and ensure correct behavior.
…vice - Added TransactionAttemptStore to RecoveryService for enhanced transaction recovery. - Implemented methods for retrieving and resolving transaction attempts during recovery. - Updated the storage interface to support atomic compare-and-swap operations with index refresh. - Enhanced tests to cover new transaction attempt functionalities and ensure correct behavior.
- Updated to return a Result for better error handling. - Improved error logging for invalid order IDs in recovery service methods. - Modified to accept transaction attempts and use the correct anchor transaction. - Added tests to verify new behavior for order ID processing and recovery scenarios.
…on monitoring - Added revert classification logic to handle transaction failures more effectively. - Integrated new types to distinguish between , , and states. - Updated order and settlement handlers to utilize the new classification during transaction monitoring. - Enhanced the to support retrieving revert data for failed transactions. - Introduced tests for revert classification to ensure accurate behavior and logging.
…canning - Updated to scan for earlier events by adjusting the starting block based on the receipt's block number. - Modified to treat transient errors during transaction attempts and revert data retrieval as , preventing permanent failure states. - Added tests to ensure correct behavior for both the chain probe and recovery service under error conditions.
- Introduced a new field in to facilitate profitability calculations. - Implemented method to determine if a transaction bump should proceed based on profitability headroom. - Enhanced event logging for cases where the proposed bumped transaction cost exceeds the available profitability. - Updated tests to cover new profitability checks and event emissions.
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (29)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codecov Report❌ Patch coverage is 📢 Thoughts on this report? Let us know! |
Summary
Testing Process
Checklist