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

[Bug] 以下这四个问题经常出现 不知道是否有解决办法 #400

Open
liuguangrui123 opened this issue May 17, 2023 · 1 comment

Comments

@liuguangrui123
Copy link

liuguangrui123 commented May 17, 2023

Environment

- wechaty:0.65
- wechaty-puppet: "wechaty-puppet-padlocal"�
- wechaty-puppet-service: 
- wechaty-plugin-contrib: 
- token type: padlocal|wxwork|xp
- the version of wechaty docker container: [0.65]

Description

问题 1 error while syncing onpush: VError: [tid:fffa56b8] request has been cancelled for reason:SERVER_ERROR: 4 DEADLINE_EXCEEDED: Deadline exceeded� 。

问题 2  onfig unhandledRejection: VError: [tid:1ccf755b] request has been cancelled for reason: SERVER_ERROR: 2 UNKNOWN: [tid:1ccf755b] internal error�

问题 3 ERR Config process.on(unhandledRejection) promise.catch(longlink socket connect timeout)Config IOError [VError]: longlink socket connect timeout�

问题4 明明已经在客户端已经退出了。查看wechaty 网关日志 貌似已经进入死循环了。

:45:53 VERB StateSwitch <PuppetPadlocal> off(true) <- (pending)
03:46:03 VERB StateSwitch <PuppetPadlocal> on(pending) <- (false)
03:46:04 INFO [PuppetPadlocal] start login with type: AutoLogin

以上这四个问题 总是不定期的出现、也没有具体的解决办法。  不确定是不是产品的bug?网管服务也不稳定?每次重启经常起不来。市面上有没有类似wechaty的产品、要求服务要稳定那种、付费也是可以接受的。

Minimum reproducible code

问题 1 error while syncing onpush: VError: [tid:fffa56b8] request has been cancelled for reason:SERVER_ERROR: 4 DEADLINE_EXCEEDED: Deadline exceeded�

2023-05-09 10:38:01 02:38:01 ERR [PadLocalClient] error while syncing onpush: VError: [tid:fffa56b8] request has been cancelled for reason: SERVER_ERROR: 4 DEADLINE_EXCEEDED: Deadline exceeded
2023-05-09 10:38:01 at Request._failAllPendingRequest (/wechaty/node_modules/padlocal-client-ts/src/Request.ts:334:15)
2023-05-09 10:38:01 at ClientDuplexStreamImpl. (/wechaty/node_modules/padlocal-client-ts/src/Request.ts:82:12)
2023-05-09 10:38:01 at ClientDuplexStreamImpl.emit (events.js:400:28)
2023-05-09 10:38:01 at ClientDuplexStreamImpl.emit (domain.js:470:12)
2023-05-09 10:38:01 at Object.onReceiveStatus (/wechaty/node_modules/@grpc/grpc-js/src/client.ts:670:18)
2023-05-09 10:38:01 at Object.onReceiveStatus (/wechaty/node_modules/@grpc/grpc-js/src/client-interceptors.ts:389:48)
2023-05-09 10:38:01 at /wechaty/node_modules/@grpc/grpc-js/src/call-stream.ts:276:24
2023-05-09 10:38:01 at processTicksAndRejections (internal/process/task_queues.js:77:11)
2023-05-09 10:38:01 at runNextTicks (internal/process/task_queues.js:64:3)
2023-05-09 10:38:01 at listOnTimeout (internal/timers.js:526:9)
2023-05-09 10:38:01 at processTimers (internal/timers.js:500:7)
2023-05-09 10:38:01 02:38:01 ERR [PadLocalClient] error while syncing onpush: VError: [tid:af7fdd84] subRequest timeout
2023-05-09 10:38:01 at Timeout. (/wechaty/node_modules/padlocal-client-ts/src/Request.ts:133:46)
2023-05-09 10:38:01 at listOnTimeout (internal/timers.js:557:17)
2023-05-09 10:38:01 at processTimers (internal/timers.js:500:7)�


问题 2 onfig unhandledRejection: VError: [tid:1ccf755b] request has been cancelled for reason: SERVER_ERROR: 2 UNKNOWN: [tid:1ccf755b] internal error�

2023-05-09 10:38:05 02:38:05 ERR Config unhandledRejection: VError: [tid:1ccf755b] request has been cancelled for reason: SERVER_ERROR: 2 UNKNOWN: [tid:1ccf755b] internal error
2023-05-09 10:38:05 at Request._failAllPendingRequest (/wechaty/node_modules/padlocal-client-ts/src/Request.ts:334:15)
2023-05-09 10:38:05 at ClientDuplexStreamImpl. (/wechaty/node_modules/padlocal-client-ts/src/Request.ts:82:12)
2023-05-09 10:38:05 at ClientDuplexStreamImpl.emit (events.js:400:28)
2023-05-09 10:38:05 at ClientDuplexStreamImpl.emit (domain.js:470:12)
2023-05-09 10:38:05 at Object.onReceiveStatus (/wechaty/node_modules/@grpc/grpc-js/src/client.ts:670:18)
2023-05-09 10:38:05 at Object.onReceiveStatus (/wechaty/node_modules/@grpc/grpc-js/src/client-interceptors.ts:389:48)
2023-05-09 10:38:05 at /wechaty/node_modules/@grpc/grpc-js/src/call-stream.ts:276:24
2023-05-09 10:38:05 at processTicksAndRejections (internal/process/task_queues.js:77:11) [object Promise]
2023-05-09 10:38:05 02:38:05 ERR Config ###########################
2023-05-09 10:38:05 02:38:05 ERR Config process.on(unhandledRejection) promise.catch([tid:1ccf755b] request has been cancelled for reason: SERVER_ERROR: 2 UNKNOWN: [tid:1ccf755b] internal error)
2023-05-09 10:38:05 Config SubRequestCancelError [VError]: [tid:1ccf755b] request has been cancelled for reason: SERVER_ERROR: 2 UNKNOWN: [tid:1ccf755b] internal error
2023-05-09 10:38:05 at Request._failAllPendingRequest (/wechaty/node_modules/padlocal-client-ts/src/Request.ts:334:15)
2023-05-09 10:38:05 at ClientDuplexStreamImpl. (/wechaty/node_modules/padlocal-client-ts/src/Request.ts:82:12)
2023-05-09 10:38:05 at ClientDuplexStreamImpl.emit (events.js:400:28)
2023-05-09 10:38:05 at ClientDuplexStreamImpl.emit (domain.js:470:12)
2023-05-09 10:38:05 at Object.onReceiveStatus (/wechaty/node_modules/@grpc/grpc-js/src/client.ts:670:18)
2023-05-09 10:38:05 at Object.onReceiveStatus (/wechaty/node_modules/@grpc/grpc-js/src/client-interceptors.ts:389:48)
2023-05-09 10:38:05 at /wechaty/node_modules/@grpc/grpc-js/src/call-stream.ts:276:24
2023-05-09 10:38:05 at processTicksAndRejections (internal/process/task_queues.js:77:11) {
2023-05-09 10:38:05 jse_shortmsg: '[tid:1ccf755b] request has been cancelled for reason: SERVER_ERROR',
2023-05-09 10:38:05 jse_cause: Error: 2 UNKNOWN: [tid:1ccf755b] internal error
2023-05-09 10:38:05 at Object.callErrorFromStatus (/wechaty/node_modules/@grpc/grpc-js/src/call.ts:81:24)
2023-05-09 10:38:05 at Object.onReceiveStatus (/wechaty/node_modules/@grpc/grpc-js/src/client.ts:670:32)
2023-05-09 10:38:05 at Object.onReceiveStatus (/wechaty/node_modules/@grpc/grpc-js/src/client-interceptors.ts:389:48)
2023-05-09 10:38:05 at /wechaty/node_modules/@grpc/grpc-js/src/call-stream.ts:276:24
2023-05-09 10:38:05 at processTicksAndRejections (internal/process/task_queues.js:77:11) {
2023-05-09 10:38:05 code: 2,
2023-05-09 10:38:05 details: '[tid:1ccf755b] internal error',
2023-05-09 10:38:05 metadata: Metadata { internalRepr: [Map], options: {} }
2023-05-09 10:38:05 },
2023-05-09 10:38:05 jse_info: {},
2023-05-09 10:38:05 reason: 1
2023-05-09 10:38:05 }
2023-05-09 10:38:05 (node:41) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 5)�


问题 3 ERR Config process.on(unhandledRejection) promise.catch(longlink socket connect timeout)Config IOError [VError]: longlink socket connect timeout�

05:20:35 ERR Config ###########################
05:20:35 ERR Config process.on(unhandledRejection) promise.catch(longlink socket connect timeout)
Config IOError [VError]: longlink socket connect timeout
at Timeout. (/wechaty/node_modules/padlocal-client-ts/src/link/WeChatLongLinkProxy.ts:365:25)
at listOnTimeout (node:internal/timers:559:17)
at processTimers (node:internal/timers:502:7) {
jse_shortmsg: 'longlink socket connect timeout',
jse_info: {},
cause: [Function: ve_cause]
}�


问题4 明明已经在客户端已经退出了。查看wechaty 网关日志 貌似已经进入死循环了。

:45:53 VERB StateSwitch off(true) <- (pending)
03:46:03 VERB StateSwitch on(pending) <- (false)
03:46:04 INFO [PuppetPadlocal] start login with type: AutoLogin
03:46:15 VERB StateSwitch off(pending) <- (false)
03:46:15 VERB StateSwitch off(true) <- (pending)
03:46:25 VERB StateSwitch on(pending) <- (false)
03:46:26 INFO [PuppetPadlocal] start login with type: AutoLogin
03:46:37 VERB StateSwitch off(pending) <- (false)
03:46:37 VERB StateSwitch off(true) <- (pending)
03:46:47 VERB StateSwitch on(pending) <- (false)
03:46:47 INFO [PuppetPadlocal] start login with type: AutoLogin
03:46:58 VERB StateSwitch off(pending) <- (false)
03:46:58 VERB StateSwitch off(true) <- (pending)
03:47:08 VERB StateSwitch on(pending) <- (false)
03:47:09 INFO [PuppetPadlocal] start login with type: AutoLogin

@hayate-hsu
Copy link

我也遇到这个问题。上个月使用就很流畅,现在经常性报错。

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants