This PR removes complex handling to try to track whether a block was issued into consensus to determine if we can register a dependency on the block or not. To replace this handling, we simply look to see if the block was either requested or is pending to determine if the block can be a dependency.
How this works
Dependencies are resolved when:
There was a request over the network for the dependency and that either succeeded or failed
There was an issuer job with this dependency that was itself blocking on a different dependency.
How this was tested
[x] Ran on Fuji
[x] Verified that this approach avoids the error introduced by #3131
Why this should be merged
This PR removes complex handling to try to track whether a block was issued into consensus to determine if we can register a dependency on the block or not. To replace this handling, we simply look to see if the block was either requested or is pending to determine if the block can be a dependency.
How this works
Dependencies are resolved when:
How this was tested