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

fix: subscriber publish fail #5433

Merged
merged 2 commits into from
Oct 9, 2024
Merged

Conversation

ganchoradkov
Copy link
Member

@ganchoradkov ganchoradkov commented Oct 9, 2024

Description

fixed an issue where failed subscription attempts were retried instead of throwing an error

Type of change

  • Chore (non-breaking change that addresses non-functional tasks, maintenance, or code quality improvements)
  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Draft PR (breaking/non-breaking change which needs more work for having a proper functionality [Mark this PR as ready to review only when completely ready])
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

How has this been tested?

tests and in canary - 2.17.1-canary-0

Checklist

  • I have performed a self-review of my own code
  • My changes generate no new warnings
  • Any dependent changes have been merged and published in downstream modules

Additional Information (Optional)

Please include any additional information that may be useful for the reviewer.

@@ -236,6 +236,7 @@ export class Subscriber extends ISubscriber {
};
this.logger.debug(`Outgoing Relay Payload`);
this.logger.trace({ type: "payload", direction: "outgoing", request });
const shouldThrow = opts?.internal?.throwOnFailedPublish;
Copy link
Contributor

Choose a reason for hiding this comment

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

this is true by default now, right? Would it cause issues in wallets that upgrade to this version? 🤔

Copy link
Member Author

Choose a reason for hiding this comment

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

nope. It would raise early feedback if there are network issues

@ganchoradkov ganchoradkov merged commit 304b77a into v2.0 Oct 9, 2024
13 checks passed
@ganchoradkov ganchoradkov deleted the fix/subscriber-publish-fail branch October 9, 2024 12:47
@ganchoradkov ganchoradkov mentioned this pull request Oct 9, 2024
20 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants