-
Notifications
You must be signed in to change notification settings - Fork 13
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
Error: TypeError: Cannot read property '0' of null #7
Comments
hey @jonathanstiansen which Elixir version are you using? Is it an umbrella project? could you run The output will look more or less like this:
Are there any cases where this part It's okay if there are cases without a "list". Like this one:
The other way to debug it would be to find which file(s) is causing this. Unfortunately, I don't have any other idea how to deal with this, sorry. |
Same problem here. I did try to run
|
I have this problem too. It's a large (1665 tests) umbrella app. In my case every test has Versions:
|
@thecristen could you show an example of the output? You can change test/file names, I'm curious about the format. |
@adamzapasnik sure! attempt at a representative excerpt:
One thing I'm realizing is we have a few compiler warnings, but I think those technically happen right before executing the test listing command. (edited to remove link to output text) |
@thecristen thanks, you can remove the outputs 🙇 https://github.com/elixir-lang/elixir/blob/v1.11/CHANGELOG.md#exunit-1
Line and file information was added in Elixir v1.11, so this extension won't work with 1.10 :( I'll add this information to readme. |
Hey folks,
![image](https://user-images.githubusercontent.com/2357736/120828632-fa5a2c80-c519-11eb-9030-b42a1de2970b.png)
All I see in the test explorer is this:
and the "output" when I click on that is this:
Error: TypeError: Cannot read property '0' of null
let me know what kind of config I can give you to help debug - I don't even know where to start other than the output.
mix test works just fine in the terminal 🤷🏽
The text was updated successfully, but these errors were encountered: