From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on starla X-Spam-Level: X-Spam-Status: No, score=-1.1 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_HELO_PASS,SPF_PASS, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 Received: from nue.mailmanlists.eu (nue.mailmanlists.eu [94.130.110.93]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id BD5D51F406 for ; Tue, 26 Dec 2023 16:46:17 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=pass (1024-bit key; secure) header.d=ml.ruby-lang.org header.i=@ml.ruby-lang.org header.a=rsa-sha256 header.s=mail header.b=hxqtT2RJ; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=ruby-lang.org header.i=@ruby-lang.org header.a=rsa-sha256 header.s=s1 header.b=fLJW2GWY; dkim-atps=neutral Received: from nue.mailmanlists.eu (localhost [127.0.0.1]) by nue.mailmanlists.eu (Postfix) with ESMTP id 5885B819BE; Tue, 26 Dec 2023 16:46:09 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ml.ruby-lang.org; s=mail; t=1703609169; bh=MBpNuwgimxUjlH8mwtH5TanSfzBfoXNLFY3mU+N2gY4=; h=Date:References:To:Reply-To:Subject:List-Id:List-Archive: List-Help:List-Owner:List-Post:List-Subscribe:List-Unsubscribe: From:Cc:From; b=hxqtT2RJjC/9uvcqo3T/2bFIhuyyBLlTsFZQkSSHnB6lIuQCbPQcqO2AgwVf9wKGv SKEEsP1i35XQBwy970JdKy5NVeUu5XpXAWFHro4vdunkrFHLT1EZv/n20nuU6x685W cr2OAmAsJT4P8mSvGDH9kY4ZJt7FQ/4h3vsDVRgw= Received: from wrqvtvtt.outbound-mail.sendgrid.net (wrqvtvtt.outbound-mail.sendgrid.net [149.72.120.119]) by nue.mailmanlists.eu (Postfix) with ESMTPS id 42291819B5 for ; Tue, 26 Dec 2023 16:46:06 +0000 (UTC) Authentication-Results: nue.mailmanlists.eu; dkim=pass (2048-bit key; unprotected) header.d=ruby-lang.org header.i=@ruby-lang.org header.a=rsa-sha256 header.s=s1 header.b=fLJW2GWY; dkim-atps=neutral DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ruby-lang.org; h=from:references:subject:mime-version:content-type: content-transfer-encoding:list-id:to:cc:content-type:from:subject:to; s=s1; bh=wDU1vctPbAjppM5zd2b6rm0vHcxXSocIxk0UllGt7bw=; b=fLJW2GWYPVqMi30Yha2kTLsQd2TJ7j4qs/qljV5Jg0TlTrzFUiF8wMECLr079pgcmxlt mUhczYRjH+LxowTb44Xu8IORfnRU7zJY1ugSfyOejWzNwjAP3/RKidyTmY/3yE4l9Ec36y NeIVqJp0rJ5XPS2f0BeH5G3iOYPPcENmicoJlSWs25KorPXyFZJPbAvwI9g3Yyt1aPu3KL 6FwXE6jl8qm3D01vd0Ex/qSE63FUEXtMom7Q6wltiOJoD3obV6x7cnMhrT/InHA1IOjJHQ jUyFdrIBTYCRL8w6/QsKfQqFZ3uiKQ2gbMNYSPtolumoIVwK8aOWw3s3aDljdotA== Received: by filterdrecv-6bb8954444-l4shx with SMTP id filterdrecv-6bb8954444-l4shx-1-658B034C-14 2023-12-26 16:46:04.710417624 +0000 UTC m=+1298542.161910254 Received: from herokuapp.com (unknown) by geopod-ismtpd-3 (SG) with ESMTP id leZBBHd_She-f0cEjdCdhA for ; Tue, 26 Dec 2023 16:46:04.652 +0000 (UTC) Date: Tue, 26 Dec 2023 16:46:04 +0000 (UTC) Message-ID: References: Mime-Version: 1.0 X-Redmine-Project: ruby-master X-Redmine-Issue-Tracker: Bug X-Redmine-Issue-Id: 20089 X-Redmine-Issue-Author: rmosolgo X-Redmine-Sender: rmosolgo X-Mailer: Redmine X-Redmine-Host: bugs.ruby-lang.org X-Redmine-Site: Ruby Issue Tracking System X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-Redmine-MailingListIntegration-Message-Ids: 92442 X-SG-EID: =?us-ascii?Q?3emfgClVsx+Kr4SsOeAt7OfdSnJSxA3SSOlByn1fytpmpcorKv9vgIMl5jD9a7?= =?us-ascii?Q?SLwuiXC2QWVJJ0VHkzDod8XtnhRh4IGbLqdlyQJ?= =?us-ascii?Q?0Mis=2F5WkMMDruNN56ZRz4oAif85yuMeIjNStAVV?= =?us-ascii?Q?HLbULLTULhjr1MwFphaygwc6Nsj7=2FabT8EQEzPg?= =?us-ascii?Q?7m8HLBGjbuVMKKrnVO+Qc72EzjKyhwXpWFB5MLn?= =?us-ascii?Q?idtnM9=2FnDjYnWX1=2Fp1WWZzjLPvoDIMzHYvJ2YvR?= =?us-ascii?Q?qhL2hFcAOhHwKsIeNVarA=3D=3D?= To: ruby-core@ml.ruby-lang.org X-Entity-ID: b/2+PoftWZ6GuOu3b0IycA== Message-ID-Hash: IH3H6J5NVPQIO6ULMLPK7SDWDZQTRMZD X-Message-ID-Hash: IH3H6J5NVPQIO6ULMLPK7SDWDZQTRMZD X-MailFrom: bounces+313651-b711-ruby-core=ml.ruby-lang.org@em5188.ruby-lang.org X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.3 Precedence: list Reply-To: Ruby developers Subject: [ruby-core:115911] [Ruby master Bug#20089] Fiber#kill transfers to root fiber List-Id: Ruby developers Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: From: "rmosolgo (Robert Mosolgo) via ruby-core" Cc: "rmosolgo (Robert Mosolgo)" Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Issue #20089 has been reported by rmosolgo (Robert Mosolgo). ---------------------------------------- Bug #20089: Fiber#kill transfers to root fiber https://bugs.ruby-lang.org/issues/20089 * Author: rmosolgo (Robert Mosolgo) * Status: Open * Priority: Normal * ruby -v: ruby 3.3.0 (2023-12-25 revision 5124f9ac75) [x86_64-darwin22] * Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- I was hoping to use `Fiber#kill` to clean up formerly `.transfer`-d Fibers and work around https://bugs.ruby-lang.org/issues/20081, but I found that `Fiber#kill` has a similar control flow jump behavior. Is this on purpose, or a bug? Here's a script to test the behavior: ```ruby manager = Fiber.new do worker = Fiber.new do puts "2. Begin Worker" manager.transfer puts "This should never print -- killed" end puts "1. Transfer to Worker" worker.transfer puts "3. Killing Worker" worker.kill puts "4. Finished manager" end manager.transfer puts "5. Finished script" ``` I expected items `1` through `5` to be printed in order, but in fact, `4` is never printed: ``` $ ruby fiber_transfer_test.rb 1. Transfer to Worker 2. Begin Worker 3. Killing Worker 5. Finished script ``` It seems like `worker.kill` is transferring control to the top-level fiber instead of giving it back to `manager`. I also tried having the thread kill _itself_, hoping it would return to the fiber that originally `.transfer`ed to it, but it also seems to jump out: ```ruby manager = Fiber.new do worker = Fiber.new do puts "2. Begin Worker" manager.transfer Fiber.current.kill puts "This should never print -- killed" end puts "1. Transfer to Worker" worker.transfer puts "3. Killing Worker" worker.transfer puts "4. Finished manager" end manager.transfer puts "5. Finished script" ``` Prints: ``` 1. Transfer to Worker 2. Begin Worker 3. Killing Worker 5. Finished script ``` -- https://bugs.ruby-lang.org/ ______________________________________________ ruby-core mailing list -- ruby-core@ml.ruby-lang.org To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-core.ml.ruby-lang.org/