jimleroyer

NOTIFY_ENVIRONMENT=development

ADMIN_CLIENT_SECRET=
AUTH_TOKENS=

SECRET_KEY=
DANGEROUS_SALT=
#DOCUMENT_DOWNLOAD_API_HOST=http://host.docker.internal:7000

ASSET_DOMAIN=

jimleroyer

API_HOST_NAME=http://host.docker.internal:6011
AWS_XRAY_SDK_ENABLED = False
ADMIN_CLIENT_SECRET=

ASSET_UPLOAD_BUCKET_NAME=
ASSET_DOMAIN=

CONTACT_EMAIL=

# current local

jimleroyer

[[Snippets]]
  Description = "Scoop update and show status"
  Filename = "C:\\Users\\jlr\\AppData\\Roaming\\pet\\snippet.toml"
  Output = ""
  Tag = ["scoop"]
  command = "scoop update && scoop status"

[[Snippets]]
  Description = "Cleaning up Scoop's installataions and cache."

jimleroyer

• AWS/bzt/Jmeter / Apache License 2.0
  • Pros
    • The AWS solution seems to distribute fairly well . I haven't tested it though as simply running locally was sufficient for Notify's needs.
    • Using the AWS solution without JMeter makes it a fairly simple and handy tool to use. This is good for test that does not require complex scenario with parameters passing or complex authentication.
    • JMeter is battle tested by years of experience. It offers a wide range of options and plugins. It can deliver on complicated scenarios.
    • bzt is compatible with many testing tools such as Gatling, but only JMeter integration is available through the AWS integration.
    • bzt offers an abstraction for simple tests that allows us to skip JMeter scripting.
• Can run tests on man

jimleroyer

{
    "homepage": "http://dahlbyk.github.io/posh-git/",
    "description": "A PowerShell module which provides Git/PowerShell integration.",
    "version": "1.0.0-beta4",
    "license": "MIT",
    "url": "https://github.com/dahlbyk/posh-git/archive/v1.0.0-beta4-8-g14e274d.zip",
    "hash": "efe378bd6318941fbc41730881def9524e4418877482e28df1a750e7eec65fd3",
    "extract_dir": "posh-git-14e274d4f3701e1f543d9bc39ac12e9dfad04895\\src",
    "psmodule": {
        "name": "posh-git"

jimleroyer

// To view the default settings, hold "alt" while clicking on the "Settings" button.
// For documentation on these settings, see: https://aka.ms/terminal-documentation
{
    "$schema": "https://aka.ms/terminal-profiles-schema",
    "defaultProfile": "{574e775e-4f2a-5b96-ac1e-a2962a402336}",
    "copyOnSelect": false,
    "initialCols": 100,
    "initialRows": 40,
    "wordDelimiters": " ./\\()\"'-:,.;<>~!@#$%^&*|+=[]{}~?\u2502",
    "showTabsInTitlebar": true,

jimleroyer

import scala.language.existentials

// Simple laboratory exercise that uses existentials everywhere for the Transition.
// But these existentials are not bound to much restriction and are not recognized
// to be compatible with the built list of transitions.

object Lab {

  /** ************** Types */

jimleroyer

import scala.language.existentials

// Simple laboratory exercise that makes use of a [[TransitionExistential]].
// The existential type hides its type parameters and provides transition
// values and parameters' conversions.

object Lab {

  /** ************** Types */

jimleroyer

import scala.language.existentials

// Simple laboratory exercise that uses incompatible parameter types, as the
// [[State]] type parameter is bound to [[Nothing]], and nothing above. That
// does not make sense at all.

object Lab {

  /** ************** Types */

jimleroyer

import scala.language.existentials

// Simple laboratory exercise that uses existentials everywhere for the Transition.
// But these existentials are not bound to much restriction and are not recognized
// to be compatible with the built list of transitions.

object Lab {

  /** ************** Types */