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

Fix InProcess path update #1449

Merged
merged 28 commits into from
Mar 4, 2024
Merged

Fix InProcess path update #1449

merged 28 commits into from
Mar 4, 2024

Conversation

PProfizi
Copy link
Contributor

@PProfizi PProfizi commented Mar 1, 2024

On Windows, since moving on from 2024.2.pre0, we noticed that starting a GrpcServer after an InProcess server made operations using the Cadoe fail on the InProcess server.
This is due to changes made server-side to the PATH environment variable, which is not picked-up by Python's os.environ due to it being a static map built when importing the os library for the first time. Only modification via os is picked-up by os.environ.
The problem arises because the instantiation of a GrpcServer manipulates the PATH, however the "starting" PATH is not up-to-date.
Conclusion: after starting an InProcess server, we have to manually update the PATH variable known to Python in os.environ.

See here for passing tests on Windows for 3.9.

@PProfizi PProfizi added the bug Something isn't working label Mar 1, 2024
@PProfizi PProfizi added this to the v0.11.1 milestone Mar 1, 2024
@PProfizi PProfizi self-assigned this Mar 1, 2024
@codecov-commenter
Copy link

codecov-commenter commented Mar 1, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 86.68%. Comparing base (5770566) to head (f9e248f).

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1449      +/-   ##
==========================================
- Coverage   86.71%   86.68%   -0.03%     
==========================================
  Files          81       81              
  Lines        9546     9548       +2     
==========================================
- Hits         8278     8277       -1     
- Misses       1268     1271       +3     

…" branch

Signed-off-by: paul.profizi <[email protected]>

Get the right standalone suffix when PR on a "maint/update_code_for_*" branch

Signed-off-by: paul.profizi <[email protected]>
@PProfizi PProfizi force-pushed the fix/inprocess_path_update branch from 5f8e252 to b9324d2 Compare March 1, 2024 11:10
Base automatically changed from maint/update_code_for_242_rcs_242_after_on_master to master March 4, 2024 08:48
@PProfizi PProfizi requested a review from a team as a code owner March 4, 2024 08:48
PProfizi added 3 commits March 4, 2024 10:47
Signed-off-by: paul.profizi <[email protected]>
Signed-off-by: paul.profizi <[email protected]>
Signed-off-by: paul.profizi <[email protected]>
@PProfizi PProfizi merged commit 0316972 into master Mar 4, 2024
35 of 36 checks passed
@PProfizi PProfizi deleted the fix/inprocess_path_update branch March 4, 2024 13:20
@PProfizi PProfizi modified the milestones: v0.12.1, v0.12.0 Apr 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants