Bug 16711 - interminable search when update site does not respond
Summary: interminable search when update site does not respond
Status: RESOLVED DUPLICATE of bug 16479
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Update (deprecated - use Eclipse>Equinox>p2) (show other bugs)
Version: 2.0   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Vlad Klicnik CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-05-21 20:32 EDT by Jim des Rivieres CLA
Modified: 2002-05-28 10:48 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jim des Rivieres CLA 2002-05-21 20:32:26 EDT
build 20020521 1339

I have a product install who's primary feature's feature.xml
includes the following update site URL:

  <url>
     <update 
         url="http://com.example.company1/myproduct/updates"
         label="Company One updates for My Product">
     </update>

     <discovery
         url="http://download.eclipse.org/updates"
         label="Eclipse Nevada Test Site">
     </discovery>
  </url>

1. open the update manager
2. select "Available Updates"
3. hit search now, 

Observe: it says "Company One updates for My Product"
(presumably opening http://com.example.company1/myproduct/updates,
which does not exist). It says "Search in progress..."
It never comes back.

Expectation: It should fail immediately (IE does).

4. Hit cancel

Observe: The "Cancel" button is greyed. But that's it.
The search continues.

Expectation: The search should be cancelled.

(The first time this happened, the only thing I could
think of doing was to close the product. I was surprised
when it saved the workspace. Later I realized that the
search is not modal (but perhaps it show be?).
Comment 1 Vlad Klicnik CLA 2002-05-24 12:38:38 EDT

*** This bug has been marked as a duplicate of 16479 ***
Comment 2 Dejan Glozic CLA 2002-05-28 10:48:13 EDT
Search is not modal because it was designed to run in the background and not 
block the UI. Searching for new upades may take a long time. The search itself 
is executing on a non-modal background thread and progress indicator is simply 
updated when there are news to report. Search can run with no UI whatsoever 
(for example, launched on startup in as a low priority background thread).