Nonexistent config files should raise a pretty error #2063

Closed
indirect opened this Issue Aug 16, 2012 · 3 comments

Comments

Projects
None yet
3 participants
@indirect
Owner

indirect commented Aug 16, 2012

If your BUNDLER_CONFIG file is explicitly set, but doesn't actually exist, YAML will explode with a backtrace. We should handle this case with a helpful error message. This was discovered as part of #2054.

@richo

This comment has been minimized.

Show comment Hide comment
@richo

richo Aug 16, 2012

Contributor

Also, that's not the case.

If BUNDLER_CONFIG is set, but doesn't exist, bundler continues with default config.

if BUNDLER_CONFIG is set, but that file doesn't contain valid YAML (ie, /dev/null) then YAML explodes with a backtrace.

Contributor

richo commented Aug 16, 2012

Also, that's not the case.

If BUNDLER_CONFIG is set, but doesn't exist, bundler continues with default config.

if BUNDLER_CONFIG is set, but that file doesn't contain valid YAML (ie, /dev/null) then YAML explodes with a backtrace.

@indirect

This comment has been minimized.

Show comment Hide comment
@indirect

indirect Aug 16, 2012

Owner

Thanks for the correction -- IMO, we should print an error message in both of those cases. Explicitly setting a settings file should not result in silently using the defaults if the file doesn't actually exist.

Owner

indirect commented Aug 16, 2012

Thanks for the correction -- IMO, we should print an error message in both of those cases. Explicitly setting a settings file should not result in silently using the defaults if the file doesn't actually exist.

@xaviershay

This comment has been minimized.

Show comment Hide comment
@xaviershay

xaviershay Aug 12, 2013

Contributor

I can't repro this.

Contributor

xaviershay commented Aug 12, 2013

I can't repro this.

@xaviershay xaviershay closed this Aug 12, 2013

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