If Tsp-Client can't clone, the error message is complex to read. #13413
Description
From the Python repo, in azure-purview-datamap, with the following tsp location:
directory: specification/purview/data-plane/datamap
commit: bdb83beae5c03e21a9778c5ba746f1f762831efb
repo: Azure/azure-rest-api-specs
additionalDirectories:
The commit has been written by Copilot, so I guess it messed up something, I didn't check exactly, but it seems it has trouble to clone, and we get this:
Failed to regenerate TypeSpec client, see generator output below
Using output directory '/home/lmazuel/git/azure-sdk-for-python/sdk/purview/azure-purview-datamap'
888 888 d8b 888
888 888 Y8P 888
888 888 888
888888 .d8888b 88888b. .d8888b 888 888 .d88b. 88888b. 888888
888 88K 888 "88b d88P" 888 888 d8P Y8b 888 "88b 888
888 "Y8888b. 888 888 888888 888 888 888 88888888 888 888 888
Y88b. X88 888 d88P Y88b. 888 888 Y8b. 888 888 Y88b.
"Y888 88888P' 88888P" "Y8888P 888 888 "Y8888 888 888 "Y888
888
888
888
0.31.0
update
Sync and generate from a TypeSpec project
Options:
-d, --debug Enable debug logging [boolean]
-o, --output-dir Specify an alternate output directory for the generated
files. [string] [default: "."]
-y, --no-prompt Skip any interactive prompts. [boolean]
--help Show help [boolean]
--repo Repository where the project is defined [string]
--commit Commit hash to be used [string]
--tsp-config Path to tspconfig.yaml [string]
--local-spec-repo Path to local spec repo [string]
--emitter-options The options to pass to the emitter [string]
--save-inputs Don't clean up the temp directory after generation
[boolean]
--skip-install Skip installing dependencies [boolean]
--trace Enable tracing during compile [array]
-v, --version Show version number [boolean]
Error: ENOENT: no such file or directory, lstat '/home/lmazuel/git/azure-sdk-for-python/../sparse-specf4a94e84-47cc-4352-8115-c0ffcc931486/specification/purview/data-plane/datamap'
at async lstat (node:internal/fs/promises:1030:18)
at async Promise.all (index 0)
at async checkPaths (node:internal/fs/cp/cp:76:39)
at async cpFn (node:internal/fs/cp/cp:65:17)
at async syncCommand (file:///home/lmazuel/.npm/_npx/6d3fef9cb048a1df/node_modules/@azure-tools/typespec-client-generator-cli/dist/commands.js:282:9)
at async updateCommand (file:///home/lmazuel/.npm/_npx/6d3fef9cb048a1df/node_modules/@azure-tools/typespec-client-generator-cli/dist/commands.js:465:5)
at async Object.handler (file:///home/lmazuel/.npm/_npx/6d3fef9cb048a1df/node_modules/@azure-tools/typespec-client-generator-cli/dist/index.js:187:5) {
errno: -2,
code: 'ENOENT',
syscall: 'lstat',
path: '/home/lmazuel/git/azure-sdk-for-python/../sparse-specf4a94e84-47cc-4352-8115-c0ffcc931486/specification/purview/data-plane/datamap'
}
That's not super clean what happened, we should try to make it easier to read.