Should escape \r\n in exception message #332
Comments
|
Should escape \r\n in exception message, closed by 8079b5d. |
tlrx
added a commit
that referenced
this issue
Nov 10, 2016
This commit updates JodaTime to version 2.9.5 that contain a fix for a bug when parsing time zones (see JodaOrg/joda-time#332, JodaOrg/joda-time#386 and JodaOrg/joda-time#373). It also remove the joda-convert dependency that seems to be unused. closes #20911 Here is the changelog for 2.9.5: ``` Changes in 2.9.5 ---------------- - Add Norwegian period translations [#378] - Add Duration.dividedBy(long,RoundingMode) [#69, #379] - DateTimeZone data updated to version 2016i - Fixed bug where clock read twice when comparing two nulls in DateTimeComparator [#404] - Fixed minor issues with historic time-zone data [#373] - Fix bug in time-zone binary search [#332, #386] The fix in v2.9.2 caused problems when the time-zone being parsed was not the last element in the input string. New approach uses a different approach to the problem. - Update tests for JDK 9 [#394] - Close buffered reader correctly in zone info compiler [#396] - Handle locale correctly zone info compiler [#397] ```
tlrx
added a commit
that referenced
this issue
Nov 10, 2016
This commit updates JodaTime to version 2.9.5 that contain a fix for a bug when parsing time zones (see JodaOrg/joda-time#332, JodaOrg/joda-time#386 and JodaOrg/joda-time#373). It also remove the joda-convert dependency that seems to be unused. closes #20911 Here is the changelog for 2.9.5: ``` Changes in 2.9.5 ---------------- - Add Norwegian period translations [#378] - Add Duration.dividedBy(long,RoundingMode) [#69, #379] - DateTimeZone data updated to version 2016i - Fixed bug where clock read twice when comparing two nulls in DateTimeComparator [#404] - Fixed minor issues with historic time-zone data [#373] - Fix bug in time-zone binary search [#332, #386] The fix in v2.9.2 caused problems when the time-zone being parsed was not the last element in the input string. New approach uses a different approach to the problem. - Update tests for JDK 9 [#394] - Close buffered reader correctly in zone info compiler [#396] - Handle locale correctly zone info compiler [#397] ``` (cherry picked from commit 2e53190)
tlrx
added a commit
that referenced
this issue
Nov 10, 2016
This commit updates JodaTime to version 2.9.5 that contain a fix for a bug when parsing time zones (see JodaOrg/joda-time#332, JodaOrg/joda-time#386 and JodaOrg/joda-time#373). It also remove the joda-convert dependency that seems to be unused. closes #20911 Here is the changelog for 2.9.5: ``` Changes in 2.9.5 ---------------- - Add Norwegian period translations [#378] - Add Duration.dividedBy(long,RoundingMode) [#69, #379] - DateTimeZone data updated to version 2016i - Fixed bug where clock read twice when comparing two nulls in DateTimeComparator [#404] - Fixed minor issues with historic time-zone data [#373] - Fix bug in time-zone binary search [#332, #386] The fix in v2.9.2 caused problems when the time-zone being parsed was not the last element in the input string. New approach uses a different approach to the problem. - Update tests for JDK 9 [#394] - Close buffered reader correctly in zone info compiler [#396] - Handle locale correctly zone info compiler [#397] ``` (cherry picked from commit 2e53190)
mindw
pushed a commit
to mindw/elasticsearch
that referenced
this issue
Sep 5, 2022
adding oleksii pub + tfvars update * adding oleksii pub * add anton and oleksii to dev1 tfvars * Merge branch 'master' of bitbucket.org:engageli/devops into dev/matan/pub_oleksii-11292021 * Merge branch 'master' of bitbucket.org:engageli/devops into dev/matan/pub_oleksii-11292021 Approved-by: Can Yildiz
cbuescher
pushed a commit
to cbuescher/elasticsearch
that referenced
this issue
Oct 2, 2023
…tic#332) While debugging using pytest in IntelliJ breakpoints get skipped. This seems to be related to [1] and enabling coverage reports in pytest. This commit removes the coverage report (below a snip of how it looks like) in favor of less hair pulling while debugging tests. The report looks like: ``` ----------- coverage: platform linux, python 3.8.5-final-0 ----------- Name Stmts Miss Cover ------------------------------------------------ night_rally/__init__.py 0 0 100% night_rally/admin.py 166 166 0% night_rally/client.py 23 22 4% night_rally/night_rally.py 569 156 73% ------------------------------------------------ TOTAL 758 344 55% ``` [1]: https://intellij-support.jetbrains.com/hc/en-us/community/posts/360008107400-PyCharm-2020-1-not-stopping-on-breakpoints-anymore-
emilykmarx
pushed a commit
to emilykmarx/elasticsearch
that referenced
this issue
Dec 26, 2023
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
see
new StreamCorruptedException("Expecting \r\n after data block");
in
MemcachedDecoder
The text was updated successfully, but these errors were encountered: