HashLoad / HashLoad/boss

Filename to long and Git branch is changed to master

Open
#279 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
626
Forks
103
Avg merge
7d 2h
Merged PRs (30d)
5

Description

Hi

I updated from version 3.0.12 to the version 3.0.17 and ran is 2 major issues. When I run Boss update I get:

  • Filename too long. (Using the Kastri)
    ❌ ❌ Installation failed: command failed: exit status 128
    Stderr: warning: unable to access 'Demos/FCMRebooted/NotificationExtension/NotificationExtension.xcodeproj/project.xcworkspace/xcuserdata/dave.xcuserdatad/.gitattributes': Filename too long
    error: unable to create file Demos/FCMRebooted/NotificationExtension/NotificationExtension.xcodeproj/project.xcworkspace/xcuserdata/dave.xcuserdatad/UserInterfaceState.xcuserstate: Filename too long
    error: unable to create file Demos/FCMRebooted/NotificationExtension/NotificationExtension.xcodeproj/xcuserdata/dave.xcuserdatad/xcschemes/xcschememanagement.plist: Filename too long
    Updating files: 100% (2479/2479), done.
    fatal: Could not reset index file to revision 'HEAD'.

  • The branch of the main project is changed from Development to Master.
    This is pretty bad.

If I can be of any assistance. Let me know.

Sincerly,
Edward

Contributor guide

Open the contributing guide

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 reproducing Boss update from version 3.0.12 to 3.0.17 using Kastri, focusing on the reported long paths under Demos/FCMRebooted and the branch change from Development to Master. Inspect the update and Git reset behavior; done means the update completes without filename errors and preserves the selected branch.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, go
Domain
cli, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.