You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Expected archive schema string does not match generated resource schema. #233
I am on the latest commit of master (b1d77cb), and I am having issues with loading archives after modifying the schema. Playing around with osmflat-rs, I added a few things to the schema. I am able to compile OSM data fine, but when I try and open an archive (using the debug example), I get ResourceStorageError.WrongSignature.
Digging in a bit, it looks like flatdata-generator and the archive.schema written to the data directory do not match with their tags. The check to see if the stored schema and expected schema is simply doing a string compare, and this fails.
if stored_schema != expected_schema {returnErr(ResourceStorageError::WrongSignature{resource_name: resource_name.into(),diff:compute_diff(stored_schema, expected_schema),});}
From the generated file, the OSM raw string representing the schema does not have a tab indenting the contents of the namespace. The archive.schema file does.
Activity
hallahan commentedon Oct 25, 2022
There is something weird about this, because I can't seem to reproduce it consistently.
VeaaC commentedon Oct 26, 2022
That is a bit weird, normally the same string is used for writing the archive's schema, as well as for checking it.
Do you maybe have some kind of automatic reformatting tool/setting configured in your IDE/Git/etc?