Closed yuudi closed 1 year ago
We could just start with a random number for job id?
We could just start with a random number for job id?
This seems vague for frontend to check if backend has restarted. Frontend may not want to check if a new job-id is in range (previous, previous + 10000)
.
So, I think a new field that use random number would be better.
Thanks for merging #7096
The associated forum post URL from
https://forum.rclone.org
N/A
What is your current rclone version (output from
rclone version
)?What problem are you are trying to solve?
A GUI frontend display backend jobs
How do you think rclone should be changed to solve that?
Currently we have rc api
job/list
to list backend jobs, but because user may restart backend or frontend at anytime, frontend cannot track job byjob_id
because it starts counting from1
on every restart, so we need a new field to help track the job.I thinks a new field
execute_id
would help. It will be generated on every restart and not changed during running. Frontend will know thejob_id
is no longer used when detectexecute_id
changes.I will make a pull request on this later.
How to use GitHub