Error: no such option: --console-log
See original GitHub issueOn branch release--0.31
using the --console-log
option flag with superset
or flask run
fails with the error: Error: no such option: --console-log
.
The docs mention interaction with --debug
/--debugger
so I tried a variety of combinations of flags and all resulted in the same error listed above:
superset run -h 0.0.0.0 -p 8088 --with-threads --reload --debugger --console-log
superset run -h 0.0.0.0 -p 8088 --with-threads --reload --debugger --console-log --debug
superset run --console-log --debug
FLASK_DEBUG=1 superset run --console-log --debug
FLASK_DEBUG=1 flask run -p 8088 --with-threads --reload --debugger --console-log
FLASK_DEBUG=1 flask run -p 8088 --with-threads --reload --debugger --console-log --debug
FLASK_DEBUG=1 flask run -p 8088 --console-log
FLASK_DEBUG=1 flask run -p 8088 --console-log --debugger
FLASK_DEBUG=1 flask run -p 8088 --console-log --debug
flask run --console-log --debug
flask run --console-log
Expected results
Something roughly like:
* Serving Flask app "superset:app" (lazy loading)
* Environment: development
* Debug mode: on
* Running on http://127.0.0.1:5000/ (Press CTRL+C to quit)
* Restarting with stat
* Debugger is active!
* Debugger PIN: 303-869-439
Actual results
Error: no such option: --console-log
How to reproduce the bug
- Create a virtualenv for superset and activate it
- Install the requirements in requirements.txt, requirements-dev.txt and docs/requirements.txt
- Run:
superset run --console-log --debug
orflask run --console-log --debug
- See error
Environment
- superset version: [e.g.
release--0.31
700cbf4f
] - python version:
Anaconda Python 3.6.7 :: Anaconda custom (64-bit)
- node.js version:
v11.14.0
- npm version:
6.9.0
Checklist
Make sure these boxes are checked before submitting your issue - thank you!
- I have checked the superset logs for python stacktraces and included it here as text if there are any.
- I have reproduced the issue with at least the latest released version of superset.
- I have checked the issue tracker for the same issue and I haven’t found one similar.
Additional context
This bug also appeared on Mac OS X 10.14.4/homebrew Python 3.7.3/Anaconda 3.6.7
Issue Analytics
- State:
- Created 4 years ago
- Comments:9 (8 by maintainers)
Top Results From Across the Web
Error: no such option: --console-log · Issue #7389 - GitHub
On branch release--0.31 using the --console-log option flag with superset or flask run fails ... Error: no such option: --console-log #7389.
Read more >Error: No such option yet I've clearly set the option up
I'm just starting out with a simple project and using the Click library and have hit a snag early on that I can't...
Read more >error saving model: No such option: --output - Prodigy Support
Hi all, I am using this line to train and save my model !python -m prodigy train --ner ner_location_distinction en_core_web_lg --output ...
Read more >Console | Node.js v19.3.0 Documentation
A Console class with methods such as console.log() , console.error() , and console.warn() that can be used to write to any Node.js stream....
Read more >Troubleshooting — SublimeLinter 3.4.24 documentation
SublimeLinter: jshint output: env: node: No such file or directory. Note. On Windows, linter errors messages will not always appear. It appears to...
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
I have seen this issue a few times as well.
@MarcusSorealheis Check out https://github.com/apache/incubator-superset/pull/7428