| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
| |
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.
|
|
|
|
|
| |
Better than duck typing, in case anyone ever passes a non-stanza table
with a 'name' field.
|
|
|
|
|
|
|
| |
`reason` was often a table, so the log said "table: 0xptr" or such.
mod_c2s, mod_bosh etc logs the stream error stanza object, so better do
the same. It would be nicer if this was an util.error object, but that
will have to be a future change.
|
|
|
|
|
|
| |
This field is empty for reasons when invoked by prosody-migrator, which
threw an error:
> bad argument #1 to 'open' (string expected, got nil)
|
| |
|
|
|
|
|
|
|
| |
If the request fails in the middle then the file~ could be left behind
because no code was invoked to delete it then. This gets rid of it when
the request is removed. It may still be left in case of an unclean
shutdown.
|
| |
|
|
|
|
| |
Context in #1006 and revisions 89c42aff8510 e1d274001855
|
|
|
|
|
|
|
|
| |
Makes it easier to find XEPs that have had new revisions since we last
looked at them and the corresponding code.
A review of changelogs between these versions point to mostly editorial
changes or otherwise without warrant for code changes.
|
|
|
|
|
| |
Makes it easier to find XEPs that have had new revisions since we last
looked at them and the corresponding code.
|
|
|
|
|
| |
Labels are supposed to be fixed sets of things, so defined hosts are
okay, but not unknown hosts.
|
|
|
|
|
|
|
| |
Should call timers less frequently when many sockets are waiting for
processing. May help under heavy load.
Requested by Ge0rG
|
|
|
|
|
|
| |
Can't find anything saying anything on whether this is needed or not.
kawaii reported that both Chrome and Firefox complained unless the
header was added to the list of allowed headers.
|
|
|
|
|
|
| |
Clients would generally be using the "max" symbol instead of discovering
this, but this also gets us validation and earlier rejection of out of
bounds values.
|