pathom

:pathom: https://github.com/wilkerlucio/pathom/ & https://pathom3.wsscode.com & https://roamresearch.com/#/app/wsscode
markaddleman 2021-02-05T16:07:07.175900Z

This code results in an internal guardrails exception in the latest Pathom3. I'm not sure if specifying a key path in ::pco/input is proper usage. In fact, if I trim the path in each of the resolvers to a single key (ie, :ui/query and :pql/query) , pathom is happy. Further, if I remove one of the resolvers, pathom is happy.

markaddleman 2021-02-06T15:40:34.179600Z

With guardrails disabled, Pathom3 has throws a stack overflow. This is the first many frames

markaddleman 2021-02-06T15:50:17.180Z

(sorry for the delayed reply - I got distracted yesterday)

markaddleman 2021-02-07T17:27:45.182200Z

Fantastic thanks!

wilkerlucio 2021-02-07T17:29:42.182400Z

the issue was a recursion in the nested thing, the edge of ui-query->time-range input was the same key as the output (`:query/timeRange`)

wilkerlucio 2021-02-07T17:29:55.182600Z

that drover the planner to do an infinite recursion, but fixed now

wilkerlucio 2021-02-07T17:30:24.182900Z

thanks for testing and bringing those cases to the light 🙂

wilkerlucio 2021-02-05T17:05:42.176200Z

from your description it seems a bug somewhere, what happens if you disable guardrails? the result is what you expect?

markaddleman 2021-02-05T17:07:12.176400Z

I haven't tried disabling guardrails - I'll give that a shot in an hour or so