mypy-pylint-fixed #21
Dismiss Review
Are you sure you want to dismiss this review?
Labels
Clear labels
auto/needs-reevaluation
controller-managed
overdue
auto/blocked-by-deps
auto/ci-timeout
auto/claimed-implementer
auto/claimed-merge
auto/claimed-reviewer
auto/driver-down
auto/invariant-violation
auto/last-attempt-tier-0
auto/last-attempt-tier-1
auto/last-attempt-tier-2
auto/last-attempt-tier-min
Automation Tracking
auto/needs-conflict-resolution
auto/needs-implementer
auto/postmortem
auto/ready-to-merge
auto/restart-throttled
auto/revert
auto/sentinel
auto/stale-inactivity
auto/unstable
Blocked
Needs Feedback
Signed-off: Owner
Signed-off: Scrum Master
Signed-off: Tech Lead
Spike
Controller deferred this PR; awaiting Phase 6+ scope-evaluator or operator re-enablement.
Auto-agents controller manages this PR/issue (see tools/controller/deploy/RUNBOOK.md). Remove this label to abandon controller management.
PR blocked by an open issue dependency. Operator must close the dep (or remove the dependency link) before the merge driver can act. Auto-cleared by merge_drive when no open deps remain.
Most recent merge cycle hit CI timeout. Driver excludes this PR while last merge_cycle row is < 30 min old; label persists thereafter as visible history.
Currently being processed by an implementer worker.
Currently being processed by the merge driver.
Currently being processed by a reviewer worker.
Merge driver heartbeat stale; pipeline halted. Closed automatically on next clean tick.
Detected master commit violating the strict merge invariant. Tracked as an issue (not a PR label); kept here for label completeness.
In-cycle escalation: most recent attempt ran at the Tier 0 slot (`tier-0`). Slot's model defined in .opencode/models/tiers.yaml.
In-cycle escalation: most recent attempt ran at the Tier 1 slot (`tier-1`). Slot's model defined in .opencode/models/tiers.yaml.
In-cycle escalation: most recent attempt ran at the Tier 2 slot (`tier-2`). Slot's model defined in .opencode/models/tiers.yaml. Gated behind IMPLEMENTER_ESCALATION_TIER2_ENABLED.
In-cycle escalation: most recent attempt ran at the Tier -1 slot (`tier-min`). Slot's model defined in .opencode/models/tiers.yaml. Suffix is ``-min`` (not ``--1``) so the Forgejo UI reads naturally.
Tracking issues used by the AI Automation system for agents to communicate and report.
Rebase conflict needs LLM conflict-resolver.
Failing CI needs implementer attention.
Documenting a driver incident or rollback.
Reviewer has APPROVED this PR and no later REQUEST_CHANGES is outstanding. The merge driver requires this label to even consider a PR for merging. Set by the reviewer worker on APPROVE; cleared on REQUEST_CHANGES.
Train repeatedly lost master-tempo races. Driver excludes via merge_cycle until cooldown elapses; label persists as visible history.
Revert PR backing out an invariant violation. Fast-tracked through the merge driver.
Sentinel PR duplicated from upstream into a personal fork by tools/duplicate_prs_to_fork.py for pipeline testing. Lives only in the fork; the canonical pipeline never sees it.
No implementer activity for N days. Flagged for human review. Auto-cleared on next push to head branch.
Repeatedly fails on current master (>= 3 ci-fail-on-rebased-sha releases in 12 h). Excluded from driver until human triage.
A ticket in a blocked state and unable to complete until some other task is completed first.
Bounty
$100
A bounty of $100 for any open-source contributor who provides a MR that solves this issue
Bounty
$1000
A bounty of $1000 for any open-source contributor who provides a MR that solves this issue
Bounty
$10000
A bounty of $10000 for any open-source contributor who provides a MR that solves this issue
Bounty
$20
A bounty of $20 for any open-source contributor who provides a MR that solves this issue
Bounty
$2000
A bounty of $2000 for any open-source contributor who provides a MR that solves this issue
Bounty
$250
A bounty of $250 for any open-source contributor who provides a MR that solves this issue
Bounty
$50
A bounty of $50 for any open-source contributor who provides a MR that solves this issue
Bounty
$500
A bounty of $500 for any open-source contributor who provides a MR that solves this issue
Bounty
$5000
A bounty of $5000 for any open-source contributor who provides a MR that solves this issue
Bounty
$750
A bounty of $750 for any open-source contributor who provides a MR that solves this issue
MoSCoW
Could have
Could have feature in order to satisfy the epic/legendary.
MoSCoW
Must have
Must have feature in order to satisfy the epic/legendary.
MoSCoW
Should have
Should have feature in order to satisfy the epic/legendary.
There are questions in the ticket that can not be completed until the project owner provides clarity.
Points
1
1 man-hours worth of work for an expert with no learning curve.
Points
13
13 man-hours worth of work for an expert with no learning curve.
Points
2
2 man-hours worth of work for an expert with no learning curve.
Points
21
21 man-hours worth of work for an expert with no learning curve.
Points
3
3 man-hours worth of work for an expert with no learning curve.
Points
34
34 man-hours worth of work for an expert with no learning curve.
Points
5
5 man-hours worth of work for an expert with no learning curve.
Points
55
55 man-hours worth of work for an expert with no learning curve.
Points
8
8 man-hours worth of work for an expert with no learning curve.
Points
88
88 man-hours worth of work for an expert with no learning curve.
Priority
Backlog
This ticket has backlogged priority and is not to be worked on yet
Priority
CI Blocker
Critical priority issue that blocks CI/CD pipeline and prevents PR merges
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.
A ticket for learning a tool or technology that is needed to be able to do future planning and design.
State
Completed
The ticket has been fully implemented, completed, and merged with the source code. This label should only be applied once a ticket is closed.
State
Duplicate
A ticket that represents the same content as an existing ticket.
State
In Progress
A ticket that is actively being developed.
State
In Review
A ticket that has had some code completed to implement but is waiting to pass peer review and is not yet merged in.
State
Paused
This ticket's work started but wasn't finished. It's on hold (likely in a feature branch) and will be resumed later, either due to a blocker or a delay.
State
Unverified
All new tickets start in this state. A developer may set it to show the ticket is unverified. This means we haven't agreed to work on it. It will either move to a verified state or be closed as wontdo.
State
Verified
The issue has been verified by a developer as legitimate. It will be worked on and verified tickets are now considered part of the backlog.
State
Wont Do
This ticket has been decided it wont be done. This may mean the bug has been determined to not be real (cant verify) or the feature is one we have decided we dont want to adopt.
Type
Automation
Any edits or discussion about the AI automated coding system.
Type
Bug
Something that doesnt work as intended.
Type
Discussion
Anytime a ticket represents a discussion about a subject and doesnt fall into one of the other categories.
Type
Documentation
An error or improvement needed in the documentation.
Type
Epic
Any first tier epic. That is, an epic which contains only issues as children and will not have sub-epics.
Type
Feature
Some new functionality not present.
Type
Legendary
A type of Epic which will contain other Epics.
Type
Refactor
A code change that restructures existing code without changing its external behavior.
Type
Support
Someone needs help using the project.
Type
Task
A generic task that doesnt fit into the other type categories.
Type
Testing
Work exclusively focusing on fixing or expanding testing.
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
aditya (Aditya Chhabra)
aleenaumair (Aleena Umair)
brent.edwards (Brent Edwards)
CoreRasurae (Luis Mendes)
drew (Drew Morris)
eugen.thaci (Eugen Thaci)
freemo (Jeffrey Phillips Freeman)
HAL9000 (HAL 9000)
HAL9001 (HAL9001)
hamza.khyari (Hamza Khyari)
hurui200320 (Rui Hu)
justin.morris
khird (Kyle Hird)
org.cleveragents
Clear assignees
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: cleveragents/cleveragents-core#21
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Delete Branch "mypy-pylint-fixed"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
fixed mypy --strict and pylint errors and warnings of feat/multi-agent , only merge after merging pr #5
Five left for
mypy --strictandpylint.You can do it!
@@ -286,3 +283,3 @@# Extract resultif hasattr(result, "messages") and result.messages:return result.messages[-1].get("content", "")content = result.messages[-1].get("content", "")In line 279 (I cannot leave a comment on code you didn't write) is
mypy --strict srcreports:@@ -450,3 +482,1 @@f"Registered {len(templates.get('agents', {}))} agent templates, "f"{len(templates.get('graphs', {}))} graph templates, "f"{len(templates.get('streams', {}))} stream templates""Registered %d agent templates, %d graph templates, %d stream templates",On line 478 (I cannot leave comments on lines you did not change) is the line
mypy --strict srcreports:Still missing this problem from
mypy --strict src. Here's what I get:It's still here this morning:
@brent.edwards
Fixed the mypy --strict issues.
@@ -56,3 +57,3 @@graph_def["name"] = self.namereturn graph_defreturn cast(Dict[str, Any], graph_def)According to
mypy --strict src:@@ -283,3 +280,3 @@result = self._apply_templates_recursive(result, templates, context)return resultreturn cast(Dict[str, Any], result)According to
mypy --strict src:@@ -52,3 +53,3 @@stream_def["name"] = self.namereturn stream_defreturn cast(Dict[str, Any], stream_def)According to
mypy --strict src:To achieve meaningful mypy compliance, the use of cast to subvert its warnings should be reduced, or at least there should be comments justifying why each usage is safe despite mypy's warning. The other issues are optional and won't block my approval of this MR.
@@ -100,3 +99,3 @@kwargs["api_key"] = api_keyreturn ChatAnthropic(**kwargs)elif self.provider.lower() == "google":if self.provider.lower() == "google":These if/elif blocks would probably be more clearly expressed as one block of code that operates on a data structure like
and decides what members of
common_kwargs(if any) to mangle based on therenamesfield.@khird
Replaced if/elif blocks with a data-driven provider_config dictionary that maps providers to their parameter renames and classes, using a unified flow for all providers.
@@ -205,2 +228,3 @@return {}async def _execute_tool(self, state: GraphState) -> Dict[str, Any]:async def _execute_tool(self, _state: GraphState) -> Dict[str, Any]:I assume this makes some automated tool shut up about you not using the argument
stateanywhere in the function body. Is there any reason not to simply remove it from the function definition? If there are places that rely on being able to call a function that might beself._execute_tool()or might beself._execute_conditional()and construct their argument list to include a GraphState, this change would cause it to break if they set it by keyword. If you absolutely can't remove it, using*argsand**kwargsmight be more forgiving.@khird
Fixed by removing the unused state parameter entirely from _execute_tool() since it wasn't being used in the function body, while keeping it in _execute_conditional() where it's actually needed.
same issue in _execute_state(). Not a blocker, so I'm approving
@@ -156,2 +156,3 @@if default_value.isdigit():return default_valueelif default_value.replace(".", "").isdigit():if default_value.replace(".", "").isdigit():What is the point of this test? If to match decimal numbers, should probably be replace(x, y, 1). If to match IP addresses, this doesn't work on IPv6. And in any case, if the condition isn't satisfied, we do the same thing (i.e. returning the default value) anyway when we fall through.
Fixed by removing the redundant decimal check since it was doing the same thing as the fall-through case - returning the default value as a string. @khird
@@ -173,2 +171,3 @@if config.isdigit():return int(config)elif config.replace(".", "").isdigit() and config.count(".") == 1:if config.replace(".", "").isdigit() and config.count(".") == 1:So I guess the answer here is that it's a decimal number. I note that negatives aren't handled; may or may not be an issue.
Fixed by using lstrip('-') to handle negative numbers and replace(".", "", 1) to properly handle decimal numbers with only one decimal point, addressing the negative number issue you mentioned. @khird
@@ -332,2 +336,2 @@import threadingimport asyncio as async_io # pylint: disable=reimported,import-outside-toplevelimport threading # pylint: disable=import-outside-toplevelIt's not clear why reimporting modules is necessary, or why they wouldn't be at the top level. Maybe comment to justify why do it this way that requires circumventing pylint + mypy?
@khird
fixed the re importing modules, only keeping it on places where there is circular import issue.
@@ -6,3 +6,4 @@from pathlib import Pathfrom typing import TYPE_CHECKINGfrom typing import Anyfrom typing import Dicttyping.Dict is deprecated in favour of dict in recent versions of python, including all the versions CleverAgents claims to support.
@khird
Replaced the Dict[..] with dict[..] and removed the import statement.
@@ -174,1 +173,3 @@return template.instantiate(params, self, context or InstantiationContext())return cast(Dict[str, Any],template.instantiate(params, self, context or InstantiationContext()),Please add a comment here explaining why fooling mypy with a
cast()is necessary - if you know thattemplate.instantiate()is going to return adict[str, Any]then why not just annotate it as such in the base submodule? And if not, please explain why it's safe to proceed as if this were true, despite mypy's warning.@khird
Replaced cast() with runtime validation that checks isinstance(result, dict) and raises ValueError with clear error message if YAML parses as anything other than a dict. This handles the case where YAML could be a list, string, or other type, making the code robust and type-safe without hiding potential issues.
@@ -84,3 +83,3 @@# If no templates, just parseif "{%" not in yaml_content and "{{" not in yaml_content:return yaml.safe_load(yaml_content)return cast(Dict[str, Any], yaml.safe_load(yaml_content))It's possible for yaml to represent a list rather than a dict. If there's a reason we know that can't be the case for the particular specimen in
yaml_content, it would be good to document that reason. If there isn't such a reason, then mypy's correct here and you ought to handle or check that case. I'm not going to spam a bunch of identical comments aboutcasteverywhere, but please give it a general look.@khird
Replaced cast() with runtime validation that checks isinstance(result, dict) and raises ValueError with clear error message if YAML parses as anything other than a dict. This handles the case where YAML could be a list, string, or other type.
@@ -53,2 +53,3 @@if template_type == TemplateType.STREAM:template = StreamTemplate(name, template_type, definition)else:if template_type not in [TemplateType.AGENT, TemplateType.GRAPH, TemplateType.STREAM]:I think the elif/else construction worked better here, because now anyone adding a new template type has to add an if block and an element to this list. If you'd just left it as elif blocks, there wouldn't be the possibility to forget the second part.
@khird
You're right elif/else is better. Adding a new template type only requires one elif block, avoiding the risk of forgetting to update both a validation list and the handling logic.
@@ -226,4 +230,3 @@parsed = {"_content": parsed}parsed["__templates__"] = templatesreturn parsedmypy --strict srcreports:@brent.edwards
Added runtime validation checks and raise ValueError with clear messages.
I feel for you. You are so close to done!
Here is the exact result from
mypy --strict src:271d3a76d3to6fff3968a6Relates to #23
hurui200320 referenced this pull request2026-03-19 09:49:43 +00:00
hurui200320 referenced this pull request2026-03-23 05:54:58 +00:00