-
-
Notifications
You must be signed in to change notification settings - Fork 52
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
Invalid arity error while using cljs.test/are with large number of args #187
Comments
Could be related to: clojure/clojurescript@8b3ce24 ? |
@logseq-cldwalker I had a similar issue here: |
Yep, it looks related to that. I hope CLJS can be bumped soon, then I can also get rid of the workarounds in the before mentioned issue. |
Good find with clojure/clojurescript#167. The are
tests are passing with clojurescript 1.10.891. I'm guessing clojurescript
interprets `are` in a way that doesn't invoke this bug
…On Tue, 10 May 2022 at 13:36, Michiel Borkent ***@***.***> wrote:
Yep, it looks related to that. I hope CLJS can be bumped soon, then I can
also get rid of the workarounds in the before mentioned issue.
—
Reply to this email directly, view it on GitHub
<#187 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AXFVC57KGGIIHNWPBPTEVCDVJKNC7ANCNFSM5VSEFZBA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Happy to wait for the cljs fix. I see they haven't released anything since
christmas so hopefully the flurry of activity is prepping for a new release
soon 🙏
…On Tue, 10 May 2022 at 13:40, Gabriel Horner ***@***.***> wrote:
Good find with clojure/clojurescript#167. The are
tests are passing with clojurescript 1.10.891. I'm guessing clojurescript
interprets `are` in a way that doesn't invoke this bug
On Tue, 10 May 2022 at 13:36, Michiel Borkent ***@***.***>
wrote:
> Yep, it looks related to that. I hope CLJS can be bumped soon, then I can
> also get rid of the workarounds in the before mentioned issue.
>
> —
> Reply to this email directly, view it on GitHub
> <#187 (comment)>, or
> unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AXFVC57KGGIIHNWPBPTEVCDVJKNC7ANCNFSM5VSEFZBA>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
|
Unfortunately with the newest CLJS it didn't work:
|
I'll take a deeper look tomorrow. |
Smallest repro possible:
|
Got a pure CLJS repro and posted it in the cljs-dev channel:
|
Fixed using a workaround. |
Thanks for finding the root cause and a workaround! ❤️ |
Confirmed this fix worked for the original test file with latest nbb-logseq. Thanks again! |
Hi @borkdude. Encountered this curious error while trying to run some logseq tests under nbb. Any ideas what's going? I got a minimal repro
version
Latest, 0.3.97
platform
osx with node 16.13.1
problem
I'm trying to convert these tests to run under nbb. I encountered an arbitrary limit of args to
are
that stops working - 22repro
In example_runner.cljs
Run tests to see failure:
Comment out one of the are arg lines and see the test pass
expected behavior
I expected these tests to pass like they do in cljs
The text was updated successfully, but these errors were encountered: