ryanditjia
Hello everyone, when I run my unit test, I sometimes (not all the time) run into this error:
(Postgrex.Error) ERROR 40P01 (deadlock_detected) deadlock detected
hint: See server log for query details. Process 11437 waits for ShareLock on transaction 56033; blocked by process 11436. Process 11436 waits for ShareLock on transaction 56040; blocked by process 11437.
The test attempts to insert 3 records:
work_orders =
for _ <- 1..3 do
{:ok, work_order} = Documents.create_work_order(attrs)
work_order
end
expected_counters = [1, 2, 3]
assert expected_counters == work_orders |> Enum.map(& &1.counter)
create_work_order is an Ecto.Multi that:
- Inserts counter to
countersDB (business requirement dictates that counter restarts from 1 every year) - Grabs the returned counter to insert together to
work_ordersDB - Repo.transaction()
Is the above loop a bad way to test? Or is my transaction function incorrect even though it works (pasted below)?
def create_work_order(attrs \\ %{}) do
counter_changeset = Counter.changeset(%Counter{}, attrs)
work_order_changeset = WorkOrder.creation_changeset(%WorkOrder{}, attrs)
Multi.new()
# Get the next counter of the year
# If year doesn’t yet exist, create one and set counter to 1 (database default)
|> Multi.insert(:next_counter, counter_changeset,
# If year exists, increment the counter by 1
conflict_target: :year,
on_conflict: [inc: [counter: 1]]
)
# Insert work order, with counter added to the changeset
|> Multi.insert(
:work_order,
fn %{next_counter: %{counter: counter}} ->
work_order_changeset
|> Ecto.Changeset.put_change(:counter, counter)
end
)
|> Repo.transaction()
|> case do
{:ok, %{work_order: work_order}} ->
{:ok, work_order}
{:error, :next_counter, _changeset, _changes} ->
# Return work_order_changeset for more thorough field checks
{:error, %{work_order_changeset | action: :insert}}
{:error, :work_order, changeset, _changes} ->
{:error, changeset}
end
end
Trending in Questions
Hey guys,
I’ve got a huge CSV ( around 10 GB ) that needs to be processed hourly
Do you guys have any suggestions what is the best prac...
New
Hello!
Could someone please give me a help/sample code, how to delete a file from s3 using waffle/waffle_ecto from Phoenix app.
I creat...
New
I have what I’ve heard referred to as a “lookup table” in my database. This is a way of assigning codes to common values. One common lo...
New
What approach to take when sending live updates to “random” users Hi! I have a question, I have a little chat app, and when I create a DM...
New
Anyone here using Honeybadger?
My Honeybadger account is being overwhelmed with noise from some bots. Seeing a lot of
Bandit.HTTPError...
New
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
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
Other Trending Topics
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hobbes is a low-level distributed database for the Elixir programming language.
Hobbes provides a simple, safe, and scalable storage lay...
New
ExRatatui lets you cook up rich terminal UIs in Elixir, powered by Rust’s ratatui via Rustler NIFs. Build interactive terminal applicatio...
New
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
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
There are three potential reasons for members of this forum to have a look at https://vutuv.de
You are tired or annoyed of LinkedIn.
Yo...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixir-ls
- #ai
- #elixirconf-us
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming










Showing Posts 1 to 2- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
kip
Have you configured the Ecto Sandbox?
It will isolate each test in a transaction and rollback the transaction so each test has a consistent view of the data. It will also make it much less likely you will encounter deadlocks.
ryanditjia
Thanks kip. Yes, I believe this is Phoenix’s default, but I rechecked just in case. I also run into a unique index constraint error with another test but that’s rarer, I’d say 5% of the time, while deadlock is 10%.
Not a dealbreaker by any stretch of the imagination, and if it gets too annoying I can simply set async to false.
If you think there could be something wrong or missing with the way my Ecto.Multi is set up, please let me know, I’m new to Elixir and Phoenix and am keen to dive deeper.
Thanks again