Calling `settings_set` writes invalid config in the daemon_settings.yml
See original GitHub issuedaemon_settings.yml
before and after passing a valid setting(happens for any setting, either valid or invalid)
Specifically lbryum_servers
field is overwritten in the python’s list format instead of colon separated
$ cat ~/.lbrynet/daemon_settings.yml
blockchain_name: lbrycrd_regtest
download_directory: /home/hackrush/Downloads
lbryum_servers:
- localhost:50001
reflect_uploads: false
share_usage_data: false
use_upnp: false
$ lbrynet-cli settings_set --download_directory="/home/hackrush/Downloads" > /dev/null
$ cat ~/.lbrynet/daemon_settings.yml
blockchain_name: lbrycrd_regtest
download_directory: /home/hackrush/Downloads
lbryum_servers:
- [localhost, 50001]
reflect_uploads: false
share_usage_data: false
use_upnp: false
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
semgrep reports "invalid configuration file" when running from ...
Describe the bug Fresh install of semgrep from brew reports this error when calling 'semgrep' via cli ➜ ~ semgrep semgrep error: missing ......
Read more >ISY994 - Invalid config - Configuration
I am new to Home Assistant. I am trying to configure my ISY994i. It is running V5.0.13a I have followed the Instructions on...
Read more >Prettier: invalid configuration file even though the file is ...
The configuration file that I created through the command "echo .prettierrc.json" created with file format UTF16 and that caused an error ...
Read more >How to solve the error: "Invalid compiler config file"
Hi Bogdan, we have had no compiler settings in the localsettings.properties. I'd thought the cpptestrace call to generate the bdf before ...
Read more >How to Fix Errors in YAML (.YML) Config Files - Knowledgebase
Below is a list of common mistakes that people make when configuring YAML files. You should be using spaces instead of tabs.
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 Free
Top 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
@KamilPiekutowski can you see if this still happens on 0.19 RC37 using his example. You should be able to create that file from scratch with his settings and see if it still messes up the sever list.
Ran into the same on Windows: If you have a custom lbryum_servers: config in your daemon_settings.yml such as:
And then go into app settings to change any persistent settings, i.e. max key fee, the file is then saved as (notice missing curley braces and syntax):
When restarting the daemon, you get:
The correct syntax would be:
or
lbryum_servers: ["victor.lbry.tech:50001"]