Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] [eclipse-mirrors] Mirror issues

First off: thank you for considering our bandwidth! It is much appreciated.

We have since tweaked download.e.o so that, if you choose to not access mirrors, we will round-robin to mirrors based on the client's location (for files > 500KB). In that case, a retry to download.e.o may result in a different mirror for the same file, which may make your builds more reliable.

My suggestion: use the p2 mirrors mechanism, and if the same mirror fails repeatedly, then please report it and we'll remove it.


Thanks,

Denis


On 2018-10-04 01:38 PM, Ernesto Posse wrote:
I didn’t manually set the mirrors. My tycho build is using whatever the default is. My latest build did succeed but checking the log I see that it did not use mirror.cc.vt.edu

My build is working for now, but for future builds I could try Nick’s suggestion of avoiding mirrors, but that, of course, is not ideal, as I don’t want to overuse bandwidth.

I’m not sure who exactly picks the mirrors: p2 or tycho? In any case, I would have hoped that whenever a mirror fails on an artiact for some reason, a different mirror would be tried. Perhaps this functionality has already been implemented? If not, I could file a bug, but on which component? p2? tycho? some other component?

Thanks


On Oct 4, 2018, at 1:20 PM, Denis Roy <denis.roy@xxxxxxxxxxxxxxxxxxxxxx> wrote:

Mirrors are one of those things... I think that specific mirror has occasional connectivity issues, since it's not the first time I see this error.

Can you switch to another mirror?

We could pull that mirror from the list if it becomes problematic, but over the last decade it has served many a terabyte.


Denis



On 2018-10-04 12:16 PM, Ernesto Posse wrote:
Thanks. Yes, that is a possibility, but unfortunately the product I’m building must be built on Neon due to some dependencies (which are absolutely necessary for the product but run only on Neon). Sometimes it is necessary to build products with older dependencies, specially when maintaining legacy applications.

Anyway, the build is now working, so maybe that was just a temporary network issue for the mirror in question, but thanks for the suggestion.

--
Ernesto Posse
Zeligsoft (2009) Ltd.



On Oct 3, 2018, at 7:22 PM, Nick Boldt <nboldt@xxxxxxxxxx> wrote:

At the risk of being That Guy, have you considered that the mirrors are trashing their ancient releases and moving up to the newer stuff?

Neon is so a couple years ago. 2016 was a much simpler time. Now we live in the Photon and 2018-09 world. Can you use one of those instead?

There's also a flag to disable using the mirrors and just pull directly from Eclipse.org




Nick

On Wed, Oct 3, 2018 at 5:20 PM Ernesto Posse <eposse@xxxxxxxxx> wrote:
Hi. I’m trying to build a project which downloads Neon artifacts from http://mirror.cc.vt.edu/pub/eclipse/releases/neon/ but I keep getting errors like this:

[INFO] Fetching org.eclipse.e4.ui.model.workbench_1.2.0.v20160229-1459.jar.pack.gz from http://eclipse.mirror.rafal.ca/releases/neon/201705151400/plugins/ (106.56kB)
[INFO] Unpacking org.eclipse.e4.ui.model.workbench_1.2.0.v20160229-1459...
[ERROR] An error occurred while transferring artifact packed: osgi.bundle,org.eclipse.e4.ui.services,1.2.100.v20160506-0759 from repository http://download.eclipse.org/releases/neon:
[ERROR]    Retry another mirror:
[ERROR] Internal error: org.eclipse.tycho.repository.local.MirroringArtifactProvider$MirroringFailedException: Could not mirror artifact osgi.bundle,org.eclipse.e4.ui.services,1.2.100.v20160506-0759 into the local Maven repository.See log output for details. Network is unreachable (connect failed) -> [Help 1]

(not only for org.eclipse.e4.ui.services_1.2.100 but other artifacts as well)

Is anyone else seeing these problems? Is this particular mirror (http://mirror.cc.vt.edudown? 

Thanks,

--
Ernesto Posse
Zeligsoft (2009) Ltd.



_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


--
Nick Boldt
Principal Software Engineer, RHCSA
Productization Lead :: JBoss Tools & Dev Studio

IM: @nickboldt / @nboldt / http://nick.divbyzero.com



“The Only Thing That Is Constant Is Change” - Heraclitus
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



_______________________________________________
eclipse-mirrors mailing list
eclipse-mirrors@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/eclipse-mirrors

--
Denis Roy
Director, IT Services | Eclipse Foundation, Inc.
Twitter: @droy_eclipse
Meet us at EclipseCon Europe 2018: LUDWIGSBURG, OCTOBER 23 - 25
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

--

Denis Roy

Director, IT Services | Eclipse Foundation, Inc.

Twitter: @droy_eclipse

Meet us at EclipseCon Europe 2018: LUDWIGSBURG, OCTOBER 23 - 25


Back to the top