TypeError: Cannot read property '10' of null

[jpmolinamatute]

I'm using Atom v1.27.1 and I get more 140 errors messages in the developer console

file with the problem /usr/lib/atom/node_modules/what-the-status/index.js:190

Uncaught (in promise) TypeError: Cannot read property '10' of null
at parseUnmergedEntry (/usr/lib/atom/node_modules/what-the-status/index.js:190:20)
at parseLine (/usr/lib/atom/node_modules/what-the-status/index.js:73:7)
at Stream. (/usr/lib/atom/node_modules/what-the-status/index.js:36:31)
at emitOne (events.js:115:13)
at Stream.emit (events.js:210:7)
at drain (/usr/lib/atom/node_modules/through/index.js:36:16)
at Stream.stream.queue.stream.push (/usr/lib/atom/node_modules/through/index.js:45:5)
at emit (/usr/lib/atom/node_modules/split/index.js:37:14)
at next (/usr/lib/atom/node_modules/split/index.js:49:7)
at Stream. (/usr/lib/atom/node_modules/split/index.js:54:5)
at Stream.stream.write (/usr/lib/atom/node_modules/through/index.js:26:11)
at Readable.ondata (_stream_readable.js:628:20)
at emitOne (events.js:115:13)
at Readable.emit (events.js:210:7)
at Readable.read (_stream_readable.js:464:10)
at flow (stream_readable.js:835:34)
at emitReadable (_stream_readable.js:503:3)
at _combinedTickCallback (internal/process/next_tick.js:135:11)
at process._tickCallback (internal/process/next_tick.js:180:9)

if you need more information to debug/fix this issue, please let me know

[mikey-]

[Caellion]

sorry for necroing, but if you have possibility to still reproduce this, can you include result of running this command in that repo:
git status --porcelain=v2 --branch --untracked-files=all --ignore-submodules=dirty -z
because it seems that this regex

what-the-status/index.js

Line 8 in 64688d7

var UNMERGED_REGEX = /^([.MADRCUT]{2}) ([NS][.C][.M][.U]) (\d+) (\d+) (\d+) (\d+) ([0-9a-f]{40}) ([0-9a-f]{40}) ([0-9a-f]{40}) (.*)$/

doesn't match anything for some 140 unmerged files in your repo. I have encountered kind of similar bug, but in different circumstances and would like to at least write a test-case for the kind of git-output you got.

Things that come to mind:

• Renames with old filenames starting with 1, 2,u or !
• Some really obscure unicode characters in names