Skip to content

Coverage: guard missing proto overrides + remove navigation (#5126)#5143

Open
btshrewsbury-viam wants to merge 1 commit into
mainfrom
fix/coverage-navigation-and-missing-overrides
Open

Coverage: guard missing proto overrides + remove navigation (#5126)#5143
btshrewsbury-viam wants to merge 1 commit into
mainfrom
fix/coverage-navigation-and-missing-overrides

Conversation

@btshrewsbury-viam

Copy link
Copy Markdown
Collaborator

Fixes two of the crashes stacked behind the gripper KeyError (#5139), both surfaced once that one was fixed.

(a) Guard missing proto-description overrides

Proto descriptions come from override files (static/include/.../overrides/protos/{resource}.{proto}.md), but the description-reading open() wasn't guarded by the os.path.isfile check the content-writing branch already uses. Guard it and fall back to a blank description with a WARNING (so a genuinely-missing override — an authoring gap — is still surfaced, not silently blanked). Same spirit as #5139.

(b) Fully remove navigation

#5067 removed the navigation docs section (redirect to motion-planning) and deleted its override files, but left navigation in sdk_protos_map.csv and the generator's services list — so coverage still tried to document it and crashed on the deleted navigation.GetMode.md. Removed navigation from the CSV, the services list, the proto-URL map, and the service anchor logic. (Removing only the CSV rows would leave navigation still scraped and flag its methods as "unused"; dropping it from services stops that.)

Verification

Ran the generator locally: completes with no crash (was KeyError then FileNotFoundError), and navigation no longer appears. Dispatching check-methods on this branch to confirm in CI (Python 3.9) — grading on the coverage step log (job is always green via continue-on-error).

Honest scope — does NOT close #5126

With the crashes gone, the check now reports ~110 pre-existing "unused" warnings it had been masking (SDK methods not mapped in the CSV). Those are the real remaining work — each a document-vs-ignore decision — and are handled separately, not silenced to force green.

Refs #5126

🤖 Generated with Claude Code

Two of the crashes that were stacked behind the gripper KeyError (#5139), both
surfaced once that one was fixed:

(a) Missing proto-description override files crashed the generator. Proto
descriptions come from override files (static/include/.../overrides/protos/
{resource}.{proto}.md), but the description-reading open() was not guarded by the
os.path.isfile check the content-writing branch already uses. Guard it and fall
back to a blank description so a missing override reports gracefully instead of
crashing (same spirit as #5139).

(b) Fully remove navigation. #5067 removed the navigation docs section (redirected
to motion-planning) and deleted its override files, but left navigation in the
CSV and in the generator's services list, so coverage still tried to document it
and crashed on the deleted navigation.GetMode.md override. Remove navigation from
sdk_protos_map.csv, the `services` list, the proto-URL map, and the service anchor
logic. (Removing only the CSV rows would leave navigation still scraped and flag
its methods as "unused"; dropping it from the services list stops that.)

Verified by running the generator locally: it now completes with no crash
(previously KeyError then FileNotFoundError), and navigation no longer appears.

Note: this does not make check-methods green -- with the crashes gone, the check
now reports ~110 pre-existing "unused" warnings it had been masking (SDK methods
not mapped in the CSV). Each is a separate document-vs-ignore decision.

Refs #5126
@netlify

netlify Bot commented Jul 2, 2026

Copy link
Copy Markdown

Deploy Preview for viam-docs ready!

Name Link
🔨 Latest commit eaeb2a5
🔍 Latest deploy log https://app.netlify.com/projects/viam-docs/deploys/6a46d5a2774ad60008302b92
😎 Deploy Preview https://deploy-preview-5143--viam-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 39 (🟢 up 3 from production)
Accessibility: 100 (no change from production)
Best Practices: 100 (no change from production)
SEO: 92 (no change from production)
PWA: 70 (no change from production)
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

@viambot viambot added the safe to build This pull request is marked safe to build from a trusted zone label Jul 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

safe to build This pull request is marked safe to build from a trusted zone

Projects

None yet

Development

Successfully merging this pull request may close these issues.

CI failure: SDK method coverage

2 participants