question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Unexpected stderr/stdout on load initial cache file in output

See original GitHub issue

Brief Issue Summary

I try to load a project which use init cache files on configuration.

settings.json: cmake.configureArgs": [ -C...cmake]

The configuration works but the cms-client provides a unexpected stderr/stdout.

[cms-client] Unexpected stderr/stdout data from CMake Server process: loading inital cache file .....cmake

Expected:

No unexpected warning

Platform and Versions

  • Operating System:Windows 10
  • CMake Version: 3.10.0
  • VSCode Version: 1.21.1
  • CMake Tools Extension Version: 0.11-beta5

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:7 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
docbrowncommented, Apr 14, 2018

With CMake 3.11, I also get these warnings using default settings (cmake.configureArgs is not set).

[cmake] Populating gsl
[cms-client] Unexpected stderr/stdout data from CMake Server process: -- Configuring done
[cms-client] Unexpected stderr/stdout data from CMake Server process: -- Generating done
[cms-client] Unexpected stderr/stdout data from CMake Server process: -- Build files have been written to: C:/Dev/wasm/build/gsl-subbuild
[cms-client] Unexpected stderr/stdout data from CMake Server process: [1/6] Performing update step for 'gsl-populate
[cms-client] Unexpected stderr/stdout data from CMake Server process: '
[cms-client] Unexpected stderr/stdout data from CMake Server process: [2/6] No configure step for 'gsl-populate'
[cms-client] Unexpected stderr/stdout data from CMake Server process: [3/6] No build step for 'gsl-populate'
[cms-client] Unexpected stderr/stdout data from CMake Server process: [4/6] No install step for 'gsl-populate'
[cms-client] Unexpected stderr/stdout data from CMake Server process: 
[cms-client] Unexpected stderr/stdout data from CMake Server process: [5/6] No test step for 'gsl-populate'
[cms-client] Unexpected stderr/stdout data from CMake Server process: [6/6] Completed 'gsl-populate'
[cmake] Configuring done
[cmake] Generating done
[build] Starting build

The messages seem to be produced by the sub-build executed by FetchContent_Populate.

0reactions
kenkitcommented, Jul 4, 2018

Is there a solution to this ? I saw this but haven’t had the time to try it OUTPUT_STRIP_TRAILING_WHITESPACE https://stackoverflow.com/questions/13037230/how-do-i-initialize-a-cmake-variable-with-the-result-of-a-shell-command

Read more comments on GitHub >

github_iconTop Results From Across the Web

Unexpected output from redirection - bash - Stack Overflow
The specific condition that triggers the bug seems to be when stderr is not a terminal. When I tried redirecting stderr to another...
Read more >
How to redirect stderr to stdout then pipe (apt-cache)
Confirmed it's using stderr . Something to do with ordering of redirects? $ apt-cache show contractor |cat 2>&1. Nope
Read more >
10+ practical examples to learn python subprocess module
A replacement program to execute. stdin, stdout, stderr, These specify the executed program's standard input, standard output, and standard ...
Read more >
Bash Reference Manual - GNU.org
This chapter briefly summarizes the shell's 'building blocks': commands, control structures, shell functions, shell parameters, shell expansions ...
Read more >
Docker Compose release notes | Docker Documentation
Pull Request compose#10030; Distinguished stdout and stderr in up logs. ... Fixed compose#9208; Load project from files when explicitly set by user.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found