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
API has some issues reading certain data from crawler database. Not sure if this is issue with the parser on API side or formatting by crawler.
Example of error in api logs:
Parser Error: Invalid length of '1' for input: 'geth'
Parser Error: Invalid length of '6' for input: 'Q-Client/v1.0.8-stable/Geth/v1.10.8-stable-825470ee/linux-amd64/go1.16.15'
1 Version string is invalid:
2 Version string is invalid: linux-amd64
Parser Error: Invalid length of '6' for input: 'Q-Client/v1.0.8-stable/Geth/v1.10.8-stable-714279ce/linux-amd64/go1.16.15'
Parser Error: Invalid length of '1' for input: 'geth'
Parser Error: Invalid length of '15' for input: 'Geth/enode://91a3c3d5e76b0acf05d9abddee959f1bcbc7c91537d2629288a9edd7a3df90acaa46ffba0e0e5d49a20598e0960ac458d76eb8fa92a1d64938c0a3a3d60f8be4@54.158.188.182:21000,enode://571be7fe060b183037db29f8fe08e4fed6e87fbb6e7bc24bc34e562adf09e29e06067be14e8b8f0f2581966f3424325e5093daae2f6afde0b5d334c2cd104c79@142.132.135.228:21000,enode://269ecefca0b4cd09bf959c2029b2c2caf76b34289eb6717d735ce4ca49fbafa91de8182dd701171739a8eaa5d043dcae16aee212fe5fadf9ed8fa6a24a56951c@65.108.72.177:21000,enode://d2afd84a880543a63f76d03a5e7a512e3b4d811c1d2d899dd9dd250ab093d892f05c559b6822498c5e29ad029ada71a93ad17e4a77f1d83474de417b4757ace2@82.146.35.68:30300,enode://52f736e778b1db7ece0ea2d20e1d2979db88456e7e8392abd7fb2c1bea7b73346a40de97e43615d3baac50b9bae2c16f1b156dd3c41dffd547eaaa6670ca992e@188.120.238.54:30300/v1.10.0-stable(quorum-v22.1.0)/linux-amd64/go1.17.2'
I suppose these incorrect strings are result of parse errors:
The text was updated successfully, but these errors were encountered:
- This will create a ParseTestCase so we can actually see if it actually
parsed correctly.
- Commented out the test cases that fail which needs to be fixed.
Bug: #31
API has some issues reading certain data from crawler database. Not sure if this is issue with the parser on API side or formatting by crawler.
Example of error in api logs:
I suppose these incorrect strings are result of parse errors:
The text was updated successfully, but these errors were encountered: