search

fork-dev / Tracker

Bug and issue tracker for Fork for Mac
494 stars 12 forks source link

v2.40 submodule error #2071

Closed marvin-yorke closed 2 months ago

marvin-yorke commented 4 months ago

After updating to Version 2.40 some of my submodules display internal errors like ones below, while others seem to work OK. I wonder if there's something wrong with my sumbodule repos or is it indeed a bug in the app itself?

Screenshot 2024-02-21 at 13 04 27 Screenshot 2024-02-21 at 13 04 02
DanPristupov commented 4 months ago

Can you try https://cdn.fork.dev/mac/Fork-2.40.3.dmg?

marvin-yorke commented 4 months ago

I've just tried 2.39.1 again (luckily the download link on https://git-fork.com/ is outdated 😄) and it works fine in this regard. 2.40.3 from above seems to work correctly as well, thanks

anbugge-silabs commented 4 months ago

The errors look a little different on my end, but seems to be the same issue. 2.40.3 seems to fix it for me as well, thanks! image

StuWebstMW commented 4 months ago

Seeing this error with Fork 2.40.3.

🔷> XCGLogger writing log to: file:///Users/****/Library/Logs/Fork.log
🔷[AppDelegate.swift:391] > 
▄████  ████▄ █▄▄▄▄ █  █▀
█▀   ▀ █   █ █  ▄▀ █▄█     Fork 2.40.3
█▀▀    █   █ █▀▀▌  █▀▄     Git: internal
█      ▀████ █  █  █  █    Update Channel: develop
 █             █     █
  ▀           ▀     ▀        https://fork.dev
🔷[WindowManager.swift:228] > Restore workspace 'Work' with 1 windows and 5 tabs
🔷[RefreshRepositoryCommand.swift:198] > Refresh '****************' data. Updated
🔷[RefreshRepositoryCommand.swift:139] > Refresh '****************' status. Updated (1 files)
🔷[GetReferencesGitCommand.swift:63] > bt_get_references (664): 1
⚠️[FileDiffView.swift:915] > Can't read submodule diff content '****/Assets/****'
❌[FileDiffView.swift:706] > bug("refs/remotes/origin/PortObjectiveOrdering != refs/remotes/origin/HEAD")
🔷[RefreshRepositoryCommand.swift:139] > Refresh '****************' status. Updated (1 files)

Screenshot 2024-03-04 at 11 59 47 AM

DanPristupov commented 4 months ago

@StuWebstMW thank you for the bug report. Is this a critical problem for you? Can you wait until the next update?

StuWebstMW commented 4 months ago

@StuWebstMW thank you for the bug report. Is this a critical problem for you? Can you wait until the next update?

Not a critical problem -- no worries waiting. Really enjoying the feature!

StuWebstMW commented 3 months ago

Issue appears to be resolved as of v2.41.1. Thanks!

DanPristupov commented 3 months ago

@StuWebstMW thank you for the confirmation 👍