status":404,"error":"Not Found","message":"Not Found","path":"/rpc/receiveAndReply"

Describe the bug
rpc调用404
我想在gateway-core模块中调用publicServce，传入userName，判断该用户是否第一次登陆；
1，我在gateway-core中
val PUBLIC_SPRING_APPLICATION_NAME = CommonVars("wds.linkis.query.application.name", "cloud-publicservice")
private val loginSender: Sender = Sender.getSender(GatewayConfiguration.PUBLIC_SPRING_APPLICATION_NAME.getValue)
var firstLogin = false
val requestLogin = new RequestLogin
requestLogin.setUserName(lowerCaseName)
Utils.tryCatch(loginSender.ask(requestLogin) match {
case r: Boolean =>
firstLogin = r
}) {
t => {
warn(s"Login rpc request error, err message ", t)
message.setStatus(1)
message.setMessage("System error, please try again later(系统异常，请稍后再试)")
message.data("errmsg", t.getMessage)
}
}
2。在publicService模块中
@Component
class LoginReceiver extends Receiver with Logging {
@Autowired
private var applicationService: ApplicationService = _
override def receive(message: Any, sender: Sender): Unit = ???
override def receiveAndReply(message: Any, sender: Sender): Any = message match {
case t: RequestLogin => {
logger.info("t--------------------" + t.getUserName)
val user = applicationService.getUserByName(t.getUserName)
logger.info("user--------------------" + user.toString)
user == null || user.getIsFirstLogin()
}
}
override def receiveAndReply(message: Any, duration: Duration, sender: Sender): Any = message match {
case _ => new Object()
}
}
3，运行程序直接在sender端报错
,"status":404,"error":"Not Found","message":"Not Found","path":"/rpc/receiveAndReply"

2020-07-01 14:22:43.790 INFO  [reactor-http-nio-2] com.netflix.config.ChainedDynamicProperty 115 checkAndFlip - Flipping property: cloud-publicservice.ribbon.ActiveConnectionsLimit to use NEXT property: niws.loadbalancer.availabilityFilteringRule.activeConnectionsLimit =<PHONE_NUMBER>
2020-07-01 14:22:43.792 INFO  [reactor-http-nio-2] com.netflix.loadbalancer.DynamicServerListLoadBalancer 150 restOfInit - DynamicServerListLoadBalancer for client cloud-publicservice initialized: DynamicServerListLoadBalancer:{NFLoadBalancer:name=cloud-publicservice,current list of Servers=[test-dn2:9102],Load balancer stats=Zone stats: {defaultzone=[Zone:defaultzone;       Instance count:1;       Active connections count: 0;    Circuit breaker tripped count: 0;        Active connections per server: 0.0;]
},Server stats: [[Server:test-dn2:9102; Zone:defaultZone;       Total Requests:0;       Successive connection failure:0;        Total blackout seconds:0;        Last connection made:Thu Jan 01 08:00:00 CST 1970;      First connection made: Thu Jan 01 08:00:00 CST 1970;    Active Connections:0;    total failure count in last (1000) msecs:0;     average resp time:0.0;  90 percentile resp time:0.0;    95 percentile resp time:0.0;    min resp time:0.0;       max resp time:0.0;      stddev resp time:0.0]
]}ServerList:org.springframework.cloud.netflix.ribbon.eureka.DomainExtractingServerList@1d6dee2f
2020-07-01 14:22:43.893 WARN  [reactor-http-nio-2] com.webank.wedatasphere.linkis.gateway.security.LDAPUserRestful 55 warn - Login rpc request error, err message feign.FeignException: status 404 reading RPCReceiveRemote#receiveAndReply(Message); content:
{"timestamp":"2020-07-01T06:22:43.879+0000","status":404,"error":"Not Found","message":"Not Found","path":"/rpc/receiveAndReply"}
at feign.FeignException.errorStatus(FeignException.java:62) ~[feign-core-9.5.1.jar:?]
at feign.codec.ErrorDecoder$Default.decode(ErrorDecoder.java:91) ~[feign-core-9.5.1.jar:?]
at feign.SynchronousMethodHandler.executeAndDecode(SynchronousMethodHandler.java:138) ~[feign-core-9.5.1.jar:?]
at feign.SynchronousMethodHandler.invoke(SynchronousMethodHandler.java:76) ~[feign-core-9.5.1.jar:?]
at feign.ReflectiveFeign$FeignInvocationHandler.invoke(ReflectiveFeign.java:103) ~[feign-core-9.5.1.jar:?]
at com.sun.proxy.$Proxy176.receiveAndReply(Unknown Source) ~[?:?]
at com.webank.wedatasphere.linkis.rpc.BaseRPCSender$$anonfun$ask$1.apply(BaseRPCSender.scala:86) ~[linkis-cloudRPC-0.9.3.jar:?]
at com.webank.wedatasphere.linkis.rpc.BaseRPCSender.execute(BaseRPCSender.scala:80) ~[linkis-cloudRPC-0.9.3.jar:?]
at com.webank.wedatasphere.linkis.rpc.BaseRPCSender.ask(BaseRPCSender.scala:83) ~[linkis-cloudRPC-0.9.3.jar:?]
at com.webank.wedatasphere.linkis.gateway.security.UserPwdAbstractUserRestful$$anonfun$tryLogin$1.apply$mcV$sp(UserRestful.scala:197) ~[linkis-gateway-core-0.9.3.jar:?]
at com.webank.wedatasphere.linkis.gateway.security.UserPwdAbstractUserRestful$$anonfun$tryLogin$1.apply(UserRestful.scala:197) ~[linkis-gateway-core-0.9.3.jar:?]
at com.webank.wedatasphere.linkis.gateway.security.UserPwdAbstractUserRestful$$anonfun$tryLogin$1.apply(UserRestful.scala:197) ~[linkis-gateway-core-0.9.3.jar:?]
at com.webank.wedatasphere.linkis.common.utils.Utils$.tryCatch(Utils.scala:48) ~[linkis-common-0.9.3.jar:?]
at com.webank.wedatasphere.linkis.gateway.security.UserPwdAbstractUserRestful.tryLogin(UserRestful.scala:200) ~[linkis-gateway-core-0.9.3.jar:?]
at com.webank.wedatasphere.linkis.gateway.security.AbstractUserRestful.login(UserRestful.scala:79) ~[linkis-gateway-core-0.9.3.jar:?]
at com.webank.wedatasphere.linkis.gateway.security.AbstractUserRestful.doUserRequest(UserRestful.scala:63) ~[linkis-gateway-core-0.9.3.jar:?]
at com.webank.wedatasphere.linkis.gateway.security.SecurityFilter$$anonfun$doFilter$1.apply$mcV$sp(SecurityFilter.scala:72) ~[linkis-gateway-core-0.9.3.jar:?]
at com.webank.wedatasphere.linkis.gateway.security.SecurityFilter$$anonfun$doFilter$1.apply(SecurityFilter.scala:72) ~[linkis-gateway-core-0.9.3.jar:?]
at com.webank.wedatasphere.linkis.gateway.security.SecurityFilter$$anonfun$doFilter$1.apply(SecurityFilter.scala:72) ~[linkis-gateway-core-0.9.3.jar:?]
at com.webank.wedatasphere.linkis.common.utils.Utils$.tryCatch(Utils.scala:48) ~[linkis-common-0.9.3.jar:?]
at com.webank.wedatasphere.linkis.gateway.security.SecurityFilter$.doFilter(SecurityFilter.scala:72) ~[linkis-gateway-core-0.9.3.jar:?]
at com.webank.wedatasphere.linkis.gateway.security.SecurityFilter.doFilter(SecurityFilter.scala) ~[linkis-gateway-core-0.9.3.jar:?]
at com.webank.wedatasphere.linkis.gateway.springcloud.http.GatewayAuthorizationFilter.gatewayDeal(GatewayAuthorizationFilter.java:136) ~[linkis-gateway-springcloudgateway-0.9.3.jar:?]
at com.webank.wedatasphere.linkis.gateway.springcloud.http.GatewayAuthorizationFilter.lambda$filter$1(GatewayAuthorizationFilter.java:207) ~[linkis-gateway-springcloudgateway-0.9.3.jar:?]
at reactor.core.publisher.MonoFlatMap$FlatMapMain.onNext(MonoFlatMap.java:118) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.FluxOnErrorResume$ResumeSubscriber.onNext(FluxOnErrorResume.java:73) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.FluxMapFuseable$MapFuseableSubscriber.onNext(FluxMapFuseable.java:121) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.FluxMapFuseable$MapFuseableSubscriber.onNext(FluxMapFuseable.java:121) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.FluxFilterFuseable$FilterFuseableSubscriber.onNext(FluxFilterFuseable.java:113) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.Operators$MonoSubscriber.complete(Operators.java:1476) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoCollectList$MonoBufferAllSubscriber.onComplete(MonoCollectList.java:118) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.FluxMap$MapSubscriber.onComplete(FluxMap.java:136) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.FluxPeek$PeekSubscriber.onComplete(FluxPeek.java:252) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.FluxMap$MapSubscriber.onComplete(FluxMap.java:136) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.ipc.netty.channel.FluxReceive.terminateReceiver(FluxReceive.java:377) ~[reactor-netty-0.7.8.RELEASE.jar:0.7.8.RELEASE]
at reactor.ipc.netty.channel.FluxReceive.drainReceiver(FluxReceive.java:202) ~[reactor-netty-0.7.8.RELEASE.jar:0.7.8.RELEASE]
at reactor.ipc.netty.channel.FluxReceive.request(FluxReceive.java:110) ~[reactor-netty-0.7.8.RELEASE.jar:0.7.8.RELEASE]
at reactor.core.publisher.FluxMap$MapSubscriber.request(FluxMap.java:155) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.FluxPeek$PeekSubscriber.request(FluxPeek.java:130) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.FluxMap$MapSubscriber.request(FluxMap.java:155) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoCollectList$MonoBufferAllSubscriber.onSubscribe(MonoCollectList.java:90) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.FluxMap$MapSubscriber.onSubscribe(FluxMap.java:86) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.FluxPeek$PeekSubscriber.onSubscribe(FluxPeek.java:163) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.FluxMap$MapSubscriber.onSubscribe(FluxMap.java:86) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.ipc.netty.channel.FluxReceive.startReceiver(FluxReceive.java:273) ~[reactor-netty-0.7.8.RELEASE.jar:0.7.8.RELEASE]
at reactor.ipc.netty.channel.FluxReceive.subscribe(FluxReceive.java:124) ~[reactor-netty-0.7.8.RELEASE.jar:0.7.8.RELEASE]
at reactor.core.publisher.FluxMap.subscribe(FluxMap.java:62) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.ipc.netty.ByteBufFlux.subscribe(ByteBufFlux.java:242) ~[reactor-netty-0.7.8.RELEASE.jar:0.7.8.RELEASE]
at reactor.core.publisher.FluxPeek.subscribe(FluxPeek.java:83) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.ipc.netty.ByteBufFlux.subscribe(ByteBufFlux.java:242) ~[reactor-netty-0.7.8.RELEASE.jar:0.7.8.RELEASE]
at reactor.core.publisher.FluxMap.subscribe(FluxMap.java:62) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoCollectList.subscribe(MonoCollectList.java:59) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoFilterFuseable.subscribe(MonoFilterFuseable.java:47) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoMapFuseable.subscribe(MonoMapFuseable.java:59) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoMapFuseable.subscribe(MonoMapFuseable.java:59) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoOnErrorResume.subscribe(MonoOnErrorResume.java:44) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoFlatMap.subscribe(MonoFlatMap.java:60) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoDefer.subscribe(MonoDefer.java:52) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoDefer.subscribe(MonoDefer.java:52) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.Mono.subscribe(Mono.java:3590) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoIgnoreThen$ThenIgnoreMain.drain(MonoIgnoreThen.java:172) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoIgnoreThen.subscribe(MonoIgnoreThen.java:56) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoDefer.subscribe(MonoDefer.java:52) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoDefer.subscribe(MonoDefer.java:52) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.Mono.subscribe(Mono.java:3590) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoIgnoreThen$ThenIgnoreMain.drain(MonoIgnoreThen.java:172) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoIgnoreThen.subscribe(MonoIgnoreThen.java:56) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoFlatMap$FlatMapMain.onNext(MonoFlatMap.java:150) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.FluxSwitchIfEmpty$SwitchIfEmptySubscriber.onNext(FluxSwitchIfEmpty.java:67) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoNext$NextSubscriber.onNext(MonoNext.java:76) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.innerNext(FluxConcatMap.java:275) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.FluxConcatMap$ConcatMapInner.onNext(FluxConcatMap.java:849) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.FluxMap$MapSubscriber.onNext(FluxMap.java:114) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.FluxSwitchIfEmpty$SwitchIfEmptySubscriber.onNext(FluxSwitchIfEmpty.java:67) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.Operators$MonoSubscriber.complete(Operators.java:1476) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoFlatMap$FlatMapMain.onNext(MonoFlatMap.java:144) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.FluxMap$MapSubscriber.onNext(FluxMap.java:114) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoNext$NextSubscriber.onNext(MonoNext.java:76) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.FluxFilterWhen$FluxFilterWhenSubscriber.drain(FluxFilterWhen.java:266) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.FluxFilterWhen$FluxFilterWhenSubscriber.onNext(FluxFilterWhen.java:134) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.FluxDematerialize$DematerializeSubscriber.onNext(FluxDematerialize.java:114) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.FluxDematerialize$DematerializeSubscriber.onNext(FluxDematerialize.java:42) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.FluxFlattenIterable$FlattenIterableSubscriber.drainAsync(FluxFlattenIterable.java:395) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.FluxFlattenIterable$FlattenIterableSubscriber.drain(FluxFlattenIterable.java:638) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.FluxFlattenIterable$FlattenIterableSubscriber.onNext(FluxFlattenIterable.java:242) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.FluxPeekFuseable$PeekFuseableSubscriber.onNext(FluxPeekFuseable.java:179) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.Operators$MonoSubscriber.complete(Operators.java:1461) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoCollectList$MonoBufferAllSubscriber.onComplete(MonoCollectList.java:118) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.DrainUtils.postCompleteDrain(DrainUtils.java:131) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.DrainUtils.postComplete(DrainUtils.java:186) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.FluxMaterialize$MaterializeSubscriber.onComplete(FluxMaterialize.java:134) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.FluxFlattenIterable$FlattenIterableSubscriber.drainAsync(FluxFlattenIterable.java:325) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.FluxFlattenIterable$FlattenIterableSubscriber.drain(FluxFlattenIterable.java:638) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.FluxFlattenIterable$FlattenIterableSubscriber.onComplete(FluxFlattenIterable.java:259) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.FluxMapFuseable$MapFuseableSubscriber.onComplete(FluxMapFuseable.java:144) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.Operators$MonoSubscriber.complete(Operators.java:1463) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoCollectList$MonoBufferAllSubscriber.onComplete(MonoCollectList.java:118) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.FluxFlatMap$FlatMapMain.checkTerminated(FluxFlatMap.java:794) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.FluxFlatMap$FlatMapMain.drainLoop(FluxFlatMap.java:560) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.FluxFlatMap$FlatMapMain.drain(FluxFlatMap.java:540) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.FluxFlatMap$FlatMapMain.onComplete(FluxFlatMap.java:426) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.FluxIterable$IterableSubscription.slowPath(FluxIterable.java:265) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.FluxIterable$IterableSubscription.request(FluxIterable.java:201) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.FluxFlatMap$FlatMapMain.onSubscribe(FluxFlatMap.java:335) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.FluxIterable.subscribe(FluxIterable.java:139) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.FluxIterable.subscribe(FluxIterable.java:63) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.FluxFlatMap.subscribe(FluxFlatMap.java:97) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoCollectList.subscribe(MonoCollectList.java:59) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoMapFuseable.subscribe(MonoMapFuseable.java:59) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoFlattenIterable.subscribe(MonoFlattenIterable.java:101) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.FluxMaterialize.subscribe(FluxMaterialize.java:40) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoCollectList.subscribe(MonoCollectList.java:59) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoPeekFuseable.subscribe(MonoPeekFuseable.java:74) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoFlattenIterable.subscribe(MonoFlattenIterable.java:101) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.FluxDematerialize.subscribe(FluxDematerialize.java:39) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.FluxDefer.subscribe(FluxDefer.java:54) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.FluxFilterWhen.subscribe(FluxFilterWhen.java:69) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoNext.subscribe(MonoNext.java:40) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoMap.subscribe(MonoMap.java:55) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoFlatMap.subscribe(MonoFlatMap.java:60) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoSwitchIfEmpty.subscribe(MonoSwitchIfEmpty.java:44) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoMap.subscribe(MonoMap.java:55) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.Mono.subscribe(Mono.java:3590) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.drain(FluxConcatMap.java:442) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.onSubscribe(FluxConcatMap.java:212) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.FluxIterable.subscribe(FluxIterable.java:139) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.FluxIterable.subscribe(FluxIterable.java:63) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.FluxConcatMap.subscribe(FluxConcatMap.java:121) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoNext.subscribe(MonoNext.java:40) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoSwitchIfEmpty.subscribe(MonoSwitchIfEmpty.java:44) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoFlatMap.subscribe(MonoFlatMap.java:60) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoFlatMap.subscribe(MonoFlatMap.java:60) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoDefer.subscribe(MonoDefer.java:52) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoPeekTerminal.subscribe(MonoPeekTerminal.java:61) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoFlatMap$FlatMapMain.onNext(MonoFlatMap.java:150) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.Operators$MonoSubscriber.complete(Operators.java:1476) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoZip$ZipCoordinator.signal(MonoZip.java:247) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoZip$ZipInner.onNext(MonoZip.java:329) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.Operators$ScalarSubscription.request(Operators.java:2041) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoZip$ZipInner.onSubscribe(MonoZip.java:318) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoJust.subscribe(MonoJust.java:54) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.Mono.subscribe(Mono.java:3590) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoZip.subscribe(MonoZip.java:128) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoFlatMap.subscribe(MonoFlatMap.java:60) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoDefer.subscribe(MonoDefer.java:52) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoDefer.subscribe(MonoDefer.java:52) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoPeekTerminal.subscribe(MonoPeekTerminal.java:61) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoPeekFuseable.subscribe(MonoPeekFuseable.java:74) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoDefer.subscribe(MonoDefer.java:52) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoDefer.subscribe(MonoDefer.java:52) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoOnErrorResume.subscribe(MonoOnErrorResume.java:44) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoOnErrorResume.subscribe(MonoOnErrorResume.java:44) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoOnErrorResume.subscribe(MonoOnErrorResume.java:44) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.Mono.subscribe(Mono.java:3590) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoIgnoreThen$ThenIgnoreMain.drain(MonoIgnoreThen.java:172) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoIgnoreThen.subscribe(MonoIgnoreThen.java:56) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoPeekFuseable.subscribe(MonoPeekFuseable.java:70) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.core.publisher.MonoPeekTerminal.subscribe(MonoPeekTerminal.java:61) ~[reactor-core-3.2.2.RELEASE.jar:3.2.2.RELEASE]
at reactor.ipc.netty.channel.ChannelOperations.applyHandler(ChannelOperations.java:380) ~[reactor-netty-0.7.8.RELEASE.jar:0.7.8.RELEASE]
at reactor.ipc.netty.http.server.HttpServerOperations.onHandlerStart(HttpServerOperations.java:398) ~[reactor-netty-0.7.8.RELEASE.jar:0.7.8.RELEASE]
at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:163) [netty-common-4.1.25.Final.jar:4.1.25.Final]
at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:404) [netty-common-4.1.25.Final.jar:4.1.25.Final]
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:465) [netty-transport-4.1.25.Final.jar:4.1.25.Final]
at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:884) [netty-common-4.1.25.Final.jar:4.1.25.Final]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_181]
2020-07-01 14:22:44.770 INFO  [PollingServerListUpdater-0] com.netflix.config.ChainedDynamicProperty 115 checkAndFlip - Flipping property: cloud-publicservice.ribbon.ActiveConnectionsLimit to use NEXT property: niws.loadbalancer.availabilityFilteringRule.activeConnectionsLimit =<PHONE_NUMBER>
2020-07-01 14:27:30.802 INFO  [AsyncResolver-bootstrap-executor-0] com.netflix.discovery.shared.resolver.aws.ConfigClusterResolver 43 getClusterEndpoints - Resolving eureka endpoints via configuration
2020-07-01 14:32:30.803 INFO  [AsyncResolver-bootstrap-executor-0] com.netflix.discovery.shared.resolver.aws.ConfigClusterResolver 43 getClusterEndpoints - Resolving eureka endpoints via configuration
2020-07-01 14:37:30.804 INFO  [AsyncResolver-bootstrap-executor-0] com.netflix.discovery.shared.resolver.aws.ConfigClusterResolver 43 getClusterEndpoints - Resolving eureka endpoints via configuration

publicService下没有jasper-*类似包

已经解决

请问下是怎么解决的！


Bring trailing while statements back

It seems that after this discussion a trailing while statement support got dropped. Here is explained why. Here is the comment that did it.
The whole problem was that Ruby's implementation meant this
# This one first checks <condition> and then executes
 while <condition>

# This one first executes  and then checks <condition> (this should've been removed)
begin

end while <condition>

Which was confusing because nobody expects the second version to run the code before checking the condition. Instead of removing the second possibility, which even the creator of Ruby would've wanted to be able to do, you guys decided to remove trailing while statements outright.
Your reasoning was that somebody with ruby experience might find the syntax confusing, even though a post-if works exactly the same.
Nobody thought that  while <condition> was confusing, it could've stayed. I use it a lot, and having to use 3 lines instead doesn't feel like Ruby's syntax anymore. It also makes porting stuff from Ruby to Crystal a pain.
In most languages something similiar would be achieved like while (<condition>)  but because Ruby doesn't support that in either it's if or while form it supports post-if and post-while syntax instead.
Matz never said he wanted to remove the whole option, just the second version of it.  while <condition> had never been an issue and should've been left alone.
In summary, there was never a problem with the  while <condition> syntax and just like  if <conditon> it's a core part of the Ruby syntax.
Honestly, you guys chose the easy way out here and it was the wrong option.
I know I am 5 years to late to this discussion, but I am hoping someone can add this feature back to Crystal.
The syntax lacks without it.

There is no problem with  while <condition> syntax, except that adding it would automatically also allow begin/end while <condition> with the same semantics, but different than Ruby's. The compiler then should make the parsing of the later a special case, and we don't like that either. Thus we decided, as explained in the FAQ, to not add that feature.

you guys chose the easy way out here and it was the wrong option

There is no such thing as "wrong" option. Designing a language is full of subjective decisions and this one was one of them. There are arguments you might agree or not, and that's fine. Nobody will ever reach 100% agreement on everything.

@waj If one allows the other, then why don't they work the same?
How did it ever happen that Ruby does this:
begin
  puts "This runs once"
end while false

However with if instead of while
begin
  puts "This doesn't print at all"
end if false

Would it be such a bad thing to bring back both methods of using trailing while, but make them behave like like how post-if behaves? Like Matz would've wanted with Ruby?

Would it be such a bad thing to bring back both methods of using trailing while, but make them behave like like how post-if behaves? Like Matz would've wanted with Ruby?

Yes, because then the behaviour would be different than Ruby. And for people coming from Ruby I think it's more confusing to have a different semantics than having a compilation error forcing to write the code differently
If we add a similar structure in the future, we could do it with a different syntax. For example (this is just me randomizing here, not something we discussed with the team or have a plan for):
repeat
  puts "This runs once"
while false

and also:
repeat
  puts "This runs once"
until false

This syntax would allow running code that must be executed at least once, but without having to resort on break statements, keeping the code structured. But my opinion is that I'd not add an analogous trailing syntax because they will be always ambiguous for the reader.
Anyway, this is probably not coming to the language anytime soon. At least not before 1.0.

Interestingly:
while true
  p "."
end
# Same as
loop do
  p "."
end
# Same as
loop { p "." }

In Lua:
while true do
  print(".")
end

while is a keyword, so its semantics are different from other methods accepting blocks.
An idea, have loop accepting an argument:
# (I added a _ to avoid a conflict with the existing loop)
macro loop_(cond = true, &)
  while {{cond}}
    {{yield}}
  end
end

i = 0
loop_ i < 10 { p i += 1 }

Even if my opinion on loop is it is quite superfluous (is while true really as long to write?). I rarely use it, but being already there, why not extending its syntax?

Yes, because then the behaviour would be different than Ruby. And for people coming from Ruby I think it's more confusing to have a different semantics than having a compilation error forcing to write the code differently

But I honestly think that this won't be the case, seeing as a lot of people that used Ruby already found begin/end while <cond> confusing beacuse it ran the code even when the condition resolved to false. Even in Crystal for the short time that that functionality was here people complained about it.
I think you won't find a single user who will complain about the syntax working correctly inside Crystal.
Either way Ruby code doesn't work the same in Crystal code. Because currently most of my Ruby code doesn't compile in crystal because I make a lot of use of trailing while. Which when I first saw it I though was a lot more confusing than I think anyone would be about begin/end while <cond> working like it should.

I'm closing this issue because it's "bring trailing while statements back" and that's never going to happen. If you want to have a way to do repeat { ... } while or similar, please open a separate issue.
Let me explain why it's never going to happen.

Your reasoning was that somebody with ruby experience might find the syntax confusing

That's me! :-) I found it confusing, and I have plenty of ruby experience.

In summary, there was never a problem with the  while

Well, we (the core team members, and some others too) found it confusing. I always struggled with that in Ruby. It's just confusing. With exp if cond there's no confusion, there's no change exp is going to be executed before cond, it just doesn't make sense. With exp while cond there's confusion, so we decided to remove it.

But I honestly think that this won't be the case

How can you be sure? One thing is gut intuition, another thing is introducing a feature and later having to introduce a massive breaking change if that goes wrong.

I think you won't find a single user who will complain about the syntax working correctly inside Crystal

Me, @waj and counting...
That's why I'm closing this. But feel free to open a separate issue to discuss ways to do repeat { ... } while cond because exp while cond can be done right now: while cond; exp; end.

Alright so I think I understand the issue more clearly now.
Crystal, used to ALWAYS run the code once before evaluating the condition, which is obviously confusing as hell. Ruby only did that for instances where the statement was inside a block, which even Ruby users found confusing.
 I mean that's like making  if <condition> run the code before checking the condition.
If you are using Ruby's syntax then why would you ever decide to change its behavior like that.
Anyway repeat  while <cond> sounds okay, that will still make a readable oneliner. However I still think that's adding an 8 character keyword for no reason.
Anyway if the dev teams do change your mind, I added a branch that implements while and until like they did in Ruby, on my fork.

I also want to point out that reading https://github.com/crystal-lang/crystal/issues/549 back,
@asterite seems to be the only person who thought Crystals implementation was right.
The other comments either wanted Crystal to make the syntax like Ruby's again (without blocks) or wanted the functionality to come back.


Please update Readme to explain how to use this component

I am trying to follow the Readme, but the example imports Progess from index.vue? and then of course this will throw 'Cannot find index.vue' what is Index.vue? how does one actually use this component

I was also wondering about this

@rizkhal
i used this
import progress from "../../node_modules/easy-circular-progress/src/index.vue";
and didn't work for me  (This relative module was not found)
can you show us how you did it?
i'm using gridsome

I will update readme  later


Parse the two hyphens in the HTML comment as one hyphen

I would like to be able to accept directive comment descriptions in eslint-plugin-vue.
However, the comment value did not produce the expected result.
The following HTML comment is parsed as follows:
<template>
  <!-- eslint-disable -- description -->
</template>

[
  {
    "type": "HTMLComment",
    "range": [ /* ...  */ ],
    "loc": { /* ...  */ },
    "value": " eslint-disable - description "
  }
]

I expect the following results.
[
  {
    "type": "HTMLComment",
    "range": [ /* ...  */ ],
    "loc": { /* ...  */ },
-    "value": " eslint-disable - description "
+    "value": " eslint-disable -- description "
  }
]

I've heard that the old HTML specification should avoid consecutive hyphens.
Do you think you should avoid separating the description with two hyphens?

Thank you for your report.
It looks like a bug.
The HTML comment parsing is defined in https://html.spec.whatwg.org/multipage/parsing.html, from the section <IP_ADDRESS> to <IP_ADDRESS>. It's complex a bit.
"Comment state" -> "Comment end dash state" -> "Comment end state", then it says "Append two U+002D HYPHEN-MINUS characters (-) to the comment token's data.", but the tokenizer appends only one hypen.

Thank you for your comment!
I have opened a PR to fix this.


Topsoil only provides "save as" for datasets

From @bowring in #284:

Also, when "Save Data Table" is invoked, Topsoil does not differentiate between "save" and "save-as". I suggest that Topsoil use the standard save / save as metaphor with relation to file paths.

Topsoil now provides both "Save" and "Save As..." for project files.


Feature: juju-jockey CLI testing

Problem
Current testing does not includes calls to juju-jockey.  Ideally, these tests commands would be run in the context of a snap, just as a real user would.
Proposed Feature
Add tests which call juju-jockey in a variety of contexts.  A minimum coverage list would be:

juju-jockey info
Querying units with various filters
Querying machines with various filters
Querying across models (in the near future)

100% +1 here. This can catch regressions in the syntax and obvious errors that unit tests may not catch due to them loading functions in through the library interface.


Fix broken links in README.md

Make sure that:

[ ] Screenshot/GIF included (to demonstrate the plugin functionality)

[ ] ToC updated

@lannonbr awesome! here's the isolated PR for the link fixes.

LGTM. Merging


Improve deb pkg upgrade process (Version: 1.5 rc1)

Issue Description

The current deb pk upgrade process restarts rippled process - it should only upgrade the files without restarting the process
Steps to Reproduce

The moment you do "apt-get install rippled"  then apt will download and unpack and then also stop rippled and update the files and then start rippled.
Expected Result

do not stop and restart rippled
Actual Result

rippled is halted and restarted.
Environment

Deb, Ubuntu 16.04 and 18.04
Supporting Files

n/a

How do you expect a binary to be updated while it keeps running? Or should ing after upgrading to the current one?

I think it's probably correct that updating the package restarts the service? I don't like the idea of upgrading the package but then having the old binary continue to run. That sounds like a recipe for version mismatches and hard-to-debug issues.


fix(ipsf-coord): Updating to v6.8.10

:tada: This PR is included in version 2.0.10 :tada:
Your semantic-release bot :package::rocket:


Use Python 3.5 image by default

Update CI Python versions to 3.5 and 3.8.

Update commit message to mention CircleCI


NotImplementedError: allocate_hosts

NotImplementedError: The allocate_hosts action has not been implemented
Method used to generate issue:
def setup_mock_dedicated_host(zone):
    response = ec2client.allocate_hosts(
        AvailabilityZone=zone,
        InstanceType='t3a.nano',
        Quantity=1
    )
    return response

I am using Moto version 1.3.13.
Creating this issue as a feature request to implement this functionality.

Thanks for opening. Tagging this as a feature request.


add code to set proxy config if the HTTP_PROXY env is set

I could not test it since I do not have a required setup available

@deepakthankachan please take a moment to review the change.

Closing this as the PR as it is missing tests, update to package.json to include required proxy library. Have opened this PR with requested feature.


Wasm interp: WASI and stack trace

Start implementing WASI, and a Wasm stack trace, and fix some bugs.
These changes were enough to get some initial Zig builtin tests working.
Summary

Implement some basic WASI syscalls

args_sizes_get, args_get, fd_write, proc_exit

Change the CLI to be compatible with other engines and zig test

Don't require -- before the Wasm arguments
Make sure the WASI app sees its own path as argv[0]. (Interpreter removes its own argv[0], its own flags, etc. before passing the rest down.)

Implement a stack trace dump for the Wasm app

At this stage, when debugging, I usually find I want a stack trace of the Wasm app, not the interpreter.
Create an Error enum and convert lots of panics to Result and ?.
There are still panics for some things though. We'll see how it evolves.

General bugfixes. See individual commits.

This PR got the first 3 out of 142 Zig tests working. So not ready to put it into action yet. But there were enough changes that it seemed worth doing a PR.
I have all Zig tests working locally now. But perf is slightly slower.
So my plan was to discuss with people and see how we want to proceed.


VM Sidecar drop connections on large number of them

Is this the right place to submit this?

[X] This is not a security vulnerability or a crashing bug
[X] This is not a question about how to use Istio

Bug Description
We installed sidecar on a virtual machine with MySQL. Our architecture requires a large number of connections to the database (up to 10,000)
But when we reach 1700-2000 connections, we can no longer connect and get errors like this

2023-11-03T10:23:44.119694Z	critical	envoy backtrace external/envoy/source/server/backtrace.h:104	Caught Aborted, suspect faulting address 0x3dd000368cc	thread=223451

2023-11-03T10:23:44.119762Z	critical	envoy backtrace external/envoy/source/server/backtrace.h:91	Backtrace (use tools/stack_decode.py to get line numbers):	thread=223451

2023-11-03T10:23:44.119802Z	critical	envoy backtrace external/envoy/source/server/backtrace.h:92	Envoy version: a1ff538a63890e27dd2add4b2680ba8dc49293ca/1.27.1-dev/Clean/RELEASE/BoringSSL	thread=223451

2023-11-03T10:23:44.119551Z	critical	envoy assert external/envoy/source/common/network/socket_interface_impl.cc:72	assert failure: SOCKET_VALID(result.return_value_). Details: socket(2) failed, got error: Too many open filesthread=223446

ulimit -n
40000
Version
version 1.19.3
OS rocky linux 9

Additional Information
No response

There is a limit in your os, try to check ulimit -a

open files                          (-n) 40000

4000 limits all the process in the os

increase limit, error disappeared but problem not
ulimit -a
real-time non-blocking time  (microseconds, -R) unlimited
core file size              (blocks, -c) 0
data seg size               (kbytes, -d) unlimited
scheduling priority                 (-e) 0
file size                   (blocks, -f) unlimited
pending signals                     (-i) 58746
max locked memory           (kbytes, -l) 8192
max memory size             (kbytes, -m) unlimited
open files                          (-n) 524288
pipe size                (512 bytes, -p) 8
POSIX message queues         (bytes, -q) 819200
real-time priority                  (-r) 0
stack size                  (kbytes, -s) 8192
cpu time                   (seconds, -t) unlimited
max user processes                  (-u) 58746
virtual memory              (kbytes, -v) unlimited
file locks                          (-x) unlimited
[root@db1-test ~]# lsof | wc -l
347505
[root@db1-test ~]# netstat -atn|wc -l
1613

IIRC, in istio we set connection pool max connections to MAXUint32, so there is not connection number limit. But there is a max idle time per idle connection. So check if this idle timeout cause connection close or there is a connection number limit on MySQL setting


compile validate functions in config module

Coverage increased (+0.04%) to 86.697% when pulling 0e332e9ed574d39990b91500fa12443cc1e7d1fb on add-validate-to-config-mods into e97c5e7d0b8a9d6be77b35f39296aed87c7fe422 on main.


Initial SQL 4 CDS extension listing

Added listing for SQL 4 CDS extension to let users query data in Microsoft Dataverse/Dynamics 365 instances from Azure Data Studio.
I've included both a direct link to the vsix file and to the GitHub release page for the downloads, please let me know if I need to remove one of them.
More information about the extension is available at https://markcarrington.dev/2023/01/31/sql-4-cds-v7-1-released/#azure_data_studio

And it's up, thank you for your contribution!

Thank you! Do you have any instructions on how to update the List of Extensions wiki page, as the link from the bot 404s?

That link for our internal usage - I've went ahead and updated the page with your extension!


feat: Support for readOnly and writeOnly Open API keywords

Resolves #741

Codecov Report

Merging #1353 (48b7854) into master (67577ff) will decrease coverage by 0.11%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master    #1353      +/-   ##
==========================================
- Coverage   99.09%   98.98%   -0.12%
==========================================
  Files          83       83
  Lines        6316     6295      -21
  Branches     1088     1096       +8
==========================================
- Hits         6259     6231      -28
- Misses         29       33       +4
- Partials       28       31       +3

Flag
Coverage Δ

unittests
98.98% <100.00%> (-0.09%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

src/schemathesis/specs/openapi/converter.py
100.00% <100.00%> (ø)

src/schemathesis/specs/openapi/references.py
96.82% <100.00%> (+0.05%)
:arrow_up:

src/schemathesis/specs/openapi/schemas.py
99.55% <100.00%> (ø)

src/schemathesis/extra/pytest_plugin.py
98.23% <0.00%> (-1.77%)
:arrow_down:

src/schemathesis/cli/callbacks.py
98.33% <0.00%> (-1.67%)
:arrow_down:

src/schemathesis/specs/openapi/serialization.py
98.00% <0.00%> (-1.00%)
:arrow_down:

src/schemathesis/specs/openapi/loaders.py
98.31% <0.00%> (-0.85%)
:arrow_down:

...rc/schemathesis/specs/openapi/negative/__init__.py
94.11% <0.00%> (-0.17%)
:arrow_down:

src/schemathesis/serializers.py
98.18% <0.00%> (-0.11%)
:arrow_down:

src/schemathesis/runner/serialization.py
97.97% <0.00%> (-0.10%)
:arrow_down:

... and 18 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 67577ff...48b7854. Read the comment docs.


Feature Request - Edit Museum Donations

Any way to change the person associated with a museum donation?
If you use the editor and change a player character's name it changes all donations on the board to say the new name. In game, if you demolish a house (delete the player), the donation board now says "Anonymous" for the donations from that player. So I imagine it must link back to the Player ID per donation, and should be something we could point towards a different player character.
I would also imagine from here you could use this to add/delete donations, giving the ability to clear the museum and start donating again.

I've added a "Fill Museum" toolstrip item that fills the museum using the selected player as the donor. It will be in the next update, but if you'd like to get it to work sooner, then you can build your own version and try it out.

I'm closing this now, @SuperMarino. Hopefully I answered your question.


[Event Request] Table 1208 - new event on triggger validate field Applies-to Entry No.

Hi,
We need a new event on table 1208 trigger validate field Applies-to Entry No. :
...
CustLedgerEntry.CalcFields("Remaining Amount");
> new event
IsHandled := false;
OnBeforeAmountMustBePositiveErr(CustLedgerEntry, IsHandled);
if not IsHandled then
< new event
if CustLedgerEntry."Remaining Amount" <= 0 then
  error(AmountMustBePositiveErr);

"Transfer Date" := CustLedgerEntry."Due Date";
...

[IntegrationEvent(false, false)]
local procedure OnBeforeAmountMustBePositiveErr(var CustLedgerEntry: Record "Cust. Ledger Entry"; var IsHandled: Boolean)
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


Can not get the error messages back from the db.

Inside the generated controller, the  save function has this function call to insert a new record:
 basel.database.insert($scope.table_name, $scope.form);
and the update is:
basel.database.update($scope.table_name, $scope.form, {
        id: id
      });

How can I access an error message that is returned from the database.

resolved - I just have to add a variable to get the response
var msg = basel.database.update($scope.table_name, $scope.form, {
id: id
});

Use assync.


Add animal models evidence section

This PR:

adds the animal models evidence section
abstracts out a component for rendering allelic composition (used on TPP and EP

Related to https://github.com/opentargets/platform/issues/673.


brand-new generated app doesn't load on iOS 9.3

I recently updated corber from 1.1.6 to 1.2.8 and now my app won't load on iOS 9.3.
So in attempting to track down the issue, I created a new app using ember new with the latest stable build of ember-cli (3.1.4) and after the minimal updates to get the stock app to build (i.e., setting locationType to hash and rootURL to the empty string). The app works fine on 10.3 and 11.4, that is to say it shows the Ember welcome page. But when I load it in the 9.3 simulator it just shows a white screen and I can't see it in the Safari debugger. This is consistent with it failing very early. Unfortunately I'm at a loss as to the problem because nothing suspicious appears in the Xcode debugging console.
Has 9.3 support been discontinued? It seems that Cordova 4.5.4 is still supposed to support iOS 9.3.

It seems the problem was simply that I needed to explicitly mention Safari 9 in my config/targets.js.

@kbullaughey  could I please have a look at your config/targets.js?

The important part for getting my app working on Safari 9 was to have ios_saf >= 8 included in the list of browsers. When I know I'm building for iOS, I set this to be the only browser version specified in the browsers list.
Here's my config/targets.js file:
'use strict';

let browsers = [
  'last 1 Chrome versions',
  'last 1 Firefox versions',
  'last 1 Safari versions'
];

if (process.env.CORBER) {
  let platform = process.env.CORBER_PLATFORM || process.env.CORDOVA_PLATFORM || "ios";
  if (platform === "ios") {
    browsers = ['ios_saf >= 8'];
  }
}

module.exports = {
  browsers
};


Multiple "Servo" PWM Outputs Simultaneously

Hello,
Not sure if this is a real "issue" but it seems like the servo library will generate nice pulses for a single channel. As soon as I try to drive multiple channels, everything above channel one just chatter.
I figured maybe a single timer etc. is used for the pulse timing, so I added delays between calls to rc_servo_send_pulse_us. My pulses are standard RC 1-2ms. Even adding a 4ms delay between issuing 2ms pulses to 4 separate channels one after another, the problem still exists, although it is marginally better.
I saw issue #60, but it was unclear if there is a solution to this other then flashing new pru code?
It seems like there would be a better way to implement the servo library that does not need continuous calling in a Linux user space program to generate PWM pulses.
Any advice to drive 4 RC servos at once? Should I be able to call rc_servo_send_pulse_us for multiple servo channels one after another? Or could it be something to do with using the newest Kernel 4.14?
model:[TI_AM335x_BeagleBone_Black_RoboticsCape]
dogtag:[BeagleBoard.org Debian Image 2018-05-27]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2018.03-00002-gac9cce7c6a]:[location: dd MBR]
kernel:[4.14.40-ti-r50]
nodejs:[v6.14.2]
device-tree-override:[dtb=am335x-boneblack-roboticscape.dtb]
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-14-TI-00A0.dtbo]
pkg:[bb-cape-overlays]:[4.4.20180424.0-0rcnee0~stretch+20180424]
pkg:[bb-wl18xx-firmware]:[1.20180517-0rcnee0~stretch+20180517]
pkg:[firmware-ti-connectivity]:[20170823-1rcnee1~stretch+20180328]

Here is a summary of my code, I have a loop timer that I know loop execution is dominated by the 250us time delay, and I have tested the PWM function is only running once every 20ms (50Hz)... There is an array motorPwms[] that contains my PWM times in us ranging from 1000 to 2000.
For testing I'm driving a small servo, with a 12V DC supply to the board. The servo in CH1 works great, CH2 it half works, and anything above that is just random bouncing. I have a oscilloscope but have not probed the signals yet.
while (true){
  ...
  ...
  //Basically while(true) adds up running time and triggers this once per 1/50Hz (20ms)
  if ( lastPwmTime_ms > (1000.0/PWM_FREQ) ){
    lastPwmTime_ms = 0;
    for (int i=1; i<5; i++){
      rc_servo_send_pulse_us(i-1, motorPwms[i-1]);
      // I have tried adding the delay below, if helps somewhat.
      //std::this_thread::sleep_for(std::chrono::microseconds(2200));
      }
  }
  ...
  ...
std::this_thread::sleep_for(std::chrono::microseconds(250));
}

I don't know why I did not think to do this earlier, but running the  sudo rc_test_servos -f 50 -s 1 program performs as expected on all channels, so i guess there must be something with how I am using it in my code. I'll have to investigate further.
I'll try stripping my program of everything.

You can close this, I realized that somewhere between a windows UI and my c++ software, I was sending a rc_servo_send_pulse_us(0, 1500); That was trying to set all channels to neutral while I was also looping through channels 1-4...
Interestingly enough, channel 1 still works fine, and as you down the line, it affects it more. Must be how the code in the pru is setup.


License?

Hello! I was considering using this library for a project but I noticed there's not license provided anywhere in the repo. What license is this code given under? Thanks!

I intended to follow the same license as the libibverbs from rdma-core and noted this in the README.  The license situation of rdma-core is a bit confusing.
I just pushed an explicit MIT license to this repo, which should hopefully clear up any questions


Error on output reference

When we try to deploy powerdns just by following what's described on README.md, this happens:
$ helm repo add fsdrw08 https://fsdrw08.github.io/helm-charts/
$ helm install powerdns fsdrw08/powerdns
Error: template: powerdns/templates/NOTES.txt:8:39: executing "powerdns/templates/NOTES.txt" at <.Values.service.type>: wrong type for value; expected string; got interface {}

This problem seems to be related to the charts/powerdns/templates/NOTES.txt file since it has a wrong reference to the possible values.

Thanks for your fixing, chart updated


Adds disk-usage build sidecar to postsubmit/periodics

Issue #, if available:
Description of changes:
Adding to the rest of the jobs now that it has been working well on the presubmits since we enabled it last week.  I have verified all jobs have the trap /status/done.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm

/lgtm


formatIMGT.sh NullPointerException

Hi again,
I have downloaded the Alignments_Rel_3330.zip from https://github.com/ANHIG/IMGTHLA and put the hla_nom_g.txt in that folder. It seem to be working fine at first to create the new reference with formatIMGT.sh but then it crashes, the last part of the log is as follow:

Processing   [Y]  <<<<<<<<<<
nucRefAl:       Y01:01 genRefAl:       Y01:01
refGeneName on nuc and gen are same
Wrting to :     /proj/uppstore2018100/kourami-0.9.6/scripts/../custom_db/3.33.0/Y_gen.txt
Wrting to :     /proj/uppstore2018100/kourami-0.9.6/scripts/../custom_db/3.33.0/Y_nuc.txt
REF SEQ names differs :
(nuc):Y*01:01
(gen):Y
java.lang.NullPointerException
at Sequence.processBlock(Sequence.java:554)
at Sequence.(Sequence.java:498)
at MergeMSFs.mergeAndAdd(MergeMSFs.java:383)
at MergeMSFs.mergeAndAdd(MergeMSFs.java:372)
at MergeMSFs.merge(MergeMSFs.java:298)
at FormatIMGT.processGene(FormatIMGT.java:199)
at FormatIMGT.main(FormatIMGT.java:100)

Any idea what the problem might be?
Thank you in advance for the help!

And as a follow-up on that question, is there a way to include MICA, MICB, TAP1 and TAP2 in the output. These genes are of interest to us in the disease we are studying and it would be great if we could get information for all genes from the same software.

Thank you for looking into this. So irritating when they change format. I already had that problem another time this week.
I downloaded the new version, I had a problem with DRB5_gen.txt now (with IMGT/HLA version 3.34.0).

Processing   [DRB5]  <<<<<<<<<<
nucRefAl:       DRB101:01:01   genRefAl:       DRB501:01:01
refGeneName on nuc and gen are NOT same
Reference sequence entry [DRB5*01:01:01] is NOT found in nuc alignments.
Check the alignment files.

I fixed it by changing name on the allele in the DRB5_gen.txt file, since I don't care about DRB5 that worked for me. But for the future, with someone that does care, it can be good to look into.
Now I have a new reference, thank you so much!
I understand, it is not possible to do everything at once.

Hi,
I didnt bother checking what was new in 3.34.0 release. Addition of an allele of DRB5 in the release, DRB5_gen.txt has been newly added in the release. I understand you don't care about DRB5 sequences, but I suggest you to use 3.33.0 release for the time being rather than modifying allele names to get away with the error. I should be able to get to this early Nov along with a possiblity of supporting MICA/B and TAP1/2.

Is there any update on this or suggestions as to a work around?

Actually the DRB5_gen.txt that comes in the Alignments_Rel_3360.zip has the right name so everything works if you just comment out the part in scripts/formatIMGT.sh where it overwrites the file from the resources directory

Thank you @mmaiers-nmdp. scripts/formatIMGT.sh works with release 3.40.0, if I comment out the following lines (or remove the code block).
if [ ! -e "$resource_dir/DRB5_gen.txt" ];then
    echo "Missing DRB5_gen.txt in the resource directory. Please git pull or git clone"
    exit 1
# else
# cp $resource_dir/DRB5_gen.txt $input_msa/.
fi

Hi,@heewookl
i have try HLA Release 3.40.0 and HLA Release 3.41.0,they all go wrong with DRB5.
And i noticed that Release 3.40.0 and HLA Release 3.41.0 noly have DRB_nuc.txt,but with DRB1_gen.txt,DRB3_gen.txt,DRB4_gen.txt,DRB5_gen.txt 4 splitted gene.txt file.so it make scripts/formatIMGT.sh can not work with the new  release.
can you work with this problems?
Thank you

Hi again,
I have downloaded the Alignments_Rel_3330.zip from https://github.com/ANHIG/IMGTHLA and put the hla_nom_g.txt in that folder. It seem to be working fine at first to create the new reference with formatIMGT.sh but then it crashes, the last part of the log is as follow:

Processing   [Y]  <<<<<<<<<<
nucRefAl:       Y_01:01 genRefAl:       Y_01:01
refGeneName on nuc and gen are same
Wrting to :     /proj/uppstore2018100/kourami-0.9.6/scripts/../custom_db/3.33.0/Y_gen.txt
Wrting to :     /proj/uppstore2018100/kourami-0.9.6/scripts/../custom_db/3.33.0/Y_nuc.txt
REF SEQ names differs :
(nuc):Y*01:01
(gen):Y
java.lang.NullPointerException
at Sequence.processBlock(Sequence.java:554)
at Sequence.(Sequence.java:498)
at MergeMSFs.mergeAndAdd(MergeMSFs.java:383)
at MergeMSFs.mergeAndAdd(MergeMSFs.java:372)
at MergeMSFs.merge(MergeMSFs.java:298)
at FormatIMGT.processGene(FormatIMGT.java:199)
at FormatIMGT.main(FormatIMGT.java:100)

Any idea what the problem might be?
Thank you in advance for the help!

This problem happens when java cannot identifiy allele "Y*01:01" correctly due to ' * ' in the first base position in  file  Y_gene.txt,  script works after deleting the first alignment position base.

@freshfischer hi, thank you for your comment. Could you please explain what do you mean by "deleting the first alignment position base"? Am I getting it correctly below? Do I need to change the -1 gDNA position to 0 and remove asterisks/G and spaces that come before the pipe in the sequence coding lines starting with Y*...?
# file: Y_gen.txt
# date: 2020-10-15
# version: IPD-IMGT/HLA 3.42.0
# origin: http://hla.alleles.org/wmda/Y_gen.txt
# repository: https://raw.githubusercontent.com/ANHIG/IMGTHLA/Latest/alignments/Y_gen.t>
# author: Steven G. E. Marsh<EMAIL_ADDRESS>
 gDNA              -1
                    |
 Y*01:01           * | ATGGCGGTC GTGGCGCCCC GAACCCTCCT CCTGCTACTC TCGGGGGCCC TGGCCCTGAC>
 Y*02:01           G | --------- ---------- ---------- ---------- ---------- ---------->
 Y*03:01           * | --------- ---------- ---------- ---------- ---------- ---------->

@freshfischer hi, thank you for your comment. Could you please explain what do you mean by "deleting the first alignment position base"? Am I getting it correctly below? Do I need to change the -1 gDNA position to 0 and remove asterisks/G and spaces that come before the pipe in the sequence coding lines starting with Y*...?
# file: Y_gen.txt
# date: 2020-10-15
# version: IPD-IMGT/HLA 3.42.0
# origin: http://hla.alleles.org/wmda/Y_gen.txt
# repository: https://raw.githubusercontent.com/ANHIG/IMGTHLA/Latest/alignments/Y_gen.t>
# author: Steven G. E. Marsh<EMAIL_ADDRESS>
 gDNA              -1
                    |
 Y*01:01           * | ATGGCGGTC GTGGCGCCCC GAACCCTCCT CCTGCTACTC TCGGGGGCCC TGGCCCTGAC>
 Y*02:01           G | --------- ---------- ---------- ---------- ---------- ---------->
 Y*03:01           * | --------- ---------- ---------- ---------- ---------- ---------->

As for this problem, I just re-edit Y_gen.txt like this to make it identified by java:

Hi again,
I have downloaded the Alignments_Rel_3330.zip from https://github.com/ANHIG/IMGTHLA and put the hla_nom_g.txt in that folder. It seem to be working fine at first to create the new reference with formatIMGT.sh but then it crashes, the last part of the log is as follow:

Processing   [Y]  <<<<<<<<<<
nucRefAl:       Y_01:01 genRefAl:       Y_01:01
refGeneName on nuc and gen are same
Wrting to :     /proj/uppstore2018100/kourami-0.9.6/scripts/../custom_db/3.33.0/Y_gen.txt
Wrting to :     /proj/uppstore2018100/kourami-0.9.6/scripts/../custom_db/3.33.0/Y_nuc.txt
REF SEQ names differs :
(nuc):Y*01:01
(gen):Y
java.lang.NullPointerException
at Sequence.processBlock(Sequence.java:554)
at Sequence.(Sequence.java:498)
at MergeMSFs.mergeAndAdd(MergeMSFs.java:383)
at MergeMSFs.mergeAndAdd(MergeMSFs.java:372)
at MergeMSFs.merge(MergeMSFs.java:298)
at FormatIMGT.processGene(FormatIMGT.java:199)
at FormatIMGT.main(FormatIMGT.java:100)

Any idea what the problem might be?
Thank you in advance for the help!

This problem happens when java cannot identifiy allele "Y*01:01" correctly due to ' * ' in the first base position in file Y_gene.txt, script works after deleting the first alignment position base.

If you use the latest update of this repository (commit https://github.com/Kingsford-Group/kourami/commit/545c770e078f81fc9aee7685ce3914c8a5970911) instead of the latest release tag (v0.9.6), you don't get that particular error.


RPP test suite upgrade

Re-orders and buckets kernels by functionality-group for all tests
UnitTests dumps output images in respective folders based on the functionality group
PerformanceTests generates results based on functionality group
OpenCV output dumps for all UnitTests corrected to show images without padding
Profile option with rocprof integrated into all test suites
Update default performance measurement provided by the repository to 8 224x224 images
Support to test kernels individually or by range
Clean up unwanted or commented code
Modify tabs to spaces and formatting

@rrawther and @r-abishek I ran all of the tests and it seems that all of them run fine with these changes. Everything is very well organized now.


Running the code

I'm new to jupyter and wanted to know if i could run this using python. Also, is there a tutorial on how to use on live data? Wanted to use this to forecast on stocks

Seems i need to use an older version of tensorflow. Any recommendations ? I've tried using tf_upgrade_v2 but it doesnt provide a quick solution and i think i still need to replace some functions.


⚠ ClamAV has degraded performance

In 41b51b3, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 69 ms

Resolved: ClamAV performance has improved in 5f0c43a.


Multiple root dirs

I want to ag recursively in . and in ./vendor (vendor is in .gitignore)
So I want search command to be: ag pattern . ./vendor
I tried :GrepRoot but didn't find how to configure multiple root dirs.
Thanks!

Not 100% sure if that's correct, but try     let g:EasyGrepRoot="search:.git,.svn,.hg,.ctrlp"


Dockerfile Error

Hello
Seems Dockerfile have some issue:
Step 10/12 : RUN python main.py createdb
 ---> Running in 51c63db01b79
Traceback (most recent call last):
  File "main.py", line 41, in <module>
    main(sys.argv)
  File "main.py", line 26, in main
    from scoreboard import wsgi
  File "/opt/scoreboard/scoreboard/wsgi.py", line 18, in <module>
    main.load_config_file(app)
  File "/opt/scoreboard/scoreboard/main.py", line 59, in load_config_file
    app.config.from_object('config')
  File "/usr/local/lib/python2.7/dist-packages/flask/config.py", line 168, in from_object
    obj = import_string(obj)
  File "/usr/local/lib/python2.7/dist-packages/werkzeug/utils.py", line 443, in import_string
    sys.exc_info()[2])
  File "/usr/local/lib/python2.7/dist-packages/werkzeug/utils.py", line 418, in import_string
    __import__(import_name)
werkzeug.utils.ImportStringError: import_string() failed for 'config'. Possible reasons are:

- missing __init__.py in a package;
- package or module path not included in sys.path;
- duplicated package or module name taking precedence in sys.path;
- missing module, class, function or variable;

Debugged import:

- 'config' not found.

Original exception:

ImportError: No module named config
The command '/bin/sh -c python main.py createdb' returned a non-zero code: 1

Oh, that's unfortunate... looks like a refactoring and no longer shipping a config broke the Dockerfile.  That was a contribution, I'll have to take a look at getting it working again.


add standardbrawl to Format.ts

noticed this appearing in legality dictionaries in the bulk download data from 2024-01-27

Oh, did this actually replace historicbrawl?

Yep, this replaced historic brawl.


Make text-box-trim a draft feature

This now depends on https://github.com/web-platform-dx/web-features/pull/965.


Use executemany for db writes and fix #1196 sqlite too many variables

This PR

adds a test for and fixes #1196
improves performance according to timeit-based benchmarking, for SQLite,
PostgreSQL (psycopg) and MySQL (pymysql)
(see https://github.com/hjoukl/bench-sqlalchemy-executemany)

make lint & make test

Thank you very much @hjoukl!. We will review it soon.

Thanks @hjoukl! It looks great to me. I have one small comment.

Thanks again @hjoukl!.
This looks good to me! @roll


Installers: Add Base Installer Files Ahead Of JDK21 release.

DO NOT MERGE UNTIL CHECKSUMS ARE CORRECT
Add the initial base files which will require the usual filename, checksum and version number updates during the release.
Fixes #736

Checks fail, as the binary files are not present yet.

DO NOT MERGE UNTIL CHECKSUMS ARE CORRECTED FOR RELEASE

@steelhead31 we've started publishing the binaries now. Can you update the shasums?

/thaw


Linking CXX executable unit_test -> undefined reference error

Hi guys,
I;m getting the following issue:
[ 82%] Linking CXX executable eosio.system.wasm
[ 82%] Built target eosio.system.wasm
[100%] Linking CXX executable unit_test
CMakeFiles/unit_test.dir/eosio.msig_tests.cpp.o: In function eosio_msig_tests::propose_approve_execute::test_method()': **/home/jj/tmp/eosio.contracts/tests/eosio.msig_tests.cpp:(.text+0x1790): undefined reference to eosio::testing::base_tester::abi_serializer_max_time'**
CMakeFiles/unit_test.dir/eosio.msig_tests.cpp.o: In function eosio_msig_tests::propose_approve_unapprove::test_method()': /home/jj/tmp/eosio.contracts/tests/eosio.msig_tests.cpp:(.text+0x5210): undefined reference to eosio::testing::base_tester::abi_serializer_max_time'
CMakeFiles/unit_test.dir/eosio.msig_tests.cpp.o: In function eosio_msig_tests::propose_approve_by_two::test_method()': /home/jj/tmp/eosio.contracts/tests/eosio.msig_tests.cpp:(.text+0x861e): undefined reference to eosio::testing::base_tester::abi_serializer_max_time'
CMakeFiles/unit_test.dir/eosio.msig_tests.cpp.o: In function eosio_msig_tests::propose_with_wrong_requested_auth::test_method()': /home/jj/tmp/eosio.contracts/tests/eosio.msig_tests.cpp:(.text+0xc42e): undefined reference to eosio::testing::base_tester::abi_serializer_max_time'
CMakeFiles/unit_test.dir/eosio.msig_tests.cpp.o: In function eosio_msig_tests::big_transaction::test_method()': /home/jj/tmp/eosio.contracts/tests/eosio.msig_tests.cpp:(.text+0xf7d7): undefined reference to eosio::testing::base_tester::abi_serializer_max_time'
CMakeFiles/unit_test.dir/eosio.msig_tests.cpp.o:/home/jj/tmp/eosio.contracts/tests/eosio.msig_tests.cpp:(.text+0x157c2): more undefined references to eosio::testing::base_tester::abi_serializer_max_time' follow CMakeFiles/unit_test.dir/eosio.msig_tests.cpp.o: In function eosio::testing::contracts::util::exchange_wasm()':
/home/jj/tmp/eosio.contracts/tests/eosio.msig_tests.cpp:(.text._ZN5eosio7testing9contracts4util13exchange_wasmEv[_ZN5eosio7testing9contracts4util13exchange_wasmEv]+0x1a): undefined reference to `eosio::testing::read_wasm(char const*)'
Environment: Ubuntu 16.04
Regards,
jj

Update: Works on Ubuntu 18.04

Update II: It was required to delete manually
/usr/local/lib/libeosio_testing.a

There is a script in eos under the scripts folder named clean_old_install.sh this will remove the old install and eliminate linkage and inclusion conflicts.


include in vue.js component: how?

I'm trying to use teoria within a Single Page Application I'm (re)writing using Vue.js...
Any suggestion on how to proceed importing the various modules?

Its very easy.
Try it out on CodeSandbox!
<script>
import teoria from "teoria";
const note = teoria.note;
const int = teoria.interval;
export default {
  name: "HelloWorld",
  computed: {
    note() {
      return note("a4")
        .interval('m3')
        .chord('m#11').simple()
    }
  }
};
</script>


weights_only default flip for torch.load

🐛 Describe the bug
We've flipped the default for the weights_only argument in torch.load to True in pytorch/pytorch, see here for details + documentation and this is coming in torch 2.6.
This is expected to be quite a BC-breaking change, especially if any torch.load calls  in torchchat are not loading state_dicts of plain tensors.
We should make sure that all the torch.load calls in torchchat are still working.
For example, this one does not explicitly set weights_only so might now be failing since torchchat doesn't use pytorch nightlies in CI
cc @Jack-Khuu
Versions
main

Fixed in pin bump


Retry first before losing message when receiving ENOTCONN

I made another contribution in the context of the ENOTCONN error coming from our applications when we restart the Datadog agent. This new version attempts to retry before dropping a message.

Thanks will a new version be built and sent to rubygems?


Copy&paste code from a taurus-notebook to a local notebook should work...

If I code somethign link this on taurus:
imsave("blobs_binary.tif", binary, target="fileserver")

and then copy it to my local notebook, that uses skimage, this line would crash because it doesn't know what target="fileserver" is.

What would work though:
imsave("blobs_binary.tif", binary)
pft.sync_to_fileserver()

see #5

this works now. (I removed the target parameter)

there still are some open issues, (windows paths and saving to the current working directory), but they are discussed in issue #6.


Fix training data field

tests seem to fail only due to links to main branch where the example model is not updated yet...


couldn't see any result

I install thor following the instruction. But when I input
thor --amount 1000 --messages 100 ws://<IP_ADDRESS>:8888

I could'n see result, as the following picture show.

I know the reason. When I install nodejs I input
apt-get install nodejs

But it should be nodejs-legacy
when I installed nodejs-legacy, thor is ok


Add convenience method for getting xarray dims and coords

It would be nice to be able to easily fill in an xarrray array's dims and coords based on a sequence. Or even to be able to directly create an xarray DataArrray from the sequence which will then be filled in via MDA.
Basic approach could be something like this
from typing import List, Dict
def sequence_to_xarray_dims_coords(sequence: MDASequence) -> [List, Dict]:
    mapping = {"t": "time_plan", "c": "channels", "z": "z_plan", "p": "positions"}
    coords = {}
    dims = []
    for ax in axis_order:
        try:
            if ax == "c":
                coords['C'] = [c.config for c in sequence.channels]
            else:
                coords[ax.upper()] = list(getattr(sequence, mapping[ax]))
            dims.append(ax.upper())
        except AttributeError:
            pass
    dims.extend(['Y', "X"])
    return dims, coords

I'm afraid i feel like this is a bit out of scope for useq-schema.  It would make sense as a helper function in pymmcore-plus perhaps, but probably is best just implemented as a one-off function wherever you need it.  If you have one you use  routinely and want to contribute it at pymmcore-plus, please open a PR there.  Thanks!


Local testing issue with token type

Trying to use tokens lib for local testing like explained here I always get 401 Unauthorized:
https://github.com/zalando-stups/tokens#local-testing
This is because of:
https://github.com/zalando-stups/tokens/blob/master/src/main/java/org/zalando/stups/tokens/AccessTokenRefresher.java#L82
creates the AccessTokens with type Fixed instead of Bearer.
These AccessTokens will then be used here:
https://github.com/zalando-stups/stups-spring-oauth2-support/blob/master/stups-spring-oauth2-client/src/main/java/org/zalando/stups/oauth2/spring/client/StupsTokensAccessTokenProvider.java#L70
to create Spring DefaultOAuth2AccessToken with the AccessToken given type.
Spring will then use this type building the Authorization header, will result on a "Authorization: Fixed ..." instead of "Authorization: Bearer ...".
This will then result in a 401 Unauthorized on any local testing because our employee token (i.e. zign token) has "token_type": "Bearer" and not "Fixed".

Issue was fixed in org.zalando.stups:stups-spring-oauth2-client:1.0.3 instead (https://github.com/zalando-stups/stups-spring-oauth2-support/commit/1aa2f6e8d616c9e1961eb80b121ba5c30d153c7d).


Added implementation for transposed for enforceNotJagged.

see<EMAIL_ADDRESS>

Linux_64_32 failure appears unrelated.


Main into develop

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 90.44%. Comparing base (973c436) to head (61d0174).

Additional details and impacted files
@@           Coverage Diff            @@
##           develop     #441   +/-   ##
========================================
  Coverage    90.44%   90.44%
========================================
  Files          123      123
  Lines         8288     8288
  Branches       695      695
========================================
  Hits          7496     7496
  Misses         659      659
  Partials       133      133

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Check that EMBREE_ISPC_SUPPORT=ON in case of OSPRAY_USE_EXTERNAL_EMBREE=ON

Followup to https://github.com/ospray/OSPRay/issues/96 so that this part isn't forgotten.

Not forgotten: already fixed in devel c448989d ;-)


Add a description about timeout error for uploading text data

Uploading plain text data may happen user unrecognizable error if the data has large amount of data what is Korean and Japanese. This would be timed-out error in most cases. Thus, I believe we need explain this behavior and workaround for users.

@riwaida : Thanks for your contribution! The author(s) have been notified to review your proposed change.

How about this:

For some languages (for example Japanese or Korean), importing large amounts of text data can take very long or time out. Please consider to divide the uploaded data into text files of up to 20.000 lines each.

This revised update appears to be in master now, so we'll close the pull request. Thanks.

thanks @ktoliver, yes, this is the case; sorry for the conflict, we should have closed this earlier


Failed OSC update

Hi,
I was trying to search for some SNe (e.g., SN 2015bn, SN 2017egm, and SN 2018bsz) on the website, and it did not find the object. The picture is attached here.
Actually, I found out this issue a couple of days ago, and I generated a post somewhere that I think it was not here. In case you see the earlier post, I am reporting the same issue.

Yes you can see that only 20k SNe are in the database (there are usually 50k). I will investigate.

This is I believe fixed now, though I'm going to keep the issue open until we have a regular update that completes successfully. Thanks for bringing this to our attention!


Improve instruction for creating a source map upload URL

Description

The upload URL is critical to source maps. The current link to generating the URL is somewhat hidden, and not enough context is provided.
Support for a configuration file has been extended, and is now the preferred integration method.

Motivation and Context
Users were failing to correctly generate an upload URL.
The configuration file will improve integration success.
Types of Changes

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Documentation fix (typos, incorrect content, missing content, etc.)

This needs review by Backtrace engineering. I'll take it out of draft when I have their approval.

@lauramthomas - This is ready for final review and merge.


Idea: add can_panic macro

I find that when I use no_panic in a crate, I end up learning more about which of my functions can panic.
For me, this typically occurs when I forget that allocations can fail, so my function can't be annotated with no_panic.
In my workflow, after I think through this reasoning, I want to annotate the function with information that informs the reader that I did try to annotate with no_panic, but that my attempt failed because the function may actually panic.
To this end, I suggest a no-op annotation called can_panic as a complement to no_panic.

I would prefer not to build this into this crate. A "no-op annotation" is what comments are for (whether that be a doc comment or an ordinary comment).
Standard library documentation has a convention of using a # Panics section in rustdoc to indicate all the panicking conditions. https://rust-lang.github.io/api-guidelines/documentation.html#c-failure


test_wal_acceptor_async.py::test_restarts_under_load  fails in CI

First failure:
https://github.com/neondatabase/neon/runs/7020122796?check_suite_focus=true
Most recent failure is
https://github.com/neondatabase/neon/runs/7040698735?check_suite_focus=true

I reproduced it locally, it seems that new etcd walreceiver connection logic has some issues. This issue is likely appeared after https://github.com/neondatabase/neon/pull/1937
Logs from my local run: https://gist.github.com/petuhovskiy/47ebb450830482609c270a4ab7e720b8
Pay attention to test.log, it explains all safekeepers restarts to understand which safekeepers should be ready for connections.
What is going not well, judging by the pageserver logs:
Changed connection when shouldn't
At 2022-06-24T12:22:12.523952Z we killed sk-1, pageserver detected that and reconnected to the sk-2 – this is ok.
At 2022-06-24T12:22:14.605800Z nothing has changed, both sk-2 and sk-3 are alive and working well, but pageserver dropped connection to sk-2 and decided to reconnect to sk-3 – this is not ok, there is no point in doing that, should be fixed.
2022-06-24T12:22:12.523952Z  INFO walreceiver_connection{id=dd694b566f414d29b4e207b00964fa72/5cab7c64fc37ffa4aab8dc541bbac339}:safekeeper_handle_db: Connection closed regularly: connection closed
2022-06-24T12:22:12.524662Z  WARN wal_connection_manager{id=dd694b566f414d29b4e207b00964fa72/5cab7c64fc37ffa4aab8dc541bbac339}: WAL receiving task failed: walreceiver connection handling failure: connection closed
2022-06-24T12:22:13.560974Z  INFO wal_connection_manager{id=dd694b566f414d29b4e207b00964fa72/5cab7c64fc37ffa4aab8dc541bbac339}: Switching to new connection candidate: NewWalConnectionCandidate { safekeeper_id: NodeId(2), wal_producer_connstr: "host=<IP_ADDRESS> port=15007 options='-c ztimelineid=5cab7c64fc37ffa4aab8dc541bbac339 ztenantid=dd694b566f414d29b4e207b00964fa72'", reason: NoExistingConnection }
2022-06-24T12:22:13.561229Z  INFO walreceiver_connection{id=dd694b566f414d29b4e207b00964fa72/5cab7c64fc37ffa4aab8dc541bbac339}: connecting to host=<IP_ADDRESS> port=15007 options='-c ztimelineid=5cab7c64fc37ffa4aab8dc541bbac339 ztenantid=dd694b566f414d29b4e207b00964fa72'
2022-06-24T12:22:13.563821Z  INFO walreceiver_connection{id=dd694b566f414d29b4e207b00964fa72/5cab7c64fc37ffa4aab8dc541bbac339}:safekeeper_handle_db: connected!
2022-06-24T12:22:13.564235Z  INFO walreceiver_connection{id=dd694b566f414d29b4e207b00964fa72/5cab7c64fc37ffa4aab8dc541bbac339}: IdentifySystem { systemid:<PHONE_NUMBER>226409973, timeline: 1, xlogpos: 0/16DAF10, dbname: None }
2022-06-24T12:22:13.564430Z  INFO walreceiver_connection{id=dd694b566f414d29b4e207b00964fa72/5cab7c64fc37ffa4aab8dc541bbac339}: last_record_lsn 0/16D6E70 starting replication from 0/16D6E70, server is at 0/16DAF10...
2022-06-24T12:22:13.570150Z  INFO walreceiver_connection{id=dd694b566f414d29b4e207b00964fa72/5cab7c64fc37ffa4aab8dc541bbac339}: caught up at LSN 0/16DAF10
2022-06-24T12:22:13.614880Z  INFO GET /v1/tenant/dd694b566f414d29b4e207b00964fa72/timeline/5cab7c64fc37ffa4aab8dc541bbac339 200 OK
2022-06-24T12:22:14.605800Z  INFO wal_connection_manager{id=dd694b566f414d29b4e207b00964fa72/5cab7c64fc37ffa4aab8dc541bbac339}: Switching to new connection candidate: NewWalConnectionCandidate { safekeeper_id: NodeId(3), wal_producer_connstr: "host=<IP_ADDRESS> port=15009 options='-c ztimelineid=5cab7c64fc37ffa4aab8dc541bbac339 ztenantid=dd694b566f414d29b4e207b00964fa72'", reason: LaggingWal { current_lsn: 0/1783C70, new_lsn: 0/1789720, threshold: 10000 } }
2022-06-24T12:22:14.617749Z  INFO walreceiver_connection{id=dd694b566f414d29b4e207b00964fa72/5cab7c64fc37ffa4aab8dc541bbac339}:safekeeper_handle_db: Connection cancelled
2022-06-24T12:22:14.618645Z  INFO walreceiver_connection{id=dd694b566f414d29b4e207b00964fa72/5cab7c64fc37ffa4aab8dc541bbac339}: connecting to host=<IP_ADDRESS> port=15009 options='-c ztimelineid=5cab7c64fc37ffa4aab8dc541bbac339 ztenantid=dd694b566f414d29b4e207b00964fa72'
2022-06-24T12:22:14.621764Z  INFO walreceiver_connection{id=dd694b566f414d29b4e207b00964fa72/5cab7c64fc37ffa4aab8dc541bbac339}:safekeeper_handle_db: connected!
2022-06-24T12:22:14.622252Z  INFO walreceiver_connection{id=dd694b566f414d29b4e207b00964fa72/5cab7c64fc37ffa4aab8dc541bbac339}: IdentifySystem { systemid:<PHONE_NUMBER>226409973, timeline: 1, xlogpos: 0/178B578, dbname: None }
2022-06-24T12:22:14.622470Z  INFO walreceiver_connection{id=dd694b566f414d29b4e207b00964fa72/5cab7c64fc37ffa4aab8dc541bbac339}: last_record_lsn 0/1751C70 starting replication from 0/1751C70, server is at 0/178B578...
2022-06-24T12:22:15.097136Z  INFO walreceiver_connection{id=dd694b566f414d29b4e207b00964fa72/5cab7c64fc37ffa4aab8dc541bbac339}: caught up at LSN 0/178C280

After that the same happens several more times:

At 2022-06-24T12:22:15.570017Z pageserver dropped connection to sk-3 and reconnected to sk-2
At 2022-06-24T12:22:16.612473Z pageserver dropped connection to sk-2 and reconnected to sk-3

Trying to connect to dead safekeeper
After several more iterations, roughly at 2022-06-24 12:22:56.411, we started sk-2 and stopped sk-3. After that connection to sk-3 broke, but pageserver still tries to connect to sk-3 many times (unsuccessfully):
2022-06-24T12:22:56.467174Z  WARN walreceiver_connection{id=dd694b566f414d29b4e207b00964fa72/5cab7c64fc37ffa4aab8dc541bbac339}:safekeeper_handle_db: Connection aborted: error communicating with the server: Broken pipe (os error 32)
2022-06-24T12:22:56.470368Z  WARN wal_connection_manager{id=dd694b566f414d29b4e207b00964fa72/5cab7c64fc37ffa4aab8dc541bbac339}: WAL receiving task failed: walreceiver connection handling failure: connection closed
2022-06-24T12:22:56.470514Z  INFO wal_connection_manager{id=dd694b566f414d29b4e207b00964fa72/5cab7c64fc37ffa4aab8dc541bbac339}: Switching to new connection candidate: NewWalConnectionCandidate { safekeeper_id: NodeId(3), wal_producer_connstr: "host=<IP_ADDRESS> port=15009 options='-c ztimelineid=5cab7c64fc37ffa4aab8dc541bbac339 ztenantid=dd694b566f414d29b4e207b00964fa72'", reason: NoExistingConnection }
2022-06-24T12:22:56.470650Z  INFO walreceiver_connection{id=dd694b566f414d29b4e207b00964fa72/5cab7c64fc37ffa4aab8dc541bbac339}: connecting to host=<IP_ADDRESS> port=15009 options='-c ztimelineid=5cab7c64fc37ffa4aab8dc541bbac339 ztenantid=dd694b566f414d29b4e207b00964fa72'
2022-06-24T12:22:56.471057Z  WARN wal_connection_manager{id=dd694b566f414d29b4e207b00964fa72/5cab7c64fc37ffa4aab8dc541bbac339}: WAL receiving task failed: walreceiver connection handling failure: Failed to open walreceiver conection: error connecting to server: Connection refused (os error 111): Connection refused (os error 111)
2022-06-24T12:22:56.471189Z  INFO wal_connection_manager{id=dd694b566f414d29b4e207b00964fa72/5cab7c64fc37ffa4aab8dc541bbac339}: Switching to new connection candidate: NewWalConnectionCandidate { safekeeper_id: NodeId(3), wal_producer_connstr: "host=<IP_ADDRESS> port=15009 options='-c ztimelineid=5cab7c64fc37ffa4aab8dc541bbac339 ztenantid=dd694b566f414d29b4e207b00964fa72'", reason: NoExistingConnection }
2022-06-24T12:22:56.471313Z  INFO walreceiver_connection{id=dd694b566f414d29b4e207b00964fa72/5cab7c64fc37ffa4aab8dc541bbac339}: connecting to host=<IP_ADDRESS> port=15009 options='-c ztimelineid=5cab7c64fc37ffa4aab8dc541bbac339 ztenantid=dd694b566f414d29b4e207b00964fa72'
2022-06-24T12:22:56.471683Z  WARN wal_connection_manager{id=dd694b566f414d29b4e207b00964fa72/5cab7c64fc37ffa4aab8dc541bbac339}: WAL receiving task failed: walreceiver connection handling failure: Failed to open walreceiver conection: error connecting to server: Connection refused (os error 111): Connection refused (os error 111)
2022-06-24T12:22:56.471816Z  INFO wal_connection_manager{id=dd694b566f414d29b4e207b00964fa72/5cab7c64fc37ffa4aab8dc541bbac339}: Switching to new connection candidate: NewWalConnectionCandidate { safekeeper_id: NodeId(3), wal_producer_connstr: "host=<IP_ADDRESS> port=15009 options='-c ztimelineid=5cab7c64fc37ffa4aab8dc541bbac339 ztenantid=dd694b566f414d29b4e207b00964fa72'", reason: NoExistingConnection }
2022-06-24T12:22:56.471940Z  INFO walreceiver_connection{id=dd694b566f414d29b4e207b00964fa72/5cab7c64fc37ffa4aab8dc541bbac339}: connecting to host=<IP_ADDRESS> port=15009 options='-c ztimelineid=5cab7c64fc37ffa4aab8dc541bbac339 ztenantid=dd694b566f414d29b4e207b00964fa72'
2022-06-24T12:22:56.472269Z  WARN wal_connection_manager{id=dd694b566f414d29b4e207b00964fa72/5cab7c64fc37ffa4aab8dc541bbac339}: WAL receiving task failed: walreceiver connection handling failure: Failed to open walreceiver conection: error connecting to server: Connection refused (os error 111): Connection refused (os error 111)
2022-06-24T12:22:56.472399Z  INFO wal_connection_manager{id=dd694b566f414d29b4e207b00964fa72/5cab7c64fc37ffa4aab8dc541bbac339}: Switching to new connection candidate: NewWalConnectionCandidate { safekeeper_id: NodeId(3), wal_producer_connstr: "host=<IP_ADDRESS> port=15009 options='-c ztimelineid=5cab7c64fc37ffa4aab8dc541bbac339 ztenantid=dd694b566f414d29b4e207b00964fa72'", reason: NoExistingConnection }
2022-06-24T12:22:56.472523Z  INFO walreceiver_connection{id=dd694b566f414d29b4e207b00964fa72/5cab7c64fc37ffa4aab8dc541bbac339}: connecting to host=<IP_ADDRESS> port=15009 options='-c ztimelineid=5cab7c64fc37ffa4aab8dc541bbac339 ztenantid=dd694b566f414d29b4e207b00964fa72'
2022-06-24T12:22:56.472857Z  WARN wal_connection_manager{id=dd694b566f414d29b4e207b00964fa72/5cab7c64fc37ffa4aab8dc541bbac339}: WAL receiving task failed: walreceiver connection handling failure: Failed to open walreceiver conection: error connecting to server: Connection refused (os error 111): Connection refused (os error 111)
2022-06-24T12:22:56.473006Z  INFO wal_connection_manager{id=dd694b566f414d29b4e207b00964fa72/5cab7c64fc37ffa4aab8dc541bbac339}: Switching to new connection candidate: NewWalConnectionCandidate { safekeeper_id: NodeId(3), wal_producer_connstr: "host=<IP_ADDRESS> port=15009 options='-c ztimelineid=5cab7c64fc37ffa4aab8dc541bbac339 ztenantid=dd694b566f414d29b4e207b00964fa72'", reason: NoExistingConnection }
2022-06-24T12:22:56.473129Z  INFO walreceiver_connection{id=dd694b566f414d29b4e207b00964fa72/5cab7c64fc37ffa4aab8dc541bbac339}: connecting to host=<IP_ADDRESS> port=15009 options='-c ztimelineid=5cab7c64fc37ffa4aab8dc541bbac339 ztenantid=dd694b566f414d29b4e207b00964fa72'
2022-06-24T12:22:56.473607Z  WARN wal_connection_manager{id=dd694b566f414d29b4e207b00964fa72/5cab7c64fc37ffa4aab8dc541bbac339}: WAL receiving task failed: walreceiver connection handling failure: Failed to open walreceiver conection: error connecting to server: Connection refused (os error 111): Connection refused (os error 111)
2022-06-24T12:22:56.473743Z  INFO wal_connection_manager{id=dd694b566f414d29b4e207b00964fa72/5cab7c64fc37ffa4aab8dc541bbac339}: Switching to new connection candidate: NewWalConnectionCandidate { safekeeper_id: NodeId(3), wal_producer_connstr: "host=<IP_ADDRESS> port=15009 options='-c ztimelineid=5cab7c64fc37ffa4aab8dc541bbac339 ztenantid=dd694b566f414d29b4e207b00964fa72'", reason: NoExistingConnection }
2022-06-24T12:22:56.473868Z  INFO walreceiver_connection{id=dd694b566f414d29b4e207b00964fa72/5cab7c64fc37ffa4aab8dc541bbac339}: connecting to host=<IP_ADDRESS> port=15009 options='-c ztimelineid=5cab7c64fc37ffa4aab8dc541bbac339 ztenantid=dd694b566f414d29b4e207b00964fa72'
2022-06-24T12:22:56.474235Z  WARN wal_connection_manager{id=dd694b566f414d29b4e207b00964fa72/5cab7c64fc37ffa4aab8dc541bbac339}: WAL receiving task failed: walreceiver connection handling failure: Failed to open walreceiver conection: error connecting to server: Connection refused (os error 111): Connection refused (os error 111)
2022-06-24T12:22:56.474388Z  INFO wal_connection_manager{id=dd694b566f414d29b4e207b00964fa72/5cab7c64fc37ffa4aab8dc541bbac339}: Switching to new connection candidate: NewWalConnectionCandidate { safekeeper_id: NodeId(3), wal_producer_connstr: "host=<IP_ADDRESS> port=15009 options='-c ztimelineid=5cab7c64fc37ffa4aab8dc541bbac339 ztenantid=dd694b566f414d29b4e207b00964fa72'", reason: NoExistingConnection }
2022-06-24T12:22:56.474512Z  INFO walreceiver_connection{id=dd694b566f414d29b4e207b00964fa72/5cab7c64fc37ffa4aab8dc541bbac339}: connecting to host=<IP_ADDRESS> port=15009 options='-c ztimelineid=5cab7c64fc37ffa4aab8dc541bbac339 ztenantid=dd694b566f414d29b4e207b00964fa72'

The two issues here:

pageserver doesn't switch connection to other safekeepers
reconnection to the same safekeeper is very often, probably worth adding exponential backoff in case we don't switch safekeeper

I haven't looked at the https://github.com/neondatabase/neon/pull/1937 in details yet, will try to find issues in its code now.
cc @SomeoneToIgnore

Thank you for the detailed explanation and looking into this generally.

At 2022-06-24T12:22:14.605800Z nothing has changed, both sk-2 and sk-3 are alive and working well, but pageserver dropped connection to sk-2 and decided to reconnect to sk-3 – this is not ok, there is no point in doing that, should be fixed.

This reconnect should be fixed by the bigger WAL threshold, presumably? The log mention why did we reconnect in this case:

reason: LaggingWal { current_lsn: 0/1783C70, new_lsn: 0/1789720, threshold: 10000 } }

what would be a reasonable value for such?
The latter issue is indeed a bug, I can work on fixing that.


Move preprocessing from the diagnostic script to the backend

Is there a list of functionalities available in the preprocessor and instructions to use them?
Any option for geographical subsetting? Any further options than those listed in the developer_guide2 (levels, regridding, masking, multi-model)?
Thanks
Example from perfmetrics_CMIP5.yml:
preprocessors:
pp850:
extract_levels:
levels: 85000
scheme: linear
regrid:
target_grid: ERA-Interim
scheme: linear
mask_fillvalues:
threshold_fraction: 0.95
multi_model_statistics:
span: overlap
statistics: [mean, median]
exclude: [reference_model, alternative_model]

Unfortunately this is not working in the online documentation yet, but you can have a look at __all__ in the esmvaltool.preprocessor module, that should give you a good impression of currently implemented functionality.
Regarding geographical subsetting: I think the function extract_region can be used to select a region by latitude/longitude, but it's untested as far as I know and apart from that there isn't much so far.

OK, I will try it. I would keep an (this?) issue open to keep track of what becomes available and what would be needed by diagnostic developers. A few words of guidance on the above functionalities would be great - is there a documentation somewhere?

Yes, the documentation is available on readthedocs, the code documentation should be available under 'ESMValTool Code API Documentation', but it's broken at the moment, see issue #135. I think we need to fix this soon, before the workshop in June.

@valeriupredoi can you help here? If I remember correctly, you implemented a very first version of this but we haven't test it so far.

@mattiarighi @earnone yes, this is in fact my "masterpiece" from back last year in May -- it needs a LOT of polishing so I'll have a look at it today, so if you guys would like to give me some more feedback as to how it should work it'd be much appreciated :)

Time and space operation were not originally planned for this release.
The reason is that they cover a huge number of possible options (extraction, average, weighted average, annual + seasonal cycle, climatologies, interannual variability etc.) and the gain of having them in the preprocessor rather than in the diags is relatively limited (both in time of CPU and memory).
But if you think it might be useful to have some of this functionalities in the preprocessor, feel free to go ahead and implement/test them.

@mattiarighi -- sounds about right -- if the message is for me then the answer is I'd rather wait for this to be discussed first and decided upon what's needed in the preprocessor, I am not willing to start coding up stuff that will be deleted in the future :grinning: but I will have a look at the extract_region nonetheless since it's there anyway

As I said, this was not planned for this release so it should not be high priority, unless @earnone thinks it is absolutely required for his diag.

@valeriupredoi @mattiarighi, thanks, sure I see it is better to include those functionalities when nicely polished. I started moving preprocessing from scripts to v2.0 preproc because I understood that was the message but we can surely go back to the current CDO preprocessing we do and wait. I may keep the extract_region in a namelist to do further tests and then update you @valeriupredoi.  Can you confirm levels, regridding, masking and multi-model preproc functionalities are ok or should we wait using those too?

I can confirm that those 4 functionalities are implemented and quite extensively tested, mostly in the framework of namelist_perfmetrics_CMIP5.yml.
Additional testing with other namelists/diags is of course welcome, as not all options have been tried yet (e.g., regridding schemes other than linear).

I guess this can be closed.
@earnone please open another issue if you have specific problems with any of the above functionalities.


SHA bump for OSAD to match kilo as of 30/07/2015

This bump addresses the issue found in #299

:+1:

:+1:


Fix apc battery state

About the PR

closes #15564
Battery Power is not updating properly though.
Media

Changelog

:cl:

fix: APCs now show correct charge and state

does this fix #15545 too

its the same thing actually


Card - openIcon & closeIcon properties not passed correctly

Problem description
For the Card component the openIcon and closeIcon properties of CardHeader are not passed correctly. Also, look here and here.

Versions

Material-UI: 0.16.1
React: 15.3.2
Browser: Chrome latest (54), Mac

Here is code to reproduce the issue
<Card>
 <CardHeader
    showExpandableButton
    openIcon={<div> Open </div>} // not passed correctly
    closeIcon={<div> Close </div>} // not passed correctly
  />
  <CardText>
    Test
  </CardText>
  <CardActions>
     <IconButton iconClassName="fa fa-trash"/>
   </CardActions>
</Card>

Just updated to 0.16.4 and it works, great!


Update community-best-practices-for-app-performance.md

Added deleting in a list after a loop.

@dominiquemunten Thank you very much for your contribution. Would you mind signing the Contributor License Agreement?

Hi @dominiquemunten,
Thanks again for your contribution. The content has been verified and I am merging the PR.
Kind regards,
Yiyun


flutter build linux not giving runnable file for linux

flutter build linux not giving runnable file like apk for linux

Hi @msarkrish
Please follow up on https://github.com/flutter/flutter/issues/38478 (as it is said in your log)
I'm closing the current one as duplicate.
If you disagree please write in the comments and I will reopen it.
Thank you

Hi @VladyslavBondarenko then i have 2 questions 1). i can't install my desktop application in other system?  2). i can run my desktop application only in my system only.

@msarkrish
I'm not sure about this, I've not used flutter for desktop (and currently using only windows on my laptop)
Please see https://flutter.dev/community for resources and asking questions like these

@VladyslavBondarenko ok brother, in windows whether flutter desktop give runnable file for windows platform with flutter build windows?

@msarkrish
For now AFAIK only debug mode is provided for windows. To run my .exe application on another computer I need to copy the entire 'Runner' folder, which includes the .exe file together with all necessary assets

Debug mode also works for Linux, see https://github.com/flutter/flutter/wiki/Desktop-shells
The executable is in a subdirectory.


Bug: Bot missing permissions

Sometimes, a bot with Administrator privileges still does not have enough permissions to update or delete items (roles, categories, channels, etc.). This seems to be either a bug on Discord's end or some missing detail somewhere in the permission's logic.
Potential problems and solutions
Was trying to update/delete the role Disma
The bot cannot delete it's own role, even if it has the MANAGE_ROLE permission (good thing I guess?), which means this is not a bug.

It seems that the order of roles is important to determine access to roles and channels management. If two roles have the MANAGE_ROLES permission, the second one will not be able to edit the first one.
Also, if a role has the ADMINISTRATOR permission and the bot only has MANAGE_ROLES and MANAGE_CHANNELS, the bot won't be able to manage that role.
Therefore, the bot must either have higher permissions than all the roles, have a higher order is same permissions, or not include the more priviledged roles in the configuration (with extra_items: KEEP to prevent deletion attempts).


Release v5.0.0-alpha2.

Preview: https://deploy-preview-31748--twbs-bootstrap.netlify.app/

The JS part looks good to me 👍 too bad we didn't land any new features but I hope it'll happen in our next alpha 🙏