Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 326202

Summary: [repository][transport] Provide better error messages for mirror timeouts
Product: [Eclipse Project] Equinox Reporter: Jeff McAffer <jeffmcaffer>
Component: p2Assignee: P2 Inbox <equinox.p2-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: enhancement    
Priority: P3 CC: curtis.windatt.public, pascal
Version: 3.6   
Target Milestone: ---   
Hardware: PC   
OS: Mac OS X - Carbon (unsup.)   
Whiteboard: stalebug

Description Jeff McAffer CLA 2010-09-24 17:28:55 EDT 
using 3.6.1 on Helios SR1 repo...

We setup a target that used the Helios SR1 repo as a software site and selected a few features. After setting this as a the current target PDE proceeded to download the bundles.  Ultimately the following flavor of error was surfaced to the user

No repository found containing: binary, org.eclipse.equinox.executable_root.win32…………

over and over. Looking in the .log it appears that various mirrors are timing out. Of course, this is the release day of SR1 and delays/timeouts are inevitable. Simply trying again (and again) later resolves this problem. Unfortunately users don't know this and they are led to believe that they have done something wrong or that there is something corrupted/missing on the server or...  when really its just a timeout.

I realize that PDE is reusing p2 infrastructure but suspect that with some tweaks the p2 infrastructure could surface more interesting information. Your advice on what needs to change will help guide the p2 team in that effort so that the PDE workflows are nice for users.
Comment 1 Curtis Windatt CLA 2010-09-27 14:39:21 EDT 
Moving to p2.

PDE displays the errors exactly as p2 reports them to us.  I don't think there needs to be any major changes in this case, just a more detailed error message.  If the user received this error while installing software it would be confusing there too, the problem isn't unique to PDE. 

If p2 is concerned about hammering the user with complex error messages, it would be nice to have an alternative way of getting more details.
Comment 2 Lars Vogel CLA 2019-11-27 07:25:56 EST 
This bug hasn't had any activity in quite some time. Maybe the problem got
resolved, was a duplicate of something else, or became less pressing for some
reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it.
The information can be, for example, that the problem still occurs, that you
still want the feature, that more information is needed, or that the bug is
(for whatever reason) no longer relevant.

If the bug is still relevant, please remove the stalebug whiteboard tag.