Help with testing 0.12.1dev2 build

Hi all,

I just pushed a new Bokeh dev build 0.12.1dev2, which is available for immediate download. Simple installation instructions for dev builds are here:

  http://bokeh.pydata.org/en/latest/docs/installation.html#developer-builds

I'd like to ask for help testing this dev build, with a particular eye towards stability in the Jupyter notebook. It seemed to be the case that with BokehJS loading from CDN, it is sometimes possible for a `show` to execute before BokehJS was ready, and unfortunately this condition could also leave a notebook in a fairly unrecoverable state, requiring a full notebook server restart. This PR:

  https://github.com/bokeh/bokeh/pull/4782

should, at a minimum, make it so that any race conditions like the one described above are always fully recoverable, typically by just re-running the relevant cells. If BokehJS is not actually loaded yet, a prominent warning with some suggested courses of action is displayed. This issue has be *extremely* hard to reproduce and pin down, so please give this dev build a workout with the Jupyter notebook, and report any ongoing problems with 0.12.1dev2 here.

For completeness, this dev build also has the following other changes:

# bugfixes
- render issue for autoload server
- reset button missing from gridplots
- draw legend after webgl glyphs

# features
- update to rbush 2.0.1
- cartodb tile providers added
- improve pypy compatibility

Additionally there were several developer-oriented improvements to build and test infrastructure, and tweaks to docs as well. Many thanks to several new contributors. We are planning to have a small incremental 0.12.1 release next week. Some other things that might make that release:

- webgl working on safari
- layout-related cleanup

Regards,

Bryan

Just tried 0.12.1dev2 - the problem I had with show() not showing figures in notebooks has disappeared. Tried a few different notebooks which had problems, all seemed to be working fine now. Magic! Thanks guys!

Will

···

On Jul 12, 2016, at 19:28, Bryan Van de Ven [email protected] wrote:

Hi all,

I just pushed a new Bokeh dev build 0.12.1dev2, which is available for immediate download. Simple installation instructions for dev builds are here:

http://bokeh.pydata.org/en/latest/docs/installation.html#developer-builds

I’d like to ask for help testing this dev build, with a particular eye towards stability in the Jupyter notebook. It seemed to be the case that with BokehJS loading from CDN, it is sometimes possible for a show to execute before BokehJS was ready, and unfortunately this condition could also leave a notebook in a fairly unrecoverable state, requiring a full notebook server restart. This PR:

https://github.com/bokeh/bokeh/pull/4782

should, at a minimum, make it so that any race conditions like the one described above are always fully recoverable, typically by just re-running the relevant cells. If BokehJS is not actually loaded yet, a prominent warning with some suggested courses of action is displayed. This issue has be extremely hard to reproduce and pin down, so please give this dev build a workout with the Jupyter notebook, and report any ongoing problems with 0.12.1dev2 here.

For completeness, this dev build also has the following other changes:

bugfixes

  • render issue for autoload server
  • reset button missing from gridplots
  • draw legend after webgl glyphs

features

  • update to rbush 2.0.1
  • cartodb tile providers added
  • improve pypy compatibility

Additionally there were several developer-oriented improvements to build and test infrastructure, and tweaks to docs as well. Many thanks to several new contributors. We are planning to have a small incremental 0.12.1 release next week. Some other things that might make that release:

  • webgl working on safari
  • layout-related cleanup

Regards,

Bryan


You received this message because you are subscribed to the Google Groups “Bokeh Discussion - Public” group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit https://groups.google.com/a/continuum.io/d/msgid/bokeh/8DB5C7CE-B295-4D61-82AF-60E7FF7BEEBE%40continuum.io.
For more options, visit https://groups.google.com/a/continuum.io/d/optout.

Hi Bryan,

I know it’s not listed in your bugfixes but thought I’d point out that the non-editable DataTable bug is still there.

Marcus.

···

On Tuesday, July 12, 2016 at 7:28:49 PM UTC+1, Bryan Van de ven wrote:

Hi all,

I just pushed a new Bokeh dev build 0.12.1dev2, which is available for immediate download. Simple installation instructions for dev builds are here:

    [http://bokeh.pydata.org/en/latest/docs/installation.html#developer-builds](http://bokeh.pydata.org/en/latest/docs/installation.html#developer-builds)

I’d like to ask for help testing this dev build, with a particular eye towards stability in the Jupyter notebook. It seemed to be the case that with BokehJS loading from CDN, it is sometimes possible for a show to execute before BokehJS was ready, and unfortunately this condition could also leave a notebook in a fairly unrecoverable state, requiring a full notebook server restart. This PR:

    [https://github.com/bokeh/bokeh/pull/4782](https://github.com/bokeh/bokeh/pull/4782)

should, at a minimum, make it so that any race conditions like the one described above are always fully recoverable, typically by just re-running the relevant cells. If BokehJS is not actually loaded yet, a prominent warning with some suggested courses of action is displayed. This issue has be extremely hard to reproduce and pin down, so please give this dev build a workout with the Jupyter notebook, and report any ongoing problems with 0.12.1dev2 here.

For completeness, this dev build also has the following other changes:

bugfixes

  • render issue for autoload server

  • reset button missing from gridplots

  • draw legend after webgl glyphs

features

  • update to rbush 2.0.1

  • cartodb tile providers added

  • improve pypy compatibility

Additionally there were several developer-oriented improvements to build and test infrastructure, and tweaks to docs as well. Many thanks to several new contributors. We are planning to have a small incremental 0.12.1 release next week. Some other things that might make that release:

  • webgl working on safari

  • layout-related cleanup

Regards,

Bryan