| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
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
|
| |
| |
| |
| |
| |
| |
| | |
Why was the test data not in chronological order?
Altho, maybe that was the point? Except for MAM, the data might *not* be
in chronological order!
|
| |
| |
| |
| |
| |
| |
| |
| | |
Standardized and structured replacement for the X-Forwarded-For,
X-Forwarded-Proto set of headers.
Notably, this allows per-hop protocol information, unlike
X-Forwarded-Proto which is always a single value for some reason.
|
| | |
|
| |
| |
| |
| | |
A test case was added in the middle, so all these need to be reordered.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
This doesn't fail because of additionalProperties, looks more like some
issue with recursive definitions and util.jsonpointer that I don't want
feel like investigating now.
|
| | |
|
| |
| |
| |
| | |
Checks that it doesn't fail on a stanza without <error> tag
|
| |
| |
| |
| |
| | |
Similar logic occurs throughout various modules in the codebase. We might even
want a module:get_option_duration()??
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
With monotonic() frozen, timers may fail to trigger. This caused problems
after the new util.startup changes that moved the server-started event to a
timer. The timer wouldn't trigger, the event didn't fire, and prosody would
fail to daemonize.
All the tests that depend on specific time behaviour are depending on wall
clock time, so only mocking util.time.now() and os.time() fixes those.
|
| | |
|
| |
| |
| |
| |
| | |
If this object key exists then this schema must validate against the
current object. Seems useful.
|
| |
| |
| |
| | |
If this field exists, then these fields must also exist.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
I plan to introduce logic to "reset" the server between individual tests,
which is currently triggered by the lack of any connections. This is the only
test that has a point where no clients are connected, and it's not necessary,
so I changed it to keep the connection open for the duration of the test.
|
| |
| |
| |
| | |
This is a newly added field, and we expect to see it in these places now.
|
| |
| |
| |
| |
| | |
publisher is no longer included by default in broadcasts, but configured via
pubsub#itemreply instead.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Previous behaviour:
- publisher was always included in PEP notifications
- publisher was never included in get_items requests
New behaviour:
- publisher is included in both notifications and retrieval if
itemreply == publisher
- publisher is not ever included if itemreply ~= publisher
|
| |
| |
| |
| |
| |
| |
| |
| | |
This combines the two most common store types, which modules often end up
opening with both interfaces separately anyway.
As well as combining them, I've taken the opportunity to improve some of the
method names to make them clearer.
|
| |
| |
| |
| | |
Absolute references, weird fractions, unevaluatedProperties???
|
| |
| |
| |
| | |
These seem to be using absolute URI references, Not Yet Implemented
|
| | |
|
| | |
|
|\| |
|
| | |
|
|\| |
|