async 2.44.0 → 2.45.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: b7ec9caa7a2e151195fa3da29d96fb2fe0f02399b89d17d93eeb7507667596ad
-  data.tar.gz: ed1548c91c789ef1ffbc268a1470cde4f1d1dc1ffed12678825e1d253b0a8d67
+  metadata.gz: 3d9408068579f9a742c20019cf9024bbc4c545c239c4c5178e929c377ac06b6c
+  data.tar.gz: 699c17d5dbff6502e1611252982c3595b7b84d57284010222462b838e683d1ac
 SHA512:
-  metadata.gz: d8cc76cc2cc6f3a19ce94383b4123e83b9274a3431b9dc2fc71bfff62946ef3dbad0b4c8f4c607b3071d219b5efc73315d589b10e4467c26e60bbd48eb2c6103
-  data.tar.gz: b914c7f81337ce52ae1aadb42b43f0d702c94847ae0052d326ee510a57c87517b957b5c0fd70988d9b08d4d9f061348b93dceaaf194b3d19ab809eb45c0387f7
+  metadata.gz: a40ca6a441ad341267c5782d089d512b45b36765afbdd1c6382ebb7f931e273cdf29d08ae3a446a0b624618981730c2ee69e15d39adb0956dc44fc1d2ccd2ab9
+  data.tar.gz: 325d951d894d7c2fb9cc042534e5e8d76c3edbeb81c061993204ef345af499cfd0fd71ebaae0a6fbbdfd62afdf99a859564554c9cb97dcd730111385948aebf1

data/context/getting-started.md

@@ -74,6 +74,42 @@ end
 puts "The number was: #{task.wait}"
 ```
 
+### Comparing `Async` and `Sync`
+
+If you are familiar with JavaScript's `async`/`await`, `Async{...}` is similar to calling an asynchronous function: it starts the work and returns a promise-like {ruby Async::Task} that you can wait on later.
+
+```ruby
+task = Async do
+	bar
+end
+
+task.wait # Returns the value of bar.
+```
+
+This is similar to JavaScript code that keeps the promise:
+
+```javascript
+const promise = bar();
+
+await promise; // Returns the value of bar.
+```
+
+`Sync{...}` is similar to immediately awaiting that work: it runs the block in an event loop and returns the block's value directly.
+
+```ruby
+result = Sync do
+	bar
+end
+```
+
+This is similar to:
+
+```javascript
+const result = await bar();
+```
+
+The main difference is that JavaScript starts with an event loop already available, while Ruby code needs one to be provided by a fiber scheduler. `Sync{...}` is the usual way to create or reuse that event loop when the caller wants a direct return value instead of a task.
+
 ## Creating a Fiber Scheduler
 
 The first (top level) async block will also create an instance of {ruby Async::Reactor} which is a subclass of {ruby Async::Scheduler} to handle the event loop. You can also do this directly using {ruby Fiber.set_scheduler}:

data/context/index.yaml

@@ -3,6 +3,8 @@
 ---
 description: A concurrency framework for Ruby.
 metadata:
+  bug_tracker_uri: https://github.com/socketry/async/issues
+  changelog_uri: https://github.com/socketry/async/blob/main/releases.md
   documentation_uri: https://socketry.github.io/async/
   funding_uri: https://github.com/sponsors/ioquatix/
   source_code_uri: https://github.com/socketry/async.git

data/lib/async/condition.rb

@@ -1,7 +1,7 @@
 # frozen_string_literal: true
 
 # Released under the MIT License.
-# Copyright, 2017-2025, by Samuel Williams.
+# Copyright, 2017-2026, by Samuel Williams.
 # Copyright, 2017, by Kent Gruber.
 # Copyright, 2026, by Robert Mosolgo.
 

data/lib/async/scheduler.rb

@@ -309,10 +309,12 @@ module Async
 		# @parameter timeout [Float | Nil] The maximum time to wait, or if nil, indefinitely.
 		def io_wait(io, events, timeout = nil)
 			fiber = Fiber.current
+			expired = false
 			
 			if timeout
 				# If an explicit timeout is specified, we expect that the user will handle it themselves:
 				timer = @timers.after(timeout) do
+					expired = true
 					fiber.transfer
 				end
 			elsif timeout = io.timeout
@@ -322,7 +324,13 @@ module Async
 				end
 			end
 			
-			return @selector.io_wait(fiber, io, events)
+			# A selector wait may return a falsy result when the fiber is resumed without the requested IO becoming ready. For example, a deferred unblock from a previous blocking operation may arrive after the fiber has moved on to this wait. Retry these stale or spurious wake-ups without resetting the original timer.
+			until result = @selector.io_wait(fiber, io, events)
+				# If the original timer resumed the fiber, the falsy result represents the timeout rather than a spurious wake-up:
+				return nil if expired
+			end
+			
+			return result
 		ensure
 			timer&.cancel!
 		end
@@ -415,7 +423,14 @@ module Async
 		# @returns [Process::Status] A process status instance.
 		# @asynchronous May be non-blocking..
 		def process_wait(pid, flags)
-			return @selector.process_wait(Fiber.current, pid, flags)
+			fiber = Fiber.current
+			
+			# A native process wait may be interrupted before the child exits. io-event reports this as `false` and leaves the retry policy to the scheduler. Retry only `false`, since `nil` is a legitimate result for `Process::WNOHANG`.
+			while true
+				status = @selector.process_wait(fiber, pid, flags)
+				
+				return status unless status == false
+			end
 		end
 		
 		# Wait for the specified IOs to become ready for the specified events.

data/lib/async/version.rb

@@ -5,5 +5,5 @@
 
 # @namespace
 module Async
-	VERSION = "2.44.0"
+	VERSION = "2.45.0"
 end

data/lib/kernel/async.rb

@@ -1,7 +1,7 @@
 # frozen_string_literal: true
 
 # Released under the MIT License.
-# Copyright, 2019-2024, by Samuel Williams.
+# Copyright, 2019-2026, by Samuel Williams.
 # Copyright, 2026, by Shopify Inc.
 
 require_relative "../async/reactor"

data/lib/kernel/sync.rb

@@ -1,7 +1,7 @@
 # frozen_string_literal: true
 
 # Released under the MIT License.
-# Copyright, 2019-2025, by Samuel Williams.
+# Copyright, 2019-2026, by Samuel Williams.
 # Copyright, 2020, by Brian Morearty.
 # Copyright, 2024, by Patrik Wenger.
 # Copyright, 2025-2026, by Shopify Inc.

data/readme.md

@@ -35,6 +35,10 @@ Please see the [project documentation](https://socketry.github.io/async/) for mo
 
 Please see the [project releases](https://socketry.github.io/async/releases/index) for all releases.
 
+### v2.45.0
+
+  - Fixed scheduler I/O and process waits returning prematurely after stale or interrupted wake-ups. I/O waits now preserve their original timeout, while blocking process waits retry and non-blocking `Process::WNOHANG` waits still return `nil`.
+
 ### v2.44.0
 
   - Fixed scheduler cleanup after forking while other fibers are blocked.
@@ -73,11 +77,6 @@ Please see the [project releases](https://socketry.github.io/async/releases/inde
   - Introduce `Async::Loop` for robust, time-aligned loops.
   - Add support for `Async::Promise#wait(timeout: N)`.
 
-### v2.36.0
-
-  - Introduce `Task#wait_all` which recursively waits for all children and self, excepting the current task.
-  - Introduce `Task#join` as an alias for `Task#wait` for compatibility with `Thread#join` and similar interfaces.
-
 ## See Also
 
   - [async-http](https://github.com/socketry/async-http) — Asynchronous HTTP client/server.

data/releases.md

@@ -1,5 +1,9 @@
 # Releases
 
+## v2.45.0
+
+  - Fixed scheduler I/O and process waits returning prematurely after stale or interrupted wake-ups. I/O waits now preserve their original timeout, while blocking process waits retry and non-blocking `Process::WNOHANG` waits still return `nil`.
+
 ## v2.44.0
 
   - Fixed scheduler cleanup after forking while other fibers are blocked.

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: async
 version: !ruby/object:Gem::Version
-  version: 2.44.0
+  version: 2.45.0
 platform: ruby
 authors:
 - Samuel Williams
@@ -109,14 +109,14 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '1.11'
+        version: '1.21'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '1.11'
+        version: '1.21'
 executables: []
 extensions: []
 extra_rdoc_files: []
@@ -173,6 +173,8 @@ homepage: https://github.com/socketry/async
 licenses:
 - MIT
 metadata:
+  bug_tracker_uri: https://github.com/socketry/async/issues
+  changelog_uri: https://github.com/socketry/async/blob/main/releases.md
   documentation_uri: https://socketry.github.io/async/
   funding_uri: https://github.com/sponsors/ioquatix/
   source_code_uri: https://github.com/socketry/async.git