mirror of
https://github.com/outbackdingo/firezone.git
synced 2026-01-27 10:18:54 +00:00
eedf852ebe
Bumps [time](https://github.com/time-rs/time) from 0.3.36 to 0.3.37. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/time-rs/time/releases">time's releases</a>.</em></p> <blockquote> <h2>v0.3.37</h2> <p>See the <a href="https://github.com/time-rs/time/blob/main/CHANGELOG.md">changelog</a> for details.</p> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/time-rs/time/blob/main/CHANGELOG.md">time's changelog</a>.</em></p> <blockquote> <h2>0.3.37 [2024-12-03]</h2> <h3>Added</h3> <ul> <li><code>Time::MAX</code>, equivalent to <code>time!(23:59:59.999999999)</code></li> <li><code>[year repr:century]</code> is now supported in format descriptions. When used in conjunction with <code>[year repr:last_two]</code>, there is sufficient information to parse a date. Note that with the <code>large-date</code> feature enabled, there is an ambiguity when parsing the two back-to-back.</li> <li>Parsing of <code>strftime</code>-style format descriptions, located at <code>time::format_description::parse_strftime_borrowed</code> and <code>time::format_description::parse_strftime_owned</code></li> <li><code>time::util::refresh_tz</code> and <code>time::util::refresh_tz_unchecked</code>, which updates information obtained via the <code>TZ</code> environment variable. This is equivalent to the <code>tzset</code> syscall on Unix-like systems, with and without built-in soundness checks, respectively.</li> <li><code>Month::length</code> and <code>util::days_in_month</code>, replacing <code>util::days_in_year_month</code>.</li> <li>Expressions are permitted in <code>time::serde::format_description!</code> rather than only paths. This also drastically improves diagnostics when an invalid value is provided.</li> </ul> <h3>Changed</h3> <ul> <li> <p>Obtaining the system UTC offset on Unix-like systems should now succeed when multi-threaded. However, if the <code>TZ</code> environment variable is altered, the program will not be aware of this until <code>time::util::refresh_tz</code> or <code>time::util::refresh_tz_unchecked</code> is called. <code>refresh_tz</code> has the same soundness requirements as obtaining the system UTC offset previously did, with the requirements still being automatically enforced. <code>refresh_tz_unchecked</code> does not enforce these requirements at the expense of being <code>unsafe</code>. Most programs should not need to call either function.</p> <p>Due to this change, the <code>time::util::local_offset</code> module has been deprecated in its entirety. The <code>get_soundness</code> and <code>set_soundness</code> functions are now no-ops.</p> <p>Note that while calls <em>should</em> succeed, success is not guaranteed in any situation. Downstream users should always be prepared to handle the error case.</p> </li> </ul> <h3>Fixed</h3> <ul> <li>Floating point values are truncated, not rounded, when formatting.</li> <li>RFC3339 allows arbitrary separators between the date and time components.</li> <li>Serialization of negative <code>Duration</code>s less than one second is now correct. It previously omitted the negative sign.</li> <li><code>From<js_sys::Date> for OffsetDateTime</code> now ensures sub-millisecond values are not erroneously returned.</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="d4e39b306d"><code>d4e39b3</code></a> v0.3.37 release</li> <li><a href="09439970e5"><code>0943997</code></a> Fix CI failure</li> <li><a href="8b50f04ee0"><code>8b50f04</code></a> Update lints</li> <li><a href="56f1db6dfa"><code>56f1db6</code></a> Add <code>Month::length</code>, <code>days_in_month</code></li> <li><a href="03bcfe9f28"><code>03bcfe9</code></a> Skip formatting some macros, update UI tests</li> <li><a href="4404638fe2"><code>4404638</code></a> Permit exprs in <code>serde::format_description!</code></li> <li><a href="6b43b44060"><code>6b43b44</code></a> strftime implementation</li> <li><a href="98569ffe5b"><code>98569ff</code></a> Hide deprecations from docs</li> <li><a href="febf3a10de"><code>febf3a1</code></a> Obtain local offset in multi-threaded situations</li> <li><a href="1e19827c5a"><code>1e19827</code></a> Update rstest and rstest_reuse; bump MSRV to 1.67.1 (<a href="https://redirect.github.com/time-rs/time/issues/716">#716</a>)</li> <li>Additional commits viewable in <a href="https://github.com/time-rs/time/compare/v0.3.36...v0.3.37">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Thomas Eizinger <thomas@eizinger.io>
Rust development guide
Firezone uses Rust for all data plane components. This directory contains the Linux and Windows clients, and low-level networking implementations related to STUN/TURN.
We target the last stable release of Rust using rust-toolchain.toml.
If you are using rustup, that is automatically handled for you.
Otherwise, ensure you have the latest stable version of Rust installed.
Reading Client logs
The Client logs are written as JSONL for machine-readability.
To make them more human-friendly, pipe them through jq like this:
cd path/to/logs # e.g. `$HOME/.cache/dev.firezone.client/data/logs` on Linux
cat *.log | jq -r '"\(.time) \(.severity) \(.message)"'
Resulting in, e.g.
2024-04-01T18:25:47.237661392Z INFO started log
2024-04-01T18:25:47.238193266Z INFO GIT_VERSION = 1.0.0-pre.11-35-gcc0d43531
2024-04-01T18:25:48.295243016Z INFO No token / actor_name on disk, starting in signed-out state
2024-04-01T18:25:48.295360641Z INFO null
Benchmarking on Linux
The recommended way for benchmarking any of the Rust components is Linux' perf utility.
For example, to attach to a running application, do:
- Ensure the binary you are profiling is compiled with the
releaseprofile. sudo perf record -g --freq 10000 --pid $(pgrep <your-binary>).- Run the speed test or whatever load-inducing task you want to measure.
sudo perf script > profile.perf- Open profiler.firefox.com and load
profile.perf
Instead of attaching to a process with --pid, you can also specify the path to executable directly.
That is useful if you want to capture perf data for a test or a micro-benchmark.