You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! I heard about bandit on the ThinkingElixir podcast and wanted to give it a try. I found what I think might be a bug.
I am using bandit 0.6.7, thousand_island 0.5.15, phoenix 1.7.0-rc.2, elixir 1.14.0 and erlang 25.0.
I make a new phoenix project via mix archive.install hex phx_new 1.7.0-rc.2 ; mix phx.new foo - then I replace plug_cowboy with {:bandit, "~> 0.6.7"} in hex.exs and add adapter: Bandit.PhoenixAdapter in config/config.exs.
If I send any messages to a liveview process, the first time such a message is sent, I see the error (FunctionClauseError) no function clause matching in Bandit.HTTP1.Handler.handle_info/2 (more lines attached below). Subsequent messages do not repeat the same error. The liveview's handle_info callback is invoked in both cases.
This is a simplified example, but it happens when sending messages "up" from a livecomponent to the surrounding liveview (via send(self(), ...), and when using pubsub to subscribe to a topic from a liveview.
Hi! I heard about bandit on the ThinkingElixir podcast and wanted to give it a try. I found what I think might be a bug.
I am using bandit 0.6.7, thousand_island 0.5.15, phoenix 1.7.0-rc.2, elixir 1.14.0 and erlang 25.0.
I make a new phoenix project via
mix archive.install hex phx_new 1.7.0-rc.2 ; mix phx.new foo
- then I replaceplug_cowboy
with{:bandit, "~> 0.6.7"}
in hex.exs and addadapter: Bandit.PhoenixAdapter
in config/config.exs.If I send any messages to a liveview process, the first time such a message is sent, I see the error
(FunctionClauseError) no function clause matching in Bandit.HTTP1.Handler.handle_info/2
(more lines attached below). Subsequent messages do not repeat the same error. The liveview'shandle_info
callback is invoked in both cases.Example liveview code
Full error output:
The text was updated successfully, but these errors were encountered: