Alir3z4

import os
import pickle
import warnings

import numpy as np
import pandas as pd
from sklearn.model_selection import train_test_split
from tensorflow.keras.callbacks import EarlyStopping
from tensorflow.keras.layers import Dense
from tensorflow.keras.layers import Dropout

justinwoo

// install @types/react-redux and other nonsense

import * as React from 'react'
import { connect } from 'react-redux'
import { YourActualAppState } from './wherever-it-is.ts'

export function mapStateToProps({
  whatever
}: YourActualAppState) {
  return {

pbabics

#!/bin/bash

BASE_PATH=/var/opt/gitlab/gitlab-rails/shared/registry/docker/registry/v2/repositories

DRY_RUN=0
KEEP_LAST_IMAGES=10
RUN_GARBAGE_COLLECTOR=0
GITLAB_CTL_COMMAND=`which gitlab-ctl`

CAFxX

📂 Persistent "pipes" in Linux

In a project I'm working on I ran into the requirement of having some sort of persistent FIFO buffer or pipe in Linux, i.e. something file-like that could accept writes from a process and persist it to disk until a second process reads (and acknowledges) it. The persistence should be both across process restarts as well as OS restarts.

AFAICT unfortunately in the Linux world such a primitive does not exist (named pipes/FIFOs do not persist

toastdriven

# For Django, at the bottom of ``settings.py`` after all your other settings...

# Setup a BoundLogger for the project/apps to use...
import structlog
structlog.BoundLogger.configure(
    context_class=structlog.ThreadLocalDict(dict),
)

paulmillr

.border-radius (@radius) {
  -webkit-border-radius: @radius;
  -o-border-radius: @radius;
  -moz-border-radius: @radius;
  -ms-border-radius: @radius;
  border-radius: @radius;
}

.user-list {
  // need to use special `.` syntax