Bug 566859 - ECA-04 when trying to accept license agreement
Summary: ECA-04 when trying to accept license agreement
Status: RESOLVED FIXED
Alias: None
Product: Community
Classification: Eclipse Foundation
Component: Accounts.eclipse.org (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 major with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Generic Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-09-10 09:37 EDT by Nils Wistoff CLA
Modified: 2021-08-10 07:50 EDT (History)
5 users (show)

See Also:


Attachments
Error message (19.65 KB, image/png)
2020-09-10 09:37 EDT, Nils Wistoff CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Nils Wistoff CLA 2020-09-10 09:37:12 EDT
Created attachment 284104 [details]
Error message

Hello,

I filled out and accepted the ECA. However, there is a red error symbol next to 'Eclipse Contributor Agreement'. When ever I try to resubmit, I get the following error: 'Error, An error has occured and your Eclipse Contributor Agreement was not submitted. (ECA-04)' (see attachment).

Best,
Nils Wistoff

PS: There was a typo in my last name when I created my account. Perhaps this is related...
Comment 1 Eclipse Webmaster CLA 2020-09-11 10:39:49 EDT
After talking to the webdev team, this error can be thrown when there is a replication delay in the backend.  I took a look and indeed our replica had stopped accepting new events.  That has been fixed, and it's now caught up, so please try to accept the ECA again.

-M.
Comment 2 Christopher Guindon CLA 2020-11-10 08:52:09 EST
(In reply to Eclipse Webmaster from comment #1)
> After talking to the webdev team, this error can be thrown when there is a
> replication delay in the backend.  I took a look and indeed our replica had
> stopped accepting new events.  That has been fixed, and it's now caught up,
> so please try to accept the ECA again.
> 
> -M.

This issue is expected if the slave is out of sync.

Thanks for reporting!
Comment 3 Javier Llorente CLA 2021-08-03 14:40:05 EDT
Hello,
I am getting the same error (ECA-04).
Could you please take a look at it?

Greetings,
Javier
Comment 4 Eric Poirier CLA 2021-08-04 08:24:23 EDT
(In reply to Javier Llorente from comment #3)
> Hello,
> I am getting the same error (ECA-04).
> Could you please take a look at it?
> 
> Greetings,
> Javier

Hi Javier,

Thanks for reporting this. I had a look at the code and this error is due to a database being out of sync.

@webmaster, can you have a look at this when you have the chance? The eclipsefoundation secondary db (slave) is out of date.

Thanks.
Comment 5 Jeen Broekstra CLA 2021-08-09 05:43:59 EDT
Hi folks, we're hitting the same (or closely related) issue on our project for a new contributor. They claim they've signed the ECA but I can't verify it: the ECA validator doesn't recognize their address. When they try to log in and sign it again to make sure, they get this ECA-04 error. 

See https://github.com/eclipse/rdf4j/pull/3269#issuecomment-893212448
Comment 6 Eclipse Webmaster CLA 2021-08-09 15:40:34 EDT
(In reply to Eric Poirier from comment #4)

The slave DB is showing up to date, so everything should be ok.

-M.
Comment 7 Eric Poirier CLA 2021-08-10 07:34:34 EDT
(In reply to Jeen Broekstra from comment #5)
> Hi folks, we're hitting the same (or closely related) issue on our project
> for a new contributor. They claim they've signed the ECA but I can't verify
> it: the ECA validator doesn't recognize their address. When they try to log
> in and sign it again to make sure, they get this ECA-04 error. 
> 
> See https://github.com/eclipse/rdf4j/pull/3269#issuecomment-893212448

By looking at the github issue, it seems that the error has been resolved. Can you confirm that it is working now?

Thanks.
Comment 8 Jeen Broekstra CLA 2021-08-10 07:41:20 EDT
Yes, sorry, should have thought of that, it's been resolved! Thanks for taking care of it.

Cheers,

Jeen
Comment 9 Eric Poirier CLA 2021-08-10 07:50:34 EDT
(In reply to Jeen Broekstra from comment #8)
> Yes, sorry, should have thought of that, it's been resolved! Thanks for
> taking care of it.
> 
> Cheers,
> 
> Jeen

Perfect, thanks for confirming.

Closing this bug now, but please reopen if the issue comes back.

Thanks!