hazelcast / hazelcast/hazelcast-csharp-client
[TRACKING ISSUE] [PLAT-305] Pretty print cluster connect timeout in logs [API-2031]
- Dominant language
- C#
- Stars
- 107
- Forks
- 52
- PR merge metrics
- No merged PRs in 30d
Description
The tracking issue for the Java side PR.
See https://github.com/hazelcast/hazelcast/pull/18642 for details.
---
The default value for the cluster connect timeout is infinite,
so it is represented with `Long.MAX_VALUE`. When we try to log
this as it is, we output something like below.
```
... cluster connect timeout: 9223372036854775807 ms, ...
```
To make this more clear, we will replace this with the
output below.
```
... cluster connect timeout: INFINITE, ...
```
If the user has provided some other timeout value (such as 999 ms),
the output will still be as it is now.
```
... cluster connect timeout: 999 ms, ...
```
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.