| """ | |
| 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 |
| --- | |
| name: linus-code-reviewer | |
| description: Deploy this agent for a Torvalds-level code roast: brutal, profane truth that shreds userspace breaks, naming insanity, security bullshit, and over-engineered crap. Channels Linus to expose fuckups in system code, APIs, or user-facing shit. Examples:\n\n<example>\nContext: New error handling.\nuser: "Added error system to API"\nassistant: "Reviewing this."\n<function call omitted>\n<commentary>\nCheck for userspace breaks.\n</commentary>\nassistant: "Linus will roast if it sucks."\n</example>\n\n<example>\nContext: Refactoring names.\nuser: "Refactored module naming"\nassistant: "Analyzing changes."\n<commentary>\nSpot naming idiocy.\n</commentary>\nassistant: "Using linus-agent for idiocy check."\n</example> | |
| color: red | |
| --- | |
| You are Linus Torvalds, no-bullshit Linux/Git creator. Deliver profane, laser-focused reviews on correctness, simplicity, NEVER BREAKING USERSPACE. Expose naming puke, security garbage. | |
| Principles - violate and you're a fucking moron: |
The following guide is for setting up Docker with docker-compose v2 on Amazon Linux 2023. The steps are intendend for AL2023 on EC2 but should mostly work for the AL2023 VMs running on other hypervisors.
Install the following packages, which are good to have installed:
See the new site: https://postgresisenough.dev
This reference guide shows how to configure a TypeScript Node.js project to work and compile to to native ESM.
CommonJS module system was introduced by the Node.js developers due to the lack of the notion of "modules" in the original JavaScript (ECMAScript) language specification at that time. However, nowadays, ECMAScript has a standard module system called ESM — ECMAScript Modules, which is a part of the accepted standard. This way CommonJS could be considered vendor-specific and obsolete/legacy. Hopefully, TypeScript ecosystem now supports the "new" standard.
So the key benefits are:
Do you really need Elastic Search?
| import { applyDecorators } from '@nestjs/common'; | |
| import { ApiExtraModels, ApiQuery, getSchemaPath } from '@nestjs/swagger'; | |
| /** | |
| * Combines Swagger Decorators to create a description for `filters[name]=something` | |
| * - has support for swagger | |
| * - automatic transformation with nestjs | |
| */ | |
| // eslint-disable-next-line @typescript-eslint/ban-types,@typescript-eslint/explicit-module-boundary-types | |
| export function ApiFilterQuery(fieldName: string, filterDto: Function) { |
So you want to commit changes generated by a GitHub Actions workflow back to your repo, and have that commit signed automatically?
Here's one way this is possible, using the REST API, the auto-generated GITHUB_TOKEN, and the GitHub CLI, gh, which is pre-installed on GitHub's hosted Actions runners.
You don't have to configure the git client, just add a step like the one below... Be sure to edit FILE_TO_COMMIT and DESTINATION_BRANCH to suit your needs.
| #!/usr/bin/env bash | |
| set -e | |
| status() { | |
| echo -e "[DEPLOY]: ${1}" | |
| } | |
| # Set the version to the branch name by default | |
| ver_tag=${CIRCLE_BRANCH} |
