Why wait 1 second for internal consistency? #182
-
|
In the quickstart example, there's a 1 second sleep. # Give GitHub some time to reach internal consistency.
await asyncio.sleep(1)What's the background behind this? Is it just for GitHub Apps and is it related to creating the |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
We have run into consistency issues in the past when performing a query against brand-new data. For instance, getting triggered on a new issue and then querying for that issue does not always lead to consistent/equivalent data in the query (e.g. the issue seemingly not existing). It was easiest to just sleep for one second and let GitHub catch up with itself. It's not a regular issue, but when things fail it was easier to just wait than toss the query out when something did go wrong. |
Beta Was this translation helpful? Give feedback.
-
|
That makes sense, thanks 👍 |
Beta Was this translation helpful? Give feedback.
We have run into consistency issues in the past when performing a query against brand-new data. For instance, getting triggered on a new issue and then querying for that issue does not always lead to consistent/equivalent data in the query (e.g. the issue seemingly not existing). It was easiest to just sleep for one second and let GitHub catch up with itself. It's not a regular issue, but when things fail it was easier to just wait than toss the query out when something did go wrong.