Home
last modified time | relevance | path

Searched full:path (Results 33451 - 33475 of 38166) sorted by relevance

1...<<1331133213331334133513361337133813391340>>...1527

/third_party/mesa3d/src/amd/registers/
H A Dparse_kernel_headers.py696 # Add the path to the filenames
877 print('Second parameter should be the path to the amd/include directory.', file=sys.stderr)
/third_party/mesa3d/src/broadcom/vulkan/
H A Dv3dv_image.c260 * instead it will use the prime blit path (use_buffer_blit flag in in create_image()
263 * As a result, on that path, swapchain images do not have any special in create_image()
/third_party/mesa3d/src/compiler/isaspec/
H A Disa.py408 self.base_path = os.path.dirname(xmlpath)
451 p = os.path.join(self.base_path, imprt.attrib['file'])
/third_party/mesa3d/src/amd/compiler/tests/
H A Dcheck_output.py24 import os.path namespace
441 parse_check(variant, check, checks, 'line %d of %s' % (line_num, os.path.split(fname)[1]))
/third_party/ltp/
H A Dltpmenu121 install $cmd or export PATH correctly before\
228 --inputbox " Please enter the full path and \
/third_party/mesa3d/src/gallium/frontends/clover/llvm/
H A Dinvocation.cpp303 // Add libclc generic search path in compile()
311 // Add opencl-c generic search path in compile()
/third_party/node/lib/internal/
H A Dutil.js369 const { sep } = require('path');
782 const { resolve } = require('path');
/third_party/node/deps/v8/third_party/jinja2/
H A Dutils.py115 use import paths as endpoints or something similar. An import path can
141 if not os.path.isfile(filename):
/third_party/node/doc/api/
H A Dpermissions.json53 "desc": "<p>An application may need to ship patched versions of modules or to prevent\nmodules from allowing all modules access to all other modules. Redirection\ncan be used by intercepting attempts to load the modules wishing to be\nreplaced.</p>\n<pre><code class=\"language-json\">{\n \"resources\": {\n \"./app/checked.js\": {\n \"dependencies\": {\n \"fs\": true,\n \"os\": \"./app/node_modules/alt-os\",\n \"http\": { \"import\": true }\n }\n }\n }\n}\n</code></pre>\n<p>The dependencies are keyed by the requested specifier string and have values\nof either <code>true</code>, <code>null</code>, a string pointing to a module to be resolved,\nor a conditions object.</p>\n<p>The specifier string does not perform any searching and must match exactly what\nis provided to the <code>require()</code> or <code>import</code> except for a canonicalization step.\nTherefore, multiple specifiers may be needed in the policy if it uses multiple\ndifferent strings to point to the same module (such as excluding the extension).</p>\n<p>Specifier strings are canonicalized but not resolved prior to be used for\nmatching in order to have some compatibility with import maps, for example if a\nresource <code>file:///C:/app/server.js</code> was given the following redirection from a\npolicy located at <code>file:///C:/app/policy.json</code>:</p>\n<pre><code class=\"language-json\">{\n \"resources\": {\n \"file:///C:/app/utils.js\": {\n \"dependencies\": {\n \"./utils.js\": \"./utils-v2.js\"\n }\n }\n }\n}\n</code></pre>\n<p>Any specifier used to load <code>file:///C:/app/utils.js</code> would then be intercepted\nand redirected to <code>file:///C:/app/utils-v2.js</code> instead regardless of using an\nabsolute or relative specifier. However, if a specifier that is not an absolute\nor relative URL string is used, it would not be intercepted. So, if an import\nsuch as <code>import('#utils')</code> was used, it would not be intercepted.</p>\n<p>If the value of the redirection is <code>true</code>, a \"dependencies\" field at the top of\nthe policy file will be used. If that field at the top of the policy file is\n<code>true</code> the default node searching algorithms are used to find the module.</p>\n<p>If the value of the redirection is a string, it is resolved relative to\nthe manifest and then immediately used without searching.</p>\n<p>Any specifier string for which resolution is attempted and that is not listed in\nthe dependencies results in an error according to the policy.</p>\n<p>Redirection does not prevent access to APIs through means such as direct access\nto <code>require.cache</code> or through <code>module.constructor</code> which allow access to\nloading modules. Policy redirection only affects specifiers to <code>require()</code> and\n<code>import</code>. Other means, such as to prevent undesired access to APIs through\nvariables, are necessary to lock down that path of loading modules.</p>\n<p>A boolean value of <code>true</code> for the dependencies map can be specified to allow a\nmodule to load any specifier without redirection. This can be useful for local\ndevelopment and may have some valid usage in production, but should be used\nonly with care after auditing a module to ensure its behavior is valid.</p>\n<p>Similar to <code>\"exports\"</code> in <code>package.json</code>, dependencies can also be specified to\nbe objects containing conditions which branch how dependencies are loaded. In\nthe preceding example, <code>\"http\"</code> is allowed when the <code>\"import\"</code> condition is\npart of loading it.</p>\n<p>A value of <code>null</code> for the resolved value causes the resolution to fail. This\ncan be used to ensure some kinds of dynamic access are explicitly prevented.</p>\n<p>Unknown values for the resolved module location cause failures but are\nnot guaranteed to be forward compatible.</p>\n<h5>Example: Patched dependency</h5>\n<p>Redirected dependencies can provide attenuated or modified functionality as fits\nthe application. For example, log data about timing of function durations by\nwrapping the original:</p>\n<pre><code class=\"language-js\">const original = require('fn');\nmodule.exports = function fn(...args) {\n console.time();\n try {\n return new.target ?\n Reflect.construct(original, args) :\n Reflect.apply(original, this, args);\n } finally {\n console.timeEnd();\n }\n};\n</code></pre>",
64 "desc": "<p>Use the <code>\"scopes\"</code> field of a manifest to set configuration for many resources\nat once. The <code>\"scopes\"</code> field works by matching resources by their segments.\nIf a scope or resource includes <code>\"cascade\": true</code>, unknown specifiers will\nbe searched for in their containing scope. The containing scope for cascading\nis found by recursively reducing the resource URL by removing segments for\n<a href=\"https://url.spec.whatwg.org/#special-scheme\">special schemes</a>, keeping trailing <code>\"/\"</code> suffixes, and removing the query and\nhash fragment. This leads to the eventual reduction of the URL to its origin.\nIf the URL is non-special the scope will be located by the URL's origin. If no\nscope is found for the origin or in the case of opaque origins, a protocol\nstring can be used as a scope. If no scope is found for the URL's protocol, a\nfinal empty string <code>\"\"</code> scope will be used.</p>\n<p>Note, <code>blob:</code> URLs adopt their origin from the path they contain, and so a scope\nof <code>\"blob:https://nodejs.org\"</code> will have no effect since no URL can have an\norigin of <code>blob:https://nodejs.org</code>; URLs starting with\n<code>blob:https://nodejs.org/</code> will use <code>https://nodejs.org</code> for its origin and\nthus <code>https:</code> for its protocol scope. For opaque origin <code>blob:</code> URLs they will\nhave <code>blob:</code> for their protocol scope since they do not adopt origins.</p>\n<h5>Example</h5>\n<pre><code class=\"language-json\">{\n \"scopes\": {\n \"file:///C:/app/\": {},\n \"file:\": {},\n \"\": {}\n }\n}\n</code></pre>\n<p>Given a file located at <code>file:///C:/app/bin/main.js</code>, the following scopes would\nbe checked in order:</p>\n<ol>\n<li><code>\"file:///C:/app/bin/\"</code></li>\n</ol>\n<p>This determines the policy for all file based resources within\n<code>\"file:///C:/app/bin/\"</code>. This is not in the <code>\"scopes\"</code> field of the policy and\nwould be skipped. Adding this scope to the policy would cause it to be used\nprior to the <code>\"file:///C:/app/\"</code> scope.</p>\n<ol start=\"2\">\n<li><code>\"file:///C:/app/\"</code></li>\n</ol>\n<p>This determines the policy for all file based resources within\n<code>\"file:///C:/app/\"</code>. This is in the <code>\"scopes\"</code> field of the policy and it would\ndetermine the policy for the resource at <code>file:///C:/app/bin/main.js</code>. If the\nscope has <code>\"cascade\": true</code>, any unsatisfied queries about the resource would\ndelegate to the next relevant scope for <code>file:///C:/app/bin/main.js</code>, <code>\"file:\"</code>.</p>\n<ol start=\"3\">\n<li><code>\"file:///C:/\"</code></li>\n</ol>\n<p>This determines the policy for all file based resources within <code>\"file:///C:/\"</code>.\nThis is not in the <code>\"scopes\"</code> field of the policy and would be skipped. It would\nnot be used for <code>file:///C:/app/bin/main.js</code> unless <code>\"file:///\"</code> is set to\ncascade or is not in the <code>\"scopes\"</code> of the policy.</p>\n<ol start=\"4\">\n<li><code>\"file:///\"</code></li>\n</ol>\n<p>This determines the policy for all file based resources on the <code>localhost</code>. This\nis not in the <code>\"scopes\"</code> field of the policy and would be skipped. It would not\nbe used for <code>file:///C:/app/bin/main.js</code> unless <code>\"file:///\"</code> is set to cascade\nor is not in the <code>\"scopes\"</code> of the policy.</p>\n<ol start=\"5\">\n<li><code>\"file:\"</code></li>\n</ol>\n<p>This determines the policy for all file based resources. It would not be used\nfor <code>file:///C:/app/bin/main.js</code> unless <code>\"file:///\"</code> is set to cascade or is not\nin the <code>\"scopes\"</code> of the policy.</p>\n<ol start=\"6\">\n<li><code>\"\"</code></li>\n</ol>\n<p>This determines the policy for all resources. It would not be used for\n<code>file:///C:/app/bin/main.js</code> unless <code>\"file:\"</code> is set to cascade.</p>",
H A Dpermissions.md203 variables, are necessary to lock down that path of loading modules.
255 Note, `blob:` URLs adopt their origin from the path they contain, and so a scope
/third_party/ntfs-3g/libntfs-3g/
H A Dxattrs.c344 * If an absolute path is provided, the mapping file is assumed
347 * If a relative path is provided, the mapping file is assumed
/third_party/ntfs-3g/src/
H A Dntfs-3g.8.in326 \fB.NTFS-3G/UserMapping\fP. If \fIfile-name\fP defines a full path, the
328 relative path, it is interpreted relative to the root of NTFS partition
/third_party/openGLES/extensions/ARB/
H A DARB_framebuffer_sRGB.txt401 8) Should sRGB framebuffer support affect the pixel path?
409 For pixel path operations, an application could use pixel maps
H A DARB_get_program_binary.txt76 GL via ProgramBinary. This is a very useful path for applications that
405 // were cached away. Fallback to source shader loading path,
/third_party/openGLES/extensions/NV/
H A DNV_draw_texture.txt245 power-efficient fixed-function path for drawing the contents of a
424 is a different beast that doesn't go through the regular pixel path, and
/third_party/musl/src/malloc/liteos_a/user_debug/
H A Dmemory_check.c248 "--mwatch or --mrecord <full path>, to call mem_check_init(char *) " in get_file()
765 printf("path: %s create failed, %s\n", mem_stat.f_path_buf, string); in mem_check_init()
/third_party/musl/src/time/
H A D__tz.c257 * standard path will be searched. */ in do_tzset()
263 /* The path is invalid, use the default value. */ in do_tzset()
/third_party/musl/porting/liteos_a/user_debug/src/malloc/
H A Dmemory_check.c233 "--mwatch or --mrecord <full path>, to call mem_check_init(char *) " in get_file()
750 printf("path: %s create failed, %s\n", mem_stat.f_path_buf, string); in mem_check_init()
/third_party/node/deps/cares/m4/
H A Dax_pthread.m4487 [#handle absolute path differently from PATH based program lookup
/third_party/node/deps/icu-small/source/common/
H A Drbbi_cache.cpp244 // next() does not clear it in the fast-path case, where everything matters. Maybe it should. in following()
509 // (subsequent calls to BreakIterator::next() will take the fast path, getting cached results. in populateFollowing()
/third_party/node/deps/icu-small/source/i18n/
H A Dnumber_formatimpl.cpp99 // Safe path: use fImmutablePatternModifier. in getPrefixSuffix()
110 // Unsafe path: use fPatternModifier. in getPrefixSuffixUnsafe()
/third_party/node/deps/npm/node_modules/diff/
H A Drelease-notes.md8 - [#448](https://github.com/kpdecker/jsdiff/pull/411) Performance improvement. Diagonals whose furthest-reaching D-path would go off the edge of the edit graph are now skipped, rather than being pointlessly considered as called for by the original Myers diff algorithm. This dramatically speeds up computing diffs where the new text just appends or truncates content at the end of the old text.
31 - Fix main reference path - b826104
/third_party/node/deps/npm/test/lib/
H A Dnpm.js2 const { resolve, dirname, join } = require('path')
131 'process.env.PATH': resolve(dirs.prefix, 'bin'),
/third_party/icu/icu4c/source/test/perf/dicttrieperf/
H A Ddicttrieperf.cpp81 // from the -s or --sourcedir path.
328 // from the -s or --sourcedir path plus -f or --file-name.
/third_party/icu/icu4c/source/samples/all/
H A Dsamplecheck.bat42 set PATH=%ICU_BINDIR%;%PATH% variable

Completed in 76 milliseconds

1...<<1331133213331334133513361337133813391340>>...1527