-
Notifications
You must be signed in to change notification settings - Fork 323
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't open custom entry point from the list of available ones #6438
Comments
Can reproduce this on a Linux machine. But this only seems to occur in the Electron app. When doing the same in a browser, it seems to work without issue. |
the error line info indicates the bug happens here ( enso/app/ide-desktop/lib/client/src/security.ts Lines 78 to 88 in ae94a9f
not 100% sure what specifically causes the bug, since |
so it seems like |
oh, maybe |
not sure if there's a way to figure out the
note for whoever wants to tackle this, the URLs will need to be updated (heading number incremented) so might as well do that at the same time:
|
the same cause is also affecting the dashboard: cloud-v2#413 |
@vitvakatu you may want to QA this PR #6507 which should fix the problem and we can merge it |
Discord username
No response
What type of issue is this?
Permanent – Occurring repeatably
Is this issue blocking you from using Enso?
Is this a regression?
What issue are you facing?
When running IDE with a non-existing
startup.entry
(like_
orfoo
), I see the list of available entry points.After clicking on some of the entries, I see an error message like in #5786
However, this time IDE crashes.
Logs:
Opening an entry point directly with
-startup.entry=interface
works fine for any entry point.Expected behaviour
I should be able to open an entry point.
How we can reproduce it?
No response
Screenshots or screencasts
No response
Enso Version
dcfbf84
Browser or standalone distribution
Standalone distribution
Browser Version or standalone distribution
dcfbf84
Operating System
MacOS
Operating System Version
MacOS Ventura 13.3.1 (22E261)
Hardware you are using
No response
The text was updated successfully, but these errors were encountered: