Use futures and tokio to send activities #620
No reviewers
Labels
No labels
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
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Plume/Plume#620
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "async-federation"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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...