Issue Report
Cli with farm parameter throws a bunch of errors
Environment
W10
Powershell
subspace-cli-windows-x86_64-v3-v0.3.3-alpha.exe
Gemini3d
Cli with farm parameter throws a bunch of errors
W10
Powershell
subspace-cli-windows-x86_64-v3-v0.3.3-alpha.exe
Gemini3d
@ivan-subspace @ozgun getting some more weird Tokio errors on CLI, not sure if its a cli or core issue, just wanted to raise to your attention
This honestly does not made sense to me. Iβm yet to reproduce this.
For plotting, the plotting bar hasnβt even started, which is really weird.
Glad that synchronization works without any error.
@RubioDeBote
Are you still getting the same error when farming?
I have started to think that this error is not reprodicable.
Yep. Still there.
It is very easy (or difficult to reproduce). Just run the βfarmβ argument from powershell.
I have not done more
./subspace-cli-windows-x86_64-v3-v0.3.3-alpha.exe farm
Iβm going to try other versions different from v0.3.3.
Letβs see if I can get it to work.
PS. Same with all of these:
-a---- 24/04/2023 18:48 71397576 subspace-cli-windows-x86_64-v2-v0.3.1-alpha.exe
-a---- 24/04/2023 18:48 71687368 subspace-cli-windows-x86_64-v2-v0.3.2-alpha.exe
-a---- 24/04/2023 18:47 71689928 subspace-cli-windows-x86_64-v2-v0.3.3-alpha.exe
-a---- 24/04/2023 18:48 71549128 subspace-cli-windows-x86_64-v3-v0.3.1-alpha.exe
-a---- 24/04/2023 18:48 71866568 subspace-cli-windows-x86_64-v3-v0.3.2-alpha.exe
-a---- 20/04/2023 10:27 71868104 subspace-cli-windows-x86_64-v3-v0.3.3-alpha.exe
Can you try wiping everything and starting again?
can you enable RUST_BACKTRACE and run farm again post those logs? (ideally in text but anything is helpful) with backtrace enabled it should give us a clearer insight into what might be happening.
Sorry for the delay. I had erased everything and started over. And synchronization⦠takes time.
This is the trace with RUST_BACKTRACE activated.
possible Instant clock skew detected: a poll's end timestamp was before its start timestamp
start = Instant { t: 359790.8234176s }
end = Instant { t: 359790.8234173s }
β [11:10:14] 100% [ββββββββββββββββββββββββββββββββββββββββββββββββ] (393194/393194) 9.78bps, Initial syncing is completed! Syncing will continue in the background..., ETA: 00:00:00 Starting farmer ...
Farmer started successfully!
Initial plotting for plot: #0 (C:\Users\bbvedf\AppData\Roaming\subspace-cli\plots)
Error:
0: solution subscription crashed
1: couldn't update summary
2: TOML parse error at line 1, column 1
2: |
2: 1 | initial_plotting_finished = false
2: | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2: missing field `vote_count`
2:
Location:
src\summary.rs:157
ββββββββββββββββββββββββββββββββββ SPANTRACE βββββββββββββββββββββββββββββββββββ
0: subspace_cli::summary::parse_summary with self=SummaryFilePointer { file: Mutex { data: "C:\\Users\\bbvedf\\AppData\\Local\\subspace-cli\\summary.toml" } }
at src\summary.rs:154
1: subspace_cli::summary::update with self=SummaryFilePointer { file: Mutex { data: "C:\\Users\\bbvedf\\AppData\\Local\\subspace-cli\\summary.toml" } } is_plotting_finished=false is_new_block_farmed=false is_new_vote=false maybe_new_reward=None
at src\summary.rs:118
2: tokio::task::runtime.spawn with kind=task task.name=solution_subscriber task.id=98554 loc.file="src\\utils.rs" loc.line=306 loc.col=10
at C:\Users\runneradmin\.cargo\registry\src\index.crates.io-6f17d22bba15001f\tokio-1.27.0\src\util\trace.rs:16
ββββββββββββββββββββββββββββββββββ BACKTRACE βββββββββββββββββββββββββββββββββββ
1: BaseThreadInitThunk<unknown>
at <unknown source file>:<unknown line>
2: RtlUserThreadStart<unknown>
at <unknown source file>:<unknown line>
Suggestion: If you think this is a bug, please submit it to our forums: https://forum.autonomys.xyz
Run with COLORBT_SHOW_HIDDEN=1 environment variable to disable frame filtering.
Run with RUST_BACKTRACE=full to include source snippets.
PS C:\Users\bbvedf\Downloads>
@ozgun heres a full backtrace on this issue. User has wiped and is still facing this problem. Let me know if you need any further info
I think the user needs to wipe the summary. Their summary has been from previous releases.
Please do cli wipe
and in the prompts, only select summary for the wipe (no need to erase farm or node, which is great news!).
For example:
./subspace-cli-macos-aarch64-v0.3.3-alpha wipe
Do you want to wipe farmer (delete plot)? [y/n]: n
Do you want to wipe node? [y/n]: n
Do you want to wipe summary? [y/n]: y
Do you want to wipe config? [y/n]: n
Well β¦ it seems that it does different things!
I would say that now it is correct. Can you confirm?
PS C:\Users\bbvedf\Downloads> .\subspace-cli-windows-x86_64-v3-v0.3.3-alpha.exe wipe
Do you want to wipe farmer (delete plot)? [y/n]: n
Do you want to wipe node? [y/n]: n
Do you want to wipe summary? [y/n]: y
Do you want to wipe config? [y/n]: n
deleted the summary file
Wipe finished!
PS C:\Users\bbvedf\Downloads> .\subspace-cli-windows-x86_64-v3-v0.3.3-alpha.exe farm
Starting node ...
Node started successfully!
β [00:09:27] 94% [βββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ ] (402961/427293) 14.27bps, syncing, ETA: 00:28:25 possible Instant clock skew detected: a poll's end timestamp was before its start timestamp
start = Instant { t: 562532.9681732s }
end = Instant { t: 562532.968173s }
...
...
possible Instant clock skew detected: a poll's end timestamp was before its start timestamp
start = Instant { t: 565205.2640008s }
end = Instant { t: 565205.2640005s }
[00:21:27] 100% [ββββββββββββββββββββββββββββββββββββββββ] (953.67 MiB/953.67 MiB) Initial plotting finished!
You have earned: 100000000000000000 SSC(s), farmed 0 block(s), and voted on 1 block(s)!possible Instant clock skew detected: a poll's end timestamp was before its start timestamp
start = Instant { t: 565263.5236217s }
end = Instant { t: 565263.523621s }
You have earned: 100000000000000000 SSC(s), farmed 0 block(s), and voted on 1 block(s)!possible Instant clock skew detected: a poll's end timestamp was before its start timestamp
start = Instant { t: 565277.2014354s }
end = Instant { t: 565277.201435s }
You have earned: 100000000000000000 SSC(s), farmed 0 block(s), and voted on 1 block(s)!possible Instant clock skew detected: a poll's end timestamp was before its start timestamp
start = Instant { t: 565340.3146312s }
end = Instant { t: 565340.3146305s }
...
...
Yes, its working!
The clock skew bug is annoying but its no blocker. Also happening to me.
Happy farming!
OS:
Windows 10
Powershell
Version:
subspace-cli-windows-x86_64-v3-v0.3.3-alpha.exe
Gemini3d
I am also getting this message
possible Instant clock skew detected: a poll's end timestamp was before its start timestamp
start = Instant { t: 1779050.8499823s }
end = Instant { t: 1779050.8499821s }