code.ivysaur.me
/
nmdc-telegramfrontend
1
0
Fork 0
Code Issues 26 Pull Requests Releases 2 Wiki Activity

Catching up messages after hub + link-bot downtime #11

New Issue
Open
opened 2018-06-24 02:25:52 +00:00 by mappu04 · 0 comments
mappu04 commented 2018-06-24 02:25:52 +00:00
Owner
Copy Link

If the hub and link-bot goes down for whatever reason, when they come back up, the linkbot will (A) reconnect to the hub, and (B) suddenly receive all TG messages at once.

This means that

  • there is a race condition, if the hub connection has not completed before the link bot wants to post something to it; leading to Couldn't sync message '...' because: Not connected error messages posted back in TG; and
  • if there were more than ~5 posts by a single user, they would hit a hub-side rate limit (same as #6).
If the hub and link-bot goes down for whatever reason, when they come back up, the linkbot will (A) reconnect to the hub, and (B) suddenly receive all TG messages at once. This means that - there is a race condition, if the hub connection has not completed before the link bot wants to post something to it; leading to `Couldn't sync message '...' because: Not connected` error messages posted back in TG; and - if there were more than ~5 posts by a single user, they would hit a hub-side rate limit (same as #6).
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
master
v1.0.1
v1.0.0
Labels
Clear labels   
bug

   
wishlist
No Label
bug
wishlist
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: code.ivysaur.me/nmdc-telegramfrontend#11
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?