Maximilian Hils

Thank you for the detailed report, @raccoonix! 🍰 The root cause here is that we unconditionally access `.content` in the hardump addon, but [`.content` may raise](https://docs.mitmproxy.org/stable/api/mitmproxy/http.html#Message.content) if servers send us...

Thanks for the detailed report! > deadline has elapsed This is a nice way of saying we hit a timeout, the rustdesk bug is very likely completely unrelated. :) The...

> Even when the proxy is running I am encountering a duplicate of #6617, #7225, or #7082: Client & mitmproxy cannot agree on a TLS version to use no matter...

Please do not click on the link shared by @AchilleasTsiamoulis, this is not a solution for this problem but a malicious phishing attempt.

Thank you for the detailed write-up, @facutuesca! 😃 🍰 Is there a reason why we cannot match on `workflow_ref` (the top-level workflow) only? What type of attack are we mitigating...

> If we only match on `workflow_ref` (that is, `ci.yml`), that means all of the workflows there will be able to publish packages. By adding the extra constraint of `job_workflow_ref`,...

> True, but I would argue that a parent-level workflow will be overscoped almost by definition, whereas a non-reusable workflow can be made minimally scoped. Reusable workflows can be made...

I think it should be fairly straightforward to build something like this based on pdoc, see https://pdoc.dev/docs/pdoc.html#using-pdoc-as-a-library! 😃 I don't wan't this in pdoc itself because I feel it's scope...

My suggestion here would be to use a custom template that overrides `is_public`: https://github.com/mitmproxy/pdoc/blob/8939754cbee82ad08b939bccfa7123d7bcb4fcc5/examples/custom-template/module.html.jinja2#L21-L32

> Thinking about it more, what I'm really looking for is filtering out inheritance that's not in the repo. This actually sounds like pretty sensible default behavior! Let's ship a...