unicode parsing issues for sample data provided? #156
-
Heyo! Not sure if this project is still active, but: When running it, 1) - the output messaging seems to claim that it is ignoring the ledgers I asked for... and 2) the execution end with an error about not being able to decode a character to unicode format? It has that same error with or without the ledgers parameter, or using any other parameters. I downloaded the sample data for bitcoin, tezos, cardano, and ethereum from the page linked in the readme. Any thoughts on this one? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 5 replies
-
Hello @fractaloutlook, thanks for raising this to our attention. For your first point, we very recently changed the way parameters are specified and I only now realise that we forgot to update the documentation, sorry about that! We will update the docs asap, but basically all the configurations are now done through the config.yaml file. So if you want only one ledger to be included, you would need to comment out the rest. Let me know if you have any questions on this. For your second issue, I'm not sure why this is happening, it's not something I can reproduce right now. Can you confirm that you haven't made any changes to this file on your local copy? |
Beta Was this translation helpful? Give feedback.
Thanks for the response. I think I figured out the issue - we have to explicitly specify the encoding when reading the identifier files in order for them to be parsed on Windows. I have opened a PR that solves this issue, I will let you know once it is approved and merged into the main branch