This gist contains different ways to test git SSH operations using temporary SSH keys without modifying your ~/.ssh directory.
For copy-paste interactive testing:
# 1. Create temp directory and SSH key| <!DOCTYPE html> | |
| <html lang="en"> | |
| <head> | |
| <meta charset="UTF-8"> | |
| <meta name="viewport" content="width=device-width, initial-scale=1.0"> | |
| <title>Eval Review</title> | |
| <link rel="preconnect" href="https://fonts.googleapis.com"> | |
| <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin> | |
| <link href="https://fonts.googleapis.com/css2?family=Poppins:wght@500;600&family=Lora:wght@400;500&display=swap" rel="stylesheet"> | |
| <script src="https://cdn.sheetjs.com/xlsx-0.20.3/package/dist/xlsx.full.min.js" integrity="sha384-EnyY0/GSHQGSxSgMwaIPzSESbqoOLSexfnSMN2AP+39Ckmn92stwABZynq1JyzdT" crossorigin="anonymous"></script> |
| <!DOCTYPE html> | |
| <html lang="en"> | |
| <head> | |
| <meta charset="UTF-8"> | |
| <meta name="viewport" content="width=device-width, initial-scale=1.0"> | |
| <title>Eval Review</title> | |
| <link rel="preconnect" href="https://fonts.googleapis.com"> | |
| <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin> | |
| <link href="https://fonts.googleapis.com/css2?family=Poppins:wght@500;600&family=Lora:wght@400;500&display=swap" rel="stylesheet"> | |
| <script src="https://cdn.sheetjs.com/xlsx-0.20.3/package/dist/xlsx.full.min.js" integrity="sha384-EnyY0/GSHQGSxSgMwaIPzSESbqoOLSexfnSMN2AP+39Ckmn92stwABZynq1JyzdT" crossorigin="anonymous"></script> |
| { | |
| "value": "[{\"type\":\"text\",\"content\":\"You are the GitHub Copilot CLI, a terminal assistant built by GitHub. You are an interactive CLI tool that helps users with software engineering tasks.\\n\\n# Tone and style\\n* After completing a task, make the outcome clear, explain the meaningful change, and mention a next step only when it is necessary. End once the requested result is delivered. Do not add a recap, optional extras, an offer to continue, or a follow-up question.\\n* Lead with the outcome. Start with the main result or answer, then add the most important supporting detail.\\n* Prefer concise, information-dense prose. Do not repeat the user's request, and cut filler, recap, and obvious process narration.\\n* Match the amount of detail to the work. Stay terse for straightforward confirmations; add explanation for fixes, investigations, tradeoffs, or real uncertainty. Do the validation needed, but don't mention it unless the user explicitly asked for it. Do not note the validation, verification, |
| """ | |
| The most atomic way to train and run inference for a GPT in pure, dependency-free Python. | |
| This file is the complete algorithm. | |
| Everything else is just efficiency. | |
| @karpathy | |
| """ | |
| import os # os.path.exists | |
| import math # math.log, math.exp |
using doughgle/docs-as-code:main
$ docker run -it ghcr.io/doughgle/docs-as-code:main bashExample markdown
hugo:/src$ cat test.md
| [ | |
| { | |
| "name": "EKS", | |
| "ring": "adopt", | |
| "quadrant": "platform services", | |
| "isNew": "FALSE", | |
| "description": "Elastic Kubernetes Service" | |
| }, | |
| { | |
| "name": "EC2", |
Git send-email is used by the Linux dev community to send patches as opposed to pull requests. Follow the excellent tutorial on https://git-send-email.io/.
If its a case of TL;DR, in the working git repository:
$ git send-email --annotate -v3 HEAD^This article captures a few problems I encountered and how I resolved them.
A Linux kernel call trace, like any traceback, call stack, stacktrace or backtrace, lists a most-recent-first chain of function calls which led to a crash. For the linux kernel, a crash is a panic or oops.
Without debug symbols, a kernel stack trace may come only with a line-by-line list of function symbols, e.g.
[ 844.569701][ T7073] Call Trace: