Use futures and tokio to send activities
#620
Zusammengeführt
elegaanz
hat 4 Commits von async-federation
nach master
vor 5 Jahren zusammengeführt
Laden…
In neuem Issue referenzieren
Hier gibt es bis jetzt noch keinen Inhalt.
Branch „async-federation“ löschen
Das Löschen eines Branches ist permanent. Es KANN NICHT rückgängig gemacht werden. Fortfahren?
Fixes #252
Publishing an article and having it federated to the whole fediverse only takes a few seconds now (instead of minutes before, on big Plume instances connected to many other ones).
👀
is this comment still relevant?
if this fails, we panic with "new rt".??
i think we should talk about our logging strategy sometime 😅
Not really, but it is for the background jobs in general, for the moment we just spawn them in a separate thread and that's it. I will remove it and create a more general issue.
Hum… yes, I could probably change that. To be honest I copied this line from reqwest examples without really thinking about it 😅
Indeed, we should probably use
log
andenv_logger
or something like that. Should I create an issue?Codecov Report
👀
I think this print should be done in the map just under, otherwise output could get mixed quickly, making both logs useless
(what is that comma for?)
(no idea, I will remove it)
Actually, it is added by cargo-fmt, because this whole expression is the argument of a function.
okay...
Reviewer
7ea4acc289
gemergt.Schritt 1:
Wechsle auf einen neuen Branch in deinem lokalen Repository und teste die Änderungen.Schritt 2:
Führe die Änderungen zusammen und aktualisiere den Stand online auf Forgejo.