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.

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

[BUG FIX] - Making JobInnerError object recursively defined #3666

Merged
merged 31 commits into from
Sep 13, 2017

Conversation

ro-joowan
Copy link
Contributor

@ro-joowan ro-joowan commented Sep 6, 2017

Description


This checklist is used to make sure that common guidelines for a pull request are followed.

General Guidelines

  • Title of the pull request 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 more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

  • Pull request includes test coverage for the included changes.

SDK Generation Guidelines

  • If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
  • The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code.
  • The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK.

ro-joowan and others added 29 commits July 24, 2017 15:23
* This change is mapped to this PR:
Azure/azure-rest-api-specs#1429

* This commit is for ADLA
* This change is mapped to this PR:
Azure/azure-rest-api-specs#1429

* This commit for ADLS
* I missed this file!
* Updating to the correct commit number:
Azure/azure-rest-api-specs#1452
* Do hydra to swagger specs migration for azure-sdk-for-net

* Fix build failed problem

* update the assemblyinfo file with the updated version 2.6.0

* Revert "update the assemblyinfo file with the updated version 2.6.0"

This reverts commit a33beb0.

* Updata the AssemblyFileVersion to 2.6.0.0

* revert package version

* Make project files concise.

* Add Provider test case

* update the pr with new tests with session records

* remove extra code
More descriptive and fixing indent issue that was not addressed in the previous commit
More descriptive and fixing indent issue not addressed in a previous commit
Adding an important note about retrieving a list of jobs and accounts
* Ran into two regressions in JobOperationTests.cs
* The custom Job Exists method is expecting a non-empty response body to
validate non-existence.  After speaking with a team member who
implemented the service, I can no longer rely on this.  Thus, I am
removing the logic that checks for a non-empty response body.
* Commenting out the test case for listing Jobs with a select parameter.
This is currently being fixed.
* Adding this as a reminder to re-enable the test
* Removing test case: DataLakeUploader_FreshFolderUploadDownload()

* Note: In the near future, the custom ADLS Filesystem code will be
replaced with a new SDK that has its own set of test cases.  The account
management side of ADLS will still remain, however.
* Skipping the flaky test as opposed to commenting it out
* Also, I forgot to replace a SessionRecord file from last update, so I
doing it now
* Based on this PR:
Azure/azure-rest-api-specs#1627

* We are essentially adding one more property to the JobInnerError
object (recursively) in order to capture the additional error
information that's returned by the service

* This added property has been tested successfully by a team member
@msftclas
Copy link

msftclas commented Sep 6, 2017

@ro-joowan,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

@@ -14,7 +14,7 @@ internal static class DataLakeAnalyticsCustomizationHelper
/// This constant is used as the default package version to place in the user agent.
/// It should mirror the package version in the project.json file.
/// </summary>
internal const string PackageVersion = "3.1.1-preview";
internal const string PackageVersion = "3.1.2-preview";
Copy link
Member

Choose a reason for hiding this comment

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

@ro-joowan can you explain what is this package number and what project.json file are you referring to.

Copy link
Contributor Author

@ro-joowan ro-joowan Sep 7, 2017

Choose a reason for hiding this comment

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

@shahabhijeet Couldn't find a project.json file in the src. Ben might be referring to the csproj file (https://github.com/ro-joowan/azure-sdk-for-net/blob/341b0bbea8d9110f2047f9d28150a4cc95ef34fc/src/SDKs/DataLake.Analytics/Management.DataLake.Analytics/Microsoft.Azure.Management.DataLake.Analytics.csproj).

This is one of the three places I've been told to update the version number -- the other place being in AssemblyInfo.cs

As for its purpose, I found this in here (https://github.com/ro-joowan/azure-sdk-for-net/blob/341b0bbea8d9110f2047f9d28150a4cc95ef34fc/src/SDKs/DataLake.Analytics/Management.DataLake.Analytics/Customizations/DataLakeAnalyticsAccountManagementClient.Customizations.cs):

    /// <param name='userAgentAssemblyVersion'>
    /// Optional. The version string that should be sent in the user-agent header for all requests. The default is the current version of the SDK.
    /// </param>

It looks like this custom method is a way for the user to set the SDK version in the user agent.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@shahabhijeet And so this PackageVersion is used as the default SDK version in the event that the user does not provide a custom version (https://github.com/ro-joowan/azure-sdk-for-net/blob/psSdkJson6/src/SDKs/DataLake.Analytics/Management.DataLake.Analytics/Customizations/DataLakeAnalyticsCustomizationHelper.cs#L29)

Copy link
Member

@shahabhijeet shahabhijeet Sep 13, 2017

Choose a reason for hiding this comment

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

Let's revisit this in the next release.
If the package version reflects what is in project.json (which is package version in csproj)
We do pass the Assembly File version in user Agent string, so how will this version be any different from the other?
Will allow now.

@ro-joowan
Copy link
Contributor Author

@shahabhijeet Friendly ping on this :)

@shahabhijeet shahabhijeet merged commit 7467c8a into Azure:psSdkJson6 Sep 13, 2017
@ro-joowan ro-joowan deleted the inner-error branch September 13, 2017 19:07
JasonYang-MSFT pushed a commit to JasonYang-MSFT/azure-sdk-for-net that referenced this pull request Dec 8, 2017
* Code gen for ADLA

* This change is mapped to this PR:
Azure/azure-rest-api-specs#1429

* This commit is for ADLA

* Code gen for ADLS

* This change is mapped to this PR:
Azure/azure-rest-api-specs#1429

* This commit for ADLS

* Code gen for ADLS (part 2)

* I missed this file!

* Code gen for ADL (part 3)

* Updating to the correct commit number:
Azure/azure-rest-api-specs#1452

* Update Azure Batch to 5.1.0 (Azure#3513)

* Fixing publishing of symbols. Fixing issue# 3518 (Azure#3519)

* Do hydra to swagger specs migration for azure-sdk-for-net (Azure#3482)

* Do hydra to swagger specs migration for azure-sdk-for-net

* Fix build failed problem

* update the assemblyinfo file with the updated version 2.6.0

* Revert "update the assemblyinfo file with the updated version 2.6.0"

This reverts commit a33beb0.

* Updata the AssemblyFileVersion to 2.6.0.0

* revert package version

* Make project files concise.

* Add Provider test case

* update the pr with new tests with session records

* remove extra code

* Fix Batch changelog references (Azure#3517)

* Fixing changelog.md

* Fixing up changelog.md

* [DataLake Analytics] Fixing changelog.md

More descriptive and fixing indent issue that was not addressed in the previous commit

* [DataLake Store] Fixing changelog.md

More descriptive and fixing indent issue not addressed in a previous commit

* [DataLake Analytics] Fixing changelog.md

Adding an important note about retrieving a list of jobs and accounts

* Revising custom Job Exists method

* Ran into two regressions in JobOperationTests.cs
* The custom Job Exists method is expecting a non-empty response body to
validate non-existence.  After speaking with a team member who
implemented the service, I can no longer rely on this.  Thus, I am
removing the logic that checks for a non-empty response body.
* Commenting out the test case for listing Jobs with a select parameter.
This is currently being fixed.

* Adding a TODO comment

* Adding this as a reminder to re-enable the test

* [CODE GEN] - Reverting readOnly for two fields

* Code gen based on this very descriptive PR:
Azure/azure-rest-api-specs@e33ebf8

* [CODE GEN] - Updating the version (3.1.0 to 3.1.1)

* [CODE REFACTOR] - Removing flaky test

* Removing test case: DataLakeUploader_FreshFolderUploadDownload()

* Note: In the near future, the custom ADLS Filesystem code will be
replaced with a new SDK that has its own set of test cases.  The account
management side of ADLS will still remain, however.

* [DOC] - Updating the changelog to describe 3.1.1-preview

* [CODE REFACTOR] - Skipping flaky test

* Skipping the flaky test as opposed to commenting it out
* Also, I forgot to replace a SessionRecord file from last update, so I
doing it now

* [BUG FIX] - Making JobInnerError object recursively defined

* Based on this PR:
Azure/azure-rest-api-specs#1627

* We are essentially adding one more property to the JobInnerError
object (recursively) in order to capture the additional error
information that's returned by the service

* This added property has been tested successfully by a team member
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.

5 participants