Fix panic in textDocument/completion when cached symbols cannot be rehydrated #1844
+99
−13
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes a panic that occurred during completion requests when the language service tried to rehydrate cached export information but couldn't find the symbol or module anymore.
Issue
The language service was panicking with errors like:
This happened when:
Solution
Changed
rehydrateCachedInfo
to return(*SymbolExportInfo, bool)
instead of panicking when symbols or modules cannot be found. Updated callers to usecore.MapFiltered
to gracefully skip entries that can't be rehydrated, allowing completions to continue with the remaining valid entries.Changes
exportInfoMap.rehydrateCachedInfo
to return a success booleanpanic()
calls with gracefulreturn nil, false
error handlingget()
andsearch()
methods to handle rehydration failuresTestCompletionNullExportCondition
The fix maintains robustness by handling transient cache state gracefully rather than crashing the language service.
Original prompt
This section details on the original issue you should resolve
<issue_title>textDocument/completion Could not find symbol</issue_title>
<issue_description>This panicked while I was typing out a new test case.