v3.0 🚀 by lucasdoell · Pull Request #77 · luxdotdev/parsertime

lucasdoell · 2026-06-16T18:23:46Z

No description provided.

…) stat and per-map inspector

…ne models

Add transaction timeouts (60s) to the three $transaction calls in recomputeAllFsr to handle large datasets (~10k cells). Add prisma.$disconnect() to the bootstrap script so the connection pool drains cleanly on exit.

…w upserts

…ditor

OpenCV's ~98MB native bundle exceeds the Vercel Python function size limit, so alignment now runs as a local CLI (scripts/map-align) that prints the pixel transform JSON to paste into the admin Replace-render dialog. Removes the serverless function and its vercel.json entry; align.py/tests are unchanged.

Loops reference/final image dirs, aligns each pair (reusing decode_bounded + align_images + rescale_transform), writes transforms.json keyed by map plus an edge-overlay QA image per map, and prints a summary table flagging low-confidence and failed alignments. Adds the edge_overlay helper and tests.

The review stacked a 500px-min canvas and a full-width aspect-ratio compare box with no bound on the dialog, overflowing the screen with no scroll. Cap the dialog at 90vh with overflow-y-auto, cap the canvas at 45vh (overriding the shared MapCanvas min-height), and give the compare box a fixed 40vh height.

The canvas only draws the image and never reads its pixels back, so crossOrigin=anonymous served no purpose but made the load fail whenever the R2 response lacked CORS headers (the image hung on 'Loading…' while the plain compare <img> with no crossOrigin loaded the same URL fine). Also reset the loading state on src change and log load failures instead of hanging silently.

min-w-0 on the grid children lets the dialog shrink instead of being forced wider than its box by the canvas's intrinsic width (the horizontal scrollbar / clipped text). The script hint rendered its raw i18n key because the string held <old-image>/<new-render>, which next-intl's ICU parser reads as malformed tags; switched to square brackets.

vercel · 2026-06-16T18:23:53Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
parsertime	Ready	Preview, ✅ 2 resolved	Jun 16, 2026 6:29pm

lucasdoell · 2026-06-16T18:24:30Z

📝 Changed routes:

/auth-error	/sign-in
^{(view full size)}	^{(view full size)}

/verify-request	/[team]/compare
^{(view full size)}	^{(view full size)}

/[team]/map-groups	/[team]/ops
^{(view full size)}	^{(view full size)}

And 32 other routes:

Commit 3f76b1b (https://parsertime-47u85y69d-luxdotdev.vercel.app).

socket-security · 2026-06-16T18:25:14Z

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/next@16.2.6
	pypi/numpy@1.26.4
	pypi/numpy@2.4.6
	pypi/opencv-python-headless@4.11.0.86
	npm/@types/pg@8.20.0
	npm/prisma@7.8.0
	pypi/pandas@2.3.3
	pypi/pandas@3.0.3
	npm/deepsec@2.0.10
	npm/@prisma/adapter-pg@7.8.0
	npm/cheerio@1.2.0
	npm/@prisma/client@7.8.0
	pypi/pytest@9.1.0
	npm/dotenv@17.4.2
	npm/pg@8.21.0
	pypi/pytest@8.4.2
	pypi/scikit-learn@1.9.0
	pypi/lightgbm@4.6.0
	pypi/requests@2.34.2

View full report

socket-security · 2026-06-16T18:25:16Z

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert (click "▶" to expand/collapse)
Warn		Obfuscated code: npm `@electric-sql/pglite` is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → `npm/prisma@7.8.0` → `npm/@electric-sql/pglite@0.4.1` ℹ Read more on: This package \| This alert \| What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/@electric-sql/pglite@0.4.1`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm `@prisma/client` is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package.json → `npm/@prisma/client@7.8.0` ℹ Read more on: This package \| This alert \| What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/@prisma/client@7.8.0`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm `cheerio` is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package.json → `npm/cheerio@1.2.0` ℹ Read more on: This package \| This alert \| What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/cheerio@1.2.0`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm `effect` is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → `npm/prisma@7.8.0` → `npm/effect@3.20.0` ℹ Read more on: This package \| This alert \| What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/effect@3.20.0`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm `htmlparser2` is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → `npm/cheerio@1.2.0` → `npm/htmlparser2@10.1.0` ℹ Read more on: This package \| This alert \| What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/htmlparser2@10.1.0`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm `next` is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package.json → `npm/next@16.2.6` ℹ Read more on: This package \| This alert \| What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/next@16.2.6`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: pypi `numpy` is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: scripts/wp/gbm-prototype/pyproject.toml → `pypi/numpy@2.4.6` ℹ Read more on: This package \| This alert \| What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at `support@socket.dev`. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore pypi/numpy@2.4.6`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

lucasdoell added 30 commits June 13, 2026 01:51

Add map-level fight-initiation assembler and summary

1343068

Add Prisma entry point for map fight initiation

89b68c5

Clarify fight-initiation window intent and tidy tests

7728000

Add fight initiation translation keys

339d39f

Add fight initiation inspector component

32f622f

Remove dead description key and fix undetermined-fight headline

3b4061a

Add Going First tab to the map page

b819b55

Guard map fight-initiation load and rename tab to Initiation

0b40e55

Show response gap and ability-commit evidence in initiation inspector

df9d63c

Overlay objective captures on the initiation timeline

6188252

Replace capture overlay with toggleable round markers

c0d99ee

Collapse round markers into single transitions and fix list keys

01ffecc

Merge fight-initiation-going-first: add fight initiation (Going First…

9e911cd

…) stat and per-map inspector

Add FSR schema: FaceitRole enum and PlayerFsr/PlayerFsrTier/FsrBaseli…

063ac05

…ne models

Add FSR shared types

854eee6

Add FSR constants with tier weights and shrinkage defaults

f899532

Add FSR per-role stat configs

1fa9dd4

Add FSR formula functions for z-scores, composites, and headline blend

eb4a8c7

Add FSR (tier x role) baseline computation

551bf37

Add FSR SQL aggregate loader for per-tier player groups

8d04e4a

Add FSR recompute orchestration with advisory lock and stale-row cleanup

70ffcbd

Add read-only FSR dry-run script for validation and weight tuning

7db0ce5

Add FSR bootstrap script and wire recompute into the daily cron

24b5aab

Add transaction timeouts (60s) to the three $transaction calls in recomputeAllFsr to handle large datasets (~10k cells). Add prisma.$disconnect() to the bootstrap script so the connection pool drains cleanly on exit.

Use bulk createMany in a transaction for FSR writes instead of per-ro…

9c11c8b

…w upserts

Move FSR recompute to its own daily cron at 06:30 UTC

c475da0

Add FACEIT team scouting types and query error

ab6432d

Add pure aggregations for FACEIT team scouting

af2ae5c

Add FACEIT team scouting metrics

1716f3a

Add FACEIT team scouting Effect service and register its layer

a2e3111

Add read-only FACEIT team scouting dry-run script

95940d2

lucasdoell added 20 commits June 16, 2026 03:32

Harden apply route: exact staged-key check, id guard, recovery docs

cba343c

Add revert route to restore the last render swap

e4d30d6

Log underlying error when revert finds no backup

fcaa6f7

Add replace-render dialog with anchor-overlay review to calibration e…

bd1415f

…ditor

Fix stale-closure discard and polish replace-render file input

ccb01c1

Add blink and swipe old-vs-new compare to render re-alignment review

dafd249

Bound alignment to a working resolution to handle high-res renders

e3db9b2

Document non-PNG full-decode boundary in decode_bounded

bce2df8

Reduce align route to staging only; transform now comes from local CLI

364d6ab

Switch replace-render dialog to paste the local alignment transform

557e9f2

Reset compare-panel state when the replace-render dialog closes

f10df88

Reformat

3fac335

Add gitignore for map alignment script

6b150a5

Fix translation key for matchmaker

86ad809

Add support for Shion

6711686

vercel Bot deployed to Preview June 16, 2026 18:24 View deployment

github-advanced-security AI found potential problems Jun 16, 2026

View reviewed changes

Comment thread src/app/api/cron/wp-retrain/route.ts Fixed

Hard-code origin route

3f76b1b

vercel Bot deployed to Preview June 16, 2026 18:29 View deployment

lucasdoell merged commit cd586dc into main Jun 16, 2026
14 checks passed

lucasdoell deleted the staging branch June 16, 2026 18:33

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

v3.0 🚀 - #77

v3.0 🚀#77
lucasdoell merged 1130 commits into
mainfrom
staging

lucasdoell commented Jun 16, 2026

Uh oh!

vercel Bot commented Jun 16, 2026 •

edited

Loading

Uh oh!

lucasdoell commented Jun 16, 2026 •

edited

Loading

Uh oh!

Uh oh!

socket-security Bot commented Jun 16, 2026 •

edited

Loading

Uh oh!

socket-security Bot commented Jun 16, 2026 •

edited

Loading

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

lucasdoell commented Jun 16, 2026

Uh oh!

vercel Bot commented Jun 16, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

lucasdoell commented Jun 16, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

📝 Changed routes:

Uh oh!

Uh oh!

socket-security Bot commented Jun 16, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

socket-security Bot commented Jun 16, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

vercel Bot commented Jun 16, 2026 •

edited

Loading

lucasdoell commented Jun 16, 2026 •

edited

Loading

socket-security Bot commented Jun 16, 2026 •

edited

Loading

socket-security Bot commented Jun 16, 2026 •

edited

Loading