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

Tokens that fail to redeem due to network errors should be added to a queue and retried #2072

Merged
merged 1 commit into from
Mar 26, 2019

Conversation

tmancey
Copy link
Collaborator

@tmancey tmancey commented Mar 26, 2019

fixes brave/brave-browser#3662

Submitter Checklist:

  • Submitted a ticket for my issue if one did not already exist.
  • Used Github auto-closing keywords in the commit message.
  • Added/updated tests for this change (for new code or code which already has tests).
  • Verified that these changes build without errors on
    • Windows
    • macOS
    • Linux
  • Verified that these changes pass automated tests (npm test brave_unit_tests && npm test brave_browser_tests && npm run test-security) on
    • Windows
    • macOS
    • Linux
  • Verified that all lint errors/warnings are resolved (npm run lint)
  • Ran git rebase master (if needed).
  • Ran git rebase -i to squash commits (if needed).
  • Tagged reviewers and labelled the pull request as needed.
  • Request a security/privacy review as needed.
  • Add appropriate QA labels (QA/Yes or QA/No) to include the closed issue in milestone

Test Plan:

Confirm failed requests are added to the Defaults/rewards_service/confirmations.json under confirmations/failed_confirmations and confirmation redemption is retried every 5 minutes +/- jitter until successful. Items that are retried and fail should move to the back of the queue.

Reviewer Checklist:

  • New files have MPL-2.0 license header.
  • Request a security/privacy review as needed.
  • Adequate test coverage exists to prevent regressions
  • Verify test plan is specified in PR before merging to source

emerick
emerick previously approved these changes Mar 26, 2019
Copy link
Contributor

@emerick emerick left a comment

Choose a reason for hiding this comment

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

LGTM

};

ConfirmationType() = default;
constexpr ConfirmationType(const Value value) : value_(value) {}
Copy link
Member

Choose a reason for hiding this comment

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

lint error here, Single-parameter constructors should be marked explicit. [runtime/explicit] [5]

Copy link
Member

Choose a reason for hiding this comment

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

as we discussed in slack, I'm fine with NOLINT and a comment stating that we allow implicit conversion from enum value to this wrapper class, similar as https://cs.chromium.org/chromium/src/v8/src/wasm/value-type.h?rcl=88a0c6d607cf023a5776193fe1786be0ca9c0767&l=64-65.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

👍 added NOLINT and comment as above, thanks

};

ConfirmationType() = default;
constexpr ConfirmationType(const Value value) : value_(value) {}
Copy link
Member

Choose a reason for hiding this comment

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

DITTO.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

👍 added NOLINT and comment as above, thanks

@tmancey tmancey force-pushed the issues/3662 branch 3 times, most recently from a82f845 to 4f25fb3 Compare March 26, 2019 19:36
Copy link
Member

@yrliou yrliou left a comment

Choose a reason for hiding this comment

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

LGTM

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

Successfully merging this pull request may close these issues.

Tokens that fail to redeem due to network errors should be added to a queue and retried
3 participants