chore: import upstream snapshot with attribution

This commit is contained in:
wehub-resource-sync
2026-07-13 13:25:10 +08:00
commit c397331b1e
3684 changed files with 990993 additions and 0 deletions
+41
View File
@@ -0,0 +1,41 @@
---
name: ❓ Questions/Help
about: Ask for help after checking existing issues and docs
labels: 'question, needs triage'
---
Notice: In order to resolve issues efficiently, please follow the template.
(注意:为了更加高效率解决您遇到的问题,请按照模板提问,补充细节。)
## Before asking
1. Search existing issues: https://github.com/modelscope/FunASR/issues
2. Search the docs: https://modelscope.github.io/FunASR/
3. Check the README quick start and deployment section.
## Question
<!-- What are you trying to do, and where are you blocked? -->
## Code or command
```bash
```
## What have you tried?
<!-- Include links to docs or examples you followed, plus the exact error/result. -->
## Environment
- OS:
- Python version:
- FunASR version:
- ModelScope version:
- PyTorch / torchaudio version:
- Install method (`pip`, source, Docker):
- Device (`cuda`, `cpu`, `mps`):
- GPU model:
- CUDA/cuDNN version:
- Docker image tag, if used:
+64
View File
@@ -0,0 +1,64 @@
---
name: 🐛 Bug Report
about: Submit a reproducible bug report to help us improve FunASR
labels: 'bug, needs triage'
---
Notice: In order to resolve issues efficiently, please follow the template and include reproducible details.
(注意:为了更加高效率解决您遇到的问题,请按照模板提问,补充可复现细节。)
## 🐛 Bug
<!-- A clear and concise description of the bug. -->
## To Reproduce
Steps to reproduce the behavior. Always include the exact command you ran.
1. Install with: `...`
2. Run: `...`
3. See error: `...`
## Code sample
<!-- Paste the smallest code sample that still reproduces the issue. -->
```python
```
## Expected behavior
<!-- A clear and concise description of what you expected to happen. -->
## Error logs
<!-- Paste the full traceback or relevant logs. Remove private tokens and paths. -->
```text
```
## Environment
- OS:
- Python version:
- FunASR version:
- ModelScope version:
- PyTorch / torchaudio version:
- Install method (`pip`, source, Docker):
- Device (`cuda`, `cpu`, `mps`):
- GPU model:
- CUDA/cuDNN version:
- Docker image tag, if used:
## Audio details
If the audio cannot be shared, please describe:
- Duration:
- Sample rate:
- Format:
- Language/dialect:
- Speaker count:
- Background noise/music:
+11
View File
@@ -0,0 +1,11 @@
blank_issues_enabled: false
contact_links:
- name: FunASR documentation
url: https://modelscope.github.io/FunASR/
about: Read installation, tutorial, deployment, benchmark, and API docs.
- name: GitHub Discussions
url: https://github.com/modelscope/FunASR/discussions
about: Share ideas, showcase usage, and ask open-ended community questions.
- name: Hugging Face models
url: https://huggingface.co/funasr
about: Browse FunASR checkpoints on Hugging Face.
+45
View File
@@ -0,0 +1,45 @@
---
name: 🚀 Deployment Help
about: Get help with API server, WebSocket, Docker, vLLM, Triton, Android, or agent integration
labels: 'deployment, needs triage'
---
## Deployment target
- [ ] OpenAI-compatible API server
- [ ] WebSocket streaming service
- [ ] Docker runtime
- [ ] vLLM acceleration
- [ ] Triton
- [ ] Android / mobile
- [ ] Browser / Web UI
- [ ] MCP / agent integration
- [ ] Other:
## Goal
<!-- What user-facing service or workflow are you trying to deploy? -->
## Command or config
```bash
```
## Error or unexpected behavior
```text
```
## Environment
- OS:
- Python version:
- FunASR version:
- Install method (`pip`, source, Docker):
- Device (`cuda`, `cpu`, `mps`):
- GPU model and memory:
- CUDA/cuDNN version:
- Docker image tag, if used:
- Network endpoint / port:
+15
View File
@@ -0,0 +1,15 @@
---
name: 📚 Documentation/Typos
about: Report an issue related to documentation or a typo
labels: 'documentation, needs triage'
---
## 📚 Documentation
For typos and doc fixes, please go ahead and:
1. Create an issue.
2. Fix the typo.
3. Submit a PR.
Thanks!
+27
View File
@@ -0,0 +1,27 @@
---
name: ✨ Feature Request
about: Suggest a model, language, runtime, deployment, benchmark, or documentation improvement
labels: 'enhancement, needs triage'
---
## Use case
<!-- What are you trying to build, deploy, evaluate, or research with FunASR? -->
## Proposed solution
<!-- Describe the desired model/API/runtime/doc/benchmark behavior. -->
## Alternatives or workarounds
<!-- What workaround are you using today? What other tools did you consider? -->
## Expected impact
<!-- Who benefits: new users, production deployers, researchers, agent builders, educators, etc.? -->
## Willing to contribute?
- [ ] I can submit a PR
- [ ] I can help test
- [ ] I can provide data, logs, or benchmark results
@@ -0,0 +1,71 @@
---
name: 📊 Migration Benchmark Report
about: Share FunASR results when comparing against Whisper, OpenAI audio APIs, or cloud ASR
labels: 'benchmark, showcase, needs triage'
---
Thanks for benchmarking FunASR on your own audio. Migration reports help new users decide whether FunASR fits their language, domain, hardware, and deployment constraints.
If you need help debugging a failure, please use Bug Report or Deployment Help instead.
## Summary
<!-- One or two sentences: what did you compare, and what was the headline result? -->
## Baseline
- Baseline ASR (`Whisper`, `Whisper large-v3`, cloud provider, internal system, other):
- Baseline runtime or API:
- Baseline hardware or pricing tier:
## FunASR setup
- FunASR version:
- Model(s):
- Runtime path (`Python API`, `funasr-server`, `OpenAI API`, `Docker`, `WebSocket`, `vLLM`, other):
- Device (`cuda`, `cpu`, `mps`):
- GPU / CPU:
- CUDA / PyTorch versions:
- Command or script used:
```bash
```
## Audio set
- Number of files:
- Total audio duration:
- Language(s) / dialect(s):
- Domain (`meeting`, `call-center`, `subtitle`, `lecture`, `media`, `noisy field audio`, other):
- Speaker count range:
- Sample rate / format:
- Can any sample be shared publicly? yes/no
## Results
<!-- Paste the aggregate section from examples/migration/benchmark_funasr.py summary.md, or summarize your own measurement. -->
```text
```
## Quality notes
<!-- Share WER/CER if available, or human-review notes about names, numbers, punctuation, timestamps, speaker labels, and domain terms. -->
## Operational notes
- Model download / warmup time:
- Steady-state throughput:
- Memory usage:
- Failed files or error rate:
- Deployment blockers:
## Links or artifacts
<!-- Public repo, demo, blog, benchmark sheet, screenshot, anonymized transcript snippet, or architecture diagram. Do not include private audio, credentials, or customer data. -->
## What should FunASR improve next?
<!-- Missing docs, rough edges, model gaps, deployment friction, benchmark needs, etc. -->
+56
View File
@@ -0,0 +1,56 @@
---
name: 🎤 Showcase / Production Story
about: Share how you use FunASR in a demo, product, benchmark, research project, or internal workflow
labels: 'showcase, needs triage'
---
Thanks for sharing your FunASR use case. Concrete usage reports help new users choose the right path and help maintainers prioritize docs, examples, models, and deployment work.
If this is a support question, please use Bug Report or Deployment Help instead.
## Summary
<!-- What did you build or evaluate with FunASR? One or two sentences is enough. -->
## Scenario
- [ ] Local transcription demo
- [ ] Private OpenAI-compatible speech API
- [ ] Agent / MCP / voice-input workflow
- [ ] Streaming ASR / live captions
- [ ] Subtitle generation
- [ ] Batch transcription / archive processing
- [ ] Benchmark or migration from Whisper/cloud ASR
- [ ] Research / education
- [ ] Production deployment
- [ ] Other:
## Deployment details
- FunASR version:
- Model(s):
- Device (`cuda`, `cpu`, `mps`):
- GPU / CPU:
- Runtime path (`Python API`, `funasr-server`, `WebSocket`, `Docker`, `vLLM`, `MCP`, other):
- Audio language/domain:
- Approximate audio duration or traffic:
## Results
<!-- Share speed, accuracy/CER/WER, latency, cost, CPU/GPU usage, or qualitative results if available. -->
```text
```
## Links or screenshots
<!-- Public demo, article, repo, benchmark report, screenshot, or architecture diagram. Do not include private audio, credentials, or customer data. -->
## What was easy?
<!-- Which docs, examples, or APIs helped most? -->
## What should be improved?
<!-- Missing docs, rough edges, model gaps, deployment friction, benchmark needs, etc. -->