Closed drdaeman closed 8 years ago
Tnx, your solution seems right. I'l check and fix it this monday.
Fixed in 0.1.12
Am I getting the same error on 0.1.12? (cleared cache, installed from github)
Apply rules
Processing String patterns: 42%|██████████████████████████████████████████████████▊ | 420157/992681 [00:32<00:43, 13024.41it/s]Traceback (most recent call last):
File "/usr/local/bin/rma", line 9, in
Sorry for that, missing more one place with this error. Commit fix with 0.1.13
First of all, thank you for this tool.
I've encountered an issue while I was trying to analyze what's taking the memory. While there's a guard against some cases when keys were removed after the scan,
rma
crashes when it encounters an integer-containing key that's already gone whenValueString
gets to it.Here's an example traceback:
The solution seems to handle
TypeError
as well asValueError
inRealStringEntry.get_int_encoded_bytes
. E.g. replacingexcept ValueError:
withexcept (ValueError, TypeError):
. Tried this on my local copy and it worked for me - I got a sensible-looking report. I'm not really sure if that's completely correct, though - maybe manually raisingResponseError("no such key")
would be a better approach there.Thanks!