The option --server.fileWatcherType does not work from the command line
See original GitHub issueSummary
The option --server.fileWatcherType does not work from the command line but works when specified in the toml config file.
Steps to reproduce
What are the steps we should take to reproduce the bug:
Run streamlit as follows:
streamlit run hello.py --server.fileWatcherType=none --logger.level debug
Looking at the log, you will notice a line like:
Watcher created for /path/to/hello.py
However, if I set this variable in the toml file to none, it works as expected.
Expected behavior:
A watcher should not be created when set to none and thus the above line should not be present in the log.
Actual behavior:
The fileWatcherType still defaults to ‘auto’ and an EventBasedFileWatcher is created.
Is this a regression?
Not sure
Debug info
- Streamlit version: (get it with
0.65, 0.69
) - Python version: (get it with
3.6
) - Using Pip
- OS version: tested on both MacOS 10.15.7 (Python 3.6.4) and Ubuntu 18.04 (Python 3.6.9)
- Browser version: N/A
Issue Analytics
- State:
- Created 3 years ago
- Reactions:3
- Comments:6 (1 by maintainers)
Top Results From Across the Web
Configuration - Streamlit Docs
Configuration. Streamlit provides four different ways to set configuration options. This list is in reverse order of precedence, i.e. command line ...
Read more >When running the Control-M/Agent utility ctmfw (file watcher ...
When running the Control-M/Agent utility ctmfw (file watcher) on a Unix host as a non Control-M user either thru a Command or File...
Read more >Config file and command line options - Jupyter Server
This may need to be increased if you run into an OSError: [Errno 24] Too many open files. This is not applicable when...
Read more >Server - IBM
You can learn to work on server using the information provided here. The following command-line options are for the IBM Security Directory Integrator...
Read more >Jigsaw command line options - W3C
That directory should (if no other command line options are provided) contain at least: ... but only one server can be run within...
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
so, this commands
echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p
helpedafter some time i get a similar error too. version 0.83.0
fs.inotify.max_user_instances
doesn’t help.