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.

Sign up for GitHub

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

Jump to bottom

econnrefused errors give no insight to cause #210

Open
joesanford opened this issue May 10, 2019 · 0 comments
Open

econnrefused errors give no insight to cause #210

joesanford opened this issue May 10, 2019 · 0 comments

Comments

@joesanford
Copy link

As I've been working with escalus, I have noticed that any time it cannot connect, it gives nothing more than a badmatch on {error, econnrefused} with no insight into what it is trying to connect to, how the host responded, etc.

Can this be expanded to include useful information on dumps? I end up having to start tcpdumping traffic just to figure out where escalus is trying to connect to.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@joesanford