Many subqueries using JQ fail with E2BIG
tokebe opened this issue · comments
After an update to Sentry tracking on Dev, it's become apparent that many JQ calls are failing with the error E2BIG.
This wasn't caught in initial testing likely because the size of queries used in testing were too small.
There may be a solution in arguments given to the node-jq package, otherwise, we'll have to disable JQ for all transformers until we can find a better solution.
Update: This is due to the APIEdge being inserted into the query string, which is occasionally large enough to go over the system arg limit. A fix is currently on Dev, PR will be made with the concurrency pass.
Relevant changes deployed to Prod.