View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007739 | Taler | libeufin-nexus | public | 2023-03-04 15:48 | 2023-11-03 14:32 |
| Reporter | MS | Assigned To | MS | Resolution deadline | |
| Implementer | Reviewer | ||||
| Release signed by | Deployed by | ||||
| Verifier | Communicator | ||||
| Data protection authority notification required | No | ||||
| CSIRT notification required | No | ||||
| Estimated effort (hours) | Actual effort (hours) | 0 | |||
| Fast-track | No | ||||
| Work package | none | ||||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | won't fix | ||
| Target Version | 0.9.4 | ||||
| Summary | 0007739: Creating background tasks should be idempotent. | ||||
| Description | Now it responds with 400, which is not even suitable for a name conflict. The "POST ../schedule" call is responsible. | ||||
| Tags | No tags attached. | ||||
| Agreed that background tasks should be just overridden by the owner, without any idempotent behavior. | |
| This waits 0007890 to be solved and the delivery of NLnet task 5. The dependency is not technical but based on priority. | |
| Well, with new architecture we may not have background tasks configured via REST anymore anyway. Should we keep this open as a reminder that background tasks need to be re-done, or mark "won't fix"? | |
| Was it agreed that Nexus will have in-Kotlin background tasks? IIRC a designer has proposed to have CRON(8) managing Nexus repetitive tasks. That would for sure cut on complexity. | |
| Yes, I think for the new design we proposed for the "background" tasks to be (separate) commands that can be invoked "at will". That said, there could be 3 variants: - one-shot: runs the repetitive task once, next time again via cron/systemd - long-poller: runs the repetitive task repeatedly, internally uses long-polling/notifications to wake up on-demand so things still appear "instantly" - sleep loop: runs the repetetive task in a while (1) { work; sleep; }-loop, so started only once to avoid high-cost of startup Which one(s) is best may depend on the task, but modulo long-polling complexity begin implemented, they can probably be all done by the same command with minor command-line option variations. | |
| Not using background tasks anymore. | |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2023-03-04 15:48 | MS | New Issue | |
| 2023-03-10 13:56 | MS | Note Added: 0019951 | |
| 2023-04-13 18:38 | Florian Dold | Category | nexus => libeufin-nexus |
| 2023-04-13 18:50 | Florian Dold | Project | libeufin => Taler |
| 2023-04-17 09:45 | Florian Dold | Target Version | => 0.9.3 |
| 2023-04-17 09:45 | Florian Dold | Assigned To | => MS |
| 2023-04-17 09:45 | Florian Dold | Status | new => assigned |
| 2023-07-24 09:10 | MS | Note Added: 0020367 | |
| 2023-07-24 09:11 | MS | Note Edited: 0020367 | |
| 2023-09-23 13:01 | Christian Grothoff | Target Version | 0.9.3 => 0.9.4 |
| 2023-09-23 13:01 | Christian Grothoff | Note Added: 0020525 | |
| 2023-09-25 09:50 | MS | Note Added: 0020539 | |
| 2023-09-25 09:54 | Christian Grothoff | Note Added: 0020540 | |
| 2023-11-03 14:32 | MS | Status | assigned => closed |
| 2023-11-03 14:32 | MS | Resolution | open => won't fix |
| 2023-11-03 14:32 | MS | Note Added: 0020624 |