[opensuse-buildservice] build flags in web interface
Hi all Sometime not far back a new thing was added to the web UI for OBS that prevented 'complex' flag combinations to be used from the web interface. I get an error like this: "ERROR Your flag configuration seems to be too complex to be saved through this interface. Please use OSC." I would like to comment that the direct result of preventing web UI users from disabling certain builds is that they will tend not to bother, and your compile farm capacity will be needless wasted. If it's possible, could I urge that the full flag functionality be restored, and even better, could some clever javascript/AJAX be used to make these flag settings more responsive -- they are quite slow to use at present (and I imagine this might have been part of the reason for the above 'error' message). I think the web UI is overall an excellent tool -- please, do keep up the great work! Cheers JP --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On 2008-02-05 18:51:20 +1100, John Pye wrote:
Sometime not far back a new thing was added to the web UI for OBS that prevented 'complex' flag combinations to be used from the web interface. I get an error like this:
"ERROR Your flag configuration seems to be too complex to be saved through this interface. Please use OSC."
I would like to comment that the direct result of preventing web UI users from disabling certain builds is that they will tend not to bother, and your compile farm capacity will be needless wasted. If it's possible, could I urge that the full flag functionality be restored, and even better, could some clever javascript/AJAX be used to make these flag settings more responsive -- they are quite slow to use at present (and I imagine this might have been part of the reason for the above 'error' message).
there is nothing to be restored. complex disable/enable configs where always the domain of osc. darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Hi Markus, Marcus Rueckert wrote:
On 2008-02-05 18:51:20 +1100, John Pye wrote:
Sometime not far back a new thing was added to the web UI for OBS that prevented 'complex' flag combinations to be used from the web interface. I get an error like this:
"ERROR Your flag configuration seems to be too complex to be saved through this interface. Please use OSC."
I would like to comment that the direct result of preventing web UI users from disabling certain builds is that they will tend not to bother, and your compile farm capacity will be needless wasted. If it's possible, could I urge that the full flag functionality be restored, and even better, could some clever javascript/AJAX be used to make these flag settings more responsive -- they are quite slow to use at present (and I imagine this might have been part of the reason for the above 'error' message).
there is nothing to be restored. complex disable/enable configs where always the domain of osc.
Thanks for the reply. I'm a bit surprised by this, but perhaps I only really started using fairly recently. Is it possible to explain how exactly one comes up against this 'complexity' limit that is triggering the error? And on the aside: is a simple javascript/AJAX improvement to those flags something that could perhaps be put on a TODO list at some point? Cheers JP --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
John Pye wrote:
Hi Markus,
Marcus Rueckert wrote:
On 2008-02-05 18:51:20 +1100, John Pye wrote:
Sometime not far back a new thing was added to the web UI for OBS that prevented 'complex' flag combinations to be used from the web interface. I get an error like this:
"ERROR Your flag configuration seems to be too complex to be saved through this interface. Please use OSC."
I would like to comment that the direct result of preventing web UI users from disabling certain builds is that they will tend not to bother, and your compile farm capacity will be needless wasted. If it's possible, could I urge that the full flag functionality be restored, and even better, could some clever javascript/AJAX be used to make these flag settings more responsive -- they are quite slow to use at present (and I imagine this might have been part of the reason for the above 'error' message).
there is nothing to be restored. complex disable/enable configs where always the domain of osc.
Thanks for the reply. I'm a bit surprised by this, but perhaps I only really started using fairly recently. Is it possible to explain how exactly one comes up against this 'complexity' limit that is triggering the error?
The cause of this message is flag configurations for non-existing repositories. This always happens if you delete a repository for which flags are set in the project metadata. A possible solution would be to make the webclient fix the flag configuration automatically after deleting a repository.
And on the aside: is a simple javascript/AJAX improvement to those flags something that could perhaps be put on a TODO list at some point?
What do you mean by simple javascript/AJAX improvement? Andreas --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Andreas Bauer wrote:
John Pye wrote:
Hi Markus,
Marcus Rueckert wrote:
On 2008-02-05 18:51:20 +1100, John Pye wrote:
Sometime not far back a new thing was added to the web UI for OBS that prevented 'complex' flag combinations to be used from the web interface. I get an error like this:
"ERROR Your flag configuration seems to be too complex to be saved through this interface. Please use OSC."
I would like to comment that the direct result of preventing web UI users from disabling certain builds is that they will tend not to bother, and your compile farm capacity will be needless wasted. If it's possible, could I urge that the full flag functionality be restored, and even better, could some clever javascript/AJAX be used to make these flag settings more responsive -- they are quite slow to use at present (and I imagine this might have been part of the reason for the above 'error' message).
there is nothing to be restored. complex disable/enable configs where always the domain of osc.
Thanks for the reply. I'm a bit surprised by this, but perhaps I only really started using fairly recently. Is it possible to explain how exactly one comes up against this 'complexity' limit that is triggering the error?
The cause of this message is flag configurations for non-existing repositories. This always happens if you delete a repository for which flags are set in the project metadata.
In this case the error message is wrong. My reading of the message was that my setting of the flags was 'too complex' because I had set/unset more options that the web GUI could tolerate.
A possible solution would be to make the webclient fix the flag configuration automatically after deleting a repository.
I'm actually not sure that I did delete a repository. But if that's the case, then yes, perhaps this needs to be implemented.
And on the aside: is a simple javascript/AJAX improvement to those flags something that could perhaps be put on a TODO list at some point?
What do you mean by simple javascript/AJAX improvement?
Use case: I upload a new version of somepackage-0.9.9.9.tar.bz2 tarball to my somepackage package in my home projects on the OBS web UI. I make some changes (using the Web UI) to the .spec file, in the hope that nothing serious will happen. But in order to avoid overloading the compile farm, I want to first check that my package works by just compiling the package on the latest version of Fedora. I also want to disable compilation in Ubuntu, because I haven't yet written the .dsc, control, etc files. Once I get the RPM building on the latest Fedora, I want to make RPMs for all the other distros, and then maybe start working on the Deb packages. Problem with the above is that the lag involved in clicking the flags on/off (also: note that a implicitly enabled flag becomes explicitly enabled before then, on a third click, becoming explicitly disabled: these are in the wrong order). Maybe when you're at SUSE HQ this is fast, but where I am (on a fast connection in Australia) it takes several seconds to change each flag (and I need to change them twice as noted). A good solution to this would be to use some asynchronous javascript requests to set/unset the flags, rather than using what currently looks like a page refresh (I might be wrong). In any case, it's rather slow and in order to be 'usable', it needs to be faster. Again, keep up the great work -- I'm really pleased that your service exists. Cheers JP
Andreas --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Thu, 7 Feb 2008, Andreas Bauer wrote:
Thanks for the reply. I'm a bit surprised by this, but perhaps I only really started using fairly recently. Is it possible to explain how exactly one comes up against this 'complexity' limit that is triggering the error?
The cause of this message is flag configurations for non-existing repositories. This always happens if you delete a repository for which flags are set in the project metadata.
That's only one part of the problem. Another one are duplicate entries. With one of the older version you could click multiple repositories and the flags were updated in parallel and the final results would be the desired one (Why would one do that? Because updating the flags is awfully slow.). When you do the same thing now, you very like get a too complex statement. I think this too complex statement should be fixed at least for these two cases: - duplicate entries (possibly stating different states) - entries for old repositories Both can be resolved automatically. Ciao -- http://www.dstoecker.eu/ (PGP key available) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (4)
-
Andreas Bauer -
Dirk Stoecker -
John Pye -
Marcus Rueckert