Page built failed: page.click: Timeout 30000ms exceeded.
liby opened this issue · comments
Graph loaded for /home/logseq/graph
page.click: Timeout 30000ms exceeded.
=========================== logs ===========================
waiting for selector ".button >> i.ti-dots"
============================================================
at publish (file:///home/logseq/publish.mjs:119:14)
at async main (file:///home/logseq/publish.mjs:202:5) {
name: 'TimeoutError'
}
Trace file saved to /home/logseq/graph/www/trace.zip
Export failed
I've tried to retry but it still failed.
The failed actions: liby/liby/runs/6140704859?check_suite_focus=true
I have the same problem.
The failed action: https://github.com/xutingzhou/xutingzhou/runs/6140679053?check_suite_focus=true
I follow steps in #28 and try to change the version, but it still did not work.
@liby @xutingzhou Hi both of you, thanks for reporting! I cloned both of your graphs and load in my local nightly Logseq built, but both failed to load. I think this might be an upstream issue. Will need more time to investigate.
The following is the error message displayed:
@pengx17
I tried to download the trace file from the action artifact and view it in the Playwright trace viewer. But it didn't work.
Could not load trace from trace.zip. Make sure to upload a valid Playwright trace.
@pengx17 I tried to download the trace file from the action artifact and view it in the Playwright trace viewer. But it didn't work.
Could not load trace from trace.zip. Make sure to upload a valid Playwright trace.
I guess you directly open it via macOS Archive Utilty. It would recursively unzip the file for you, but we only need to unzip it once.
I did a Git bisect on the Logseq history between 0.6.6 ~ master version, and it seems the first bad version is logseq/logseq@79bc33e
@pengx17
Uh, There are so many changes to the code that it seems difficult to find suspicious parts. sigh~
@pengx17 Uh, There are so many changes to the code that it seems difficult to find suspicious parts. sigh~
I will report this issue to @xyhp915 to take a look. Meanwhile I think you could replace version with 0.6.5, which should work for you @liby and @xutingzhou
@pengx17 Uh, There are so many changes to the code that it seems difficult to find suspicious parts. sigh~
I will report this issue to @xyhp915 to take a look. Meanwhile I think you could replace version with
0.6.5, which should work for you and @xutingzhou
As @xutingzhou says, 0.6.5 doesn't work.
I follow steps in #28 and try to change the version, but it still did not work.
I forgot the script in 0.6.5 is broken. Will rebuilt it and 0.6.6
This issue should have been fixed by logseq/logseq#5061