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

Bump to version 0.54.1 #1790

Merged
merged 4 commits into from
Nov 30, 2021
Merged

Bump to version 0.54.1 #1790

merged 4 commits into from
Nov 30, 2021

Conversation

ivoanjo
Copy link
Member

@ivoanjo ivoanjo commented Nov 30, 2021

Preparation for releasing 0.54.1.

@ivoanjo ivoanjo added the release Official release label Nov 30, 2021
@ivoanjo ivoanjo added this to the 0.54.1 milestone Nov 30, 2021
@ivoanjo ivoanjo requested a review from a team November 30, 2021 14:21
@ivoanjo ivoanjo self-assigned this Nov 30, 2021
@ivoanjo ivoanjo merged commit 4d77d37 into master Nov 30, 2021
@ivoanjo ivoanjo deleted the bump_to_version_0.54.1 branch November 30, 2021 16:30
ivoanjo added a commit that referenced this pull request Feb 2, 2022
While being installed, the grpc gem compiles a bunch of native code.

In #1791 I documented an issue we were running into in Circle CI where
the CI worker was running out of memory because grpc was spawning
too many parallel processes for compilation.

I brought the issue up with upstream in
grpc/grpc#28244 and in
grpc/grpc#28250 a new flag was added to
enable us to limit the number of processes used.

So now we can remove our workaround of bumping the resource class
put in place in #1790 and instead use the `GRPC_RUBY_BUILD_PROCS`
flag to tell grpc how many processes to use.

Fixes #1791
ivoanjo added a commit that referenced this pull request Mar 25, 2022
While being installed, the grpc gem compiles a bunch of native code.

In #1791 I documented an issue we were running into in Circle CI where
the CI worker was running out of memory because grpc was spawning
too many parallel processes for compilation.

I brought the issue up with upstream in
grpc/grpc#28244 and in
grpc/grpc#28250 a new flag was added to
enable us to limit the number of processes used.

So now we can remove our workaround of bumping the resource class
put in place in #1790 and instead use the `GRPC_RUBY_BUILD_PROCS`
flag to tell grpc how many processes to use.

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

Successfully merging this pull request may close these issues.

None yet

2 participants