Remove async_task_outputs from repo (accidentally committed)
The previous commit pulled in 51 transient async-task-output markdown files from the local workspace's reviewer.py runs. Drop them and add the directory to .gitignore so it cannot recur.
This commit is contained in:
parent
29a6bde4d1
commit
5cb5eb7446
52 changed files with 1 additions and 52 deletions
1
.gitignore
vendored
1
.gitignore
vendored
|
|
@ -235,3 +235,4 @@ package-lock.json
|
|||
!studio/backend/core/data_recipe/oxc-validator/package-lock.json
|
||||
!studio/package-lock.json
|
||||
llama.cpp/
|
||||
async_task_outputs/
|
||||
|
|
|
|||
|
|
@ -1 +0,0 @@
|
|||
- Docker GPU-free build rationale done
|
||||
|
|
@ -1 +0,0 @@
|
|||
- Docker ok; run `bash docker/test_locally.sh --skip-notebook`
|
||||
|
|
@ -1 +0,0 @@
|
|||
- PR `#5748` pushed commit `58693c4c`
|
||||
|
|
@ -1 +0,0 @@
|
|||
- `externally-managed-environment`
|
||||
|
|
@ -1 +0,0 @@
|
|||
- PR `#5748`: added/pushed script.
|
||||
|
|
@ -1 +0,0 @@
|
|||
- Buildx required; edited/pushed `56d2701a`
|
||||
|
|
@ -1 +0,0 @@
|
|||
- PR `unslothai/unsloth`: `sm_120`
|
||||
|
|
@ -1 +0,0 @@
|
|||
- Build OK; smoke `ImportError`
|
||||
|
|
@ -1 +0,0 @@
|
|||
- Pushed `f7b34793`; pending retry.
|
||||
|
|
@ -1 +0,0 @@
|
|||
- Pushed `23a5b431`; pending retry.
|
||||
|
|
@ -1 +0,0 @@
|
|||
- `Failed to find C compiler`; exit 1
|
||||
|
|
@ -1 +0,0 @@
|
|||
- Asked: `test on other machines`
|
||||
|
|
@ -1 +0,0 @@
|
|||
- Asked: `gzip` multiprocessing? slow
|
||||
|
|
@ -1 +0,0 @@
|
|||
- Asked: `So what did you do to make the docker work?`
|
||||
|
|
@ -1 +0,0 @@
|
|||
- Wants executable `sh`-like script
|
||||
|
|
@ -1 +0,0 @@
|
|||
- Chose apt `docker-buildx`; run `bash docker/test_locally.sh --skip-notebook`
|
||||
|
|
@ -1 +0,0 @@
|
|||
- Recommended `pigz`; gzip-compatible.
|
||||
|
|
@ -1 +0,0 @@
|
|||
- Ran `docker info`; Docker works
|
||||
|
|
@ -1,2 +0,0 @@
|
|||
- `dde5170e` pushed
|
||||
- GPU tests pending
|
||||
|
|
@ -1 +0,0 @@
|
|||
- Asked why RTX 6000/5090 needed
|
||||
|
|
@ -1 +0,0 @@
|
|||
- `docker build --progress` unsupported; build failed exit `125`
|
||||
|
|
@ -1 +0,0 @@
|
|||
- Fixed Triton JIT via `1cdc5f17`
|
||||
|
|
@ -1 +0,0 @@
|
|||
- Pending: upload `/tmp/unsloth-blackwell.tar.gz`
|
||||
|
|
@ -1 +0,0 @@
|
|||
- Gave docker build/run commands; pending output
|
||||
|
|
@ -1 +0,0 @@
|
|||
- Asked `docker` GPU for `unsloth`
|
||||
|
|
@ -1 +0,0 @@
|
|||
- `56d2701a`: buildx fix OK; done
|
||||
|
|
@ -1 +0,0 @@
|
|||
- Asked `So what should we try next`
|
||||
|
|
@ -1 +0,0 @@
|
|||
- Build fails: `docker buildx` missing
|
||||
|
|
@ -1 +0,0 @@
|
|||
- fixed Dockerfile PEP668; pushed `fd55ed0a`
|
||||
|
|
@ -1 +0,0 @@
|
|||
- `latest docker`; vllm web search
|
||||
|
|
@ -1 +0,0 @@
|
|||
- `Ok you upload to danielhanchen`
|
||||
|
|
@ -1 +0,0 @@
|
|||
- pushed `4bfb4b89` add `docker/hf_*.sh`
|
||||
|
|
@ -1 +0,0 @@
|
|||
- HF repo made; upload tar pending.
|
||||
|
|
@ -1 +0,0 @@
|
|||
Continue the user’s latest directive: make the Docker setup work for DGX Spark via emulation. The WebSearch tool for Docker buildx multi-platform/QEMU CUDA build context is already done, so do not re-run it. Next, inspect the search result context and continue researching current linux/arm64 CUDA/PyTorch/xformers/bitsandbytes/flash-attn wheel availability, then update the Docker/build/test/publish files as needed for a build-time QEMU arm64 path.
|
||||
|
|
@ -1 +0,0 @@
|
|||
- Need support SM 7.5..12.1
|
||||
|
|
@ -1 +0,0 @@
|
|||
- LoRA train OK; all blocks completed
|
||||
|
|
@ -1 +0,0 @@
|
|||
- User said `Yes try it out`
|
||||
|
|
@ -1 +0,0 @@
|
|||
- PR `#5748` opened; push used scoped token
|
||||
|
|
@ -1 +0,0 @@
|
|||
- Docker push via `huggingface_hub`
|
||||
|
|
@ -1 +0,0 @@
|
|||
- Ran `docker save`; completed
|
||||
|
|
@ -1 +0,0 @@
|
|||
- Docker build needn't GPU; sm_120 only test
|
||||
|
|
@ -1 +0,0 @@
|
|||
Continue the latest directive: make the Docker image work for DGX Spark via build-time emulation, targeting a proper linux/arm64 image rather than CUDA runtime emulation. The assistant had started checking current multi-platform/QEMU and arm64 CUDA/PyTorch wheel availability; one WebSearch result for Docker buildx multi-platform builds has returned, so do not re-run that completed search. Next action is to continue the remaining live research from the in-flight WebSearch context, especially whether PyTorch/CUDA, xformers, bitsandbytes, flash-attn, and Unsloth dependencies have usable arm64 wheels or need conditional Dockerfile handling.
|
||||
|
|
@ -1 +0,0 @@
|
|||
- PR #5748 smoke passed; comment posted.
|
||||
|
|
@ -1 +0,0 @@
|
|||
- Validated; fixed `Dockerfile`; pending none
|
||||
|
|
@ -1 +0,0 @@
|
|||
- PENDING: test Docker notebook
|
||||
|
|
@ -1 +0,0 @@
|
|||
- Pushed `00cbc825`; retry `bash docker/test_locally.sh --skip-notebook`
|
||||
|
|
@ -1 +0,0 @@
|
|||
- `--skip-notebook`; Docker smoke OK
|
||||
|
|
@ -1 +0,0 @@
|
|||
- Asked if Blackwell image supports GPUs
|
||||
|
|
@ -1 +0,0 @@
|
|||
- Installed `docker-buildx`; build failed Docker socket perm
|
||||
|
|
@ -1 +0,0 @@
|
|||
- Answered GPU support matrix; DGX pending
|
||||
|
|
@ -1 +0,0 @@
|
|||
- B200 OK; pending HF upload cmds
|
||||
Loading…
Add table
Add a link
Reference in a new issue