[AnKiT-GaRG2]

.read_yaml_header() always opened its input with file(), so when text= (or input=) was a single string containing newlines, the data itself was treated as a file name and failed with cannot open the connection. A multi-element text= worked because it is written to a temp file first.

The header is now read through textConnection() when the input contains \n or \r.

Tests 16.23 and 16.24 in other.Rraw fail without the fix (verified against the unpatched build) and pass with it. I also checked all the csvy test files read identically from a file, text= and input=. NEWS item added.

Closes #7896

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.08%. Comparing base (fe94435) to head (0ac3799).

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #7938   +/-   ##
=======================================
  Coverage   99.08%   99.08%           
=======================================
  Files          88       88           
  Lines       17429    17429           
=======================================
  Hits        17270    17270           
  Misses        159      159           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[ben-schwen]

Most unix filesysteme currently allow \n and I would rather not break this. See also Stack Superuser

[AnKiT-GaRG2]

Thanks @ben-schwen, you're right that file names can contain newlines. I no longer look for \n in the string. fread() now tells .read_yaml_header() whether the input is the data itself (!identical(input, file)), so a file name with a newline still opens with file(). The change is in 0ac3799. I couldn't run R here, so the tests (16.23, 16.24) haven't been run against this commit; I'll check CI.