Jose Celano

I made it work by commenting on the TimeoutAcceptor. It's a custom acceptor that introduces timeouts for the first client request after opening the HTTP connection. ```rust match tls {...

ACK 5d9e068f4460119c749ca164ca49d184d6e7659e

> Hi @josecelano. > > > Maybe we could enable this automatically when the **host** is `localhost` or `127.0.0.1` to make the setup easier. > > Which is the **host**...

I'm closing this because the Index could be behind a reverse proxy so it might not be easy to detect if we are running in a development environment. I will...

Reminder: check if we need to create and drop the weak pointer (`weak_tracker_statistics_importer.upgrade`). Maybe we can always use the same because now it's executed more often. In the first implementation...

I've added the error to the output but it's not very useful: ``` ---- e2e::web::api::v1::contexts::category::contract::it_should_not_allow_adding_empty_categories stdout ---- thread 'e2e::web::api::v1::contexts::category::contract::it_should_not_allow_adding_empty_categories' panicked at tests/environments/shared.rs:21:25: Test server is not running on localhost:3001. Error:...

The [PR](https://github.com/torrust/torrust-index/pull/687) didn't work.

I've temporarily moved the execution of E2E tests to a new workflow. See https://github.com/torrust/torrust-index/pull/736. Surprisingly, they are [now passing](https://github.com/torrust/torrust-index/actions/workflows/e2e.yaml). There must be a problem with containers after executing E2E tests...

I think I'm also having problems with nested spawned tasks, but I have not been able to reproduce it with a minimal example yet. I'm trying to refactor this [PR](https://github.com/torrust/torrust-tracker/pull/1142)...

I've created a test repo to play with different configurations: https://github.com/josecelano/tracing-test-bug