-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[PROD] SurgeAlerts export has bugs #2047
Comments
The failure seems to have this root cause: The API gives the response, but some newline chars can mess up the format. Normally this shouldn't cause issue via quotation marks:
|
I see a reason!
Unfortunately the "flattening" of the different pages (to enity.0, entity.1...) depends on the data of the seen data set. |
I don't see any option to give triggerExportStart any argument to filter results with event or country. |
Issue
If we push the (upper right) Export button in https://go.ifrc.org/alerts/all – the export happens, but some rows are shifted horizontally: not the proper values appear in some cells.
If we push the (upper right) Export button in https://go.ifrc.org/alerts/all?event=6061, we receive a
Failed to generate export
warning, though on backend it seems to be not using that event-id (and seems to work):
"GET /api/v2/surge_alert/?offset=0&limit=100&format=csv HTTP/1.0" 200 ...
(200 means OK)
The text was updated successfully, but these errors were encountered: