- Sort Score
- Result 10 results
- Languages All
Results 41 - 50 of 261 for knop (0.04 sec)
-
docs/en/docs/advanced/additional-status-codes.md
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Sun Oct 27 16:12:23 UTC 2024 - 1.9K bytes - Viewed (0) -
impl/maven-core/lifecycle-executor.txt
</execution> </executions> </plugin> . . . </plugins>
Registered: Sun Nov 03 03:35:11 UTC 2024 - Last Modified: Fri Oct 25 12:31:46 UTC 2024 - 9.7K bytes - Viewed (0) -
impl/maven-core/plugin-manager.txt
* * from igor: two plugins A and B, both depend on the same library but use different versions, say * lib 1.0 and lib 2.0 when debugger hits a breakpoint inside a class from the library, IDE needs to * know which version of library the class comes from */
Registered: Sun Nov 03 03:35:11 UTC 2024 - Last Modified: Fri Oct 25 12:31:46 UTC 2024 - 12.9K bytes - Viewed (0) -
cmd/healthcheck-handler.go
w.Header().Set(xhttp.MinIOHealingDrives, strconv.Itoa(result.HealingDrives)) } if !result.Healthy { // As a maintenance call we are purposefully asked to be taken // down, this is for orchestrators to know if we can safely // take this server down, return appropriate error. if opts.Maintenance { writeResponse(w, http.StatusPreconditionFailed, nil, mimeNone) } else {
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Wed Jun 26 07:44:34 UTC 2024 - 6.9K bytes - Viewed (0) -
docs/en/docs/advanced/index.md
You could still use most of the features in **FastAPI** with the knowledge from the main [Tutorial - User Guide](../tutorial/index.md){.internal-link target=_blank}. And the next sections assume you already read it, and assume that you know those main ideas. ## External Courses
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Tue Aug 06 04:48:30 UTC 2024 - 1.8K bytes - Viewed (0) -
docs/en/docs/tutorial/extra-models.md
* The **database model** would probably need to have a hashed password. /// danger Never store user's plaintext passwords. Always store a "secure hash" that you can then verify. If you don't know, you will learn what a "password hash" is in the [security chapters](security/simple-oauth2.md#password-hashing){.internal-link target=_blank}. /// ## Multiple models
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Sun Oct 06 20:36:54 UTC 2024 - 7.7K bytes - Viewed (0) -
guava-gwt/src/com/google/thirdparty/publicsuffix/PublicSuffixType.gwt.xml
<!-- 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 Java package; see
Registered: Fri Nov 01 12:43:10 UTC 2024 - Last Modified: Fri Jul 19 16:02:36 UTC 2024 - 1.4K bytes - Viewed (0) -
guava-gwt/src/com/google/common/cache/Cache.gwt.xml
<!-- 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 Java package; see
Registered: Fri Nov 01 12:43:10 UTC 2024 - Last Modified: Fri Jul 19 16:02:36 UTC 2024 - 1.6K bytes - Viewed (0) -
guava-gwt/test/com/google/common/testing/Testing.gwt.xml
<!-- 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 Java package; see
Registered: Fri Nov 01 12:43:10 UTC 2024 - Last Modified: Fri Jul 19 16:02:36 UTC 2024 - 1.6K bytes - Viewed (0) -
docs/en/docs/deployment/https.md
* The encryption of the connection happens at the **TCP level**. * That's one layer **below HTTP**. * So, the **certificate and encryption** handling is done **before HTTP**. * **TCP doesn't know about "domains"**. Only about IP addresses. * The information about the **specific domain** requested goes in the **HTTP data**.
Registered: Sun Nov 03 07:19:11 UTC 2024 - Last Modified: Tue Aug 06 04:48:30 UTC 2024 - 12K bytes - Viewed (0)