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

DCO check stays as expected #211

Closed
frouioui opened this issue Jun 3, 2024 · 13 comments · Fixed by opensearch-project/OpenSearch#13970
Closed

DCO check stays as expected #211

frouioui opened this issue Jun 3, 2024 · 13 comments · Fixed by opensearch-project/OpenSearch#13970
Assignees

Comments

@frouioui
Copy link

frouioui commented Jun 3, 2024

Although the DCO app is installed in the org/user and on the repository, the check is no longer running for Pull Requests, the check stays as expected. This worked fine about an hour ago, and suddenly stopped working.

Is anyone experiencing this too?

EDIT: for those blocked by this issue @wagoodman proposed a nice solution (anchore/syft#2926)

@zkoppert
Copy link

zkoppert commented Jun 3, 2024

Yes, others experiencing this as well. It is a hosting side issue and I'm looking at it now.

Update: This may not be resolved this week due to folks being out of office. I'll post updates here as I've got them.

@frouioui
Copy link
Author

frouioui commented Jun 3, 2024

Thanks for the update @zkoppert.

@JeyJeyGao
Copy link

JeyJeyGao commented Jun 4, 2024

We are also afacted: notaryproject/notation#952.
Our release process is blocked.

yurishkuro added a commit to jaegertracing/jaeger that referenced this issue Jun 4, 2024
## Which problem is this PR solving?
- Several PRs are stuck with DCO check pending. Apparently there's an
ongoing issue with the DCO app: dcoapp/app#211

## Description of the changes
- Add an alternative DCO check into the lint workflow using
https://github.com/christophebedard/dco-check

## How was this change tested?
Ran the script manually:
```shell
$ python3 scripts/dco_check.py -b main
Detected: git (default)

Checking commits: 5863430..7a5e58b

All good!
```

With an unsigned commit:
```shell
$ gca -m bad
[manual-dco-check 7da95684] bad
 1 file changed, 1 insertion(+)

$ python3 scripts/dco_check.py -b main
Detected: git (default)

Checking commits: 5863430..7da95684408ebd3f32692e9444940bdf0e04348d

Missing sign-off(s):

	7da95684408ebd3f32692e9444940bdf0e04348d
		no sign-off found
```

---------

Signed-off-by: Yuri Shkuro <github@ysh.us>
@mihaimaruseac
Copy link

Thank you @zkoppert for looking at this.

I tried the close/open suggestion in sigstore/model-transparency#195 but it doesn't seem to work. Will try pushing a new commit to see if that changes things.

@zkoppert
Copy link

zkoppert commented Jun 5, 2024

Thank you for mentioning that. The above were my best guesses. :)

mihaimaruseac added a commit to mihaimaruseac/model-transparency that referenced this issue Jun 5, 2024
See dcoapp/app#211 (comment)

Signed-off-by: Mihai Maruseac <mihaimaruseac@google.com>
@mihaimaruseac
Copy link

Pushing an empty commit on sigstore/model-transparency#190 has worked.

Thank you.

mihaimaruseac added a commit to sigstore/model-transparency that referenced this issue Jun 5, 2024
)

* Migrate `serialize_v0` to new API.

This is the middle layer of the API design work (#172). We add a manifest abstract class to represent various manifests (#111 #112) and also ways to serialize a model directory into manifests and ways to verify the manifests.

For now, this only does what was formerly known as `serialize_v0`. The v1 and the manifest versions will come soon.

Note: This has a lot of inspiration from #112, but makes the API work with all the usecases we need to consider right now.

Signed-off-by: Mihai Maruseac <mihaimaruseac@google.com>

* Clarify some comments

Signed-off-by: Mihai Maruseac <mihaimaruseac@google.com>

* Encode name with base64

Signed-off-by: Mihai Maruseac <mihaimaruseac@google.com>

* Add another test case

Signed-off-by: Mihai Maruseac <mihaimaruseac@google.com>

* Empty commit to retrigger DCO check.

See dcoapp/app#211 (comment)

Signed-off-by: Mihai Maruseac <mihaimaruseac@google.com>

---------

Signed-off-by: Mihai Maruseac <mihaimaruseac@google.com>
@rbarkerSL
Copy link

I've been able to progress PRs waiting on DCO again in the last 30 minutes or so. 👍

@mynameistechno
Copy link

Thanks @zkoppert !

DEiselt added a commit to SovereignCloudStack/cluster-stacks that referenced this issue Jun 6, 2024
See dcoapp/app#211 (comment)

Signed-off-by: Danny Eiselt <eiselt@b1-systems.de>
DEiselt added a commit to SovereignCloudStack/cluster-stacks that referenced this issue Jun 6, 2024
see dcoapp/app#211 (comment)

Signed-off-by: Danny Eiselt <eiselt@b1-systems.de>
DEiselt added a commit to SovereignCloudStack/cluster-stacks that referenced this issue Jun 6, 2024
* changed: v1alpha7 to v1beta1

Signed-off-by: Danny Eiselt <eiselt@b1-systems.de>

* added: oidc to new version + v1beta1

Signed-off-by: Danny Eiselt <eiselt@b1-systems.de>

* chore(node-images): update to 1.27.14

Signed-off-by: Jan Schoone <6106846+jschoone@users.noreply.github.com>

* chore(node-images): update to 1.27.14

Signed-off-by: Jan Schoone <6106846+jschoone@users.noreply.github.com>

* fix: change cluster stack name

Signed-off-by: Jan Schoone <6106846+jschoone@users.noreply.github.com>

* Dummy commit to trigger DCO

See dcoapp/app#211 (comment)

Signed-off-by: Danny Eiselt <eiselt@b1-systems.de>

* Dummy commit to retrigger DCO

see dcoapp/app#211 (comment)

Signed-off-by: Danny Eiselt <eiselt@b1-systems.de>

---------

Signed-off-by: Danny Eiselt <eiselt@b1-systems.de>
Signed-off-by: Jan Schoone <6106846+jschoone@users.noreply.github.com>
Co-authored-by: Jan Schoone <6106846+jschoone@users.noreply.github.com>
Co-authored-by: Malte Münch <muench@b1-systems.de>
@frouioui
Copy link
Author

Thanks a lot 🙇🏻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants