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

No traces available for a single transaction in a block #2626

Closed
SMihai97 opened this issue Jan 23, 2024 · 7 comments · Fixed by #2707
Closed

No traces available for a single transaction in a block #2626

SMihai97 opened this issue Jan 23, 2024 · 7 comments · Fixed by #2707

Comments

@SMihai97
Copy link

Block 5327887 has transaction 0xd91d98b539720d8a42069268126d366fd29165e487d94b165a97e0158842657b that doesn't have any traces when requesting them.
Example:
curl -H "Content-Type: application/json" -d '{"id":1,"jsonrpc":"2.0","method":"debug_traceTransaction","params":["0xd91d98b539720d8a42069268126d366fd29165e487d94b165a97e0158842657b",{"tracer":"callTracer"}]}' http://localhost:9944 {"jsonrpc":"2.0","error":{"code":-32603,"message":"DispatchError: Other(\"\")"},"id":1}

The other transactions in the block seem to have traces.
Example of a transaction from the same block that has traces:
curl -H "Content-Type: application/json" -d '{"id":1,"jsonrpc":"2.0","method":"debug_traceTransaction","params":["0x90878f66568d39eb8f6d4a7f4f87bbd2ad8ddb68fff3ccbfd1ae7353ab2430da",{"tracer":"callTracer"}]}' http://localhost:9944 {"jsonrpc":"2.0","result":{"from":"0x5ed29a67e1b32b16ff7dcb8d19a65e30bd50c43d","gas":"0x0","gasUsed":"0x8f6a","type":"CALL","to":"0xffffffff7d3875460d4509eb8d0362c611b4e841","input":"0x095ea7b3000000000000000000000000841ce48f9446c8e281d3f1444cb859b4a6d0738cffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff","output":"0x0000000000000000000000000000000000000000000000000000000000000001","value":"0x0"},"id":1}

We are running on the latest version moonbeam-skylake 0.35.0-7131ef902c0 and latest runtime 2700. This seems to affect other providers as well.

@noandrea
Copy link
Contributor

thanks for reporting, we'll be looking into it

@blocknodehub
Copy link

thanks for reporting, we'll be looking into it
I also have this problem, you can't get trace data through the transaction hash, but you can get trace data through the block height
#2629

@rrozek
Copy link

rrozek commented Feb 12, 2024

any news on this one? ETA on delivery?

For some context, this prevents subsquid indexer from indexing chain traces which are of significant value to some projects based on data provided by subsquid archives :)
As subsquid is the go-to solution for accessing data from Moonbeam chain, no full support hurts the whole ecosystem

@noandrea
Copy link
Contributor

noandrea commented Mar 4, 2024

no news on this one so far, but we are tracking it. I'll write as soon as we have identified the problem and have a solution

@librelois librelois added B5-clientnoteworthy Changes should be mentioned in any downstream projects' release notes D3-trivial PR contains trivial changes in a runtime directory that do not require an audit not-breaking Does not need to be mentioned in breaking changes and removed B5-clientnoteworthy Changes should be mentioned in any downstream projects' release notes D3-trivial PR contains trivial changes in a runtime directory that do not require an audit not-breaking Does not need to be mentioned in breaking changes labels Mar 18, 2024
@noandrea
Copy link
Contributor

@noandrea
Copy link
Contributor

I'm reopening this one for now waiting for confirmation.

@noandrea noandrea reopened this Mar 22, 2024
@RomarQ
Copy link
Contributor

RomarQ commented May 17, 2024

Just confirmed that the issue has been fixed.

@RomarQ RomarQ closed this as completed May 17, 2024
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 a pull request may close this issue.

6 participants