if you are using multiple languages and would like to ignore default files or folders, just add those files to global gitignore.
Example
.gitignore.global look like this
.DS_Store
Quality Assurance?
In terms of Operation
const getDrivers = () => { | |
return new Promise((resolve, reject) => { | |
setTimeout(() => { | |
resolve([ | |
{ | |
id: 1, | |
name: 'Hamilton' | |
}, | |
{ | |
id: 1, |
"use strict"; | |
const _ = require("lodash"); | |
const chalk = require("chalk"); | |
const Promise = require("bluebird"); | |
const ServiceBroker = require("../src/service-broker"); | |
const { MoleculerError } = require("../src/errors"); | |
// --- SAGA MIDDLEWARE --- | |
const SagaMiddleware = function() { |
"use strict"; | |
const _ = require("lodash"); | |
const chalk = require("chalk"); | |
const Promise = require("bluebird"); | |
const ServiceBroker = require("../src/service-broker"); | |
const { MoleculerError } = require("../src/errors"); | |
// --- SAGA MIDDLEWARE --- | |
const SagaMiddleware = function() { |
var elastic = require('elasticsearch'); | |
var client = new elastic.Client({ host: 'localhost:9200' }); | |
var index = 'myindex'; | |
var type = 'document'; | |
(function init() { | |
Promise.resolve() | |
.then(deleteIndex, handleError) |
| | |
By Gopal K. Kapur
Published at Computerworld • JUN 21, 2004 6:00 AM PST
Early in my career, when I worked as an engineer, my boss had a process by which the engineering team was expected to report project status. He insisted that we use the following steps, in the specified order:
Punch line: The facts; no adjectives, adverbs or modifiers. "Milestone 4 wasn't hit on time, and we didn't start Task 8 as planned." Or, "Received charter approval as planned."
Current status: How the punch-line statement affects the project. "Because of the missed milestone, the critical path has been delayed five days."
If you bump into running Docker engine in Fedora, remember to uninstall Docker Desktop as it conflicts with docker service.
Error
Cannot connect to the Docker daemon at unix:///home/{username}/.docker/desktop/docker.sock
The error "Cannot connect to the Docker daemon at unix:///home/{username}/.docker/desktop/docker.sock" typically indicates that Docker is trying to use an incorrect or non-standard socket path (/home/xxx/.docker/desktop/docker.sock), instead of the default path (/var/run/docker.sock). This is especially common if Docker Desktop for Linux was attempted but is not supported on Fedora or if there's a misconfiguration in Docker’s settings.