- Sort Score
- Result 10 results
- Languages All
Results 11 - 20 of 267 for describe (0.25 sec)
-
architecture-standards/0002-avoid-using-java-serialization.md
## Decision We do not use Java serialization. Instead, we use custom serialization where we explicitly describe how data objects should be serialized and deserialized. For internal purposes, we use binary formats for their brevity. We use the `Serializer` abstraction to separate the actual implementation of serialization from its uses.
Plain Text - Registered: Wed Feb 14 11:36:15 GMT 2024 - Last Modified: Thu Feb 08 21:48:27 GMT 2024 - 1.9K bytes - Viewed (0) -
.github/ISSUE_TEMPLATE/40_contributor_documentation.yml
- Typo (please open a PR instead) validations: required: true - type: textarea id: description attributes: label: Problem description description: | Please describe the problem as concisely as possible. validations: required: true - type: textarea id: context attributes: label: Context (optional) description: |
Others - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Mon Jan 15 10:01:01 GMT 2024 - 1.6K bytes - Viewed (0) -
architecture/standards/0002-avoid-using-java-serialization.md
Java serialization does not enforce type safety as strictly as some alternatives, potentially leading to runtime errors. ## Decision We do not use Java serialization. Instead, we use custom serialization where we explicitly describe how data objects should be serialized and deserialized. For internal purposes, we use binary formats for their brevity. We use the `Serializer` abstraction to separate the actual implementation of serialization from its uses.
Plain Text - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Thu Feb 29 22:32:18 GMT 2024 - 2.3K bytes - Viewed (0) -
build-logic/binary-compatibility/src/main/groovy/gradlebuild/binarycompatibility/rules/AbstractGradleViolationRule.groovy
return repository.isOverride(method) } Violation acceptOrReject(JApiCompatibility member, Violation rejection) { List<String> changes = member.compatibilityChanges.collect { Violation.describe(it) } return acceptOrReject(member, changes, rejection) } Violation acceptOrReject(JApiCompatibility member, List<String> changes, Violation rejection) {
Groovy - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Tue Apr 23 08:40:36 GMT 2024 - 10.4K bytes - Viewed (0) -
.github/ISSUE_TEMPLATE/bug_report.yaml
Thank you for filing a bug report. Please help us identify and resolve the bug by filling out the following fields. - type: textarea attributes: label: Description description: Please describe the issue you encountered. validations: required: true - type: textarea attributes: label: Example description: >
Others - Registered: Fri Apr 26 12:43:10 GMT 2024 - Last Modified: Fri Oct 27 19:53:41 GMT 2023 - 2.2K bytes - Viewed (0) -
common-protos/k8s.io/api/networking/v1alpha1/generated.proto
repeated IPAddress items = 2; } // IPAddressSpec describe the attributes in an IP Address. message IPAddressSpec { // ParentRef references the resource that an IPAddress is attached to. // An IPAddress must reference a parent object. // +required optional ParentReference parentRef = 1; } // ParentReference describes a reference to a parent object. message ParentReference {
Plain Text - Registered: Wed May 01 22:53:12 GMT 2024 - Last Modified: Mon Mar 11 18:43:24 GMT 2024 - 6K bytes - Viewed (0) -
Makefile
sed 's#RELEASE\.\([0-9]\+\)-\([0-9]\+\)-\([0-9]\+\)T\([0-9]\+\)-\([0-9]\+\)-\([0-9]\+\)Z#\1-\2-\3T\4:\5:\6Z#'))) $(eval VERSION := $(shell git describe --tags --abbrev=0).hotfix.$(shell git rev-parse --short HEAD)) hotfix: hotfix-vars clean install ## builds minio binary with hotfix tags
Plain Text - Registered: Sun Apr 28 19:28:10 GMT 2024 - Last Modified: Thu Apr 25 21:55:41 GMT 2024 - 10.3K bytes - Viewed (1) -
architecture-standards/0001-use-architectural-decision-records.md
## Decision The *Build Tool Team* has decided to use Architectural Decision Records (aka ADR) to track decisions we want to follow. The main logic with ADRs is to describe (architectural) decisions made: * To provide best practices and solutions we (as *build tool* team) want to promote. * To avoid asking the same thing multiple times during code review.
Plain Text - Registered: Wed Feb 14 11:36:15 GMT 2024 - Last Modified: Wed Feb 07 00:43:19 GMT 2024 - 2.8K bytes - Viewed (0) -
architecture/standards/0001-use-architectural-decision-records.md
## Decision The *Build Tool Team* has decided to use Architectural Decision Records (aka ADR) to track decisions we want to follow. The main logic with ADRs is to describe (architectural) decisions made: * To provide best practices and solutions we (as the *build tool* team) want to promote. * To avoid asking the same thing multiple times during code review.
Plain Text - Registered: Wed May 01 11:36:15 GMT 2024 - Last Modified: Sat Mar 02 21:54:40 GMT 2024 - 2.8K bytes - Viewed (0) -
istioctl/cmd/root.go
"istio.io/istio/istioctl/pkg/cli" "istio.io/istio/istioctl/pkg/completion" "istio.io/istio/istioctl/pkg/config" "istio.io/istio/istioctl/pkg/dashboard" "istio.io/istio/istioctl/pkg/describe" "istio.io/istio/istioctl/pkg/injector" "istio.io/istio/istioctl/pkg/internaldebug" "istio.io/istio/istioctl/pkg/kubeinject" "istio.io/istio/istioctl/pkg/metrics" "istio.io/istio/istioctl/pkg/multicluster"
Go - Registered: Wed May 01 22:53:12 GMT 2024 - Last Modified: Thu Apr 11 20:51:30 GMT 2024 - 10K bytes - Viewed (0)