search

nteract / nteract

📘 The interactive computing suite for you! ✨
https://nteract.io
BSD 3-Clause "New" or "Revised" License
6.2k stars 551 forks source link

error when opening fresh installed nteract #5009

Open santo2 opened 4 years ago

santo2 commented 4 years ago

Application or Package Used nteract desktop for windows (Windows 10 Pro)

When opening nteract after installation, this message is being shown. image

I tried on 2 machines.

dboe1776 commented 4 years ago

I am encountering the same issue - Windows 10 Pro.

willingc commented 4 years ago

Thanks for the reports @santo2 @dboe1776.

This workaround reported in #4957 https://github.com/nteract/nteract/issues/4957#issue-571613160 may help until we release a proper fix.

@captainsafia Perhaps related to #5013 #4957

willingc commented 4 years ago

Regression may have been introduced here: applications/desktop/src/main/index.ts between 0.21 and 0.22

captainsafia commented 4 years ago

This issue has been reported prior to 0.21. I'm starting to suspect that it has something to do with the way the Python PATH attribute is added on Windows machines. I've seen this pop up a few times on my own Windows machine and it went away after mucking about with different installs.

This particularly stack trace is bubbling up from this line of code. We can resolve this issue by adding a try-catch handler around this particular being of code.

willingc commented 4 years ago

@captainsafia Ahh...that could be. We could ping Steve Dower if needed.

captainsafia commented 4 years ago

Something must be in the air because I've been running into a lot of interesting flaky issues lately.

Some research online also suggests that this might be a lower-level issue with filesystem APIs on Windows. Thankfully, I pushed a fix to jupyter-paths that adds a try-catch handler to this particular piece of code so that it no longer causes an exception.

A consequence of this might be that some Windows users don't see the correct list of runtimes but we'll have to play this fix bit by bit.

puetsch commented 4 years ago

Same error in 0.22.4 image

stale[bot] commented 2 years ago

This issue hasn't had any activity on it in the last 90 days. Unfortunately we don't get around to dealing with every issue that is opened. Instead of leaving issues open we're seeking to be transparent by closing issues that aren't being prioritized. If no other activity happens on this issue in one week, it will be closed. It's more than likely that just by me posting about this, the maintainers will take a closer look at these long forgotten issues to help evaluate what to do next. If you would like to see this issue get prioritized over others, there are multiple avenues 🗓:

Thank you!