Closed jrk closed 3 years ago
Very weird. Can you increase the timeout like in https://github.com/puppeteer/puppeteer/issues/782#issuecomment-329429325, so we can test if is only due to the time it takes to load Roam?
I added just {'timeout': 3000000}
on the relevant call (the first document.goto
in signin
)—the other parameters on the page you link report as deprecated and unsupported. The result is it just locking up forever (or presumably for 3000 seconds—I have only waited about 10 minutes so far).
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.
The backup errors should be fixed by #92 🍾.
@jrk Puppeteer is unreliable even on Linux... But Selenium looks much more robust!
I'm closing that issue, but feel free to re-open it if you get new errors.
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).