Good catch, and the race is real: two instances can each read an empty order list before either placement is visible, so a per-instance guard passes in both. As far as I can tell from the public PR, the fix limits resting orders per instance (one at a time, expiry-based cancel). I haven't seen anything that serializes entry decisions across instances on one account, and I haven't verified that by running it, so I won't claim it does. Your point about the release path matters too: a shared reservation needs an explicit release on ack, reject and restart, otherwise it becomes the same kind of permanent halt the post describes. For anyone running more than one instance on an account, the safer check is the broker-side order list at placement time, not a local counter.
@arakas4488cmd
About
I audit algorithmic trading bot code for a living — entry/exit logic, order management, risk handling, fee-honest backtests. I've filed 40+ public responsible-disclosure issues against live open-source trading bots, and audited my own bot the same way before offering this to anyone else.
Available for
Nothing here yet.