task #38
closed
Recurring error causes all recurrences doesn't be generated
Added by lupa18 about 2 years ago. Updated 7 months ago.
Description
Hi ! One issue was moved from a proyect to another and then a error occurs:
- creating recurrence at {:start=>Thu, 02 Feb 2023, :due=>Thu, 02 Feb 2023}
...exception raised. Check output for errors. Either there is bug you may want to report or your db is corrupted.
That prevents the other tasks from being generated :(
Also should be interesting if this happens, the task could be assigned to default account or similar.
Files
| info_redmine.txt (734 Bytes) info_redmine.txt | lupa18, 2023-03-01 18:56 | ||
| redmine_complete_log.txt (6.64 KB) redmine_complete_log.txt | lupa18, 2023-03-01 19:04 |
Updated by cryptogopher almost 2 years ago
Hi,
Thanks for reporting. I will look into it in few days. I had a laptop failure at the end of last year and only now getting up to speed :|
Having exception means, that something very wrong is happening in the code - some unexpected, unusual condition that has not been accounted for. Continuing generation of tasks would risk data integrity. That's why it's justified to stop once something like this happens.
Also should be interesting if this happens, the task could be assigned to default account or similar.
I don't understand the context for this statement. Could you elaborate?
Also: can you please provide /admin/info content of your Redmine installation?
Updated by lupa18 almost 2 years ago
- File info_redmine.txt info_redmine.txt added
- File redmine_complete_log.txt redmine_complete_log.txt added
Hi,
cryptogopher wrote:
Hi,
Thanks for reporting. I will look into it in few days. I had a laptop failure at the end of last year and only now getting up to speed :|
Thanks for your time!
Having exception means, that something very wrong is happening in the code - some unexpected, unusual condition that has not been accounted for. Continuing generation of tasks would risk data integrity. That's why it's justified to stop once something like this happens.
Also should be interesting if this happens, the task could be assigned to default account or similar.
I don't understand the context for this statement. Could you elaborate?
Sorry, I think I miss some important part of the log (I'm attaching complete log for this issue). It seems something related with permissions when you move a task to anocher project and next one will be generated from that moved task.
That's why I think that if the task can't be generated by some user, maybe can be generated by admin user.
Also: can you please provide /admin/info content of your Redmine installation?
Info attached.
thanks again,
Updated by cryptogopher 7 months ago
- Status changed from new to in progress
It took me much longer than expected, but finally I'm catching up and working on reported issues to release few fixes and improvements soon (hopefully :).
I think I have found the source of your issue, but before fixing it I would like to ask some extra questions, to make sure that I'm actually addressing your problem and not something else that also needs fixing.
Sorry, I think I miss some important part of the log (I'm attaching complete log for this issue). It seems something related with permissions when you move a task to anocher project and next one will be generated from that moved task.
That's why I think that if the task can't be generated by some user, maybe can be generated by admin user.
- Could you please let me know the exact snapshot of the plugin code you have installed? To do this you need to get into plugin directory and run
gitcommand as shown below (the directory location on your server can vary):$ cd /var/lib/redmine/plugins/issue_recurring $ git log -1
- Can you recall whether the:
- author of the issue in question (Tareas #7430: Actualizar contenedores (docker) en servidores) and
- the author of the new recurrence to be created (if it was different from the author of original issue) had Redmine permissions to view/edit recurrences?
Updated by cryptogopher 7 months ago
lupa18 wrote in #note-4:
Hi !
Answer 1: commit ef2964467c5278830b5f126e495fbf638c0ba9f5
Ok, so you have pulled updates after error report, because that commit is dated at 2024-01-01.
Answer 2:
- Author of the original issue appear as: "Anonymus"
Is this a copy or reopen/in-place type of recurrence schedule?
- Not sure, how/where could I see that? Last recurrence has been created by a user that has full permissions
Does that mean that recurrence has been created finally? What did you do to overcome the error that you initially reported?
Updated by lupa18 7 months ago
cryptogopher wrote in #note-5:
lupa18 wrote in #note-4:
Hi !
Answer 1: commit ef2964467c5278830b5f126e495fbf638c0ba9f5Ok, so you have pulled updates after error report, because that commit is dated at 2024-01-01.
It appear yes
Answer 2:
- Author of the original issue appear as: "Anonymus"
Is this a copy or reopen/in-place type of recurrence schedule?
- Not sure, how/where could I see that? Last recurrence has been created by a user that has full permissions
Does that mean that recurrence has been created finally? What did you do to overcome the error that you initially reported?
Yes, I don't remember how. Probably I deleted the recurrence and created again, I'm not sure actually.
Updated by cryptogopher 7 months ago
- Status changed from in progress to closed
Applied in changeset issue-recurring-github|be268b026d68bdb1a056e5a3c65011bc308808f9.