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

Data Access API 502 errors #55

Open
daralynnrhode opened this issue Jun 18, 2024 · 1 comment · May be fixed by #87
Open

Data Access API 502 errors #55

daralynnrhode opened this issue Jun 18, 2024 · 1 comment · May be fixed by #87
Assignees
Labels

Comments

@daralynnrhode
Copy link
Contributor

Provide more informative error messages for when this error is thrown in certain cases. See User Testing #40 for more information and clearer instances when it occurs.

@daralynnrhode
Copy link
Contributor Author

Commenting here the notes I took while trying to track down the errors:

  • Not applied to —instrument because input is checked before passing to query
  • For —data-level, random input or capital ‘L’ causes 502 Error. Will need to double check input before passing to the query
  • For —descriptor It does not need to be double checked because input could be anything.
  • For —start-date the error is triggered when a string is passed instead of numbers, or if a number is too long, or if the date is in the wrong format, ie. ‘MMDDYYYY’
  • For —end-date it is the same as —start-date
  • —output-format is working correctly
  • —repointing seems to be working fine and checking for itself
  • —version, does not check, should make sure it is 4 characters and starts with a ‘v’
  • —filename does not check, but not sure how it should, maybe double checking it starts with ‘imap_’, or use the correct Science Naming Function

@daralynnrhode daralynnrhode linked a pull request Sep 7, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: In Progress
Development

Successfully merging a pull request may close this issue.

1 participant