Mailinglist Archive: opensuse-bugs (4664 mails)

< Previous Next >
[Bug 537883] YaST Package Management UI becomes unresponsive if a network repository is unavailable
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Wed, 3 Feb 2010 11:40:13 +0000
  • Message-id: <20100203114013.4F834CC7CE@xxxxxxxxxxxxxxxxxxxxxx>
http://bugzilla.novell.com/show_bug.cgi?id=537883

http://bugzilla.novell.com/show_bug.cgi?id=537883#c16


Michael Andres <ma@xxxxxxxxxx> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |ma@xxxxxxxxxx

--- Comment #16 from Michael Andres <ma@xxxxxxxxxx> 2010-02-03 11:40:11 UTC ---
(In reply to comment #14)
@ma: what do you think about running some operations, like the curl downloads,
in new threads (c#11)? Another potential candidate for this is the building of
the @System.solv, which also takes all ranges of time, without any report. Or
should we avoid this and leave it on the UIs?

@System.solv: The missing progress is my fault. I lost bug #438622.
I'll fix that ASAP.

@curl: We are far from being thread safe (but we'll improve this for 11.3).
Nevertheless it could be possible to run curl_perform in a thread and do a
timed_join to guarantee at least one callback per second. Only join loop and
curl callback need to be synchronized.

But what I don't know, is how to cleanly abort the other threads curl_perform
that's waiting for a connect/data, if the timed callback says 'ABORT'.


A commandline tool like aria2c is far easier to handle. You can do a timed read
on the pipe, and kill it in case of abort. Maybe it's an option to use 'curl'
instead of 'libcurl' in the future. This could also ease the task to implement
parallel downloads, which is one of the tops for 11.3.

--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >
This Thread
  • No further messages