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

services/horizon: Return both inner and outer result codes for fee bump transactions. #4081

Merged
merged 1 commit into from
Nov 18, 2021

Conversation

erika-sdf
Copy link
Contributor

PR Checklist

PR Structure

  • This PR has reasonably narrow scope (if not, break it down into smaller PRs).
  • This PR avoids mixing refactoring changes with feature changes (split into two PRs
    otherwise).
  • This PR's title starts with name of package that is most changed in the PR, ex.
    services/friendbot, or all or doc if the changes are broad or impact many
    packages.

Thoroughness

  • This PR adds tests for the most critical parts of the new functionality or fixes.
  • I've updated any docs (developer docs, .md
    files, etc... affected by this change). Take a look in the docs folder for a given service,
    like this one.

Release planning

  • I've updated the relevant CHANGELOG (here for Horizon) if
    needed with deprecations, added features, breaking changes, and DB schema changes.
  • I've decided if this PR requires a new major/minor version according to
    semver, or if it's mainly a patch change. The PR is targeted at the next
    release branch if it's not a patch change.

What

Return both inner and outer result codes for fee bump transactions.

Why

Currently only the outer code is returned for fee bump transactions

Known limitations

N/A

Copy link
Member

@leighmcculloch leighmcculloch left a comment

Choose a reason for hiding this comment

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

💯 I would have found this sooo helpful recently. Thank you!

Copy link
Contributor

@Shaptic Shaptic left a comment

Choose a reason for hiding this comment

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

Minor notes below ⬇️

services/horizon/internal/txsub/errors.go Outdated Show resolved Hide resolved
services/horizon/internal/txsub/errors.go Outdated Show resolved Hide resolved
services/horizon/CHANGELOG.md Outdated Show resolved Hide resolved
protocols/horizon/main.go Outdated Show resolved Hide resolved
@2opremio
Copy link
Contributor

@tamirms PTAL. I am not sure the code is correct for a scenario in which a transaction and a fee bump transaction concurrently compete to get to the ledger, and the transaction makes it to the ledger first.

@@ -38,18 +38,29 @@ func (fte *FailedTransactionError) Result() (result xdr.TransactionResult, err e
return
}

func (fte *FailedTransactionError) TransactionResultCode(transactionHash string) (result string, err error) {
type OuterInnerResultCodes struct {
Copy link
Contributor

Choose a reason for hiding this comment

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

nit: since it's an exported type it would be worth adding a comment for this struct

Copy link
Contributor

Choose a reason for hiding this comment

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

I think it would be better to rename the struct to:

type ResultCodes struct {
Code string
InnerCode string
}

that way it matches the structure of TransactionResultCodes in the protocols/horizon package where we default to TransactionCode and only populate InnerTransactionCode if the request was attempting to submit a feebump transaction

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done

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.

services/horizon: result codes are incomplete for fee bump transactions
5 participants