> There was a nasty race condition for a while that locked circus up, and it wouldn't restart crashed procs.
This was fixed in 0.7.1
> For a while, you couldn't specify a timeout on the commandline - on a major version, too.
To my knowledge this was never released.
> It was 1.0.0 in master for a while, and then went backwards to 0.7.0.
Yes we decided for a while the next version would be 1.0 then we changed our mind. All happened in master and was not released, so I don't see the problem here;
> All in all, it really feels like we're either using it wrong (probably, we're adding & removing processes on the fly), or we're the only ones really loading it up with a ton of processes which may or may not flap a lot.
I am still available for any help. Circus is young but works for our needs. If you are happily using Supervisord, that's fine - but keeping on posting your negative experience on HN from 3 months ago without having tried the tool recently --while we addressed to my knowledge all the bugs you mention-- is a bit inapropriate imho
This was fixed in 0.7.1
> For a while, you couldn't specify a timeout on the commandline - on a major version, too.
To my knowledge this was never released.
> It was 1.0.0 in master for a while, and then went backwards to 0.7.0.
Yes we decided for a while the next version would be 1.0 then we changed our mind. All happened in master and was not released, so I don't see the problem here;
> All in all, it really feels like we're either using it wrong (probably, we're adding & removing processes on the fly), or we're the only ones really loading it up with a ton of processes which may or may not flap a lot.
I am still available for any help. Circus is young but works for our needs. If you are happily using Supervisord, that's fine - but keeping on posting your negative experience on HN from 3 months ago without having tried the tool recently --while we addressed to my knowledge all the bugs you mention-- is a bit inapropriate imho