kvcache-ai/accelerate
1
0
Fork 0
mirror of https://github.com/kvcache-ai/accelerate.git synced 2026-11-05 01:17:22 +00:00
Code Issues 1 Projects Packages Wiki Activity

[PR #3] [WIP]Full fine tune support #3

New issue
Open
opened 2026-10-29 14:17:55 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-10-29 14:17:55 +00:00
Owner
Copy link

📋 Pull Request Information

Original PR: https://github.com/kvcache-ai/accelerate/pull/3
Author: @poryfly
Created: 5/22/2026
Status: 🔄 Open

Base: sft-v5 ← Head: full-fine-tune-support

📝 Commits (1)

  • 5981edd full-fine-tune-support for kt

📊 Changes

1 file changed (+2 additions, -0 deletions)

View changed files

📝 src/accelerate/utils/launch.py (+2 -0)

📄 Description

What does this PR do?

support full finetune for kt

Fixes # (issue)

Before submitting

  • This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
  • Did you read the contributor guideline,
    Pull Request section?
  • Was this discussed/approved via a Github issue or the forum? Please add a link
    to it if that's the case.
  • Did you make sure to update the documentation with your changes? Here are the
    documentation guidelines, and
    here are tips on formatting docstrings.
  • Did you write any new necessary tests?

Who can review?

Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/kvcache-ai/accelerate/pull/3 **Author:** [@poryfly](https://github.com/poryfly) **Created:** 5/22/2026 **Status:** 🔄 Open **Base:** `sft-v5` ← **Head:** `full-fine-tune-support` --- ### 📝 Commits (1) - [`5981edd`](https://github.com/kvcache-ai/accelerate/commit/5981edd6bdae57843d239771aaee40620f897130) full-fine-tune-support for kt ### 📊 Changes **1 file changed** (+2 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `src/accelerate/utils/launch.py` (+2 -0) </details> ### 📄 Description # What does this PR do? support full finetune for kt <!-- Congratulations! You've made it this far! You're not quite done yet though. Once merged, your PR is going to appear in the release notes with the title you set, so make sure it's a great title that fully reflects the extent of your awesome contribution. Then, please replace this with a description of the change and which issue is fixed (if applicable). Please also include relevant motivation and context. List any dependencies (if any) that are required for this change. Once you're done, someone will review your PR shortly (see the section "Who can review?" below to tag some potential reviewers). They may suggest changes to make the code even better. If no one reviewed your PR after a week has passed, don't hesitate to post a new comment @-mentioning the same persons---sometimes notifications get lost. --> <!-- Remove if not applicable --> Fixes # (issue) ## Before submitting - [ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case). - [ ] Did you read the [contributor guideline](https://github.com/huggingface/accelerate/blob/main/CONTRIBUTING.md#submitting-a-pull-request-pr), Pull Request section? - [ ] Was this discussed/approved via a Github issue or the [forum](https://discuss.huggingface.co/)? Please add a link to it if that's the case. - [ ] Did you make sure to update the documentation with your changes? Here are the [documentation guidelines](https://github.com/huggingface/accelerate/tree/main/docs), and [here are tips on formatting docstrings](https://github.com/huggingface/accelerate/tree/main/docs#writing-documentation---specification). - [ ] Did you write any new necessary tests? ## Who can review? Anyone in the community is free to review the PR once the tests have passed. Feel free to tag members/contributors who may be interested in your PR. <!-- Your PR will be replied to more quickly if you can figure out the right person to tag with @ If you know how to use git blame, that is the easiest way, otherwise, here is a rough guide of **who to tag**. - Big modeling: @SunMarc - Fully-Sharded Data Parallism: @SunMarc - DeepSpeed: @SunMarc - Command Line Interface: @SunMarc - Documentation: @SunMarc - Core parts of the library: @BenjaminBossan @SunMarc - Maintained examples: @SunMarc --> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
perf/fsdp2-bf16-grad-norm-20261010
sft-v5
fix/kt-activation-policy-forwarding
release
kt
No results found.
Labels
Clear labels   
pull-request
Mirrored from GitHub Pull Request

No labels
pull-request
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
kvcache-ai/accelerate#3
No description provided.