Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update FAQ #345

Merged
merged 1 commit into from
Apr 8, 2024
Merged

Update FAQ #345

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file added docs/assets/images/none_type_not_callable.png
View file
Open in desktop
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
6 changes: 6 additions & 0 deletions docs/pages/faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,3 +34,9 @@ The definition of [200/201 Responses](https://github.com/Azure/azure-rest-api-sp
## Why my codegen V2 generated cmds' help message not inherited from my "summary" message from its swagger file?

Codegen v2 uses "description" of swagger definition for cmd's 'help' message, not 'summary'

## Long running operation(LRO) command execute failed with error: 'None' type object is not callable.

!['None' type object is not callable](../assets/images/none_type_not_callable.png)

This issue is caused by the miss match between Swagger(OpenAPI Spec) definition and LRO behavior. It seems the final response body from LRO is not empty, but the `x-ms-long-running-operation-options.final-state-schema` field in swagger is not defined. You can reference this swagger doc https://github.com/Azure/autorest/tree/main/docs/extensions#x-ms-long-running-operation-options For details. BTW, when you run the cli command, you can add `--debug` argument to display the request logs.
Loading