This is fixed in 2.1.9. I don't see it acknowledged in patch notes, but the most relevant change looks to be viewtopic.php?p=696983

Thanks for the fix!

I just updated my test world here to 2.1 assembler control changes (read on red, write on green) and aside from a few bugs in the test world (I didn't realize before that some quality prod modules are non-integers) all floating point errors are gone. This is great!

https://forums.factorio.com ...

For what it's worth, I would have named the title of this request: "Allow Any Virtual Signal for Inserter Stack Size".

TL;DR:
Allow `Any` virtual signal in `Set stack size` inserter control. Drop boilerplate combinators for exact item+count controlled inserters from three to zero.

The bottom half of the screenshot show current subsystem needed for exact item control, the top half shows the hypothetical feature ...

Fair enough! Out of personal curiosity, I would be interested to know if there are reasonable epsilon calculation fixes which could fix the behavior. Separately (and more broadly), I'd also be interested to hear about considerations around fixed-point arithmetic implementations compared to the ...

I'd like for each gcd batch of productivity crafting to result in an integer amount of recipe finishes to yield expected results. I derive batch size by 100/gcd(100+productivity,100) . The in-game scenario this comes up is switching recipes on machines with productivity modules after exact batch ...