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
When running on Windows with git-bash (at least the way I have it configured), echo $w | $csum | awk '{print $1}' does not produce the expected hash of 7c85d987a917c2a555d1391426978f05. As a result, it prints the line: Well, congratulations!! You fixed my conflict!!... (even though the player has not yet completed the level's challenge of performing the merge and resolving the conflict).
I traced the problem to the fact that the read function in bash on Windows (at least in my configuration) reads a CRLF, and the hash was generated with just a LF.
The text was updated successfully, but these errors were encountered:
When running on Windows with git-bash (at least the way I have it configured),
echo $w | $csum | awk '{print $1}'
does not produce the expected hash of7c85d987a917c2a555d1391426978f05
. As a result, it prints the line:Well, congratulations!! You fixed my conflict!!
... (even though the player has not yet completed the level's challenge of performing the merge and resolving the conflict).I traced the problem to the fact that the
read
function in bash on Windows (at least in my configuration) reads a CRLF, and the hash was generated with just a LF.The text was updated successfully, but these errors were encountered: