Ruby 3.2.0 build fails

1

(Looks like the usual new Ruby version issue on Render )I tried to upgrade my Rails app to use the newly released Ruby 3.2.0 but the build fails. Here’s the end of the log:

Dec 26 11:47:00 PM installing bundled gem cache: /opt/render/project/rubies/ruby-3.2.0/lib/ruby/gems/3.2.0/cache
Dec 26 11:47:00 PM >>> Removing /tmp/ruby-3.2.0.tar.xz …
Dec 26 11:47:00 PM >>> Removing /tmp/ruby-3.2.0 …
Dec 26 11:47:00 PM >>> Successfully installed ruby 3.2.0 into /opt/render/project/rubies/ruby-3.2.0
Dec 26 11:47:00 PM /opt/render/project/rubies/ruby-3.2.0/bin/ruby: File name too long
Dec 26 11:47:00 PM /home/render/ruby-installer.sh: line 70: /usr/local/bin/gem: Argument list too long
Dec 26 11:47:00 PM /home/render/ruby-installer.sh: line 79: /usr/local/bin/gem: Argument list too long
Dec 26 11:47:00 PM /home/render/colors.sh: line 3: /usr/bin/tput: Argument list too long

1 Like
2

Can confirm, I’m seeing the same issue installing Ruby 3.2.0.

3

Ruby 3.2 was only released 2 days ago, we’ll get it available probably in the New Year,

Regards,

John B

1 Like
4

works now

5

We made Ruby 3.2.0 available on the platform on Tuesday,

Regards,

John B

6

I’m still having the same issue. The last time, I tried a manual build with ‘Clear cache & deploy’ and it died without a relevant error message, as far as I can tell:

# installing Ruby 3.2
...
Jan 15 07:07:40 AM   69% [692/999]  lib/rubygems/commands/lock_command.rb
Jan 15 07:07:40 AM   69% [693/999]  lib/rubygems/commands/mirror_command.rb
Jan 15 07:07:40 AM   69% [694/999]  lib/rubygems/commands/open_command.rb
Jan 15 07:07:40 AM   69% [695/999]  lib/rubygems/commands/outdated_command.rb
Jan 15 07:07:40 AM   69% [696/999]  lib/rubygems/commands/owner_command.rb
Jan 15 07:07:40 AM   69% [697/999]  lib/rubygems/commands/pristine_command.rb
Jan 15 07:07:40 AM   69% [698/999]  lib/rubygems/commands/push_command.rb
Jan 15 07:07:40 AM   69% [699/999]  lib/rubygems/commands/query_command.rb
Jan 15 07:07:40 AM   70% [700/999]  lib/rubygems/commands/rdoc_command.rb
Jan 15 07:07:40 AM   70% [701/999]  lib/rubygems/commands/search_command.rb

That’s the end of the output…

Is it better to switch back to Ruby 3.1 for now? Or can this be fixed somehow?

7

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.