-
Notifications
You must be signed in to change notification settings - Fork 133
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
Timeout on signin step #11
Comments
Very weird. Can you increase the timeout like in puppeteer/puppeteer#782 (comment), so we can test if is only due to the time it takes to load Roam? |
I added just Notably, the Roam load time is not at all an issue when I enable debug mode and visually watch the progress (even just a few seconds before or after this always-repeatable failure in non-debug mode). Is there any way to inspect the status in more detail, short of enabling the non-headless debug mode which seems to just magically work? |
Followup: it works as expected on a relatively conventional Ubuntu 18.04 LTS machine. It fails in the same way on a different Mac on a different network (the same network as the Ubuntu machine). Has this been tested on macOS? |
For now I've worked around this by running it in Docker. (And since that container has no access to my ssh keys, I've also submitted a PR #13 to optionally skip just the final push step.) |
I develop it on my Mac ;) It's less reliable than on Linux, but it does work. Debugging is not easy, between heisenbug, async, not being able to see the gui, and it's hard to do tests. |
I also found Puppeteer flakey and unreliable on macOS in the Node-based roam-backup, too, for what it’s worth. It was less consistently unable to get *anywhere* than this, but still obviously problematic.
|
When running for the first time (locally, with a pipx install on macOS 10.15.4), I consistently get
pyppeteer.errors.TimeoutError: Navigation Timeout Exceeded: 30000 ms exceeded.
seemingly in the first "Opening signin page" step (logs below).This same setup, with the
--debug
flag, shows the Chromium GUI as expected and works with no long lags, right up through the end (where I believe it fails to actually unpack the zip files with a warning that this doesn't work in--debug
mode).The text was updated successfully, but these errors were encountered: