composite_primary_keys gem v 5.0.10 missing dependencies in dependencies API about bundler-api

[elskwid]

@rsutphin, thank you for opening this issue!

During our pairing session, @phlipper and I spent most of the day looking through this issue as we have projects that are not resolving gem dependencies correctly.

We see the same behavior as you are with the newer versions of a gem having missing dependencies. I used your script to check against our gem thincloud-postmark:

# ruby list_gem_deps.rb thincloud-postmark

[{:name=>"thincloud-postmark",
  :number=>"0.4.0",
  :platform=>"ruby",
  :dependencies=>[]},
 {:name=>"thincloud-postmark",
  :number=>"0.3.2",
  :platform=>"ruby",
  :dependencies=>[]},
 {:name=>"thincloud-postmark",
  :number=>"0.3.1",
  :platform=>"ruby",
  :dependencies=>[]},
 {:name=>"thincloud-postmark",
  :number=>"0.3.0",
  :platform=>"ruby",
  :dependencies=>[]},
 {:name=>"thincloud-postmark",
  :number=>"0.2.0",
  :platform=>"ruby",
  :dependencies=>[["postmark-rails", "~> 0.4.1"]]},
 {:name=>"thincloud-postmark",
  :number=>"0.1.1",
  :platform=>"ruby",
  :dependencies=>[["postmark-rails", "~> 0.4.1"]]},
 {:name=>"thincloud-postmark",
  :number=>"0.1.0",
  :platform=>"ruby",
  :dependencies=>[]}]

As we were testing we wanted to see what would happen with a newly created gem. We used bundle gem command for the initial structure and then pushed with both rake release and gem push. We also used different methods of requiring dependencies (add_dependency vs add_runtime_depency):

# ruby list_gem_deps.rb elskwid-gem-test

[{:name=>"elskwid-gem-test",
  :number=>"0.0.3",
  :platform=>"ruby",
  :dependencies=>[]},
 {:name=>"elskwid-gem-test",
  :number=>"0.0.2",
  :platform=>"ruby",
  :dependencies=>[]},
 {:name=>"elskwid-gem-test",
  :number=>"0.0.1",
  :platform=>"ruby",
  :dependencies=>[]}]

Issuing bundle install will not find dependencies for these gems since it relies on this endpoint.

Bottom line, it didn't matter what the dependencies were or how we required them in our gemspec.

One final note: When we run bundler with the --verbose flag we can see the gem names coming back correctly during the fetch metadata stage but they are not included in the install list.

[elskwid]

⬆️

[phlipper]

🎉 👍

[TigerWolf]

rubygems/bundler#2185 (comment)

Is there a way to update the database so that the older gems and dependencies are updated so that all of the gems work correctly? I saw this mentioned in issue #18

[hone]

A fix has been deployed and the migration has been run. Please let me know if you're still running into issues.

[rsutphin]

Thanks @elskwid, @hone, and all. I have verified that the fixed data has resolved my original issue.