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

Avoid incorrectly setting LD_LIBRARY_PATH #408

Merged
merged 3 commits into from
Oct 16, 2024

Conversation

blast-hardcheese
Copy link
Contributor

Why

When I split out the binary Python wrapper, I misread that LD_LIBRARY_PATH should be set in all cases, not just the legacy case.

What changed

Increasing readability and addressing the underlying bug. Also removed the REPLIT_RTLD_LOADER = "1" check as the flag has been rolled out and burned in, and is unlikely to get rolled back.

Test plan

Attempt to fork and run one of the test cases supplied by support.

Rollout

Describe any procedures or requirements needed to roll this out safely (or check the box below)

  • This is fully backward and forward compatible

@blast-hardcheese blast-hardcheese requested a review from a team as a code owner October 16, 2024 17:00
@blast-hardcheese blast-hardcheese requested review from vlinkz and removed request for a team October 16, 2024 17:00
@airportyh
Copy link
Collaborator

When do we use the shell wrapper vs the binary wrapper?

@blast-hardcheese
Copy link
Contributor Author

@airportyh only in pip and poetry wrappers. Once Python 3.8 is EOL then #397 can be merged and the shell wrapper can be cleaned up.

@blast-hardcheese blast-hardcheese merged commit e898a8c into main Oct 16, 2024
1 check passed
@blast-hardcheese blast-hardcheese deleted the dstewart/bug/python-wrapper-legacy-channel branch October 16, 2024 17:49
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.

3 participants