Daily GitHub activity summaries — commits, PRs, and issues.https://rusty.today/https://rusty.today/activity/https://rusty.today/activity/Rusty had a busy day maintaining and updating the DuckDB ecosystem, with particular focus on the community extensions and addressing build issues in the core DuckDB library. ## Community Extensions Maintenance The bulk of activity centered on `duckdb/community-extensions`, where Rusty performed a systematic update sweep across 20+ extensions. This included version bumps for **inflector**, **json_schema**, **minijinja**, **rapidfuzz**, **radio**, **quickjs**, **marisa**, **lindel**, **textplot**, **tera**, **stochastic**, **shellfs**, **redis**, **fuzzycomplete**, **evalexpr_rhai**, **hashfuncs**, **tsid**, **httpclient**, **datasketches**, and **cronjob**. Each update was paired with a corresponding PR to capture the latest commits from upstream repositories. Additionally, he added a new **events** feature to the extensions platform and updated reference configurations. ## Core DuckDB Build System Fixes On `duckdb/duckdb`, Rusty identified and addressed a critical linker issue affecting ARM64 Linux builds during community extension compilation. The `plan_serializer` tool introduced in v1.5.2 was causing multiple definition errors for `BufferedFileWriter::DEFAULT_OPEN_FLAGS`. He opened PR #22099 to guard the `plan_serializer` build behind the `BUILD_SHELL` flag, matching existing patterns in the CMake configuration, and also opened PR #22100 with the same fix. Additionally, he filed issue #22097 documenting the problem for visibility. He also contributed two significant feature proposals: PR #22082 introduces **tensor-lite** functionality, building multi-dimensional array syntax and Arrow FixedShapeTensor interop on top of existing nested ARRAY types, and PR #22079 adds **shell extension hooks** for registering custom dot-commands, enabling deeper integration of extensions like LLM agent demos. A separate issue (#22101) was opened regarding **aggregate function ergonomics**, highlighting the need for better access to AggregateInputData and batching support in initialize callbacks. ## HTTP Client Updates Over on `Query-farm/httpclient`, Rusty merged main branch changes and bumped submodules to keep dependencies current. He also replied to a community issue requesting a release compatible with DuckDB v1.5.2, providing timely support. ## Cross-Project Issues and Feedback Rusty opened two issues on `perspective-dev/perspective` related to UI behavior: numeric column formatting (issue #3159) and a field panel close button issue (issue #3158). On `duckdb/duckdb-httpfs`, he reported issue #310 regarding HTTP/2 stream errors lacking HTTP/1.1 fallback handling. He also contributed review feedback on the Apache Arrow repository regarding integration test data generation inconsistencies. Private repository activity across 4 repos with 6 commits remained ongoing throughout the day.Wed, 15 Apr 2026 00:00:00 GMTduckdb/community-extensionsQuery-farm/httpclientduckdb/duckdbperspective-dev/perspectiveduckdb/duckdb-httpfshttps://rusty.today/activity/https://rusty.today/activity/Rusty spent the day working on query optimization and join semantics in the DuckDB codebase. Over 23 commits, he refined critical logic in the join execution path. The main contribution was opening PR #22039 on `duckdb/duckdb`, which addresses a subtle bug in the hash join implementation. The fix guards the `chains_longer_than_one` flag assignment in `InsertMatchesAndIncrementMisses` with a check for `ht.insert_duplicate_keys`, ensuring the flag is only set when duplicate keys actually form chains. This distinction matters for **SEMI/ANTI/MARK joins**, where matched rows are dropped rather than chained, preventing incorrect state tracking in the hash table. Beyond the primary PR, Rusty engaged in community stewardship by replying to PR #22021 on `duckdb/duckdb`, which adds **COMMENT ON COLUMN** support for STRUCT type fields. This kind of targeted review feedback helps move forward infrastructure improvements in the DuckDB ecosystem. Additional work continues across three private repositories, reflecting ongoing development efforts outside the public codebase.Mon, 13 Apr 2026 00:00:00 GMTduckdb/duckdbhttps://rusty.today/activity/https://rusty.today/activity/Rusty focused on **join elimination optimization** in DuckDB, tackling a feature to improve query performance when joins can be safely removed based on primary key and uniqueness constraints. Over on `duckdb/duckdb`, he opened PR #22023 on the `join-elimination-pk-unique` branch, building on work from an earlier iteration (PR #22022, which was closed and reopened). The branch name suggests the optimization targets scenarios where a join can be eliminated when one side has a primary key or unique constraint that guarantees no row duplication. He also pushed commits to his fork at `rustyconover/duckdb` to iterate on the implementation. Beyond his own work, Rusty provided community support by commenting on issue #22021 regarding **COMMENT ON COLUMN support for STRUCT type fields**, offering feedback or guidance on that feature request. Additionally, he made a commit to a private repository, keeping some work off the public radar.Sun, 12 Apr 2026 00:00:00 GMTduckdb/duckdbrustyconover/duckdbhttps://rusty.today/activity/https://rusty.today/activity/Rusty focused on optimizing **DISTINCT ON** query handling in DuckDB, specifically targeting hash join deduplication filters. Work was spread across both his personal fork and the main DuckDB repository. On `rustyconover/duckdb`, he created and iterated on the `distinct-on-hash-join-chain-only-dedup-filter` branch with five pushes, refining the implementation through incremental commits. This branch explores a targeted approach to deduplication—limiting the filter to only apply within hash join chains rather than globally, which should improve performance on queries using DISTINCT ON with joins. The work culminated in opening **PR #22013** on the upstream `duckdb/duckdb` repository, bringing the optimization into the community review process. This represents active contribution to DuckDB's core query optimization engine, addressing a specific performance consideration in how distinct operations interact with join operations. Beyond the public work, Rusty also made 25 commits across two private repositories, suggesting parallel investigation or related feature development.Sat, 11 Apr 2026 00:00:00 GMTrustyconover/duckdbduckdb/duckdbhttps://rusty.today/activity/https://rusty.today/activity/Rusty had a productive day spanning multiple projects, with a focus on DuckDB enhancements and community contributions. Work on `vgi-rpc-python` included releasing two versions back-to-back: v0.6.11 and v0.6.12. Both releases involved updates to the `main` branch, suggesting bug fixes or feature refinements to the RPC library. Maintenance updates flowed through `inflector` on the `v1.4` and `v1.5` branches, keeping the library current across versions. Three issues were identified and opened on `apache/arrow-js`, all related to precision and type safety concerns: **Issue #421** flagged that `Timestamp.get()` throws for valid data outside `Number.MAX_SAFE_INTEGER` range, **Issue #422** revealed that `Date32.getDateDay()` silently loses precision for dates outside approximately 1685–2255, and **Issue #423** noted the absence of an extension type registry requiring manual FixedSizeBinary decoding by consumers. These findings suggest thorough testing of edge cases in the Arrow JavaScript implementation. DuckDB received significant attention across multiple branches. Rusty opened **PR #22009** on `duckdb/duckdb` for a left-join unique-right optimization (`feat-left-join-unique-right-v2` branch), and also submitted **PR #22001** addressing autocomplete qualified names issues. Development on the autocomplete fix also appeared on `rustyconover/duckdb` in **PR #3**. Additionally, he commented on **issue #21998**, providing support for a TIMESTAMP WITH TIME ZONE precision bug affecting extreme values near the int64 boundary. Perspective work included forking `perspective-dev/perspective` to `Query-farm/perspective` and creating a new branch `duckdb-type-support`, indicating work to enhance DuckDB type handling within the Perspective visualization library. Private repository activity included 29 commits across 2 repositories, suggesting ongoing work on internal projects.Fri, 10 Apr 2026 00:00:00 GMTQuery-farm/vgi-rpc-pythonQuery-farm/inflectorQuery-farm/perspectiveperspective-dev/perspectiveduckdb/duckdbrustyconover/duckdbapache/arrow-jshttps://rusty.today/activity/https://rusty.today/activity/Rusty was actively engaged across the DuckDB ecosystem today, balancing community support with new feature development. On the **DuckDB core** (`duckdb`), he opened two significant feature PRs aimed at extending type system capabilities. PR #21968 introduces **statistics hooks for extension types**, allowing custom types to define their own statistics behavior. Alongside this, PR #21966 adds **default compression type support for extension types**, enabling extensions to specify preferred compression strategies. Both branches (`feature/extension-type-statistics` and `feature/type-default-compression`) represent infrastructure improvements for the extension ecosystem. Beyond the feature work, Rusty provided targeted feedback on several open issues and PRs. He engaged with issue #21998 regarding **TIMESTAMP WITH TIME ZONE display precision near int64 boundaries**, commented on PR #21984 about optimizing MERGE INTO logical extraction, and weighed in on issue #21850 involving **Arrow union appender bounds checking**. He also replied to PR #21907 regarding a segfault when creating scalar macros with window-only functions. This steady stream of community engagement demonstrates ongoing stewardship of the DuckDB project. On the extension side, activity centered on updating `geosilo` within `duckdb/community-extensions`. He opened and then superseded PR #1708 with PR #1709 (both featuring automated bump branches), which successfully merged. Related work on `Query-farm/geosilo` included creating a `v1.5` branch on the main repository and pushing updates to `rustyconover/community-extensions`. These changes keep the geospatial extension in sync with the latest upstream commits. Private repository work totaled 9 commits across one repo, suggesting parallel development efforts not visible in the public activity log.Thu, 09 Apr 2026 00:00:00 GMTduckdb/duckdbduckdb/community-extensionsrustyconover/community-extensionsQuery-farm/geosilorustyconover/duckdbhttps://rusty.today/activity/https://rusty.today/activity/Rusty put in a solid day across multiple projects, with particularly active work on `geosilo` and ongoing contributions to the DuckDB ecosystem. **`geosilo` Development** The majority of activity centered on `geosilo`, with 15 commits pushed to the main branch throughout the day. This sustained effort suggests active feature development or refactoring work, though the specific changes would be visible in the commit details. **DuckDB Core Contributions** Two important bug fixes merged into `duckdb` today: PR #21852 addressing **Arrow query result bugs** and PR #21848 fixing **Arrow union type IDs offset** issues. Both were handled on focused feature branches (`fix/arrow-query-result-bugs` and `fix/arrow-union-type-ids-offset`), indicating careful isolation of the fixes. Beyond these merges, Rusty engaged in community support by commenting on issue #21905 regarding an **Interval 'ago' keyword overflow bug at INT32_MIN boundary**, and on issue #21908 about **window macro expansion silently dropping FILTER, DISTINCT, and ORDER BY attributes**—providing feedback and helping triage issues for the broader DuckDB community. **Community Extensions** Work continued on both `duckdb/community-extensions` and the personal fork `rustyconover/community-extensions`. PR #1707 merged into the main DuckDB community extensions repository, and corresponding commits were pushed to the personal fork, suggesting active maintenance or extension development. **Private Work** Additional commits were made across 2 private repositories (4 commits total), indicating parallel work on internal projects.Wed, 08 Apr 2026 00:00:00 GMTQuery-farm/geosiloduckdb/duckdbduckdb/community-extensionsrustyconover/community-extensionshttps://rusty.today/activity/https://rusty.today/activity/A productive day focused on DuckDB development and maintenance across multiple VGI RPC language bindings. **DuckDB Arrow Support & Bug Fixes** Rusty continued work on Arrow dense union support in `rustyconover/duckdb` on the `feature/arrow-dense-union-support` branch, advancing this feature toward integration with the main DuckDB project. He also engaged with the upstream `duckdb/duckdb` community on PR #21875, which merged a fix for HTTP extension gzip install checks. Additionally, Rusty commented on issue #21898, providing input on the dense union read/write support effort. **Bug Discovery & Reporting** A systematic code review session yielded eight new issues reported to `duckdb/duckdb`, uncovering bugs across multiple areas: - **Typos & Format String Bugs**: Issue #21910 documents a typo in CTAS error messages ("colum" vs "column"), and issue #21909 reports an internal error when using `COMPRESSION` with a format string bug using `%d` for string values - **Macro & Window Function Issues**: Issues #21908 and #21907 reveal that window macro expansion silently drops user-specified `FILTER`, `DISTINCT`, and `ORDER BY` attributes, and that creating scalar macros wrapping window-only functions (like `LAG`, `LEAD`, `ROW_NUMBER`) triggers segfaults - **Cast State & Interval Handling**: Issue #21906 identifies an uninitialized `to_varchar_local` variable in `InitEnumCastLocalState`, and issue #21905 documents silent overflow at `INT32_MIN` boundary when using the `'ago'` interval keyword - **MERGE INTO Failures**: Issues #21904 and #21903 show that `MERGE INTO` silently resolves cross-context column references to NULL instead of rejecting them, and fails with internal errors when the ON condition contains a subquery **VGI RPC Language Bindings** Rusty released `vgi-rpc-python` v0.6.10 and pushed updates across all three language binding repositories—`vgi-rpc-python`, `vgi-rpc-typescript`, and `vgi-rpc-go`—keeping the RPC client libraries in sync. Work also continued on private repositories with 18 commits across 4 codebases.Tue, 07 Apr 2026 00:00:00 GMTrustyconover/duckdbduckdb/duckdbQuery-farm/vgi-rpc-pythonQuery-farm/vgi-rpc-typescriptQuery-farm/vgi-rpc-gohttps://rusty.today/activity/https://rusty.today/activity/**DuckDB upstream contributions** dominated the day, with six merged PRs addressing a range of bugs and features. Rusty fixed geometry coordinate corruption in scientific notation (PR #21893), corrected a sequence error message typo (PR #21892), and resolved a case-insensitive default database check vulnerability (PR #21863). Additional merged work included shell C++ bugs (PR #21857), column tag exposure via `duckdb_columns()` (PR #21794), secret drop-if-exists storage handling (PR #21877), filter propagation correctness (PR #21859), and qualified alias method call binding (PR #21865). He also opened PR #21898 on `duckdb/duckdb` to implement **Arrow dense union support**, along with supporting work on `rustyconover/duckdb` branches `feature/arrow-dense-union-support` and `fix/arrow-union-type-ids-offset` to address union type_ids buffer handling that ignores chunk offsets. Community engagement included comments on multiple issues providing technical feedback and supporting ongoing discussions. Work on the **Arrow library** spanned multiple push events to the `query-farm-pyarrow-slim` branch. Rusty forked `apache/arrow` to `Query-farm/arrow` and established the specialized branch for query farm–specific PyArrow optimizations, with sustained iteration throughout the day on this customized implementation. **RPC library updates** across TypeScript, Go, and Python maintained steady progress. The `vgi-rpc-python` package reached **v0.6.9** with a formal release, and commits flowed through `main` branches on all three language implementations (`vgi-rpc-typescript`, `vgi-rpc-go`, `vgi-rpc-python`), indicating alignment of features across the polyglot RPC ecosystem. Private repository work included 2 commits across separate projects, keeping internal tooling in sync with the day's broader development efforts.Mon, 06 Apr 2026 00:00:00 GMTQuery-farm/arrowQuery-farm/vgi-rpc-typescriptQuery-farm/vgi-rpc-goQuery-farm/vgi-rpc-pythonduckdb/duckdbrustyconover/duckdbapache/arrowhttps://rusty.today/activity/https://rusty.today/activity/A remarkably productive day focused on bug fixes and open-source stewardship across the DuckDB ecosystem. In `duckdb`, Rusty opened 20 pull requests tackling diverse issues across the codebase. The fixes span mathematical functions (`fix/atanh-negative-one-sign`, `fix/acosh-domain-validation`, `fix/skewness-zero-variance-null`), date handling (`fix/datediff-overflow-extreme-dates`), profiling infrastructure (`fix/profiler-peak-buffer-memory-accumulation`, `fix/profiler-null-deref-html-graphviz`), list operations (`fix/list-where-oob-read`, `worktree-fix-list-repeat-overflow`), HTTP extensions (`fix/http-extension-install-gzip-check`), and autocomplete functionality (`fix/autocomplete-fuzzy-suggestion-limit`). He also investigated and reported issues including a **gzip decompression assumption in HTTP extension installs** (issue #21874) and **skewness() returning garbage for zero-variance input** (issue #21870). Additionally, six of his earlier PRs were merged: addressing arrow batch task shadowing, constraint preservation with table samples, profiler peak buffer accumulation, and autocomplete fuzzy suggestion limits. Work on `duckdb-inet` shows active engagement with the networking extension. Rusty forked the repository and opened three pull requests addressing critical bugs: **IPv6 buffer overflow** (PR #28), **IPv4 add off-by-one error** (PR #29), and **IPv4 broadcast upper bits handling** (PR #30). Multiple commits were pushed to support these fixes across the `fix/ipv6-buffer-overflow` and related branches. In his fork of `duckdb`, several feature branches remain active, including `worktree-fix-list-repeat-overflow` and `fix/skewness-zero-variance-null`, with multiple pushes suggesting iterative refinement and testing.Sun, 05 Apr 2026 00:00:00 GMTrustyconover/duckdbduckdb/duckdbduckdb/duckdb-inetrustyconover/duckdb-inethttps://rusty.today/activity/https://rusty.today/activity/Rusty focused on private repository work today, making 2 commits to an internal project. While the specifics of the private codebase remain undisclosed, the day's activity suggests focused iteration on an ongoing initiative.Sat, 04 Apr 2026 00:00:00 GMThttps://rusty.today/activity/https://rusty.today/activity/Rusty cut multiple releases on `vgi-rpc-python` today, shipping three versions in quick succession: v0.6.6, v0.6.7, and v0.6.8. The rapid release cadence suggests either bug fixes or refinements rolling out to address issues discovered in testing or production use. On the DuckDB front, work continued on the `feature/column-tags-in-duckdb-columns` branch in `rustyconover/duckdb`. This feature branch indicates ongoing development to add column tags support to DuckDB's column metadata, likely extending the query engine's ability to track and expose additional column-level information. Beyond the public repositories, Rusty maintained active development across four private projects with 11 commits, suggesting parallel work on either internal tools or unreleased features.Fri, 03 Apr 2026 00:00:00 GMTQuery-farm/vgi-rpc-pythonrustyconover/duckdbhttps://rusty.today/activity/https://rusty.today/activity/**DuckDB work** dominated the day. A fix for `DELETE ... RETURNING` with local storage merged into the main `duckdb` repository (PR #21541). More significantly, Rusty opened PR #21794 on `duckdb/duckdb` to expose **column tags via `duckdb_columns()`**, addressing a feature request for better column metadata discovery. The work involved multiple commits on the `feature/column-tags-in-duckdb-columns` branch in his fork (`rustyconover/duckdb`), and he also commented on the PR to discuss implementation details with the community. Three new issues were opened across DuckDB and Perspective. On `duckdb/duckdb`, Rusty filed issue #21777 requesting a way to discover whether a table has a **rowid pseudo-column** — useful metadata for tools that need to understand table structure. Over on `perspective-dev/perspective`, two issues were created: issue #3148 identifies a bug where `GenericSQLVirtualServerModel` double-aggregates when both `group_by` and `split_by` are used with `PIVOT`, and issue #3149 documents missing type coercion support in `VirtualServer.coerce_column` for common Arrow types from external databases. Beyond public contributions, private repository work continued across three codebases with 3 commits total.Thu, 02 Apr 2026 00:00:00 GMTduckdb/duckdbrustyconover/duckdbperspective-dev/perspectivehttps://rusty.today/activity/https://rusty.today/activity/**SEC Filing Data Consistency Work** Rusty opened two issues on `edgartools` addressing data consistency problems in SEC form parsing. Issue #749 flags an inconsistency in 13F-HR filings where the **Value column** uses different units depending on the filing date — thousands for pre-Q4 2022 submissions but dollars post-Q4 2022. He also created the corresponding fix branch `fix/13f-value-units-normalization` to address this normalization challenge. A second issue (#748) highlights that the `obj()` method returns `None` for Schedule 13D/13G form names ('SC 13D' and 'SC 13G'), prompting the creation of `fix/sc-13d-13g-form-aliases` to resolve form name aliasing problems. These issues were opened on the upstream `dgunning/edgartools` repository, and Rusty forked the project to his own account to work on fixes. **DuckDB Ecosystem Updates** Activity across the DuckDB VGI RPC libraries shows regular maintenance: commits landed on `vgi-rpc-typescript`, `vgi-rpc-go`, and `vgi-rpc-python`. The Python package saw a release of **v0.6.5** with corresponding changes to `main`. On `duckdb-httpfs`, Rusty opened PR #303 on the upstream DuckDB repository to fix handling of **non-200 HTTP responses**. The branch `fix-non-200-responses` addresses a gap in error handling for HTTP status codes beyond successful responses. He also merged a dependency bump in `duckdb/community-extensions` (PR #1666) to keep extensions synchronized with the latest DuckDB versions. **Private Infrastructure** Two commits were pushed across private repositories, suggesting ongoing internal work separate from public contributions.Wed, 01 Apr 2026 00:00:00 GMTrustyconover/edgartoolsdgunning/edgartoolsduckdb/community-extensionsQuery-farm/vgi-rpc-typescriptQuery-farm/vgi-rpc-goQuery-farm/vgi-rpc-pythonduckdb/duckdb-httpfsrustyconover/duckdb-httpfshttps://rusty.today/activity/https://rusty.today/activity/Rusty spent the day managing dependency updates and providing community support across the DuckDB ecosystem. Over in `community-extensions`, he opened two PRs to bump extension dependencies. PR #1667 targets an update to the airport extension, while PR #1666 addresses an a5 extension dependency bump. Both PRs involved creating feature branches with commit hash references to track the specific versions being updated. He also pushed changes to the `main` branch of his fork (`rustyconover/community-extensions`) to support the upstream work. On the community front, Rusty provided feedback on issue #6648 in `duckdb-web` regarding the DuckDB Table Visualizer, helping troubleshoot functionality issues. He also commented on issue #47 in `airport`, addressing a bug where `LookupSchema` was returning null for the DEFAULT_SCHEMA and blocking table function resolution — diving into schema resolution logic to unblock that work. In addition to public activity, he made 6 commits across 2 private repositories, likely related to parallel development efforts.Tue, 31 Mar 2026 00:00:00 GMTduckdb/community-extensionsrustyconover/community-extensionsduckdb/duckdb-webQuery-farm/airporthttps://rusty.today/activity/https://rusty.today/activity/A high-velocity day focused on **filter accessor improvements** for DuckDB and coordinated updates across the Query-farm extension ecosystem. ## DuckDB Core Development Rusty opened three related PRs to enhance filter accessibility in DuckDB's query optimization layer. PR #21695 adds **read-only accessors to BloomFilter and BFTableFilter**, establishing the foundation for safer filter introspection. Building on this, PR #21696 (`feature/perfect-hash-join-filter-accessors`) and PR #21697 (`feature/prefix-range-filter-accessors`) extend accessor support to additional filter types, enabling better integration with external systems and extensions. He also engaged in community discussion on issue #21695, providing feedback on the accessor interface design. ## DuckDB Community Extensions The `duckdb/community-extensions` repository saw significant activity with **five version bump PRs** addressing upstream changes in key extensions. PR #1641 bumps `adbc_scanner`, PR #1642 updates `bitfilters`, and PR #1643 refreshes `cronjob`. Three earlier bump PRs (PRs #1639, #1640, #1637) targeting `a5`, `airport`, and `bitfilters` were closed, likely superseded or merged. This coordinated update cycle reflects ongoing maintenance of the extension ecosystem. ## Query-Farm Extension Ecosystem Across the 30+ Query-farm extension repositories, Rusty pushed commits to `v1.5` branches in a sweeping wave of updates. Major extensions receiving updates include `bitfilters`, `stochastic`, `crypto`, `airport`, `tsid`, `tributary`, and many others spanning text processing, data structures, scripting, and utility tools. The consistent `v1.5` branch targeting suggests a coordinated release or feature branch rollout across the entire extension collection. ## Supporting Infrastructure Private repository work (15 commits across 7 repos) continues in parallel, suggesting ongoing internal tooling or integration work.Sun, 29 Mar 2026 00:00:00 GMTduckdb/community-extensionsrustyconover/community-extensionsduckdb/duckdbrustyconover/duckdbQuery-farm/bitfiltersQuery-farm/stochasticQuery-farm/cryptoQuery-farm/airportQuery-farm/tsidQuery-farm/tributaryQuery-farm/textplotQuery-farm/teraQuery-farm/shellfsQuery-farm/redisQuery-farm/rapidfuzzQuery-farm/radioQuery-farm/quickjsQuery-farm/minijinjaQuery-farm/marisaQuery-farm/lindelQuery-farm/jsonataQuery-farm/json_schemaQuery-farm/intervaltoolsQuery-farm/inflectorQuery-farm/httpclientQuery-farm/hashfuncsQuery-farm/fuzzycompleteQuery-farm/evalexpr_rhaiQuery-farm/discretureQuery-farm/datasketchesQuery-farm/cronjobQuery-farm/collectQuery-farm/blake3Query-farm/adbc_scannerQuery-farm/a5duckdb/duckdb-wasmhttps://rusty.today/activity/https://rusty.today/activity/No GitHub activity recorded today.Sat, 28 Mar 2026 00:00:00 GMThttps://rusty.today/activity/https://rusty.today/activity/Rusty spent the day focused on modernizing the WebAssembly build infrastructure and supporting community work across multiple DuckDB-related projects. Over in `duckdb-wasm`, he pushed commits to the `emsdk-5.0.4-upgrade` branch, advancing the effort to upgrade Emscripten to version 5.0.4. He also engaged with upstream DuckDB community work by commenting on issue #2198 regarding build configuration compatibility with Emscripten 3.x, providing input on the broader modernization strategy. On the `airport` project, Rusty reviewed and commented on issue #47, which addresses a critical bug where **LookupSchema returns null for DEFAULT_SCHEMA**, causing table function resolution to fail. This type of schema handling issue can have cascading effects on query execution, so the fix is important for stability. Additionally, he made a commit to a private repository, continuing work on a separate initiative. The day reflected focused effort on infrastructure modernization and community stewardship, with attention to both upstream compatibility concerns and downstream project reliability.Fri, 27 Mar 2026 00:00:00 GMTQuery-farm/duckdb-wasmduckdb/duckdb-wasmQuery-farm/airporthttps://rusty.today/activity/https://rusty.today/activity/A productive day spanning multiple repositories across the DuckDB ecosystem and supporting infrastructure projects. Work on `duckdb-wasm` dominated the day, with six pushes to the `emsdk-5.0.4-upgrade` branch as Rusty iterated through an upgrade to Emscripten SDK 5.0.4. This represents significant ongoing work to modernize the WebAssembly build toolchain. The **vgi-rpc** family of projects—TypeScript, Go, and Python implementations—all received v0.6.3 releases. Each language binding was updated and tagged on `main`, indicating a coordinated release across the polyglot RPC suite. On the DuckDB side, Rusty pushed work to `rustyconover/duckdb` on the `fix-delete-returning-local-storage` branch, addressing an issue with DELETE RETURNING statements for rows inserted within the same transaction. He also engaged with the upstream DuckDB project on PR #21541, reviewing and discussing the fix. Community support continued across several repos: - Replied to issue #18 on `tributary` regarding missing Linux AMD64 builds for version 1.5.1 - Addressed issue #5 on `hashfuncs` concerning hash functions returning 0 when input columns contain NULLs with an active selection vector - Engaged twice on issue #50 in `httpserver` regarding a release targeting DuckDB 1.5 Additional work included 28 commits across two private repositories, likely related to broader platform or integration efforts. All work reflects active development across data infrastructure, WebAssembly compilation, and RPC service layers with careful attention to compatibility and correctness.Thu, 26 Mar 2026 00:00:00 GMTQuery-farm/tributaryduckdb/duckdbQuery-farm/httpserverQuery-farm/hashfuncsrustyconover/duckdbQuery-farm/duckdb-wasmQuery-farm/vgi-rpc-typescriptQuery-farm/vgi-rpc-goQuery-farm/vgi-rpc-pythonhttps://rusty.today/activity/https://rusty.today/activity/**VGI RPC Libraries** — Rusty released v0.6.2 and v0.6.1 across the three VGI RPC language implementations (`vgi-rpc-typescript`, `vgi-rpc-go`, and `vgi-rpc-python`), with multiple commits on `main` pushing updates to each. **DuckDB Core & Infrastructure** — Several significant contributions to the DuckDB ecosystem. He commented on issue #21607 regarding FK reference resolution for external catalogs, which was subsequently merged. Additionally, a reply was provided on issue #21087 about ENUM extension metadata in Arrow export/import for lossless roundtrips, offering community feedback on a feature request. **WebAssembly & Emscripten Toolchain** — Work is underway to upgrade the Emscripten SDK to version 5.0.4. Rusty forked both `duckdb-wasm` and `extension-ci-tools` from the DuckDB organization and created corresponding `emsdk-5.0.4-upgrade` branches in his own `Query-farm` forks. Multiple pushes to the feature branch on `Query-farm/duckdb-wasm` indicate active development on this upgrade path. **DuckDB Feature Development** — Ongoing work spans multiple branches in `rustyconover/duckdb`: commits on `feature/suspended-query-contexts` and `fix-delete-returning-local-storage` show exploration of query context suspension and delete-returning functionality, while `fix-fk-external-catalog` aligns with the FK resolution work mentioned above. **Community Extensions Maintenance** — Extensive stewardship of the DuckDB community extensions. Fifteen dependency bump PRs were merged on `duckdb/community-extensions` (PR #1580–#1599, #1601–#1602), updating extensions including `airport`, `httpclient`, `adbc_scanner`, `bitfilters`, `cronjob`, `crypto`, `datasketches`, `evalexpr_rhai`, `fuzzycomplete`, `hashfuncs`, `inflector`, `json_schema`, `jsonata`, `lindel`, `marisa`, `minijinja`, `openprompt`, `quickjs`, `radio`, `redis`, and `shellfs`. These maintenance updates keep the community extension ecosystem current. **Exploratory Work** — An issue was opened on `duckdb/duckdb-web` (issue #6648) regarding the DuckDB Table Visualizer not working, indicating ongoing investigation into web-based tooling. Private repository activity shows 9 commits across 3 private repos, suggesting additional work not publicly disclosed.Wed, 25 Mar 2026 00:00:00 GMTQuery-farm/vgi-rpc-typescriptQuery-farm/vgi-rpc-goQuery-farm/vgi-rpc-pythonduckdb/duckdbQuery-farm/extension-ci-toolsduckdb/extension-ci-toolsQuery-farm/duckdb-wasmduckdb/duckdb-wasmduckdb/duckdb-webrustyconover/duckdbQuery-farm/airportduckdb/community-extensionsrustyconover/community-extensionshttps://rusty.today/activity/https://rusty.today/activity/Rusty pushed commits across two repositories today, continuing work on upcoming releases. Over in `airport`, he advanced the `v1.5` branch with targeted changes as the release cycle progresses. The work maintains the existing trajectory toward the next major version. Meanwhile, the `crypto` repository saw updates on the `v1.4` branch, keeping that codebase in sync with its own development schedule. Additionally, he contributed a commit to a private repository, indicating ongoing work outside the public-facing projects.Tue, 24 Mar 2026 00:00:00 GMTQuery-farm/airportQuery-farm/cryptohttps://rusty.today/activity/https://rusty.today/activity/Rusty opened two complementary PRs addressing a fundamental limitation in DuckDB: the inability to interleave streaming SELECT queries with DML operations (UPDATE, INSERT, DELETE) within the same transaction. On `duckdb-python`, PR #397 introduces a new `subcursor()` method that enables this pattern at the Python API level. The subcursor shares the parent connection and transaction context, allowing multiple independent streaming operations to coexist. Importantly, subcursors are restricted from managing transactions themselves — attempting to call `begin`, `commit`, or `rollback` on a subcursor will raise an error, ensuring transaction coherence. In parallel, the core `duckdb` repository received PR #21569, which implements **Suspended Query Contexts** at the engine level. This feature removes the hard constraint that previously destroyed in-progress streaming scans whenever any new statement executed on a connection. The PR description illustrates the motivation: a common pattern of streaming rows from a large table, processing them, and updating a separate tracking table — all within a single transaction. Together, these changes represent significant progress on query interleaving, a long-standing request in the DuckDB community. The paired PRs suggest careful coordination between the C++ query engine and Python bindings to deliver a cohesive feature.Mon, 23 Mar 2026 00:00:00 GMTduckdb/duckdb-pythonduckdb/duckdbhttps://rusty.today/activity/https://rusty.today/activity/Rusty spent the day coordinating a synchronized v0.6.0 release across the vgi-rpc ecosystem while addressing critical bugs upstream in DuckDB. Work on `vgi-rpc-go` included fixing **staticcheck warnings** by removing a deprecated `Record()` call and cleaning up an unused `medianDuration` variable. He also implemented a **GCS (Google Cloud Storage) backend** for external storage, expanding the supported storage options for the Go implementation. The `vgi-rpc-typescript` implementation received the most activity. Beyond the v0.6.0 version bump, Rusty added both **GCS and S3 storage backends** for external storage capabilities. He also fixed smoke and HTTP conformance tests that were failing due to URL path changes (removing the `/vgi` prefix to match the new default configuration). Website updates in `vgi-rpc-website` reflected the v0.6.0 release cycle—the feature matrix and language cards were refreshed, and test count references were removed from the Go language card description. Version bumps in `vgi-rpc-python` brought the implementation in line with the synchronized 0.6.0 release, along with a separate 0.1.28 patch and uv.lock updates for v0.1.27 dependencies. Upstream in the DuckDB community, Rusty identified and opened **PR #21541** to fix a critical bug where `DELETE RETURNING` silently returned empty results for rows inserted in the same explicit transaction. The root cause was that `table.Fetch()` only reads from committed row groups, missing rows in transaction-local storage. He also opened **issue #21540** to track the `DELETE RETURNING` behavior and **issue #21538** to propose `RETURNING` projection pushdown optimizations for external catalog write operators—both representing important performance and correctness improvements for DuckDB.Sun, 22 Mar 2026 00:00:00 GMTQuery-farm/vgi-rpc-goQuery-farm/vgi-rpc-websiteQuery-farm/vgi-rpc-typescriptQuery-farm/vgi-rpc-pythonduckdb/duckdbhttps://rusty.today/activity/https://rusty.today/activity/A productive day spanning multiple VGI RPC implementations and upstream contributions. Work centered on standardizing cross-language behavior, adding observability instrumentation, and enhancing external storage support. **VGI RPC Go** (`vgi-rpc-go`) saw significant expansion with 10 commits addressing core protocol features. The **__describe__ schema was upgraded from v2 to v3**, aligning with language-agnostic specifications. External storage support received major attention: SHA-256 checksums were added to pointer batches, compression and round-trip tests were implemented, and the feature was wired throughout the server dispatch pipeline and input resolution paths. Additionally, an **--otel-export flag** was added to the conformance worker for cross-implementation testing, and the default HTTP prefix was changed from `/vgi` to an empty string to match the Python client. **VGI RPC TypeScript** (`vgi-rpc-typescript`) tracked closely with 11 commits implementing parity features. The schema upgrade to v3 was completed, and **external storage support was fully integrated** with SHA-256 checksums across HTTP client resolution paths and all server dispatch routes. OpenTelemetry instrumentation was added via dispatch hooks, with support for the **VGI_OTEL_FILE environment variable** in the conformance worker. Several UI improvements rounded out the work: HTML landing page, describe page, and 404 page were implemented, and error propagation to dispatch hooks was fixed in the HTTP handler. **VGI RPC Python** (`vgi-rpc-python`) received 3 commits implementing SHA-256 checksum support for external storage pointer batches, with corresponding test coverage added to both unit tests and the HTTP conformance suite. Upstream contributions included opening PR #1558 on `community-extensions` to update the `hashfuncs` extension to its latest commits, and filing issue #21533 on `duckdb` requesting the addition of OPTIONS to the HTTPUtil RequestType enum. Rusty also responded to a community request on `httpclient` regarding v1.5.0 compilation support. A demo video was initialized in `lindel_video` to showcase the lindel extension. Private repository activity included 10 commits across 3 repositories.Sat, 21 Mar 2026 00:00:00 GMTQuery-farm/lindel_videoQuery-farm/vgi-rpc-goQuery-farm/vgi-rpc-typescriptQuery-farm/vgi-rpc-pythonduckdb/community-extensionsduckdb/duckdbhttps://rusty.today/activity/https://rusty.today/activity/Rusty wrapped up work on the **xxh3_128_hex()** feature, merging PR #4 on `hashfuncs` and updating documentation to reflect the new function that returns a canonical hex VARCHAR representation. He also bumped the version of `hashfuncs` in `community-extensions` to keep the extension catalog in sync. On the DuckDB side, Rusty engaged in community stewardship across two projects. He reviewed and provided feedback on PR #21502 in `duckdb` regarding profiler and progress bar interactions, and chimed in on PR #1554 in `community-extensions` to discuss updates needed for the http_client extension with v1.15.0 compatibility. Beyond the public repositories, Rusty made progress across 4 private projects with 6 commits, indicating parallel work on internal initiatives.Fri, 20 Mar 2026 00:00:00 GMTduckdb/community-extensionsQuery-farm/hashfuncshttps://rusty.today/activity/https://rusty.today/activity/A productive day of dependency management, feature additions, and community support across the Query-farm ecosystem and DuckDB extensions. **DuckDB Community Extensions** Rusty submitted three PRs to keep extensions in sync with their latest upstream work. PR #1557 and #1555 both update `httpclient` to incorporate recent commits, while PR #1556 brings `inflector` to its latest version. These version bumps ensure the community extension versions stay current with active development. **HTTP Client Library** In `httpclient`, Rusty fixed a test suite issue by replacing references to the deprecated httpbingo.org service with httpbin.org, ensuring tests remain reliable. He also updated submodules to pull in the latest dependencies. **RPC Libraries** Both `vgi-rpc-typescript` and `vgi-rpc-python` received significant updates. A key change across both libraries involved shifting the default HTTP prefix from "/vgi" to "" (root), simplifying the API surface. The TypeScript implementation gained support for client-side device code OAuth fields and signing algorithm configuration, along with an authentication example. In `vgi-rpc-python`, lint and format issues were resolved, with a new guideline added to CLAUDE.md emphasizing reformatting before pushing. The Python version was bumped to 0.1.27. **Inflector Extension** The `inflector` extension received two notable improvements. A Linux ARM64 build issue was resolved by adding a missing `expression_executor` include. More notably, he implemented a new `strip_accents` option for the `inflect()` function, enabling users to remove diacritical marks from text—addressing community interest in the feature as evidenced by a comment reply on issue #4. **Community Engagement** Rusty provided support across multiple repos: clarifying the release status for `httpserver` (issue #50), explaining the architectural differences between his `lindel` spatial indexing implementation and ST_Hilbert, and responding to the diacritics removal inquiry on `inflector` that directly motivated the new feature. **Private Work** Additional development activity across 6 private repositories totaled 17 commits.Thu, 19 Mar 2026 00:00:00 GMTduckdb/community-extensionsQuery-farm/httpclientQuery-farm/vgi-rpc-typescriptQuery-farm/inflectorQuery-farm/vgi-rpc-pythonhttps://rusty.today/activity/https://rusty.today/activity/Rusty spent the day working on the `vgi-rpc-website` repository, making 26 commits focused on refining the capabilities data handling. The key change involved **removing automated capability matrix overwriting** and **fixing the capabilities data structure**, which suggests he was resolving conflicts or inconsistencies in how capability information is stored and managed on the site. Beyond the public work, he also made 25 commits to a private repository, indicating parallel development efforts that warrant continued attention.Wed, 18 Mar 2026 00:00:00 GMTQuery-farm/vgi-rpc-websitehttps://rusty.today/activity/https://rusty.today/activity/A lighter day focused on private work. Rusty made a single commit to a private repository, keeping development momentum on internal projects without public activity on open-source repositories.Tue, 17 Mar 2026 00:00:00 GMThttps://rusty.today/activity/https://rusty.today/activity/Rusty spent the day working on private projects, making **4 commits across 2 private repositories**. While the specifics of this work remain private, the activity suggests focused development effort on internal tooling or experimental features.Mon, 16 Mar 2026 00:00:00 GMThttps://rusty.today/activity/https://rusty.today/activity/Rusty worked on deployment configuration handling in `superfly/flyctl` today, addressing how image configurations are substituted during the deploy process. The commit message indicates he resolved an issue where image config references using "." notation needed to be properly mapped to the actual build image, likely improving the consistency and reliability of deployments when using relative image path syntax. Beyond the primary work on `flyctl`, he also made progress across 2 private repositories with 3 commits, suggesting concurrent development on internal or proprietary tools.Sun, 15 Mar 2026 00:00:00 GMTsuperfly/flyctl