Repository navigation
[pull] main from MaterializeInc:main - #1297
Merged
Merged
Conversation
…/dataflow-visualizer in the simple group across 1 directory (#35875) Bumps the simple group with 1 update in the /test/dataflow-visualizer directory: [@playwright/test](https://github.com/microsoft/playwright). Updates `@playwright/test` from 1.58.2 to 1.61.1 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/microsoft/playwright/releases">@playwright/test's releases</a>.</em></p> <blockquote> <h2>v1.61.1</h2> <h3>Bug Fixes</h3> <ul> <li><a href="https://redirect.github.com/microsoft/playwright/issues/41365">#41365</a> [Bug]: Expect.Extend matcher with same name as default matcher in same expect instance overrides default matchers implementation to custom matcher</li> <li><a href="https://redirect.github.com/microsoft/playwright/issues/41351">#41351</a> [Bug]: Playwright UI mode: apiRequestContext._wrapApiCall reports unexpected number of bytes (same test passes in headed mode)</li> <li><a href="https://redirect.github.com/microsoft/playwright/issues/41360">#41360</a> [Bug]: Trace viewer: message times in websockets are downscaled by 1000</li> <li><a href="https://redirect.github.com/microsoft/playwright/issues/41311">#41311</a> [Bug]: [Regression]: Sync loader throws "context.conditions?.includes is not a function" on Node 22.15</li> <li><a href="https://redirect.github.com/microsoft/playwright/issues/41371">#41371</a> [Regression]: Sync ESM loader (registerHooks) fails to resolve extensionless .ts subpath imports across pnpm workspace symlinks</li> </ul> <h2>v1.61.0</h2> <h2>🔑 WebAuthn passkeys</h2> <p>New <a href="https://playwright.dev/docs/api/class-credentials">Credentials</a> virtual authenticator, available via <a href="https://playwright.dev/docs/api/class-browsercontext#browser-context-credentials">browserContext.credentials</a>, lets tests register passkeys and answer <code>navigator.credentials.create()</code> / <code>navigator.credentials.get()</code> ceremonies in the page — no real hardware key required, works in all browsers:</p> <pre lang="js"><code>const context = await browser.newContext(); <p>// Seed a passkey your backend provisioned for a test user. await context.credentials.create('example.com', { id: credentialId, userHandle, privateKey, publicKey, }); await context.credentials.install();</p> <p>const page = await context.newPage(); await page.goto('<a href="https://example.com/login">https://example.com/login</a>'); // The page's navigator.credentials.get() is answered with the seeded passkey. </code></pre></p> <p>You can also let the app register a passkey once in a setup test, read it back with <a href="https://playwright.dev/docs/api/class-credentials#credentials-get">credentials.get()</a>, and seed it into later tests — see <a href="https://playwright.dev/docs/api/class-credentials">Credentials</a> for details.</p> <h2>🗃️ Web Storage</h2> <p>New <a href="https://playwright.dev/docs/api/class-webstorage">WebStorage</a> API, available via <a href="https://playwright.dev/docs/api/class-page#page-local-storage">page.localStorage</a> and <a href="https://playwright.dev/docs/api/class-page#page-session-storage">page.sessionStorage</a>, reads and writes the page's storage for the current origin:</p> <pre lang="js"><code>await page.localStorage.setItem('token', 'abc'); const token = await page.localStorage.getItem('token'); const items = await page.sessionStorage.items(); </code></pre> <h2>New APIs</h2> <h3>Network</h3> <ul> <li><a href="https://playwright.dev/docs/api/class-apiresponse#api-response-security-details">apiResponse.securityDetails()</a> and <a href="https://playwright.dev/docs/api/class-apiresponse#api-response-server-addr">apiResponse.serverAddr()</a> mirror the browser-side <a href="https://playwright.dev/docs/api/class-response#response-security-details">response.securityDetails()</a> and <a href="https://playwright.dev/docs/api/class-response#response-server-addr">response.serverAddr()</a>.</li> </ul> <h3>Browser and Screencast</h3> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/microsoft/playwright/commit/39e3553a4f283a41134d75d7e404484bd9e6865a"><code>39e3553</code></a> cherry-pick(<a href="https://redirect.github.com/microsoft/playwright/issues/41399">#41399</a>): fix(test): load require-reached files as commonjs in syn...</li> <li><a href="https://github.com/microsoft/playwright/commit/4328122a0fa91df1be287f12d26f272f598ccca7"><code>4328122</code></a> chore: mark v1.61.1 (<a href="https://redirect.github.com/microsoft/playwright/issues/41404">#41404</a>)</li> <li><a href="https://github.com/microsoft/playwright/commit/2c29a94ed59a2dbb2cb2553ee7d1ba429f027826"><code>2c29a94</code></a> fix(tracing): stop recording websocket frames outside of chunks (<a href="https://redirect.github.com/microsoft/playwright/issues/41398">#41398</a>)</li> <li><a href="https://github.com/microsoft/playwright/commit/4324b1904199c58ae56d864390f5210df18e33f6"><code>4324b19</code></a> cherry-pick(<a href="https://redirect.github.com/microsoft/playwright/issues/41367">#41367</a>): fix(test): keep builtin expect matchers on base extend</li> <li><a href="https://github.com/microsoft/playwright/commit/041e7e30002e7c384e1918c29720b34c435145f4"><code>041e7e3</code></a> cherry-pick(<a href="https://redirect.github.com/microsoft/playwright/issues/41364">#41364</a>): fix(har): <code>WebSocket</code> message timestamps should be in mi...</li> <li><a href="https://github.com/microsoft/playwright/commit/b8a0fc33932399fc5cfcd211165cf16f8ca01d71"><code>b8a0fc3</code></a> cherry-pick(<a href="https://redirect.github.com/microsoft/playwright/issues/41309">#41309</a>, <a href="https://redirect.github.com/microsoft/playwright/issues/43149">#43149</a>): Revert "fix(firefox): treat `navigationCommitted...</li> <li><a href="https://github.com/microsoft/playwright/commit/b5a31759e6611397bf3afaaa6049a420a5f082bd"><code>b5a3175</code></a> cherry-pick(<a href="https://redirect.github.com/microsoft/playwright/issues/41319">#41319</a>): fix(loader): support other node versions</li> <li><a href="https://github.com/microsoft/playwright/commit/d4724a91b280ae1ee9a87c426e9d6a953c59756e"><code>d4724a9</code></a> cherry-pick(<a href="https://redirect.github.com/microsoft/playwright/issues/41290">#41290</a>): feat(docker): add Ubuntu 26.04 (Resolute Raccoon) image</li> <li><a href="https://github.com/microsoft/playwright/commit/1cc5a90cfa3eaa430b1a991963100f95126caa47"><code>1cc5a90</code></a> cherry-pick(<a href="https://redirect.github.com/microsoft/playwright/issues/41295">#41295</a>): chore: PLAYWRIGHT_TRACING_NO_WEBSOCKET_FRAMES and PLAYWR...</li> <li><a href="https://github.com/microsoft/playwright/commit/a6772bdede34028cbbd417a3b3d778801899e870"><code>a6772bd</code></a> cherry-pick(<a href="https://redirect.github.com/microsoft/playwright/issues/41280">#41280</a>): Revert "fix(trace-viewer): add keyboard navigation to `N...</li> <li>Additional commits viewable in <a href="https://github.com/microsoft/playwright/compare/v1.58.2...v1.61.1">compare view</a></li> </ul> </details> <br /> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [security-framework](https://github.com/kornelski/rust-security-framework) from 2.11.1 to 3.7.0. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/kornelski/rust-security-framework/commit/5f6e65114b77d5bc161d2b099cad09f2a67609d2"><code>5f6e651</code></a> Bump</li> <li><a href="https://github.com/kornelski/rust-security-framework/commit/0b6b4ecff6ba0b93193b80ba72f261d50c9c94a8"><code>0b6b4ec</code></a> Key attributes</li> <li><a href="https://github.com/kornelski/rust-security-framework/commit/73cf4645426ea19798e167177de12143939b7434"><code>73cf464</code></a> Mark deprecated</li> <li><a href="https://github.com/kornelski/rust-security-framework/commit/91e22a9c73a41490eed68a676ffdec73ddf71fd1"><code>91e22a9</code></a> Deprecate trait</li> <li><a href="https://github.com/kornelski/rust-security-framework/commit/1aab2fc212abed172f295daadfd76483f85881c4"><code>1aab2fc</code></a> Cache more</li> <li><a href="https://github.com/kornelski/rust-security-framework/commit/61d8c9d02de5a64096b0f3923af4da3414d49502"><code>61d8c9d</code></a> Cache registry</li> <li><a href="https://github.com/kornelski/rust-security-framework/commit/229dfd46dd90aeabe137afcc30ece900feb3d3f1"><code>229dfd4</code></a> Re-enable tests</li> <li><a href="https://github.com/kornelski/rust-security-framework/commit/6829c2ecc745ab4eddc2c9b9dacfd58efa863ab0"><code>6829c2e</code></a> Regenerate test certs</li> <li><a href="https://github.com/kornelski/rust-security-framework/commit/758d045b6a6c3427afc358d3f850848fdcdf98cc"><code>758d045</code></a> Rename tests</li> <li><a href="https://github.com/kornelski/rust-security-framework/commit/31d29f8d8e6ebb2df6408cd9e036ce066de86150"><code>31d29f8</code></a> Allow string-like alpn</li> <li>Additional commits viewable in <a href="https://github.com/kornelski/rust-security-framework/compare/v2.11.1...v3.7.0">compare view</a></li> </ul> </details> <br /> > **Note** > Automatic rebases have been disabled on this pull request as it has been open for over 30 days. Co-authored-by: Dennis Felsing <dennis@felsing.org> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Bumps [opentelemetry_sdk](https://github.com/open-telemetry/opentelemetry-rust) from 0.31.0 to 0.32.1. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/open-telemetry/opentelemetry-rust/blob/main/docs/release_0.32.md">opentelemetry_sdk's changelog</a>.</em></p> <blockquote> <h1>Release Notes 0.32</h1> <p>OpenTelemetry Rust 0.32 continues to drive the Logs, Metrics, and Distributed Tracing components forward. The Logs and Metrics API and SDK remain stable, with no breaking changes in this release. The OTLP Exporters and the Distributed Tracing API/SDK remain in pre-stable states (Release-Candidate and Beta respectively), and this release introduces a small number of intentional breaking changes in those areas to prepare them for stabilization.</p> <p>For detailed changelogs of individual crates, please refer to their respective changelog files. This document serves as a summary of the main changes.</p> <h2>Key Changes</h2> <h3>Metrics SDK</h3> <ol> <li> <p><strong>Bound instruments (experimental)</strong>: Added <code>Counter::bind()</code> and <code>Histogram::bind()</code> returning pre-bound measurement handles (<code>BoundCounter<T></code>, <code>BoundHistogram<T></code>). Bound instruments resolve the attribute-to-aggregator mapping once at bind time and cache the result, eliminating per-call HashMap lookups on the hot path. Benchmarks show ~28x speedup for counter operations and ~9x for histograms. Gated behind the <code>experimental_metrics_bound_instruments</code> feature flag.</p> </li> <li> <p><strong>Delta collection efficiency</strong>: Delta metrics collection now uses in-place eviction instead of draining the HashMap on every collect cycle. Stale attribute sets that received no measurements since the last collection are evicted.</p> </li> <li> <p><strong>Stable <code>Aggregation</code> API</strong>: <code>Aggregation</code> and <code>StreamBuilder::with_aggregation()</code> are now stable and no longer require the <code>spec_unstable_metrics_views</code> feature flag.</p> </li> </ol> <h3>Logs</h3> <ol> <li> <p><strong>Tracing-span attribute enrichment (experimental)</strong>: The <code>opentelemetry-appender-tracing</code> crate can now copy attributes from active <code>tracing</code> spans onto each emitted log record. ("Span" here refers to <code>tracing::span!</code>, not an <code>opentelemetry::trace::Span</code>.) Enrichment is disabled by default with zero per-span overhead, and is gated behind the new <code>experimental_span_attributes</code> cargo feature.</p> </li> <li> <p><strong><code>spec_unstable_logs_enabled</code> removed</strong>: The capability (and the backing specification) is now stable and is enabled by default. The feature flag has been removed.</p> </li> </ol> <h3>Distributed Tracing (Beta)</h3> <p>The Distributed Tracing API and SDK remain in beta. This release contains intentional breaking changes to clean up the public surface ahead of</p> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/open-telemetry/opentelemetry-rust/commit/74cb6f3a4129bf11fa3191f28d38c518c4ec4ae6"><code>74cb6f3</code></a> chore: Release opentelemetry-semantic-conventions 0.32.1 (<a href="https://redirect.github.com/open-telemetry/opentelemetry-rust/issues/3562">#3562</a>)</li> <li><a href="https://github.com/open-telemetry/opentelemetry-rust/commit/10dde1813e2ec93f819b115b50f0c9746f4b7ddf"><code>10dde18</code></a> chore(sdk): add missing changelog entry (<a href="https://redirect.github.com/open-telemetry/opentelemetry-rust/issues/3550">#3550</a>)</li> <li><a href="https://github.com/open-telemetry/opentelemetry-rust/commit/ec2da129b01b1e88ec17e28a55ba05001cc2aa1c"><code>ec2da12</code></a> refactor: leverage static str key when possible (<a href="https://redirect.github.com/open-telemetry/opentelemetry-rust/issues/3529">#3529</a>)</li> <li><a href="https://github.com/open-telemetry/opentelemetry-rust/commit/90a39a0b5b1db04c495a213090c152f6ae3454bf"><code>90a39a0</code></a> feat(api): accept quoted-key fields in otel logging macros (<a href="https://redirect.github.com/open-telemetry/opentelemetry-rust/issues/3567">#3567</a>)</li> <li><a href="https://github.com/open-telemetry/opentelemetry-rust/commit/8c922bc62dcc4b114faf2e74e0d4a50efc4433f5"><code>8c922bc</code></a> feat(appender-tracing): add builder support for custom instrumentation scope ...</li> <li><a href="https://github.com/open-telemetry/opentelemetry-rust/commit/fb2af9d76e26201b0848a837231b44ebad30867d"><code>fb2af9d</code></a> feat(metrics): add BoundUpDownCounter under experimental_metrics_bound_instru...</li> <li><a href="https://github.com/open-telemetry/opentelemetry-rust/commit/1b3846ca8f0c204007c91b0a9860e498c674038f"><code>1b3846c</code></a> feat(metrics): add BoundGauge under experimental_metrics_bound_instruments (#...</li> <li><a href="https://github.com/open-telemetry/opentelemetry-rust/commit/ee359dbb863e149d0277031a3b3fb9b41f7bee3d"><code>ee359db</code></a> fix: remove reqwest-rustls-webpki-roots (<a href="https://redirect.github.com/open-telemetry/opentelemetry-rust/issues/3524">#3524</a>)</li> <li><a href="https://github.com/open-telemetry/opentelemetry-rust/commit/4d4fd4d4b3a2ebf203efa6612f397034925c82fe"><code>4d4fd4d</code></a> chore: Bump semantic-conventions to v1.42.0 (<a href="https://redirect.github.com/open-telemetry/opentelemetry-rust/issues/3561">#3561</a>)</li> <li><a href="https://github.com/open-telemetry/opentelemetry-rust/commit/69213f2047647b56bc27dfa84726d3ff94a945d3"><code>69213f2</code></a> fix(prometheus-exporter): Concatenate metric attributes with Scope during col...</li> <li>Additional commits viewable in <a href="https://github.com/open-telemetry/opentelemetry-rust/compare/v0.31.0...opentelemetry-semantic-conventions-0.32.1">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 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) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/MaterializeInc/materialize/network/alerts). </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Fixes: https://buildkite.com/materialize/nightly/builds/18090 We haven't had to use version overrides in scalability framework in a while, and they have apparently broken! Test run: https://buildkite.com/materialize/nightly/builds/18091
…w-visualizer (#35721) Bumps [typescript](https://github.com/microsoft/TypeScript) from 5.7.3 to 6.0.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 6.0</h2> <p>For release notes, check out the <a href="https://devblogs.microsoft.com/typescript/announcing-typescript-6-0/">release announcement blog post</a>.</p> <ul> <li><a href="https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93&q=milestone%3A%22TypeScript+6.0.0%22">fixed issues query for TypeScript 6.0.0 (Beta)</a>.</li> <li><a href="https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93&q=milestone%3A%22TypeScript+6.0.1%22">fixed issues query for TypeScript 6.0.1 (RC)</a>.</li> <li><a href="https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93&q=milestone%3A%22TypeScript+6.0.2%22">fixed issues query for TypeScript 6.0.2 (Stable)</a>.</li> </ul> <p>Downloads are available on:</p> <ul> <li><a href="https://www.npmjs.com/package/typescript">npm</a></li> </ul> <h2>TypeScript 6.0 Beta</h2> <p>For release notes, check out the <a href="https://devblogs.microsoft.com/typescript/announcing-typescript-6-0-beta/">release announcement</a>.</p> <ul> <li><a href="https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93&q=milestone%3A%22TypeScript+6.0.0%22+is%3Aclosed+">fixed issues query for Typescript 6.0.0 (Beta)</a>.</li> </ul> <p>Downloads are available on:</p> <ul> <li><a href="https://www.npmjs.com/package/typescript">npm</a></li> </ul> <h2>TypeScript 5.9.3</h2> <p>Note: this tag was recreated to point at the correct commit. The npm package contained the correct content.</p> <p>For release notes, check out the <a href="https://devblogs.microsoft.com/typescript/announcing-typescript-5-9/">release announcement</a></p> <ul> <li><a href="https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93&q=milestone%3A%22TypeScript+5.9.0%22+is%3Aclosed+">fixed issues query for Typescript 5.9.0 (Beta)</a>.</li> <li><a href="https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93&q=milestone%3A%22TypeScript+5.9.1%22+is%3Aclosed+">fixed issues query for Typescript 5.9.1 (RC)</a>.</li> <li><em>No specific changes for TypeScript 5.9.2 (Stable)</em></li> <li><a href="https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93&q=milestone%3A%22TypeScript+5.9.3%22+is%3Aclosed+">fixed issues query for Typescript 5.9.3 (Stable)</a>.</li> </ul> <p>Downloads are available on:</p> <ul> <li><a href="https://www.npmjs.com/package/typescript">npm</a></li> </ul> <h2>TypeScript 5.9</h2> <p>Note: this tag was recreated to point at the correct commit. The npm package contained the correct content.</p> <p>For release notes, check out the <a href="https://devblogs.microsoft.com/typescript/announcing-typescript-5-9/">release announcement</a></p> <ul> <li><a href="https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93&q=milestone%3A%22TypeScript+5.9.0%22+is%3Aclosed+">fixed issues query for Typescript 5.9.0 (Beta)</a>.</li> <li><a href="https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93&q=milestone%3A%22TypeScript+5.9.1%22+is%3Aclosed+">fixed issues query for Typescript 5.9.1 (RC)</a>.</li> <li><em>No specific changes for TypeScript 5.9.2 (Stable)</em></li> </ul> <p>Downloads are available on:</p> <ul> <li><a href="https://www.npmjs.com/package/typescript">npm</a></li> </ul> <h2>TypeScript 5.9 RC</h2> <p>Note: this tag was recreated to point at the correct commit. The npm package contained the correct content.</p> <p>For release notes, check out the <a href="https://devblogs.microsoft.com/typescript/announcing-typescript-5-9-rc/">release announcement</a></p> <ul> <li><a href="https://github.com/Microsoft/TypeScript/issues?utf8=%E2%9C%93&q=milestone%3A%22TypeScript+5.9.0%22+is%3Aclosed+">fixed issues query for Typescript 5.9.0 (Beta)</a>.</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/microsoft/TypeScript/commit/607a22a90d1a5a1b507ce01bb8cd7ec020f954e7"><code>607a22a</code></a> Bump version to 6.0.2 and LKG</li> <li><a href="https://github.com/microsoft/TypeScript/commit/9e72ab71b575e26795d0d9eac3d2d9957beed17c"><code>9e72ab7</code></a> 🤖 Pick PR <a href="https://redirect.github.com/microsoft/TypeScript/issues/63239">#63239</a> (Fix missing lib files in reused pro...) into release-6.0 (#...</li> <li><a href="https://github.com/microsoft/TypeScript/commit/35ff23d4b0cc715691323ebe54f523c16fe6e3a5"><code>35ff23d</code></a> 🤖 Pick PR <a href="https://redirect.github.com/microsoft/TypeScript/issues/63163">#63163</a> (Port anyFunctionType subtype fix an...) into release-6.0 (#...</li> <li><a href="https://github.com/microsoft/TypeScript/commit/e175b69138038953d4e85bf6529afe88d56d8fbe"><code>e175b69</code></a> Bump version to 6.0.1-rc and LKG</li> <li><a href="https://github.com/microsoft/TypeScript/commit/af4caac0e91e838c46b3fdc1c9afacad68800f89"><code>af4caac</code></a> Update LKG</li> <li><a href="https://github.com/microsoft/TypeScript/commit/8efd7e8544d8b35c9b33bca44a3124aa2613bf09"><code>8efd7e8</code></a> Merge remote-tracking branch 'origin/main' into release-6.0</li> <li><a href="https://github.com/microsoft/TypeScript/commit/206ed1a00ffde637d821bbb3172d1488e3d949e8"><code>206ed1a</code></a> Deprecate assert in import() (<a href="https://redirect.github.com/microsoft/TypeScript/issues/63172">#63172</a>)</li> <li><a href="https://github.com/microsoft/TypeScript/commit/e688ac8bc3cbb698c4341ee06401bd6beeb1c4ba"><code>e688ac8</code></a> Update dependencies (<a href="https://redirect.github.com/microsoft/TypeScript/issues/63156">#63156</a>)</li> <li><a href="https://github.com/microsoft/TypeScript/commit/29b300deb56c775f19c2f0528012896e4d1db3e0"><code>29b300d</code></a> Bump the github-actions group across 1 directory with 2 updates (<a href="https://redirect.github.com/microsoft/TypeScript/issues/63205">#63205</a>)</li> <li><a href="https://github.com/microsoft/TypeScript/commit/0c2c7a358297d66df690230deaed8c98e7d77c04"><code>0c2c7a3</code></a> DOM update (<a href="https://redirect.github.com/microsoft/TypeScript/issues/63183">#63183</a>)</li> <li>Additional commits viewable in <a href="https://github.com/microsoft/TypeScript/compare/v5.7.3...v6.0.2">compare view</a></li> </ul> </details> <br /> > **Note** > Automatic rebases have been disabled on this pull request as it has been open for over 30 days. Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
…36589) Bumps [copy-to-clipboard](https://github.com/sudodoki/copy-to-clipboard) from 3.3.3 to 4.0.2. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/sudodoki/copy-to-clipboard/releases">copy-to-clipboard's releases</a>.</em></p> <blockquote> <h2>v4.0.2</h2> <p><a href="https://github.com/sudodoki/copy-to-clipboard/compare/v4.0.1...v4.0.2">compare changes</a></p> <h3>🩹 Fixes</h3> <ul> <li>Make sure execCommand works in fullscreen (<a href="https://redirect.github.com/sudodoki/copy-to-clipboard/pull/158">#158</a>)</li> </ul> <h3>🏡 Chore</h3> <ul> <li>Bump axios from 1.14.0 to 1.15.2 (<a href="https://redirect.github.com/sudodoki/copy-to-clipboard/pull/155">#155</a>)</li> <li>Bump follow-redirects from 1.15.11 to 1.16.0 (<a href="https://redirect.github.com/sudodoki/copy-to-clipboard/pull/157">#157</a>)</li> <li>Bump basic-ftp from 5.2.0 to 5.3.0 (<a href="https://redirect.github.com/sudodoki/copy-to-clipboard/pull/156">#156</a>)</li> </ul> <h3>❤️ Contributors</h3> <ul> <li>Джон, Просто Джон (<a href="https://github.com/sudodoki"><code>@sudodoki</code></a>)</li> </ul> <h2>v4.0.1</h2> <p><a href="https://github.com/sudodoki/copy-to-clipboard/compare/v4.0.0...v4.0.1">compare changes</a></p> <h3>🏡 Chore</h3> <ul> <li>Fix copy in modal for execCommand fallback (<a href="https://redirect.github.com/sudodoki/copy-to-clipboard/pull/151">#151</a>)</li> <li>Add changelog (<a href="https://redirect.github.com/sudodoki/copy-to-clipboard/pull/153">#153</a>)</li> </ul> <h3>✅ Tests</h3> <ul> <li>Add e2e scenario for modal tests (<a href="https://redirect.github.com/sudodoki/copy-to-clipboard/pull/152">#152</a>)</li> </ul> <h3>❤️ Contributors</h3> <ul> <li>Джон, Просто Джон (<a href="https://github.com/sudodoki"><code>@sudodoki</code></a>)</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/sudodoki/copy-to-clipboard/blob/main/CHANGELOG.md">copy-to-clipboard's changelog</a>.</em></p> <blockquote> <h2>v4.0.2</h2> <p><a href="https://github.com/sudodoki/copy-to-clipboard/compare/v4.0.1...v4.0.2">compare changes</a></p> <h3>🩹 Fixes</h3> <ul> <li>Make sure execCommand works in fullscreen (<a href="https://redirect.github.com/sudodoki/copy-to-clipboard/pull/158">#158</a>)</li> </ul> <h3>🏡 Chore</h3> <ul> <li>Bump axios from 1.14.0 to 1.15.2 (<a href="https://redirect.github.com/sudodoki/copy-to-clipboard/pull/155">#155</a>)</li> <li>Bump follow-redirects from 1.15.11 to 1.16.0 (<a href="https://redirect.github.com/sudodoki/copy-to-clipboard/pull/157">#157</a>)</li> <li>Bump basic-ftp from 5.2.0 to 5.3.0 (<a href="https://redirect.github.com/sudodoki/copy-to-clipboard/pull/156">#156</a>)</li> </ul> <h3>❤️ Contributors</h3> <ul> <li>Джон, Просто Джон (<a href="https://github.com/sudodoki"><code>@sudodoki</code></a>)</li> </ul> <h2>v4.0.1</h2> <p><a href="https://github.com/sudodoki/copy-to-clipboard/compare/v4.0.0...v4.0.1">compare changes</a></p> <h3>🏡 Chore</h3> <ul> <li>Fix copy in modal for execCommand fallback (<a href="https://redirect.github.com/sudodoki/copy-to-clipboard/pull/151">#151</a>)</li> <li>Add changelog (<a href="https://redirect.github.com/sudodoki/copy-to-clipboard/pull/153">#153</a>)</li> </ul> <h3>✅ Tests</h3> <ul> <li>Add e2e scenario for modal tests (<a href="https://redirect.github.com/sudodoki/copy-to-clipboard/pull/152">#152</a>)</li> </ul> <h3>❤️ Contributors</h3> <ul> <li>Джон, Просто Джон (<a href="https://github.com/sudodoki"><code>@sudodoki</code></a>)</li> </ul> <h2>v4.0.0</h2> <p><a href="https://github.com/sudodoki/copy-to-clipboard/compare/v3.3.3...v4.0.0">compare changes</a></p> <h3>⚠️ Breaking Changes</h3> <ul> <li><code>copy()</code> is now async — returns <code>Promise<boolean></code> instead of <code>boolean</code>. All call sites must be updated to <code>await copy(...)</code> or <code>.then(...)</code>.</li> <li>IE11 support dropped — <code>window.clipboardData</code> and all IE-specific code paths removed.</li> <li><code>window.prompt()</code> fallback is now opt-in — pass <code>options.fallbackToPrompt: true</code> to restore. Off by default.</li> <li>Build output moved to <code>dist/</code> — direct <code>require('copy-to-clipboard/index.js')</code> imports will break; use the package name only.</li> </ul> <h3>🚀 Enhancements</h3> <ul> <li><code>navigator.clipboard.writeText()</code> is now the default copy path in secure contexts (HTTPS / <code>localhost</code>).</li> <li><code>navigator.clipboard.write()</code> with <code>ClipboardItem</code> for rich text / HTML copying when <code>options.format</code> or <code>options.onCopy</code> is set.</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/sudodoki/copy-to-clipboard/commit/bf69f76573537765769849e2b9f4efc6b8b51177"><code>bf69f76</code></a> chore(release): v4.0.2</li> <li><a href="https://github.com/sudodoki/copy-to-clipboard/commit/e8329c774d899991d5748fcf1901f42d98b15f9e"><code>e8329c7</code></a> fix: make sure execCommand works in fullscreen (<a href="https://redirect.github.com/sudodoki/copy-to-clipboard/issues/158">#158</a>)</li> <li><a href="https://github.com/sudodoki/copy-to-clipboard/commit/0c4238ce997b08ca02b7f2745707518a58af3af6"><code>0c4238c</code></a> chore: Bump basic-ftp from 5.2.0 to 5.3.0 (<a href="https://redirect.github.com/sudodoki/copy-to-clipboard/issues/156">#156</a>)</li> <li><a href="https://github.com/sudodoki/copy-to-clipboard/commit/d8283c20dd018bba76ea6c66c19adbb02c3354d2"><code>d8283c2</code></a> chore: Bump follow-redirects from 1.15.11 to 1.16.0 (<a href="https://redirect.github.com/sudodoki/copy-to-clipboard/issues/157">#157</a>)</li> <li><a href="https://github.com/sudodoki/copy-to-clipboard/commit/75ee47c6ff43514bdfcf5359465e38d671521c63"><code>75ee47c</code></a> chore: Bump axios from 1.14.0 to 1.15.2 (<a href="https://redirect.github.com/sudodoki/copy-to-clipboard/issues/155">#155</a>)</li> <li><a href="https://github.com/sudodoki/copy-to-clipboard/commit/91df35d1325a9d1439632ddb9e2b124960ba1fcc"><code>91df35d</code></a> chore(release): v4.0.1</li> <li><a href="https://github.com/sudodoki/copy-to-clipboard/commit/10420d668465bd51e7bba78ea3a64da05899d1ff"><code>10420d6</code></a> chore: add changelog (<a href="https://redirect.github.com/sudodoki/copy-to-clipboard/issues/153">#153</a>)</li> <li><a href="https://github.com/sudodoki/copy-to-clipboard/commit/89305890030f81d0011637e3c2adf52ce09c4d6b"><code>8930589</code></a> test: add e2e scenario for modal tests (<a href="https://redirect.github.com/sudodoki/copy-to-clipboard/issues/152">#152</a>)</li> <li><a href="https://github.com/sudodoki/copy-to-clipboard/commit/20329e816e6ba6783dcc82f4a09608bb5989dd89"><code>20329e8</code></a> chore: fix copy in modal for execCommand fallback (<a href="https://redirect.github.com/sudodoki/copy-to-clipboard/issues/151">#151</a>)</li> <li><a href="https://github.com/sudodoki/copy-to-clipboard/commit/bbb5d59f2bc8eb04d957070b81df5b0a127f7429"><code>bbb5d59</code></a> 4.0.0</li> <li>Additional commits viewable in <a href="https://github.com/sudodoki/copy-to-clipboard/compare/v3.3.3...v4.0.2">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) You can trigger a rebase of this PR 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 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> > **Note** > Automatic rebases have been disabled on this pull request as it has been open for over 30 days. Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…uilder (#37665) Bumps node from 24-trixie-slim to 26-trixie-slim. [](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 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>
### Motivation Operator names in Materialize can contain double quotes (e.g., `ArrangeBy[[Column(0, "id")]]`). When these names are embedded in DOT graph labels without proper escaping, the quotes terminate the label prematurely, causing GraphViz to reject the entire graph. This breaks the hierarchical-memory visualizer for any dataflow containing such operators. ### Description This PR fixes DOT graph generation by properly escaping special characters in operator names: 1. **Added `escapeDotLabel()` function** in `hierarchical-memory.jsx` that escapes backslashes and double quotes according to DOT syntax requirements. This function is applied to all operator name labels before they're embedded in DOT graph definitions. 2. **Improved error handling** across both visualizer files (`hierarchical-memory.jsx` and `memory.jsx`) by converting error objects to strings with `String(error)` instead of relying on implicit toString conversion. This ensures error messages render correctly even for non-standard error types. 3. **Enhanced test coverage** with a new test case that verifies graphs render correctly for operators with quoted names. The test creates a table and index (which generates an `ArrangeBy` operator with quotes), then verifies the visualizer renders without errors and displays the operator name correctly. 4. **Improved existing test robustness** by capturing page errors and checking for error messages in rendered content, rather than just checking if the body element exists. This provides better detection of render-time failures. ### Verification - New test `renders graphs for operator names containing double quotes` validates the fix by creating a table with an index and verifying the visualizer renders the operator name correctly without GraphViz errors. - Existing test `page renders without crashing after data load` enhanced to capture and assert on page errors. - All changes are backward compatible and don't affect existing functionality. https://claude.ai/code/session_01DSKUa7Eu3SxYdwLT2SoXXV Co-authored-by: Claude <noreply@anthropic.com>
Add docs for sinking to turbopuffer. ### Motivation Why does this change exist? Link to a GitHub issue, design doc, Slack thread, or explain the problem in a sentence or two. A reviewer who has no context should understand *why* after reading this section. If this implements or addresses an existing issue, it's enough to link to that: Closes <issue> Fixes <bug> etc. ### Description What does this PR actually do? Focus on the approach and any non-obvious decisions. The diff shows the code --- use this space to explain what the diff *can't* tell a reviewer. ### Verification How do you know this change is correct? Describe new or existing automated tests, or manual steps you took. --------- Co-authored-by: kay-kim <kay.kim@materialize.com>
…7958) Problem: To maintain cluster metrics we defined the MetricSink compute operator. However, there is no way to ask for one. We need a SQL surface that names a metric sink and a durable catalog representation that survives a restart. Solution: Add `CREATE METRIC SINK <name> IN CLUSTER <c> FROM <rel>` and `DROP METRIC SINK`, gated behind `enable_metric_sink`. Creating a sink writes a catalog item and nothing else: no dataflow is optimized or shipped, so a sink created today publishes no metrics. Planning checks that the `FROM` relation exposes the five columns the operator reads (`metric_name`, `metric_type`, `labels`, `value`, `help`). Note: order is not enforced and extra columns are fine. Nullability is not checked. Metric sinks need no new durable record. They persist as ordinary `Item`s and `item_type` works the type out from `create_sql`. However, the changes to audit and serialization does bump the catalog version. There are some gaps in: - `mz_comments` has no `MetricSink` branch, but `CommentObjectType` has no variant either, so `COMMENT ON METRIC SINK` does not parse and no such record can exist - `MZ_DEFAULT_PRIVILEGES` has no CASE arm, but `ON METRIC SINKS` is rejected during planning Note: `enable_metric_sink` is off by default Testing: - New `test/sqllogictest/metric_sink.slt`: the column contract and each way of violating it, `FROM` targets with no rows to read, `IF NOT EXISTS`, the flag-off refusal, and the seven views above answering with a metric sink present. **Note to reviewers**: The most important files to look at are: - ddl.rs which has the actual plan for create/drop metric sink - create_metric_sink.rs which writes the catalog item - objects.rs which defines the item_type - mz_catalog.rs small tweak here - rbac.rs/acl.rs for privilege handling - lib.rs/jsonb.rs for audit logging - v90_to_v91.rs the no-op migration - metric_sink.slt for what is expected behaviour The rest is threading this all through --------- Co-authored-by: Moritz Hoffmann <mh@materialize.com> Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )