SQL Staging (obviously don't merge) - #106
Draft
psilabs-dev wants to merge 41 commits into
Draft
psilabs-dev wants to merge 41 commits into
psilabs-dev wants to merge 41 commits into
Conversation
psilabs-dev
added
downstream
psilabs-dev
force-pushed
the
custom-release/staging-sql
branch
from
March 20, 2026 00:42
5443506 to
e56aa17
Compare
psilabs-dev
marked this pull request as draft
March 20, 2026 00:46
psilabs-dev
force-pushed
the
custom-release/staging-sql
branch
6 times, most recently
from
March 22, 2026 05:07
3dd55c5 to
b9c648c
Compare
psilabs-dev
force-pushed
the
custom-release/staging-sql
branch
from
April 30, 2026 03:33
b9c648c to
91bdba4
Compare
psilabs-dev
force-pushed
the
custom-release/staging-sql
branch
3 times, most recently
from
August 23, 2026 01:25
dceca1b to
9730297
Compare
psilabs-dev
force-pushed
the
custom-release/staging-sql
branch
4 times, most recently
from
September 8, 2026 05:40
d33dea5 to
6abfc27
Compare
# Conflicts: # public/js/reader.js
toggle pin/category and delete category
otherwise a tag stats call would take 10s on 100k archives/tags
The cache and cache invalidation logic is incorrect and not well-planned.
The hash was returned from inside the eval block, which returns from the eval rather than the sub. Execution fell through to the trailing error check, whose false branch made the sub return a one-element list, so the edit page rendered every field blank and never redirected on an unknown id. Assign inside the eval and return after it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019Q557x7LbNK29b9v1CqGak
# Conflicts: # public/js/mod/index.js
Difegue#1670's context menu predates #120's multi-category API, so the delete handler still tested the deprecated singular selectedCategory. Under the multi-select model that is always "", and deleting the active category would no longer clear the filter. Integration glue between Difegue#1670 and #120: it lives in neither branch, so a staging rebuild cannot reproduce it by merging. Kept as an explicit commit so future rebuilds can cherry-pick it.
psilabs-dev
force-pushed
the
custom-release/staging-sql
branch
from
September 12, 2026 06:54
6abfc27 to
5542623
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Base Stack: #86
Apply same accepted PRs as #119.
Issues for debugging: