fix null error handling

[xavdid]

Fixes https://github.com/zapier/zapier/issues/18163.

If a user calls Promise.reject(null) in a somewhere, it bubbles to here and causes a further error. This should fix it

I'm not sure how to test this - I would think that it's in integration-test, but adding a test that looks a lot like this didn't seem to trip like i thought it would. Any ideas would be appreciated!

[eliangcs]

Pulled and porked around a bit. I think we can't test it because here we're stopping the error from raising in the integration test runner. I tried testing on production but can't seem to do so. Did you test it on production? If so, what does your example app look like?

[xavdid]

Yeah! I'm using CLI app 2174. The one currently pushed has a modified core.

Here's the trigger that shows the error:

perform: async (z, bundle) => {
    await Promise.reject(null)
    return [{ a: 1 }]
}

To see it in action, we want to look at the console_logs in GL:

• before
• after

So yeah. not sure we can unit test it, but it's fixed!

[eliangcs]

Cool! I think we can take a pass on the unit test then!