-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Change default of --fatal
command line arg to terminate on error
#3317
base: main
Are you sure you want to change the base?
Conversation
Honestly, I don't quite understand why "ignore" is treated differently in one spot (made into ""), and "errors" is passed into a different spot. I was just recreating the functionality in the other PR. |
Ugh, this breaks a lot of unit tests. |
The original PR used "ignore" to ignore, but did not change |
--fatal
command line arg to terminate on error
I haven't had time to dig into this topic very deeply, but I believe this change could affect people who rely on the current default. As such, I'm going to mark this as a WIP but only to prevent accidental merge until we are ready, particularly given the presence of a Before that major release, I would prefer to publish a new release sometime soon with what is currently in @avaris: Given your discussion in the previous PR thread, what are your thoughts about the current state of things here? |
Yes, this breaks a lot of unit tests, BUT There should be no need for I do believe we should slowly start identifying all those fatals as really "a hill to die on". |
Unfortunately, I don't understand the desired behavior well enough to represent this PR. I just submitted something with some fixes to try to move forward #3173. Can someone describe next steps here? |
I noticed #3173 is now conflicted and also in the "pelican 5.0" milestone.
So, this is a re-implementation, along with a simple unit test.
I don't know how to test it well, so it's worth comparing carefully to #3173 during review.
Resolves: 3172