Skip to content

chore(nix): update flake.lock#1

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
update_flake_lock_action
Open

chore(nix): update flake.lock#1
github-actions[bot] wants to merge 1 commit into
mainfrom
update_flake_lock_action

Conversation

@github-actions

@github-actions github-actions Bot commented Feb 15, 2026

Copy link
Copy Markdown

Automated changes by the update-flake-lock GitHub Action.

Flake lock file updates:

• Updated input 'nixpkgs':
    'github:NixOS/nixpkgs/a4bf066' (2026-04-25)
  → 'github:NixOS/nixpkgs/d6df351' (2026-06-15)

Running GitHub Actions on this PR

GitHub Actions will not run workflows on pull requests which are opened by a GitHub Action.

To run GitHub Actions workflows on this PR, close and re-open this pull request.

scbrown pushed a commit that referenced this pull request Feb 15, 2026
…townhall#1706)

* perf(doctor): fix O(n) full-table scans causing 130s doctor runs

Three performance fixes for bd doctor on large databases (23k+ issues):

1. CheckDuplicateIssues (66s → 10ms): Replace SearchIssues() that loaded
   ALL issues into memory with SQL GROUP BY aggregation. The old code
   transferred 23k full issue rows (50+ columns) over MySQL wire protocol
   just to count duplicates.

2. CheckStaleClosedIssues (57s → 4ms): Replace SearchIssues() that loaded
   ALL closed issues with SELECT COUNT(*) SQL query. Same root cause as #1.

3. ResolvePartialID (60s+ → <1s for missing IDs): The substring search
   fallback loaded ALL issues when exact match failed. Now passes the hash
   as a search query to leverage SQL-level id LIKE filtering instead of
   transferring the entire database to Go for in-memory matching.

Total bd doctor runtime: 130s → 6s (22x speedup).
Total gt doctor runtime: infinite hang → 15s.

Root cause: These checks used store.SearchIssues() which does SELECT id
then GetIssuesByIDs() (full row fetch). On Dolt server mode with 23k+
issues, transferring all rows over MySQL wire protocol is catastrophically
slow. SQL aggregation and filtering avoid the data transfer entirely.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* test(doctor): add 7 missing tests for performance PR

CheckStaleClosedIssues (6 tests):
- DisabledSmallCount: threshold=0, <10k closed → OK
- DisabledLargeCount: threshold=0, ≥10k closed → warning
- EnabledWithCleanable: threshold=30d, old issues → correct count
- EnabledNoneCleanable: threshold=30d, recent issues → OK
- PinnedExcluded: all pinned → 0 cleanable
- MixedPinnedAndStale: 5 stale + 3 pinned → reports 5

CheckDuplicateIssues (2 tests):
- MultipleDuplicateGroups: 2+ groups → correct groupCount/dupCount
- ZeroDuplicatesNullHandling: SUM() NULL → defaults to 0

ResolvePartialID (1 test):
- TitleFalsePositive: hash in title but different ID → rejected

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
@github-actions github-actions Bot force-pushed the update_flake_lock_action branch from c439a04 to 2ae656c Compare February 22, 2026 01:15
@github-actions github-actions Bot force-pushed the update_flake_lock_action branch 2 times, most recently from 2fcb3c0 to f302bc1 Compare March 8, 2026 01:14
@github-actions github-actions Bot force-pushed the update_flake_lock_action branch 2 times, most recently from 48437c9 to a5f5456 Compare March 22, 2026 01:18
@github-actions github-actions Bot force-pushed the update_flake_lock_action branch from a5f5456 to 558ae79 Compare March 29, 2026 01:25
@github-actions github-actions Bot force-pushed the update_flake_lock_action branch from 558ae79 to 2619c5b Compare April 5, 2026 01:26
@github-actions github-actions Bot force-pushed the update_flake_lock_action branch from 2619c5b to 80dfda3 Compare April 12, 2026 01:30
@github-actions github-actions Bot force-pushed the update_flake_lock_action branch from 80dfda3 to a64c4a1 Compare April 19, 2026 01:46
@github-actions github-actions Bot force-pushed the update_flake_lock_action branch from a64c4a1 to 28796ec Compare April 26, 2026 01:48
@github-actions github-actions Bot force-pushed the update_flake_lock_action branch from 28796ec to 5b6a55a Compare May 3, 2026 01:54
@github-actions github-actions Bot force-pushed the update_flake_lock_action branch from 5b6a55a to 2e6864f Compare May 10, 2026 01:57
@github-actions github-actions Bot force-pushed the update_flake_lock_action branch from 2e6864f to 0dff2c7 Compare May 17, 2026 02:05
@github-actions github-actions Bot force-pushed the update_flake_lock_action branch from 0dff2c7 to 32970c7 Compare May 24, 2026 02:13
@github-actions github-actions Bot force-pushed the update_flake_lock_action branch from 32970c7 to e2566c9 Compare May 31, 2026 02:32
@github-actions github-actions Bot force-pushed the update_flake_lock_action branch from e2566c9 to e8c1879 Compare June 7, 2026 02:36
@github-actions github-actions Bot force-pushed the update_flake_lock_action branch from e8c1879 to ef2ae08 Compare June 14, 2026 02:40
Flake lock file updates:

• Updated input 'nixpkgs':
    'github:NixOS/nixpkgs/a4bf066' (2026-04-25)
  → 'github:NixOS/nixpkgs/d6df351' (2026-06-15)
@github-actions github-actions Bot force-pushed the update_flake_lock_action branch from ef2ae08 to 63f365d Compare June 21, 2026 02:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants