+Eric Chip Childers | VP Technology | Cloud Foundry Foundation

layne, does this 401 issue only affect the new DEAs (previous ones work fine) or does it affect all DEAs (previously existing and the new scaled out ones)? -- Thank you, James Bayer

Hi, my cf-release is v200. And I met an issue when scale out the DEA number with BOSH. When I ssh to my DEA_NEXT node, the log

Dear Eric, thanks for the update on the current state of mailman3. The digest bug you linked seems to be related to 'summary digests' only. However, I also don't get any mails delivered, if I choose

https://groups.google.com/forum/#!searchin/golang-nuts/Inconsistent$20X-Forwarded-For/golang-nuts/iUnZgzrOszI/ngxcLbSm1VYJ Mail thread about the issue at golang-nuts. This is not really a massive

Incase of datadog nozzle https://github.com/cloudfoundry-incubator/datadog-firehose-nozzle I am assuming that - datadogclient is a custom client which is a kind of aggregator which is fetching

erik, is there a set of tests for log message length? ---------- Forwarded message ---------- From: Koper, Dies <diesk(a)fast.au.fujitsu.com> Date: Thu, Aug 20, 2015 at 1:17 PM Subject: [cf-dev] max

Ah I see the problem. Nice find. I'll await reply from Golang devs, but I'm wondering how much of a problem this is for you? We could come up with a work around if this was hurting you in some

ok, so UAA is pretty picky about the "host names" that come in. by default only localhost and *.localhost where * is a zone name are allowed. There is a property that configures that called zones:

Hi Filip, It works now. Does Tomcat only listen to "localhost"? Can I not point a browser from another machine to Tomcat? thanks, alex

Hi Filip, $ java -version java version "1.8.0_60" Java(TM) SE Runtime Environment (build 1.8.0_60-b27) Java HotSpot(TM) 64-Bit Server VM (build 25.60-b23, mixed mode) $ javac -version javac

hi Alex, can you confirm that. java -version javac -version both return Java 8 "Uh oh, something went amiss" means that Tomcat is indeed up, but the app is not working. So try ./gradlew clean

and http://localhost:8080/uaa returned the same Uh oh. Something went amiss. © 2015 Pivotal Software, Inc. All Rights Reserved.

Hi Filip, Yes, the "--info" help to know tomcat is up @ 8080. However, it's still aint working properly.. I see this on my browser.. Uh oh. Something went amiss. © 2015 Pivotal Software, Inc. All

and yes, you will see gradle stuck on Tomcat 7.x started on port [8080] [ant:cargo] Press Ctrl-C to stop the container... Press Ctrl-C to stop the container... Until you hit Ctrl+C Filip

./gradlew run --info The --info flag will print out the UAA and Tomcat logs to screen. the server will then be accessible on http://localhost:8080/uaa

Can someone shed some light on why my UAA local run got stuck at cargoRunLocal? I don't think the service is up because I don't see anything listening to port 8080. When I did a Ctrl-C, everything

Thanks for the confirmation. Guess for now we will use 4 buckets. Hopefully this could be an added feature in the future. -Rich

Spiff is not currently replaced by another tool, but it is not the ideal tool for the job (too many features to shoot yourself in the foot with, not enough features about BOSH knowledge, and just some

Hi, My service broker provisions a service asynchronously but doesn't get the management url until the service is provisioned. Currently the poll to the endpoint /{instanceId}/last_operation doesn't