| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
After recent changes, '--foo bar' was working, but '--foo=bar' was not. The
test had a typo (?) (bar != baz) and because util.argparse is not strict by
default, the typo was not caught.
The typo caused the code to take a different path, and bypassed the buggy
handling of --foo=bar options.
I've preserved the existing test (typo and all!) because it's still an
interesting test, and ensures no unintended behaviour changes compared to the
old code.
However I've added a new variant of the test, with strict mode enabled and the
typo fixed. This test failed due to the bug, and this commit introduces a fix.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Inspired by something MattJ said
Allows retrieving config values from files which are expected to be
relative to the config directory, extending on the ENV_ method of
retrieving config values from outside the config file.
- FileLine retrieves the first line, stripping any trailing newline
- FileContents reads the whole file
- FileLines reads lines into an array
|
| |
|
|
|
|
|
|
| |
More correct handling of namespaces here.
This works with both prefixes from the parser and hacky .attr["foo:bar"]
|
| |
|
|
|
|
|
|
| |
Allows granting read only access to other sets of users using a separate
access control capability, which makes sense as some properties may be
intended to be public but read-only.
|
|
|
|
|
| |
Seems exposing publisher is not enabled in mod_pep, but then it'll be
the user themselves most of the time
|
|
|
|
| |
This corresponds to the file mod_bookmarks2/tests/bookmarks2.scs
|
|
|
|
|
|
|
| |
pkey_meth_derive: to derive a shared symmetric key from two ECC keys
pkey_meth_public_raw: to get the raw form of the public key
import_public_ec_raw: to import the raw form of the public key
generate_p256_keypair: key generation for the P-256 curve
|
| |
|
|
|
|
| |
Continuation of 4b39691a274e
|
| |
|
|\ |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
This returns the number of bits that two strings have in common. It is
significantly more efficient than similar calculations in Lua.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
It was mainly used to determine whether to try IPv6 or IPv4 first,
following the rules for this in the RFC.
Now we always try IPv6 and IPv4 at roughly the same time, thus there no
need to carry these rules.
|
| | |
|
| |
| |
| |
| |
| | |
Ref #667
Ref #1838
|
|\| |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Having to add these in *there* places seems less than ideal.
I would also think that advertising disco#info is a bit redundant, since
it is a requirement for everything in XMPP and if it was missing you
would get an error back.
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
> Mockery is one of the things I hold dear! And he's making a mockery of it!!
-- Belkar Bitterleaf
|
| |
| |
| |
| |
| |
| |
| |
| | |
It iterates over childtags, so a template like {foo|each{...}} would be
equivalent to root:childtags("foo"), while a deeper query needs the bit
that becomes arguments to :childtags as an argument to each, e.g.
{foo/bar|each(baz)} would behave like
root:get_child("foo"):get_child("bar"):childtags("baz")
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
Strict typing does not magically make code correct
|
| | |
|
|\| |
|
| |
| |
| |
| | |
This case would eventually be rejected by the buffer size limit.
|
| |
| |
| |
| | |
Backport of ffe4adbd2af9 since new was added in the 0.12 branch
|
| |
| |
| |
| |
| | |
The new method parse_duration_lax() exports the old behaviour, mainly for
compatibility purposes.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Allows sorting by id as a substitute for sorting by timestamp since it
has the timestamp in the encoded in the first part, and only things that
happen extremely close together may get out of order by such a sort,
which might not matter.
From draft-ietf-uuidrev-rfc4122bis formerly draft-peabody-dispatch-new-uuid-format
|
| | |
|
| |
| |
| |
| |
| | |
Fixes that LuaDBI being unavailable makes these produce nothing but
endless stack overflows in luarocks.
|
| |
| |
| |
| |
| | |
Part of an attempt to make these tests work again. Previously they would
just explode in a million luarocks stack overflows
|
| | |
|
| |
| |
| |
| | |
This way the relevant arguments are shown in case a test case fails
|
| |
| |
| |
| |
| |
| | |
This is probably not guaranteed to work and might vary with Lua version,
but it's good enough for me to get accurate line numbers out of Busted
that don't all point to the test() function.
|
| |
| |
| |
| |
| |
| |
| | |
Simplifies access to the cache without moving code around a lot given
the currently common pattern of
local some_cache = cache.new(size, function(k,v) end)
|
| |
| |
| |
| |
| | |
Previously either the old or the new values would be rejected, even if
the cache was resized to allow more items.
|
| |
| |
| |
| | |
These are gathered into arrays
|