You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When combining SCIP data from many sources it is very useful to know the language of the file.
message Document {
string language = 4;
I believe scip-typescript may be setting this to "" .
there's also something funky with non-utf8 in the symbol fields.
$ protoc --decode scip.Occurrence scip.proto < /tmp/index.scip
E0626 17:07:01.064803 1569665 wire_format_lite.cc:626] String field 'scip.Occurrence.symbol' contains invalid UTF-8 data when parsing a protocol buffer. Use the 'bytes' type if you intend to send raw bytes.
The text was updated successfully, but these errors were encountered:
donsbot
added a commit
to donsbot/Glean
that referenced
this issue
Jun 26, 2023
Summary:
Faster, more precise. Aligned with go and rust-analyer
Also works around sourcegraph/scip-typescript#263 by setting an optional language hint.
Pull Request resolved: #344
Test Plan: will need to fix the relative path prefix to the indexer as it bakes in the full path
Reviewed By: simonmar
Differential Revision: D47050745
Pulled By: donsbot
fbshipit-source-id: 582c1cd7b0fc69daabcae64770cda3320ba273ce
When combining SCIP data from many sources it is very useful to know the language of the file.
I believe scip-typescript may be setting this to "" .
there's also something funky with non-utf8 in the symbol fields.
The text was updated successfully, but these errors were encountered: