Skip to content

fix: framework: store retain flag of messages published before connected#1798

Merged
hikinggrass merged 1 commit into
mainfrom
bugfix/framework-store-retain-flag
Feb 12, 2026
Merged

fix: framework: store retain flag of messages published before connected#1798
hikinggrass merged 1 commit into
mainfrom
bugfix/framework-store-retain-flag

Conversation

@hikinggrass
Copy link
Copy Markdown
Member

Describe your changes

If this flag is not stored the retained flag is accidentally dropped which can lead to issues further down the line

This mostly would be an issue in the framework manager which publishes a few topics on startup such as everest/interfaces which must be retained for modules to receive their payload later. If the flag is not set the module would try to get() this data only to timeout with a "Timeout while waiting for result of get()" error message, terminating the startup of the module

Issue ticket number and link

Checklist before requesting a review

  • I have performed a self-review of my code
  • I have made corresponding changes to the documentation
  • I read the contribution documentation and made sure that my changes meet its requirements

…cted

If this flag is not stored the retained flag is accidentally dropped which can lead to issues further down the line

This mostly would be an issue in the framework manager which publishes a few topics on startup such as everest/interfaces which must be retained for modules to receive their payload later.
If the flag is not set the module would try to get() this data only to timeout with a "Timeout while waiting for result of get()" error message, terminating the startup of the module

Signed-off-by: Kai-Uwe Hermann <kai-uwe.hermann@pionix.de>
@hikinggrass hikinggrass added this pull request to the merge queue Feb 12, 2026
Merged via the queue into main with commit b7925fc Feb 12, 2026
11 of 12 checks passed
@hikinggrass hikinggrass deleted the bugfix/framework-store-retain-flag branch February 12, 2026 21:55
Dalachowsky pushed a commit to Dalachowsky/everest-core that referenced this pull request Feb 20, 2026
…cted (EVerest#1798)

If this flag is not stored the retained flag is accidentally dropped which can lead to issues further down the line

This mostly would be an issue in the framework manager which publishes a few topics on startup such as everest/interfaces which must be retained for modules to receive their payload later.
If the flag is not set the module would try to get() this data only to timeout with a "Timeout while waiting for result of get()" error message, terminating the startup of the module

Signed-off-by: Kai-Uwe Hermann <kai-uwe.hermann@pionix.de>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working framework

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants