Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 10 of 4,738 for they (0.25 sec)

  1. common-protos/k8s.io/api/apiserverinternal/v1alpha1/generated.proto

      // API server instances report the version they can decode and the version they
      // encode objects to when persisting objects in the backend.
      optional StorageVersionStatus status = 3;
    }
    
    // Describes the state of the storageVersion at a certain point.
    message StorageVersionCondition {
      // Type of the condition.
      // +required
      optional string type = 1;
    
      // Status of the condition, one of True, False, Unknown.
    Plain Text
    - Registered: Wed May 01 22:53:12 GMT 2024
    - Last Modified: Mon Mar 11 18:43:24 GMT 2024
    - 4.1K bytes
    - Viewed (0)
  2. common/config/.golangci-format.yml

    # WARNING: DO NOT EDIT, THIS FILE IS PROBABLY A COPY
    #
    # The original version of this file is located in the https://github.com/istio/common-files repo.
    # If you're looking at this file in a different repo and want to make a change, please go to the
    # common-files repo, make the change there and check it in. Then come back to this repo and run
    # "make update-common".
    
    run:
      # Timeout for analysis, e.g. 30s, 5m.
      # Default: 1m
      timeout: 20m
      build-tags:
    Others
    - Registered: Wed May 01 22:53:12 GMT 2024
    - Last Modified: Fri Apr 05 03:02:37 GMT 2024
    - 2K bytes
    - Viewed (0)
  3. android/guava/src/com/google/common/eventbus/Dispatcher.java

        // 2. It's possible for subscribers to actually be dispatched to in a different order than they
        //    were added to the queue. It's easily possible for one thread to take the head of the
        //    queue, immediately followed by another thread taking the next element in the queue. That
        //    second thread can then dispatch to the subscriber it took before the first thread does.
        //
    Java
    - Registered: Fri Apr 26 12:43:10 GMT 2024
    - Last Modified: Fri Dec 15 19:31:54 GMT 2023
    - 7.3K bytes
    - Viewed (0)
  4. docs/en/docs/deployment/https.md

    <img src="/img/deployment/https/https01.svg">
    
    ### TLS Handshake Start
    
    The browser would then communicate with that IP address on **port 443** (the HTTPS port).
    
    The first part of the communication is just to establish the connection between the client and the server and to decide the cryptographic keys they will use, etc.
    
    <img src="/img/deployment/https/https02.svg">
    
    Plain Text
    - Registered: Sun Apr 28 07:19:10 GMT 2024
    - Last Modified: Thu Jan 11 16:31:18 GMT 2024
    - 12K bytes
    - Viewed (0)
  5. docs/metrics/prometheus/grafana/README.md

    - Grafana installed as explained [here](https://grafana.com/grafana/download).
    
    ## MinIO Grafana Dashboard
    
    Visualize MinIO metrics with our official Grafana dashboard available on the [Grafana dashboard portal](https://grafana.com/grafana/dashboards/13502).
    
    Refer to the dashboard [json file here](https://raw.githubusercontent.com/minio/minio/master/docs/metrics/prometheus/grafana/minio-dashboard.json).
    
    Plain Text
    - Registered: Sun Apr 28 19:28:10 GMT 2024
    - Last Modified: Thu Mar 28 17:15:39 GMT 2024
    - 2.4K bytes
    - Viewed (0)
  6. docs/en/docs/advanced/generate-clients.md

    You can see those schemas because they were declared with the models in the app.
    
    That information is available in the app's **OpenAPI schema**, and then shown in the API docs (by Swagger UI).
    
    And that same information from the models that is included in OpenAPI is what can be used to **generate the client code**.
    
    ### Generate a TypeScript Client
    
    Now that we have the app with the models, we can generate the client code for the frontend.
    
    Plain Text
    - Registered: Sun Apr 28 07:19:10 GMT 2024
    - Last Modified: Thu Apr 18 19:53:19 GMT 2024
    - 10.5K bytes
    - Viewed (0)
  7. analysis/analysis-api-fir/src/org/jetbrains/kotlin/analysis/api/fir/components/KtFirExpressionInfoProvider.kt

         * climbing up the syntax tree, passing control back and forth between the
         * two.
         *
         * Whether an expression is used is defined by the context in which it
         * appears. E.g. a "statement" in a block is considered used if it is the
         * last expression in that block AND the block itself is used -- a
         * recursive call to `isUsed`, one level higher in the syntax tree.
         *
    Plain Text
    - Registered: Fri Apr 26 08:18:10 GMT 2024
    - Last Modified: Mon Feb 12 20:38:23 GMT 2024
    - 17.6K bytes
    - Viewed (0)
  8. architecture/standards/0001-use-architectural-decision-records.md

    ## Context
    
    In a distributed team with many subteams, the best solution to communicate decisions is to use a format accessible by everyone in charge of development.
    
    We use *Specification* and *Discovery* documents stored in Google Drive, but they present some downsides:
    
    * They are rarely updated after creation and initial review, and then become hard to follow, especially after important decisions are made
    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)
  9. architecture-standards/0001-use-architectural-decision-records.md

    ## Context
    
    In a distributed team with many subteams, the best solution to communicate decisions is to use a format accessible by everyone in charge of development.
    
    We use *Specification* and *Discovery* documents stored in Google Drive, but they present some downsides:
    
    * They are rarely updated after creation and initial review, and then become hard to follow, especially after important decisions are made
    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)
  10. docs/en/docs/deployment/concepts.md

    This Manager Process would probably be the one listening on the **port** in the IP. And it would transmit all the communication to the worker processes.
    
    Those worker processes would be the ones running your application, they would perform the main computations to receive a **request** and return a **response**, and they would load anything you put in variables in RAM.
    
    Plain Text
    - Registered: Sun Apr 28 07:19:10 GMT 2024
    - Last Modified: Thu Apr 18 19:53:19 GMT 2024
    - 18K bytes
    - Viewed (0)
Back to top