Skip to content

Commit

Permalink
Deploying to gh-pages from @ bb1f36d 🚀
Browse files Browse the repository at this point in the history
  • Loading branch information
gavinleroy committed Sep 13, 2024
1 parent c276dc0 commit df714dc
Show file tree
Hide file tree
Showing 5 changed files with 8 additions and 2 deletions.
2 changes: 2 additions & 0 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -322,6 +322,8 @@ <h2 id="up-the-search-tree"><a class="header" href="#up-the-search-tree">Up the
<source alt="Bottom-Up Argus view" src="assets/axum-hello-server/bottom-up-start.mp4" type="video/mp4" />
</video>
<p>The above demonstrates that Argus identifies <code>Res: IntoResponse</code> as a root cause of the overall failure in addition to the second failure: <code>LoginAttempt: FromRequestParts&lt;_, _&gt;</code>. The note icon in the Bottom-Up view indicates that the two failures must be resolved together if you want to us the function as a handler.</p>
<p>It’s always important to <strong>read</strong> and <strong>understand</strong> the failing obligation(s) that Argus presents first in the Bottom Up view. These errors are the <em>leaves</em> of the search tree, in other words, the <em>root cause</em> of the overall error; if you satisfy these bounds, then the root bound will also be satisfied.</p>
<p>If additional failing bounds are present under “Other failures,” you need to only resolve a single set of these failures. Argus shows you the set it believes was your intent, but as the developer with intent double check for yourself that it makes sense.</p>
<video controls>
<source alt="Fix Future and IntoResponse" src="assets/axum-hello-server/async-fix-response.mp4" type="video/mp4" />
</video>
Expand Down
2 changes: 2 additions & 0 deletions print.html
Original file line number Diff line number Diff line change
Expand Up @@ -323,6 +323,8 @@ <h2 id="up-the-search-tree"><a class="header" href="#up-the-search-tree">Up the
<source alt="Bottom-Up Argus view" src="assets/axum-hello-server/bottom-up-start.mp4" type="video/mp4" />
</video>
<p>The above demonstrates that Argus identifies <code>Res: IntoResponse</code> as a root cause of the overall failure in addition to the second failure: <code>LoginAttempt: FromRequestParts&lt;_, _&gt;</code>. The note icon in the Bottom-Up view indicates that the two failures must be resolved together if you want to us the function as a handler.</p>
<p>It’s always important to <strong>read</strong> and <strong>understand</strong> the failing obligation(s) that Argus presents first in the Bottom Up view. These errors are the <em>leaves</em> of the search tree, in other words, the <em>root cause</em> of the overall error; if you satisfy these bounds, then the root bound will also be satisfied.</p>
<p>If additional failing bounds are present under “Other failures,” you need to only resolve a single set of these failures. Argus shows you the set it believes was your intent, but as the developer with intent double check for yourself that it makes sense.</p>
<video controls>
<source alt="Fix Future and IntoResponse" src="assets/axum-hello-server/async-fix-response.mp4" type="video/mp4" />
</video>
Expand Down
2 changes: 1 addition & 1 deletion searchindex.js

Large diffs are not rendered by default.

2 changes: 1 addition & 1 deletion searchindex.json

Large diffs are not rendered by default.

2 changes: 2 additions & 0 deletions trait-debugging-101.html
Original file line number Diff line number Diff line change
Expand Up @@ -322,6 +322,8 @@ <h2 id="up-the-search-tree"><a class="header" href="#up-the-search-tree">Up the
<source alt="Bottom-Up Argus view" src="assets/axum-hello-server/bottom-up-start.mp4" type="video/mp4" />
</video>
<p>The above demonstrates that Argus identifies <code>Res: IntoResponse</code> as a root cause of the overall failure in addition to the second failure: <code>LoginAttempt: FromRequestParts&lt;_, _&gt;</code>. The note icon in the Bottom-Up view indicates that the two failures must be resolved together if you want to us the function as a handler.</p>
<p>It’s always important to <strong>read</strong> and <strong>understand</strong> the failing obligation(s) that Argus presents first in the Bottom Up view. These errors are the <em>leaves</em> of the search tree, in other words, the <em>root cause</em> of the overall error; if you satisfy these bounds, then the root bound will also be satisfied.</p>
<p>If additional failing bounds are present under “Other failures,” you need to only resolve a single set of these failures. Argus shows you the set it believes was your intent, but as the developer with intent double check for yourself that it makes sense.</p>
<video controls>
<source alt="Fix Future and IntoResponse" src="assets/axum-hello-server/async-fix-response.mp4" type="video/mp4" />
</video>
Expand Down

0 comments on commit df714dc

Please sign in to comment.