Skip to content

BUG - Updating SDK's causes broken pipe and SDK seems not to update #410

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
tlogik opened this issue Mar 27, 2025 · 2 comments
Open

BUG - Updating SDK's causes broken pipe and SDK seems not to update #410

tlogik opened this issue Mar 27, 2025 · 2 comments

Comments

@tlogik
Copy link

tlogik commented Mar 27, 2025

Hi
Thanks for this very nice tap that help immensely when working with multiple frameworks.
I really appreciate your work 🥇

My problem:
I have started getting this error when updating my NET SDK's (last week or so)
I have not experienced this before.

Error: Problems with multiple casks:
isen-ng/dotnet-sdk-versions/dotnet-sdk8-0-400: Broken pipe.
     
isen-ng/dotnet-sdk-versions/dotnet-sdk9-0-200: Broken pipe.
 
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!

The problem resides and it seems like the SDK is not updated.

Do you have any input?

@isen-ng
Copy link
Owner

isen-ng commented Mar 28, 2025

Actually I don't have a clue why this happens. A broken pipe refers to an exception thrown when trying to write to a closed socket, or when a socket is closed and a thread is interrupted.

At this point it could be:

  1. your machine is unable to reach github over the network to update the cask
  2. your machine is unable to reach microsoft servers to download the sdk package, or
  3. some other issue with homebrew

Are you still experiencing this after a day or two? or after changing a network?
Anyone else experiencing this as well?

@tlogik
Copy link
Author

tlogik commented Mar 29, 2025

I can understand that - i have no clue myself :-)

  • your machine is unable to reach github over the network to update the cask
    Not an issue
  • your machine is unable to reach microsoft servers to download the sdk package, or
    Not an issue
  • some other issue with homebrew
    Might be an issue

I think i will have to uninstall your tab and the SDK's to clear out.
Then i will reinstall the tab and try again.

For brevity i will report back :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants