lilac cipher
I had issue with my flutter recently. so I downloaded latest stable version.
upon checking shorebird commands I received the following error :
error: pathspec 'e8206cf2e76e3a4e0c8e062c20bb563cae39a1f1?' did not match any file(s) known to git
Note : I'm using mac
foggy bobcat
"downloaded the latest stable version"?
Downgrading the shorebird CLI is almost never what you want. If you're having issues with a particular version of Flutter, 1: we'd would love to know what they are and 2: you can change which verison of Flutter shorebird uses using the --flutter-version parameter for shorebird release
lilac cipher
I have not downgraded but I guess you can say that I did overwrite my flutter version (not shorebird) although I actually deleted the folder and replaced with last version
so I'm guessing cache issue confusion
foggy bobcat
So you changed your system Flutter?
lilac cipher
yes
foggy bobcat
I'd try uninstalling and reinstalling shorebird. I don't think your system flutter should have any issues
I'm not sure if Flock causes any problems here
lilac cipher
from 3.24.3 to 3.24.4
foggy bobcat
You might be the first user to try it
lilac cipher
alright
though I suspect by simply changing this name e8206cf2e76e3a4e0c8e062c20bb563cae39a1f1 would resolve it but I don't know which file to update
foggy bobcat
I don't think that would do what you expect
Let's try a fresh shorebird install first
lilac cipher
how to reinstall I don't even know my shorebird path on my mac
foggy bobcat
which shorebird will tell you
lilac cipher
I think the team should consider removing older version after update cause it's been taking a lot of space 5.717.439.056 bytes (5,85 GB on disk)
eager spoke
I think the team should consider removing older version after update cause it's ...
Agreed. It's just not risen to the top of the list.
lilac cipher
after download
curl --proto '=https' --tlsv1.2 https://raw.githubusercontent.com/shorebirdtech/install/main/install.sh -sSf | bash
I got : env bash r no such file or directory
any ideas ?
eager spoke
Where are you pasting that command into?
curl --proto '=https' --tlsv1.2 https://raw.githubusercontent.com/shorebirdtech/install/main/install.sh -sSf | bash is the correct install command
And should just be possible to paste in a terminal
lilac cipher
I'm pasting in terminal
It did download I have to set the path again for terminal to recgonize
foggy bobcat
What does which shorebird show you?
lilac cipher
/Users/g-besoin/.shorebird/bin/shorebird
I mean since I only deleted the folder I thought I wouldn't have to set the path again (.zshrc or bash)
foggy bobcat
The install script should set that for you
If you cat the result of which shorebird, what do you see?
eager spoke
I'm confused as to why there are \r
\r should only happen on windows
I wonder if somehow you have your Git set up to checkout files with windows line endings
eager spoke
dos2unix isn't needed, git will manage this all itself.
what does git config --global core.autocrlf say?
lilac cipher
If you `cat` the result of `which shorebird`, what do you see?
here
eager spoke
it should be either empty or say "input"
lilac cipher
what does `git config --global core.autocrlf` say?
git config --global core.autocrlf
true
eager spoke
I belive that's the bug
getting you a man page, sec.
core.autocrlf
If you’re programming on Windows and working with people who are not (or vice-versa), you’ll probably run into line-ending issues at some point. This is because Windows uses both a carriage-return character and a linefeed character for newlines in its files, whereas macOS and Linux systems use only the linefeed character. This is a subtle but incredibly annoying fact of cross-platform work; many editors on Windows silently replace existing LF-style line endings with CRLF, or insert both line-ending characters when the user hits the enter key.
Git can handle this by auto-converting CRLF line endings into LF when you add a file to the index, and vice versa when it checks out code onto your filesystem. You can turn on this functionality with the core.autocrlf setting. If you’re on a Windows machine, set it to true — this converts LF endings into CRLF when you check out code:
$ git config --global core.autocrlf true
If you’re on a Linux or macOS system that uses LF line endings, then you don’t want Git to automatically convert them when you check out files; however, if a file with CRLF endings accidentally gets introduced, then you may want Git to fix it. You can tell Git to convert CRLF to LF on commit but not the other way around by setting core.autocrlf to input:
$ git config --global core.autocrlf input
This setup should leave you with CRLF endings in Windows checkouts, but LF endings on macOS and Linux systems and in the repository.
If you’re a Windows programmer doing a Windows-only project, then you can turn off this functionality, recording the carriage returns in the repository by setting the config value to false:
$ git config --global core.autocrlf false
git config --global core.autocrlf input is the correct setting for macos
Your git was set up to check out everything with windows line-endings I think?
Sorry that should have been "was set up". not "we set up". We don't ever change your git settings.
lilac cipher
well I applied git config --global core.autocrlf input
but It didn't help should I delete the .shorebird folder and reinstall ?
eager spoke
well I applied git config --global core.autocrlf input
but It didn't help shoul...
re-installing should likely fix, yes.
This also should make it so that other git repos you work with don't have the wrong line endings
lilac cipher
alright I'll check thanks
eager spoke
I suspect technically you can just run git checkout HEAD in any git repo to get git to fix, but re-installing Shorebird is the simple way.
I'm not sure how you ended up with the wrong setting for line number handling 🤷
Presumably having copy-pasted something from the web
lilac cipher
I shift my projects from windows to mac occasionally and when commit push I've had issue with git line ending
so I tried different commands method which resulted in this
eager spoke
Git should automatically handle line endings.
You can configure it more specifically https://docs.github.com/en/get-started/getting-started-with-git/configuring-git-to-handle-line-endings
I'm not entirely sure what "true" was doing there, but "input" (or unset) is the correct setting for Mac it seems.
the ? seems to be just the rendering of \r (which makes sense)
So somehow you were causing Shoreibrd to check out with windows lineendings 🤷
Presumably that setting.
lilac cipher
Oh no wonder then 😅 my bad thanks for the clarification