Ошибка монопольного чтения plugins.json
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- cli
Research direction
Start with gitsync\plugins\plugins.json and the file-handling module at src/core/Классы/internal/files/Модули/РаботаСФайлами.os, then reproduce the failure by running the provided command concurrently. Done means two or more simultaneous jobs can access plugins.json without the reported System.IO.IOException.
Written by the indexing model from the issue text.
Description
Описание ошибки
При одновременной работе нескольких линий дженкинса происходит ошибка при попытке монопольного чтения файла: gitsync\plugins\plugins.json
{Модуль C:\Program Files\OneScript\lib\gitsync\src\core\Классы\internal\files\Модули\РаботаСФайлами.os / Ошибка в строке: 5 / Внешнее исключение (System.IO.IOException): Процесс не может получить доступ к файлу "C:\Users\jenkins_uat\AppData\Local\gitsync\plugins\plugins.json", так как этот файл используется другим процессом.}
Сценарий воспроизведения
Шаги по воспроизведению:
Одновременно запускаем два или более задания:
gitsync --v8version 8.3.12.1529 -C /Fs:/1c/ibase -t s:/gitsync -v sync -u user -p pass -l 1 -R -F tcp://repo-serv:1529/ibase ./src/cf/ https://mygitlab.ru/ibase
Ожидаемое поведение если бы ошибки не было
отсутствие исключения
- Dominant language
- 1C Enterprise
- Stars
- 334
- Forks
- 98
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 10
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
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 oscript-library/gitsync
-
УстановщикПлагинов.os:142 использует удалённый метод ПолучитьВыводКоманды() (1commands ≥ 1.5.0)Open
Difficulty 1/5 Under an hour Newbie friendliness 90/100
oscript-library/gitsync#368 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
oscript-library/gitsync#355 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
oscript-library/gitsync#241 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
oscript-library/gitsync#366 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
oscript-library/gitsync#361 · 6 comments ·
Maintainers usually reply within 1 day
All issues in oscript-library/gitsync
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
comp/tools P2 platform/telegram sweeper:risk-message-delivery type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 61/100
NousResearch/hermes-agent#133164 · 2 comments ·
Maintainers usually reply within 1 day
-
first-Agent inherits Docker TLS settings for its recorded Unix socketPossibly taken @ericcaiwx-star claimed this today. Openclawsweeper:bulk-filed clawsweeper:linked-pr-open clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster P2
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
openclaw/openclaw-enterprise#1337 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
jobs restart --verify: hotlane restart timeout (10s) shorter than its shutdown (~30s) → false exit 1Open
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
EtanHey/brainlayer#1072 ·
Maintainers usually reply within 1 day
-
maintainer-needed p2 remote triaged
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day