A client that is also a BlockingQueueWorker that has two motorsDrivers on StaticNavigation fails to start a job Chain, at the client BlockingQueueWorker when it has to block on both Drivers' jobs before continuing with its own job chain.
Each link in the chain starts jobs for downstream Drivers. At some point upstream BlockingQueueWorker and downstream MotorDrivers (also BlockingQueueWorker) when using static nav fails.
Sounds like Corner case since Chains are designed for non-blocking situations like DynamicNavigation, but shouldn't fail.
A client that is also a
BlockingQueueWorker
that has two motorsDrivers onStaticNavigation
fails to start a job Chain, at the clientBlockingQueueWorker
when it has to block on both Drivers' jobs before continuing with its own job chain. Each link in the chain starts jobs for downstream Drivers. At some point upstreamBlockingQueueWorker
and downstreamMotorDriver
s (alsoBlockingQueueWorker
) when using static nav fails.Sounds like Corner case since Chains are designed for non-blocking situations like DynamicNavigation, but shouldn't fail.