osmirbresciani
I’m developing process automation using oban, but lately I’m facing a problem with updating the code in worker modules.
Whenever I update the module for the worker and start the application, the worker keeps processing jobs as if the code hasn’t been updated. In the worker module, even if I comment out everything that is in the perform(_job) function, the oban continues processing the code that was there. It’s like there’s some kind of cache.
ie.:
this job successfully run:
@impl Oban.Worker
def perform(_job) do
Users.list_users_from_last_day()
|> Emails.digest_email()
|> Mailer.deliver_now()
if I changes to:
@impl Oban.Worker
def perform(_job) do
IO.inspect("Nothing to do")
the previous job before the change continues to run successfully. Or if I change the tags for testing, they don’t change in db.
Another common error I’m experiencing is the “unknown worker”- oban error, when I change the worker set in config.exs.
I’ve already tried:
- clear cache files →
sudo rm -rf ./_build ./.elixir_ls ./mix.lock ~/.hex/cache.ets - recompile the app from scratch
Running through IEX or running the automated tests, everything works. The problem only occurs in homolog environment
Could anyone give a help on how to debug this problem?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest Oban Threads
Latest on Elixir Forum
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
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #ai
- #phoenix_html
- #iex
- #elixirconf-us
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming










Showing Posts 1 to 10- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
sorentwo
It seems like you’re experiencing a combination of multiple versions of a module in memory, and lingering data in the database. Is it possible you have another app instance running somewhere?
osmirbresciani
There are no instances running in the background. Running via docker or locally without the docker, is the same problem. The only thing that works is updating the crontab. Do you have any test suggestions I can do to check if it’s something in the app’s startup config?
Ty!
sorentwo
There isn’t anything in the config or worker definitions that would prevent code reloading. As far as Oban knows, the worker is a string that represents a module name. When the job executes it looks up the module name and executes the job—the module definition isn’t stored in the database.
lud
Can you call the
perform/1function directly from a test to ensure that it works as intended?osmirbresciani
Yes, it works. The “bug” appears when running
mix phx.serverwithMIX_ENV=devgabriel137
Lately I’ve had an error with it a bit similar, after many executions of jobs it stops showing any debug messages for me, but the work runs normally, this in my dev environment, in production it doesn’t happen.
sorentwo
This sounds like the telemetry handler for logging gets detached in development. There will be a warning in your logs stating that the handler encountered an error if that’s the case.
lud
That’s strange.
As a workaround you can always delete the
_builddirectory (or just_build/dev/lib/myapp).Also you can call
:code.which(MyWorker)to retrieve the beam file for your module so you could check the modification time of this file, or load it in an iex session to check stuff.egze
Curious to find out more what you’re building. We are also starting a process automation project soon. Would appreciate if you drop me a message.
osmirbresciani
updating:
Running oban tests using iex in dev:
Everything worked as it should. The module is recognized. I also run the app in production with oban workers and it worked!! The error only continues running locally in dev environment:
iex -S mix phx.serverandmix phx.serverwhere the code doesn’t update and I get the error:unknown workerfrom oban.I believe it’s a problem in the compilation of my code because when I start the app, I sometimes get the error:
** (File.Error) could not write to file "/home/desktop/projects/api/_build/dev/lib/api/ebin/my-worker-file.beam": permission denied, but running withreleasein prod works. Thanks for the help, I’ll search for the cause of this compilation issue.