Version 1.7.2 #3797
Merged
Version 1.7.2 #3797
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: Vsevolod Tolstopyatov <[email protected]>
The previous version 2.17 contains a bug that leads to a memory leak, resulting in OutOfMemoryError Signed-off-by: Nikita Koval <[email protected]>
* Also, exclude integration from docs, it shouldn't be there Fixes #3701
The scenario in question: - tryLock(owner), but the mutex was locked with the same owner - tryAcquire() fails - another thread releases the mutex - holdsLock(owner) fails, as the mutex is unlocked - another thread acquires the mutex with owner - isLocked returns true, and tryLock(owner) returns false. However, tryLock(o) should throw an exception. Fixes #3745 Signed-off-by: Nikita Koval <[email protected]> Co-authored-by: Vsevolod Tolstopyatov <[email protected]>
…3778) `flowOn` uses its own undispatched coroutine start when it detects a fast path. Previously, it concatenated the context missing the copy of CopyableThreadContextElement. Fixed by replacing concatenation with `newCoroutineContext`. Fixes #3787 Co-authored-by: Vsevolod Tolstopyatov <[email protected]>
* Remove unnecessary newline (#3756) * Properly name Flow.timeout param in the documentation --------- Co-authored-by: Hanbit Kang <[email protected]>
* OptIn for ExperimentalNativeApi Any.identityHashCode(), processUnhandledException(Throwable) and kotlin.native.Platform became ExperimentalNativeApi in 1.9.0. In 1.9.20 the opt-in requirement level of the annotation was raised to ERROR.
Update user projects config: adapt build script to new TeamCity variables
…3784) Such coroutines typically are a subject for significant debugger overhead, can be observed with more conventional tools, and do not contribute to the state of the system that is typically observed with coroutines debugger Fixes #3782 Co-authored-by: Oleg Yukhnevich <[email protected]> Co-authored-by: Dmitry Khalanskiy <[email protected]>
…3769) * Fix newSingleThreadContext awaiting cancelled scheduled coroutines Before the change, the Worker is not notified about its work being cancelled, due to no API being present for that. We work around the issue by checking every 100 milliseconds whether cancellation happened. Also, alias 'newSingleThreadContext' to 'newFixedThreadPoolContext(1)` for the sake of consistent implementation Fixes #3768
dkhalanskyjb
approved these changes
Jun 29, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.