Jose Celano

Instead of removing the token from the logs we could add a new authentication method. We could use a [bearer token authentication scheme](https://datatracker.ietf.org/doc/html/rfc6750). We are using it in the Index,...

Relates to: https://github.com/torrust/torrust-tracker/pull/814#issuecomment-2093272796 What I wanted to do is to include the bytes in the response in the error message. For example, this is a normal response: ```output cargo run...

> When exactly does it panic? > > Also, on a side note, I’m planning to upload a new aquatic release to crates.io very soon, if that is what is...

> I don’t get it, does it still panic? If it does, where exactly? Parsing IPs and ports shouldn’t panic either, due to chunks_exact. Hi @greatest-ape Yes, you are right....

> Anyway, a new aquatic_udp_protocol is on crates.io now. I actually added tests of parsing requests from various length byte vectors and could not produce a panic. OK, It looks...

> It is a new major version as to speak, with Rust-flavored semver :-) OK, thank you @greatest-ape! I guess you mean this:  I didn't know this particular behavior....

Hi @mickvandijke what is the status of this PR? Maybe: - Rebase - And https://github.com/torrust/torrust-tracker/issues/646 By the way, why did you use [deepsize](https://github.com/Aeledfyr/deepsize/)? I'm just curious, I've found this one...

Hi @mickvandijke I'm closing this PR: - [The Dashmap was already implemented](https://github.com/torrust/torrust-tracker/blob/develop/packages/torrent-repository/src/repository/dash_map_mutex_std.rs). - The [memory limit should be implemented for all repos](https://github.com/torrust/torrust-tracker/discussions/789) or [not implemented at all](https://github.com/torrust/torrust-tracker/discussions/825).

Finally, you can execute it with: ```bash cargo run --bin e2e_tests_runner -- --config-toml-path "./share/default/config/tracker.e2e.container.sqlite3.toml" ``` Or: ```bash TORRUST_TRACKER_CONFIG_TOML_PATH="./share/default/config/tracker.e2e.container.sqlite3.toml" cargo run --bin e2e_tests_runner ``` Or: ```bash TORRUST_TRACKER_CONFIG_TOML=$(cat "./share/default/config/tracker.e2e.container.sqlite3.toml") cargo run --bin...

Hi, @WarmBeer I think an explicit limit is a nice feature but it would also be good to set a no-limit option so the tracker can consume as much memory...