You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is a shortcut for AbsaOSS/enceladus#677 (moving it from Enceladus to here)
Describe the bug
If Timestamp/Date pattern contains both literal parts or variable length entry (month name, day name, ...) and fractions of second placeholders namely if any literal part is before any second fraction placeholder it will fail Standardization of such filed or even crash with an exception.
To Reproduce
Steps to reproduce the behavior OR commands run:
Set the timestamp pattern to "'at' HH:mm:ss.SSS"
Try to Standardize or just use 'EnceladusDateTimeParser.format'
Exception, wouldn't it be SSS be at the tail it would "just" fail the conversion in Standardization
Expected behavior
This needs to work properly
Additional context
The reason is that the quote characters are counted in when the position of second fractions are analyzed. But in the actual string to convert they are not present making the index out of place, even outside the boundaries.
This issue is a shortcut for AbsaOSS/enceladus#677 (moving it from Enceladus to here)
Describe the bug
If Timestamp/Date pattern contains both literal parts or variable length entry (month name, day name, ...) and fractions of second placeholders namely if any literal part is before any second fraction placeholder it will fail Standardization of such filed or even crash with an exception.
To Reproduce
Steps to reproduce the behavior OR commands run:
"'at' HH:mm:ss.SSS"
SSS
be at the tail it would "just" fail the conversion in StandardizationExpected behavior
This needs to work properly
Additional context
The reason is that the quote characters are counted in when the position of second fractions are analyzed. But in the actual string to convert they are not present making the index out of place, even outside the boundaries.
Related to AbsaOSS/enceladus#466
The text was updated successfully, but these errors were encountered: