An error occurred fetching the project authors.
- 08 Aug, 2017 1 commit
-
-
Ł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 cleanup. /reviewed-on nexedi/slapos!206
-
- 25 Jul, 2017 1 commit
-
-
Łukasz Nowak authored
-
- 21 Jun, 2017 1 commit
-
-
Iliya Manolov authored
@luke @Tyagov In Jupyter notebooks users could enter the url of their `Base_executeJupyter` function, but [it now gets filled in automatically](https://lab.nexedi.com/nexedi/slapos/blob/2f2a5ad0/software/ipython_notebook/template/ERP5kernel.py.jinja#L10). This makes the `%erp5_url` magic redundant which is why we can remove it. This commit also removes all mentions of `%erp5_url` in the kernel output and `custom.js`. /reviewed-on nexedi/slapos!185
-
- 12 Jun, 2017 1 commit
-
-
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](nexedi/erp5@4a3e5173) from my erp5 repo, so the changes there must be available for the kernel to work. [This merge request](nexedi/erp5!283) addresses those changes. Sample screenshot: ![Screenshot](/uploads/a34e0b70b991302539c572ad4344ba56/Screenshot.png) /reviewed-on nexedi/slapos!177
-
- 08 Jun, 2017 1 commit
-
-
Iliya Manolov authored
@Tyagov @kirr /reviewed-on nexedi/slapos!171
-
- 17 Mar, 2017 1 commit
-
-
Yusei Tahara authored
software/ipython_notebook: Update ERP5kernel.py.jinja, send store_history parameter to ERP5 so that we can use this flag to decide whether to add a data notebook line or not.
-
- 18 Feb, 2017 1 commit
-
-
Yusei Tahara authored
-
- 20 Jan, 2017 1 commit
-
-
Yusei Tahara authored
Jupyter: Add extra_data_list option to support display data similar to the original jupyter python backend.
-
- 21 Nov, 2016 1 commit
-
-
Ivan Tyagov authored
Tests passing here: https://nexedi.erp5.net/test_result_module/20161117-147BEEA9 /reviewed-on nexedi/slapos!118
-
- 18 Feb, 2016 1 commit
-
-
Ayush Tiwari authored
This fix is for bug https://nexedi.erp5.net/bug_module/20160212-76EAAC/view?ignore_layout:int=1 where the image base64 string was only shoeing. The error in this case was that the mime_type of content code_result was not being updated by the kernel before display. Reported by : @ivan
-
- 01 Feb, 2016 2 commits
-
-
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 nexedi/slapos!43)
-
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 (nexedi/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 (nexedi/erp5!29) which just got merged to erp5.git recently (see nexedi/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 nexedi/slapos!43
-
- 21 Dec, 2015 1 commit
-
-
Ayush Tiwari authored
Pin versions required for ipython==4.0.0 with ipykernel separated from ipython eggs. The split was in accordance to : https://blog.jupyter.org/2015/04/15/the-big-split/ /reviewed-by @kirr (on nexedi/slapos!33)
-
- 18 Dec, 2015 1 commit
-
-
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 nexedi/erp5!29 ] /initially-reviewed-by @kirr, @Tyagov (in a lot of places, last time on nexedi/slapos!33)
-