You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Submitted tx that passes simulation fine but fails immediately with TxSorobanInvalid when submitted. Running soroban-cli with --very-verbose mode.
What did you expect to see?
Diagnostic logs about why the TxSorobanInvalid error occurred. Diagnostic events are outputted for the simulation, but not for the submission, even though stellar-core provides these on the submission /tx endpoint.
I'm not actually sure which stellar-core the submission occurs through, but if it occurs through the soroban-rpc's stellar-core which has diagnostic logs enabled (as evidenced by the diagnostic events visible during simulation), the immediate error response from stellar-core should have diagnostic logs according to @dmkozh.
The text was updated successfully, but these errors were encountered:
This issue is stale because it has been assigned for 30 days with no activity. It will be closed in 30 days unless the stale label is removed, and the assignee is removed or updated.
What version are you using?
Ref: https://discord.com/channels/897514728459468821/966788672164855829/1174863875229892708
What did you do?
Submitted tx that passes simulation fine but fails immediately with
TxSorobanInvalid
when submitted. Running soroban-cli with--very-verbose
mode.What did you expect to see?
Diagnostic logs about why the
TxSorobanInvalid
error occurred. Diagnostic events are outputted for the simulation, but not for the submission, even though stellar-core provides these on the submission/tx
endpoint.What did you see instead?
No diagnostic events/logs on the submission.
Full logs: https://discord.com/channels/897514728459468821/966788672164855829/1174863666252877834
Discussion
It is possible this is a bug in the RPC, unclear.
I'm not actually sure which stellar-core the submission occurs through, but if it occurs through the soroban-rpc's stellar-core which has diagnostic logs enabled (as evidenced by the diagnostic events visible during simulation), the immediate error response from stellar-core should have diagnostic logs according to @dmkozh.
The text was updated successfully, but these errors were encountered: