New file error: 'Sibling page failed to parse'
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 255
- Forks
- 17
- Avg merge
- 6h 20m
- Merged PRs (30d)
- 109
Description
I have a project, where one of the files contains an error.
Then I create a new .qmd file, the following error immediately shows up:
Sibling page '/project/index.qmd' failed to parse
⚠ /project/index.qmd failed to parse
Line 126: Parse error - unexpected character or token here
Line 126: Parse error - unexpected character or token here
Other existing files in the project do not show this error, even as I modify them.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the report by opening the project with /project/index.qmd containing the error, then creating a new .qmd file. Start by inspecting /project/index.qmd at line 126 and compare the new-file behavior with modifying existing files. Done means the sibling-page parse error is reported consistently or the triggering behavior is corrected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100