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
This seems to be caused by a line ending issue in this file which used CRLF line endings. When we read the file with BufferedReader::readLine, lines are split by LF or CRLF until EOF. However, git blame (and the GitHub file viewer) sees this as a single line file and only produces authorship for the first line. The produced authorship.json line info for this file then has missing fields for subsequent lines, which fails frontend schema validation, causing it to erroneously display "0 files changed".
Potential Fix
In reading non-binary files, we should probably split lines by only \n, perhaps using Scanner and Scanner::useDelimiter to match git output. We should also add tests for files with CRLF line endings, and have a check during report generation to ensure that the final authorship (and other) configs contain all required fields.
In the meantime, having the team standardize their line endings to LF (and their git autocrlf settings) is a quick temporary fix.
Happening in this dashboard
One team is showing '0 files changed' for all team members. All other teams are fine.
Any idea about the case?
Repo https://github.com/nus-cs2113-AY2425S1/tp-dashboard
The text was updated successfully, but these errors were encountered: