ihsan demir

closing for now. To be done in the future.

fixed by https://github.com/hazelcast/hazelcast-cpp-client/pull/1038

fixed by https://github.com/hazelcast/hazelcast-cpp-client/pull/1011

closing for now. To be done int he future.

closing for now. To be done int he future.

Another failure during PR run: https://github.com/hazelcast/hazelcast/pull/24944#issuecomment-1620147416

Another failure: https://hazelcast-l337.ci.cloudbees.com/job/new-lab-fast-pr/11048/testReport/junit/com.hazelcast.map.impl.nearcache.invalidation/MemberMapReconciliationTest/test_reconciliation_does_not_cause_premature_removal_mapInMemoryFormat_BINARY_nearCacheInMemoryFormat_BINARY_/ Error Message ``` Wrong expectedHits [NearCacheStatsImpl{ownedEntryCount=100, ownedEntryMemoryCost=10800, creationTime=1507017374295, hits=99, misses=101, ratio=98.0%, evictions=0, expirations=0, lastPersistenceTime=0, persistenceCount=0, lastPersistenceDuration=0, lastPersistenceWrittenBytes=0, lastPersistenceKeyCount=0, lastPersistenceFailure=''}] expected: but was: Stacktrace java.lang.AssertionError: Wrong expectedHits [NearCacheStatsImpl{ownedEntryCount=100,...

> > Question: The problem is about at the client side not seeing exception details, right? We actually put the [stack trace information into the error codec](https://github.com/hazelcast/hazelcast-mono/blob/master/hazelcast/hazelcast/src/main/java/com/hazelcast/client/impl/protocol/codec/builtin/ErrorsCodec.java#L45), and it was...

Discussed with @srknzl and we concluded that why we need to try serialize a throwable in the first place? Normally, in a callable, you either return a real non-throwable object...