Alvinkariuki

Alvinkariuki

I’m currently trying to tests file upload functionality for multiple files, here is a snippet of the code in a form

      files =
        file_input(live, "#upload_form", :files, [
          %{
            last_modified: 1_551_913_973,
            name: "file_1.png",
            content: File.read!("test/live/sample.png"),
            size: 512_623,
            type: "image/png"
          },
          %{
            last_modified: 1_551_913_974,
            name: "file_2.png",
            content: File.read!("test/live/sample.png"),
            size: 512_623,
            type: "image/png"
          }
        ])
       
        form_preupload =
        live
        |> form("#upload_form",
            some_form: %{
              user_name: "Employ",
              start_date: "2023-07-19",
            }
          }
        )

      render_upload(
        files,
        "file_1.png"
      )
    
     render_upload(
        files,
        "file_1.png"
      )

    render_submit(form_preupload)

everything works fine till the render submit. to which I get this error

** (RuntimeError) cannot consume uploaded file that is still in progress

the files are being consumed with consume_uploaded_entry/3 in a loop for loop

What could the problem possibly be

Showing Posts 1 to 5

mcrumm

mcrumm

Phoenix Core Team

It appears you are uploading the same file twice :slight_smile: If you change the second file name to "file_2.png" does it work?

Alvinkariuki

Alvinkariuki OP

No, the outcome is still the same

mcrumm

mcrumm

Phoenix Core Team

The test code looks fine. Can you share your LiveView code as well?

Alvinkariuki

Alvinkariuki OP

sure thing

here is the liveview code

def update(assigns, socket) do
  socket =
    assigns
    |> allow_upload(:files,
      max_entries: 10,
      accept: ~w(.jpg .jpeg .png .webp .pdf),
      auto_upload: true
    )

  {:ok, socket}
end

def handle_event("update_profile", params, socket) do
  {:noreply,
   socket
   |> maybe_consume_uploads(socket.assigns.profile)}
end

def maybe_consume_uploads(socket, profile) do
  uploaded_files =
    socket
    |> uploaded_entries(:files)
    |> format_and_consume_entries(socket, :files, profile)
end

def format_and_consume_entries({[entry], []}, socket, field, profile) do
  uploaded_file =
    socket
    |> consume_uploaded_entry(entry, fn %{path: path} ->
      file = %Plug.Upload{
        path: path,
        filename: "#{generate_file_name(socket, entry, field)}",
        content_type: entry.client_type
      }

      Profile.update(profile, %{field => file})
    end)

  uploaded_file
end

def format_and_consume_entries({[_ | _] = entries, []}, socket, field, profile) do
  uploaded_fields =
    for {entry, index} <- Enum.with_index(entries, 1) do
      socket
      |> consume_uploaded_entry(entry, fn %{path: path} ->
        file = %Plug.Uploda{
          path: path,
          filename: "#{generate_file_name(socket, entry, field, index)}",
          content_type: entry.client_type
        }

        Profile.update(profile, %{field => file})
      end)
    end

  uploaded_fields
end

def generate_file_name(socket, entry, field, index \\ nil) do
  username =
    if is_nil(index),
      do: "#{socket.assigns.user.fname}_#{socket.assigns.user.lname}",
      else: "#{socket.assigns.user.fname}_#{socket.assigns.user.lname}#{index}"

  case field do
    :files ->
      "file_#{username}"
  end
end
trisolaran

trisolaran

Check whether the size value you pass to file_input matches the size of the content. I get the error you’re seeing when they differ.

To be on the safe side, do not hard code the size value but set it directly from the file content. This is what I do in one of my tests:

      file_content = File.read!(Path.join(__DIR__, "two_sigma.csv"))

      file_upload =
        file_input(view, "#resolution_form", :ledes_file, [
          %{
            name: new_file_name,
            type: "text/csv",
            size: byte_size(file_content),
            content: file_content
          }
        ])
— 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