text:
---
layout: default
---

# 1996-09-02 - Re: Los Angeles Times article on Helsingius and anon.penet.fi

## Header Data

From: Damaged Justice<EMAIL_ADDRESS>To<EMAIL_ADDRESS>(Julian Assange)

Message Hash: 8724ea021fd09baa96d06153d7a91a3b145d77e3f05cbf12a1b9652cada6a2ed

Message ID<EMAIL_ADDRESS>Reply To<EMAIL_ADDRESS>UTC Datetime: 1996-09-02 17:05:42 UTC

Raw Date: Tue, 3 Sep 1996 01:05:42 +0800

## Raw message

```
{% raw  %}From: Damaged Justice<EMAIL_ADDRESS>Date: Tue, 3 Sep 1996 01:05:42 +0800
To<EMAIL_ADDRESS>(Julian Assange)
Subject: Re: Los Angeles Times article on Helsingius and anon.penet.fi
In-Reply-To<EMAIL_ADDRESS>Message-ID<EMAIL_ADDRESS>MIME-Version: 1.0
Content-Type: text

> Examining in detail Dyson's interests it appears she maintains a
> sizeable and long-standing interest in Eastern European technology
> companies. She is also clearly very far to the right of the political
> spectrum (rampant capitalist would be putting it mildly). She also speaks
> Russian.

And all these would certainly be excellent reasons to denounce her as an
enemy of liberty, now wouldn't they.

[CIA snip]

> "Of all tyrannies a tyranny sincerely  exercised for the good of its victims
>  may be the most  oppressive.  It may be better to live under  robber barons
>  than  under  omnipotent  moral busybodies,  The robber baron's  cruelty may
>  sometimes sleep,  his cupidity may at some point be satiated; but those who
>  torment us for own good  will torment us  without end,  for they do so with
>  the approval of their own conscience."    -   C.S. Lewis, _God in the Dock_

So what's wrong with her being an Evil Capitalist(tm) again?

--
http://yakko.cs.wmich.edu/~frogfarm ...for the best in unapproved information
"We think people like seeing somebody in a uniform on the porch."  -US Postal
spokeswoman, quoted in AP, 1/27/96. I don't know about you, but most people I
know who saw someone in uniform on their porch would pull out the shotgun...

{% endraw %}
```

## Thread

+ Return to [September 1996](/archive/1996/09)

+ Return to "["Angelos D. Keromytis" <angelos@gradin.cis.upenn.edu>](/authors/angelos_d_keromytis_angelos_at_gradin_cis_upenn_edu_)"
+ Return to "[Black Unicorn <unicorn@schloss.li>](/authors/black_unicorn_unicorn_at_schloss_li_)"
+ Return to "[Damaged Justice <frogfarm@yakko.cs.wmich.edu>](/authors/damaged_justice_frogfarm_at_yakko_cs_wmich_edu_)"
+ Return to<EMAIL_ADDRESS>(Esther Dyson)](/authors/edyson_at_edventure_com_esther_dyson_)"
+ Return to "[John Gilmore <gnu@toad.com>](/authors/john_gilmore_gnu_at_toad_com_)"
+ Return to "[Julian Assange <proff@suburbia.net>](/authors/julian_assange_proff_at_suburbia_net_)"
+ Return to "[Stanton McCandlish <mech@eff.org>](/authors/stanton_mccandlish_mech_at_eff_org_)"

+ 1996-09-02 (Mon, 2 Sep 1996 08:04:19 +0800) - [Re: Los Angeles Times article on Helsingius and anon.penet.fi](/archive/1996/09/5eb58ecd5d16021afed766928bf25009c6132d5eb4d42fe74f4e2f6889a34514) -<EMAIL_ADDRESS>(Esther Dyson)_
  + 1996-09-02 (Mon, 2 Sep 1996 10:50:32 +0800) - [Re: Los Angeles Times article on Helsingius and anon.penet.fi](/archive/1996/09/1d7f79d8e12c1bbc67da6edc302c3888f66b42a931830c0194d599b6f08b0d19) - _"Angelos D. Keromytis"<EMAIL_ADDRESS>  + 1996-09-02 (Mon, 2 Sep 1996 17:33:27 +0800) - [Re: Los Angeles Times article on Helsingius and anon.penet.fi](/archive/1996/09/bea6292af9fe6bd9699fb7e25eba7bb8059e4208416ba4469b1a2a5deba6380d) - _Black Unicorn<EMAIL_ADDRESS>    + 1996-09-02 (Mon, 2 Sep 1996 21:23:51 +0800) - [Re: Los Angeles Times article on Helsingius and anon.penet.fi](/archive/1996/09/8cd2beda40fb96dae883c1197a20530bbce66498cd4cf0141ac4e545d51ed988) - _Julian Assange<EMAIL_ADDRESS>      + 1996-09-02 (Tue, 3 Sep 1996 01:05:42 +0800) - Re: Los Angeles Times article on Helsingius and anon.penet.fi - _Damaged Justice<EMAIL_ADDRESS>  + 1996-09-02 (Tue, 3 Sep 1996 06:56:10 +0800) - [Re: Los Angeles Times article on Helsingius and anon.penet.fi](/archive/1996/09/def15f89d4f25b86873242f1d604dfbc34db99dc8be60c3536e794e8b6d44913) - _John Gilmore<EMAIL_ADDRESS>  + 1996-09-03 (Tue, 3 Sep 1996 11:28:35 +0800) - [Re: Los Angeles Times article on Helsingius and anon.penet.fi](/archive/1996/09/9c12ce885841165584ba31ebbd2e0e3a8ecc8d3a80923340feec948f93a19411) - _Stanton McCandlish<EMAIL_ADDRESS>


text:
---
title: Parsing chromedriver logs in Haskell
date: 20180310T00:00Z
---

chromedriver (the tool for programmatic interaction with Chrome) doesn't have an output format amenable to analysis, so I wrote a Haskell program to convert it to JSON [chromedriver-logs](https://github.com/chrismwendt/chromedriver-logs), which:

- Outputs JSON
- Keeps track of commands and their response times
- Streams log lines
- Ignores junk lines

<script src="https://asciinema.org/a/44dRKLg0E2Mp9CXrZb113IHAK.js" id="asciicast-44dRKLg0E2Mp9CXrZb113IHAK" async></script>

license: MIT

branch_name: refs/heads/master

extension: md

license_type: permissive


text:
# Development

Here we'll cover a few common tasks developers might face when setting up formBuilder.

## Clone the repo

```bash
$ git clone git@github.com:kevinchappell/formBuilder.git form-builder && cd form-builder
```

## Install Dependencies

```bash
$ npm install
```

## Local development

Once you've cloned the project and installed it's dependencies you can get a local version running by running:

```bash
$ npm start
```

This will run the default webpack config and open a new browser tab and that serves a demo of the plugin. This demo can be used to test features and bugs.

## Languages

At the time of writing this, formBuilder is available in dozens of languages thanks to generous contributors around the world. If you would like to contribute, formBuilder's language repo can be found [here](https://github.com/kevinchappell/formBuilder-languages). By default formBuilder will load languages from https://formbuilder.online/assets/lang unless the `i18n.location` option is set.

## Custom Controls

See the Control and Control Plugin Architecture Documentation to learn about how to create custom controls.

- [Overview](https://formbuilder.online/docs/formBuilder/overview/)
- [Control](https://formbuilder.online/docs/formBuilder/controls/)
- [Control Plugins](https://formbuilder.online/docs/formBuilder/control-plugins/)

repository: kevinchappell/formBuilder

gha_language: JavaScript

gha_license_id: MIT

repo_name: kevinchappell/formBuilder


text:
# MHCdouble [![Build Status](https://travis-ci.org/hammerlab/mhcdouble.svg?branch=master)](https://travis-ci.org/hammerlab/mhcdouble)

Predicting presentation of peptides by Class II MHC molecules using convolutional neural networks.

This library allows you to train and predict with a collection of allele-specific MHC II
peptide presentation models from categorical binding data (such as from a
mass spec. assay).

## Training Convolutional Predictors

Here's an example of a minimal invocation required to train a model on a new
dataset:

```
mhc2-train-convolutional \
    --model-dir trained-models \
    --dataset dataset.csv
```

The file `dataset.csv` must contain the columns `allele`, `peptide`, and `hit`.

You can also specifiy training parameters and architectural hyperparameters:

```
mhc2-train-convolutional \
    --model-dir trained-models \
    --dataset dataset.csv \
    --conv-activation linear \
    --global-batch-normalization 0 \
    --embedding-dim 10 \
    --conv-dropout 0 \
    --batch-size 16 \
    --patience 2
```

A more complete list of parameters can be seen by running `mhc2-train --help`.

## Prediction

The following code will generate binding predictions for one or more alleles on a given set of peptides:

```
mhc2-predict \
    --model-dir trained-models \
    --allele DRB1*01:01 \
    --peptides-file peptides.txt
```

Additional alleles can be specified as part of the `--allele` flag, such as `--allele DRB1*01:01 DRB1*11:01`.

Peptides can also be given manually on the commandline using the `--peptide` option, such as `--peptide SIINFEKLQQQQQQ`.

If you want to make predictions for different peptides associated with each allele, you can provide a CSV file with columns "allele" and "peptide" using the `--input-csv` option.

## Which alleles are available?

To see which alleles are available in a directory of trained models, run:

```mhc2-list-alleles MODEL-DIR```

repository: openvax/mhcdouble

repo_name: openvax/mhcdouble


text:
# Split json

Embedding all the translations in a js file and loading all at application startup may not
be ideal for medium and big sized applications.

In this sample we will split the translations files in separted json files, and we will
load them on deman.

# Steps

- Let's taking as starting point sample 02

```
npm install
```

- Let's create a subfolder called _locales_.

* Inside that subfolder let's create two subfolders more, one
  called _en_ and another called _es_

* We are going to split the translation files into two json files.

_./src/locales/en.json_

```json
{
  "login": "Login",
  "Invalid login or password, please type again": "Invalid login or password, please type again",
  "error, review the fields": "error, review the fields rrr",
  "login plus username": "Usuario: {{username}}",
  "REQUIRED": "Mandatory field"
}
```

_./src/locales/es.json_

```json
{
  "login": "Introduzca credenciales",
  "Invalid login or password, please type again": "Usuario o clave no validos, porfavor intentelo de nuevo",
  "error, review the fields": "Error, revise los campos por favor",
  "login plus username": "Usuario: {{username}}",
  "REQUIRED": "Campo obligatorio"
}
```

- We need to copy this files to the dist folder when generating the bundle
  with webpack (another option could be to server this from a CDN or from a
  database).

- First let's install a plugin that will let us copy files.

```bash
npm i -D copy-webpack-plugin
```

- Now let's configure it on webpack.

_./webpack.config.json_

Require the plugin on top of the file.

_./webpack.config.json_

```javascript
const CopyWebpackPlugin = require("copy-webpack-plugin");
```

Let's configure the plugin

_./webpack.config.json_

```diff
  plugins: [
+   new CopyWebpackPlugin([{ from: "locales/**/*" }]),
    //Generate index.html in /dist => https://github.com/ampedandwired/html-webpack-plugin
    new HtmlWebpackPlugin({
      filename: 'index.html', //Name of file in ./dist/
      template: 'index.html', //Name of template in ./src
      hash: true,
    }),
    new MiniCssExtractPlugin({
      filename: "[name].css",
      chunkFilename: "[id].css"
    }),
  ],
```

- Let's give a try and check that files are copied into the right
  destination folder.

```bash
npm run build
```

- Now it's time to install an i18next plugin that will allow us
  request remote language files.

```bash
npm install i18next-xhr-backend --save
```

- Let's configure it.

_./src/i18n.ts_

```diff
import i18n from "i18next";
import { initReactI18next } from "react-i18next";
+ import XHR from 'i18next-xhr-backend';

- // the translations
- // (tip move them in a JSON file and import them)
- const resources = {
-   en: {
-     translation: {
-       login: "Login",
-       "Invalid login or password, please type again":
-         "Invalid login or password, please type again",
-       "error, review the fields": "error, review the fields rrr",
-       "login plus username": "Usuario: {{username}}",
-       REQUIRED: "Mandatory field"
-     }
-   },
-   es: {
-     translation: {
-       login: "Introduzca credenciales",
-       "Invalid login or password, please type again":
-         "Usuario o clave no validos, porfavor intentelo de nuevo",
-       "error, review the fields": "Error, revise los campos por favor",
-       "login plus username": "Usuario: {{username}}",
-       REQUIRED: "Campo obligatorio"
-     }
-   }
- };

i18n
  .use(initReactI18next) // passes i18n down to react-i18next
+ .use(XHR)
  .init({
-    resources,
    lng: "es",
+    fallbackLng: 'es' || 'en',
+    load: 'currentOnly',
+    react: {
+      wait: true,
+    },
    interpolation: {
      escapeValue: false // react already safes from xss
    },
+    backend: {
+      loadPath: '/locales/{{lng}}.json',
+    }
  });

export default i18n;
```

> If something break, you can consider adding _debug: true_ to your
> _init_ section.

- Before giving a try let's suspend our react app meanwhile the
  resource json is being loaded and display a _loading..._ message.

_./src/main.tsx_

```diff
+ import { Suspense } from "react";

// (...)

ReactDOM.render(
+  <Suspense fallback={<div>Loading...</div>}>
    <MuiThemeProvider theme={theme}>
      <SessionProvider>
        <HashRouter>
          <Switch>
            <Route exact={true} path="/" component={LoginPage} />
            <Route path="/pageB" component={PageB} />
          </Switch>
        </HashRouter>
      </SessionProvider>
    </MuiThemeProvider>
+  </Suspense>,
  document.getElementById("root")
);
```

- Let's give a try.

```bash
npm start
```


text:
# PubMedTag

## Still in development ... Functionality untested

## This is a python script which facilitates tagging of studies for literature reviews

Required modules: OpenPyXl (for Excel functionality), TKinter, JSON

Using a spreadsheet of the same format generated by PubMedToSheet (see my other repos):

1) Studies are tagged with keywords/phrases

2) Tags are each unique columns (i.e. if two studies are tagged with "word" both are marked in the same column. This makes them sortable!)

3) The spreadsheet is saved along with a list of unique tags, and a previously edited spreadsheet/list of tags can be imported. That way, you can take a break instead of tagging the 10's/100's/1000's of articles in one sitting.

### Feel free to use, modify, etc. Credit is appreciated. MIT License.

### Please share any issues or bugs with me via email or the issues page

repository: danalber/PubMedTag

repo_name: danalber/PubMedTag


text:
# shell code execution

## simple

~~~{#simple .shell-exec}
echo 'HELLO! SHELL!'
~~~

## piped

~~~{#piped .shell-exec}
echo 'HELLO! SHELL!'	|
tr 'A-Z' 'a-z'
~~~

## multiple

~~~{#multiple .shell-exec}
echo 'HELLO! SHELL!'	|
tr 'A-Z' 'a-z'
echo 'FROM PANDOC!'	|
tr 'A-Z' 'a-z'
~~~

## program designation

~~~{#prog .shell-exec prog="bc 		-ql "}
1+1
~~~

repository: kaznak/pandocfilter-shell-exec

repo_name: kaznak/pandocfilter-shell-exec


text:
Combat
Conditions
Frightened

You have disadvantage on ability checks and attack rolls while the source of your fear is within line of sight.

You cannot willingly move closer to the source of your fear.

extension: markdown

gha_language: Vue


text:
# Instanews README

Project designing an HTML/CSS website that uses the jQuery ajax method to populate the homepage with information from the New York Times Top Stories API.

![Sample of Instanews](instanews-sample.gif)

## Features

* Used the jQuery AJAX method to get the data from the New York Times API. Learned how to iterate through multiple objects using the .each function.

* Incorporated CSS transitions to glide the header smoothly to the top, and to glide the images while re-sizing the browser.

* Used CSS transitions to glide the paragraph up when the user is hovered over the image.

## Contributing

Please feel free to submit an issue or pull request. To run the build process, download the files then run 'gulp' in the project's root directory.

## License

[MIT](LICENSE)

repository: DakotaPaige/instanews

gha_language: CSS

repo_name: DakotaPaige/instanews


text:
---
title:  "Firefox 52 beta 7 Test day invitation"
date:   2017-02-10 1:30:00 +0530
description: Mozilla Tamilnadu Community Testing day invitation
categories: blog
tags: [firefoxqa]
author: surentharan
---

![Firefox 52 beta 7 Test day]({{ site.url }}/assets/qmo.jpeg)

**Hello Everyone!**

Coming Friday, 17th February, We will have another testday, Firefox 52 beta 7. We’ll be focusing our testing on the following features : Graphics, Bug Verification and Bug Triage. Check out the detailed instructions via this [etherpad](https://public.etherpad-mozilla.org/p/MozillaIN_QA_Testing_Day-20170217)

It will be a great learning and contributing experience for everyone. And hereby invite you to join us. Lets work together for a better Firefox!!!

Participants Kindly RSVP by commenting your name along with your twitter handle, telegram handle and fb profile link.

##### FAQ

**Any previous experience is required ?**

No previous experience is required for Testing.

**Prerequisite?**

Bugzilla Account- to access bugs.

gha_language: HTML


text:
# Resources

## Functional Programming

- https://maryrosecook.com/blog/post/a-practical-introduction-to-functional-programming
- https://www.reddit.com/r/javascript/comments/4vr0pe/anjana_vakil_learning_functional_programming_with/

## Optimizing React

- http://www.slideshare.net/grgur/webpack-react-performance-in-16-steps

gha_license_id: NOASSERTION


text:
# v0.6.5
  * compatibility with ancient versions of node

# v0.6.4
  * avoid xxx..html (double dot)

# v0.6.3
  * fixed looping search for start of doc when end not found (very large docs)

# v0.6.2
  * bunyan for logging

# v0.6.1
  * fixed bug that xml not cleared when processed

# v0.6.0
  * refactored to move all anomaly handling into the doOneFile file splitter

# v0.5.13,14
  * handling timing issues

# v0.5.12
  * improve info message

# v0.5.11
  * avoid double call of getonefile
  * make getonefile artificially wait til processing can be assumed done before going on
  * correct errors in bad xml doc start

# v0.5.10
  * destroy stream on error

# v0.5.9
  * on error processing for stream

# v0.5.8
  * cheap-logger fix

# v0.5.7
  * clean up error messages.

# v0.5.6
  * clean up checkStart

# v0.5.5
  * logic for input.resume

# v0.5.4
  * typo fix (log->logger)

# v0.5.3
  * handle case where input is empty (xml translation problem?)
  * handle preprocess returning error in callback

# v0.5.2
  * handle file containing multiple html files

# v0.5.1
  * updated superagent to 1.8.3

# v0.5.0
  * new cheap-logger
  * preprocess gets json from config.json

# v0.4.3
  * Bug if infile list ends in comma, drill finds random files from null "directory".

# v0.4.2
  * Error on no closing element visible and no more input

# v0.4.1
  * Error from ElasticIndexer submitObject gives file in http error message

# v0.4.0
  * processFiles takes a second optional argument for a progress callback (config, msg)
  * changed engine to Node v4.2.2+ (0.10.29 gives errors on the tests for odd reasons)

# v0.3.34
  * did not handle \n<?xml...

# v0.3.33
  * handle file with just whitespace in it

# v0.3.32 (31 was a false save)
  * fixes missed assignment on previous fix

# v0.3.30
  * handle <?xml in embedded documents

# v0.3.29
  * Was failing on large files (~1 GB) with multiple xml docs. Fixed by passing keeping buffer small.

# v0.3.28
  * fix for new bug single file fileExt missing

# v0.3.27
  * Fixed generation (for html typically) to produce correct output filename

# v0.3.26
  * added options to new xml2js: attrkey: @, charkey: #, explicitarray: false == not default children to array

# v0.3.25
  * switch to xml2js in order to have bi-directional. (good performance!)

# v0.3.24
  * fix ref to adm-zip in the wrong dependency group

# v0.3.23
  * can handle single-entry zip files.  todo: multiple entries

# v0.3.22
  * Fix to drill for list of input directories: do not exit if one file is missing, just make a note.

# v0.3.21
  * update superagent requirement

# v0.3.20
  * report empty xml file instead of throwing error

# v0.3.19
  * add format to String.prototype ("{0}=={1}".format("this","that") ==> "this==that"
  * make html generator async safe so that it doesn't exit before writing is finished.

# v0.3.18
  * gz not initializing xml, so documents accumulating

# v0.3.17
  * add README.md to npm dist

# v0.3.16
  * used setimmediate to drop stack and hopefully buffer

# v0.3.15
  * simplified gz

# v0.3.14
  * fixed test to handle gz filename properly

# v0.3.13
  * can handle .gz files now

# v0.3.12
  * bug when no mapping: ElasticIndexer:224
  * bug when no src in xml-to-es:deepExtend: 366

# v0.3.11
  * Refixed bug where fileExt is more than just the extension

# v0.3.10
  * Broke out collectFiles from parseOptions processing to make multi-threaded (Cluster) use easier;
  * Demoted ElasticIndexer.js log message from INFO to DEBUG.

# v0.3.9
  * Fixed bug where fileExt is applied not to end of filename but only to formal extension.

# v0.3.8
  * Fixed resolving generator fn in nofile case

# v0.3.7
  * use setImmediate to trim stack on callbacks

# v0.3.6
  * Fix bug in Generation.js, line 69, createOneDocPerFile not running callback.

# v0.3.5
  * Add and correct added generator test

# v0.3.4
  * fix make generators available in Generation.js

# v0.3.3
  * Fixed setGenerator produced incorrect structure.

# v0.3.2
  * make generators available in Generation.js

# v0.3.1
  * handle filename properly when id is "" or " ", etc.

# v0.3.0
  * BREAKING CHANGE: config.input.preProcess takes a callback argument cb(json). This enables async processing in
  preprocess (doh).

# v0.2.17
  * Check that database has been created and attempt to create if not.

# v0.2.16
  * If config.index exists, initialize the indexer.

# v0.2.15
  * make test of fmt and type case-insensitive by using regexp

# v0.2.14
  * throw exception if ignoring user's generator

# v0.2.13
  * fix logger npe in Generation.js

# v0.2.12
  * handle setConfig property in output.generator so that generator can insure that it has
    the final version of the config object.

# v0.2.11
  * allow parser and indexer to take config as an object as well as a filename

# v0.2.10
  * fixes to ElasticIndexer

# v0.2.5
  * change lewis-config to lewis-input-config
  * added cheerio for parsing html input

# v0.2.4
  * substituted config.input.currentFile for config.inputFiles[0] where feasible

# v0.2.3
  * fixed bug where giving a list of input file names (not comma delimited) gives an error.
  * added recursive processing to subdirectories of directories submitted

# v0.2.2
  * put input file path (or URI, or dbRef) on config.input.currentFile during runs
  * pass config to input-config preProcess function.

# v0.2.1
  * fixed dbconfig to run callback correctly

# v0.2.0  API additions but no breaking API changes (applies to 0.1.4, 0.1.5 as well)
  * added
    * ability to define your own generator in output config
    * ability to specify a callback in output config to be called when all files are processed
  * example to save json output to mongodb
  * changed requires in examples/convert.js and example/indexFiles.js so that they can be run in place.
    Added comment for developer to change them for use outside the examples dir.

# v0.1.5
  * Skip indexing tests if ES is not running.

# v0.1.4
  * for input-config
    * added preProcess for gross output manipulation before other processing
    * added delete to enable property deletion
    * added rename to enable property key renaming (useful after promoting)

# v0.1.3

# v0.1.2   May 27, 2014
  * Changed ````require```` calls in ````examples```` scripts to suit npm usage, so that examples run correctly when
   copied to a top level directory (above ````node_modules/xml-to-es````).

# v0.1.1   May 24, 2014

 * Create index.js to collect API exports into one require.
 * Modify tests and examples to load index.js.
 * API using lib/xml-to-es and lib/indexFiles backward compatible.
 * Fixed bug on --clean, request.delete --> request.del; adjusted tests to exercise
 * Fixed serious bug where attempt to get the mapping was creating the index with wrong settings because of URL
 misspelling
 * cheap-logger ````log```` method now logs absolutely; it ignores log levels

repository: imbroglioj/xml-to-es

repo_name: imbroglioj/xml-to-es


text:
# Issue Alert.

Kindly adhere to the template!

## Prerequisites

Before we work on your issue, can you help us a bit more but completing this checklist?

- [ ] Can you reproduce the problem in safe mode?
- [ ] Are you running the latest version?
- [ ] Did you check the debugging guide?
- [ ] Did you check the FAQs on Discuss?
- [ ] Are you reporting to the correct repository?
- [ ] Did you perform a cursory search?

## Description

[Description of the bug or feature]

## Steps to Reproduce

1. [First Step]
2. [Second Step]
3. [You get it ;-) ...]

**Expected behavior:** [What you expected to happen]

**Actual behavior:** [What actually happened]

## Sugggested Fix

[Insert a fix that you think might work. If you can work on it, fix the bug and generate a PR, again following our *thoughtful* template]

## Versions

You can get this information from executing `npm version`.

---

### Thank you for your support!


text:
# Endogone macrocarpa (Tul. & C. Tul.) Tul. & C. Tul., 1851 SPECIES

#### Status
SYNONYM

#### According to
The Catalogue of Life, 3rd January 2011

#### Published in
Fungi hypog. 182 (1851)

#### Original name
Glomus macrocarpum Tul. & C. Tul., 1845

### Remarks
null

repository: mdoering/backbone

path: /life/Fungi/Glomeromycota/Glomeromycetes/Glomerales/Glomeraceae/Glomus/Glomus macrocarpum/ Syn. Endogone macrocarpa/README.md

repo_name: mdoering/backbone


text:
# Pyscript: Python scripting integration

This is a custom component that adds rich Python scripting to Home Assistant.

You can write Python functions and scripts that implement a wide range of automation, logic and
triggers.  State variables are bound to Python variables and services are callable as Python
functions, so it's easy and concise to implement high-level logic.

Functions you write can be configured to be called as a service or run upon time, state-change or
event triggers. Functions can also call any service, fire events and set state variables.
Functions can sleep or wait for additional changes in state variables or events, without slowing or
affecting other operations. You can think of these functions as small programs that run in
parallel, independently of each other, and they could be active for extended periods of time.

Pyscript also interfaces with the Jupyter front-ends (eg, notebook, console and lab).  That allows
you to develop and test pyscript functions, triggers, automation and logic interactively.

## Installation

Under HACS -> Integrations, select "+", search for `pyscript` and install it.

See the documentation if you want to install pyscript manually.

## Configuration

* Go to the Integrations menu in the Home Assistant Configuration UI and add `Pyscript Python scripting` from there, or add `pyscript:` to `<config>/configuration.yaml`; there is one optional parameter (see docs)
* Add files with a suffix of `.py` in the folder `<config>/pyscript`.
* Whenever you change a script file, make a `reload` service call to `pyscript`.
* Watch the HASS log for `pyscript` errors and logger output from your scripts.
* Consider installing the optional Jupyter kernel, so you can use pyscript interactively.

## Useful Links

* [Documentation](https://hacs-pyscript.readthedocs.io/en/latest)
* [Using Jupyter](https://github.com/craigbarratt/hass-pyscript-jupyter)
* [Jupyter notebook tutorial](https://nbviewer.jupyter.org/github/craigbarratt/hass-pyscript-jupyter/blob/master/pyscript_tutorial.ipynb)
* [GitHub repository](https://github.com/custom-components/pyscript) (please add a star if you like pyscript!)
* [Issues](https://github.com/custom-components/pyscript/issues)
* [Wiki](https://github.com/custom-components/pyscript/wiki)

repository: swazrgb/pyscript

gha_language: Python

repo_name: swazrgb/pyscript


text:
## PBHbounds

[![DOI](https://zenodo.org/badge/220053456.svg)](https://zenodo.org/badge/latestdoi/220053456) [![arXiv](https://img.shields.io/badge/arXiv-2007.10722-B31B1B.svg)](http://arxiv.org/abs/2007.10722) [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)

*A collection of bounds on primordial black holes (PBHs) and code for plotting them.*

 ![Messy summary of all PBH bounds](plots/PBH_bounds.png)

### Bounds

The list of available, tabulated bounds is in the [bounds/](bounds/) folder (see the readme there). The fact that I've included or omitted a particular bound shouldn't be taken as an endorsement or otherwise. I'll leave the user to exercise their own judgement when choosing which bounds are relevant. Note also that some of the bounds plotted above as dashed lines are projections.

### Contributing

If you'd like to add a bound to the repo, there are a few options:
1. Make the changes yourself:
	* Add the new bound as a `.txt` file in the [bounds/](bounds/) folder. Each file should have two columns, corresponding to the PBH mass in Solar mass, and the constraint on the PBH fraction. Also include a comment at the top of the file giving a link to the source of the bound.
	* Update the [bounds/README.md](https://github.com/bradkav/PBHbounds/blob/master/bounds/README.md) file with information about the new bound.
	* Submit a pull request
2. Create an issue here on the github repo, pointing to the paper/bound which is missing.
3. Contact me directly at<EMAIL_ADDRESS>and let me know which bound you think should be added.

### Plots

Some example plots summarising the bounds are in the [plots/](plots/) folder.

You can produce a plot with
```
python PlotPBHbounds.py -listfile LIST_FILE -outfile OUT_FILE
```
where `LIST_FILE` is a text file containing a list of bounds to be plotted (see `listfiles/list_all.txt` for an example) and `OUT_FILE` is the full filename of the image to be output (e.g. `plots/PBHbounds.pdf`). You can use the short flags `-lf` and `-of` for specifying the list file and output file.

A dark theme (with black background and white text) can be set using the flag `--dark`.

The plot style and some of the bounds are inspired by [arXiv:1801.00808](https://arxiv.org/abs/1801.00808).

Constraints on the primordial power spectrum can be plotted with
```
python PlotPSbounds.py
```
which is roughly inspired by plots from [arXiv:1811.11158](https://arxiv.org/abs/1811.11158), [arXiv:1812.00674](https://arxiv.org/abs/1812.00674) and [arXiv:1909.01593](https://arxiv.org/abs/1909.01593).

### Versions

**Updates:**
- 22/03/2022: Added new bounds from microlensing of quasars ([arXiv:2203.04777](https://arxiv.org/abs/2203.04777))
- 07/03/2022: Added long duration microlensing constraints from [arXiv:2202.13819](https://arxiv.org/abs/2202.13819)
- 22/02/2022: Added new EDGES 21cm constraints from Mittal et al. (2021), presented in [arXiv:2107.02190](https://arxiv.org/abs/2107.02190)
- 04/05/2021: Added some projected constraints in the asteroid-mass region, as well as a new flag for dark themes.
- 24/03/2021: Added Lyman alpha forest constraint and SKA forecast, shown in [arXiv:2103.12087](https://arxiv.org/abs/2103.12087).
- 13/01/2021: Added code for plotting Power Spectrum constraints (Fig. 1 of PBH review).
- 20/07/2020: Substantial updates, to coincide with PBH review article (more details to follow).
- 07/01/2020: added bounds on PBH evaporation from 511 keV gamma ray line

**Version 1.0 (12/11/2019):** Release version. Created for the first [GW4FP workshop](https://indico.cern.ch/event/843270/) (Amsterdam 2019).

### Citation

Feel free to use the bounds and code for anything you like, but please link to the repo if you do and cite the DOI: [10.5281/zenodo.3538999](https://doi.org/10.5281/zenodo.3538999).

Please also get in touch to let me know you've used the code. That way I can keep track! Thanks.

### Papers using PBHbounds

An incomplete list of papers which make use of PBHbounds. Please get in touch if you've used the code or digitised bounds, so I can keep track!

- *Constraints on the Abundance of PBHs from X-ray Quasar Microlensing Observations: Substellar to Planetary Mass Range*, Esteban-Gutiérrez et al., [arXiv:2307.07473](https://arxiv.org/abs/2307.07473)
- *Primordial black holes from Higgs inflation with a Gauss-Bonnet coupling*, Kawaguchi & Tsujikawa, [arXiv:2211.13364](https://arxiv.org/abs/2211.13364)
- *The Effect of Gravitational Lensing on Fast Transient Event Rates*, Sammons et al., [arXiv:2210.09487](https://arxiv.org/abs/2210.09487)
- *Snowmass 2021 Cosmic Frontier White Paper: Primordial Black Hole Dark Matter*, Bird et al., [arXiv:2203.08967](https://arxiv.org/abs/2203.08967)
- *Limits on Primordial Black Holes from M87*, Silk & Stodolsky, [arXiv:2201.03591](https://arxiv.org/abs/2201.03591)
- *Shedding light on Dark Matter through 21 cm Cosmology and Reionization constraints*, Villanueva-Domingo, [arXiv:2112.08201](https://arxiv.org/abs/2112.08201)
- *Can breakdown of perturbation in the α-attractor inflation lead to PBH formation?*, Sarkar et al., [arXiv:2112.05408](https://arxiv.org/abs/2112.05408)
- *Baryogenesis from ultra-slow-roll inflation*, Wu et al., [arXiv:2109.00118](https://arxiv.org/abs/2109.00118)
- *Primordial Black Holes from CDM Isocurvature Perturbations*, Passaglia & Sasaki, [arXiv:2109.12824](https://arxiv.org/abs/2109.12824)
- *Primordial blackholes from Gauss-Bonnet-corrected single field inflation*, Kawai & Kim, [arXiv:2108.01340](arXiv:2108.01340)
- *On Primordial Black Holes and secondary gravitational waves generated from inflation with solo/multi-bumpy potential*, Zheng et al., [arXiv:2106.04303](https://arxiv.org/abs/2106.04303)
- *Signatures of primordial black hole dark matter at DUNE and THEIA*, De Romeri et al., [arXiv:2106.05013](https://arxiv.org/abs/2106.05013)
- *A brief review on primordial black holes as dark matter*, Villanueva-Domingo et al., [arXiv:2103.12087](https://arxiv.org/abs/2103.12087)
- *Navigating the asteroid field: New evaporation constraints for primordial black holes as dark matter*, Picker, [arXiv:2103.02815](https://arxiv.org/abs/2103.02815)
- *Primordial black hole formation in α-attractor models: an analysis using optimized peaks theory*, Mahbub, [2103.15957](https://arxiv.org/abs/2103.15957)
- *Solar Mass Primordial Black Holes in Moduli Dominated Universe*, Bhattacharya et al., [arXiv:2101.02234](https://arxiv.org/abs/2101.02234)

repository: bradkav/PBHbounds

repo_name: bradkav/PBHbounds


text:
# Auto-tag out-of-stock products

Tags: Auto-Tag, Inventory, Out of Stock, Products

Does what it says on the tin. :) Optionally, emails you an alert when a product goes out of stock.

* View in the task library: [usemechanic.com/task/auto-tag-out-of-stock-products](https://usemechanic.com/task/auto-tag-out-of-stock-products)
* Task JSON, for direct import: [task.json](../../tasks/auto-tag-out-of-stock-products.json)
* Preview task code: [script.liquid](./script.liquid)

## Default options

```json
{
  "out_of_stock_inventory_level__number_required": 0,
  "product_tag__required": "out-of-stock",
  "email_alert_recipient__email": null
}
```

[Learn about task options in Mechanic](https://docs.usemechanic.com/article/471-task-options)

## Subscriptions

```liquid
shopify/inventory_levels/update
mechanic/user/trigger
```

[Learn about event subscriptions in Mechanic](https://docs.usemechanic.com/article/408-subscriptions)

## Documentation

Does what it says on the tin. :) Optionally, emails you an alert when a product goes out of stock.

Run this task manually to scan and tag all products in your store, according to their respective total inventory levels. Fill in the email alert recipient to send an email alert when a product goes out of stock.

## Installing this task

Find this task [in the library at usemechanic.com](https://usemechanic.com/task/auto-tag-out-of-stock-products), and use the "Try this task" button. Or, import [this task's JSON export](../../tasks/auto-tag-out-of-stock-products.json) – see [Importing and exporting tasks](https://docs.usemechanic.com/article/505-importing-and-exporting-tasks) to learn how imports work.

## Contributions

Found a bug? Got an improvement to add? Start here: [../../CONTRIBUTING.md](../../CONTRIBUTING.md).

repository: Ferrallv/mechanic-tasks

repo_name: Ferrallv/mechanic-tasks


text:
# Opegrapha bicolor R. C. Harris & Lendemer SPECIES

#### Status
ACCEPTED

#### According to
The Catalogue of Life, 3rd January 2011

#### Published in
Opuscula Philolichenum 2: 10 (2005)

#### Original name
Opegrapha bicolor R. C. Harris & Lendemer

### Remarks
null


text:
# Event When

This is an event library that emphasizes flow-control from a single dispatch
object.

## Introduction

This provides a succinct introduction to the library for the readme and this
file.

[doc]()

    This is an event library, but one in which events and listeners are
    coordinated through a single object. The emphasis throughout is on
    coordinating the global flow of the program.

    It addresses what I find to be the pain points of JavaScript programming:
    when does code execute and how does it have access to the objects it
    needs? Most event libraries handle the first well enough for linear
    sequences of event firing, but they fail when multiple events need to
    happen, in any order, before triggering a response. It can also require
    a lot of closures or globals to handle manipulating state from event
    calls. This library is designed to address those needs.

    Most event libraries suggest making objects (such as a button) into
    emitters; this is to promote separation of concerns, a good goal. But we
    want to coordinate events from multiple sources. So to do this,
    event-when is designed to allow you to attach the object to the
    event/handler/emit.  It also allows you to listen for events before the
    corresponding object exists. This is more like having listeners on a
    form element responding to button clicks in the form.

    There are several noteworthy features of this library:

    * [When](#when). This is the titular notion.  The `.when` method allows
      you to specify an event to emit after various specified events have all
      fired.  For example, if we call a database and read a file to assemble
      a webpage, then we can do something like

        ```
        emitter.when([["file parsed, "jack"], ["database returned", "jack"]],
            ["all data retrieved","jack"]);

        emitter.when(["file parsed, "database returned"],
            "all data retrieved", {scope: "jack"});

        ```

        This is why the idea of a central emitter is particularly useful to
        this library's intent.
    * [Scope](#scope). Events can be scoped. In the above example, each of
      the events are scoped based on the user jack. The emitter hosts a scope
      object where data for scopes can be stashed.
    * [Actions](#action). Events should be statements of fact. Actions can be
      used to call functions and are statements of doing. "Compile document"
      is an action and is a nice way to represent a function handler.
      "Document compiled" would be what might be emitted after the
      compilation is done.  This is a great way to have a running log of
      event --> action. To implement the log, you can run `emitter.makeLog()`
      and then when you want the event action, filter the logs with
      `emitter.log.logs("Executing action")` for an array of such statements.
    * Stuff can be attached to events, emissions, and handlers. Emits send
      data, handlers have contexts, and events have scope contexts.
    * [Monitor](#monitor) One can place a filter and listener to monitor all
      emits and act appropriately. Could be great for debugging.

    Please note that no particular effort at efficiency has been made. This is
    about making it easier to develop the flow of an application. If you need
    something that handles large number of events quickly, this may not be the
    right library. Benchmarking a simple emit can be found in benchmark.js.

    ### Using

    In the browser, include index.js. It will store the constructor as
    EventWhen in the global space.

    For node, use `npm install index.js` or, better, add it to the
    package.json file with `--save` appended.

    Then require and instantiate an emitter:
    ```
    var EventWhen = require('event-when');
    emitter = new EventWhen();
    ```

## Files

The file structure is fairly simple. The main output is the index.js file and
the rest are all ancillary files. We read in most of the stuff from
`src/event-when.md`.

### Loading

* [fevw](event-when.md "load:")  Main code
* [test](test.md "load:") Tests
* [examples](examples.md "load:") Examples for console

### Saving

* [../index.js](#main "save:|jshint") This is the node module entry point and
  only relevant file.
* [index.js](#main "save:") This is for browser access.
* [benchmark.js](#benchmark "save:|jshint") This is a very simple benchmark
  test.
* [../README.md](#fevw::readme "save: ") The standard README, new version.
* [../testrunner.js](#test::testrunner "save: |jshint")

## Main

This is the main structure of the module file.

    /*jshint eqnull:true,esversion:6 */
    /*global setTimeout, setImmediate, module, console */

    ;(function () {

        var noop = function () {};

        let identity = a=>a;

        var filter = _"fevw::filter";

        var decycle = _"fevw::cycle:main";

        var serial = _"fevw::serial";

        var Handler = _"fevw::handler";

        _"fevw::handler:prototype"

        var Tracker = _"fevw::tracker";

        _"fevw::tracker:prototype"

        var EvW = _"fevw::constructor";

        _"fevw::constructor:prototype"

        if (module) {
            module.exports = EvW;
        } else {
            this.EventWhen = EvW;
        }

    } () );

## Benchmark

Here we benchmark the basic emit, handler code. This is presumably where
the most number of operations occurs.

    /*jshint eqnull:true,esversion:6 */
    /*global require, process, console */

    var n = parseFloat(process.argv[2], 10) || 5e5;
    const EvW = require('./index.js');
    var EE = require("events").EventEmitter;

    var i, time, c;

    var log = function (time, count, tag) {
        var diff = process.hrtime(time);
        console.log("##", tag);
        console.log("count", count);
        console.log('benchmark took ' + diff[0] + ' seconds and ' +
            diff[1]*1e-6 + ' milliseconds');
    };

    console.log(process.memoryUsage());

    c = 0;

    _":second"
    console.log(process.memoryUsage());

    c = 0;
    _":first"
    console.log(process.memoryUsage());

    _":evw scope"
    console.log(process.memoryUsage());

    _":evw embedded scope"
    console.log(process.memoryUsage());

[first]()

    var emitter = new EvW();

    emitter.loopMax = 2*n;

    emitter.on("go", "add 1", function count (num) {
        c += num;
    });

    time = process.hrtime();

    for (i = 0; i < n; i += 1) {
        emitter.emit("go", 1);
    }

    log(time, c, "event-when");

[evw scope]()

    emitter = new EvW();

    emitter.loopMax = 2*n;

    emitter.scope('c', {a:0});

    emitter.action('add', function count (num, scope, context) {
        context.a += num;
    });

    emitter.on("go", "add:c");

    time = process.hrtime();

    for (i = 0; i < n; i += 1) {
        emitter.emit("go", 1);
    }

    log(time, emitter.scope('c').a, "event-when scope");

[evw embedded scope]()

    emitter = new EvW();

    emitter.loopMax = 2*n;

    emitter.scope('numbers', {c:0});

    emitter.action('add', function count (num, s) {
        o = this.emitter.scope(s);
        o.c += num;
    });

    emitter.on("go", "add");

    time = process.hrtime();

    let a = {c:1};

    for (i = 0; i < n; i += 1) {
        emitter.emit("go:numbers", 1);
    }

    log(time, emitter.scope('numbers').c, "event-when embedded scope");

[second]()

Native event emitter

        emitter = new EE();

        emitter.on("go", function (num) {
            c += num;
        });

        time = process.hrtime();

        for (i = 0; i < n; i += 1) {
            emitter.emit("go", 1);
        }

        log(time, c, "native");

## Use cases

Here we detail a variety of use cases.

     1. Get info from different sources, then emit them all together.

            gcd.when("file returned:dude!=>json", "db returned:dude",
            gcd.fs.readFile("dude.json", "file returned:dude");

     2.  Translate data and uniformize from different sources:

            gcd.when(["mouse drag!oo=>xy", "keyboard press!oo=>kbxy"], "position
            given!oo=")

        This will listen, without blocking, for one of those events, pipe the
        raw event through a specific pipe, and then emit a unified event from
        that. It will emit for each.

## Change Log

### Version 2

Version 1 had many events and scopes being fired from one emit. This was to
model it like the bubbling up of DOM events in the browser. But that is needed
in the browser because when one clicks on something, one is clicking on
multiple items and there is no way to see which one is the target.

After working with event-when for awhile, such options are not needed. If they
are, one can always fire another event up the chain.

Instead, we will drop to one event being emitted with one scope. The actions
can be triggered by the event and, optionally, in conjunction with a match of
the scope, either exact or not.

This impacts the .when function to include those options as well.

The .when tracker should also end up with some functional enhancements that
allow one to manipulate the data array before it is sent along as an emitter.
This includes flattening it in some ways, reducing, mapping, etc.

Actions should be emphasized with the written description action being
associated with a handler that takes in the data, the scope, the emitter, and
a context if provided. On and once need to have actions listed; a named
context is just a scope name as well.

Debugging is hoped to be augmented with a better tracking of the relationships
between the events and actions.

Also would like to add an ability to have a wait queue for (external) events
that adds to the queue of events for deciding when to emit an empty queue
event.

The handlers are treated differently. Handlers that are attached at the time
of the emit will be used; there is no stopping them. As soon as the event is
emitted, once handlers will decrement even before they are fired. This ensures
they are called in the exact order of emitting. This also eliminates the need
for an array of functions, handlers, etc. Everything is simplified.

Timing will be removed as well. All emit events are emitted in the order they
are encountered with the handlers being called in the order, from most
specific to general.

Benchmark from version 1 on my 2017 iMac was 5e5 events at 430ms while native
events was 16 ms as done in benchmark.js (after converting the argument to a
number in the initialize phase instead of having it do that every iteration of
the loop -- oops). Also did a bit of memory investigation. For 5e5, the memory
increased by a third from before the event emitting; the native one had no
increase.

### Version 1.3.0

Removed empty handlers and created .onces to track labelled onces to show they
did not get used up. No tests added :(

1.3.1: Added an array in onces of event, original count, and current count.

### Version 1.2.0

Introduced flat when

### Version 1.1.0

Added ability to order the data in .when according to initial creation
ordering, not event emitting ordering. Default is old behavior to avoid
breaking changes -- semver!

### Version 1.0.0

Switching to semver kind of thinking. Now using it extensively in
literate-programming and it works well.

Added in .cache method.

### Version 0.7.1

Better logs have been designed.

### Version 0.6.0 Thoughts

At the very least, better documentation. I wrote this thing and find it hard
to figure out how to use it the way I want to. But I also think there might be
some inaccuracies. So I hope to fix this up.

What I want is a very clear ability to use actions. I am also wondering about
scoping it. One could have separate event emitters or perhaps we can use one
which scopes an event to something, which could be a key string with an object
value that becomes available somehow.

... So the scope thing is cool. It bubbles up with the possibility of events
being stopped. Each handler has access to the data at each of the scope
levels. So the general scope level can get a scope object from the specific.

But the data for the handlers is getting complicated. So the callback
signature will be f(data, obj) where data is anything being passed along by
the event (for simple functions) while obj contains all the different
contexts, etc.  There is no this being bound; one can bind the function f if
you want a context, but this will not do anything. All needed stuff should be
in obj.

So what will be in obj? The keys will be data (redundant, but...),  hanCon for
handler context, hanArgs for an array of "data" to pass in,  evObj, ev,
emitter,

Thinking about .when only emitting events, not doing other handlers. I think
that makes it much cleaner to handle. Not sure why I included the other ways.
Maybe thought that having to define an event and then just one handler on it
seemed silly. But really, that's what events are about.

---

Decided to jettison all the myth/data stuff and the passin object. Instead,
events emit data (a single object) and the context of arguments is either
provided by the handler or is the empty object. The second argument is the
event Object which should have the current scope too. The event definitions
will not have any distinct data -- this can be put in the handler's context if
needed.

### Version 0.5.0 Thoughts

I have made a mess of the emit events. So here is the new paradigm. `.emit` is
equivalent to a function call. It gets called immediately and its sequence of
emits is followed as if they are function calls. The hope is that all the
handlers of an event emitted from within an emitted event sequence wil be done
completely before the rest of the original emit's handlers fire.

`.later` is asynchronous mode. It will emit the events, in the order queued,
at the next tick. Each one happens after a next tick. So the entire sequence
from one emit event will happen before the next `.later` is called. I think I
will have an optional parameter to specify push vs unshift behavior with
default being push.

Also, adding use of emitter.name in logs as well as numbering the emits called
for a given event. The string form for a handler will also lead to a log event
if no action/event fits.

### Version 0.4.0 Thoughts

The idea is to create an action sentence that invokes the handler. So we
attach the sentence to the event and then stuff happens to that. The handler
can be a function or it could be an array of functions, etc. The point of
invocation is when the sentence is used as a key to get the handler. So this
allows dynamism which could be good, could be bad. The hard work, I think, is
to rewrite the handler calling to be abstracted out to another level. I
probably need to introduce an object of type handler.

repository: jostylr/event-when

repo_name: jostylr/event-when


text:
# Changelog
All notable changes to this project will be documented in this file.

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/).

Currently this project DOES NOT adhere to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## 2020-04-17
### Added
- Parameter for calculation domain ("spatial" or "spectral")
- `scipy` to `environment.yml`

### Changed
- Updated README.md
- Configuration files can now be stored anywhere, as long as full path is used for `-c` parameter values
- Updated requirement for `python` (Used to be `=3.7`, now is `>=3.7`)
- Updated requirement for `pysteps` (Used to be `=1.1`, now is `>=1.2`)
- Moved `environment.yml` to main folder
- `-t` is now shorthand for `--timestamp` command line argument

### Removed
- References to version numbers from changelog, as they don't reflect the current situation anymore
- Obsolete `--test` command line argument

## 2020-01-29
### Added
- Folder for configuration files
- Utility functions for generating a configuration json file
- Parameters `NORAIN_VALUE` and `RAIN_THRESHOLD` for thresholding
- MIT License

### Changed
- Configurations are now read from json files
- Updated default configuration based on Pysteps article (Pulkkinen et al. 2019)
- Updated pysteps version to 1.1.1
- `LOG_FOLDER`, `LOG_LEVEL` and `OUTPUT_PATH` configuration parameters are no longer included in output metadata

### Removed
- Configuration parameters `DBZ_MIN`, `DBZ_THRESHOLD`, `R_MIN`, `R_THRESHOLD` (Replaced with new parameters).

### Fixed
- Program tried to write a log file before logging was initialised, when program couldn't find a given configuration. Now program raises an error instead.
- Input data is now thresholded properly
- Now it is possible to output values in mm/h, even if calculations are done in dBZ

## 2019-12-20
### Added
- New parametrisations and configurations for operational use
- Usage and Configuration descriptions to readme

### Changed
- Now `pystepsrc` file is tracked, previously it was ignored
- Renamed "dev" parametrisation to "test"
- Updated default parameters: now generates 25 ensemble members for up to 120 minutes
- Updated docstrings
- Updated .gitignore
- Improved markdown syntax usage in changelog and readme

### Removed
- Parametrisations used in research

### Fixed
- Dangerous default argument value in `utils.store_timeseries()`
- Removed unused import from `utils`
- Version tag links in changelog

## 2019-09-02
### Added
- Changelog
- New dependency: pysteps (1.0.0)
- Now it is possible to set motion perturbation parameters
- Default motion perturbation parameters for Lucas-Kanade method
- STEPS nowcasts can now be calculated in dBZ, no need to convert to rain rate first
- Functionality for regenerating perturbed motion fields (for a given `SEED`)
- Projection metadata is now stored in output file
- Configuration parameters and their values are now stored in output file
- Added new configuration parameters for controlling program flow
- Added configuration for heavy rainfall event in Helsinki on 23 Aug 2019

### Changed
- Renamed readme.md to README.md
- Deterministic nowcast uses now extrapolation
- Old deterministic nowcast is renamed as "unperturbed nowcast"
- `utcnow_floored()` function was moved to `utils` module
- Edited "dev" and "verification" parameters a bit

### Removed
- Extra dependencies that were unused or no longer needed

## 2019-05-06
### Added
- New parameters: `SEED`, `ZR_A`, `ZR_B`, `SCALE_ZERO`, `SCALER`, `FIELD_VALUES`
- Now it is possible to set random number generator seed via `SEED` parameter
- Now R(Z)-relation coefficients _a_ and _b_ can be set via parameters `ZR_A` and `ZR_B`
- Nowcasts can be stored either in dBZ or mm/h units. This is chosen via `FIELD_VALUES` parameter
- Scaling parameter in output file can now be set via parameter `SCALER`
- Scaling offset in output file can now be set via `SCALE_ZERO` parameter
- Program uses nowcast data array's minimum non-NaN value as scaling offset, unless given via configuration parameters
- Parameters `SEED` and `FIELD_VALUES` are stored in output file's metadata

### Changed
- "Valid for" attribute in output file is now an integer (was: string)
- `OUTPUT_TIME_FORMAT` parameter no longer affects the "Valid for" attribute

## 2019-01-22
- First prototype version given to operational testing

repository: fmidev/fmippn-oper

gha_language: C

repo_name: fmidev/fmippn-oper


text:
# nirvanam-watch

[Nirvanam](http://www.nirvanam.jp/) is a South Indian specialty restaurant
in Tokyo, Japan and located near my office.
I'm a just a fan and don't have no connection with them,
but I'm making application to check "today's lunch special menu" automatically.
The menu is published on their [Facebook page](https://www.facebook.com/NirvanamTokyo/).

## Install
At first, you have to get Google Cloud Vision API key from [Google API Console](https://console.developers.google.com).
Then put it into settings file. If settings file doesn't exist, it can be created from sample file.

    copy settings.py.sample settings.py
    echo "GOOGLE_API_KEY = 'YourGoogleAPIKey'" >> settings.py

repository: kikei/nirvanam-watch

repo_name: kikei/nirvanam-watch


text:
# Evaluate

Evaluate expression started with `__putout_evaluate: `. Part of [`eslint-plugin-putout`](https://github.com/coderaiser/putout/tree/master/packages/eslint-plugin-putout#rules).
Provided code is processed with [`@putout/plugin-declare`](https://github.com/coderaiser/putout/tree/master/packages/plugin-declare):

```js
__putout_evaluate: join('hello', ' ', 'world');
```

and converted to:

```js
const fn = (__filename, __dirname, require) => {
    const {join} = require('path');
    return join('hello', ' ', 'world');
};
```

When you want to evaluate expressions `source` of `ImportDeclaration`:

## ❌ Example of incorrect code

```js
import {readFile} from '__putout_evaluate: `./` + basename(__filename).replace(`.spec.js`, `.js`)';
```

## ✅ Example of correct code

```js
import {readFile} from './hello.js';
```

repository: coderaiser/putout

repo_name: coderaiser/putout


text:
## Git

### Delete local branches

When you have merged and deleted a branch on github this command will delete the local branches that dont exist remotely.

```bash
$ git branch -vv | grep 'origin/.*: gone]' | awk '{print $1}' | xargs git branch -d
```

### Add something to .gitignore

Refreshes the tracking of your files. Super useful for adding new things to your .gitignore file.

```bash
$ git rm -r --cached .
```

### Git stash

```bash
# to save changes in a stash
$ git stash save "optional message for yourself"

# view stash list
$ git stash list

# apply the stash
$ git stash apply

# apply the stash and remove the files from the stash
$ git stash pop

# clear the entire stash
$ git stash clear
```

repository: velasco/portfolio-site

repo_name: velasco/portfolio-site


text:
PmodJSTK2 IP
============

Using the IP in Vivado
------------
A tutorial for using Pmod IP cores in  Vivado is available [here](https://reference.digilentinc.com/learn/programmable-logic/tutorials/pmod-ips/start).
At the step for connecting reference clocks, be sure to connect the IP's
ext_spi_clk port to a 16 MHz clock. The 16 MHz clock can be generated by either
the Clocking Wizard or the Memory Interface Generator (MIG). Instructions are
available for both approaches in the tutorial.

Demo Program in Xilinx SDK
------------
There are two demo programs for the PmodJSTK2 IP, basic_example.c and
calibrate_example.c.

The basic_example program reads the X and Y position of the joystick and maps
those values to the LED. If either the trigger button or the joystick button are
pressed, the LED will turn green. The program also prints the X and Y position
of the joystick and messages indicating when the joystick or trigger buttons are
pressed to the terminal.

The calibrate_example program runs through the calibration process for the
PmodJSTK2. After programming your board, wait for the blue blinking light on the
JSTK2 to turn on. Then, move the joystick in a circle at the far edges of where
it can move. After completing one full circle, release the joystick. Let the
joystick stay still until the green light flashes twice, this indicates that the
calbration process is complete. Status messages are printed to the terminal.

To see text output from the example programs, you will need to open a serial
terminal, such as TeraTerm. Settings for the terminal will vary depending on
your board.

For Zynq Projects, apply the following settings:
- Baud rate: 115200
- Data bits: 8
- Parity:    none
- Stop bits: 1

For MicroBlaze projects, apply the settings according to the AXI Uartlite IP
configurations. These settings can be found by double clicking the AXI Uartlite
IP in the block design and clicking the IP Configuration tab. By default, these
settings are:
- Baud rate: 9600
- Data bits: 8
- Parity:    none
- Stop bits: 1

repository: Digilent/vivado-library

repo_name: Digilent/vivado-library


text:
# 6502 Documentation

 Resources:
   - [Online 6502 Emulator](https://skilldrick.github.io/easy6502/)
   - [Overflow Flag explained mathematically](http://www.righto.com/2012/12/the-6502-overflow-flag-explained.html)
   - [In-depth analysis of opcodes](http://www.llx.com/~nparker/a2/opcodes.html)

----
## Status Flags

    NVsB DIZC
    |||| ||||
    |||| |||`- Carry: 1 if last addition or shift resulted in a carry, or if last subtraction resulted in no borrow
    |||| ||`-- Zero: 1 if last operation resulted in a 0 value
    |||| |`--- Interrupt: Interrupt inhibit
    |||| |       (0: /IRQ and /NMI get through; 1: only /NMI gets through)
    |||| `---- Decimal: 1 to make ADC and SBC use binary-coded decimal arithmetic
    ||||         (ignored on second-source 6502 like that in the NES)
    ||``------ s: No effect, used by the stack copy, see note below
    |`-------- Overflow: 1 if last ADC or SBC resulted in signed overflow, or D6 from last BIT
    `--------- Negative: Set to bit 7 of the last operation

----
## OpCodes

![6502 OpCodes Page 1](https://github.com/rossdrew/emuRox/blob/master/docs/6502/img/6502_ISR_first_page.gif "6502 OpCodes Page 1")
![6502 OpCodes Page 2](https://github.com/rossdrew/emuRox/blob/master/docs/6502/img/6502_ISR_second_page.gif "6502 OpCodes Page 2")

----

## Block Diagram

![6502 Block Diagram](https://github.com/rossdrew/emuRox/blob/master/docs/6502/img/6502_block_diagram.jpg "6502 Block Diagram")

repository: rossdrew/emuRox

gha_language: Java

repo_name: rossdrew/emuRox


text:
# Visual Recognition Demo
[![Build Status](https://travis-ci.org/watson-developer-cloud/visual-recognition-nodejs.svg?branch=master)](https://travis-ci.org/watson-developer-cloud/visual-recognition-nodejs?branch=master)
[![codecov.io](https://codecov.io/github/watson-developer-cloud/visual-recognition-nodejs/coverage.svg?branch=master)](https://codecov.io/github/watson-developer-cloud/visual-recognition-nodejs?branch=master)

The [Visual Recognition][visual_recognition_service] Service uses deep learning algorithms to analyze images for scenes, objects, faces, text, and other subjects that can give you insights into your visual content. You can organize image libraries, understand an individual image, and create custom classifiers for specific results that are tailored to your needs.

Give it a try! Click the button below to fork into IBM DevOps Services and deploy your own copy of this application on Bluemix.

[![Deploy to Bluemix](https://bluemix.net/deploy/button.png)](https://bluemix.net/deploy?repository=https://github.com/watson-developer-cloud/visual-recognition-nodejs)

## Getting Started

1. You need a Bluemix account. If you don't have one, [sign up][sign_up]. Experimental Watson Services are free to use.

2. Download and install the [Cloud-foundry CLI][cloud_foundry] tool if you haven't already.

3. Edit the `manifest.yml` file and change `<application-name>` to something unique. The name you use determines the URL of your application. For example, `<application-name>.mybluemix.net`.
  ```yaml
  ---
  declared-services:
    visual-recognition-service:
      label: watson_vision_combined
      plan: free
  applications:
  - name: <application-name>
    path: .
    command: npm start
    memory: 512M
    services:
    - visual-recognition-service
    env:
  NODE_ENV: production
  ```

4. Connect to Bluemix with the command line tool.

  ```sh
  cf api https://api.ng.bluemix.net
  cf login
  ```

5. Create the Visual Recognition service in Bluemix.
  ```sh
  cf create-service watson_vision_combined free visual-recognition-service
  cf create-service-key visual-recognition-service myKey
  cf service-key visual-recognition-service myKey
  ```

6. Create a `.env` file in the root directory by copying the sample `.env.example` file using the following command:

  ```none
  cp .env.example .env
  ```
  You will update the `.env` with the information you retrieved in steps 5 and 6

  The `.env` file will look something like the following:

  ```none
  VISUAL_RECOGNITION_API_KEY=
  ```

7. Install the dependencies you application need:

  ```none
  npm install
  ```

8. Start the application locally:

  ```none
  npm start
  ```

9. Point your browser to [http://localhost:3000](http://localhost:3000).

10. **Optional:** Push the application to Bluemix:

  ```none
  cf push
  ```

After completing the steps above, you are ready to test your application. Start a browser and enter the URL of your application.

            <your application name>.mybluemix.net

For more details about developing applications that use Watson Developer Cloud services in Bluemix, see [Getting started with Watson Developer Cloud and Bluemix][getting_started].

## Environment Variables

  - `VISUAL_RECOGNITION_API_KEY` : This is the API key for the vision service, used if you don't have one in your bluemix account.
  - `PRESERVE_CLASSIFIERS` : Set if you don't want classifiers to be deleted after one hour. *(optional)*
  - `PORT` : The port the server should run on. *(optional, defaults to 3000)*
  - `OVERRIDE_CLASSIFIER_ID` : Set to a classifer ID if you want to always use a custom classifier. This classifier will be used instead of training a new one. *(optional)*

## Changing the Included Images

### Sample Images

The sample images are the first 7 images when the site loads.  They
are called from a Jade mixin found in
`views/mixins/sampleImages.jade`.  If you just want to replace those
images with different images, you can replace them in
`public/images/samples` and they are numbered 1 - 7 and are `jpg`
formatted.

### Custom Classifier Bundles

Adding new/different custom classifer bundles is much more invovled.
You can follow the template of the existing bundles found in
`views/includes/train.jade`.

Or, you can train a custom classifier using the api or the form and
then use the classifier ID.

## Getting the Classifier ID

When you train a custom classifier, the name of the classifier is
displayed in the test form.

![Classifier ID Tooltip](screengrab-tooltip.png)

If you hover your mouse over the classifier name, the classifier ID
will be shown in the tooltip. You can also click on the name, and it
will toggle between the classifier name and the classifier ID.

You can then use this custom classifier id by placing it after the hash
in the request URL.  For example, lets say you are running the system
locally, so the base URL is `http://localhost:3000` and then you train
a classifier.  This newly trained classifier might have an id like
`SatelliteImagery_859438478`.   If you wanted to use this classifier
instead of training a new one, you can navigate to
`http://localhost:3000/train#SatelliteImagery_859438478` and use the
training form with your existing classifier.

## License

  This sample code is licensed under Apache 2.0. Full license text is available in [LICENSE](LICENSE).

## Contributing

  See [CONTRIBUTING](CONTRIBUTING.md).

## Open Source @ IBM
  Find more open source projects on the [IBM Github Page](http://ibm.github.io/).

### Privacy Notice

This node sample web application includes code to track deployments to Bluemix and other Cloud Foundry platforms. The following information is sent to a [Deployment Tracker][deploy_track_url] service on each deployment:

* Application Name (`application_name`)
* Space ID (`space_id`)
* Application Version (`application_version`)
* Application URIs (`application_uris`)

This data is collected from the `VCAP_APPLICATION` environment variable in IBM Bluemix and other Cloud Foundry platforms. This data is used by IBM to track metrics around deployments of sample applications to IBM Bluemix. Only deployments of sample applications that include code to ping the Deployment Tracker service will be tracked.

### Disabling Deployment Tracking

Deployment tracking can be disabled by removing `require('cf-deployment-tracker-client').track();` from the beginning of the `server.js` file at the root of this repo.

[deploy_track_url]: https://github.com/cloudant-labs/deployment-tracker
[service_url]: https://www.ibm.com/watson/services/visual-recognition/
[cloud_foundry]: https://github.com/cloudfoundry/cli
[visual_recognition_service]: https://www.ibm.com/watson/services/visual-recognition/
[sign_up]: https://console.ng.bluemix.net/registration/
[getting_started]: https://console.bluemix.net/docs/services/watson/index.html#about
[node_js]: http://nodejs.org/
[npm]: https://www.npmjs.com


text:
# Scala Priority Queue

[![Build Status](https://travis-ci.org/paulporu/flexible-user-queue.svg?branch=master)](https://travis-ci.org/paulporu/flexible-user-queue)

This Scala class implements a flexible priority queue using a min-heap. The code is based on the Scala collection [PriorityQueue.scala](https://github.com/scala/scala/blob/2.12.x/src/library/scala/collection/mutable/PriorityQueue.scala), but the advantage here is that all the operations are implemented so the min-heap paradigm stays true at all times. This means whatever operation you do on this priority queue the output will always keep / yield the elements of the queue ordered by priority, which is not the case in the default Scala implementation.

One of the main applications for this is to manage physical user queues. As such a few extra utility functions that you would not find in a regular priority queue implementation were thrown in for good measure (remove, getAllByPriority, etc).

## Setup

The library has been released to Maven Central so you can use it by simply listing it as a dependency in your build.sbt:
```scala
"com.github.paulporu" %% "flexible-user-queue" % "1.2"
```
You can also have a look at [this Play application](https://github.com/paulporu/Play-User-Queue) for an example of how to use this priority queue in your own project.

## Usage

Import the class in your code:
```scala
import com.github.paulporu.PriorityQueue
```

The following functions are now available.
```scala
val emptyQueue = new PriorityQueue[Int]

// Returns true
emptyQueue.isEmpty

var queue = PriorityQueue(1)

// Returns 1, queue remains unchanged
queue.head

// Returns 1, queue is now empty
queue.dequeue()

// Adds 3 to the queue
queue += 3

// Adds the elements of the List to the queue while keeping the min priority of the heap, so now queue = PriorityQueue(1, 3, 12, 5)
val elements = List(5,12,1)
queue ++= elements

// Returns the element with index 2 and deletes it from the queue
queue.remove(2)

// Returns a List containing all elements of the queue sorted ascendingly by priority
queue.getAllByPriority()

// Prints the queue as a String
queue.toString()

// Empties the queue
queue.clear()
```

## Dependencies

[Scalatest](http://www.scalatest.org/) was used in combination with the [scoverage SBT plugin](https://github.com/scoverage/sbt-scoverage) for unit testing. [Scalastyle](http://www.scalastyle.org/) was used because it's always good to follow some guidelines. The [Sonatype SBT plugin](https://github.com/xerial/sbt-sonatype) was used to release the library to the Maven Central repository.

[Scoverage](https://github.com/scoverage/scalac-scoverage-plugin) shows on the current version of this library (v1.2) a statement coverage of 89.16 % and a branch coverage of 78.57 %.

## License

MIT License

repository: paulporu/flexible-user-queue

repo_name: paulporu/flexible-user-queue


text:
---
hrs_structure:
  division: '1'
  volume: '2'
  title: '9'
  chapter: '105'
  section: 105-9
type: hrs_section
tags:
  - Government
menu:
  hrs:
    identifier: HRS_0105-0009
    parent: HRS0105
    name: 105-9 Duty of performance
weight: 69045
title: Duty of performance
full_title: 105-9 Duty of performance
---
**§105-9 Duty of performance.** The duty of carrying out sections 105-6 to 105-8, insofar as they relate to motor vehicles, the property, or under the control, of the State, shall be vested in the comptroller, and, insofar as they relate to the several counties, shall be vested in the respective county councils, and insofar as they relate to independent boards and commissions having charge of their own funds shall be vested in the respective boards or commissions. [L 1919, c 227, §3; RL 1945, §464; am L 1949, c 389, §1(c); RL 1955, §7-18; am L Sp 1959 2d, c 1, §12; [HRS §105-9](/title-9/chapter-105/section-105-9/)]

Revision Note

"County councils" substituted for "boards of supervisors or city council".

repository: SamMade/BlueAndKrabby

repo_name: SamMade/BlueAndKrabby


text:
[CoreProtect Lookup Web Interface (CoLWI)](https://github.com/chuushi/CoreProtect-Lookup-Web-Interface)
===============================================================================
*A flexible lookup web interface for CoreProtect 2.*

![Imgur](https://i.imgur.com/gre6LpC.png)

**Version:** [v1.0.0-pre2](https://github.com/chuushi/CoreProtect-Lookup-Web-Interface/releases/latest)

*[Changelog](changelog.md) | [Contributing](contributing.md)*

This is a _feature-packed_ web application that gives you the power to look up
anything CoreProtect is capable of logging in the most efficient way.
[CoreProtect, a Minecraft plugin,](https://www.spigotmc.org/resources/8631/)
is developed by Intellii.

This web app is capable of looking up logged data as if doing it from the game.
Some filters are ported to this plugin, such as:

* Lookup by action
* Lookup by username
* Lookup by block name
* Lookup by time

In addition, this plugin makes it possible to:

* Lookup data by coordinates and world
* View more than four results per page
* Filter out rolled back data
* ~~View what was written on the signs~~ (TBD)
* Search by keywords

# Setup

## Prerequisites

- A web server with **PHP 5.6** or above
    - Required extensions: PDO, PDO-SQLITE or PDO-MYSQL
- A CoreProtect database used by **CoreProtect 2.12** or above.
    - If using SQLite in real-time, the web server must be on the same machine
      as the Minecraft server.

## Download

- **Option 1:** `git clone`
    - This option makes it easier to update the web app.
    - Run the following command in somewhere on the web server.
```sh
git clone https://github.com/chuushi/CoreProtect-Lookup-Web-Interface.git
```

- **Option 2:** Download
    - Download the
      [latest release `.zip` file](https://github.com/chuushi/CoreProtect-Lookup-Web-Interface/releases/latest).
    - Extract the .zip file somewhere on the web server.

## Configuration

Edit all the necessary configuration from `config.php`.  All fields are
documented in the configuration file.

## Updating

If you used the **option 1** to download the web app, you can run:
```sh
git stash
git pull
git stash pop
```

- `git stash` stashes uncommitted changes
- `git pull` downloads and updates the repository with the latest changes
- `git stash pop` applies the stashed changes into the repository.

If you see this message after running `git stash pop`:
```
CONFLICT (content): Merge conflict in config.php
```

then you must edit the file manually (look for `<<<<<<<`, `=======`, and
`>>>>>>>`) then run:
```sh
git add config.php
```

If you used the **option 2**, then you must re-download the `.zip` file and
manually migrate the `config.php` file over.

# Plugin Links

* [BukkitDev](//dev.bukkit.org/bukkit-plugins/coreprotect-lwi/)
* [Spigot](//www.spigotmc.org/resources/coreprotect-lookup-web-interface.28033/)

~Chuu


text:
# DLL Diagnostic Tools

The `dlldiag` command-line tool provides functionality to assist in identifying the DLL dependencies of an application or library and diagnosing dependency loading issues. It is primarily intended for use when migrating existing applications to Windows containers, where traditional GUI-based tools are unavailable. Identifying the minimal set of dependencies for an application facilitates a workflow where the required DLL files can be copied from the [mcr.microsoft.com/windows](https://hub.docker.com/_/microsoft-windows) base image into the [mcr.microsoft.com/windows/servercore](https://hub.docker.com/_/microsoft-windows-servercore) base image, thus maximising application compatibility whilst maintaining the minimum possible image size.

## Contents

- [Requirements and installation](#requirements-and-installation)
- [Usage](#usage)
- [Legal](#Legal)

## Requirements and installation

The `dll-diagnostics` Python package requires the following:

- Python 3.6 or newer
- Windows Server 2016 or newer, or Windows 10 version 1607 or newer
- [Microsoft Visual C++ Redistributable for Visual Studio 2015-2019](https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads)
- [Debugging Tools for Windows 10 (WinDbg)](https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/debugger-download-tools) (only needed for running the `dlldiag trace` command)

You can install the package by running the following command:

```
pip install dll-diagnostics
```

If you don't need the package on your host system then you can [download a prebuilt container image from Docker Hub](https://hub.docker.com/r/adamrehn/dll-diagnostics) to start using the `dlldiag` command inside a Windows container.

## Usage

The `dlldiag` command-line tool provides the following subcommands:

- `dlldiag deps`: this subcommand lists the direct dependencies for a module (DLL/EXE) and checks if each one can be loaded. [Delay-loaded dependencies](https://docs.microsoft.com/en-us/cpp/build/reference/linker-support-for-delay-loaded-dlls) are also listed, but indirect dependencies (i.e. dependencies of dependencies) are not.

- `dlldiag docker` this subcommand generates a Dockerfile suitable for using the `dlldiag` command inside a Windows container, allowing the user to optionally specify the base image to be used in the Dockerfile's `FROM` clause. This is handy when you want to extend an existing image of your choice, rather than simply extending the Windows Server Core image as the [prebuilt images from Docker Hub](https://hub.docker.com/r/adamrehn/dll-diagnostics) do.

- `dlldiag graph` this subcommand runs executable modules with an injected DLL that uses [Detours](https://github.com/microsoft/Detours) to instrument calls to [LoadLibrary()](https://docs.microsoft.com/en-us/windows/win32/api/libloaderapi/nf-libloaderapi-loadlibraryw) so the call hierarchy can be reconstructed. This is handy when you want to see which indirect dependencies are being loaded by an executable's direct dependencies or want to identify dependencies that are loaded programmatically at runtime.

- `dlldiag trace`: this subcommand uses the Windows debugger to trace a [LoadLibrary()](https://docs.microsoft.com/en-us/windows/win32/api/libloaderapi/nf-libloaderapi-loadlibraryw) call for a module (DLL/EXE) and provide detailed reports of the results. The trace makes use of the Windows kernel [loader snaps](https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/show-loader-snaps) feature to obtain fine-grained information, as discussed in [Junfeng Zhang's blog post "Debugging LoadLibrary Failures"](https://blogs.msdn.microsoft.com/junfeng/2006/11/20/debugging-loadlibrary-failures/). The trace captures information about both indirect dependencies and delay-loaded dependencies.

## Legal

Copyright © 2019-2023, Adam Rehn. Licensed under the MIT License, see the file [LICENSE](https://github.com/adamrehn/dll-diagnostics/blob/master/LICENSE) for details.

Binary distributions of this package include parts of [Detours](https://github.com/microsoft/Detours) in object form. Detours is Copyright (c) Microsoft Corporation and is [licensed under the MIT license](https://github.com/microsoft/Detours/blob/master/LICENSE.md).

repository: adamrehn/dll-diagnostics

repo_name: adamrehn/dll-diagnostics


text:
# Plugin Guide #

## example1.js ##

This file shows how to write a quick script to connect your bot instance to a server.

### Get a HipChat user instance ###

HipBot is a user just like any other user, have your admin create a new user and you can find its XMPP/Jabber Account Information under that users settings.

The account details are commented in the example1.js code.

### Live testing ###

You should be able to run the script locally and invite your bot to a private room and test out some of the commands to ensure you've set it up correctly. Careful though, hipbot can become quite chatty if left unchecked.

## Building your own plugin ##

The bot is created by the lib/createBot.js module and its `loadPlugin` method used to load user specified plugin bot commands. This wraps the HipChat API nicely so you can focus on writing commands and eating donuts.

The lib/bot.js is the API wrapper code. You can refer to this file to see all options available to the HipChat bot.

The examples/plugins/template.js is intended to be copied to help you get going on your new plugin. Refer to the code to see what sections to start filling out.

### Testing ###

So... do you have any free time? ;-)

Since the commands are usually simple, testing in line works well enough for the time being.

**Happy botting!**

repository: kingnebby/hipchat-bot

repo_name: kingnebby/hipchat-bot


text:
Members are required to enter into contractual agreements with the KochiOrgBook Consortium.

## **Stewards**

- [KOBPIU Steward Agreement](contracts/steward_agreement.md)
- [Transaction Author Agreement](contracts/trans_auth_agreement.md)
- [Transaction Endorser Agreement](contracts/trans_endorser_agreement.md)
- [Steward Data Processing Agreement](contracts/steward_data_processing_agreement.md)

repository: hyperledgerkochi/KochiOrgBook

repo_name: hyperledgerkochi/KochiOrgBook


text:
# Topic

> 【人權教育】人權危機：被世界領袖漠視的原因 (World Leaders are Failing Human Rights. Here's Why. | NYT Opinion)

> Most of our political leaders are morally weak, shortsighted and mediocre.

> 大部分的政治領導人都道德感薄弱、目光短淺且能力不足。

[![Image](https://cdn.voicetube.com/assets/thumbnails/8Dp8t-0HR-o.jpg)](https://www.youtube.com/embed/8Dp8t-0HR-o?rel=0&showinfo=0&cc_load_policy=0&controls=1&autoplay=1&iv_load_policy=3&playsinline=1&wmode=transparent&start=72&end=79&enablejsapi=1&origin=https://tw.voicetube.com&widgetid=1)

Host: Celeste

Today issue: Freedom is like the air you breathe. You don’t think about it until you are gasping for your last breath.

[Host record](https://cdn.voicetube.com/tmp/everyday_records/celeste.chen/3215.mp3)

## learning points
1. _
	* mediocre [ˋmidɪ͵okɚ] (adj.) 平庸的；不夠好的
		- The manager was extremely disappointed by his mediocre performance.
			+ 經理對他平庸的表現感到非常失望。

2. _
	* shortsighted [ˋʃɔrtˋsaɪtɪd] (adj.) 近視的；目光短淺的
		- You can't be short-sighted if you want to launch a start-up.
			+ 如果你想要啟動一個初創企業，你不能短視。
		- I am nearsighted or I am short-sighted.
			+ I have myopia/hyperopia.

3. _
	* morally [ˋmɔrəlɪ] (adv.) 道德上
		- What you did was legal but morally wrong?
			+ 你做了什麼是合法的，但在道德上是錯誤的？
		-  morally bankrupt/  morally weak
	* moral [ˋmɔrəl] (n.) 道德
		- morals => 道德
		- ethics => 倫理

4. _
	* political [pəˋlɪtɪk!] (adj.) 政治的
		- Chinese human rights activist Liu Xiaobo was imprisoned for political reasons for 11 years.
			+ 中國人權活動家劉曉波11年因政治原因被監禁。


text:
# Binary Search Trees
# All source codes to operations performed on BST

What is the difference between Binary and Binary Search Tree?
-> In BST the left of a particular node has to smaller than the right of the node. Wheresas in binary tree this is not necessary.
# In BST --> (Node->left > Node > Node->right)
![image](https://user-images.githubusercontent.com/83713146/134126265-7c14b586-7846-4b99-aa7a-5353f99a30ab.png)

branch_name: refs/heads/main


text:
---
layout: post
title: OWASP's BWA and sql injection notes
---

Mutillae has a great SQLMAP target on it. I have been using [owasp's bwa vm](http://sourceforge.net/projects/owaspbwa/files/latest/download) to work on more web apps.

[websec's writeup on sql injection filtering](https://websec.wordpress.com/2010/03/19/exploiting-hard-filtered-sql-injections/) has been helping a lot with filtering evasion.


text:
# Minio

Minio is a high performance distributed object storage server, designed for large-scale private cloud infrastructure.

## Moved

This plan has been moved. For more information see [here](https://github.com/habitat-sh/core-plans#additional-plans)

repository: JarvusInnovations/habitat-core-plans

repo_name: JarvusInnovations/habitat-core-plans


text:
# TANK: Mandalae Unveils New Assault Tank: the AV-4A

Posted by: mandalae

Nations involved: Mandalae

The Mandalean military just unveiled the new assault tank that will be used throughout the armed forces: the AV-4A.

The AV-3C, which has been used since the early 1970s, was proven to be far too outdated and lackluster in its performance, which was all the more clear during the Mandalaean takeover of Borneo.

The AV-4A is equipped with a 90mm main armament, and can travel up to 85 kph. It is designed to easily maneuver in and out of combat, and its low profile enables it to hide behind cover.

Images of the AV-4A can be seen here:

http://i.imgur.com/pBHRdEO.jpg

http://i.imgur.com/GbSOeWD.jpg


text:
#  Silicon Valley’s gender gap is the result of computer-game marketing 20 years ago
  - **Programming:** is fast becoming the most lucrative skill you can have in the modern world.
  - **The experience gap widens:**This led to what researcher Jane Margolis calls the `experience gap.`

# Why diversity matters to your tech company?
  - As the push for diversity in tech continues, a growing number of companies and leaders are confronting the topic for the first time.
  - Diversity efforts are most successful when they’re driven by a commitment from company leaders.
  - And meaningful commitment requires leaders to understand why diversity matters.

# Diverse companies perform better:
  - Given that diverse teams are smarter and more creative than homogeneous ones, it is unsurprising that a wealth of research shows a strong correlation between diverse organizations and positive financial outcomes.


text:
# One-Resharpened Visual Studio Code Theme
A dark theme for Visual Studio Code based on One Dark Vivid.

## Screenshot
![](https://raw.githubusercontent.com/lenconda/vscode-theme-darkplusplusplus/master/screenshot.png?raw=true)

## Repository
* [GitHub Repository](https://github.com/lenconda/vsc-theme-one-resharpened)

repository: lenconda/vscode-theme-darkplusplusplus

repo_name: lenconda/vscode-theme-darkplusplusplus


text:
ActiveMQ

Building and saving Apache ActiveMQ

Step 1) Build the ActiveMQ builder image (once per release)
	$ docker build -t activemq_builder .
Step 2) Compile and package ActiveMQ binary
	$ docker run --rm -v `pwd`:/ws activemq_builder bash -l -c "cd /ws; ./build.sh"

repository: pratham-m/build-scripts

gha_language: Shell

repo_name: pratham-m/build-scripts


text:
## Compatibility Testing Scenario Usage
Pre-requirements: Both provider and consumer can not use the same `POM`, because you cannot guarantee that all the codes you write Dubbo 2.0 and 3.0 support at the same time,  they must be divided into two independent projects. This is also applicable in daily business compatibility testing

Add new grammar to `case-versions.conf`:
```yaml
# 原常规配置
# dubbo.version=2.7*, 3.*
spring.version=4.*, 5.*

# 支持不同的 servcie 应用，配置不同的 dubbo 版本依赖，与 dubbo.version 二选一
# 为防止构建用例倍级增长，不建议配置多个版本
# dubbo.{service}.verison 中的 service 可以任意自定义
dubbo.provider.version=3.*
dubbo.consumer.version=2.7.*
```
And then in each consumer and provider project, you can configure `POM`'s properties as follows:
```xml
<!-- consumer side -->
<properties>
    <dubbo.consumer.version>2.7.13</dubbo.consumer.version>
</properties>

<!-- provider side -->
<properties>
    <dubbo.provider.version>2.7.13</dubbo.provider.version>
</properties>
```

If we have the env of `DUBBO_VERSION=3.0.3-SNAPSHOT,2.7.13`, when the Integration Tests trigger, these properties will be overwritten by maven, for example:
```shell
mvn -Ddubbo.provider.version=3.0.3-SNAPSHOT -Ddubbo.consumer.version=2.7.13 -Dspring.version=4.3.16.RELEASE
```

But in the dubbo-samples's Dubbo 3 CI env, there only has `DUBBO_VERSION=3.0.3-SNAPSHOT`, we have to specify one side's version to prevent the test being ignored, for example:
```yaml
dubbo.provider.version=3.*
dubbo.consumer.version=2.7.13 # <= specific version
```

repository: apache/dubbo-samples

repo_name: apache/dubbo-samples


text:
---
hasBody: true
date: 2019-04-17
title: Split Screen Without Tabs
technologies: []
topics: [editing, testing]
author: pwe
subtitle: Get your code and tests side-by-side without resorting to tabs.
seealso:
  - title: Splitting and unsplitting editor window
    href: https://www.jetbrains.com/help/pycharm/managing-editor-tabs.html#splitting-and-unsplitting-editor-window
  - title: Tabs and split windows
    href: https://www.jetbrains.com/help/pycharm/migrating-from-text-editors.html#tabs_split_windows
thumbnail: ./thumbnail.png
cardThumbnail: ./card.png
shortVideo:
  poster: ./poster_short.png
  url: https://www.youtube.com/watch?v=-yiOTOK1xVY
longVideo:
  poster: ./poster_long.png
  url: https://youtu.be/VcqbOtn1s0w
leadin: |
    *Get into TDD focus with side-by-side editors.*

    Testing means three things: code that you're testing, the code for the test,
    and the output from the test runner. Arrange all 3 to get into the testing flow.

---

As discussed previously, disabling tabs and focusing on the keyboard helps
productivity. But without tabs, how can I see two files at once? For example,
the code I'm testing and the tests I'm writing?

You can still split screens without tabs. Simply use the `Split Vertically`
action (no default keybinding so use `Find Action`) and you'll get two frames.
Then open your to-be-tested code on the left and test code on the right.

By default, PyCharm visual test runner tool window is at the bottom. This gives a
familiar "TDD" (test-driven development) visual orientation: left for code, right
for test, bottom for results. (Although on wide monitors, docking the test tool
window on the right might make more sense.)

How to move between the left and right "Split Vertically" frames? The
`Go To Next Splitter` action (`Alt-Tab` Win/Linux/macOS) is a convenient keybinding.
Since these are the two files you are switching between editing, our old friend the
`Recent Files` action (`Ctrl-E` Win/Linux, `Cmd-E` macOS) is a nice, already-memorized
key sequence.


text:
# WritingTips
"Good scientific writing is not a matter of life and death; it is much more serious than that."

- 2010-Matt Welsh-[The Paper Formatting Gestapo](http://matt-welsh.blogspot.com/2010/01/paper-formatting-gestapo.html)
- 2012-Matt Welsh-[In Defense of the Scientific Paper](http://matt-welsh.blogspot.com/2012/07/in-defense-of-scientific-paper.html)
- 2014-Bill Freeman-[How to write a good CVPR submission](https://billf.mit.edu/sites/default/files/documents/cvprPapers.pdf) (mark!)
- 2015-Jia-Bin Huang-[Computer Vision Online Meetup](https://www.youtube.com/watch?v=cfn7oYPa53Y&t=4113s)
- 2017-Ming-Hsuan Yang-[How to Get Your CVPR Paper Rejected](https://www.youtube.com/watch?v=jp_TGMU4ASI) [[Slide](http://faculty.ucmerced.edu/mhyang/course/eecs286-2016/lectures/How%20to%20get%20your%20CVPR%20paper%20rejected.pptx)]
- [Paper_Writing_Tips](https://github.com/MLNLP-World/Paper_Writing_Tips)
<!-- - [Some Collected Resources for New PhD Students from Prof. Philip Torr](https://www.robots.ox.ac.uk/~phst/) -->

https://twitter.com/jbhuang0604/status/1490559552475041795

repository: MingSun-Tse/WritingTips

repo_name: MingSun-Tse/WritingTips


text:
# Vue GWT and Widgets

For easy backward compatibility it's possible to wrap any Vue GWT Component in a GWT `Widget`.
For this you need to use `VueGwtWidget`.

## Adding the dependency

`VueGwtWidget` is in it's own Maven module.
If you want to use it, add this Maven Dependency to your `pom.xml`:
```xml
<dependency>
	<groupId>com.axellience</groupId>
	<artifactId>vue-gwt-gwt2</artifactId>
	<version>${vue-gwt.version}</version>
</dependency>
```
And this in your `gwt.xml`:
```xml
<inherits name='com.axellience.vuegwt.GWT2'/>
```

## Instantiating a DemoComponent

Let's instantiate a `DemoComponent` with `VueGwtWidget`:

***GwtIndex.html***

```html
<div id="childComponentAttachPoint"></div>
```

***RootGwtApp.java***

```java
public class RootGwtApp implements EntryPoint {
    public void onModuleLoad() {
        // Create a VueGwtPanel, it's a regular GWT Widget and can be attached to any GWT Widget
        VueGwtWidget<DemoComponent> vueGwtWidget = new VueGwtWidget<>(DemoComponent.class);

        // Attach it to inside our DOM element
        RootPanel.get("childComponentAttachPoint").add(vueGwtWidget);
    }
}
```

## Accessing our Vue Instance

It's even possible to interact with our instantiated `Vue`.

Let's say our `DemoComponent` has a method `increaseCounter()`.
We can do:

```java
VueGwtWidget<DemoComponent> vueGwtWidget = new VueGwtWidget<>(DemoComponent.class);
RootPanel.get("childComponentAttachPoint").add(vueGwtWidget);

vueGwtWidget.getComponent().increaseCounter();
```

## Cleaning Up
If you don't need your `VueGwtWidget` anymore, you can destroy it's Vue instance by calling:

```java
vueGwtWidget.getComponent().vue().$destroy();
```

repository: VueGWT/vue-gwt

branch_name: refs/heads/develop

repo_name: VueGWT/vue-gwt


text:
# How to bump up Zipkin Lens dependency

Because SkyWalking embeds Zipkin Lens UI as a part of the SkyWalking UI, and Zipkin Lens UI contains
a lot of other front-end dependencies that we also distribute in SkyWalking binary tars, so we have
to take care of the dependencies' licenses when we bump up the Zipkin Lens dependency.

Make sure to do the following steps when you bump up the Zipkin Lens dependency:

- Clone the Zipkin project into a directory.

```shell
ZIPKIN_VERSION=<the Zipkin version you want to bump to>
git clone https://github.com/openzipkin/zipkin && cd zipkin
git checkout $ZIPKIN_VERSION

cd zipkin-lens
```

- Create `.licenserc.yaml` with the following content.

```shell
cat > .licenserc.yaml << EOF
header:
  license:
    spdx-id: Apache-2.0
    copyright-owner: Apache Software Foundation
dependency:
  files:
    - package.json
  licenses:
    - name: cli-table
      version: 0.3.1
      license: MIT
    - name:  domutils
      version: 1.5.1
      license: BSD-2-Clause
    - name: rework
      version: 1.0.1
      license: MIT
EOF
```

- Create license template `LICENSE.tpl` with the following content.

```
{{ range .Groups }}
========================================================================
{{ .LicenseID }} licenses
========================================================================
The following components are provided under the {{ .LicenseID }} License. See project link for details.
{{- if eq .LicenseID "Apache-2.0" }}
The text of each license is the standard Apache 2.0 license.
{{- else }}
The text of each license is also included in licenses/LICENSE-[project].txt.
{{ end }}

    {{- range .Deps }}
    https://npmjs.com/package/{{ .Name }}/v/{{ .Version }} {{ .Version }} {{ .LicenseID }}
    {{- end }}
{{ end }}
```

- Make sure you're using the supported NodeJS version and NPM version.

```shell
node -v
# should be v14.x.x
npm -v
# should be 6.x.x
```

- Run the following command to generate the license file.

```shell
license-eye dependency resolve --summary LICENSE.tpl
```

- Copy the generated file `LICENSE` to replace the `zipkin-LICENSE` in SkyWalking repo.

Note: if there are dependencies that license-eye failed to identify the license, you should manually
identify the license and add it to the step above in `.licenserc.yaml`.

repository: parampavar/skywalking

repo_name: parampavar/skywalking


text:
---
layout: post
title:  "Effects of lysozyme-rich milk on intestinal gene expression of malnourished piglets"
date:   2022-09-16
excerpt: "Gene expression and multi-omics intergration to analyze the effect of hLZ-rich milk supplementation on malanourished piglets."
project: true
tag:
- pigs
- hLZ milk
- gene expression
- Omics integration
- project
comments: true
---

## Period

2014 - 2019

## Colaborators

**Responsible:** Raquel Pinho

**PI:** Dr.Elizabeth Maga, University of Californa, Davis, CA - United States

**Colaborator:** Dr. Lydia Garas, University of Californa, Davis, CA - United States

**Colaborator:** Dr. Elizabeth Maga, University of Californa, Davis, CA - United States

**Colaborator:** Dr. Bart Weimer, University of Californa, Davis, CA - United States

**Colaborator:** Dr. Carol Huang, University of Californa, Davis, CA - United States

## Location

* University of California, Davis, CA - United States

## Raquel Pinho's main responsabilities

* Experiment design and project writing.
* Library construction for RNA-sequencing.
* RNA-seq data processing in Linux.
* RNA-seq data analysis in R.
* RNA-seq data visualization in R.
* Weighted co-expression network analysis using WGCNA.
* Integration of intestinal transcriptome, hepatic metabolome and intestinal
microbiota 16S data using MixOmics.
* Validation of NGS results using qPCR for relative gene expression analysis.

## Description

Goat milk containing human lysozyme (hLZ) has shown beneficial effects on microbiome composition, gastro-intestinal (GI) morphology and the clinical condition of pigs. To explore the effect of hLZ milk on intestinal gene expression in malnourished animals, RNA-seq was conducted with tissue from the duodenum, jejunum and ileum of malnourished piglets fed with hLZ milk, regular goat milk or with no milk supplementation. Gene co-expression analysis and pheno- typic correlations were made with WGCNA, while integration of transcriptome with microbiota information and the hepatic metabolite profile was done using mixOmics.

## Data

BioProject: [PRJNA823693](https://www.ncbi.nlm.nih.gov/bioproject/?term=PRJNA823693)

## Publications

* PINHO, R. M.; GARAS L.C.; HUANG B.C; WEIMER B.C.; MAGA, E.A.. Lysozyme-rich milk affects gene expression along the
length of porcine small intestine before and during enteropathogenic Escherichia coli infection. (submitted 2022).
* PINHO, R. M.; GARAS L.C.; HUANG B.C; WEIMER B.C.; MAGA, E.A. Milk from lysozyme transgenic goats influences gene expression in the intestine in a pig
model of malnutrition. XII Transgenic Animal Research Conference (TARC), Lake Tahoe City, CA, United States. 2019.

## More

Github page

Dashboard

repository: RaquelPinho/RaquelPinho

repo_name: RaquelPinho/RaquelPinho