-
Notifications
You must be signed in to change notification settings - Fork 44
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
Python parsing Bug: Issues with codebases like dspy, textgrad , litellm etc #28
Comments
@phodal - we are doing this effort inspired from you and your work here - https://github.com/unoplat/unoplat-code-confluence . |
Can you paste the failed code ? |
But in other way, In you use Python for your project, I suggest you can use TreeSitter to parse code. |
Avoid crashes due to null contexts by using nullable types and safe calls in the PythonAstBaseListener. This ensures the parser can handle cases where child contexts may not be present.
Thanks sure will do first thing in morning it's late here in India. Also the codebases I tested with were dspy litellm textgrad etc using arcguard cli as we use that as a base for the project - unoplat code confluence |
this was the file where it failed and for which the exception is shared- https://github.com/zou-group/textgrad/blob/main/textgrad/tasks/gpqa.py . @phodal |
@phodal - |
yea you are right we could use tree sitter for python but we would want to be based on chapi/arcguard to keep things simple and work closely with arcguard. |
already publish new version 2.3.6 to maven central, it's still need 15~30mins maybe for maven to publish. |
So is the new version for arcguard ? @phodal . As we also like most people just use arcguard cli to parse codebases into chapi - Thankyou @phodal ! Also if you get time we would to plug https://github.com/unoplat/unoplat-code-confluence it in to your agents if the current work/roadmap excites/aligns with you. |
OK, it will do it later. |
Update the `chapi` library version from 2.3.5 to 2.3.6 in the `gradle/libs.versions.toml` file to incorporate the latest changes and potentially bug fixes.
@JayGhiya Already publish new version to GitHub, and for Maven Central still need 15~30mins to waiting for it. |
Example exception that happens
The text was updated successfully, but these errors were encountered: