| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
Signed-off-by: Josh Soref <jsoref@users.noreply.github.com>
|
|
|
|
| |
It was a bit weird that the API had mempool creation but no deletion.
|
|
|
|
|
|
|
| |
murmurhash3.c:43:40: runtime error: addition of unsigned offset
to 0x7ffce41c2014 overflowed to 0x7ffce41c2000
The `i` was used in a super-ugly way; I suspect the only reason was
to optimize that end-loop condition was zero comparison *vomit*
|
|
|
|
|
| |
libknot >= 2.9 provides it and their version is less buggy :-)
In particular, it works with unaligned pointers.
|
|
|
|
|
| |
Experience proved that it can be confused with mm_alloc()
and it may not be trivial to find the mistake.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
It seems just easier than having the copies in the current way.
I don't think the `static inline` were helping us anyway,
except for avoiding KR_EXPORT in some cases.
Still, differences when copying:
- we use plain memset() in the implementation
(no motivation here to use the complex memzero() approach)
- we expose mm_malloc(), as we've been referring to it
- we KR_EXPORT some of the functions (for lua and modules)
|
|
|
|
|
|
| |
- advantage: `auto_free anyType *foo;` works (for anyType != char)
- disadvantage: `auto_free anyType bar;` is also accepted,
though I expect such problems will be relatively easy to debug.
|
| |
|
|
|
|
|
| |
Working server-side GET/POST HTTPS method - Proof-of-Concept
Working server-side GET/POST HTTP/2 method - WiP
|
|
|
|
|
|
|
|
|
| |
It's mainly about the fact that FD can be zero (though it's not common).
Our current usage is just in tests and seems fine.
I don't think that other negative FDs are possible, but I'm lazy to find
"proof" in POSIX and using other negative values than -1 doesn't make
sense to me anyway (might be an assert, I guess).
|
|
|
|
|
| |
s/gitlab\.labs\.nic/gitlab.nic/g
Redirects are in place, so it shouldn't be required now, but why not.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The SPDX file contains hand-written metadata about source URL, version,
authors, and license.
There are two missing pieces in HTTP module:
- bootswatch theme - I could not find what theme we ship, maybe it is
based on one of bootswatch themes but heavily modified
- selectize.js source does not match respective files in upstream but
contains minor changes
I will deal with these in later commits.
|
|
|
|
| |
https://www.kernel.org/doc/html/latest/process/license-rules.html#license-identifier-syntax
|
|
|
|
|
| |
These files did not have GNU GPL v3 boilderplate in them so
I've added machine readable tag with appropriate license.
|
|
|
|
|
| |
Long GNU GPLv3 boilderplate was automatically replaced
with machine readable tag.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Perhaps it served some purpose in 28b230823, but it seems incorrect.
|
|
|
|
|
|
|
| |
GnuTLS 3.3 contained these as public symbols. This doesn't seem
important, but why not use more collision-resistant names anyway?
Details/discussion: https://github.com/CZ-NIC/knot/pull/14
Basically noone should notice, so I didn't include any NEWS entry.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Unfortunately, CFLAGS are concatenated in the other order than we would
need for this, so let's choose this approach.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
There's still an unresolved "problem" with QRVERBOSE getting
empty variadic list sometimes, and I can't see a good way around that.
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This fix copies over an updated #if clause from libknot's
src/contrib/endian.h.
This should resolve:
https://gitlab.labs.nic.cz/knot/knot-resolver/issues/348
See also discussion about this same problem in libknot from a couple
years ago:
https://bugs.debian.org/840460
I note that contrib/wire.h in knot-resolver is out of sync with
src/contrib/wire.h (and src/contrib/endian.h) from libknot. I don't
know whether there's any upstream preference for keeping these in sync
in some more reliable way than manual comparisons. For now i'm just
providing a narrow fix for the specific problem.
|
| | |
|