Merge ~cjwatson/turnip:cgit-timeout into turnip:master
Proposed by
Colin Watson
Status: | Merged |
---|---|
Approved by: | Colin Watson |
Approved revision: | acb5fafdd667cbafb5536403ab1d509632169585 |
Merge reported by: | Otto Co-Pilot |
Merged at revision: | not available |
Proposed branch: | ~cjwatson/turnip:cgit-timeout |
Merge into: | turnip:master |
Diff against target: |
25 lines (+5/-1) 2 files modified
charm/turnip-pack-frontend-http/config.yaml (+4/-0) charm/turnip-pack-frontend-http/templates/cgitwrap.j2 (+1/-1) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Jonathan Hartley (community) | Approve | ||
Review via email: mp+369762@code.launchpad.net |
Commit message
Time out cgit processes
We don't want these to hang around forever if something is going wrong.
cgit can legitimately take a while to render large files, so I started
out with a relatively lenient value of 30 seconds and we can see how
things look in practice.
To post a comment you must log in.
For my education: This is the kind of change that isn't amenable to unit tests, but could be amenable to end-to-end tests, of a kind I think that we don't have any of, around this bit of code. Is that correct?
Are there reasons we don't have them that I ought to know about, other than the generic 'It's hard and might not be worth the effort" ?
I'm only asking for my education, no judgement! :-)
Thank you!