Eftakhairul's World

Github’s “repository not found” error and How to fix it

Eftakhairul Islam — Fri, 07 Apr 2023 17:51:56 +0000

GitHub is an excellent platform for managing code repositories and collaborating with other developers. One of the great features of GitHub is Github Action, which automates your workflow for private and public repositories. However, recently, I noticed that GitHub Action is throwing an error while using GITHUB_TOKEN in the private repo. This issue is not occurring for the private repos under the Enterprise Plan. In my case, it was the private repo under the Free Plan. The error looks like below:


Fetching the repository
  /usr/bin/git -c protocol.version=2 fetch --no-tags --prune --progress --no-recurse-submodules --depth=1 origin +a6f81a034bf482d652ccb6d1609f1a25d8ec947b:refs/remotes/pull/5/merge
  remote: Repository not found.
  Error: fatal: repository 'https://github.com/eftakhairul/helloworld/' not found
  The process '/usr/bin/git' failed with exit code 128
  Waiting 18 seconds before trying again
  /usr/bin/git -c protocol.version=2 fetch --no-tags --prune --progress --no-recurse-submodules --depth=1 origin +a6f81a034bf482d652ccb6d1609f1a25d8ec947b:refs/remotes/pull/5/merge
  remote: Repository not found.
  Error: fatal: repository 'https://github.com/eftakhairul/helloworld/' not found
  The process '/usr/bin/git' failed with exit code 128
  Waiting 11 seconds before trying again
  /usr/bin/git -c protocol.version=2 fetch --no-tags --prune --progress --no-recurse-submodules --depth=1 origin +a6f81a034bf482d652ccb6d1609f1a25d8ec947b:refs/remotes/pull/5/merge
  remote: Repository not found.
  Error: fatal: repository 'https://github.com/eftakhairul/helloworld/' not found
  Error: The process '/usr/bin/git' failed with exit code 128

Why?

I found an issue reported on May 22, 3020. The issue is probably due to the default token: GITHUB_TOKEN doesn’t have permission to checkout the private repo. It doesn’t work even if you setup the permissions to GITHUB_TOKEN to access other private repo. Right now, the issue is closed. Multiple users reported that they were having the same issues. Today I got the same error.

Solutions

I don’t know whether the Github will fix it or not. However, there is a work around to bypass the issue. I will explain that one now.

Steps:

1. Generate your own Persona access token with the proper permissions. Go to: settings > Developer settings under your account & create Personal access tokens. Click on Tokens (classic)

With the following permissions

2. Add the token to the repo’s Secrets. Go to: Repo’s Settings > Secrets and variables > Actions

3. Update your Action’s workflow steps


- uses: actions/checkout@v2
  with:
    token: ${{ secrets.YOUR_CUSTOM_GITHUB_TOKEN }}

Re-run your Github’s workflow again. It will work. Happy Hacking

The post Github’s “repository not found” error and How to fix it first appeared on Eftakhairul's World.

Inspect HTTP Request and Response in Golang

Eftakhairul Islam — Sun, 22 May 2022 04:49:29 +0000

Golang is getting popular for writing a web applications. One of the core concepts of this web application is handling requests and responses. In Golang, net/http package from the standard library provides all HTTP requests and responses mechanisms.

As a developer, you often print this HTTP request or the response for debug purposes. net/http/httputil package has two excellent methods DumpRequest for printing pretty request. and DumpResponse methods for printing pretty response. Let’s look at examples…

Example of httputil.DumpRequest :


requestDump, err := httputil.DumpRequest(req, true)
if err != nil {
fmt.Println(err)
}
fmt.Printf("%q", requestDump)

Output:


POST / HTTP/1.1
Host: www.example.com
Accept: */*
Content-Length: 6
Content-Type: application/x-www-form-urlencoded
User-Agent: curl/7.71.1

foo=bar

It prints the whole request object. If you don’t want the body, change the boolean argument from true to false in httputil.DumpRequest().

You can also print only the body of the request. Just read the body from buffer.


buf, err := ioutil.ReadAll(req.Body)
if err != nil {
	fmt.Println(err) //log it
	return
}
fmt.Printf("%+v", string(buf))

Remember, you will have to write it back after reading it from the buffer; neither request will fail.

req.Body = ioutil.NopCloser(bytes.NewBuffer(buf))

Example of httputil.DumpResponse:


dumpResponse, err := httputil.DumpResponse(resp, true)
if err != nil {
	fmt.Println(err)
}

fmt.Printf("%q", dumpResponse)

Output:


HTTP/1.1 200 OK
Accept-Ranges: bytes
Age: 357425
Cache-Control: max-age=604800
Content-Type: text/html; charset=UTF-8
Date: Fri, 25 Feb 2022 06:48:03 GMT
Etag: "3247526947+gzip"
Expires: Fri, 04 May 2022 06:48:03 GMT
Last-Modified: Thu, 03 May 2022 07:18:26 GMT
Server: ECS (bsa/EB18)
Vary: Accept-Encoding
X-Cache: HIT

 
 
    Example Domain 
    charset="utf-8" /> 
    ="Content-type" content="text/html; charset=utf-8" /> 
    name="viewport" content="width=device-width, initial-scale=1" /> 
 ...

The post Inspect HTTP Request and Response in Golang first appeared on Eftakhairul's World.

Build SQL update query for HTTP Patch request in Golang

Eftakhairul Islam — Sun, 20 Mar 2022 19:54:42 +0000

It seems pretty straightforward to implement HTTP Patch request. The handler receives the request, unmarshals the body, validates the payload, sanitizes it and then sends it to persist layer for persisting into the Database. Let’s look into an example.

For example, we are updating a user resource.


type UserResource struct {
    FirstName   string `json:"first_name,omitempty" db:"first_name"`
    LastName    string `json:"last_name,omitempty"  db:"last_name"`
    Age         int    `json:"age,omitempty"        db:"age"`
    Email       string `json:"email,omitempty"      db:"email"`
}

We expect the user to send partial fields to update the resource in an HTTP Patch request. WE use omitempty tag in our UserResource, which means the user resource object might be missing multiple properties; thus, we cannot just prepare a statement with hard-coded fields and placeholders. I will have to build it dynamically, and this is where all the complexity started.

One easy solution is using an ORM. For example, GORM has a function: Updates. It supports updating DB with struct or map[string]interface{}, when updating with struct, it will only update non-zero fields by default and updating with map, you can pass selective fields.

db.Model(&user).Updates(map[string]interface{}{"first_name": "John", "last_name": "Doe", "age": 18})

What if you didn’t use any ORM in your project. Well, the only solution is now to make SQL update queries dynamically. You might use string manipulation or a complex reflect package to build the query. When I was looking for potential solution, I found an excellent open-source library: https://github.com/imdario/mergo

Mergo merged structs and maps in Golang. By using the transformer WithOverride, you can overwrite the values of the destination object.


if err := mergo.Merge(&dst, src, mergo.WithOverride); err != nil {
  // handling error
}

In our case, we can retrieve the user resource from DB, override the user resource with request data and persists the user resource object again.


var userRequest UserResource
json.Unmarshal([]byte(`{"LastName": "Smith"}`), &userRequest)

// Retrieve user resource from DB 
user, err := RetiveUser(userId) 


// Override user with partial userRequest object value
if err := mergo.Merge(&user, userRequest, mergo.WithOverride); err != nil {
	// handle error
}

// Update user in DB again
if err := UpdateUser(user); err != nil {
	// handle error
}

Inside UpdateUser function, you will not have to write SQL queries dynamically. You write a regular update query with all fields. Because by merging the userRequest object with the user object, you have all the fields and values.

The post Build SQL update query for HTTP Patch request in Golang first appeared on Eftakhairul's World.

Upgrade to PHP 7.4 from PHP 7.2

Eftakhairul Islam — Sat, 05 Jun 2021 19:17:17 +0000

This is the upgrade of my previous post . Previously, I showed how to upgrade to 7.2. Now, it’s time for one more jump to new version.

The latest version of PHP comes with a couple of changes

Arrow functions (Adds short closures)
Preloading to improve performance
Typed properties in classes
Improved type variance
The null coalescing assignment operator as a shorthand
FFI for better extension development in PHP
Underscores can be used to format numeric values
Spread operator in arrays
Opcache Preloading

More details: http://php.net/releases/7_4_0.php

Even it’s your first time, just follow the following steps. First, update your system.


sudo apt-get update
sudo apt-get install python-software-properties

Second, add Ondřej’s PPA to the system’s Apt sources:

sudo LC_ALL=C.UTF-8 add-apt-repository ppa:ondrej/php

Update your local package cache again

sudo apt-get update

Now Install PHP 7.4

sudo apt-get install php7.4

In order to version check, run:
php -v

You also need to install some modules

sudo apt-get install libapache2-mod-php7.4 php7.4-cgi php7.4-cli php7.4-common php7.4-curl php7.4-gd php7.4-imap php7.4-intl php7.4-json php7.4-ldap php7.4-mbstring php7.4-mysql php7.4-opcache php7.4-pspell php7.4-readline php7.4-soap php7.4-xml php7.4-zip

One more module for Nginx server

sudo apt-get install php7.4-fpm

You can check whether the installation is successful or not.

php-fpm7.4 -v

Attention:

You can ignore the following steps if you install PHP 7.4 for the first time.

For Nginx Server

Update the unix socket path at default configuration as well as other configurations.

/var/run/php/php7.4-fpm.sock

Check the Nginx configuration

sudo nginx -t

Restart the Nginx server

sudo service nginx restart

For Apache server

You need to disable the old version on Apache and tell Apache to use PHP 7.4.

sudo a2dismod php7.2  
sudo a2enmod php7.4

Restart the Apache server

sudo /etc/init.d/apache2 restart

Last Part, update the php ini for better performance in web application

Update the following values in php.ini. php.ini located in /etc/php/7.4/fpm/php.ini for Nginx and located in /etc/php/7.4/apache2/php.ini for apache.

upload_max_filesize = 32M 
post_max_size = 48M 
memory_limit = 256M 
max_execution_time = 600 
max_input_vars = 3000 
max_input_time = 1000

Now, you can remove the old version

sudo apt-get install ppa-purge
sudo apt-get purge php7.2-common

Happy hacking

The post Upgrade to PHP 7.4 from PHP 7.2 first appeared on Eftakhairul's World.

Backup your Seagate Personal Cloud to pCloud

Eftakhairul Islam — Sun, 08 Nov 2020 00:29:06 +0000

I was looking for a proper solution to take the backup of my Seagate Personal Clould (NAS server) to another cloud storage. It’s just an extra layer of backup in case any hazard occurs in my home. Seagate Personal cloud already has some built-in supports for well known cloud services likes Dropbox, One drive and others. But, it doesn’t have the support for the cloud service I use: pCloud. I am big fan of pCloud because of it life time pricing policy. I am not marketing for it, I just use it.

The whole solution will be something like below:

My all device will be connected to Segete NAS where I will keep all of my primary backups. Then, Seagate personal cloud will sync with secondary cloud backup service: pCloud. I was planning to write a custom script. But, then after some googling, I found that both pCloud and Seagete support WebDAV protocol.

What is WebDAV protocol?

WebDAV stands for Web Distributed Authoring and Versioning. It’s an extension to HTTP that lets clients edit content remotely. Basically, WebDAV enables a web server to act as a file server.

It uses stand HTTP headers, methods and ports (443 for SSL/TLS) for create, move, edit and delete files and folders.

How did I implement it?

Steps:
1. SSL/TLS enabled pCloud WebDAV url is webdav.pcloud.com

2. Log in into your Seagate personal cloud and navigate to Backup Manager

3. Configure pCloud url with usernamae and password.

Select following options into Backup Wizard

Click on Next. Configure WebDAV URL in destination with username and password.

Click on Next.

It will connect to pCloud and will list all the folders of source (Seagate personal cloud) & designation (pCloud).
You will have to choice folder of source you sync with destination folder.

Click on Next.
On next window, it will ask whether you want delete file from destination folder or not. Keep uncheck if you want. Click On Next again.

Now you will have to select backup mode.

Manual: you will have to click that button manually to take the backup. Better for one time backup.
Schedule: You can take the backup periodically based on time, day and month.

In this case, I choose weekly schedule backup. I want to take backup every Friday night.

Click On Next. It will show summary.

Click on Finish. You are done.

It will start immediately as well as it will take backup on every week.

What are the cloud storage services that support WebDAV protocol?

1&1 Online-Speicher (DSL)	https://sd2dav.1und1.de
1&1 Online-Speicher (Webhosting)	https://webdav.office.1und1.de
blaucloud	https://{username}.blaucloud.de/remote.php/webdav
Box	https://dav.box.com/dav
Cubby	https://webdav.cubby.com
freenetcloud	https://webmail.freenet.de/webdav
GMX MediaCenter	https://webdav.mc.gmx.net
HiDrive	https://webdav.hidrive.strato.com
IceDrive	https://webdav.icedrive.io/
IDrive	https://dav.idrivesync.com
kDrive	https://connect.drive.infomaniak.com
Koofr	https://app.koofr.net/dav/Koofr
MagentaCLOUD	https://webdav.magentacloud.de
Mail.Ru	https://webdav.cloud.mail.ru
Nextcloud	https://{host}/{path}/remote.php/dav/files/{username} or https://{host}/{path}/remote.php/webdav
ownCloud	https://{host}/{path}/remote.php/webdav
pCloud	https://webdav.pcloud.com
Seafile (self-hosted)	https://{host}/{path}/seafdav
STACK	https://{username}.stackstorage.com/remote.php/webdav
Strato HiDrive	https://webdav.hidrive.strato.com
Syncwerk (formerly Seafile.de)	https://app.syncwerk.com/seafdav
WEB.DE Online-Speicher	https://webdav.smartdrive.web.de
wölkli	https://cloud.woelkli.com/remote.php/webdav
Yandex.Disk	https://webdav.yandex.com
Mailbox.org	https://dav.mailbox.org/servlet/webdav.infostore/

Note: Some cloud services may disable WebDAV access when two factor authentication is enabled. pCloud does that too.

Happy Hacking

The post Backup your Seagate Personal Cloud to pCloud first appeared on Eftakhairul's World.

Logging with Winston in your Node.js application

Eftakhairul Islam — Wed, 21 Aug 2019 05:15:39 +0000

Logging is an essential part of application. According to Twelve-Factor App methodology it’s the XI factor of application development. A proper logging gives you a valuable insite of your application. In Node.js application, it is always suggested to use logging libraryrather than just using console.log in productione environment. Log4js, Bunyan , and Winston are the best logging libraries among other libraries. I am not going to discuss here which is the best logging library among them.

In this tutorials I will cover the Winston logging library with Morgan logger middleware. Winston is most popular, simple and versatile logging library for NodeJs application. You can easily customize it, format the log messages and send them any internal or cloud log management tools.

Logging with Winston

Let’s create a custom nodejs app with Winston logging library. Create a blank package.json file that automatically accepts all the defaults without prompting.

mkdir ~/myapp 
cd ~/myapp
npm init -y

Install Winston

npm install  winston --save

Now, create a config folder file with logger.js file which contains the winston configuraiton.

mkdir ~/myapp/config
touch  ~/myapp/config/logger.js

Let’s talk about a little bit about Winston logging library. It supports

Pre-defined levels as well as custom error levels
Multiple transports as well as custom transport
Handle exceptions
Different log formats as well as custom formats

Transport

Transport is a concept that stores or output the logs into file, console, stream or cloud platform over http. It’s loaded as module while creating an instance of a winston logger. You can use multiple transports at different log level at the same time. What it means actually you can output to console and send to http at the same time. Built-in available transports are Console, File, Http and Stream. There are also some aditional community transports available.

Logging level

Logging level is part of transport which indicate the minimum logging priority that transport will listen out for. Logong level is denoted the by integer number and it follows npm logging levels.

0: error
1: warn
2: info
3: verbose
4: debug
5: silly

For example, you configure transport with setting logging level to debug: 4.This means, it will log levels

4 (debug)
3 (verbose)
2 (info)
1 (warn)
0 (error)

If you set the logging level to info then the logs will show only info messages as well as less than or equal to this level, You wont see the debug or verbose messages. This helps to avoid clutter in the logs and prevents too much info being shown in the logs in a production environment.

Next, define a logger with a very basic winston configurations.

//~/myapp/config/logging.js
// Import modules
const winston = require('winston');

// Logger configuration
const logConfiguration = {
    exitOnError: false,
    transports: [
        new winston.transports.Console({
            level: 'info'
        }),
        new winston.transports.File({
            level: 'error',
            filename: `./logs/app.log`
        })
    ]
};

// Create the logger
const logger = winston.createLogger(logConfiguration);

// Export the logger
module.exports = logger;

Let me explain what properties I configured here. In logConfiguration object, I initiated two transports: console with level: info and file with level: error. File tranporter will log only errors into log/app.log file at application root. Console transporter will log upto info or any logs less than info level. I also set exitOnError to false. Means it will not exit after logging an uncaughtException.

Now, I am going to use the logger in my app.js.
//~/myapp/app.js
const logger = require('./config/logger');
logger.info("hello world!");

It print hello world! in console as below. It doesn’t add any log into app.log file because of log level.

{"message":"hello world!","level":"info"}

Now, we print another log with error level.

logger.error("error occured");

This time, you see following message in console as well into app.log file.

{"message":"hello world!","level":"error"}

Custom log formats

Another important advantage of Winston is customizing log message format as well as creating your own custom format. By default it supports JSON formatting, coloring log output, and the ability to change with formats. You can add different message formats to diferent transports. Let’s start with an example that adds a timestamp, label, colorizes the level and message, lowercase message content and prints using the template [level] [timestamp-label]: message.

// Import modules
const { createLogger, format, transports } = require('winston');
const { combine, timestamp, label, colorize, printf } = format;

const customFormat = printf(({ level, message, label, timestamp }) => {
  return `$[${level}] [${timestamp}-${label}] ${message.toLowerCase()}`;
});

// Logger configuration
const logConfiguration = {
  format: combine(
    label({ label: 'Custom APP log!' }),
    timestamp(),
    colorize({ all: true }),  
    customFormat
  ),
  transports: [
    new transports.Console({ level: 'info' })
  ],
  exitOnError: false,
};

// Create the logger
const logger = createLogger(logConfiguration);

Now if you try again logger.info("HELLO WORLD"), you will see following message into console.

More details on format: See Winston Format

Send log message to Cloud platform

There are multiple cloud platforms with paid and limited free subscribtions where you can send log messages. I used couple of them, but for this tutorials I chose Papertrail.

// import modules
const winston = require('winston');

// Install papertail: npm install winston-papertrail --save
// Requiring `winston-papertrail` will expose  
require('winston-papertrail').Papertrail;

const winstonPapertrail = new winston.transports.Papertrail({
        level: 'info',
        colorize: true, 
        host: 'logs.papertrailapp.com', 
        port: 12345 });
 
// Logger configuration 
const logConfiguration = { 
   exitOnError: false, 
   transports: [winstonPapertrail] 
};


// Create the logger 
const logger = winston.createLogger(logConfiguration); 

// Export the logger 
module.exports = logger;

I almost covered everything about Winston as a proper logger. One more thing I want to add using winston with morgan.

Why Morgan?

Morgan is HTTP request middleware logger for Node.js. It basically simplifies the process of request logging. Most of the time it’s used with Winston to consolidate HTTP request data logs. Morgan supports a handful of pre-defined logged formats with well-know names/structures: combined, common, dev, short, tiny as well as custom format. Beside the format, it also accepts following properties as into its optiont object.

immediate: set it to true in order to log request even server crashes.
skip: skip log outputs based on some custom logic
stream: Output stream for writing log lines. Defaults to process.stdout

Let’s look at an example of Morgan with Winston logger into an express based Node.js application. By default, it outputs to the console, so let’s define a stream function into Winston so that we can transfer morgan’s output into the Winston log files.

//~/myapp/config/logging.js
...

logger.stream = {
  write: function(message, encoding) {
    logger.info(message);
  },
};


// Export the logger 
module.exports = logger;

In app.js (Example based on express framework)

const express = require('express');
const bodyParser = require('body-parser');
const app = express();


const morgan = require('morgan');
const logger = require('./config/logger');

app.use(bodyParser.json());
app.use(bodyParser.urlencoded({
    extended: true
}));

app.use(morgan('combined', {
    immediate: true,
    stream: logger.stream
}));

...

Morgan supports token. To know more details token and logged format: Morgan NPM Package documentation

In this tutotial, I mostly focused on Winston logger with Morgan HTTP middleware for simplicity. I mentioned before that there are more better logger libraries availabe based on different features. Choice one that best fits into your application. Happy Hacking.

The post Logging with Winston in your Node.js application first appeared on Eftakhairul's World.

SSH to AWS EC2 instance without key pairs

Eftakhairul Islam — Tue, 18 Sep 2018 06:39:28 +0000

This is a common issue for the developers to access ec2 instances by username and password authentication. It requires a few steps to do that.

First, login as root using the key pairs.
Second, create a user

sudo adduser username

Third, you need to grant root level permission to the new user

visudo

Add following line

username ALL=(ALL) ALL

Forth, edit /etc/ssh/sshd_config setting and then set PasswordAuthentication to yes. Open the vim or nano

sudo vim /etc/ssh/sshd_config

Find and set PasswordAuthentication to yes

PasswordAuthentication yes

Finally, restart the ssh daemon

For Ubuntu

sudo service ssh restart

For CentOS

sudo service sshd restart

Done, now you are able to login into your ec2 instance without the key pairs. Happy Hacking

The post SSH to AWS EC2 instance without key pairs first appeared on Eftakhairul's World.

Upgrade PHP from 7.0 to 7.2

Eftakhairul Islam — Fri, 14 Sep 2018 06:20:30 +0000

A long ago, I wrote about how to upgrade to 7.0. PHP 7.2 is released. Now, it’s the time again to upgrade to the new version.

The latest version of PHP comes with a couple of changes

More details: http://php.net/releases/7_2_0.php

Even it’s your first time, just follow the following steps. First, update your system.

sudo apt-get update
sudo apt-get install python-software-properties

Second, add Ondřej’s PPA to the system’s Apt sources:

sudo LC_ALL=C.UTF-8 add-apt-repository ppa:ondrej/php

Update your local package cache again

sudo apt-get update

Now Install PHP 7.2

sudo apt-get install php7.2

In order to version check, run: php -v

You also need to install some modules

sudo apt-get install libapache2-mod-php7.2 php7.2-cgi php7.2-cli php7.2-common php7.2-curl php7.2-gd php7.2-imap php7.2-intl php7.2-json php7.2-ldap php7.2-mbstring php7.2-mysql php7.2-opcache php7.2-pspell php7.2-readline php7.2-soap php7.2-xml php7.2-zip

One more module for Nginx server

sudo apt-get install php7.2-fpm

Attention:

You can ignore the following steps if you install PHP 7.2 for first time.

For Nginx Server

Update the unix socket path at default configuration as well as other configurations.

/var/run/php/php7.2-fpm.sock

estart the Nginx server

sudo service nginx restart

For Apache server

You need to disable the old version on Apache and tell Apache to use PHP 7.2.

sudo a2dismod php7.0  
sudo a2enmod php7.2

Restart the Apache server

sudo /etc/init.d/apache2 restart

Now, you can remove the old version.

sudo apt-get install ppa-purge
sudo apt-get purge php7.0-common

Happy hacking

The post Upgrade PHP from 7.0 to 7.2 first appeared on Eftakhairul's World.

GIT Squashing and open source contribution

Eftakhairul Islam — Mon, 12 Feb 2018 21:09:34 +0000

Never thought that GIT squashing would be that important for the open source contribution. I was contributing to an open source project. I finished the feature and created a pull request. Surprise!!! the community didn’t accept my pull request. Okay. … It was not rejected because of my wrong implementation or bad code. It was rejected just because of my commit history.

So, in the open source project, this is kinda common practice to use one commit message per feature/branch per push. It actually makes sense when you look at the commit history of an open source project. Nobody wants to see your code noises in the commit history. Basically, you will have to squash multiple commits into one commit before creating pull request.

What is GIT Squashing?

Normally, we do commit as we progress. But, we don’t want to push all of them into the repository. GIT squashing compress down multiple commits into one single meaningful commit. Sometime, we do some unnecessary commits or we find some commits that should be belong to the same logical change-set. GIT squashing enables rewrite the history by keeping one commit message, and squashing those subsequent commits into the previous one.

In this tutorial we will use GIT interactive rebase command for squashing. We will use squash and fixup.

squash (s for short), which melds the commit into the previous one (the one in the line before)
fixup (f for short), which acts like “squash”, but discards this commits message

Let’s go through an example. We have five commits in log history.

bbf19a9 my 1st commit
9added2 my 2nd commit
1a8482a my 3rd commit
68782bd my 4th commit
3c9956e my 5th commit

We want squash the last three commits (3c9956e to 1a8482a) into the first commit (bbf19a9 )and discard the forth commit from the last (9added2). You need to run the command: interactive (-i for short ) rabsae

git rebase -i HEAD~5

It will show a list of each commit as below in your default git editor (either nano or vim)

pick bbf19a9 my 1st commit
pick 9added2 my 2nd commit
pick 1a8482a my 3rd commit
pick 68782bd my 4th commit
pick 3c9956e my 5th commit

# Rebase 187a597..3c9956e onto 187a597 (5 commands)
#
# Commands:
# p, pick = use commit
# r, reword = use commit, but edit the commit message
# e, edit = use commit, but stop for amending
# s, squash = use commit, but meld into previous commit
# f, fixup = like "squash", but discard this commit's log message
# x, exec = run command (the rest of the line) using shell
# d, drop = remove commit
#
# These lines can be re-ordered; they are executed from top to bottom.
#
# If you remove a line here THAT COMMIT WILL BE LOST.
#
# However, if you remove everything, the rebase will be aborted.
#
# Note that empty commits are commented out

The above screen already describes with all the options and what exactly you have to use based on our requirement. In our case, we use squash and fixup.

pick bbf19a9 my 1st commit
fixup 9added2 my 2nd commit
squash 1a8482a my 3rd commit
squash 68782bd my 4th commit
squash 3c9956e my 5th commit

You can also use s as short for squash and f as short for fixup.

Save and exit the editor. It will show another screen

# This is a combination of 5 commits.
# This is the 1st commit message:

my 1st commit

# The commit message #2 will be skipped:

# third commit

# This is the commit message #3:

my 3rd commit

# This is the commit message #4:

my 4th commit

# This is the commit message #5:

my 5th commit

# Please enter the commit message for your changes. Lines starting
# with '#' will be ignored, and an empty message aborts the commit.
#
# Date: Sat Nov 11 18:29:04 2017 -0500
#
# interactive rebase in progress; onto 187a597
# Last commands done (5 commands done):
# s 68782bd fifth commit
# s 3c9956e sixth commit
# No commands remaining.
# You are currently rebasing branch 'master' on '187a597'.
#
# Changes to be committed:
# modified: indext.html
#

The above screen describes what would be your new modified and composite commit message. You can leave as it is or you can write your new commit message. If you leave as it, all commit messages will appear except the commit: my 2nd commit.

If you check git log, you will get one commit with all of your changes

git log

When you shouldn’t do this?

Don’t sqaush or rewrite the history if they have been already push to public repository.

Some developers have different thought, they don’t like to squash because the commits are well-structured a series of commits which represents a logical series of meaningful changes. The main trick is not squashing everything into one gigantic commits, rather clean up or remove the unnecessary commits from git change history.

Tips:

1. To halt the squashing middle of rebase, simple run this command: git rebase --abort
2. To see git log in a cleaner way: git log --pretty=oneline
3. To rewrite the commit message, use reword rather than squash or fixup.
4. Just to change the last commit message: git commit --amend

Helpful links:

https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History
http://stackoverflow.com/questions/2563632/how-can-i-merge-two-commits-into-one

The post GIT Squashing and open source contribution first appeared on Eftakhairul's World.

Transfer tokens from orderbook.io to MyEtherWallet (MEW) wallet

Eftakhairul Islam — Sun, 17 Dec 2017 05:48:47 +0000

It’s always suggested to transfer tokens to a new wallet that supports ERC20 tokens. MyEtherWallet (aka MEW) is an ERC20-compliant wallet and you can hold any ERC20 tokens there.

In this tutorial, I will cover how to transfer tokens from orderbook.io to MyEtherWallet. I used Hacken Token (HKN) as example and wrote this tutorial for newbies.

Step 1: You can skip this step if you already have a MyEtherWallet wallet.

To create wallet, please visit any of following links:

Text tutorials: https://www.cryptocompare.com/wallets/guides/how-to-use-myetherwallet/
Video tutorials: https://www.youtube.com/watch?v=phht73IvUDI

Step 2: Copy your Ethereum address from MyEtherWallet wallet

Login to MyEtherWallet wallet
Copy your Ethereum address (Account Address)

(NB. Don’t use the address in the picture above, use your own Ethereum address)

Step 3: Withdraw tokens from orderbook.io

1. Login to orderbook.io

2. Navigate to BALANCES tab and click on the Withdraw icon on the right of the token.

3. You will get two inputs fields. Type your Etherium address in the recipient field and the amount you want to withdraw in the amount field. Click on CONFIRM and you are done. Orderbook charged me 2 HKN fees for withdrawing HKN tokens. For different tokens, fees could be different.

5. You will receive a verification code through your email/phone. A pop-up will come for the final withdraw confirmation, you will have to type verification code as below and then click on CONFIRM.

Step 4: Load token to MyEtherWallet

1. Again, login to your MyEtherWallet

2. Click on Add Custom Tokens

3. Type your token’s contact address, symbol and decimals. And, then click on “Save” button as below. Following example is based on Hacken Token (HKN )

You can also follow this tutorial: https://myetherwallet.github.io/knowledge-base/send/adding-new-token-and-sending-custom-tokens.html

Finally, Click on Load Tokens. You will see your token balance. BTW, It might take some times to finish your transaction, so don’t be panic.. just wait.

The post Transfer tokens from orderbook.io to MyEtherWallet (MEW) wallet first appeared on Eftakhairul's World.