[alpha.3] libevent2.d(1140): Range violation

[9il]

core.exception.RangeError@../../.dub/packages/vibe-d-0.7.27-alpha.3/source/vibe/core/drivers/libevent2.d(1140): Range violation
violation
----------------
??:? _d_arraybounds [0x952363]
??:? vibe.core.drivers.libevent2.__array [0x918fbf]
../../.dub/packages/vibe-d-0.7.27-alpha.3/source/vibe/core/drivers/libevent2.d:1140 bool vibe.core.drivers.libevent2.InotifyDirectoryWatcher.readChanges(ref vibe.core.file.DirectoryChange[], core.time.Duration) [0x8bc02e]
source/app.d:178 void app.start(uint, uint) [0x78b2c7]
source/app.d:53 void app.main(immutable(char)[][]).__lambda2(uint, uint) [0x78abdd]
../../.dub/packages/vibe-d-0.7.27-alpha.3/source/vibe/core/core.d:486 void vibe.core.core.makeTaskFuncInfo!(void delegate(uint, uint), uint, uint).makeTaskFuncInfo(ref void delegate(uint, uint), ref uint, ref uint).callDelegate(vibe.core.core.TaskFuncInfo*) [0x79fc7d]
../../.dub/packages/vibe-d-0.7.27-alpha.3/source/vibe/core/core.d:1039 void vibe.core.core.CoreTask.run() [0x8b2ebf]
??:? void core.thread.Fiber.run() [0x9aa921]
??:? fiber_entryPoint [0x9aa69b]
??:? [0xffffffff]
Converted /home/ilya/data/grad_sharded/merger_20151223T075036Z_audio_kp2_26998510_27001509_v0_i2.json.gz: 10.5282M json, 1.2866M json.gz, 0.1501M bin, 0.045490M bin.gz
Converted /home/ilya/data/grad_sharded/merger_20151223T094808Z_audio_kp50_27052489_27055488_v0_i2.json.gz: 11.6206M json, 1.3948M json.gz, 0.1580M bin, 0.047737M bin.gz
Task terminated with unhandled exception: Range violation

[s-ludwig]

Looks strange. Looking at the code, I couldn't see an issue on vibe.d's side. I'll add an explicit check and a log message for this case to at least avoid the crash.

[etcimon]

It happens, all the time. Linux can pass some garbage file descriptors or watch descriptors for some reason. That was a big question mark for me in libasync, until I just decided there's probably a lot of undocumented stuff going on. Checking for validity on the descriptor is something that always needs to be done because of that.

[s-ludwig]

Okay, good to know.

[9il]

Looks strange. Looking at the code, I couldn't see an issue on vibe.d's side. I'll add an explicit check and a log message for this case to at least avoid the crash.

Thanks!