nostr:nprofile1qqswuyd9ml6qcxd92h6pleptfrcqucvvjy39vg4wx7mv9wm8kakyujgpypmhxue69uhkx6r0wf6hxtndd94k2erfd3nk2u3wvdhk6w35xs6z7qgwwaehxw309ahx7uewd3hkctcpypmhxue69uhkummnw3ezuetfde6kuer6wasku7nfvuh8xurpvdjj7a0nq40 Question about relay-tester: is it possible to configure it to wait a bit longer between tests? A given test will send a CLOSE and before a CLOSED is read by relay-tester, the next test started. You can see in the relay-tester that the very next thing it receive from the relay is the CLOSED message. Looking at my relay logs, I can see the CLOSE is handled and the CLOSED is sent within milliseconds. 

Also, thank you for building such a handy tool.  

 That is a fair request.  You could edit main.rs and add after line 123 (at the end of the for loop) this line:

	thread::sleep(std::time::Duration::new(0, 100));

Then it will wait 100ms between tests.  But tests that do multiple messages in a row won't have waits between those.

You could instead try editing connection.rs and add this at the top of send_message() (to wait before every send).

Let me know if those help. 

 HANG ON, that's not 100 milliseconds, that is 100 nanoseconds. You might make it bigger, or do Duration::from_millis(100) to be more sure.