Cannot read property 'type' of null
See original GitHub issueFollowed all steps of the deployment process outlined in the default Github Actions yml. This step always ends in a null pointer exception, and since index.js
is so massive, it’s hard to debug anything. The error is also only as verbose as the title, no stacktrace, line numbers, anything.
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
TypeError: Cannot read property 'type' of null - Stack Overflow
I resolve it by installing the @angular/cdk 8.0.0 version. When I installed 8.2.3, as build would report error as Cannot read property 'type'...
Read more >Uncaught TypeError: Cannot read property of null - iDiallo
This error occurs when you read a property or call a method on a null object . That's because the DOM API returns...
Read more >Improve error message: TypeError: Cannot read property 'type ...
If library-b is installed that way, then ng build library-a fails with "Cannot read property 'type' of null" (only if components are listed...
Read more >TypeError: Cannot read property 'value' of Null in JS
To solve the "Cannot read property 'value' of null" error, make sure that the JS script tag is placed at the bottom of...
Read more >How to deal with TypeError: cannot read properties of null
While coding in Javascript, you must have at least once received a Type Error which has the message “cannot read properties of null”....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
There is not an API that will give you the task definition in the input format. This command will generate the skeleton to start off with:
aws ecs register-task-definition --generate-cli-skeleton > task-definition.json
Based on the logs above, it looks like you’re now able to register the task definition but ECS is not able to start your containers. For next steps, I would suggest looking at the service in the ECS console, going to Tasks -> Stopped to see why the containers are dying.
Yeah, please open a separate issue.
If you’re able to reproduce the initial issue, I have some additional debugging turned on in my fork that should give us a stacktrace: