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

Content of environment variable set by another ruby library gets lost #405

Closed
maxmeyer opened this issue Jun 5, 2016 · 8 comments
Closed

Comments

@maxmeyer
Copy link
Member

maxmeyer commented Jun 5, 2016

Summary

The [middleman/middleman] project supports "stylus"-templates. This is a javascript library which is bundled into a ruby gem. The gem modifies the content of some nodejs environment variables which are required to be modified so that, "stylus" get be found.

Expected Behavior

The "stylus"-gem should work with aruba.

Current Behavior

The content of the environment variables gets lost because of aruba's isolation mechanism for environment variables.

Possible Solution

Fix the isolation mechanism

Steps to Reproduce (for bugs)

Try to migrate "middleman" to new version of aruba. Some tests will fail. See https://github.com/maxmeyer/middleman/commits/feature/upgrade-aruba-012 for this.

Your Environment

@maxmeyer
Copy link
Member Author

This might be fixed by #442

@mvz
Copy link
Contributor

mvz commented Nov 8, 2017

I can't reproduce this with the branch given. @maxmeyer can you?

There are commits in 0.12.0 that seem to address this (specifically: bc0f98b), which is confusing since this bug applies to 0.12.0.

@maxmeyer
Copy link
Member Author

maxmeyer commented Nov 13, 2017

I'm really sorry, but I don't have time to dig into code. I can only help with small tasks. I will try to concentrate on documentation and some other more "lightweight" tasks.

@mvz
Copy link
Contributor

mvz commented Nov 14, 2017

Ok, I'll look into this one then.

@stale
Copy link

stale bot commented Jan 13, 2018

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in a week if no further activity occurs.

@stale stale bot added the stale These issues were closed by stalebot and need to be reviewed to see if they're still relevant. label Jan 13, 2018
@stale
Copy link

stale bot commented Jan 20, 2018

This issue has been automatically closed because of inactivity. You can support the Cucumber core team on opencollective.

@stale stale bot closed this as completed Jan 20, 2018
@mvz mvz removed the stale These issues were closed by stalebot and need to be reviewed to see if they're still relevant. label Jan 27, 2019
@mvz mvz reopened this Jan 27, 2019
@mvz
Copy link
Contributor

mvz commented May 20, 2019

This may very well be related to #608.

@mvz
Copy link
Contributor

mvz commented Jun 16, 2019

Closing for now as no longer reproducible.

@mvz mvz closed this as completed Jun 16, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants