Select to view content in your preferred language

Notebooks finish execution but still appear to be executing

242
3
04-30-2025 08:30 AM
Glasnoct
Regular Contributor

I've recently started getting odd behavior from my notebooks and I can't figure out what happened to cause it. Any cell I run, regardless of how simple or involved the code is, always displays "In [*]" regardless of whether it's done executing or not. The kernel says that it is idle and if I have the cell simply print "done" after it executes all other code, then it will do that but "In" never updates to a number like it used to.

Not that I ever use them, but magic commands don't seem to work either. The docs say I can use "%reset -f" but that just returns an exception complaining about the syntax.

I've tried changing the environment, trying it in a new project, and trying it with a new notebook but the behavior persists which is leading me to the belief something, somewhere, screwed up with the installation itself.

Has anyone else run into this behavior?

0 Kudos
3 Replies
Clubdebambos
MVP Regular Contributor

Hi @Glasnoct,

This happened to me the other day. It was a once off so far. I just refreshed the page it it went back to normal. I'll be sure to add here again if it repeats.

~ learn.finaldraftmapping.com
0 Kudos
David_McRitchie
Esri Regular Contributor

Hey Glasnoct,

That is a strange one. If you try opening this in a Jupyter Notebook and repeating do you get the same issue?

 

If so then might be worth raising a comment on more Jupyter specific forums. The following Stack Overflow post seems fairly similar and has some suggestions relating to the underlying packages.

 

Hope that helps,

David

Esri UK -Technical Support Analyst
0 Kudos
Glasnoct
Regular Contributor

No solution yet but it was a nice surprise to learn they run via a local server and that I can open and interact with the notebooks through my browser (I don't otherwise use jupyter notebooks outside of ArcPro).

I tried a couple of the suggested solutions but they didn't work. I'll have to try updating/deactivating/reactivating Conda and, as I'm still on 3.3, perhaps this will finally be a good excuse to update Arc to 3.4!

0 Kudos