comparison tests/test-bundle2.t @ 21183:4345274adc4b stable

bundle2: gracefully handle UnknownPartError during unbundle

Same as for Abort error, we catch the error, encode it into a bundle2 reply
(expected by the client) and stream this reply. The client processing of the
error will raise the exception again.

21182:08c84fd99aac

  >     extradata = orig(pushop, bundler)
  >     reason = pushop.ui.config('failpush', 'reason', None)
  >     part = None
  >     if reason == 'abort':
  >         part = bundle2.bundlepart('test:abort')
  >     if part is not None:
  >         bundler.addpart(part)
  >     return extradata
  > 
  > @bundle2.parthandler("test:abort")

  abort: Abandon ship!
  (don't panic)
  [255]

21183:4345274adc4b

  >     extradata = orig(pushop, bundler)
  >     reason = pushop.ui.config('failpush', 'reason', None)
  >     part = None
  >     if reason == 'abort':
  >         part = bundle2.bundlepart('test:abort')
  >     if reason == 'unknown':
  >         part = bundle2.bundlepart('TEST:UNKNOWN')
  >     if part is not None:
  >         bundler.addpart(part)
  >     return extradata
  > 
  > @bundle2.parthandler("test:abort")

  abort: Abandon ship!
  (don't panic)
  [255]


Doing the actual push: unknown mandatory parts

  $ cat << EOF >> $HGRCPATH
  > [failpush]
  > reason = unknown
  > EOF

  $ hg -R main push other -r e7ec4e813ba6
  pushing to other
  searching for changes
  abort: missing support for 'test:unknown'
  [255]

  $ hg -R main push ssh://user@dummy/other -r e7ec4e813ba6
  pushing to ssh://user@dummy/other
  searching for changes
  abort: missing support for "'test:unknown'"
  [255]

  $ hg -R main push http://localhost:$HGPORT2/ -r e7ec4e813ba6
  pushing to http://localhost:$HGPORT2/
  searching for changes
  abort: missing support for "'test:unknown'"
  [255]