Details
-
Type:
Bug
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: Firefly
-
Labels:None
-
Story Points:2
-
Epic Link:
-
Sprint:SUIT Sprint 2019-02
-
Team:Science User Interface
Description
The server extension for the Jupyterlab Firefly extension has not been working in the science platform since the d_2019_01_30 daily. This manifests as a failure to connect to the Firefly server. The environment variables set by the server side of the extension, like fireflyLabExtension, fireflyURLLab, and fireflyChannelLab are undefined.
The quickest way to test the connection in Jupyterlab is to open the Command Palette, find the Firefly section and then Open Firefly. The tab that opens should show a large "Firefly Ready" with the Firefly toolbars. When the server extension does not work, the tab is all white with a small "Firefly Loading" message at the top.
The build environment changed to use Python and pip, from SCL (Software Collections) to EPEL (Extra Packages for Enterprise Linux).
The initial fix we will make in this ticket is to remove a pip install from the packages.json file, and to change the version to 0.2.2.
Attachments
Issue Links
- links to
Activity
Reviewed on the linked Github PR.
David Shupe
added a comment - Reviewed on the linked Github PR. The updated package has been published to npm as version 0.2.2. The server extension side has been published to PyPI as version 0.2.2. I have tested that these install and run successfully into a standalone Docker container for the stack, for weekly w_2019_06.
David Shupe
added a comment - The updated package has been published to npm as version 0.2.2. The server extension side has been published to PyPI as version 0.2.2. I have tested that these install and run successfully into a standalone Docker container for the stack, for weekly w_2019_06 . 
Small changes, should be a fast review.