Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

portable-ruby 3.3.5 #239

Merged
merged 1 commit into from
Sep 27, 2024
Merged

portable-ruby 3.3.5 #239

merged 1 commit into from
Sep 27, 2024

Conversation

BrewTestBot
Copy link
Member

@BrewTestBot BrewTestBot commented Sep 4, 2024

Created by brew bump


Created with brew bump-formula-pr.

  • resource blocks have been checked for updates.

@p-linnane p-linnane force-pushed the bump-portable-ruby-3.3.5 branch from 85569da to 249a07f Compare September 4, 2024 00:08
@Bo98
Copy link
Member

Bo98 commented Sep 4, 2024

Patch is safe to remove now. Upstream included it with Ruby 3.3.5.

It seems 3.3.5 has a change that throws deprecation for require "ostruct" so this might require some work in Homebrew/brew to support. Unfortunately it seems this falsely triggers for require "json" too as json indirectly depends on ostruct (but not in Ruby 3.4). Could backport the relevant json fix though maybe we need to think about system Ruby on Linux.

@Bo98
Copy link
Member

Bo98 commented Sep 4, 2024

Might just hack some code to globally disable those warnings over at Homebrew/brew tbh. They're useful on paper but they have caused unfixable problems given we cannot be building native extensions on the fly like upstream expect, especially when it is now covering things that are already fixed upstream but not in any released version.

@Bo98
Copy link
Member

Bo98 commented Sep 4, 2024

Will check on CI later but I think it might just be a case of replacing --disable-gems with Gem.discover_gems_on_require = false

@MikeMcQuaid
Copy link
Member

Might just hack some code to globally disable those warnings over at Homebrew/brew tbh.

Works for me 👍🏻

Copy link

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@github-actions github-actions bot added the stale label Sep 26, 2024
@Bo98 Bo98 force-pushed the bump-portable-ruby-3.3.5 branch from f38b9df to 5ec8936 Compare September 26, 2024 00:59
@Bo98 Bo98 removed the stale label Sep 26, 2024
@Bo98
Copy link
Member

Bo98 commented Sep 27, 2024

Hmm looks like there's another 3.3.5 bug here:

Non-executables were installed to "/opt/homebrew/opt/portable-ruby/bin".
The offending files are:
  /opt/homebrew/opt/portable-ruby/bin/ri.lock
  /opt/homebrew/opt/portable-ruby/bin/bundler.lock
  /opt/homebrew/opt/portable-ruby/bin/rdoc.lock
  /opt/homebrew/opt/portable-ruby/bin/rdbg.lock
  /opt/homebrew/opt/portable-ruby/bin/bundle.lock
  /opt/homebrew/opt/portable-ruby/bin/syntax_suggest.lock
  /opt/homebrew/opt/portable-ruby/bin/erb.lock
  /opt/homebrew/opt/portable-ruby/bin/irb.lock
  /opt/homebrew/opt/portable-ruby/bin/bootsnap.lock

https://bugs.ruby-lang.org/issues/20721

It is already fixed for 3.3.6 (Nov 5th). Though we could backport the relevant patches (4 commits).

@Bo98 Bo98 disabled auto-merge September 27, 2024 02:31
@p-linnane
Copy link
Member

Let's backport so we can get this shipped. I can take a crack at it in a bit.

Co-authored-by: Bo Anderson <[email protected]>
Co-authored-by: Patrick Linnane <[email protected]>
@Bo98 Bo98 force-pushed the bump-portable-ruby-3.3.5 branch from 5ec8936 to d5df7a5 Compare September 27, 2024 04:13
@Bo98
Copy link
Member

Bo98 commented Sep 27, 2024

Basically patched in the majority of 3.3.6 at this point but it is what it is.

@p-linnane p-linnane enabled auto-merge September 27, 2024 04:21
@p-linnane p-linnane merged commit deeb0bb into master Sep 27, 2024
5 checks passed
@p-linnane p-linnane deleted the bump-portable-ruby-3.3.5 branch September 27, 2024 04:34
@Bo98
Copy link
Member

Bo98 commented Sep 27, 2024

Somehow pulled a masterclass and builds on the new Intel image on the newer hardware is now over 2x faster and is now nearly as fast as arm64.

Almost seems like it's wrong.

@MikeMcQuaid
Copy link
Member

@Bo98 nice work!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants