Autorest failure with Node 14.15.0
See original GitHub issueI’m seeing the following error in my build pipeline in Azure Devops…
========================== Starting Command Output ===========================
/bin/bash --noprofile --norc /home/vsts/work/_temp/670d10df-438b-4166-90e4-649f59e656dd.sh
AutoRest code generation utility [cli version: 3.0.6247; node: v14.15.0, max-memory: 2048 gb]
(C) 2018 Microsoft Corporation.
https://aka.ms/autorest
NOTE: AutoRest core version selected from configuration: ~2.0.4413.
Loading AutoRest core '/home/vsts/.autorest/@microsoft.azure_autorest-core@2.0.4417/node_modules/@microsoft.azure/autorest-core/dist' (2.0.4417)
Loading AutoRest extension '@microsoft.azure/autorest.python' (~3.0.56->3.0.62)
Loading AutoRest extension '@microsoft.azure/autorest.modeler' (2.3.44->2.3.44)
TypeError [ERR_INVALID_ARG_TYPE]: The "data" argument must be of type string or an instance of Buffer, TypedArray, or DataView. Received null
OS: ubuntu-latest image AutoRest CLI: 3.0.6247 node: 14.15.0
I think the issue is some weird combination between ubuntu and node as I’m not able to replicate this on my local windows machine. But my actual question how does Autorest choose the version of node to run against? Can we specify the node version on the command line? In my pipeline I am overriding the node version back to 12.19.0 (this version worked as of a few weeks ago), but autorest is still running against 14.15.0 (node -v is showing 12.19.0 in my pipeline)
This very well could be an azure pipelines issue, but I thought I would start here first for any suggestions.
Issue Analytics
- State:
- Created 3 years ago
- Comments:12 (7 by maintainers)
Top Results From Across the Web
autorest - npm
The AutoRest tool generates client libraries for accessing RESTful web services. Input to AutoRest is a spec that describes the REST API using ......
Read more >Netlify says, "error Gatsby requires Node.js 14.15.0 or higher ...
The problem is that you have Node 17.2.0. locally but in Netlify's environment, you are running a lower version (by default it's not...
Read more >typeerror [err_invalid_arg_type]: the "data" argument must be ...
Receiving a error trying to list the table of database postgres TypeError [ERR_INVALID_ARG_TYPE] ... Azure/autorestAutorest failure with Node 14.15.0#3706.
Read more >AutoRest Versioning
Supports C#, PowerShell, Go, Java, Node.js, TypeScript, Python. ... The AutoRest CLI is updated like any Node package, via NPM: npm install -g...
Read more >node - Official Image | Docker Hub
Node.js is a JavaScript-based platform for server-side and networking ... the Docker Community Slack, Server Fault, Unix & Linux, or Stack Overflow ...
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
Don’t seem to encounter this issue with node 14. Might have been an issue at the time. I’ll close this, please reopen if you reencounter the problem.
Can you double check this is not happening with the latest version of
2.0.x
: (2.0.4421
). Think this might be due to a change on node 14 when writting file not accepting null which was fixed in v2