-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Retain return type from @dispatcher.span #17817
base: main
Are you sure you want to change the base?
Conversation
OK, I believe the type checking is working better now. However, this has uncovered typing issues in 11 other files. 🤔 |
Some of these might be actual bugs. For example, llama_index/llama-index-core/llama_index/core/query_engine/retry_source_query_engine.py Lines 42 to 48 in f43e337
llama_index/llama-index-core/llama_index/core/base/response/schema.py Lines 234 to 236 in f43e337
|
Note, commit 9303917 is a pretty good branching point before I went down a deep rabbit hole. (8 mypy errors remaining there) |
d54996e gets back to 7 mypy errors (better than before the rabbit hole) |
For these remaining mypy errors, I'm not sure I know the code well enough to determine whether it's best to "fix" the types, squelch the error (with a cast or type ignore), or if there are potential bugs in the code.
https://github.com/run-llama/llama_index/actions/runs/13335762370/job/37250483650?pr=17817 |
Attempt to fix run-llama#16915
Looks safe based on the structure of the existing code.
1a743c0
to
4e9d83a
Compare
Reworked commits to be a little more cohesive. |
Attempt to fix #16915
Type of Change
Please delete options that are not relevant.
How Has This Been Tested?
Your pull-request will likely not be merged unless it is covered by some form of impactful unit testing.
Suggested Checklist:
make format; make lint
to appease the lint gods