-
Notifications
You must be signed in to change notification settings - Fork 5.1k
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.
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
[Hub Generated] Review request for Microsoft.Subscription: Removed an unused API to make things simple, also corrected examples #7540
Conversation
In Testing, Please Ignore[Logs] (Generated from 3773562, Iteration 4).NET: test-repo-billy/azure-sdk-for-net [Logs] [Diff]
Go: test-repo-billy/azure-sdk-for-go [Logs] [Diff]
Python: test-repo-billy/azure-sdk-for-python [Logs] [Diff]
JavaScript: test-repo-billy/azure-sdk-for-js [Logs] [Diff]
|
Automation for azure-sdk-for-pythonEncountered a Subprocess error: (azure-sdk-for-python)
Command: ['/usr/local/bin/autorest', '/tmp/tmplg_7b9cz/rest/specification/subscription/resource-manager/readme.md', '--perform-load=false', '--swagger-to-sdk', '--output-artifact=configuration.json', '--input-file=foo', '--output-folder=/tmp/tmp0xonvvez'] AutoRest code generation utility [version: 2.0.4283; node: v8.12.0]
(C) 2018 Microsoft Corporation.
https://aka.ms/autorest
Failure:
Error: Unable to start AutoRest Core from /root/.autorest/@microsoft.azure_autorest-core@2.0.4405/node_modules/@microsoft.azure/autorest-core
Error: Unable to start AutoRest Core from /root/.autorest/@microsoft.azure_autorest-core@2.0.4405/node_modules/@microsoft.azure/autorest-core
at main (/opt/node_modules/autorest/dist/app.js:232:19)
at <anonymous>
/root/.autorest/@microsoft.azure_autorest-core@2.0.4405/node_modules/@microsoft.azure/autorest-core/dist/app.js:33
autorest_core_1.Shutdown();
^
ReferenceError: autorest_core_1 is not defined
at process.on (/root/.autorest/@microsoft.azure_autorest-core@2.0.4405/node_modules/@microsoft.azure/autorest-core/dist/app.js:33:5)
at emitOne (events.js:121:20)
at process.emit (events.js:211:7)
at process.emit (/node_modules/source-map-support/source-map-support.js:439:21)
fs.js:612
return binding.close(fd);
^
Error: EBADF: bad file descriptor, close
at Object.fs.closeSync (fs.js:612:18)
at StaticVolumeFile.shutdown (/opt/node_modules/autorest/dist/static-loader.js:352:10)
at StaticFilesystem.shutdown (/opt/node_modules/autorest/dist/static-loader.js:406:17)
at process.exit.n [as exit] (/opt/node_modules/autorest/dist/static-loader.js:169:11)
at printErrorAndExit (/node_modules/source-map-support/source-map-support.js:423:11)
at process.emit (/node_modules/source-map-support/source-map-support.js:435:16)
at process._fatalException (bootstrap_node.js:391:26) |
Automation for azure-sdk-for-goNothing to generate for azure-sdk-for-go |
We have introduced the removed API as part of PR #7352 (around week back). |
Can one of the admins verify this patch? |
...anager/Microsoft.Subscription/preview/2018-11-01-preview/examples/createCspSubscription.json
Outdated
Show resolved
Hide resolved
...iption/resource-manager/Microsoft.Subscription/preview/2018-11-01-preview/subscriptions.json
Outdated
Show resolved
Hide resolved
...iption/resource-manager/Microsoft.Subscription/preview/2018-11-01-preview/subscriptions.json
Outdated
Show resolved
Hide resolved
"public.rest-api-specs In progress — This check has started..." > running for last 5.5 hours. |
Making minor change to rerun the checks as public.rest-api-specs check is reporting as running for more than a day when it has actually got completed.
@xccc-msft can you please review and merge the PR. |
@arm review team - can one of you please review the changes? |
@sriramvu I dropped message with this PR to ARM reviewers. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No actual API changes in this PR
@xccc-msft - can you please merge the changes. |
If you are a MSFT employee you can view your work branch via this link.
Contribution checklist: