Bug #21216
closed
Fix "memoryRetryMultipler" misspelled name
Description
This is in our CWL OutOfMemoryRetry extension. "Multipler" is not a word. I don't know whether we meant "Multiple" or "Multiplier".
I don't know what the backwards compatibility story is here, that should be specified before development. But when you're writing code in YAML with little tooling support to catch errors, predictable names go a long way, so I think this is worth fixing somehow.
Updated by Peter Amstutz about 1 year ago
That's embarrassing. Yes, that was supposed to be "Multiplier".
We can fix it to accept both (the misspelled value and the new one) and have the documentation tell people to use the correct spelling.
Updated by Peter Amstutz about 1 year ago
- Target version changed from Future to Development 2024-01-17 sprint
Updated by Peter Amstutz 12 months ago
21216-multiplier-typo-fix @ 798a896a1a5f411d0d9675a513e1ddeccc3c818d
Updated by Peter Amstutz 12 months ago
21216-multiplier-typo-fix @ 999ef5f71d522283465b54b6468bae6badf28ca4
- All agreed upon points are implemented / addressed.
- yes
- Anything not implemented (discovered or discussed during work) has a follow-up story.
- n/a
- Code is tested and passing, both automated and manual, what manual testing was done is described
- yes, updated the tests with the new, fixed spelling and added a regression test with the old spelling
- Documentation has been updated.
- yes, only lists the new spelling
- Behaves appropriately at the intended scale (describe intended scale).
- n/a
- Considered backwards and forwards compatibility issues between client and server.
- accepts both spellings, with the correct spelling taking precedence
- Follows our coding standards and GUI style guidelines.
- yes
Updated by Peter Amstutz 12 months ago
No changes, just rebased on main:
21216-multiplier-typo-fix @ 5c2f3f465ac10b674e9033083063489a2d9b73c2
Updated by Peter Amstutz 12 months ago
- Target version changed from Development 2024-01-17 sprint to Development 2024-01-31 sprint
Updated by Peter Amstutz 11 months ago
- Target version changed from Development 2024-01-31 sprint to Development 2024-02-14 sprint
Updated by
Updated by Peter Amstutz 11 months ago
- Status changed from In Progress to Resolved