Skip to content
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

Use Bloop fork, default to 100% domain sockets for Bloop communication #469

Merged
merged 8 commits into from
Dec 22, 2021

Conversation

alexarchambault
Copy link
Contributor

No description provided.

@SethTisue
Copy link
Contributor

io.github.alexarchambault.bleep 👀

@sjrd
Copy link

sjrd commented Dec 8, 2021

How come this is necessary? We have control over bloop. We can upstream the necessary changes there, if required.
/cc @tgodzik

@SethTisue
Copy link
Contributor

https://github.com/oyvindberg/bleep , but I don't think anyone's using blaap or bluup

@alexarchambault
Copy link
Contributor Author

alexarchambault commented Dec 9, 2021

FYI, the fork of Bloop (called bleep for now) lives here. The name collision with https://github.com/oyvindberg/bleep is unfortunate, but scala-cli/bleep might be temporary.

Some of the motivations to work from it rather than from upstream Bloop are

  • making the build bearable, by removing what makes the sbt build of Bloop unnecessarily and outrageously complex (mainly the shading and meta-meta-meta-meta build stuff)
  • actively investigating and trying to address the numerous transient errors in the tests when they happen

It's 100% my own personal initiative for now. We (VirtusLab) might soon come up with plans to ease the maintenance of Bloop, and hopefully make this fork unnecessary.

@alexarchambault alexarchambault marked this pull request as ready for review December 22, 2021 06:55
@alexarchambault alexarchambault merged commit e480ee6 into VirtusLab:master Dec 22, 2021
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

Successfully merging this pull request may close these issues.

None yet

3 participants