You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're getting a lot of new developers, and we have a lot of custom tools. Add Guide pages for all of the ones new developers may want to interact with. Also add expanded top level doccomments to all binaries. Also update and expand a few more general Guide pages.
Also remove the code/guide mapping table in the SKILL, it was out of date and does not appear to be working. Just tell AI to scan the guide instead.
This adds a link to ../reference/openvmm/binary_lifecycle.md, but that file is not present in Guide/src/reference/openvmm, so the new Guide page renders a broken link. Either add the referenced page and include it in SUMMARY.md, or remove this link and point readers only to the existing openvmm/run.md page.
The [OpenVMM binary lifecycle](../reference/openvmm/binary_lifecycle.md)
describes what that executable links, how it resolves a command line into a VM,
and how to diagnose startup and shutdown. For practical launch commands, begin
with [Running OpenVMM](./openvmm/run.md).
The reason will be displayed to describe this comment to others. Learn more.
🟢 Approval recommended
The reviewed findings are minor documentation nits and do not block approval.
Review details
Suppressed comments (11)
Guide/src/SUMMARY.md:50
This section now has real child pages, but the parent remains an empty placeholder link. In the generated Guide navigation, Performance Benchmarks is therefore not clickable and the existing perf.md page is not the section landing page; link the heading to the performance overview.
- [Performance Benchmarks]()
Guide/src/dev_guide/tests/perf.md:99
This replacement drops the only Guide documentation for the memory benchmark's emitted metrics (memory_rss_kib, memory_private_kib, memory_vmm_overhead_kib, memory_process_count, and memory_pss_kib), even though petri/burette/src/tests/memory.rs:147-170 still produces them. Please retain a metric list under the memory section so developers can interpret the JSON reports; the new network paragraph does not cover those fields.
The report records TCP throughput and UDP packet-rate metrics. Keep the NIC,
network backend, host CPU placement, and MTU constant between compared runs.
Each wrapped source/rustdoc reference in this file has the same stray leading | before Docs:. It renders literal pipe characters throughout the page instead of the intended label; remove the pipe from this line and the corresponding wrapped labels below.
The leading | is left over from the previous same-line Source code | Docs formatting. Because Docs: is now on its own line, Markdown renders this character literally before the label; remove it so the reference renders as normal text.
These newly split source/doc reference blocks retain the table separator from the old one-line form. In this context the line is not a table row, so the leading | renders as stray text in the guide. Remove the leading pipe from each Docs: line (or keep the reference on one line).
The split reference block retains a leading table pipe even though these lines are not a Markdown table, so the guide renders a stray | before Docs:. Remove the leading pipe here and in the other similarly split reference blocks.
The split reference block retains a leading table pipe even though these lines are not a Markdown table, so the guide renders a stray | before Docs:. Remove the leading pipe here and in the other similarly split reference blocks.
The split reference block retains a leading table pipe even though these lines are not a Markdown table, so the guide renders a stray | before Docs:. Remove the leading pipe here and in the other similarly split reference blocks.
The split reference block retains a leading table pipe even though these lines are not a Markdown table, so the guide renders a stray | before Docs:. Remove the leading pipe here and in the other similarly split reference blocks.
The split reference block retains a leading table pipe even though these lines are not a Markdown table, so the guide renders a stray | before Docs:. Remove the leading pipe here and in the other similarly split reference blocks.
The split reference block retains a leading table pipe even though these lines are not a Markdown table, so the guide renders a stray | before Docs:. Remove the leading pipe here and in the other similarly split reference blocks.
The split reference block retains a leading table pipe even though these lines are not a Markdown table, so the guide renders a stray | before Docs:. Remove the leading pipe here and in the other similarly split reference blocks.
This leading | is left over from the former single-line Source code | Docs layout. Because the preceding line is not a table row, Markdown renders this as a literal pipe instead of a separator, so the reference block displays incorrectly. Remove the leading pipe (or keep both labels on one line).
TestConfig derives clap::ValueEnum without explicit names, so this value is exposed as ak-cert-request-failure-and-retry (kebab-case), not the Rust variant spelling shown here. The documented command currently fails argument parsing.
Fix malformed Docs separators throughout the architecture page
The leading | is rendered as literal text rather than the separator used by the surrounding architecture pages, so the Docs label is malformed. Put the separator at the end of the source link, as in Guide/src/reference/architecture/openvmm/mesh.md:15-17.
This issue also appears in the following locations of the same file:
The leading | is rendered as literal text rather than the separator used by the surrounding architecture pages, so the Docs label is malformed. Put the separator at the end of the source link, as in Guide/src/reference/architecture/openvmm/mesh.md:15-17.
The reason will be displayed to describe this comment to others. Learn more.
Copilot review overview
🔵 Needs a closer look
Documentation inaccuracies and incomplete binary coverage remain.
Review effort: Lite Findings: None
Previously missed (2)
In code that hasn't changed since last review
Memory metric definitions were removed from the documentation
Guide/src/dev_guide/tests/perf.md:98
This replacement removes the definitions of the memory metrics while the rest of the page still tells developers to compare memory overhead. burette continues to emit memory_rss_kib, memory_private_kib, memory_vmm_overhead_kib, memory_pss_kib, and memory_process_count (see petri/burette/src/tests/memory.rs), so please restore these definitions or link to an authoritative schema.
TestConfig example uses an invalid non-kebab-case value
TestConfig derives Clap's default ValueEnum names, which are kebab-case, so AkCertRequestFailureAndRetry is not an accepted value for --test-config. This example exits with an invalid-value error; use the generated kebab-case value instead.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We're getting a lot of new developers, and we have a lot of custom tools. Add Guide pages for all of the ones new developers may want to interact with. Also add expanded top level doccomments to all binaries. Also update and expand a few more general Guide pages.
Also remove the code/guide mapping table in the SKILL, it was out of date and does not appear to be working. Just tell AI to scan the guide instead.