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
Fix extended trait change issues #621
Conversation
Codecov Report
@@ Coverage Diff @@
## master #621 +/- ##
==========================================
+ Coverage 69.43% 69.76% +0.33%
==========================================
Files 40 40
Lines 6282 6285 +3
Branches 1295 1296 +1
==========================================
+ Hits 4362 4385 +23
+ Misses 1521 1501 -20
Partials 399 399
Continue to review full report at Codecov.
|
As a data point, this is causing a significant number of test failures on a largish Traits-using project; some repetitions, but it looks like 10-15 different instances of failure. |
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.
Given the extent of the breakage seen in testing, I don't think we can get this into 6.0.0. We need to find some way to provide a non-breaking upgrade-path for Traits-using applications.
@corranwebster Thoughts on what to do with this PR? We can leave it open and use it as a starting-point for more far-reaching updates. Or should it be closed? |
I think it needs to be closed sooner or later: I think we've demonstrated that too much downstream code will be broken by this change. Certainly we don't want an accidental merge. |
This fixes #537 and fixes #538.
It also removes expected failures of tests.
This may break existing code that accidentally uses buggy behaviour.