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

bump faraday version - to avoid multipart warning #1

Open
wants to merge 6 commits into
base: master
Choose a base branch
from

Conversation

BassamAziz
Copy link

No description provided.

@mfittko mfittko self-assigned this Feb 7, 2024
@@ -31,7 +31,7 @@ Gem::Specification.new do |spec|
spec.require_paths = ['lib']

spec.add_dependency 'activesupport'
spec.add_dependency 'faraday', '1.7.2'
spec.add_dependency 'faraday', '1.9.0'
Copy link
Member

@0000magda0000 0000magda0000 Feb 22, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mfittko @BassamAziz any reason why we don't update this to 1.9.3?

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

imo no

@mfittko
Copy link

mfittko commented Feb 26, 2024

@bassam we could probably go to latest faraday (2.9.0) - let's run the tests though

@@ -13,7 +13,7 @@ def connection
@_connection ||= build_connection.tap do |conn|
if authorize?
HelpScout::API::AccessToken.refresh!
conn.authorization(:Bearer, access_token) if access_token
conn.request :authorization, 'Bearer', 'authentication-token' if access_token
Copy link
Member

@0000magda0000 0000magda0000 Feb 27, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mfittko I think this isn't working yet, because when I run a HelpsScout query in the console of the update-bugsnag-faraday branch, I get the error HelpScout::API::NotAuthorized: The access token is invalid or has expired I don't get the error if I try that on master. Also the same error shows up on bugsnag for the testing_cobain_testing stage on bugsnag from last nights cron-jobs - not sure if that is related?

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ouch, yeah we need to use the token not some random string 🤦

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants