dfalling

dfalling

Tips for troubleshooting PubSub messages not received?

I’m trying to follow LiveBeat’s example of using PubSub to send messages to LiveViews. I’ve also read through a ton of topics here, so I’m not sure what I’m doing wrong…

I’m broadcasting on a PubSub topic that a LiveView is subscribed to. I think the topic and everything is wired up correctly, but the LiveView never sees the message (or shows a failure for not handling it properly.)

Here’s my PubSub setup:

defmodule Ido.Trips.PubSub do
  @moduledoc """
  PubSub for trips
  """

  # defined in application.ex
  @pubsub Ido.PubSub

  def broadcast_email_processed(element) do
    msg = %Ido.Trips.Events.EmailProcessed{element: element}
    broadcast!(element.trip_id, msg)
  end

  defp broadcast!(trip_id, msg) do
    Phoenix.PubSub.broadcast!(@pubsub, topic(trip_id), {__MODULE__, msg})
  end

  def subscribe_to_trip_id(trip_id) do
    Phoenix.PubSub.subscribe(@pubsub, topic(trip_id))
  end

  def unsubscribe_to_trip_id(trip_id) do
    Phoenix.PubSub.unsubscribe(@pubsub, topic(trip_id))
  end

  defp topic(trip_id) do
    "trip:#{trip_id}"
  end
end

I’m subscribing to it in a handle_params in my LiveView, not mount because I need the id of the Trip:

@impl true
  def handle_params(%{"id" => id} = params, _, socket) do
    if connected?(socket) do
      # make sure no duplicates
      Ido.Trips.PubSub.unsubscribe_to_trip_id(id)

      Ido.Trips.PubSub.subscribe_to_trip_id(id)
    end
...

@impl true
  def handle_info(
        {Ido.Trips.PubSub, %Ido.Trips.Events.EmailProcessed{element: element}},
        socket
      ) do
        {:noreply, put_flash(socket, :info, "An element was processed from email")}
  end

What did I mess up? I don’t have any warnings/errors in the console during startup or when I broadcast the message.

Thanks!

Marked As Solved Switch mode

dfalling

dfalling

Ooof, I’m an idiot. So I was testing by running mix phx.server in one shell, and iex -S mix, and I somehow thought those would be the same app.

I just ran an iex -S mix phx.server, and then in that same REPL triggered some broadcasts and it worked perfectly.

Thank you all so much!

Also Liked

thomas.fortes

thomas.fortes

First thing I would check is if a generic handle_info(msg, socket) catch something in the msg.

sodapopcan

sodapopcan

Subscribing in handle_params could prove to be problematic. It’s hard to see without more context—is your LiveView handling both “index” and “show” pages? If not, then you can still get the id from def mount(%{"id" => id}, _session, socket). If they are sharing a LiveView, then as you have it you aren’t unsubscribing from the previous trip before subscribing to the new one which means they would pile up. handle_params get called any time there is a patch event. This applies to things like query params or subroutes that may potentially point to the same LiveView. This means that on any patch to the same trip it will unsubscribe and resubscribe. I’m not actually sure what effect that would have, but I wouldn’t say it’s the best place to put it. Possibly there is a sane way to do so but it’s not something I’ve ever seen before and I feel like it could lead to confusing bugs.

sodapopcan

sodapopcan

Ah, so is your problem that you are patching when switching between trips and that’s why you need handle_params? Otherwise, params is the first parameter given to mount so you should definitely be able to get the id from there.

You could also subscribe to a general trips channel and see if it’s the current one or not:

handle_info({:trip_updated, trip}, socket)
    when trip.id == socket.assigns.trip.id do
  # ...
  {:noreply, socket}
end

Where Next?

Trending in Questions Top

jonnycharles
I’m in search of an Elixir library that offers PDF generation capabilities similar to Ruby’s Prawn. While there have been discussions abo...
New
spammy
I’m looking to build a personal workflow to quickly deploy web applications written in elixir/phoenix, for local consumption (ie not on t...
New
silverdr
Using Phoenix.LiveView.TagEngine as an EEx.Engine is deprecated! To compile HEEx, use Phoenix.LiveView.TagEngine.compile/2 instead. Sta...
New
saveman71
Hello ! We want new/edit form pages to POST/PUT to their own URL rather than the resources REST defaults (post /things, put /things/:id)...
New
dli
Before I dive in myself, did anyone successfully sprinkle Hologram into their existing LiveView app? Looking for hints regarding: Addi...
New
bottlenecked
Hi all, I wanted to ask how the community is dealing with post-release steps. Today we have Ecto migrations, which make sure that the db...
New
michallepicki
I am using Oban and occasionally, shortly after a deployment, a handful of jobs can fail because of dependency on other parts of the syst...
New

Other Trending Topics Top

JesseHerrick
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
jimsynz
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Damirados
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge & Solve. They are GUI (Emerge) and State management (S...
New
ausimian
Emily is an Elixir library that runs Nx computations on Apple’s MLX. Install it as the default Nx backend and Nx, defn, Axon, Nx.Serving,...
New
type1fool
I just stumbled on a newly redesigned elixir-lang.org. :tada: It looks like @Software_Mansion did the work, and I think it is generally a...
New
akoutmos
@hugobarauna and I (Alex Koutmos) have been hard at work on writing a book on Nerves that takes you from simply blinking LEDs to building...
New

We're in Beta

About us Mission Statement