Skip to content

Conversation

@taleib
Copy link
Contributor

@taleib taleib commented May 6, 2019

If you are a MSFT employee you can view your work branch via this link.

Contribution checklist:

@AutorestCI
Copy link

AutorestCI commented May 6, 2019

Automation for azure-sdk-for-js

Nothing to generate for azure-sdk-for-js

@AutorestCI
Copy link

AutorestCI commented May 6, 2019

Automation for azure-sdk-for-python

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-python#5332

@AutorestCI
Copy link

AutorestCI commented May 6, 2019

Automation for azure-sdk-for-java

Nothing to generate for azure-sdk-for-java

@AutorestCI
Copy link

AutorestCI commented May 6, 2019

Automation for azure-sdk-for-ruby

Encountered a Subprocess error: (azure-sdk-for-ruby)

Command: ['/usr/local/bin/autorest', '/tmp/tmplcqwdy1h/rest/specification/cost-management/resource-manager/readme.md', '--perform-load=false', '--swagger-to-sdk', '--output-artifact=configuration.json', '--input-file=foo', '--output-folder=/tmp/tmpmibf5a4k']
Finished with return code 7
and output:

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)

@AutorestCI
Copy link

AutorestCI commented May 6, 2019

Automation for azure-sdk-for-go

The initial PR has been merged into your service PR:
Azure/azure-sdk-for-go#4830

@azuresdkci
Copy link
Contributor

Can one of the admins verify this patch?

@taleib
Copy link
Contributor Author

taleib commented May 6, 2019

@noferrar

Copy link
Member

@jhendrixMSFT jhendrixMSFT left a comment

Choose a reason for hiding this comment

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

Can you please remove the BOM from ExternalBillingAccountForecast.json

@jhendrixMSFT jhendrixMSFT added the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label May 6, 2019
Copy link
Member

@majastrz majastrz left a comment

Choose a reason for hiding this comment

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

Looks good from ARM side.

@majastrz majastrz removed the WaitForARMFeedback <valid label in PR review process> add this label when ARM review is required label May 7, 2019
@majastrz majastrz added the ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review label May 7, 2019
@taleib taleib requested a review from jhendrixMSFT May 12, 2019 11:38
@taleib
Copy link
Contributor Author

taleib commented May 12, 2019

Can you please remove the BOM from ExternalBillingAccountForecast.json

resolved

@jhendrixMSFT
Copy link
Member

There are several model validation failures due to invalid examples that need to be addressed. Please see the following log.
https://dev.azure.com/azure-sdk/public/_build/results?buildId=30021

@taleib
Copy link
Contributor Author

taleib commented May 16, 2019

There are several model validation failures due to invalid examples that need to be addressed. Please see the following log.
https://dev.azure.com/azure-sdk/public/_build/results?buildId=30021

these errors are from another service and not Forecast. can we advance without addressing them?
is it okay for us to suppress all these errors not relatd to our PR?

@jhendrixMSFT
Copy link
Member

@taleib these errors cannot be suppressed. Please file an issue to track fixing them, then we can go ahead with the PR.

@taleib
Copy link
Contributor Author

taleib commented May 19, 2019

@taleib these errors cannot be suppressed. Please file an issue to track fixing them, then we can go ahead with the PR.

resolved

@jhendrixMSFT jhendrixMSFT merged commit 1a9dcf1 into Azure:master May 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ARMSignedOff <valid label in PR review process>add this label when ARM approve updates after review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants