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

update lock file #179

Merged
merged 6 commits into from
Feb 19, 2024
Merged

update lock file #179

merged 6 commits into from
Feb 19, 2024

Conversation

ocefpaf
Copy link
Member

@ocefpaf ocefpaf commented Feb 19, 2024

I also want to investigate some of the CI failures here.

@ocefpaf
Copy link
Member Author

ocefpaf commented Feb 19, 2024

2016-11-16-CF-UGRID-SGRID-conventions.ipynb is failing b/c the https://geoport.whoi.edu/thredds/catalog/coawst_4/use/fmrc/catalog.html?dataset=coawst_4/use/fmrc/coawst_4_use_best.ncd endpoint seems to be down. I'm not sure if it moved, is down permanently, or if it is a temporary issue. I'm looking into other datasets that could be used here instead.

@ocefpaf
Copy link
Member Author

ocefpaf commented Feb 19, 2024

jupyterbook/content/code_gallery/data_access_notebooks/2017-06-12-NCEI_RA_archive_history.ipynb failed with HTTPError: HTTP Error 503: Service Unavailable. This is most likely temporary, merging this one so we can move forward with other PRs.

@ocefpaf ocefpaf merged commit 5cd4a49 into ioos:main Feb 19, 2024
10 of 11 checks passed
@ocefpaf ocefpaf deleted the update_lockfile branch February 19, 2024 17:36
@MathewBiddle
Copy link
Contributor

2016-11-16-CF-UGRID-SGRID-conventions.ipynb is failing b/c the https://geoport.whoi.edu/thredds/catalog/coawst_4/use/fmrc/catalog.html?dataset=coawst_4/use/fmrc/coawst_4_use_best.ncd endpoint seems to be down. I'm not sure if it moved, is down permanently, or if it is a temporary issue. I'm looking into other datasets that could be used here instead.

We seem to run into this a lot with these notebooks. Would it be worthwhile to write a test Action that tests all the endpoints we hit to ensure they are functioning properly? Then, run that before the CI's?

It's difficult to highlight IOOS data services and tools when some of the services are down...

@ocefpaf
Copy link
Member Author

ocefpaf commented Feb 20, 2024

We seem to run into this a lot with these notebooks.

In a way, the notebook itself is a test for the endpoint. Separating the endpoint test may hinder the failure when it happens during download time or accessing a variable.

It's difficult to highlight IOOS data services and tools when some of the services are down...

Indeed. We should however have a list of essential/important services that we could track in another repo and have some diagnostics for them.

@MathewBiddle
Copy link
Contributor

Great points!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants