ayan4m1

Old npm-upgrade repo from Node 10-12.x era

cloc

github.com/AlDanial/cloc v 1.98 T=0.01 s (1216.9 files/s, 67572.7 lines/s)

Language	files	blank	comment	code
JSON	5	0	0	8237
JavaScript	19	179	31	791

ayan4m1

#!/usr/bin/env bash

now=$(date '+%Y%m%d%H%M%S')
echo -e "SecsElapsed,Temp" >> test-${now}.csv

runtime=900
resolution=5
SECONDS=0
while (( $SECONDS < $runtime )); do
  cpu_temp=$($(cat /sys/class/thermal/thermal_zone0/temp) / 1000)

ayan4m1

{
  "[javascript]": {
    "editor.defaultFormatter": "esbenp.prettier-vscode"
  },
  "[yaml]": {
    "editor.defaultFormatter": "redhat.vscode-yaml"
  },
  "[cpp]": {
    "editor.wordBasedSuggestions": false,
    "editor.suggest.insertMode": "replace",

ayan4m1

BenchmarkDotNet=v0.13.4, OS=Windows 11 (10.0.22000.1455/21H2)
Intel Core i7-9750H CPU 2.60GHz, 1 CPU, 12 logical and 6 physical cores
.NET SDK=7.0.102
  [Host]   : .NET 7.0.2 (7.0.222.60605), X64 RyuJIT AVX2
  .NET 7.0 : .NET 7.0.2 (7.0.222.60605), X64 RyuJIT AVX2

Job=.NET 7.0  Runtime=.NET 7.0  

|   Method |  Items |           Mean |         Error |        StdDev |
|--------- |------- |---------------:|--------------:|--------------:|

ayan4m1

Redis Desktop Manager for Windows

Yes, it's been done already. No, it's still not particularly easy. You do not need to use either Qt Creator or VS2015.

I am building on information found here, here, and here. Thanks to these folks and the contributors to RDM.

With this document, I sought to "trim the fat" from these other guides and prove that VS2015 itself was not in fact necessary - just its tooling.

Prerequisites

ayan4m1

import torch
import cv2
import RRDBNet_arch as arch
import numpy as np
import BLIP.models.blip
import os

from torchvision import transforms
from torchvision.transforms.functional import InterpolationMode
from diffusers import StableDiffusionPipeline, StableDiffusionImg2ImgPipeline, LMSDiscreteScheduler

ayan4m1

ayan4m1

raspberry pi print server

prerequisites

• Raspberry Pi 3/4
• USB Printer
• 8GB+ microSD card
• 2+ Amp Micro-USB power supply (Pi 3) or 3+ Amp USB-C power supply (Pi 4)

If you're smart, you'll use the 64-bit Lite image, but I didn't find that at first and went with the 64-bit Desktop image. This meant more work cleaning up unnecessary packages.

ayan4m1

NOTE: Click the "Raw" button in the upper right corner of this pane to get a template you can copy into Reddit. Thanks to /r/DIY_ejuice and /u/ConcreteRiver for commentary and the original format respectively!

Hardware: Describe your build (coil diameter, material, wicking, and resistance), atomizer (model), and device (model and settings) information.

Mixing: Describe everything required to reproduce the liquid you used to test. VG/PG ratio and percentage(s) at a minimum, ideally with notes about handling and/or steeping.

Flavor profile: Describe the quantitative and qualitative aspects of the concentrate. Pay particular attention to the experience that the flavor(s) impart.

Throat hit: Describe quantitatively (a ten point scale is common) and qualitatively (what your throat feels like during and after a hit).

ayan4m1

#include <Arduino.h>
#include <ESP8266WiFi.h>

#define WIFI_SSID "bar"
#define WIFI_PSK "changeme"
#define IFTTT_WEBHOOK_URL "https://maker.ifttt.com/trigger/YOUR EVENT NAME HERE/with/key/YOUR KEY HERE"
#define IFTTT_WEBHOOK_HOST "maker.ifttt.com"
#define IFTTT_WEBHOOK_PORT 80
#define HTTP_TIMEOUT 5 // 5 seconds