- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 594 for Define (0.22 sec)
-
ci/official/containers/ml_build_arm64/builder.devtoolset/gcc9-fixups.patch
# define hidden_ver(local, name) __hidden_ver1(local, __GI_##name, name); # define hidden_data_ver(local, name) hidden_ver(local, name) # define hidden_def(name) __hidden_ver1(__GI_##name, name, name); @@ -541,7 +550,8 @@ for linking") # define __hidden_nolink1(local, internal, name, version) \ __hidden_nolink2 (local, internal, name, version) # define __hidden_nolink2(local, internal, name, version) \
Registered: Tue Sep 09 12:39:10 UTC 2025 - Last Modified: Mon Nov 11 19:25:56 UTC 2024 - 8.9K bytes - Viewed (0) -
ci/official/containers/ml_build_arm64/builder.devtoolset/stringop_trunc.patch
#ifndef _UTMP_H # error "Never include <bits/utmp.h> directly; use <utmp.h> instead." @@ -24,11 +24,13 @@ #include <time.h> -#define UT_NAMESIZE 8 -#define UT_LINESIZE 8 -#define UT_HOSTSIZE 16 +#define UT_LINESIZE 32 +#define UT_NAMESIZE 32 +#define UT_HOSTSIZE 256 +/* The structure describing an entry in the database of + previous logins. */ struct lastlog { time_t ll_time;
Registered: Tue Sep 09 12:39:10 UTC 2025 - Last Modified: Mon Nov 11 19:25:56 UTC 2024 - 42.9K bytes - Viewed (0) -
docs/pt/docs/advanced/openapi-webhooks.md
Isso normalmente é chamado de **webhook**. ## Etapas dos Webhooks Normalmente, o processo é que **você define** em seu código qual é a mensagem que você irá mandar, o **corpo da sua requisição**. Você também define de alguma maneira em quais **momentos** a sua aplicação mandará essas requisições ou eventos. E os **seus usuários** definem de alguma forma (em algum painel por exemplo) a **URL** que a sua aplicação deve enviar essas requisições.
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Mon Nov 18 02:25:44 UTC 2024 - 3.2K bytes - Viewed (0) -
.bazelrc
build:mkl --define=build_with_mkl=true --define=enable_mkl=true build:mkl --define=tensorflow_mkldnn_contraction_kernel=0 build:mkl --define=build_with_openmp=true build:mkl -c opt # config to build OneDNN backend with a user specified threadpool. build:mkl_threadpool --define=build_with_mkl=true --define=enable_mkl=true build:mkl_threadpool --define=tensorflow_mkldnn_contraction_kernel=0
Registered: Tue Sep 09 12:39:10 UTC 2025 - Last Modified: Fri Aug 22 21:03:34 UTC 2025 - 56K bytes - Viewed (0) -
ci/official/containers/ml_build/builder.devtoolset/glibc2.17-inline.patch
inline semantics, unless -fgnu89-inline is used. */ -#if (!defined __cplusplus || __GNUC_PREREQ (4,3)) && defined __GNUC__ +#if (!defined __cplusplus || __GNUC_PREREQ (4,3) || defined __clang__) && defined __GNUC__ # if defined __GNUC_STDC_INLINE__ || defined __cplusplus # define __extern_inline extern __inline __attribute__ ((__gnu_inline__))
Registered: Tue Sep 09 12:39:10 UTC 2025 - Last Modified: Tue Sep 24 20:45:58 UTC 2024 - 663 bytes - Viewed (0) -
docs/en/docs/advanced/openapi-webhooks.md
This is normally called a **webhook**. ## Webhooks steps { #webhooks-steps } The process normally is that **you define** in your code what is the message that you will send, the **body of the request**. You also define in some way at which **moments** your app will send those requests or events. And **your users** define in some way (for example in a web dashboard somewhere) the **URL** where your app should send those requests.
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun Aug 31 09:15:41 UTC 2025 - 2.9K bytes - Viewed (0) -
docs/en/docs/advanced/events.md
# Lifespan Events { #lifespan-events } You can define logic (code) that should be executed before the application **starts up**. This means that this code will be executed **once**, **before** the application **starts receiving requests**. The same way, you can define logic (code) that should be executed when the application is **shutting down**. In this case, this code will be executed **once**, **after** having handled possibly **many requests**.
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun Aug 31 09:15:41 UTC 2025 - 7.9K bytes - Viewed (0) -
docs/en/docs/tutorial/request-forms-and-files.md
```console $ pip install python-multipart ``` /// ## Import `File` and `Form` { #import-file-and-form } {* ../../docs_src/request_forms_and_files/tutorial001_an_py39.py hl[3] *} ## Define `File` and `Form` parameters { #define-file-and-form-parameters } Create file and form parameters the same way you would for `Body` or `Query`: {* ../../docs_src/request_forms_and_files/tutorial001_an_py39.py hl[10:12] *}
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun Aug 31 09:15:41 UTC 2025 - 1.5K bytes - Viewed (0) -
src/test/java/jcifs/SmbConstantsTest.java
import org.junit.jupiter.api.Test; /** * Test class for SmbConstants interface constants */ @DisplayName("SmbConstants Tests") class SmbConstantsTest extends BaseTest { @Test @DisplayName("Should define default connection constants") void testDefaultConstants() { assertEquals(445, SmbConstants.DEFAULT_PORT); assertEquals(10, SmbConstants.DEFAULT_MAX_MPX_COUNT);
Registered: Sun Sep 07 00:10:21 UTC 2025 - Last Modified: Thu Aug 14 05:31:44 UTC 2025 - 11.3K bytes - Viewed (0) -
docs/en/docs/tutorial/header-params.md
You can define Header parameters the same way you define `Query`, `Path` and `Cookie` parameters. ## Import `Header` { #import-header } First import `Header`: {* ../../docs_src/header_params/tutorial001_an_py310.py hl[3] *} ## Declare `Header` parameters { #declare-header-parameters } Then declare the header parameters using the same structure as with `Path`, `Query` and `Cookie`.
Registered: Sun Sep 07 07:19:17 UTC 2025 - Last Modified: Sun Aug 31 09:15:41 UTC 2025 - 3K bytes - Viewed (0)