- May 03, 2024
-
-
Signed-off-by:
strawberry <strawberry@puppygock.gay>
-
Signed-off-by:
strawberry <strawberry@puppygock.gay>
-
Signed-off-by:
Jason Volk <jason@zemos.net>
-
This way all 4 major configurations are linted.
-
-
In particular this fixes `cargo build --all-features`.
-
-
Signed-off-by:
Jason Volk <jason@zemos.net>
-
Signed-off-by:
Jason Volk <jason@zemos.net>
-
Signed-off-by:
Jason Volk <jason@zemos.net>
-
-
Hardcoding the output path to something in CWD is a pain if you're running conduwuit through systemd or similar. Also made the error message when it's unable to create the output file a little more friendly.
-
Previously we were dropping the flush guard early, possibly causing samples to be lost on exit.
-
The previous hardcoded filter `trace,h2=off` isn't appropriate in all cases, it's better to have this be configurable.
-
Previously, enabling the `tracing_flame` or `allow_jaeger` options would prevent any logs from being written to stdout. In addition, enabling the `allow_jaeger` option would inhibit the `tracing_flame` option. Now that we have a way to use separate tracing filters with different layers, we can enable all three at the same time without issues. This commit also prevents the `debug log_level` command from modifying the `tracing-flame` filter. This was supported previously, but I don't think it's something that you would ever want to do intentionally. Now that we have both the normal log filter and the `tracing-flame` filter enabled at the same time, we want to `debug log_level` to only modify the normal filter.
-
Signed-off-by:
strawberry <strawberry@puppygock.gay>
-
imagine this SQL query but in conduwuit: select * from users_in_public_rooms where user_id like '%user_id%'; Signed-off-by:
strawberry <strawberry@puppygock.gay>
-
Signed-off-by:
strawberry <strawberry@puppygock.gay>
-
Signed-off-by:
strawberry <strawberry@puppygock.gay>
-
Signed-off-by:
Jason Volk <jason@zemos.net>
-
Signed-off-by:
Jason Volk <jason@zemos.net>
-
Signed-off-by:
Jason Volk <jason@zemos.net>
-
Signed-off-by:
strawberry <strawberry@puppygock.gay>
-
Signed-off-by:
strawberry <strawberry@puppygock.gay>
-
Signed-off-by:
strawberry <strawberry@puppygock.gay>
-
Signed-off-by:
strawberry <strawberry@puppygock.gay>
-
Signed-off-by:
strawberry <strawberry@puppygock.gay>
-
Signed-off-by:
strawberry <strawberry@puppygock.gay>
-
This turned out to be quite hairy, mostly because we need to apply the config's log level filter to the actual logs (stdout and, optionally sentry), but do not want to filter out the tokio tracing events needed by the console_subscriber. I hit several edge cases in tracing getting this to work, and we now depend on a git version of tracing with a backported patch :(
-
- Apr 26, 2024
-
-
Signed-off-by:
strawberry <strawberry@puppygock.gay>
-
Signed-off-by:
strawberry <strawberry@puppygock.gay>
-
Signed-off-by:
Jason Volk <jason@zemos.net>
-
Signed-off-by:
strawberry <strawberry@puppygock.gay>
-
Signed-off-by:
strawberry <strawberry@puppygock.gay>
-
Signed-off-by:
strawberry <strawberry@puppygock.gay>
-
Signed-off-by:
Jason Volk <jason@zemos.net>
-
Signed-off-by:
strawberry <strawberry@puppygock.gay>
-
Signed-off-by:
strawberry <strawberry@puppygock.gay>
-
Signed-off-by:
strawberry <strawberry@puppygock.gay>
-
All images should be generating correctly with parallelism and Docker manifests, and should output the end of the CI testing errors in a job summary box when the test fails. When the test succeeds you get a big
then at the end of the Docker publish it should include the `docker pull` commands for both Docker Hub and GHCR registries to make those pesky Docker users lives easier!
-