-
Notifications
You must be signed in to change notification settings - Fork 116
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
Decode class for "Compact<u32>" not found #336
Comments
Could you provide a bit more context, like logs or example code to reproduce? The type |
Here's the error, when trying to retrieve a block from polkadot using Polkadot's relay chain mainnet: Any ideas on how to surpass it, or even find an implementation of this decoder class elsewhere? |
This is odd.. Retrieving a block from Polkadot is such a basic tasks, this shouldn't go wrong under normal circumstances. Can you tell a bit more about your setup (OS, Python version, etc). Are you using threads or some other kind of async configuration? Because then it seems a like described in #246 I wasn't able to reproduce that scenario yet, but I'll run some more tests. |
I'm also seeing the same error, along with this one:
My use case is querying blocks from a Substrate based chain in parallel using threads. I use a I can try slimming my code down to a minimal example if that would be helpful. What I noticed is that this only occurs in a fresh environment. Previously I did not have the issue running the same code using older package versions. I tested on both Python 3.10 and 3.11. Here's the working package list:
Versus the fresh install that produces the error:
The versions in my working set are more recent than those reported in #246, so that suggests there is not a common root cause that was introduced in the set of updates between my two package sets. That is, the issue reported there was already occurring in versions earlier than those that worked for me. |
We are getting the same error, only while multi-threading. It seems that downgrading |
I'm still seeing this issue with I have here a minimal script that reproduces the issue on the majority of runs. This is on Python
In my experience, it's often only a single thread that has the error and always toward the beginning of the run. My workaround is to just let the thread(s) die and then spawn new ones to take their place. The replacement threads seem to never fail. So the failure condition appears to be something around the simultaneous launching of many threads in a fresh environment. Hope this can help you to reproduce and get to the bottom of this one, @arjanz. Thanks! |
Are there any updates regarding this error?
Is there a way to overcome it/come around it for the timebeing?
The text was updated successfully, but these errors were encountered: