fix

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,64 @@
+# ✨ Description
+
+Please provide a brief summary of the changes, relevant motivation, and context.
+Include any related issue numbers or links to discussions, and explain why this change is necessary.
+
+Closes # <!-- Insert issue number here, if applicable -->
+
+## 🔍 Type of change
+
+Select all that apply:
+
+- [ ] 🐛 **Bug fix** (non-breaking change that addresses a specific issue)
+- [ ] 🚀 **New feature** (non-breaking change that adds functionality)
+- [ ] ⚠️ **Breaking change** (a change that could affect existing functionality)
+- [ ] 📈 **Performance improvement/optimization** (improves speed, memory usage, or efficiency)
+- [ ] 🛠️ **Code refactor** (non-functional changes that improve code readability, structure, etc.)
+- [ ] 📦 **Dependency bump** (updates dependencies, including Dockerfile or package changes)
+- [ ] 📝 **Documentation change** (updates documentation, including new content or typo fixes)
+- [ ] 🔧 **Infrastructure/Build change** (affects build process, CI/CD, or dependencies)
+
+## 📝 Changes
+
+List the key changes introduced in this PR:
+
+1. Change A
+2. Change B
+
+# ✅ Checklist
+
+Make sure the following tasks are completed before submitting the PR:
+
+### General:
+- [ ] 📜 I have read and followed the [contributing guidelines](CONTRIBUTING.md).
+- [ ] 🎉 The functionality is complete, and I have tested the changes.
+- [ ] 📝 I have updated the documentation if needed.
+- [ ] ⚠️ The change does not introduce any new issues (e.g., runtime warnings, type checker errors, linting problems, unhandled edge cases).
+- [ ] 🧩 I have commented my code, especially in hard-to-understand areas.
+
+### Dependencies and Configuration:
+- [ ] 🐋 I have updated the Docker configuration or dependencies, if applicable.
+- [ ] 🔄 I have ensured compatibility with the existing setup after dependency changes.
+
+### Testing:
+- [ ] 🧪 I have added or updated tests to cover my changes.
+- [ ] ✔️ New and existing tests pass locally with my changes.
+- [ ] 🚦 I have tested these changes on GPUs and verified training stability.
+- [ ] 🏋️ I have tested the changes on realistic training workloads, if applicable.
+
+### Performance Impact:
+- [ ] 📊 I have run benchmarks where applicable to evaluate the performance impact.
+- [ ] ✅ The benchmarks show no performance regression.
+- [ ] 🚀 The benchmarks indicate a potential performance improvement.
+- [ ] ⚠️ The benchmarks indicate a potential performance degradation.
+- [ ] 📈 I have provided benchmark results and detailed any performance impact below, if applicable.
+
+# 📊 Performance Impact Details
+
+If there is any impact on performance, describe it and provide benchmark results, if applicable:
+
+---
+
+# 📝 Additional Notes
+
+Include any additional context, information, or considerations here, such as known issues, follow-up tasks, or backward compatibility concerns.

.github/workflows/ci.yaml

@@ -0,0 +1,85 @@
+name: CI
+
+on:
+  schedule:
+    - cron: "0 10 * * *"
+  push:
+    branches:
+      - "main"
+    tags:
+      - "v*.*.*"
+  pull_request:
+    branches:
+      - "main"
+
+jobs:
+  test:
+    name: Test
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+
+      - uses: actions/setup-python@v5
+        with:
+          python-version: '3.12'
+          cache: 'pip'
+
+      - name: Install dependencies
+        run: |
+          pip install "torch>=2.2.2"
+          FLASH_ATTENTION_SKIP_CUDA_BUILD=TRUE FLASH_ATTENTION_FORCE_BUILD=TRUE pip install --no-build-isolation -e ".[CORE,OPTIONAL,DEV,DOCS]"
+
+      - name: Run tests
+        run: pytest .
+
+  docker:
+    name: Docker
+    runs-on: ubuntu-latest
+    needs: test
+    steps:
+      - name: Clean unused files
+        run: |
+          sudo rm -rf /usr/local/lib/android || true  # will release about 10 GB
+          sudo rm -rf /usr/share/dotnet || true  # will release about 20GB
+          sudo rm -rf /opt/ghc || true
+          sudo rm -rf /usr/local/.ghcup || true
+
+      - name: Checkout repository
+        uses: actions/checkout@v4
+
+      - name: Docker meta
+        id: meta
+        uses: docker/metadata-action@v5
+        with:
+          images: |
+            ghcr.io/servicenow/fast-llm
+          tags: |
+            type=schedule
+            type=ref,event=branch
+            type=semver,pattern={{version}}
+            type=semver,pattern={{major}}.{{minor}}
+            type=semver,pattern={{major}}
+            type=sha
+            type=raw,value=latest,enabled={{github.ref == 'refs/heads/main'}}
+
+      - name: Set up Docker Buildx
+        uses: docker/setup-buildx-action@v3
+
+      - name: Login to GHCR
+        uses: docker/login-action@v3
+        with:
+          registry: ghcr.io
+          username: ${{ github.repository_owner }}
+          password: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Build and push
+        uses: docker/build-push-action@v6
+        with:
+          context: .
+          # push: ${{ github.event_name != 'pull_request' }}
+          push: true
+          tags: ${{ steps.meta.outputs.tags }}
+          labels: ${{ steps.meta.outputs.labels }}
+          cache-from: type=registry,ref=ghcr.io/servicenow/fast-llm:cache
+          cache-to: type=registry,ref=ghcr.io/servicenow/fast-llm:cache,mode=max

.github/workflows/docs.yaml

@@ -0,0 +1,59 @@
+name: Documentation
+
+on:
+  push:
+    branches:
+      - main
+  pull_request:
+    branches:
+      - main
+
+permissions:
+  contents: write
+
+jobs:
+  build:
+    name: Build
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+          cache: "pip"
+      - run: echo "cache_id=$(date --utc '+%V')" >> $GITHUB_ENV
+      - uses: actions/cache@v4
+        with:
+          key: mkdocs-material-${{ env.cache_id }}
+          path: .cache
+          restore-keys: |
+            mkdocs-material-
+      - run: |
+          pip install "torch>=2.2.2"
+          FLASH_ATTENTION_SKIP_CUDA_BUILD=TRUE FLASH_ATTENTION_FORCE_BUILD=TRUE pip install --no-build-isolation -e ".[CORE,OPTIONAL,DEV,DOCS]"
+      - name: Build the documentation
+        run: mkdocs build
+
+  deploy:
+    if: github.event_name == 'push'
+    name: Deploy
+    needs: build
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.12"
+          cache: "pip"
+      - run: echo "cache_id=$(date --utc '+%V')" >> $GITHUB_ENV
+      - uses: actions/cache@v4
+        with:
+          key: mkdocs-material-${{ env.cache_id }}
+          path: .cache
+          restore-keys: |
+            mkdocs-material-
+      - run: |
+          pip install "torch>=2.2.2"
+          FLASH_ATTENTION_SKIP_CUDA_BUILD=TRUE FLASH_ATTENTION_FORCE_BUILD=TRUE pip install --no-build-isolation -e ".[CORE,OPTIONAL,DEV,DOCS]"
+      - name: Publish the documentation
+        run: mkdocs gh-deploy --force --dirty

CITATION.cff

@@ -0,0 +1,28 @@
+cff-version: 1.2.0
+message: "If you use Fast-LLM in your research, please cite it as follows:"
+title: "Fast-LLM"
+repository-code: "https://github.com/ServiceNow/Fast-LLM"
+url: "https://github.com/ServiceNow/Fast-LLM"
+license: "Apache-2.0"
+keywords:
+  - large language models
+  - machine learning
+  - deep learning
+  - distributed training
+  - open source
+authors:
+  - family-names: "Lamy Poirier"
+    given-names: "Joel"
+  - family-names: "Tian"
+    given-names: "Max"
+  - family-names: "Li"
+    given-names: "Raymond"
+  - family-names: "Guille-Escuret"
+    given-names: "Charles"
+  - family-names: "Kumar"
+    given-names: "Luke Nitish"
+  - family-names: "Kocetkov"
+    given-names: "Denis"
+  - family-names: "Scholak"
+    given-names: "Torsten"
+date-released: "2024-10-19"

CODE_OF_CONDUCT.md

@@ -0,0 +1,46 @@
+### ServiceNow Open Source Code-of-Conduct
+
+This code of conduct provides guidelines for participation in ServiceNow-managed open-source communities and projects.
+
+**Discussion forum guidelines**
+
+Communities thrive when members support each other and provide useful feedback.
+
+- Be polite and courteous. Respect and treat others as you would expect to be treated yourself.
+- Respect your audience. Posts should not upset, annoy, threaten, harass, abuse or embarrass other members.
+- User Contributions must not include material that is defamatory, obscene, indecent, abusive, offensive, harassing, violent, hateful, inflammatory or otherwise objectionable.
+- Lively and collegial discussions are always encouraged in a healthy community. It is okay to argue facts but not okay to argue personalities or personal beliefs.
+- Do not use text formats such as all caps or bold that may be read as annoying, rude or send a strong message.
+- Do not publish anyone’s private personal information without their explicit consent.
+- Avoid using abbreviations or terminology that others may not understand. An abbreviation may mean something to you but in another context or country, it may have another meaning.
+- Be accountable for your actions by correcting your mistakes and indicating where you have changed a previous post of yours.
+- Mark content as correct and helpful, and provide feedback. If you read a discussion post that you find helpful, we encourage you to leave a positive vote and comment in the replies. If you find a post that is unhelpful, please provide more information in the issue comments.
+
+**Issue board guidelines**
+
+Many open-source projects provide an Issues board, with similar functionality to a Discussions forum. The same rules from the discussion forum guidelines apply to the Issues board.
+
+ServiceNow suggests the following technical support pathways for open-source projects:
+
+1. Clearly identify and document the issue or question you have.
+2. View the Documentation.
+3. Search the Discussions.
+4. Search the project knowledge base or Wiki for known errors, useful solutions, and troubleshooting tips.
+5. Check the project guidelines in the [`CONTRIBUTING.md`](CONTRIBUTING.md) file if you would like details on how you can submit a change. Community contributions are valued and appreciated!
+6. Log an Issue if it hasn’t already been logged. If the issue has already been logged by another user, vote it up, and add a comment with additional or missing information. Do your best to choose the correct category when logging a new issue. This will make it easier to differentiate bugs from new feature requests or ideas. If after logging an issue you find the solution, please close your issue and provide a comment with the solution. This will help the project owners and other users.
+7. Contact the project team contributors of the project to see if they can help as a last resort only.
+
+**Repositories**
+
+- Read and follow the license instructions
+- Remember to include citations if you use someone else’s work in your own project. Use the [`CITATION.cff`](CITATION.cff) to find the correct project citation reference.
+- ‘Star’ project repos to save for future reference.
+- ‘Watch’ project repos to get notifications of changes – this can get noisy for some projects, so only watch the ones you really need to track closely.
+
+**Enforcement and reporting**
+
+We encourage community members and users to help each other and to resolve issues amongst themselves as much as possible. If a matter cannot be resolved in good faith within the means available, please reach out to a team member or email [email protected].
+
+**ServiceNow Disclaimer.**
+
+We may, but are under no obligation to, monitor or censor comments made by users or content provided by contributors and we are not responsible for the accuracy, completeness, appropriateness or legality of anything posted, depicted or otherwise provided by third‑party users and we disclaim any and all liability relating thereto.

CONTRIBUTING.md

@@ -0,0 +1,62 @@
+# Contributing to Fast-LLM 🚀
+
+Thank you for your interest in contributing to Fast-LLM! We're thrilled to have you here, and your support is invaluable in helping us accelerate LLM training to full speed. This guide will walk you through the steps to contribute, from reporting issues to submitting changes and setting up your development environment.
+
+If you have questions or want to start a discussion, feel free to [open a discussion](https://github.com/ServiceNow/Fast-LLM/discussions) on our GitHub page.
+
+## Getting Started
+
+To get started with contributing to Fast-LLM, follow these steps to set up your environment:
+
+1. **Set Up the Development Environment**: Fast-LLM is built on [PyTorch](https://pytorch.org/) and [Triton](https://triton-lang.org/). Check out our [setup guide](https://servicenow.github.io/Fast-LLM/development/setup) for instructions on getting everything ready, including the development environment and dependencies.
+2. **Learn Our Best Practices**: Get familiar with our [development best practices](https://servicenow.github.io/Fast-LLM/development/dev-practices/), which cover code style, pre-commit hooks, and testing strategies.
+3. **Launch Fast-LLM Locally or with Docker**: Need help getting started? Follow the instructions in the [launching section](https://servicenow.github.io/Fast-LLM/development/launching) to get Fast-LLM up and running.
+
+## How to Report a Bug 🐞
+
+Found a bug? Let's squash it together! [Open an issue](https://github.com/ServiceNow/Fast-LLM/issues/new/choose) and select "Bug report." Please include as much information as possible:
+
+- Steps to reproduce the issue.
+- What you expected to happen versus what actually happened.
+- Screenshots, log files, or error messages (if applicable).
+- Details about your environment setup (e.g., OS, Docker version, and relevant configurations).
+
+If you're familiar with the codebase, consider adding a failing unit test to demonstrate the problem (optional, but helpful!).
+
+## Proposing Changes
+
+Before diving into code, [open an issue](https://github.com/ServiceNow/Fast-LLM/issues) to discuss your proposal. This is especially important if you're planning significant changes or adding new dependencies. Once your idea is approved, follow these steps:
+
+1. **Fork the Repository**: [Fork Fast-LLM](https://github.com/ServiceNow/Fast-LLM/fork) to your own GitHub account.
+2. **Clone Your Fork Locally**: Use `git clone` to bring the code to your local machine.
+3. **Create a New Branch**: Name your branch descriptively, such as `feature/awesome-feature` or `fix/nasty-bug`.
+4. **Make Your Changes**: Work your magic! Don't forget to add or update tests, benchmarks, or configurations as needed.
+5. **Create a Properly Titled Pull Request**: When you're ready to open a PR, make sure to use a clear and descriptive title that follows our [PR title guidelines](https://servicenow.github.io/Fast-LLM/development/pr-title-guidelines). This title will become the commit message for the squashed merge.
+6. **Push to Your Fork**: Push the branch to your GitHub fork.
+7. **Open a Pull Request**: [Submit a pull request](https://github.com/ServiceNow/Fast-LLM/compare) to the `main` branch. Reference the original issue number and provide a brief summary of your changes.
+
+### Guidelines for a Successful Pull Request
+
+Here are some tips to ensure your pull request gets reviewed and merged promptly:
+
+- **Follow our coding standards**: Stick to our [development best practices](https://servicenow.github.io/Fast-LLM/development/dev-practices/) to keep the code clean and consistent.
+- **Write tests**: Verify your changes with unit tests for new features or bug fixes.
+- **Test on GPUs and real-world workloads**: Since Fast-LLM is all about training large language models, make sure your changes work smoothly in GPU environments and on typical training setups.
+- **Run benchmarks and performance tests**: Make sure your changes don't slow things down. If there's any impact on performance, provide benchmark results to back it up.
+- **Avoid introducing new issues**: Check that there are no new runtime warnings, type checker errors, linting problems, or unhandled edge cases.
+- **Comment non-trivial code**: Make your code easy to understand for others.
+- **Keep sensitive data out**: Make sure your code or commit messages don't expose private or proprietary information.
+- **Use the [PR template](https://github.com/ServiceNow/Fast-LLM/blob/main/.github/pull_request_template.md)**: Complete the checklist to make sure everything is in order before hitting submit.
+
+## Seeking Help or Clarification
+
+If you're unsure about something or need help, you've got options:
+
+- **GitHub Discussions**: [Start a discussion](https://github.com/ServiceNow/Fast-LLM/discussions) if you need advice or just want to chat.
+- **Project Maintainers**: Mention a maintainer in an issue or pull request if you need a review or guidance.
+
+## Contributors
+
+We're grateful for all the awesome contributors who help make Fast-LLM better. Join our contributors' list and make your first contribution!
+
+To learn more about the team and maintainers, visit our [About page](https://servicenow.github.io/Fast-LLM/about-us/).