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
What we're after: While testing the front-end implementation of the 2-year restriction lift, I came across a significant number of errors, particularly when changing the selected filters.
We need to investigate this possible front-end bug a little more to understand why, when a query is still running is a "trouble processing" error displaying in the datatables. It appears that the code (looks like: DataTable.prototype.fetch in tables.js) that triggers the error is "jumping to conclusions" even when it's not necessary for it to display. We see this most often when a user removes a filter criteria during an ongoing or search in-progress.
Preliminary documentation of some of these instances is in the testing notes doc.
Completion criteria:
Investigate and make a recommendation for a fix
Fix
The text was updated successfully, but these errors were encountered:
AmyKort
changed the title
Premature "trouble processing" error on schedule a datatables
Premature "trouble processing" error on datatables
May 16, 2019
Related work: #2853
What we're after: While testing the front-end implementation of the 2-year restriction lift, I came across a significant number of errors, particularly when changing the selected filters.
We need to investigate this possible front-end bug a little more to understand why, when a query is still running is a "trouble processing" error displaying in the datatables. It appears that the code (looks like:
DataTable.prototype.fetch
intables.js
) that triggers the error is "jumping to conclusions" even when it's not necessary for it to display. We see this most often when a user removes a filter criteria during an ongoing or search in-progress.Preliminary documentation of some of these instances is in the testing notes doc.
Completion criteria:
The text was updated successfully, but these errors were encountered: