Search Options

Results per page
Sort
Preferred Languages
Advance

Results 81 - 90 of 585 for rounding (0.05 sec)

  1. .github/workflows/arm-cd.yml

          matrix:
            pyver: ['3.9', '3.10', '3.11', '3.12']
        steps:
          - name: Stop old running containers (if any)
            shell: bash
            run: |
              running_containers=$(docker ps -q) && \
              if [[ $running_containers == "" ]]; then
                echo "No running containers";
              else
                echo "Running container(s) found" && \
                docker stop $running_containers;
              fi
    Registered: Tue Sep 09 12:39:10 UTC 2025
    - Last Modified: Mon Sep 01 15:40:11 UTC 2025
    - 3K bytes
    - Viewed (0)
  2. CONTRIBUTING.md

    *   [Google Objective-C Style Guide](https://google.github.io/styleguide/objcguide.html)
    
    #### Running sanity check
    
    If you have Docker installed on your system, you can perform a sanity check on
    your changes by running the command:
    
    ```bash
    tensorflow/tools/ci_build/ci_build.sh CPU tensorflow/tools/ci_build/ci_sanity.sh
    ```
    
    Registered: Tue Sep 09 12:39:10 UTC 2025
    - Last Modified: Sat Jan 11 04:47:59 UTC 2025
    - 15.9K bytes
    - Viewed (0)
  3. docs/en/docs/deployment/server-workers.md

    Let's check back those deployment concepts from before:
    
    * Security - HTTPS
    * Running on startup
    * Restarts
    * **Replication (the number of processes running)**
    * Memory
    * Previous steps before starting
    
    Up to this point, with all the tutorials in the docs, you have probably been running a **server program**, for example, using the `fastapi` command, that runs Uvicorn, running a **single process**.
    
    Registered: Sun Sep 07 07:19:17 UTC 2025
    - Last Modified: Sun Aug 31 09:15:41 UTC 2025
    - 8.3K bytes
    - Viewed (0)
  4. docs/en/docs/advanced/testing-events.md

    {* ../../docs_src/app_testing/tutorial004.py hl[9:15,18,27:28,30:32,41:43] *}
    
    
    You can read more details about the ["Running lifespan in tests in the official Starlette documentation site."](https://www.starlette.io/lifespan/#running-lifespan-in-tests)
    
    For the deprecated `startup` and `shutdown` events, you can use the `TestClient` as follows:
    
    Registered: Sun Sep 07 07:19:17 UTC 2025
    - Last Modified: Sun Aug 31 10:29:21 UTC 2025
    - 615 bytes
    - Viewed (0)
  5. api/maven-api-core/src/main/java/org/apache/maven/api/VersionRange.java

         */
        @Nonnull
        @Override
        String toString();
    
        /**
         * Represents range boundary.
         */
        interface Boundary {
            /**
             * The bounding version.
             */
            Version getVersion();
    
            /**
             * Returns {@code true} if version is included of the range.
             */
            boolean isInclusive();
        }
    Registered: Sun Sep 07 03:35:12 UTC 2025
    - Last Modified: Fri Jun 06 14:28:57 UTC 2025
    - 2.4K bytes
    - Viewed (0)
  6. android-test/src/test/kotlin/okhttp/android/test/NonRobolectricOkHttpClientTest.kt

    import assertk.assertions.hasMessage
    import assertk.assertions.isNotNull
    import java.io.IOException
    import org.junit.Test
    import org.junit.runner.RunWith
    import org.junit.runners.JUnit4
    
    /**
     * Android test running with only stubs.
     */
    @RunWith(JUnit4::class)
    class NonRobolectricOkHttpClientTest : BaseOkHttpClientUnitTest() {
      @Test
      override fun testPublicSuffixDb() {
        assertFailure { super.testPublicSuffixDb() }.all {
    Registered: Fri Sep 05 11:42:10 UTC 2025
    - Last Modified: Mon Jul 28 07:33:49 UTC 2025
    - 1.6K bytes
    - Viewed (0)
  7. cmd/callhome.go

    		for {
    			if !globalCallhomeConfig.Enabled() {
    				return
    			}
    
    			if !runCallhome(ctx, objAPI) {
    				// callhome was disabled or context was canceled
    				return
    			}
    
    			// callhome running on a different node.
    			// sleep for some time and try again.
    			duration := max(time.Duration(r.Float64()*float64(globalCallhomeConfig.FrequencyDur())),
    				// Make sure to sleep at least a second to avoid high CPU ticks.
    Registered: Sun Sep 07 19:28:11 UTC 2025
    - Last Modified: Fri Aug 29 02:39:48 UTC 2025
    - 5.3K bytes
    - Viewed (0)
  8. src/test/java/org/codelibs/fess/helper/IntervalControlHelperTest.java

            helper.setCrawlerWaitMillis(50);
    
            // Test when crawler is running
            assertTrue(helper.isCrawlerRunning());
            long start = System.currentTimeMillis();
            helper.checkCrawlerStatus();
            long end = System.currentTimeMillis();
            assertTrue(end - start < 100); // Should return quickly
    
            // Test when crawler is not running
            helper.setCrawlerRunning(false);
    Registered: Thu Sep 04 12:52:25 UTC 2025
    - Last Modified: Thu Jul 10 13:41:04 UTC 2025
    - 13.1K bytes
    - Viewed (0)
  9. .github/workflows/arm-ci.yml

        strategy:
          matrix:
            pyver: ['3.10']
        steps:
          - name: Stop old running containers (if any)
            shell: bash
            run: |
              running_containers=$(docker ps -q) && \
              if [[ $running_containers == "" ]]; then
                echo "No running containers";
              else
                echo "Running container(s) found" && \
                docker stop $running_containers;
              fi
    Registered: Tue Sep 09 12:39:10 UTC 2025
    - Last Modified: Mon Sep 01 15:40:11 UTC 2025
    - 2.2K bytes
    - Viewed (0)
  10. docs/resiliency/resiliency-tests.sh

    		echo -e "${RED}${1} Failed${NC}"
    		TESTS_RUN_STATUS=$((TESTS_RUN_STATUS & 0))
    	else
    		echo -e "${GREEN}${1} Passed${NC}"
    	fi
    }
    
    function test_resiliency_success_with_server_down() {
    	echo
    	echo -e "${GREEN}Running test_resiliency_success_with_server_down ...${NC}"
    	# Stop one node
    	docker stop resiliency-minio1-1
    	sleep 10
    
    	verify_resiliency "${FUNCNAME[0]}"
    
    	# Finally restart the node
    	docker start resiliency-minio1-1
    Registered: Sun Sep 07 19:28:11 UTC 2025
    - Last Modified: Sat Dec 21 04:24:45 UTC 2024
    - 20.5K bytes
    - Viewed (0)
Back to top