Fork of duckdb-ui to see if I can add additional functionality that I want/need
active 2025-04-05 → 2026-06-18 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 440 days from 2025-04-05 to 2026-06-18. Pushes: 33 total, peak 8 in a day. Pull requests: 10 total, peak 2 in a day. Issues: 82 total, peak 6 in a day. Comments: 200 total, peak 10 in a day. Stars: 94 total, peak 3 in a day.
- Pushes
- Pull requests
- Issues
- Comments
- Stars
Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.
Top contributors
Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| jraymakers | 144 | 2 | 3 | 98 |
| Y-- | 43 | 31 | 4 | 7 |
| garyLiuxh | 10 | 0 | 0 | 8 |
| djouallah | 5 | 0 | 0 | 3 |
| tdunning | 4 | 0 | 0 | 4 |
| carlopi | 4 | 0 | 0 | 4 |
| shwivel | 4 | 0 | 0 | 3 |
| winston-riley-zocdoc | 3 | 0 | 0 | 1 |
| xchray | 3 | 0 | 0 | 1 |
| pbrady32 | 3 | 0 | 0 | 3 |
| loicalleyne | 3 | 0 | 0 | 2 |
| eibednejo | 3 | 0 | 0 | 1 |
| davikor | 3 | 0 | 0 | 3 |
| szarnyasg | 3 | 0 | 0 | 0 |
| wijnanjo | 2 | 0 | 0 | 1 |
| hrunting | 2 | 0 | 0 | 2 |
| s7726 | 2 | 0 | 0 | 2 |
| mldisibio | 2 | 0 | 0 | 1 |
| dhirschfeld | 2 | 0 | 0 | 1 |
| MiguelElGallo | 2 | 0 | 0 | 1 |
Recent activity
Latest issues, pull requests and releases
- Issue comment#201CurrieJL2026-05-09 04:08Could not fetch: '/' from 'https://ui.duckdb.org': Could not establish connection
- Issue comment#233jraymakers2026-04-09 00:37Add UI setting to bind to 0.0.0.0
- Issue comment#233kaashmonee2026-04-04 19:55Add UI setting to bind to 0.0.0.0
- Issue#230jraymakers2026-04-03 03:58Run multiple instances of the UI
- Issue#230jraymakers2026-04-03 03:58Run multiple instances of the UI
- Issue#230jraymakers2026-04-03 03:55Run multiple instances of the UI
- Issue comment#230jraymakers2026-04-03 03:53Run multiple instances of the UI
- Issue comment#212bartzwemmer2026-03-25 10:16Launch UI without TTY
- Issue comment#43CGenie2026-02-10 08:56Segfault when attempting to attach sqlite database while ui is running
- Issue#225jraymakers2026-02-07 00:00Allow filtering schemas
- Issue comment#221dhirschfeld2026-02-03 10:38Attached Postgres DB results in error "Catalog Error: SET schema: No catalog + schema named "staging.main" found."
- Issue#225dhirschfeld2026-02-03 02:41Allow filtering schemas
- Issue comment#223MiguelElGallo2026-01-27 19:08Cannot use UI in v1.4.4/osx_arm64 - Fails with error: An error occurred while trying to automatically install the required extension 'ui'
- Issue#223MiguelElGallo2026-01-27 19:07Cannot use UI in v1.4.4/osx_arm64 - Fails with error: An error occurred while trying to automatically install the required extension 'ui'
- Issue comment#221matthiasfeist2026-01-15 09:06Attached Postgres DB results in error "Catalog Error: SET schema: No catalog + schema named "staging.main" found."
- Issue comment#43ngdangtu-vn2026-01-14 20:16Segfault when attempting to attach sqlite database while ui is running
- Issue comment#43Y--2026-01-14 12:15Segfault when attempting to attach sqlite database while ui is running
- Issue comment#221jraymakers2026-01-13 23:44Attached Postgres DB results in error "Catalog Error: SET schema: No catalog + schema named "staging.main" found."
- Issue comment#221jraymakers2026-01-13 01:25Attached Postgres DB results in error "Catalog Error: SET schema: No catalog + schema named "staging.main" found."
- Issue#220jraymakers2026-01-13 01:15JOIN USING with SELECT * fails due to duplicate column names since DuckDB 1.4 UI
- Issue#220jraymakers2026-01-13 01:15JOIN USING with SELECT * fails due to duplicate column names since DuckDB 1.4 UI
- Issue comment#220jraymakers2026-01-13 01:15JOIN USING with SELECT * fails due to duplicate column names since DuckDB 1.4 UI
- Issue comment#43Y--2026-01-12 16:42Segfault when attempting to attach sqlite database while ui is running
- Issue comment#62gafo252026-01-06 12:02Is there any way to use duckdb ui in offline environment?
- Issue#220estndard2026-01-03 08:55JOIN USING with SELECT * fails due to duplicate column names since DuckDB 1.4 UI
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 94 stars here means stars gained during the window, not the repo's star count.