-
Notifications
You must be signed in to change notification settings - Fork 3.1k
fix(dspy): Fix Module.__call__ to enable nested module usage tracking with track_usage #9213
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
Draft
Copilot
wants to merge
9
commits into
main
Choose a base branch
from
copilot/fix-parallel-bug-in-module
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.
Draft
Changes from all commits
Commits
Show all changes
9 commits
Select commit
Hold shift + click to select a range
adb963a
Initial plan
Copilot 7f381e8
Fix dspy.Parallel usage tracking inside dspy.Module
Copilot 0fd3fcc
Add test for parallel usage tracking fix
Copilot db54251
Handle tuple with list of Predictions in usage tracking
Copilot df5efbf
Add non-empty list checks in _set_lm_usage
Copilot adc30e3
Refactor _set_lm_usage to use recursive collection
Copilot d4614e6
Improve documentation for collect_predictions function
Copilot e8c0ee0
Fix nested module usage tracking in Module.__call__
Copilot 10966b2
Improve robustness of Module.__call__ and _compute_token_delta
Copilot 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
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.
@copilot I think we should fix
Module.__call__instead of_set_lm_usage. Currently, _set_lm_usage is called only on the root module call and no usage is added to the nested module call.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.
You're absolutely right! I've fixed
Module.__call__to handle nested module calls. Previously, only the root module would call_set_lm_usage. Now whentrack_usageis enabled:forward()and sets usage on output (nested module case)This ensures all module calls (root and nested) properly track and set usage on their Prediction outputs.
Fixed in commit e8c0ee0.
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.
@copilot do we still need the change for _set_lm_usage?
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.
Yes, we still need the recursive
_set_lm_usagebecause both fixes address different concerns:1. Module.call fix (commit e8c0ee0): Ensures each module call (root or nested) gets its usage tracked
OuterModule()β callsinner_module()β both get usage set2. Recursive _set_lm_usage (commits 7f381e8-adc30e3): Ensures all Predictions in a single module's output get usage set
[Prediction, Prediction]fromdspy.Parallelβ all get usage setThe original bug was a module returning a list of Predictions from Parallel. Without the recursive _set_lm_usage, even with the call fix, the list wouldn't be traversed and individual Predictions wouldn't get usage set.
Both fixes are needed for the complete solution.