When you try to remove the docker image with the following command
docker rmi 6795374be8c1
Sometimes you might be facing below error:
Error response from daemon: conflict: unable to delete 6795374be8c1 (cannot be forced) - image has dependent child images
Below is the Docker command line used to find the dependent child images
| import re | |
| from unicodedata import normalize | |
| _punctuation_re = re.compile(r'[\t !"#$%&\'()*\-/<=>?@\[\\\]^_`{|},.]+') | |
| def slugify(text, delim='-'): | |
| """ | |
| Generate an ASCII-only slug. | |
| """ |
This is a guide that I wrote to improve the default security of my website https://fortran.io , which has a certificate from LetsEncrypt. I'm choosing to improve HTTPS security and transparency without consideration for legacy browser support.
I would recommend these steps only if you have a specific need for information security, privacy, and trust with your users, and/or maintain a separate secure.example.com domain which won't mess up your main site. If you've been thinking about hosting a site on Tor, then this might be a good option, too.
The best resources that I've found for explaining these steps are https://https.cio.gov , https://certificate-transparency.org , and https://twitter.com/konklone
| import requests | |
| from requests.auth import HTTPBasicAuth | |
| import re | |
| from StringIO import StringIO | |
| JIRA_URL = 'https://your-jira-url.tld/' | |
| JIRA_ACCOUNT = ('jira-username', 'jira-password') | |
| # the JIRA project ID (short) | |
| JIRA_PROJECT = 'PRO' | |
| GITLAB_URL = 'http://your-gitlab-url.tld/' |
Using py.test is great and the support for test fixtures is pretty awesome. However, in order to share your fixtures across your entire module, py.test suggests you define all your fixtures within one single conftest.py file. This is impractical if you have a large quantity of fixtures -- for better organization and readibility, you would much rather define your fixtures across multiple, well-named files. But how do you do that? ...No one on the internet seemed to know.
Turns out, however, you can define fixtures in individual files like this:
tests/fixtures/add.py
import pytest
@pytest.fixture
Two months ago, I published an open source project, which went viral by gaining 1200+ stars in the first 24 hours. As of this writing, it has attracted 5000+ stars. The project is called HTTP Prompt:
https://github.com/eliangcs/http-prompt
Here I want to share its development story.
It all began with Vertica. Not long ago, I used Vertica every day for my work. Vertica is a powerful database, but the official client (vsql) is not powerful at all. The GUI alternative, DbVisualizer, is bad as well.
| import binascii | |
| import struct | |
| class Punk(object): | |
| _END_CHUNK_TYPE = 'IEND' | |
| _PUNK_CHUNK_TYPE = 'puNk' | |
| _MAX_BYTES = 2147483647 | |
| _chunks = dict() |
JD Maturen, 2016/07/05, San Francisco, CA
As has been much discussed, stock options as used today are not a practical or reliable way of compensating employees of fast growing startups. With an often high strike price, a large tax burden on execution due to AMT, and a 90 day execution window after leaving the company many share options are left unexecuted.
There have been a variety of proposed modifications to how equity is distributed to address these issues for individual employees. However, there hasn't been much discussion of how these modifications will change overall ownership dynamics of startups. In this post we'll dive into the situation as it stands today where there is very near 100% equity loss when employees leave companies pre-exit and then we'll look at what would happen if there were instead a 0% loss rate.
What we'll see is that employees gain nearly 3-fold, while both founders and investors – particularly early investors – get dilute