-
Notifications
You must be signed in to change notification settings - Fork 12
Logging output errors with CF_TRACE=true cf enable diego #6
Comments
We have created an issue in Pivotal Tracker to manage this: https://www.pivotaltracker.com/story/show/131618579 The labels on this github issue will be updated when the story is started. |
The team told me the issue indeed only occurs when CF_TRACE is enabled, and there is no easy way to fix this. Are you OK to keep using it without the trace enabled? |
Yes we'll do our best :) Do you know roughly when it might be fixed? Thanks |
When we run out of other important things to do or when we start revamping the plugin architecture. Maybe in 3 months? |
Okay thank you! |
I have added this to the known issues list, with tested work-arounds. Regards, |
dependencies
may be similar to #3
Diego-Enabler v1.2.1
CF version 240
issue
when running
CF_TRACE=true cf enable-diego <app>
you get the following errorhowever, the command succeeds, because running
cf has-diego-enabled <app>
afterwards returnstrue
and i have indeed checked that the app is running on a cell and not a dea.this is an issue because it means the command exits 1.
just to be clear, running
cf enable-diego <app>
withoutCF_TRACE=true
before it succeeds and exits 0.thanks!
The text was updated successfully, but these errors were encountered: