November 2009 - YaST Development - openSUSE Mailing Lists

[yast-devel] Re: [yast-commit] <web-client> master : showing flash if no data is available (bnc#524614)
by Josef Reidinger 12 Nov '09

12 Nov '09

Stefan Schubert write: > ref: refs/heads/master > commit a31f5e4c62058ff85094a86c38ff574bb3e067db > Author: Stefan Schubert <schubi(a)suse.de> > Date: Thu Nov 12 10:12:42 2009 +0100 > > showing flash if no data is available (bnc#524614) > --- > .../status/app/controllers/status_controller.rb | 25 > +++++++++++++++++-- 1 files changed, 22 insertions(+), 3 deletions(-) > > diff --git a/plugins/status/app/controllers/status_controller.rb > b/plugins/status/app/controllers/status_controller.rb index > 012449f..7b4cf03 100644 > --- a/plugins/status/app/controllers/status_controller.rb > +++ b/plugins/status/app/controllers/status_controller.rb > @@ -101,11 +101,30 @@ class StatusController < ApplicationController > > till = Time.new > from = till - 300 #last 5 minutes > - ActionController::Base.benchmark("Status data read from the server") > do - status = @client.find(:dummy_param, :params => { :start => > from.to_i.to_s, :stop => till.to_i.to_s }) + begin > + ActionController::Base.benchmark("Status data read from the server") > do + status = @client.find(:dummy_param, :params => { :start => > from.to_i.to_s, :stop => till.to_i.to_s }) + end > + create_data_map status > + rescue Exception => e ^^^ catch general Exception is not good idea, as it can enclose bugs. If you have for missing data proper BackendException with its unique identifier and you can check there simple as rescue Exception => e raise e unless ClientException.new(e).backend_exception_type == "YOUR_ID" flash...etc... end This catch only expected exception and other is not hidden and properly reported ( e.g. this change breaks control center, as on my pc AJAX set this message stuff which is then showed in language module which I select.) Josef > + flash[:warning] = e.message > + logger.warn e > end > - create_data_map status > # logger.debug @data_group.inspect > + > + #checking if there is one valid data entry at least > + found = false > + @data_group.each do |key, map| > + map.each do |graph_key, list_value| > + unless list_value.empty? > + found = true > + break > + end > + end > + break if found > + end > + flash[:notice] = _("No data found for showing system status.") unless > found + > true > end > -- Josef Reidinger YaST team maintainer of perl-Bootloader, YaST2-Repair, webyast (language,time,basesystem,ntp) -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 0

[yast-devel] Re: [yast-commit] Build failed in Hudson:
by Klaus Kaempf 11 Nov '09

11 Nov '09

Now that git is back up, this is a real packaging error :-} Klaus * Hudson Integration Service <hudson(a)suse.de> [Nov 11. 2009 14:57]: > See http://yast.suse.de:3334/job/webyast-service-head-i586/596/changes > > Changes: > > [Josef Reidinger] fix removing files from package in osc_submit task, release 0.0.10 > > [Josef Reidinger] rename script for grnating webyast rights and place to proper location (bnc#542077) > > [Josef Reidinger] don't automatic use index.php, as we not use php for webyast > > [Stefan Schubert] version 0.0.7 > > [Stefan Schubert] Merge branch 'master' of git@git.opensuse.org:projects/yast/rest-service > > [Stefan Schubert] added doc files > > ------------------------------------------ > A SCM change trigger started this job > Checkout > [workspace] $ git fetch > Checking out origin/master > [workspace] $ git checkout -f origin/master > Previous HEAD position was c9c9108... fix version of yast2-network > HEAD is now at 42c2433... added doc files > [workspace] $ git rev-parse origin/master > [workspace] $ git log --numstat -M --summary --pretty=raw 329b2610999c8f4478c3feb948ef7d66520652fe..42c243333c783c05bacb80a01d7aae2d9e9c3499 > [locks-and-latches] Checking to see if we really have the locks > [locks-and-latches] Have all the locks, build can start > [workspace] $ /bin/sh -xe /tmp/hudson1681495046727357549.sh > + sudo -E /data/hudson/bin/build-chroot.sh webyast rest-service head-i586 > SCRIPT ID: I am /data/hudson/bin/build-chroot.sh at http://yast.suse.de:3334/job/webyast-service-head-i586/ws/ > ..copying source code http://yast.suse.de:3334/job/webyast-service-head-i586/ws/* /data/hudson/HUDSON-CHROOT/webyast-head-i586/src/rest-service > ..copying make script to /data/hudson/HUDSON-CHROOT/webyast-head-i586/root > ... mounting sys > ... mounting proc > ... mounting pts > mount: special device none does not exist > Can't mount devpts /data/hudson/HUDSON-CHROOT/webyast-head-i586/dev/pts > ... switching to chroot and starting build > SCRIPT ID: I am /root/make-zypp.sh at / > > ??,????????'????????,????,????????'????????,????,????????'????????,????,????????'????????,????,????????'????????,?? > > + echo webyast-rest-service > webyast-rest-service > + case "${MODULE}" in > + SUBDIR=webservice > + cd /src/rest-service > + echo /src/rest-service > /src/rest-service > + ls > INSTALL > Makefile > README > Rakefile > doc > index.html.template > plugins > policy-tools > rpam > ruby-polkit > webservice > webservice-tasks > + [[ rest-service == \r\e\s\t\-\s\e\r\v\i\c\e ]] > + echo 'start dbus..' > start dbus.. > + /etc/init.d/dbus start > Starting D-Bus daemon..done > + echo 'Running as root' > Running as root > + echo 'Test plain SCR call' > Test plain SCR call > + echo '`Read(.target.tmpdir)' > + /usr/lib/YaST2/bin/y2base -l - stdio scr > 2009-11-11 13:50:47 <1> golelet(4490) [liby2] genericfrontend.cc(main):668 Launched YaST2 component 'y2base' '-l' '-' 'stdio' 'scr' > 2009-11-11 13:50:47 <1> golelet(4490) [ui-component] YUIComponentCreator.cc(createInternal):113 Creating UI component for "" > 2009-11-11 13:50:47 <1> golelet(4490) [liby2] genericfrontend.cc(main):822 YAST_IS_RUNNING is yes > ([]) > ("/tmp/YaST2-04490-PYIGFy") > ((nil)) > 2009-11-11 13:50:47 <2> golelet(4490) [liby2] Y2StdioComponent.cc(doActualWork):120 Communication ended prior to result () message > 2009-11-11 13:50:47 <1> golelet(4490) [liby2] genericfrontend.cc(main):837 Finished YaST2 component 'y2base' > 2009-11-11 13:50:47 <1> golelet(4490) [liby2] genericfrontend.cc(main):842 Exiting with client return value 'nil' > + check_exit 0 > + '[' -z 0 ']' > + MYEXIT=0 > + '[' 0 == 0 ']' > + echo 'exit code: 0 ... good, lets continue' > exit code: 0 ... good, lets continue > + return > + case "${MODULE}" in > + echo 'Creating shared tasks gem' > Creating shared tasks gem > + pushd webservice-tasks > /src/rest-service/webservice-tasks /src/rest-service > + rake package-local > gem build yast2-webservice-tasks.gemspec > (in /src/rest-service/webservice-tasks) > Updating yast2-webservice-tasks.gemspec (0.0.10)... > Updating package/rubygem-yast2-webservice-tasks.spec (0.0.10)... > WARNING: no description specified > WARNING: no rubyforge_project specified > Successfully built RubyGem > Name: yast2-webservice-tasks > Version: 0.0.10 > File: yast2-webservice-tasks-0.0.10.gem > cp yast2-webservice-tasks-0.0.10.gem package > + echo 'Installing gem...' > Installing gem... > + gem install yast2-webservice-tasks-0.0.10.gem > ERROR: http://gems.rubyforge.org/ does not appear to be a repository > Successfully installed yast2-webservice-tasks-0.0.10 > 1 gem installed > Installing ri documentation for yast2-webservice-tasks-0.0.10... > Installing RDoc documentation for yast2-webservice-tasks-0.0.10... > + popd > /src/rest-service > + sudo rake install_policies > (in /src/rest-service) > (in /src/rest-service/webservice) > Running from /src/rest-service/webservice-tasks/lib/tasks/install_policies.rake > (in /src/rest-service/plugins/time) > Running from /src/rest-service/webservice-tasks/lib/tasks/install_policies.rake > (in /src/rest-service/plugins/patches) > Running from /src/rest-service/webservice-tasks/lib/tasks/install_policies.rake > (in /src/rest-service/plugins/users) > Running from /src/rest-service/webservice-tasks/lib/tasks/install_policies.rake > (in /src/rest-service/plugins/network) > Running from /src/rest-service/webservice-tasks/lib/tasks/install_policies.rake > (in /src/rest-service/plugins/basesystem) > Running from /src/rest-service/webservice-tasks/lib/tasks/install_policies.rake > (in /src/rest-service/plugins/samba_server) > Running from /src/rest-service/webservice-tasks/lib/tasks/install_policies.rake > (in /src/rest-service/plugins/system) > Running from /src/rest-service/webservice-tasks/lib/tasks/install_policies.rake > (in /src/rest-service/plugins/administrator) > Running from /src/rest-service/webservice-tasks/lib/tasks/install_policies.rake > (in /src/rest-service/plugins/registration) > Running from /src/rest-service/webservice-tasks/lib/tasks/install_policies.rake > (in /src/rest-service/plugins/mail_settings) > Running from /src/rest-service/webservice-tasks/lib/tasks/install_policies.rake > (in /src/rest-service/plugins/securities) > Running from /src/rest-service/webservice-tasks/lib/tasks/install_policies.rake > (in /src/rest-service/plugins/language) > Running from /src/rest-service/webservice-tasks/lib/tasks/install_policies.rake > (in /src/rest-service/plugins/services) > Running from /src/rest-service/webservice-tasks/lib/tasks/install_policies.rake > (in /src/rest-service/plugins/eulas) > Running from /src/rest-service/webservice-tasks/lib/tasks/install_policies.rake > (in /src/rest-service/plugins/ntp) > Running from /src/rest-service/webservice-tasks/lib/tasks/install_policies.rake > (in /src/rest-service/plugins/status) > Running from /src/rest-service/webservice-tasks/lib/tasks/install_policies.rake > + check_exit 0 > + '[' -z 0 ']' > + MYEXIT=0 > + '[' 0 == 0 ']' > + echo 'exit code: 0 ... good, lets continue' > exit code: 0 ... good, lets continue > + return > + cat > + check_exit 0 > + '[' -z 0 ']' > + MYEXIT=0 > + '[' 0 == 0 ']' > + echo 'exit code: 0 ... good, lets continue' > exit code: 0 ... good, lets continue > + return > + pushd webservice > /src/rest-service/webservice /src/rest-service > + ruby package/policyKit-rights.rb --user root --action grant > ruby: No such file or directory -- package/policyKit-rights.rb (LoadError) > ++ error_exit 1 > ++ echo 'ERROR: detected exit code 1' > ERROR: detected exit code 1 > ++ footer_and_exit 1 > ++ '[' -z 1 ']' > ++ MYEXIT=1 > ++ '[' 1 == 0 ']' > ++ ascii_failed > ++ cat > > ( ) > ( ) ( > ) _ ) > ( \_ > _(_\ \)__ > (____\___)) > > build failed > > ++ echo 'stopping dbus..' > stopping dbus.. > ++ /etc/init.d/dbus stop > Shutting down D-Bus daemon..done > ++ exit 1 > ... unmounting sys > ... unmounting proc > ... unmounting pts > umount: /data/hudson/HUDSON-CHROOT/webyast-head-i586/dev/pts: not mounted > Can't unmount devpts /data/hudson/HUDSON-CHROOT/webyast-head-i586/dev/pts > [locks-and-latches] Releasing all the locks > [locks-and-latches] All the locks released > Publishing Javadoc > Archiving artifacts > Build wasn't successful, skipping saikuro coverage report > Publishing rails stats report... > [workspace] $ rake --silent stats > Failed to send e-mail to Stefan Schubert because no e-mail address is known, and no default e-mail domain is configured > > -- > To unsubscribe, e-mail: yast-commit+unsubscribe(a)opensuse.org > For additional commands, e-mail: yast-commit+help(a)opensuse.org --- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

2 2

[yast-devel] WebYaST status call 09-Nov-2009
by Duncan Mac-Vicar Prett 11 Nov '09

11 Nov '09

present: mvidnet, jsrain, jsuchome, jreidinger, mkudlvasr, schubi, jdsn, bbrunner, kkaempf, mschmidkunz, dmacvicar mvidner: new image will be renamed to RC1. We will not wait for new license text. appliance_doc branch has announcement AI: kkaempf : remove beta in product metadata (talk to ro) jsrain: opened bugs for backports that should go to SLE11GA yast2-storage can be removed after core is there (and see what happens) jsuchome: pepa log viewer, removing SCR::execute looking in some checking permissions bug discussion about permission checking on the client jreidinger: rewrote permissions module, changed behavior today: log viewer, if works bug about SCR::execute can be closed mkudlvasr : testing RC1, REST API docs schubi: images icons licenses, COPYING jdsn: fixing hudson, test RC1 bbrunner: test RC1, filed bugs kkaempf: thanks! for RC1. mschmidkunz: status UI dmacvicar: fixed yast2-ruby-bindings, cleanup bugzilla/fate -- Duncan Mac-Vicar P. - Engineering Manager, YaST SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

2 2

[yast-devel] Versioning YaST packages in the Code11 branch
by Jiri Srain 10 Nov '09

10 Nov '09

Hi! I recently noticed that several of us use incorrect versioning of the packages in the Code-11 branch in SVN (which means for SLES11 and/or openSUSE 11.1 maintenance updates). To summarize: SuSE-Code-11-Branch: 2.17.x.y, where 1.17.x is the version which was released in SLES11 and y is increasing with every new submit SuSE-Code-11-SP1-Branch 2.17.x, where x is increasing with every new submit This ensures that we avoid having two different packages (one from Code-11 branch and another one from SP1 branch) with the same version. Please, follow this policy strictly. The only exception is when the SP1 and Code11 packages are the same. Thanks! Jiri -- Regards, Jiri Srain YaST Team Leader --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain(a)suse.cz Lihovarska 1060/12 tel: +420 284 028 959 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 0

[yast-devel] git question
by Martin Schmidkunz 09 Nov '09

09 Nov '09

Hi, when committing my stuff I first use "git commit -a -m "explanatory text"" and then "git push" But when using "git push" I receive the following message: To git+ssh://git@git.opensuse.org/projects/yast/web-client.git ! [rejected] master -> master (non-fast forward) error: failed to push some refs to 'git+ssh://git@git.opensuse.org/projects/yast/web-client.git' To prevent you from losing history, non-fast-forward updates were rejected. Merge the remote changes before pushing again. See 'non-fast forward' section of 'git push --help' for details. Unfortunately the git help was not useful for me, so I hope that someone can help me answering my questions: * how can I avoid this message? * are my changes committed at all? (couldn`t spot them at http://git.opensuse.org/?p=projects/yast/web-client.git;a=summary) Thanks and have a nice evening, Martin -- Martin Schmidkunz User Experience Specialist martin.schmidkunz(a)novell.com +49 (0) 911 740 53-346 ----------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) ----------------------------------------------------------------- Novell, Inc. SUSE® Linux Enterprise 10 Your Linux is ready http://www.novell.com/linux -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

2 2

[yast-devel] Re: [opensuse-ruby] WebYaST: loading patches and status in the control center
by Klaus Kaempf 09 Nov '09

09 Nov '09

[Switching discussion to yast-devel] * Ladislav Slezak <lslezak(a)suse.cz> [Nov 09. 2009 14:27]: > > Hi all, > > I'd like to discuss the problem reported in bug #550934 > ('It takes minutes to refresh "system is up to date" and "system is healthy"') > > It takes very long time to load the initial patches and system status information > which is displayed on the first page (the WebYaST control center) using AJAX requests. > > I already have implemented caching in the patches module so the available patches are > not evaluated in every control center reload. But the first call still takes much time... > > The problem is that the first patch status request triggers repository metadata > download and cache rebuild which in case of slow/bad/overloaded network connection > can take several minutes (as reported in the bug). > > A similar problem is in the status module, but not that serious - the status is read > from the local machine so network is not involved in this case. And even on a slow > machine it won't block for more than several seconds. > > > I have these possible solutions for reading the patch status: > > * don't display the status messages at all (IMO bad solution, I find the overview > messages quite useful...) > > * make displaying of the status messages configurable (so users can hide and disable > status loading if it's too slow) > > * use a background job for reading patches (display a generic message like > "Reading patches" when the request takes too long and refresh the status after > some time again to get the real status.) > > AFAIK an AJAX request cannot be stopped (at least the [Stop] button in FF is disabled > when the page is loaded but an AJAX request is in progress). > > I'd prefer the last solution. Me too. Its important to present a honest explanation without being too technical. Maybe adding more steps to visualize progress would be helpful, i.e. "contacting update server", "retrieving update information", "evaluating update information", ... Klaus --- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 0

[yast-devel] Webyast: Changing permissions to not use Scr (bnc#472752)
by Josef Reidinger 09 Nov '09

09 Nov '09

Hi, as part of removing Scr.Execute I plan to remove it from permissions module and I have three questions: 1) Does we support granting or removing permissions for users this release ( the most problematic part as granting permission is really great permission) ? 2) is problem if anyone can read what permissions have any user? (Maybe I can restrict it only to current login user, but then permissions module have problem) 3) Have yastws always enough permissions to run polkit-auth and polkit-action? (for current appliance yes) Thanks Josef -- Josef Reidinger YaST team maintainer of perl-Bootloader, YaST2-Repair, webyast modules language and time -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

2 1

[yast-devel] permissions rewrite
by Martin Kudlvasr 09 Nov '09

09 Nov '09

irc.suse.de#rails > <jreidinger> schubi: Who is owner of permissions rest service? I found it > that implementation is ... not good. I plan to rewrite it to use model, > because now it is badly testable. I had the same feeling when I went through the code 2 days ago. I just didn't want to break the RC release (and had some bugs to solve). The work in progress is in "refactor-permissions" branch. Martin -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

4 4

[yast-devel] openSUSE 11.2 review, some critics on YaST
by Klaus Kaempf 09 Nov '09

09 Nov '09

YaSTies, watch starting at approx. 1:30 http://www.youtube.com/watch?v=vquPKhszDes Klaus --- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 0

[yast-devel] Images/icons in WebYaST
by Stefan Schubert 06 Nov '09

06 Nov '09

Hi, I have cleaned up the images and icons directory and have added a COPYING file. For the future please make an entry in COPYING ( where the image comes from and the concerning license) when you add a new image/icon. Thank you and greetings Stefan -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 0