Łukasz Magiera 60d576241c fix: sched: Address GET_32G_MAX_CONCURRENT regression (#10850) ... * Fix 1.21 regression: GET_32G_MAX_CONCURRENT + mixed prepared/executing leads to stuck scheduler If you have 12 GET tasks and GET_32G_MAX_CONCURRENT=1, sealing jobs will only show assigned tasks for GET of the miner and is stuck. I believe this to be a regression of 1.21 unifying the counters, in the case of GETs where PrepType and TaskType both being seal/v0/fetch leading to a state where tasks are blocked since already counted towards the limit. * itests: Repro issue from PR #10633 * make counters int (non-working) * fix: worker sched: Send taskDone notifs after tasks are done * itests: Make TestPledgeMaxConcurrentGet actually reproduce the issue * make the linter happy --------- Co-authored-by: Steffen Butzer <steffen.butzer@outlook.com>		2023-05-10 15:45:50 -04:00
..
config.yml	fix: sched: Address GET_32G_MAX_CONCURRENT regression (#10850)	2023-05-10 15:45:50 -04:00
gen.go	Remove AppImage and Snapcraft build automation	2023-01-20 15:11:16 -05:00
template.yml	ci: run release on ci/ branches, include m1	2023-05-10 15:21:34 -04:00