build(deps): bump org.jetbrains.kotlinx:kotlinx-coroutines-core-jvm from 1.6.4 to 1.8.0

[dependabot]

Bumps org.jetbrains.kotlinx:kotlinx-coroutines-core-jvm from 1.6.4 to 1.8.0.

Release notes

Sourced from org.jetbrains.kotlinx:kotlinx-coroutines-core-jvm's releases.

1.8.0

• Implement the library for the Web Assembly (Wasm) for JavaScript (#3713). Thanks @​igoriakovlev!
• Major Kotlin version update: was 1.8.20, became 1.9.21.
• On Android, ensure that Dispatchers.Main != Dispatchers.Main.immediate (#3545, #3963).
• Fixed a bug that caused Flow operators that limit cancel the upstream flow to forget that they were already finished if there is another such operator upstream (#4035, #4038).
• kotlinx-coroutines-debug is published with the correct Java 9 module info (#3944).
• kotlinx-coroutines-debug no longer requires manually setting DebugProbes.enableCoroutineCreationStackTraces to false, it's the default (#3783).
• kotlinx-coroutines-test: set the default timeout of runTest to 60 seconds, added the ability to configure it on the JVM with the kotlinx.coroutines.test.default_timeout=10s (#3800).
• kotlinx-coroutines-test: fixed a bug that could lead to not all uncaught exceptions being reported after some tests failed (#3800).
• delay(Duration) rounds nanoseconds up to whole milliseconds and not down (#3920). Thanks @​kevincianfarini!
• Dispatchers.Default and the default thread for background work are guaranteed to use the same context classloader as the object containing it them (#3832).
• It is guaranteed that by the time SharedFlow.collect suspends for the first time, it's registered as a subscriber for that SharedFlow (#3885). Before, it was also true, but not documented.
• Atomicfu version is updated to 0.23.1, and Kotlin/Native atomic transformations are enabled, reducing the footprint of coroutine-heavy code (#3954).
• Added a workaround for miscompilation of withLock on JS (#3881). Thanks @​CLOVIS-AI!
• Small tweaks and documentation fixes.

1.8.0-RC2

• Fixed a bug introduced in 1.8.0-RC where Mutex.onLock would not unlock if a non-local return was performed (#3985).
• Fixed a bug introduced in 1.8.0-RC where depending on kotlinx-coroutines in Native code failed with a compilation error Could not find "org.jetbrains.kotlinx:atomicfu-cinterop-interop" (#3968).
• Small documentation fixes.

1.8.0-RC

• Implement the library for the Web Assembly (Wasm) for JavaScript (#3713). Thanks @​igoriakovlev!
• On Android, ensure that Dispatchers.Main != Dispatchers.Main.immediate (#3545, #3963).
• kotlinx-coroutines-debug is published with the incorrect Java 9 module info (#3944).
• Major Kotlin version update: was 1.8.20, became 1.9.21.
• kotlinx-coroutines-test: set the default timeout of runTest to 60 seconds, added the ability to configure it on the JVM with the kotlinx.coroutines.test.default_timeout=10s (#3800).
• kotlinx-coroutines-test: fixed a bug that could lead to not all uncaught exceptions being reported after some tests failed (#3800).
• delay(Duration) rounds nanoseconds up to whole milliseconds and not down (#3920). Thanks @​kevincianfarini!
• Dispatchers.Default and the default thread for background work are guaranteed to use the same context classloader as the object containing it them (#3832).
• It is guaranteed that by the time SharedFlow.collect suspends for the first time, it's registered as a subscriber for that SharedFlow (#3885). Before, it was also true, but not documented.
• Atomicfu version is updated to 0.23.1, and Kotlin/Native atomic transformations are enabled, reducing the footprint of coroutine-heavy code (#3954).
• Added a workaround for miscompilation of withLock on JS (#3881). Thanks @​CLOVIS-AI!
• Small tweaks and documentation fixes.

1.7.3

• Disabled the publication of the multiplatform library metadata for the old (1.6 and earlier) KMP Gradle plugin (#3809).
• Fixed a bug introduced in 1.7.2 that disabled the coroutine debugger in IDEA (#3822).

1.7.2

Bug fixes and improvements

• Coroutines debugger no longer keeps track of coroutines with empty coroutine context (#3782).
• CopyableThreadContextElement now properly copies an element when crossing the coroutine boundary in flowOn (#3787). Thanks @​wanyingd1996!
• Coroutine timeouts no longer prevent K/N newSingleThreadContext from closing (#3768).
• A non-linearizability in Mutex during tryLock/unlock sequence with owners is fixed (#3745).
• Atomicfu version is updated to 0.21.0.

1.7.1

Bug fixes and improvements

... (truncated)

Changelog

Sourced from org.jetbrains.kotlinx:kotlinx-coroutines-core-jvm's changelog.

Version 1.8.0

• Implement the library for the Web Assembly (Wasm) for JavaScript (#3713). Thanks @​igoriakovlev!
• Major Kotlin version update: was 1.8.20, became 1.9.21.
• On Android, ensure that Dispatchers.Main != Dispatchers.Main.immediate (#3545, #3963).
• Fixed a bug that caused Flow operators that limit cancel the upstream flow to forget that they were already finished if there is another such operator upstream (#4035, #4038)
• kotlinx-coroutines-debug is published with the correct Java 9 module info (#3944).
• kotlinx-coroutines-debug no longer requires manually setting DebugProbes.enableCoroutineCreationStackTraces to false, it's the default (#3783).
• kotlinx-coroutines-test: set the default timeout of runTest to 60 seconds, added the ability to configure it on the JVM with the kotlinx.coroutines.test.default_timeout=10s (#3800).
• kotlinx-coroutines-test: fixed a bug that could lead to not all uncaught exceptions being reported after some tests failed (#3800).
• delay(Duration) rounds nanoseconds up to whole milliseconds and not down (#3920). Thanks @​kevincianfarini!
• Dispatchers.Default and the default thread for background work are guaranteed to use the same context classloader as the object containing it them (#3832).
• It is guaranteed that by the time SharedFlow.collect suspends for the first time, it's registered as a subscriber for that SharedFlow (#3885). Before, it was also true, but not documented.
• Atomicfu version is updated to 0.23.1, and Kotlin/Native atomic transformations are enabled, reducing the footprint of coroutine-heavy code (#3954).
• Added a workaround for miscompilation of withLock on JS (#3881). Thanks @​CLOVIS-AI!
• Small tweaks and documentation fixes.

Changelog relative to version 1.8.0-RC2

• kotlinx-coroutines-debug no longer requires manually setting DebugProbes.enableCoroutineCreationStackTraces to false, it's the default (#3783).
• Fixed a bug that caused Flow operators that limit cancel the upstream flow to forget that they were already finished if there is another such operator upstream (#4035, #4038)
• Small documentation fixes.

Version 1.8.0-RC2

• Fixed a bug introduced in 1.8.0-RC where Mutex.onLock would not unlock if a non-local return was performed (#3985).
• Fixed a bug introduced in 1.8.0-RC where depending on kotlinx-coroutines in Native code failed with a compilation error Could not find "org.jetbrains.kotlinx:atomicfu-cinterop-interop" (#3968).
• Small documentation fixes.

Version 1.8.0-RC

• Implement the library for the Web Assembly (Wasm) for JavaScript (#3713). Thanks @​igoriakovlev!
• On Android, ensure that Dispatchers.Main != Dispatchers.Main.immediate (#3545, #3963).
• kotlinx-coroutines-debug is published with the correct Java 9 module info (#3944).
• Major Kotlin version update: was 1.8.20, became 1.9.21.
• kotlinx-coroutines-test: set the default timeout of runTest to 60 seconds, added the ability to configure it on the JVM with the kotlinx.coroutines.test.default_timeout=10s (#3800).
• kotlinx-coroutines-test: fixed a bug that could lead to not all uncaught exceptions being reported after some tests failed (#3800).
• delay(Duration) rounds nanoseconds up to whole milliseconds and not down (#3920). Thanks @​kevincianfarini!
• Dispatchers.Default and the default thread for background work are guaranteed to use the same context classloader as the object containing it them (#3832).
• It is guaranteed that by the time SharedFlow.collect suspends for the first time, it's registered as a subscriber for that SharedFlow (#3885). Before, it was also true, but not documented.
• Atomicfu version is updated to 0.23.1, and Kotlin/Native atomic transformations are enabled, reducing the footprint of coroutine-heavy code (#3954).
• Added a workaround for miscompilation of withLock on JS (#3881). Thanks @​CLOVIS-AI!
• Small tweaks and documentation fixes.

Version 1.7.3

• Disabled the publication of the multiplatform library metadata for the old (1.6 and earlier) KMP Gradle plugin (#3809).
• Fixed a bug introduced in 1.7.2 that disabled the coroutine debugger in IDEA (#3822).

Version 1.7.2

... (truncated)

Commits

• 8c516f5 Version 1.8.0
• 90d9a30 Disable DebugProbes.enableCreationStackTraces by default (#4028)
• c5a579e Merge pull request #4042 from Kotlin/dk-doc-improvements
• 83fa0b4 Supply MDC context propagation with examples.
• 1d04452 Revisit SupervisorScope, supervisorScope, and coroutineScope docs
• 17bae3f Don't say that job completion causes CancellationException
• 92df6e1 Reword the prompt cancellation guarantee
• 8eb4963 Improve the explanation of how await throws exceptions
• fdc0818 Clarify that using runBlocking in suspend functions is allowed
• d0dabb9 Ensure that flow operators propagate the cancellation exceptions (#4038)
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[pull-request-quantifier-deprecated]

This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Extra Small
Size       : +1 -1
Percentile : 0.8%

Total files changed: 1

Change summary by file extension:
.kts : +1 -1

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detected.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.