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

Swarm - Issue with logs being shown in new Chrome window for any device via it's IP address #446

Open
STSMiner1 opened this issue Nov 2, 2024 · 0 comments

Comments

@STSMiner1
Copy link

STSMiner1 commented Nov 2, 2024

Describe the bug

I've been testing the latest updates that have been pushed to the 'Master Branch' in the last 24 hours that includes the new AxeOS Theme and Swarm updates.

#429 & #430

First device - Logs output works fine, go to Swarm, then click on any IP address for any one of the devices, new Chrome window opens for that device, Logs don't show, even after refreshing / reloading the page, only starts to work after going to the Swarm page for the 2nd device (or any device via it's IP link).

To Reproduce
Steps to reproduce the behavior:

Chrome is the default browser.

  1. Go to 'Logs' for first device, click 'Show Logs' - all will be fine here for the first device.
  2. Click on 'Swarm' - wait for device list to populate.
  3. Click on any one of the devices IP addresses in the list, a new Chrome window will open for that device.

All steps here onwards are done with the 2nd device in the new browser window for it

  1. Click on 'Logs', then 'Show Logs' - nothing gets displayed in the log window for the device, refreshing / reloading the page does not change anything.
  2. Click on 'Swarm' - wait for device list to populate.
  3. Click on 'Logs' then click on 'Show Logs' - logs now show in the lower window.

Expected behavior
Log output to be shown from the device in the window - this is not happening until you populate the 'Swarm' list for that device (or any device when accessed via it's IP address from the first device).

Video of the issue can be found in the OSMU discord in the firmware-testing channel.
Video showing the issue is too big to upload here.

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

1 participant