Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

--force should stop warnings #3

Closed
garlandkr opened this issue Jul 29, 2013 · 1 comment
Closed

--force should stop warnings #3

garlandkr opened this issue Jul 29, 2013 · 1 comment

Comments

@garlandkr
Copy link

If you are warned that --force may be needed to proceed, why are you again warned after using --force?

Warning: stdout maxBuffer exceeded.� Used --force, continuing.
Done, but with warnings.

This can give unwanted results in Jenkins depending on what types of plugins you are using.

@weitzman
Copy link
Member

weitzman commented Aug 7, 2013

Drush is not giving that message.

@weitzman weitzman closed this as completed Aug 7, 2013
weitzman added a commit that referenced this issue Feb 12, 2018
DieterHolvoet added a commit to DieterHolvoet/drush that referenced this issue Sep 14, 2023
…: Argument drush-ops#3 ($showMachineNames) must be of type bool, string given'
DieterHolvoet added a commit that referenced this issue Sep 14, 2023
…: Argument #3 ($showMachineNames) must be of type bool, string given' (#5759)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants