Mercurial > p > roundup > code
view website/issues/html/_generic.collision.html @ 8269:341841a9edc5
Handle timeout exception in roundup-server better.
A timeout in roundup-server used to generate another exception:
OSError: cannot read from timed out object
when it tried to reuse the socket that timed out.
Now return status 408, a brief message and trigger closing of the
socket.
Manual testing, no CI.
To test used curl -X POST with no --data defined.
| author | John Rouillard <rouilj@ieee.org> |
|---|---|
| date | Sun, 12 Jan 2025 12:59:41 -0500 |
| parents | c2d0d3e9099d |
| children | 4ac0bbb3e440 |
line wrap: on
line source
<tal:block metal:use-macro="templates/page/macros/icing"> <title metal:fill-slot="head_title" i18n:translate="" ><span tal:replace="python:context._classname.capitalize()" i18n:name="class" /> Edit Collision - <span i18n:name="tracker" tal:replace="config/TRACKER_NAME" /></title> <tal:block metal:fill-slot="body_title" i18n:translate="" ><span tal:replace="python:context._classname.capitalize()" i18n:name="class" /> Edit Collision</tal:block> <td class="content" metal:fill-slot="content" i18n:translate=" There has been a collision. Another user updated this node while you were editing. Please <a href='${context}'>reload</a> the node and review your edits. "><span tal:replace="context/designator" i18n:name="context" /> </td> </tal:block>