Bernard Normier
Bernard Normier
From https://github.com/zeroc-ice/ice/actions/runs/11405309276/job/31736484488?pr=2930: ``` [ running client/server test - 10/18/24 15:13:47 ] - Config: ssl,ipv6,mx (swift run -c release --skip-build TestDriver Ice_ami Server --Ice.Default.Host=::1 --Test.BasePort=14200 --Ice.Warn.Connections=1 --Ice.Default.Protocol=ssl --Ice.IPv6=1 --Ice.PreferIPv6Address=1 --Ice.Admin.Endpoints="tcp -h...
Still failing: https://github.com/zeroc-ice/ice/actions/runs/11506846491/job/32031722095
I believe this issue occurs only on Windows 11.
Probably a duplicate of #2124.
We should document the difference between compileSlice and loadSlice, as it's not obvious from their names.
> it's possible that this map is deleted The map is never deleted - it's leaked on purpose. As a result, I don't see the potential ordering issue.
For many objects like Communicator and Connection, it's critical to return the same Swift wrapper all the time.
We actually have the same code in the C++ IceSSL/configuration - it's not C# specific.
Ok, I am leaving this as-is.
The log files from https://github.com/zeroc-ice/ice/actions/runs/11411974091/job/31757173288 suggests a deadlock in ObjectAdapter::hold. Note that the adapter processing the request is different from the object adapter being held here: client ``` -- 10/18/24...