You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We had a similar problem with otter some days ago. :ets.lookup/2 fails with an ArgumentError when the ETS tables does not exist. You may need to start prometheus_ecto.
We had a similar problem with otter some days ago. :ets.lookup/2 fails with an ArgumentError when the ETS tables does not exist. You may need to start prometheus_ecto.
I am pretty new to ETS, but I suspect that the prometheus tables do exist prior to the migration.
For example, when I invoke :ets.all/0, I see :prometheus_histogram_table in the results. Also, if I start Observer from an iex -S mix session and select the Table Viewer I see a number of prometheus tables in the list:
Using
prometheus_ecto
version 1.3.0, I observe the following stack trace:The
Core.RepoInstrumenter
module refers to my instrumenter (MyApp.Repo.Instrumenter
in the README).The migration starts by dropping all the rows in a table using
Ecto.Repo.delete_all/1
. Something like:I can work-around the error by using
Ecto.Migration.drop/1
andEcto.Migration.create/1
in place ofdelete_all/1
:The text was updated successfully, but these errors were encountered: