Skip to content
This repository has been archived by the owner on Dec 16, 2021. It is now read-only.

feat!: handle new drive error codes #405

Merged
merged 15 commits into from
Sep 15, 2021
Merged

feat!: handle new drive error codes #405

merged 15 commits into from
Sep 15, 2021

Conversation

shuplenkov
Copy link
Member

@shuplenkov shuplenkov commented Sep 6, 2021

Issue being fixed or feature implemented

Handle new Drive error codes dashevo/js-drive#562

What was done?

  • Handle new drive error codes
  • Get error data from the info field of ABCI response, instead of log

How Has This Been Tested?

  • With CI

Breaking Changes

DAPI responds with new error codes

Checklist:

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have added or updated relevant unit/integration/functional/e2e tests
  • I have made corresponding changes to the documentation

For repository code-owners and collaborators only

  • I have assigned this pull request to a milestone

shumkov
shumkov previously approved these changes Sep 15, 2021
Copy link
Member

@shumkov shumkov left a comment

Choose a reason for hiding this comment

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

LGTM! 👍

@shumkov shumkov changed the title feat: handle new drive error codes feat!: handle new drive error codes Sep 15, 2021
@shumkov shumkov merged commit 2a02887 into v0.21-dev Sep 15, 2021
@shumkov shumkov deleted the error-codes branch November 2, 2021 15:14
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants