Hector Sanjuan 21855c3130 Fix bad context propagation / deadlocks ... We are propagating the wrong context (mostly from the Cluster top-level methods). This makes that request cancellations (and cancellations of the associated contexts) are not propagated to many methods, and can result in deadlocks when an operation that is holding a lock is not aborted. This affects for example the operation tracker. Getting all operations from the tracker relies on someone reading from the out channel, or on the context being cancelled. When a request is aborted in the middle of the response, and the context is not cancelled, everything that wants to list operations would become deadlocked, including operations that need write locks like TrackNewOperation. This fixes it.		2022-09-26 19:35:55 +02:00
..
optracker	Fix bad context propagation / deadlocks	2022-09-26 19:35:55 +02:00
stateless	api: return errors on stream response requests with 0 items	2022-09-15 16:40:34 +02:00
pintracker_test.go	Dependency upgrades (#1755)	2022-09-06 16:57:17 +02:00