Skip to content
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

Closed
ederenn opened this issue Nov 20, 2019 · 2 comments
Assignees
Labels
0.22 release bug P2 Severity-Low/ Effort-easy

Comments

@ederenn
Copy link

ederenn commented Nov 20, 2019

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:

2019-11-20 14:13:21 INFO     golem.task.tasksession              Provider can't compute subtask: '859f5a14-0b97-11ea-a9ae-2f67ff27ad1e' Reason: <REASON.OfferCancelled: 'OfferCancelled'>
2019-11-20 14:13:21 CRITICAL twisted                             
Traceback (most recent call last):
  File "/home/ederenn/projects/golem-env/lib/python3.6/site-packages/twisted/internet/asyncioreactor.py", line 136, in _readOrWrite
    why = method()
  File "/home/ederenn/projects/golem-env/lib/python3.6/site-packages/twisted/internet/tcp.py", line 243, in doRead
    return self._dataReceived(data)
  File "/home/ederenn/projects/golem-env/lib/python3.6/site-packages/twisted/internet/tcp.py", line 249, in _dataReceived
    rval = self.protocol.dataReceived(data)
  File "/home/ederenn/projects/golem/golem/network/transport/tcpnetwork.py", line 326, in dataReceived
    self._interpret(data)
  File "/home/ederenn/projects/golem/golem/network/transport/tcpnetwork.py", line 352, in _interpret
    self.session.interpret(m)
  File "/home/ederenn/projects/golem/golem/task/tasksession.py", line 196, in interpret
    BasicSafeSession.interpret(self, msg)
  File "/home/ederenn/projects/golem/golem/network/transport/session.py", line 75, in interpret
    action(msg)
  File "/home/ederenn/projects/golem/golem/task/tasksession.py", line 725, in _react_to_cannot_compute_task
    timeout,
  File "/home/ederenn/projects/golem/golem/core/common.py", line 179, in func_wrapper
    return func(*args, **kwargs)
  File "/home/ederenn/projects/golem/golem/task/taskmanager.py", line 860, in task_computation_cancelled
    new_status=SubtaskStatus.cancelled,
  File "/home/ederenn/projects/golem/golem/core/common.py", line 179, in func_wrapper
    return func(*args, **kwargs)
  File "/home/ederenn/projects/golem/golem/task/taskmanager.py", line 983, in restart_subtask
    self.tasks[task_id].restart_subtask(subtask_id)
  File "/home/ederenn/projects/golem/apps/wasm/task.py", line 548, in restart_subtask
    vbr_subtask.restart_subtask(subtask_id)
  File "/home/ederenn/projects/golem/apps/wasm/task.py", line 149, in restart_subtask
    if subtask['status'] != SubtaskStatus.starting:
TypeError: 'SubtaskInstance' object is not subscriptable

Steps To Reproduce

Short description of steps to reproduce the behavior:
e.g.

  1. Launch Golem on two nodes
  2. Request simultaneously a dask on different requestor, best one Gwasm, one Blender
  3. Wait for computations to start, check if nodes are failing
  4. See error in 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)

@prekucki
Copy link
Member

bug is also on b0.22 and on mainet (b0.21).

@prekucki prekucki removed their assignment Nov 26, 2019
@shadeofblue shadeofblue added P2 Severity-Low/ Effort-easy and removed P3 Severity-Low/Effort-hard labels Dec 2, 2019
@kmazurek
Copy link
Contributor

kmazurek commented Dec 6, 2019

Closed by #4933

@kmazurek kmazurek closed this as completed Dec 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
0.22 release bug P2 Severity-Low/ Effort-easy
Projects
None yet
Development

No branches or pull requests

5 participants