rebuild_references_index command should respect verbosity=0
See original GitHub issueIs your proposal related to a problem?
The ./manage.py rebuild_references_index
command generates a lot of output, which may crowd out more useful messages when running setup scripts.
Describe the solution you’d like
This command should respect the conventional --verbosity=0
flag to suppress output:
./manage.py rebuild_references_index --verbosity=0
This is supported by similar commands such as ./manage.py update_index
- for anyone interested in picking this up, I’d recommend referring to how this was done in #9271, and applying a similar change to wagtail/management/commands/rebuild_references_index.py.
Issue Analytics
- State:
- Created a year ago
- Comments:13 (10 by maintainers)
Top Results From Across the Web
Database Engine events and errors - SQL Server
Consult this MSSQL error code list to find explanations for error messages for SQL Server database engine events.
Read more >Command Line Interface and Environment Variables Reference
When exporting as .env format, defines how connections should be serialized. Default is uri . -v, --verbose. Make logging ...
Read more >Picard - GitHub Pages
To obtain the DETAILED metric table, you must add the PROB_EXPLICIT_READS option to your command line and set the value between 0 and...
Read more >git-apply Documentation - Git
git-apply - Apply a patch to files and/or to the index ... This command applies the patch but does not create a commit....
Read more >8. cabal.project Reference — Cabal 3.4.0.0 User's Guide
Control the verbosity of cabal commands, valid values are from 0 to 3. ... respect to preferences; specifically, no single package could be...
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
@MRZHD1 Sure, go for it!
Completed in #9602