Closed Scotchman0 closed 1 year ago
I should also note: Thanks very much for making this tool available in the first place, it's been a boon to my success and I appreciate that you took the time to create it. Hopefully this issue's not a massively annoying one to review/find/debug; and I also respect that wontfix
is a valid closure code. :)
self-closing due to length of time without update, have been using omc
which is currently supported at --> https://github.com/gmeghnag/omc Thank you!
Hey there!
I was running into a repeated issue with what appears to be a logical search problem with the
omg
tool:I observed that when I search for a common/easily found resource in a namespace:
oc get deployment
; omg is quite efficient at returning the results:However, when I misspell this resource (or call for something that doesn't exist; like
eip
on a gather from an sdn platform)omg
will review every resource file available in the cluster and take an exceedingly long time to return the result; which is inevitably:[Error] Invalid object type: <string>
Example:
Note that in the above test, we observe 218s go by before the system unlocks the process and returns the fail-result. (note also the multiple failed siginterupts being ignored by the process)
I am unable to
sigint
(ctrl+c) this process while it is running/stalled and I am forced to either abort the process entirely and recreate a new shell session and call the process again, or wait. (or forcibly terminate the process from another session).This is a low-priority problem, but It is one that causes not-so-insignificant pain when I fat-finger a call and have to wait it out.
Appreciate your time!