#docker-dev

runcom: you're awesome, thanks for all the help!

cpuguy83: at some point i thought you will shout at me telling me to stop pushing shit :D

btw, yw, i love the project :)

hello there

backjlack: nope, that issue still verified with 1.6.0RC2 :(

Pid is returned as 1.107555e+06

gdm85: Did you try on master?

cpuguy83: no. but maybe I should try with gh11839?

Allow go template to work properly with inspect …: https://github.com/docker/docker/pull/11839

Yeah. There's been a couple of changes... And yeah I guess that inspect one.

My pid numbers are really low so it works just fine for me :)

eheh :)

I did run into it in one of the tests I was writing trying to parse the HostConfig.Memory field, though.

I intentionally changed the max pid number on this server, as it was going to see a lot of processes

yeah, surely it affects all other int fields

Ended up just making it a float in the test

mmh..in order to test this issue, I'd have to restart docker. that will push back the pid number, thus helping the issue evading detection

I'll need to write a 100k parallel sleeps test for this :)

did you try 11839 ?

duglin: I am compiling it now

ok - I was playing with it last week and it seems to work for me

I just need to create 1M processes, should be easy - the slight pid randomization will also help a bit :P

is it correct that master reports 1.5.0-dev?

gdm85: Yes.

ok, thanks