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
After investigation, I found that it was caused by the working logic of snakeyaml.
1
In YamlEngine, we construct the Yaml object by passing representer, set dumperOptions in representer, and specify the type of lineBreak in dumperOptions.
2
However, in the construction flow, Yaml initializes a new dumperOptions instead of using the one provided in the representer, which causes the lineBreak type set in advance to be invalid.
3
And the new initialized dumperOptions, its lineBreak has the default value: LineBreak.UNIX
* Fixes#29429, fix yaml lineBreak on windows
* Fix DQL E2E for PostgreSQL
* Comment case for pg_catalog.pg_stat_xact_all_tables
* Comment case for pg_catalog.pg_stat_xact_all_tables
Details: https://github.com/apache/shardingsphere/actions/runs/7240149841/job/19722816797
After investigation, I found that it was caused by the working logic of snakeyaml.
1
In YamlEngine, we construct the Yaml object by passing
representer
, setdumperOptions
in representer, and specify the type oflineBreak
indumperOptions
.2
However, in the construction flow, Yaml initializes a new
dumperOptions
instead of using the one provided in therepresenter
, which causes thelineBreak
type set in advance to be invalid.3
And the new initialized
dumperOptions
, itslineBreak
has the default value:LineBreak.UNIX
4
Relatedly, this issue can be traced to #28805
https://github.com/apache/shardingsphere/pull/28805/files#diff-806e38b8fb7f6f30a4e93659923cf23f84aaa77833f9eb4665063d8df2809f23
The text was updated successfully, but these errors were encountered: