-
Notifications
You must be signed in to change notification settings - Fork 22
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
switch tag keywords for external tags to wildcards #370
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #370 +/- ##
=======================================
Coverage 95.32% 95.32%
=======================================
Files 4 4
Lines 171 171
=======================================
Hits 163 163
Misses 8 8 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One question.
"tag:stsci.edu:asdf/time/time-1.*", | ||
"tag:stsci.edu:asdf/core/ndarray-1.*", | ||
"tag:stsci.edu:asdf/unit/quantity-1.*", | ||
"tag:stsci.edu:asdf/unit/unit-1.*", | ||
"tag:astropy.org:astropy/units/unit-1.*", | ||
"tag:astropy.org:astropy/table/table-1.*", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If I recall how this gets used, with this change the use of external tags with a 1.*
version instead of a 1.0.0
(or whatever version) will be enforced by this test. Can you confirm that we get test failures if a tag a non *
version external tag is used?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for taking a look! Your recollection is spot-on. I made a draft PR which changes time-1.*
to time-1.0
in the exposure
schema (see commit). This causes the mentioned test to fail with:
E AssertionError: assert 'tag:stsci.edu:asdf/time/time-1.0.0' in {'asdf://stsci.edu/datamodels/roman/tags/aperture-1.0.0', 'asdf://stsci.edu/datamodels/roman/tags/associations-1.0.0',...models/roman/tags/calibration_software_version-1.0.0', 'asdf://stsci.edu/datamodels/roman/tags/coordinates-1.0.0', ...}
See: https://github.com/spacetelescope/rad/actions/runs/7846209023/job/21412354776?pr=371#step:10:104
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, I wanted to make sure that future changes wouldn't slowly undo this work.
Please do a regression test run. It should not cause any issues, but with the impending build release its better to be safe. |
Thanks again! The regression tests passed without issue: |
@PaulHuwe please let us know if your happy with these changes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Please confirm with @ddavis-stsci before merging (or merge after the release).
6be126b
to
cff381f
Compare
@ddavis-stsci I updated this PR moving the changelog entry to |
Since 0.19.0 is out merging this should be fine. |
It appears I do not have write access to this repository so please feel free to merge whenever. |
Merged. |
This PR switches the
tag
keywords in the rad schemas to wildcard expressions for all tags outside of rad. For example:rad/src/rad/resources/schemas/wfi_image-1.0.0.yaml
Line 34 in 64cf407
is replaced by
The use of the wildcard
*
means that anyndarray
tag with a version starting with1.
will be considered valid.This change is needed for asdf standard 1.6.0 (the current development version and upcoming stable version) which contains an increase in the
ndarray
tag version (from1.0.0
to1.1.0
). Many other tags will also see version changes to comply with 1.6.0 (includingtime
,quantity
, etc).The type of failure that this PR will avoid can be seen in the following example:
which results in an error:
Regression tests passed: https://plwishmaster.stsci.edu:8081/blue/organizations/jenkins/RT%2FRoman-Developers-Pull-Requests/detail/Roman-Developers-Pull-Requests/598/pipeline/247
Checklist
CHANGES.rst
under the corresponding subsection