Releases: revoltphp/event-loop
Releases · revoltphp/event-loop
0.2.4
What's Changed
- Fixed the fiber reference in
DriverSuspensionbeing nulled early during shutdown, leading to an assertion error when attempting to resume the suspension.
Full Changelog: v0.2.3...v0.2.4
0.2.3
What's Changed
- Fixed
Undefined property: Revolt\EventLoop\Internal\DriverSuspension::$fiberin an error path
Full Changelog: v0.2.2...v0.2.3
0.2.2
What's Changed
- Fixed memory leak with suspensions keeping a reference to fibers (#42, #52)
Similar leaks might still happen if suspensions are never resumed, so ensure your suspensions are eventually resumed.
New Contributors
- @nhedger made their first contribution in #48
- @tnsoftbear made their first contribution in #50
Full Changelog: v0.2.1...v0.2.2
0.2.1
0.2.0
This release is mostly backwards compatible with v0.1.x.
What's Changed
- Add
FiberLocalto store data specific to each fiber, e.g. logging context (#40) - Throw
UnhandledThrowableif event loop stops due to an exception (#32) - Reduce fiber switches by queueing callbacks for each tick (#34)
- Avoid creating unnecessary fibers if exceptions are thrown from callbacks
- Add
EventLoop::getErrorHandler()to get the currently set error handler - Remove return value of
EventLoop::setErrorHandler(), useEventLoop::getErrorHandler()instead - Remove default value for first argument of
EventLoop::setErrorHandler()(#30) - Cache suspensions and always return the same value for a specific fiber (#37)
EventLoop::getSuspension()has been added as replacement forEventLoop::createSuspension()EventLoop::createSuspension()has been deprecated and will be removed in the next version
- Fix multiple interrupts on double resumption leading to an assertion error instead of an exception (#41)
- Fix suspensions keeping their pending state after the event loop exceptionally stopped
Full Changelog: v0.1.1...v0.2.0