oxy fetch says 'up to date' while the local bookmark is behind; show can't find a fetched change issue #56
closed: completed andymccall opened this · 0 comments
andymccall
From metalgear dogfooding (2026-10-02): after a fetch brought 31c9aa21 into origin/main, every later oxy fetch printed 'Fetched origin/main - 2 heads - up to date', and oxy show 31c9aa21 said 'no change matches'. Only bookmark list's -1 showed it.
fetch: compare each tracked bookmark with its remote one and say 'origin/main is N changes ahead of main; oxy pull to take it' instead of 'up to date'.
change lookup (id or hash prefix): fall back to the remote bookmarks' states, and say the change is only in origin/main.
check the older finding (pull saying 'Already up to date' while behind) still holds after issue #48.
From metalgear dogfooding (2026-10-02): after a fetch brought 31c9aa21 into origin/main, every later
oxy fetchprinted 'Fetched origin/main - 2 heads - up to date', andoxy show 31c9aa21said 'no change matches'. Onlybookmark list's -1 showed it.