You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please fill out the issue checklist below and provide ALL the requested information.
I reviewed open and closed github issues that may be related to my problem.
I tried updating to the latest version of the CF CLI to see if it fixed my problem.
I attempted to run the command with CF_TRACE=1 to help debug the issue.
I am reporting a bug that others will be able to reproduce.
Describe the bug and the command you saw an issue with
Provide details on what you were trying to do (and why).
I use cf-cli implicitly in other scripts that do more heavy duty work and these often run in parallel. For even low levels of concurrency, like 5--10 you sporadically see errors of the type:
error: caught error during cf oauth-token
non-zero return code 1
FAILED
Error read/writing config: remove HOME/.cf/temp-config2869106190: no such file or directory
error: caught error during cf oauth-token
non-zero return code 1
FAILED
Error read/writing config: remove HOME/.cf/temp-config2869106190: no such file or directory
The error occurs more reliably with more concurrency. For 16 or 20 parallel executions it happens every time on my machine. I suspect the temp filename generator is tied to something that doesn't handle parallel execution well, like a low-resolution timestamp.
What happened
A clear and concise description of what happened.
See above.
Expected behavior
A clear and concise description of what you expected to happen.
IMO there is no reason cf oauth-token should not work for, say 20 processes running in parallel.
Exact Steps To Reproduce
Steps to reproduce the behavior; include the exact CLI commands and verbose output:
Please fill out the issue checklist below and provide ALL the requested information.
CF_TRACE=1
to help debug the issue.Describe the bug and the command you saw an issue with
Provide details on what you were trying to do (and why).
I use cf-cli implicitly in other scripts that do more heavy duty work and these often run in parallel. For even low levels of concurrency, like 5--10 you sporadically see errors of the type:
The error occurs more reliably with more concurrency. For 16 or 20 parallel executions it happens every time on my machine. I suspect the temp filename generator is tied to something that doesn't handle parallel execution well, like a low-resolution timestamp.
What happened
A clear and concise description of what happened.
See above.
Expected behavior
A clear and concise description of what you expected to happen.
IMO there is no reason
cf oauth-token
should not work for, say 20 processes running in parallel.Exact Steps To Reproduce
Steps to reproduce the behavior; include the exact CLI commands and verbose output:
I wrote a simple bash script to produce:
Provide more context
unrelated
Notes regarding V6 and V7 CLI support:
The text was updated successfully, but these errors were encountered: