These are chat archives for arenanet/api-cdi

Oct 2016
Oct 03 2016 14:05
anyone here that has knowledge about docker?
after a container has been on for a while, my iptables are reset to not include docker rules... and therefore every docker container has no internet access
Edgar Doiron
Oct 03 2016 14:08
@Nabrok I had this error this morning
{ [Error: ETIMEDOUT] code: 'ETIMEDOUT', connect: false }
                ranks.forEach(rank => { membersInRank[] = []; });

TypeError: Cannot read property 'forEach' of undefined
    at /home/ubuntu/workspace/features/ranks.js:32:8
    at /home/ubuntu/workspace/node_modules/async/dist/async.js:3679:13
    at iteratorSymbol (/home/ubuntu/workspace/node_modules/async/dist/async.js:486:20)
    at replenish (/home/ubuntu/workspace/node_modules/async/dist/async.js:879:29)
    at iterateeCallback (/home/ubuntu/workspace/node_modules/async/dist/async.js:869:21)
    at /home/ubuntu/workspace/node_modules/async/dist/async.js:847:20
    at /home/ubuntu/workspace/node_modules/async/dist/async.js:3676:17
    at /home/ubuntu/workspace/node_modules/async/dist/async.js:339:31
    at iteratorSymbol (/home/ubuntu/workspace/node_modules/async/dist/async.js:486:20)
    at /home/ubuntu/workspace/node_modules/async/dist/async.js:855:24
    at eachOfLimit (/home/ubuntu/workspace/node_modules/async/dist/async.js:915:26)
    at FUNC_ERROR_TEXT$1 (/home/ubuntu/workspace/node_modules/async/dist/async.js:920:20)
    at eachOf (/home/ubuntu/workspace/node_modules/async/dist/async.js:1052:9)
    at Object.eachLimit (/home/ubuntu/workspace/node_modules/async/dist/async.js:3111:7)
    at initServer (/home/ubuntu/workspace/features/ranks.js:16:8)
    at async.each.async.series.membersInRank (/home/ubuntu/workspace/features/ranks.js:29:20)
Oct 03 2016 14:49
Thanks @Coffee4cr , just pushed up a change that should prevent it from crashing when that happens.
Oct 03 2016 17:57
discord itself seems to be having some problems at the moment
Oct 03 2016 18:01
Oct 03 2016 18:08
seems to be over now
Oct 03 2016 18:09
yep you can see the spike
@codemasher uhh crap, I didn't look at the rects
But the marker positions were put into the right place in content (e.g., not set via script) so the coordinates at least should be correct once I do a deploy