Comments (8)
@fperez I suspect you're right. It sounds like the solution is better response handling/testing for a proper session after icepyx tries to log the user in. Is that something you could take on? It should fit well within the Earthdata class functionality.
from icepyx.
Thanks @JessicaS11! Yes, I'm happy to take a look at that code later on :) Unfortunately today my time for the hack week is winding down, I have to switch gears in 15 min.. But I'll tag this one for later and we can see if it can be made more robust.
from icepyx.
We'll need to experiment with exactly when these error codes come from NSIDC - I'm not an expert web person at all. Some input from perhaps folks on the NSIDC/EarthData side would help a lot, in terms of knowing when/which error codes can come from their end. It seems to me that what we need to do is, if a login is successful (which evidently can happen even when the service is down), learn exactly which error info can come back and check for those. We can then immediately surface such errors appropriately to the user...
from icepyx.
@asteiker @nicholas-kotlinski @wallinb Can one of you provide any of this information from the NSIDC side?
from icepyx.
It seems as though a 503 would not be generated from, or delivered by, NSIDC proper - but that the error is passed along from dependent upstream systems like EDSC or CMR. Based on some sleuthing by Amy FitzGerrell at NSIDC, it seems this most often happens during preventative maintenance on their end. When the error occurs outside of planned preventative maintenance, itβs not possible to predict it. The fix for the issue would be to have icepyx do a better job of surfacing the error, somehow, so that it isnβt buried.
HTTP Status Code 503 β Internal error because a service dependency is not available
Search HTTP Status Code 503 here for a short description: https://cmr.earthdata.nasa.gov/search/site/docs/search/api.html
from icepyx.
A few additional points: This error may be caused by either CMR or Earthdata Login. Earthdata Search Client (which we refer to internally across EOSDIS as "EDSC") isn't involved in our API response (though it also queries the NSIDC API just like icepyx or any other application or client). Both the CMR and Earthdata Login rarely have planned maintenance in their production environment so usually this will be caused by an ephemeral unplanned issue. Thanks Nic for tracking this down with Amy F. further!
from icepyx.
In digging into #166, I just started a branch surf_err that completes the first step of this issue (surfaces errors returned during the granules.get_avail()
search step of Query). It'd be great if @facusapienza21 or @fperez could begin expanding this to other areas of API interaction to move this issue along.
from icepyx.
While debugging another user issue (which resulted from no subset data messages no longer being surfaced as an error), I added on to this branch to re-catch the no subset data orders and let the user know they can't be downloaded (in case they miss the order message). @facusapienza21 @fperez @nicholas-kotlinski @wallinb - if you have a few minutes to review #195 it would be greatly appreciated!
from icepyx.
Related Issues (20)
- improve QUEST documentation HOT 2
- figure out where the codecov reports went HOT 2
- become PEP8 compliant HOT 1
- NSIDC request url generation currently includes duplicate keywords HOT 4
- Allow generating variables wanted from a list of h5 paths HOT 4
- Editable install instructions on contributing page could be clearer HOT 7
- remove metadata fix after next ATL{11,14,15} version up
- Add Examples Directory HOT 1
- Unable to download 5000005497555 HOT 1
- transition to Harmony API from on-prem EGI
- [harmony] transition `ipx.APIformatting` to Harmony keys
- [harmony] point granules module to Harmony instead of EGI
- [harmony] [docs] variables and subsetting
- [harmony] components of `ipx.query` likely impacted by transition from EGI HOT 1
- Add deprecation warning to icepyx v1
- Consolidate CI from Travis -> GitHub Actions?
- Move `requirements*.txt` files into `pyproject.toml` HOT 7
- Refactor setter for performance and readability
- Travis failing on fork PRs due to EDL auth error HOT 3
- Test PyPI failing due to accidental publishes from another branch HOT 7
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. πππ
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google β€οΈ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from icepyx.