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

[Access] Pending response from send and subscribe should return immediately #6573

Closed
Tracked by #6163
peterargue opened this issue Oct 18, 2024 · 1 comment · Fixed by #6737
Closed
Tracked by #6163

[Access] Pending response from send and subscribe should return immediately #6573

peterargue opened this issue Oct 18, 2024 · 1 comment · Fixed by #6737
Assignees
Labels

Comments

@peterargue
Copy link
Contributor

Problem Definition

The SendAndSubscribe streaming grpc endpoint allows a user to send a transaction and immediately subscribe to status updates. Currently, it takes one or more seconds before receiving the first response indicating the transaction is pending. Since the transaction was submitted to that streaming node, it should know that the tx is pending immediately.

I suspect the issue is that it waits until the next block is finalized before triggering, then searches several blocks to catch up with the block the tx was included in.

Proposed Solution

Instead of waiting, add the pending status message immediately after creating the subscription:

return b.subscriptionHandler.Subscribe(ctx, nextHeight, b.getTransactionStatusResponse(&txInfo))

Definition of Done

When calling SendAndSubscribe, the pending response should be received immediately with no delay.

Copy link
Contributor

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the Stale Label used when marking an issue stale. label Feb 25, 2025
@franklywatson franklywatson added Preserve Stale Bot repellent and removed Stale Label used when marking an issue stale. labels Feb 25, 2025
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 a pull request may close this issue.

3 participants