Spencer Bartholomew

Rust Docker image documentation needs to be updated

1

The example code for the Rust Docker image documentation should be updated to something like this. The previous example is out of date. ```Dockerfile FROM rust:1.64 AS builder COPY ....

This repo needs to be archived and marked as deprecated

4

Too many sites are recommending this repo but this repo has major security issues. It needs to be fixed or taken down.

deprecate this crate

2

This crate needs to be deprecated #109 #107 #106

can't handle null values if they are present

2

 Json deserializing breaks when "aud" is null like in this case. Here's the error message ``` Error(Json(Error("duplicate field `aud`", line: 1, column: 257))) ```...

Flashing issue with information window when hovering over functions, structs, etc.

4

  The information window alternates between open and closed at various frequencies when hovering over functions, structs, etc. I...

 On the left is vscode. On the right is zed. It appears that the syntax highlighting ends after a non-traditional use case.

Question: is there a way to set up automatic performance monitoring transaction for each incoming request for Tonic

4

Is there a way to do something similar like this ```Rust let layer = tower::ServiceBuilder::new() .layer(sentry_tower::NewSentryLayer::::new_from_top()) .layer(sentry_tower::SentryHttpLayer::with_transaction()); ``` but for Tonic? The description for sentry_tower::SentryHttpLayer::with_transaction() is `Creates a new Layer...

Currently there is a server api [`UpdateSubscriptions`](https://docs.livekit.io/reference/server/server-apis/#updatesubscriptions) that accepts a single `identity`, a list of `track_sids`, and a boolean `subscribe` value. It would dramatically improve our use case if this...

[pgRouting](https://github.com/pgRouting/pgrouting) extension would be huge for those of us building goespatial and graph based applications. Thanks for your hard work and building an amazing system!

backoff is unmaintained https://rustsec.org/advisories/RUSTSEC-2025-0012 and it is recommended to use backon #264. This is a breaking change.