capturing EWT events

100%

capturing EWT events

✓ Published0🌍 Public

Last edited Jan 28, 2016

Created on Jan 28, 2016

This example demonstrates how to capture Event Tracing for Windows (ETW) events in real time using a trace session. It creates a `TraceEventSession` and an `ETWTraceEventSource`, then attaches a `DynamicTraceEventParser` whose `All` handler prints every received event to the console. The code enables a specific provider by GUID before processing the session. It relies on the Microsoft.Diagnostics.Tracing.TraceEvent NuGet package to parse events dynamically, showing the basic plumbing for consuming ETW data without a pre-defined event schema.

AI-generated description

Similar vizzes

Loading thumbnail…

Gist 5001434

This example shows a debugging scenario for event sourcing, where two events with identical timestamps are replayed and returned in unpredictable order. The code displays two event objects—`UserCreatedEvent` and `UserCredentialsCreatedEvent`—with their UUIDs and aggregate root IDs, using JavaScript object literals. It illustrates the problem of sorting by `DateTime.Utc.Now` when fast-sequenced commands produce equal dates, leading to logical ordering failures. The example renders the raw event data and aggregates as plain text, relying on standard JavaScript syntax rather than any visualization library, focusing on the conceptual issue of timestamp collisions in EventStore queries.

RRestuta

50% match

Loading thumbnail…

Gist 93b658784fcafb1a5676

This example shows Azure Table Storage query results as a flattened, tabular dump of dynamic entities, displaying each row’s PartitionKey, RowKey, ETag, Timestamp, and all custom properties. The code uses the Azure Storage SDK’s `CloudTable` and `TableQuery<DynamicTableEntity>` to fetch data, then a custom `ToDynamicList` extension converts each entity into an `ExpandoObject`. It handles all `EdmType` property values—Binary, Boolean, DateTime, Double, Guid, Int32, Int64, and String—and fills missing properties with empty strings. The final output is rendered via LINQPad’s `Dump` method.

Aamithegde

49% match

Loading thumbnail…

Emacs Debugging Workshop

This visualization demonstrates the Emacs debugging workflow through a series of instrumented Lisp examples, showing how the built-in debugger and Edebug interact with source buffers, stack frames, and invocation messages. The buffer uses `lisp-interaction-mode` and defines key bindings for `eval-print-last-sexp`, while examples trigger `debug-on-variable-change`, `debug-on-message`, and `debug-on-error` to pause execution. The code also exercises Edebug’s stepping, tracing via `edebug-trace`, and conditional breaks through `edebug` calls, relying on standard Emacs Lisp functions like `(debug)`, `toggle-debug-on-quit`, and `with-output-to-temp-buffer` to produce backtraces and evaluation control. The source text itself serves as the data, with the rendering being the interactive debugging session.

DDarMontou

48% match

Loading thumbnail…

prototype for easy and declarative definition of Events that should be present in the EventStore during testing of something

This example shows a fluent C# API for declaratively defining expected events in an EventStore during testing. It uses a builder pattern with `InsertEventsTo(EventStore)` and chained `.AggregateId(...)` calls, mapping aggregate IDs to arrays of `FakeEvent` objects like `ContactCreated` and `TaskCreated`. The code highlights a readable, intention-revealing syntax for setting up test fixtures without explicit event construction logic.

RRestuta

48% match

Loading thumbnail…

intercept *.addEventListener for debugging

This example demonstrates how to intercept and log every `addEventListener` call on HTML element prototypes for debugging purposes. It enumerates all `HTML*` interfaces from `window`, then wraps each prototype’s `addEventListener` method to print the event type, listener, and `useCapture` flag, followed by a stack trace via `console.trace()`. The code uses native browser APIs like `Object.getOwnPropertyNames`, `window`, and prototype manipulation, with no external libraries, and is based on a Stack Overflow solution adapted for Firefox.

Aalessioalex

46% match

Loading thumbnail…

Gist 79280caf928b23ee59ac2acd56d84be6

This example converts a conference schedule exported from Excel into a localized timetable by manipulating the displayed time values. It shows how the original EDT-based event times are recalculated to reflect the viewer’s timezone, using the browser’s `Date` object and `getTimezoneOffset()` to compute the offset. The script targets specific spreadsheet cells via `document.querySelector` and replaces the “EDT” label with “CET,” while adjusting each event’s hour and minute through string parsing. No external visualization libraries are used; the approach relies purely on vanilla JavaScript DOM manipulation.

UUtopiah

44% match

Loading thumbnail…

Running a Trace Sync gpx file through togeojson

This example visualizes a GPS running trace by converting a GPX file to GeoJSON, then rendering the route as a line on a map. It shows a short, high-frequency recorded path with timestamps every 200 milliseconds, likely representing a brief burst of movement. The visualization relies on the `geojson` data structure, with the `coordTimes` property enabling time-based animation or styling. The work uses the togeojson library for conversion and can be rendered with mapping libraries like Leaflet or Mapbox GL JS to display the trace geographically.

DDylanFM

44% match

Loading thumbnail…

Gist 302c3f0062de516f2d53

This example demonstrates filtering Atom feed entries by category using a StAX parser. It reads an XML file and extracts the text content of `<title>` and `<category>` elements, printing only titles whose category contains “HTML.” The code relies on the `javax.xml.stream` API, specifically `XMLInputFactory`, `XMLEventReader`, and `XMLStreamConstants`, to iterate through events. It handles `START_ELEMENT` cases to capture element text via `parser.getElementText()`, while skipping other event types. The data source is a local file path (`webtec.atom.xml`), and error handling uses a try-catch block that outputs any exception message.

Aamirothman

44% match