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

Coalesce buffer missed a TG message despite 20s deadline #22

New Issue
Open
opened 2019-01-05 07:19:48 +00:00 by mappu04 · 0 comments
mappu04 commented 2019-01-05 07:19:48 +00:00
Owner
Copy Link

A TG user posted a message. Some time later, it was reflected by the link bot back to TG as an uncoalesced message.

This means the message took longer than 20s (+ 10s variable worker interval) to round-trip TG->DC->hub->DC.

Probably this was just caused by large number of DC connections on an underspecced server, and won't happen often.

Perhaps the coalesce buffer should always preserve the most recent message too?

A TG user posted a message. Some time later, it was reflected by the link bot back to TG as an uncoalesced message. This means the message took longer than 20s (+ 10s variable worker interval) to round-trip TG->DC->hub->DC. Probably this was just caused by large number of DC connections on an underspecced server, and won't happen often. Perhaps the coalesce buffer should always preserve the most recent message too?
mappu04 changed title from Coalesce buffer missed a message despite 20s deadline to Coalesce buffer missed a TG message despite 20s deadline 2019-01-05 07:20:03 +00:00
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#22
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?