Tim Bussmann

btw. I raised an issue for that here: https://github.com/Particular/GitHubReleaseNotes/issues/31, so you might want to close this issue @danielmarbach

 (btw. just came across this one more time today)

Another case where the current base64 encoding makes external integration scenarios more difficult: https://discuss.particular.net/t/aws-ses-integration-with-native-messages/3167

> Another option would be to not include the PR if the PR mentions an issue with the same milestone (funky logic though) yeah that idea came up in yesterdays...

> Well, there can be a config switch so that the current behavior is default but you can opt in to filter out the PRs. good enough imho

We also ran into the same issue. [`samplingDecision.Drop`](https://github.com/open-telemetry/opentelemetry-dotnet/blob/main/src/OpenTelemetry/Trace/SamplingDecision.cs#L30) states: > The activity will be created but not recorded. which is not happening currently. As @ghelyar mentioned, it kinda looks like...

Thanks for the hint with the Rust executor @Riolku , that helped to get me started. I'm struggling to grasp how `get_versionable_commands` is working, is there any documentation that you...

I've started a first draft via https://github.com/DMOJ/judge-server/pull/1064, help and feedback are very welcome.

so are you currently using a workaround to access those information or is some feature potentially blocked by this?

slightly adjusted the title to not limit any added metadata to a specific stage.