1. 08 Aug, 2017 1 commit
    • Łukasz Nowak's avatar
      jupyter: Simplify ERP5kernel maintenance · 554dc32d
      Łukasz Nowak authored
      Instead of templating python code, make it static and parameterize it
      with parameters.
      kernel.json can pass default ERP5 url, which is (dirty) read by
      ERP5kernel. Additionally ERP5kernel.py is just linked into kernel
      directory, which simplifies debugging.
      Note: This commit is still dirty, but it prepares ERP5kernel.py to be
            packaged, thus there is no reason to make more changes and
      /reviewed-on !206
  2. 25 Jul, 2017 1 commit
  3. 21 Jun, 2017 1 commit
  4. 12 Jun, 2017 1 commit
    • Iliya Manolov's avatar
      Added a warning about using old references on Jupyter notebooks · 3ba2543c
      Iliya Manolov authored
      @Tyagov @luke 
      This MR adds the following to all Jupyter notebooks:
       - A warning when a user inputs a reference that has already been used in one of his old Jupyter notebooks. 
       - Some extra information when entering magics such as the remaining required magics.
       - Entering the reference MUST now be the last magic entered(otherwise the reference check doesn't work).
       - A small addition to the message at the top of the notebook for the command ```%notebook_set_title```
      Also, do note that the edited kernel uses files from [this commit](erp5@4a3e5173) from my erp5 repo, so the changes there must be available for the kernel to work. [This merge request](erp5!283) addresses those changes.
      Sample screenshot:
      /reviewed-on !177
  5. 08 Jun, 2017 1 commit
  6. 17 Mar, 2017 1 commit
  7. 18 Feb, 2017 1 commit
  8. 20 Jan, 2017 1 commit
  9. 21 Nov, 2016 1 commit
  10. 18 Feb, 2016 1 commit
  11. 01 Feb, 2016 2 commits
    • Douglas's avatar
      Jupyter: ERP5 kernel sends code using POST · cf117ccd
      Douglas authored
      Query strings used on GET requests have size limitations
      on servers and this causes big code cells to not be executed
      at all, returning only an Internal Server Error with no
      further explanation.
      /reviewed-by @kirr, @Tyagov (on !43)
    • Kirill Smelkov's avatar
      ERP5 and Jupyter integrated together · 0a446263
      Kirill Smelkov authored
      This patch teaches ERP5 software release to automatically instantiate Jupyter
      notebook web UI and tune it to connect to ERP5 by default. When Jupyter is
      enabled, it also installs on-server erp5_data_notebook bt5 (erp5!29)
      which handles code execution requested for Jupyter.
      For ERP5 - for security and backward compatibility reasons - Jupyter
      instantiation and erp5_data_notebook bt5 install happen only if jupyter is
      explicitly enabled in instance parameters. The default is not to have Jupyter
      out of the box.
      On the other hand for Wendelin SR, which inherits from ERP5 SR, the
      default is to have Jupyter out of the box, because Wendelin SR is fresh
      enough without lots of backward compatibility needs, and Jupyter is
      usually very handy for people who use Wendelin.
      For integration, we reuse already established in ERP5 infrastructure, to
      request various slave instances, and request Jupyter in a way so it
      automatically tunes and connects to balancer of one of Zope family.
      Jupyter code itself is compiled by reusing
      software/ipython_notebook/software.cfg, and Jupyter instance code is
      reused by hooking software/ipython_notebook/instance.cfg.in into ERP5 SR
      properly (the idea to override instance-jupyter not to render into
      default template.cfg is taken from previous work by @tiwariayush).
      I tested this patch inside webrunner with create-erp5-site software type and
      various configurations (whether to have or not have jupyter, to which zope
      family to connect it, etc).
      I have not tested frontend instantiation fully - because tests were done only
      in webrunner, but I've tried to make sure generated buildout code is valid for
      cases with frontend.
      NOTE the code in this patch depends erp5_data_notebook bt5 (erp5!29) which just got merged to erp5.git recently (see erp5@f662b5a2)
      NOTE even when erp5_data_notebook bt5 is installed, on a freshly installed ERP5, it
      is required to "check site consistency" first, so that initial bt5(s) are
      actually installed and erp5 is ready to function.
      /cc @vpelletier, @Tyagov, @klaus, @Camata, @tiwariayush, @Kreisel, @jerome, @nexedi
      /proposed-for-review-on !43
  12. 21 Dec, 2015 1 commit
  13. 18 Dec, 2015 1 commit
    • Ayush Tiwari's avatar
      Jupyter: Hook ERP5 Kernel · 33954c66
      Ayush Tiwari authored
      ERP5 kernel basic info/workflow:
      1. User enters code on notebook cell and executes
      2. Code is sent to kernel via websockets
      3. Kernel sends request to ERP5
      4. Code is executed by ERP5 and the result is returned back via request.
      5. Result is received and rendered on the notebook frontend.
      6. Other message formats such as error and status are also conveyed by the Kernel.
      [ kirr: in IPython notebook speak kernel is something that allows IPython
        notebook server side to talk to execution backend. ERP5 kernel is a thing that
        allows ipython notbook to talk to ERP5 (with help on-ERP5-server special bt5
        installed which accepts and executes commands).
        The bt5 to handle notebook calls on ERP5 side - erp5-data-notebook - is
        proposed to be merged into erp5.git on erp5!29 ]
      /initially-reviewed-by @kirr, @Tyagov  (in a lot of places, last time on !33)