fix(client): remove destructive pb_migrations that drop core collections - #226
Merged
Merged
Conversation
pocketbase/pb_migrations/ contained 26 auto-generated deleted_* migrations (a leftover from a local schema diff during the Clerk/PocketBase cutover) that each delete a core collection (anomalies, classifications, profiles, etc). docker-compose never mounted this directory, but the newly-live Cloudflare/Fly production path isn't docker-compose based, and its PocketBase deploy isn't managed in this repo -- if it picks up pb_migrations/, applying these on startup would wipe the live schema, matching the prod "blank screen for logged-in users" incident (active-planet 500s: "Missing or invalid collection context"). Delete the destructive files and document the incident/recovery steps in pocketbase/README.md.
Gizmotronn
commented
Jul 26, 2026
Gizmotronn
left a comment
Gizmotronn
left a comment
Member
Author
There was a problem hiding this comment.
Hopefully this sorts out:
contentscript.js:14083 MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 close listeners added. Use emitter.setMaxListeners() to increase limit
n @ contentscript.js:14083
u @ contentscript.js:14083
a.addListener @ contentscript.js:14083
Z.on @ contentscript.js:14082
a.once @ contentscript.js:14083
j.pipe @ contentscript.js:14063
q @ contentscript.js:14063
D @ contentscript.js:14063
P @ contentscript.js:14063
M @ contentscript.js:14063
I @ contentscript.js:14063
(anonymous) @ contentscript.js:14083
call.__webpack_require__._LM_.__webpack_require__.__webpack_require__ @ contentscript.js:14083
(anonymous) @ contentscript.js:14083
(anonymous) @ contentscript.js:14083
contentscript.js:14083 MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 end listeners added. Use emitter.setMaxListeners() to increase limit
n @ contentscript.js:14083
u @ contentscript.js:14083
a.addListener @ contentscript.js:14083
Z.on @ contentscript.js:14082
O @ contentscript.js:14083
q @ contentscript.js:14063
D @ contentscript.js:14063
P @ contentscript.js:14063
M @ contentscript.js:14063
I @ contentscript.js:14063
(anonymous) @ contentscript.js:14083
call.__webpack_require__._LM_.__webpack_require__.__webpack_require__ @ contentscript.js:14083
(anonymous) @ contentscript.js:14083
(anonymous) @ contentscript.js:14083
contentscript.js:14083 ObjectMultiplex - orphaned data for stream "app-init-liveness"
warn @ contentscript.js:14083
_write @ contentscript.js:14082
M @ contentscript.js:14063
x @ contentscript.js:14063
E.write @ contentscript.js:14063
d @ contentscript.js:14082
a.emit @ contentscript.js:14083
J @ contentscript.js:14082
K @ contentscript.js:14082
Z.push @ contentscript.js:14082
(anonymous) @ contentscript.js:14063
contentscript.js:14083 ObjectMultiplex - orphaned data for stream "app-init-liveness"
warn @ contentscript.js:14083
_write @ contentscript.js:14082
M @ contentscript.js:14063
x @ contentscript.js:14063
E.write @ contentscript.js:14063
d @ contentscript.js:14082
a.emit @ contentscript.js:14083
J @ contentscript.js:14082
K @ contentscript.js:14082
Z.push @ contentscript.js:14082
(anonymous) @ contentscript.js:14082
transform @ contentscript.js:14063
s._write @ contentscript.js:14082
I @ contentscript.js:14083
L @ contentscript.js:14083
O.write @ contentscript.js:14083
d @ contentscript.js:14082
a.emit @ contentscript.js:14083
J @ contentscript.js:14082
K @ contentscript.js:14082
Z.push @ contentscript.js:14082
(anonymous) @ contentscript.js:14063
contentscript.js:14083 ObjectMultiplex - orphaned data for stream "background-liveness"
warn @ contentscript.js:14083
_write @ contentscript.js:14082
M @ contentscript.js:14063
x @ contentscript.js:14063
E.write @ contentscript.js:14063
d @ contentscript.js:14082
a.emit @ contentscript.js:14083
J @ contentscript.js:14082
K @ contentscript.js:14082
Z.push @ contentscript.js:14082
(anonymous) @ contentscript.js:14063
contentscript.js:14083 ObjectMultiplex - orphaned data for stream "background-liveness"
warn @ contentscript.js:14083
_write @ contentscript.js:14082
M @ contentscript.js:14063
x @ contentscript.js:14063
E.write @ contentscript.js:14063
d @ contentscript.js:14082
a.emit @ contentscript.js:14083
J @ contentscript.js:14082
K @ contentscript.js:14082
Z.push @ contentscript.js:14082
(anonymous) @ contentscript.js:14082
transform @ contentscript.js:14063
s._write @ contentscript.js:14082
I @ contentscript.js:14083
L @ contentscript.js:14083
O.write @ contentscript.js:14083
d @ contentscript.js:14082
a.emit @ contentscript.js:14083
J @ contentscript.js:14082
K @ contentscript.js:14082
Z.push @ contentscript.js:14082
(anonymous) @ contentscript.js:14063
content.js:2 Check phishing by URL: Passed.
_vercel/insights/script.js:1 Failed to load resource: net::ERR_BLOCKED_BY_CONTENT_BLOCKER
3569-f2180c29c19a6255.js:9 [Vercel Web Analytics] Failed to load script from /_vercel/insights/script.js. Be sure to enable Web Analytics for your project and deploy again. See https://vercel.com/docs/analytics/quickstart for more information.
_vercel/speed-insights/script.js:1 Failed to load resource: net::ERR_BLOCKED_BY_CONTENT_BLOCKER
3569-f2180c29c19a6255.js:9 [Vercel Speed Insights] Failed to load script from /_vercel/speed-insights/script.js. Please check if any content blockers are enabled and try again.
6293-ed8143f5259ef93c.js:1 Warning: Missing `Description` or `aria-describedby={undefined}` for {DialogContent}.
(anonymous) @ 6293-ed8143f5259ef93c.js:1
game:1 Failed to load resource: the server responded with a status of 408 ()
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
pocketbase/pb_migrations/ contained 26 auto-generated deleted_* migrations (a leftover from a local schema diff during the Clerk/PocketBase cutover) that each delete a core collection (anomalies, classifications, profiles, etc). docker-compose never mounted this directory, but the newly-live Cloudflare/Fly production path isn't docker-compose based, and its PocketBase deploy isn't managed in this repo -- if it picks up pb_migrations/, applying these on startup would wipe the live schema, matching the prod "blank screen for logged-in users" incident (active-planet 500s: "Missing or invalid collection context").
Delete the destructive files and document the incident/recovery steps in pocketbase/README.md.