A CompletableFuture object is a placeholder for a result that might not be available at present but will be available in future.

The CompletableFuture library provides mechanisms to perform asynchronous

In python, you have floats and decimals that can be rounded. If you care about the accuracy of rounding, use decimal type. If you use floats, you will have issues with accuracy.

All the examples use demical types, except for the original value, which is automatically casted as a float.

To set the context of what we are working with, let's start with an original value.

Host bitbucket.org-name1
    HostName bitbucket.org
    User git
    IdentityFile ~/.ssh/halc_bitbucket_rsa
    IdentitiesOnly yes

Host bitbucket.org-name1
    HostName bitbucket.org
 User git

Create a pytz.timezone object

>> import pytz
>> tz = pytz.timezone('Asia/Kolkata')
>> tz
<DstTzInfo 'Asia/Kolkata' HMT+5:53:00 STD>

There are two main modes to run the Let's Encrypt client (called Certbot):

• Standalone: replaces the webserver to respond to ACME challenges
• Webroot: needs your webserver to serve challenges from a known folder.

Webroot is better because it doesn't need to replace Nginx (to bind to port 80).

In the following, we're setting up mydomain.com. HTML is served from /var/www/mydomain, and challenges are served from /var/www/letsencrypt.

git fetch origin master
git reset --hard FETCH_HEAD
git clean -df

Replace all local changes and pull remote repo

Drop all tables from a database in MySQL

SET FOREIGN_KEY_CHECKS = 0; 
SET @tables = NULL;
SELECT GROUP_CONCAT(table_schema, '.', table_name) INTO @tables
  FROM information_schema.tables 
  WHERE table_schema = 'DATABASE_NAME'; -- specify DB name here.

SET @tables = CONCAT('DROP TABLE ', @tables);

To ignore changes to a file

git update-index --assume-unchanged <file>

To tracking again

git update-index --no-assume-unchanged