- Sort Score
- Result 10 results
- Languages All
Results 21 - 30 of 190 for Every (0.21 sec)
-
.github/workflows/feedback.yml
name: Feedback on: schedule: - cron: '0 * * * *' # every hour workflow_dispatch: permissions: {} jobs: feedback: permissions: issues: write pull-requests: write runs-on: ubuntu-latest steps: # Feedback loop: ask for something on PR/Issue and close if not provided or return to the queue on update. # https://github.com/gradle/issue-management-action/blob/main/src/feedback.ts
Others - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Thu May 02 09:13:16 GMT 2024 - 516 bytes - Viewed (0) -
analysis/analysis-api-fe10/src/org/jetbrains/kotlin/analysis/api/descriptors/utils/ValidityAwareCachedValue.kt
import org.jetbrains.kotlin.analysis.api.lifetime.assertIsValidAndAccessible import kotlin.properties.ReadOnlyProperty import kotlin.reflect.KProperty /** * Lazy value that guaranties safe publication and checks validity on every access */ internal class ValidityAwareCachedValue<T>( private val token: KtLifetimeToken, init: () -> T ) : ReadOnlyProperty<Any, T> { private val lazyValue = lazy(LazyThreadSafetyMode.PUBLICATION, init)
Plain Text - Registered: Fri Apr 26 08:18:10 GMT 2024 - Last Modified: Mon Aug 15 09:04:58 GMT 2022 - 1.1K bytes - Viewed (0) -
common-protos/k8s.io/api/node/v1/generated.proto
// implementation will use to handle pods of this class. The possible values // are specific to the node & CRI configuration. It is assumed that all // handlers are available on every node, and handlers of the same name are // equivalent on every node. // For example, a handler called "runc" might specify that the runc OCI // runtime (using native Linux containers) will be used to run the containers // in a pod.
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Mar 11 18:43:24 GMT 2024 - 4.4K bytes - Viewed (0) -
.cm/summary_table.cm
# Each automation is independent of the others. Every time one of the `on` conditions match for # this PR, this automations will have its `if` checked to run. In a way, the `on` conditions # function as an implicit first `if` for every automation in the file. # You can define multiple automations in a .cm file, but each automation name should be unique # within the file. We keep each automation (or very closely related group of automations) in
Plain Text - Registered: Wed Apr 17 11:36:08 GMT 2024 - Last Modified: Thu Feb 08 15:20:44 GMT 2024 - 6.5K bytes - Viewed (0) -
docs/iam/access-management-plugin.md
When configured, MinIO sends request and credential details for every API call to an external HTTP(S) endpoint and expects an allow/deny response. MinIO is thus able to delegate access management to an external system, and users are able to use a custom solution instead of S3 standard IAM policies.
Plain Text - Registered: Sun May 05 19:28:20 GMT 2024 - Last Modified: Tue Dec 13 22:28:48 GMT 2022 - 4.4K bytes - Viewed (0) -
common-protos/k8s.io/api/node/v1beta1/generated.proto
// implementation will use to handle pods of this class. The possible values // are specific to the node & CRI configuration. It is assumed that all // handlers are available on every node, and handlers of the same name are // equivalent on every node. // For example, a handler called "runc" might specify that the runc OCI // runtime (using native Linux containers) will be used to run the containers // in a pod.
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Mar 11 18:43:24 GMT 2024 - 4.4K bytes - Viewed (0) -
common-protos/k8s.io/api/node/v1alpha1/generated.proto
// CRI implementation will use to handle pods of this class. The possible // values are specific to the node & CRI configuration. It is assumed that // all handlers are available on every node, and handlers of the same name are // equivalent on every node. // For example, a handler called "runc" might specify that the runc OCI // runtime (using native Linux containers) will be used to run the containers // in a pod.
Plain Text - Registered: Wed May 08 22:53:08 GMT 2024 - Last Modified: Mon Mar 11 18:43:24 GMT 2024 - 5K bytes - Viewed (0) -
.github/workflows/team-triage-stale.yml
name: 'Requeue stale team-triage items' on: schedule: # Execute every day at 00:05 to avoid conflicts with other workflows - cron: '5 0 * * *' permissions: {} jobs: requeue: permissions: issues: write pull-requests: write runs-on: ubuntu-latest steps: - uses: actions/stale@v9 with: operations-per-run: 50 remove-stale-when-updated: false
Others - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Thu May 02 09:13:16 GMT 2024 - 835 bytes - Viewed (0) -
ci/official/utilities/setup.sh
# variables in it, OR may be left empty if the user has already exported the # relevant variables in their environment. Because of 'set -o allexport' above # (which is equivalent to "set -a"), every variable in the file is exported # for other files to use. # # Separately, if TFCI is set *and* there are also additional TFCI_ variables # set in the shell environment, those variables will be restored after the
Shell Script - Registered: Tue Apr 30 12:39:09 GMT 2024 - Last Modified: Fri Jan 26 00:33:34 GMT 2024 - 5.2K bytes - Viewed (1) -
.github/ISSUE_TEMPLATE/20_contributor_feature_request.yml
labels: [ "a:feature", "to-triage" ] assignees: [ ] body: - type: markdown attributes: value: | Please follow the instructions below. We receive dozens of issues every week, so to stay productive, we will close issues that don't provide enough information. Please open Android-related issues on [the Android Issue Tracker](https://source.android.com/source/report-bugs)
Others - Registered: Wed May 08 11:36:15 GMT 2024 - Last Modified: Thu Apr 06 11:10:39 GMT 2023 - 1.5K bytes - Viewed (0)