This repository has been archived by the owner on Feb 23, 2023. It is now read-only.
Update dependency org.jetbrains.kotlinx:kotlinx-coroutines-android to v1.6.4 #38
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.
This PR contains the following updates:
1.4.1
->1.6.4
Release Notes
Kotlin/kotlinx.coroutines
v1.6.4
Compare Source
TestScope.backgroundScope
for launching coroutines that perform work in the background and need to be cancelled at the end of the test (#3287).kotlinx-coroutines-debug
having an incorrect reference tokotlinx-coroutines-bom
, which cause the builds of Maven projects using the debug module to break (#3334).Publisher.await
functions inkotlinx-coroutines-reactive
not ensuring that theSubscriber
methods are invoked serially (#3360). Thank you, @EgorKulbachka!withTimeout
on K/N with the new memory model (#3351).Throwable
implementations in the core library are serializable (#3328).v1.6.3
Compare Source
v1.6.2
Compare Source
ThreadLocalElement
not being correctly updated when the most outersuspend
function was called directly withoutkotlinx.coroutines
(#2930).runBlocking
event loop, and a benign data race inMutex
(#3250, #3251).TestCoroutineContext
is removed, which fixes thekotlinx-coroutines-test
JPMS package being split betweenkotlinx-coroutines-core
andkotlinx-coroutines-test
(#3218).0.17.2
, which includes a more efficient and robust JS IR transformer (#3255).1.6.21
, Gradle version is updated to7.4.2
(#3281). Thanks, @wojtek-kalicinski!v1.6.1
Compare Source
Dispatchers.Main
.This behavior was introduced in 1.6.0 and then found inconvenient and erroneous (#3106, #3113).
CopyableThreadContextElement
to solve issues uncovered after the initial release (#3227).ThreadLocalElement
not being properly updated in racy scenarios (#2930).CoroutineExceptionHandler
that triggered ANR on some devices (#3180).CoroutineDispatcher
to a Rx scheduler (#968, #548). Thanks @recheej!flow
builder being retained in memory (#3197).limitedParallelism
on K/N with new memory model throwingClassCastException
(#3223).CoroutineContext
is added to the exception printed to the defaultCoroutineExceptionHandler
to improve debuggability (#3153).Dispatchers.Default
was significantly reduced (#3137).kotlinx-coroutines-slf4j
from 1.7.25 to 1.7.32.v1.6.0
Compare Source
Note that this is a full changelog relative to the 1.5.2 version. Changelog relative to 1.6.0-RC3 can be found at the end.
kotlinx-coroutines-test rework
kotlinx-coroutines-test
became a multiplatform library usable from K/JVM, K/JS, and K/N.).
Dispatchers
CoroutineDispatcher.limitedParallelism
that allows obtaining a view of the original dispatcher with limited parallelism (#2919).Dispatchers.IO.limitedParallelism
usages ignore the bound on the parallelism level ofDispatchers.IO
itself to avoid starvation (#2943).Dispatchers.shutdown
method for containerized environments (#2558).newSingleThreadContext
andnewFixedThreadPoolContext
are promoted to delicate API (#2919).Breaking changes
future
builder no longer reports unhandled exceptions into the globalCoroutineExceptionHandler
. Thanks @vadimsemenov! (#2774, #2791).Mutex.onLock
is deprecated for removal (#2794).Dispatchers.Main
is now used as the default source of time fordelay
andwithTimeout
when present(#2972).kotlinx.coroutines.main.delay
system property can be set tofalse
.collect
no longer resolves when used with a non-in-place argument of a functional type. This is a candidate for a fix, uncovered after 1.6.0, see #3107 for the additional details.Bug fixes and improvements
kotlin.native.binary.memoryModel
is enabled (#2914).CopyableThreadContextElement
for mutable context elements shared among multiple coroutines. Thanks @yorickhenning! (#2893).transformWhile
,awaitClose
,ProducerScope
,merge
,runningFold
,runingReduce
, andscan
are promoted to stable API (#2971).SharedFlow.subscriptionCount
no longer conflates incoming updates and gives all subscribers a chance to observe a short-lived subscription (#2488, #2863, #2871).Flow
exception transparency mechanism is improved to be more exception-friendly (#3017, #2860).flat*
operators that leverage multiple coroutines is no longer propagated upstream (#2964).SharedFlow.collect
now returnsNothing
(#2789, #2502).DisposableHandle
is nowfun interface
, and corresponding inline extension is removed (#2790).FlowCollector
is nowfun interface
, and corresponding inline extension is removed (#3047).processUnhandledException
(#2981).Task
callbacks inkotlinx-coroutines-play-services
(#2990).CoroutineExceptionHandler
is loaded eagerly and does not invokeServiceLoader
on its exception-handling path (#2552).ServiceLoader
optimization (#2880).SendChannel.trySendBlocking
is now available on Kotlin/Native (#3064).ClassValue
when available (#2997).Delay
interface is deprecated (#2979).CommonPool
is removed.@ExperimentalTime
is no longer needed for methods that useDuration
(#3041).Changelog relative to version 1.6.0-RC3
v1.5.2
Compare Source
onUndeliveredElement
was incorrectly called on a properly received elements on JS (#2826).Dispatchers.Default
on React Native, it now fully relies onsetTimeout
instead of stubprocess.nextTick
. Thanks to @Legion2 (#2843).Mutex
implementation (#2581).Mutex
implementation is made completely lock-free as stated (#2590).v1.5.1
Compare Source
update
,getAndUpdate
, andupdateAndGet
operations ofMutableStateFlow
(#2720).Executor.asCoroutineDispatcher
implementation improvements (#2601):ScheduledExecutorService
, then itsschedule
API is used for time-related coroutine operations.RemoveOnCancelPolicy
is now part of the public contract.Task.asDeferred
andTask.await
that acceptCancellationTokenSource
for bidirectional cancellation (#2527).1.0.3
(#2740).CopyableThrowable
is allowed to modify the exception message during stacktrace recovery (#1931).CoroutineDispatcher.releaseInterceptedContinuation
is now afinal
method (#2785).Handler.asCoroutineDispatcher
now causes the dispatched coroutines to be canceled onDispatchers.IO (#​2778)
.ClassCastException
inreleaseInterceptedContinuation
andIllegalStateException
fromtryReleaseClaimedContinuation
(#2736, #2768).CompletableFuture.asDeferred
when the target future has a long chain of listeners (#2730).CoroutineDispatcher.isDispatchNeeded
are now considered as fatal and are propagated to the caller (#2733).DebugProbesKt
(used in the debugger implementation) are moved fromdebug
tocore
module.v1.5.0
Compare Source
Note that this is a full changelog relative to 1.4.3 version. Changelog relative to 1.5.0-RC can be found in the end.
Channels API
offer
,poll
, andsendBlocking
methods are deprecated, internalreceiveCatching
andonReceiveCatching
removed,receiveOrNull
andonReceiveOrNull
are completely deprecated. Previously deprecatedSendChannel.isFull
declaration is removed. Channel operators deprecated withERROR
are nowHIDDEN
.receiveCatching
,onReceiveCatching
trySend
,tryReceive
, andtrySendBlocking
along with the new result typeChannelResult
are introduced. They provide better type safety, are less error-prone, and have a consistent future-proof naming scheme. The full rationale behind this change can be found here.BroadcastChannel
andConflatedBroadcastChannel
are marked asObsoleteCoroutinesApi
in the favor orSharedFlow
andStateFlow
. The migration scheme can be found in their documentation. These classes will be deprecated in the next major release.callbackFlow
andchannelFlow
are promoted to stable API.Reactive integrations
kotlinx-coroutines-rx2
,kotlinx-coroutines-rx3
,kotlinx-coroutines-reactive
,kotlinx-coroutines-reactor
, andkotlinx-coroutines-jdk9
were revisited and promoted to stable (#2545).publish
is no longer allowed to emitnull
values (#2646).awaitSingleOr*
functions onPublisher
type are deprecated (#2591).MaybeSource.await
is deprecated in the favor ofawaitSingle
, additional lint functions forMono
are added in order to prevent ambiguousPublisher
usages (#2628, #1587).ContextView
support inkotlinx-coroutines-reactor
(#2575).MaybeSource.collect
andMaybe.collect
properly finish when they are completed without a value (#2617).Other improvements
Flow.last
andFlow.lastOrNull
operators (#2246).Flow.runningFold
operator (#2641).CoroutinesTimeout
rule for JUnit5 (#2197).Job
andAbstractCoroutine
was reworked, resulting in smaller code size, less memory footprint, and better performance (#2513, #2512).CancellationException
from Kotlin standard library is used for cancellation on Koltin/JS and Kotlin/Native (#2638).DelicateCoroutinesApi
annotation that warns users about potential target API pitfalls and suggests studying API's documentation first. The only delicate API right now isGlobalScope
(#2637).1.4.3
whenkotlinx-coroutines-core.jar
triggered IDEA debugger failure (#2619).ChildHandlerNode
with reusable continuations (#2564).Changelog relative to version 1.5.0-RC
emitAll
called from cancelledonCompletion
operator (#2700).stateIn
/shareIn
keep strong reference to sharing job (#2557).TimeSource
toAbstractTimeSource
due to import issues (#2691).watchosX64
target support for Kotlin/Native (#2524).v1.4.3
Compare Source
General changes
ThreadContextElement
(#985)ThreadContextElement
s are now restored in the opposite order from update (#2195)kotlinx-coroutines-reactor
to3.4.1
, thanks to @sokomishalov (#2432)callInPlace
contract added toReceiveChannel.consume
(#941)CoroutineStart.UNDISPATCHED
promoted to stable API (#1393)kotlinx.coroutines
are now released directly to MavenCentralDispatchedCoroutine
by a fieldTimeSource
renamed toSchedulerTimeSource
to prevent wildcard import issues (#2537)Bug fixes
Job
interface (#2423)await
/asDeferred
forMinimalStage
implementations in jdk8 module (#2456)onUndeliveredElement
wasn't called for unlimited channels (#2435)ListenableFuture.isCancelled
returned fromasListenableFuture
could have thrown an exception, thanks to @vadimsemenov (#2421)callbackFlow
andproduce
is properly cancelled when the channel was closed separately (#2506)v1.4.2
Compare Source
StackOverflowError
inJob.toString
whenJob
is observed in its intermediate state (#2371).Dispatchers.Default
andDispatchers.IO
in low-loaded mode (#2381).Channel.cancel
invocations (#2384).SharingStarted
is nowfun
interface (#2397).SharedFlow
to catch programmatic errors early (#2376).CoroutineStackFrame
in exception recovery that triggered failures of instrumented code (#2386).kotlinx-coroutines-javafx
(#2360).Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.