NoMethodError: undefined method `full_name' for nil:NilClass #5088
Comments
|
Thank you, I can repro this. I'll work on it. |
|
May I ask how you generated that
and also
Which are incompatible with each other. It's also weird that it doesn't include blank lines between sections. Did you maybe edit it directly? Or if not, which bundler commands did you run to generate it? |
|
Actually I just realized that previous bundler versions without this bug generate this lockfile, nevermind. |
|
Ps. I just run I did try to remove the lock file to workaround the issue, but the lockfile automatically gets generated (as it should). But in the long run, this is a real bug. |
|
Alright, I see what's going on now. I thought bundler would automatically resolve all Anyways, the current behaviour is to ignore dependencies for other platforms, but changes in bundler 2.2.32 made this regress. I'll fix this now to restore bundler 2.2.31 behaviour. |
|
I will release a new version quickly since I suspect this will bite a few people. |
|
yeah, I also think this is not a pretty bug. |
|
Also: try to introduce a test-case in GitHub Actions that fails with Bundler v0.2.32 and with your new change/release the test case succeed. So you have a nice regression testcase for the future. Avoiding this problem occurring ever again in the future. |
|
I still get this error running (I do not have any issues running the bundle install command against derived apps, or on other architectures... I don't see anything architecture-specific in Gemfile or EnvironmentBundler Build MetadataGemfileGemfilesource 'https://rubygems.org'
gemspec
group :development, :test do
gem 'pry-byebug'
gem 'rake'
# lock to a specific version to prevent breaking CI when new versions come out
gem 'sorbet', '= 0.5.6433'
end
group :test do
gem 'rspec', '~> 3.0'
endGemfile.lockGemspecskuby-core.gemspec$:.unshift File.expand_path('lib', __dir__)
require 'kuby/version'
Gem::Specification.new do |s|
s.name = 'kuby-core'
s.version = ::Kuby::VERSION
s.authors = ['Cameron Dutro']
s.email = ['camertron@gmail.com']
s.homepage = 'http://github.com/getkuby/kuby-core'
s.description = s.summary = 'Deploy your Rails app onto Kubernetes the easy way.'
s.platform = Gem::Platform::RUBY
s.add_dependency 'colorize', '~> 0.8'
s.add_dependency 'docker-remote', '~> 0.6'
s.add_dependency 'gli', '~> 2.0'
s.add_dependency 'helm-cli', '~> 0.3'
# See: https://github.com/Shopify/krane/pull/720
# See: https://github.com/Shopify/krane/blob/master/CHANGELOG.md#114
s.add_dependency 'krane', '>= 1.1.4', '< 2.0'
s.add_dependency 'kuby-cert-manager', '>= 0.3'
s.add_dependency 'kube-dsl', '~> 0.4'
s.add_dependency 'kuby-kube-db', '>= 0.6'
s.add_dependency 'kubernetes-cli', '~> 0.3'
s.add_dependency 'railties', '>= 5.1'
s.add_dependency 'rouge', '~> 3.0'
s.add_dependency 'sorbet-runtime-stub', '~> 0.2'
s.add_development_dependency 'rspec'
s.require_path = 'lib'
s.executables << 'kuby'
s.files = Dir['{lib,spec}/**/*', 'Gemfile', 'LICENSE', 'CHANGELOG.md', 'README.md', 'Rakefile', 'kuby-core.gemspec']
end |
|
I can reproduce this, thanks for letting me know. Let me have a look! |
|
So the cause is that the
The |
|
EDIT: OK, the new bundler version fix it. But be sure you clear any cache in your CI/CD pipeline. And most importantly upgrade the bundler version to v2.2.33 locally. Remove the old Gem file. Run: Successful job: https://gitlab.melroy.org/melroy/melroy-site/-/jobs/9161 |
|
@Danger89 This is a different issue. The end user error is the same, but the root cause is different. |
|
Alright, I have this fix almost ready at #5168. New output in this case will be like this $ bundle install
Fetching gem metadata from https://rubygems.org/........
Resolving dependencies...
Bundler could not find compatible versions for gem "sorbet-static":
In Gemfile:
sorbet (= 0.5.6433) was resolved to 0.5.6433, which depends on
sorbet-static (= 0.5.6433)
Could not find gem 'sorbet-static (= 0.5.6433) arm64-darwin-21', which is required by gem 'sorbet (= 0.5.6433)', in rubygems repository https://rubygems.org/ or installed locally.
The source contains the following gems matching 'sorbet-static (= 0.5.6433)':
* sorbet-static-0.5.6433-java
* sorbet-static-0.5.6433-universal-darwin-14
* sorbet-static-0.5.6433-universal-darwin-15
* sorbet-static-0.5.6433-universal-darwin-16
* sorbet-static-0.5.6433-universal-darwin-17
* sorbet-static-0.5.6433-universal-darwin-18
* sorbet-static-0.5.6433-universal-darwin-19
* sorbet-static-0.5.6433-universal-darwin-20
* sorbet-static-0.5.6433-x86_64-linux |
|
@deivid-rodriguez To reproduce:
source 'https://rubygems.org'
gem 'sorbet', :group => :development
gem 'sorbet-runtime'
And see: EnvironmentBundler Build MetadataGemfileGemfilesource 'https://rubygems.org'
gem 'sorbet', :group => :development
gem 'sorbet-runtime'Gemfile.lock |
|
@deivid-rodriguez Are there any temporary workarounds I can do now to make it work before you release? |
|
@lem0nify Unfortunately the release is not going to do much for you, it's just going to give you a more clear message about what's going on. Sorbet does not support Windows: https://sorbet.org/docs/faq#what-platforms-does-sorbet-support. |
Bundler 2.3.3 has a bug that fails to resolve platforms rubygems/rubygems#5088
Describe the problem as clearly as you can
Bundle install fails with "NoMethodError: undefined method `full_name' for nil:NilClass". I'm using GitLab Pipelines, but that shouldn't really matter. As long as you use Ruby Docker image.
Related issue, but already closed while NOT solved: #4922
Did you try upgrading rubygems & bundler?
Yes I tried Ruby 2.7 and Ruby 3.0 (stable) using Ruby official Docker images.
Both runs are using the same bundler version: v2.2.32
Output Ruby 2.7: https://gitlab.melroy.org/melroy/melroy-site/-/jobs/8978#L107
Output Ruby 3.0 https://gitlab.melroy.org/melroy/melroy-site/-/jobs/8979#L110
Post steps to reproduce the problem
Run a basic Jekyll init project, add the following plugins to the Gemfile:
And run:
And use Ruby Docker image for reproducibility.
Which command did you run?
bundle installWhat were you expecting to happen?
No errors.
What actually happened?
Environment
Bundler Build Metadata
Bundler settings
Gemfile
Gemfile
Gemfile.lock
The text was updated successfully, but these errors were encountered: