| Summary: | can't invalidate ECA, can't sign ECA | ||
|---|---|---|---|
| Product: | Community | Reporter: | Ulf Caspers <UCaspers> |
| Component: | Accounts.eclipse.org | Assignee: | Eclipse Web <webdev> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | chris.guindon, chrisguindon84+new9, eric.poirier, thatnitind, webmaster |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows NT | ||
| Whiteboard: | |||
|
Description
Ulf Caspers
Hi Ulf, We were having problems with our databases and Friday night and it might be the cause of your problem. Can you try to invalidate again your ECA and resign it? Thanks. The situation hasn't changed. I still can't invalidate my ECA and I can't sign a new one. Although less of an issue so far, my links in Bugzilla show that I haven't signed it, but the page for signing says "The Eclipse Contributor Agreement that we have on record for you will expire on 2019-09-01" (which seems unusually far ahead?). (In reply to Ulf Caspers from comment #2) > The situation hasn't changed. I still can't invalidate my ECA and I can't > sign a new one. There was an issue with our new account moderation tool and I deployed a patch to fix it a few minutes ago. I did a few tests and it's working for me now, can you confirm? (In reply to Nitin Dahyabhai from comment #3) > Although less of an issue so far, my links in Bugzilla show that I haven't > signed it, but the page for signing says "The Eclipse Contributor Agreement > that we have on record for you will expire on 2019-09-01" (which seems > unusually far ahead?). A cla is valid for 3 years. The date is correct if you signed in on Sept 1st, 2016. If the bugzilla sign says you did not sign the CLA, it means that you are not in the cla group. Can you try revoking it and re-siging it? (In reply to christopher guindon from comment #4) > (In reply to Ulf Caspers from comment #2) > > The situation hasn't changed. I still can't invalidate my ECA and I can't > > sign a new one. > > There was an issue with our new account moderation tool and I deployed a > patch to fix it a few minutes ago. > > I did a few tests and it's working for me now, can you confirm? Signing a new ECA worked for me now. But at time of writing these lines my ECA sign in bugzilla is still red. I will try a new push to gerrit on thursday and report the results here. (In reply to Ulf Caspers from comment #6) > (In reply to christopher guindon from comment #4) > > (In reply to Ulf Caspers from comment #2) > > > The situation hasn't changed. I still can't invalidate my ECA and I can't > > > sign a new one. > > > > There was an issue with our new account moderation tool and I deployed a > > patch to fix it a few minutes ago. > > > > I did a few tests and it's working for me now, can you confirm? > > Signing a new ECA worked for me now. But at time of writing these lines my > ECA sign in bugzilla is still red. I will try a new push to gerrit on > thursday and report the results here. You are not seeing the new eca badge because your browser is caching the previous image. I see the green badge next to your name, it looks like everything is working! Keep me posted if you experience any other issues. (In reply to christopher guindon from comment #5) > If the bugzilla sign says you did not sign the CLA, it means that you are > not in the cla group. > > Can you try revoking it and re-siging it? Looks better. (In reply to Nitin Dahyabhai from comment #8) > (In reply to christopher guindon from comment #5) > > If the bugzilla sign says you did not sign the CLA, it means that you are > > not in the cla group. > > > > Can you try revoking it and re-siging it? > > Looks better. Awesome! Looks like things are back to normal! Thanks everyone for your time and feedback to get this resolved! |