-
-
Notifications
You must be signed in to change notification settings - Fork 756
Do not call disabled deferred procedures #5183
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
Conversation
I don't know if it should print a warning, because then I'm one of those people who always compiles with |
I can toss that out. I made it a warning because that's what I did when I fixed disabled |
That's more likely to be an unintentional error. You run things under |
(These things are hard, aren't they, deciding sane defaults? But we can always revisit these decisions if we get feedback on these particular obscure use cases.) |
Yeah, I have a tendency to go for caution and informing the user as much as possible, but I can also see this being a less annoying result if it's commonplace for someone to have disabled deferrals for some reason. |
That's twice now that github's CDN failed:
|
I've had issues with downloading the test assets locally today too. |
I can see wanting to be cautious, but I also figure that if you're going out of your way to use |
And FreeBSD caps it off with a "VM is booting" loop. I think I'll merge the patch. :-) |
Confirmed the fix works locally. Thanks as always, Feoramund. |
Fixes #5083
I put the warning token on the
proc
with the deferral as it's the first step to the cause of the issue, but I can see a case for either proc as being a valid warning source.