Dominik Picheta

This commit **fixes a bug** where **Pyodide dynamic workers** would fail to initialize if a dedicated snapshot was missing. It addresses this by modifying the `checkSnapshotType` function in **Pyodide's snapshot handling** to **skip snapshot type validation** specifically for dynamic workers. To enable this, a new `IS_DYNAMIC_WORKER` constant is introduced in `src/pyodide/internal/metadata.ts`, and the **Workerd Pyodide API** is extended with an `isDynamicWorkerFlag` to properly identify these worker types. This ensures **Pyodide applications running in dynamic worker environments** can operate robustly without requiring specific snapshot configurations, improving their stability and deployment flexibility.

This commit performs a **documentation fix** by removing an erroneous "enable date" reference from the **Python workers** documentation. Specifically, it updates the `python-workers.md` file to accurately reflect that a particular compatibility flag does not possess an associated enable date. This **maintenance** task ensures the precision of the project's developer documentation, preventing potential confusion for users or contributors referencing the guide.

This commit **enhances error reporting** within the **Pyodide integration** by modifying its JavaScript fatal error handling logic. It specifically updates the `_REPLACEMENTS` section in `src/pyodide/helpers.bzl` to ensure that all fatal JavaScript errors are consistently reported by invoking `API.on_fatal`. This **maintenance fix** improves the reliability of error diagnostics, providing Pyodide users with more comprehensive information for debugging critical issues.

Adds a new test for Durable Object concurrency behavior in Python Workers. This is an isolated change to test utilities with no production impact, improving test coverage for `blockConcurrencyWhile`.

Updates the `AGENTS.md` documentation to highlight using boolean arguments as an anti-pattern. This is an isolated documentation change with no runtime impact on any system.

This enhancement to Workerd's Pyodide integration adds `sawWorkerFatal` to the `InvocationEnd` event, enabling better observability and diagnostics for fatal Pyodide worker terminations.

This commit fixes an internal issue within `workerd`'s socket API concerning TLS connection data management. It resolves a bug related to how TLS connections are initiated.

This fix significantly alters how Python Workers parse and handle HTTP request headers, ensuring raw header values and commas are preserved, especially for duplicate headers. This change impacts all Python Workers processing HTTP requests, potentially altering their behavior based on the compatibility flag.

This commit re-applies a change to `workerd`'s socket handling, specifically forcing `AsyncIoStream` shutdown on `Socket::close()`. This affects the core network I/O behavior within `workerd` and could impact resource management or connection stability.

This fixes a critical Use-After-Free vulnerability within `workerd`'s async I/O stream management, preventing potential crashes or security exploits for services utilizing these streams.

This is an isolated refactor within the Python `wd-tests` for the `workerd` server, removing redundant syntax. It has no impact on production code or functionality.

This commit improves the robustness of Workerd's sockets API by adding a check for socket closure before starting TLS, preventing potential errors or crashes in that specific scenario.

This is an isolated change removing a Python test for `node_compat_v2` within the `workerd` server's test suite. It has no impact on production code or functionality, only on test coverage.

This refactor improves the internal structure and maintainability of the Workerd Python Worker module registration. It is an isolated change with no direct impact on external behavior or production functionality.

This fixes a critical module loading issue affecting Workerd's Python Workers when `nodecompat v2` is enabled, ensuring Python applications can reliably load modules in this specific configuration.

This commit fixes a potential resource leak or incorrect shutdown behavior within `workerd`'s socket and system stream handling. It ensures `AsyncIoStream` is properly terminated when a `Socket` is closed, improving the stability and correctness of I/O operations.

This commit **enhances the R2 API Workers documentation** by integrating **Python examples** for various operations. Specifically, it adds a Python example for `PUT` object requests to the `workers-api-reference.mdx` file and includes Python examples for general R2 object operations and request authorization within the `workers-api-usage.mdx` guide. This **documentation improvement** makes it easier for developers using Python to understand and implement interactions with the R2 API via Workers.

This commit **enhances the Queues documentation** by adding **Python code examples** across several configuration topics. It provides practical examples for **batching, retries, and delayed messages** within the `batching-retries.mdx` file, and demonstrates **sending and consuming messages** in the context of JavaScript APIs in `javascript-apis.mdx`. Furthermore, it includes examples for **pull consumers**, covering message pulling, acknowledgment, and retries in `pull-consumers.mdx`. This **documentation improvement** significantly aids **Python developers** in understanding and implementing various queue patterns.

This commit **enhances the Durable Objects documentation** by integrating **Python code examples** into the `best-practices/websockets.mdx` guide. It specifically adds new examples demonstrating **WebSocket hibernation** and **server-side WebSocket implementations**, providing language-specific guidance for these patterns. This **documentation enhancement** improves the clarity and utility of the existing best practices, making it easier for developers to implement robust WebSocket applications with Durable Objects using Python.

This commit **enhances the documentation** for the **Cloudflare Durable Objects API** by integrating comprehensive **Python examples** across various API sections. It provides practical code snippets for features such as setting and handling `alarms`, basic `DurableObject` implementation, comparing `DurableObjectId` instances, interacting with `namespace` stubs, and utilizing both the `legacy-kv-storage-api` and `sqlite-storage-api`. This **documentation enhancement** significantly improves the **developer experience** for Python users, offering clear guidance and practical demonstrations for implementing Durable Objects functionality.