logseq / logseq/db-test

Table Deleted During Import ("Ignored ast node")

Open
#1,048 0 comments 0 reactions 1 assignee View on GitHub

@megayu is already working on this.

Since Aug 10, 2026.

Dominant language
No language data
Stars
28
Forks
2
PR merge metrics
No merged PRs in 30d

Description

### Search first

- [x] I searched and no similar issues were found

### What Happened?

Logseq DB deleted a whole block during import. I have a small sample graph to reproduce the issue.

### Reproduce the Bug

1. "Import existing notes"
2. "File to DB graph"
3. Choose this graph: [missing-node-repro.zip](https://github.com/user-attachments/files/30868378/missing-node-repro.zip)
4. Go to the journal page for August 8 and compare with the markdown file.

### Expected Behavior

Import the table from Logseq OG.

### Screenshots

Image

### Files

[missing-node-repro.zip](https://github.com/user-attachments/files/30868378/missing-node-repro.zip)

### Browser, Desktop or Mobile Platform Information

OS: Arch Linux
Browser: Firefox
test.logseq.com revision: [5a23230](https://github.com/logseq/logseq/commit/5a23230)

### Additional Context

Console log:

```
:ast->text "Ignored ast node" :node ["Table" {:header [[["Plain" "Old event handler"]] [["Plain" "New event handler"]] [["Plain" "Note"]]], :groups [[[[["Plain" "OnInitComplete"]] [["Plain" "OnBoot"]] [["Plain" ""]]] [[["Plain" "OnShutdown"]] [["Plain" "OnShutdown"]] [["Plain" ""]]] [[["Plain" "OnOpened"]] [["Plain" "OnOpen"]] [["Plain" ""]]] [[["Plain" "OnClosed"]] [["Plain" "OnClose"]] [["Plain" ""]]] [[["Plain" "React"]] [["Plain" "OnTraffic"]] [["Plain" ""]]] [[["Plain" "Tick"]] [["Plain" "OnTick"]] [["Plain" ""]]] [[["Plain" "PreWrite"]] [["Plain" "-"]] [["Plain" "Deprecated"]]] [[["Plain" "AfterWrite"]] [["Plain" "-"]] [["Plain" "Deprecated"]]]]], :col_groups [3]}]
```

### Are you willing to submit a PR? If you know how to fix the bug.

- [ ] I'm willing to submit a PR (Thank you!)

Contributor guide

No contributing guide indexed for this repository

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.