Conversation
This was referenced Sep 10, 2026
This reverts commit 330affa.
Contributor
Author
|
hi @pierre-rouanet, mind taking a look at this one when you get a chance? a mode switch and a policy load can quietly undo each other. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
fixes #227
a policy change is refused while a mode switch is in flight, but not the other way round. accept a switch while a load is still on its thread and the switch goes home, swaps the other mode's bundle in, then the load lands on top and puts the old mode's params and networks back — with robot.mode still reporting the new one.
also refuses a policy change during the shutdown sit, same reason robot.init is already gated there: a change to the driving network takes the home-first path and stands the robot up out of its sit.
two tests. the load one trips on main first try every time.