F3 Task won't restart in case of an error #312
Comments
Kubuxu
changed the title
Kubuxu
added a commit
to Kubuxu/curio
that referenced
this issue
Nov 1, 2024
lotus-rc2 miss-registered error types, rc3 does it correctly Next release will additionally contain fix for early reneweal. filecoin-project/lotus#12667 filecoin-project#312 is still an issue Signed-off-by: Jakub Sztandera <[email protected]>
Kubuxu
added a commit
to Kubuxu/curio
that referenced
this issue
Nov 1, 2024
lotus-rc2 miss-registered error types, rc3 does it correctly Next release will additionally contain fix for early reneweal. filecoin-project/lotus#12667 filecoin-project#312 is still an issue Signed-off-by: Jakub Sztandera <[email protected]>
magik6k
pushed a commit
that referenced
this issue
Nov 2, 2024
lotus-rc2 miss-registered error types, rc3 does it correctly Next release will additionally contain fix for early reneweal. filecoin-project/lotus#12667 #312 is still an issue Signed-off-by: Jakub Sztandera <[email protected]>
|
IIUC this was fixed in #302 |
|
It wasn't |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If the F3 task exits with an error, it will not restart until manual intervention is performed by removing it from the
f3_taskstable.Verified by running Curio, killing the Lotus node until RPC errors out. Standing up the node again does not resume the task.
The text was updated successfully, but these errors were encountered: