[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
  1. https://travis-ci.org/Chatie/wechaty/jobs/211306521#L811
  2. https://travis-ci.org/Chatie/wechaty/jobs/211306523#L811
  3. https://travis-ci.org/Chatie/wechaty/jobs/211306375#L808
  4. https://travis-ci.org/Chatie/wechaty/jobs/211252499#L811
  5. https://travis-ci.org/Chatie/wechaty/jobs/212333837#L845

Potential Possible Solutions:

  1. use initAsync to replace init in WechatyBro, and retry 3 times, wait 300ms each time.

Issue Analytics

  • State:closed
  • Created 7 years ago
  • Comments:15 (13 by maintainers)

github_iconTop GitHub Comments

1reaction
JasLincommented, Mar 28, 2017

@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 bash

ping wx.qq.com , it’s ok

bash-4.3# ping wx.qq.com
PING wx.qq.com (101.227.160.102): 56 data bytes
64 bytes from 101.227.160.102: seq=0 ttl=37 time=0.342 ms
64 bytes from 101.227.160.102: seq=1 ttl=37 time=0.386 ms
64 bytes from 101.227.160.102: seq=2 ttl=37 time=0.370 ms
64 bytes from 101.227.160.102: seq=3 ttl=37 time=0.292 ms

ping qq.com , it’s bad address

bash-4.3# ping qq.com
ping: bad address 'qq.com'

ping baidu.com , it’s bad address also.

then, i cat /etc/resolv.conf

bash-4.3# cat /etc/resolv.conf
# Generated by dhcpcd from eth0.dhcp
# /etc/resolv.conf.head can replace this line
nameserver 192.168.65.1
# /etc/resolv.conf.tail can replace this line
nameserver 114.114.114.114
nameserver 114.114.115.115

even more, i sepecify dns on docker run container with --dns=114.114.114.114 , and cat the resolv.conf

bash-4.3# cat /etc/resolv.conf
nameserver 114.114.114.114
nameserver 114.114.114.114
nameserver 114.114.115.115

the problem still the same as above.(qq.com and baidu.com is bad address) even the wx.qq.com is bad too

0reactions
huancommented, Oct 8, 2017

This issue should be fixed at v0.10 or above.

Read more comments on GitHub >

github_iconTop 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 >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found