oxy pull said 'Already up to date' while the bookmark was one behind issue #29 closed: completed andymccall opened this · 1 comment
andymccall referenced by change b9c2d543933b on main ·
andymccall
Cause, from rstar-api's operation log: each 'Already up to date' pull ran while the subrepo was on its feature bookmark (x16-rgm-speed, then x16-ram-ay). The pull fetched, which updated origin/main, correctly found the current bookmark up to date, and never mentioned main. A bookmark switch to main followed about 0.3 s later, then the pull that took main. The sync was right and the message misled. pull now says which bookmark it pulled, and names every other bookmark the fetch left behind, with the command that takes them. A core test covers a remote main moving to changes already here, as a landing does.
closed by change 7d9dab131937 ·
From metalgear feedback issue #22, in the rstar-api subrepo: the first oxy pull origin answered 'Already up to date' while bookmark list showed main behind 1; a second pull then pulled it. The first pull seems to fetch without unioning the bookmark, or to report the state from before the fetch. Needs a reproduction and a test.