Regarding Crossfile Completion Prompt Format for Seed-Coder-8B Series Models on CrossCodeEval Benchmark
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- documentation, machine-learning
Research direction
Start with the technical report and the CrossCodeEval evaluation setup referenced in the issue. Verify the exact prompt template, any cross-file context handling, and any special tokens used for Seed-Coder-8B-Base. Done means documenting the confirmed format and an example prompt, or clearly noting which details are unavailable.
Written by the indexing model from the issue text.
Description
Referencing the technical report, could you please provide the specific prompt format used to evaluateSeed-Coder-8B-Base on the CrossCodeEval benchmark?
This information is needed to accurately reproduce the evaluation setup and for comparative analysis.
Specifically:
CrossCodeEval Prompt Format:
- What was the exact prompt structure/template used for Seed-Coder-8B-Base during the CrossCodeEval evaluation?
Cross-File Context Handling:
- How was cross-file context incorporated into the prompts for the CrossCodeEval evaluation (if applicable)?
- More generally, does the Seed-Coder model series utilize special tokens or a specific prompt format for handling multi-file context in repository-level code completion tasks (potentially similar to mechanisms in models like the Qwen2.5-Coder series)?
Details on the format(s), including any special tokens, or providing an example prompt would be very helpful.
Thanks!
- Dominant language
- No language data
- Stars
- 759
- Forks
- 60
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from ByteDance-Seed/Seed-Coder
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
ByteDance-Seed/Seed-Coder#24 ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
ByteDance-Seed/Seed-Coder#23 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
ByteDance-Seed/Seed-Coder#22 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
ByteDance-Seed/Seed-Coder#21 ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
ByteDance-Seed/Seed-Coder#20 ·
All issues in ByteDance-Seed/Seed-Coder
Similar issues
-
sync-en
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
sync-en
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 4 days
-
area:connector bug
Difficulty 1/5 Under an hour Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
environment: OPENCODE_API_KEY is described as a Console service account key, but a Go subscription key worksPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
tester-army/e2e#1015 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
chroma-core/chroma#7879 ·
Maintainers usually reply within 1 day