profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/jaymcgrath/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.
Jay McGrath jaymcgrath Portland, OR

jaymcgrath/ewe_ebooks 4

A django based web application for creating, configuring, and managing Twitter mashup bots.

jaymcgrath/flutter 1

Django based twitter clone

jaymcgrath/housing-17 1

Hack Oregon Housing Project, 2016-2017

jaymcgrath/runbooks 1

Collection of runbooks for accomplishing various things I will probably forget

jaymcgrath/5calls 0

Frontend for the 5calls.org site

jaymcgrath/area4 0

🚀 Dividers in Python, the easy way! (As seen on PyPI)

jaymcgrath/Beginners-Python-Examples 0

Basic Python CLI programs

jaymcgrath/celery 0

Distributed Task Queue (development branch)

jaymcgrath/challenges 0

PyBites Code Challenges

startedfoambubble/foam

started time in a day

startedmanna-harbour/qmk_firmware

started time in 2 days

startedCirclesUBI/circles-contracts

started time in 3 days

startedGokuMohandas/MadeWithML

started time in 15 days

startedheruka-urgyen/react-playing-cards

started time in 2 months

startedlistingslab/react-playing-cards

started time in 2 months

startedMonadical-SAS/oddslingers.poker

started time in 2 months

startedChia-Network/chia-blockchain

started time in 2 months

startedstephane-monnot/react-vertical-timeline

started time in 2 months

push eventjaymcgrath/runbooks

Jay McGrath

commit sha 13f05ca80fbf46e21f2c2c3d398d81266d8f5ece

add wsl pyenv setup

view details

push time in 2 months

push eventjaymcgrath/runbooks

Jay McGrath

commit sha 6f896a2c75e014a5309dc2cf8c84047f34abadfa

add wsl pyenv setup

view details

push time in 2 months

fork jaymcgrath/pptparser

Parse ProPokerTools style Pot-Limit Omaha hand range syntax

fork in 2 months

startedtredfern0/pptparser

started time in 2 months

startedtansey/pycfr

started time in 2 months

startedakmhmgc/range-converter

started time in 2 months

startedbrianstrauch/spotify-cli

started time in 2 months

push eventjaymcgrath/docs-website

Jay McGrath

commit sha c0d1796ef5179f03fec065d96bf074db62a5b381

Update create-nrql-alert-conditions.mdx

view details

push time in 3 months

PR opened newrelic/docs-website

Clarify violation close for LoS violations

<!-- Thanks for contributing to our docs! -->

<!-- For Japanese readers: もしドキュメントの日本語訳で問題を見つけた場合はPRではなくissueを提出してください。 日本語訳へのPRについてはまだ取り込む準備ができていません。-->

Give us some context

As an engineer working in the platform, I was unsure what conditions needed to be met for a loss of signal violation to automatically close. Does the signal need to resume and maintain across the chosen expiration window? Does it immediately resume once it's detected? I tested this with a synthetics monitor and the violation closed immediately once a new data point was detected. Hopefully this can help our customers who have similar questions.

Are you making a change to site code?

No! 😅

+1 -1

0 comment

1 changed file

pr created time in 3 months

push eventjaymcgrath/docs-website

Jay McGrath

commit sha c18fab4be16e8bfc0884bbc22555c82d6b65ca67

Clarify violation close for LoS violations As an engineer working in the platform, I was unsure what conditions needed to be met for a loss of signal violation to automatically close. Does the signal need to resume and maintain across the chosen expiration window? Does it immediately resume once it's detected? I tested this with a synthetics monitor and the violation closed immediately once a new data point was detected. Hopefully this can help our customers who have similar questions.

view details

push time in 3 months

startedDimaKudosh/pydfs-lineup-optimizer

started time in 3 months

startedvramework/schemats

started time in 3 months