[Hub Generated] Review request for Microsoft.Media to add version preview/2019-05-01-preview and stable/2018-07-01 #6147
Conversation
… to version 2019-05-01-preview
Only steaming service has new API.
Automation for azure-sdk-for-pythonThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-jsThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-javaEncountered a Subprocess error: (azure-sdk-for-java)
Command: ['/usr/local/bin/autorest', '/tmp/tmpajbnvp4t/rest/specification/mediaservices/resource-manager/readme.md', '--perform-load=false', '--swagger-to-sdk', '--output-artifact=configuration.json', '--input-file=foo', '--output-folder=/tmp/tmpofene7e6'] 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/@[email protected]/node_modules/@microsoft.azure/autorest-core
Error: Unable to start AutoRest Core from /root/.autorest/@[email protected]/node_modules/@microsoft.azure/autorest-core
at main (/opt/node_modules/autorest/dist/app.js:232:19)
at <anonymous>
/root/.autorest/@[email protected]/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/@[email protected]/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-rubyThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-goThe initial PR has been merged into your service PR: |
|
Will review the issues with the examples in subsequent PRs |
|
Can one of the admins verify this patch? |
|
Can't merge this due to the failing checks. |
SDK Automation [Logs] (Generated from 8e92338)
|
…https://github.com/BrianBlum/azure-rest-api-specs into dev-mediaservices-Microsoft.Media-2019-05-01-preview
|
@AutorestCI the failure in the first check is a exception thrown by the diff tool. Is there anything I can do to resolve that? |
|
I didn't understand your command: the failure in the first check is a exception thrown by the diff tool. Is there anything I can do to resolve that?in this context, sorry :(
|
5 similar comments
|
I didn't understand your command: the failure in the first check is a exception thrown by the diff tool. Is there anything I can do to resolve that?in this context, sorry :(
|
|
I didn't understand your command: the failure in the first check is a exception thrown by the diff tool. Is there anything I can do to resolve that?in this context, sorry :(
|
|
I didn't understand your command: the failure in the first check is a exception thrown by the diff tool. Is there anything I can do to resolve that?in this context, sorry :(
|
|
I didn't understand your command: the failure in the first check is a exception thrown by the diff tool. Is there anything I can do to resolve that?in this context, sorry :(
|
|
I didn't understand your command: the failure in the first check is a exception thrown by the diff tool. Is there anything I can do to resolve that?in this context, sorry :(
|
… rather than long max.
|
@tjprescott Any idea why files aren't being passed to autorest? |
|
@BrianBlum I'm not sure. I mentioned your PR in the Swagger reviewers channel to see if someone else has an idea. |
|
Thanks @tjprescott |
|
@AutorestCI generate azure-sdk-for-net |
|
I didn't understand your command: generate azure-sdk-for-netin this context, sorry :(
|
4 similar comments
|
I didn't understand your command: generate azure-sdk-for-netin this context, sorry :(
|
|
I didn't understand your command: generate azure-sdk-for-netin this context, sorry :(
|
|
I didn't understand your command: generate azure-sdk-for-netin this context, sorry :(
|
|
I didn't understand your command: generate azure-sdk-for-netin this context, sorry :(
|
|
@AutorestCI regenerate azure-sdk-for-net |
|
@tjprescott I found the bad package tag in the readme.md. And there was a typo in a description that was causing a failure in csharp generation. |
|
@tjprescott Thanks Travis. |
Specs commit Azure/azure-rest-api-specs#6147. Skip tests that use new version.
* Generated with --tag=package-2019-05-preview to get Live Transcript Specs commit Azure/azure-rest-api-specs#6147. Skip tests that use new version. * Update the parameters in generate to use LiveTranscription version * Add metadata files * Rerecord tests that use 2019-05-01-preview. Co-authored-by: Yeming Liu <[email protected]>
…6147) * Adding swagger definitions and examples for 2022-05-01-preview API * fixing avacado errors * Change the name of the API to listManagedProxyDetails * Fixing semantic and model validation * Fixing lintDiff * Fixing the description * Adding integer format * fixing the name to ListManagedProxyDetails * Adding description for provisioningState parameter * fixing go-sdk build errors
If you are a MSFT employee you can view your work branch via this link.
Contribution checklist: