-
Notifications
You must be signed in to change notification settings - Fork 13k
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
surprises in resolve #6143
Comments
This appears to have been milestoned without being nominated. Re-nominating to move to milestone 1, well-defined. |
accepted for well-defined milestone |
Nominating to de-milestone. I believe the high-priority blocker is #8215, and there are otherwise associated issues, but I don't believe that they should be blockers. |
De-milestoning inf avor of more specific bugs |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There are a number of ... surprises in resolve, which may be intentional, may not be, or may represent the need to make backwards-incompatible changes. I think they're related, but I'm not sure. I'm collecting them into a metabug here.
The ones I see are #4536 , #5238 , #5248 , #5269 and #3352 (though the last seems less likely related, it provokes a similarly-unclear "shouldn't this work?" feeling from me, and I'm not sure how to classify the bug)
The text was updated successfully, but these errors were encountered: