Skip to content
Snippets Groups Projects
  1. Nov 11, 2018
    • Yuya Nishihara's avatar
      logtoprocess: drop support for ui.log() call with invalid msg arguments (BC) · d2c997b8
      Yuya Nishihara authored
      Before, the logtoprocess extension put a formatted message into $MSG1, and
      its arguments to $MSG2... If the specified arguments couldn't be formatted
      because of a caller bug, an unformatted message was passed in to $MSG1
      instead of exploding. This behavior doesn't make sense.
      
      Since I'm planning to formalize the ui.log() interface such that we'll no
      longer have to extend the ui class, I want to remove any features not
      conforming to the ui.log() API. So this patch removes the support for
      ill-formed arguments, and $MSG{n} (where n > 1) parameters which seems
      useless as long as the message can be formatted. The $MSG1 variable isn't
      renamed for the maximum compatibility.
      
      In future patches, a formatted msg will be passed to a processlogger object,
      instead of overriding the ui.log() function.
      
      .. bc::
      
         The logtoprocess extension no longer supports invalid ``ui.log()``
         arguments. A log message is always formatted and passed in to the
         ``$MSG1`` environment variable.
      d2c997b8
    • Yuya Nishihara's avatar
  2. Nov 13, 2018
  3. Oct 13, 2018
  4. Nov 13, 2018
  5. Nov 12, 2018
  6. Nov 04, 2018
  7. Nov 08, 2018
  8. Jan 18, 2015
    • Yuya Nishihara's avatar
      ui: extract helpers to write message with type or label · 83dd8c63
      Yuya Nishihara authored
      This provides a 'type' attribute to command-server clients, which seems
      more solid than relying on 'ui.<type>' labels. In future patches,
      type='progress' will be added to send raw progress information.
      83dd8c63
    • Yuya Nishihara's avatar
      commandserver: add experimental option to use separate message channel · 054d0fcb
      Yuya Nishihara authored
      This is loosely based on the idea of the TortoiseHg's pipeui extension,
      which attaches ui.label to message text so the command-server client can
      capture prompt text, for example.
      
      https://bitbucket.org/tortoisehg/thg/src/4.7.2/tortoisehg/util/pipeui.py
      
      I was thinking that this functionality could be generalized to templating,
      but changed mind as doing template stuff would be unnecessarily complex.
      It's merely a status message, a simple serialization option should suffice.
      
      Since this slightly changes the command-server protocol, it's gated by a
      config knob. If the config is enabled, and if it's supported by the server,
      "message-encoding: <name>" is advertised so the client can stop parsing
      'o'/'e' channel data and read encoded messages from the 'm' channel. As we
      might add new message encodings in future releases, client can specify a list
      of encoding names in preferred order.
      
      This patch includes 'cbor' encoding as example. Perhaps, 'json' should be
      supported as well.
      054d0fcb
  9. Nov 10, 2018
  10. Nov 07, 2018
  11. Nov 10, 2018
  12. Nov 09, 2018
  13. Nov 08, 2018
  14. Nov 07, 2018
  15. Nov 06, 2018
  16. Nov 07, 2018
  17. Oct 03, 2018
    • Boris Feld's avatar
      perf: introduce a perfrevlogwrite command · 164b2e77
      Boris Feld authored
      The command record times taken by adding many revisions to a revlog. Timing
      each addition, individually. The "added revision" are recreations of the
      original ones.
      
      To time each addition individually, we have to handle the timing and the
      reporting ourselves.
      
      This command is introduced to track the impact of sparse-revlog format on
      delta computations at initial storage time. It starts with the full text, a
      situation similar to the "commit". Additions from an existing delta are better
      timed with bundles.
      
      The complaints from `check-perf-code.py` are not relevant. We are accessing
      and "revlog" opener, not a repository opener.
      164b2e77
  18. Nov 06, 2018
  19. Nov 03, 2018
  20. Nov 05, 2018
  21. Nov 06, 2018
  22. Oct 31, 2018
    • Danny Hooper's avatar
      fix: add a config to abort when a fixer tool fails · 93bab809
      Danny Hooper authored
      This allows users to stop and address tool failures before proceeding, instead
      of the default behavior of continuing to apply any tools that didn't fail. For
      example, a code formatting tool could fail if you have syntax errors, and you
      might want your repo to stay in its current state while you fix the syntax
      error before re-running 'hg fix'. It's conceivable that this would even be
      necessary for the correctness of some fixer tools across a chain of revisions.
      
      Differential Revision: https://phab.mercurial-scm.org/D5200
      93bab809
  23. Oct 24, 2018
Loading