Search Options

Results per page
Sort
Preferred Languages
Advance

Results 411 - 420 of 576 for reflow (3.86 sec)

  1. internal/grid/muxclient.go

    	defer func() {
    		m.parent.deleteMux(false, m.MuxID)
    		// addErrorNonBlockingClose will close the response channel.
    		xioutil.SafeClose(responseCh)
    	}()
    
    	// Cancelation and errors are handled by handleTwowayRequests below.
    	for resp := range internalResp {
    		m.send(message{Op: OpUnblockSrvMux, MuxID: m.MuxID})
    		responseCh <- resp
    	}
    }
    
    func (m *muxClient) handleTwowayRequests(errResp chan<- Response, requests <-chan []byte) {
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Sun Sep 28 20:59:21 UTC 2025
    - 15.9K bytes
    - Viewed (0)
  2. compat/maven-artifact/src/test/java/org/apache/maven/artifact/versioning/VersionRangeTest.java

            assertNull(restriction.getUpperBound(), CHECK_UPPER_BOUND);
            assertFalse(restriction.isUpperBoundInclusive(), CHECK_UPPER_BOUND_INCLUSIVE);
    
            // TODO test reversed restrictions on all below
            range1 = VersionRange.createFromVersionSpec("[1.0,)");
            range2 = VersionRange.createFromVersionSpec("1.1");
            mergedRange = range1.restrict(range2);
    Registered: Sun Dec 28 03:35:09 UTC 2025
    - Last Modified: Sun Mar 30 23:08:36 UTC 2025
    - 44.1K bytes
    - Viewed (0)
  3. CONTRIBUTING.md

    ### Copyright and License
    
    When updating/modifying a file, please do not make changes to the copyright header.
    
    When creating a new file, please make sure to add a header as defined below.
    
    #### Required Files for Copyright Headers:
    
    - Source code files (e.g., `.java`, `.kt`, `.groovy`).
    - Documentation files, where applicable (e.g., `.adoc`, `.md`).
    
    #### Exempt Files for Copyright Headers:
    Registered: Wed Dec 31 11:36:14 UTC 2025
    - Last Modified: Tue Nov 25 06:57:22 UTC 2025
    - 19K bytes
    - Viewed (0)
  4. helm-releases/minio-3.3.2.tgz

    "ClusterIP" "NodePort" }} MinIO can be accessed via port {{ .Values.service.port }} on the following DNS name from within your cluster: {{ template "minio.fullname" . }}.{{ .Release.Namespace }}.svc.cluster.local To access MinIO from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "release={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace {{ .Release.Namespace }} Read more about...
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Sat Dec 11 17:26:01 UTC 2021
    - 14.6K bytes
    - Viewed (0)
  5. helm-releases/minio-3.3.4.tgz

    "ClusterIP" "NodePort" }} MinIO can be accessed via port {{ .Values.service.port }} on the following DNS name from within your cluster: {{ template "minio.fullname" . }}.{{ .Release.Namespace }}.svc.cluster.local To access MinIO from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "release={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace {{ .Release.Namespace }} Read more about...
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Sat Dec 11 17:59:34 UTC 2021
    - 14.6K bytes
    - Viewed (0)
  6. helm-releases/minio-3.4.2.tgz

    "ClusterIP" "NodePort" }} MinIO can be accessed via port {{ .Values.service.port }} on the following DNS name from within your cluster: {{ template "minio.fullname" . }}.{{ .Release.Namespace }}.svc.cluster.local To access MinIO from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "release={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace {{ .Release.Namespace }} Read more about...
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Tue Dec 21 02:58:25 UTC 2021
    - 15.2K bytes
    - Viewed (0)
  7. helm-releases/minio-3.4.4.tgz

    "ClusterIP" "NodePort" }} MinIO can be accessed via port {{ .Values.service.port }} on the following DNS name from within your cluster: {{ template "minio.fullname" . }}.{{ .Release.Namespace }}.svc.cluster.local To access MinIO from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "release={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace {{ .Release.Namespace }} Read more about...
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Fri Dec 31 04:21:24 UTC 2021
    - 15.2K bytes
    - Viewed (0)
  8. helm-releases/minio-3.4.5.tgz

    "ClusterIP" "NodePort" }} MinIO can be accessed via port {{ .Values.service.port }} on the following DNS name from within your cluster: {{ template "minio.fullname" . }}.{{ .Release.Namespace }}.svc.cluster.local To access MinIO from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "release={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace {{ .Release.Namespace }} Read more about...
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Wed Jan 05 19:32:55 UTC 2022
    - 15.2K bytes
    - Viewed (0)
  9. helm-releases/minio-3.5.3.tgz

    "ClusterIP" "NodePort" }} MinIO can be accessed via port {{ .Values.service.port }} on the following DNS name from within your cluster: {{ template "minio.fullname" . }}.{{ .Release.Namespace }}.svc.cluster.local To access MinIO from localhost, run the below commands: 1. export POD_NAME=$(kubectl get pods --namespace {{ .Release.Namespace }} -l "release={{ .Release.Name }}" -o jsonpath="{.items[0].metadata.name}") 2. kubectl port-forward $POD_NAME 9000 --namespace {{ .Release.Namespace }} Read more about...
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Sun Feb 13 23:43:44 UTC 2022
    - 15.4K bytes
    - Viewed (0)
  10. docs/pt/docs/tutorial/security/simple-oauth2.md

    ## Obtenha o `username` e a `password` { #get-the-username-and-password }
    
    É utilizado o utils de segurança da **FastAPI** para obter o `username` e a `password`.
    
    OAuth2 especifica que ao usar o "password flow" (fluxo de senha), que estamos usando, o cliente/usuário deve enviar os campos `username` e `password` como dados do formulário.
    
    Registered: Sun Dec 28 07:19:09 UTC 2025
    - Last Modified: Wed Nov 12 16:23:57 UTC 2025
    - 10.3K bytes
    - Viewed (0)
Back to top