-
Notifications
You must be signed in to change notification settings - Fork 5
feat/add-support-qwen3 #17
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
Open
fengzz-coding
wants to merge
11
commits into
main
Choose a base branch
from
feat/add-support-qwen3
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
a213598
add support qwen3
fengzz-coding ea5f3fa
update dependencies
fengzz-coding 46c9983
only support for qwen model
fengzz-coding c36db98
Merge branch 'main' into feat/add-support-qwen3
fengzz-coding cbfeac9
delete template.py
fengzz-coding a21c3ec
Merge remote-tracking branch 'origin/feat/add-support-qwen3' into fea…
fengzz-coding 13df7e5
add hf_tokenizer mapping
fengzz-coding be3280d
only keep qwen3.5 model
fengzz-coding ff452a5
fix qwen3.5 model function calling bug.
fengzz-coding 4ec68cf
fix qwen3.5 model function calling bug.
fengzz-coding 6440edc
fix some Tool call bug
fengzz-coding File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,12 @@ | ||
| SUPPORTED_BASE_MODELS = [ | ||
| # qwen3.5 | ||
| "Qwen/Qwen3.5-0.8B", | ||
| "Qwen/Qwen3.5-0.8B-Base", | ||
| "Qwen/Qwen3.5-2B", | ||
| "Qwen/Qwen3.5-2B-Base", | ||
| "Qwen/Qwen3.5-4B", | ||
| "Qwen/Qwen3.5-4B-Base", | ||
| "Qwen/Qwen3.5-9B", | ||
| "Qwen/Qwen3.5-9B-Base", | ||
| "Qwen/Qwen3.5-27B", | ||
| ] |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
1. Reference extraction can be misaligned with the actual prompt
You extract the reference using:
but you truncate the processed messages with:
Problem:
conversations= raw inputconversation_to_process= filtered + transformed versionIf any messages were:
function_call→assistant),then the “last raw message” may not match the “last processed message”.
You may remove one message from the prompt, but use a different one as the reference.
2.
function_callreference is raw JSON string (may not match your evaluation goal)When the last message is a
function_call, you do:This gives you something like:
{"name":"get_weather","arguments":{"city":"Toronto"}}So your reference is:
This is only correct if your evaluation expects:
Otherwise it may be inconsistent with:
tool_callsstructure)3. Tool call ↔ observation matching is simplified (not robust)
You assign each observation to the most recent tool call:
This assumes:
Works fine for simple ReAct-style traces like:
But breaks or becomes ambiguous if: