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
Use environment variable for switching SoX dep #669
Conversation
README.md
Outdated
This is known to work on a few major Linux distributions such as Ubuntu and CentOS 7 and macOS. | ||
If you try this on a new system and found a solution to make it work, feel free to share it by opening and issue. | ||
|
||
#### Troubleshooting: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can put this section (or the whole installation direction) into a separate file or Wiki too.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The installation section should stay in the readme. I do like the folds you are adding, which avoids cluttering part of the wiki, at least when rendered such as on github. I'd say to leave troubleshooting here, with the installation steps, but I'm ok either for this.
Since we may leave some pull requests opened for troubleshooting, the troubleshooting section may be redundant, and more work to keep up-to-date. That would be a vote for just using issues for troubleshooting.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added minor comments, but otherwise LGTM.
# Temporary fix for building in fbcode | ||
# at the moment, we have to use external sox in fbcode | ||
_BUILD_DEPS = not (_ROOT_DIR / '.use_external_sox').exists() | ||
_BUILD_SOX = 'BUILD_SOX' in os.environ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have seen more often a check for whether BUILD_SOX=1
instead of just the existence. I could imagine someone doing BUILD_SOX=0
and be surprise that sox is built.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So, for this kind of env var, there is no standard of what values are acceptable.
there are really a lot of variations like 0, 1, true, false, on, off, yes, no
etc...
and since this is env var, we should not really raise an error if the value is something unexpected.
I am open in defining values for our case, but my personal preference for binary behavior is just define variable or not.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I changed the behavior to expect 0/1 (and some others)
README.md
Outdated
This is known to work on a few major Linux distributions such as Ubuntu and CentOS 7 and macOS. | ||
If you try this on a new system and found a solution to make it work, feel free to share it by opening and issue. | ||
|
||
#### Troubleshooting: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The installation section should stay in the readme. I do like the folds you are adding, which avoids cluttering part of the wiki, at least when rendered such as on github. I'd say to leave troubleshooting here, with the installation steps, but I'm ok either for this.
Since we may leave some pull requests opened for troubleshooting, the troubleshooting section may be redundant, and more work to keep up-to-date. That would be a vote for just using issues for troubleshooting.
More downloads mean more instances of files that can't be downloaded when running circleci :) |
Closes #666? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
More downloads mean more instances of files that can't be downloaded when running circleci :)
I do not get what you mean. Can you elaborate ?
# Temporary fix for building in fbcode | ||
# at the moment, we have to use external sox in fbcode | ||
_BUILD_DEPS = not (_ROOT_DIR / '.use_external_sox').exists() | ||
_BUILD_SOX = 'BUILD_SOX' in os.environ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So, for this kind of env var, there is no standard of what values are acceptable.
there are really a lot of variations like 0, 1, true, false, on, off, yes, no
etc...
and since this is env var, we should not really raise an error if the value is something unexpected.
I am open in defining values for our case, but my personal preference for binary behavior is just define variable or not.
Codecov Report
@@ Coverage Diff @@
## master #669 +/- ##
=======================================
Coverage 88.80% 88.80%
=======================================
Files 21 21
Lines 2225 2225
=======================================
Hits 1976 1976
Misses 249 249 Continue to review full report at Codecov.
|
This was not meant as an actionable statement. :) I was just noting that if more files are downloaded when setting up circle ci, we may get more timeouts/etc. |
thanks! |
This PR changes
It check whether
BUILD_SOX
env is defined or not. (Originally, it was checking the existence of.use_external_sox
file.)It does not build codecs/SoX by default.