Skip to content
This repository has been archived by the owner on Apr 14, 2021. It is now read-only.

Tasks anyone can claim #4871

Closed
17 of 23 tasks
indirect opened this issue Aug 11, 2016 · 9 comments
Closed
17 of 23 tasks

Tasks anyone can claim #4871

indirect opened this issue Aug 11, 2016 · 9 comments
Labels
contribution: small contribution: unclaimed good first issue type: administrative

Comments

@indirect
Copy link
Member

indirect commented Aug 11, 2016 •
edited by segiddins
Loading

never say I didn't give you things you could do, @segiddins 😁
@segiddins segiddins mentioned this issue Aug 18, 2016
Merged
homu added a commit that referenced this issue Aug 20, 2016
@homu
Auto merge of #4893 - bundler:seg-block-update-regressions, r=indirect
9fe7b6c 
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
Copy link
Contributor

I would like to work on #4913

@indirect
Copy link
Member Author

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

@JuanitoFatas JuanitoFatas mentioned this issue Aug 26, 2016
Merged
@JuanitoFatas
Copy link
Contributor

@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 :)

@indirect indirect mentioned this issue Aug 28, 2016
Closed
@JuanitoFatas
Copy link
Contributor

#4846 merged, can check it off.

@ChaeOkay ChaeOkay mentioned this issue Nov 16, 2016
Closed
4 tasks
@jonathanpike jonathanpike mentioned this issue Mar 7, 2017
Merged
bundlerbot added a commit that referenced this issue Apr 5, 2017
@bundlerbot
Auto merge of #5505 - jonathanpike:master, r=colby-swandale
6a7262c 
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
Copy link
Member

updated status of this board

@hmistry hmistry mentioned this issue Apr 13, 2017
Closed
@mctaylorpants mctaylorpants mentioned this issue Apr 16, 2017
Closed
philipefarias added a commit to dleemoo/rc-images that referenced this issue Jun 12, 2017
@philipefarias
Update bundler version
bb7fbcf 
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 (rubygems/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 (rubygems/bundler#5678, @segiddins)
  - `bundle env` will print well-formed markdown when there are no settings (rubygems/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 (rubygems/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 (rubygems/bundler#5620, @segiddins)

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

Bugfixes:

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

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

Features:

  - print a notification when a newer version of bundler is available (rubygems/bundler#4683, @segiddins)
  - add man pages for all bundler commands (rubygems/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 (rubygems/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 (rubygems/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 (rubygems/bundler#4871, @jonathanpike)
  - add `--source` and `--group` options to the `bundle inject` command (rubygems/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 (rubygems/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 (rubygems/bundler#5031, rubygems/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 (rubygems/bundler#5458, @Shekharrajak, @colby-swandale)
  - suggest the appropriate command to unfreeze a bundle (rubygems/bundler#5009, @denniss)
  - ensure nested calls to `bundle exec` resolve default gems correctly (rubygems/bundler#5500, @segiddins)
  - ensure that a plugin failing to install doesn't uninstall other plugins (@kerrizor, @roseaboveit)
  - ensure `socket` is required before being referenced (rubygems/bundler#5533, @rafaelfranca)
  - allow running `bundle outdated` when gems aren't installed locally (rubygems/bundler#5553, @segiddins)
  - print a helpful error when `bundle exec`ing to a gem that isn't included in the bundle (rubygems/bundler#5487, @segiddins)
  - print an error message when a non-git gem is given a `branch` option (rubygems/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 (rubygems/bundler#5579, @segiddins)
  - avoid deadlocking when installing with a lockfile that is missing dependencies (rubygems/bundler#5378, rubygems/bundler#5480, rubygems/bundler#5519, rubygems/bundler#5526, rubygems/bundler#5529, rubygems/bundler#5549, rubygems/bundler#5572, @segiddins)
@philipefarias philipefarias mentioned this issue Jun 12, 2017
Merged
@jumbosushi jumbosushi mentioned this issue Oct 24, 2017
Merged
@prog1dev
Copy link

@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
Copy link
Member

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

@colby-swandale
Copy link
Member

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

@hmistry
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 subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
contribution: small contribution: unclaimed good first issue type: administrative
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@indirect @colby-swandale @JuanitoFatas @hmistry @segiddins @coilysiren @prog1dev