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

Web_repl file operations don't work with Chromium (Linux). #11

Open
rkompass opened this issue Jun 25, 2024 · 10 comments
Open

Web_repl file operations don't work with Chromium (Linux). #11

rkompass opened this issue Jun 25, 2024 · 10 comments
Labels
bug Something isn't working

Comments

@rkompass
Copy link

Hello,

I have the error: Timeout reached before finding the ending sequence when connecting with the Wemos w600 Pico (robert-hh s port) through the web_repl.
The hierarchy of the few files on the board at first is displayed correctly. Terminal works.
But: When I double-click a file to open in the editor, (or create a new file, after entering it's name) then this error occurrs.
The terminal then also stops echoing my keystrokes.
At the w600 primary terminal (screen /dev/ttyUSB0 115200) then I see (if file doubleclick)

raw REPL; CTRL-B to exit

is displayed without accepting any input (tried also the Ctrl-B: no reaction).

This problem only occurs on my Chromium browser (with Manjaro Linux).

On Firefox the file operations work o.k., as previously tested by Robert.

So perhaps a solution might be to complement the Tested with - list by a list of browsers tested to work.

@rkompass rkompass changed the title File operations don't work with Chromium (Linux). Web_repl file operations don't work with Chromium (Linux). Jun 25, 2024
@vshymanskyy
Copy link
Owner

Sometimes it works, sometimes doesn't. WebREPL is not stable on W600 in general, but it works on ESP8266, ESP32 and Pi Pico W.

@rkompass
Copy link
Author

rkompass commented Jun 25, 2024 via email

@vshymanskyy
Copy link
Owner

@robert-hh this is an interesting observation

@robert-hh
Copy link

I tested that with Google Chrome and it worked.

@robert-hh
Copy link

I installed Brave on my Debian system, and the Viper IDE works fine with a W600. No problem with file operations.
Brave: Version 1.67.119 Chromium: 126.0.6478.114 (Offizieller Build) (64-Bit)

@vshymanskyy
Copy link
Owner

Try doing this:

  • check you're using the latest w600 firmware build
  • ensure only minimal WebREPL code is running, no custom application
  • perform power reset
  • try connecting cleanly

Usually it works after this but it fails if i reconnect to the device, maybe after several times (on my side)

@rkompass
Copy link
Author

Of course I did that. web_repl is started in main.py. After re-plugging the w600 viper-ide is there.

All (including file-) operations work with Firefox (Version 127.0 64-bit for Manjaro Linux) and Brave (Version 1.67.119 Chromium: 126.0.6478.114 (Offizieller Build) (64-Bit)), from the WebRepl.

Only terminal and first directory tree display with pure Chromium (Version 126.0.6478.114 (Offizieller Build) Arch Linux (64-Bit)), and Opera.

At an attempt to do file operations (after clicking a file for display, for example) the above error:
Timeout reached before finding the ending sequence is diplayed in the upper right corner.

Some strange configuration detail with the browsers, I suppose. Probably not worth investigating too much.
No problem with w600 firmware anymore, as Robert stated already :-)

My suggestion again is to only document that, so that users aren't thinking their board or firmware might have a problem.

@vshymanskyy
Copy link
Owner

Got it. Let's leave the ticket open for now

@rkompass
Copy link
Author

Can add: With the Pico W and web_repl it's exactly the same: Firefox, Brave work. Chromium(linux) and Opera same error.
No difference between w600 and Pico W (what is what we want :-)).

@vshymanskyy
Copy link
Owner

Interesting! I'll try it later, probably Opera.

@vshymanskyy vshymanskyy added the bug Something isn't working label Aug 8, 2024
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

3 participants