Search Options

Results per page
Sort
Preferred Languages
Advance

Results 221 - 230 of 569 for releases (0.04 sec)

  1. android/guava/src/com/google/common/util/concurrent/AggregateFutureState.java

       * The following fields are package-private, even though we intend never to use them outside this
       * file. For discussion, see AbstractFutureState.
       */
    
      // Lazily initialized the first time we see an exception; not released until all the input futures
      // have completed and we have processed them all.
      volatile @Nullable Set<Throwable> seenExceptionsField = null;
    
      volatile int remainingField;
    
    Registered: Fri Sep 05 12:43:10 UTC 2025
    - Last Modified: Thu Aug 07 16:05:33 UTC 2025
    - 8.5K bytes
    - Viewed (0)
  2. src/test/java/jcifs/smb/NetServerEnumIteratorTest.java

            iterator.close();
            iterator.close(); // Second close should be safe
    
            // Then: Tree handle should be released only once
            verify(treeHandle, times(1)).release();
        }
    
        @Test
        @DisplayName("Iterator should handle filter that rejects all entries")
        void testIterator_FilterRejectsAll() throws Exception {
    Registered: Sun Sep 07 00:10:21 UTC 2025
    - Last Modified: Thu Aug 14 05:31:44 UTC 2025
    - 9.8K bytes
    - Viewed (0)
  3. android/guava-tests/test/com/google/common/util/concurrent/AbstractFutureBenchmarks.java

         * as well as to handle state changes in a thread-safe manner. The current state of the future
         * is held in the Sync state, and the lock is released whenever the state changes to {@link
         * #COMPLETED}, {@link #CANCELLED}, or {@link #INTERRUPTED}
         *
         * <p>To avoid races between threads doing release and acquire, we transition to the final state
         * in two steps. One thread will successfully CAS from RUNNING to COMPLETING, that thread will
    Registered: Fri Sep 05 12:43:10 UTC 2025
    - Last Modified: Thu Jan 30 16:59:10 UTC 2025
    - 13.7K bytes
    - Viewed (0)
  4. helm-releases/minio-1.0.2.tgz

    .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 port forwarding here: http://kubernetes.io/docs/user-guide/kubectl/...
    Registered: Sun Sep 07 19:28:11 UTC 2025
    - Last Modified: Tue Aug 24 18:58:05 UTC 2021
    - 13.6K bytes
    - Viewed (0)
  5. src/main/java/jcifs/internal/smb2/persistent/PersistentHandleManager.java

                    guidToHandle.remove(info.getCreateGuid());
                    removePersistedHandle(info);
                    log.debug("Released handle for: {}", path);
                }
            } finally {
                lock.writeLock().unlock();
            }
        }
    
        /**
         * Get handle information by GUID
         * @param guid the handle GUID
         * @return the handle info or null if not found
         */
    Registered: Sun Sep 07 00:10:21 UTC 2025
    - Last Modified: Sun Aug 24 00:49:49 UTC 2025
    - 13K bytes
    - Viewed (0)
  6. helm-releases/minio-3.1.0.tgz

    .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 port forwarding here: http://kubernetes.io/docs/user-guide/kubectl/...
    Registered: Sun Sep 07 19:28:11 UTC 2025
    - Last Modified: Sun Sep 12 18:19:27 UTC 2021
    - 14.3K bytes
    - Viewed (0)
  7. helm-releases/minio-3.0.1.tgz

    .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 port forwarding here: http://kubernetes.io/docs/user-guide/kubectl/...
    Registered: Sun Sep 07 19:28:11 UTC 2025
    - Last Modified: Thu Sep 02 01:47:43 UTC 2021
    - 13.8K bytes
    - Viewed (0)
  8. helm-releases/minio-3.0.2.tgz

    .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 port forwarding here: http://kubernetes.io/docs/user-guide/kubectl/...
    Registered: Sun Sep 07 19:28:11 UTC 2025
    - Last Modified: Fri Sep 03 08:11:32 UTC 2021
    - 13.8K bytes
    - Viewed (0)
  9. README.md

    - Read the release notes for MinIO *before* performing any upgrade, there is no forced requirement to upgrade to latest release upon every release. Some release may not be relevant to your setup, avoid upgrading production environments unnecessarily.
    Registered: Sun Sep 07 19:28:11 UTC 2025
    - Last Modified: Tue Aug 12 18:20:36 UTC 2025
    - 18.7K bytes
    - Viewed (0)
  10. helm-releases/minio-1.0.0.tgz

    .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 port forwarding here: http://kubernetes.io/docs/user-guide/kubectl/...
    Registered: Sun Sep 07 19:28:11 UTC 2025
    - Last Modified: Fri Aug 20 22:30:54 UTC 2021
    - 13.5K bytes
    - Viewed (0)
Back to top