daemon/session: fix an issue with timers

See merge request !1195

The practical problem was also mitigated by libuv >= 1.32.0 (2ee2d46)

utils/cache_gc nit: use dynarray from libknot 3.1

See merge request !1194

It's compatible, so the only real effect is avoiding compiler:
warning: "DYNARRAY_VISIBILITY_PUBLIC" redefined

support Knot DNS master (3.1)

See merge request !1192

The go stuff probably never worked on buster and we just forgot to test.

This part is fully compatible with 3.0, fortunately.
It was insufficient inclusion on our side anyway, working by accident.

meson.build: add a simple sanity check of kres-gen result

See merge request !1190

Now those type definitions can be simply loaded without any error, e.g.
luajit daemon/lua/kres-gen.lua
That will be useful for checking them without regenerating them.

ci: packaging test for RockyLinux 8

See merge request !1187

add nix: apkg + CI

See merge request !1189

Vladimír Čunát authored 3 years ago and Tomas Krizek committed 3 years ago

For now just a simple docker-based build, atop nixos-unstable
(for now my nixpkgs branch that also adds apkg itself).

Vladimír Čunát authored 3 years ago and Tomas Krizek committed 3 years ago

- Support is in apkg master now.
- The generated default.nix is exactly as in the distro:
  https://github.com/NixOS/nixpkgs/blob/master/pkgs/servers/dns/knot-resolver/default.nix
  (except for new version+hash, and one test needed a tweak since 5.3.2)

ci: test on armhf and arm64

See merge request !1186

Some tests (typically those using network) ocassionally fail due to
timeouts, which is probably due to increased CI load - perhaps reducing
it could make the tests more stable.

The test attempts to use the timestamp 2050-12-31T23:59:59, which can't
be represented with 32bit time_t due to Year 2038 problem.

Make sure we use the correct lemgth modifiers to support both 32b and
64b architectures.

ci: make the pkgbuild jobs re-use the archive (job)

See merge request !1188

The child pipelines behave a bit differently than expected,
in this respect.

policy.FLAGS: fix not applying properly in edge cases

See merge request !1179

Vladimír Čunát authored 3 years ago and Štěpán Balážik committed 3 years ago

The requests get traced even without verbose logging.
I expect it was a copy&paste mistake from QTRACE docs.