Repository navigation
fix: give the theme commands a longer timeout - #45
Merged
Merged
Conversation
`theme available` and `theme install` make Fess reach the remote theme repository while handling the request, which regularly exceeds the 5 second default client timeout (CI failed with "Network error: timed out" on the available-themes test). Use a 60 second timeout for both.
The pull_request trigger was limited to main, so a pull request stacked on another branch got no checks. Drop the branch filter; pushes are still limited to main, so a branch push does not build twice.
This was referenced Oct 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
fessctl theme availableandtheme installmake the Fess server call the remote theme repository (and download the archive forinstall) while serving the request. The 5 second default client timeout is too short for that: the integration test foravailabletimed out on CI runners. Both commands now use a 60 second timeout.Test plan
uv run pytest tests/unit: all pass.This PR also drops the
branchesfilter from thepull_requesttrigger ofrun-tests.yml: it was limited tomain, so pull requests stacked on another branch got no checks. Pushes are still limited tomain.Stacked PRs (merge from the bottom; each PR's base is the branch below it, so no conflicts remain):
main← #45 theme timeout (+ CI runs for stacked PRs) ← #46 typer ← #43 ops commands ← #44 dict ← #41 general/plugin/storage ← #42 searchlist/documents.After a PR is squash-merged GitHub retargets the next one to
main.