Closed mihow closed 4 months ago
Name | Link |
---|---|
Latest commit | 49d8862415487c46b8c25f8b47af170a1db68d71 |
Latest deploy log | https://app.netlify.com/sites/ami-web/deploys/65d433091172bb00083b023f |
Deploy Preview | https://deploy-preview-358--ami-web.netlify.app/ |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
Lighthouse |
1 paths audited Performance: 74 Accessibility: 95 Best Practices: 92 SEO: 92 PWA: 70 View the detailed breakdown and full score reports |
To edit notification comments on pull requests, go to your Netlify site configuration.
Name | Link |
---|---|
Latest commit | 49d8862415487c46b8c25f8b47af170a1db68d71 |
Latest deploy log | https://app.netlify.com/sites/ami-storybook/deploys/65d43309db35820008de9953 |
Deploy Preview | https://deploy-preview-358--ami-storybook.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
Jobs continue to fail randomly when they are first started because the task gets a DoesNotExist error when looking up the job ID (which certainly does exist). This fixes a couple potential causes, as well as adds some tests, which uncovered more issues like allowed unauthenticated requests. Which it fixes as well.
Here is the primary DoesNotExist / IntegrityError I hope this PR fixes in production: https://amii.sentry.io/share/issue/512c752a224641a8b046a82c1d0fd9c5/