Content
View differences
Updated by Christophe Bliard over 3 years ago
See [https://appsignal.com/openproject-gmbh/sites/62bf0cc2d2a5e4832c923ff0/exceptions/incidents/8?timestamp=2022-07-29T08%3A46%3A11Z](https://appsignal.com/openproject-gmbh/sites/62bf0cc2d2a5e4832c923ff0/exceptions/incidents/8?timestamp=2022-07-29T08%3A46%3A11Z)
The `ArgumentError` happens because `raise ArgumentError if latest_time < earliest_time || (latest_time - earliest_time) > 1.day` ([source](https://github.com/opf/openproject/blob/8c2457f4ec0b7cbc725317d85aa3408a781b574e/app/models/users/scopes/having_reminder_mail_to_send.rb#L158))
* `latest_time` is current time
* `earliest_time` is the `run_at` field of the job `Notifications::ScheduleReminderMailsJob`, read from the database.
* It raises an error because the time at which the worker runs the job should be before current time, not after, or because it is more than 24 hours in the past.
This error happened three times, each time at the same moment as a deploy:
on 21st October
* Error occurs at 17:34:45+02:00
* Deploy of version 12.4.0.3467f4747a happened at 17:34:46+02:00
Same pattern with the ones on 18th October:
* Errors at 20:18:40+02:00
* Deploy of 12.4.0.d8076b0edf at 20:18:41+02:00
And same pattern with the ones on 8th October:
* Errors at 23:42:29+02:00
* Deploy of 12.3.0.33fd68d2da at 23:42:28+02:00
Reported times may be inaccurate, it depends on when exactly this information is sent to AppSignal, on which node's clock is reporting this time, and if there is a time skew for one of the nodes.
Not sure of why or how this error happens for now. https://appsignal.com/openproject-gmbh/sites/62bf0cc2d2a5e4832c923ff0/exceptions/incidents/8?timestamp=2022-07-29T08%3A46%3A11Z
The `ArgumentError` happens because `raise ArgumentError if latest_time < earliest_time || (latest_time - earliest_time) > 1.day` ([source](https://github.com/opf/openproject/blob/8c2457f4ec0b7cbc725317d85aa3408a781b574e/app/models/users/scopes/having_reminder_mail_to_send.rb#L158))
* `latest_time` is current time
* `earliest_time` is the `run_at` field of the job `Notifications::ScheduleReminderMailsJob`, read from the database.
* It raises an error because the time at which the worker runs the job should be before current time, not after, or because it is more than 24 hours in the past.
This error happened three times, each time at the same moment as a deploy:
on 21st October
* Error occurs at 17:34:45+02:00
* Deploy of version 12.4.0.3467f4747a happened at 17:34:46+02:00
Same pattern with the ones on 18th October:
* Errors at 20:18:40+02:00
* Deploy of 12.4.0.d8076b0edf at 20:18:41+02:00
And same pattern with the ones on 8th October:
* Errors at 23:42:29+02:00
* Deploy of 12.3.0.33fd68d2da at 23:42:28+02:00
Reported times may be inaccurate, it depends on when exactly this information is sent to AppSignal, on which node's clock is reporting this time, and if there is a time skew for one of the nodes.
Not sure of why or how this error happens for now.