František Bořánek
František Bořánek
This file [ShakePeer Leaks.txt](https://github.com/rufuscoder/Shakespeer/files/888549/ShakePeer.Leaks.txt) contains all leaks. Definitely, the issue is the process **sphashd** where are repeating two leaks: ``` Leak: 0x2d31890 size=16 zone: DefaultMallocZone_0x1bf000 length: 5 "16779" Leak: 0x2d31950...
Here are the logs: ``` $ /Applications/ShakesPeer.app/Contents/MacOS/ShakesPeer -d debug 2014-12-08 20:49:38.969 ShakesPeer[1896:17311] got init completion level 25 2014-12-08 20:49:38.969 ShakesPeer[1896:17311] got init completion level 50 2014-12-08 20:49:59.038 ShakesPeer[1896:17311] Failed to...
I run into this right now. ``` unknown location(0): fatal error: in "memory_access_violation_test": memory access violation at address: 0x00000000: no mapping at fault address test_s3client.cc(136): last checkpoint: "memory_access_violation_test" test entry...
It is regression, in fact. I have test running against mock implementation running on localhost. Now I change S3 Client to Crt version and it stop working since the mock...
> Also, it seems to me that the producer checks the _uncompressed_ message size before sending, while the broker checks the _compressed_ message size. You are right. The comprimation is...
I solve my original problem with custom `ResourceVersionResolver` in `Snapshot`. Now when resource list is changed the version is changed to force discovery service send response. ```java private static ResourceVersionResolver...
> Probably related: [grpc/grpc-go#7013 (comment)](https://github.com/grpc/grpc-go/issues/7013#issuecomment-1972805644) It's likely not. This case was there was still active connection so the resource list was not completely empty. Whats happen was in app: -...
> > Probably related: [grpc/grpc-go#7013 (comment)](https://github.com/grpc/grpc-go/issues/7013#issuecomment-1972805644) > > It's likely not. This case was there was still active connection so the resource list was not completely empty. @atollena On second...
> > Bug or feature, it’s definitely the most upvoted issue > > I don't know how to upvote, but I just did run into this issue trying to run...
> It does not fix the original issue reported here though, we will also check the original/root issue of PooledThreadExecutor cyclic references. I think, it cannot be solved otherwise than...