Michael Graf
Michael Graf
+1 interested.
is there a maximum value for stopTimeout ?
We too have encountered issues where celery workers seem to just stall out. No jobs being processed even though the queue grows very large. We eventually theorized that "ETA" jobs...
Or ever.
+1 Also seeing in our production code 
solved in: https://github.com/davecheney/gophercon2018-performance-tuning-workshop/pull/5
I see now that the issue is just in the PDF. http://diwakergupta.github.io/thrift-missing-guide/thrift.pdf I guess a new pdf needs to be generated/hosted.
License is here: https://github.com/jmespath/go-jmespath/blob/master/LICENSE IMO this should be closed.
Could you implement Setter and do it yourself? something like: ```golang type cfg struct { Stuff StuffSlice } type StuffSlice []SecondLevelConfig func (ss *StuffSlice) Set(data string) error { return json.Unmarshal([]byte(data),...
is this still the planned path? I can see if I can handle `-s`