RSSNext / RSSNext/Folo

Obsidian save error

Open
#2,797 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
TypeScript
Stars
39k
Forks
2.1k
Avg merge
1d 4h
Merged PRs (30d)
10

Description

Describe the bug

I tried to save the article to obsidian, but there was no response. The console reported an error:
index-QD-ao7WT.js:20 Uncaught (in promise) Error: Cannot handle unknown nodedelete``

This may not be a common problem, I can successfully save in other feeds

Image

Feed Info

https://sspai.com/post/96120
http://ftr.fivefilters.net/makefulltextfeed.php?url=https%3A%2F%2Fsspai.com%2Ffeed
114542188252742656

Reproduction Video

No response

Environment
Environment

App Version: 0.3.5
OS: Windows
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Follow/0.3.5 Chrome/130.0.6723.118 Electron/33.2.0 Safari/537.36
Env: electron
Browser: Chrome
Session Trace Id: GPQoR9rSymE3MgdVW3zux
Renderer: 0.3.5

Validations
  • Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
  • Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
  • This issue is valid
Contributions
  • I am willing to submit a PR to fix this issue
  • I am willing to submit a PR with failing tests (actually just go ahead and do it, thanks!)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The report names no source files, tests, or entry points; start by locating the Obsidian save flow and the handling for the reported unknown node delete error. Reproduce with the linked feed in the stated Electron environment, and consider the issue resolved when saving that article to Obsidian completes without the console error.

Written by the indexing model from the issue text.

Assessment

Tech stack
electron, typescript
Domain
desktop
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.