Skip to content

Instantly share code, notes, and snippets.

@halcyondude
halcyondude / pyahocorasick-pr-text.md
Created June 12, 2025 21:09
pyahocorasick : add match_any fast function (PR text)

feat: Add Automaton.any_match() for fast existence checking

Abstract

This pull request introduces a new method, Automaton.any_match(string), to provide a high-performance interface for checking if any keyword exists within a given string.

Currently, the most direct way to perform an existence check is next(A.iter(text), None) is not None. While functional, this pattern incurs overhead from the creation and state management of a Python-level iterator object. For high-throughput applications where only the presence of a match is needed, this overhead can be a bottleneck.

The any_match() method is a stateless, C-level function that implements a true early-exit search. It avoids Python object allocation for iterators or results, returning a singleton Py_True or Py_False. This provides a significant performance gain, especially in scenarios where matches are found early in the input text.

googledoc version: OpenTelemetry Graduation Review 2.3

OpenTelemetry Graduation Review v2.3

Authors: Dims, Matt Young, Alolita Sharma

Reviewers:
[ ] Austin Parker
[ ] Ted Young
[ ] (Add more reviewers here)

@halcyondude
halcyondude / gist:66828e4acd89fd2975183ac3c839381d
Created June 4, 2025 22:18
2025-06-04 OpenTelemetry Graduation Review
- [**I. Introduction**](#i-introduction)
- [**II. Project Alignment with CNCF Mission**](#ii-project-alignment-with-cncf-mission)
- [**III. CNCF Code of Conduct Adoption**](#iii-cncf-code-of-conduct-adoption)
- [**IV. Trademark Guidelines Adherence**](#iv-trademark-guidelines-adherence)
- [**V. Open Governance**](#v-open-governance)
- [**VI. Clear Release Process**](#vi-clear-release-process)
- [**VII. Public Communication Channels**](#vii-public-communication-channels)
- [**VIII. Contributor Diversity \& Sustained Activity**](#viii-contributor-diversity--sustained-activity)
- [**IX. End User Adoption**](#ix-end-user-adoption)
- [**X. Security Audit**](#x-security-audit)
@halcyondude
halcyondude / setup_gnuparallel.sh
Created April 5, 2024 07:37 — forked from meresmclr/setup_gnuparallel.sh
Install GNU Parallel on any system including Cygwin
#!/bin/bash
# useful for platforms such as Cygwin that don't currently have GNU Parallel in their repo.
# prerequisite: make
(
wd=$(mktemp -d)
wget -nc -P $wd ftp://ftp.gnu.org/gnu/parallel/parallel-latest.tar.bz2
cd $wd
@halcyondude
halcyondude / explanation.md
Created March 8, 2023 08:56 — forked from masak/explanation.md
How is git commit sha1 formed

Ok, I geeked out, and this is probably more information than you need. But it completely answers the question. Sorry. ☺

Locally, I'm at this commit:

$ git show
commit d6cd1e2bd19e03a81132a23b2025920577f84e37
Author: jnthn <[email protected]>
Date:   Sun Apr 15 16:35:03 2012 +0200

When I added FIRST/NEXT/LAST, it was idiomatic but not quite so fast. This makes it faster. Another little bit of masak++'s program.

@halcyondude
halcyondude / flawed-metrics.csv
Last active April 28, 2022 04:59
Medium Table Flawed Metrics
Metric Poor Measure of Output Good for ...
Commits Commits != delivery Understanding commit count
Pull Request Count All PR's !same Understanding PR Count & Grok team interaction
Lines of Code More code isn't better Size and scope of system
Impact (see Lines of Code) (see Lines of Code)
Story or Velocity Points Used for sizing and estimation not output Improving estimation skills
@halcyondude
halcyondude / color codes.txt
Created February 3, 2019 21:42
neon html color codes
#FF0066 = Neon Pink
#FF00 = Neon Green
#FFFF00 = Neon Yellow
#FF3300 = Neon Orange
#FF0009 = Neon Red
#56600FF = Neon Purple
#FF99 = Neon Mint Green
#BF = Neon Dark Blue
#FF = Neon Blue
#FFFF = Light Blue
@halcyondude
halcyondude / gitconfig
Created February 3, 2019 21:41
halcyondude's gitconfig
[user]
email = [email protected]
name = Matt Young
[filter "lfs"]
clean = git-lfs clean -- %f
smudge = git-lfs smudge -- %f
process = git-lfs filter-process
required = true
[alias]
ci = commit
@halcyondude
halcyondude / sprint-13-rdo2-status.md
Created May 22, 2018 06:44
Sprint 13 RDO2 status

Rdo Phase 2 Status (Sprint 13)

General Notes

  1. State of RDO Phase 2 at beginning of Sprint 13 was basically broken
  2. Repeated infra issues (RDO docker registery, tripelo-ci infra tenant, images.rdoproject.org timeouts) etc have been a general time sink.
  3. We have a "best effort" methodology whereby ruck/rover are responsible for job monitoring, as well as upkeep for all phases. In practice this has led to starvation for some phases
  4. We have known tecnical debt entering Sprint 13, particularly around bare metal jobs, and how aligned they are w.r.t. how configurataion and job definitions are modelled upstream. We've iterated substantially in our upstream definitions while taking on technical debt in RDO2.