-
Notifications
You must be signed in to change notification settings - Fork 54
Stuck on "... building dashboard ..." and 404 GET /voila/templates/flex/static/jupyter-flex-embed.js #169
Comments
Similar problem here, with both But for me the browser is first stuck on a page with "Opening Voila-Flex | This page should redirect you to your app. If it doesn't, click here.". At this point I already have a Then if I click on "click here", I get following similar errors: Also, I don't have any of the 2 missing files at expected location (
Traceback:
Environment:
|
Hello! Don't know if you still have this problem; it appears that jupyter-flex, ipywidgets and voila have several dependency problems in new versions. The only way I managed to make things work is using these versions of the libraries:
|
It indeed works for me with this, but I also had to use the following
|
For readers of this thread, note there was a security fix to voila, do not use |
Indeed, I encountered a GitHub warning while working with |
@benoitfrisque I've just deployed last night a web app with an upgraded environment voila 0.2.17, and it works fine, so far as I tested interactively. I could operate ipywidget based actions to check my changes. An environment with the following versions (not quite my prod, but my local dev), includes:
|
Thanks @jmp75 , but I get |
No idea why you get this behavior. I don't know how jinja detects templates provided by other packages. I've had a quick search over the jinja codebase, https://github.com/search?q=repo%3Apallets%2Fjinja%20TemplateNotFound&type=code but this is beyond my know-how. If I were to encounter this kind of issue I personally may try to run in debug mode to glean more info, but only if I ran out of options to try (like, re-create a conda environment from scratch after messing it up over time). I'd really resort to interactive debug session as a last resort, this is often a rabbit hole. In case it helps, I have the following VSCode debug configs to handle debugging voila apps, including third party packages via the 'justMyCode' key:
{
"version": "0.2.0",
"configurations": [
{
"name": "Python: Attach using Process Id",
"type": "python",
"request": "attach",
"processId": "${command:pickProcess}",
"justMyCode": false
}
]
} If I need to catch things at process startup immediately {
"version": "0.2.0",
"configurations": [
{
"name": "jupyter-flex",
"type": "python",
"request": "launch",
"program": "/home/xxxxxx/.venvs/my_env/bin/jupyter-flex",
"cwd": "/home/xxxxxx/src/biomass/notebooks",
"args": ["MyDashboard.ipynb", "--VoilaConfiguration.file_whitelist", "\"['.*.json', '.*my_dashboard.css']\"", "--enable_nbextensions=True"],
"console": "integratedTerminal",
"justMyCode": false
}
]
} |
I am trying to upgrade an environment to use the latest versions of
jupyter-flex
and dependencies. I cannot get the dashboard to display.Repro
Conda environment created using
mambaforge
include:Starting my app with:
voila \ --template=flex \ --no-browser \ --VoilaConfiguration.file_allowlist ".*" \ --MappingKernelManager.cull_interval=60 \ --MappingKernelManager.cull_idle_timeout=900 \ Biomass.ipynb
Observation
kernel starts and visibly notebook cells are being run. The format is looking "raw" however
Then it remains stuck on:
the command line reports:
dong a disk search it appears indeed that
jupyter-flex-embed.js
is not under my new conda environment, but is present in my previous environment "my_prod_environment/" which was using jupyter-flex 0.7.x:The text was updated successfully, but these errors were encountered: