VisionSystemsInc / VisionSystemsInc/vsi_common

Submodule update on windows

Open
#85 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug just windows
Dominant language
Shell
Stars
8
Forks
9
Avg merge
36m
Merged PRs (30d)
1

Description

Updating the vsi_common submodule from just on windows, will cause git to error if it tries to rewrite the just file itself, as it is in use, and Windows doesn't support this like *nix does.

The result is a horrible explosion of a partially checked out vsi_common repo, in a dirty state, that takes both a git reset --hard and git clean df, followed by a manual update.

Possible solutions:

  1. Someway to detangle using the just file on windows, an exec to a tmp file?
    • setup.env could define the function just instead, that would source what is currently the file just
  2. git hook on windows, to keep vsi_common up to date...
  3. Detecting the problem before it happens, and echoing out that you need to git submodule update --recursive vsi_common manually

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Start by inspecting the just file and setup.env, then reproduce the Windows submodule update path involving git. Done means updating vsi_common on Windows no longer leaves a partially checked-out dirty repository, or detects the condition and clearly directs the manual recursive update.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.