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
With the new change on error display when export to csv button is used, I could see that when a task was successful and contained an error, it will display to the user the whole error, like this: Error: Unexpected result: {'error': 'error!', 'report_filename': 'poll-data-export-2021-07-08-222643.csv', 'start_timestamp': 1625783203.2447248, 'generation_time_s': 0.018067359924316406}
which is caused by the way we keep this results(as a string with "Unexpected results: " added):
I think that would be better to send to json to the frontend instead of the repr and process it in the frontend itself showing just the "error" part to the user and logging the rest to the browser console
The text was updated successfully, but these errors were encountered:
With the new change on error display when export to csv button is used, I could see that when a task was
successful
and contained an error, it will display to the user the whole error, like this:Error: Unexpected result: {'error': 'error!', 'report_filename': 'poll-data-export-2021-07-08-222643.csv', 'start_timestamp': 1625783203.2447248, 'generation_time_s': 0.018067359924316406}
which is caused by the way we keep this results(as a string with "Unexpected results: " added):
I think that would be better to send to json to the frontend instead of the repr and process it in the frontend itself showing just the "error" part to the user and logging the rest to the browser console
The text was updated successfully, but these errors were encountered: