-
Notifications
You must be signed in to change notification settings - Fork 158
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
VdebugEval! Can't get values of array at depth > 1 #503
Comments
I was wrong about Vorbis comments. According to to xiph.org specs, the encoding must be utf8. So evidently, the FLAC files were either corrupted or improperly encoded. I confirmed that the FLAC files were the problem by examining an mp3 file with Vdebug while stepping through the code, so I will close this issue. Vdebug is a great vim plugin. Along with the ALE plugin, I have a very effective IDE with only 3 gb ram on a Samsung tablet. Thanks |
I repeated the testwith the mp3 file. On second attempt to reproduce , it also didplayed the same AttributeError. |
I get this error when trying to inspect most variables (occasionally it works, haven't figured out the pattern, though!)
It also blows up if I try to get back to the context window:
Is this related? I'm on nvim 0.5.0 and vdebug 2.0.0 |
$apics = $data['flac']['PICTURE'];
The statement
:VdebugEval! $apics
reports a type of "$apics[0] = (array[10])" with no values.The statement
:VdebugEval! $apics[0]
gives the error "AttributeError: 'NoneType' object has no attribute 'isdigit'".if I explicitely request a value
:VdebugEval! $apic[0]['description']
the value will be displayed with no errors.result of Issuing request for info from array with depth = 1:
Vdebug version 2.0.0
Python version 3.9.3
vim version 8.1.2269
Ubuntu version 'focal' prooted distribution for running on Android 10 (unrooted)
xdebug.var_display_max_depth = -1 (1023)
Could a config setting change be required? Maybe with Python?
I am Working with metadata from flac files provided by the getID3 php library. Data could include utf-16 encoded values.
The text was updated successfully, but these errors were encountered: