-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove PG_INDEXER feature flag and drop obsolete code #1244
Remove PG_INDEXER feature flag and drop obsolete code #1244
Conversation
Host Tests (In-Memory Index) Test Results 1 files ±0 1 suites ±0 14m 22s ⏱️ + 3m 11s For more details on these errors, see this check. Results for commit cdb8083. ± Comparison against base commit 0821c54. This pull request skips 1 and un-skips 2 tests.
♻️ This comment has been updated with latest results. |
…e-flag-pg-indexer-and-cleanup-obsolete-code
// allow any WIP index requests to query the index while it's building up | ||
if (!request.headers.get('X-Boxel-Use-WIP-Index')) { | ||
await this.ready; | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
turns out I was using the loader wrong. the realm's loader has the internal fetch URL handler. once I started passing a clone of that to the worker then this condition became unnecessary
`${message}. created a new generation while there was still unfinished indexing. ` + | ||
`The most likely reason this happens is that there was an error encountered during incremental ` + | ||
`indexing that prevented the indexing from completing (and realm version increasing), ` + | ||
`then the realm was restarted and the left over WIP indexing artifact(s) collided with the ` + | ||
`from-scratch indexing. To resolve this issue delete the WIP indexing artifacts (the row(s) ` + | ||
`that triggered the unique constraint) and restart the realm.`; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
trying to win the oscar for best error message 😆
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
seems helpful!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🥇
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
seems like a smooth transition!
`${message}. created a new generation while there was still unfinished indexing. ` + | ||
`The most likely reason this happens is that there was an error encountered during incremental ` + | ||
`indexing that prevented the indexing from completing (and realm version increasing), ` + | ||
`then the realm was restarted and the left over WIP indexing artifact(s) collided with the ` + | ||
`from-scratch indexing. To resolve this issue delete the WIP indexing artifacts (the row(s) ` + | ||
`that triggered the unique constraint) and restart the realm.`; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
seems helpful!
@@ -937,6 +829,9 @@ export class Realm { | |||
return undefined; | |||
} | |||
|
|||
// TODO we could really improve performance if this utilized the index instead | |||
// of directly hitting the filesystem--especially the TS transpilation | |||
// involved in making JS. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this a full project or could an issue be opened for it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it’s probably a project
hmm actually I approved before I saw these |
No prob, that’s my Monday work |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎉
Co-authored-by: Buck Doyle <[email protected]>
…e-flag-pg-indexer-and-cleanup-obsolete-code
…lete-code' of https://github.com/cardstack/boxel into cs-6719-remove-feature-flag-pg-indexer-and-cleanup-obsolete-code
No description provided.