prosody
cf367ab36fcc
spec/scansion/version.scs

Find changesets by keywords by author, files, the commit message, revision number or hash, or revset expression.

Software / code / prosody

File

spec/scansion/version.scs @ 13491:cf367ab36fcc

util.prosodyctl: Use notify socket to wait for Prosody to be ready Previously, prosodyctl only waits for the pidfile to appear, which does not necessarily mean that Prosody is fully ready to receive traffic. By waiting until Prosody says it's ready via the systemd notify socket we know for sure that Prosody is really ready. Notably this should ensure that when running `make integration-test` Prosody is really ready when Scansion starts running tests. Not sure if this timeout handling is optimal.
author Kim Alvefur <zash@zash.se>
date Sun, 19 May 2024 13:06:55 +0200
parent 10729:dbce2b94a7eb
line wrap: on
line source

# XEP-0092: Software Version / mod_version

[Client] Romeo
	password: password
	jid: romeo@localhost/dfaZpuxV

-----

Romeo connects

Romeo sends:
	<iq id='lx2' to='localhost' type='get'>
		<query xmlns='jabber:iq:version'/>
	</iq>

# Version string would vary so we can't do an exact match atm
# Inclusion of <os/> is disabled in the config, it should be absent
Romeo receives:
	<iq id='lx2' from='localhost' type='result'>
		<query xmlns='jabber:iq:version' scansion:strict='true'>
			<name>Prosody</name>
			<version scansion:strict='false'/>
		</query>
	</iq>


Romeo disconnects