[ci] execute proxyWechaty(init) error: 503, init() without a ready angular env
See original GitHub issue✖ test › puppet-web › bridge › WechatyBro.ding() exception: execute proxyWechaty(init) error: 503, init() without a ready angular env
- https://travis-ci.org/Chatie/wechaty/jobs/211306521#L811
- https://travis-ci.org/Chatie/wechaty/jobs/211306523#L811
- https://travis-ci.org/Chatie/wechaty/jobs/211306375#L808
- https://travis-ci.org/Chatie/wechaty/jobs/211252499#L811
- https://travis-ci.org/Chatie/wechaty/jobs/212333837#L845
Potential Possible Solutions:
- use
initAsyncto replaceinitin WechatyBro, and retry 3 times, wait 300ms each time.
Issue Analytics
- State:
- Created 7 years ago
- Comments:15 (13 by maintainers)
Top Results From Across the Web
execute proxyWechaty(init) error: 503, init() without a ready ...
Error : execute proxyWechaty(init) error: 503, init() without a ready angular ... Run npm run doctor or wechaty run doctor (for docker user), ......
Read more >Changelog | Wechaty - JS.ORG
bot.logonoff()报错【static puppet not found for Wechaty】 #1878 ... [ci] execute proxyWechaty(init) error: 503, init() without a ready angular env #329 ...
Read more >wechaty | Yarn - Package Manager
... [ci] WebDriver Error: "no such session" #756; [ci] execute proxyWechaty(init) error: 503, init() without a ready angular env #329; [ci log] watchdog ......
Read more >[ci] execute proxyWechaty(init) error: 503, init() without a ready ...
@xinbenlv https://github.com/xinbenlv When this issue happens, it means that the Angular.js is not ready inside the Browser. Wechaty will open a browser when...
Read more >Issue · wechaty / wechaty · GitCode
[ci] execute proxyWechaty(init) error: 503, init() without a ready angular env · Cannot send image after restart.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@zixia bro , i had exprience this problem too , it seems docker’s network is unstable. after this error raise , i login to container
docker exec -it robot_test bashping wx.qq.com , it’s ok
ping qq.com , it’s bad address
ping baidu.com , it’s bad address also.
then, i cat /etc/resolv.conf
even more, i sepecify dns on docker run container with
--dns=114.114.114.114, and cat theresolv.confthe problem still the same as above.(qq.com and baidu.com is bad address) even the wx.qq.com is bad too
This issue should be fixed at v0.10 or above.