-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
srcd parse: do not check the list of languages #449
Conversation
@@ -123,6 +110,12 @@ func (cmd *parseUASTCmd) Execute(args []string) error { | |||
} | |||
|
|||
if err != nil { | |||
if strings.Contains(err.Error(), "missing driver for language") { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do we have an issue in bblfsh to export this error instead of strings.Contains
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, it's this one https://github.com/src-d/engine/issues/297
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wait. this is an issue in engine about aliasing.
I'm talking about an issue in bblfsh-sdk / bblfsh-go-client that would differentiate lang not found error from any other error.
I don't see any link or any conversation about it in 297.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@carlosms ping
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't mind to merge this but on another hand, it doesn't fix anything...
Signed-off-by: Carlos Martín <[email protected]>
Signed-off-by: Carlos Martín <[email protected]>
c96dfcf
to
1f158ea
Compare
This is a workaround for #297.
The command now does not try to check if the file language is in the list of bblfsh drivers. But if bblfsh reports that the parsing failed because of a missing driver, engine will still print the same nice error message with the current list of supported languages.
It works for
c#
-> bblfshcsharp
c++
-> bblfshcpp
.It still fails for
shell
-> bblfshbash
.Unfortunately now that the tests parse the cpp and csharp files, they fail, so I had to disable them.
See bblfsh/cpp-driver#31, bblfsh/bblfshd#259