Search Options

Results per page
Sort
Preferred Languages
Advance

Results 51 - 60 of 343 for printf (0.15 sec)

  1. SECURITY.md

    in TensorFlow ops can be recognized as security issues only if they are
    reachable and exploitable through production-grade, benign models.
    
    ### Compilation
    
    Compiling models via the recommended entry points described in
    [XLA](https://www.tensorflow.org/xla) and
    [JAX](https://jax.readthedocs.io/en/latest/jax-101/02-jitting.html)
    documentation should be safe, while some of the testing and debugging tools that
    Plain Text
    - Registered: Tue May 07 12:40:20 GMT 2024
    - Last Modified: Sun Oct 01 06:06:35 GMT 2023
    - 9.6K bytes
    - Viewed (0)
  2. licenses/cloud.google.com/go/trace/LICENSE

          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
          file or class name and description of purpose be included on the
          same "printed page" as the copyright notice for easier
          identification within third-party archives.
    
       Copyright [yyyy] [name of copyright owner]
    
       Licensed under the Apache License, Version 2.0 (the "License");
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Tue Nov 01 23:31:22 GMT 2022
    - 11.1K bytes
    - Viewed (0)
  3. licenses/github.com/AdaLogics/go-fuzz-headers/LICENSE

          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
          file or class name and description of purpose be included on the
          same "printed page" as the copyright notice for easier
          identification within third-party archives.
    
       Copyright [yyyy] [name of copyright owner]
    
       Licensed under the Apache License, Version 2.0 (the "License");
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Jun 28 18:00:28 GMT 2021
    - 11.1K bytes
    - Viewed (0)
  4. licenses/cloud.google.com/go/longrunning/LICENSE

          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
          file or class name and description of purpose be included on the
          same "printed page" as the copyright notice for easier
          identification within third-party archives.
    
       Copyright [yyyy] [name of copyright owner]
    
       Licensed under the Apache License, Version 2.0 (the "License");
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Tue Nov 01 23:31:22 GMT 2022
    - 11.1K bytes
    - Viewed (0)
  5. licenses/cloud.google.com/go/auth/LICENSE

          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
          file or class name and description of purpose be included on the
          same "printed page" as the copyright notice for easier
          identification within third-party archives.
    
       Copyright [yyyy] [name of copyright owner]
    
       Licensed under the Apache License, Version 2.0 (the "License");
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Tue Apr 30 13:56:46 GMT 2024
    - 11.1K bytes
    - Viewed (0)
  6. licenses/github.com/google/btree/LICENSE

          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
          file or class name and description of purpose be included on the
          same "printed page" as the copyright notice for easier
          identification within third-party archives.
    
       Copyright [yyyy] [name of copyright owner]
    
       Licensed under the Apache License, Version 2.0 (the "License");
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Sat Oct 26 02:47:39 GMT 2019
    - 11.1K bytes
    - Viewed (0)
  7. licenses/github.com/google/gnostic-models/LICENSE

          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
          file or class name and description of purpose be included on the
          same "printed page" as the copyright notice for easier
          identification within third-party archives.
    
       Copyright [yyyy] [name of copyright owner]
    
       Licensed under the Apache License, Version 2.0 (the "License");
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Mon Jul 24 18:16:35 GMT 2023
    - 11.1K bytes
    - Viewed (0)
  8. licenses/github.com/google/go-containerregistry/LICENSE

          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
          file or class name and description of purpose be included on the
          same "printed page" as the copyright notice for easier
          identification within third-party archives.
    
       Copyright [yyyy] [name of copyright owner]
    
       Licensed under the Apache License, Version 2.0 (the "License");
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Fri Jul 30 04:02:55 GMT 2021
    - 11.1K bytes
    - Viewed (0)
  9. licenses/github.com/containerd/stargz-snapshotter/estargz/LICENSE

          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
          file or class name and description of purpose be included on the
          same "printed page" as the copyright notice for easier
          identification within third-party archives.
    
       Copyright [yyyy] [name of copyright owner]
    
       Licensed under the Apache License, Version 2.0 (the "License");
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Fri Jul 30 04:02:55 GMT 2021
    - 11.1K bytes
    - Viewed (0)
  10. licenses/github.com/docker/distribution/LICENSE

          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
          file or class name and description of purpose be included on the
          same "printed page" as the copyright notice for easier
          identification within third-party archives.
    
       Copyright {yyyy} {name of copyright owner}
    
       Licensed under the Apache License, Version 2.0 (the "License");
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Sat Oct 26 02:47:39 GMT 2019
    - 11.1K bytes
    - Viewed (0)
Back to top