handle: enable VF info collection by default for pkgHandle

[zeeke]

The package-level handle (pkgHandle) was initialized without collectVFInfo, causing package-level functions like LinkByName to no longer collect Virtual Function information. This restores the previous default behavior.

Summary by CodeRabbit

• Improvements
  • Virtual Function (VF) information collection is now enabled by default, providing enhanced visibility into network interface details. The existing option to disable this collection remains available if needed.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: d9c89483-0e02-4762-96a0-c99e17eed775

📥 Commits

Reviewing files that changed from the base of the PR and between ddba687 and c9b22c9.

📒 Files selected for processing (1)

• handle_linux.go

---

📝 Walkthrough

Walkthrough

The default initialization of the package-level pkgHandle variable is modified to enable VF information collection by default instead of using an empty Handle. This single-line change affects the default behavior of VF info gathering for netlink handle operations.

Changes

Cohort / File(s)	Summary
VF Info Collection Default handle_linux.go	Changed default pkgHandle initialization to enable collectVFInfo: true, modifying the default behavior of VF information collection across netlink handle usage.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~5 minutes

Poem

🐰 A tiny change, but mighty in its way,
Default VF info now collected each day,
One line adjusted, behavior refined,
Better data gathering, peace of mind! 💫

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and specifically summarizes the main change: enabling VF info collection by default for the package-level handle variable.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

📝 Coding Plan

• Generate coding plan for human review comments

---

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.}

Tip

You can enable review details to help with troubleshooting, context usage and more.

Enable the reviews.review_details setting to include review details such as the model used, the time taken for each step and more in the review comments.

[ti-mo]

I just filed #1174 which should address this by making the default value useful/backwards-compatible. Handle.DisableVFInfoCollection() is pretty painful to use as well. Note that it's pending the merge of #1170 so it may take a bit longer to land.

[aboch]

Agree with @ti-mo, lets wait for his PR to move this extra flag under the options