Skip to content
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

[Bug]: admin 1 and admin 2 level analysis fails for Mozambique #1299

Open
wadhwamatic opened this issue Jul 4, 2024 · 3 comments
Open

[Bug]: admin 1 and admin 2 level analysis fails for Mozambique #1299

wadhwamatic opened this issue Jul 4, 2024 · 3 comments
Assignees
Labels
bug Something isn't working triage to be triaged for next action

Comments

@wadhwamatic
Copy link
Member

What happened?

When I tried to run an analysis at admin level 1 or 2, I get an error response 'failed to fetch'. Level 3 works as expected.

I'm not sure what would cause this and if it was undetected when we merged PR #1163 or if a change that came later caused the issue. I thought perhaps this is related to the boundary file but I'm not seeing any issues in the file.

Steps to reproduce:

  1. REACT_APP_COUNTRY=mozambique yarn start
  2. Run analysis using any hazard layer, baseline layer = admin 2, default all other inputs
  3. See the error in PRISM
  4. Try again with baseline layer = admin 3. Results will appear as expected

Which country / deployment are you running?

main / mozambique

Add a screenshot (if relevant)

Screenshot 2024-07-04 at 15 49 33
@wadhwamatic wadhwamatic added bug Something isn't working triage to be triaged for next action labels Jul 4, 2024
@ericboucher
Copy link
Collaborator

@wadhwamatic it fails locally because the key we use does not exist on the file uploaded in S3 but it should work on deployed versions. But i think in general we should find a better way to do this and stop relying on the uploaded files altogether

@wadhwamatic
Copy link
Member Author

Thanks for looking into this @ericboucher. I updated the files on S3 so that they are the same as what we have locally but it still failed. I'll do a quick deploy to double-check though.

Agreed, good if we can move away from relying on remote files in this case.

@ericboucher
Copy link
Collaborator

@wadhwamatic I think we fixed that with the ?v2 trick in the file name, correct?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working triage to be triaged for next action
Projects
None yet
Development

No branches or pull requests

2 participants