Mateusz Paprocki

No, it still needs fixes, but it isn't too far off.

The remaining sub-tasks to finalize the release: - [ ] Establish a migration path and/or compatibility mode after CSS modularization (see #12082). - [x] Finalize layout redesign (#11915). - [x]...

It looks like there's a mixup between ipv4 and ipv6 addresses. Is this a new issue? Perhaps you've updated chromium recently? Or maybe you have a very new (and possible...

Downgrade nodejs to 16 and it should work again.

It looks like starting with nodejs 17, ipv6 is preferred over ipv4. I'm guessing you can try using `NODE_OPTIONS=--dns-result-order=ipv4first` with 17 as a workaround. However, we support only even number...

Possibly, at least until a solution is devised. I'm pretty sure preference for ipv6 isn't going away in 18, so we need to figure out how to deal with this...

By default nothing will change, however, PR #8085 adds support for configuring frame dimensions (instead of plot dimensions), so with some configuration this issue will be solvable.

> I will work up a fuller PR with a BOKEH_PROPERTY_ERROR_MAXLEN config env var and tests, etc. Does this really have to be configurable? Who will be adjusting it?

This seems like a problem with the notebook as well, because you can easily issue a command like `np.array(['a'*10000000])` with similar results. Notebook should be aware that dumping tens or...

> Property does need to be configurable for debugging I doubt making it configurable will help with debugging. If the limit is set to some reasonable value, then on those...