smartcontractkit / external-initiator

Initiate Chainlink job runs from external sources

smartcontractkit/external-initiator Issues

Reduce integration/CI testing times
Updated 3 years ago
FM service should implement contexts
Updated 3 years ago
No indicators for idle FluxMonitor
Closed 3 years ago3
Increase FM test coverage
Updated 3 years ago1
JobSpec improvements
Updated 3 years ago
FM is starting even if job is not present in the CL node
Closed 3 years ago4
Increase lastSubmittedRound only on successful oracle submission
Closed 3 years ago
Unit tests should be blockchain agnostic
Updated 3 years ago
Initiate a new poll if the stored answer is older than the poll timer and there's no poll in progress
Closed 3 years ago6
Complete WS integration
Closed 3 years ago
FM tests should use mock servers
Closed 3 years ago
Poll timer and heartbeat should be optional
Closed 3 years ago
Heartbeat should reset whenever there's a new round
Closed 3 years ago
Syncing FluxAggregatorState more accurately
Updated 3 years ago
FM should submit on startup if it hasn't participated in the last round
Updated 3 years ago4
New substrate DB migration
Closed 3 years ago2
Clean up logic in FM service
Closed 3 years ago1
Prevent oracle from starting new rounds within the restart delay
Closed 3 years ago1
how to configure external-initiator port
Closed 3 years ago1
failed to start chainlink container in integration test
Closed 4 years ago4