** Step 1 **
Install ffmpeg with the vidstab plugin.
- OSX: Install via Homebrew -
brew install ffmpeg --with-libvidstab - Linux: download binaries here (vidstab included)
- Windows: download binaries here (vidstab included)
| import java.io.FileInputStream; | |
| import java.io.InputStream; | |
| import java.util.Iterator; | |
| import org.apache.poi.hssf.usermodel.HSSFCell; | |
| import org.apache.poi.hssf.usermodel.HSSFRow; | |
| import org.apache.poi.hssf.usermodel.HSSFSheet; | |
| import org.apache.poi.hssf.usermodel.HSSFWorkbook; | |
| import org.apache.poi.ss.usermodel.Row; |
| #include <stdio.h> | |
| void DumpHex(const void* data, size_t size) { | |
| char ascii[17]; | |
| size_t i, j; | |
| ascii[16] = '\0'; | |
| for (i = 0; i < size; ++i) { | |
| printf("%02X ", ((unsigned char*)data)[i]); | |
| if (((unsigned char*)data)[i] >= ' ' && ((unsigned char*)data)[i] <= '~') { | |
| ascii[i % 16] = ((unsigned char*)data)[i]; |
| # Get IAM Role name from Instance Profile Id | |
| curl http://169.254.169.254/latest/meta-data/iam/info | |
| # Get credentials | |
| curl http://169.254.169.254/latest/meta-data/iam/security-credentials/<role-name> | |
| # More info | |
| http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-metadata.html | |
| import os | |
| from azure.common.credentials import ServicePrincipalCredentials | |
| from azure.mgmt.network import NetworkManagementClient | |
| subscription_id = os.environ.get( | |
| 'AZURE_SUBSCRIPTION_ID', | |
| '11111111-1111-1111-1111-111111111111') # your Azure Subscription Id | |
| credentials = ServicePrincipalCredentials( | |
| client_id=os.environ['AZURE_CLIENT_ID'], |
** Step 1 **
Install ffmpeg with the vidstab plugin.
brew install ffmpeg --with-libvidstab| # serverless.yml | |
| service: | |
| name: myService | |
| awsKmsKeyArn: arn:aws:kms:us-east-1:XXXXXX:key/some-hash # Optional KMS key arn which will be used for encryption for all functions | |
| frameworkVersion: ">=1.0.0 <2.0.0" | |
| provider: | |
| name: aws |
If you're encountering ping github.com failing inside WSL with a Temporary failure in name resolution, you're not alone — this has been a long-standing issue, especially when using VPNs or corporate networks.
This issue is now fixed robustly with DNS tunneling, which preserves dynamic DNS behavior and avoids limitations like WSL’s former hard cap of 3 DNS servers in /etc/resolv.conf.
DNS tunneling is enabled by default in WSL version 2.2.1 and later, meaning that if you're still seeing DNS resolution issues, the first and most effective fix is simply to upgrade WSL. Upgrading WSL updates the WSL platform itself, but does not affect your installed Linux distributions, apps, or files.
To upgrade WSL, follow these steps,
#[no_mangle]
pub extern fn double_input(input: i32) -> i32 {
input * 2
| AWSTemplateFormatVersion: '2010-09-09' | |
| Description: AWS CloudFormation Sample Template for CFN Init | |
| Parameters: | |
| KeyName: | |
| Description: Name of an existing EC2 KeyPair to enable SSH access to the instances | |
| Type: AWS::EC2::KeyPair::KeyName | |
| ConstraintDescription: must be the name of an existing EC2 KeyPair. | |
| SSHLocation: | |
| Description: The IP address range that can be used to SSH to the EC2 instances | |
| Type: String |