create file fail with special name in windows env
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 35/100
Research direction
Start by locating LocalStorage.Save and reproducing the failure on a Windows environment with the cited provider model name. Check the error returned by os.WriteFile; done when failures for special names return useful error information and the behavior is covered by the project's existing tests, if applicable.
Written by the indexing model from the issue text.
Description
func (l *LocalStorage) Save(key string, data []byte) error {
path := filepath.Join(l.root, key)
filePath := filepath.Dir(path)
if err := os.MkdirAll(filePath, 0o755); err != nil {
return err
}
return os.WriteFile(path, data, 0o644)
}
dify pluge model provider like langgenius/deepseek:0.0.11@35bcd3f233f99d07bdadef8b326945df3bda5e8f773330144bc90d84800336b9 this os.WriteFile(path, data, 0o644) is error, you should return error info
- Dominant language
- Go
- Stars
- 16
- Forks
- 21
- Avg merge
- 1m
- Merged PRs (30d)
- 1
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 langgenius/dify-cloud-kit
-
needs-info
Difficulty 4/5 3-5 days Newbie friendliness 35/100
langgenius/dify-cloud-kit#9 · 1 comment ·
All issues in langgenius/dify-cloud-kit
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
praetorian-inc/augustus#334 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
TestTOMLBigFileParsesInLinearTime: a 1s wall-clock bound on a 3 MB parse fails under load (1.27s)Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
peasant-labs/village#293 ·
Maintainers usually reply within 1 day