Skip to content
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

Fix gem proxy config on Ruby <3.2 with psych 5 #914

Merged
merged 1 commit into from
Jan 20, 2023

Conversation

tombruijn
Copy link
Member

We got several reports in issue #904 that installing the AppSignal gem on system with Ruby < 3.2 with also the psych gem version 5 installed won't work and raise an error breaking the app installation.

This related PR #913, which is also needed to fix the whole issue. This PR removes the need for YAML parsing during the installation for the extension download information.

This change silences the secondary error that is triggered when we fetch the rubygems config, specified in the .gemrc file. This also triggers that error from within rubygems. Instead, users can use the HTTP_PROXY environment variable to configure the HTTP proxy.

This is not an ideal fix. We also don't communicate that this behavior is happening with this fix. I suggest we report a bug report upstream as detailed in #904, so we can remove this rescue-statement.

We got several reports in issue #904 that installing the AppSignal gem
on system with Ruby < 3.2 with also the psych gem version 5 installed
won't work and raise an error breaking the app installation.

This related PR #913, which is also needed to fix the whole issue. This
PR removes the need for YAML parsing during the installation for the
extension download information.

This change silences the secondary error that is triggered when we fetch
the rubygems config, specified in the `.gemrc` file. This also triggers
that error from within rubygems. Instead, users can use the `HTTP_PROXY`
environment variable to configure the HTTP proxy.

This is not an ideal fix. We also don't communicate that this behavior
is happening with this fix. I suggest we report a bug report upstream as
detailed in #904, so we can remove this rescue-statement.
@tombruijn tombruijn merged commit 87040a6 into main Jan 20, 2023
@tombruijn tombruijn deleted the rescue-gem-config-load branch July 31, 2023 09:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants