| /third_party/typescript/tests/baselines/reference/tsserver/cachingFileSystemInformation/ |
| D | watchDirectories-for-config-file-with-case-insensitive-file-system.js | 3 //// [/Users/someuser/work/applications/frontend/src/app/utils/Analytic.ts]
6 //// [/Users/someuser/work/applications/frontend/src/app/redux/configureStore.ts]
22 //// [/Users/someuser/work/applications/frontend/tsconfig.json]
32 Info 1 [00:00:34.000] Search path: /Users/someuser/work/applications/frontend/src/app/utils
33 …fo: /Users/someuser/work/applications/frontend/src/app/utils/Analytic.ts :: Config file name: /Use…
34 Info 3 [00:00:36.000] Creating configuration project /Users/someuser/work/applications/frontend/…
35 …tchInfo: /Users/someuser/work/applications/frontend/tsconfig.json 2000 undefined Project: /Users/s…
36 Info 5 [00:00:38.000] Config: /Users/someuser/work/applications/frontend/tsconfig.json : {
38 "/Users/someuser/work/applications/frontend/src/app/redux/configureStore.ts",
39 "/Users/someuser/work/applications/frontend/src/app/utils/Analytic.ts"
[all …]
|
| D | watchDirectories-for-config-file-with-case-sensitive-file-system.js | 3 //// [/Users/someuser/work/applications/frontend/src/app/utils/Analytic.ts]
6 //// [/Users/someuser/work/applications/frontend/src/app/redux/configureStore.ts]
22 //// [/Users/someuser/work/applications/frontend/tsconfig.json]
32 Info 1 [00:00:34.000] Search path: /Users/someuser/work/applications/frontend/src/app/utils
33 …fo: /Users/someuser/work/applications/frontend/src/app/utils/Analytic.ts :: Config file name: /Use…
34 Info 3 [00:00:36.000] Creating configuration project /Users/someuser/work/applications/frontend/…
35 …tchInfo: /Users/someuser/work/applications/frontend/tsconfig.json 2000 undefined Project: /Users/s…
36 Info 5 [00:00:38.000] Config: /Users/someuser/work/applications/frontend/tsconfig.json : {
38 "/Users/someuser/work/applications/frontend/src/app/redux/configureStore.ts",
39 "/Users/someuser/work/applications/frontend/src/app/utils/Analytic.ts"
[all …]
|
| /third_party/curl/docs/libcurl/ |
| D | libcurl-security.3 | 37 Many applications are used in closed networks where users and servers can
40 some risks in the ways in which applications commonly use libcurl and
42 classes of attacks that robust applications should consider. The Common
63 For applications that enable .netrc use, a user who manage to set the right
103 enabled by default. Applications may opt to restrict that set further.
129 Applications can mitigate against this by disabling
151 10.1.2.3. Applications can mitigate against this by setting a
159 and display the result. Applications can mitigate against this with the
165 behind a firewall. Applications can mitigate against this by using the
198 overwritten. Applications must not allow any unsanitized URL to be passed in
[all …]
|
| /third_party/openssl/doc/man7/ |
| D | fips_module.pod | 20 Applications written to use the OpenSSL 3.0 FIPS module should not use any
45 =head2 Making all applications use the FIPS module by default
47 One simple approach is to cause all applications that are using OpenSSL to only
50 This approach can be done purely via configuration. As long as applications are
99 Any applications that use OpenSSL 3.0 and are started after these changes are
100 made will start using only the FIPS module unless those applications take
108 are required in applications in order to benefit from the FIPS module. There are
115 You may not want all applications to use the FIPS module.
117 It may be the case that some applications should and some should not use the
122 If applications take explicit steps to not load the default config file or
[all …]
|
| D | migration_guide.pod | 28 of applications will work unchanged with OpenSSL 3.0 if those applications
31 applications need to take advantage of some of the new features available in
72 L</Using the FIPS Module in applications>.
89 your applications, but you may start to see deprecation warnings during
104 Applications using the EVP APIs to access these algorithms should instead use
105 more modern algorithms. If that is not possible then these applications
119 This is particularly relevant for applications written to use the OpenSSL 3.0
173 Existing applications that use KDF algorithms using EVP_PKEY
176 All new applications should use the new L<EVP_KDF(3)> interface.
188 All new applications should use the new L<EVP_MAC(3)> interface.
[all …]
|
| /third_party/node/deps/openssl/openssl/ |
| D | README-ENGINES.md | 58 applications when they use that ENGINE. Work is in progress (or at least
60 NCONF) code so that applications using OpenSSL's existing configuration
62 Presently however, applications must use the ENGINE API itself to provide
86 devices from common OpenSSL-based applications. Bugs and/or inexplicable
119 This way, applications do not need to know anything specific to any
135 applications. This could be because existing compiled-in implementations
141 The other use-case for "dynamic" is with applications that wish to
147 applications based on OpenSSL 0.9.7 or later. If you're using an
180 ENGINE's "id". For most applications, this isn't necessary - but some
216 Applications that support the ENGINE API and more specifically, the
[all …]
|
| /third_party/openssl/ |
| D | README-ENGINES.md | 58 applications when they use that ENGINE. Work is in progress (or at least
60 NCONF) code so that applications using OpenSSL's existing configuration
62 Presently however, applications must use the ENGINE API itself to provide
86 devices from common OpenSSL-based applications. Bugs and/or inexplicable
119 This way, applications do not need to know anything specific to any
135 applications. This could be because existing compiled-in implementations
141 The other use-case for "dynamic" is with applications that wish to
147 applications based on OpenSSL 0.9.7 or later. If you're using an
180 ENGINE's "id". For most applications, this isn't necessary - but some
216 Applications that support the ENGINE API and more specifically, the
[all …]
|
| /third_party/vk-gl-cts/external/vulkan-docs/src/appendices/ |
| D | boilerplate.txt | 18 Khronos provides a corresponding set of header files for applications using
37 Applications normally will include the header `{full_header}`.
136 Applications that do not make use of window system-specific extensions may
166 Applications should not use this value as their
168 Instead applications should explicitly select a specific fixed major/minor
222 Applications must: not define handles in a way that is not binary compatible
272 allowing applications to decide which ones should be defined and how the
278 Before including these platform-specific Vulkan headers, applications must:
282 As a convenience for applications that do not need the flexibility of
286 Applications control which platform-specific headers are included by
[all …]
|
| /third_party/rust/crates/libc/ci/ |
| D | android-emulator-package.xml | 29 …usive, and non-sublicensable license to use the SDK solely to develop applications for compatible …
31 …applications for other platforms (including non-compatible implementations of Android) or to devel…
39 …e to you and that future versions of the SDK may be incompatible with applications developed on pr…
48 …o any software applications that you develop using the SDK, including any intellectual property ri…
50 4.2 You agree to use the SDK and write applications only for purposes that are permitted by (a) the…
52 4.3 You agree that if you use the SDK to develop applications for general public users, you will pr…
56 …resources that you create, transmit or display through Android and/or applications for Android, an…
62 …u may choose yourself and that you will be solely responsible for all applications that are develo…
71 7. Third Party Applications
73 …applications developed by a third party or that access data, content or resources provided by a th…
[all …]
|
| /third_party/openssl/doc/man3/ |
| D | EVP_PKEY_set1_RSA.pod | 81 functions are deprecated. Applications should instead use
88 I<pkey> is freed. These macros are deprecated. Applications should instead read
96 These functions are deprecated. Applications should instead use the EVP_PKEY
98 then applications should use L<EVP_PKEY_get_params(3)> and other similar
107 are deprecated. Applications should instead use the EVP_PKEY directly where
109 applications should use L<EVP_PKEY_get_params(3)> and other similar functions.
130 function is deprecated. Applications should use providers instead of engines
136 error occurs. This function is deprecated. Applications should use providers
159 in order that applications can "free" the return value. However applications
176 Most applications wishing to know a key type will simply call
|
| /third_party/ltp/testcases/kernel/device-drivers/v4l/user_space/doc/spec/ |
| D | x1859.htm | 89 applications, for example video images, raw or sliced VBI data, RDS
93 reopening a device, applications should always negotiate a data format
97 applications can also just query the current selection.</P
146 multiple panel applications can access the same device concurrently to
166 >When applications omit the
211 applications must support the <CODE
252 by all drivers exchanging image data with applications.</P
263 conversion routine or library for integration into applications.</P
295 enumerate) seems useless, but there are applications serving as proxy
296 between drivers and the actual video applications for which this is
|
| D | r11680.htm | 167 captured or output, applications can request frame skipping or
190 >To get and set the streaming parameters applications call
385 >Set by drivers and applications, see <A
408 >Applications store here the desired frame
420 reset manually applications can just set this field to
444 unused, applications and drivers must set this field to zero.
445 Applications using this field should check the driver name and
460 >Applications set this field to the desired number
485 applications must set the array to zero.</TD
538 >Set by drivers and applications, see <A
[all …]
|
| D | x294.htm | 80 >When multiple applications share a device it may be
83 could for example block other applications from changing video
85 permit low priority applications working in background, which can be
86 preempted by user controlled applications and automatically regain
106 Applications requiring a different priority will usually call
130 An event mechanism to notify applications about asynchronous property
|
| /third_party/EGL/extensions/NV/ |
| D | EGL_NV_stream_origin.txt | 50 applications will rarely have to worry about frame orientation.
52 However, in some cases consumer applications such as compositors
55 stream frames. This will allow applications to adjust the way they
58 Similarly, producer applications might need to adjust how rendering
131 implementation. Applications must coordinate what they are
156 implementation. Applications must coordinate what they are
180 implementation. Applications must coordinate what they are
252 EGL_DONT_CARE and applications must coordinate what they do.
264 applications do not need to worry about it.
|
| /third_party/mesa3d/src/util/ |
| D | driconf_static.py | 73 self.applications = []
77 self.applications.append(Application(application))
143 const struct driconf_application *applications;
173 % for application in device.applications:
177 %if len(device.applications) > 0:
179 % for application in device.applications:
214 .num_applications = ${len(device.applications)},
215 % if len(device.applications) > 0:
216 .applications = ${device.cname}_applications,
|
| /third_party/skia/third_party/externals/opengl-registry/extensions/EXT/ |
| D | GLX_EXT_buffer_age.txt | 47 applications about how the driver manages the set of front and
48 back buffers associated with a given surface to allow applications
59 This extension lets applications query the age of the back buffer
80 buffers may be recycled so it wasn't safe for applications to try
81 and reuse their contents. Now applications can keep track of all
100 elapsed since it was most recently defined. Applications can,
145 reset. In other words, applications can assume that no event
150 It is up to applications to track pixel ownership using data
227 boundary otherwise applications can't be absolutely sure of
|
| /third_party/openGLES/extensions/EXT/ |
| D | GLX_EXT_buffer_age.txt | 47 applications about how the driver manages the set of front and
48 back buffers associated with a given surface to allow applications
59 This extension lets applications query the age of the back buffer
80 buffers may be recycled so it wasn't safe for applications to try
81 and reuse their contents. Now applications can keep track of all
100 elapsed since it was most recently defined. Applications can,
145 reset. In other words, applications can assume that no event
150 It is up to applications to track pixel ownership using data
227 boundary otherwise applications can't be absolutely sure of
|
| /third_party/vk-gl-cts/external/vulkan-docs/src/chapters/VK_KHR_present_wait/ |
| D | present_wait.txt | 8 Applications wanting to control the pacing of the application by monitoring
22 applications can discover when images were presented, but only
26 Providing a mechanism which allows applications to block, waiting for a
31 The `apiext:VK_KHR_present_wait` extension allows applications to tell the
|
| /third_party/gstreamer/gstplugins_bad/sys/dvb/ |
| D | camapplication.c | 101 al->applications = g_hash_table_new (resource_id_hash, g_direct_equal); in cam_al_new()
115 g_hash_table_destroy (al->applications); in cam_al_destroy()
122 if (g_hash_table_lookup (al->applications, in cam_al_install()
128 g_hash_table_insert (al->applications, in cam_al_install()
139 ret = g_hash_table_remove (al->applications, in cam_al_uninstall()
148 return CAM_AL_APPLICATION (g_hash_table_lookup (al->applications, in cam_al_get()
177 g_hash_table_foreach (al->applications, foreach_get_key, &resource_ids); in cam_al_get_resource_ids()
238 application = g_hash_table_lookup (al->applications, in open_session_request_cb()
|
| /third_party/openGLES/extensions/NV/ |
| D | NV_3dvision_settings.txt | 44 requiring applications to change their rendering methods. However
45 there are cases where applications can benefit from adjusting 3D
47 applications not yet known to 3D Vision, to assist 3D Vision in
183 for Applications with established stereo profiles will have
190 with are orthographic and perspective settings. For Applications
192 Applications that use context creation attributes to enable 3D
221 this matches behavior of 3D Vision enabled applications that do not
225 applications that make meaningful use of ReadPixels. Such
|
| /third_party/skia/third_party/externals/opengl-registry/extensions/NV/ |
| D | NV_3dvision_settings.txt | 44 requiring applications to change their rendering methods. However
45 there are cases where applications can benefit from adjusting 3D
47 applications not yet known to 3D Vision, to assist 3D Vision in
183 for Applications with established stereo profiles will have
190 with are orthographic and perspective settings. For Applications
192 Applications that use context creation attributes to enable 3D
221 this matches behavior of 3D Vision enabled applications that do not
225 applications that make meaningful use of ReadPixels. Such
|
| /third_party/gstreamer/gstreamer/docs/gst/ |
| D | building.md | 2 title: Building GStreamer and GStreamer Applications
3 short-description: How to build the GStreamer framework and applications using it.
38 # Building GStreamer Applications
40 Applications and libraries can use `pkg-config` to get all the needed
|
| /third_party/vk-gl-cts/external/vulkan-docs/src/proposals/ |
| D | VK_KHR_dynamic_rendering.asciidoc | 19 . Most applications do not or cannot use subpasses, but still pay the cost of setting them up
38 The disadvantage of this is that applications still have to manage render pass objects, and it does…
40 Option 2 effectively allows applications to provide the same information to applications again with…
86 Applications should use other synchronization primitives (barriers, events) to manage synchronizati…
174 This allows applications to use secondary command buffers with dynamic rendering as they would have…
208 Applications can suspend a render pass in one command buffer using `VK_RENDERING_SUSPENDING_BIT_KHR…
213 Applications can resume a dynamic render pass in the same command buffer as it was suspended.
214 Applications can record a dynamic render pass wholly inside secondary command buffers.
255 …ects, it is now necessary to provide some of that same information to applications at pipeline cre…
273 Applications can provide a valid format here and then not specify an attachment in `vkCmdBeginRende…
[all …]
|
| /third_party/gstreamer/gstplugins_base/gst-libs/gst/pbutils/ |
| D | pbutils.c | 25 * libgstpbutils is a general utility library for plugins and applications.
33 * * support for applications to initiate installation of missing plugins (if
40 * * API for applications to recognise and handle missing-plugin messages
50 * Before using any of its functions, applications and plugins must call
109 * thread-safe. Applications should call it after calling gst_init(),
|
| /third_party/EGL/extensions/EXT/ |
| D | EGL_EXT_swap_buffers_with_damage.txt | 86 applications using this API must still ensure that the entire
178 1) Do applications have to make sure the rectangles don't overlap?
180 RESOLVED: No, that would be inconvenient for applications and we
189 purposes so although it wouldn't be beneficial to applications if
212 and this can make it difficult for applications to avoid certain
235 and we saw very little benefit to applications from providing
238 The number of applications that would be able to avoid fully
245 this limitation doesn't introduce any new issue for applications
246 to consider. Applications should already fully redraw buffer
|