Sylvain Zimmer
Sylvain Zimmer
In the benchmark against the `regexp` package, the DOTALL regexp option should be used because without it `.*` is not the same as the glob `*` (`regexp` has to exclude...
I ran into a situation where I had 9999 such files left in /tmp and no more webworkers would be able to start. There should be a periodic garbage collection...
For users with a non-standard config file path, it would be great to be able to set an environment variable like `FLINTROCK_CONFIG_PATH` to avoid prepending every command with `--config ...`.
I think `run-command` could be even more useful if the user was able to see the output of the command on each instance. This could be added as a flag...
I don't know if this is considered to be in the scope of flintrock, so this is obviously just a suggestion. It could be handy after launching a cluster to...
See documentation about the feature here: http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/spot-fleet.html Adding a `--spot-fleet-request-config` flag that points to the user-supplied `config.json` file would be great!
1318946429614 'Fetched computing games : ' 1 1318946429682 'Fetching unresolved pos for game' 4e8dc6af85b793867c0003ad /home/deploy/app/source/www/master/engines/distributed-mongo.js:179 models.Position.count({resolved:false,fen:{$in:_.keys(pos.children)}}, ^ TypeError: Object.keys called on non-object at Function.keys (native) at Promise. (/home/deploy/app/source/www/master/engines/distributed-mongo.js:179:58) at Promise....
"suicidal" moves (gave a lot of quality pieces) once seen problematic situation - resign would be more elegant...