-
Notifications
You must be signed in to change notification settings - Fork 169
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
Internal-network use of ██████████ no longer works #9058
Comments
Traceback (most recent call last): |
Comment by Jonathan Eisenhamer on JIRA: This would be a fallout from the introduction of the version-defined contexts. At the moment, the workaround is to either define just CRDS_CONTEXT, or define the CRDS_PATH/CRDS_SERVER_URL pair. Will create a CCD issue to explore methods of supported an offline version of the version-defined context system. In the meantime, the documentation will need to be updated. Will have a CCD issue to ensure the CRDS documentation itself is updated; I believe most of it already has been. However, I believe the other documentation, such as JDox and JWST package, will also need updating. |
Got it, thanks Jonathan Eisenhamer |
Based on feedback from Rachel Plesha it sounds like usage of CRDS from central server works fine so long as the CRDS_SERVER_URL is defined. Indeed, I've confirmed that (while on the internal network) if CRDS_SERVER_URL is defined properly but CRDS_PATH is undefined the pipeline successfully determines the correct context to use for a given pipeline version and then uses those files successfully from central store without needing to cache them. As such, there's no work required for this ticket to have things operating as desired. All we need to do is to update the documentation about internal usage. As far as I'm aware the only thing that thus needs to be changed is jwst/README.md; see #9078 for a PR implementing what I think the necessary changes are. |
Comment by Rachel Plesha on JIRA: This page should also be updated: |
Comment by Melanie Clarke on JIRA: Fixed by #9078 |
Issue JP-3838 was created on JIRA by David Law:
With thanks to Rachel Plesha for the original report, it looks like internal usage of CRDS from ██████████ no longer seems to be working.
Typically, most users need to set both CRDS_PATH and CRDS_SERVER_URL, so that necessary files will be pulled from the server and cached locally at CRDS_PATH. However, I believe there was also a method where users on the STScI internal network didn't need to do either of these, as the pipeline would default to using information on a shared disk at ██████████ (thereby saving internal users the need to download their own copies of all reference files).
It's been a long time since I last tried using this approach myself, but indeed it looks like it's now not working. Traceback in comments below, although it should be easy to reproduce for anyone by simply deleting the env variables.
Any thoughts Jonathan Eisenhamer? Also tagging Rosa Diaz Meaghan McDonald Hunter Brown
The text was updated successfully, but these errors were encountered: