Tags

Tags give the ability to mark specific points in history as being important
  • v0.3.2

    procscope v0.3.2 — fix the log-searching cross-reference
    
    The section pointed at slog-configurator and slogconfigurator.AddHandler. The
    module is now slogging and the function is slogconf.AddSink; the old snippet
    could not compile. Heading renamed to disclaim ownership, and the repository
    description no longer advertises log searching this library does not do.
    
    No library code changed.
  • v0.3.1

    procscope v0.3.1 — imported-by badge, refreshed weekly
    
    CI only; the library is unchanged. The README gains a count of importing
    packages linking to the repositories behind it.
    
    Blast radius, not adoption: the number is what tells you how much breaks when an
    exported name moves.
    
    It reads 'unknown' until pkg.go.dev crawls this module — 'nothing imports this'
    and 'I could not tell' are different facts, and only one of them is worth
    rendering as a zero.
  • v0.3.0

    procscope v0.3.0 — typed Options
    
    Capture(kind string, debug int, seconds int) becomes Capture(Options), with
    every axis a named type: Kind, Format, Detail, and Window as a time.Duration.
    
    The debug integer is gone from the API. It conflated format with verbosity --
    0 meant protobuf, higher meant text AND a detail level -- so it is now Format
    plus Detail, and the pprof integer stays internal.
    
    An unrecognised Kind/Format/Detail is now an error rather than a silent
    fallback to heap, and FormatText is refused for cpu and trace, which have no
    text form.
    
    The package moves to the repo root: procscope.Capture(...).
  • v0.2.1

    procscope v0.2.1 — repo plumbing
    
    Mirroring to GitLab and Codeberg on every push, archiving to the Wayback
    Machine / Software Heritage / archive.org for tags and the default branch,
    issue pull-back from both mirrors every six hours, and collaborators-only pull
    requests. Cron minutes staggered against the sibling repos.
    
    pre-commit.sh runs make lint && make test-coverage.
    
    No library code changed. The README's logring example is updated for
    slog-configurator v1.4.0, where Search returns a Page.
  • v0.2.0

    procscope v0.2.0 — logsearch removed
    
    logring.Handler in slog-configurator already is the slog.Handler and already
    exposes Search / Count / Tail / Clear / Stats, so logsearch was wrapping a type
    that needed no wrapper. Its filter type was already an alias of the ring's own,
    so no query capability is lost.
    
    Migration: logring.New(...) -> AddHandler(ring) -> ring.Search(...). The
    extras logsearch added (page clamp, line truncation, count-before-paging)
    belong on the ring and are not yet upstream; clamp and truncate at the call
    site until they are.
    
    The slog-configurator dependency goes with it. procscope now depends on
    common-go and ctxerrors alone.
    
    Also: pprofcapture gains a full README with runnable programs, and the root
    README's log example -- which was missing its imports entirely -- is fixed.
  • v0.1.0

    procscope v0.1.0 — first release
    
    A Go process can profile itself and search its own logs, returning the answer
    as a value rather than serving it on a port -- which is the one thing you
    cannot reach when you most need it.
    
    pprofcapture: eight profile kinds, protobuf or text. Block and mutex profiling
    arm themselves for a bounded window and restore the process-global knobs
    exactly, including the case where another caller already enabled them.
    
    logsearch: searches the slog-configurator ring by structured attribute rather
    than by substring, so it works in JSON or text and finds attributes bound
    upstream via With. Counts matches before paging, bounds the page, and truncates
    a pathological line on a rune boundary.
    
    No transport, no Prometheus, no MCP SDK. Nothing enabled at rest.