Description
LogStream already puts a space between streamed items, but the KVS logging also
writes spaces into the string literals, so most messages come out double spaced.
Where a value was wrapped in quotes, the spaces land inside them.
Actual output from a unit-test run:
error: file ./data_folder/kvs_123_0.json could not be read
max snapshot count: 3
Failed to open file ' ./data_folder/kvs_123_0.hash '
Fix is to drop the spaces from the literals. A few lines have quotes or brackets
sitting flush against a value, which can't be kept as-is since the separator
always goes in between.
Same thing arkjedrz raised reviewing #308, which fixed the two lines it touched.
Analysis results
No response
Solution
No response
Error Occurrence Rate
None
How to reproduce
No response
Supporting Information
No response
Classification
Minor
First Affected Release
not released (main)
Last Affected Release
not released (main)
Expected Fixed Release
before release (main)
Category
Description
LogStream already puts a space between streamed items, but the KVS logging also
writes spaces into the string literals, so most messages come out double spaced.
Where a value was wrapped in quotes, the spaces land inside them.
Actual output from a unit-test run:
Fix is to drop the spaces from the literals. A few lines have quotes or brackets
sitting flush against a value, which can't be kept as-is since the separator
always goes in between.
Same thing arkjedrz raised reviewing #308, which fixed the two lines it touched.
Analysis results
No response
Solution
No response
Error Occurrence Rate
None
How to reproduce
No response
Supporting Information
No response
Classification
Minor
First Affected Release
not released (main)
Last Affected Release
not released (main)
Expected Fixed Release
before release (main)
Category