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

Tasks anyone can claim #4871

Closed
indirect opened this Issue Aug 11, 2016 · 9 comments

Comments

Projects
None yet
7 participants
@indirect
Copy link
Member

indirect commented Aug 11, 2016

  • resurrect the unfinished add command #4901
  • store a Gemfile checksum in Gemfile.lock, so we can skip the resolver when unchanged
  • Add a bundle issue command that prints instructions for reporting issues as well as the output from env and doctor #5505
  • add --parsable option to config #4913 #4919 #5306
  • fix build and merge OpenSSL version for env #4624
  • on gem install errors, print the last ten lines of make output if possible
  • parse settings keys on "." first so keys are always accurate #4830
  • setting to only install newer options during update #4511, #4893
  • Refactor RSpec matchers into proper classes #4806
  • Use /tmp/bundler for compact_index when Dir.home isn't writable #4792 #4819
  • Skip persisting global settings to disk if Dir.home is missing or unwritable #4918
  • Fix running bundler/inline blocks twice #4837
  • add support for the compact index to Gemstash
  • Address comments and merge symlink support for standalone bins #4782
  • Retry downloading gems #4846
  • Refactor Definition to avoid evaling Gemfile twice #4417 #4952
  • Run Travis specs in parallel using parallel_tests #4345
  • Write an RFC for and/or implement a fix for platform, which today means multiple conflicting things: gem architecture (eg x86_64), gem platform OS (eg java), engine version (eg mri_22). This may involve adding gemspec support for Ruby engine and version requirements?
  • Rebase and merge resolver-style errors for Ruby version conflicts #4654
  • Add a bundle plugin list command to list the current plugins in the bundle. #5467
  • Add a bundle plugin update command to update the version of an installed plugin #5446
  • Fix vendored git gems not being updated on bundle update #5423 #5398
  • Document why bundle exec updates the Gemfile.lock #5245

never say I didn't give you things you could do, @segiddins 😁

homu added a commit that referenced this issue Aug 20, 2016

Auto merge of #4893 - bundler:seg-block-update-regressions, r=indirect
Block resolving to older versions during an update

This is currently behind the only_update_to_newer_versions setting

Closes #4511.

See #4856 and #4871
@JuanitoFatas

This comment has been minimized.

Copy link
Contributor

JuanitoFatas commented Aug 26, 2016

I would like to work on #4913

@indirect

This comment has been minimized.

Copy link
Member

indirect commented Aug 26, 2016

@JuanitoFatas sounds great. once you send a PR, come back and check it off. 😁

@JuanitoFatas

This comment has been minimized.

Copy link
Contributor

JuanitoFatas commented Aug 26, 2016

@JuanitoFatas sounds great. once you send a PR, come back and check it off.

Hi! I think check is only available for collaborator, not for contributor, but I link the PR back, so you can check it off when you revisit this issue :)

@JuanitoFatas

This comment has been minimized.

Copy link
Contributor

JuanitoFatas commented Aug 28, 2016

#4846 merged, can check it off.

@ChaeOkay ChaeOkay referenced this issue Nov 16, 2016

Closed

Store a Gemfile checksum in Gemfile.lock #5177

2 of 4 tasks complete

bundlerbot added a commit that referenced this issue Apr 5, 2017

Auto merge of #5505 - jonathanpike:master, r=colby-swandale
Add `bundle issue` command that prints instructions for reporting issues

This is my stab at adding a `bundle issue` command, as listed in the list of tasks anyone can claim (#4871).  This is also my first contribution (of what I hope will be many) to Bundler!

I hope that this is useful, and please let me know how to improve it!
@colby-swandale

This comment has been minimized.

Copy link
Member

colby-swandale commented Apr 7, 2017

updated status of this board

philipefarias added a commit to dleemoo/rc-images that referenced this issue Jun 12, 2017

Update bundler version
Changes since last version used (1.14.6):

== 1.15.1 (2017-06-02)

Bugfixes:

  - `bundle lock --update GEM` will fail gracefully when the gem is not in the lockfile (bundler/bundler#5693, @segiddins)
  - `bundle init --gemspec` will fail gracefully when the gemspec is invalid (@colby-swandale)
  - `bundle install --force` works when the gemfile contains git gems (bundler/bundler#5678, @segiddins)
  - `bundle env` will print well-formed markdown when there are no settings (bundler/bundler#5677, @segiddins)

== 1.15.0 (2017-05-19)

This space intentionally left blank.

== 1.15.0.pre.4 (2017-05-10)

Bugfixes:

  - avoid conflicts when `Gem.finish_resolve` is called after the bundle has been set up (@segiddins)
  - ensure that `Gem::Specification.find_by_name` always returns an object that can have `#to_spec` called on it (bundler/bundler#5592, @jules2689)

== 1.15.0.pre.3 (2017-04-30)

Bugfixes:

  - avoid redundant blank lines in the readme generated by `bundle gem` (@koic)
  - ensure that `open-uri` is not loaded after `bundle exec` (@segiddins)
  - print a helpful error message when an activated default gem conflicts with
    a gem in the gemfile (@segiddins)
  - only shorten `ref` option for git gems when it is a SHA (bundler/bundler#5620, @segiddins)

== 1.15.0.pre.2 (2017-04-23)

Bugfixes:

  - ensure pre-existing fit caches are updated from remote sources (bundler/bundler#5423, @alextaylor000)
  - avoid duplicating specs in the lockfile after updating with the gem uninstalled (bundler/bundler#5599, @segiddins)
  - ensure git gems have their extensions available at runtime (bundler/bundler#5594, @jules2689, @segiddins)

== 1.15.0.pre.1 (2017-04-16)

Features:

  - print a notification when a newer version of bundler is available (bundler/bundler#4683, @segiddins)
  - add man pages for all bundler commands (bundler/bundler#4988, @feministy)
  - add the `bundle info` command (@fredrb, @colby-swandale)
  - all files created with `bundle gem` comply with the bundler style guide (@zachahn)
  - if installing a gem fails, print out the reason the gem needed to be installed (bundler/bundler#5078, @segiddins)
  - allow setting `gem.push_key` to set the key used when running `rake release` (@DTrierweiler)
  - print gem versions that are regressing during `bundle update` in yellow (bundler/bundler#5506, @brchristian)
  - avoid printing extraneous dependencies when the resolver encounters a conflict (@segiddins)
  - add the `bundle issue` command that prints instructions for reporting issues (bundler/bundler#4871, @jonathanpike)
  - add `--source` and `--group` options to the `bundle inject` command (bundler/bundler#5452, @Shekharrajak)
  - add the `bundle add` command to add a gem to the gemfile (@denniss)
  - add the `bundle pristine` command to re-install gems from cached `.gem` files (bundler/bundler#4509, @denniss)
  - add a `--parseable` option for `bundle config` (@JuanitoFatas, @colby-swandale)

Performance:

  - speed up gemfile initialization by storing locked dependencies as a hash (@jules2689)
  - speed up gemfile initialization by making locked dependency comparison lazy, avoiding object allocation (@jules2689)
  - only validate git gems when they are downloaded, instead of every time `Bundler.setup` is run (@segiddins)
  - avoid regenerating the lockfile when nothing has changed (@segiddins)
  - avoid diffing large arrays when no sources in the gemfile have changed (@segiddins)
  - avoid evaluating full gemspecs when running with RubyGems 2.5+ (@segiddins)

Bugfixes:

  - fix cases where `bundle update` would print a resolver conflict instead of updating the selected gems (bundler/bundler#5031, bundler/bundler#5095, @segiddins)
  - print out a stack trace after an interrupt when running in debug mode (@segiddins)
  - print out when bundler starts fetching a gem from a remote server (@segiddins)
  - fix `bundle gem` failing when `git` is unavailable (bundler/bundler#5458, @Shekharrajak, @colby-swandale)
  - suggest the appropriate command to unfreeze a bundle (bundler/bundler#5009, @denniss)
  - ensure nested calls to `bundle exec` resolve default gems correctly (bundler/bundler#5500, @segiddins)
  - ensure that a plugin failing to install doesn't uninstall other plugins (@kerrizor, @roseaboveit)
  - ensure `socket` is required before being referenced (bundler/bundler#5533, @rafaelfranca)
  - allow running `bundle outdated` when gems aren't installed locally (bundler/bundler#5553, @segiddins)
  - print a helpful error when `bundle exec`ing to a gem that isn't included in the bundle (bundler/bundler#5487, @segiddins)
  - print an error message when a non-git gem is given a `branch` option (bundler/bundler#5530, @colby-swandale)
  - allow interrupts to exit the process after gems have been installed (@segiddins)
  - print the underlying error when downloading gem metadata fails (bundler/bundler#5579, @segiddins)
  - avoid deadlocking when installing with a lockfile that is missing dependencies (bundler/bundler#5378, bundler/bundler#5480, bundler/bundler#5519, bundler/bundler#5526, bundler/bundler#5529, bundler/bundler#5549, bundler/bundler#5572, @segiddins)
@prog1dev

This comment has been minimized.

Copy link

prog1dev commented Dec 17, 2017

@indirect Is it worth of working on this request?

store a Gemfile checksum in Gemfile.lock, so we can skip the resolver when unchanged

Looks like in Bundler::Definition there is some kind of caching already and this is unnecessary to implement

@segiddins

This comment has been minimized.

Copy link
Member

segiddins commented Dec 17, 2017

I've done some experimental work on that one, @prog1dev

@colby-swandale

This comment has been minimized.

Copy link
Member

colby-swandale commented Feb 23, 2018

I'm closing this issue, we've replaced this list with the help wanted and good first issue Github tags.

@hmistry

This comment has been minimized.

Copy link
Contributor

hmistry commented Feb 24, 2018

@colby-swandale I think this list was good to have for those looking to contribute. Having multiple paths to discover issues to work on caters to different ways people look to find info. To me this list was a much easier way to find a list of issues to work on and it's a good central way to track and prioritize what needs to be worked on.

I highly recommend reviving it by making a new version since 3/4's of this is done. Also keep the Github tags as another method to find things to work on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment