Skip to content

send an message/event saying the startup sequence has completed or failed#362

Open
jordaneburton wants to merge 7 commits intomainfrom
issue-307-attempt2
Open

send an message/event saying the startup sequence has completed or failed#362
jordaneburton wants to merge 7 commits intomainfrom
issue-307-attempt2

Conversation

@jordaneburton
Copy link
Copy Markdown
Contributor

@jordaneburton jordaneburton commented Mar 25, 2026

Send Event Logs for Whether the Startup Sequence has Completed or Failed

Description

This pull request enhances the StartupManager component by improving the handling and logging of start-up sequences. The main changes include adding support for tracking when a sequence begins, and updating the component's internal state to store sequence file path.

  • Added a new input port sequenceStarted for receiving notifications when a start-up sequence begins, and implemented the corresponding handler method sequenceStarted_handler. This handler stores the file name of the sequence being run.
  • Updated the deployment topology to connect the new sequenceStarted port between cmdSeq and startupManager.
  • Added a new event StartupSequenceStarted to log when a start-up sequence is initiated.
  • Added a member variable m_sequence_file to StartupManager to keep track of the currently running sequence file.
  • Enhanced the completeSequence_handler to log the completion status of the start-up sequence based on the stored sequence filepath and the command response.

Related Issues/Tickets

Closes #307

How Has This Been Tested?

Tested on a brand new board. Here's event logs from the test:

  • Sequence outputs message on successful completion
  • Sequence outputs error message on unsuccessful completion
cmdSeqFinished cmdSeqErrorsOut

Checklist

  • Written detailed sdd with requirements, channels, ports, commands, telemetry defined and correctly formatted and spelled
  • Have written relevant integration tests and have documented them in the sdd
  • Have done a code review with
  • Have tested this PR on every supported board with correct board definitions

Further Notes / Considerations

@jordaneburton jordaneburton marked this pull request as draft March 26, 2026 00:09
@jordaneburton jordaneburton marked this pull request as ready for review March 26, 2026 01:47
@jordaneburton jordaneburton marked this pull request as draft March 26, 2026 01:49
@jordaneburton
Copy link
Copy Markdown
Contributor Author

I've successfully gotten a working build where the component can read in the file path for the currently running sequence.
I still need to test whether the port for reading in that file path is triggered by ALL sequences, otherwise the handler might get "stuck" on the cmd sequence file path, and may not update for other sequences.

@jordaneburton jordaneburton changed the title send an message/event saying the startup sequence has been initiated send an message/event saying the startup sequence has completed or failed Mar 26, 2026
@jordaneburton
Copy link
Copy Markdown
Contributor Author

I uploaded pics from my testing on the new board. Not sure if these are my exact events though?

@jordaneburton
Copy link
Copy Markdown
Contributor Author

Alright. This issue is done!

@jordaneburton jordaneburton marked this pull request as ready for review April 1, 2026 23:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

[BUG] Startup Sequence "Fails" on Any Sequence Being Cancelled

1 participant