Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

EasyCLA: 502 error appears request-employee-signature api at ECLA flow #4225

Closed
thakurveerendras opened this issue Feb 1, 2024 · 9 comments
Closed

EasyCLA: 502 error appears request-employee-signature api at ECLA flow #4225

thakurveerendras opened this issue Feb 1, 2024 · 9 comments
Assignees
@mlehotskylf @nickmango
Labels
bug Something isn't working Regression Issue/Bug related to a previously working feature that is now failing

Comments

@thakurveerendras
Copy link
Contributor

Summary

EasyCLA: 502 error appears request-employee-signature api at ECLA flow

Background

  1. Create a new GitLab branch
  2. Create new PR(cla gated)
  3. Click on the Not Covered button
  4. Click on proceed as Corporate Contributor
  5. Search & select Organization & click on the proceed button

Actual behavior

502 error appears request-employee-signature api at ECLA flow

Screenshots

image
@thakurveerendras thakurveerendras added the bug Something isn't working label Feb 1, 2024
@mlehotskylf
Copy link
Contributor

According to @nickmango, this issue is fixed to moving to Ready for QA.

@thakurveerendras
Copy link
Contributor Author

Tested issue on GitHub & GitLab MR and found that issue is not reproducible as reported.

@thakurveerendras
Copy link
Contributor Author

Retested issue with new user & found that it is failed again, So reopening this ticket

image

@thakurveerendras thakurveerendras added the Regression Issue/Bug related to a previously working feature that is now failing label Feb 2, 2024
@nickmango
Copy link
Collaborator

nickmango commented Feb 5, 2024 •
edited
Loading

@thakurveerendras I am unable to reproduce this issue. Kindly help me reproduce

@mlehotskylf
Copy link
Contributor

@thakurveerendras to check with Pooja if this is still reproducible.

nickmango added a commit to nickmango/easycla that referenced this issue Feb 6, 2024
@nickmango
[communitybridge#4225,communitybridge#4228] Bug/Incorrect date format…
b734abb 
… for ccla

- Resolved wrong date_modified format for ccla signature
- Handled none values for ecla signature_reference_name attribute

Signed-off-by: Harold Wanyama <[email protected]>
nickmango added a commit that referenced this issue Feb 6, 2024
@nickmango
Merge pull request #4232 from nickmango/bug/signature-date-format
2adfda1 
[#4225,#4228] Bug/Incorrect date format for ccla
@thakurveerendras
Copy link
Contributor Author

the root cause of this issue is the wrong "date_modified" format. it will automatic fix after fixes of issue #4231

@nickmango nickmango mentioned this issue Feb 6, 2024
Closed
@nickmango
Copy link
Collaborator

Resolved @thakurveerendras . Kindly verify

@thakurveerendras
Copy link
Contributor Author

Retested issue on fresh setup & found that it is not reproducible, So making issue status to "Ready for release"
image

@thakurveerendras
Copy link
Contributor Author

Tested issue on prod site & found that it is fixed as expected, So cling to this issue
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mlehotskylf mlehotskylf

@nickmango nickmango

Labels
bug Something isn't working Regression Issue/Bug related to a previously working feature that is now failing
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mlehotskylf @thakurveerendras @nickmango