Dmytro Haidashenko
Dmytro Haidashenko
This came up as a follow-up of testing on canary, by QA teams. If an RPC node is newly setup, and still syncing the blockchain, it may not be ready...
Marking it as draft while we are waiting for sec review * Added new endpoint that allows users to submit transaction request to TXM. Primary use case for this endpoint...
- Added `finalized` state to TXM Tx and TxAttempt that signals the inclusion of the corresponding transaction into the block that is deeper than configured finality depth. If the finality...
* Mark block finalized based on FinalityTag or FinalityDepth * Add to Head function that returns LatestFinalizedHead in the chain * Previously, we've kept only `historyDepth` blocks in the cache....
Fix guarantee that the block, used as a start filter in query to verify that event is present on chain, was actually committed before event.
Fixed HeadTracker's flaky test `TestHeadTracker_CallsHeadTrackableCallbacks`. gomega by default uses 1s timeout for `Eventually` assertion. HeadTracker by default has 1s heads sampling interval, which delays fulfilment of the assertion.
The flakiness of the original test might have been caused by CL Node's failure to gracefully shut down in some cases. However, it's unclear why the graceful shutdown issue only...
Cherry-pick from [14236](https://github.com/smartcontractkit/chainlink/pull/14236)