[Bug] Recovery from corrupt conversation_index.xml
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
Research direction
The issue identifies conversation_index.xml and individual conversation files but names no source files or tests. Start by locating where the Eclipse plugin reads and writes the conversation index, then inspect how it handles malformed XML and existing conversation files. Done means a truncated index no longer prevents existing conversations from appearing or new chats from being saved; recovery behavior still needs to be chosen.
Written by the indexing model from the issue text.
Description
Environment
- OS: Windows 11
- Eclipse Version: 4.38.0.v20251201-0920
- Plugin Version: 0.21.0.202609221612_nightly
Describe the bug
Somehow my conversation_index.xml got truncated. There didn't appear to be any connection to an Eclipse crash or particular activity. After this happened none of the existing conversations showed in the chat history panel but also new conversations failed to be added too. It was necessary to delete the existing conversation_index.xml file for chat history to function again with new conversations.
To Reproduce
Steps to reproduce the behavior:
- Edit the conversation_index.xml file and delete the file from midway through a conversation element to the end.
- Start Eclipse.
- Start a new chat.
- Start another chat or restart Eclipse.
- See that the first chat is not present in the history.
Expected behavior
Recovery from the corrupted file. This could be from a backup file that is guaranteed to validate or ideally recreating it from the individual conversation files.
- Dominant language
- Java
- Stars
- 125
- Forks
- 63
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 3
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from microsoft/copilot-for-eclipse
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 12/100
microsoft/copilot-for-eclipse#477 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 45/100
microsoft/copilot-for-eclipse#474 ·
Maintainers usually reply within 1 day
-
[Feature Request] Copilot CLI Quick Launcher (Just like Intellij) with WSL & Auto-Install SupportOpenenhancement
Difficulty 5/5 Over a week Newbie friendliness 42/100
microsoft/copilot-for-eclipse#473 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 48/100
microsoft/copilot-for-eclipse#472 · 1 reaction ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
microsoft/copilot-for-eclipse#465 ·
Maintainers usually reply within 1 day
All issues in microsoft/copilot-for-eclipse
Similar issues
-
[BUG] 订单：会员凭订单号即可取消其他会员的待付款订单（取消接口不校验订单归属）Possibly taken @dadiyang claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
macrozheng/mall#1016 ·
-
[Bug] The producer summary counts an unreported client version as a second version and warns about a version mixPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
apache/rocketmq-dashboard#6110 ·
Maintainers usually reply within 4 days
-
Feature:Resolution
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
intellij-elixir/intellij-elixir#4396 ·
Maintainers usually reply within 1 day
-
Python 3.15 supportPossibly taken @amnesiaof claimed this today. OpenL: python L: python:uv
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
dependabot/dependabot-core#16524 · 1 comment ·
Maintainers usually reply within 1 day
-
`Processing lsp` never exits and leaves orphaned processesPossibly taken @overcast302 claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
processing/processing4#1578 · 1 comment ·