Search Options

Results per page
Sort
Preferred Languages
Advance

Results 381 - 390 of 413 for Unit (0.04 sec)

  1. src/cmd/asm/internal/asm/testdata/s390x.s

    	VSTRCZBS V18, V20, V22, V24	// e78240306f8a
    	VSTRCZHS V18, V20, V22, V24	// e78241306f8a
    	VSTRCZFS V18, V20, V22, V24	// e78242306f8a
    
    	RET
    	RET	foo(SB)
    
    TEXT main·init(SB),DUPOK|NOSPLIT,$0 // TEXT main.init(SB), DUPOK|NOSPLIT, $0
    	RET
    
    TEXT main·main(SB),DUPOK|NOSPLIT,$0 // TEXT main.main(SB), DUPOK|NOSPLIT, $0
    	BL      main·foo(SB)    // CALL main.foo(SB)
    Registered: Tue Oct 29 11:13:09 UTC 2024
    - Last Modified: Wed Sep 18 15:49:24 UTC 2024
    - 22.1K bytes
    - Viewed (0)
  2. src/main/java/org/codelibs/fess/crawler/transformer/FessXpathTransformer.java

        protected Map<String, Boolean> fieldPrunedRuleMap = new HashMap<>();
    
        protected Map<String, PrunedTag[]> prunedTagsCache = new HashMap<>();
    
        @PostConstruct
        public void init() {
            if (logger.isDebugEnabled()) {
                logger.debug("Initialize {}", this.getClass().getSimpleName());
            }
            fessConfig = ComponentUtil.getFessConfig();
        }
    
        @Override
    Registered: Mon Oct 28 08:04:08 UTC 2024
    - Last Modified: Thu Oct 24 13:01:38 UTC 2024
    - 42.9K bytes
    - Viewed (0)
  3. docs/zh/docs/deployment/concepts.md

    /// tip
    
    另外,请记住,根据您的设置,在某些情况下,您在开始应用程序之前**可能甚至不需要任何先前的步骤**。
    
     在这种情况下,您就不必担心这些。 🤷
    
    ///
    
    ### 前面步骤策略的示例
    
    这将在**很大程度上取决于您部署系统的方式**,并且可能与您启动程序、处理重启等的方式有关。
    
    以下是一些可能的想法:
    
    * Kubernetes 中的“Init Container”在应用程序容器之前运行
    * 一个 bash 脚本,运行前面的步骤,然后启动您的应用程序
         * 您仍然需要一种方法来启动/重新启动 bash 脚本、检测错误等。
    
    /// tip
    
    我将在以后的章节中为您提供使用容器执行此操作的更具体示例:[容器中的 FastAPI - Docker](docker.md){.internal-link target=_blank}。
    
    ///
    Registered: Sun Oct 27 07:19:11 UTC 2024
    - Last Modified: Tue Aug 06 04:48:30 UTC 2024
    - 16.2K bytes
    - Viewed (0)
  4. cmd/sts-handlers_test.go

    	baseTestCases := []TestSuiteCommon{
    		// Init and run test on ErasureSD backend with signature v4.
    		{serverType: "ErasureSD", signer: signerV4},
    		// Init and run test on ErasureSD backend, with tls enabled.
    		{serverType: "ErasureSD", signer: signerV4, secure: true},
    		// Init and run test on Erasure backend.
    		{serverType: "Erasure", signer: signerV4},
    		// Init and run test on ErasureSet backend.
    Registered: Sun Oct 27 19:28:09 UTC 2024
    - Last Modified: Thu Oct 10 23:40:37 UTC 2024
    - 97.1K bytes
    - Viewed (0)
  5. docs/em/docs/deployment/docker.md

    /// info
    
    🚥 👆 ⚙️ Kubernetes, 👉 🔜 🎲 <a href="https://kubernetes.io/docs/concepts/workloads/pods/init-containers/" class="external-link" target="_blank">🕑 📦</a>.
    
    ///
    
    🚥 👆 ⚙️ 💼 📤 🙅‍♂ ⚠ 🏃‍♂ 👈 ⏮️ 📶 **💗 🕰 🔗** (🖼 🚥 👆 🚫 🏃 💽 🛠️, ✋️ ✅ 🚥 💽 🔜), ⤴️ 👆 💪 🚮 👫 🔠 📦 ▶️️ ⏭ ▶️ 👑 🛠️.
    
    ### 👁 📦
    
    Registered: Sun Oct 27 07:19:11 UTC 2024
    - Last Modified: Mon Aug 12 21:47:53 UTC 2024
    - 27.9K bytes
    - Viewed (0)
  6. docs/de/docs/deployment/concepts.md

    Es hängt **stark** davon ab, wie Sie **Ihr System bereitstellen**, und hängt wahrscheinlich mit der Art und Weise zusammen, wie Sie Programme starten, Neustarts durchführen, usw.
    
    Hier sind einige mögliche Ideen:
    
    * Ein „Init-Container“ in Kubernetes, der vor Ihrem Anwendungs-Container ausgeführt wird
    * Ein Bash-Skript, das die Vorab-Schritte ausführt und dann Ihre Anwendung startet
    Registered: Sun Oct 27 07:19:11 UTC 2024
    - Last Modified: Tue Aug 06 04:48:30 UTC 2024
    - 20.6K bytes
    - Viewed (0)
  7. docs/pt/docs/deployment/concepts.md

    Isso **dependerá muito** da maneira como você **implanta seu sistema** e provavelmente estará conectado à maneira como você inicia programas, lida com reinicializações, etc.
    
    Aqui estão algumas ideias possíveis:
    
    * Um "Init Container" no Kubernetes que roda antes do seu app container
    * Um script bash que roda os passos anteriores e então inicia seu aplicativo
    Registered: Sun Oct 27 07:19:11 UTC 2024
    - Last Modified: Fri Oct 04 11:04:50 UTC 2024
    - 19.7K bytes
    - Viewed (0)
  8. src/bytes/buffer_test.go

    var testBytes []byte  // test data; same as testString but as a slice.
    
    type negativeReader struct{}
    
    func (r *negativeReader) Read([]byte) (int, error) { return -1, nil }
    
    func init() {
    	testBytes = make([]byte, N)
    	for i := 0; i < N; i++ {
    		testBytes[i] = 'a' + byte(i%26)
    	}
    	testString = string(testBytes)
    }
    
    // Verify that contents of buf match the string s.
    Registered: Tue Oct 29 11:13:09 UTC 2024
    - Last Modified: Tue Sep 03 20:55:15 UTC 2024
    - 18.6K bytes
    - Viewed (0)
  9. docs/ko/docs/deployment/docker.md

    /// info | "정보"
    
    만약 여러분이 쿠버네티스를 사용하고 있다면, 아마도 이는 <a href="https://kubernetes.io/docs/concepts/workloads/pods/init-containers/" class="external-link" target="_blank">Init Container</a>일 것입니다.
    
    ///
    
    만약 여러분의 이용 사례에서 이전 단계들을 **병렬적으로 여러번** 수행하는데에 문제가 없다면 (예를 들어 데이터베이스 이전을 실행하지 않고 데이터베이스가 준비되었는지 확인만 하는 경우), 메인 프로세스를 시작하기 전에 이 단계들을 각 컨테이너에 넣을 수 있습니다.
    
    ### 단일 컨테이너
    Registered: Sun Oct 27 07:19:11 UTC 2024
    - Last Modified: Mon Aug 12 21:47:53 UTC 2024
    - 42.7K bytes
    - Viewed (0)
  10. docs/en/docs/deployment/concepts.md

    This will **depend heavily** on the way you **deploy your system**, and it would probably be connected to the way you start programs, handling restarts, etc.
    
    Here are some possible ideas:
    
    * An "Init Container" in Kubernetes that runs before your app container
    * A bash script that runs the previous steps and then starts your application
        * You would still need a way to start/restart *that* bash script, detect errors, etc.
    
    Registered: Sun Oct 27 07:19:11 UTC 2024
    - Last Modified: Wed Sep 18 16:09:57 UTC 2024
    - 17.8K bytes
    - Viewed (0)
Back to top