See how a minor change to your commit message style can make you a better programmer.
Format: <type>(<scope>): <subject>
<scope>
is optional
2teams() { | |
NOW=$(date +"%Y-%m-%d_%H%M") | |
if [ ! -z $2 ] ; then | |
echo $NOW"_"$2.mp4 | |
ffmpeg -i $1 -codec copy $NOW"_"$2.mp4 | |
else | |
echo $NOW"_teamsvid".mp4 | |
ffmpeg -i $1 -codec copy $NOW"_teamsvideo".mp4 | |
fi | |
} |
All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.
Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.
elem.offsetLeft
, elem.offsetTop
, elem.offsetWidth
, elem.offsetHeight
, elem.offsetParent
* { | |
font-size: 12pt; | |
font-family: monospace; | |
font-weight: normal; | |
font-style: normal; | |
text-decoration: none; | |
color: black; | |
cursor: default; | |
} |
// Pretend that cookies work | |
(function (document) { | |
var cookies = {}; | |
document.__defineGetter__('cookie', function () { | |
var output = []; | |
for (var cookieName in cookies) { | |
output.push(cookieName + "=" + cookies[cookieName]); | |
} | |
return output.join(";"); | |
}); |
adb shell "stop b2g" | |
adb shell "cd /data/b2g/mozilla/*.default/ && echo 'user_pref(\"devtools.debugger.forbid-certified-apps\", false);' >> prefs.js" | |
adb shell "start b2g" |
There are many times we have contributors who want to contribute to Mozilla/Gaia, but we always would meet some new friends who are not so familiar with our working flows and Git.
In spite of keep telling them how to do that every time, I think it would be better to record screencasts about how to do that step by step. By following these instructions, you can easily jump into the ecosystem of Mozilla without too many obstacles.
Please fasten your seatbelt and let's start to hack :)
First, we need to figure out what the actual error is. This is obviously frustrating given that the error message is intentionally truncating it. | |
1) SSH in to your node (various guides available for this if you're not already familiar with this). | |
2) Run this command (basically an Elastic Beanstalk wrapper command for npm install I found in a blog post [1]): | |
$ sudo /opt/elasticbeanstalk/containerfiles/ebnode.py --action npm-install 2 | |
3) Find the actual error message in the output from the npm install. | |
Once you know the error, it should hopefully be fairly obvious how to fix it. I've run into two different errors over the last couple days on Elastic Beanstalk: | |
The first was a dependency that was using the new "^X.Y.Z" version syntax, which is only supported in Node >= v0.10.26 (whereas Elastic Beanstalk only supports up to v0.10.21 as of today). The solution here was easy: hardcode a dependency version *prior* to when that dependency adopted to the new syntax. |
Bootstrap Stuffs
Icon fonts