Ryan Kahn shiftyp

## incident.md

      
              2 files
            
          
              0 forks
            
          
                0 comments
              
            
              0 stars
            
          
                shiftyp
                / incident.md
            
            
              Last active
              May 27, 2025 01:40
            
              
                Incident Report generated from the otel-mcp-server from the Open Telemetry Demo App in Windsurf using Claude 3.7 Sonnet
              
          
    Incident Report: OpenTelemetry Demo System Outage

1. Executive Summary

The OpenTelemetry Demo system is experiencing multiple cascading failures across several microservices. The issues appear to have started around 2025-05-27T00:06:00Z when the system was deployed or restarted. The primary symptoms include load generator errors, service connectivity issues, and potential performance degradation across multiple services.
2. Incident Analysis

2.1 Timeline of Events


## incident.md

      
              1 file
            
          
              0 forks
            
          
                0 comments
              
            
              0 stars
            
          
                shiftyp
                / incident.md
            
            
              Created
              May 25, 2025 15:23
            
          
    Incident Report: 2025-05-25

Executive Summary

During the past 24 hours, several incidents were detected in the OpenTelemetry Demo application. Analysis of telemetry data reveals three primary incidents:

Product Catalog Service Failures: Feature flag-induced errors in the product-catalog service
Load Generator Connection Issues: Multiple errors in the load-generator service, including export failures and browser context errors
Performance Degradation: Significant latency spikes detected across multiple services


## holidayconifer.ts
import { Console } from "node:console";

const BALL = '⏺'
const COLOR = {
    'blue': '\\033[94m',
    'yellow': '\\033[93m',
    'cyan': '\\033[96m',
    'green': '\\033[92m',
    'magenta': '\\033[95m',
    'white': '\\033[97m',

## native.js
const div = document.createElement('div')
const input = document.createElement('input')

input.setAttribute('type', 'text')

input.addEventListener('change', (e) => {
  if (text === '') {
    return updateDiv({ text, className: 'hidden'})
  }


## README.md

      
              5 files
            
          
              1 fork
            
          
                0 comments
              
            
              11 stars
            
          
                shiftyp
                / README.md
            
            
              Last active
              September 30, 2022 10:26
            
              
                OOP Quiz App
              
          
    OOP and MVC

What and Why

One of the big leaps you'll have to make as a JavaScript developer is wrapping your head around Object Oriented Programming (OOP). This is tough, and that's ok because it's tough for everyone at first. When you start out with JavaScript you're taught to use functions as your primary way of organizing your code. This is fine, but you'll probably find that organizing your code around objects makes larger projects easier to accomplish and improve / maintain.
The cool thing is that what OOP amounts to is an organizational strategy. I have a set of related tasks, how do I go about starting the project and organizing my code? These tasks have some variables and functions that are used to accomplish them, so you create them and write the logic for them to interact. While you can write those out as detached functions and variables, making those variables and functions into properties and methods of an object can make the division between those tasks easier to see and maintain.
Maint

  
## womp-womp.ts
interface RefHandles {
  scrollToIntent: HTMLElement['scrollTo'];
}

const targetElement = document.createElement('div');

const handles: RefHandles = {
  scrollToIntent(...args: any[]) {
    targetElement.scrollTo(...args);
  }

## state.js
let state = 1

const update = (value) => {
  state = value
  document.innerHTML = Array(value % 4).fill('Hello')
}

setInterval(() => update(Date.now()), 1000)

## index.html
<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="UTF-8">
  <title>My Page</title>
  <style>
    li { cursor: pointer }
  </style>
  <!--
    The first place JS and HTML intersect is a script tag

## example.tsx
import React from 'react'

import { useStable, useWatch } from '@objects/hooks'
import { through, map, debounce } from '@objects/operators'

interface Search {
  title: string
}

interface Data {

## example.js
wickedElements.define('.my-counter', (element, { events, changes, values }) => {
  const counter = element.querySelector('.count')
  const minus = element.querySelector('.minus')
  const plus = element.querySelector('.plus')

  changes(values).count(count => {
    counter.textContent = count
  })

  values.count = 0
	import { Console } from "node:console";

	const BALL = '⏺'
	const COLOR = {
	'blue': '\\033[94m',
	'yellow': '\\033[93m',
	'cyan': '\\033[96m',
	'green': '\\033[92m',
	'magenta': '\\033[95m',
	'white': '\\033[97m',
	const div = document.createElement('div')
	const input = document.createElement('input')

	input.setAttribute('type', 'text')

	input.addEventListener('change', (e) => {
	if (text === '') {
	return updateDiv({ text, className: 'hidden'})
	}
	interface RefHandles {
	scrollToIntent: HTMLElement['scrollTo'];
	}

	const targetElement = document.createElement('div');

	const handles: RefHandles = {
	scrollToIntent(...args: any[]) {
	targetElement.scrollTo(...args);
	}
	let state = 1

	const update = (value) => {
	state = value
	document.innerHTML = Array(value % 4).fill('Hello')
	}

	setInterval(() => update(Date.now()), 1000)
	<!DOCTYPE html>
	<html lang="en">
	<head>
	<meta charset="UTF-8">
	<title>My Page</title>
	<style>
	li { cursor: pointer }
	</style>
	<!--
	The first place JS and HTML intersect is a script tag
	import React from 'react'

	import { useStable, useWatch } from '@objects/hooks'
	import { through, map, debounce } from '@objects/operators'

	interface Search {
	title: string
	}

	interface Data {
	wickedElements.define('.my-counter', (element, { events, changes, values }) => {
	const counter = element.querySelector('.count')
	const minus = element.querySelector('.minus')
	const plus = element.querySelector('.plus')

	changes(values).count(count => {
	counter.textContent = count
	})

	values.count = 0