auto-purge weird behavior

[peregrineshahin]

Suppose a run has auto purge on, and the code of the run is bugged and keeps crashing for most/all the games, the question is does it make sense to enter an infinite loop of purging the tasks and resuming/restarting the run?
Solution: don't restart/resume any run automatically after pruging

[dubslow]

yea but what about when the purge is legit and the run should be resumed.

possibly it may make sense to use your solution, since users can still manually restart a run which was correctly purged back into the llr window...?

[peregrineshahin]

yea but what about when the purge is legit and the run should be resumed.

possibly it may make sense to use your solution, since users can still manually restart a run which was correctly purged back into the llr window...?

Yes sure.

[vdbergh]

Dunno. If the run does not restart people also complain (not everyone is aware of the modify hack).

EDIT: I don't feel strongly about this. The server code would be simpler if the run does not auto-restart (this would mean that stop_run() is guaranteed to stop a run, which is currently not the case).

[peregrineshahin]

Dunno. If the run does not restart people also complain (not everyone is aware of the modify hack).

GitHub uses this trick, the same button can have different options
maybe this is the equivalent in bootstrap https://getbootstrap.com/docs/5.3/components/button-group/#nesting