Commit 10917b062adf "commands.push: use paths API" changed the way paths work and now pushing to a bad path succeeds. ~/myrepo> hg-3.5 push doesntexist pushing to doesntexist abort: repository doesntexist not found! ~/myrepo> hg-latest push doesntexist pushing to ssh://myserver.com//data/myrepo searching for changes ...
Sure sounds like a regression to me -> urgent
Bug marked urgent for 10 days, bumping
I'll send a patch up shortly.
Fixed by https://selenic.com/repo/hg/rev/663fbc336e22 Gregory Szorc <gregory.szorc@gmail.com> ui: change default path fallback mechanism (issue4796) The previous paths API code always fell back to the default path. This was wrong because if a requested path doesn't exist, that should error. Only if no path was requested should we fall back to the default. As part of implementing the test case for issue 4796, it was discovered that the "repository does not exist" error message raised by localrepository.__init__ wasn't being seen because the paths API validates paths before localrepository.__init__ was being called. The exception and error message from localrepository.__init__ has been introduced to getpath(). This necessitated rewriting expandpath() both to catch the exception and to have proper default fallback. This code is more complicated than I'd like. But making all tests pass was a big chore. As more code moves to getpath(), there will likely be opportunities to improve things a bit. (please test the fix)
Bug was set to TESTING for 39 days, resolving