Setting the default zone name has unexpected impact on equality
See original GitHub issueSetting the Settings.defaultZoneName
impacts Interval.equal
behavior in unexpected ways.
Execute this
const isoRange = '2021-03-24/2021-03-25';
range01 = Interval.fromISO(isoRange);
range02 = Interval.fromISO(isoRange);
Settings.defaultZoneName = Settings.defaultZoneName;
range03 = Interval.fromISO(isoRange);
range01.equals(range02); // true
range01.equals(range03); // false?
After Settings.defaultZoneName = Settings.defaultZoneName;
intervals are no more equal.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Google Associate Cloud Engineer Practice Exam Part 1
Google Associate Cloud Engineer Practice Exam are designed by experts to help you familiar with real GCP certification exam.
Read more >8. Configuration Reference — BIND 9 9.18.8 documentation
Controls global server configuration options and sets defaults for other statements. parental-agents. Defines a named list of servers for inclusion in primary ...
Read more >How do I resolve cluster creation errors in Amazon EKS? - AWS
Complete the steps in the Recreate the cluster in a different Availability Zone section.
Read more >Bug Patterns - Error Prone
This test has @Parameters but is using the default JUnit4 runner. The parameters will have no effect. ParcelableCreator. Detects classes which implement ...
Read more >MySQL JDBC Driver 5.1.33 - Time Zone Issue - Stack Overflow
therefore setting these 2 parameters has no effect as they are completely ignored (new default is useLegacyDateTimeCode=false ); In this manner setting ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@huilibaba thanks
I have ran a test to check for
and
range01.equals(range03)
appears to betrue
.@icambron I think this not an issue anymore.