Hello, When the LIST_OFFSETS API doesn't find messages with timestamps larger or equal to the requested, it returns the end of the log offsets. In this scenario the API response contains the offsets but not corresponding timestamps. This makes it very hard to get the latest timestamp which is very useful e.g. for monitoring purposes.
I was able to patch "Log.fetchOffsetByTimestamp" to provide timestamps in the described scenario. Is there a reason *not* to do that, or should I contribute a fix? -- Andrey Klochkov
