-
If I move a task to the background, then the task no longer automatically appends its output to the UI (even if that task is the current task).
You have to click on the task again in the left tree to…
-
-
Currently the 30 second timeout on Heroku does mean that unusually expensive actions or high server load can mean that some actions might not complete. In very large tournaments this can occasionally …
-
Currently all APIs that trigger a background task return a job id. The http status code is `201` like all other `PUT` and `POST` requests.
Should we use `202`?
@joelthe1 @sijumoncy
-
# Common Reasons for Background Tasks to Fail in iOS • Andy Ibanez
[https://www.andyibanez.com/posts/common-reasons-background-tasks-fail-ios/](https://www.andyibanez.com/posts/common-reasons-backg…
-
Right now `Task.Run` and `Thread.Start` is used liberally with the responsibility of ending the tasks local to the usage. This won't scale well and can already lead to weird race conditions.
In dis…
peppy updated
4 years ago
-
On iOS, sending the current app into background will result in an assert/app termination.
Some rendering jobs are still being executed, hence making OpenGL calls, which is prohibited by iOS backgrou…
-
## Background/Request
As part of the zero silent errors effort, I found that we have VAOS v1 APIs that are not being used by the FE webapp. I'm not sure what the history is regarding the v1 APIs and …
-
we can consider this lib:
https://github.com/jcoutch/NCrontab-Advanced/commits/master
#1711
#2528
-
## Background
Currently we can query the study index by studyId.
```
query study{
gwasStudy(studyId: "GCST000124")
{
studyId
diseases{
id
}
}
}
```
## Tasks…