Headless chrome indexer error audit results fixes#3445
Conversation
- waiting for linked fields to load only _after_ /render/html templates have been rendered - more efficient render options - improve error msg settling - all node indexing test for headless chrome passing
…or-isused-field-directive-to-include-linked
…oveChild' on 'Node': The node to be removed is not a child of this node." - scoped-css needs to respect the DOM tree that glimmer is managing when it moves the style tag around. otherwise this will blow up during re-renders in the /render route.
…s when links are being loaded still.
…en we try to render the serialized error
…lms with lots of render errors.
…ll-indexing-errors-that-we-see-when-starting-up
Host Test Results 1 files ± 0 1 suites ±0 3h 2m 23s ⏱️ + 1h 53m 5s For more details on these errors, see this check. Results for commit f4ee460. ± Comparison against base commit 7486399. This pull request removes 2 and adds 100 tests. Note that renamed tests count towards both.♻️ This comment has been updated with latest results. |
…mer scoped styles manipulating the DOM out from under glimmer)
|
@codex review |
|
Codex Review: Didn't find any major issues. Bravo. ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
| // that a node it was tracking is no longer there. performing a new prerender | ||
| // capture with a cleared store/loader cache will workaround this issue. | ||
| [`Failed to execute 'removeChild' on 'Node'`, 'NotFoundError'], | ||
| ]; |
There was a problem hiding this comment.
I’m surprised the style element is even present, I thought the AST transform would remove it from the component altogether
There was a problem hiding this comment.
agreed, I wonder if it’s the AST removing it that is what glimmer is mad about. i did confirm tho if I change the AST to leave the style tag in the card DOM it error goes away.
There was a problem hiding this comment.
Maybe there’s a way to have the transform happen earlier in the chain, before Glimmer has a hold on any elements at all. The way it runs on boxel-ui, for instance, is static. But I’m definitely out of my depth here.
…ll-indexing-errors-that-we-see-when-starting-up
This PR fixes indexing issues discovered during the headless chrome indexer error audit:
Most of the rest of the issues are actually related to downloading modules from external sites and CORS violations due to our own custom headers. I broke that out into a separate ticket that i'll followup with shortly https://linear.app/cardstack/issue/CS-9562/remove-the-need-to-use-x-boxel-building-index-header.
Beyond that there are a handful of other errors that we don't see in the current indexer that I'm still tracking down. One nice thing tho is that there are also a bunch of errors in our current indexer around rendering cycles that are actually solved in the headless chrome indexer.