pathom

:pathom: https://github.com/wilkerlucio/pathom/ & https://pathom3.wsscode.com & https://roamresearch.com/#/app/wsscode
wilkerlucio 2021-05-28T13:34:16.021200Z

hello people, I've made a few changes to Pathom 3 error handling and add a documentation page about it in the docs, feedback welcome as always 🙏  https://pathom3.wsscode.com/docs/error-handling

👍 2
2021-05-31T20:04:32.029100Z

You don’t seem to mention in the docs what happens if multiple mutations are run and there’s an error in one — whether it continues executing the remaining mutations or stops. Just might be worth mentioning for newcomers who might expect one behaviour or the other?

wilkerlucio 2021-05-28T14:27:55.022200Z

Also extended docs around resolver prioritization https://pathom3.wsscode.com/docs/resolvers/#prioritization to cover edge cases and point out this still experimental

henrik 2021-05-28T17:57:43.023800Z

Btw, @wilkerlucio, I managed to blow my heap by making a big query the other day. Just an FYI, I've broken it up into smaller queries.

wilkerlucio 2021-05-28T17:58:42.023900Z

do you know if exploded during plan or run?

henrik 2021-05-28T17:59:38.024100Z

I think it was during run. If it's interesting, I could check out the old code and try to figure out which it is.

wilkerlucio 2021-05-28T18:00:42.024400Z

I'm interested, the goal is to support arbitrarily large queries, good to know where the current implementation is topping

wilkerlucio 2021-05-28T18:01:31.024600Z

your guess would be because of query size, data size (large number of entities) or both?

wilkerlucio 2021-05-28T18:03:29.024800Z

also curious about the available resources on the machine, does increasing the max size is an option for you to fix?

wilkerlucio 2021-05-28T20:05:27.025400Z

sorry the question storm, but one other thing to check, are you running with guardrails enabled?