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

Maybe we shouldn't syncContactsAndRooms per 3 hours #1414

Closed
lijiarui opened this issue Jun 29, 2018 · 10 comments
Closed

Maybe we shouldn't syncContactsAndRooms per 3 hours #1414

lijiarui opened this issue Jun 29, 2018 · 10 comments

Comments

@lijiarui
Copy link
Member

lijiarui commented Jun 29, 2018

see here:

I'm trying to syncContactAndRooms every 3 hours yesterday, but today I got the following result...

All bots cannot receive the user push message and always get the following result... I'm not sure the exact reason, but maybe we shouldn't sync Contact and Room too frequently...

10:56:42 WARN PuppetPadchatManager syncContactsAndRooms() cannot get array result: {"message":"不支持的请求","status":-19}
10:56:42 SILL PuppetPadchatManager syncContactsAndRooms() while() syncing WXSyncContact ...
10:56:42 SILL PadchatRpc rpcCall(WXSyncContact, [])
10:56:42 SILL PadchatRpc initHeartbeat() throttleQueue.subscribe(ws.on(message))
10:56:42 SILL PuppetPadchat startWatchdog() padchatManager.on(heartbeat)
10:56:42 SILL PuppetPadchat startWatchdog() watchdog.on(feed, food={type=undefined, data=ws.on(message)})
10:56:52 WARN PuppetPadchatManager syncContactsAndRooms() cannot get array result: {"message":"不支持的请求","status":-19}
10:56:52 SILL PuppetPadchatManager syncContactsAndRooms() while() syncing WXSyncContact ...
10:56:52 SILL PadchatRpc rpcCall(WXSyncContact, [])
10:56:52 SILL PadchatRpc initHeartbeat() throttleQueue.subscribe(ws.on(message))
10:56:52 SILL PuppetPadchat startWatchdog() padchatManager.on(heartbeat)
10:56:52 SILL PuppetPadchat startWatchdog() watchdog.on(feed, food={type=undefined, data=ws.on(message)})
10:57:02 WARN PuppetPadchatManager syncContactsAndRooms() cannot get array result: {"message":"不支持的请求","status":-19}
10:57:02 SILL PuppetPadchatManager syncContactsAndRooms() while() syncing WXSyncContact ...
10:57:02 SILL PadchatRpc rpcCall(WXSyncContact, [])
10:57:02 SILL PadchatRpc initHeartbeat() throttleQueue.subscribe(ws.on(message))
10:57:02 SILL PuppetPadchat startWatchdog() padchatManager.on(heartbeat)
10:57:02 SILL PuppetPadchat startWatchdog() watchdog.on(feed, food={type=undefined, data=ws.on(message)})
10:57:12 WARN PuppetPadchatManager syncContactsAndRooms() cannot get array result: {"message":"不支持的请求","status":-19}
10:57:12 SILL PuppetPadchatManager syncContactsAndRooms() while() syncing WXSyncContact ...
10:57:12 SILL PadchatRpc rpcCall(WXSyncContact, [])
10:57:12 SILL PadchatRpc initHeartbeat() throttleQueue.subscribe(ws.on(message))
10:57:12 SILL PuppetPadchat startWatchdog() padchatManager.on(heartbeat)
10:57:12 SILL PuppetPadchat startWatchdog() watchdog.on(feed, food={type=undefined, data=ws.on(message)})
10:57:22 WARN PuppetPadchatManager syncContactsAndRooms() cannot get array result: {"message":"不支持的请求","status":-19}
10:57:22 SILL PuppetPadchatManager syncContactsAndRooms() while() syncing WXSyncContact ...
  • When I change the code from server to my local laptop, all works well...
  • When I restart docker on the server, all works well...
@suntong
Copy link
Contributor

suntong commented Jun 30, 2018

Whe you said "all works well", does it means even doing syncContactAndRooms every 3 hours?

@lijiarui
Copy link
Member Author

lijiarui commented Jul 1, 2018

no, just the moment when I restart the code.

@suntong
Copy link
Contributor

suntong commented Jul 1, 2018

OK.

I second that we shouldn't syncContactsAndRooms/Pulling every 3 hours, especially now that it is raising red flag to the WX server, which we should avoid as much as possible.

Many people might live even without pulling at all, like me.

@windmemory
Copy link
Member

The sync logic has been removed since wechaty-puppet-padchat 0.4.4. This issue can be closed.

@suntong
Copy link
Contributor

suntong commented Jul 10, 2018

I was using the latest wechaty-puppet-padchat last night, with the simple wechaty-getting-started example, but saw all of sudden a huge list of "cannot lookup wechat id" (or something similar) dumped to the terminal.

Whatever that logic is, that need to be removed as well.

@windmemory
Copy link
Member

@suntong We are supposed to discuss about the sync issue, so let's move to wechaty-puppet-padchat

Please open an issue in wechaty-puppet-padchat, we will track the issue there :)

@suntong
Copy link
Contributor

suntong commented Jul 11, 2018

Please disregard. Wrong message deleted.

@huan
Copy link
Member

huan commented Jul 12, 2018

@lijiarui Can we close this issue for now?

@huan
Copy link
Member

huan commented Jul 15, 2018

ping @lijiarui

@lijiarui
Copy link
Member Author

done

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

4 participants