Skip to content

Pin the Step06 documentation pages and wait longer for Ollama - #11

Merged
Laurianti merged 2 commits into
mainfrom
fix-step06-links-ollama-timeout
Oct 23, 2026
Merged

Laurianti merged 2 commits into
mainfrom
fix-step06-links-ollama-timeout

Conversation

@Laurianti

Copy link
Copy Markdown
Member

The Step06 samples download two pages of the Agent Framework documentation from the main branch of MicrosoftDocs/semantic-kernel-docs. On October 23 the pages were removed from main, and both samples stopped at the first download:

System.Net.Http.HttpRequestException: Response status code does not indicate success: 404 (Not Found).
  • Pin the documentation pages of Step06 to a commit (38519f5): the two URLs point to commit caf5bacd, the last one where main had the pages. The samples read the same content as before.
  • Wait up to 10 minutes for Ollama (3ab7216): the _Ollama samples built OllamaApiClient from a URI, so its HttpClient gave up after the default 100 seconds. On a CPU a qwen2.5:3b answer can take longer: in these runs, up to 2 min 36 s in Step06 and 4 min 1 s in Step07. The sample then stopped with a TaskCanceledException. Step06, Step07 and Step10 built the client the same way. All three now pass it an HttpClient with a 10-minute timeout.

Tested with Chroma 1.5.9 in Docker:

  • dotnet test: 10/10.
  • Before: both Step06 samples stop with the 404 at the first download.
  • After: AgentWithRAG_Step06_ChromaRAG with Microsoft Foundry answers the four questions and cites the pinned pages. The three _Ollama samples run to the end with qwen2.5:3b and nomic-embed-text. With the pinned pages but without the timeout change, Step06 Ollama stopped on the 100-second timeout in 3 runs out of 3.

@Laurianti
Laurianti merged commit 849dba7 into main Oct 23, 2026
1 check passed
@Laurianti
Laurianti deleted the fix-step06-links-ollama-timeout branch October 23, 2026 11:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant