github-starred/ollama
2
0
Fork 0
mirror of https://github.com/ollama/ollama.git synced 2026-05-08 17:49:24 -05:00
Code Issues 14.5k Packages Projects Releases 122 Wiki Activity

[PR #15946] docs(cmd/serve): list OLLAMA_DEBUG_LOG_REQUESTS in serve --help #77665

New Issue
Open
opened 2026-05-05 10:20:28 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-05-05 10:20:28 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/ollama/ollama/pull/15946
Author: @Anai-Guo
Created: 5/3/2026
Status: 🔄 Open

Base: main ← Head: fix/serve-help-debug-log-requests

📝 Commits (1)

  • a75af3f docs(cmd/serve): list OLLAMA_DEBUG_LOG_REQUESTS in serve --help

📊 Changes

1 file changed (+1 additions, -0 deletions)

View changed files

📝 cmd/cmd.go (+1 -0)

📄 Description

Summary

OLLAMA_DEBUG_LOG_REQUESTS=1 is a supported env var (added in #14106) that turns on request-body logging and curl-replay-command emission for inference requests. It's registered in envconfig/config.go and consumed by server/inference_request_log.go, but it was not in the env-var list rendered by ollama serve --help, so users had no CLI-discoverable hint that it exists.

This PR adds it to the serveCmd env-doc block in cmd/cmd.go, placed right after OLLAMA_DEBUG since the two are conceptually paired (both control debug instrumentation).

After this change, ollama serve --help will include the line:

OLLAMA_DEBUG_LOG_REQUESTS  Log inference request bodies and replay curl commands to a temp directory

(description text comes from the existing registration in envconfig/config.go:308).

Why

Without this entry, the only way to learn about OLLAMA_DEBUG_LOG_REQUESTS is reading source or finding the original PR — which is exactly what the reporter in #15945 had to do. Listing every supported env var in --help is the existing convention; this just closes the gap.

Test plan

  • git diff shows a single +1/-0 change to cmd/cmd.go
  • go build ./... passes (CI)
  • ollama serve --help includes OLLAMA_DEBUG_LOG_REQUESTS between OLLAMA_DEBUG and OLLAMA_HOST

Fixes #15945

🤖 Generated with Claude Code

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/ollama/ollama/pull/15946 **Author:** [@Anai-Guo](https://github.com/Anai-Guo) **Created:** 5/3/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `fix/serve-help-debug-log-requests` --- ### 📝 Commits (1) - [`a75af3f`](https://github.com/ollama/ollama/commit/a75af3fcf93838049df645090ee8b3cd7cb02433) docs(cmd/serve): list OLLAMA_DEBUG_LOG_REQUESTS in serve --help ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `cmd/cmd.go` (+1 -0) </details> ### 📄 Description ## Summary `OLLAMA_DEBUG_LOG_REQUESTS=1` is a supported env var (added in #14106) that turns on request-body logging and curl-replay-command emission for inference requests. It's registered in `envconfig/config.go` and consumed by `server/inference_request_log.go`, but it was not in the env-var list rendered by `ollama serve --help`, so users had no CLI-discoverable hint that it exists. This PR adds it to the `serveCmd` env-doc block in `cmd/cmd.go`, placed right after `OLLAMA_DEBUG` since the two are conceptually paired (both control debug instrumentation). After this change, `ollama serve --help` will include the line: ``` OLLAMA_DEBUG_LOG_REQUESTS Log inference request bodies and replay curl commands to a temp directory ``` (description text comes from the existing registration in `envconfig/config.go:308`). ## Why Without this entry, the only way to learn about `OLLAMA_DEBUG_LOG_REQUESTS` is reading source or finding the original PR — which is exactly what the reporter in #15945 had to do. Listing every supported env var in `--help` is the existing convention; this just closes the gap. ## Test plan - [x] `git diff` shows a single +1/-0 change to `cmd/cmd.go` - [ ] `go build ./...` passes (CI) - [ ] `ollama serve --help` includes `OLLAMA_DEBUG_LOG_REQUESTS` between `OLLAMA_DEBUG` and `OLLAMA_HOST` Fixes #15945 🤖 Generated with [Claude Code](https://claude.com/claude-code) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-05-05 10:20:28 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
amd
api
app
bug
build
cli
cloud
compatibility
context-length
create
docker
documentation
embeddings
feature request
feedback wanted
good first issue
gpt-oss
gpu
harmony
help wanted
image
install
intel
js
launch
linux
macos
memory
mlx
model
needs more info
networking
nvidia
ollama.com
performance
pull-request
Mirrored from GitHub Pull Request
 python
question
registry
rendering
thinking
tools
top
vulkan
windows
wsl
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/ollama#77665
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?