Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
i dunno how the `and not exists` is going to work out over time,
probably need some kinda checkpointing so that i don't have to rule out
the entire build history for a host every time it asks for a new task
|
|
|
|
|
|
|
|
onward, `rustc --version`!!
|
|
|
|
|
|
BETWEEN x86 AND aarch64
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
task_info kind overwrites the containing clientproto kind
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
from invalid bounds
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
afaict holding the lock over an await point gives tokio an opportunity
to run a different task - perhaps a different API request that would try
acquring the db connection lock. then it deadlocks; the second task
holds the thread hostage while waiting for the first task to release its
lock, which it can't do due to no thread being available for it to run
on.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|