An http target's max_queue_size was stored and shown in the target list as "Max Queue Size", but nothing in delivery ever read it, so an operator who set it got no bound on anything. This removes the field from the target, its line in the target list, its row in the README's target table, and the two view tests' use of it. Nothing replaces it and nothing checks for a leftover value.
An existing database keeps its max_queue_size column: the schema is built by adding columns and never drops one, so the old column simply goes unread and no database needs recreating.
Disclosures:
Judgement call: the issue mentions the field on the add and edit forms and their validation, but on next neither form has such a field and nothing validates it, so there was nothing to remove there.
Judgement call: the README table's first column keeps its old padding; the repo has no markdown formatter and re-padding every row would be noise.
An `http` target's `max_queue_size` was stored and shown in the target list as "Max Queue Size", but nothing in delivery ever read it, so an operator who set it got no bound on anything. This removes the field from the target, its line in the target list, its row in the README's target table, and the two view tests' use of it. Nothing replaces it and nothing checks for a leftover value.
An existing database keeps its `max_queue_size` column: the schema is built by adding columns and never drops one, so the old column simply goes unread and no database needs recreating.
Disclosures:
- Judgement call: the issue mentions the field on the add and edit forms and their validation, but on `next` neither form has such a field and nothing validates it, so there was nothing to remove there.
- Judgement call: the README table's first column keeps its old padding; the repo has no markdown formatter and re-padding every row would be noise.
Issue: https://git.eeqj.de/sneak/webhooker/issues/477
Model: opus-5-5
Nothing in delivery ever read it, so setting it bounded nothing. The
field, the "Max Queue Size" line in the target list, its README row and
the tests that set or checked it are gone. An existing database keeps
its old column, which is no longer read.
Model: opus-5-5
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
An
httptarget'smax_queue_sizewas stored and shown in the target list as "Max Queue Size", but nothing in delivery ever read it, so an operator who set it got no bound on anything. This removes the field from the target, its line in the target list, its row in the README's target table, and the two view tests' use of it. Nothing replaces it and nothing checks for a leftover value.An existing database keeps its
max_queue_sizecolumn: the schema is built by adding columns and never drops one, so the old column simply goes unread and no database needs recreating.Disclosures:
nextneither form has such a field and nothing validates it, so there was nothing to remove there.Issue: #477
Model: opus-5-5
Review passed.
Model: opus-5-5