| # train_grpo.py | |
| # | |
| # See https://github.com/willccbb/verifiers for ongoing developments | |
| # | |
| import re | |
| import torch | |
| from datasets import load_dataset, Dataset | |
| from transformers import AutoTokenizer, AutoModelForCausalLM | |
| from peft import LoraConfig | |
| from trl import GRPOConfig, GRPOTrainer |
The screenshots were taken on different sessions.
The entire sessions are included on the screenshots.
I lost the original prompts, so I had to reconstruct them, and still managed to reproduce.
The "compressed" version is actually longer! Emojis and abbreviations use more tokens than common words.
| # shellcheck disable=all | |
| # PATH | |
| # export CODE="${VSCODE_GIT_ASKPASS_NODE%/*}/bin/remote-cli" | |
| # export PATH="$CODE:$HOME/.asdf/shims:$PATH" | |
| # check if binary exists | |
| check_bin() { command -v "$1" >/dev/null 2>&1; } | |
| # aliases |
It happens that there are many standards for storing cryptography materials (key, certificate, ...) and it isn't always obvious to know which standard is used by just looking at file name extension or file content. There are bunch of questions on stackoverflow asking about how to convert from PEM to PKCS#8 or PKCS#12, while many tried to answer the questions, those answers may not help because the correct answer depends on the content inside the PEM file. That is, a PEM file can contain many different things, such as an X509 certificate, a PKCS#1 or PKCS#8 private key. The worst-case scenario is that someone just store a non-PEM content in "something.pem" file.
| { | |
| "name": "Discord RTC Regions", | |
| "description": "allowlist for all Discord voice regions", | |
| "rules": [ | |
| { | |
| "action": "allow", | |
| "process": "/Applications/Discord.app/Contents/MacOS/Discord", | |
| "remote-addresses": "5.200.3.71,5.200.3.100,5.200.3.119,5.200.6.179,5.200.14.132,5.200.14.138,5.200.14.172,5.200.14.186,5.200.14.196,5.200.14.231,5.200.14.243,31.204.133.6,31.204.133.9,31.204.133.14,31.204.133.16,31.204.133.22,31.204.133.27,31.204.133.30,31.204.133.31,31.204.133.37,31.204.133.43,31.204.133.44,31.204.133.48,31.204.133.49,31.204.133.52,31.204.133.58,31.204.133.74,31.204.133.76,31.204.133.80,31.204.133.81,31.204.133.82,31.204.133.87,31.204.133.95,31.204.133.97,31.204.133.101,31.204.133.102,31.204.133.103,31.204.133.104,31.204.133.105,31.204.134.11,31.204.134.16,31.204.134.19,31.204.134.26,31.204.134.28,31.204.134.30,31.204.134.32,31.204.134.34,31.204.134.36,31.204.134.40,31.204.134.50,31.204.134.54,31.204.134.58,31.204.134.61,31.204.134.63,31.204.134.64,31.204.134.69,31.204.134.72,31.2 |
| # code to load the JWT token in PowerShell | |
| # Call teh Get-JWTToken method with the App ID and the App Private Key (normal string from env var or file contents, make sure there is no extra line ending at the end of it!). | |
| function Build-Payload { | |
| Param ( | |
| [string] $app_id | |
| ) | |
| $iat = [Math]::Floor([decimal](Get-Date(Get-Date) -UFormat %s)) | |
| $payload = @{ | |
| "iat" = [int]$iat # issues at = now |
| name: Create diff on updated HelmReleases | |
| on: | |
| pull_request: | |
| branches: | |
| - master | |
| paths: | |
| - "clusters/**.yaml" | |
| env: |
| # !!! IMPORTANT | |
| # Must point to the correct director or this entire script breaks | |
| eval $(/opt/homebrew/bin/brew shellenv) | |
| # The next line updates PATH for the Google Cloud SDK. | |
| if [ -f '/usr/local/google-cloud-sdk/path.bash.inc' ]; then . '/usr/local/google-cloud-sdk/path.bash.inc'; fi | |
| # The next line enables shell command completion for gcloud. | |
| if [ -f '/usr/local/google-cloud-sdk/completion.bash.inc' ]; then . '/usr/local/google-cloud-sdk/completion.bash.inc'; fi |