Merged
Conversation
neko-kai
force-pushed
the
feature/distage-testkit-js-followup
branch
from
d961a4c to
540e161
Compare
neko-kai
force-pushed
the
feature/distage-testkit-js-followup-2
branch
from
b30daf5 to
cbd9ca6
Compare
Base automatically changed from
feature/distage-testkit-js-followup
to
develop
December 24, 2025 23:20
…rrect JS-specific time-UUID makeNode impl. Use cats-effect SecureRandom in Entropy1; drop linking requirement for scalajs-java-securerandom.
…s required to implement other protected methods
neko-kai
force-pushed
the
feature/distage-testkit-js-followup-2
branch
from
53ab194 to
2031122
Compare
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## develop #2329 +/- ##
===========================================
+ Coverage 67.32% 67.82% +0.51%
===========================================
Files 636 635 -1
Lines 12640 12808 +168
Branches 1540 1588 +48
===========================================
+ Hits 8508 8686 +178
+ Misses 4132 4122 -10 🚀 New features to boost your workflow:
|
… and ZIO in distage-testkit - Add syncThrowableInterruptible to IO2 (defaults to syncThrowable) - Override in AsyncZio to use ZIO.attemptBlockingInterrupt - Add maybeSuspendInterruptible to QuasiIO, use in RunnerToF.BlockingImpl - For cats-effect, uses IO.interruptible; for ZIO, uses attemptBlockingInterrupt This ensures fiber cancellation propagates as thread interrupt to the actual compute thread, regardless of thread shifts from async operations.
…gnify required bindings.
issue was caused by `ZIO.attemptBlockingInterrupt` bombarding nested unsafeRun with interrupts and seemingly preventing `interruptionFiber.start` (not `startConcurrently`) from evaluating up to `tell(FiberMessage.InterruptSignal)` Fixed by sending `tell` immediately, not running any fibers - avoiding any java calls that could trigger InterruptedException
…ocket missing and docker pull failure, unless system property `izumi.distage.testkit.skip.docker.failures` or env var `IZUMI_SKIP_DOCKER_FAILURES` is set
- adobe/kafka was incompatible with KafkaKRaftDocker settings
This reverts commit 4deb631.
…2.unsafe.run implementation (interruption handling fix to arrive in ZIO 1.2.25)
- Update pureconfig 0.17.8 → 0.17.10 (Scala 2.13, 3) - Keep pureconfig 0.17.8 for Scala 2.12 (0.17.9+ dropped 2.12 support) - Bump Scala 2.12.20 → 2.12.21 (JDK 25 support) - Bump ScalaJS 1.20.1 → 1.21.0
…stkit-js-followup-2 # Conflicts: # flake.lock
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.