TypeError: extension.updatePythonPath is not a function after CLI version 3.6.2 was made available. #4599
Comments
bryan-strassner
changed the title
|
Guessing this is an issue with the dependency not being pinned. |
|
Yes- have tried pinning to 5.19.0. It fails with a different problem. In fact, other versions > 5.4.0 gets this error. I've also tried 5.5.0, 6.1.1: See log attached: |
|
can you remove |
|
This indeed succeeds in running but doesn't change that there was a behavior change... back to the drawing board I suppose. The goal here is to preinstall modules, such that we can use autorest to: Seems quite the maze of dependencies and not a real clear way to achieve all in the same environment. (what we had before worked until 2 days ago... but maybe we're doing it wrong !!!) Any thoughts or guidance on a path? |
|
Agree with you that autorest dependency is a mess, the ability to get download on the fly make you loose the ability to have locked dependencies which cause those issues where things randomly start failing due to a dep of a dep getting updated. For the If you want to preload things you can always them one by one and all the various different version should get installed and be ready for next use. Which command was working well 2 days ago, the 1st one on the issue? Did you have the packages cached on your machine by chance? |
|
Yes, the first command on the issue is what changed behavior in our pipelines. Yes, the local worked due to cached resources. I agree that the dep-of-a-dep, and ">" ranged dependency specifications are exactly what bit us. Good to know on the As a temporary work-around, we bundled up one developer's cached dependencies as an archive and unarchive it in the pipeline. This is obviously not ideal, but it unblocked us for the time being. |
|
I have been facing similar issues with python version:5.4.0, core: 3.7.6 and cli: 3.6.2 -------------------------------------------- Logs: ----------------------------------------------------- |
|
Our team is seeing this as well when trying to create an az cli sdk: > autorest --az .\readme.md
AutoRest code generation utility [cli version: 3.6.2; node: v18.4.0]
(C) 2018 Microsoft Corporation.
https://aka.ms/autorest
info | Loading AutoRest core 'C:\Users\bfjelds\.autorest\@[email protected]\nodemodules\@autorest\core\dist' (3.9.0)
info | Loading AutoRest extension '@autorest/az' (latest->1.8.0)
info | Loading AutoRest extension '@autorest/python' (5.4.0->5.4.0)
info | Loading AutoRest extension '@autorest/clicommon' (0.6.2->0.6.2)
info | Loading AutoRest extension '@autorest/modelerfour' (4.15.421->4.15.421)
TypeError: extension.updatePythonPath is not a function
fatal | Process() cancelled due to failure
error | [Exception] AutoRest extension '@autorest/python' terminated.
error | Error: [Exception] AutoRest extension '@autorest/python' terminated.
error | Autorest completed with an error. If you think the error message is unclear, or is a bug, please declare an issues at https://github.com/Azure/autorest/issues with the error message you are seeing.Any help in understanding how we can workaround this would be super appreciated! |
|
You can find the particular issue with using |
Before filling a bug
Until the 3.6.2 version of the cli was made available, the following command worked for us to setup/install autorest dependencies in a CI pipeline:
Coinciding with the 3.6.2 message showing up:
Prior to this version advertisement, the pipelines were able to successfully acquire the modules and produce the help messages. Even without moving to the new 3.6.2 version (still running 3.6.1), we now receive the following exception:
I was able to reproduce this locally (as you can see from the paths in the snips above), by doing:
Expected behavior
The expectation is that the help command output is produced without exception.
Additional context
autorest3.6.2exception.log
autorest3.6.1success.log
The text was updated successfully, but these errors were encountered: