[PR #26414] Refactor: Enable type checking for core/ops and fix type errors #31428

Closed
opened 2026-02-21 20:49:26 -05:00 by yindo · 0 comments
Owner

Original Pull Request: https://github.com/langgenius/dify/pull/26414

State: closed
Merged: Yes


This commit enables type checking for the core/ops directory by removing it from the exclude list in pyrightconfig.json.

The following type errors were fixed:

  • Corrected Status and StatusCode imports in aliyun_trace_entity.py.
  • Handled a potential None value for current_trace_config in ops_trace_manager.py.
  • Fixed multiple type errors in weave_trace.py related to incorrect argument types and access to protected members.

Important

  1. Make sure you have read our contribution guidelines
  2. Ensure there is an associated issue and you have been assigned to it
  3. Use the correct syntax to link this PR: Fixes #<issue number>.

Summary

part of #26412

Screenshots

Before After
... ...

Checklist

  • This change requires a documentation update, included: Dify Document
  • I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!)
  • I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change.
  • I've updated the documentation accordingly.
  • I ran dev/reformat(backend) and cd web && npx lint-staged(frontend) to appease the lint gods
**Original Pull Request:** https://github.com/langgenius/dify/pull/26414 **State:** closed **Merged:** Yes --- This commit enables type checking for the `core/ops` directory by removing it from the exclude list in `pyrightconfig.json`. The following type errors were fixed: - Corrected `Status` and `StatusCode` imports in `aliyun_trace_entity.py`. - Handled a potential `None` value for `current_trace_config` in `ops_trace_manager.py`. - Fixed multiple type errors in `weave_trace.py` related to incorrect argument types and access to protected members. > [!IMPORTANT] > > 1. Make sure you have read our [contribution guidelines](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) > 1. Ensure there is an associated issue and you have been assigned to it > 1. Use the correct syntax to link this PR: `Fixes #<issue number>`. ## Summary <!-- Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change. --> part of #26412 ## Screenshots | Before | After | |--------|-------| | ... | ... | ## Checklist - [ ] This change requires a documentation update, included: [Dify Document](https://github.com/langgenius/dify-docs) - [x] I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!) - [x] I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change. - [x] I've updated the documentation accordingly. - [x] I ran `dev/reformat`(backend) and `cd web && npx lint-staged`(frontend) to appease the lint gods
yindo added the pull-request label 2026-02-21 20:49:26 -05:00
yindo closed this issue 2026-02-21 20:49:27 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#31428