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=0.1 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI,RCVD_IN_BL_SPAMCOP_NET,SPF_HELO_PASS, SPF_PASS autolearn=no 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)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 8FEEA1F4EB for ; Tue, 18 Feb 2025 18:40:16 +0000 (UTC) Authentication-Results: dcvr.yhbt.net; dkim=pass (1024-bit key; unprotected) header.d=ml.ruby-lang.org header.i=@ml.ruby-lang.org header.a=rsa-sha256 header.s=mail header.b=f5UNHu+q; 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=hMDvJV0v; dkim-atps=neutral DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ml.ruby-lang.org; s=mail; t=1739904014; bh=h3K4Xret+NtFOJSAx7mS/VGbThRTi6g2zn/5x8CbEaQ=; 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=f5UNHu+qYcEyPALSjkJgYk8ehN/ZUEI5lnqRN61Mg9EELQ1XXCUQ4ODgbGg3PqpRv zyrzuRUrD7h/WOt7SL7fMdY36n9K5Cg7ha6AGAblz7UA1Z1thiCfflnU7HZusVxTy4 BaGTPoQChGSAReayXye4m+5ovuOcX1x8GfelIVcA= Received: from nue.mailmanlists.eu (localhost [IPv6:::1]) by nue.mailmanlists.eu (Postfix) with ESMTP id 184B3469D9 for ; Tue, 18 Feb 2025 18:40:14 +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=hMDvJV0v; dkim-atps=neutral Received: from s.wrqvtbkv.outbound-mail.sendgrid.net (s.wrqvtbkv.outbound-mail.sendgrid.net [149.72.123.24]) by nue.mailmanlists.eu (Postfix) with ESMTPS id B18C0469B8 for ; Tue, 18 Feb 2025 18:40:08 +0000 (UTC) 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=NDCfbs7HiKJ7Vnw7DQAphq6hN3eejvYQSrfQGcXX/3c=; b=hMDvJV0vqOY2Aqw4PqmBerd55j0ZRewUZcSKkgzmCTS+EkT98UedhpTDtewGtAFE1DJz pj0Mkr7+pZy2EICiBdFuXfCU6e+TrIFab1QEUW0sAFGFyAkAmE4BNsnq7HIx/yCsl2OVEm w/STff0bJjDZ7WbfaKkobuGX9SAGUJ4ybaKMat1BBnixpYRmlr1Ug62OE4/Qfno3DO1GGX myBquqKeVohlrazxQvP0uRsQVzJh9NdC6q7pE3xf4OU2+8ItH8NCcGFqR3aUgf2nWj0dn3 nsKGjsj/gCLAEHQNxcZs/8QuANfEaccV65K4G/unLqARAuMh+UKEU3Uu3CBF1vmQ== Received: by recvd-5f54b5d587-6btv9 with SMTP id recvd-5f54b5d587-6btv9-1-67B4D407-B 2025-02-18 18:40:07.145528192 +0000 UTC m=+8284569.224953399 Received: from herokuapp.com (unknown) by geopod-ismtpd-20 (SG) with ESMTP id eSYDkNJkQQqPI4MbgE846w for ; Tue, 18 Feb 2025 18:40:07.094 +0000 (UTC) Date: Tue, 18 Feb 2025 18:40:07 +0000 (UTC) Message-ID: References: Mime-Version: 1.0 X-Redmine-Project: ruby-master X-Redmine-Issue-Tracker: Bug X-Redmine-Issue-Id: 20968 X-Redmine-Issue-Author: koic X-Redmine-Issue-Priority: Normal X-Redmine-Sender: mame 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: 97829 X-SG-EID: =?us-ascii?Q?u001=2Ep+ckLDtT+4Y5c+H0YCkEnsuWiCQmn3OZA=2F9FzjoR6ZZlPaMv54M7EFoSM?= =?us-ascii?Q?CX5Trc79ep2R5F+0oYS4n23jq1cv+U6MvmxPY76?= =?us-ascii?Q?oYp75HFLQl8KcgV2jXRkY=2FEJJ7giRtofk0rlpNN?= =?us-ascii?Q?Srg2U89o4bZSwV5fnkWq=2FWYad0kE0BIZ=2FtZqsyA?= =?us-ascii?Q?wcMZd0UfI8XieQUPH3UvI1KfieI4mJyZQfy7Iet?= =?us-ascii?Q?ham84Qx6NINWHf1E3TKx6id=2FX2dbA+HBZ2VDzvs?= =?us-ascii?Q?hPNA?= To: ruby-core@ml.ruby-lang.org X-Entity-ID: u001.I8uzylDtAfgbeCOeLBYDww== Message-ID-Hash: 7HHHQTPYUA6VAVMHBXITKJZDD64YEK5O X-Message-ID-Hash: 7HHHQTPYUA6VAVMHBXITKJZDD64YEK5O 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.9 Precedence: list Reply-To: Ruby developers Subject: [ruby-core:121107] [Ruby master Bug#20968] `Array#fetch_values` unexpected method name in stack trace List-Id: Ruby developers Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: From: "mame (Yusuke Endoh) via ruby-core" Cc: "mame (Yusuke Endoh)" Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Issue #20968 has been updated by mame (Yusuke Endoh). This issue was discussed briefly at the dev meeting and Matz agreed with koic's expectation. https://github.com/ruby/dev-meeting-log/blob/47882270bd90fb0027e8fe62e421b398d6b3195b/2025/DevMeeting-2025-01-09.md?plain=1#L454 --- The following is my opinion. I agree that this is not a bug, but I think koic's expectations are clearly better than the current from a user benefit perspective, not from a consistency perspective. I think it is significantly unlikely that `:211` is valuable information for user to debug a bug. It would be more convenient to combine `` backtraces into one and substitute the name of the calling Ruby source file and line number, as in the current C-implemented method. ---------------------------------------- Bug #20968: `Array#fetch_values` unexpected method name in stack trace https://bugs.ruby-lang.org/issues/20968#change-112027 * Author: koic (Koichi ITO) * Status: Open * ruby -v: ruby 3.4.0dev (2024-12-19T04:44:56Z master 2783868de2) +PRISM [x86_64-darwin23] * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- It seems that the current Ruby implementation is displaying unexpected method name in stack trace. ## Expected Similar to `Hash#fetch_values`, the method name `Array#fetch_values` is expected to be displayed in the stack trace. ```console $ ruby -e '{k: 42}.fetch_values(:unknown)' -e:1:in 'Hash#fetch_values': key not found: :unknown (KeyError) from -e:1:in '
' $ ruby -e '[1].fetch_values(42)' -e:1:in 'Array#fetch_values': index 42 outside of array bounds: -1...1 (IndexError) from -e:1:in '
' ``` ## Actual The stack trace displays the `Array#fetch` method, which user is not aware of, along with the `` stack trace. ```console $ ruby -e '[1].fetch_values(42)' :211:in 'Array#fetch': index 42 outside of array bounds: -1...1 (IndexError) from :211:in 'block in Array#fetch_values' from :211:in 'Array#map!' from :211:in 'Array#fetch_values' from -e:1:in '
' ``` It likely requires an approach such as implementing it in C, as suggested in https://github.com/ruby/ruby/pull/11555. -- 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/lists/ruby-core.ml.ruby-lang.org/