Skip to content

Conversation

pllim
Copy link
Collaborator

@pllim pllim commented Apr 24, 2025

Resolves JP-3932

This PR addresses #3116

I don't think this needs a change log?

Tasks

Copy link

codecov bot commented Apr 24, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 75.63%. Comparing base (1c227fb) to head (fe4369a).
⚠️ Report is 690 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #9412   +/-   ##
=======================================
  Coverage   75.63%   75.63%           
=======================================
  Files         368      368           
  Lines       36900    36900           
=======================================
  Hits        27908    27908           
  Misses       8992     8992           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@pllim
Copy link
Collaborator Author

pllim commented Apr 25, 2025

8189 warnings, 70 errors 😱

Note to self:

  File "jwst/assign_wcs/nirspec.py", line 2214, in _nrs_wcs_set_input_lite
    slit_wcs.bounding_box = bb

@melanieclarke
Copy link
Collaborator

melanieclarke commented Apr 25, 2025

For the logging message - I think we want the original message to stay as it is, for its primary use in assign_wcs. We just want the messages from msa_flagging to say something different. I was envisioning something like temporarily turning off the log while calling the assign_wcs function, and separately logging the total number of failed open shutters.

@pllim
Copy link
Collaborator Author

pllim commented Apr 25, 2025

Thanks for the clarification, @melanieclarke .

What about the side discussion on "Invalid interval"? Should I ignore that for now or you want that fixed in the same PR?

@melanieclarke
Copy link
Collaborator

Thanks for the clarification, @melanieclarke .

What about the side discussion on "Invalid interval"? Should I ignore that for now or you want that fixed in the same PR?

Let's go ahead and get that fixed too.

@pllim pllim force-pushed the to-log-or-not-to-log branch from ab437d9 to 170ec57 Compare April 28, 2025 19:33
@pllim pllim force-pushed the to-log-or-not-to-log branch from 3f7f196 to 1fc83a9 Compare April 28, 2025 21:34
@pllim pllim marked this pull request as ready for review April 29, 2025 00:20
@pllim pllim requested review from a team as code owners April 29, 2025 00:20
Copy link
Collaborator

@melanieclarke melanieclarke left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this looks good now, thanks!

Can you please add a change log, though? This will change the user-facing logs and addresses a long-standing request for the pipeline, so I think it's worth noting.

pllim added 3 commits April 29, 2025 11:42
Capture log and emit different message
and catch RuntimeWarning.
@pllim pllim force-pushed the to-log-or-not-to-log branch from c35c549 to 87cd18e Compare April 29, 2025 15:47
Copy link
Collaborator

@melanieclarke melanieclarke left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Latest regtests are clean. Thanks!

@melanieclarke melanieclarke enabled auto-merge April 29, 2025 18:47
@melanieclarke melanieclarke merged commit a052902 into spacetelescope:main Apr 29, 2025
19 checks passed
@pllim pllim deleted the to-log-or-not-to-log branch April 29, 2025 19:18
@pllim
Copy link
Collaborator Author

pllim commented Apr 29, 2025

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

Successfully merging this pull request may close these issues.

4 participants