[opensuse-buildservice] osc tab completion ...
Hi, osc tab completion is broken since always. If wanted I could give you many utterly broken examples but I can't imagine that there is someone who does not know the problems. Does it acually does something useful for somebody? Do we really need to enable it by default? At least we should disable network access in _any_ tab completion. Even if osc would work at all ...obs servers are very often not reachable ... even more annoying. BTW what is the preferred way to disable it? Does removing /etc/profile.d/osc.*sh survives an update? cu, Rudi -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Tue, Dec 17, 2013 at 4:48 AM, Ruediger Meier <sweet_f_a@gmx.de> wrote:
osc tab completion is broken since always. If wanted I could give you many utterly broken examples but I can't imagine that there is someone who does not know the problems. Does it acually does something useful for somebody?
It has never worked for me either. It always just hangs. I always thought it was just me, but now I'm glad to have company :) -Archie -- Archie L. Cobbs -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Tue, Dec 17, 2013 at 8:56 AM, Archie Cobbs <archie@dellroad.org> wrote:
On Tue, Dec 17, 2013 at 4:48 AM, Ruediger Meier <sweet_f_a@gmx.de> wrote:
osc tab completion is broken since always. If wanted I could give you many utterly broken examples but I can't imagine that there is someone who does not know the problems. Does it acually does something useful for somebody?
It has never worked for me either. It always just hangs.
I always thought it was just me, but now I'm glad to have company :)
I did a little investigation. It hangs running the command "osc ls /" which can take an arbitrarily long time due to network delays, build server load, etc. IMHO completion scripts should not be performing network I/O. -Archie -- Archie L. Cobbs -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Tuesday 17 December 2013, Archie Cobbs wrote:
On Tue, Dec 17, 2013 at 8:56 AM, Archie Cobbs <archie@dellroad.org> wrote:
On Tue, Dec 17, 2013 at 4:48 AM, Ruediger Meier <sweet_f_a@gmx.de> wrote:
osc tab completion is broken since always. If wanted I could give you many utterly broken examples but I can't imagine that there is someone who does not know the problems. Does it acually does something useful for somebody?
It has never worked for me either. It always just hangs.
I always thought it was just me, but now I'm glad to have company :)
I did a little investigation. It hangs running the command "osc ls /" which can take an arbitrarily long time due to network delays, build server load, etc.
It's broken in so many ways... For example if you try to redirect the output $ osc rdiff devel:libraries:c_c++/ginac science/ginac > /tm<TAB> ... takes ages as usuallly and then ... Server returned an error: HTTP Error 400: Bad Request invalid project name '>' p/Server returned an error: HTTP Error 400: Bad Request invalid project name '>' Or this one for new users without config, You would need to create an obs account to let the completion work on your local machine... $ mv ~/.osc.projects ~/.osc.projects.bak $ mv ~/.oscrc ~/.oscrc.bak $ osc <TAB> Your user account / password are not configured yet. You will be asked for them below, and they will be stored in /home/rudi/.oscrc for future use. Creating osc configuration file /home/rudi/.oscrc ... ... will hang forever ... Or even an (almost) working example without network access after projects are cached already: $ osc rdiff ho<TAB> ... takes 30 secs 100% CPU to complete it to $ osc rdiff home: ... and then $ osc rdiff home:r<TAB> ... takes another 20 secs to complete it to $ osc rdiff home:home:r ... but such project does not exists
IMHO completion scripts should not be performing network I/O.
At least this has to be disabled by default. Users with fast network or with enough time to wait for the funny, broken completions could enable it. cu, Rudi -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Ruediger Meier <sweet_f_a@gmx.de> writes:
Or this one for new users without config, You would need to create an obs account to let the completion work on your local machine... $ mv ~/.osc.projects ~/.osc.projects.bak
Using a single file for caching the available projects is also broken by design, once you are working with more than one OBS instance. Andreas. -- Andreas Schwab, SUSE Labs, schwab@suse.de GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Ruediger Meier <sweet_f_a@gmx.de> Tue, 17 Dec 2013 13:48:38 +0300:
Hi,
osc tab completion is broken since always. If wanted I could give you many utterly broken examples but I can't imagine that there is someone who does not know the problems. Does it acually does something useful for somebody?
Do we really need to enable it by default? At least we should disable network access in _any_ tab completion. Even if osc would work at all ...obs servers are very often not reachable ... even more annoying.
BTW what is the preferred way to disable it? Does removing /etc/profile.d/osc.*sh survives an update?
cu, Rudi
It works fine at zsh ;) I was really surprised because of your topic. -- Best regards, Dmitriy DA(P).DarkneSS Perlow @ Linux x64 -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Tuesday 17 December 2013, Dmitriy Perlow wrote:
Ruediger Meier <sweet_f_a@gmx.de> Tue, 17 Dec 2013 13:48:38 +0300:
Hi,
osc tab completion is broken since always. If wanted I could give you many utterly broken examples but I can't imagine that there is someone who does not know the problems. Does it acually does something useful for somebody?
Do we really need to enable it by default? At least we should disable network access in _any_ tab completion. Even if osc would work at all ...obs servers are very often not reachable ... even more annoying.
BTW what is the preferred way to disable it? Does removing /etc/profile.d/osc.*sh survives an update?
cu, Rudi
It works fine at zsh ;) I was really surprised because of your topic.
Probably because the installed rules are made for bash only. :) cu, Rudi -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Hi,
BTW what is the preferred way to disable it? Does removing /etc/profile.d/osc.*sh survives an update?
I guess filing a bugreport and asking for the completions to be removed would help (yes, they're entirely broken, first thing I uninstall every time). I can hardly imagine anyone actually using them. Greetings, Dirk -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
participants (5)
-
Andreas Schwab -
Archie Cobbs -
Dirk Müller -
Dmitriy Perlow -
Ruediger Meier