Skip Menu |

This queue is for tickets about the Image-Synchronize CPAN distribution.

Report information
The Basics
Id: 129106
Status: resolved
Priority: 0/
Queue: Image-Synchronize
People
Owner: LSTROUS [...] cpan.org
Requestors: SREZIC [...] cpan.org
Cc:
AdminCc:
Bug Information
Severity: (no value)
Broken in: 1.2
Fixed in: 1.4.2

History Show all quoted text
  Wed Apr 10 02:11:24 2019 SREZIC [...] cpan.org - Ticket created
Subject: YAML stringinfication test may fail
See http://www.cpantesters.org/cpan/report/5831c2c4-aaa0-11e8-8d5b-40c35a612c1e for a sample test report. The difference is hard to spot: there's an extra space after the "---" start marker in the "got" version, the "expected" version does not have this space.
  Sat Jun 08 04:19:33 2019 SREZIC [...] cpan.org - Correspondence added
On 2019-04-10 02:11:24, SREZIC wrote: Show quoted text
> See http://www.cpantesters.org/cpan/report/5831c2c4-aaa0-11e8-8d5b- > 40c35a612c1e for a sample test report. The difference is hard to spot: > there's an extra space after the "---" start marker in the "got" > version, the "expected" version does not have this space.
Happens also with 1.4.
  Sat Jun 08 04:36:03 2019 LSTROUS [...] cpan.org - Correspondence added
On Wed Apr 10 02:11:24 2019, SREZIC wrote: Show quoted text
> See http://www.cpantesters.org/cpan/report/5831c2c4-aaa0-11e8-8d5b- > 40c35a612c1e for a sample test report. The difference is hard to spot: > there's an extra space after the "---" start marker in the "got" > version, the "expected" version does not have this space.
This problem is due to YAML::Syck::Dump producing a whitespace character after the "---" start marker and YAML::XS::Dump not producing a whitespace character after the start marker, if there is no further text on that line. My module uses YAML::Any, which passes the request to the "best available" YAML module on the system. On my system that was YAML::XS, and on your system it was YAML::Syck. I've now also looked at modules YAML, YAML::LibYAML, and YAML::Tiny, and they behave like YAML::XS in this respect. I'll fix the problem by using the same Dump to construct the "expected" value, too.
  Sat Jun 08 04:36:03 2019 The RT System itself - Status changed from 'new' to 'open'
  Sat Jun 08 04:36:03 2019 LSTROUS [...] cpan.org - Taken
  Sat Jun 08 14:23:14 2019 LSTROUS [...] cpan.org - Status changed from 'open' to 'resolved'
  Sat Jun 08 14:23:14 2019 LSTROUS [...] cpan.org - Fixed in 1.4.2 added