@sreetej510/pi-shipd-checks 0.9.4 → 0.9.6
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +2 -1
- package/dist/fargate-worker.mjs +47 -47
- package/dist/index.js +54 -54
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -38,7 +38,8 @@ current checks, starts Test Quality before Solution Quality in one browser tab,
|
|
|
38
38
|
`"Not fair"`, and the complete `details.solutionQuality.evaluation` block. Its compact UI is labeled `Quality Checks`,
|
|
39
39
|
shows live elapsed time, and only displays unfair-test count, suggestion count, code-quality score, and
|
|
40
40
|
comprehensiveness score. It takes no parameters. It uses one fresh headless browser tab at a time: it closes the
|
|
41
|
-
browser after starting the needed jobs, checks after 5 minutes, then reopens every 90 seconds until those jobs finish
|
|
41
|
+
browser after starting the needed jobs, checks after 5 minutes, then reopens every 90 seconds until those jobs finish, with no
|
|
42
|
+
client-side overall timeout. If
|
|
42
43
|
all checks are current, it uses existing reports without starting a job. Each
|
|
43
44
|
browser context blocks images, fonts, and media to reduce memory use. It does not click the final orange
|
|
44
45
|
challenge-submit button. Authentication comes from `SHIPD_STORAGE_STATE` or the saved state created by
|