Read about our upcoming Code of Conduct on this issue

This instance was upgraded to Heptapod 0.28.0 today

  1. 06 Jun, 2020 4 commits
  2. 31 May, 2020 1 commit
  3. 29 May, 2020 1 commit
  4. 24 May, 2020 2 commits
  5. 22 May, 2020 1 commit
  6. 24 May, 2020 5 commits
  7. 23 May, 2020 1 commit
  8. 21 May, 2020 1 commit
  9. 19 May, 2020 3 commits
  10. 16 May, 2020 7 commits
  11. 14 May, 2020 1 commit
    • Anton Shestakov's avatar
      obslog: make obslog --no-origin -f work with multiple successor sets · 6ea05c9744de
      Anton Shestakov authored
      When trying to sort multiple successor sets, this block of code used to fail
      with:
      
      - TypeError: '<' not supported between instances of 'dict' and 'dict' (on py3)
      - TypeError: cannot compare sets using cmp() (on py2)
      
      So for sorted() to work properly, we need to remove dicts and sets from the
      data.
      
      --HG--
      branch : stable
      6ea05c9744de
  12. 09 May, 2020 2 commits
  13. 08 May, 2020 3 commits
  14. 03 May, 2020 1 commit
  15. 29 Apr, 2020 1 commit
  16. 06 May, 2020 2 commits
  17. 21 Apr, 2020 1 commit
  18. 23 Apr, 2020 1 commit
  19. 08 May, 2020 1 commit
  20. 07 May, 2020 1 commit
    • Martin von Zweigbergk's avatar
      evolve: mark new hash-salting extras keys as uninteresting for effect flag · 142827ad86f3
      Martin von Zweigbergk authored
      The user doesn't care if the
      `evolve_source_local`/`evolve_source_other` values in the extras
      changed, so this patch adds them to the blacklist that already exists
      for that purpose.
      
      This should also fix the flakiness we've seen in some tests. The
      flakiness seemed to stem from `mercurial.obsutil.geteffectflag()` not
      sorting extras keys. That means we ran into it relatively often for
      the `evolve_source_local`/`evolve_source_other` keys because there
      were two of them. That sorting bug should be fixed upstream.
      142827ad86f3