-
Notifications
You must be signed in to change notification settings - Fork 914
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
racc default gem bits are not being included in the distribution #6604
Comments
Thank you for the new issue. I will try to reproduce locally. |
I can reproduce locally but it really doesn't seem like something we are doing. I suspect bundler but will try to dig into this and figure out what is happening. For the record I get this output from running the same
The racc gem appears in the Gemfile.lock and seems to be fine:
Attempting to update it, as the error suggests, changes nothing:
So this is a mystery. 🤔 |
Running
This may be specific to the build and how it activates racc. |
This looks like it may be a Bundler bug. I just managed to get it to work, but using bundler 2.2.11 rather than 2.2. @deivid-rodriguez Does this sound like anything recently fixed in Bundler? This might also explain why I was not able to reproduce locally until now. |
After initially being able to reproduce this, I am now unable. 😖
This is with Bundler 2.2.0. I cleaned the rubocop-ast repo and rebundled and reran and it still works! |
I believe this is a packaging issue rather than anything broken in JRuby itself. It seems that not all of the racc bits are getting included in the distribution, leading to issues loading the
We see here that the default gemspec is in place, but the executable
Installing the gem manually leads to the next issue, because it still tries to activate the default gem and that executable still is not present where default gems install executables:
When run against a HEAD build of JRuby, of course the executable is there, but in a different location (the layout of default gems has changed, perhaps?):
At a minimum we need to figure out why the default gem bits are not getting included in the distribution. I will try to come up with a workaround. |
Hi! I wasn't able to repro the exact error the Github Actions job is running into, but I did repro the same errors @headius got. I suspect the specific error depends on whether |
I will work on the dist today. We will make a small change for 9.2.x to include everything that is supposed to be there, and the larger change on master for 9.3 will be to switch to a blacklist of sources we do not want in the dist, rather than a whitelist that will get out of date. |
The following diff shows the files in a freshly cloned and build
Interestingly, the |
So this turned out to be a bigger mess than expected. Our build installs the bundled and default gems while processing lib/pom.rb, using the
In addition, when packaging the project only a whitelisted set of bin stubs were included in the distribution, which would exclude racc anyway. I have pushed a
The only questionable diff here is that some gems that appeared in the director of bundled gems are no longer there... but these four gems are default gems, not bundled gems, so we should not see them show up. They show up here because the old logic for copying binscripts for default gems only worked on non-platform gems, and then did not install the files in the right place anyway. The contents of those four gems show there's nothing lost:
(The Finally, the listing of bin files for the faux 9.2.17.0 shows that all the appropriate files are present with their bat file equivalents:
We will want to reexamine and greatly simplify this process on master, but I believe the diff is fairly minimal and produces the correct file layout. @marcandre Your original issue was about jruby-head, which should be fixed without a release once we merge this to master. The GHA ruby-install builds are based on snapshots of our normal distribution tarball from master HEAD, which was also broken in the same way as the release distributions from 9.2.x. |
Fixed by #6609. |
Glad this is fixed 💪 |
Just to confirm this fixes our build on JRuby-head 🎉 , and one day on jruby too. Thanks! |
@marcandre Thank you! We will do a 9.2.17 release in a couple weeks. |
See report rubocop/rubocop-ast#132
See also #6416
The text was updated successfully, but these errors were encountered: