求puppeteer问题的解决方法····

看起来没有解决办法呢··· 都没人看····

3 个赞

koishi-plugin-puppeteer提示未找到index.html - 互助 - Koishi Forum

你现在的问题并没有表现出相似的特征,很难认为是相同原因;但是既然暂时没有其他思路,或许你可以试试其中的解决方案,也就是更换浏览器。因为插件本身都能在其他用户环境下 work,假设你的本地环境有问题比较 convincing。

3 个赞

好的,我试试····

3 个赞

我用的Windows····

3 个赞

Windows 也一样需要排查浏览器。因为对 puppeteer 来说,报错 connection closed 就是其连接的浏览器 tab 在关闭后被 puppeteer 访问了。虽然目前看不出具体的问题原因,但是排查一下浏览器应该是比较直观的思路。

4 个赞

我确定了一个大致的方向··· 插件大概是都没问题的,问题可能是出在了我系统上,我Windows服务器今天好了我把备份全都弄到服务器上正常显示了,但是我本地的系统不会正常显示。

3 个赞

求puppeteer问题的解决方法···· - #10,来自 tang1158 浏览器昨天有人别人大佬看了下 说是没问题···· 那么问题应该是出在我系统了····· 以前到是没问题来着····

4 个赞

2024-05-09 17:13:27 [I] assets missing config “selfUrl”, fallback to “file:” scheme
2024-05-09 17:13:28 [I] puppeteer chrome executable found at C:\Program Files\Google\Chrome\Application\chrome.exe
2024-05-09 17:13:28 [I] server server listening at http://127.0.0.1:5140
2024-05-09 17:13:28 [I] console webui is available at http://127.0.0.1:5140
2024-05-09 17:13:28 [E] app Error: Protocol error: Connection closed. Most likely the page has been closed.
at assert (C:\Users\Administrator\AppData\Roaming\Koishi\Desktop\data\instances\default\node_modules\koishi-plugin-puppeteer\node_modules\puppeteer-core\lib\cjs\puppeteer\util\assert.js:18:15)
at CdpPage.close (C:\Users\Administrator\AppData\Roaming\Koishi\Desktop\data\instances\default\node_modules\koishi-plugin-puppeteer\node_modules\puppeteer-core\lib\cjs\puppeteer\cdp\Page.js:864:32)
at default_1.start (C:\Users\Administrator\AppData\Roaming\Koishi\Desktop\data\instances\default\node_modules\koishi-plugin-puppeteer\lib\canvas.js:152:24)
at async C:\Users\Administrator\AppData\Roaming\Koishi\Desktop\data\instances\default\node_modules@cordisjs\core\lib\index.cjs:1057:7
at async Promise.all (index 0)
at async Proxy.flush (C:\Users\Administrator\AppData\Roaming\Koishi\Desktop\data\instances\default\node_modules@cordisjs\core\lib\index.cjs:91:7)
at async Proxy.start (C:\Users\Administrator\AppData\Roaming\Koishi\Desktop\data\instances\default\node_modules@cordisjs\core\lib\index.cjs:177:5)
at async start (C:\Users\Administrator\AppData\Roaming\Koishi\Desktop\data\instances\default\node_modules\koishi\lib\worker\index.js:149:3)
2024-05-09 17:13:35 [W] app Error: property koishi.database is not registered, declare it as inject to suppress this warning
at checkInject (C:\Users\Administrator\AppData\Roaming\Koishi\Desktop\data\instances\default\node_modules@cordisjs\core\lib\index.cjs:807:38)
at Object.get (C:\Users\Administrator\AppData\Roaming\Koishi\Desktop\data\instances\default\node_modules@cordisjs\core\lib\index.cjs:817:11)
at Object.get (C:\Users\Administrator\AppData\Roaming\Koishi\Desktop\data\instances\default\node_modules@cordisjs\core\lib\index.cjs:971:31)
at Object.get (C:\Users\Administrator\AppData\Roaming\Koishi\Desktop\data\instances\default\node_modules@cordisjs\core\lib\index.cjs:814:29)
at Object.get (C:\Users\Administrator\AppData\Roaming\Koishi\Desktop\data\instances\default\node_modules@cordisjs\core\lib\index.cjs:845:22)
at Reflect.get ()
at Object.get (C:\Users\Administrator\AppData\Roaming\Koishi\Desktop\data\instances\default\node_modules@cordisjs\core\lib\index.cjs:244:22)
at ctx.console.addListener.authority (C:\Users\Administrator\AppData\Roaming\Koishi\Desktop\data\instances\default\node_modules@koishijs\plugin-sandbox\lib\index.js:236:27)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async WebSocket.receive (C:\Users\Administrator\AppData\Roaming\Koishi\Desktop\data\instances\default\node_modules@koishijs\console\lib\index.js:127:21)
2024-05-09 17:14:00 [W] app Error: property koishi.database is not registered, declare it as inject to suppress this warning
at checkInject (C:\Users\Administrator\AppData\Roaming\Koishi\Desktop\data\instances\default\node_modules@cordisjs\core\lib\index.cjs:807:38)
at Object.get (C:\Users\Administrator\AppData\Roaming\Koishi\Desktop\data\instances\default\node_modules@cordisjs\core\lib\index.cjs:817:11)
at Object.get (C:\Users\Administrator\AppData\Roaming\Koishi\Desktop\data\instances\default\node_modules@cordisjs\core\lib\index.cjs:971:31)
at Object.get (C:\Users\Administrator\AppData\Roaming\Koishi\Desktop\data\instances\default\node_modules@cordisjs\core\lib\index.cjs:814:29)
at Object.get (C:\Users\Administrator\AppData\Roaming\Koishi\Desktop\data\instances\default\node_modules@cordisjs\core\lib\index.cjs:845:22)
at Reflect.get ()
at Object.get (C:\Users\Administrator\AppData\Roaming\Koishi\Desktop\data\instances\default\node_modules@cordisjs\core\lib\index.cjs:244:22)
at ctx.console.addListener.authority (C:\Users\Administrator\AppData\Roaming\Koishi\Desktop\data\instances\default\node_modules@koishijs\plugin-sandbox\lib\index.js:236:27)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async WebSocket.receive (C:\Users\Administrator\AppData\Roaming\Koishi\Desktop\data\instances\default\node_modules@koishijs\console\lib\index.js:127:21)

有大佬看看是什么意思么····

2 个赞

一个报错:连接关闭,可能由于页面已关闭
一个警告: koishi.database 没有注册,系统建议使用inject声明

3 个赞

怎么解决报错呢···

2 个赞

大佬,你试试把puppeteer这个插件停用后再启动然后再停用··· 看下它会不会出现自己占用自己的情况···




重启了一下koishi
image

启动后再停用就会变成上面三张截图,我在我正常服务器上这样试了一下也会变成被占用然后功能失效,但是重启一下就正常,我本地就不会正常显示了·····

2 个赞

并没有复现出来,主要是我koishi也不在本地

3 个赞

好吧··· 也许用我的完全备份或许会复现出来···

2 个赞

用新的系统··· 重新安装也会出现这个问题···· koishi官方能不能看下····

2 个赞

能看下系统的版本号和浏览器的版本号吗?

3 个赞

我也遇到过,重启整个koishi就好了

3 个赞

开发模式也出现相同问题:
1.puppeteer本体提示“此插件将会提供 component:html 服务,但此服务已被其他插件实现。”


2.依赖puppeteer插件显示黄点且无法使用

3.重启koishi可以解决,但模块热替换会重新出错

Chrome版本 124.0.6367.158(正式版本) (64 位)

System:
OS: Windows 11 10.0.22631
CPU: (20) x64 13th Gen Intel(R) Core™ i9-13900H

Binaries:
Node: 20.12.1
Yarn: 4.1.1

Koishi:
Core: 4.17.6
Console: 5.28.4

3 个赞


77eb138e9c0625f47b294d5c50b05c7e
唔··· 主题上好像发了···
环境信息···
System:
OS: Windows 10 10.0.19045
CPU: (8) x64 Intel(R) Core™ i7-8700 CPU @ 3.20GHz

Binaries:
Node: 20.3.1
Yarn: 4.0.1

Koishi:
Core: 4.17.5
Console: 5.28.4
Koishi Desktop: 1.0.0

2 个赞

诶? 你不是说··· 没复现出来问题嘛···?

2 个赞

今天给插件做新功能,用开发模式才出现的 :sob: :sob: :sob:

4 个赞