earthaccess search handling CMR error

[meteodave]

When the NASA CMR service is degraded (as on January 10, 2025), for example, I get an "internal error" message when searching for concept ID and temporal range in CMR.

start_date = "2019-09-26"
end_date = "2019-09-27"

id = "C1276812830-GES_DISC"

auth = earthaccess.login(persist=True)
granules = earthaccess.search_data(concept_id = id, temporal = (start_date,end_date))

HTTPError: 500 Server Error: Server Error for url: https://cmr.earthdata.nasa.gov/search/granules.umm_json?concept_id%5B%5D=C1276812830-GES_DISC&temporal%5B%5D=2019-09-26T00:00:00Z,2019-09-27T23:59:59Z&page_size=0

The above exception was the direct cause of the following exception:

If there is an error from CMR, perhaps output a link to the CMR application status page; this information would be helpful in debugging and understanding why earthaccess search is failing when I know the inputs are correct.

[betolink]

This would be very useful, perhaps we can run these checks right after import earthaccess statement and warn our users if CMR is having issues.

[chuckwondo]

We do not want to make a network request upon import. Not only does such a thing lengthen the import time, but it's also a transient state that we're checking, which might change by the time the user actually attempts a CMR operation. In other words, upon import, we might produce a warning, but by the time the user actually makes a CMR call, the system is actually operational again.

[betolink]

I guess, we could also have try statement and check for the status of CMR on the exception block on those operations.