ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: "professor (Todd Sedano) via ruby-core" <ruby-core@ml.ruby-lang.org>
To: ruby-core@ml.ruby-lang.org
Cc: "professor (Todd Sedano)" <noreply@ruby-lang.org>
Subject: [ruby-core:117691] [Ruby master Bug#20450] Ruby 3.3.1 broken with bootsnap
Date: Wed, 24 Apr 2024 19:20:44 +0000 (UTC)	[thread overview]
Message-ID: <redmine.journal-108100.20240424192044.53313@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-20450.20240424092531.53313@ruby-lang.org

Issue #20450 has been updated by professor (Todd Sedano).


Thank you for fixing this. I confirmed that making this change fixed Ruby 3.3.1 for gusto

----------------------------------------
Bug #20450: Ruby 3.3.1 broken with bootsnap
https://bugs.ruby-lang.org/issues/20450#change-108100

* Author: philippe.bs.noel@tutanota.com (Philippe Noel)
* Status: Assigned
* Assignee: hsbt (Hiroshi SHIBATA)
* ruby -v: ruby 3.3.1 (2024-04-23 revision c56cd86388) [x86_64-linux]
* Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN
----------------------------------------
The issue looks like https://bugs.ruby-lang.org/issues/20060

With the new release of ruby 3.1.1, bootsnap does not work anymore.

```
bin/rails aborted!
ArgumentError: comparison of String with nil failed (ArgumentError)

    msg = " #{RUBY_VERSION < SINCE[gem] ? "will no longer be" : "is not"} part of the default gems since Ruby #{SINCE[gem]}."
                             ^^^^^^^^^^
/usr/local/bundle/gems/bootsnap-1.18.3/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in `require'
```

It's working with DISABLE_BOOTSNAP=1 with the following message : `warning: parser/current is loading parser/ruby33, which recognizes 3.3.0-compliant syntax, but you are running 3.3.1.`



-- 
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/

  parent reply	other threads:[~2024-04-24 19:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-24  9:25 [ruby-core:117674] [Ruby master Bug#20450] Ruby 3.1.1 broken with bootsnap philippe.bs.noel@tutanota.com (Philippe Noel) via ruby-core
2024-04-24  9:34 ` [ruby-core:117675] " hsbt (Hiroshi SHIBATA) via ruby-core
2024-04-24 10:36 ` [ruby-core:117677] " philippe.bs.noel@tutanota.com (Philippe Noel) via ruby-core
2024-04-24 11:14 ` [ruby-core:117681] " eugeneius (Eugene Kenny) via ruby-core
2024-04-24 19:20 ` professor (Todd Sedano) via ruby-core [this message]
2024-04-24 22:40 ` [ruby-core:117694] [Ruby master Bug#20450] Ruby 3.3.1 " shan (Shannon Skipper) via ruby-core
2024-04-25  8:53 ` [ruby-core:117701] " hsbt (Hiroshi SHIBATA) via ruby-core
2024-04-27  1:47 ` [ruby-core:117731] " shan (Shannon Skipper) via ruby-core

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.ruby-lang.org/en/community/mailing-lists/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=redmine.journal-108100.20240424192044.53313@ruby-lang.org \
    --to=ruby-core@ruby-lang.org \
    --cc=noreply@ruby-lang.org \
    --cc=ruby-core@ml.ruby-lang.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).