async 2.40.0 → 2.41.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 58621f01c092a84a7cf528ed883d25b167fbc9be35cb85547b6f7f4d744d4f92
-  data.tar.gz: 2543abb1cf45a52ba369af6e86aa6c93c29d9ece5dda28f3a846d28f16a49cb0
+  metadata.gz: c707fb6001b639a32c63b2eac330cde48e8d411dc766fca44b98816991f4daea
+  data.tar.gz: cff7be5da559c06c9d040717057270d9e2369f26b9ac481fa56e92d8383103b5
 SHA512:
-  metadata.gz: f2696102d8dbfa20b3f55ebeb772f5c536ab20b160383ab3d5a6b42a8b402e674fc4b10115fb20be45537e33e615d971f00b1d9b8a43611ab6b6bf64fa163351
-  data.tar.gz: 38ec316c57fe4bf60447b6e6406d41acfe0eded9d6f2ed8e6d64e221b08bf75d4e6e3110969d469ab37518116b50d0a7e65021ce896fb078fe8871a3fb9675ff
+  metadata.gz: 8ff5660626ce3c460bfe1b5796185a3421c5b060da99624a0fcf8943e2a634c5c5f1919ca281d29debaf04687ed5be6b7f70c36cf63a12bd96a776a06ec7e3ac
+  data.tar.gz: c5d0a80e1f6795afabd7b0ae1f5dda8d3d9f5083be0cbb2b5cb121977e389b68c71ef87e875d521bed65080652be5e5843061f32247a6bab35ef20e1d06e5484

data/lib/async/scheduler.rb

@@ -525,12 +525,25 @@ module Async
 			cancel
 		end
 		
-		private def run_loop(&block)
+		# Run the event loop, until the scheduler is interrupted or finished.
+		#
+		# @parameter initial [Proc | Nil] The initial block to execute before the first loop iteration.
+		# @yields {...} The block to execute on each loop iteration.
+		# @raises {Interrupt} If the scheduler is interrupted.
+		private def run_loop(initial = nil, &block)
 			interrupt = nil
 			
 			begin
 				# In theory, we could use Exception here to be a little bit safer, but we've only shown the case for SignalException to be a problem, so let's not over-engineer this.
 				Thread.handle_interrupt(::SignalException => :never) do
+					if initial
+						begin
+							initial.call
+						ensure
+							initial = nil
+						end
+					end
+					
 					until self.interrupted?
 						# If we are finished, we need to exit:
 						break unless yield
@@ -570,9 +583,15 @@ module Async
 			begin
 				@profiler&.start
 				
-				initial_task = self.async(...) if block_given?
+				initial_task = nil
 				
-				self.run_loop do
+				if block_given?
+					initial = proc do
+						initial_task = self.async(...)
+					end
+				end
+				
+				self.run_loop(initial) do
 					run_once
 				end
 				

data/lib/async/version.rb

@@ -5,5 +5,5 @@
 
 # @namespace
 module Async
-	VERSION = "2.40.0"
+	VERSION = "2.41.0"
 end

data/lib/kernel/sync.rb

@@ -32,8 +32,7 @@ module Kernel
 			
 			begin
 				# Use finished: false to suppress warnings since we're handling exceptions explicitly
-				task = reactor.async(annotation: annotation, finished: false, &block)
-				reactor.run
+				task = reactor.run(annotation: annotation, finished: false, &block)
 				return task.wait
 			ensure
 				Fiber.set_scheduler(nil)

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.41.0
+
+  - **Fixed**: Protect initial task from Interrupt exceptions.
+
 ### v2.40.0
 
   - Introduce `Async::Condition#waiting_count`. This allows you to see how many tasks are currently waiting on the condition, which can be useful for debugging and monitoring purposes.
@@ -75,10 +79,6 @@ Please see the [project releases](https://socketry.github.io/async/releases/inde
 
   - Fix incorrect handling of spurious wakeups in `Async::Promise#wait`, which could lead to premature (incorrect) resolution of the promise.
 
-### v2.35.0
-
-  - `Process.fork` is now properly handled by the Async fiber scheduler, ensuring that the scheduler state is correctly reset in the child process after a fork. This prevents issues where the child process inherits the scheduler state from the parent, which could lead to unexpected behavior.
-
 ## See Also
 
   - [async-http](https://github.com/socketry/async-http) — Asynchronous HTTP client/server.

data/releases.md

@@ -1,5 +1,9 @@
 # Releases
 
+## v2.41.0
+
+  - **Fixed**: Protect initial task from Interrupt exceptions.
+
 ## v2.40.0
 
   - Introduce `Async::Condition#waiting_count`. This allows you to see how many tasks are currently waiting on the condition, which can be useful for debugging and monitoring purposes.

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: async
 version: !ruby/object:Gem::Version
-  version: 2.40.0
+  version: 2.41.0
 platform: ruby
 authors:
 - Samuel Williams