Skip to content

Conversation

@struniu
Copy link
Contributor

@struniu struniu commented Oct 26, 2021

Features and Improvements

  • Faraday updated to version > 1.0
  • Optional parameters max_retry and retry_statuses to specify no. of retries on failed request and statuses to retry.

May break compatibility because of the new Faraday

@struniu struniu self-assigned this Oct 26, 2021
end

def client_with_basic_retry
@client_with_basic_retry ||= BaseCRM::Client.new(access_token: access_token, base_url: base_url, max_retry: 1, retry_statuses: [200])

Choose a reason for hiding this comment

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

This setup is misleading, why retrying on HTTP 200? I know this is just for test, but someone may explore possible options by looking at specs.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

To be double sure? 🤣
But to be serious I got your point this may push people to actually retry on 200. Changed.

@struniu struniu force-pushed the strus/faraday-update branch from ffd650f to d3fb75c Compare October 27, 2021 08:08
@struniu struniu force-pushed the strus/faraday-update branch from d3fb75c to 23629df Compare October 27, 2021 08:12
@struniu struniu merged commit a031e48 into master Oct 27, 2021
@struniu struniu deleted the strus/faraday-update branch October 27, 2021 09:45
This was referenced Oct 27, 2021
@struniu struniu mentioned this pull request Jan 11, 2022
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