Skip to content

feat(providers): add skip_ping support and upgrade nntppool to v4.5.0 - #388

Merged
javi11 merged 1 commit into
mainfrom
feat/nntppool-v4.5.0-skip-ping
Mar 5, 2026
Merged

feat(providers): add skip_ping support and upgrade nntppool to v4.5.0#388
javi11 merged 1 commit into
mainfrom
feat/nntppool-v4.5.0-skip-ping

Conversation

@javi11

@javi11 javi11 commented Mar 5, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Upgrades nntppool from v4.4.1 → v4.5.0, which adds the SkipPing field on Provider
  • Exposes skip_ping end-to-end (backend config, frontend types, provider modal UI)
  • Adds troubleshooting docs for users who hit DATE command errors when adding a provider

Changes

Backend

  • go.mod/go.sum: bump github.com/javi11/nntppool/v4 to v4.5.0
  • internal/config/manager.go: add SkipPing bool to ProviderConfig, map it in ToNNTPProvider(), and include it in providersFieldsEqual() so toggling the flag triggers a pool reload

Frontend

  • src/types/config.ts: add skip_ping to ProviderConfig, ProviderFormData, ProviderUpdateRequest, and ProviderCreateRequest
  • src/components/config/ProviderModal.tsx: add Skip server ping checkbox in the Options & Security section with descriptive helper text; initialized from existing provider in edit mode

Docs

  • docs/docs/5. Troubleshooting/common-issues.md: new "Date Error When Adding a Provider" section explaining the DATE ping issue and how to resolve it via YAML or UI

Test plan

  • Add a provider with skip_ping: true in config — pool starts without DATE ping errors
  • Toggle "Skip server ping" in the UI for a new or existing provider — value round-trips correctly
  • Without the flag, existing behaviour is unchanged
  • go build ./... passes
  • bun run check && bun run build passes

🤖 Generated with Claude Code

Bumps nntppool from v4.4.1 to v4.5.0 which introduces the SkipPing
field on Provider. Exposes the option end-to-end so users with servers
that don't support the DATE NNTP command can bypass the startup ping
check.

- go.mod/go.sum: upgrade nntppool v4 to v4.5.0
- internal/config: add SkipPing to ProviderConfig, map it in
  ToNNTPProvider(), and include it in providersFieldsEqual() so a
  config change triggers a pool reload
- frontend/types: add skip_ping to ProviderConfig, ProviderFormData,
  ProviderUpdateRequest, and ProviderCreateRequest
- frontend/ProviderModal: add "Skip server ping" checkbox with helper
  text in the Options & Security section
- docs: add "Date Error When Adding a Provider" troubleshooting section

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@javi11
javi11 merged commit f8c3887 into main Mar 5, 2026
2 checks passed
@javi11
javi11 deleted the feat/nntppool-v4.5.0-skip-ping branch March 5, 2026 22:29
yoshitaka420 pushed a commit to yoshitaka420/altmount that referenced this pull request Jun 1, 2026
…kipsilabs#388)

Bumps nntppool from v4.4.1 to v4.5.0 which introduces the SkipPing
field on Provider. Exposes the option end-to-end so users with servers
that don't support the DATE NNTP command can bypass the startup ping
check.

- go.mod/go.sum: upgrade nntppool v4 to v4.5.0
- internal/config: add SkipPing to ProviderConfig, map it in
  ToNNTPProvider(), and include it in providersFieldsEqual() so a
  config change triggers a pool reload
- frontend/types: add skip_ping to ProviderConfig, ProviderFormData,
  ProviderUpdateRequest, and ProviderCreateRequest
- frontend/ProviderModal: add "Skip server ping" checkbox with helper
  text in the Options & Security section
- docs: add "Date Error When Adding a Provider" troubleshooting section

Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
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