Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 10 of 10 for Borins (0.31 sec)

  1. manifests/charts/istio-control/istio-discovery/values.yaml

        # assigned.
        #
        # Within a multicluster mesh, each cluster must be (manually or auto)
        # configured to have the same Mesh ID value. If an existing cluster 'joins' a
        # multicluster mesh, it will need to be migrated to the new mesh ID. Details
        # of migration TBD, and it may be a disruptive operation to change the Mesh
        # ID post-install.
        #
    Others
    - Registered: Wed Mar 20 22:53:08 GMT 2024
    - Last Modified: Mon Mar 11 16:58:23 GMT 2024
    - 19.6K bytes
    - Viewed (0)
  2. .github/workflows/sigbuild-docker.yml

              username: _json_key
              password: ${{ secrets.GCP_CREDS }}
          -
            name: Grab the upcoming TF version to tag this container
            run: |
              # [[:digit:]] searches for numbers and \+ joins them together
              major_version=$(grep "^#define TF_MAJOR_VERSION" ./tensorflow/core/public/version.h | grep -o "[[:digit:]]\+")
    Others
    - Registered: Tue Apr 30 12:39:09 GMT 2024
    - Last Modified: Mon Oct 23 18:43:43 GMT 2023
    - 3.8K bytes
    - Viewed (0)
  3. manifests/charts/istiod-remote/values.yaml

        # assigned.
        #
        # Within a multicluster mesh, each cluster must be (manually or auto)
        # configured to have the same Mesh ID value. If an existing cluster 'joins' a
        # multicluster mesh, it will need to be migrated to the new mesh ID. Details
        # of migration TBD, and it may be a disruptive operation to change the Mesh
        # ID post-install.
        #
    Others
    - Registered: Wed Mar 20 22:53:08 GMT 2024
    - Last Modified: Mon Mar 11 16:58:23 GMT 2024
    - 19.6K bytes
    - Viewed (0)
  4. ci/official/containers/linux_arm64/builder.devtoolset/stringop_trunc.patch

    -#define	UT_NAMESIZE	8
    -#define	UT_LINESIZE	8
    -#define	UT_HOSTSIZE	16
    +#define UT_LINESIZE	32
    +#define UT_NAMESIZE	32
    +#define UT_HOSTSIZE	256
     
     
    +/* The structure describing an entry in the database of
    +   previous logins.  */
     struct lastlog
       {
         time_t ll_time;
    @@ -36,12 +38,16 @@ struct lastlog
         char ll_host[UT_HOSTSIZE];
       };
     
    +/* The structure describing an entry in the user accounting database.  */
     struct utmp
    Others
    - Registered: Tue Apr 30 12:39:09 GMT 2024
    - Last Modified: Mon Sep 18 14:52:45 GMT 2023
    - 42.9K bytes
    - Viewed (1)
  5. operator/cmd/mesh/testdata/manifest-generate/data-snapshot.tar.gz

    conditions may become true in # the future, they should ensure their meshes have different Mesh IDs # assigned. # # Within a multicluster mesh, each cluster must be (manually or auto) # configured to have the same Mesh ID value. If an existing cluster 'joins' a # multicluster mesh, it will need to be migrated to the new mesh ID. Details # of migration TBD, and it may be a disruptive operation to change the Mesh # ID post-install. # # If the mesh admin does not specify a value, Istio will use the value...
    Others
    - Registered: Wed Mar 20 22:53:08 GMT 2024
    - Last Modified: Wed Jan 10 05:10:03 GMT 2024
    - 198.1K bytes
    - Viewed (1)
  6. src/cmd/asm/internal/asm/testdata/ppc64.s

    	XOR $-32768, R6                 // 3be080007fe63278
    	XOR $-32768, R6, R7             // 3be080007fe73278
    	XOR $1234567, R5                // 6ca5001268a5d687
    	XOR $1234567, R5, R3            // 6ca300126863d687
    	XORIS $15, R3, R4               // 6c64000f
    	XOR   $983040, R3, R4           // 6c64000f
    
    	// TODO: the order of CR operands don't match
    	CMP R3, R4                      // 7c232000
    	CMPU R3, R4                     // 7c232040
    Others
    - Registered: Tue Apr 30 11:13:12 GMT 2024
    - Last Modified: Wed Apr 24 15:53:25 GMT 2024
    - 49K bytes
    - Viewed (0)
  7. okhttp/src/main/resources/okhttp3/internal/publicsuffix/PublicSuffixDatabase.gz

    tomobe.ibaraki.jp tonaki.okinawa.jp tonami.toyama.jp tondabayashi.osaka.jp tone.ibaraki.jp tonkotsu.jp tono.iwate.jp tonosho.kagawa.jp tonsberg.no toolforge.org tools toon.ehime.jp top topology.museum torahime.shiga.jp toray toride.ibaraki.jp torino.it torino.museum torproject.net torsken.no tos.it tosa.kochi.jp tosashimizu.kochi.jp toscana.it toshiba toshima.tokyo.jp tosu.saga.jp total tottori.jp tottori.tottori.jp touch.museum tourism.bj tourism.pl tourism.tn tours towada.aomori.jp town town.museum...
    Others
    - Registered: Fri Apr 26 11:42:10 GMT 2024
    - Last Modified: Wed Dec 20 23:27:07 GMT 2023
    - 40.4K bytes
    - Viewed (0)
  8. docs/en/data/sponsors_badge.yml

    logins:
      - jina-ai
      - deta
      - investsuite
      - mikeckennedy
      - deepset-ai
      - cryptapi
      - xoflare
      - DropbaseHQ
      - VincentParedes
      - BLUE-DEVIL1134
      - ObliviousAI
      - Doist
      - nihpo
      - armand-sauzay
      - databento-bot
      - databento
      - nanram22
      - Flint-company
      - porter-dev
      - fern-api
      - ndimares
      - svixhq
      - Alek99
      - codacy
      - zanfaruqui
      - scalar
      - bump-sh
    Others
    - Registered: Sun Apr 28 07:19:10 GMT 2024
    - Last Modified: Wed Jan 31 22:13:52 GMT 2024
    - 415 bytes
    - Viewed (0)
  9. manifests/charts/gateways/istio-egress/values.yaml

        # assigned.
        #
        # Within a multicluster mesh, each cluster must be (manually or auto)
        # configured to have the same Mesh ID value. If an existing cluster 'joins' a
        # multicluster mesh, it will need to be migrated to the new mesh ID. Details
        # of migration TBD, and it may be a disruptive operation to change the Mesh
        # ID post-install.
        #
    Others
    - Registered: Wed Apr 24 22:53:08 GMT 2024
    - Last Modified: Tue Feb 27 16:55:16 GMT 2024
    - 12.4K bytes
    - Viewed (0)
  10. manifests/charts/gateways/istio-ingress/values.yaml

        # assigned.
        #
        # Within a multicluster mesh, each cluster must be (manually or auto)
        # configured to have the same Mesh ID value. If an existing cluster 'joins' a
        # multicluster mesh, it will need to be migrated to the new mesh ID. Details
        # of migration TBD, and it may be a disruptive operation to change the Mesh
        # ID post-install.
        #
    Others
    - Registered: Wed Apr 24 22:53:08 GMT 2024
    - Last Modified: Tue Feb 27 16:55:16 GMT 2024
    - 13K bytes
    - Viewed (0)
Back to top