admin管理员组文章数量:1355540
I am experiencing an issue with the getParsedTransaction
method in my production-level Solana application. Below is the function I am using:
and this is the
transactionHash - 5fjQhxghz4wHDUgECnMYo82C5THbkaJ55PSoJQPT9YxhR95sXfw3Equx3vmDhy4zrqfev97U3cqTA48o88Qei1tT
async getParsedTransactionReceipt(transactionHash: string) {
const connection = await this.getConnectionWithFallback();
const tx = await connection.getParsedTransaction(transactionHash, {
commitment: 'confirmed',
maxSupportedTransactionVersion: 2,
});
return tx;
}
While this function works as expected in most cases, I have noticed that it intermittently returns null for the same transaction. This inconsistency is causing significant issues in my production environment.
Observations: The transaction hash is valid.
The function sometimes returns the expected parsed transaction and, at other times, returns null for the same transaction.
I am using commitment: 'confirmed'.
The issue occurs unpredictably and is not easily reproducible.
Has anyone else encountered this behavior with getParsedTransaction?
What could be the underlying cause of this intermittent response?
Are there any best practices or alternative approaches to ensure a more consistent and reliable response?
Any insights or solutions would be greatly appreciated. Thank you in advance for your help!
本文标签: Nondeterministic returns from getParsedTransaction function of solanaStack Overflow
版权声明:本文标题:Non-deterministic returns from getParsedTransaction function of solana - Stack Overflow 内容由网友自发贡献,该文观点仅代表作者本人, 转载请联系作者并注明出处:http://www.betaflare.com/web/1744052608a2582696.html, 本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌抄袭侵权/违法违规的内容,一经查实,本站将立刻删除。
发表评论