coord_vseqr is already wired (see env) to chan_a_sqr and chan_b_sqr, the two channel sequencers, and to chan_a_drv, channel A’s driver: the only place that learns the tag channel A’s item carried, once it has been driven.
RequirementsFor coord_vseq::body()
p_sequencer.chan_a_sqr, with any tag (e.g. $urandom).fork/join, send one item on p_sequencer.chan_b_sqr whose tag is the value p_sequencer.chan_a_drv recorded for channel A’s item.chan_a_drv.last_tag is only right once channel A’s driver has pulled and processed the item: not when you call start_item on channel A, and not because channel A’s branch comes first in the fork. Reading it early doesn’t error; it returns whatever was recorded last, which at the start of the test is nothing.
One working answer: brokenbench's own fix for this exercise. Try a few runs first.
What changes, against the code you started with:
docker run --pull always --rm -p 127.0.0.1:8787:8787 ghcr.io/adibis/brokenbench-runnerLooking for a runner on this computer…
The first start downloads about 250 MB; after that it starts in seconds and only downloads again when there's an update. Your code goes to the runner on your computer, not to chipdv.io.