Skip to content
New issue

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

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

Already on GitHub? # to your account

POWERPIPE_PORT is not honored #362

Closed
electriquo opened this issue May 27, 2024 · 1 comment · Fixed by #374
Closed

POWERPIPE_PORT is not honored #362

electriquo opened this issue May 27, 2024 · 1 comment · Fixed by #374
Labels
bug Something isn't working

Comments

@electriquo
Copy link

Describe the bug

POWERPIPE_PORT environment variable is not honored by powerpipe server and it forces to pass --port "$POWERPIPE_PORT" option, otherwise the default port (9033) is used.

Below you can see that although POWERPIPE_PORT environment variable is used, powerpipe server does not honor it and listens on the default port (9033).

$ env | grep POWERPIPE_PORT
POWERPIPE_PORT=9194

$ powerpipe server
[ Wait    ] Starting WorkspaceEvents Server
[ Message ] WorkspaceEvents loaded
[ Message ] Initialization complete
[ Ready   ] Dashboard server started on 9033 and listening on local
[ Message ] Visit http://localhost:9033
[ Message ] Press Ctrl+C to exit

Powerpipe version (powerpipe -v)

$ powerpipe -v
Powerpipe v0.3.1

To reproduce

  1. Use POWERPIPE_PORT
  2. Execute powerpipe server
  3. Try to access powerpipe with the port specified in POWERPIPE_PORT

Expected behavior

POWERPIPE_PORT environment variable should be honored by powerpipe server without specifying --port option.

Additional context

@electriquo electriquo added the bug Something isn't working label May 27, 2024
@pskrbasu
Copy link
Collaborator

Thanks for raising this @electriquo. We will get this fixed. 👍

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

Successfully merging a pull request may close this issue.

2 participants