Search Options

Results per page
Sort
Preferred Languages
Advance

Results 51 - 60 of 218 for costly (0.18 sec)

  1. .cm/code_experts.cm

    # function as an implicit first `if` for every automation in the file.
    
    # You can define multiple automations in a .cm file, but each automation name should be unique
    # within the file.  We keep each automation (or very closely related group of automations) in
    # its own file.
    
    on:
      - pr_created
      - commit
      - comment_added
    
    automations:
    
      # Also post a comment that lists the best experts for the files that were modified.
    Plain Text
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Fri Apr 12 13:42:16 GMT 2024
    - 1.3K bytes
    - Viewed (0)
  2. android/guava-tests/test/com/google/common/io/FilesCreateTempDirTest.java

         * filesystem) does our prod code look up the username. Thus, this test doesn't necessarily test
         * anything interesting under most environments. Still, we can run it (except for Android, at
         * least old versions), so we mostly do. This is useful because we don't actually run our CI on
         * Windows under Java 8, at least as of this writing.
         *
         * Under Windows in particular, we want to test that:
         *
    Java
    - Registered: Fri May 03 12:43:13 GMT 2024
    - Last Modified: Fri Oct 06 17:11:11 GMT 2023
    - 4.3K bytes
    - Viewed (0)
  3. internal/disk/stat_linux.go

    					devName = dstat.DeviceName
    					break
    				}
    			}
    			if devName != "" {
    				info.Name = devName
    				qst, err := bfs.SysBlockDeviceQueueStats(devName)
    				if err != nil { // Mostly not found error
    					// Check if there is a parent device:
    					//   e.g. if the mount is based on /dev/nvme0n1p1, let's calculate the
    					//        real device name (nvme0n1) to get its sysfs information
    Go
    - Registered: Sun May 05 19:28:20 GMT 2024
    - Last Modified: Mon Feb 26 19:34:50 GMT 2024
    - 4.8K bytes
    - Viewed (0)
  4. android/guava/src/com/google/common/reflect/AbstractInvocationHandler.java

        return super.toString();
      }
    
      private static boolean isProxyOfSameInterfaces(Object arg, Class<?> proxyClass) {
        return proxyClass.isInstance(arg)
            // Equal proxy instances should mostly be instance of proxyClass
            // Under some edge cases (such as the proxy of JDK types serialized and then deserialized)
            // the proxy type may not be the same.
    Java
    - Registered: Fri Apr 26 12:43:10 GMT 2024
    - Last Modified: Wed Jan 05 17:43:40 GMT 2022
    - 5.2K bytes
    - Viewed (0)
  5. .cm/add_usual_expert.cm

    # function as an implicit first `if` for every automation in the file.
    
    # You can define multiple automations in a .cm file, but each automation name should be unique
    # within the file.  We keep each automation (or very closely related group of automations) in
    # its own file.
    
    on:
      - pr_created
      - commit
      - comment_added
    
    automations:
    
    Plain Text
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Fri Apr 12 13:42:16 GMT 2024
    - 1.4K bytes
    - Viewed (0)
  6. guava/src/com/google/common/base/FinalizableSoftReference.java

    @ElementTypesAreNonnullByDefault
    public abstract class FinalizableSoftReference<T> extends SoftReference<T>
        implements FinalizableReference {
      /**
       * Constructs a new finalizable soft reference.
       *
       * @param referent to softly reference
       * @param queue that should finalize the referent
       */
      protected FinalizableSoftReference(@CheckForNull T referent, FinalizableReferenceQueue queue) {
        super(referent, queue.queue);
        queue.cleanUp();
    Java
    - Registered: Fri Apr 05 12:43:09 GMT 2024
    - Last Modified: Thu Feb 23 15:09:35 GMT 2023
    - 1.6K bytes
    - Viewed (0)
  7. .cm/javadoc_on_new_files.cm

    # function as an implicit first `if` for every automation in the file.
    
    # You can define multiple automations in a .cm file, but each automation name should be unique
    # within the file.  We keep each automation (or very closely related group of automations) in
    # its own file.
    
    on:
      - pr_created
      - commit
      - comment_added
    
    automations:
    
      javadoc_on_new_files:
        # Triggered for new Java files that lack Javadoc content.
    Plain Text
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Fri Apr 12 13:42:16 GMT 2024
    - 1.8K bytes
    - Viewed (0)
  8. .cm/complex_changes.cm

    # function as an implicit first `if` for every automation in the file.
    
    # You can define multiple automations in a .cm file, but each automation name should be unique
    # within the file.  We keep each automation (or very closely related group of automations) in
    # its own file.
    
    on:
      - pr_created
      - commit
      - comment_added
    
    automations:
    
      # If a PR is very complex, require 2 approvals
      complex_changes:
        if:
    Plain Text
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Fri Apr 12 13:42:16 GMT 2024
    - 1.7K bytes
    - Viewed (0)
  9. .teamcity/README.md

    # CI Pipeline Configuration
    
    ## Open & import the project
    
    In your IDEA, `File` - `Open`, select `.teamcity/pom.xml`, `import as project`, and you'll have a Maven project.
    
    ## Project structure
    
    Mostly a standard Maven project structure. The entry point `settings.kts` defines the TeamCity project.
    
    There are 3 subprojects in the TeamCity project hierarchy: `Check` for Gradle builds, `Promotion` for releasing Gradle versions, `Util` for miscellaneous utilities.
    Plain Text
    - Registered: Wed May 08 11:36:15 GMT 2024
    - Last Modified: Wed Mar 06 23:02:25 GMT 2024
    - 4K bytes
    - Viewed (0)
  10. architecture/networking/pilot.md

    Various components described in Config Ingestion can trigger a Config Update. These are batched up ("debounced"), to avoid excessive activity when many changes happen in succession, and eventually enqueued in the Push Queue.
    
    The Push Queue is mostly a normal queue, but it has some special logic to merge push requests for each given proxy. This results in each proxy having 0 or 1 outstanding push requests; if additional updates come in the existing push request is just expanded.
    
    Plain Text
    - Registered: Wed May 08 22:53:08 GMT 2024
    - Last Modified: Wed Feb 07 17:53:24 GMT 2024
    - 19.1K bytes
    - Viewed (0)
Back to top