vergenzt

type JsonVal = bool | int | float | str | None | dict[str, JsonVal] | list[JsonVal]


def escape_jinja_in_leaf_strs(val: JsonVal) -> JsonVal:
    """
    Escape Jinja template markers in leaf strings.

    Assuming that any strings at leaf nodes of the given JSON object, sanitize them so that:
    (a) Jinja processing doesn't fail, and
    (b) the result after such processing is equivalent to the input `val`.

vergenzt

#!/usr/bin/env python
"""
Manage databricks dashboards with dbt exposure metadata; sync changes up or down.
"""

from functools import cached_property, lru_cache
import json
from argparse import ArgumentParser, RawDescriptionHelpFormatter
from dataclasses import dataclass
from enum import Enum

vergenzt

// ==UserScript==
// @name        Abbreviate "Product Backlog Item" -> "PBI"
// @match       https://dev.azure.com/*
// ==/UserScript==

window.addEventListener("load", () => {
  document.title = document.title.replace("Product Backlog Item", "PBI");
});

vergenzt

#!/usr/bin/env python3
import ast
import os
import sys
from argparse import ArgumentParser, FileType
from collections import defaultdict
from configparser import ConfigParser
from graphlib import TopologicalSorter
from subprocess import check_call, check_output
from typing import Any, Iterable, Iterator, Tuple

vergenzt

#!/usr/bin/env python3
import ast
import os
import sys
from collections import defaultdict
from graphlib import TopologicalSorter
from pathlib import Path
from subprocess import check_call, check_output
from typing import Any, Iterable, Iterator, Tuple, Union

vergenzt

#!/usr/bin/env pip-run
"""
Parse Python requirements files into AST JSON representation
"""

# /// script
# dependencies = ['tree-sitter-requirements']
# ///

import json

vergenzt

If you have a command line that can generate a result, and you want to test whether successive results are statistically indepenent of each other, you can use the following:

seq <N_TESTS> \
| parallel -n0 <COMMAND...> \
| uniq -c \
| awk '{ NR%2 ? n1+=$1 : n2+=$1 } END { print NR, n1, n2 }' \
| python -c 'from statistics import NormalDist as N; import math; n_runs, n1, n2 = map(int, input().split()); n = n1+n2; μ=1.0*(2*n1*n2)/n + 1; σ=math.sqrt(1.0*(μ-1)*(μ-2)/(n-1)); Z = (n_runs-μ)/σ; p = N().cdf(-abs(Z)); p_two_tailed = p*2; print(); print(*list(vars().items())[-9:], sep="\n")'

vergenzt

Previous discussion elsewhere on Github

Comments by me

jpadilla/pyjwt#814 (comment):

Y'all this was litigated previously at #190. The JWT spec does NOT say to reject tokens with iat ("issued at") in the future, so this behavior goes beyond the spec and is inconsistent with many other JWT libraries.

4.1.6. "iat" (Issued At) Claim The "iat" (issued at) claim identifies the time at which the JWT was

vergenzt

--rpl '{[(.*?)]} $Global::use{"IPC::Open2"} ||= eval "use IPC::Open2; 1;"; my $jq = open2(my $jq_out, my $jq_in, "jq", "-Rrc", "[ try(fromjson) // . | $$1 | tostring | \@sh] | join(\" \")") or die "Could not open pipe to jq!"; print $jq_in $_; close $jq_in; $_ = <$jq_out>; chomp $_; uq(); waitpid $jq, 0; $? && die'

vergenzt

!include _header.puml

group #lightblue "Parse phase"
  
  dbt -> project ++: //read all yaml and SQL files//
  return
  rnote right of dbt #white: Evalute config
  rnote right of dbt #white
    Evalute ""generate_schema_name""
    on all nodes to determine