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

First 5 of 5 Posts Switch mode

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

stjefim
Hello! Suppose you are building workflow (order / task / payment) processing system with the following requirements: Each workflow con...
New
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
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
roeland
Kia ora, We have been using elixir-google-api to connect to Google Drive. However, with the updates to Tesla due to CVEs this is now bro...
New
rahultumpala
Hello, I have an Elixir backend that implements a custom protocol over TCP. I want to load test the backend and assess the performance o...
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 &amp; Solve. They are GUI (Emerge) and State management (S...
New
netoum
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
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
juhalehtonen
There has been a thread to discuss the Stack Overflow Developer Survey on this forum every year since 2018, so here’s yet another one for...
New

We're in Beta

About us Mission Statement