John Niang

@guycall , I found https://github.com/spring-projects/spring-security/issues/13305 was closed by . And the feature was released into [6.4.0-RC1](https://github.com/spring-projects/spring-security/releases/tag/6.4.0-RC1).

Hi @rwinch , thank you for your contribution of Passkeys support! Reactive support was introduced in , and Webauthn project has implemented Non-Blocking API in . Can we add reactive...

I encountered the same issue after I connected to MySQL container terminal and inputed `exit` command to exit.

I still reproduced this issue in version `1.10.27-lts`. I'm going to reopen this issue. /reopen

建议按 `F12` 后打开控制台看看实际的网络请求，另外，建议提供完整的日志。 /triage needs-information

This issue should be partially fixed by . Currently, we haven't found a deep reason why extension client was blocked.

After upgrading to Halo 2.20.18, we received the error logs below: ```java 2025-04-05T14:04:52.074+08:00 INFO 7 --- [reactor-tcp-epoll-2] i.a.r.mysql.client.ReactorNettyClient : Response: OkMessage{isEndOfRows=true, affectedRows=0, lastInsertId=0, serverStatuses=22, warnings=1, information='', systemVariables={}}, reports 1 warning(s)...

/remove-triage not-producible /kind bug /area editor /ping @halo-dev/sig-halo-console /milestone 2.20.x

可能的原因是：数据库连接的空闲超时时间和 Halo 侧配置的有冲突。如果你没有配置 `spring.r2dbc.pool.max-idle-time` 的话，则默认为 30 分钟。建议检查一下相关的数据库配置。 /triage needs-information

从 [Aliyun 官方 RDS MySQL 文档](https://help.aliyun.com/zh/rds/apsaradb-rds-for-mysql/parameters-for-apsaradb-rds-instances-that-run-mysql-8-0)看，默认系统配置如下：`interaction_timeout = 7200s` 和 `wait_timeout = 86400s`。 不过还是建议你登录 RDS 查询一下 MySQL 服务器实际运行参数。