Skip to content
Snippets Groups Projects
  1. Nov 15, 2018
  2. Nov 13, 2018
  3. Nov 15, 2018
  4. Nov 14, 2018
    • Augie Fackler's avatar
      tests: allow for 100% of profiled time in sleep in test-profile.t · 4790732559ad
      Augie Fackler authored
      I'm getting an annoying failure in this test on our builder, and I
      *think* what's happening is that the profiler is taking _just_ long
      enough to start that we're spending 100% of the profiled time in the
      sleep function, which was causing the leading space to not be printed
      since the 100 was in the first column of output.
      
      Differential Revision: https://phab.mercurial-scm.org/D5272
      4790732559ad
    • Augie Fackler's avatar
      tests: fix bytes/str issue I introduced when adding this test · ab59cc71f80c
      Augie Fackler authored
      # skip-blame just b prefixes for py3
      
      Differential Revision: https://phab.mercurial-scm.org/D5271
      ab59cc71f80c
    • Matt Harbison's avatar
      tests: document a known failing interaction between narrow and lfs · 7c5a922be068
      Matt Harbison authored
      This is one of the two remaining aborts I found looking into issue5794.  I've
      got no idea what's wrong with the hook, since the changes there fixed the other
      two problems noted in that bug report.  It seems like it might go away when the
      narrow issue is fixed, but let's make sure this doesn't get lost.
      
      The stacktrace for the hook seems to indicate that the missing file *is* in ctx:
      
        remote: Traceback (most recent call last):
        remote:   File "c:\Users\Matt\projects\hg\hgext\lfs\__init__.py", line 253, in checkrequireslfs
        remote:     if any(f in ctx and match(f) and ctx[f].islfs() for f in ctx.files()):
        remote:   File "c:\Users\Matt\projects\hg\hgext\lfs\__init__.py", line 253, in <genexpr>
        remote:     if any(f in ctx and match(f) and ctx[f].islfs() for f in ctx.files()):
        remote:   File "c:\Users\Matt\projects\hg\hgext\lfs\wrapper.py", line 191, in filectxislfs
        remote:     return _islfs(self.filelog(), self.filenode())
        remote:   File "c:\Users\Matt\projects\hg\mercurial\context.py", line 631, in filenode
        remote:     return self._filenode
        remote:   File "c:\Users\Matt\projects\hg\mercurial\util.py", line 1528, in __get__
        remote:     result = self.func(obj)
        remote:   File "c:\Users\Matt\projects\hg\mercurial\context.py", line 579, in _filenode
        remote:     return self._filelog.lookup(self._fileid)
        remote:   File "c:\Users\Matt\projects\hg\mercurial\filelog.py", line 68, in lookup
        remote:     self._revlog.indexfile)
        remote:   File "c:\Users\Matt\projects\hg\mercurial\utils\storageutil.py", line 218, in fileidlookup
        remote:     raise error.LookupError(fileid, identifier, _('no match found'))
        remote: LookupError: data/inside2/f.i@f59b4e021835: no match found
      7c5a922be068
  5. Nov 11, 2018
    • Yuya Nishihara's avatar
      logtoprocess: drop support for ui.log() call with invalid msg arguments (BC) · d2c997b8001f
      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.
      d2c997b8001f
    • Yuya Nishihara's avatar
      175b590b1f51
  6. Nov 13, 2018
  7. Nov 14, 2018
  8. Oct 13, 2018
  9. Nov 13, 2018
  10. Nov 12, 2018
  11. Nov 04, 2018
  12. Nov 08, 2018
  13. Jan 18, 2015
    • Yuya Nishihara's avatar
      ui: extract helpers to write message with type or label · 83dd8c63a0c6
      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.
      83dd8c63a0c6
    • Yuya Nishihara's avatar
      commandserver: add experimental option to use separate message channel · 054d0fcba2c4
      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.
      054d0fcba2c4
  14. Nov 10, 2018
  15. Nov 07, 2018
  16. Nov 10, 2018
  17. Nov 09, 2018
  18. Nov 08, 2018
  19. Nov 07, 2018
  20. Nov 06, 2018
  21. Nov 07, 2018
Loading