You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When the custom sort for processes is enabled (env var SORT_PROCESSES_BY_DATE=true), the front processes index return an HTTP error 500. This need to be investigate but the probable cause is that existing processes have empty or missing start/end date.
To Reproduce
Steps to reproduce the behavior:
Enable Custom sort for processes with env var SORT_PROCESSES_BY_DATE=true
Check if there at least one process with an empty end date
Got to /processes
See error
Expected behavior
No error and the custom sort for processes enabled
Describe the bug
When the custom sort for processes is enabled (env var
SORT_PROCESSES_BY_DATE=true
), the front processes index return an HTTP error 500.This need to be investigate but the probable cause is that existing processes have empty or missing start/end date.
To Reproduce
Steps to reproduce the behavior:
SORT_PROCESSES_BY_DATE=true
Expected behavior
No error and the custom sort for processes enabled
Stacktrace
Application log
Additional context
see Pull request #596
The text was updated successfully, but these errors were encountered: