Jonathan KelleyandEvan Almloff
e43bf05b69
* wip * wip: basic telemetry * fix merge * keep errors for telemetry * fix upload when queued events are empty * add per session id and keep track of build timing * keep track of what commands are run * capture panics * keep track of panics * better path stripping * better tracing error telemetry * only sync every week and check settings before sending any telemetry * keep track of the args passed to commands * anonymize commands * more error tolerant * wip * wip * wip * merge cnflict * other merg conflict * migrate everything from telemetry to logging * update docs * wip... about to merge trace controller * lil bit more refactor to clean up tracer * more performant log writer * cleanup ci detecting * wire up to posthog * re-uploads work * yoink out the anon from each file * cleanup sig * lil bit cleaner * dont write empty files * wip log handler * fmt * cleanup logging of backtraces * add proper backtrace support * use stable reporter * adhere to posthog format * fix stacktraces * use anyhow for capturing backtraces * I think we're done? * cleanup logging * properly collect! * move out keycode handling * she works * typo * add extra fields * fix cargo doc --------- Co-authored-by: Evan Almloff <evanalmloff@gmail.com>
16 lines
588 B
Rust
16 lines
588 B
Rust
//! Configuration of the CLI at runtime to enable certain experimental features.
|
|
|
|
/// Should we force the entropy to be used on the main exe?
|
|
///
|
|
/// This is used to verify that binaries are copied with different names such that they don't collide
|
|
/// and should generally be only enabled on certain platforms that require it.
|
|
pub(crate) fn should_force_entropy() -> bool {
|
|
std::env::var("DIOXUS_FORCE_ENTRY").is_ok()
|
|
}
|
|
|
|
/// Should we test the installs?
|
|
#[allow(dead_code)] // -> used in tests only
|
|
pub(crate) fn test_installs() -> bool {
|
|
std::env::var("TEST_INSTALLS").is_ok()
|
|
}
|