-
Notifications
You must be signed in to change notification settings - Fork 493
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
[Investigation] Allow tealdbg to listen to any address #1809
Comments
Makes sense - is there any reason for it to just not listen on all interfaces? Changing to :%d should suffice. |
We need to investigate the feasibility of this request. Thanks for porting this into an issue (from discord @fabrice102 ) |
@fabrice102 please review the PR I linked. |
By the way I needed to run "docker-compose up -d" after changing the docker-compose.yml file. Restarting my docker container was not sufficient. Possibly should add it as a step. |
Is your feature request related to a problem? Please describe.
When using
tealdbg
from inside sandbox (https://github.com/algorand/sandbox),tealdbg
needs to allow listening from any address and not just localhost. (This is true on macOS. It is possible that Docker on Ubuntu does not require that.)Currently, the only solution I know how to use
tealdbg
inside sandbox is the following:- 9392:9392
inside the ports section ofdocker-compose.yml
: https://github.com/algorand/sandbox/blob/0c15c8f5e0256770ef434333fee4ca55bb794ce0/docker-compose.yml#L21./sandbox enter algod
socat
:apt install socat
echo "int 1" > a.teal
tealdbg
in the background with new port (e.g., 1234):tealdbg debug --remote-debugging-port 1234 a.teal &
socat tcp-listen:9392,reuseaddr,fork tcp:localhost:1234
tealdbg
where 1234 is replaced by 9392.For information: netstat
Describe the solution you'd like
Add a flag to
tealdbg
to allow to listen to any address rather than just127.0.0.1
.That is to change
127.0.0.1
ingo-algorand/cmd/tealdbg/server.go
Line 97 in 693b673
Additional context
This issue comes from a discussion on Discord.
The text was updated successfully, but these errors were encountered: