not known, but I guess it may happen as part of a change I did recently, are you on the latest?

but could also be a legit detection, can you tell me more about this case?

Okay. I will try to reproduce a small case]

(let [register [(pc/resolver `foo
                             {::pc/output [::foo]}
                             (fn [env _]
                               (s/explain (s/keys) env)
                               {::foo 33}))]
      plugins [(pc/connect-plugin {::pc/register register})]
      parser (p/parallel-parser {::p/plugins plugins})]
  (async/<!! (parser {::p/reader [p/map-reader pc/parallel-reader]}
                     [::foo])))

In "real world" it occours when my-function is instrumented

(fn [env _]
  {::foo (http/my-function env ..)}

that seems a bug in the specs, let me debug that here, should be simple to fix

yeah, I think I get it, the problem I'm using ::pc/plan improperly... the ::pc/plan is supposed to be a collection of paths to follow, in this case I'm using ::pc/plan as a single path (instead of a collection)

I'll see if its easy to replace the usage to ::pc/plan-path, which is the correct name for it

I started to run things instrumented only recently, thanks for pointing the bad spec

@U2J4FRT2T fixed: https://github.com/wilkerlucio/pathom/pull/99/files

please let me know if you find any other issues with [2.2.17]

already running 2.2.17 in homolog env 😅 also removed some random (dissoc ::pc/plan) from code