Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 7 of 7 for further (0.16 sec)

  1. .github/workflows/stale-issues.yml

                This issue is stale because it has been open for 7 days with no activity.
                It will be closed if no further activity occurs. Thank you.
              close-issue-message: >
                This issue was closed because it has been inactive for 7 days since being marked as stale.
                Please reopen if you'd like to work on this further.
              days-before-pr-stale: 14
              days-before-pr-close: 14
    Others
    - Registered: Tue May 07 12:40:20 GMT 2024
    - Last Modified: Thu Nov 23 20:04:38 GMT 2023
    - 4.1K bytes
    - Viewed (0)
  2. CODE_OF_CONDUCT.md

    However, for the vast majority of issues, we aim to empower individuals to first resolve conflicts themselves, asking for help when needed, and only after that fails to escalate further. This approach gives people more control over the outcome of their dispute. 
    
    If you are experiencing or witnessing conflict, we ask you to use the following escalation strategy to address the conflict:
    
    Plain Text
    - Registered: Tue May 07 12:40:20 GMT 2024
    - Last Modified: Fri Feb 05 18:43:16 GMT 2021
    - 5.2K bytes
    - Viewed (0)
  3. tensorflow/c/eager/dlpack.h

    namespace tensorflow {
    
    // PyCapsule name for DLPack Tensor
    const char* const kDlTensorCapsuleName = "dltensor";
    
    // Converts eager tensor handle to DLPack (DLManagedTensor*), and return the
    // void* for further PyCapsule construction.
    TF_CAPI_EXPORT extern void* TFE_HandleToDLPack(TFE_TensorHandle* h,
                                                   TF_Status* status);
    
    // Converts DLPack (DLManagedTensor*) to eager tensor handle.
    C
    - Registered: Tue Apr 30 12:39:09 GMT 2024
    - Last Modified: Sat Mar 28 08:41:24 GMT 2020
    - 1.6K bytes
    - Viewed (0)
  4. ci/official/containers/linux_arm64/devel.usertools/wheel_verification.bats

        echo "# Size of $TF_WHEEL is $WHEEL_MEGABYTES / $LARGEST_OK_SIZE megabytes." >&3
        test "$WHEEL_MEGABYTES" -le "$LARGEST_OK_SIZE"
    }
    
    # Note: this runs before the tests further down the file, so TF is installed in
    # the venv and the venv is active when those tests run. The venv gets cleaned
    # up in teardown_file() above.
    @test "Wheel is installable" {
        python3 -m venv /tf/venv
    Plain Text
    - Registered: Tue May 07 12:40:20 GMT 2024
    - Last Modified: Tue Jan 23 02:14:00 GMT 2024
    - 2.7K bytes
    - Viewed (0)
  5. ci/official/README.md

    #   Non-Googlers should replace "nightly_upload" or "rbe" with
    #   "public_cache,disk_cache".
    #   Googlers should replace "nightly_upload" with "public_cache,disk_cache" or
    #   "rbe", if you have set up your system to use RBE (see further below).
    #
    # Here is how to choose your TFCI value:
    # 1. A Python version must come first, because other scripts reference it.
    #      Ex. py39  -- Python 3.9
    #      Ex. py310 -- Python 3.10
    #      Ex. py311 -- Python 3.11
    Plain Text
    - Registered: Tue May 07 12:40:20 GMT 2024
    - Last Modified: Thu Feb 01 03:21:19 GMT 2024
    - 8K bytes
    - Viewed (0)
  6. LICENSE

    All rights reserved.
    
    Caffe uses a shared copyright model: each contributor holds copyright over
    their contributions to Caffe. The project versioning records all such
    contribution and copyright details. If a contributor wants to further mark
    their specific copyright on a particular contribution, they should indicate
    their copyright solely in the commit message of the change when it is
    committed.
    
    LICENSE
    
    Plain Text
    - Registered: Tue May 07 12:40:20 GMT 2024
    - Last Modified: Mon Nov 29 17:31:56 GMT 2021
    - 13.3K bytes
    - Viewed (0)
  7. CONTRIBUTING.md

    **4. Approved**
    
    -   Once the PR is approved, it gets `kokoro:force-run` label applied and it
        initiates CI/CD tests.
    -   We can't move forward if these tests fail.
    -   In such situations, we may request you to make further changes to your PR
        for the tests to pass.
    -   Once the tests pass, we now bring all the code into the internal code base,
        using a job called "copybara".
    
    **5. Copy to Google Internal codebase and run internal CI**
    Plain Text
    - Registered: Tue May 07 12:40:20 GMT 2024
    - Last Modified: Thu Mar 21 11:45:51 GMT 2024
    - 15.6K bytes
    - Viewed (0)
Back to top