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

commands which are meant to connect to "process-compose" via REST API fail silently if server is not accessible or returns unexpected result #69

Closed
adrian-gierakowski opened this issue Jul 19, 2023 · 2 comments
Labels
bug Something isn't working

Comments

@adrian-gierakowski
Copy link
Contributor

Defect

running commands like:

process-compose process list

doesn't exit with non-zero status if server is not accessible, or returns unexpected result

Version of process-compose:

Process Compose
Version:        v0.51.4
Commit:         e3cc52e

OS environment:

nixos

Steps or code to reproduce the issue:

make sure there is no process-compose running on default port and run

process-compose process list

Expected result:

exits with non-zero status, and prints an error that it could not connect to server on given port

if some sever is accessible but returns unexpected result, this should also result non-zero status and a message that connection was established but requests failed, suggesting that some process other than process-compose might be running on given host\port

Actual result:

exists silently with status 0

@F1bonacc1 F1bonacc1 added the bug Something isn't working label Jul 19, 2023
@F1bonacc1
Copy link
Owner

Good catch.
Will be fixed in the next release.

@F1bonacc1
Copy link
Owner

Should be fixed in v0.60.0
Feel free to reopen if it doesn't work as expected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants