add timeout to keep the github check status sane

[todo]

add timeout to keep the github check status sane

[pacospace]

Is this still relevant?

It is not implemented yet actually. Nor the best solution has been selected for implementation. wdyt @fridex ?

[pacospace]

https://github.com/thoth-station/Qeb-Hwt/blob/a8ed3cd6fd5c94667eb09c24592af99cc1592d55/app.py#L150-L155

This issue was generated by todo based on a TODO comment in a8ed3cd when #6 was merged. cc @goern.

What we want is a way to monitor created check runs (https://developer.github.com/v3/checks/runs/#get-a-check-run)?

There are two cases to be taken into account:

• If the PR is opened and user-api gives back error we do not create check run with in progress state but we directly put it in failed state: Sorry, internal error, Qeb-Hwt will come back to you soon. We need to collect this type of messages.

• if the PR is opened and user-api is started, the check run goes to in progress state. To have a timeout we need another service that know the check runs in progress and check their creation date, if that reaches the maximum time we set, it will put the check run in failed state, with timeout error: Sorry services exceed timeout! Open an issue in Qeb-Hwt. We need to collect this type of messages.

We could make the creation of issues automatically so we track the errors? @goern

[fridex]

Is this still relevant?

[pacospace]

there is a conclusion state in check run specific timed_out https://docs.github.com/en/rest/reference/checks#runs

[sesheta]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[sesheta]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

[pacospace]

component deprecated!