Live data from Hacker News

Show HN: Httpdbg – A tool to trace the HTTP requests sent by your Python code

github.com

31–40 of 62 posts

Re: Show HN: Httpdbg – A tool to trace the HTTP requests sent by your Python code

#31

Earlier quoted context omitted.

> If you're coding something up, why wouldn't you know that piece of code does a HTTP/s request? Because tracing all side-effects in a huge codebase with a lot of libraries and layers can be a daunting task. Update: if you haven't worked with 20 year old >1m LOC codebase which went through many different teams and doesn't have any documentation whatsoever, you may lack necessary perspective to see value tools like th…

Sounds like people dealing with code they have no idea what it does. No amount of tools are going to help with that.

I think you attract downvotes because tools are helpful. If you have a huge unknown codebase, it can be nice to attack it from different angles. Reading code is useful, but observing what it does in runtime can be useful, too. Also, with hairier code, it can be more useful to first observe and prod it like a black box.

Re: Show HN: Httpdbg – A tool to trace the HTTP requests sent by your Python code

#32

Earlier quoted context omitted.

Sounds like people dealing with code they have no idea what it does. No amount of tools are going to help with that.

I think you attract downvotes because tools are helpful. If you have a huge unknown codebase, it can be nice to attack it from different angles. Reading code is useful, but observing what it does in runtime can be useful, too. Also, with hairier code, it can be more useful to first observe and prod it like a black box.

Just the 1 downvote.

Yes, "tools are helpful", but whether there's a python/http specific tool that doesn't do what more generic tools do remains to be seen.

Re: Show HN: Httpdbg – A tool to trace the HTTP requests sent by your Python code

#33
post #29

I've always used a proxy, like charles proxy, for this exact purpose. A neutral middle-man that gives exact timing/response data.

That’s fine if you can, but say you want to trace deployed on stage, or shudders even production. Or you code tests against some CI and can only add Python.

Re: Show HN: Httpdbg – A tool to trace the HTTP requests sent by your Python code

#35

Earlier quoted context omitted.

If a 3rd party library you depend on has bugs, you have bugs. And you need to either submit a patch to the library or find a workaround.

Or just not use arbitrary 3rd party stuff hoping it works :) libcurl is used on billions of devices across the world and has plenty of debugging capabilities. MITM proxy works across all languages.

[flagged]

Re: Show HN: Httpdbg – A tool to trace the HTTP requests sent by your Python code

#36
post #35

Earlier quoted context omitted.

Or just not use arbitrary 3rd party stuff hoping it works :) libcurl is used on billions of devices across the world and has plenty of debugging capabilities. MITM proxy works across all languages.

[flagged]

[flagged]

Re: Show HN: Httpdbg – A tool to trace the HTTP requests sent by your Python code

#37
That's pretty cool! I was playing last night and implemented resumable downloads[0] for pip so that it could pick up where it stopped upon a network disconnect or a user interruption. It sucks when large packages, especially ML related, fail at the last second and pip has to download from scratch. This tool would have been nice to have. Thanks a bunch,

- [0]: https://asciinema.org/a/1r8HmOLCfHm40nSvEZBqwm89k

Re: Show HN: Httpdbg – A tool to trace the HTTP requests sent by your Python code

#38

I could be lost here (C/PHP/Node coder mainly in code I've used) Why is it a special case to track HTTP/s requests, that otherwise couldn't be logged like any other process/function? I'd guess most people use libcurl and you can wrap something around that. I guess I'm lost on why this is HTTP or Python specific, or if it is, fine.

[deleted]

Re: Show HN: Httpdbg – A tool to trace the HTTP requests sent by your Python code

#40
post #29

I've always used a proxy, like charles proxy, for this exact purpose. A neutral middle-man that gives exact timing/response data.

That’s fine if you can, but say you want to trace deployed on stage, or shudders even production. Or you code tests against some CI and can only add Python.

Well I would never use a script like this at a real job outside of local testing.

What you'd want on stage is probably using opentelemetry, which I believe has auto-instrumentation for all network calls. Then you have the data forever and it's in a public, shared platform that is permissioned and everybody knows, and will still exist in 10 years.

Post reply on HN