Improved error handline, fixes #5

This commit is contained in:
Alicia Sykes 2023-07-22 00:19:13 +01:00
parent f9437ea964
commit b2204728ea
3 changed files with 3 additions and 10 deletions

View File

@ -31,8 +31,8 @@ exports.handler = async (event, context, callback) => {
browser = await puppeteer.launch({
args: chromium.args,
defaultViewport: { width: 800, height: 600 },
executablePath: '/usr/bin/chromium',
// executablePath: await chromium.executablePath(),
// executablePath: '/usr/bin/chromium',
executablePath: await chromium.executablePath(),
headless: chromium.headless,
ignoreHTTPSErrors: true,
});

View File

@ -52,7 +52,7 @@ const useMotherOfAllHooks = <ResultType = any>(params: UseIpAddressProps<ResultT
})
.catch((err) => {
// Something fucked up, log the error
updateLoadingJobs(jobId, 'error', err.message, reset);
updateLoadingJobs(jobId, 'error', err.error || err.message, reset);
throw err;
})
}

View File

@ -154,18 +154,11 @@ const Results = (): JSX.Element => {
const parseJson = (response: Response): Promise<any> => {
return new Promise((resolve) => {
if (response.ok) {
response.json()
.then(data => resolve(data))
.catch(error => resolve(
{ error: `Failed to process response, likely due to Netlify's 10-sec limit on lambda functions. Error: ${error}`}
));
} else {
resolve(
{ error: `Response returned with status: ${response.status} ${response.statusText}.`
+ `This is likely due to an incompatibility with the lambda function.` }
);
}
});
};