You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
TypeError: Cannot read property 'constructor' of null #160
I use parTraverse_ to run test cases in parallel and have the following error (undeterministically, sometimes it doesn't pop-up)
/project/ui-tests/output/Effect.Aff/foreign.js:83
throw error;
^
TypeError: Cannot read property 'constructor' of null
at Object.isLeft (/project/ui-tests/output/Effect.Aff/index.js:76:112)
at join (/project/ui-tests/output/Effect.Aff/foreign.js:720:16)
at /project/ui-tests/output/Effect.Aff/foreign.js:778:19
at /project/ui-tests/output/Effect.Aff/foreign.js:669:29
at runEff (/project/ui-tests/output/Effect.Aff/foreign.js:80:7)
at run (/project/ui-tests/output/Effect.Aff/foreign.js:496:15)
at /project/ui-tests/output/Effect.Aff/foreign.js:333:19
at drain (/project/ui-tests/output/Effect.Aff/foreign.js:120:9)
at Object.enqueue (/project/ui-tests/output/Effect.Aff/foreign.js:141:11)
at /project/ui-tests/output/Effect.Aff/foreign.js:330:27
Thanks for the bug report! Without any specific information or a reproduction, it's very unlikely it will get addressed directly. If it looks related to an existing closed issue, please make sure you are using the latest release.
Activity
natefaubion commentedon Aug 21, 2018
Thanks for the bug report! Without any specific information or a reproduction, it's very unlikely it will get addressed directly. If it looks related to an existing closed issue, please make sure you are using the latest release.
Unisay commentedon Aug 21, 2018
I am happy to provide information needed:
5.0.012.3.00.12.0Unfortunately I am not allowed to share the code needed to reproduce the problem, but here is an excerpt:
Unisay commentedon Aug 21, 2018
After changing
parTraverse_toforM_- the error is gone (as well as parallelism)natefaubion commentedon Aug 21, 2018
Have you tried upgrading to 5.0.1, which has the fix for the bug you referenced?