Skip to content

Improve troubleshooting when updating the python emitter version in emitter-package.json #46964

@catalinaperalta

Description

@catalinaperalta

I recently encountered an issue where I was attempting to update the python emitter version in eng/emitter-package.json, however due to black not being cached in the CFS feed yet I kept getting 401 unauthorized errors during emitter installation. It was unclear what was happening behind the scenes to make this installation fail since I've never encountered this error before or needed to authenticate to install the python emitter dependencies (even the ones through pip). Eventually with @scbedd's help we found that these docs show the process to mitigate this error: https://github.com/Azure/azure-sdk-for-python/blob/main/CONTRIBUTING.md#authentication-for-upstream-pull-through

The ask is that we ensure this information and process is clear and easy for cases when folks have to update the python emitter version locally, for example a service partner might need to roll back or fast forward their python emitter version due to compatibility issues with their typespec and will need to find these docs in order to do so.

Another idea is to potentially update the error message to point to the right docs whenever this happens.

cc @danieljurek @JennyPng @LibbaLawrence

Metadata

Metadata

Assignees

Labels

needs-triageWorkflow: This is a new issue that needs to be triaged to the appropriate team.

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions