Bug #3194
closed
When archiving reports, if the query is very long, we have the dreaded "Server cannot be contacted at this time"
Added by Nicolas CHARLES almost 12 years ago.
Updated over 11 years ago.
Category:
Web - Maintenance
Description
If I want to archive reports, and the query is too long, then the request is sent another time by Ajax
So it tries to archive twice reports, resulting in an error (duplicate key entry in the database).
The archiving is done in the end, but the log contains error, and the user see an error..
I couldn't reproduce this bug in 2.4.0~rc1 (but the UI is not updated with Rudder 2.4.0~rc1)
- Assignee set to Vincent MEMBRÉ
Since the process can be artibrarly long (minutes, hours even) we should probably have a message saying that's its been taken into account rather than waiting for the process to stop.
- Status changed from New to Pending technical review
- Assignee changed from Vincent MEMBRÉ to François ARMAND
It would be great to have in the interface the status of the cleaning, so that the user now:
- if a cleaning is currently running,
- if no cleaning is in process, what was the date/status of the last cleaning : success or error, and if error, what was the reason.
I believe it could be done with addind a "queryStatus" query message to LADatabaseCleaner that return a "Status" message with these information.
- Status changed from Pending technical review to In progress
- Assignee changed from François ARMAND to Vincent MEMBRÉ
That's an idea i got this morning while having my shower !! very nice, i'll add this immediatly :)
Beside I think the user should not be able to launch a clean action if there is one in progress, and he should be notified about that
- Status changed from In progress to Pending technical review
- Assignee changed from Vincent MEMBRÉ to François ARMAND
I made the changes, they are available on the pull request!
- Status changed from Pending technical review to Pending release
- Status changed from Pending release to Released
Also available in: Atom
PDF