Fergal
Fergal
We've started to encounter test flakes under automation 2.0 here: https://github.com/smartcontractkit/chainlink/actions/runs/9517599286/job/26311750004?pr=13555 The only recent change that impacted automation 2.0 was this PR: https://github.com/smartcontractkit/chainlink/pull/13481/files This change was included in automation v1.0.4;...
- Use a dequeueCoordinator to identify which block window we should dequeue from - The dequeueCoordinator examines each block window for minimum dequeue - If no window is eligible for...
Use the dequeueCoordinator to mark block windows as having been reorg'd
Testing with short ID and txHash and log index: ``` ./chaincli keeper debug 45922550481167474801016462395345942974472459369486901665448449256127185529335 0x9d3fa0425351ba3a6be7ac210e7d54df80739ef22477554a9091ee83a2b08b97 3 time=2024-05-29T17:27:41.248+01:00 level=INFO msg="Using config file .env" time=2024-05-29T17:27:41.569+01:00 level=INFO msg="WARNING: no PRIVATE_KEY set: cannot use...
This is just a simple change to test out how we'd emit custom events from capabilities It probably makes sense to hide as much of the beholder interaction as possible...