This repository has been archived by the owner on Oct 31, 2023. It is now read-only.
SubtaskStatus.starting: TypeError: 'SubtaskInstance' object is not subscriptable; Provider can't compute subtask: REASON.OfferCancelled #4915
Labels
Description
Golem Version: 2019-11-19 15:51:01 INFO golemapp GOLEM Version: 0.21.0+dev460.g0c9ad08
Golem-Messages version (leave empty if unsure): 3.14.0
Electron version (if used): 0.21.0
OS [e.g. Windows 10 Pro]: All
Branch (if launched from source): b0.22-multicore-wasm
Mainnet/Testnet:
Priority label is set to the lowest by default. To setup higher priority please change the label
P0 label is set for Severity-Critical/Effort-easy
P1 label is set for Severity-Critical/Effort-hard
P2 label is set for Severity-Low/ Effort-easy
P3 label is set for Severity-Low/Effort-hard
Description of the issue:
When subtask offer is cancelled for provider, it gives critical in logs,
SubtaskStatus.starting: TypeError: 'SubtaskInstance' object is not subscriptable
Provider can't compute subtask: REASON.OfferCancelled
this stops tasks from finishing. Subtasks ends in failure, provider is blocked.Actual result:
What is the observed behavior and/or result in this issue
Screenshots:
Steps To Reproduce
Short description of steps to reproduce the behavior:
e.g.
golem.log
Expected behavior
(What is the expected behavior and/or result in this scenario)
Logs and any additional context
(Any additional information that could help to resolve the issue, which systems were checked to reproduce the issue)
Please upload your logs if possible
Proposed Solution?
(Optional: What could be a solution for that issue)
The text was updated successfully, but these errors were encountered: