Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Ошибка установки плагинов gitsync

Open
#254 9 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Domain
cli, tooling

Research direction

Reproduce the failure with gitsync p init and inspect src/core/Классы/internal/Классы/ПодключениеПлагиновКаталога.os around line 73. Compare behavior before and after clearing C:\Users\<ИмяПользователя>\AppData\Local\gitsync\plugins\gitsync-plugins on the reported Windows, OScript, Gitsync, 1C, and .NET versions. Done means plugin initialization and subsequent gitsync commands no longer raise the reported exception.

Written by the indexing model from the issue text.

Description

plugins

Описание ошибки
Установил gitsync, после инициализации плагинов (gitsync p init) при любом обращении gitsync падает с ошибкой:
{Модуль C:\OneScript\lib\gitsync\src\core\Классы\internal\Классы\ПодключениеПлагиновКаталога.os / Ошибка в строке: 73 /
Внешнее исключение (System.Reflection.TargetInvocationException): Адресат вызова создал исключение.}
После очистки папки C:\Users<ИмяПользователя>\AppData\Local\gitsync\plugins\gitsync-plugins gitsync работает,
но после gitsync p init или установки любого плагина ошибка возвращается.

Пробовал на oscript 1.5.0 + gitsync 3.3.3 и oscript 1.2.0 + gitsync 3.1.0

Окружение:

  • Версия операционной системы: Windows server 2016
  • Редакция 1С платформы 8.3.16.1814
  • Версия Gitsync 3.3.3
  • Версия OScript 1.5.0
  • Версия .Net 4.7.03062
Dominant language
1C Enterprise
Stars
334
Forks
98
Avg merge
2d 10h
Merged PRs (30d)
10

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from oscript-library/gitsync

All issues in oscript-library/gitsync

Similar issues

More CLI issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.