o
emergency-poncho
o | emergency-poncho | |
---|---|---|
1 | 2 | |
1 | 10 | |
- | - | |
10.0 | 0.0 | |
almost 7 years ago | over 1 year ago | |
Shell | JavaScript | |
- | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
o
-
Ask HN: Small scripts, hacks and automations you're proud of?
my favorite is a little command line helper called “o”. it’s a helper for copy and rename commands. If I want to edit a misspelled filename I can just type
o mv mispelled.txt
and it will make an interactive prompt that looks like:
mv mispelled.txt mispelled.txt_
but the last word is editable, so I can use the arrow keys to alter it in place
https://github.com/jes5199/o
emergency-poncho
-
Ask HN: Small scripts, hacks and automations you're proud of?
I've created a tool for replaying HTTP archives:
https://github.com/Tade0/emergency-poncho
There are many like it, but this one is mine.
Useful when you're a front-end developer and the backend app is not easily deployable locally and the test environment is down.
Also with it you can make a blazing-fast, browsable snapshot of JIRA.
-
Ask HN: Show me your Half Baked project
https://github.com/Tade0/emergency-poncho
This is a HTTP mock server for reproducing issues on the front-end using a recorded HTTP archive(.har file).
The gimmick is that for a given endpoint it stores all the responses and serves them in a round-robin sequence.
This way you can simulate situations where e.g. a request has been retried after the JWT expired, or something special happens when an item is added to a list, and the list is refreshed afterwards - basically every case in which you need backend state.
It works... sometimes. Each new project I'm in uncovers new issues.
That being said with the test team giving me both videos and .har files of the bug reproduction I was able to solve a few long standing bugs in one legacy system.
What are some alternatives?
semanticText - Copy paste tool that analyzes the semantic description of all text in the DOM
BotServer - LLM Orchestrator powered by langchain and Bot Framework V4 & several features including Whatsapp.
gpt-emacs-macro - Connect GPT-3 to Emacs and run "semantic" kbd macros
diarycli - diaryman.sh as pip package
work-cli - Awesome command line tools for managing the lifecycle of Github pull requests.
headless-ida - Run IDA scripts headlessly.
validator - Nu Html Checker – Helps you catch problems in your HTML/CSS/SVG
pyodide - Pyodide is a Python distribution for the browser and Node.js based on WebAssembly
observable-state-tree - An observable state tree is a normal object except that listeners can be bound to any subtree of the state tree.
zettelkasten - Creating notes with the zettelkasten note taking method and storing all notes on github
Kiilogger - C# based keylogger for general purpose keyboard logging and computer usage debugging :stuck_out_tongue: