Skip to content

Instantly share code, notes, and snippets.

enum Interface {
CW20,
}
# (see: https://github.com/CosmWasm/wasmd/blob/v0.27.0/x/wasm/types/types.pb.go#L39)
enum AccessType {
// AccessTypeUnspecified placeholder for empty value
Unspecified
// AccessTypeNobody forbidden
AccessTypeNobody AccessType = 1
# WARN [handleDelegateWithdrawRewardEvent] (!SKIPPED!) no claim msgs found in tx: BCB1B0915F...
query investigation {
allClaims: distDelegatorClaims {
totalCount
}
txClaims: distDelegatorClaims (filter: {transactionId: {startsWith: "BCB1B9815F"}}) {
totalCount
nodes {
validatorAddress
@bryanchriswhite
bryanchriswhite / README.md
Last active May 22, 2023 06:04
chatGPT assisted log analysis

Background

While debugging, after refactoring some tests and test helpers, I found myself struggling to make use of the debug log output that I was adding as it can easily get lost in the structured logging and myriad other debug log lines which print in the context of integration tests.

Summary

The threshold for writing a script to solve a one-off problem like this might typically be measured in a large number of hours or perhaps even day(s) for me. Using LLMs to generate and test such a script can greatly reduce the time and directed attention required to get to making use of your scirpt to solve your actual problem (rather than debugging it). So much so, that I would argue that it's worth reconsidering that threshold to prefer giving LLMs a shot much earlier than one otherwise may.

@bryanchriswhite
bryanchriswhite / README.md
Last active June 8, 2023 01:22
libp2p PubSub debugging / tracing

Background

While pursuing minimal background gossip support I've encountered a need more observability into the state of the network as it evolves.

Fortunately go-libp2p-pubsub includes support for tracing. example_trace.json is the result of using a JSONTracer in a background gossip broadcast integration test.

The Problem

By default, the library encodes the PeerIDs in these traces using base64 (as seen in example_trace.json).

itest

Purpose

Ensuring critical tests against flakiness with a faster feedback loop and easier developer experience.

  • Avoiding the uncertainty about the health of long-running tests which have no output
  • Automate the tedium of running smaller batches

Usage

gitGraph
    commit
    commit
    branch FeatureA
    commit
    commit
    branch FeatureAB
    commit id: "AB1"
 commit id: "AB2"