zulip/zulip

Import process breaks near-links in the imported messages

Open

#31,100 建立於 2024年7月25日

在 GitHub 查看
 (7 留言) (0 反應) (1 負責人)Python (19,672 star) (7,339 fork)batch import
area: data import/exportbughelp wantedin progresspriority: high

描述

The import process remapped the foreign keys of the imported tables but didn't reformat imported messages with near-links. This breaks all near-links because they still point to the old message ID, channel ID, etc.

For example, one channel ID was remapped from 223 to 271 during the import, which breaks this near-link: image image

CZO thread

貢獻者指南

技術棧
pythondjangopostgresql
領域
backenddatabase
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
active
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
PythonDjango
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
30
研究方向
Examine the import process in Zulip's codebase, particularly in files related to data import and message formatting. Look for how near links (like `/near/` in messages) are stored and how foreign keys are remapped during import. The issue indicates that message content is not updated to reflect remapped IDs. Investigate relevant functions in `zerver/lib/import realm.py` or similar. Ensure that after remapping, all near links in message bodies are replaced with the new IDs.