CRLF causes WA
See original GitHub issueSummary / 概要
output の改行コードが CRLF, expected では LF となっていて、その他の部分は一致しているようなテストケースで WA と判定されます。
なお verification-helper 内で oj test が呼ばれている状況で、全ての問題 / テストケースで同様です。
Steps to reproduce / 再現方法
- oj-verify run
environments:
- version: 11.3.0 (latest)
- OS: Windows 10
- shell: Git Bash
Actual behavior / 実際の挙動
judge's output:
(empty)
[FAILURE] WA
input:
4 5
1 2 3 4
5 6 7 8 9
output:
5 16 34 60 70 70 59 36\r
expected:
5 16 34 60 70 70 59 36
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:14 (7 by maintainers)
Top Results From Across the Web
CRLF Injection - OWASP Foundation
A CRLF Injection attack occurs when a user manages to submit a CRLF into an application. This is most commonly done by modifying...
Read more >CRLF Injection Tutorial: Vulnerabilities & Prevention - Veracode
Let's examine how CRLF injections cause damage by looking at one of the most basic example of a CRLF attack: adding fake entries...
Read more >What is the difference between a "line feed" and a "carriage ...
A line feed means moving one line forward. The code is \n . A carriage return means moving the cursor to the beginning...
Read more >CRLF in Unix being translated on Mainframe to x'25'
A programmer I am working with is getting a file from Unix which will be sent to the mainframe. This will be using...
Read more >Carriage Return Line Feed (CRLF) - Vulners
perl is vulnerable to Carriage Return Line Feed (CRLF). Perl CGI module processed a sequence of non-whitespace preceded by newline characters in the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

最新の oj + Windows 11 でふと試してみたら、なぜかこの問題が解消されてました。 お騒がせいたしました。
やっぱりなんだか「library-checker-problems あるいは testlib などで解決するべき問題のようです。」というので正しそうな気がします