-
Notifications
You must be signed in to change notification settings - Fork 467
Driver Security Improvements: Go Driver Dependencies #714
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
Conversation
|
Did you mean the interface related files inside the parser folder? I had already removed the unneeded generated *.token and *.interp files prior to this commit. |
|
@jrgemignani @aru-d-at On the ANTLR modification for the python driver, I asked Arun to remove the generated files from the commit-- I think he would apply similar logic to this one as well. As far as I can see, there are no generated files. Looks good to me. |
I'm referring to the age_*.go files in golang/parser. All of them are generated by Age.g4 it looks like. We can probably remove them all. |
@aru-d-at can you go and see if it is possible to remove these files from the repository? Thank you |
@dehowef @jrgemignani Various functions and interfaces from the 'parser' package are used in the 'builder.go' and 'mapper.go'. These are just some of the ones in first few lines. Seems like it is necessary to keep these functions and interfaces as well as it dependencies located inside the Parser package. |
|
@aru-d-at I just checked and they [.go files in parser] are generated by antlr4. However, we don't provide antlr4 in our package, just the runtime. It looks like if those files aren't there, it would be a pain for anyone to regenerate them manually. So, ignore my concerns about the .go files in parser. |
|
@jrgemignani @dehowef So in that case all good for the merge? |
|
@jrgemignani All parser files were generated then licenses were edited in. I needed to edit the antlr import statement to reflect newer import path for v4.11.1 for mapper and builder inside age folder. |
Is it possible to add something to the go driver to automatically build these files or something in a README explaining how to build them so that we don't need to include the generated files in the distribution? |
|
@jrgemignani I have this Batch script ready for Windows and have tested it. I also have the Bash script ready and tested on Linux but, haven't found a way to test it on Mac yet. Should I go ahead and commit them? Batch script |
|
@aru-d-at go ahead and commit it |
|
@aru-d-at but yeah we should remove as many auto generated files as possible-- there is no need to track those unless absolutely necessary |
02c6f72 to
1de90fa
Compare
|
@dehowef I have pushed the scripts after testing on all 3 OS's |
1de90fa to
b1e2595
Compare
|
@dehowef Seems the Go Workflow needed to be updated as well as a Go Target Generation file. |
b1e2595 to
d5f9d9a
Compare
|
@dehowef Updated the workflow again since generation was failing as ANTLR jar is non-existent. Hopefully workflow works now. (If it doesn't may need to inspect Java dependency in yml) |
|
@aru-d-at Yeah, it still seems to be failing 2 tests-- this issue has been plaguing us for awhile |
d5f9d9a to
cbca575
Compare
|
@dehowef Sorry, my bad, I should have run workflow on a separate repo first. |
|
@aru-d-at All checks passed. Great work! I'll merge it now |






ANTLR v4.9.2 -> v4.11.1
Go Dependencies
Parser README
### TESTING Steps:
go get -u ./...-> SUCCESSgo test ./...-> SUCCESS - Output