> gproc_pool:defined_workers(p2).
** exception error: bad argument
in function ets:lookup_element/3
called as ets:lookup_element(gproc,
{{c,l,{gproc_pool,p2,w,a}},<0.71.0>},
3)
in call from gproc:get_value1/2 (src/gproc.erl, line 1392)
in call from gproc:get_value/1 (src/gproc.erl, line 1365)
in call from gproc_pool:'-defined_workers/1-lc$^0/1-0-'/2 (src/gproc_pool.erl, line
I also noticed though that after the workers pass a few messages around, it does not crash. is some application or operation a pre-requisite before running defined_workers?
The docs say that defined_workers also gives stats about how often a worker is picked. Running pick > length of workers and then querying defined_workers/1 still gave me the error.
worker_pool/1 shows the said workers
but defined_workers does not.
I also noticed though that after the workers pass a few messages around, it does not crash. is some application or operation a pre-requisite before running defined_workers?
The docs say that defined_workers also gives stats about how often a worker is picked. Running pick > length of workers and then querying defined_workers/1 still gave me the error.