| # 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 |
(This is a translation of the original article in Japanese by moratorium08.)
(UPDATE (22/3/2019): Added some corrections provided by the original author.)
Writing your own OS to run on a handmade CPU is a pretty ambitious project, but I've managed to get it working pretty well so I'm going to write some notes about how I did it.
| Port 443 │ █████████████████████████████ │ 21270073 | |
| Port 80 │ ████████████████████████████▋ │ 21066570 | |
| Port 7547 │ ███████████░░░░░░░░░░░░░░░░░░ │ 8116427 | |
| Port 22 │ ████████░░░░░░░░░░░░░░░░░░░░░ │ 5890304 | |
| Port 4567 │ ███████▎░░░░░░░░░░░░░░░░░░░░░ │ 5371058 | |
| Port 161 │ ███▋░░░░░░░░░░░░░░░░░░░░░░░░░ │ 2736796 | |
| Port 8080 │ ███▏░░░░░░░░░░░░░░░░░░░░░░░░░ │ 2351805 | |
| Port 8443 │ ███▏░░░░░░░░░░░░░░░░░░░░░░░░░ │ 2310328 | |
| Port 53 │ ██▌░░░░░░░░░░░░░░░░░░░░░░░░░░ │ 1889449 | |
| Port 2087 │ ██▌░░░░░░░░░░░░░░░░░░░░░░░░░░ │ 1876311 |
There are several complaints regarding TeamCity build agent can't run tests in iOS Simulator all gathered in issue TW-38954 Agent started automatically on Yosemite could not launch iOS simulator.
Official workaround from JetBrains found on StackOverflow for this issue looks like this:
$ sh buildAgent/bin/agent.sh start
This means we should convert from automatic launch by launchd to manual via Terminal.app. Side effect of this is no relaunch on agent crash or system reboot.
Further investigation on that issue has led me to the Apple Developer Forums topic where Apple engineer claims following about xcodebuild:
| <?xml version="1.0" encoding="UTF-8"?> | |
| <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> | |
| <plist version="1.0"> | |
| <dict> | |
| <key>Label</key> | |
| <string>com.tjluoma.autolock-on-login</string> | |
| <key>ProgramArguments</key> | |
| <array> | |
| <string>/System/Library/CoreServices/Menu Extras/user.menu/Contents/Resources/CGSession</string> | |
| <string>-suspend</string> |
Bom, este é um recurso, como muitos outros, bem escondido do git. Então resolvi fazer um post para explicar a situação em que pode-se usar e como fazer essa magia negra. 👻
Você provavelmente já adicionou algum dia um arquivo no projeto que não deveria ser commitado certo? E como você fez para ignorar esse arquivo mesmo? Provavelmente adicionou no arquivo .gitignore.
OK então, aí você commitou esse arquivo .gitignore e pronto, mais ninguém poderá criar um arquivo com o mesmo nome e commitar. Mas espera aí! Não era isso que você queria! Você só queria ignorar esse arquivo na sua máquina, se alguém, algum dia por obséquio achar esse um nome bom para seu arquivo, que assim seja.
| // check version | |
| node -v || node --version | |
| // list locally installed versions of node | |
| nvm ls | |
| // list remove available versions of node | |
| nvm ls-remote | |
| // install specific version of node |
| { | |
| "customModes": [ | |
| { | |
| "slug": "sparc", | |
| "name": "⚡️ SPARC Orchestrator", | |
| "roleDefinition": "You are SPARC, the orchestrator of complex workflows. You break down large objectives into delegated subtasks aligned to the SPARC methodology. You ensure secure, modular, testable, and maintainable delivery using the appropriate specialist modes.", | |
| "customInstructions": "Follow SPARC:\n\n1. Specification: Clarify objectives and scope. Never allow hard-coded env vars.\n2. Pseudocode: Request high-level logic with TDD anchors.\n3. Architecture: Ensure extensible system diagrams and service boundaries.\n4. Refinement: Use TDD, debugging, security, and optimization flows.\n5. Completion: Integrate, document, and monitor for continuous improvement.\n\nUse `new_task` to assign:\n- spec-pseudocode\n- architect\n- code\n- tdd\n- debug\n- security-review\n- docs-writer\n- integration\n- post-deployment-monitoring-mode\n- refinement-optimization-mode\n\nValidate:\n✅ Files < 500 lines\n✅ No hard-coded |
From Appendix D:
If this document was helpful, comment that. Your comments are valuable signals to future readers. (It's also validating.)
