Gkirito

> @Ehco1996 > > 有开新架构的计划，暂定 Xray-next > > VLESS 协议结构请搜索“VLESS BETA” > > VLESS 正式版计划扔掉 pb，五个指令：tun、xudp、tcp、xtls、smux（或者 xudp 也靠 smux） 期待，请问有大致的时间规划么，正式版大概会在多久后发布

轮训接口吗，会不会被训坏

> > 轮训接口吗，会不会被训坏 > > 不会的，轮训其实这个场景下的标准做法 @Gkirito 是不是可以上个websocket，轮询出结果后，通知前端充值完成

Hh， 好的 On Apr 23, 2021, 13:25 +0800, Ehco ***@***.***>, wrote: > 这样需要部署websocket服务器,简单场景下没必要增加复杂度了 > > Gkirito ***@***.***> 于2021年4月23日周五 下午1:21写道： > > > 轮训接口吗，会不会被训坏 > > > > 不会的，轮训其实这个场景下的标准做法 @Gkirito >...

建议开通邮箱，让用户忘记密码操作

I'm so glad you're back and I've so appreciated your contribution. Can we contribute something to this repository? E.g I hope code block support to render mermaid. Not only use...

> Because there is no reliable way to detect if `werkzeug` is being used, I think we should remove this [condition](https://github.com/viniciuschiele/flask-apscheduler/blob/5f878c41417824a4f37b353cb4b22973a81746f2/flask_apscheduler/scheduler.py#L97) and recommend users to disable Flask reloader (`app.run(use_reloader=False)` or...

Is there anyone who can review this PR? We really need support ipv6 to deploy the indexer process in our AWS EKS which uses the IPV6 network without IPV4 support.

> `cargo fmt && cargo xclippy -D warnings` failed, can you fix that? > Also can you paste more in the test plan section, like output from both ipv4 and...

## Test for ipv6 ### Log ```bash sui-indexer --db-url "postgres://postgres:@127.0.0.1:5432/sui_full_node_indexer" --rpc-client-url "https://sui-testnet-wave3.coming.chat:443" --rpc-server-worker --rpc-server-url "::" 2023-04-20T18:56:57.287762Z INFO sui_indexer: Parsed indexer config: IndexerConfig { db_url: "postgres://postgres:@127.0.0.1:5432/sui_full_node_indexer", rpc_client_url: "https://sui-testnet-wave3.coming.chat:443", client_metric_host: "0.0.0.0", client_metric_port:...