Seth Michael Larson
Seth Michael Larson
Hey nice catch! Looks like Virtualbox named the .so module wrong somewhere? Maybe I'll investigate being able to package all of these together so that this doesn't happen in the...
That's a good source. We can maybe work around this by packaging VBoxPython or emitting a better error.
I opened a defect with VirtualBox: https://www.virtualbox.org/ticket/17448
I think I've seen this before too, I was unable to figure out why. The only thing I can think of is objects being de-allocated and threading not playing nice...
Can you do me a favor and remove all the `try-except` logic within `_call_method` and post the actual traceback? I'm going to be rewriting this logic in v2.
It looks like for whatever reason XPCOM is converting the data into UTF-8 when it's probably just raw bytes or a bytearray. :/ It's a shame that traceback doesn't include...
I think this might be XPCOM's fault? Even though our logic incorrectly identifies the type `octet` as a `str` in the documentation we don't convert the output at all when...
I'm aware of the distinction. :) I'm not sure what XPCOM does to load that function into existence because it's not defined within the Python bindings that come with the...
It gets distributed with the VirtualBox SDK. XPCOM is the library that communicates with the VirtualBox process.
Thanks for debugging this! This means the fault may be outside our jurisdiction?