Skip to content

Record rosbags for each PA - #1

Open
seijiito-airoa wants to merge 2 commits into
deploy/gui-webserverfrom
deploy/feat/record_rosbag
Open

Record rosbags for each PA#1
seijiito-airoa wants to merge 2 commits into
deploy/gui-webserverfrom
deploy/feat/record_rosbag

Conversation

@seijiito-airoa

Copy link
Copy Markdown
Contributor

No description provided.

@seijiito-airoa seijiito-airoa changed the title Deploy/feat/record rosbag Record rosbags for each PA Mar 10, 2026
Comment on lines 849 to 855
elif action == "next_pa":
if self.phase != "awaiting_pa_next" or self.pending_pa_record is None:
raise RuntimeError(f"Cannot move next PA while phase={self.phase}")
record = self.pending_pa_record
self.pending_pa_record = None
self.pending_pa_label = None
self._commit_pa_and_continue_locked(record)

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is a potential dead-end in the next_pa transition. pending_pa_record is cleared before the next-PA setup fully succeeds.
If start_pa_rosbag(), set_motion_enabled(True), or set_instruction() fails, the state can remain around awaiting_pa_next while the pending record is already gone.
In that case, the PA result modal no longer appears and the operator has no clean way to retry from the UI. Could we keep pending_pa_record until the transition succeeds, or restore it on failure and roll back any partial state such as pa_idx / rosbag startup?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants