Upgraded from Brass Beta 0.22.1 (latest) to Clay Beta 0.23.0. Upgrade went smoothly. I notices that my most recent transaction was dated 02/10/2019. Went to the transaction list and noticed that the list stopped at 02/10/2019 even though I had transactions in 0.22.1 up to 04/05/2020 (probably many hundreds). I can only assume that many of these 'missing' transactions were still in the 'waiting' stage and were not 'completed yet'. The log (list) resumed with the next job at 10:08:52 on 04/05/2020.
Golem Version: 0.23.0
Golem-Messages version (leave empty if unsure):
Electron version:
OS [e.g. Windows 10 Pro]: Windows 10 Home
Branch (if launched from source):
Mainnet/Testnet: Mainnet
Priority label is set to the lowest by default. To setup higher priority please change the labelP0 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:
A clear and concise description of what went wrong, in which component, when and where.
Actual result:
What is the observed behavior and/or result in this issue
Screenshots:
If applicable, add screenshots to help explain your problem.
Steps To Reproduce
Short description of steps to reproduce the behavior:
e.g.
Launch the app with '...'
Click on '....'
Scroll down to '....'
See error
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)
Description
Upgraded from Brass Beta 0.22.1 (latest) to Clay Beta 0.23.0. Upgrade went smoothly. I notices that my most recent transaction was dated 02/10/2019. Went to the transaction list and noticed that the list stopped at 02/10/2019 even though I had transactions in 0.22.1 up to 04/05/2020 (probably many hundreds). I can only assume that many of these 'missing' transactions were still in the 'waiting' stage and were not 'completed yet'. The log (list) resumed with the next job at 10:08:52 on 04/05/2020.
Golem Version: 0.23.0
Golem-Messages version (leave empty if unsure):
Electron version:
OS [e.g. Windows 10 Pro]: Windows 10 Home
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:
A clear and concise description of what went wrong, in which component, when and where.
Actual result:
What is the observed behavior and/or result in this issue
Screenshots:
If applicable, add screenshots to help explain your problem.
Steps To Reproduce
Short description of steps to reproduce the behavior: e.g.
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)