You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 31, 2023. It is now read-only.
Golem-Messages version (leave empty if unsure): golem_messages Version: 3.13.0
Electron version (if used): 0.2.3
OS [e.g. Windows 10 Pro]: Linux
Branch (if launched from source): develop
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:
In blender task reserved GNT amount is several times higher than the correct value.
Actual result:
Reserved GNT amount for subtasks is several times higher than it should be payed, as a result value shown in wallet is on minus. Too big numbers shown in requestor's transactions history in awaiting state, on provider's side transaction history looks correct.
2019-10-18 14:41:18 INFO golem.task.taskmanager Creating task. type=<class 'apps.blender.task.blenderrendertask.BlenderRenderTask'>, id=94a63580-f1a4-11e9-9df6-2f67ff27ad1e
2019-10-18 14:41:18 INFO golem.ethereum.fundslocker Locking funds for task: '94a63580-f1a4-11e9-9df6-2f67ff27ad1e' price: 0.017 GNTB num: 4
2019-10-18 14:41:18 INFO golem.ethereum.transactionsystem Locking 0.067 GNTB and 0.00089840 ETH for 4 payments
019-10-18 14:43:30 INFO golem.verifier.blender_verifier Verification completed. Subtask_id: a245f802-f1a4-11e9-8345-2f67ff27ad1e. Verification verdict: positive.
2019-10-18 14:43:30 INFO apps.core.verification_queue Finished verification of subtask 'a245f802-f1a4-11e9-8345-2f67ff27ad1e'
2019-10-18 14:43:30 INFO golem.ethereum.paymentprocessor Adding payment for a245f802-f1a4-11e9-8345-2f67ff27ad1e to 0xe1D92383296F093515643ff8Fc5Cd128Fc038559 (60.00000000 GNTB)
2019-10-18 14:43:30 INFO golem.ethereum.paymentprocessor Reserved 60.000 GNTB
2019-10-18 14:43:30 INFO golem.ethereum.fundslocker Removing subtask lock for task '94a63580-f1a4-11e9-9df6-2f67ff27ad1e'
2019-10-18 14:43:30 INFO golem.ethereum.transactionsystem Unlocking 0.017 GNTB for 1 payments
Screenshots:
requestor's side:
provider's side:
Steps To Reproduce
Short description of steps to reproduce the behavior:
e.g.
Launch Golem on two nodes, provider and requestor
Start a short task, Small shark, resolution and samples from file, 2 frames, 4 subtasks, bid 0.1, task time 10 min for a task, 5 min for a subtask
Wait for task to finish
Check wallet and history of payments.
Chek amounts for subtasks in golem.log
Expected behavior
(What is the expected behavior and/or result in this scenario)
Description
Golem Version: 0.21.0+dev122.g9a56168
Golem-Messages version (leave empty if unsure): golem_messages Version: 3.13.0
Electron version (if used): 0.2.3
OS [e.g. Windows 10 Pro]: Linux
Branch (if launched from source): develop
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:
In blender task reserved GNT amount is several times higher than the correct value.
Actual result:
Reserved GNT amount for subtasks is several times higher than it should be payed, as a result value shown in wallet is on minus. Too big numbers shown in requestor's transactions history in awaiting state, on provider's side transaction history looks correct.
Screenshots:
requestor's side:

provider's side:

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
golem.log
task dump:
Proposed Solution?
(Optional: What could be a solution for that issue)
The text was updated successfully, but these errors were encountered: