occ commands to manage the job list#24551
Conversation
|
By analyzing the blame information on this pull request, we identified @nickvergessen, @icewind1991 and @blizzz to be potential reviewers |
26e2d12 to
79d669c
Compare
I looked a bit into |
exactly |
|
@nickvergessen please update status, PR was merged. Raise doc / QA tickets if applicable. |
|
Done, didn't update this PR, the worker still looks good, but the table change of course is in conflict now. |
d639831 to
4dbf074
Compare
|
We're past feature freeze, move to 9.2 ? @DeepDiver1975 @nickvergessen |
agreed |
4dbf074 to
d1d3b1e
Compare
|
Is there still interest in getting this feature finished ? Not sure how this fits in with the latest changes with bkg jobs |
|
moving to backlog for now unless there is interest and time in reviving this soon and getting it completed |
903148e to
887821d
Compare
| $this->logger = new CommandLogger($output); | ||
|
|
||
| $waitTime = $input->getOption('sleep'); | ||
| while (true) { |
There was a problem hiding this comment.
Any idea how this is expected to be executed? I'm not fan of infinite loops without any escape route, and if this is going to be run as a service the only way to stop the loop would be kill it with fire (aka, sigkill signal).
I think it would be good to capture signals if possible in order to try to make a smooth exit if possible. While this is possible in between the jobs during the sleep time, the challenge is to send some kind of notice to the background job in order to stop it nicely, otherwise the execution thread will likely be running inside the background job without any chance to process the incomming signal, which will lead to the admin to kill the process forcefully.
There was a problem hiding this comment.
signal handling has need added
| protected function execute(InputInterface $input, OutputInterface $output) { | ||
| $this->logger = new CommandLogger($output); | ||
|
|
||
| $waitTime = $input->getOption('sleep'); |
There was a problem hiding this comment.
Maybe we should force a minimum value. I'm not sure if setting a value of 0 will keep the CPU running near 100%
There was a problem hiding this comment.
addressed - there is a minimum of 1 now
887821d to
0296b45
Compare
|
@ownclouders rebase |
|
Hey! I'm GitMate.io! This pull request is being rebased automatically. Please DO NOT push while rebase is in progress or your changes would be lost permanently |
|
Automated rebase with GitMate.io was successful! 🎉 |
b10eca9 to
71a5414
Compare
|
@ownclouders rebase |
|
Hey! I'm GitMate.io! This pull request is being rebased automatically. Please DO NOT push while rebase is in progress or your changes would be lost permanently |
|
Automated rebase with GitMate.io was successful! 🎉 |
71a5414 to
f274363
Compare
|
use owncloud/market#86 which introduces a command to download the latest revocation list from the marketplace. |
f274363 to
3929f66
Compare
|
@DeepDiver1975 Is thisPR still valid? Linking: Merged: #31630 (Adding background:queue commands: status and delete) |
|
No longer relevant, obsolete |
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
ToDo:
introduce select for updatetable lock in query builderselect for update tolock selected job