It should have been not abbreviated this whole time.
Pff OK if that's the argument you want to go with, I don't think we need to continue.
This grill is not a hoooooome.
Not exactly. I'm talking specifically about being able to call axum::serve with non-Send futures.
I'm not sure what tokio (or axum) can do to avoid the trait bounds. Would it makes sense to provide a "share nothing" runtime implementation that can be injected at startup? I wonder how the intermediate layers (e.g. axum) would indicate that futures are usable by a more generic runtime which may or may not need Send + 'static.
Without some way to write generic code for either runtime, the whole tokio ecosystem would end up bifurcated by this choice of runtime.
Rate-limiting could also be applied at the federation level, but I'm less sure of what the implementation would look like. Requiring filters on a per-account basis might be resource intensive.
- The Descent
- The VVitch
- The Shining
- The Texas Chainsaw Massacre (1974)
- Audition
Layton is baby puzzles. Or at least it made me feel that way after two levels.
What sentence are you referring to?
Yea that works too.
Oh interesting I wasn't aware of the push behavior. That's cool, but perhaps over-eager at times?
tatterdemalion
0 post score0 comment score
I believe both
SERIALIZABLEandREPEATABLE READisolation levels would raise an error for this example.And I looked this up: Postgres won't retry the transaction for you either. Though ultimately I think this a good default behavior.