Use futures and tokio to send activities #620
Nav izskatītāju
Iezīmes
Nav iezīmju
A: API
A: Backend
A: Federation
A: Front-End
A: I18N
A: Meta
A: Security
Build
C: Bug
C: Discussion
C: Enhancement
C: Feature
Compatibility
Dependency
Design
Documentation
Good first issue
Help welcome
Mobile
Rendering
S: Blocked
S: Duplicate
S: Incomplete
S: Instance specific
S: Invalid
S: Needs Voting/Discussion
S: Ready for review
Suggestion
S: Voted on Loomio
S: Wontfix
Nav atskaites punkta
Nav projektu
Nav atbildīgo
2 dalībnieki
Paziņojumi
Izpildes datums
Nav uzstādīts izpildes datums.
Atkarības
Nav atkarību.
Atsauce: Plume/Plume#620
Notiek ielāde…
Pievienot tabulu
Atsaukties jaunā pieteikumā
Nav sniegts apraksts.
Izdzēst zaru "async-federation"
Zara izdzēšana ir neatgriezeniska. Kaut arī izdzēstais zars neilgu laiku var turpināt pastāvēt, pirms tas patiešām tiek noņemts, to vairumā gadījumu NEVAR atsaukt. Turpināt?
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...