feviskus
Hello there,
I inherited a rather complicated LiveComponent from a colleague: due to complex JS there’s no render/1 function, only update/2.
I have a hook which publishes an event to said component, which should then start an async operation on the backend.
@impl true
def handle_event("classify-users", _params, socket) do
socket =
socket
|> start_async(:perform_classification, fn ->
raise "Some error"
end)
{:noreply, socket}
end
I expect this code to eventually call the handle_async callback:
@impl true
def handle_async(:perform_classification, {:exit, reason}, socket) do
Logger.error("Could not perform classification: #{reason}")
{:noreply,
push_event(socket, "classification-finished", %{class: "Error #{reason}"})}
end
However, the component simply crashes and I don’t know why it never executes said handle_async function.
Any idea?
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Producing high quality Elixir screencasts since 2017.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixirconf-us
- #elixir-ls
- #ai
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Bringing learning, work and compliance together since 1987.
Producing high quality Elixir screencasts since 2017.
**Building the future of software with AI, trust, and human connection.**
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 2- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
tcoopman
The following is just a guess, I’m on my phone so can’t check it out.
A live component lives in the same process of the liveview. Maybe the error can be caught on the liveview itself?
As I said this is just a guess, it could be something completely different.
feviskus
thanks, but after careful investigation I came to the conclusion that it’s a layer 8 problem:
The
:exit-matching function was indeed called but not logged as the interpolation of#{reason}raises an Exception ifreasonis a tuple…Using
"#{inspect(reason)}"instead.