Closed mafloh closed 2 years ago
Yes, I can reproduce this with the latest version. This is very weird, given that the exact same code is running in numerous other environments well. Very, very weird. I've never seen this sort of bug before. Will fix it asap.
The logs are in /var/log/hub for the systemwide hub and ~/.smc/logs/log for each project. They should be there.
OK, this should now be fixed. I didn't change any code, but just did a clean build and push of the Docker image. I think something must have been corrupted involving something that got installed during that Docker build.
Thanks for your help! I pulled the new Docker image and the issue pertains.
I realised I searched at the wrong place. Of course I have to go inside the docker first container with sudo docker exec -it cocalc bash
.
***
Thu, 26 Aug 2021 09:25:04 GMT body-parser deprecated bodyParser: use individual json/urlencoded middlewares at dist/servers/app/api.js:81:37
Thu, 26 Aug 2021 09:25:04 GMT body-parser deprecated undefined extended: provide extended option at node_modules/body-parser/index.js:105:29
Thu, 26 Aug 2021 09:25:04 GMT express-session deprecated undefined resave option; provide resave option at dist/auth.js:454:66
Thu, 26 Aug 2021 09:25:04 GMT express-session deprecated undefined saveUninitialized option; provide saveUninitialized option at dist/auth.js:454:66
Warning: connect.session() MemoryStore is not
designed for a production environment, as it will leak
memory, and will not scale past a single process.
origin="https://something.domain.org" is not allowed
origin="https://something.domain.org" is not allowed
Thanks for your help! I pulled the new Docker image and the issue pertains.
As a triple check that you're running the new version, can you type "sage --version" in a terminal and show me the output?
"sage --version" returns:
SageMath version 9.3, Release Date: 2021-05-09
Thanks. Unfortunately, I'm now definitely 100% stumped by your problem. I'll reopen this issue.
In the meantime, the best suggestion I have is that you try building the cocalc-docker image yourself from source.
Update: Workaround of Issue 5467 (Evaluate Cell again) does not help. Restarting Kernel works for Python 3 (SageMath)
and Python 3 (Ubuntu Linux)
but not for Python 3 (ipykernel)
.
I tested using Brave (Chromium 1.28.106 arm64), Firefox(91.0.2) and Chrome (Version 92.0.4515.159 (Offizieller Build) (arm64).
Interesting that restarting the kernel works. I'll hopefully fix https://github.com/sagemathinc/cocalc/issues/5467 soon; maybe that's actually responsible for the same problem. We'll see.
I've fixed https://github.com/sagemathinc/cocalc/issues/5467 and I really don't have any other ideas related to even reproducing this... so I'm closing it. If you do update to the new version of cocald-docker (from right now) and test this, let me know if it works.
I confirm the issue is solved. Thanks so much!
Bug Description
Cells process (showing a small arrow pointing to the left) but do not show [Out] with output, nor an error. It is a fresh install with Ubuntu 20.04 and nginx reverse proxy.
A few times it has worked, I could not reproduce. Sometimes the backend is spawning forever, sometimes it is ready. Same behaviour in both cases.
Classic Jupyter Notebook works like a charm.
Troubleshooting
/var/log/hub.log
and~/.smc/logs/log
do not exist (?)I can send the server address in a private message.