Runtime error on special Phoenix.Endpoint usage about bandit HOT 5 CLOSED

Yep. Looks like you have a process sending a message ({#Reference<0.2692061718.3879796743.144965>, :ok}) to the underlying HTTP handler process. This isn't generally a supported thing (the Plug API doesn't give us any way to expose such messages up to the application, and because of the way that the underlying server works there's no other easy way for your application to be notified of them).

Is this a new error (since 0.6.9)? I don't see offhand where this would be coming from telemetry, at least within our implementation, but it's brand new so it's always a possibility. I might also suspect that it is something our telemetry calls in your code; what telemetry events are you hooking, and what's the implementation on your side of them?

from bandit.

I don’t know if it’s new, what version would you like me to try on?

what telemetry events are you hooking, and what's the implementation on your side of them

I’m attaching handlers for phoenix.router_dispatch.stop.duration in my code, do you think it can be linked? I’ll try again but with my telemetry handlers disabled 👍

from bandit.

I would try with Bandit 0.6.8 if you could, just to ensure it's nothing related to our recent telemetry additions (the event you mention is emitted by phoenix itself, so I'm doubtful, but want to be sure).

I suspect that you'll continue to see the errors occurring even on 0.6.8, at which point we can confidently start looking at what it is specifically that your telemetry handlers are doing. Is it possible to share them here?

from bandit.

I’m using TelemetryUI to attach handlers. You can see the code here: https://github.com/mirego/telemetry_ui/blob/v2.0.1/lib/telemetry_ui/reporter.ex#L20

from bandit.

Closing as there's nothing for us to do here.

from bandit.