Skip to content

Conversation

@vanbasten23
Copy link
Contributor

@vanbasten23 vanbasten23 commented Jun 1, 2018

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.

PR information

  • The title of the PR is clear and informative.
  • There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
  • Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
  • If applicable, the PR references the bug/issue that it fixes.
  • Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

vanbasten2323 and others added 30 commits May 15, 2018 14:08
@AutorestCI
Copy link

AutorestCI commented Jun 1, 2018

Automation for azure-sdk-for-go

Nothing to generate for azure-sdk-for-go

@lmazuel
Copy link
Member

lmazuel commented Jun 4, 2018

@AutorestCI regenerate azure-sdk-for-python

"description": "Error response describing why the operation failed.",
"schema": {
"$ref": "#/definitions/CloudError"
"$ref": "#/definitions/ApiError"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is the change that breaks existing Python SDK clients (including CLI )with unhandled exceptions
//CC: @lmazuel @johanste

@sarangan12 sarangan12 removed their assignment Jun 8, 2018
@sarangan12
Copy link
Contributor

@vanbasten23 Are you part of Compute service team?

@vanbasten23
Copy link
Contributor Author

@sarangan12 Yes, I am part of Compute service team.

description: Compute Client
openapi-type: arm
tag: package-2018-04-01
tag: package-2018-06-01
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you update this default tag to include gallery, it is very difficult to change later. If gallery is still preview, do not update default tag.

@sarangan12
Copy link
Contributor

@hyonholee Please resolve the conflicts

@AutorestCI
Copy link

AutorestCI commented Jun 19, 2018

Automation for azure-sdk-for-java

Encountered an unknown error: (azure-sdk-for-java)

Traceback (most recent call last):
  File "/usr/local/lib/python3.6/dist-packages/swaggertosdk/github_tools.py", line 32, in exception_to_github
    yield context
  File "/usr/local/lib/python3.6/dist-packages/swaggertosdk/restapi/github.py", line 167, in rest_handle_action
    return rest_pull_close(body, restapi_repo, sdk_pr_target_repo, sdkbase, sdk_tag)
  File "/usr/local/lib/python3.6/dist-packages/swaggertosdk/restapi/github.py", line 182, in rest_pull_close
    rest_pr_management(rest_pr, sdk_pr_target_repo, sdk_tag, sdk_default_base)
  File "/usr/local/lib/python3.6/dist-packages/swaggertosdk/restapi/github_handler.py", line 151, in rest_pr_management
    sdk_tag=sdk_tag
  File "/usr/local/lib/python3.6/dist-packages/swaggertosdk/SwaggerToSdkNewCLI.py", line 237, in generate_sdk_from_git_object
    raise ValueError("Unable to locate configuration in {}".format(branch_list))
ValueError: Unable to locate configuration in ['restapi_auto_compute/resource-manager', 'restapi_auto_3175', 'master']

@hyonholee
Copy link
Contributor

LGTM, Thanks.

@sarangan12 sarangan12 merged commit c242706 into Azure:master Jun 19, 2018
@lmazuel
Copy link
Member

lmazuel commented Jul 6, 2018

@AutorestCI regenerate azure-sdk-for-python

weidongxu-microsoft pushed a commit to weidongxu-microsoft/azure-rest-api-specs that referenced this pull request Jan 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants