loom-dev  

Messages by Thread

• Small issue with StructuredTaskScopeImpl.ensureOwner Kasper Nielsen
  • Re: Small issue with StructuredTaskScopeImpl.ensureOwner David Alayachew
  • Re: Small issue with StructuredTaskScopeImpl.ensureOwner Alan Bateman
  • Re: Small issue with StructuredTaskScopeImpl.ensureOwner Kasper Nielsen
• Question on small optimization Dmitry Zaslavsky
  • Re: Question on small optimization Alan Bateman
• git: openjdk/loom: master: 26 new changesets duke
• Rethinking Exceptions in the Context of Loom and Structured Concurrency Eric Kolotyluk
  • Re: Rethinking Exceptions in the Context of Loom and Structured Concurrency Davor Hrg
  • Re: Rethinking Exceptions in the Context of Loom and Structured Concurrency Holo The Sage Wolf
  • Re: Rethinking Exceptions in the Context of Loom and Structured Concurrency Eric Kolotyluk
  • Re: Rethinking Exceptions in the Context of Loom and Structured Concurrency Alex Otenko
  • Re: Rethinking Exceptions in the Context of Loom and Structured Concurrency Robert Engels
  • Re: Rethinking Exceptions in the Context of Loom and Structured Concurrency Jonas Nordin
  • Re: Rethinking Exceptions in the Context of Loom and Structured Concurrency Robert Engels
  • Re: Rethinking Exceptions in the Context of Loom and Structured Concurrency David Alayachew
  • Re: Rethinking Exceptions in the Context of Loom and Structured Concurrency David Alayachew
  • Re: Rethinking Exceptions in the Context of Loom and Structured Concurrency Eric Kolotyluk
  • Re: Rethinking Exceptions in the Context of Loom and Structured Concurrency Robert Engels
  • Re: Rethinking Exceptions in the Context of Loom and Structured Concurrency Brian Goetz
  • Re: Rethinking Exceptions in the Context of Loom and Structured Concurrency Robert Engels
  • Re: Rethinking Exceptions in the Context of Loom and Structured Concurrency Robert Engels
  • Re: Rethinking Exceptions in the Context of Loom and Structured Concurrency David Alayachew
  • Re: Rethinking Exceptions in the Context of Loom and Structured Concurrency Eric Kolotyluk
  • Re: Rethinking Exceptions in the Context of Loom and Structured Concurrency Attila Kelemen
  • Re: Rethinking Exceptions in the Context of Loom and Structured Concurrency Alan Bateman
  • Re: Rethinking Exceptions in the Context of Loom and Structured Concurrency Alan Bateman
  • Re: Rethinking Exceptions in the Context of Loom and Structured Concurrency Attila Kelemen
  • Re: Rethinking Exceptions in the Context of Loom and Structured Concurrency Remi Forax
• Timeouts in structured concurrency Holo The Sage Wolf
  • Re: Timeouts in structured concurrency David Alayachew
  • Re: Timeouts in structured concurrency Holo The Sage Wolf
  • Re: Timeouts in structured concurrency Eric Kolotyluk
  • Re: Timeouts in structured concurrency Holo The Sage Wolf
  • Re: Timeouts in structured concurrency Robert Engels
  • Re: Timeouts in structured concurrency Eric Kolotyluk
  • Re: Timeouts in structured concurrency Eric Kolotyluk
  • Re: Timeouts in structured concurrency Alan Bateman
  • Re: Timeouts in structured concurrency Remi Forax
  • Re: Timeouts in structured concurrency Alan Bateman
  • Re: Timeouts in structured concurrency Robert Engels
  • Re: Timeouts in structured concurrency David Alayachew
  • Re: Timeouts in structured concurrency Alan Bateman
  • Re: Timeouts in structured concurrency David Alayachew
  • Re: Timeouts in structured concurrency David Alayachew
  • Re: Timeouts in structured concurrency Alan Bateman
  • Re: Timeouts in structured concurrency Holo The Sage Wolf
  • Re: Timeouts in structured concurrency David Alayachew
• git: openjdk/loom: master: 57 new changesets duke
  • git: openjdk/loom: master: 57 new changesets duke
• [StructuredTaskScope] Poor man's "back pressure" ? Benoit LEFEVRE -CAMPUS-
  • Re: [StructuredTaskScope] Poor man's "back pressure" ? Attila Kelemen
  • Re: [StructuredTaskScope] Poor man's "back pressure" ? Alan Bateman
  • Re: [StructuredTaskScope] Poor man's "back pressure" ? Attila Kelemen
  • Re: [StructuredTaskScope] Poor man's "back pressure" ? Benoit LEFEVRE -CAMPUS-
  • Re: [StructuredTaskScope] Poor man's "back pressure" ? Holo The Sage Wolf
  • Re: [StructuredTaskScope] Poor man's "back pressure" ? Attila Kelemen
  • Re: [StructuredTaskScope] Poor man's "back pressure" ? Alan Bateman
  • Re: [StructuredTaskScope] Poor man's "back pressure" ? Attila Kelemen
• class loading deadlock Benjamin Peterson
  • Re: class loading deadlock Alan Bateman
  • Re: class loading deadlock Benjamin Peterson
  • Re: class loading deadlock Patricio Chilano Mateo
  • Re: class loading deadlock Benjamin Peterson
  • Re: class loading deadlock Patricio Chilano Mateo
  • Re: class loading deadlock Benjamin Peterson
  • Re: class loading deadlock Patricio Chilano Mateo
• git: openjdk/loom: fibers: 27 new changesets duke
• git: openjdk/loom: master: 23 new changesets duke
  • git: openjdk/loom: master: 23 new changesets duke
• Non-obvious behavior in newVirtualThreadPerTaskExecutor Stig Rohde Døssing
  • Re: Non-obvious behavior in newVirtualThreadPerTaskExecutor Viktor Klang
  • Re: Non-obvious behavior in newVirtualThreadPerTaskExecutor Stig Rohde Døssing
  • Re: Non-obvious behavior in newVirtualThreadPerTaskExecutor Alan Bateman
  • Re: Non-obvious behavior in newVirtualThreadPerTaskExecutor Attila Kelemen
  • Re: Non-obvious behavior in newVirtualThreadPerTaskExecutor Robert Engels
  • Re: Non-obvious behavior in newVirtualThreadPerTaskExecutor Attila Kelemen
• git: openjdk/loom: master: 7 new changesets duke
• "Memory leak" caused by WorkQueue#topLevelExec Olivier Peyrusse
  • Re: "Memory leak" caused by WorkQueue#topLevelExec Vicente Pader
  • Re: "Memory leak" caused by WorkQueue#topLevelExec Olivier Peyrusse
  • Re: "Memory leak" caused by WorkQueue#topLevelExec David Holmes
  • Re: "Memory leak" caused by WorkQueue#topLevelExec Robert Engels
  • Re: "Memory leak" caused by WorkQueue#topLevelExec David Holmes
• git: openjdk/loom: fibers: 29 new changesets duke
• Virtual vs platform performance at 10K HTTP requests David
  • Re: Virtual vs platform performance at 10K HTTP requests Robert Engels
  • Re: Virtual vs platform performance at 10K HTTP requests Alan Bateman
  • Re: Virtual vs platform performance at 10K HTTP requests David
  • Re: Virtual vs platform performance at 10K HTTP requests Thomas Matthijs
  • Re: Virtual vs platform performance at 10K HTTP requests Cay Horstmann
  • Re: Virtual vs platform performance at 10K HTTP requests Viktor Klang
  • Re: Virtual vs platform performance at 10K HTTP requests Alan Bateman
  • Re: Virtual vs platform performance at 10K HTTP requests Robert Engels
  • Re: Virtual vs platform performance at 10K HTTP requests Daniel Andres Pelaez Lopez
  • Re: Virtual vs platform performance at 10K HTTP requests David
  • Re: Virtual vs platform performance at 10K HTTP requests Robert Engels
  • Re: Virtual vs platform performance at 10K HTTP requests Alan Bateman
  • Re: Virtual vs platform performance at 10K HTTP requests David
• Question About PR #27802 and JDK 25 Backport Mengyang Li
  • Re: Question About PR #27802 and JDK 25 Backport Patricio Chilano Mateo
• Significant degradation of Thread.sleep with virtual threads in JDK 25 vs JDK 21 Fredriksson, Christian
  • Re: Significant degradation of Thread.sleep with virtual threads in JDK 25 vs JDK 21 Alan Bateman
  • Re: Significant degradation of Thread.sleep with virtual threads in JDK 25 vs JDK 21 Fredriksson, Christian
  • Re: Significant degradation of Thread.sleep with virtual threads in JDK 25 vs JDK 21 Pavel Rappo
  • Re: Significant degradation of Thread.sleep with virtual threads in JDK 25 vs JDK 21 Alan Bateman
  • RE: Significant degradation of Thread.sleep with virtual threads in JDK 25 vs JDK 21 Fredriksson, Christian
  • Re: Significant degradation of Thread.sleep with virtual threads in JDK 25 vs JDK 21 Alan Bateman
  • Re: Significant degradation of Thread.sleep with virtual threads in JDK 25 vs JDK 21 Fredriksson, Christian
  • Re: Significant degradation of Thread.sleep with virtual threads in JDK 25 vs JDK 21 Alan Bateman
  • Re: Significant degradation of Thread.sleep with virtual threads in JDK 25 vs JDK 21 Fredriksson, Christian
  • Re: Significant degradation of Thread.sleep with virtual threads in JDK 25 vs JDK 21 Alan Bateman
  • Re: Significant degradation of Thread.sleep with virtual threads in JDK 25 vs JDK 21 Attila Kelemen
• git: openjdk/loom: master: 29 new changesets duke
  • git: openjdk/loom: master: 29 new changesets duke
• git: openjdk/loom: fibers: 32 new changesets duke
  • git: openjdk/loom: fibers: 32 new changesets duke
  • git: openjdk/loom: fibers: 32 new changesets duke
• git: openjdk/loom: master: 39 new changesets duke
• git: openjdk/loom: fibers: 43 new changesets duke
• JDK 26 EA builds: changes to avoid pinning while waiting for class initialization Patricio Chilano Mateo
  • Re: JDK 26 EA builds: changes to avoid pinning while waiting for class initialization Viktor Klang
• git: openjdk/loom: master: 19 new changesets duke
• git: openjdk/loom: fibers: 21 new changesets duke
• git: openjdk/loom: fibers: 44 new changesets duke
  • git: openjdk/loom: fibers: 44 new changesets duke
  • git: openjdk/loom: fibers: 44 new changesets duke
  • git: openjdk/loom: fibers: 44 new changesets duke
• git: openjdk/loom: master: 43 new changesets duke
  • git: openjdk/loom: master: 43 new changesets duke
  • git: openjdk/loom: master: 43 new changesets duke
  • git: openjdk/loom: master: 43 new changesets duke
• git: openjdk/loom: master: 33 new changesets duke
• git: openjdk/loom: fibers: 34 new changesets duke
• git: openjdk/loom: master: 21 new changesets duke
• git: openjdk/loom: fibers: 25 new changesets duke
  • git: openjdk/loom: fibers: 25 new changesets duke
• git: openjdk/loom: fibers: Allow pollerMode=3 when using custom default scheduler duke
• git: openjdk/loom: fibers: 17 new changesets duke
• git: openjdk/loom: fibers: 12 new changesets duke
  • git: openjdk/loom: fibers: 12 new changesets duke
• Re: loom-dev Digest, Vol 95, Issue 2 Xialin Liu
  • Re: loom-dev Digest, Vol 95, Issue 2 Alan Bateman
  • Re: loom-dev Digest, Vol 95, Issue 2 Patricio Chilano Mateo
• Fwd: Class initialization pinning deadlock with Log4j 2 Danny Thomas
  • Re: Class initialization pinning deadlock with Log4j 2 Francesco Nigro
  • Re: Fwd: Class initialization pinning deadlock with Log4j 2 Alan Bateman
  • Re: Fwd: Class initialization pinning deadlock with Log4j 2 Patricio Chilano Mateo
  • Re: Fwd: Class initialization pinning deadlock with Log4j 2 Danny Thomas
• git: openjdk/loom: master: 31 new changesets duke
  • git: openjdk/loom: master: 31 new changesets duke
• git: openjdk/loom: master: 14 new changesets duke
  • git: openjdk/loom: master: 14 new changesets duke
• git: openjdk/loom: fibers: 53 new changesets duke
  • git: openjdk/loom: fibers: 53 new changesets duke
  • git: openjdk/loom: fibers: 53 new changesets duke
• git: openjdk/loom: master: 11 new changesets duke
• git: openjdk/loom: fibers: 14 new changesets duke
• Adapted StructuredTaskScope for Context and cancellation Wesley Hill
  • Re: Adapted StructuredTaskScope for Context and cancellation Alan Bateman
  • Re: Adapted StructuredTaskScope for Context and cancellation Wesley Hill
  • Re: Adapted StructuredTaskScope for Context and cancellation Alan Bateman
• git: openjdk/loom: master: 49 new changesets duke
• StructuredTaskScope.TimeoutException vs UncheckedTimeoutException Pavel Rappo
  • Re: StructuredTaskScope.TimeoutException vs UncheckedTimeoutException Robert Engels
  • Re: StructuredTaskScope.TimeoutException vs UncheckedTimeoutException Pavel Rappo
  • Re: StructuredTaskScope.TimeoutException vs UncheckedTimeoutException Pavel Rappo
  • Re: StructuredTaskScope.TimeoutException vs UncheckedTimeoutException Alan Bateman
  • Re: StructuredTaskScope.TimeoutException vs UncheckedTimeoutException Pavel Rappo
  • Re: StructuredTaskScope.TimeoutException vs UncheckedTimeoutException Viktor Klang
• Structured Concurrency Feedback Josiah Noel
  • Re: Structured Concurrency Feedback Filip Egeric
  • Re: Structured Concurrency Feedback Alan Bateman
  • Re: Structured Concurrency Feedback Filip Egeric
  • Re: Structured Concurrency Feedback Alan Bateman
  • Re: Structured Concurrency Feedback Alan Bateman
  • Re: Structured Concurrency Feedback Viktor Klang
• git: openjdk/loom: fibers: 20 new changesets duke
  • git: openjdk/loom: fibers: 20 new changesets duke
• git: openjdk/loom: fibers: 59 new changesets duke
  • git: openjdk/loom: fibers: 59 new changesets duke
• git: openjdk/loom: master: 37 new changesets duke
  • git: openjdk/loom: master: 37 new changesets duke
  • git: openjdk/loom: master: 37 new changesets duke
• StructureTaskScope joiner naming Remi Forax
  • Re: StructureTaskScope joiner naming David Alayachew
  • Re: StructureTaskScope joiner naming forax
  • Re: StructureTaskScope joiner naming David Alayachew
  • Re: StructureTaskScope joiner naming David Alayachew
  • Re: StructureTaskScope joiner naming David Alayachew
  • Re: StructureTaskScope joiner naming Paul Bjorkstrand
  • Re: StructureTaskScope joiner naming Alan Bateman
• git: openjdk/loom: master: 42 new changesets duke
  • git: openjdk/loom: master: 42 new changesets duke
  • git: openjdk/loom: master: 42 new changesets duke
  • git: openjdk/loom: master: 42 new changesets duke
• git: openjdk/loom: master: 32 new changesets duke
  • git: openjdk/loom: master: 32 new changesets duke
  • git: openjdk/loom: master: 32 new changesets duke
• git: openjdk/loom: master: 17 new changesets duke

• Earlier messages
• Later messages