Skip to content
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

Merged

Conversation

habdelra
Copy link
Contributor

No description provided.

@habdelra habdelra changed the title Cs-6719-remove-feature-flag-pg-indexer-and-cleanup-obsolete-code Remove PG_INDEXER feature flag and drop obsolete code May 10, 2024
Copy link

github-actions bot commented May 10, 2024

Host Tests (In-Memory Index) Test Results

    1 files  ±0      1 suites  ±0   14m 22s ⏱️ + 3m 11s
611 tests ±0  603 ✔️  - 2  5 💤  - 1  0 ±0  3 🔥 +3 
611 runs  ±0  600 ✔️  - 5  5 💤  - 1  3 +3  3 🔥 +3 

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.
Chrome 124.0 ‑ Acceptance | operator mode tests: can open code submode when card or field has no embedded template
Chrome 124.0 ‑ Integration | search-index > query: can filter on an array of primitive fields inside a containsMany using 'eq'
Chrome 124.0 ‑ Integration | search-index > query: can sort on multiple paths in combination with 'any' filter

♻️ This comment has been updated with latest results.

@habdelra habdelra marked this pull request as ready for review May 10, 2024 19:28
Comment on lines -886 to -894
// 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;
}
Copy link
Contributor Author

@habdelra habdelra May 10, 2024

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

Comment on lines +1088 to +1093
`${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.`;
Copy link
Contributor Author

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 😆

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

seems helpful!

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🥇

Copy link
Contributor

@backspace backspace left a 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!

packages/realm-server/main.ts Outdated Show resolved Hide resolved
Comment on lines +1088 to +1093
`${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.`;
Copy link
Contributor

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.
Copy link
Contributor

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?

Copy link
Contributor Author

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

@backspace
Copy link
Contributor

hmm actually I approved before I saw these host test failures.

@habdelra
Copy link
Contributor Author

hmm actually I approved before I saw these host test failures.

No prob, that’s my Monday work

Copy link
Contributor

@jurgenwerk jurgenwerk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎉

habdelra and others added 4 commits May 14, 2024 10:02
Co-authored-by: Buck Doyle <[email protected]>
…lete-code' of https://github.com/cardstack/boxel into cs-6719-remove-feature-flag-pg-indexer-and-cleanup-obsolete-code
Copy link

github-actions bot commented May 14, 2024

Host Tests Test Results

611 tests   601 ✔️  13m 54s ⏱️
    1 suites    10 💤
    1 files        0

Results for commit f46e53b.

♻️ This comment has been updated with latest results.

@habdelra habdelra merged commit 1b380dc into main May 15, 2024
35 checks passed
@delete-merged-branch delete-merged-branch bot deleted the cs-6719-remove-feature-flag-pg-indexer-and-cleanup-obsolete-code branch May 15, 2024 01:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants