-
Notifications
You must be signed in to change notification settings - Fork 40
pick develop/eagle to master #572
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
Changes from all commits
9271e9b
a26d1aa
b21ca87
4ad588e
4f640b7
bbdbd49
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
@@ -53,6 +53,13 @@ void DeviceCpu::setCpuInfo(const QMap<QString, QString> &mapLscpu, const QMap<QS | |||||||||||||||||||||||||||||||||||
| m_Name.replace(QRegularExpression("x [0-9]*$"), ""); | ||||||||||||||||||||||||||||||||||||
| qCDebug(appLog) << "CPU name after regex replacement: " << m_Name; | ||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||
| if (Common::specialComType == Common::kSpecialType5 || | ||||||||||||||||||||||||||||||||||||
| Common::specialComType == Common::kSpecialType6 || | ||||||||||||||||||||||||||||||||||||
| Common::specialComType == Common::kSpecialType7) { | ||||||||||||||||||||||||||||||||||||
| m_Frequency = m_Frequency.replace("2.189", "2.188"); | ||||||||||||||||||||||||||||||||||||
| m_MaxFrequency = m_MaxFrequency.replace("2189", "2188"); | ||||||||||||||||||||||||||||||||||||
| } | ||||||||||||||||||||||||||||||||||||
|
Comment on lines
+56
to
+61
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. suggestion (bug_risk): Consider making the frequency replacement more robust and avoiding the redundant assignment. In this block:
Suggested change
|
||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||
| // 获取逻辑数和core数 | ||||||||||||||||||||||||||||||||||||
| m_LogicalCPUNum = logicalNum; | ||||||||||||||||||||||||||||||||||||
| m_CPUCoreNum = coreNum; | ||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -22,7 +22,7 @@ class Common | |
| KLVV, | ||
| KLVU, | ||
| PGUV, | ||
| PGUX, | ||
| kSpecialType5, | ||
| kSpecialType6, | ||
| kSpecialType7, | ||
| kCustomType | ||
|
|
||
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.
issue: Introducing a 60s wait timeout may leave device updates incomplete without any handling.
Changing
waitForDonefrom infinite to 60s changes behavior: if the pool is still busy after 60s, we return and still setm_firstUpdatetofalse, treating the update as complete. For long-running updates, this can leave device info partially updated with no signal to the caller. Consider either making the timeout configurable, or explicitly handling a timeout (if the pool API supports it), e.g. by logging it, not clearingm_firstUpdate, retrying, or otherwise surfacing an error state.