burkeholland

Beast Mode

Beast Mode is a custom chat mode for VS Code agent that adds an opinionated workflow to the agent, including use of a todo list, extensive internet research capabilities, planning, tool usage instructions and more. Designed to be used with 4.1, although it will work with any model.

Below you will find the Beast Mode prompt in various versions - starting with the most recent - 3.1

Installation Instructions

• Go to the "agent" dropdown in VS Code chat sidebar and select "Configure Modes".
• Select "Create new custom chat mode file"

stanek-michal

-1) Quick primer on HF models

Models can be grabbed from HuggingFace, most UIs have a text window where you paste in a HF identifier such as:
TheBloke/CodeLlama-7B-Instruct-GGML

the UI then downloads the model from HF automatically.

here is an example link to a model
https://huggingface.co/TheBloke/CodeLlama-7B-Instruct-GGML

Mikaayenson

openapi: 3.0.0
info:
  title: Elastic Security SIEM Signals API (https://www.elastic.co/guide/en/security/current/security-apis.html)
  version: 1.0.0
servers:
  - url: 'http://{kibana_host}:{port}'
paths:
  /api/detection_engine/index:
    summary: Signal index operations (used to store detection alerts)
    post:

rylnd

#!/usr/bin/env bash

KIBANA_URI="${KIBANA_URL:-"http://localhost:5601"}"
KIBANA_USR="${KIBANA_USER:-"elastic"}"
KIBANA_PWD="${KIBANA_PASS:-"changeme"}"

KIBANA_SPACE="${SPACE_ID:-""}"
if [ -n "$KIBANA_SPACE" ]; then
  SPACE_PART="s/${KIBANA_SPACE}/"
fi

pmuellr

{"attributes":{"fieldAttrs":"{\"event.outcome\":{\"count\":3},\"kibana.alerting.status\":{\"count\":5},\"message\":{\"count\":7},\"event.action\":{\"count\":4},\"kibana.alerting.action_group_id\":{\"count\":2},\"kibana.alerting.instance_id\":{\"count\":2},\"event.duration\":{\"count\":7},\"error.message\":{\"count\":4},\"event.end\":{\"count\":1},\"event.reason\":{\"count\":2},\"event.start\":{\"count\":1},\"rule.id\":{\"count\":1},\"kibana.spaceId\":{\"count\":1}}","fieldFormatMap":"{\"event.duration\":{\"id\":\"duration\",\"params\":{\"inputFormat\":\"nanoseconds\",\"outputFormat\":\"asSeconds\",\"showSuffix\":true,\"useShortSuffix\":true}},\"event.duration.ms\":{\"id\":\"duration\",\"params\":{\"inputFormat\":\"milliseconds\",\"outputFormat\":\"asMilliseconds\",\"showSuffix\":true,\"useShortSuffix\":true}}}","fields":"[]","runtimeFieldMap":"{\"event.duration.ms\":{\"type\":\"long\",\"script\":{\"source\":\"def duration = doc['event.duration'];\\nif (duration == null) return;\\nif (duration.size() == 0) ret

astoilkov

Async Operations with useReducer Hook

9 March, 2019

We were discussing with @erusev what we can do with async operation when using useReducer() in our application. Our app is simple and we don't want to use a state management library. All our requirements are satisfied with using one root useReducer(). The problem we are facing and don't know how to solve is async operations.

In a discussion with Dan Abramov he recommends Solution 3 but points out that things are fresh with hooks and there could be better ways of handling the problem.

Problem

FrankHassanabad

#
# Full text queries
#

# Match all
GET /auditbeat-*/_search
{
  "query": {
    "match_all": {}
  }

FrankHassanabad

export PLUGIN_NAME=secops

# Start kibana
alias start-kibana='cd $HOME/projects/kibana && yarn start --no-base-path'

# Start bootstrap
alias start-bootstrap='cd $HOME/projects/kibana && yarn kbn bootstrap'

# Start typecheck
alias start-type-check='cd $HOME/projects/kibana && node scripts/type_check.js'

a7madgamal

FINALLY no need for tricks!

bonus tip: for more darkness > https://darkreader.org/

jk2K

#!/bin/bash
ADB_PATH="/Users/lee/Library/Android/sdk/platform-tools"
PACKAGE_NAME="com.yourcompany.app"
DB_NAME="default.realm"
DESTINATION_PATH="/Users/lee/Downloads/${DB_NAME}"
NOT_PRESENT="List of devices attached"
ADB_FOUND=`${ADB_PATH}/adb devices | tail -2 | head -1 | cut -f 1 | sed 's/ *$//g'`
if [[ ${ADB_FOUND} == ${NOT_PRESENT} ]]; then
    echo "Make sure a device is connected"
else