Skip to content
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

[Frontend] improve hermes_tool_parser.py #11444

Closed
wants to merge 3 commits into from

Conversation

paulcx
Copy link

@paulcx paulcx commented Dec 24, 2024

Using json_repair can improve the robustness of parsing the JSON output

Using json_repair can improve the robustness of parsing the JSON output
Copy link

👋 Hi! Thank you for contributing to the vLLM project.
Just a reminder: PRs would not trigger full CI run by default. Instead, it would only run fastcheck CI which starts running only a small and essential subset of CI tests to quickly catch errors. You can run other CI tests on top of those by going to your fastcheck build on Buildkite UI (linked in the PR checks section) and unblock them. If you do not have permission to unblock, ping simon-mo or khluu to add you in our Buildkite org.

Once the PR is approved and ready to go, your PR reviewer(s) can run CI to test the changes comprehensively before merging.

To run CI, PR reviewers can do one of these:

  • Add ready label to the PR
  • Enable auto-merge.

🚀

@mergify mergify bot added the frontend label Dec 24, 2024
Comment on lines 4 to 10
try:
from json_repair import json_repair
except ImportError:
# might remove codes below by adding json_repair in requirement.txt
import subprocess
subprocess.check_call(["pip", "install", "json_repair"])
from json_repair import json_repair
Copy link
Member

@DarkLight1337 DarkLight1337 Dec 24, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's not install things automatically during runtime. Can you add this to the requirements file instead?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's not install things automatically during runtime. Can you add this to the requirements file instead?

I noticed there are a lot of requirements files, and I'm not familiar with their specific uses. It might need some assistance with it.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The base dependencies of vLLM are contained in requirements-common.txt. Since tool parsing is applicable to all backends, you can add the dependency there.

@DarkLight1337 DarkLight1337 requested a review from mgoin December 24, 2024 05:51
@paulcx paulcx closed this Dec 24, 2024
@paulcx paulcx deleted the patch-1 branch December 24, 2024 06:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants