docs(cli): clarify logging for readiness timeout warnings by sumerchoudhary78 · Pull Request #1826 · lexmount/moli · GitHub
Skip to content

docs(cli): clarify logging for readiness timeout warnings - #1826

Merged
ldm0 merged 1 commit into
lexmount:mainfrom
sumerchoudhary78:fix/cli-surface-best-effort-readiness-timeout
Oct 22, 2026
Merged

ldm0 merged 1 commit into
lexmount:mainfrom
sumerchoudhary78:fix/cli-surface-best-effort-readiness-timeout

Conversation

@sumerchoudhary78

@sumerchoudhary78 sumerchoudhary78 commented Oct 21, 2026 •

Copy link
Copy Markdown
Contributor

The moli fetch --timeout help promises a warning even though fetch disables diagnostic logs by default.

Clarify that network-idle and DOM-stable timeouts return the current page, and point users to --log-level warn to display the timeout warnings.

Validation:

  • cargo fmt --all
  • cargo clippy --workspace --all-targets --all-features -- -D warnings
  • cargo nextest run --no-fail-fast: 20,530 passed, 18 skipped
  • Checked the rendered moli fetch --help output for the timeout guidance.

@ldm0
ldm0 self-requested a review October 21, 2026 12:21
@sumerchoudhary78
sumerchoudhary78 force-pushed the fix/cli-surface-best-effort-readiness-timeout branch from 65018fd to 8d9e915 Compare October 21, 2026 14:36
@sumerchoudhary78

Copy link
Copy Markdown
Contributor Author

Explain that network-idle and DOM-stable timeouts return the current page,
and point to --log-level warn for timeout warnings.

Co-authored-by: ldm0 <ldm2993593805@163.com>
@ldm0
ldm0 force-pushed the fix/cli-surface-best-effort-readiness-timeout branch from 83b7493 to e3e61ed Compare October 22, 2026 13:13
@ldm0 ldm0 changed the title fix(cli): report best-effort readiness timeouts on stderr docs(cli): clarify logging for readiness timeout warnings Oct 22, 2026
@ldm0
ldm0 merged commit 420e054 into lexmount:main Oct 22, 2026
1 of 10 checks passed
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.

2 participants