Skip to content

Conversation

@littleaj
Copy link
Contributor

@littleaj littleaj commented Mar 1, 2018

This brings the branches back together after the fork for 2.0.0.

dhaval24 and others added 18 commits February 1, 2018 09:00
* Fix null ref check in TelemetryCorrelationUtils

* Modifying log level to warning

* Updating Changelog
* Handle NaN and +/-Infinity in metrics

* Default NaN/Infinity serialization to 0 to be consistent with other AI SDKs and make the code compatible with Java 6
* Initial commit of retry and backoff logic fixes

* Fixing warnings on files I touched this round

* Fix the eclipse UI from screaming about the docker Contstants

* Fixed backoff logic to use existing method. Added more logging to the sender channel.

* Added the partial response handler, more logging

* Added gson to core. Fixed backoff manager to keep original functionality. Added extension to return the timeout values as expected before.

* Added unit tests.

* Fixing string typed ArrayList<> to List<> per Dhaval

* Missed one

* Making tests consistent.

* Added javadoc comments, simplified logic for a few methods

* Added exception logging per @dhaval24. Fixed formatting on touched files

* Updates per last round of commits

Moved the Handlers out of the concrete package to the common package to keep the same consistency.  Removed a couple of unessecary methods. Added docs.

* Latest fixes

* Add MaxInstantRetry

Added MaxInstantRetry configuration to allow for instantaneous retry on a failed transmission.

* Javadoc Updates

Javadoc and formatting updates

* NumberFormatException fix

Added null check

* JavaDocs for TPM
…540)

Overriding default sampling percentage when programatically specified sampling percentage by user.
* Reliable channel: close resources in finally block.

* change logging to warning when closing resources
* Refactor

* BUGFIX Logic would never backoff

After adding the instant retry amount logic to the code this line of code could cause the transmissions to not back off.

* Changes requested
@littleaj littleaj self-assigned this Mar 1, 2018
@littleaj littleaj requested review from dhaval24 and grlima March 1, 2018 21:53
@@ -1,4 +1,4 @@
// Project properties
version=2.0.0-BETA
version=2.0.0
Copy link
Contributor

Choose a reason for hiding this comment

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

There are missing STABLE release commits in this PR. Stable branch is at version 2.0.1, for example.

Copy link
Contributor

Choose a reason for hiding this comment

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

@littleaj did you pulled the latest stable before merging locally?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@dhaval24 nope :) fixed.

## Version 2.0.0

- Fix #506 Null Reference Check causing Null Pointer Exception in `TelemetryCorrelationUtils.java`

Copy link
Contributor

Choose a reason for hiding this comment

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

There should be more items in this changelog for 2.0.0 - i believe this PR is missing the last commits from Stable branch

@dhaval24
Copy link
Contributor

dhaval24 commented Mar 1, 2018

Also FYI don't delete the stable branch. We might need if we want to do a hot fix.

grlima
grlima previously requested changes Mar 1, 2018
Copy link
Contributor

@grlima grlima left a comment

Choose a reason for hiding this comment

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

Commits are missing from 2/27 and 2/28

@littleaj
Copy link
Contributor Author

littleaj commented Mar 2, 2018

@grlima @dhaval24 Fixed. I needed to update my local 2.0.0-STABLE apparently.

Also, Since we have a tag on the commit we released, we can delete the branch; but I'll leave it for convenience. If we ever need to do this again, we can just merge the version branch (e.g. 2.0.0-STABLE) straight into master after the release is tagged. We won't lose the commit as long as something is pointing to it. See this post: https://stackoverflow.com/questions/33283350/what-happen-to-git-tags-pointing-to-a-removed-commit

@lhotari
Copy link

lhotari commented Mar 4, 2018

@littleaj please review #582 since that's a PR for 2.0.0-STABLE branch.

@dhaval24
Copy link
Contributor

dhaval24 commented Mar 4, 2018

@lhotari thanks for pointing out. Yes we should review this before merge.

littleaj and others added 3 commits March 5, 2018 14:23
* Fix customizing pom.xml in Gradle build

* Insert license after 1. row in pom.xml

* Filter artifacts relocated by shadow task from pom dependencies

- match artifacts by groupId
- fixes #583 

* Generate a pom file "beside" the artifact jar file
@littleaj
Copy link
Contributor Author

littleaj commented Mar 6, 2018

@grlima I think all the issues have been addressed.

@littleaj littleaj dismissed grlima’s stale review March 8, 2018 00:25

We discussed this offline

@littleaj littleaj merged commit abab7bb into master Mar 8, 2018
@grlima grlima deleted the merge_2.0.0_to_master branch March 15, 2018 22:39
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.

9 participants