-
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
Uncaught null
in Chrome Inspector
#6270
Comments
This does not work if I just I won't be surprised if this is related to #6258. |
Confirmed can still reproduce as of today. Just small modifications to the repro code needed to update to changes:
|
I am getting following error when I try to execute the snippet:
I am using |
Right, I somehow pasted the wrong (old) snippet, I don't know how I mixed them up. Updated with up-to-date snippet ( |
Yesterday I was able to reproduce the problem. Today I upgraded to 59329bd and it seems to be working fine: Given there are just three fixes in between $ git log 2023.2.1-nightly.2023.8.8...59329bd59aeacc4f60ccc4ef323dfaf6629c7710
commit 59329bd59aeacc4f60ccc4ef323dfaf6629c7710 (HEAD -> develop, origin/develop, origin/HEAD)
New Top Bar
commit b656b336c7d239ef95a548f87deb5af2f4801368
Author: Radosław Waśko <[email protected]>
Report `Loss_Of_Integer_Precision` when an integer is not exactly representable as a float during conversion
commit 05e8aade1f5586f011b4943ba9fb4fa221405a56
Author: Jaroslav Tulach <[email protected]>
Date: Tue Aug 8 11:18:38 2023 +0200
Exclusive context policy ensures EnsoContext.get returns compilation constant (#7493) and most of #7493 actually focuses on fixing |
Awesome 🎉 and thanks for checking! |
Jaroslav Tulach reports a new STANDUP for yesterday (2023-08-09): Progress: - Fixed NPE while debugging: #6270
Next Day: Python interop & bugfixes
|
I was able to get an error in the Chrome Inspector REPL when debugging an Enso script.
The repro is following:
Run the following script (I called it
too-many-warnings.enso
) with the--inspect
option:Set a breakpoint at line
10
:t2.print
and run up to this line.When in this line, observe the following interaction in the REPL:
The text was updated successfully, but these errors were encountered: