[GitHub] lzh3636 opened a new pull request #2547: CLOUDSTACK-10315 Inconsistent debugging info in catch block
lzh3636 opened a new pull request #2547: CLOUDSTACK-10315 Inconsistent debugging info in catch block URL: https://github.com/apache/cloudstack/pull/2547 ## Description The description of the problem: https://issues.apache.org/jira/browse/CLOUDSTACK-10315 I modified some stack traces information to those logging statements with the same log messages, make their stack trace consistent. ## Types of changes - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [ ] New feature (non-breaking change which adds functionality) - [ ] Bug fix (non-breaking change which fixes an issue) - [x] Enhancement (improves an existing feature and functionality) - [ ] Cleanup (Code refactoring and cleanup, that may add test cases) ## Checklist: - [x] I have read the [CONTRIBUTING](https://github.com/apache/cloudstack/blob/master/CONTRIBUTING.md) document. - [x] My code follows the code style of this project. - [ ] My change requires a change to the documentation. - [ ] I have updated the documentation accordingly. Testing - [ ] I have added tests to cover my changes. - [ ] All relevant new and existing integration tests have passed. - [x] A full integration testsuite with all test that can run on my environment has passed. @blueorangutan package This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[GitHub] lzh3636 opened a new pull request #2547: CLOUDSTACK-10315 Inconsistent debugging info in catch block
lzh3636 opened a new pull request #2547: CLOUDSTACK-10315 Inconsistent debugging info in catch block URL: https://github.com/apache/cloudstack/pull/2547 ## Description The description of the problem: https://issues.apache.org/jira/browse/CLOUDSTACK-10315 I modified some stack traces information to those logging statements with the same log messages, make their stack trace consistent. ## Types of changes - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [ ] New feature (non-breaking change which adds functionality) - [ ] Bug fix (non-breaking change which fixes an issue) - [x] Enhancement (improves an existing feature and functionality) - [ ] Cleanup (Code refactoring and cleanup, that may add test cases) ## Screenshots (if appropriate): ## How Has This Been Tested? ## Checklist: - [x] I have read the [CONTRIBUTING](https://github.com/apache/cloudstack/blob/master/CONTRIBUTING.md) document. - [x] My code follows the code style of this project. - [ ] My change requires a change to the documentation. - [ ] I have updated the documentation accordingly. Testing - [ ] I have added tests to cover my changes. - [ ] All relevant new and existing integration tests have passed. - [x] A full integration testsuite with all test that can run on my environment has passed. @blueorangutan package This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
