config should be validated (like a schema check)
See original GitHub issueUser reported some confusing issues with paths. Turns out they had tmp: /my/path
instead of tmp: [/my/path]
(or a multiline yaml list). The config file should be checked against a schema before we go using it. The following code expects a list but is just fine taking a string '/my/path'
and turning it into a bunch of temporary directories like ['/', 'm', 'y', '/', 'p', 'a', 't', 'h']
. This bug (we guess) also resulted in temporary files getting dumped in /
which strikes me as extra bad.
tmp: /root/venvChia/plots/temp1
complete config file
# Where to plot and log.
directories:
# One directory in which to store all plot job logs (the STDOUT/
# STDERR of all plot jobs). In order to monitor progress, plotman
# reads these logs on a regular basis, so using a fast drive is
# recommended.
log: /root/venvChia/plotman/logs
# One or more directories to use as tmp dirs for plotting. The
# scheduler will use all of them and distribute jobs among them.
# It assumes that IO is independent for each one (i.e., that each
# one is on a different physical device).
#
# If multiple directories share a common prefix, reports will
# abbreviate and show just the uniquely identifying suffix.
tmp: /root/venvChia/plots/temp1
# Optional: tmp2 directory. If specified, will be passed to
# chia plots create as -2. Only one tmp2 directory is supported.
# tmp2:
# One or more directories; the scheduler will use all of them.
# These again are presumed to be on independent physical devices,
# so writes (plot jobs) and reads (archivals) can be scheduled
# to minimize IO contention.
dst: /root/venvChia/plots/plot4
# Archival configuration. Optional; if you do not wish to run the
# archiving operation, comment this section out.
#
# Currently archival depends on an rsync daemon running on the remote
# host, and that the module is configured to match the local path.
# See code for details.
# archive:
# rsyncd_module: plots
# rsyncd_path: /plots
# rsyncd_bwlimit: 80000 # Bandwidth limit in KB/s
# rsyncd_host: myfarmer
# rsyncd_user: chia
# Plotting scheduling parameters
scheduling:
# Don't run a job on a particular temp dir until all existing jobs
# have progresed at least this far. Phase major corresponds to the
# plot phase, phase minor corresponds to the table or table pair
# in sequence.
tmpdir_stagger_phase_major: 2
tmpdir_stagger_phase_minor: 1
# Don't run more than this many jobs at a time on a single temp dir.
tmpdir_max_jobs: 1
# Don't run any jobs (across all temp dirs) more often than this.
global_stagger_m: 30
# How often the daemon wakes to consider starting a new plot job
polling_time_s: 1000
# Plotting parameters. These are pass-through parameters to chia plots create.
# See documentation at
# https://github.com/Chia-Network/chia-blockchain/wiki/CLI-Commands-Reference#create
plotting:
k: 32
e: True # Use -e plotting option
n_threads: 4 # Threads per job
n_buckets: 128 # Number of buckets to split data into
job_buffer: 3300 # Per job memory
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (6 by maintainers)
Top Results From Across the Web
Schema validator check tool
The schema validator tool validates that the passed in configuration conforms to a given schema. The configuration may be JSON or YAML. To...
Read more >Schema Validation - App Config
The schema file should be a normal JSON Schema object. We do allow you to omit $schema and $id if you want to...
Read more >Validation schema of config.yaml - RAPIDS
Each key in config.yaml , for example PIDS , has a corresponding entry in the schema where we can validate its type, possible...
Read more >Config file validation should consider dynamic data for ...
Given the following config schema: // config.d.ts { /** * some random ... Config file validation should consider dynamic data for required ...
Read more >Validate configuration schema before importing configuration
It is possible to validate configuration using schema prior to importing. This will make the configuration import more robust by doing a pre ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Cool! Just leaving a pointer here, I just rambled a bit about config file handling and validation on the CLI level over in #84.
I’m happy to take on that side of the equation, but I’m pretty busy at the moment - if you end up buildin a solution that covers both the actual YAML validation as well as how config files are handled generally, knock yourself out 😃. I’ll check back here before spending any time on it, when I actually end up having time to spend.
I’ll give it a go, basing off #98. And
desert
looks nice! At first glance, it reminds me a bit of pydantic – which I like a lot 👍