This file was inconsistent with the other files in our course.
I don’t actually know if both work, but if not, we should consider
erroring out to ensure consistency going forward.
The most significant change for users is that the search index is
downloaded on demand.
For us as a project, it’s good to see the server used by `mdbook serve`
change from `warp` to `asum`: the former hadn’t been updated in a while,
leading us to have old dependencies in our `Cargo.lock`.
I also ran `cargo update` to further unify the versions of our
dependencies. This shrunk `cargo tree --duplicates` a little more.
---------
Co-authored-by: Michael Kerscher <kerscher@google.com>
## What does this PR do?
This PR extends the existing `format` job in
`.github/workflows/build.yml` to
**check Rust formatting with nightly `rustfmt`**:
**Closes #2794**
I had Google Gemini do this Turkish translation again.
I gave Gemini my previous translations and the part I wanted it to
translate as two separate PO files. As a prompt, I told it to stick to
my terminology and methodology. Then, I went through the output that
Gemini produced one by one. I estimated that I corrected a small
percentage of the entire translation, around 5-10% (for this pr).
NOTE: I opened this branch in this PR via
"Enes1313:tr-translation-of-day-2-morning" . This PR can be reviewed
when the PR for #2809 is finished.
Part of #500
I asked Gemini to review the English for inconsistencies and grammar
mistakes. This is the result and I hope it's useful!
As a non-native speaker, it is hard for me to evaluate the finer
details, so let me know if you would like to see changes (or even
better: make them directly in the PR with the suggestion function).
---------
Co-authored-by: Dmitri Gribenko <gribozavr@gmail.com>
I asked Gemini to review the English for inconsistencies and grammar
mistakes. This is the result and I hope it's useful!
As a non-native speaker, it is hard for me to evaluate the finer
details, so let me know if you would like to see changes (or even
better: make them directly in the PR with the suggestion function).
---------
Co-authored-by: Dmitri Gribenko <gribozavr@gmail.com>
I asked Gemini to review the English for inconsistencies and grammar
mistakes. This is the result and I hope it's useful!
As a non-native speaker, it is hard for me to evaluate the finer
details, so let me know if you would like to see changes (or even
better: make them directly in the PR with the suggestion function).
---------
Co-authored-by: Dmitri Gribenko <gribozavr@gmail.com>
I asked Gemini to review the English for inconsistencies and grammar
mistakes. This is the result and I hope it's useful!
As a non-native speaker, it is hard for me to evaluate the finer
details, so let me know if you would like to see changes (or even
better: make them directly in the PR with the suggestion function).
---------
Co-authored-by: Dmitri Gribenko <gribozavr@gmail.com>
I asked Gemini to review the English for inconsistencies and grammar
mistakes. This is the result and I hope it's useful!
As a non-native speaker, it is hard for me to evaluate the finer
details, so let me know if you would like to see changes (or even
better: make them directly in the PR with the suggestion function).
---------
Co-authored-by: Dmitri Gribenko <gribozavr@gmail.com>
I asked Gemini to review the English for inconsistencies and grammar
mistakes. This is the result and I hope it's useful!
As a non-native speaker, it is hard for me to evaluate the finer
details, so let me know if you would like to see changes (or even
better: make them directly in the PR with the suggestion function).
---------
Co-authored-by: Dmitri Gribenko <gribozavr@gmail.com>
I asked Gemini to review the English for inconsistencies and grammar
mistakes. This is the result and I hope it's useful!
As a non-native speaker, it is hard for me to evaluate the finer
details, so let me know if you would like to see changes (or even
better: make them directly in the PR with the suggestion function).
---------
Co-authored-by: Dmitri Gribenko <gribozavr@gmail.com>
I asked Gemini to review the English for inconsistencies and grammar
mistakes. This is the result and I hope it's useful!
As a non-native speaker, it is hard for me to evaluate the finer
details, so let me know if you would like to see changes (or even
better: make them directly in the PR with the suggestion function).
I asked Gemini to review the English for inconsistencies and grammar
mistakes. This is the result and I hope it's useful!
As a non-native speaker, it is hard for me to evaluate the finer
details, so let me know if you would like to see changes (or even
better: make them directly in the PR with the suggestion function).
I asked Gemini to review the English for inconsistencies and grammar
mistakes. This is the result and I hope it's useful!
As a non-native speaker, it is hard for me to evaluate the finer
details, so let me know if you would like to see changes (or even
better: make them directly in the PR with the suggestion function).
---------
Co-authored-by: Dmitri Gribenko <gribozavr@gmail.com>
I asked Gemini to review the English for inconsistencies and grammar
mistakes. This is the result and I hope it's useful!
As a non-native speaker, it is hard for me to evaluate the finer
details, so let me know if you would like to see changes (or even
better: make them directly in the PR with the suggestion function).
---------
Co-authored-by: Dmitri Gribenko <gribozavr@gmail.com>
I asked Gemini to review the English for inconsistencies and grammar
mistakes. This is the result and I hope it's useful!
As a non-native speaker, it is hard for me to evaluate the finer
details, so let me know if you would like to see changes (or even
better: make them directly in the PR with the suggestion function).
I asked Gemini to review the English for inconsistencies and grammar
mistakes. This is the result and I hope it's useful!
As a non-native speaker, it is hard for me to evaluate the finer
details, so let me know if you would like to see changes (or even
better: make them directly in the PR with the suggestion function).
---------
Co-authored-by: Dmitri Gribenko <gribozavr@gmail.com>
I asked Gemini to review the English for inconsistencies and grammar
mistakes. This is the result and I hope it's useful!
As a non-native speaker, it is hard for me to evaluate the finer
details, so let me know if you would like to see changes (or even
better: make them directly in the PR with the suggestion function).
I asked Gemini to review the English for inconsistencies and grammar
mistakes. This is the result and I hope it's useful!
As a non-native speaker, it is hard for me to evaluate the finer
details, so let me know if you would like to see changes (or even
better: make them directly in the PR with the suggestion function).
I asked Gemini to review the English for inconsistencies and grammar
mistakes. This is the result.
As a non-native speaker, it is hard for me to evaluate the finer details
of this, so let me know if you would like to see changes (or even
better:
make them directly in the PR with the suggestion function).
I asked Gemini to review the English for inconsistencies and grammar
mistakes. This is the result and I hope it's useful!
As a non-native speaker, it is hard for me to evaluate the finer
details, so let me know if you would like to see changes (or even
better: make them directly in the PR with the suggestion function).
---------
Co-authored-by: Dmitri Gribenko <gribozavr@gmail.com>
I asked Gemini to review the English for inconsistencies and grammar
mistakes. This is the result and I hope it's useful!
As a non-native speaker, it is hard for me to evaluate the finer
details, so let me know if you would like to see changes (or even
better: make them directly in the PR with the suggestion function).
I asked Gemini to review the English for inconsistencies and grammar
mistakes. This is the result and I hope it's useful!
As a non-native speaker, it is hard for me to evaluate the finer
details, so let me know if you would like to see changes (or even
better: make them directly in the PR with the suggestion function).
I asked Gemini to review the English for inconsistencies and grammar
mistakes. This is the result and I hope it's useful!
As a non-native speaker, it is hard for me to evaluate the finer
details, so let me know if you would like to see changes (or even
better: make them directly in the PR with the suggestion function).
I asked Gemini to review the English for inconsistencies and grammar
mistakes. This is the result and I hope it's useful!
As a non-native speaker, it is hard for me to evaluate the finer
details, so let me know if you would like to see changes (or even
better: make them directly in the PR with the suggestion function).
Bumps the cargo group with 1 update in the / directory:
[h2](https://github.com/hyperium/h2).
Updates `h2` from 0.3.26 to 0.3.27
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a
href="https://github.com/hyperium/h2/blob/v0.3.27/CHANGELOG.md">h2's
changelog</a>.</em></p>
<blockquote>
<h1>0.3.27 (July 11, 2025)</h1>
<ul>
<li>Fix notifying wakers when detecting local stream errors.</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a
href="f6237accb3"><code>f6237ac</code></a>
v0.3.27</li>
<li><a
href="f61332ed48"><code>f61332e</code></a>
refactor: change local reset counter to use type system more</li>
<li><a
href="3f1a8e34cd"><code>3f1a8e3</code></a>
style: fix anonymous lifetime syntax</li>
<li><a
href="778aa7eba9"><code>778aa7e</code></a>
fix: notify_recv after send_reset() in reset_on_recv_stream_err() to
ensure l...</li>
<li><a
href="be10b774f0"><code>be10b77</code></a>
ci: pin more deps for MSRV job (<a
href="https://redirect.github.com/hyperium/h2/issues/817">#817</a>)</li>
<li><a
href="c0d9febc18"><code>c0d9feb</code></a>
ci: pin deps for MSRV</li>
<li><a
href="5ccd9cfb10"><code>5ccd9cf</code></a>
lints: fix unexpected cfgs warnings</li>
<li><a
href="e6e3e9c87f"><code>e6e3e9c</code></a>
fix: return a WriteZero error if frames cannot be written (<a
href="https://redirect.github.com/hyperium/h2/issues/783">#783</a>)</li>
<li>See full diff in <a
href="https://github.com/hyperium/h2/compare/v0.3.26...v0.3.27">compare
view</a></li>
</ul>
</details>
<br />
[](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
Dependabot will resolve any conflicts with this PR as long as you don't
alter it yourself. You can also trigger a rebase manually by commenting
`@dependabot rebase`.
[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits
that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after
your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating
it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all
of the ignore conditions of the specified dependency
- `@dependabot ignore <dependency name> major version` will close this
group update PR and stop Dependabot creating any more for the specific
dependency's major version (unless you unignore this specific
dependency's major version or upgrade to it yourself)
- `@dependabot ignore <dependency name> minor version` will close this
group update PR and stop Dependabot creating any more for the specific
dependency's minor version (unless you unignore this specific
dependency's minor version or upgrade to it yourself)
- `@dependabot ignore <dependency name>` will close this group update PR
and stop Dependabot creating any more for the specific dependency
(unless you unignore this specific dependency or upgrade to it yourself)
- `@dependabot unignore <dependency name>` will remove all of the ignore
conditions of the specified dependency
- `@dependabot unignore <dependency name> <ignore condition>` will
remove the ignore condition of the specified dependency and ignore
conditions
You can disable automated security fix PRs for this repo from the
[Security Alerts
page](https://github.com/google/comprehensive-rust/network/alerts).
</details>
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
**I had Google Gemini do this Turkish translation.**
I gave Gemini my previous translations and the part I wanted it to
translate as two separate PO files. As a prompt, I told it to stick to
my terminology and methodology. Then, I went through the output that
Gemini produced one by one. I estimated that I corrected a small
percentage of the entire translation, around 1-5%.
Part of #500
Bumps the patch group in /src/bare-metal/aps/examples with 2 updates:
arm-pl011-uart and [bitflags](https://github.com/bitflags/bitflags).
Updates `arm-pl011-uart` from 0.3.1 to 0.3.2
Updates `bitflags` from 2.9.1 to 2.9.3
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps the patch group in /src/exercises/bare-metal/rtc with 3 updates:
arm-gic, arm-pl011-uart and
[bitflags](https://github.com/bitflags/bitflags).
Updates `arm-gic` from 0.6.0 to 0.6.1
Updates `arm-pl011-uart` from 0.3.1 to 0.3.2
Updates `bitflags` from 2.9.1 to 2.9.3
Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
I don't know how, but the existing link points to an article that
doesn't actually discuss the course. I updated it to the link I
originally had in mind now.
This section covers both references and slices, but the exercise focuses
on references. This speaker note briefly discusses the option to use
slices instead, and a cost of doing so.
As mentioned in #2803 , if someone has the `cargo-xtask` crate installed
in their system, they will get a deprecation warning every time they run
one of the `cargo xtask ...` commands.
The only way to encounter the deprecation warning is by someone
intentionally running `cargo install cargo-xtask`. To mitigate this we
are adding a note in the README to explain the usage of xtask in the
project and that it is not a package to be installed.
A previous PR #2804 addressed this by adding aliases for each xtask
subcommand and deprecating the use of `cargo xtask` as a prefix for
these commands. While this fixes the warning, the disadvantage is that
it doesn't allow one to run `cargo xtask` to view all available
subcommands in the project with help instructions. Also the help message
that appears if one does e.g. `cargo install-tools --help` still refers
to `xtask` which might be confusing for the user. So overall it's a
better user experience to keep the usage as `cargo xtask <subcommand>`.
Also the use of `cargo xtask` is a pattern used in other large rust
projects (see some examples
[here](https://github.com/matklad/cargo-xtask?tab=readme-ov-file#external-examples)).
Co-authored-by: Eric Githinji <egithinji@google.com>
