catra
ArgumentError :ets.lookup in Absinthe Middleware using FunWithFlags
I’m trying to use FunWithFlags.enabled? (ref fwf) inside an absinthe middleware but I got the following error:
(ArgumentError) argument error
(stdlib) :ets.lookup(:fun_with_flags_cache, :some_flag)
Stacktrace:
│ lib/fun_with_flags/store/cache.ex:35: FunWithFlags.Store.Cache.get/1
│ lib/fun_with_flags/store.ex:12: FunWithFlags.Store.lookup/1
│ lib/fun_with_flags.ex:77: FunWithFlags.enabled?/2
I haven’t tried too much. I just narrowed down where the issue is happening. I’m guessing that the middleware compiles before the :some_flag record (or maybe the :fun_with_flags_cache table) is created and then failed because there is no record/table.
This link says:
It stores flag information in Redis or a relational DB (PostgreSQL or MySQL, with Ecto) for persistence and synchronization across different nodes, but it also maintains a local cache in an ETS table for fast lookups. When flags are added or toggled on a node, the other nodes are notified via PubSub and reload their local ETS caches
So I’m guessing one option could be disable the ETS with the following config:
config :fun_with_flags, :cache,
enabled: false,
ttl: 900
But we lost all of the benefits of the cache.
Anyway, Any thought are welcome. Thanks in advance.
Thanks! 
Note: It doesn’t work adding the config. 
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Error tracking, logs, APM, uptime and cron monitoring in one dev-friendly platform. Find and fix problems before your users notice.
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
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #performance
- #security
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Practical resources that improve the lives of professional developers.
Enabling companies to succeed by building software people love.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
First Post!
benwilson512
Can you show how you are using it?
Most Liked
benwilson512
Gotcha.
Yeah the issue here is that this function is actually run at compile time. This means that your ets tables are likely not loaded. Using the persistent_term schema backend would probably help (in that it will refresh the value at runtime), but I think this still runs at compile time to do a check.
Last Post!
catra
Hey @benwilson512 Thanks for reply. We ended using an env variable in the middle function and inside the middleware module we were able to use FeatureFlags. BTW, I’m enjoying reading you book, thank you for writing it. Such a gem for GraphQL API crafters.