| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| | |
So that the same things happen as when triggered by an outgoing stanza
|
| |
| |
| |
| | |
Not exactly the way it was before, but close enough and useful.
|
| |
| |
| |
| |
| |
| | |
Since it changes the state to "flushing" while doing just that.
Attempting to remove the filters from a session that does not have them
should be a safe noop.
|
| | |
|
| |
| |
| |
| |
| | |
Definitely should not be firing an event that triggers like csi-flushing
from which it may make sense to send things, which leads right back here
|
| |
| |
| |
| |
| |
| | |
E.g. mod_smacks could queue an <r>, which would be more likely to be
included in the same write and TCP segment as the previously buffered
data, reducing syscalls and network packets needing to be sent.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
.affiliation
It appears nothing currently uses this field in prosody or prosody-modules
|
| | |
|
| |
| |
| |
| | |
...and fixing the logic bug that broke everything in the previous commit.
|
| |
| |
| |
| | |
data
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This was originally not done based on my interpretation of XEP-0045. Today's
reading, however, revealed that it actually says the result
> SHOULD contain **at least** a <username/> element
(emphasis mine)
I take this to mean that including a form **is** allowed (and I think this is
sensible). Tigase already includes the form I believe.
I've gated the new behaviour behind a (default off) option, because it hasn't
been tested for compatibility with clients. My primary desire for it is in
Snikket, where the clients will be tested to ensure compatibility with this.
I don't anticipate that (m)any clients would break, so maybe after 0.12 we can
experiment with enabling it by default and eventually remove the option.
|
| |
| |
| |
| |
| |
| | |
arcseconds)
I surmise this can happen in a disconnected/smacks hibernation state.
|
| |
| |
| |
| |
| |
| |
| | |
In this case `ret` is a table not containing the node, which makes
pubsub_error_reply() try to get an error template with that `ret` table
as index, which returns a `nil` then passed to table.unpack, which in
turn throws the error.
|
| |
| |
| |
| |
| | |
E.g. "connection refused" over one IP version instead of NoError for the
other IP version.
|
| |
| |
| |
| | |
I miss my custom ANSI-colored greeting!
|
| |
| |
| |
| |
| |
| |
| |
| | |
Previously it would only say "unable to resolve server" for all DNS
problems. While "NoError in A lookup" might not make much sense to
users, it should help in debugging more than the previous generic error.
Friendlier errors will be future work.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The existing events do not fire for unauthed sessions, for example (because
the type does not match). I deemed changing their behaviour too risky, and
the current behaviour may even be more desirable for some uses.
This means we now have roughly paired events:
- s2s-created -> s2s-destroyed (global only)
- s2sin-established -> s2sin-destroyed (global + host)
- s2sout-established -> s2sout-destroyed (global + host)
|
| |
| |
| |
| |
| | |
The overlapping logic for deletion and password changed has been merged into
a single function.
|
| | |
|
| | |
|
| |
| |
| |
| | |
Down the rabbit hole we go...
|
| |
| |
| |
| |
| |
| |
| | |
This should fix basic problems with multi-byte UTF-8 sequences getting
cut in the middle.
Down the rabbit hole we go...
|
| |
| |
| |
| | |
Could be useful elsewhere
|
| | |
|
| |
| |
| |
| |
| | |
Seems more like conventional Lua than passing an empty string to signal
lack of value.
|
| |
| |
| |
| |
| | |
Makes it so that returning e.g. util.cache :table() produces useful
output, which otherwise would look like empty tables.
|
| | |
|
| |
| |
| |
| | |
Avoids ellipsis
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
as column
Similar to the earlier view
|
| |
| |
| |
| |
| |
| | |
Nicer and more readable.
Thanks jonas’ and prosody@ for JID length stats to inform column widths.
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
Previously this would return item-not-found, even when you could see the
node in disco#items.
|
| |
| |
| |
| | |
Otherwise very large fields would be serialized in e notation
|
| |
| |
| |
| |
| |
| |
| | |
Assumes that most number fields are integers, as most numeric types
listed in XEP-0122 are, as are all such fields in Prosody as of this.
Otherwise %g produces something like 1.1259e+15
|
| |
| |
| |
| |
| | |
So they're separate from the datetime tests, and any future validation
tests
|
| |
| |
| |
| | |
Makes it symmetric with parsing.
|
| |
| |
| |
| |
| | |
Makes more sense than coercing to a string, which would always be
truthy.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
Internal use of XEP-0122 to shift the responsibility for converting
numbers to strings.
|
| | |
|
| |
| |
| |
| |
| | |
prosodyctl -h showing an error was not very helpful, especially since
prosodyctl shows its help for any unknown (or none) command.
|
| |
| |
| |
| |
| | |
Seems more suitable than asking if prosodyctl was meant to be used, or
going ahead and starting.
|