We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
uncaughtException GError: 状态同步超过172.392s未响应,5s后尝试重启 at Wechat.checkPolling (/data/node/JF/node_modules/wechat4u/lib/wechat.js:298:19) at Timeout._onTimeout (/data/node/JF/node_modules/wechat4u/lib/wechat.js:319:25) at listOnTimeout (node:internal/timers:569:17) at process.processTimers (node:internal/timers:512:7) { code: 2, details: 'Error: 状态同步超过172.392s未响应,5s后尝试重启\n' + ' at Wechat.checkPolling (/data/node/JF/node_modules/wechat4u/lib/wechat.js:298:19)\n' + ' at Timeout._onTimeout (/data/node/JF/node_modules/wechat4u/lib/wechat.js:319:25)\n' + ' at listOnTimeout (node:internal/timers:569:17)\n' + ' at process.processTimers (node:internal/timers:512:7)' }
I got this error message sometimes and the system is hang and I need to login again anyone know why please?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
uncaughtException GError: 状态同步超过172.392s未响应,5s后尝试重启
at Wechat.checkPolling (/data/node/JF/node_modules/wechat4u/lib/wechat.js:298:19)
at Timeout._onTimeout (/data/node/JF/node_modules/wechat4u/lib/wechat.js:319:25)
at listOnTimeout (node:internal/timers:569:17)
at process.processTimers (node:internal/timers:512:7) {
code: 2,
details: 'Error: 状态同步超过172.392s未响应,5s后尝试重启\n' +
' at Wechat.checkPolling (/data/node/JF/node_modules/wechat4u/lib/wechat.js:298:19)\n' +
' at Timeout._onTimeout (/data/node/JF/node_modules/wechat4u/lib/wechat.js:319:25)\n' +
' at listOnTimeout (node:internal/timers:569:17)\n' +
' at process.processTimers (node:internal/timers:512:7)'
}
I got this error message sometimes and the system is hang and I need to login again anyone know why please?
The text was updated successfully, but these errors were encountered: