Skip to content

Version 1.2.1 #1142

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

Merged
merged 46 commits into from
Apr 26, 2019
Merged

Version 1.2.1 #1142

merged 46 commits into from
Apr 26, 2019

Conversation

qwwdfsad
Copy link
Collaborator

No description provided.

objcode and others added 30 commits February 24, 2019 19:48
Add deprecations to new API for changes.
- removed asyncTest
- added pauseDispatcher(), pausDispatcher(block), and resumeDispatcher() API to delayController
- removed dispatchImmediately (the name was fairly opaque in an actual test case)
- added exception handling to runBlockingTest
- Added missing defaults to ctor of TestCoroutineScope
- Docs cleanup & tests for coverage
- Removed some added-as-deprecated APIs that might have helped with
automatic refactoring via ReplaceWith. Not sure if these should be
shipped.
* Moved 'kotlinx-coroutines-test' to a new root folder
* Removed ThreadSafeHead duplication by promoting it core's internal
  class to public @InternalCoroutinesApi
* Kotlin libraries code style: explicit visibility and other style-issues
* DelayController.currentTime() is val
* Using atomicfu in place of AtomicXxx classes
* Added version to ExperimentCoroutineApi annotations
* Some todos are added for future consideration
* Fixed long overflows on delay (clamp) and added test
* License headers added to files
* Tests moved to an appropriate package
* Additional ordering tests using TestBase "expect" infrastructure
…estCoroutineDispatcher, TestCoroutineExceptionHandler.
Hopefully, this is going to make this test less flaky (more stable)
due to more predictably scheduling of two stressed tasks onto two
different core and, at the time, increases quality of the test
by stressing multi-threaded channel operation more.
Sender must be slowed down when it goes too fast
* Update to atomicfu 0.12.4, which fixes plugin operation with
  kotlin-multiplatform
* Remove explicit dependencies (plugins adds them automatically)

Fixes #1116
Fixes #1064
It can be treated ambiguously (do nothing vs cancel immediately), so we better wait for a user feedback with a use-cases before allowing this
* It was not working after `gradlew publishToMavenLocal` due to
  extra jar files in the build/libs
elizarov and others added 14 commits April 23, 2019 12:13
This should really fix processing of class files

Fixes #1116
Fixes #1064
…uilding in Job with enabled stacktrace recovery

  * Efficiently prevent cycles for recovered1(original).addSuppressed(recovered2(original))
  * Disable virtual time output in regular tests
Job.asCompletableFuture

Fixes #1104
  * Postpone version expansion on after evaluate phase

Fixes #1118
…pending.

    * It allows using flowViaChannel for integration with Java callbacks
    * CoroutineScope is provided to provide a lifecycle object (that is not otherwise accessible)
    * Suspending use-cases are covered with flow builder

Fixes #1081
… introduce collect extension instead to be aligned with Flow

First wave of #1080
The race happens in the slow-path of 'join' implementation when
parent invokes join on a child coroutines that crashes and cancels
the parent.

Fixes #1123
Flow operators:

    * switchMap
    * debounce
    * sample
    * Update RxJava version to 2.2.8

Partially fixes #1107
@qwwdfsad qwwdfsad marked this pull request as ready for review April 25, 2019 13:13
@qwwdfsad qwwdfsad requested a review from elizarov April 25, 2019 13:13
    * Yield support in test dispatcher
    * Allow partial override of coroutine context
    * Code style fixes
@qwwdfsad qwwdfsad merged commit 4d5246a into master Apr 26, 2019
@qwwdfsad qwwdfsad deleted the version-1.2.1 branch July 15, 2019 17:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants