- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 279 for We (0.14 sec)
-
architecture/standards/0003-avoid-introducing-Groovy-types-to-public-api.md
- **Reduce the size of the Gradle distribution** - We no longer need to carry multiple standard libraries for different languages. ## Decision We do not introduce new public API methods that include Groovy types in their signatures. Existing Groovy methods will not be removed immediately. ## Status ACCEPTED ## Consequences
Plain Text - Registered: Wed Mar 27 11:36:08 GMT 2024 - Last Modified: Sun Mar 10 20:38:06 GMT 2024 - 1.8K bytes - Viewed (0) -
docs/en/docs/tutorial/sql-databases.md
Each instance of the `SessionLocal` class will be a database session. The class itself is not a database session yet. But once we create an instance of the `SessionLocal` class, this instance will be the actual database session. We name it `SessionLocal` to distinguish it from the `Session` we are importing from SQLAlchemy. We will use `Session` (the one imported from SQLAlchemy) later.
Plain Text - Registered: Sun Mar 24 07:19:08 GMT 2024 - Last Modified: Fri Mar 22 01:42:11 GMT 2024 - 29.6K bytes - Viewed (0) -
architecture/standards/0001-use-architectural-decision-records.md
## Consequences * X * Y * Z ``` ## Status ACCEPTED ## Consequences * We start to use Architectural Decision Records * We use the proposed template from this ADR * We locate `.md` files in the folder `/architecture-standards` * We highly encourage usage of ADR to communicate decisions
Plain Text - Registered: Wed Mar 27 11:36:08 GMT 2024 - Last Modified: Sat Mar 02 21:54:40 GMT 2024 - 2.8K bytes - Viewed (0) -
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. When sharing data with external tools, we use JSON. ## Status ACCEPTED
Plain Text - Registered: Wed Mar 27 11:36:08 GMT 2024 - Last Modified: Thu Feb 29 22:32:18 GMT 2024 - 2.3K bytes - Viewed (0) -
cmd/metacache-set.go
if askDisks == -1 { newDisks := getQuorumDisks(disks, infos, (len(disks)+1)/2) if newDisks != nil { // If we found disks signature in quorum, we proceed to list // from a single drive, shuffling of the drives is subsequently. disks = newDisks askDisks = 1 } else { // If we did not find suitable disks, perform strict quorum listing // as no disk agrees on quorum anymore.
Go - Registered: Sun Mar 24 19:28:08 GMT 2024 - Last Modified: Tue Mar 19 20:23:12 GMT 2024 - 30.4K bytes - Viewed (0) -
cmd/metacache-server-pool.go
if !HasPrefix(o.Marker, o.Prefix) { return entries, io.EOF } } // With max keys of zero we have reached eof, return right here. if o.Limit == 0 { return entries, io.EOF } // For delimiter and prefix as '/' we do not list anything at all // along // with the prefix. On a flat namespace with 'prefix' // as '/' we don't have any entries, since all the keys are // of form 'keyName/...'
Go - Registered: Sun Mar 24 19:28:08 GMT 2024 - Last Modified: Tue Mar 19 20:23:12 GMT 2024 - 12.9K bytes - Viewed (0) -
cni/pkg/iptables/iptables.go
cfg: cfg, } // By detecting iptables versions *here* once-for-all we are // committing to using the same binary/variant (legacy or nft) // within all pods as we do on the host. // // This should be fine, as the host binaries are all we have to work with here anyway, // as we are running within a privileged container - and we don't want to take the time to // redetect for each pod anyway. // // Extreme corner case:
Go - Registered: Wed Mar 27 22:53:09 GMT 2024 - Last Modified: Mon Mar 11 17:46:23 GMT 2024 - 19.1K bytes - Viewed (0) -
analysis/analysis-api-fir/src/org/jetbrains/kotlin/analysis/api/fir/references/FirReferenceResolveHelper.kt
// If we are at a super-type constructor call, adjust the resolution expression so that we // get the constructor instead of the class. // // For the example: // // class A { // constructor() // } // class B: <caret>A() //
Plain Text - Registered: Fri Mar 22 08:18:09 GMT 2024 - Last Modified: Thu Mar 21 15:21:57 GMT 2024 - 37.3K bytes - Viewed (0) -
maven-core/src/site/apt/configuration-management.apt
that currently we have information about a project scattered across the project.xml and the various properties files. What needs to be done is to encapsulate all of this in the POM. Typically users parameterize the use of plugins, or have custom values like ${user.name} for use in elements like the <developerConnection/>. It would be idea if we
Plain Text - Registered: Sun Mar 24 03:35:10 GMT 2024 - Last Modified: Mon Mar 18 00:24:53 GMT 2024 - 5.8K bytes - Viewed (0) -
android/pom.xml
If we're building with JDK8, then clearly we're sticking to JDK8 APIs. However, I assume (but did not confirm) that we'd have the same issue with our -android builds, which need animal-sniffer so that they can check that we're sticking to JDK6-like APIs. So instead, we use javac9, which doesn't lead to this error.
XML - Registered: Fri Mar 22 12:43:11 GMT 2024 - Last Modified: Tue Mar 12 20:26:18 GMT 2024 - 19.4K bytes - Viewed (0)