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

Gateway - Does not reconnect after executing gateway config command #415

Open
rapcmia opened this issue Mar 3, 2025 · 1 comment
Open
Labels
bug Something isn't working docker

Comments

@rapcmia
Copy link
Contributor

rapcmia commented Mar 3, 2025

Describe the bug

When testing staging on docker, found that gateway will not reconnect after executing gateway config xxx

Screencast.from.2025-03-03.11-34-27.webm

Steps to reproduce

  1. Clone on source (dont install)
  2. Setup hummingbot and gateway using docker compose
  3. After successfully connected gateway:
    • Run any gateway config command and wait until it reconnects after successful update
    • Go to terminal where gateway is active, manually close it cltr + c
      • Then check hummingbot client status online even when gateway was terminated manually
      • To confirm if port is in use execute command sudo lsof -i :15888 (works on mac and linux)

Release version

staging 2.4.0 / dev-2.4.0

Type of installation

Source

Attach required files

No response

@rapcmia
Copy link
Contributor Author

rapcmia commented Mar 6, 2025

Found another use to reproduce the issue:

Image

Steps to reproduce:

  • After i update a config using gateway config, decided to relaunch the hummingbot client and confirm connection is still okay
  • Then to check if it will disconnect if gateway is manually stop using ctrl + c but observed that it still active
  • When you start the gateway again gateway start --passphrase=yourpassword, hummingbot client crash

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

No branches or pull requests

1 participant