Use Debug instead of Info when manifest fetch cancelled

[Jack251970]

Follow on with #3975

[gitstream-cm]

🥷 Code experts: no user but you matched threshold 10

Jack251970 has most 👩‍💻 activity in the files.
Jack251970 has most 🧠 knowledge in the files.

See details

Flow.Launcher.Core/ExternalPlugins/CommunityPluginSource.cs

Activity based on git-commit:

	Jack251970
SEP
AUG
JUL
JUN
MAY
APR	61 additions & 39 deletions

Knowledge based on git-blame:
Jack251970: 45%

✨ Comment /gs review for LinearB AI review. Learn how to automate it here.

[gitstream-cm]

Be a legend 🏆 by adding a before and after screenshot of the changes you made, especially if they are around UI/UX.

[coderabbitai]

📝 Walkthrough

Walkthrough

Adjusted logging level for cancellation in CommunityPluginSource.FetchAsync: OperationCanceledException when the token is canceled is now logged at Debug instead of Info. No control-flow or public API changes.

Changes

Cohort / File(s)	Summary
Logging level adjustment Flow.Launcher.Core/ExternalPlugins/CommunityPluginSource.cs	In FetchAsync, changed cancellation catch block to log at Debug level instead of Info; returns null unchanged; no signature or behavior changes beyond log verbosity.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Catch scary exception, print friendly log #3975 — Also modifies cancellation handling and logging in CommunityPluginSource.FetchAsync, directly overlapping the same code path.

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description Check	❓ Inconclusive	The description "Follow on with #3975" shows the PR is related to a previous change but does not describe what was changed, why, or how it was tested, so it is too vague to be useful on its own. Because it provides only linkage and no substantive summary, it is insufficient under the "very vague or generic" criterion.	Request the author to expand the PR description to briefly state what was changed (e.g., changed cancellation log level from Info to Debug and the file/function affected), the rationale for the change, any impact or risk, and reference how this follows on from PR #3975 so reviewers can evaluate the change without inspecting all files.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title "Use Debug instead of Info" clearly and concisely reflects the primary change in the changeset, which is lowering the log level for cancellation handling from Info to Debug in FetchAsync (Flow.Launcher.Core/ExternalPlugins/CommunityPluginSource.cs). It is short, focused, and relevant for a reviewer scanning PR titles. While accurate, it could be slightly more specific by naming the file or function for extra context.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

✨ Finishing touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch improve_log

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

Flow.Launcher.Core/ExternalPlugins/CommunityPluginSource.cs (1)

76-80: Downgrading cancellation to Debug is correct; minor spelling nit.

Change “cancelled” → “canceled” to match .NET spelling. Search found no remaining API.LogInfo cancellation logs.

-                API.LogDebug(ClassName, $"Fetching from {ManifestFileUrl} was cancelled by caller.");
+                API.LogDebug(ClassName, $"Fetching from {ManifestFileUrl} was canceled by caller.");

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1689571 and 7a5e55e.

📒 Files selected for processing (1)

• Flow.Launcher.Core/ExternalPlugins/CommunityPluginSource.cs (1 hunks)

🧰 Additional context used

🧠 Learnings (1)

📚 Learning: 2025-07-06T12:21:37.947Z

Learnt from: Jack251970
PR: Flow-Launcher/Flow.Launcher#3572
File: Flow.Launcher/App.xaml.cs:214-216
Timestamp: 2025-07-06T12:21:37.947Z
Learning: In Flow Launcher, the UpdatePluginManifestAsync method in PluginsManifest.cs already has comprehensive internal try-catch handling that logs exceptions and returns false on failure rather than throwing, making external try-catch wrappers unnecessary.

Applied to files:

• Flow.Launcher.Core/ExternalPlugins/CommunityPluginSource.cs

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: gitStream.cm
• GitHub Check: build