feat: add diagnostic logging for GLM model detection #11080
Draft
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.
This PR attempts to address Issue #11071 by adding diagnostic logging to help users verify GLM model detection.
Problem
Users testing PR #11077 cannot verify whether:
Solution
Added console logging at key points:
parallel_tool_callsvalue being sent to the APIExample Output
When using a GLM model like
glm-4.5:When using a non-GLM model:
Testing
Notes
Feedback and guidance are welcome!
Important
Adds diagnostic logging for GLM model detection and optimizations, with utility functions and tests for model identification and option retrieval.
base-openai-compatible-provider.tsandlm-studio.ts.parallel_tool_callsvalue.isGlmModel()andgetGlmModelOptions()inmodel-detection.tsfor GLM model detection and option retrieval.model-detection.spec.tsfor GLM model detection and option retrieval.This description was created by
for 2c5d905. You can customize this summary. It will automatically update as commits are pushed.