Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RemoteActionTest sometimes waits endlessly on exeuction state #51

Closed
pLeminoq opened this issue Jan 11, 2022 · 4 comments · Fixed by #60
Closed

RemoteActionTest sometimes waits endlessly on exeuction state #51

pLeminoq opened this issue Jan 11, 2022 · 4 comments · Fixed by #60
Assignees

Comments

@pLeminoq
Copy link
Contributor

pLeminoq commented Jan 11, 2022

Sometimes the remote action test fails on waiting for the execution state. This only happens seldom. Using a debugger, we could see that the state of the action in the data type of the unit remote is EXECUTING. Therefore the following things have to be investigated:

  • Is the event filtered because of a permission issue?
  • Can it happen that the notification of the state change is skipped? 👎
  • Does the RemoteAction handle the notifications correctly?
@DivineThreepwood
Copy link
Member

DivineThreepwood commented Jan 12, 2022

@pLeminoq We performed the debugging on remote side and could see that the action was already marked as executing in the target remote action list, right? Thus, this seems to be a remote issue and we can skip Can it happen that the notification of the state change is skipped?.

@pLeminoq
Copy link
Contributor Author

Yes, you are right. With the notification skip, I meant the observer notification of the remote.

@DivineThreepwood
Copy link
Member

Even when the debugging seems to target the remote site, I would guess that this bug is addressed by the next bco PR that fixes a bug where the action list was not always correctly synchronized with the data builder.

@DivineThreepwood
Copy link
Member

please reopen otherwise.

@DivineThreepwood DivineThreepwood linked a pull request Mar 31, 2022 that will close this issue
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 a pull request may close this issue.

2 participants