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

Debug console only works intermitantly #60

Closed
kimburgess opened this issue May 29, 2020 · 5 comments
Closed

Debug console only works intermitantly #60

kimburgess opened this issue May 29, 2020 · 5 comments
Assignees

Comments

@kimburgess
Copy link
Contributor

Describe the bug
When monitoring a module and using the debug console, functionality of this is intermittent.

It's possible to see log output on the backend, but this is not rendering within the Backoffice "Debug Console" view.

Note: issue may not be front end related (required further investigation), but creating this here for tracking / linking as it is where the symptom is visible.

To Reproduce
Steps to reproduce the behavior:

  1. Choose a system
  2. Go to modules
  3. Start monitoring a module instance
  4. Watch debug console and backend logs simultaneously.

Expected behavior
Module debug output should always reflect in both locations.

@kimburgess kimburgess added the bug label May 29, 2020
@stakach stakach assigned benhoad and unassigned MrYuion Jun 9, 2020
@stakach
Copy link
Member

stakach commented Jun 15, 2020

@benhoad solving this and the websocket Auth issue would be awesome.

@stakach stakach assigned alexchuvand and unassigned benhoad Jun 26, 2020
@alexchuvand alexchuvand assigned MrYuion and unassigned alexchuvand Jul 10, 2020
@MrYuion
Copy link
Collaborator

MrYuion commented Jul 31, 2020

@kimburgess, is there a module I can use in the partner-env to test this?

@kimburgess
Copy link
Contributor Author

If you use the “Logic Example” driver it will generate a message on settings update.

This may be a downstream issue from PlaceOS/core#40 too.

@MrYuion
Copy link
Collaborator

MrYuion commented Aug 10, 2020

@kimburgess, looks to be working as expected on the frontend.

@kimburgess
Copy link
Contributor Author

No probs. Cheers for double checking.

With the knowledge that driver debug state does not persist driver stop/start, I’m almost certain that what originally caused this.

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

No branches or pull requests

5 participants