fix prints.

[gouhongshen]

User description

What type of PR is this?

• API-change
• BUG
• Improvement
• Documentation
• Feature
• Test and CI
• Code Refactoring

Which issue(s) this PR fixes:

issue ##21713

What this PR does / why we need it:

fix prints

---

PR Type

Bug fix

---

Description

• Fix conditional logic in partition state handling

• Remove error check from partition state condition

---

Changes diagram

flowchart LR
  A["getPartitionState method"] --> B["Conditional check fix"]
  B --> C["Remove error condition"]
  C --> D["Cleaner partition state handling"]

Loading

---

Changes walkthrough 📝

	Relevant files
Bug fix	txn_table.go Fix partition state conditional logic                                        pkg/vm/engine/disttae/txn_table.go Modified conditional statement in getPartitionState method Removed || err != nil from partition state check condition Simplified logic to only check if partition state is not nil +1/-1

---

Need help?

Type /help how to ... in the comments thread for any questions about Qodo Merge usage.

Check out the documentation for more information.

[qodo-merge-pro]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

🎫 Ticket compliance analysis ✅ 21713 - PR Code Verified Compliant requirements: • Clean the workspace to make it more simple, efficient, and manageable (by removing unnecessary error condition check) Requires further human verification: • Whether this specific change contributes meaningfully to overall workspace cleanliness goal

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Logic Error The condition was changed from checking both ps != nil || err != nil to only ps != nil. If err != nil but ps == nil, the code will now take the else branch and call ps.GetDuration() on a nil pointer, causing a panic. if ps != nil { start, end = ps.GetDuration()

[qodo-merge-pro]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
Possible issue	Handle error from function call The error handling logic has been removed but the error is still not being handled. If getOrCreateSnapPartBy returns an error, it should be handled appropriately rather than ignored. Consider checking the error and handling it properly. pkg/vm/engine/disttae/txn_table.go [2044-2048] if ps != nil { start, end = ps.GetDuration() msg = "Txn-Table-GetSSPS-Succeed" +} else if err != nil { + logger = logutil.Error + // Handle error appropriately } else { logger = logutil.Error Apply / Chat Suggestion importance[1-10]: 8 __ Why: The suggestion correctly identifies that the PR, while fixing a potential panic, introduces an issue where the err variable from getOrCreateSnapPartBy is completely ignored, which could mask underlying problems.	Medium
More