-
Notifications
You must be signed in to change notification settings - Fork 3
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
Getting Null Values from transaction logs #6
Comments
Can you elaborate what is Null values? Do you see any records in the transaction table? |
No records in the transactions table when running the query SELECT (meta).log_messages FROM transaction |
Thanks for reporting this issue -- I will look into this as a priority. |
@Dassy23 -- can you try add the following arguments in your validator command line as a workaround? --enable-cpi-and-log-storage --enable-rpc-transaction-history I will make a change to support it without requiring these args. |
This issue seems to be caused by a recent change: 45458e71393 ledger/src/blockstore_processor.rs (Justin Starry 2022-01-05 10:15:15 +0800 1434) if !self.enable_cpi_and_log_storage { |
Thanks for the quick response on this @lijunwangs |
Transaction logs are not being saved to the database through the plugin interface. Summary of Changes Retain the transaction logs when transaction notification plugin is loaded. Fixes # lijunwangs/solana-accountsdb-plugin-postgres#6
…-labs#22874) Transaction logs are not being saved to the database through the plugin interface. Summary of Changes Retain the transaction logs when transaction notification plugin is loaded. Fixes # lijunwangs/solana-accountsdb-plugin-postgres#6
Appears that transaction logs are not being saved to the database
The text was updated successfully, but these errors were encountered: