-
Notifications
You must be signed in to change notification settings - Fork 36
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 the additional lifecycle events to work as documented #149
Conversation
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.
it's an internal change, so could be released as a patch release normally.
CHANGELOG.md
Outdated
#### Bugfixes | ||
- Make the additional lifecycle events match the docs |
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.
It's a bit unclear what was exactly changed, probably should describe the behavior that could be observed (like endless loop due to use of lifecycle events).
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.
I think this is sufficient because:
- there are, to my knowledge, no users of this API, so no-one will have run into this
- The pr is readily available
- I don't want to make the changelog be really long with useless content
But I'll put whatever you prefer, if you give me the text you want to put here
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.
I mean, - Fix infinite loop when using a source with lifecycle events
is short enough from what I can say? Or is it not reflecting the situation correctly?
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.
So the infinite loop was only because the events were never getting read - we were still making progress, and other sources would have worked.
That is, the infinite loop is in the WaylandSource - yes because of this issue, but that isn't the only way this could manifest
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.
Hm, yeah, that's actually fair. I'm fine with the changelog like that, it's just reads without providing a real value to the user.
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.
probably @elinorbgr has a better suggestion on that matter, since we'd need to patch release and maybe yank 0.12.
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.
Overall, I'd prefer to have a quick description of what the bug was, so something like this would be fine imo:
- Fix `EventSource::before_handle_events()` being erroneously give an iterator over synthetic events instead of real events
CI should be fixed after #150 |
👍 with a rebase & changelog adjusment |
874e856
to
a5415ee
Compare
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## master #149 +/- ##
==========================================
- Coverage 86.82% 86.20% -0.62%
==========================================
Files 14 12 -2
Lines 1806 1624 -182
==========================================
- Hits 1568 1400 -168
+ Misses 238 224 -14
Flags with carried forward coverage won't be shown. Click here to find out more.
☔ View full report in Codecov by Sentry. |
Perfect thanks! |
Required for Smithay/calloop-wayland-source#1.
I think this only needs to be a patch release, as this just brings the behaviour in-line with the docs