Dependency Issue puffing billy bundler told me to report #4203
Comments
|
Hi @MichaelOdumosu57! Thanks for reporting this. I think this is the same report as #4197. Does it still happen if you upgrade rubygems using |
|
Lemme attempt, the difference there was the dev end user was not permitted |
|
Still came up with the same error |
|
Could you copy the new error? |
|
@MichaelOdumosu57 You're trying to install eventmachine, and Bundler is using So, Bundler will install it, but it doesn't run/load. You need to force bundler to use the equivalent of RubyGem's |
|
@deivid-rodriguez Error ReportQuestionsPlease fill out answers to these questions, it'll help us figure out
BacktraceEnvironmentBundler Build MetadataBundler settingsGemfileGemfile# frozen_string_literal: true
source "https://rubygems.org"
git_source(:github) {|repo_name| "https://github.com/#{repo_name}" }
# gem "rails"
# frozen_string_literal: true
gem 'capybara'
gem 'ffi'
gem 'rspec'
gem 'rails_helper'
gem 'rake'
gem 'percy-capybara', '~> 4.3.3'
gem 'sauce_whisk'
gem 'selenium-webdriver'
gem 'puffing-billy',:group => :testGemfile.lock |
|
@MichaelOdumosu57 Does it also happen if you run |
|
@MichaelOdumosu57 I tried this locally. The only way I found to do it was:
|
|
Yeah, I think this is due to now having correct platform specific variant selection 🤣. This essentially surfaces a bug in the platform specific gem that should specificy an upper bound on ruby 3 if it's broken on it. A way to alleviate this issue is: #4049. I'll look into revisiting that. Still, the error seems weird, why is it failing on install? Shouldn't if fail at runtime? That's why I was thinking it could be a threading issue. |
|
I use bundle install --path="path/to/project", since I dont want to corrupt the per user or system installation. |
|
Sure, I understand. Did you try with the |
|
still failed First, try this link to see if there are any existing issue reports for this error: If there aren't any reports for this error yet, please create copy and paste the report template above into a new issue. Don't forget to anonymize any private data! Error ReportQuestionsPlease fill out answers to these questions, it'll help us figure out
BacktraceEnvironmentBundler Build MetadataBundler settingsGemfileGemfile# frozen_string_literal: true
source "https://rubygems.org"
git_source(:github) {|repo_name| "https://github.com/#{repo_name}" }
# gem "rails"
# frozen_string_literal: true
gem 'capybara'
gem 'ffi'
gem 'rspec'
gem 'rails_helper'
gem 'rake'
gem 'percy-capybara', '~> 4.3.3'
gem 'sauce_whisk'
gem 'selenium-webdriver'
# gem 'eventmachine', :platforms => :ruby
gem 'puffing-billy', '~> 2.3', '>= 2.3.1'Gemfile.lock |
|
something is getting notciable worse, mabye I should have listened to the path deprecation |
|
And does it work if you configure |
|
It would try to overwrite, nokogiri,unf_ext,ffi and other dependencies, depended on x64-mingw32, I'll try to do seperte for each |
|
it did not try ton install the x64-mingw32 platform however it falied Error ReportQuestionsPlease fill out answers to these questions, it'll help us figure out
BacktraceEnvironmentBundler Build MetadataBundler settingsGemfileGemfile# frozen_string_literal: true
source "https://rubygems.org"
git_source(:github) {|repo_name| "https://github.com/#{repo_name}" }
# gem "rails"
# frozen_string_literal: true
# gem 'capybara'
# gem 'ffi'
# gem 'rspec'
# gem 'rails_helper'
# gem 'rake'
# gem 'percy-capybara', '~> 4.3.3'
# gem 'sauce_whisk'
# gem 'selenium-webdriver'
# gem 'eventmachine', :platforms => :ruby
gem 'puffing-billy', '~> 2.3', '>= 2.3.1'Gemfile.lock--- TEMPLATE END ---------------------------------------------------------------- |
|
That sounds like an issue, yeah. If you unset the path configuration with |
|
It still adds those slashes it seems to have succeeded installing eventmachine, |
|
Hei! Just to clarify, the PR I pointed to implements In addition, I had an idea about what's going on that I think makes sense. If I recall correctly, some Windows had issues with paths longer than 260 characters, and I measured the one giving trouble and it's 261. Can you try setting a shorter path to see if the issue is fixed? |
|
absolutely Python talks about this on installation. That must be the issue
will follow around this time tmr , I'll try to deal with the path limit,
then install from source, is that the C+, themed configure , make logic?
…On Mon, Dec 28, 2020 at 12:31 PM David Rodríguez ***@***.***> wrote:
Hei!
Just to clarify, the PR I pointed to implements force_ruby_platform but
has not been merged yet, so you would need to clone the repository and
install from source if you want to try it.
In addition, I had an idea about what's going on that I think makes sense.
If I recall correctly, some Windows had issues with paths longer than 260
characters, and I measured the one giving trouble and it's 261. Can you try
setting a shorter path to see if the issue is fixed?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#4203 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFCVX4LPQGTJZ3C2AV3KMGTSXC6HBANCNFSM4VJ7AUTQ>
.
--
Michael Odumosu
Clerical Office Associate and Fullstack Freelance Software Developer
*Information*
Tel:929-353-8278
Linkedin: https://www.linkedin.com/in/michael-odumosu-a58367b1
Facebook: https://www.facebook.com/mchael.odumosu
Github: https://github.com/MichaelOdumosu57
|
|
First fix the path thing, and then we can see what the other errors look like. Not sure if we can do something in bundler to make this kind of thing easier to spot 🤔. |
|
To install from source, you would need to run the following: But wait until the next error first :) |
|
modify the application manifest, I have checked the registry and in the ruby_builtin_dlls.manifest, I feel like I need to edit this system ruby file, however I just dont know this type of thing I wish I learned more of desktop instead of mobile apps anyway here is the xml data I need to add, replace,integrate <application xmlns="urn:schemas-microsoft-com:asm.v3">
<windowsSettings xmlns:ws2="http://schemas.microsoft.com/SMI/2016/WindowsSettings">
<ws2:longPathAware>true</ws2:longPathAware>
</windowsSettings>
</application> |
|
@MichaelOdumosu57 I thought you were going to change the bundler configuration to use a shorter path 😅. If you can do that to skip the error for now (and also to confirm that's the culprit), then we can move on to the next error. I agree though that the proper fix would be to change your Windows configuration, but unfortunately I don't use Windows so I'm not able to help there. But I think you're on the right track though, the link you posted looks very promising! |
|
Seemed to solve many problems now we have a make issue |
|
I'm happy it fixed things. Can you delete the |
|
moved_to_shorter_path_make_failed.zip |
|
I think you need to use the master branch eventmachine_httpserver to fix that error. You can add the following to the In any case, it has become super clear now that this is not an issue in bundler, so I'll close this! |
|
I put together a youtube video and github resource on how to install puffing billy and deal with the eventmachine here |
Error Report
Questions
Please fill out answers to these questions, it'll help us figure out
why things are going wrong.
A dependency for puffing_billy was not installing so I deleted Gemfile.lock to see if I can get things to work
I ran the command
c:/Users/oluod/.gem/ruby/2.7.0/bin/bundle install --redownload --path=C:\Users\oluod\My_Notebook\cases\FinancialUpwardCase\Youtube\codequickie\capybara_and_puffing_billy\AngularApp\testing\e2eWhat did you expect to happen?
I expected Bundler to Install things as normal
What happened instead?
Instead, it indicates theres something I need to do to make sure "`gem install eventmachine -v '1.2.7' --source" succesds
Have you tried any solutions posted on similar issues in our issue tracker, stack overflow, or google?
I tried...
Have you read our issues document, https://github.com/rubygems/rubygems/blob/master/bundler/doc/contributing/ISSUES.md?
...
Backtrace
Environment
Bundler Build Metadata
Bundler settings
Gemfile
Gemfile
Gemfile.lock
The text was updated successfully, but these errors were encountered: