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

feat: http error handling without retries #226

Merged
merged 8 commits into from Mar 15, 2024
Merged

Conversation

vtsaplin
Copy link
Collaborator

@vtsaplin vtsaplin commented Mar 14, 2024

Description

What's inside:

  • Removed the retry feature + related refactoring.
  • Added error mapping for error code 429 (rate limit).
  • Display a standard error message for unexpected issues.
  • Respect the 60s execution limit and stop actions gracefully with a proper error message (408 status).

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • I have signed the Adobe Open Source CLA.
  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

Copy link
Member

@basecode basecode left a comment

Choose a reason for hiding this comment

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

LGTM

})
.get()
.json();
const { valid } = response;
Copy link
Member

Choose a reason for hiding this comment

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

return response.valid?

Comment on lines 32 to 34
.resolve((_) => _.setTimeout(REQUEST_TIMEOUT))
.resolve((_) => {
return _.fetchError((error) => {
Copy link
Member

Choose a reason for hiding this comment

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

Generally, _ is used as a placeholder for unused parameter. However, using _ in this way creates confusion as to why a method is called on it. I would have preferred a parameter name such as request.

Comment on lines 25 to 26
.resolve((_) => {
return _
Copy link
Member

Choose a reason for hiding this comment

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

I would have preferred a parameter name such as request.

Copy link
Member

@askayastha22 askayastha22 left a comment

Choose a reason for hiding this comment

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

Left some minor comments.

@vtsaplin vtsaplin merged commit 495011f into main Mar 15, 2024
3 checks passed
@vtsaplin vtsaplin deleted the show-retry-message branch March 15, 2024 14:23
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.

None yet

3 participants