1. 24 Sep, 2019 1 commit
  2. 20 Sep, 2019 2 commits
  3. 14 Aug, 2019 1 commit
    • Vladimír Čunát's avatar
      lib/resolve answer_finalize: don't SERVFAIL bogus +cd · e80fb5e6
      Vladimír Čunát authored
      As kresd works now, typically we do not know whether these records are
      bogus, as with +cd we do not attempt validation.  Still, it's possible
      that we have those records in cache from an occasion without +cd, in
      which case we know they're bogus and this regression happened.
      
      The potential impact of this issue seems minimal.
      e80fb5e6
  4. 23 Jul, 2019 3 commits
  5. 20 Jul, 2019 1 commit
  6. 10 Jul, 2019 8 commits
  7. 03 Jul, 2019 5 commits
  8. 27 Jun, 2019 2 commits
  9. 25 Jun, 2019 5 commits
  10. 24 Jun, 2019 1 commit
  11. 13 Jun, 2019 6 commits
  12. 03 Jun, 2019 1 commit
  13. 30 May, 2019 1 commit
    • Vladimír Čunát's avatar
      lib/nsrep: refactor a piece of code · f13d3ef8
      Vladimír Čunát authored
      This is yet another logically equivalent change after 270d9964.
      Now it's written in a way that expresses the original intention more
      clearly and without copy&paste or long lines.
      
      It seems easiest to verify by inspecting the meaning of the code
      *separartely* for the two cases, based on condition:
      cur_addr_score < KR_NS_TIMEOUT
      f13d3ef8
  14. 18 Apr, 2019 2 commits
    • Vladimír Čunát's avatar
      simplify approach to bind() · 8cecbf0d
      Vladimír Čunát authored
      The complication is that we need to work with addresses and
      just file-descriptors passed from some parent process.
      The former approach lead to logical duplication of some steps;
      now we add a step converting addresses to file-descriptors.
      Thanks to that we always do bind() without touching libuv,
      so the problem with forking disappears :-)
      8cecbf0d
    • Vladimír Čunát's avatar
      lib/generic/lru: try to resolve alignof warnings · ee67a8a3
      Vladimír Čunát authored
      We run meson with -std=gnu11, but apparently some compiler still
      complained about it.  Unfortunately it wouldn't be easy to use
      standard C11 in this case.
      ee67a8a3
  15. 17 Apr, 2019 1 commit