Callbacks called twice
See original GitHub issueIt’s been a few days that, as far as I can tell from logs, some callbacks are called twice. This leads to all kind of inconsistencies.
Is this a telegraf issue? A telegram issue? I will run more tests as soon as possible, just wanted to know if anyone is experiencing this. I’m on ^3.6.4
and that should jump to latest.
I’ll try with 3.6.10
and let you know.
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Preventing callbacks from accidentally being called twice
Wrap the callback so calling it twice throws an error ... Another option is to keep track of whether the callback has already...
Read more >Javascript callback called twice - Stack Overflow
The function yourCallback is firing twice, so even when I only console.log hello world it returns hello world twice to my browser.
Read more >Callback is called twice in a sigler event - Dash Python
In the next code ( is an example), callback is called twice in every single event. when you show the slider's id the...
Read more >Callback Functions Double Executing? Dont Forget To return
It may not be immediately apparent why a callback executes twice. A common mistake made by early node developers is forgetting to return...
Read more >Callbacks called twice · Issue #25159 · nodejs/node - GitHub
Async library checks if callback was fired twice which should not happen. The issue happens very rarely (once every 1-2 hours on one...
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
Ok man, I’ll be back to you next week hopefully.
3.6.10
seems to work fine.