You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
node: propagate git failures from store::ls_tree and tree APIs (#400 class) #604
store::ls_tree in crates/gitlawb-node/src/git/store.rs still maps any non-zero git ls-tree exit to Ok(vec![]). GET /api/v1/repos/:owner/:repo/tree and .../tree/*path in repos.rs call it with .unwrap_or_default(), so corrupt or unreadable object stores can return 200 with "entries": []—the same silent-empty class #400 addressed for store::log, changelog, and list_commits.
Motivation
#438 scoped the three issue #400 sites plus store::log classification; tree listing was unchanged on merge-base and head. Worth a dedicated follow-up so API clients do not treat a read failure as an empty directory.
Mirror the #438 pattern: distinguish genuinely empty trees from read failures in ls_tree (or propagate Err like log), and remove handler folds. Add endpoint or store tests analogous to changelog_on_corrupt_object_store_*.
Notes
Not blocking #438; opened from merge-gate review drift tracking.
Activity