alexandrubagu
Hi,
I want to handle the following exit example ( String.to_integer(input) is jus an example and can be replaced with raise). This happen when I call My.GenServer.some_method(My.GenServer, "test"). I will be grateful if someone has a suggestion for this.
10:26:42.321 [error] GenServer My.GenServer terminating
** (stop) exited in: Task.await(%Task{owner: #PID<0.124.0>, pid: #PID<0.128.0>, ref: #Reference<0.4181578440.4035444737.94083>}, 5000)
** (EXIT) an exception was raised:
** (ArgumentError) argument error
:erlang.binary_to_integer("test")
Here’s the code:
defmodule My.Application do
use Application
def start(_type, _args) do
import Supervisor.Spec, warn: false
children = [
worker(My.GenServer, []),
supervisor(Task.Supervisor, [[name: My.Task.Supervisor, restart: :transient]]),
]
opts = [strategy: :one_for_one, name: Test.Supervisor]
Supervisor.start_link(children, opts)
end
end
defmodule My.GenServer do
def start_link do
GenServer.start_link(__MODULE__, :ok, name: __MODULE__)
end
def init(:ok) do
# Process.flag(:trap_exit, true)
{:ok, []}
end
def some_method(pid, input) do
GenServer.call(pid, {:some_method, input})
end
def handle_call({:some_method, input}, _from, state) do
# because we don't want to terminate GenServer use Task.async_nolink
task = Task.Supervisor.async_nolink(My.Task.Supervisor, fn ->
# raise argument error when passing binary
String.to_integer(input)
end)
{:reply, Task.await(task), state}
end
def handle_info({:EXIT, from, reason}, state) do
IO.inspect "handle_info::exit"
IO.inspect reason
{:noreply, state}
end
def handle_info({_ref, result}, state) do
IO.inspect "handle_info::result"
IO.inspect result
{:noreply, state}
end
def handle_info({:DOWN, _ref, :process, _pid, reason}, state) do
IO.inspect "handle_info::down"
IO.inspect reason
{:noreply, state}
end
def handle_info(msg, state) do
IO.inspect "handle_info"
IO.inspect msg
{:noreply, state}
end
end
I’ve read the docs from here regarding Task.Supervisor.async_link: if you create a task using async_nolink inside an OTP behaviour like GenServer, you should match on the message coming from the task inside your GenServer.handle_info/2 callback.
My problem is that handle_info is not called, I try to debug using observer attaching a trace to My.GenServer and I see that My.GenServer is receiving a :DOWN message:
Any solution to this problem ?
Thanks
Trending in Questions
Hello everyone!
I am new to coding with Elixir/Erlang. And i am looking for some utilities for fuzzing testing like AFL++.
Does anyone ...
New
I’m very new to Elixir, so sorry if this is a silly question:
I am wondering what happens to the mailbox of a process when the machine i...
New
How do I tell Hologram not to escape HTML when substituting into templates?
{Textile.render(@product.long_description)}
escapes the HTM...
New
I load tested a plain Phoenix chat app backed by Postgres with 100 million messages in it, everything on default settings, to see what br...
New
Background
When trying to execute mix release on a Windows 11 machine for a Phoenix project I get the following error:
* assembling mark...
New
I’d like to create a file with 600 permissions (rw-------), but there’s a race condition if I create it and then change the permissions. ...
New
Is there a way to import record definitions in the iex shell for pretty printing (similar to the rr command in the erl shell)? This woul...
New
Other Trending Topics
Edit: 2026 May 15 - This post is archived.
Mob is alive!!
Main docs: mob v0.7.11 — Documentation
A bit of explanation for the slightly c...
New
I fully migrated to my own harness from Anthropic/Gemini and I think it’s time to share it. Welcome DSH, the DeepSeek Harness, fully writ...
New
(I just needed to vent somewhere and LinkedIn is full of hope, or hype, I’m not sure which exactly)
AI dream has many faces, but general...
New
Localize is the next generation localisation library for Elixir. Think of it as ex_cldr version 3.0. The first version will be released ...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
ExRatatui lets you cook up rich terminal UIs in Elixir, powered by Rust’s ratatui via Rustler NIFs. Build interactive terminal applicatio...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #code-sync
- #discussion
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #ai
- #elixirconf-us
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #blog-post
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #elixirconf-eu
- #security
- #processes
- #api
- #forms
- #hex












Showing Posts 1 to 10- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
dom
You’re not getting a result because there is no result: the task failed. It never got a chance to reply. :DOWN is the right thing to handle in that case.
NobbZ
When using
Task.await/1it will handle the:DOWN-message from theTask. It will handle it by callingexit/1. So theGenServerwill be exited because of that.If you want to be more failsafe, you have to do the waiting for the result and the
:DOWN-message completely on your own.alexandrubagu
I don’t get a :DOWN message in
handle_info({:DOWN, _ref, :process, _pid, reason}, state)If I remove
Task.await(task)and replace{:reply, Task.await(task), state}with{:reply, :ok, state}I got that a :DOWN message but I need to wait for response from task.dom
Oh, I see what you mean. Instead of using await you can store the task’s ref and the caller in your GenServer state, then use GenServer.reply in your handle_info to send back the response to the caller.
NobbZ
As it is now you gain nothing from the
Taskexcept for the timeout, you could do the work in theGenServerdirectly and it wouldn’t matter (as long as no timout would happen in theTask)The more correct way were to put the returned task into your state, alongside the
fromand return a:noreturntuple inhandle_call/3.Some time later you will receive a message with either the result of the computation done in the Task, which you then can
GenServer(from, answer)to your caller.Or you might receive a
:DOWN, which you will need to find ways to tell your caller about. Most idiomatic way were to use an:error-tuple I think.alexandrubagu
Thanks a lot for your help @NobbZ and @dom , right now works.
NobbZ
This will break when your
GenServerwill be hit by multiple calls before the result of the spawned task is sent back!Each time you end up in your
handle_castyou are overwriting the receiver of the answer.Once you get an answer back, you will send it to the last one who asked for the info, letting all other processes starve. Also when subsequent answers from all the other tasks come in, you will send them into the mailbox of the same process (unless another one has asked in the meantime), spamming that processes mailbox with stuff that will probably never be read again.
Please make sure, that you map a task to a caller, and only send the answers/results back correspondingly.
alexandrubagu
Something like this ?
Thanks again, @NobbZ
NobbZ
Looks good on a first glance. I’d prefer to not call functions from inside the result tuple, but thats more of a personal and stylistic issue.
kaa.python
what’s the name of this application?
https://forum.elixirforum.com/uploads/default/original/2X/c/c695484a987ec6420117f28fa472ca5b9b9b6bf3.png