-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
relay.span-normalization.allowed_hosts
global options failed to deserialized
#3936
Comments
Figured gonna do it this weekend and brace myself to use nightly... |
jjbayer
added a commit
that referenced
this issue
Sep 3, 2024
…spans (#3939) Closes #3936 ### Legal Boilerplate Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms. --------- Co-authored-by: Joris Bayer <joris.bayer@sentry.io>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I implemented this a while back: #3813
On 24.8.0 (self-hosted), it turns out
String
or&str
can't be properly deserialized intoHost
type. There's this upstream issue on theurl
crate: servo/rust-url#543 and servo/rust-url#895.The solution is quite simple, we'll just have to override the
deserialize
method forHost
specifically. We'll just need to implement a custom deserializer function and change this specific line:relay/relay-dynamic-config/src/global.rs
Line 223 in 92c008e
I made a working repro:
Cargo.toml
src/main.rs
Might work on this later this weekend, or the next weekend. I can't work on this right now since I got work to do. Also I guess I need to write few tests here and there for deserializing the new global option I made 😒
The text was updated successfully, but these errors were encountered: