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.

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

EasyCLA not trigger after add PR on GitHub #4071

Closed
thakurveerendras opened this issue Jul 31, 2023 · 4 comments
Closed

EasyCLA not trigger after add PR on GitHub #4071

thakurveerendras opened this issue Jul 31, 2023 · 4 comments
Assignees
Labels
bug Something isn't working

Comments

@thakurveerendras
Copy link
Contributor

Summary

EasyCLA not trigger after add PR

Background

  1. Go to cla enforced GitHub repo
  2. Add commit
  3. Add PR

Actual behavior

EasyCLA Expected — Waiting for status to be reported remain in PR

Expected behavior

PR should be gated

PR: SunEarthChildOrg/devRepo01#14

Screenshots

image

@thakurveerendras thakurveerendras added the bug Something isn't working label Jul 31, 2023
@thakurveerendras
Copy link
Contributor Author

Prod PR: CLATestOrg/VulDetect1#47

@WillsonHG
Copy link
Member

A fix is being deployed for this, we are currently testing and validating.

@WillsonHG
Copy link
Member

We have reverted the changes which caused this issue, so it is now resolved in production. If you have an easycla status of 'expected' please comment /easycla in your PR to get the latest status.

We will continue to test the bug that caused the issue in dev.

@WillsonHG
Copy link
Member

Postmortem:
Recently, we encountered a challenge related to a significant number of commits (approximately 500) from one of our clients. Our primary objective in addressing this issue was to enhance the efficiency of processing a Pull Request with a high volume of commits, prompting us to initiate a hotfix.
This hotfix incorporated the use of a Python package, 'multiprocessor'. Regrettably, this package presented unexpected compatibility issues with our AWS Lambdas. Consequently, the deployment of the hotfix in our production environment disrupted the EasyCLA service.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants