Closed peterroelants closed 1 year ago
I experience the same error.
@mattpap, any idea what is causing this?
inner_height
is a readonly property set by bokehjs and returned back to bokeh. Seeing this code:
getattr(resolved, p, None)
If I understand this code correctly, then this is expected to fail. Since the introduction of unset values, getting bokeh's properties like this will result in UnsetValueError
, if the value is unset. None
is a perfectly valid value in bokeh's type system (see Nullable
), thus it shouldn't be expected to be viable missing value indicator. try-expect UnsetValueError
should resolve this, at least on the surface. However, if someone could explain the intention behind this code, then I can point to the right API to deal with this.
The behavior only happens in VSCode, which uses jupyter_bokeh
.
As far as I can see, the example works even with the error.
As far as I can see, the example works even with the error.
That's expected. inner_height
and similar properties are for informational purpose and have no real bearing on anything. If the failure doesn't interrupt anything important, then a bokeh process will continue fine, just with the relevant value missing.
The behavior only happens in VSCode,
It may be a timing issue. If those properties are read before bokehjs has a chance to update them, then UnsetValueError
will occur. If things happen in holoviews (or whichever layer of integration) before bokehjs signals the ready state, then errors like this one should be expected.
Description of expected behavior and the observed behavior
Using
rasterize
leads to the following being printed to the output:For some reason the result is non-deterministic, I can not always replicate this (only exactly the same setting). Testing this on VSCode notebooks.
Complete, minimal, self-contained example code that reproduces the issue
Stack traceback and/or browser JavaScript console output
ALL software version info