-
Notifications
You must be signed in to change notification settings - Fork 282
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
[BUG] More broken fix faulty tests #4884
Comments
Hi @Felienne! No worries!! I will take a look at the broken tests tonight. |
Thanks!! |
Hi @ToniSkulj I suspect that #4887 fixes this too, but I did not have time to check! So before you dive in and spend time, you might want to explore that haha |
mergify bot
pushed a commit
that referenced
this issue
Dec 13, 2023
Fixes #2394 (finally!!) by checking if declared variables are actually used, also fixes #4884 that was introduced here. Depends-On: #4880 **How to test** I have added a test for the exception. To see it in action on the front-end, run code that defines but not uses a variable, and observe you get a warning but the code still runs: <img width="1382" alt="image" src="https://github.com/hedyorg/hedy/assets/1003685/bb00c145-8d81-4e86-8ea1-316b0ae955c6"> Note that this PR needs #4880 to show the warning in the front-end!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi @ToniSkulj!
I am afraid I am wrecking more havoc on your tests, sorry! See: #4881
I commented out the broken tests for now. Could you take a look 🙏?
(I suspect that #4879 too might have something to do with the skip faulty code, I took a look at what is going wrong but it does seem to raise the right exception, it looks like it is just caught somewhere in your code)
The text was updated successfully, but these errors were encountered: