You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 1, 2023. It is now read-only.
Note: a patch is available for time, which we depend on via chrono (it suffers twice from the same API usage error). However, chrono itself does not yet have a public patch.
AB#39994083
The text was updated successfully, but these errors were encountered:
Closes#1366 and incidentally closes#1266.
Requires using a not-yet-merged modification to the latest version of `appinsights-rs` to remove the `time` feature from the `chrono` dependency (dmolokanov/appinsights-rs#280).
There are changes to use the new (tokio-based) version of `appinsights-rs`, e.g., made `set_appinsights_clients` async to ensure it is always called from an async context, since the constructor for appinsights now invokes `Tokio::spawn`.
ghost
locked as resolved and limited conversation to collaborators
Oct 7, 2022
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The
chrono
andtime
crates share a possible segfault related to thread-unsafe use ofgetenv()
andsetenv()
.time
chrono
Ensure these are both fixed upstream.
Note: a patch is available for
time
, which we depend on viachrono
(it suffers twice from the same API usage error). However,chrono
itself does not yet have a public patch.AB#39994083
The text was updated successfully, but these errors were encountered: