Long term issue on my todo list which I never got around to look into:
We messed with the various *MODULECALL() macros so that they now don't consist any more of a single for()-loop. This means that "break" now might behave differently than it did previously. Someone should go through all places where *MODULECALL is used and check if "break" is used and if does The Right Thing (tm).
Symptoms in case "break" were used in the wrong way: "return HALT;" in a module wouldn't stop other modules from being called (e.g. user module HALTs, but network modules are still called?).
Long term issue on my todo list which I never got around to look into:
We messed with the various *MODULECALL() macros so that they now don't consist any more of a single for()-loop. This means that "break" now might behave differently than it did previously. Someone should go through all places where *MODULECALL is used and check if "break" is used and if does The Right Thing (tm).
Symptoms in case "break" were used in the wrong way: "return HALT;" in a module wouldn't stop other modules from being called (e.g. user module HALTs, but network modules are still called?).
<!-- github-sync-id:3004024 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Long term issue on my todo list which I never got around to look into:
We messed with the various *MODULECALL() macros so that they now don't consist any more of a single for()-loop. This means that "break" now might behave differently than it did previously. Someone should go through all places where *MODULECALL is used and check if "break" is used and if does The Right Thing (tm).
Symptoms in case "break" were used in the wrong way: "return HALT;" in a module wouldn't stop other modules from being called (e.g. user module HALTs, but network modules are still called?).
Hooks which cause this issue