abort: HTTP Error 400: Bad Request When There is Nothing to Pull
Jensen, Aaron
ajensen at webmd.net
Thu Jun 9 19:42:35 UTC 2016
Mercurial 3.7.3, Windows 7 x64
Yesterday I started getting an "abort: HTTP Error 400 Bad Request" when I run `hg pull` and there isn't anything to pull. Another of my co-workers, running 2.5.4, told me he saw it today. Pulling in changes works [1]. Verbose/debug output doesn't reveal anything to me [2].
Is this a known issue? How can I go about figuring out what is going on?
[1]
> hg pull
pulling from https://********/********
searching for changes
adding changesets
adding manifests
adding file changes
added 1 changesets with 2 changes to 2 files (-1 heads)
(run 'hg update' to get a working copy)
> hg pull
pulling from https://********/********
searching for changes
no changes found
abort: HTTP Error 400: Bad Request
[2] Verbose/debug output:
> hg pull --verbose --debug
pulling from https://********/********
using https://********/********
sending capabilities command
using auth.wbmd.* for authentication
******** certificate successfully verified
query 1; heads
sending batch command
using auth.wbmd.* for authentication
searching for changes
all remote heads known locally
no changes found
sending getbundle command
using auth.wbmd.* for authentication
abort: HTTP Error 400: Bad Request
More information about the Mercurial
mailing list