sennett-lau

const { responseCode, responseType } = require('./constants.js')
const {
	checkResponse,
	getArrayFromRequest,
	getCallbackId,
} = require('./socket.io.js')
const { uuidv4: uuid } = require('https://jslib.k6.io/k6-utils/1.4.0/index.js')
const { setTimeout, clearTimeout } = require('k6/experimental/timers')
const { check } = require('k6')

andrew-delph

import { responseCode, responseType } from './constants';
import { checkResponse, getArrayFromRequest, getCallbackId } from './socket.io';
import { uuidv4 as uuid } from 'https://jslib.k6.io/k6-utils/1.4.0/index.js';
import { setTimeout, clearTimeout } from 'k6/experimental/timers';
import { check } from 'k6';

export abstract class K6SocketIoBase {
  socket: any;

  callbackCount = 0;

duongphuhiep

Why mediator?

In a ASP.NET Web application. You don't need mediator

• If you prefers to make controlers depends directly to the Application Codes instead of indirectly via the Mediator.
• If you prefers to make a normal ASP.NET Web Application instead of a Mediator Application

Frankly it is not a Bad choice, no need to use a Mediator framework or make a Mediator Application just because everyone did.. Though, There are benefits in making a Mediator Application:

• Event sourcing (Messages broadcast), CQS pattern..
• Decouple the Controler (presentation) from Application codes, so that you could swap the presentation technology. For eg, if you make a "MassTransit" application, then you can swap the presentation layer to Mediator or RabbitMQ, or Grpc.. => you are not to be sticked with or limited by ASP.NET presentation => but rather sticked with and limited by your mediator framework!

krisek

groups:
- name: node_exporter_alerts
  rules:
  - alert: Node down
    expr: up{job="monitoring-pi"} == 0
    for: 2m
    labels:
      severity: warning
    annotations:
      title: Node {{ $labels.instance }} is down

ruanbekker

Inspired By: grafana/loki#333

• docker-compose.yml

version: "3"

networks:
  loki:

silver-xu

Setup a Node.js project with Typescript, ESLint, Prettier, Husky

Starting a personal node project could be easy; starting a team node project could be challenging.

I am a developer currently working in SEEK Australia.

In my experience, common mistakes developer make when starting a projects are:

• No Linting

mrk-han

Install and Create Emulators using AVDMANAGER and SDKMANAGER

TL;DR

For an emulator that mimics a Pixel 5 Device with Google APIs and ARM architecture (for an M1/M2 Macbook):

1. List All System Images Available for Download: sdkmanager --list | grep system-images

2. Download Image: sdkmanager --install "system-images;android-30;google_atd;arm64-v8a"

ernestkamara

== Adb Server
adb kill-server
adb start-server 

== Adb Reboot
adb reboot
adb reboot recovery 
adb reboot-bootloader

== Shell

shortjared

a4b.amazonaws.com
access-analyzer.amazonaws.com
account.amazonaws.com
acm-pca.amazonaws.com
acm.amazonaws.com
airflow-env.amazonaws.com
airflow.amazonaws.com
alexa-appkit.amazon.com
alexa-connectedhome.amazon.com
amazonmq.amazonaws.com

ericksli

import com.facebook.react.bridge.Arguments
import com.facebook.react.bridge.WritableArray
import com.facebook.react.bridge.WritableMap

fun writableMapOf(vararg values: Pair<String, *>): WritableMap {
    val map = Arguments.createMap()
    for ((key, value) in values) {
        when (value) {
            null -> map.putNull(key)
            is Boolean -> map.putBoolean(key, value)