Dan Lapid

This commit fixes a critical segfault in `workerd`'s JavaScript/V8 integration, preventing crashes when `Wrappables` (e.g., WebSockets) are destroyed after their V8 isolate has already shut down. This ensures stability for services utilizing object hibernation.

This is a breaking change to Workerd's internal tracing API, removing the ability to create or tag *only* user spans. It enforces that all tracing operations will now include both user and internal traces, impacting all Workerd API modules that interact with the tracing system.

This commit fixes an unsafe attachment issue within `workerd`'s SQL API and I/O context, improving the stability and security of how user spans are handled.

This revert impacts `workerd`'s internal alarm and timer management, particularly for actor-based services using `actor-cache` and `actor-sqlite`. This change restores the previous, stable behavior, fixing issues related to alarm synchronization or execution.

This commit fixes a bug in `workerd`'s HTTP API cache validation, preventing a `TypeError` when `cache: no-store` is used with a `cacheTtl` of -1. This ensures correct handling of specific caching configurations, improving reliability for services utilizing these headers.

This commit introduces a **bug fix** to the **worker** component, specifically addressing the handling of the `cacheTtl` property within **Cloudflare request initialization**. Previously, the `cache_ttl` field in the `CfProperties` struct was an `Option<u32>`, which prevented the representation of negative values. By changing this field to `Option<i32>` in `worker/src/request_init.rs`, the system can now correctly interpret and utilize negative `cacheTtl` values. This enhancement provides more robust and flexible caching control for **Cloudflare Worker requests**, allowing for behaviors like "no cache" to be properly expressed.

This commit introduces a **new feature** by adding a `cache` option to the **`RequestInit`** structure within the **`worker`** module, enabling explicit control over HTTP caching behavior. It integrates a new `CacheMode` enum, allowing developers to specify `NoStore`, `NoCache`, or `Reload` modes for requests, mirroring the Cloudflare Workers runtime. This **new capability** provides more granular control over how network requests interact with the HTTP cache, facilitated by enabling the `RequestCache` feature in the `web-sys` dependency.

This commit reverts a recently added feature in the `unenv-preset` module, removing support for the native `node:sqlite` module. This change removes a new capability, meaning any applications relying on `unenv-preset` will no longer have this specific `node:sqlite` integration.

This change affects all GitHub Actions CI/CD workflows, upgrading them to use larger runners. This is an operational improvement expected to enhance the performance and reliability of automated builds and tests.

This change introduces a new capability to the `RequestObserver` in `workerd/io`, enabling the reporting of internal exceptions. This enhances observability and error handling for internal system failures during request processing.

This change significantly improves Windows CI performance by enabling real symlinks, and enhances observability for all Bazel runs by consistently uploading build profiles and disk usage metrics.

This commit delivers a major performance and stability upgrade to the entire CI build system, with significant speedups for macOS builds and improved resource management across all configurations. Developers will benefit from substantially faster feedback loops and reduced CI job failures.

This commit extensively updates the `workerd` test suite to ensure compatibility with new `all-compat-flags` variants. It temporarily disables Python test variants due to their high impact on CI build times, indicating a significant adjustment to the testing process rather than a change in production functionality.

This change significantly enhances the `workerd test` framework, allowing developers to override compatibility dates for all workers via a new CLI flag and introducing new test variants for comprehensive compatibility flag testing. This provides a powerful new capability for validating worker behavior across different compatibility dates and configurations, impacting how all future `workerd` tests are written and executed.

This change introduces a new testing capability for `wd_test` within the `workerd` project, enabling tests to be run with all autogates enabled. This enhances the testing infrastructure for `workerd` developers, providing more comprehensive coverage for autogate-related functionality.

This commit introduces an experimental compatibility flag that allows Workerd users to enable Node.js-style global timers, providing a new capability to align timer function behavior with Node.js within the runtime. This change affects how global timer functions operate when the flag is enabled.

This commit fixes the timing of JSRPC 'Return' tracing events within `workerd`, ensuring they accurately reflect when a handler returns. This significantly improves the reliability and accuracy of observability data for JSRPC calls, impacting monitoring and debugging tools.

This is an isolated internal refactoring within `workerd`'s I/O and caching components. It improves code robustness by ensuring `featureFlagsForFl` is copied rather than passed by reference, preventing unintended side effects without user-facing impact.

This fixes `workerd`'s compatibility date logic by removing a default date for `fetchIterableTypeSupport`. This ensures the feature's behavior is explicitly controlled rather than implicitly enabled or disabled based on a compatibility date.

This change refines logging within `workerd`'s `IoContext` by removing a specific "timed out" log message from actors. It's an isolated diagnostic improvement that reduces log noise without altering core functionality.