On the home page for OPA https://www.openpolicyagent.org/ we have:

Which is somewhat confusing as it looks like one big button but each of the text items is a separate link. We should split them up into separate buttons or something more distinctive.

Issue type

• Defect - Unexpected behaviour (obvious or verified by project member).

Defect

How to reproduce the issue

When querying a non-cached group membership by name, debug output states that the object the user is a member of was the parent of the group object.

if (&LDAP-Group == 'my-group') {
   # success
}

Will emit a debug message similar to `ou=groups,dc=e

I've seen unexplained warnings in my logs:

int_dataplane.go 354: Failed to query VXLAN device error=Link not found

Expected Behavior

When not using VXLAN, no VXLAN related warning should appear in the logs.

Current Behavior

The above log warning is printed on every pod startup.

Possible Solution

Change the logic around https://github.com/projectcalico/felix/blob/00c71c865d9

1. What's the name of the policy?

https://github.com/github/site-policy/blob/master/Policies/github-terms-of-service.md

2. Is this issue related to a specific section within one of our policies (e.g. the Terms of Service)? If so, please include a link to the section or subsection.

https://github.com/github/site-policy/blob/master/Policies/github-terms-of-service.md#3-github-may-

Currently it just ignores invalid handles, unless all of them are invalid, in which case it does return an error.

See https://github.com/project-oak/oak/blob/c2b2ff4b666de2a4f5fe7ff7cbfadbfc00af69f2/docs/abi.md#wait_on_channels

This should also allow to simplify some of the Runtime logic dealing with optional handles for this ABI call:

https://github.com/project-oak/oak/blob/c2b2ff4b666de

dbsalt was a compile-time option for 4.1.x and before - it is not something that can be changed after upgrade.

document this behavior and reasoning in the upgrade section of the docs.

Organisations usually come up with some best practices for monitoring and managing pods. A new policy could enforce a configurable list of labels to be mandatory to run a pod in the environment.
For example all pods should have an app label.

The policies.Config would need to be extended with a new field.

type Config struct {
...
PolicyMandatoryPodLabels  []string
}

🤔 Exte

What happened

A common workflow:

1. I make a PR, all the CI goes green, but the overall light is still stuck at yellow
2. I click through to the policy bot UI to see what I need to do to get my thing merged
   
   Unfortun

Suggestion : dans https://github.com/DISIC/politique-de-contribution-open-source/blob/master/pratique.md mettre d’abord les éléments obligatoires, puis les éléments recommandés, puis les suggestions, et possiblement le mettre en avant dans les titres des chapitres

The implementation is generic so any set should work, however, the format is somewhat finicky (e.g., v1/services, NOT v1/Service or v1/service, etc.)

URL / Link to page

https://digital.gov/resources/required-web-content-and-links/

Tell us how we can make this page better

Under headings like: About Page, the bulleted information is not capped. Later down the page, Headings like: "Budget and Performance Reports" and "Privacy Policy" the bulleted information is title Capped.