-
Notifications
You must be signed in to change notification settings - Fork 59
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
control-service: java 17 #1439
control-service: java 17 #1439
Conversation
Signed-off-by: murphp15 <[email protected]>
Signed-off-by: murphp15 <[email protected]>
Signed-off-by: murphp15 <[email protected]>
Signed-off-by: murphp15 <[email protected]>
Signed-off-by: murphp15 <[email protected]>
Signed-off-by: murphp15 <[email protected]>
Signed-off-by: murphp15 <[email protected]>
Signed-off-by: murphp15 <[email protected]>
Signed-off-by: murphp15 <[email protected]>
Signed-off-by: murphp15 <[email protected]>
Signed-off-by: murphp15 <[email protected]>
Signed-off-by: murphp15 <[email protected]>
Signed-off-by: murphp15 <[email protected]>
Great, thanks for dealing with this! |
...rvice/src/integration-test/java/com/vmware/taurus/graphql/it/GraphQLExecutionsLogsUrlIT.java
Outdated
Show resolved
Hide resolved
Signed-off-by: murphp15 <[email protected]>
Signed-off-by: murphp15 <[email protected]>
Signed-off-by: murphp15 <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
nit: maybe link at major diff 11->17 transition in case you've looked for it
* java .now() gives nano-second precision and it causes tests written before we adopted that java | ||
* version to fail. | ||
*/ | ||
public static OffsetDateTime getTimeAccurateToMicroSecond() { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I find the documentation great. My only concern is with duplicated methods
with JobExecutionUtil
Why
Java 17 is more secure and needed for a lot of modern libraries.
More details can be seen here: #1440
What
When using java 17
time.now()
returns nanosecond accuracy.This causes problems for us because we only store micro second accuracy in the database.
To overcome this for a lot of tests we use timestamps which are accurate to micro seconds only.
How has this been tested?
Unit and integration tests
closes: #1440
Signed-off-by: murphp15 [email protected]