Grvzard

[https://github.com/Grvzard/Xray-core/tree/fix-stats](https://github.com/Grvzard/Xray-core/tree/fix-stats) I don't think it's wise to use the built-in user management stuff, but check this out if it helps.

> 1. Write Everything Twice, then de-duplicate if more than three times Totally agree. > I think current code is ok I think xray-core is a tool for creating new...

The issue has been fixed in the main branch, but it hasn't been released yet. Related PR: #19685

a temporary workaround is to specify the `batch_size` explicitly in `Model.fit()`.

I think a better workaround is to validate the shape of the mask in keras.

> because it doesn't account for the broadcasting (i.e. it gives a value of 2 in the above example, when it should be 2 * 3 * 4). broadcasting from...

> I'm getting a build error on main after the Sentry option PR https://github.com/cloudflare/pingora/pull/410 https://github.com/cloudflare/pingora/pull/399#issuecomment-2398927180

That's the usage in Keras 2. In Keras 3, you can refer to: https://github.com/keras-team/keras/blob/933579d3c4a585f236982d05d3a74921f9567415/keras/src/layers/rnn/rnn.py#L105-L110

I just checked the commit https://github.com/cloudflare/pingora/commit/ab1b717bf587723c1c537d6549a8f8096f0900d4. There is an oversight causing it to fail to compile in release mode: https://github.com/cloudflare/pingora/blob/ab1b717bf587723c1c537d6549a8f8096f0900d4/pingora-core/src/server/mod.rs#L121-L122 should be ``` #[cfg(all(not(debug_assertions), feature = "sentry"))] sentry::capture_error(&e); ``` You...