- Sort Score
- Num 10 results
- Language All
Results 671 - 680 of 1,090 for friends (0.16 seconds)
-
helm-releases/minio-3.1.4.tgz
use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. Configuration ---------- Refer the [Values file](./values.yaml) for all the possible config fields. You can specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, ```bash helm install --name my-release --set persistence.size=1Ti...
Created: Sun Apr 05 19:28:12 GMT 2026 - Last Modified: Mon Sep 20 05:30:22 GMT 2021 - 14.4K bytes - Click Count (0) -
helm-releases/minio-3.1.5.tgz
use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. Configuration ---------- Refer the [Values file](./values.yaml) for all the possible config fields. You can specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, ```bash helm install --name my-release --set persistence.size=1Ti...
Created: Sun Apr 05 19:28:12 GMT 2026 - Last Modified: Wed Sep 22 16:52:01 GMT 2021 - 14.4K bytes - Click Count (0) -
helm-releases/minio-3.6.4.tgz
use. Now update the chart using ```bash helm upgrade -f old_values.yaml my-release minio/minio ``` Default upgrade strategies are specified in the `values.yaml` file. Update these fields if you'd like to use a different strategy. ### Configuration Refer the [Values file](./values.yaml) for all the possible config fields. You can specify each parameter using the `--set key=value[,key=value]` argument to `helm install`. For example, ```bash helm install --name my-release --set persistence.size=1Ti minio/minio...
Created: Sun Apr 05 19:28:12 GMT 2026 - Last Modified: Tue Apr 12 01:30:28 GMT 2022 - 17.9K bytes - Click Count (0) -
cmd/os-instrumented.go
var globalOSMetrics osMetrics func init() { // Inject metrics. ioutilx.OsOpenFile = OpenFile ioutilx.OpenFileDirectIO = OpenFileDirectIO ioutilx.OsOpen = Open } type osMetrics struct { // All fields must be accessed atomically and aligned. operations [osMetricLast]uint64 latency [osMetricLast]lockedLastMinuteLatency } // time an os action. func (o *osMetrics) time(s osMetric) func() {
Created: Sun Apr 05 19:28:12 GMT 2026 - Last Modified: Fri Aug 29 02:39:48 GMT 2025 - 6.2K bytes - Click Count (0) -
src/test/java/org/codelibs/fess/cors/CorsHandlerTest.java
} // Test that constants are protected static final @Test public void test_constantsModifiers() throws Exception { Field[] fields = CorsHandler.class.getDeclaredFields(); for (Field field : fields) { if (field.getName().startsWith("ACCESS_CONTROL_")) { int modifiers = field.getModifiers();Created: Tue Mar 31 13:07:34 GMT 2026 - Last Modified: Sat Mar 21 06:04:58 GMT 2026 - 26.3K bytes - Click Count (0) -
docs/ja/docs/tutorial/body-nested-models.md
**FastAPI** を使用すると、深くネストされた任意のモデルを定義、検証、文書化、使用することができます(Pydanticのおかげです)。 ## リストのフィールド { #list-fields } 属性をサブタイプとして定義することができます。例えば、Pythonの`list`: {* ../../docs_src/body_nested_models/tutorial001_py310.py hl[12] *} これにより、各項目の型は宣言されていませんが、`tags`はリストになります。 ## タイプパラメータを持つリストのフィールド { #list-fields-with-type-parameter } しかし、Pythonには内部の型、または「タイプパラメータ」を使ってリストを宣言するための特定の方法があります:Created: Sun Apr 05 07:19:11 GMT 2026 - Last Modified: Fri Mar 20 14:07:17 GMT 2026 - 8.6K bytes - Click Count (0) -
src/test/java/jcifs/smb1/smb1/SmbTreeTest.java
@Mock private SmbSession session; @Mock private SmbTransport transport; @BeforeEach void setUp() { MockitoAnnotations.openMocks(this); // Setup transport fields that are accessed directly transport.tconHostName = "testHost"; // Setup session.transport field (accessed directly in SmbTree) session.transport = transport;Created: Sun Apr 05 00:10:12 GMT 2026 - Last Modified: Thu Aug 14 07:14:38 GMT 2025 - 10.2K bytes - Click Count (0) -
impl/maven-core/lifecycle-executor.txt
<parameters/> element. From these elements we need to make a component configuration for the MojoExecution. The actual DOM like structure we create is of type PlexusConfiguration and is the type we use with the ComponentConfigurator to initialize fields in a Plexus component. Typically this is done within Plexus with the configuration supplied with component configuration, but in Maven we take configuration values from the POM. So we have to use the ComponentConfigurator outside of Plexus in order...
Created: Sun Apr 05 03:35:12 GMT 2026 - Last Modified: Fri Oct 25 12:31:46 GMT 2024 - 9.7K bytes - Click Count (0) -
docs/en/docs/tutorial/extra-models.md
/// ## Multiple models { #multiple-models } Here's a general idea of how the models could look like with their password fields and the places where they are used: {* ../../docs_src/extra_models/tutorial001_py310.py hl[7,9,14,20,22,27:28,31:33,38:39] *} ### About `**user_in.model_dump()` { #about-user-in-model-dump }Created: Sun Apr 05 07:19:11 GMT 2026 - Last Modified: Thu Mar 05 18:13:19 GMT 2026 - 6.7K bytes - Click Count (0) -
internal/event/target/mqtt.go
RootCAs *x509.CertPool `json:"-"` QueueDir string `json:"queueDir"` QueueLimit uint64 `json:"queueLimit"` } // Validate MQTTArgs fields func (m MQTTArgs) Validate() error { if !m.Enable { return nil } u, err := xnet.ParseURL(m.Broker.String()) if err != nil { return err } switch u.Scheme {
Created: Sun Apr 05 19:28:12 GMT 2026 - Last Modified: Fri Sep 06 23:06:30 GMT 2024 - 8.2K bytes - Click Count (0)