Search Options

Results per page
Sort
Preferred Languages
Advance

Results 871 - 880 of 2,088 for dpath (0.02 sec)

  1. compat/maven-model-builder/src/test/resources/poms/inheritance/flat-urls-parent.xml

      <description>Flat directory structure case: module = ../child-artifact-id + child directory path == child-artifact-id</description>
    
      <modules>
        <module>../inheritance</module>
      </modules>
    
      <!-- 5 urls in the pom will be inherited with path added -->
      <url>http://www.apache.org/path/to/parent/</url>
      <scm>
        <connection>scm:my-scm:http://domain.org/base</connection>
    Registered: Sun Dec 28 03:35:09 UTC 2025
    - Last Modified: Fri Oct 25 12:31:46 UTC 2024
    - 1.8K bytes
    - Viewed (0)
  2. okhttp-idna-mapping-table/src/main/kotlin/okhttp3/internal/idn/GenerateIdnaMappingTableCode.kt

    import okio.FileSystem
    import okio.Path.Companion.toPath
    
    fun main(vararg args: String) {
      val data = loadIdnaMappingTableData()
      val file = generateMappingTableFile(data)
      file.writeTo(File(args[0]))
    }
    
    fun loadIdnaMappingTableData(): IdnaMappingTableData {
      val path = "/okhttp3/internal/idna/IdnaMappingTable.txt".toPath()
      val table =
        FileSystem.RESOURCES.read(path) {
          readPlainTextIdnaMappingTable()
        }
    Registered: Fri Dec 26 11:42:13 UTC 2025
    - Last Modified: Wed Mar 19 19:25:20 UTC 2025
    - 2.8K bytes
    - Viewed (1)
  3. apache-maven/src/assembly/maven/conf/settings.xml

              xsi:schemaLocation="http://maven.apache.org/SETTINGS/2.0.0 https://maven.apache.org/xsd/settings-2.0.0.xsd">
      <!-- localRepository
       | The path to the local repository maven will use to store artifacts.
       |
       | Default: ${user.home}/.m2/repository
      <localRepository>/path/to/local/repo</localRepository>
      -->
    
      <!-- interactiveMode
       | This will determine whether maven prompts you when it needs input. If set to false,
    Registered: Sun Dec 28 03:35:09 UTC 2025
    - Last Modified: Wed Jan 22 07:44:50 UTC 2025
    - 11.1K bytes
    - Viewed (0)
  4. cmd/batch-replicate_gen.go

    			}
    		case "Endpoint":
    			z.Endpoint, err = dc.ReadString()
    			if err != nil {
    				err = msgp.WrapError(err, "Endpoint")
    				return
    			}
    		case "Path":
    			z.Path, err = dc.ReadString()
    			if err != nil {
    				err = msgp.WrapError(err, "Path")
    				return
    			}
    		case "Creds":
    			var zb0003 uint32
    			zb0003, err = dc.ReadMapHeader()
    			if err != nil {
    				err = msgp.WrapError(err, "Creds")
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Sun Sep 28 20:59:21 UTC 2025
    - 40.7K bytes
    - Viewed (0)
  5. src/test/java/jcifs/smb1/smb1/SmbTreeTest.java

            // Verify session.send was called
            verify(session).send(request, response);
            assertEquals(123, request.tid);
            // For A: service with DFS, path should be modified (share name is uppercased)
            assertEquals("\\testHost\\TESTSHARE\\testPath", request.path);
            assertEquals(ServerMessageBlock.FLAGS2_RESOLVE_PATHS_IN_DFS, request.flags2 & ServerMessageBlock.FLAGS2_RESOLVE_PATHS_IN_DFS);
        }
    
        @Test
    Registered: Sat Dec 20 13:44:44 UTC 2025
    - Last Modified: Thu Aug 14 07:14:38 UTC 2025
    - 10.2K bytes
    - Viewed (0)
  6. docs/en/docs/tutorial/handling-errors.md

    Because it's a Python exception, you don't `return` it, you `raise` it.
    
    This also means that if you are inside a utility function that you are calling inside of your *path operation function*, and you raise the `HTTPException` from inside of that utility function, it won't run the rest of the code in the *path operation function*, it will terminate that request right away and send the HTTP error from the `HTTPException` to the client.
    
    Registered: Sun Dec 28 07:19:09 UTC 2025
    - Last Modified: Wed Dec 17 20:41:43 UTC 2025
    - 9K bytes
    - Viewed (0)
  7. src/main/resources/fess_env_crawler.properties

    # SMTP server settings for main: host:port
    mail.smtp.server.main.host.and.port = localhost:25
    
    # The prefix of subject to show test environment or not
    mail.subject.test.prefix = 
    
    # The common return path of all mail
    mail.return.path = root@localhost
    
    
    # ========================================================================================
    #                                                                                      DB
    Registered: Sat Dec 20 09:19:18 UTC 2025
    - Last Modified: Mon Jan 29 07:34:32 UTC 2018
    - 2.2K bytes
    - Viewed (0)
  8. src/main/resources/fess_env_thumbnail.properties

    # SMTP server settings for main: host:port
    mail.smtp.server.main.host.and.port = localhost:25
    
    # The prefix of subject to show test environment or not
    mail.subject.test.prefix = 
    
    # The common return path of all mail
    mail.return.path = root@localhost
    
    
    # ========================================================================================
    #                                                                                      DB
    Registered: Sat Dec 20 09:19:18 UTC 2025
    - Last Modified: Mon Feb 12 13:38:57 UTC 2018
    - 2.2K bytes
    - Viewed (0)
  9. docs/es/docs/advanced/additional-responses.md

    ## Combina responses predefinidos y personalizados { #combine-predefined-responses-and-custom-ones }
    
    Es posible que desees tener algunos responses predefinidos que se apliquen a muchas *path operations*, pero que quieras combinarlos con responses personalizados necesarios por cada *path operation*.
    
    Para esos casos, puedes usar la técnica de Python de "desempaquetar" un `dict` con `**dict_to_unpack`:
    
    ```Python
    old_dict = {
        "old key": "old value",
    Registered: Sun Dec 28 07:19:09 UTC 2025
    - Last Modified: Wed Dec 17 20:41:43 UTC 2025
    - 9.3K bytes
    - Viewed (0)
  10. docs/en/docs/advanced/additional-responses.md

    ## Combine predefined responses and custom ones { #combine-predefined-responses-and-custom-ones }
    
    You might want to have some predefined responses that apply to many *path operations*, but you want to combine them with custom responses needed by each *path operation*.
    
    For those cases, you can use the Python technique of "unpacking" a `dict` with `**dict_to_unpack`:
    
    ```Python
    old_dict = {
        "old key": "old value",
    Registered: Sun Dec 28 07:19:09 UTC 2025
    - Last Modified: Wed Dec 17 20:41:43 UTC 2025
    - 8.9K bytes
    - Viewed (0)
Back to top