You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The fuel-core started reading environment variables recently. This introduces potential issues for our users.
One example is they use a generic PERIOD env variable to set the poa-interval which causes problems. Zsh users which use zplug are going to have PERIOD set in their environment and then fuel-core is going to have issues with it.
The best approach might just be to either switch off the environment reading by the fuel-core or make the environment empty for the spawned fuel-core process.
The text was updated successfully, but these errors were encountered:
The fuel-core started reading environment variables recently. This introduces potential issues for our users.
One example is they use a generic PERIOD env variable to set the poa-interval which causes problems. Zsh users which use zplug are going to have PERIOD set in their environment and then fuel-core is going to have issues with it.
The best approach might just be to either switch off the environment reading by the fuel-core or make the environment empty for the spawned fuel-core process.
The text was updated successfully, but these errors were encountered: