Survivor
Survivor
I also encountered the same problem
I got the same error and version is 3.3.1
```2024-10-15T10:37:20.842+08:00 WARN 1 --- [d-engine] [ientWorker-16-1] r.p.t.t.TripleHttp2ClientResponseHandler : [DUBBO] Meet Exception on ClientResponseHandler, status code is: INTERNAL, dubbo version: 3.3.1, current host: 10.224.202.60, error code: 4-10. This may be caused...
> ``` > java.util.concurrent.RejectedExecutionException: null > at org.apache.dubbo.common.threadpool.ThreadlessExecutor.execute(ThreadlessExecutor.java:101) ~[dubbo-3.3.1.jar!/:3.3.1] > at org.apache.dubbo.common.threadpool.serial.SerializingExecutor.schedule(SerializingExecutor.java:73) ~[dubbo-3.3.1.jar!/:3.3.1] > at org.apache.dubbo.common.threadpool.serial.SerializingExecutor.execute(SerializingExecutor.java:65) ~[dubbo-3.3.1.jar!/:3.3.1] > at org.apache.dubbo.rpc.protocol.tri.stream.AbstractTripleClientStream$ClientTransportListener.onClose(AbstractTripleClientStream.java:459) ~[dubbo-3.3.1.jar!/:3.3.1] > at org.apache.dubbo.rpc.protocol.tri.transport.TripleHttp2ClientResponseHandler.channelInactive(TripleHttp2ClientResponseHandler.java:83) ~[dubbo-3.3.1.jar!/:3.3.1] > at io.netty.channel.AbstractChannelHandlerContext.invokeChannelInactive(AbstractChannelHandlerContext.java:303) ~[netty-transport-4.1.112.Final.jar!/:4.1.112.Final] >...
> `Client` is already timeout and throw reject execution exception So, how can I solve this?
I've had the same problem
This is our merge code： const mergePolygons = (polygons) => { if (!polygons || polygons.length === 1) return polygons; // 将所有多边形的路径转换为 GeoJSON 格式 let geoPolygons = []; polygons.forEach((item) => {...
> Hi [@AllKai](https://github.com/AllKai). Can you please attach the geojson and function calls you used to generate the result? Thank you! https://github.com/Turfjs/turf/issues/2917#issuecomment-3064528299
> Hi [@AllKai](https://github.com/AllKai). Have reproduced this locally using your code and the result looks ok. > > https://geojson.io > > > https://geojsonlint.com > > > I'm not sure which mapping...
> Maybe. Does it normally display ok for polygons with holes in them? I don't know, this problem is also a problem that our testers inadvertently draw, and this kind...