Bugzilla – Full Text Bug Listing
| Summary: | Unable to create initial contribution CQ for LemMinX | ||
|---|---|---|---|
| Product: | Community | Reporter: | Fred Bricon <fbricon> |
| Component: | Project Management & Portal | Assignee: | Eclipse Web <webdev> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | chris.guindon, eric.poirier, okurinny, wayne.beaton, webmaster |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Mac OS X | ||
| Whiteboard: | |||
|
Description
Fred Bricon
I can confirm this issue. I see the following log associated with your user: Exception: Internal Error in BugBuilder->create() (line 257 of ..pmi/bugzilla/BugzillaClient.class.inc). @eric can you investigate? It seems that the Internal Error is from posting data to ipzilla. Fred, I will need to reproduce the error. Can you describe each step that you took starting with this page: https://projects.eclipse.org/projects/technology.lemminx/cq/create From https://projects.eclipse.org/projects/technology.lemminx/cq/create: - select Project Content (Content to be maintained by an Eclipse Foundation Project) - click continue - What is the name of the contribution?: Initial contribution for LemMinx - Description: Initial code contribution for LemMinX. A part of the XML parser has been written as a “transcription” of some code present in the VSCode HTML Language Service (copyright Microsoft Corporation, MIT-licensed), from TypeScript to Java. Affected files are clearly identified in their copyright headers. - Reason: Initial contribution to the project - Contribution record: https://bugs.eclipse.org/bugs/show_bug.cgi?id=553372 - Cryptography No - Authors: Lines Author Email Organization % 1 Felix Becker felix.b@outlook.com SourceGraph 0.00011% 1 Heyward Fann fannheyward@gmail.com - 0.00011% 1 Martin Lippert mlippert@gmail.com Pivotal 0.00011% 3 Jonathan Burstein jonathan@jargon.com - 0.00034% 6 Vildan Softic zewa666@gmail.com - 0.00068% 37 Lindsey Tulloch ltulloch@redhat.com Red Hat 0.00419% 65 Snjezana Peco snjezana.peco@redhat.com Red Hat 0.00735% 94 Andrew Obuchowicz aobuchow@redhat.com Red Hat 0.01063% 149 Mickael Istria mistria@redhat.com Red Hat 0.01686% 317 Dennis Huebner dennis.huebner@gmail.com Typefox 0.03586% 1265 Seiphon wang seiphon.wang@liferay.com Liferay 0.14310% 1397 Fred Bricon fbricon@gmail.com Red Hat 0.15804% 2353 David Kwon dakwon@redhat.com Red Hat 0.26619% 17668 Nikolas Komonen nikolaskomonen@gmail.com Red Hat 1.99871% 860612 Angelo Zerr angelo.zerr@gmail.com Red Hat 97.35771% It appears to be broken for Dash as well. I think that we can assume that everybody is broken. Based on the log entry, IPZilla is returning an unexpected result. I'd start by checking that the PMI is able to reach IPzilla. Then, check with webmaster that the genie credentials haven't been changed. Fred, I deployed a temporary fix to the cq form which should allow you to submit your CQ now. When posting to ipzilla, the value for the bug severity was empty which is causing the internal error. I fix it by setting the bug severity to 'new' for all new cq. Eric, please take a look at this on monday! We need a better fix than the one I posted just now! (In reply to Christopher Guindon from comment #5) > Fred, > > I deployed a temporary fix to the cq form which should allow you to submit > your CQ now. > > When posting to ipzilla, the value for the bug severity was empty which is > causing the internal error. > > I fix it by setting the bug severity to 'new' for all new cq. > > Eric, please take a look at this on monday! We need a better fix than the > one I posted just now! I created the following patch to fix this issue. https://foundation.eclipse.org/r/c/drupal/custom/pmi/+/3786 We were not using the proper value for the "Awaiting IP" bug severity field. I looked in the production database and there is an "awaiting_ipteam" bug severity value and I also confirmed with Sharon that this is the proper key to use. I will rebuild the PMI as soon as this patch is merged. Was hoping to get through Chris' fix, but it failed again (In reply to Fred Bricon from comment #7) > Was hoping to get through Chris' fix, but it failed again I was able to login as you and submit a CQ: https://dev.eclipse.org/ipzilla/show_bug.cgi?id=21713 Can you login/logout and start the process from scratch? https://projects.eclipse.org/projects/technology.lemminx/cq/create (In reply to Christopher Guindon from comment #8) > (In reply to Fred Bricon from comment #7) > > Was hoping to get through Chris' fix, but it failed again > > I was able to login as you and submit a CQ: > https://dev.eclipse.org/ipzilla/show_bug.cgi?id=21713 > > Can you login/logout and start the process from scratch? > > https://projects.eclipse.org/projects/technology.lemminx/cq/create logout and login :) I managed to create the CQ from Firefox: https://dev.eclipse.org/ipzilla/show_bug.cgi?id=21714. Thanks! For some reason, I couldn't log out from Chrome (nothing happened when clicking on the log out link, ie., page reloaded but I was still logged in) I faced same issue trying to create a CQ both on Chrome and Firefox as well. https://projects.eclipse.org/projects/ecd.che/cq/create/summary shows the page with the error message "The website encountered an unexpected error. Please try again later." I was just able to create a "project code" CQ for Eclipse Dash using Firefox. I don't see anything in the code that should make this browser-specific, so I'm wondering if there might be a browser cache issue. (In reply to Oleksii Kurinnyi from comment #11) > I faced same issue trying to create a CQ both on Chrome and Firefox as well. > https://projects.eclipse.org/projects/ecd.che/cq/create/summary shows the > page with the error message "The website encountered an unexpected error. > Please try again later." Reopening. (In reply to Oleksii Kurinnyi from comment #11) > I faced same issue trying to create a CQ both on Chrome and Firefox as well. > https://projects.eclipse.org/projects/ecd.che/cq/create/summary shows the > page with the error message "The website encountered an unexpected error. > Please try again later." Oleksii, When did you start creating your CQ? Today or while it was already broken? Can you send me the information you are trying to fill-in, I will try to login as you and submit the cq to see if I can reproduce this error. (In reply to Christopher Guindon from comment #13) > (In reply to Oleksii Kurinnyi from comment #11) > > I faced same issue trying to create a CQ both on Chrome and Firefox as well. > > https://projects.eclipse.org/projects/ecd.che/cq/create/summary shows the > > page with the error message "The website encountered an unexpected error. > > Please try again later." > > Oleksii, > > When did you start creating your CQ? Today or while it was already broken? > > Can you send me the information you are trying to fill-in, I will try to > login as you and submit the cq to see if I can reproduce this error. Hello Christopher, The last my attempt was half an hour earlier than I reported the issue. Steps to create the CQ: From https://projects.eclipse.org/projects/ecd.che/cq/create select "Third-Party Code Request..." . On the next page: - Name and Version of the Library "@patternfly/patternfly@2.65.3" Then on page Create a Contribution Questionnaire: - Please choose one of the following: Request IP Team Assistance - Description PatternFly is an open source design system built to drive consistency and unify teams. - Intellectual Property Rights No - Cryptography No - Project Website of the Contribution https://github.com/patternfly/patternfly-next - Source URL https://github.com/patternfly/patternfly-next/archive/v2.65.3.zip - License MIT - Distribution Binary Only - Modified Unmodified (Usual Case) Oleksii, You should of received by now n email regarding this cq. I created it for you to test this problem. The bug is still on our servers but I have a patch under code review to address this problem. Christopher, thanks! Hopefully it will be fixed soon. (In reply to Oleksii Kurinnyi from comment #16) > Christopher, thanks! > > Hopefully it will be fixed soon. We are planning to deploy the patch this morning! (In reply to Christopher Guindon from comment #17) > (In reply to Oleksii Kurinnyi from comment #16) > > Christopher, thanks! > > > > Hopefully it will be fixed soon. > > We are planning to deploy the patch this morning! The patch has been deployed successfully. Let me know if there's anything else. Thanks. (In reply to Eric Poirier from comment #18) > (In reply to Christopher Guindon from comment #17) > > (In reply to Oleksii Kurinnyi from comment #16) > > > Christopher, thanks! > > > > > > Hopefully it will be fixed soon. > > > > We are planning to deploy the patch this morning! > > The patch has been deployed successfully. > > Let me know if there's anything else. > > Thanks. thanks |