dave0

dave0

Hi, I’m trying to test a live_file_input and everything seems to work, but I’m getting a weird error, specifically:

[error] Phoenix.LiveViewTest.UploadClient #PID<0.776.0> received unexpected message in handle_info/2: :garbage_collect

If I blow away my _build, I also get this error on the first run (but not subsequent runs):

[error] Phoenix.LiveViewTest.UploadClient #PID<0.7054.0> received unexpected message in handle_info/2: {:socket_close, #PID<0.7055.0>, {:shutdown, :closed}}

My form is simply the live_file_input along with a submit button. The error happens when submitting the form (render_submit). However, the test will continue and complete successfully.

How would I go about debugging this or getting rid of the error? Currently using version 0.15.4.

The only issue I could find that’s remotely related is the following, but that seems to be taken care of already:

https://github.com/phoenixframework/phoenix_live_view/issues/1269

The Test

defmodule MyAppWeb.Settings.ProfileLiveTest do
  use MyAppWeb.ConnCase

  import Phoenix.LiveViewTest

  setup :register_and_log_in_user

  test "GET /settings/profile/update_avatar", %{conn: conn} do
    {:ok, index_live, html} = live(conn, Routes.settings_profile_path(conn, :index))
    assert html =~ "gravatar"
    refute html =~ "Progress:"

    avatar = file_input(index_live, "#change-avatar-form", :avatar, [%{
      last_modified: 1_594_171_879_000,
      name: "elixir.png",
      content: File.read!("test/support/files/elixir.png"),
      size: 8_290,
      type: "image/png"
    }])

    assert render_upload(avatar, "elixir.png") =~ "Progress:"
    assert %{"elixir.png" => _channel_pid} = Phoenix.LiveViewTest.UploadClient.channel_pids(avatar)

    submitted_form =
      index_live
      |> form("#change-avatar-form")
      |> render_submit()

    refute submitted_form =~ "gravatar"
  end
end

Test Output (clean)

➜  mix test

21:59:21.548 [error] Phoenix.LiveViewTest.UploadClient #PID<0.7054.0> received unexpected message in handle_info/2: :garbage_collect

21:59:21.569 [error] Phoenix.LiveViewTest.UploadClient #PID<0.7054.0> received unexpected message in handle_info/2: {:socket_close, #PID<0.7055.0>, {:shutdown, :closed}}

.

Finished in 0.6 seconds
1 test, 0 failures

Randomized with seed 445784

Test Output

➜  mix test

21:44:48.667 [error] Phoenix.LiveViewTest.UploadClient #PID<0.776.0> received unexpected message in handle_info/2: :garbage_collect

.

Finished in 0.8 seconds
1 test, 0 failures

Randomized with seed 485533

Showing Posts 1 to 6

brandynbennett

brandynbennett

I’m also experiencing this issue. Would like to able to test my submit logic after the upload is consumed, but have been tripped up by this issue.

APB9785

APB9785

Creator of ECSx

I’m experiencing the same issue. The test passes, but gives an error in red:

15:05:45.708 [error] Phoenix.LiveViewTest.UploadClient #PID<0.571.0> received unexpected message in handle_info/2: :garbage_collect

The code in question is mostly copy/paste from Phoenix.LiveViewTest.file_input/4:

{:ok, view, _html} = live(conn, "/")
view |> element("#user-menu-settings") |> render_click
refute render(view) =~ "100%"

avatar =
  file_input(view, "#change-user-avatar-form", :avatar, [
    %{
      last_modified: 1_594_171_879_000,
      name: "elixir.png",
      content: File.read!("test/support/fixtures/elixir.png"),
      size: 2_118,
      type: "image/png"
    }])

assert render_upload(avatar, "elixir.png") =~ "100%"

Is this working as intended? If so, what is the official way of handling this kind of test so there is no error displayed?

mcrumm

mcrumm

Phoenix Core Team

The :garbage_collect messages should be suppressed as of v0.15.5 which was just released :slight_smile:

APB9785

APB9785

Creator of ECSx

Indeed they are - thanks!

megalithic

megalithic

Might this still be happening with LiveView 0.19.x? We’re hitting this with tests instrumenting UploadClient

hudsonbay

hudsonbay

It still happens to me on:

   {:phoenix_live_view, "~> 0.17.11"},
   {:phoenix, "~> 1.6.11"},
— All posts loaded —

Where Next? Top

Trending in Questions Top

RSP87
I’m working on a project that simulates the bumbl example in the programming phoenix book. It acts almost like an email client. We have a...
New
nseaSeb
Hello, I know there is an approach for handling lists that allows for optimized traversal, but I can’t recall the specific method (somet...
New
RemyXRenard
I’m seeing that a list inside a Kino.DataTable will be interpreted as a charlist, even if the Kino.configure() is set to charlists: :as_l...
New
velrest
So my question is quite simple and i have found no conclusive answer on forum, google or AI. Should we use :erlang.float for Integer to ...
New
samoloth
Hi, I’ve just set up an application with ash_authentication. There is only magic link strategy for now, so there is no confirmation add o...
New
brecabral
Documentation While reading the Scoped Routes section, I noticed that the documentation currently refers to a problem without explainin...
New
FlyingNoodle
If a change or preparation module uses Ash.Changeset.get_argument/2 or Ash.Query.get_argument/2 (or any of the other get_argument functio...
New

Other Trending Topics Top

mudasobwa
I am happy to introduce the very α version of the new programming language compiled to BEAM. Welcome Cure. It has literally three kille...
New
marciok
Hi there! We created Gust: A task orchestrator inspired by Airflow. For those who have never heard about Aiflow, it’s a Python-based wor...
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
Dmk
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New
netoum
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
webofbits
With AI doing more of the implementation work, I’ve been wondering how much coding I should deliberately keep doing myself. My main conc...
#ai
New

We're in Beta

About us Mission Statement

Options

Thread Display Mode




Thread Preview

Skip Thread Previews