Open Dragony opened 3 years ago
This error can sometimes occur when the spec does not match what is present in the actual dat file you are trying to read.
OK thanks. I've seen the Specification row size ...
error a lot and wasn't sure if this one was from the same category.
To be a bit more specific: I'm not sure if that is the only thing that can cause this error, but it's the only thing that I've personally had cause it.
Do you know if it is reasonable to expect an update from the maintainers? Or do you think I will have more luck fixing this myself?
checks project's commit history
It seems that some people occasionally submit specification updates, but I don't see a standard release cycle anywhere.
Generally, if I have a spec error I fix it myself. (There are instructions for how to name different types of fields in fields.py). If you do so, consider submitting your spec update as a PR, so that everyone can benefit.
If you wait, there is a chance someone might come along and update it, but there is no official update strategy/deadline afaik.
E: I imagine many people simply update the spec for just the files that they need to reference, and leave the rest.
Hello there! Thanks for investing so much time into such a usefull tool :-)
Today I tried to extract data via the CLI:
That seems to work for a while until:
Any idea why this is happening?