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

EXPERIMENTAL_tx_status times out on light-client #4404

Closed
frol opened this issue Jun 23, 2021 · 6 comments
Closed

EXPERIMENTAL_tx_status times out on light-client #4404

frol opened this issue Jun 23, 2021 · 6 comments
Labels
A-network Area: Network A-RPC Area: rpc T-public-interfaces Team: issues relevant to the public interfaces team

Comments

@frol
Copy link
Collaborator

frol commented Jun 23, 2021

Describe the bug

Light-client routes the tx requests to full nodes and our network layer is only capable to fetch transactions without receipts. This means that we need to extend the network protocol with a new command or patch the existing one if we want tx to return receipts. Alternatively, we may consider other options, but either way EXPERIMENTAL_tx_status is essentially currently broken and cannot be stabilized as is to become tx endpoint.

#4364 (comment)

Other options:

To Reproduce

Boot light-client node (the node that does not track any shard "tracked_shards": []) and query EXPERIMENTAL_tx_status:

$ http post http://127.0.0.1:3030/ jsonrpc=2.0 method=EXPERIMENTAL_tx_status params:='["<tx-hash>", "near"]' id=dontcare

The response will be a timeout server error, while querying tx endpoint will bring the result

Expected behavior

That is yet to be decided in #4393

@frol frol added A-network Area: Network A-RPC Area: rpc labels Jun 23, 2021
@bowenwang1996 bowenwang1996 added the T-public-interfaces Team: issues relevant to the public interfaces team label Jun 28, 2021
@stale
Copy link

stale bot commented Sep 26, 2021

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

@stale stale bot added the S-stale label Sep 26, 2021
@bowenwang1996
Copy link
Collaborator

I believe this is already done. @frol please reopen if it is not the case

@frol
Copy link
Collaborator Author

frol commented Oct 11, 2021

I feel we have not arrived to any solution there. #4364

@frol frol reopened this Oct 11, 2021
@stale stale bot removed the S-stale label Oct 11, 2021
@stale
Copy link

stale bot commented Jan 9, 2022

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

@stale stale bot added the S-stale label Jan 9, 2022
@frol frol removed the S-stale label Jan 11, 2022
@frol
Copy link
Collaborator Author

frol commented Jan 11, 2022

Just for the record, there is some update to the conversation happening here: #4393 (reply in thread)

@bowenwang1996
Copy link
Collaborator

@frol let's close this issue in favor of the discussion then

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-network Area: Network A-RPC Area: rpc T-public-interfaces Team: issues relevant to the public interfaces team
Projects
None yet
Development

No branches or pull requests

2 participants