Bugzilla – Full Text Bug Listing
| Summary: | Automated Error Reporting (AERI) Server not reachable | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Community | Reporter: | Alois Zoitl <alois.zoitl> | ||||
| Component: | Servers | Assignee: | Eclipse Webmaster <webmaster> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | chris.guindon, denis.roy, thatnitind, wayne.beaton | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| Whiteboard: | stalebug | ||||||
| Attachments: |
|
||||||
|
Description
Alois Zoitl
As part of archiving a project we shutdown any vservers they may have been operating, so yes the AERI infrastructure is offline. I guess the recommendation is for projects that used AERI to remove it's code/plugin from their code bases. There is also the possibility that any projects that depend on this functionality could volunteer to keep the AERI service running for the whole community. We should also look at removing the link to the AERI login, but I don't happen to see it on the accounts page. Can you provide the page that links to it? -M. FWIW, I've initiated a discussion with the Eclipse Architecture Council on their mailing list to gather their insights and opinions regarding what we should do with AERI, and to solicit their participation in driving a more permanent solution. The short version is that this is/was a service provided by the Eclipse Code Recommenders project. With that project no longer staffed, AERI no longer has any committers working on it or providing support. Thanks for all the clarifications. This really helped me to understand the situation. I think it would be good to get feedback from the Eclipse Architecture council. The last time I could log into this server I saw that there where at least a 100 different project collecting there feedback on potential issue. And in principle if I remember correctly the AERI eclipse plugin is still part of EPP. I can only speak for Eclipse 4diac, but it helped us a lot to improve stability of our 4diac IDE. For us it must not be as fancy as the infrastructure provided up to now. But haveing a simple and easy to use way to submit execution issues would be a great benefit. Created attachment 279917 [details]
Snapshot of the commiter tools
Please find here attached a screenshot snippet from the commiter tools where there is the link to the AERI infrastructure.
(In reply to Alois Zoitl from comment #3) > And in principle if I remember correctly the AERI eclipse > plugin is still part of EPP. AFAIK, the AERI plug-ins were last included in the 2018-12 packages. I believe that they were removed from all packages when Eclipse Code Recommenders dropped out of 2019-03. > I can only speak for Eclipse 4diac, but it helped us a lot to improve > stability of our 4diac IDE. For us it must not be as fancy as the > infrastructure provided up to now. But haveing a simple and easy to use way > to submit execution issues would be a great benefit. Understood. To have your input considered by the Architecture Council (AC), I recommend that you connect with your PMC (via their mailing list) to request that the PMC representative to the AC represent your case. At this point, unless somebody steps up to take on responsibility for (at least) the plug-ins, the future doesn't look good for AERI. (In reply to Alois Zoitl from comment #4) > Created attachment 279917 [details] > Snapshot of the commiter tools > > Please find here attached a screenshot snippet from the commiter tools where > there is the link to the AERI infrastructure. Chris, can you remove this entry while we sort out what we're going to do? >
> > I can only speak for Eclipse 4diac, but it helped us a lot to improve
> > stability of our 4diac IDE. For us it must not be as fancy as the
> > infrastructure provided up to now. But haveing a simple and easy to use way
> > to submit execution issues would be a great benefit.
>
> Understood. To have your input considered by the Architecture Council (AC),
> I recommend that you connect with your PMC (via their mailing list) to
> request that the PMC representative to the AC represent your case. At this
> point, unless somebody steps up to take on responsibility for (at least) the
> plug-ins, the future doesn't look good for AERI.
Thanks I'll do that.
(In reply to Wayne Beaton from comment #6) > (In reply to Alois Zoitl from comment #4) > > Created attachment 279917 [details] > > Snapshot of the commiter tools > > > > Please find here attached a screenshot snippet from the commiter tools where > > there is the link to the AERI infrastructure. > > Chris, can you remove this entry while we sort out what we're going to do? +1 I am currently re-building the site to remove the link! *** Bug 551125 has been marked as a duplicate of this bug. *** 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. -- The automated Eclipse Genie. I think this is done. |