golemfactory / clay

Golem is creating a global market for computing power.
https://golem.network
GNU General Public License v3.0
2.91k stars 286 forks source link

CLI: Error: WampError(WampError { code: Canceled, message: "callee disconnected from in-flight request", extra: {} }) #5181

Open ederenn opened 4 years ago

ederenn commented 4 years ago

Description

Golem Version: 0.23.0

Golem-Messages version (leave empty if unsure):

Electron version (if used):0.2.5

OS [e.g. Windows 10 Pro]: Ubuntu 18.04

Branch (if launched from source):

Mainnet/Testnet: mainnet

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:

During computations of a task (20 frames, 40 subtasks) checking list of subtasks in cli appeared

Error: WampError(WampError { code: Canceled, message: "callee disconnected from in-flight request", extra: {} })

When checking some of the subtasks were timed out, task was still computing. Reproduced it several times when this task was being computed. Later on, after the task was finishing listing subtasks for this task worked normally. In next tasks it was also possible to check list of subtasks from cli.

Actual result:

It was not possible to check subtasks in a task

Steps To Reproduce

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

  1. Launch the app 0.23.0 version
  2. Start a task, DiscBoyBlender frames 40-59, subtasks 40, task timeout 3h, subtask timeout 20 min, res and samples from file, bid 0.1, concent off
  3. Wait for computations of a task
  4. Task should be still computing, several subtasks finished and several timed out
  5. Type in terminal `golemcli tasks subtasks list

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)