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

[Bug] Remote Modules - Deactivation on on host; Reactivation on client #62

Open
LukePiewalker opened this issue Aug 14, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@LukePiewalker
Copy link
Contributor

Version

Development

What is affected by the bug?

Module state of remote module is not displayed in the correct status upon reactivation from the client.

When does the bug occur?

After deactivating a remote (hardware) module on the host, reloading, and activating (cause after reload the module is not displayed as active in the manager GUI) on the client makes the module accessible again, yet it is still listed as deactivated in the manager GUI on the host.

How do we replicate the issue?

  • Set up a remote module i.e. a simple switch_dummy with which I tested it (did only use the SwitchDummy, not the SwitchInterfuse) on one machine (Win10)
  • Connecting to the remote module from another machine (Win10)
  • Deactivating the remote module on the host machine
  • Pressing "Reload", then "Activate" on the client machine

Expected behavior

The manager GUI on the host PC should display the correct module state.

Relevant log output

No response

Additional Comments

No response

Contact Details

[email protected]

@LukePiewalker LukePiewalker added the bug Something isn't working label Aug 14, 2023
@LukePiewalker LukePiewalker changed the title [Bug] Remote modules - Deactivation on on host; Reactivation on client [Bug] Remote Modules - Deactivation on on host; Reactivation on client Aug 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant