mirror of
https://github.com/outbackdingo/firezone.git
synced 2026-01-27 10:18:54 +00:00
9ac9dedfb9c3e1b1ca05f9ef15596c1126232657
4919 Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
|
9ac9dedfb9 |
feat: Azure scalable Gateway module and docs (#5644)
Resolves #2603 |
||
|
|
5fd321c4bb |
chore(connlib): forward non-address record queries (#5674)
Since we only handle `A`, `AAAA` and `PTR` records of names we handle, this can lead to unexpected behavior with other record types, where using Firezone breaks `TXT`, `MX` or other record types for the resources we handle. So this is a bit of a refactor, now we lookup a resource and explicitly return `Some` when there is a record we should be returning (even if it's empty due to IP exhaustion) or `None` when we should just forward the query. This has the added benefit of no longer breaking bonjour or other non-standard `PTR` queries. Fixes: #5673. --------- Co-authored-by: Thomas Eizinger <thomas@eizinger.io> |
||
|
|
e472f21bb0 |
revert: "fix(website): Handle JS errors during Mixpanel init" (#5685)
Reverts firezone/firezone#5684 |
||
|
|
c0f98ea896 |
fix(portal): bump auth constant time to 2s (#5668)
Fixes https://console.cloud.google.com/monitoring/alerting/incidents/0.nes28ktmvdk8?channelType=slack&project=firezone-prod ``` elapsed_time: 1300 ``` |
||
|
|
b0e35aa148 |
fix(website): Handle JS errors during Mixpanel init (#5684)
Adds an `ErrorBoundary` to catch the errors that may occur when rendering the Suspense ``` Uncaught Error: Minified React error #419; visit https://react.dev/errors/419 for the full message or use the non-minified dev environment for full errors and additional helpful warnings. ``` |
||
|
|
1edc827bca |
feat(portal): enable welcome email sending on manually provisionned o… (#5679)
…idc users (#5127) Currently we can only send a welcome email to oidc users who have already logged in once. For manually provisionned oidc users, we can't. This PR aims to solve this issue --------- Co-authored-by: Antoine <antoinelabarussias@gmail.com> |
||
|
|
33dff8af96 |
docs: Add more Gateway deploy examples (#5646)
- ~~Adds `fontawesome` icons to the portal and integrates them into the existing `icon` component. Use just like the heroicons except prefixed `fa-`.~~ Edit: removed these because I don't think it's worth the increased bundle size. Just going to inline the icons we need instead. - Fixes #3041 - Fixes #5072 |
||
|
|
4b6b706d46 |
refactor(gui-client): remove the heartbeat module (#5682)
We added this to diagnose a hang in the IPC service, #5441. That hang, to the best of our knowledge, was caused by a deadlock which we fixed in #5571. So the heartbeat task just adds a lot of noise to the stdout which is annoying for debugging and won't be used in production logs. The system uptime measuring is still useful, so we now log that just once when logging starts, next to the git version and log directives. If we see this pattern in either process' logs, we know something is suspicious: - Log file ends without a clean shutdown message - Next log file starts with a high system uptime Updates should always result in a clean shutdown message, and a sudden power loss (mains power outage, or laptop battery dying) would result in the system uptime being low for the 2nd log file. |
||
|
|
ee8b42af26 | chore(website): Add missing section in Overview (#5677) | ||
|
|
a5b7507932 |
refactor(website): Remove flowbite library in favor of flowbite-react (#5676)
Flowbite hard-fails on 2.4.1 with NextJS/React causing the build error `document is not defined`. To fix this, we need to use Flowbite's React library (we already were, now it's the sole flowbite lib). |
||
|
|
79fd8f6063 |
chore(connlib): add message type to the no records found logs (#5641)
Added for clarity when debugging, it used to look like: ``` 2024-06-30T00:16:05.718337Z DEBUG firezone_tunnel::dns: No records for github.com, returning NXDOMAIN ``` And now looks like: ``` 2024-06-30T00:16:05.718337Z DEBUG firezone_tunnel::dns: No MX records for github.com, returning NXDOMAIN ``` |
||
|
|
e046987a69 |
build(deps): Bump flowbite from 2.3.0 to 2.4.1 in /elixir/apps/web/assets (#5653)
Bumps [flowbite](https://github.com/themesberg/flowbite) from 2.3.0 to 2.4.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/themesberg/flowbite/releases">flowbite's releases</a>.</em></p> <blockquote> <h2>v2.4.1</h2> <ul> <li>fix datepicker module declaration naming for TypeScript</li> </ul> <h2>v2.4.0</h2> <ul> <li>the datepicker is now a core component of Flowbite and has API methods, events, and options</li> <li>updated the documentation for the datepicker component and related integration guides</li> <li>minor visual bug fixes and improvements</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href=" |
||
|
|
4075b779b5 |
refactor(gui-client): reload log filter immediately (#5671)
This will simplify #5590 some. The API URL and auth URL still take effect on the next sign-in, but we don't have to explain that the settings take effect after restarting the entire Client process, those take effect somewhat immediately. For some reason I see some lag, maybe the tracing layers don't check for a new filter on every span, maybe they have some delay to save CPU time. |
||
|
|
155a815ae7 |
build(deps): Bump androidx.test.ext:junit from 1.1.5 to 1.2.1 in /kotlin/android in the junit group (#5656)
Bumps the junit group in /kotlin/android with 1 update: androidx.test.ext:junit. Updates `androidx.test.ext:junit` from 1.1.5 to 1.2.1 [](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 <dependency name> major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore <dependency name> minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore <dependency name>` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore <dependency name>` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore <dependency name> <ignore condition>` will remove the ignore condition of the specified dependency and ignore conditions </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Jamil <jamilbk@users.noreply.github.com> |
||
|
|
976cdfa731 |
refactor(headless-client): vendor uptime_lib (#5625)
This does the same thing as #5621 without removing the library, since it will now compile against whatever version of `windows` we need We could do the same with `hostname`, either vendor or ask upstream to bump deps, and then `windows` 0.52.0 should be gone. ```[tasklist] ### Tasks - [x] Remove macOS code and shrink everything ``` |
||
|
|
02f5c67974 |
chore(windows): reduce nesting in wintun recv-thread (#5573)
Related: #5571. |
||
|
|
f4d9a204df |
ci: increase sleep for flaky integration tests due to slow GH runners (#5667)
Both of these deal with the tunnel interface being initialized, which seems to take more than 1s when we have a lot of jobs running. --------- Signed-off-by: Jamil <jamilbk@users.noreply.github.com> |
||
|
|
8388efcf52 |
fix(apple): Fix ResourceList bug showing cached Resources from last session (#5645)
On macOS and iOS, the TunnelManager instance stays active across sessions. This contains a Resource cache used to fetch Resources from the tunnel process. This cache wasn't cleared across sessions, so the first time the callback fired the Resources shown were the ones from the last session. After `1s`, they were correctly set to the current session's Resources due to the `beginUpdatingResources` timer. We were already clearing the stored Hash of the Resource cache on disconnect, but not the Resource cache itself. This patch fixes that bug by re-initializing the cache when the tunnel session is `disconnected`. |
||
|
|
8c5092cf6c |
build(deps-dev): Bump typescript from 5.4.5 to 5.5.2 in /rust/gui-client (#5664)
Bumps [typescript](https://github.com/Microsoft/TypeScript) from 5.4.5 to 5.5.2. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/Microsoft/TypeScript/releases">typescript's releases</a>.</em></p> <blockquote> <h2>TypeScript 5.5</h2> <p>For release notes, check out the <a href="https://devblogs.microsoft.com/typescript/announcing-typescript-5-5/">release announcement</a>.</p> <p>For the complete list of fixed issues, check out the</p> <ul> <li><a href="https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93&q=is%3Aissue+milestone%3A%22TypeScript+5.5.2%22+is%3Aclosed+">fixed issues query for TypeScript v5.5.2 (Stable)</a>.</li> <li><a href="https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93&q=is%3Aissue+milestone%3A%22TypeScript+5.5.1%22+is%3Aclosed+">fixed issues query for TypeScript v5.5.1 (RC)</a>.</li> <li><a href="https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93&q=is%3Aissue+milestone%3A%22TypeScript+5.5.0%22+is%3Aclosed+">fixed issues query for TypeScript v5.5.0 (Beta)</a>.</li> </ul> <p>Downloads are available on:</p> <ul> <li><a href="https://www.npmjs.com/package/typescript">npm</a></li> <li><a href="https://www.nuget.org/packages/Microsoft.TypeScript.MSBuild">NuGet package</a></li> </ul> <h2>TypeScript 5.5 RC</h2> <p>For release notes, check out the <a href="https://devblogs.microsoft.com/typescript/announcing-typescript-5-5-rc/">release announcement</a>.</p> <p>For the complete list of fixed issues, check out the</p> <ul> <li><a href="https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93&q=milestone%3A%22TypeScript+5.5.0%22+is%3Aclosed+">fixed issues query for Typescript 5.5.0 (Beta)</a>.</li> <li><a href="https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93&q=milestone%3A%22TypeScript+5.5.1%22+is%3Aclosed+">fixed issues query for Typescript 5.5.1 (RC)</a>.</li> </ul> <p>Downloads are available on:</p> <ul> <li><a href="https://www.nuget.org/packages/Microsoft.TypeScript.MSBuild">NuGet package</a></li> </ul> <h2>TypeScript 5.5 Beta</h2> <p>For release notes, check out the <a href="https://devblogs.microsoft.com/typescript/announcing-typescript-5-5-beta/">release announcement</a>.</p> <p>For the complete list of fixed issues, check out the</p> <ul> <li><a href="https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93&q=milestone%3A%22TypeScript+5.5.0%22+is%3Aclosed+">fixed issues query for Typescript 5.5.0 (Beta)</a>.</li> </ul> <p>Downloads are available on:</p> <ul> <li><a href="https://www.npmjs.com/package/typescript">npm</a></li> <li><a href="https://www.nuget.org/packages/Microsoft.TypeScript.MSBuild">NuGet package</a></li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href=" |
||
|
|
278d26b083 |
build(deps-dev): Bump @types/node from 20.14.2 to 20.14.9 in /rust/gui-client (#5663)
Bumps [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) from 20.14.2 to 20.14.9. <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node">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> |
||
|
|
184c982d75 |
build(deps): Bump @types/node from 20.14.2 to 20.14.9 in /website (#5659)
Bumps [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) from 20.14.2 to 20.14.9. <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node">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> |
||
|
|
c5bf5f118c |
build(deps): Bump docker/build-push-action from 5 to 6 (#5652)
Bumps [docker/build-push-action](https://github.com/docker/build-push-action) from 5 to 6. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/docker/build-push-action/releases">docker/build-push-action's releases</a>.</em></p> <blockquote> <h2>v6.0.0</h2> <ul> <li>Export build record and generate <a href="https://docs.docker.com/build/ci/github-actions/build-summary/">build summary</a> by <a href="https://github.com/crazy-max"><code>@crazy-max</code></a> in <a href="https://redirect.github.com/docker/build-push-action/pull/1120">docker/build-push-action#1120</a></li> <li>Bump <code>@docker/actions-toolkit</code> from 0.24.0 to 0.26.0 in <a href="https://redirect.github.com/docker/build-push-action/pull/1132">docker/build-push-action#1132</a> <a href="https://redirect.github.com/docker/build-push-action/pull/1136">docker/build-push-action#1136</a> <a href="https://redirect.github.com/docker/build-push-action/pull/1138">docker/build-push-action#1138</a></li> <li>Bump braces from 3.0.2 to 3.0.3 in <a href="https://redirect.github.com/docker/build-push-action/pull/1137">docker/build-push-action#1137</a></li> </ul> <blockquote> <p>[!NOTE] This major release adds support for generating <a href="https://docs.docker.com/build/ci/github-actions/build-summary/">Build summary</a> and exporting build record for your build. You can disable this feature by setting <a href="https://docs.docker.com/build/ci/github-actions/build-summary/#disable-job-summary"> <code>DOCKER_BUILD_NO_SUMMARY: true</code> environment variable in your workflow</a>.</p> </blockquote> <p><strong>Full Changelog</strong>: <a href="https://github.com/docker/build-push-action/compare/v5.4.0...v6.0.0">https://github.com/docker/build-push-action/compare/v5.4.0...v6.0.0</a></p> <h2>v5.4.0</h2> <ul> <li>Show builder information before building by <a href="https://github.com/crazy-max"><code>@crazy-max</code></a> in <a href="https://redirect.github.com/docker/build-push-action/pull/1128">docker/build-push-action#1128</a></li> <li>Handle attestations correctly with provenance and sbom inputs by <a href="https://github.com/crazy-max"><code>@crazy-max</code></a> in <a href="https://redirect.github.com/docker/build-push-action/pull/1086">docker/build-push-action#1086</a></li> <li>Bump <code>@docker/actions-toolkit</code> from 0.19.0 to 0.24.0 in <a href="https://redirect.github.com/docker/build-push-action/pull/1088">docker/build-push-action#1088</a> <a href="https://redirect.github.com/docker/build-push-action/pull/1105">docker/build-push-action#1105</a> <a href="https://redirect.github.com/docker/build-push-action/pull/1121">docker/build-push-action#1121</a> <a href="https://redirect.github.com/docker/build-push-action/pull/1127">docker/build-push-action#1127</a></li> <li>Bump undici from 5.28.3 to 5.28.4 in <a href="https://redirect.github.com/docker/build-push-action/pull/1090">docker/build-push-action#1090</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/docker/build-push-action/compare/v5.3.0...v5.4.0">https://github.com/docker/build-push-action/compare/v5.3.0...v5.4.0</a></p> <h2>v5.3.0</h2> <ul> <li>Bump <code>@docker/actions-toolkit</code> from 0.18.0 to 0.19.0 in <a href="https://redirect.github.com/docker/build-push-action/pull/1080">docker/build-push-action#1080</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/docker/build-push-action/compare/v5.2.0...v5.3.0">https://github.com/docker/build-push-action/compare/v5.2.0...v5.3.0</a></p> <h2>v5.2.0</h2> <ul> <li>Disable quotes detection for <code>outputs</code> input by <a href="https://github.com/crazy-max"><code>@crazy-max</code></a> in <a href="https://redirect.github.com/docker/build-push-action/pull/1074">docker/build-push-action#1074</a></li> <li>Warn about ignored inputs by <a href="https://github.com/favonia"><code>@favonia</code></a> in <a href="https://redirect.github.com/docker/build-push-action/pull/1019">docker/build-push-action#1019</a></li> <li>Bump <code>@docker/actions-toolkit</code> from 0.14.0 to 0.18.0 in <a href="https://redirect.github.com/docker/build-push-action/pull/1070">docker/build-push-action#1070</a></li> <li>Bump undici from 5.26.3 to 5.28.3 in <a href="https://redirect.github.com/docker/build-push-action/pull/1057">docker/build-push-action#1057</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/docker/build-push-action/compare/v5.1.0...v5.2.0">https://github.com/docker/build-push-action/compare/v5.1.0...v5.2.0</a></p> <h2>v5.1.0</h2> <ul> <li>Add <code>annotations</code> input by <a href="https://github.com/crazy-max"><code>@crazy-max</code></a> in <a href="https://redirect.github.com/docker/build-push-action/pull/992">docker/build-push-action#992</a></li> <li>Add <code>secret-envs</code> input by <a href="https://github.com/elias-lundgren"><code>@elias-lundgren</code></a> in <a href="https://redirect.github.com/docker/build-push-action/pull/980">docker/build-push-action#980</a></li> <li>Bump <code>@babel/traverse</code> from 7.17.3 to 7.23.2 in <a href="https://redirect.github.com/docker/build-push-action/pull/991">docker/build-push-action#991</a></li> <li>Bump <code>@docker/actions-toolkit</code> from 0.13.0-rc.1 to 0.14.0 in <a href="https://redirect.github.com/docker/build-push-action/pull/990">docker/build-push-action#990</a> <a href="https://redirect.github.com/docker/build-push-action/pull/1006">docker/build-push-action#1006</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/docker/build-push-action/compare/v5.0.0...v5.1.0">https://github.com/docker/build-push-action/compare/v5.0.0...v5.1.0</a></p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href=" |
||
|
|
d939699e0c |
build(deps-dev): Bump @types/node from 20.14.2 to 20.14.9 in /scripts/tests/browser (#5650)
Bumps [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) from 20.14.2 to 20.14.9. <details> <summary>Commits</summary> <ul> <li>See full diff in <a href="https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node">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> |
||
|
|
7a979179a4 |
build(deps): Bump puppeteer from 22.12.0 to 22.12.1 in /scripts/tests/browser (#5649)
Bumps [puppeteer](https://github.com/puppeteer/puppeteer) from 22.12.0 to 22.12.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/puppeteer/puppeteer/releases">puppeteer's releases</a>.</em></p> <blockquote> <h2>puppeteer-core: v22.12.1</h2> <h2><a href="https://github.com/puppeteer/puppeteer/compare/puppeteer-core-v22.12.0...puppeteer-core-v22.12.1">22.12.1</a> (2024-06-26)</h2> <h3>Bug Fixes</h3> <ul> <li>execution contexts might be created before previous is destroyed (<a href="https://redirect.github.com/puppeteer/puppeteer/issues/12666">#12666</a>) (<a href=" |
||
|
|
258a7a0d74 |
build(deps-dev): Bump typescript from 5.4.5 to 5.5.2 in /scripts/tests/browser (#5648)
Bumps [typescript](https://github.com/Microsoft/TypeScript) from 5.4.5 to 5.5.2. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/Microsoft/TypeScript/releases">typescript's releases</a>.</em></p> <blockquote> <h2>TypeScript 5.5</h2> <p>For release notes, check out the <a href="https://devblogs.microsoft.com/typescript/announcing-typescript-5-5/">release announcement</a>.</p> <p>For the complete list of fixed issues, check out the</p> <ul> <li><a href="https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93&q=is%3Aissue+milestone%3A%22TypeScript+5.5.2%22+is%3Aclosed+">fixed issues query for TypeScript v5.5.2 (Stable)</a>.</li> <li><a href="https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93&q=is%3Aissue+milestone%3A%22TypeScript+5.5.1%22+is%3Aclosed+">fixed issues query for TypeScript v5.5.1 (RC)</a>.</li> <li><a href="https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93&q=is%3Aissue+milestone%3A%22TypeScript+5.5.0%22+is%3Aclosed+">fixed issues query for TypeScript v5.5.0 (Beta)</a>.</li> </ul> <p>Downloads are available on:</p> <ul> <li><a href="https://www.npmjs.com/package/typescript">npm</a></li> <li><a href="https://www.nuget.org/packages/Microsoft.TypeScript.MSBuild">NuGet package</a></li> </ul> <h2>TypeScript 5.5 RC</h2> <p>For release notes, check out the <a href="https://devblogs.microsoft.com/typescript/announcing-typescript-5-5-rc/">release announcement</a>.</p> <p>For the complete list of fixed issues, check out the</p> <ul> <li><a href="https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93&q=milestone%3A%22TypeScript+5.5.0%22+is%3Aclosed+">fixed issues query for Typescript 5.5.0 (Beta)</a>.</li> <li><a href="https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93&q=milestone%3A%22TypeScript+5.5.1%22+is%3Aclosed+">fixed issues query for Typescript 5.5.1 (RC)</a>.</li> </ul> <p>Downloads are available on:</p> <ul> <li><a href="https://www.nuget.org/packages/Microsoft.TypeScript.MSBuild">NuGet package</a></li> </ul> <h2>TypeScript 5.5 Beta</h2> <p>For release notes, check out the <a href="https://devblogs.microsoft.com/typescript/announcing-typescript-5-5-beta/">release announcement</a>.</p> <p>For the complete list of fixed issues, check out the</p> <ul> <li><a href="https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93&q=milestone%3A%22TypeScript+5.5.0%22+is%3Aclosed+">fixed issues query for Typescript 5.5.0 (Beta)</a>.</li> </ul> <p>Downloads are available on:</p> <ul> <li><a href="https://www.npmjs.com/package/typescript">npm</a></li> <li><a href="https://www.nuget.org/packages/Microsoft.TypeScript.MSBuild">NuGet package</a></li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href=" |
||
|
|
486ea14ea8 |
build(deps): Bump com.google.firebase:firebase-bom from 33.1.0 to 33.1.1 in /kotlin/android (#5657)
Bumps com.google.firebase:firebase-bom from 33.1.0 to 33.1.1. [](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> |
||
|
|
804ab80c59 |
build(deps): Bump @next/mdx from 14.2.3 to 14.2.4 in /website (#5658)
Bumps
[@next/mdx](https://github.com/vercel/next.js/tree/HEAD/packages/next-mdx)
from 14.2.3 to 14.2.4.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a
href="https://github.com/vercel/next.js/releases"><code>@next/mdx</code>'s
releases</a>.</em></p>
<blockquote>
<h2>v14.2.4</h2>
<blockquote>
<p>[!NOTE]<br />
This release is backporting bug fixes. It does <strong>not</strong>
include all pending features/changes on canary.</p>
</blockquote>
<h3>Core Changes</h3>
<ul>
<li>fix: ensure route handlers properly track dynamic access (<a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-mdx/issues/66446">#66446</a>)</li>
<li>fix NextRequest proxy in edge runtime (<a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-mdx/issues/66551">#66551</a>)</li>
<li>Fix next/dynamic with babel and src dir (<a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-mdx/issues/65177">#65177</a>)</li>
<li>Use vercel deployment url for metadataBase fallbacks (<a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-mdx/issues/65089">#65089</a>)</li>
<li>fix(next/image): detect react@19 for fetchPriority prop (<a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-mdx/issues/65235">#65235</a>)</li>
<li>Fix loading navigation with metadata and prefetch (<a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-mdx/issues/66447">#66447</a>)</li>
<li>prevent duplicate RSC fetch when action redirects (<a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-mdx/issues/66620">#66620</a>)</li>
<li>ensure router cache updates reference the latest cache values (<a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-mdx/issues/66681">#66681</a>)</li>
<li>Prevent append of trailing slash in cases where path ends with a
file extension (<a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-mdx/issues/66636">#66636</a>)</li>
<li>Fix inconsistency with 404 getStaticProps cache-control (<a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-mdx/issues/66674">#66674</a>)</li>
<li>Use addDependency to track metadata route file changes (<a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-mdx/issues/66714">#66714</a>)</li>
<li>Add timeout/retry handling for fetch cache (<a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-mdx/issues/66652">#66652</a>)</li>
<li>fix: app-router prefetch crash when an invalid URL is passed to Link
(<a
href="https://github.com/vercel/next.js/tree/HEAD/packages/next-mdx/issues/66755">#66755</a>)</li>
</ul>
<h3>Credits</h3>
<p>Huge thanks to <a
href="https://github.com/ztanner"><code>@ztanner</code></a>, <a
href="https://github.com/ijjk"><code>@ijjk</code></a>, <a
href="https://github.com/wbinnssmith"><code>@wbinnssmith</code></a>, <a
href="https://github.com/huozhi"><code>@huozhi</code></a>, and <a
href="https://github.com/lubieowoce"><code>@lubieowoce</code></a> for
helping!</p>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="
|
||
|
|
b2a79fe1d1 |
build(deps): Bump mixpanel-browser from 2.52.0 to 2.53.0 in /website (#5661)
Bumps [mixpanel-browser](https://github.com/mixpanel/mixpanel-js) from 2.52.0 to 2.53.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/mixpanel/mixpanel-js/releases">mixpanel-browser's releases</a>.</em></p> <blockquote> <h2>Session recording updates</h2> <ul> <li>Network payload format for session recording batches has changed, including client-side compression on browsers which support it</li> <li>Google Tag Manager wrapper now includes session-recording start/stop methods</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/mixpanel/mixpanel-js/blob/master/CHANGELOG.md">mixpanel-browser's changelog</a>.</em></p> <blockquote> <p><strong>2.53.0</strong> (21 Jun 2024)</p> <ul> <li>Switch to new session-recording network payload format, utilizing client-side compression when available</li> <li>Session-recording methods are now available through Google Tag Manager wrapper</li> </ul> <p><strong>2.52.0</strong> (7 Jun 2024)</p> <ul> <li>Reverted UTM param persistence change from 2.51.0: UTM parameters are again persisted by default</li> </ul> <p><strong>2.51.0</strong> (30 May 2024)</p> <ul> <li>UTM parameter properties are no longer persisted by default</li> <li>Existing superproperties persisted in localStorage are now copied back to cookie storage if the library is initialized with cookie persistence (support migrations from localStorage->cookie)</li> <li>Added session-recording options <code>record_block_class</code>, <code>record_block_selector</code>, and <code>record_mask_text_class</code></li> <li>Added method <code>mixpanel.get_session_recording_properties()</code> for interop with other client-side SDKs</li> </ul> <p><strong>2.50.0</strong> (26 Apr 2024)</p> <ul> <li>Initial support for session recording</li> </ul> <p><strong>2.49.0</strong> (5 Feb 2024)</p> <ul> <li>SPA support in pageview-tracking</li> <li>Support for configurable UTM parameter persistence</li> <li>Initial-referrer profile properties are now stored with <code>set_once</code> instead of <code>set</code></li> <li>Ignore AhrefsSiteAudit crawler</li> </ul> <p><strong>2.48.1</strong> (14 Nov 2023)</p> <ul> <li>UTM campaign properties will always be persisted super properties (fixes discrepancy between minified and unminified package)</li> </ul> <p><strong>2.48.0</strong> (7 Nov 2023)</p> <ul> <li>API endpoint routes can now be configured individually (i.e. rename /track, /engage, /groups)</li> <li>Event properties object passed to mixpanel.track() will no longer be mutated</li> <li>Super properties are now reloaded from persistence when making every tracking call (i.e., kept fresh when another tab/window in the same browser has updated them)</li> <li>Extra failsafe behavior for trying to clear queued requests when localStorage doesn't work on startup, e.g., when localStorage is full so writes fail</li> <li>Block Chrome-Lighthouse user agent</li> <li>Fix for error in add_group() when adding a new group to an existing list</li> </ul> <p><strong>2.47.0</strong> (27 Apr 2023)</p> <ul> <li>Collect richer marketing attribution properties for multi-touch attribution</li> <li>New implementation of previously-deprecated track_pageview() method and init option to send automatically</li> <li>Use performance.now when available for time-based entropy component of UUID-generation (thanks <a href="https://github.com/adrianherd"><code>@adrianherd</code></a>)</li> <li>Looser API Host check for default JSON-payload sending to mipxanel.com hosts</li> </ul> <p><strong>2.46.0</strong> (20 Mar 2023)</p> <ul> <li>Updates for new identity management system</li> <li>More aggressive deduplication within batch sender</li> </ul> <p><strong>2.45.0</strong> (17 Feb 2022)</p> <ul> <li>Remove all code related to in-app messaging feature</li> <li>Add <code>error_reporter</code> config option for user-configurable handling of errors</li> <li>Fix missing <code>var</code> declarations in HTML script snippet</li> <li>Fixes for some batch/retry edge cases where localStorage write failures resulted in duplicate sends</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href=" |
||
|
|
ddf9f4ed0d |
build(deps-dev): Bump typescript from 5.4.5 to 5.5.2 in /website (#5662)
Bumps [typescript](https://github.com/Microsoft/TypeScript) from 5.4.5 to 5.5.2. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/Microsoft/TypeScript/releases">typescript's releases</a>.</em></p> <blockquote> <h2>TypeScript 5.5</h2> <p>For release notes, check out the <a href="https://devblogs.microsoft.com/typescript/announcing-typescript-5-5/">release announcement</a>.</p> <p>For the complete list of fixed issues, check out the</p> <ul> <li><a href="https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93&q=is%3Aissue+milestone%3A%22TypeScript+5.5.2%22+is%3Aclosed+">fixed issues query for TypeScript v5.5.2 (Stable)</a>.</li> <li><a href="https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93&q=is%3Aissue+milestone%3A%22TypeScript+5.5.1%22+is%3Aclosed+">fixed issues query for TypeScript v5.5.1 (RC)</a>.</li> <li><a href="https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93&q=is%3Aissue+milestone%3A%22TypeScript+5.5.0%22+is%3Aclosed+">fixed issues query for TypeScript v5.5.0 (Beta)</a>.</li> </ul> <p>Downloads are available on:</p> <ul> <li><a href="https://www.npmjs.com/package/typescript">npm</a></li> <li><a href="https://www.nuget.org/packages/Microsoft.TypeScript.MSBuild">NuGet package</a></li> </ul> <h2>TypeScript 5.5 RC</h2> <p>For release notes, check out the <a href="https://devblogs.microsoft.com/typescript/announcing-typescript-5-5-rc/">release announcement</a>.</p> <p>For the complete list of fixed issues, check out the</p> <ul> <li><a href="https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93&q=milestone%3A%22TypeScript+5.5.0%22+is%3Aclosed+">fixed issues query for Typescript 5.5.0 (Beta)</a>.</li> <li><a href="https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93&q=milestone%3A%22TypeScript+5.5.1%22+is%3Aclosed+">fixed issues query for Typescript 5.5.1 (RC)</a>.</li> </ul> <p>Downloads are available on:</p> <ul> <li><a href="https://www.nuget.org/packages/Microsoft.TypeScript.MSBuild">NuGet package</a></li> </ul> <h2>TypeScript 5.5 Beta</h2> <p>For release notes, check out the <a href="https://devblogs.microsoft.com/typescript/announcing-typescript-5-5-beta/">release announcement</a>.</p> <p>For the complete list of fixed issues, check out the</p> <ul> <li><a href="https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93&q=milestone%3A%22TypeScript+5.5.0%22+is%3Aclosed+">fixed issues query for Typescript 5.5.0 (Beta)</a>.</li> </ul> <p>Downloads are available on:</p> <ul> <li><a href="https://www.npmjs.com/package/typescript">npm</a></li> <li><a href="https://www.nuget.org/packages/Microsoft.TypeScript.MSBuild">NuGet package</a></li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href=" |
||
|
|
9994690f63 |
build(deps): Bump flowbite from 2.3.0 to 2.4.1 in /rust/gui-client (#5665)
Bumps [flowbite](https://github.com/themesberg/flowbite) from 2.3.0 to 2.4.1. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/themesberg/flowbite/releases">flowbite's releases</a>.</em></p> <blockquote> <h2>v2.4.1</h2> <ul> <li>fix datepicker module declaration naming for TypeScript</li> </ul> <h2>v2.4.0</h2> <ul> <li>the datepicker is now a core component of Flowbite and has API methods, events, and options</li> <li>updated the documentation for the datepicker component and related integration guides</li> <li>minor visual bug fixes and improvements</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href=" |
||
|
|
ce974a8c31 | docs: Dependabot note for apple secrets instructions (#5666) | ||
|
|
53557f46e4 | feat(website): Mention IPv6 features on website (#5640) | ||
|
|
eaf981597b |
fix(gateway): Add default RUST_LOG level to Docker-deployed Gateways (#5639)
This has been an issue for some time(!) Fixes #5141 |
||
|
|
25b6528942 |
chore: Bump versions and update changelog (#5636)
Signed-off-by: Jamil <jamilbk@users.noreply.github.com> |
||
|
|
04476880e7 |
ci: only set up runtime tauri deps for smoke tests (#5632)
Setting up Tauri's runtime dependencies takes about a minute and is unnecessary for the Rust unit tests. The Rust Windows unit tests jobs are amongst the slowest and thus impact the overall CI runtime. See https://github.com/firezone/firezone/actions/runs/9719218798/job/26828616349 for a recent run on `main`. --------- Signed-off-by: Thomas Eizinger <thomas@eizinger.io> Co-authored-by: Jamil <jamilbk@users.noreply.github.com> |
||
|
|
b5fd980fb2 |
fix(relay): don't log all request failures on the same level (#5622)
Currently, the relay logs all failed requests on WARN. This is a bit excessive because during normal operation, clients are expected to hit several 401s due to stale or missing nonces. In order to not flood the logs with these, we introduce a new type, `ResponseErrorLevel` that represents the subset of `tracing::Level` that `make_error_response` can log: - `Warn` - `Debug` Both variants mapping to the variants in `tracing::Level` with the same name, and the function will log accordingly. So now the caller can pick what level of error is meant to be used and reduce the noise on the logs when it's meant to be part of normal operation. Fixes: #5490. --------- Co-authored-by: conectado <gabrielalejandro7@gmail.com> |
||
|
|
96536a23cf |
refactor(connlib): ignore relays per connection (#5631)
In a previous design of firezone, relays used to be scoped to a certain connection. For a while now, this constraint has been lifted and all connections can use all relays. A related, outdated concern is the idea of STUN-only servers. Those also used to be assigned on a per-connection basis. By removing any use of per-connection relays and STUN-only servers, the entire `StunBinding` concept is unused code and can thus be deleted. To push this over the finish line, the `snownet-tests` which test the hole-punching functionality needed to be slightly adapted to make use of the more recently introduced API `Node::update_relays`. Resolves: #4749. |
||
|
|
f2b6c205c2 |
refactor(snownet): change reconnect to reset (#5630)
Currently, `snownet` still supports this notion of "reconnecting" which is a mix between resetting some state but keeping other. In particular, we currently retain the `StunBinding` and `Allocation` state. This used to be important because allocations are bound to the 3-tuple of the client and thus needed to be kept around in case we weren't actually roaming. We always rebind the the local UDP sockets upon reconnecting and thus the 3-tuple always changes anyway. In addition, we always reconnect to the portal, meaning we receive another `init` message and thus can actually completely clear the `Node`'s state. This PR does that an in the process, rebrands `reconnect` as `reset` which now makes more sense. Related: #5619. |
||
|
|
38275ecad0 |
refactor(gateway): extract fn for update-device task (#5581)
Follow-up feedback from #5512. |
||
|
|
839292b1e3 |
ci: use sccache for building Tauri clients (#5617)
Using sccache results in a more efficient cache usage. GitHub's built-in cache appears to grow over time and takes ~3minutes to download for the Windows Tauri builds where it is ~2GB large. Whilst researching bad performance on Windows runners in general, I came across the hint to disable Windows defender which appears to slow things down massively in the case of sccache which performs many small network downloads and file writes. This PR harmonizes our cache usage and prefers sccache over GitHub's cache for everything apart from `cross` builds. The runtimes are either roughly the same or noticeably better. Overally, the GUI smoke tests are usually among the last ones to finish, meaning these changes should have an overall net-positive impact on CI time. |[`main`](https://github.com/firezone/firezone/actions/runs/9707704927)|[`head`](https://github.com/firezone/firezone/actions/runs/9709368060)| |---|---| ||| ||| ||| ||| ||| ||| |
||
|
|
8973cc5785 |
refactor(android): use fmt::Layer with custom writer (#5558)
Currently, the logs that go to logcat on Android are pretty badly
formatted because we use `tracing-android` and it formats the span
fields and message fields itself. There is actually no reason for doing
the formatting ourselves. Instead, we can use the `MakeWriter`
abstraction from `tracing_subscriber` to plug in a custom writer that
writes to Android's logcat.
This results in logs like this:
```
[nix-shell:~/src/github.com/firezone/firezone/rust]$ adb logcat -s connlib
--------- beginning of main
06-28 19:41:20.057 19955 20213 D connlib : phoenix_channel: Connecting to portal host=api.firez.one user_agent=Android/14 5.15.137-android14-11-gbf4f9bc41c3b-ab11664771 connlib/1.1.1
06-28 19:41:20.058 19955 20213 I connlib : firezone_tunnel::client: Network change detected
06-28 19:41:20.061 19955 20213 D connlib : snownet::node: Closed all connections as part of reconnecting num_connections=0
06-28 19:41:20.365 19955 20213 I connlib : phoenix_channel: Connected to portal host=api.firez.one
06-28 19:41:20.601 19955 20213 I connlib : firezone_tunnel::io: Setting new DNS resolvers
06-28 19:41:21.031 19955 20213 D connlib : firezone_tunnel::client: TUN device initialized ip4=100.66.86.233 ip6=fd00:2021:1111::f:d9c1 name=tun1
06-28 19:41:21.031 19955 20213 I connlib : connlib_client_shared::eventloop: Firezone Started!
06-28 19:41:21.031 19955 20213 I connlib : firezone_tunnel::dns: Activating DNS resource address=*.slackb.com
06-28 19:41:21.031 19955 20213 I connlib : firezone_tunnel::dns: Activating DNS resource address=*.test-ipv6.com
06-28 19:41:21.032 19955 20213 I connlib : firezone_tunnel::client: Activating CIDR resource address=5.4.6.7/32 name=5.4.6.7
06-28 19:41:21.032 19955 20213 I connlib : firezone_tunnel::client: Activating CIDR resource address=10.0.32.101/32 name=IPerf3
06-28 19:41:21.032 19955 20213 I connlib : firezone_tunnel::dns: Activating DNS resource address=ifconfig.net
06-28 19:41:21.032 19955 20213 I connlib : firezone_tunnel::dns: Activating DNS resource address=*.slack-imgs.com
06-28 19:41:21.032 19955 20213 I connlib : firezone_tunnel::dns: Activating DNS resource address=*.google.com
06-28 19:41:21.032 19955 20213 I connlib : firezone_tunnel::client: Activating CIDR resource address=10.0.0.5/32 name=10.0.0.5
06-28 19:41:21.032 19955 20213 I connlib : firezone_tunnel::dns: Activating DNS resource address=*.githubassets.com
06-28 19:41:21.032 19955 20213 I connlib : firezone_tunnel::dns: Activating DNS resource address=dnsleaktest.com
06-28 19:41:21.033 19955 20213 I connlib : firezone_tunnel::dns: Activating DNS resource address=*.slack-edge.com
06-28 19:41:21.033 19955 20213 I connlib : firezone_tunnel::dns: Activating DNS resource address=*.github.com
06-28 19:41:21.033 19955 20213 I connlib : firezone_tunnel::dns: Activating DNS resource address=speed.cloudflare.com
06-28 19:41:21.033 19955 20213 I connlib : firezone_tunnel::dns: Activating DNS resource address=*.githubusercontent.com
06-28 19:41:21.033 19955 20213 I connlib : firezone_tunnel::client: Activating CIDR resource address=10.0.14.11/32 name=Staging resource performance
06-28 19:41:21.033 19955 20213 I connlib : firezone_tunnel::dns: Activating DNS resource address=*.whatismyip.com
06-28 19:41:21.033 19955 20213 I connlib : firezone_tunnel::client: Activating CIDR resource address=10.0.0.8/32 name=10.0.0.8
06-28 19:41:21.033 19955 20213 I connlib : firezone_tunnel::client: Activating CIDR resource address=9.9.9.9/32 name=Quad9 DNS
06-28 19:41:21.034 19955 20213 I connlib : firezone_tunnel::client: Activating CIDR resource address=10.0.32.10/32 name=CoreDNS
06-28 19:41:21.216 19955 20213 I connlib : snownet::node: Added new TURN server id=bd6e9d1a-4696-4f8b-8337-aab5d5cea810 address=Dual { v4: 35.197.171.113:3478, v6: [2600:1900:40b0:1504:0:27::]:3478 }
```
---------
Signed-off-by: Thomas Eizinger <thomas@eizinger.io>
|
||
|
|
8655b711db |
fix(connlib): Don't use operatingSystemVersionString on Apple OSes (#5628)
The [HTTP 1.1 RFC](https://datatracker.ietf.org/doc/html/rfc2616) states that HTTP headers should be US-ASCII. This is not the case when the macOS Client is run from a host that has a non-English language selected as its system default due to the way we build the user agent. This PR fixes that by normalizing how we build the user agent by more granularly selecting which fields compose it, and not just relying on OS-provided version strings that may contain non-ASCII characters. fixes https://github.com/firezone/firezone/issues/5467 --------- Signed-off-by: Jamil <jamilbk@users.noreply.github.com> |
||
|
|
e5cba1caf4 |
refactor(apple): use fmt::Layer with custom writer (#5623)
Currently, we use the `tracing-oslog` crate to ingest logs on MacOS and iOS. This crate has a "feature" where it creates so called "Activities" for spans. Whilst that may initially sound useful, Apple's UI for viewing these activities is absolutely useless. Instead of tinkering around with that, we remove the `tracing-oslog` crate and let `tracing-subscriber` format our logs first and then only send a single string to the oslog backend. Related: #5619. |
||
|
|
9fe070c72f |
chore(aws-infra): log all portal messages on the gateway (#5615)
Now that we have split the `wire` target into sub-targets, we can selectively enable the wire messages to and from the API which is very helpful in debugging what messages are being sent. |
||
|
|
37d3ebbb7c |
chore(gui-client/windows): bump tauri-winrt-notification (#5627)
This eliminates `windows` 0.54.0 so it should speed up Windows builds a little. It's 6% faster on my Macbook according to `cargo build --timing`, in debug mode. |
||
|
|
d3a091f90b |
ci: pre-install required tools for smoke tests (#5620)
Currently, the smoke tests rebuild the `dump_syms` and `minidump-stackwalk` tools from scratch every time which is slow, especially on Windows. We can speed this up by utilising the `taiki-e/install-action` GitHub action which discovers and downloads the latest binary releases of those projects and installs them into $PATH. I think those binaries might also be cached as part of the Rust cache action (https://github.com/Swatinem/rust-cache) so the visible speed-up is only within a few seconds and comes from the binaries not being re-built inside the script. Caching those binaries on Github still requires us to build them at least once and also rebuild them in case the cache gets invalidated. Hence I still think this is a good idea on its own. |
||
|
|
a315c49b3c |
chore(firezone-tunnel/windows): reduce ring buffer from 64 MiB to 1 MiB (#5609)
Oops. It runs the same either way so we definitely don't need all that RAM to be tied up. The Linux and macOS Clients probably have similar buffer sizes already. I tested before and after with CloudFlare's speed test and got roughly 140/12 with latency 50 ms both times. The error bars on speed tests are pretty wide, but we definitely aren't falling 60 MiB behind on processing and then catching up. ```[tasklist] ### Tasks - [x] (failed, can't do it right now) ~~Log if we knowingly drop a lot of packets~~ - [x] Extract constant - [x] Add comment about not knowing if we drop packets - [x] Merge - [ ] (skipped) Test while the CPU is loaded ``` |
||
|
|
649db863ca |
chore(gui-client): explain why the update check has redirects disabled (#5608)
Closes #5383 |
||
|
|
ed34ca096b |
chore(gateway): remove dead IP detection (#5618)
This does not work as well as intended and spams the logs. We may need #5542 before we can implement this properly. Fixes: #5593. |
||
|
|
fc8d89ea73 |
docs: Add AWS NAT Gateway example (#5543)
- Adds the AWS equivalent of our GCP scalable NAT Gateway. - Adds a new kb section `/kb/automate` that will contain various automation / IaaC recipes going forward. It's better to have these guides in the main docs with all the other info. ~~Will update the GCP example in another PR.~~ Portal helper docs in the gateway deploy page will come in another PR after this is merged. |