vim-wordmotion - More useful word motions for Vim
NvChad - An attempt to make neovim cli functional like an IDE while being very beautiful, blazing fast startuptime ~ 0.06 secs
LazyVim - Neovim config for the lazy
vim-wordmotion - More useful word motions for Vim
NvChad - An attempt to make neovim cli functional like an IDE while being very beautiful, blazing fast startuptime ~ 0.06 secs
LazyVim - Neovim config for the lazy
version: "3" | |
services: | |
# configuration manager for NiFi | |
zookeeper: | |
hostname: myzookeeper | |
container_name: zookeeper_container_persistent | |
image: 'bitnami/zookeeper:3.7.0' # latest image as of 2021-11-09. | |
restart: on-failure | |
environment: | |
- ALLOW_ANONYMOUS_LOGIN=yes |
import logging | |
import multiprocessing | |
import time | |
import mplog | |
FORMAT = '%(asctime)s - %(processName)s - %(levelname)s - %(message)s' | |
logging.basicConfig(level=logging.DEBUG, format=FORMAT) | |
existing_logger = logging.getLogger('x') |
Posted by Brian Borg on Nov 19 2020
The terms 'end-to-end' and 'integration testing' seem to have a lot of people in the software testing world conflicted. We've trawled the internet and found many different opinions, so we thought we'd compare the two, provide some context and create a definitive guide.
End-to-end testing verifies that your software works correctly from the beginning to the end of a particular user flow. It replicates expected user behavior and various usage scenarios to ensure that your software works as whole.
{ "path": "/content/geometrixx/my-first-jinja-page", | |
"properties": [ | |
{ "name": "jcr:primaryType", | |
"value": "cq:Page" }], | |
"nodes": [ | |
{ "path": "jcr:content", | |
"properties": [ | |
{ "name": "jcr:primaryType", | |
"value": "cq:PageContent"}, |
// the main app file | |
import express from "express"; | |
import loadDb from "./loadDb"; // dummy middleware to load db (sets request.db) | |
import authenticate from "./authentication"; // middleware for doing authentication | |
import permit from "./authorization"; // middleware for checking if user's role is permitted to make request | |
const app = express(), | |
api = express.Router(); | |
// first middleware will setup db connection |
# https://github.com/pypa/build/blob/main/setup.cfg | |
[metadata] | |
name = build | |
version = 0.5.1 | |
description = A simple, correct PEP517 package builder | |
long_description = file: README.md | |
long_description_content_type = text/markdown | |
author = Filipe Laíns | |
author_email = lains@riseup.net |
# see https://editorconfig.org/ | |
root = true | |
[*] | |
# Use Unix-style newlines for most files (except Windows files, see below). | |
end_of_line = lf | |
trim_trailing_whitespace = true | |
indent_style = space | |
insert_final_newline = true | |
indent_size = 4 |