Skip to content

Conversation

@HeyNonster
Copy link
Contributor

@HeyNonster HeyNonster commented Mar 25, 2025

In #148 I added setpgid as a configuration option and noted that the default value is true when I actually set it to false.

That's partially due to the fact that I didn't change the default kwarg value of setpgid in clean_fork. That said, we are now explicitly passing the configuration value of setpgid to clean_fork so the default value of the kwarg is unused unless someone is calling it manually.

Perhaps it would make sense to remove the default so that if someone is calling clean_fork manually then they have to be explicit about the behavior that they want. I don't know who would be doing that though.

In Shopify#148 I added `setpgid` as a configuration option and noted that the
[default value is
true](https://github.com/Shopify/pitchfork/pull/148/files#diff-58f184d7415a8c22e56e4908527cfd1c7c28ea1c5720cf4280b2d511b25f7409R181)
when I [actually set it to
false](https://github.com/Shopify/pitchfork/pull/148/files#diff-c548fe87144e0b662fbdfa224a8e2fc458da80bb2bc04bdcddcff77d6afc5cfcR82).

That's due to the fact that I [didn't change the default kwarg value of
setpgid in
clean_fork](https://github.com/Shopify/pitchfork/blob/a68238217379fb283561f812b66fc06c8cdd8697/lib/pitchfork.rb#L139).
That said, we are now explicitly passing the configuration value of
`setpgid` to `clean_fork` so the default value of the kwarg is unused
unless someone is calling it manually. Perhaps it would make sense to remove the
default so that if someone is calling `clean_fork` manually then they
have to be explicit about the behavior that they want. I don't know who
would be doing that though.
@HeyNonster HeyNonster marked this pull request as ready for review March 25, 2025 13:27
@casperisfine casperisfine merged commit 6366979 into Shopify:master Mar 25, 2025
10 checks passed
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.

2 participants