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

api.at warn Unable to map [u8; 32] to a lookup index #5871

Closed
3 of 10 tasks
jiqiang90 opened this issue May 8, 2024 · 3 comments
Closed
3 of 10 tasks

api.at warn Unable to map [u8; 32] to a lookup index #5871

jiqiang90 opened this issue May 8, 2024 · 3 comments

Comments

@jiqiang90
Copy link
Contributor

  • I'm submitting a ...
  • Bug report
  • Feature request
  • Support request
  • Other
  • What is the current behavior and expected behavior?

We are recently update to v11, and we found decorated method api.at will throw warning, this flood so all other logs within our app, it also lead other logs monitoring app crashes.

To reproduce this:

const { ApiPromise, WsProvider } = require(`@polkadot/api`)
const provider = new WsProvider('wss://rpc-polkadot.luckyfriday.io');


async function main(){
    const api = await ApiPromise.create({provider});
    // block height 38565
    const apiAt = await api.at('0xad17bc48645d34fb7e7109f047d027d7db21cfda17e4bade2007a247e47f7c79');
}

main().catch(e=>process.exit(1));

this should warn

Unable to map [u8; 32] to a lookup index
  • What is the motivation for changing the behavior?

Improved logging

  • Please tell us about your environment:

    • Version: 11.0.2

    • Environment:

      • Node.js v18.17.1
      • Browser
      • Other (limited support for other environments)
    • Language:

      • JavaScript
      • TypeScript (include tsc --version)
      • Other
@TarikGul
Copy link
Member

rel: #5764

I will have this on the project board queue, but I don't see much that can be done to resolve this. At best we can switch the type of logging so that it can be turned off and or reduced.

@TarikGul
Copy link
Member

Closing as any additional changes the to logging here wont change - I did general testing across sidecar and saw only limited logging per runtime across polkadot and kusama.

@polkadot-js-bot
Copy link

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query.

@polkadot-js polkadot-js locked as resolved and limited conversation to collaborators Nov 5, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants