| /external/python/cpython3/Lib/logging/ |
| D | config.py | 165 When (re)configuring logging, handle loggers which were in the previous
170 However, don't disable children of named loggers, as that's probably not
171 what was intended by the user. Also, allow existing loggers to NOT be
186 """Create and install loggers"""
189 llist = cp["loggers"]["keys"]
209 #we don't want to lose the existing loggers,
211 #existing is set to contain all existing loggers,
214 #what's left in existing is the set of loggers
219 #avoid disabling child loggers of explicitly
220 #named loggers. With a sorted list it is easier
[all …]
|
| /external/python/cpython2/Lib/logging/ |
| D | config.py | 184 """Create and install loggers"""
187 llist = cp.get("loggers", "keys")
208 #we don't want to lose the existing loggers,
210 #existing is set to contain all existing loggers,
213 #what's left in existing is the set of loggers
218 #avoid disabling child loggers of explicitly
219 #named loggers. With a sorted list it is easier
220 #to find the child loggers.
222 #We'll keep the list of existing loggers
223 #which are children of named loggers here...
[all …]
|
| /external/slf4j/slf4j-api/src/main/java/org/slf4j/helpers/ |
| D | SubstituteLoggerFactory.java | 43 …final ConcurrentMap<String, SubstituteLogger> loggers = new ConcurrentHashMap<String, SubstituteLo… field in SubstituteLoggerFactory
46 SubstituteLogger logger = loggers.get(name); in getLogger()
49 SubstituteLogger oldLogger = loggers.putIfAbsent(name, logger); in getLogger()
57 return new ArrayList<String>(loggers.keySet()); in getLoggerNames()
61 return new ArrayList<SubstituteLogger>(loggers.values()); in getLoggers()
65 loggers.clear(); in clear()
|
| /external/pigweed/pw_console/py/pw_console/ |
| D | embed.py | 51 loggers: Optional[
74 loggers={
94 # Setup Python loggers to output to a file instead of STDOUT.
105 loggers: Dict with keys of log window titles and values of either:
122 self.loggers = loggers
234 """Add loggers to ConsoleApp log pane(s)."""
235 if not self.loggers:
240 if isinstance(self.loggers, list):
241 self.console_app.add_log_handler('Logs', self.loggers)
243 elif isinstance(self.loggers, dict):
[all …]
|
| D | python_logging.py | 25 """Iterates over all loggers known to Python logging."""
94 # Make sure all known loggers propagate to the root logger.
97 # Prevent these loggers from propagating to the root logger.
|
| /external/python/cpython2/Doc/library/ |
| D | logging.config.rst | 93 :param disable_existing_loggers: If specified as ``False``, loggers which
98 disable any existing loggers unless they or
104 existing loggers were *always* disabled.
236 * *loggers* - the corresponding value will be a dict in which each key
252 The specified loggers will be configured according to the level,
268 * *disable_existing_loggers* - whether any existing loggers are to be
285 the object graph of loggers, handlers, filters, formatters at
286 run-time, once a configuration is set up; the verbosity of loggers and
288 loggers, propagation flags). Changing the object graph arbitrarily in
297 ``propagate`` settings in the ``loggers`` and ``root`` entries.
[all …]
|
| D | logging.rst | 44 * Loggers expose the interface that application code directly uses.
45 * Handlers send the log records (created by loggers) to the appropriate
57 Loggers have the following attributes and methods. Note that Loggers are never
64 Loggers that are further down in the hierarchical list are children of loggers
66 loggers with names of ``foo.bar``, ``foo.bar.baz``, and ``foo.bam`` are all
68 package hierarchy, and identical to it if you organise your loggers on a
79 handlers of higher level (ancestor) loggers, in addition to any handlers
81 loggers' handlers - neither the level nor filters of the ancestor loggers in
85 of ancestor loggers.
93 hierarchy, then it will see all events logged by all descendant loggers,
[all …]
|
| /external/slf4j/log4j-over-slf4j/src/main/java/org/apache/log4j/spi/ |
| D | LoggerRepository.java | 25 * <code>Loggers</code>. The relation between loggers in a repository
26 * depends on the repository but typically loggers are arranged in a
30 * <code>LoggerRepository</code> can be queried for existing loggers,
31 * can act as a point of registry for events related to loggers.
|
| /external/python/cpython3/Doc/library/ |
| D | logging.config.rst | 105 :param disable_existing_loggers: If specified as ``False``, loggers which
110 disable any existing non-root loggers unless
181 disable existing loggers, you will need to use a JSON format for
316 * *loggers* - the corresponding value will be a dict in which each key
332 The specified loggers will be configured according to the level,
348 * *disable_existing_loggers* - whether any existing non-root loggers are
365 the object graph of loggers, handlers, filters, formatters at
366 run-time, once a configuration is set up; the verbosity of loggers and
368 loggers, propagation flags). Changing the object graph arbitrarily in
377 ``propagate`` settings in the ``loggers`` and ``root`` entries.
[all …]
|
| D | logging.rst | 40 * Loggers expose the interface that application code directly uses.
41 * Handlers send the log records (created by loggers) to the appropriate
53 Loggers have the following attributes and methods. Note that Loggers should
60 Loggers that are further down in the hierarchical list are children of loggers
62 loggers with names of ``foo.bar``, ``foo.bar.baz``, and ``foo.bam`` are all
64 package hierarchy, and identical to it if you organise your loggers on a
75 passed to the handlers of higher level (ancestor) loggers, in addition to
77 ancestor loggers' handlers - neither the level nor filters of the ancestor
78 loggers in question are considered.
81 of ancestor loggers.
[all …]
|
| /external/python/cpython2/Doc/howto/ |
| D | logging.rst | 331 of components: loggers, handlers, filters, and formatters.
333 * Loggers expose the interface that application code directly uses.
334 * Handlers send the log records (created by loggers) to the appropriate
340 Log event information is passed between loggers, handlers, filters and
344 class (hereafter called :dfn:`loggers`). Each instance has a name, and they are
346 separators. For example, a logger named 'scan' is the parent of loggers
350 A good convention to use when naming loggers is to use a module-level logger,
358 The root of the hierarchy of loggers is called the root logger. That's the
390 The flow of log event information in loggers and handlers is illustrated in the
395 Loggers section in Advanced Logging Tutorial
[all …]
|
| /external/python/cpython2/Lib/test/ |
| D | test_logging.py | 72 # Set two unused loggers: one non-ASCII and one Unicode.
74 # loggers in the configuration code. See issue 8201.
215 #Logging levels in a nested namespace, inherited from parent loggers.
511 [loggers]
537 [loggers]
569 [loggers]
607 [loggers]
637 [loggers]
679 [loggers]
716 [loggers]
[all …]
|
| /external/autotest/server/cros/power/ |
| D | power_telemetry_logger.py | 49 # Dictionary to make passing the default arguments for loggers to the NaN
130 loggers = self._load_and_trim_data(start_ts, end_ts)
134 self._upload_data(loggers, checkpoint_logger)
290 @return a list of loggers, where each logger contains raw power data and
320 '_load_and_trim_data and return a list of loggers.')
341 def _upload_data(self, loggers, checkpoint_logger): argument
344 @param loggers: a list of loggers, where each logger contains raw power
348 for logger in loggers:
456 @return a list of loggers, where each logger contains raw power data and
487 loggers = list()
[all …]
|
| /external/python/cpython3/Doc/howto/ |
| D | logging.rst | 352 of components: loggers, handlers, filters, and formatters.
354 * Loggers expose the interface that application code directly uses.
355 * Handlers send the log records (created by loggers) to the appropriate
361 Log event information is passed between loggers, handlers, filters and
365 class (hereafter called :dfn:`loggers`). Each instance has a name, and they are
367 separators. For example, a logger named 'scan' is the parent of loggers
371 A good convention to use when naming loggers is to use a module-level logger,
379 The root of the hierarchy of loggers is called the root logger. That's the
413 The flow of log event information in loggers and handlers is illustrated in the
418 Loggers section in Advanced Logging Tutorial
[all …]
|
| D | logging-cookbook.rst | 160 Loggers are plain Python objects. The :meth:`~Logger.addHandler` method has no
236 # Now, define a couple of other loggers which might represent areas in your
347 :class:`QueueHandler` to those loggers which are accessed from
354 attach only ``QueueHandlers`` to your loggers) for the benefit of other
426 # Now, define a couple of other loggers which might represent areas in your
806 LOGGERS = ['a.b.c', 'd.e.f']
833 logger = logging.getLogger(choice(LOGGERS))
888 loggers = ['foo', 'foo.bar', 'foo.bar.baz',
892 logger = logging.getLogger(random.choice(loggers))
930 'loggers': {
[all …]
|
| /external/autotest/client/site_tests/power_Dummy/ |
| D | control | 18 loggers, and measurement dashboards. Run for a short amount of time, collect
20 Loggers included in this test are all loggers in power_test and
|
| /external/ComputeLibrary/arm_compute/core/utils/logging/ |
| D | LoggerRegistry.h | 40 /** Registry class holding all the instantiated loggers */
55 … * @param[in] printers Printers to attach to the system loggers. Defaults with a @ref StdPrinter.
71 /** Creates reserved library loggers
74 …* @param[in] printers (Optional) Printers to attach to the system loggers. Defaults with a @ref S…
|
| /external/pigweed/pw_console/py/ |
| D | console_app_test.py | 57 loggers = {
64 for window_title, logger_instances in loggers.items():
67 # Two panes, one for the loggers and one for the repl.
|
| /external/slf4j/log4j-over-slf4j/src/main/java/org/apache/log4j/ |
| D | Log4jLoggerFactory.java | 26 * This class is a factory that creates and maintains org.apache.log4j.Loggers
27 * wrapping org.slf4j.Loggers.
30 * all newly created instances are not duplicates of existing loggers.
|
| /external/slf4j/slf4j-api/src/main/java/org/slf4j/ |
| D | LoggerFactory.java | 43 * The <code>LoggerFactory</code> is a utility class producing Loggers for
177 List<SubstituteLogger> loggers = TEMP_FACTORY.getLoggers(); in fixSubstitutedLoggers() local
179 if (loggers.isEmpty()) { in fixSubstitutedLoggers()
183 Util.report("The following set of substitute loggers may have been accessed"); in fixSubstitutedLoggers()
186 Util.report("loggers will work as normally expected."); in fixSubstitutedLoggers()
188 for (SubstituteLogger subLogger : loggers) { in fixSubstitutedLoggers()
|
| /external/testng/src/main/java/org/testng/log4testng/ |
| D | Logger.java | 38 * # Specifies the root Loggers logging level. Will log DEBUG level and above
48 * In your source files you will typically instantiate and use loggers this ways:
120 /** Map of all known loggers. */
121 private static final Map<Class, Logger> loggers = Maps.newHashMap(); field in Logger
139 * will be returned. Otherwise, a new instance is created. By default, loggers
148 Logger logger= loggers.get(pClass); in getLogger()
154 loggers.put(pClass, logger); in getLogger()
405 * "org.testng.TestNG" the the following loggers are searched in this order:
478 loggers.clear(); in testInitialize()
557 * Tests that the root logger's default level is WARN and that loggers do not
|
| /external/pigweed/pw_cli/py/pw_cli/ |
| D | log.py | 102 If you have Python loggers separate from the root logger you can use
170 # propagated from child loggers are handled.
211 """Iterates over all loggers known to Python logging."""
219 """Increases the log level to the specified value for all known loggers."""
|
| /external/crosvm/base/src/ |
| D | syslog.rs | 197 /// All the loggers we have
198 loggers: Vec<Box<dyn Log + Send>>, field
272 let mut loggers: Vec<Box<dyn Log + Send>> = vec![]; in new() localVariable
299 loggers.push(Box::new(builder.build())); in new()
317 loggers.push(Box::new(builder.build())); in new()
327 loggers.push(logger); in new()
341 loggers, in new()
454 for logger in self.loggers.iter() { in log()
461 for logger in self.loggers.iter() { in flush()
|
| /external/oss-fuzz/projects/hugo/ |
| D | fuzz.go | 20 "github.com/gohugoio/hugo/common/loggers"
35 cs, _ := helpers.NewContentSpec(l, loggers.NewErrorLogger(), afero.NewMemMapFs())
|
| /external/nist-sip/java/gov/nist/core/ |
| D | StackLogger.java | 7 * interface that loggers should implement so that the stack can log to various
8 * loggers impl such as log4j, commons logging, sl4j, ...
|