| Age | Commit message (Collapse) | Author |
|---|
|
this is a contribution from jk (sectore) that I rebased and squashed
into this commit.
the tests were broken in the last few commits to rush out some fixes.
this change may introduce more issues because of
Relay.respond_standard_req.
|
|
the tool had not been tested with large number of user relays, some of
which are misbehaving. It works well when sending events to relays but
struggles when fetching messages.
it seems to crash when accessing a large number of relays. this change
queues up relays so many are not connected to at the same time.
it also shows more verbose messages about its connection and success
with relays.
many of the tests will fail as a result of this change as I havn't
updated them to expect details of more relay interaction.
further changes are urgently needed to improve the speed of fetching
events.
- relay interaction UI should reflect the smooth approach used for
sending events
- we don't need to fetch user events from every relay
- we could show the user information that we have already collected
and allow them to interact
|
|
to prevent tests from poluting public relays
|
|
- fetch prs and present as a selectable list
- create and / or checkout branch for selected pr
- apply latest patches as commits
|
|
reuse client across login and send events
|
|
connect immediately before requesting or sending events
no longer waiting for all relays to connect before interacting with any of them
|
|
immediately request metadata and relay list from any newly discovered
user write relays
|
|
get user relay list and metadata events from relays when keys are
used and last fetch attempt was more than an hour ago
uses user's write relays if known, otherwise uses fallback relays
to achieve this a method for intergration testing event fetching
from relays was added
|
|
add tests but these currently don't work when run together
|
|
- add client
- use client to send event
- add async functionality - enabler for relay interaction whilst
getting cli input
|