groups.list: the three in-call retries of a nil side unit list fail together #6
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
groups.listreadsVP_GetSide({guid = SIDE}).unitsup to three times in one call, because CMO gave nil about one read in twenty on 2026-10-02. On CMOnet's laboratory trial tpl-mixed-dispersed-worldwide (live 2026-10-17, CMOnet 0.7.87, expert-commander r72) 3 of 84 calls still failed with "The units of side Allies can't be read: CMO gave nil, not a list": one 40 s after the scenario loaded, two about 7 and 9 game hours in. The next call, seconds later, read the list each time.Three reads that all fail inside one call, when one in twenty fails on its own, suggest the retries aren't independent: the game doesn't move while the Lua runs, so the second and third read see what the first saw. They add nothing.
Impact is small: the flow runs that met it succeeded, the
groupsnode failing for that cycle. Worth finding, on the lab game, what makesunitsnil (a unit launching, landing or being destroyed in that tick?) and whether another getter gives the side's units then; otherwise drop the in-call retries and let the next call read again.