Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 10 of 53 for Chad (0.18 sec)

  1. src/main/webapp/js/admin/plugins/form-validator/location.js

    bonaire","bosnia and herzegovina","botswana","bouvet island","brazil","british indian ocean territory","brunei darussalam","bulgaria","burkina faso","burundi","cabo verde","cambodia","cameroon","canada","cayman islands","central african republic","chad","chile","china","christmas island","cocos islands","colombia","comoros","democratic republic of the congo","congo","cook islands","costa rica","côte d'ivoire","croatia","cuba","curaçao","cyprus","czechia","denmark","djibouti","dominica","dominican...
    JavaScript
    - Registered: Mon Apr 29 08:04:11 GMT 2024
    - Last Modified: Mon Jan 01 05:12:47 GMT 2018
    - 5.2K bytes
    - Viewed (0)
  2. .github/stale.yml

    exemptAssignees: false
    
    # Label to use when marking as stale
    staleLabel: stale
    
    # Comment to post when marking as stale. Set to `false` to disable
    markComment: >-
      This issue has been automatically marked as stale because it has not had
      recent activity. It will be closed after 15 days if no further activity
      occurs. Thank you for your contributions.
    # Comment to post when removing the stale label.
    # unmarkComment: >
    #   Your comment here.
    
    Others
    - Registered: Sun Apr 28 19:28:10 GMT 2024
    - Last Modified: Mon Jan 24 04:36:59 GMT 2022
    - 2K bytes
    - Viewed (0)
  3. docs/kms/IAM.md

       change the cluster root credentials since they were used to en/decrypt the IAM data.
       So, both - the old and new credentials - had to be present at the same time during a rotation
       and the old credentials had to be removed once the rotation completed. This process is now gone.
       The root credentials can now be changed easily.
    
    > Does this mean I need an enterprise KMS setup to run MinIO (securely)?
    Plain Text
    - Registered: Sun Apr 28 19:28:10 GMT 2024
    - Last Modified: Thu Jan 18 07:03:17 GMT 2024
    - 5.3K bytes
    - Viewed (0)
  4. guava-testlib/src/com/google/common/collect/testing/testers/AbstractSetTester.java

    @GwtCompatible
    @Ignore // Affects only Android test runner, which respects JUnit 4 annotations on JUnit 3 tests.
    public class AbstractSetTester<E> extends AbstractCollectionTester<E> {
      /*
       * Previously we had a field named set that was initialized to the value of
       * collection in setUp(), but that caused problems when a tester changed the
       * value of set or collection but not both.
       */
      protected final Set<E> getSet() {
    Java
    - Registered: Fri Apr 26 12:43:10 GMT 2024
    - Last Modified: Tue Jan 09 20:10:38 GMT 2018
    - 1.3K bytes
    - Viewed (0)
  5. .github/workflows/issue-manager.yml

                  },
                  "changes-requested": {
                    "delay": 2628000,
                    "message": "As this PR had requested changes to be applied but has been inactive for a while, it's now going to be closed. But if there's anyone interested, feel free to create a new PR."
                  }
    Others
    - Registered: Sun Apr 28 07:19:10 GMT 2024
    - Last Modified: Tue Jan 30 18:46:56 GMT 2024
    - 1.1K bytes
    - Viewed (0)
  6. guava-gwt/src/com/google/thirdparty/publicsuffix/PublicSuffixType.gwt.xml

    <module>
    <source path="">
      <!-- Hack to keep collect from hiding collect.testing supersource: -->
      <exclude name="**/testing/**"/>
    </source>
    
    <!--
        We used to set this only for packages that had manual supersource. That
        worked everywhere that I know of except for one place: when running the GWT
        util.concurrent tests under Guava.
    
        The problem is that GWT responds poorly to two .gwt.xml files in the same
    XML
    - Registered: Fri Apr 26 12:43:10 GMT 2024
    - Last Modified: Thu Jan 06 15:30:58 GMT 2022
    - 1.4K bytes
    - Viewed (0)
  7. guava-gwt/src/com/google/common/base/Base.gwt.xml

    <module>
    <source path="">
      <!-- Hack to keep collect from hiding collect.testing supersource: -->
      <exclude name="**/testing/**"/>
    </source>
    
    <!--
        We used to set this only for packages that had manual supersource. That
        worked everywhere that I know of except for one place: when running the GWT
        util.concurrent tests under Guava.
    
        The problem is that GWT responds poorly to two .gwt.xml files in the same
    XML
    - Registered: Fri Apr 26 12:43:10 GMT 2024
    - Last Modified: Thu Jan 06 15:30:58 GMT 2022
    - 1.4K bytes
    - Viewed (0)
  8. guava-gwt/src/com/google/common/html/Html.gwt.xml

    <module>
    <source path="">
      <!-- Hack to keep collect from hiding collect.testing supersource: -->
      <exclude name="**/testing/**"/>
    </source>
    
    <!--
        We used to set this only for packages that had manual supersource. That
        worked everywhere that I know of except for one place: when running the GWT
        util.concurrent tests under Guava.
    
        The problem is that GWT responds poorly to two .gwt.xml files in the same
    XML
    - Registered: Fri Apr 26 12:43:10 GMT 2024
    - Last Modified: Thu Jan 06 15:30:58 GMT 2022
    - 1.4K bytes
    - Viewed (0)
  9. guava-gwt/test/com/google/common/escape/testing/Testing.gwt.xml

    <module>
    <source path="">
      <!-- Hack to keep collect from hiding collect.testing supersource: -->
      <exclude name="**/testing/**"/>
    </source>
    
    <!--
        We used to set this only for packages that had manual supersource. That
        worked everywhere that I know of except for one place: when running the GWT
        util.concurrent tests under Guava.
    
        The problem is that GWT responds poorly to two .gwt.xml files in the same
    XML
    - Registered: Fri Apr 26 12:43:10 GMT 2024
    - Last Modified: Thu Jan 06 15:30:58 GMT 2022
    - 1.5K bytes
    - Viewed (0)
  10. maven-compat/src/main/java/org/apache/maven/artifact/resolver/ResolutionListenerForDepMgmt.java

     * Should only be implemented by DebugResolutionListener.  Remove this
     * when the ResolutionListener interface deprecation of the manageArtifact
     * method (and the [yet to be done] addition of these methods to that
     * interface) has had a chance to propagate to all interested plugins.
     */
    @Deprecated
    public interface ResolutionListenerForDepMgmt {
        void manageArtifactVersion(Artifact artifact, Artifact replacement);
    
    Java
    - Registered: Sun Apr 28 03:35:10 GMT 2024
    - Last Modified: Tue Nov 22 13:26:01 GMT 2022
    - 1.5K bytes
    - Viewed (0)
Back to top