can't test async: (DBConnection.OwnershipError) cannot find ownership process

Open
#20 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
elixir
Domain
backend, databases

Research direction

Reproduce the simplified MyAppTest example with async execution and compare it with async: false. Start at lib/flame/runner.ex:408, then follow the Ecto ownership error through the reported Ecto SQL and Repo.Queryable stack frames. Done means the async FLAME call can run Repo.all(MySchema) without the ownership-process error.

Written by the indexing model from the issue text.

Description

testing flame calls that involve the repo get hung up on the ownership process.

edit: simplified example

defmodule MyAppTest do
  test "flame accessing the db" do
    FLAME.call(MyPool, fn -> Repo.all(MySchema) end)
  end
end

raises

** (EXIT from #PID<0.544.0>) an exception was raised:
         ** (DBConnection.OwnershipError) cannot find ownership process for #PID<0.592.0>.

             (ecto_sql 3.9.2) lib/ecto/adapters/sql.ex:910: Ecto.Adapters.SQL.raise_sql_call_error/1
             (ecto_sql 3.9.2) lib/ecto/adapters/sql.ex:828: Ecto.Adapters.SQL.execute/6
             (ecto 3.9.6) lib/ecto/repo/queryable.ex:229: Ecto.Repo.Queryable.execute/4
             (ecto 3.9.6) lib/ecto/repo/queryable.ex:19: Ecto.Repo.Queryable.all/3
             (flame 0.1.7) lib/flame/runner.ex:408: anonymous fn/3 in FLAME.Runner.remote_call/4

this does not apply when async: false

Dominant language
Elixir
Stars
1.2k
Forks
68
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from phoenixframework/flame

All issues in phoenixframework/flame

Similar issues

More Elixir issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.