Skip to content

Comments

fix: notify client of timeout and cleanup#469

Merged
MichalPrincNXP merged 2 commits intoEmbeddedRPC:mainfrom
elupus:arbitrator-timeout
Feb 23, 2026
Merged

fix: notify client of timeout and cleanup#469
MichalPrincNXP merged 2 commits intoEmbeddedRPC:mainfrom
elupus:arbitrator-timeout

Conversation

@elupus
Copy link
Contributor

@elupus elupus commented Sep 4, 2025

Pull request

Choose Correct

  • bug
  • feature

Describe the pull request

When transport times out, and the client is woken up. It should be informed
that it's message buffer is invalid, as well as given the reason for it's wakeup.

Set the status of the codec to the correct error, so
a correct error handler is triggered in the client.

To Reproduce

Trigger a timeout in underlying protocol, when a client is waiting for a response.

Expected behavior

Client is signaled that a timeout occured.

Screenshots

Desktop (please complete the following information):

  • OS:
  • eRPC Version:

Steps you didn't forgot to do

  • I checked if other PR isn't solving this issue.
  • I read Contribution details and did appropriate actions.
  • PR code is tested.
  • PR code is formatted.
  • Allow edits from maintainers pull request option is set (recommended).

Additional context

@elupus elupus mentioned this pull request Sep 4, 2025
7 tasks
When transport times out or has a reception failure,
it should inform readers that it's message buffer is
invalid.

Set the status of the codec to the error, so
a correct error handler is triggered in the client.
@MichalPrincNXP MichalPrincNXP merged commit 4a28864 into EmbeddedRPC:main Feb 23, 2026
8 checks passed
@MichalPrincNXP
Copy link
Member

Thank you for the effort

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

Development

Successfully merging this pull request may close these issues.

2 participants