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

Composer writes debug data into stderr instead of stdout #4034

Closed
FractalizeR opened this issue May 15, 2015 · 2 comments

Comments

@FractalizeR
Copy link

commented May 15, 2015

We were performing a deploy using SaltStack to one of our servers and noted, that composer writes insignificant data into stderr (and some more from the same command to stdout). Composer version is Composer version 1.0-dev (bc45d9185513575434021527d7756420e9f4b2cf) 2015-05-11 14:49:39

I think this should not be an intended behaviour.

----------
          ID: run_composer_install
    Function: cmd.run
        Name: composer install --prefer-dist --no-dev --no-interaction
      Result: True
     Comment: Command "composer install --prefer-dist --no-dev --no-interaction" run
     Started: 16:20:12.554394
    Duration: 3143.24 ms
     Changes:
              ----------
              pid:
                  19162
              retcode:
                  0
              stderr:
                  Loading composer repositories with package information
                  Installing dependencies from lock file
                  Nothing to install or update
                  Generating autoload files
              stdout:
                  Generating optimized class loader
                  Compiling common classes
@sbuzonas

This comment has been minimized.

Copy link
Contributor

commented May 15, 2015

This is the intended behavior. Relatively standard for unix commands to have only their standard output in stdout and ancillary messages depending on verbosity to stderr. Check the exit code if you want to know if it failed.

#3787 (comment) has more details as to why it has changed.

@FractalizeR

This comment has been minimized.

Copy link
Author

commented May 16, 2015

I see. Thanks.

Refs for further readers: #1905, #3715

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.