text:
# Jira: [TKT-000](https://clever.atlassian.net/browse/TKT-000)

# Overview:

# Screenshots/GIFs:

# Testing:

- [ ] Unit tests
- Manual tests:
  - [ ] Chrome
  - [ ] Safari
  - [ ] IE11

# Roll Out:

- Before merging:
  - [ ] Updated docs
  - [ ] Bumped version in `package.json`
    - Breaking change?
      - If it is a beta component run `npm version minor`
      - If the component is not in beta run `npm version major`
    - New component or backward-compatible component feature change? Run `npm version minor`
    - Only changing documentation? All good. Skip this step.
  - After creating a new component, make sure to add it to the Components List in `ComponentsView.jsx`. To do so:
    - [ ] Add a screenshot of the component in `docs/assets/img` with the format `<COMPONENT URL LINK>.png`
- After merging:
  - [ ] Deployed updated docs (`make deploy-docs`)
  - [ ] Posted in #eng if I made a breaking change to a beta component

repository: Clever/components

gha_language: TypeScript

repo_name: Clever/components


text:
## 5 resource limits
On the host show `docker stats` and keep them open to watch CPU usage
```PowerShell
PS C:\Users\AdminTechDays> docker stats
CONTAINER ID        NAME                CPU %               PRIV WORKING SET    NET I/O             BLOCK I/O
```
Lines will appear when we start containers
```PowerShell
PS C:\Users\AdminTechDays> docker run --rm --name sql -e sa_password=Passw0rd*123 -e ACCEPT_EULA=Y microsoft/mssql-server-windows-express
Unable to find image 'microsoft/mssql-server-windows-express:latest' locally
latest: Pulling from microsoft/mssql-server-windows-express
3889bb8d808b: Downloading [=======================>                           ]  1.938GB/4.07GB
449343c9d7e2: Download complete
a336350523ea: Download complete
2c12ef99f411: Download complete
8ebb28bb3276: Download complete
3bb8431b46ce: Download complete
a4a938096b3c: Download complete
656eb837f7e6: Download complete
a3d536b0e79d: Download complete
a0aec5f46615: Download complete
64a0f6512541: Download complete
b900d04a68bd: Download complete
VERBOSE: Starting SQL Server
VERBOSE: Changing SA login credentials
VERBOSE: Started SQL Server.
```
You should see CPU usage go over 10% frequently
Now stop the container and start it again with a CPU limit to 3% (we can't limit memory as SQL wouldn't even start)
```PowerShell
PS C:\Users\AdminTechDays> docker stop sql
sql
PS C:\Users\AdminTechDays> docker run --rm --name sql -e sa_password=Passw0rd*123 -e ACCEPT_EULA=Y --cpu-percent 3 microsoft/mssql-server-windows-express
VERBOSE: Starting SQL Server
VERBOSE: Changing SA login credentials
VERBOSE: Started SQL Server.
```
CPU usage should only show quick peaks above 3% but usually stay below

license: MIT

repository: tfenster/presentations

branch_name: refs/heads/master

extension: md

filename: 5 resource limits.md

gha_language: JavaScript

gha_license_id: MIT

license_type: permissive

repo_name: tfenster/presentations


text:
# Assembly language in zxdb

Zxdb supports the following commands for dealing with assembly language:

  * `disassemble` / `di`: Disassemble at the current location (or a given location)

  * `nexti` / `ni`: Step to the next instruction, stepping over function calls.

  * `stepi` / `si`: Step the next instruction, following function calls.

  * `regs`: Get the CPU registers.

zxdb maintains information about whether the last command was an assembly command or a source-code
and will show that information on stepping or breakpoint hits. To switch to assembly-language mode,
type `disassemble`, and to switch back to source-code mode, type `list`.

repository: carbonatedcaffeine/zircon-rpi

repo_name: carbonatedcaffeine/zircon-rpi


text:
BeeKeeper
=========

Look after all the little worker bees.

Getting started
---------------

To deploy a new BeeKeeper instance, clone this repo, and then run::

    $ heroku create
    $ git push heroku master
    $ heroku addons:create heroku-postgresql:hobby-dev
    $ heroku addons:create heroku-redis:hobby-dev
    $ heroku config:set BEEKEEPER_URL=https://<your domain>
    $ heroku scale worker=1
    $ heroku run ./manage.py migrate
    $ heroku run ./manage.py createsuperuser

Django
~~~~~~

Configure a `SECRET_KEY` for the Django instance

    >>> from django.core.management.utils import get_random_secret_key
    >>> get_random_secret_key()
    'qn219x$#ox1$+(m4hdzi-q+5g&o9^7)(x5l8^y51+rrcvs*o3-'

Then set a `SECRET_KEY` configuration variable in your Heroku instance, and
put::

    SECRET_KEY=<your key here>

in the .env file inthe project home directory.

Sendgrid
~~~~~~~~

Sign up for a Sendgrid account, then get an API key. Create a
`SENDGRID_API_KEY` configuration value on Heroku, and put::

    SENDGRID_API_KEY=<your key here>

In the .env file in the project home directory.

Amazon AWS
~~~~~~~~~~

Log into (or sign up for) your Amazon AWS account, and obtain an access key
and secret access key. Create the `AWS_ACCESS_KEY_ID`, `AWS_REGION` and
`AWS_SECRET_ACCESS_KEY` Heroku configuration variables, and put::

    AWS_ACCESS_KEY_ID=<your key here>
    AWS_REGION=<your AWS region>
    AWS_SECRET_ACCESS_KEY=<your secret key here>

In the .env file in the project home directory.

Go to the ECS panel and create an EC2 cluster in an AWS
region of your choice. If you create an "empty" cluster, BeeKeeper
will spin up new instances whenever build tasks are submitted. If you
create a non-empty cluster, those resources will be permanently
available for builds - but you'll also be paying for that availability.

Once you've created your cluster, set the `AWC_EC2_KEY_PAIR_NAME`,
`AWS_ECS_AMI`, `AWS_ECS_CLUSTER_NAME`, `AWS_ECS_SUBNET_ID` and
`AWS_ECS_SECURITY_GROUP_IDS` Heroku configuration variables, and put::

    AWS_EC2_KEY_PAIR_NAME=<your keypair name>
    AWS_ECS_AMI=<your prefered AWS image; 'ami-57d9cd2e' by default>
    AWS_ECS_CLUSTER_NAME=<your cluster name here>
    AWS_ECS_SUBNET_ID=<your ECS subnet>
    AWS_ECS_SECURITY_GROUP_IDS=<colon separate list of security key IDs>

In the .env file in the project home directory.

Docker images
~~~~~~~~~~~~~

Check out a Comb, (BeeWare uses `this one
<https://github.com/pybee/comb/tree/pybee>`__). Create a file named `.env` in
the root of that checkout, and create a file called `.env` that contains the
following content::

    AWS_REGION=<Your AWS region (e.g., us-west-2)>
    AWS_ACCESS_KEY_ID=<Your AWS access key>
    AWS_SECRET_ACCESS_KEY=<Your AWS secret access key>

Then waggle the tasks in the comb::

    $ pip install waggle
    $ waggle waggler

Profiles
~~~~~~~~

Log into the admin, and create an AWS profile with the slug of `default`. This
is the machine type that will run tests by default. A reasonable starting point
is:

* **Instance type:** `t2.micro`
* **CPU:** 0
* **Memory:** 200

The value for CPU specifies how many compute units will be reserved by a task
running with that profile; 1 CPU represents 1024 compute units. The value for
memory indicates how much RAM (in MB) will be reserved for the task.

You may also want to add other profile types (e.g., a hi-cpu type). The slug
you specify for the profile can then be referenced by build tasks deployed on
the BeeKeeper cluster.

Github
~~~~~~

Last, go to the repository you want to manage with BeeKeeper, go to Settings,
then Webhooks, and add a new webhook for
`https://<your app name>.herokuapp.com/github/notify>`. When prompted for a
secret, you can generate one using Python::

    >>> from django.utils.crypto import get_random_string
    >>> get_random_string(50)
    'nuiVypAArY7lFDgMdyC5kwutDGQdDc6rXljuIcI5iBttpPebui'

Once the webhook has been created, create a `GITHUB_WEBHOOK_KEY` Heroku
configuration variable to this string, and put::

    GITHUB_WEBHOOK_KEY=<your key here>

in the .env file in the project home directory.

Then, generate a `personal access token
<https://help.github.com/articles/creating-a-personal-access-token-for-the-
command-line/>`__, create `GITHUB_USERNAME` and `GITHUB_ACCESS_TOKEN` Heroku
configuration variables with that value, and put::

    GITHUB_USERNAME=<your github username>
    GITHUB_ACCESS_TOKEN=<your token here>

in the .env file in the project home directory.

When the webhook is created, it will ping your BeeKeeper instance. This should
result in BeeKeeper responding and recording the existence of the project.
Any user logged in as an admin should see the project listed on the BeeKeeper
homepage. If you approve the project, any PR or repository push will start a
build as described in the `beekeeper.yml` file in the project home directory.

.. Documentation
.. -------------

.. Documentation for BeeKeeper can be found on `Read The Docs`_.

Community
---------

BeeKeeper is part of the `BeeWare suite`_. You can talk to the community through:

* `@pybeeware on Twitter`_

* The `pybee/general`_ channel on Gitter.

We foster a welcoming and respectful community as described in our
`BeeWare Community Code of Conduct`_.

Contributing
------------

If you experience problems with BeeKeeper, `log them on GitHub`_. If you
want to contribute code, please `fork the code`_ and `submit a pull request`_.

.. _BeeWare suite: http://pybee.org
.. _Read The Docs: https://beekeeper.readthedocs.io
.. _@pybeeware on Twitter: https://twitter.com/pybeeware
.. _pybee/general: https://gitter.im/pybee/general
.. _BeeWare Community Code of Conduct: http://pybee.org/community/behavior/
.. _log them on Github: https://github.com/pybee/beekeeper/issues
.. _fork the code: https://github.com/pybee/beekeeper
.. _submit a pull request: https://github.com/pybee/beekeeper/pulls

repository: MarkusH/beekeeper

repo_name: MarkusH/beekeeper


text:
---
title: "NEWS"
output:
  html_document:
    toc: true
    toc_float:
      collapsed: false
      smooth_scroll: false
    toc_depth: 2
vignette: >
  %\VignetteIndexEntry{NEWS}
  %\VignetteEncoding{UTF-8}
---

# rgee 0.5.3
- **CRAN release**
- Fix a bug in ee_check_python_packages.
- \donttest changed by \dontrun in the documentation.
- gdal and v8 system dependencies added to GH actions.
- Fix a bug in the paper (`ee_extract` example).
- Fix a minor bug in `ee_extract`, now the argument ... works.
- `ee_table_to_drive`: changed the initial value of the argument folder from NULL to "rgee_backup".
- Fix a minor bug in `ee_monitoring`.
- Fix a minor bug in `ee_manage_cancel_all_running_task`.
- Fix a minor bug in `ee_manage_cancel_all_running_task`.
- Improvement in the documentation of `ee_install`.
- Changes in vignettes, `Best Practices` vignette added.

# rgee 0.5.2
- DESCRIPTION: single quotes in title and description.
- DESCRIPTION: A more compresible description of what rgee does.
- DESCRIPTION: Added web reference to the Earth Engine API.
- \dontrun changed by \donttest in all our examples.
- Added "#' @return" to several functions.
- Added "#' @family" to all the functions.
- Added 'quiet' argument to all the functions that needed.
- Added new contributors to rgee (Kevin Ushey, Tim Appelhans, JJ Allaire, Yuan Tang).
- New environmental variable for rgee "EARTHENGINE_INIT_MESSAGE". It will be used to display a message to new users.
- Earth Engine Python API updated to 0.1.213.
- Documentation updated for ee_print and ee_manage_*.
- Fix a bug in ee_install_set_pyenv that did not permit to create properly
the .Renviron_backup file.

# rgee 0.5.1
- ee_install_* functions were deprecated and replaced by ee_install. ee_install create an isolated Python virtual environment with all rgee dependencies.
- ee_install_set_pyenv can be used to set the EARTHENGINE_PYTHON variable.

# rgee 0.5.0
- **Initial CRAN submit**
- Several typos fixed.
- rgee paper added.
- GitHub actions for automated testing and build the website.
- Due the changes in latest `reticulate` version (1.1.5), the functions `ee_install_earthengine_upgrade` and `ee_install_python_packages` were deprecated and both will remove in rgee 0.5.3.
- Config/reticulate added to DESCRIPTION file.
- .onLoad IMPORTANT CHANGES: Now `rgee` set EARTHENGINE_PYTHON instead of RETICULATE_PYTHON directly and RETICULATE_PYTHON_ENV is no longer required. This change will permit users to avoid problems with other R packages that use Python in the backend (such as tensorflow or keras).
- `ee_search_display` function added.
- Several typos fixed in all the documentation.
- Minor changes in `ee_as_sf` to support ee$FeatureCollections without elements.
- `data.colec.fbf` eliminated from all the examples.
- `rgee` now pass all `goodpractice` checks.
- `ee_get_img_date` and `ee_get_ic_date` are now `ee_get_date_img` and `ee_get_date_ic`.
- A new group of functions was created at `ee_utils.R`. `ee_pyfunc` is now `ee_utils_pyfunc`.
- Added new examples in `README.R`.

# rgee 0.4.3
- ee_extract improved: when RGEE_NAME is not defined, columns name will use the band name for `ee$Images` and the `system:index` property for `ee$ImageCollections`. Various bugs fixed.
- ee_manage upgrade. documentation enhanced.
- I/O module upgrade.

# rgee 0.4.2
- ee_image_to_local and ee_local_image_as_ee removed.
- ee_image_as_stars and ee_image_as_raster now is ee_as_stars and ee_as_raster.
- ee_gcs_to_image renamed to gcs_to_ee_image.
- minor bug in ee_print solved.

# rgee 0.4.1
- ee_extract bug fixed now sf arg works for Earth Engine tables.
- ee_install_create_pyenv now return a Python Path
- doc upgrade

# rgee 0.4
- travis and appveyor replaced by github-actions.
- docker folder deleted and saved in docker branch.
- examples folder deleted and saved in examples branch.
- Changes in installation module.
- Readme and documentation upgrade.
- new test added.

# rgee 0.3.16
- New test added.
- minor bugs solved

# rgee 0.3.15
- git action button added.
- minor bugs solved

# rgee 0.3.14
- ee_image module upgrade: new tests, new doc, and several bugs fixed.
- functions ee_gcs_to_asset_* renamed to ee_gcs_to_*

# rgee 0.3.13
- new function inside the ee_search interface: `ee_datacatalog_display`
- sf_as_ee doc upgrade.
- `ee_Image_to_local`: now region arg must be a ee$Geometry$Rectangle only when via = "getInfo" is used. It is will affect also to download of `ee$ImageCollections`.

# rgee 0.3.12
- Minor changes in ee_Initialize and ee_install-
- ee_version passed from 0.1.127 to 0.1.128.

# rgee 0.3.11
- sf_as_ee now permits their use not just in polygons.
- ee_as_thumbnail bug: it does not work in one-band images (fixed).
- ee_user_info new display.
- ee_Initialize now does not display Python version used (use ee_user_info instead).

# rgee 0.3.10
- ee_imagecollection_to_local local added.
- ee_as_stars changed by ee_as_stars.
- ee_image_stars and ee_image_to_local added
- ee_extract new argument added "sf = FALSE".
- ee_as_thumbnail arguments modified.
- ee_print new display.
- ee_help bug fixed.
- ee_fix_offset function added to support image downloads by getInfo.

# rgee 0.3.9
- ee_date functions upgraded
- Documentation enhanced
- Several bug fixed

# rgee 0.3.8
- ee_as_sf support the download of large tables
- Several bug fixed

# rgee 0.3.6
- bugs in ee_as_thumbnail and ee_as_stars were fixed.

# rgee 0.3.5
- ee_help display enhanced.
- ee_Initialize now display reticulate Python version.
- Several bug fixed.

# rgee 0.3.4
- Several bugs fixed

# rgee 0.3.3
- Several bugs fixed

# rgee 0.3.0
- changed ee_map from Map.
- New friendly-user installation module implemented.
- ee_download and ee_upload were deprecated
- selenium functionality deprecated
- ee_as_sf and sf_as_ee now support gcs and drive
- ee_as_stars and stars_as_ee functions created.
- rgee support geometry with different CRS.
- arguments evenOdd, Geodesic, and proj implemented in several functions.
- ee_help permit you display Earth Engine documentation.

# rgee 0.2.0
- Several bugs fixed.
- A collection of 300+ examples for using Google Earth Engine in [R](https://github.com/csaybar/rgee-examples).
- Functions added:
  - **non-R** installation module added
  - **ee_pyfunc:** Wrap an R function in a Python function with the same signature.
  - **ee_remove_\*:** Delete credentials and selenium drivers.

# rgee 0.1.0
- Documentation improved.
- Examples for all functions.
- py_help: Generate compressible documentation in an html format.
- Unit testing in both Python and R.
- Functions added:
  - **ee$...:** Complete access to the Earth Engine API from within R.
  - **ee_Initialize:** Multi-user support for Initialize Earth Engine, a wrapper around `ee$Initialize`.
  - **ee_install:** Interface for installing Selenium drivers and Python packages effortlessly.
  - **ee_check:** Interface for dependencies checking.
  - **ee_manage:** Manage EE assets and tasks recursively.
  - **ee_map:** Display EE spatial objects using [mapview](https://r-spatial.github.io/mapview/).
  - **ee_print:** Print EE metadata.
  - **ee_upload:** Upload ESRI shapefiles or GeoTIFF files to Earth Engine.
  - **ee_download:** Download EE spatial objects.
  - **ee_as_sf** & **sf_as_ee:** Convert EE tables (Feature Collection) to sf and vice-versa.
  - **ee_as_thumbnail:** Create a stars object based on an EE thumbnail image.
  - **ee_extract:** Extract values for EE ImageCollections, similarly to [raster::extract].
  - **ee_search:** Search among the Earth Engine Data Catalog.
  - **ee_help:** Display the Earth Engine documentation.

repository: dondealban/rgee

gha_license_id: NOASSERTION

repo_name: dondealban/rgee


text:
---
layout: post
title:  "The Secret"
comments: true
date:   2018-11-08 12:00:00 -0500
categories: leadership
draft: false
---

A great post by Bill Barnett on learning and business, called [The Secret](http://www.barnetttalks.com/2018/10/the-secret.html?m=1).

> The philosopher Alfred North Whitehead long ago made the point that valuable learning comes not from being told a fact. Recited facts are "inert" ideas disconnected from the fullness of our understanding. Valuable learning, says Whitehead, means discovering "living" knowledge: ideas "utilised, tested, or thrown into fresh combinations." Yet we persist in believing the myth of the special secret.

repository: tarunsachdeva/blog

branch_name: refs/heads/gh-pages

extension: markdown

gha_language: HTML

repo_name: tarunsachdeva/blog


text:
```javascript
{
  addedCourses: {},
  fetchedBuildings: {},
  fetchedCourses: {},
  //TODO change stats to a better name like scraperStats, syllabusStats?
  stats: {},
  user: {
    // Boolean true or false
    isFirstTimeAccess: false,
    // Support "en" and "jp"
    displayLang: "en",
    // Limited to at most 5 schools
    // Will be set at first time access.
    // Can be changed at 'filter by' in syllabus
    schools:[]
  }
}
```

#### Potential BUG:

BUG: Assume a user selected school `FSE`, added a course `C Programming` which belongs to `FSE`, and then deleted school `FSE` in syllabus. How do we rehydrate `C Programming` in `addedCourses` when the user visits next time? We only have `id` in localStorage.

SOL: Add a new key called `school` in user's localStorage for tracking the school that each course belongs to. If we cannot find the course by `id` and confirm that the school it belongs to is indeed not selected by the user, we fetch the api json file which corresponds to the not selected `school`. Else, we drop the course.

repository: AustinZhu/wasedatime-web

repo_name: AustinZhu/wasedatime-web


text:
---
order: 25
title:
  en-US: Routing guard
  zh-CN: 路由守卫
type: Documents
---

## Written in front

When a route does not initiate a request, it means that the Token validity cannot be verified in the interceptor, and the routing guard can solve the problem, for example, in your root path:

```ts
[
  {
    path: 'home',
    component: MockComponent,
    canActivate: [authJWTCanActivate],
  },
  {
    path: 'my',
    canActivateChild: [authJWTCanActivateChild],
    children: [
      { path: 'profile', component: MockComponent }
    ],
  },
  {
    path: 'login',
    component: MockComponent,
  },
]
```

## How to choose?

Similarly, the different authentication styles are:

- `authSimpleCanActivate`, `authSimpleCanActivateChild`, `authSimpleCanMatch` based on Simple Web Token authentication style
- `authJWTCanActivate`, `authJWTCanActivateChild`, `authJWTCanMatch` based on Json Web Token authentication style

repository: ng-alain/delon

repo_name: ng-alain/delon


text:
# Samu Social Hackathon

Hackathon organized at the [Hive](https://www.hackathon.com/event/the-data-hive-hackathon---when-data-meets-social-good-52493822436)
in February 2019.

## Context

To help the [_Samu Social de Paris_](https://www.samusocial.paris/) visit the different hotels we propose a
tool to help the visit planing process.

- Our solution proposes to:
    - Create pairs of workers that are available for a visit on a shared time window
    - Propose itinerary of hotel to visit for each pairs of workers based on their initial localisation.

## Setup

NB: Phe project runs on `python 3.6`
1. create a virtualenv
````bash
python3 -m venv samu_social
````

2. Install requirements
````bash
pip install -r requirements.txt
````

3. Run the main to get itineraries based on the data provided in the hackathon (not shared in this repo)
````bash
python src/main.py
````

## Useful resources
https://adresse.data.gouv.fr/api (to get `long` and `lat` from an address)

Google [OR-Tools](https://developers.google.com/optimization/routing/) for optimisation
and especially routing problem.

## Notes
This project is no longer updated.


text:
# Referring Image Segmentation via Cross-Modal Progressive Comprehension
Code for Referring Image Segmentation via Cross-Modal Progressive Comprehension, CVPR2020

#### Interpretation of our progressive referring segmentation method.

* (a) Input referring expression and image.

* (b) The model first perceives all the entities described in the expression based on entity words and attribute words, e.g., “man” and “white frisbee”(orange masks and blue outline).

* (c) After finding out all the candi-date entities that may match with input expression, relational word 087 “holding” can be further exploited to highlight the entity involved with the relationship (green arrow) and suppress the others which are not involved.

* (d) Benefiting from the relation-aware reasoning process, the referred entity is found as the final prediction (purple mask).
![interpretation](motivation.png)

repository: XrosLiang/CMPC-Refseg

repo_name: XrosLiang/CMPC-Refseg


text:
[![](https://codecov.io/gh/FalkonML/falkon/branch/master/graphs/badge.svg?branch=master)](https://codecov.io/gh/FalkonML/falkon/)

# Falkon

Python implementation of the Falkon algorithm for large-scale, approximate kernel ridge regression.

The code is well optimized and can scale to problems with tens of millions of points.
Full kernel matrices are never computed explicitly so that you will not run out of memory on large problems.

Preconditioned conjugate gradient optimization ensures that only few iterations are necessary to obtain good results.

The basic algorithm is a Nyström approximation to KRR, which needs only three hyperparameters:
 1. The number of centers `M` - this controls the quality of the approximation: a higher number of centers will
    produce more accurate results at the expense of more computation time, and higher memory requirements.
 2. The penalty term, which controls the amount of regularization.
 3. The kernel function. A good default is always the Gaussian (or RBF) kernel
    ([`falkon.kernels.GaussianKernel`](https://falkonml.github.io/falkon/api_reference/kernels.html#gaussian-kernel)).

For more information about the algorithm and the optimized solver, download our paper:
[Kernel methods through the roof: handling billions of points efficiently](https://arxiv.org/abs/2006.10350)

The API is sklearn-like, so that Falkon should be easy to integrate in your existing code.

## Documentation

Extensive documentation is available at https://falkonml.github.io/falkon/. Several worked-through examples
are also provided in [the docs](https://falkonml.github.io/falkon/examples/examples.html).

If you find a bug, please open a new issue on GitHub!

## Installing

Prerequisites are PyTorch >= 1.4 (with the CUDA toolkit if GPU support is desired) and a patched version of KeOps (which
is distributed as a git submodule of this repository), `cmake`, and a C++ compiler which can compile PyTorch extensions
(i.e. capable of compiling with `-std=c++11`).

Once the prerequisites are met, you can `pip install .` from the root of this repository.

**For more detailed installation instructions see [the docs](https://falkonml.github.io/falkon/install.html).**

## Reference

If you find this library useful for your work, please cite the following publication:
```
@misc{falkonlibrary2020,
    title={Kernel methods through the roof: handling billions of points efficiently},
    authors={Meanti, Giacomo and Carratino, Luigi and Rosasco, Lorenzo and Rudi, Alessandro},
    year = {2020},
    archivePrefix = {arXiv},
    eprint = {2006.10350}
}
```


text:
# Form

Form is used to collect, validate, and submit the user input, usually contains various form items including checkbox, radio, input, select, and etc.

## Form

You can align the controls of a `form` using the `layout` prop：

- `horizontal`：to horizontally align the `label`s and controls of the fields. (Default)
- `vertical`：to vertically align the `label`s and controls of the fields.
- `inline`：to render form fields in one line.

## Form fields

A form consists of one or more form fields whose type includes input, textarea, checkbox, radio, select, tag, and more.
A form field is defined using `<Form.Item />`.

```jsx
<Form.Item {...props}>{children}</Form.Item>
```

## Examples

### Horizontal Login Form

Horizontal login form is often used in navigation bar.

<demo-form-horizontal-login/>

<demo-code-box>
^^^ @/docs/.vuepress/components/demo/form/horizontal-login.vue
</demo-code-box>

### Login Form

Normal login form which can contain more elements.

<demo-form-normal-login/>

<demo-code-box>
^^^ @/docs/.vuepress/components/demo/form/normal-login.vue
</demo-code-box>

### Registration

Fill in this form to create a new account for you.

<demo-form-register/>

<demo-code-box>
^^^ @/docs/.vuepress/components/demo/form/register.vue
</demo-code-box>

### Advanced search

Three columns layout is often used for advanced searching of data table.

Because the width of label is not fixed, you may need to adjust it by customizing its style.

<demo-form-advanced-search/>

<demo-code-box>
^^^ @/docs/.vuepress/components/demo/form/advanced-search.vue
</demo-code-box>

### Form in Modal to Create

When user visit a page with a list of items, and want to create a new item. The page can popup a form in Modal, then let user fill in the form to create an item.

<demo-form-form-in-modal/>

<demo-code-box>
^^^ @/docs/.vuepress/components/demo/form/form-in-modal.vue
</demo-code-box>

### Dynamic Form Item

Add or remove form items dynamically.

<demo-form-dynamic-form-item/>

<demo-code-box>
^^^ @/docs/.vuepress/components/demo/form/dynamic-form-item.vue
</demo-code-box>

### Customized Form Controls

Customized or third-party form controls can be used in Form, too. Controls must follow these conventions:
> * It has a controlled property `value`
> * It has event `onChange`
> * It must be a class component.

<demo-form-customized-form-controls/>

<demo-code-box>
^^^ @/docs/.vuepress/components/demo/form/customized-form-controls.vue
</demo-code-box>

### Store Form Data into Upper Component

We can store form data into upper component

**Note:** You must wrap field data with `Form.createFormField` in `mapPropsToFields`.

<demo-form-global-state/>

<demo-code-box>
^^^ @/docs/.vuepress/components/demo/form/global-state.vue
</demo-code-box>

### Handle Form Data Manually

`Form.create` will collect and validate form data automatically. But if you don't need this feature or the default behaviour cannot satisfy your business, you can drop `Form.create` and handle form data manually.

<demo-form-without-form-create/>

<demo-code-box>
^^^ @/docs/.vuepress/components/demo/form/without-form-create.vue
</demo-code-box>

### Customized Validation

We provide properties like `validateStatus` `help` `hasFeedback` to customize your own validate status and message, without using `Form.create` and `getFieldDecorator`.

1. `validateStatus`: validate status of form components which could be 'success', 'warning', 'error', 'validating'.
2. `hasFeedback`: display feed icon of input control
3. `help`: display validate message.

<demo-form-validate-static/>

<demo-code-box>
^^^ @/docs/.vuepress/components/demo/form/validate-static.vue
</demo-code-box>

### Form Layout

There are three layout for form: `horizontal`, `vertical`, `inline`.

<demo-form-layout/>

<demo-code-box>
^^^ @/docs/.vuepress/components/demo/form/layout.vue
</demo-code-box>

### Dynamic Rules

Perform different check rules according to different situations.

<demo-form-dynamic-rule/>

<demo-code-box>
^^^ @/docs/.vuepress/components/demo/form/dynamic-rule.vue
</demo-code-box>

### Other Form Controls

Demostration for validataion configuration for form controls which are not show in the above demos.

<demo-form-validate-other/>

<demo-code-box>
^^^ @/docs/.vuepress/components/demo/form/validate-other.vue
</demo-code-box>

## API

### Form

| Property         | Description                                                                       | Type                               | Default Value |
| ---------------- | --------------------------------------------------------------------------------- | ---------------------------------- | ------------- |
| form             | Decorated by `Form.create()` will be automatically set `this.props.form` property | object                             | n/a           |
| hideRequiredMark | Hide required mark of all form items                                              | Boolean                            | false         |
| layout           | Define form layout                                                                | 'horizontal'\|'vertical'\|'inline' | 'horizontal'  |
| onSubmit         | Defines a function will be called if form data validation is successful.          | Function(e:Event)                  |               |

### Form.create(options)

How to use：

```jsx
class CustomizedForm extends Vue.Component {}

CustomizedForm = Form.create({})(CustomizedForm);
```

The following `options` are available:

| Property         | Description                                                                                | Type                                                |
| ---------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------- |
| mapPropsToFields | Convert props to field value(e.g. reading the values from Redux store). And you must mark returned fields with `Form.createFormField`                            | (props) => ({ \[fieldName\]: FormField { value } }) |
| validateMessages | Default validate message. And its format is similar with [newMessages](https://github.com/yiminghe/async-validator/blob/master/src/messages.js)'s returned value | Object { [nested.path]: String }               |
| onFieldsChange   | Specify a function that will be called when the value a `Form.Item` gets changed. Usage example: saving the field's value to Redux store.                        | Function(props, fields)                             |
| onValuesChange   | A handler while value of any field is changed                                                                                | (props, changedValues, allValues) => void           |

If you want to get `ref` after `Form.create`, you can use `wrappedComponentRef` provided by `rc-form`

```jsx
class CustomizedForm extends Vue.Component { ... }

// use wrappedComponentRef
const EnhancedForm =  Form.create()(CustomizedForm);
<EnhancedForm wrappedComponentRef={(form) => this.form = form} />
this.form // => The instance of CustomizedForm
```

If the form has been decorated by `Form.create` then it has `this.props.form` property. `this.props.form` provides some APIs as follows:

> Note: Before using `getFieldsValue` `getFieldValue` `setFieldsValue` and so on, please make sure that corresponding field had been registered with `getFieldDecorator`.

| Method                  | Description                                                                                | Type                                                                                |
| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
| getFieldDecorator       | Two-way binding for form, please read below for details.                                                                                |                                                                                |
| getFieldError           | Get the error of a field.                                                                                | Function(name)                                                                                |
| getFieldsError          | Get the specified fields' error. If you don't specify a parameter, you will get all fields' error.                                                                                | Function(\[names: string\[]])                                                                                |
| getFieldsValue          | Get the specified fields' values. If you don't specify a parameter, you will get all fields' values.                                                                                | Function(\[fieldNames: string\[]])                                                                                |
| getFieldValue           | Get the value of a field.                                                                                | Function(fieldName: string)                                                                                |
| isFieldsTouched         | Check whether any of fields is touched by `getFieldDecorator`'s `options.trigger` event                                                                                | (names?: string\[]) => boolean                                                                                |
| isFieldTouched          | Check whether a field is touched by `getFieldDecorator`'s `options.trigger` event                                                                                | (name: string) => boolean                                                                                |
| isFieldValidating       | Check if the specified field is being validated.                                                                                | Function(name)                                                                                |
| resetFields             | Reset the specified fields' value(to `initialValue`) and status. If you don't specify a parameter, all the fields will be reset.                                                      | Function(\[names: string\[]])                                                                                |
| setFields               | Set the value and error of a field.                                                                                | Function({ [fieldName]: { value: any, errors: [Error] } })                                                                             |
| setFields               | Set value and error state of fields                                                                                | ({
  \[fieldName\]: {value: any, errors: \[Error\] }
}) => void                                                         |
| setFieldsValue          | Set the value of a field.                                                                                | ({ \[fieldName\]: value }) => void                                                                                |
| validateFields          | Validate the specified fields and get theirs values and errors. If you don't specify the parameter of fieldNames, you will validate all fields.                                       | (
  \[fieldNames: string\[]],
  \[options: object\],
  callback(errors, values)
) => void |
| validateFieldsAndScroll | This function is similar to `validateFields`, but after validation, if the target field is not in visible area of form, form will be automatically scrolled to the target field area. | same as `validateFields`                                                                                |

### validateFields/validateFieldsAndScroll

```jsx
const {
  form: { validateFields }
} = this.props;
validateFields((errors, values) => {
  // ...
});
validateFields(["field1", "field2"], (errors, values) => {
  // ...
});
validateFields(["field1", "field2"], options, (errors, values) => {
  // ...
});
```

| Method              | Description                                                                                | Type      | Default |
| ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------- | ------- |
| options.first       | If `true`, every field will stop validation at first failed rule                                                                                | boolean   | false   |
| options.firstFields | Those fields will stop validation at first failed rule                                                                                | String\[] | \[]     |
| options.force       | Should validate validated field again when `validateTrigger` is been triggered again                                                                            | boolean   | false   |
| options.scroll      | Config scroll behavior of `validateFieldsAndScroll`, more: [dom-scroll-into-view's config](https://github.com/yiminghe/dom-scroll-into-view#function-parameter) | Object    | {}      |

#### Callback arguments example of validateFields

- `errors`:

```json
{
  "userName": {
    "errors": [
      {
        "message": "Please input your username!",
        "field": "userName"
      }
    ]
  },
  "password": {
    "errors": [
      {
        "message": "Please input your Password!",
        "field": "password"
      }
    ]
  }
}
```

- `values`:

```json
{
  "userName": "username",
  "password": "password"
}
```

### Form.createFormField

To mark the returned fields data in `mapPropsToFields`

### this.props.form.getFieldDecorator(id, options)

After wrapped by `getFieldDecorator`, `value`(or other property defined by `valuePropName`) `onChange`(or other property defined by `trigger`) props will be added to form controls，the flow of form data will be handled by Form which will cause:

1. You shouldn't use `onChange` to collect data, but you still can listen to `onChange`(and so on) events.
2. You cannot set value of form control via `value` `defaultValue` prop, and you should set default value with `initialValue` in `getFieldDecorator` instead.
3. You shouldn't call `setState` manually, please use `this.props.form.setFieldsValue` to change value programmatically.

#### Special attention

#### getFieldDecorator(id, options) parameters

| Property                  | Description                                                                                | Type                                       | Default Value |
| ------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------ | ------------- |
| id                        | The unique identifier is required                                                                                | string                                     |               |
| options.getValueFromEvent | Specify how to get value from event or other onChange arguments                                                                                | function(..args)                           | reference     |
| options.getValueProps     | Get the component props according to field value.                                                                                | function(value): any                       | reference     |
| options.initialValue      | You can specify initial value, type, optional value of children node. (Note: Because `Form` will test equality with `===` internally, we recommend to use variable as `initialValue`, instead of literal) |                                            | n/a           |
| options.normalize         | Normalize value to form component                                                                                | function(value, prevValue, allValues): any | -             |
| options.rules             | Includes validation rules. Please refer to "Validation Rules" part for details.                                                                                | object\[]                                  | n/a           |
| options.trigger           | When to collect the value of children node                                                                                | string                                     | 'onChange'    |
| options.validateFirst     | Whether stop validate on first rule of error for this field.                                                                                | boolean                                    | false         |
| options.validateTrigger   | When to validate the value of children node.                                                                                | string\|string\[]                          | 'onChange'    |
| options.valuePropName     | Props of children node, for example, the prop of Switch is 'checked'.                                                                                | string                                     | 'value'       |

### Form.Item

Note: if Form.Item has multiple children that had been decorated by `getFieldDecorator`, `help` and `required` and `validateStatus` can't be generated automatically.

| Property       | Description                                                                                | Type            | Default Value |
| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | --------------- | ------------- |
| colon          | Used with `label`, whether to display `:` after label text.                                                                                | boolean         | true          |
| extra          | The extra prompt message. It is similar to help. Usage example: to display error message and prompt message at the same time.                  | string\|VueNode |               |
| hasFeedback    | Used with `validateStatus`, this option specifies the validation status icon. Recommended to be used only with `Input`.                        | boolean         | false         |
| help           | The prompt message. If not provided, the prompt message will be generated by the validation rule.                                              | string\|VueNode |               |
| label          | Label text                                                                                | string\|VueNode |               |
| labelCol       | The layout of label. You can set `span` `offset` to something like `{span: 3, offset: 12}` or `sm: {span: 3, offset: 12}` same as with `<Col>` | object          |               |
| required       | Whether provided or not, it will be generated by the validation rule.                                                                          | boolean         | false         |
| validateStatus | The validation status. If not provided, it will be generated by validation rule. options: 'success' 'warning' 'error' 'validating'             | string          |               |
| wrapperCol     | The layout for input controls, same as `labelCol`                                                                                | object          |               |

### Validation Rules

| Property   | Description                                                                                | Type                                    | Default Value |
| ---------- | ----------------------------------------------------------------------------------------------- | --------------------------------------- | ------------- |
| enum       | validate a value from a list of possible values                                                 | string                                  | -             |
| len        | validate an exact length of a field                                                             | number                                  | -             |
| max        | validate a max length of a field                                                                | number                                  | -             |
| message    | validation error message                                                                        | string\|VueNode                         | -             |
| min        | validate a min length of a field                                                                | number                                  | -             |
| pattern    | validate from a regular expression                                                              | RegExp                                  | -             |
| required   | indicates whether field is required                                                             | boolean                                 | `false`       |
| transform  | transform a value before validation                                                             | function(value) => transformedValue:any | -             |
| type       | built-in validation type, [available options](https://github.com/yiminghe/async-validator#type) | string                                  | 'string'      |
| validator  | custom validate function                                                                        | function(rule, value, callback)         | -             |
| whitespace | treat required fields that only contain whitespace as errors                                    | boolean                                 | `false`       |

See more advanced usage at [async-validator](https://github.com/yiminghe/async-validator).

repository: LVMM-PC/nebula

repo_name: LVMM-PC/nebula


text:
# compressed_js_code

This test project seeks to optimize server side bandwidth usage by downloading javascript code to the browser compressed in a zip file. It uses jszip to decompress the code. You can test it by opening it using any http server and opening the index.html in the browser.

The "files" folder contains the testing files, which are compressed into the "files.zip" file.
The "lib" folder contains jszip, a library that allows the browser to unzip the test files.
You can check the code in the "unzip_and_run.js" file.

The project successfully compresses a 364KB transfer down to 128KB. The project also reduces the amount of GET calls to the server from 5 down to 1. Next step is to create a system to compress image transfers using the same system (Coming soon).

Libraries used:

https://stuk.github.io/jszip/

Libraries used to test the code:

https://d3js.org/

https://jquery.com/

branch_name: refs/heads/main


text:
ATLO/NGINX Container
====================

Configuration of nginx via etcd
-------------------------------
The container must be configured using etcd-confd software. To configure it in a proper way the user of the image must create several keys in the etcd key-value directory as follows:

###General config

 - prefix/nginx/conf/worker_processes:Number of worker processess.
 - prefix/nginx/conf/worker_rlimit_nofile:Limit of **rlimit** # of files.
 - prefix/nginx/conf/worker_connections:Connections per worker.
 - prefix/nginx/conf/events: Nginx configuration for 'events' section.
 - prefix/nginx/conf/index: list of index files.
 - prefix/nginx/conf/httpconf: Nginx configuration for 'http' section.

###Defining sites (servers,locations,upstreams)
Nginx uses two major concepts to manage responses to request: Servers and locations. Upstreams are optional and only are when nginx are used as load balancer. Servers, howerver, are mandatory.

####Servers
Creating a server in nginx typically encompases the definition of the following attributes:

 - Server domain and listen port.
 - Index page and root directory.
 - Server level properties: Such logs, http parameters.
 - A set of locations.

To define a server an entry must be created on etcd with the following keys:

- prefix/sites/site-[name]: Directory defining the site with diferent name.
	- prefix/sites/site-[name]/domain: domain or domains of the site. [Sintax](http://nginx.org/en/docs/http/ngx_http_core_module.html#server_name)
	- prefix/sites/site-[name]/listen: ports to listen. [Sintax](http://nginx.org/en/docs/http/ngx_http_core_module.html#listen)
	- prefix/sites/site-[name]/root: Root directory of the site.
	- prefix/sites/site-[name]/index: list of index files for site.
	- prefix/sites/site-[name]/extra_options: extra nginx parameters for the site
	- prefix/sites/site-[name]/locations: Directory with locations.
		-  prefix/sites/site-[name]/locations/location-[name]:Directory with locations with diferent names.
			- prefix/sites/site-[name]/locations/location-[name]/route: Route of the location [Sintax](http://nginx.org/en/docs/http/ngx_http_core_module.html#location)
			- prefix/sites/site-[name]/locations/location-[name]/body: Body of location tag in nginx [Sintax](http://nginx.org/en/docs/http/ngx_http_core_module.html#location)
	- prefix/sites/site-[name]/extra_locations: Nginx extra tags after locations.

####Upstreams

To use nginx as Load balancer it is needed to define uptreams servers to which trafic will be proxied. To configure an upstream etcd values are econded in json as following:

```
{address:"some address ip:port or unix socket",options:"nginx options in upstream"}
```

 Within the etcd directory nginx/upstreams two kind of entries:

 - prefix/nginx/upstreams/server-[name]: Each sub key of this entry need to be a upstream json value.
 - prefix/nginx/upstreams/key-[name]: Point to other etcd where upstream entries are stored. By design of confd this key is **relative to prefix**.

####Typical values (example configuration for linux):

- **worker_process**:  auto;
- **worker_connections**: 1024
- **events**:
```
multi_accept on;
use epoll;
```
- **index**: index.php index.html index.htm
- **http_conf**:

```
   	# File and tcp tweaks
	sendfile on;
	tcp_nopush on;
	tcp_nodelay on;

	# MIME types
	include 	  /etc/nginx/mime.types;
	default_type  application/octet-stream;

	# Logs
	log_format  main  '$remote_addr - $remote_user [$time_local] "$request" '
                     '$status $body_bytes_sent "$http_referer" '
                      '"$http_user_agent" "$http_x_forwarded_for"';
    access_log off;
    error_log	/var/log/nginx/error.log crit;

    # Keep Alive, timeouts
    send_timeout 	20;
    keepalive_timeout 15s;
	reset_timedout_connection on;

   client_body_timeout 25;
   client_header_timeout 25;

    # Buffers
	client_body_buffer_size
	client_body_in_file_only off;

   # Gzip
    gzip on;
    gzip_proxied any;
    gzip_comp_level 5;
   gzip_disable “msie6”;
    gzip_min_length 1024;
    gzip_types text/plain text/css application/json application/x-javascript text/xml application/xml application/xml+rss text/javascript;
    gzip_vary on;

    # FD cache
    open_file_cache max=5500 inactive=20s;
    open_file_cache_valid 30s;
    open_file_cache_min_uses 2;
    open_file_cache_errors on;

```

repository: ludiazv/cell

repo_name: ludiazv/cell


text:
# StreetFoodWeb1
#### {This is a StreetFood website that is to make an appealing information accompanied by photos of different types of food offered and a complete menu.
}, {23 July 2021}
#### By **{Ezekiel Kibiego}**
## Description
{The Website has photos of the Street Food photos  }
### Design
file:///home/moringa/Desktop/StreetFoodWeb1/StreetFood.png

## Setup/Installation Requirements
* Clone this repo to your desktop and run sudo install to install all the dependencies.
## Known Bugs
{None}
## {HTML and CSS}
## Support and contact details
<EMAIL_ADDRESS>### License
MIT License
Copyright (c) {2021} **{Ezekiel Kibiego}**


text:
# Random Wallpaper

A little utility I wrote for myself to pick a random wallpaper.

## How does it work?

First, it finds where your current wallpaper exists. Then it looks for other images1 in that same directory and picks one at random. Then it sets that as your new wallpaper.

## How to use it

You'll need to have [Rust installed.](https://www.rust-lang.org/en-US/install.html)

```bash
$ git clone https://github.com/MCluck90/random-wallpaper-rs.git
$ cd random-wallpaper-rs
$ cargo run --release
```

---

1: Images are defined as files which end with one of the following extensions: .bmp, .gif, .jpg, .jpeg, .png. It does not check if these are valid files.


text:
# Mini-lab: Add Guest users to Azure AD in the Azure Portal

You can invite anyone to collaborate with your organization by adding them to your directory as a guest user. Then you can either send an invitation email that contains a redemption link or send a direct link to an app you want to share.

Guest users can sign in with their own work, school, or social identities.

In this mini-lab, you'll add a new guest user to Azure AD and send an invitation.

## Prerequisites

To complete the scenario in this mini-lab you need:

* A role that allows you to create users in your tenant directory, like the Global Administrator role or any of the limited administrator directory roles.

* A valid email account that you can add to your tenant directory, and that you can use to receive the test invitation email.

## Add Guest users to Azure AD

1. Sign in to the [Azure portal](https://portal.azure.com/) as an Azure AD administrator.

1. In the left pane, select **Azure Active Directory**.

1. On the **Manage** left panel on the left, select **Users**.

    ![Screenshot showing where to select the Users option](../../Linked_Image_Files/guest_user_image1.png)

1. Select **New guest user** on the top bar

    ![Screenshot showing where to select the New guest user option](../../Linked_Image_Files/guest_user_image2.png)

1. On the **New user** page, select **Invite user** and  add the guest user's information.

    ![Screenshot showing where to select the New guest user option](../../Linked_Image_Files/guest_user_image3.png)

    - ***Identity***
        - **Name:** The first and last name of the guest user.

        - **Email address (required):** The email address of the guest user.

    - ***Personal message (optional):*** Include a personal welcome message to the guest user.

    - ***Groups and roles***

        - **Groups:** You can add the guest user to one or more existing groups, or you can do it later.

        - **Directory role:** If you require Azure AD administrative permissions for the user, you can add them to an Azure AD role.
    - ***Settings***
        - **Block sign in (optionl):** Allows you to block an user to sign-in without deleting the profile
        - **Usage location (optional):** The physicall location of the user
    - ***Job info***
        - **Job totle (optionla)**
        - **Department (optional)**

1. Select **Invite** to automatically send the invitation to the guest user. A notification appears in the upper right with the message Successfully invited user.

1. After you send the invitation, the user account is automatically added to the directory as a guest.

## Assign an App to a Guest user

Add the *Active Directory for GitHub Enterprise* app to your test tenant and assign the test guest user to the app.

1. Sign in to the Azure portal as an Azure AD administrator.

1. In the left pane, select **Enterprise applications**.
    - Alternatively, you can search for it on the search box on top of the page

1. Select **New application**.

    ![Screenshot showing the Add from the gallery search box](../../Linked_Image_Files/guest_user_image4.png)

1. Under **Add from the gallery**, search for **GitHub**, and then select **Active Directory for GitHub Enterprise**.

    ![Screenshot showing the Add from the gallery search box](../../Linked_Image_Files/guest_user_image6.png)

1. Select **Add** (or Create). It will show you a new window

    ![Screenshot showing the Add from the gallery search box](../../Linked_Image_Files/guest_user_image7.png)

1. Under the Manage left pane, select Single **sign-on**, and under **Single Sign-on Mode**, select **Password-based Sign-on**, and click **Save**.

1. Under the **Manage** left pane, select **Users and groups > Add user**

1.  Click **Users**, a rigth pane will appear, click the user you want to add, and then Users click **Select**.

    ![Screenshot showing Add user to group.](../../Linked_Image_Files/guest_user_image9.png)

1. Select **Assign**.

## Accept the Guest user invite

Now sign in to the guest user email account to view the invitation.

1. Sign in to your test guest user's email account.

1. In the inbox, find the "*You're invited*" email.

1. In the email body, select Get Started. A Review permissions page opens in the browser.

1. Select **Accept Invitation**. The Access Panel opens, which lists the applications the guest user can access.

    ![Screenshot showing the Review permissions page](../../Linked_Image_Files/guest_user_image5.png)

url: https://raw.githubusercontent.com/vee73/AZ-030T00-Microsoft-Azure-technologies-for-AWS-architects/a380295ce14915316060b5f0121261a0fce84630/Instructions/Mini-labs/Module 03/02-MiniLab_Configure Guest Users in Azure AD.md


text:
# Lithographa tesserata var. petraea (Ach.) Redinger VARIETY

#### Status
SYNONYM

#### According to
Index Fungorum

#### Published in
Rabenhorst's Kryptogamenflora (Leipzig) 9(2,1): 193 (1938)

#### Original name
Opegrapha petraea Ach.

### Remarks
null

repository: mdoering/backbone

path: /life/Fungi/Ascomycota/Lecanoromycetes/Baeomycetales/Trapeliaceae/Lithographa/Lithographa tesserata/ Syn. Lithographa tesserata petraea/README.md

repo_name: mdoering/backbone


text:
# radar-upload-connect-backend
[![Artifact HUB](https://img.shields.io/endpoint?url=https://artifacthub.io/badge/repository/radar-upload-connect-backend)](https://artifacthub.io/packages/helm/radar-base/radar-upload-connect-backend)

![Version: 0.2.4](https://img.shields.io/badge/Version-0.2.4-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 0.5.10](https://img.shields.io/badge/AppVersion-0.5.10-informational?style=flat-square)

A Helm chart for RADAR-base upload connector backend application. This application is an upload system that stores uploaded data and its metadata in PostgreSQL for later processing.

**Homepage:** <https://radar-base.org>

## Maintainers

| Name | Email | Url |
| ---- | ------ | --- |
| Keyvan Hedayati |<EMAIL_ADDRESS>| <https://www.thehyve.nl> |
| Joris Borgdorff |<EMAIL_ADDRESS>| <https://www.thehyve.nl/experts/joris-borgdorff> |
| Nivethika Mahasivam |<EMAIL_ADDRESS>| <https://www.thehyve.nl/experts/nivethika-mahasivam> |

## Source Code

* <https://github.com/RADAR-base/radar-helm-charts/tree/main/charts/radar-upload-connect-backend>
* <https://github.com/RADAR-base/radar-upload-source-connector>

## Prerequisites
* Kubernetes 1.22+
* Kubectl 1.22+
* Helm 3.1.0+

## Values

| Key | Type | Default | Description |
|-----|------|---------|-------------|
| replicaCount | int | `2` | Number of radar-upload-connect-backend replicas to deploy |
| image.repository | string | `"radarbase/radar-upload-connect-backend"` | radar-upload-connect-backend image repository |
| image.tag | string | `"0.5.10"` | radar-upload-connect-backend image tag (immutable tags are recommended) Overrides the image tag whose default is the chart appVersion. |
| image.pullPolicy | string | `"IfNotPresent"` | radar-upload-connect-backend image pull policy |
| imagePullSecrets | list | `[]` | Docker registry secret names as an array |
| nameOverride | string | `""` | String to partially override radar-upload-connect-backend.fullname template with a string (will prepend the release name) |
| fullnameOverride | string | `""` | String to fully override radar-upload-connect-backend.fullname template with a string |
| podSecurityContext | object | `{}` | Configure radar-upload-connect-backend pods' Security Context |
| securityContext | object | `{}` | Configure radar-upload-connect-backend containers' Security Context |
| service.type | string | `"ClusterIP"` | Kubernetes Service type |
| service.port | int | `8085` | radar-upload-connect-backend port |
| ingress.enabled | bool | `true` | Enable ingress controller resource |
| ingress.annotations | object | check values.yaml | Annotations that define default ingress class, certificate issuer and proxy settings |
| ingress.path | string | `"/upload/api/?(.*)"` | Path within the url structure |
| ingress.pathType | string | `"ImplementationSpecific"` |  |
| ingress.hosts | list | `["localhost"]` | Host to listen to requests to |
| ingress.tls.secretName | string | `"radar-base-tls"` | Name of the secret containing TLS certificates |
| resources.requests | object | `{"cpu":"100m","memory":"2Gi"}` | CPU/Memory resource requests |
| nodeSelector | object | `{}` | Node labels for pod assignment |
| tolerations | list | `[]` | Toleration labels for pod assignment |
| affinity | object | `{}` | Affinity labels for pod assignment |
| client_id | string | `"radar_upload_backend"` | OAuth2 client id of the upload connect backend application |
| client_secret | string | `"secret"` | OAuth2 client secret of the upload connect backend |
| postgres.host | string | `"radar-upload-postgresql"` | Host name of the database to store uploaded data and metadata |
| postgres.user | string | `"postgres"` | Database username |
| postgres.password | string | `"password"` | Database password |
| managementportal_host | string | `"management-portal"` | Host name of the management portal application |
| serverName | string | `"localhost"` | Server name or domain name |

repository: RADAR-base/radar-helm-charts

gha_language: Mustache

repo_name: RADAR-base/radar-helm-charts


text:
# 3ID DID

3ID is one of a few DID methods supported by Ceramic that can be used to perform authenticated writes to streams that require DIDs. This includes the two default StreamTypes: Tile Documents and CAIP-10 Links.

When 3IDs are used in conjunction with IDX and the 3ID Keychain (as is implemented in 3ID Connect), a 3ID can easily be controlled with any number of blockchain accounts from any L1 or L2 network. This provides a way to unify a user's identity across all other platforms.

## Usage

See the [Authentication](https://developers.ceramic.network/build/authentication/) page to learn how to use the 3ID DID method in your Ceramic project.

## Design

The DID document for a 3ID is stored natively on Ceramic as a Tile Document StreamType, allowing for mutability and enabling it to securely handle key rotations. This is a desireable property particularly for end user DIDs. Additionally since 3ID is native to Ceramic, developers do not need to operate additional infrastructure or rely on other external technologies.

See [CIP-79](https://github.com/ceramicnetwork/CIP/blob/main/CIPs/CIP-79/CIP-79.md) for the full technical specification of the 3ID DID method.

## Other DID methods
Ceramic supports a few different DID methods for authentication. Below find links to the others:

- [Key DID](./key.md)
- NFT DID (coming soon)
- Safe DID (coming soon)


text:
# project-kron

## Features

### TODO

 - Manage Posts
   - Format
     - Instagram Post
     - Instagram Story
     - Twitter Posto
     - LinkedIn Article
     - ...
   - Picture(s) / Video(s)
   - Social Media Copy
   - Date & Time
   - Group / Client
   - Post State (Development, Ready, Published)
 - Manage Campaigns
   - A campaign can have multiple posts
 - Monthly Calendar View
 - Manage Groups/Clients
 - Manage Client
 - Platform Scripts

## Project setup
```
npm install
```

### Compiles and hot-reloads for development
```
npm run serve
```

### Compiles and minifies for production
```
npm run build
```

### Lints and fixes files
```
npm run lint
```

### Customize configuration
See [Configuration Reference](https://cli.vuejs.org/config/).

repository: BlatStudio/project-kron

repo_name: BlatStudio/project-kron


text:
BattleNationsWikia
==================

Wikitext builder for the game BattleNations.

Written in Perl.

The main script, readbn, finds the latest game files and processes
them into wikitext suitable for battlenations.wikia.com.

Installation
------------

If you are not a Perl Master, I recommend using MacPorts
(http://www.macports.org/install.php). After doing the base install,
you will need to run this command to get the dependencies:

   sudo port install perl5 p5-data-dump p5-dbi p5-dbd-sqlite p5-digest-sha1 p5-file-homedir p5-json-xs

If you are on Linux or Windows, you can probably find packages with
the required modules somewhere.

license: Unlicense

repository: bobmath/BattleNationsWikia

repo_name: bobmath/BattleNationsWikia


text:
# SignalR

SignalR Connection Interface Written in Go

Forked from github.com/hweom/signalr.  Credit where credit is due.

## Installation

SignalR client can be included in any project:

`go get gitlab.com/techviking/signalr`

## Usage

### Import

This part is typical of most libraries.

    import (gitlab.com/techviking/signalr)

Each SignalR connection is represented by a seperate instance.  (THIS IS NOT A SINGLETON!)  To simplify some things, the parameter for the constructor is a `Config` struct.

### Instantiation
    peerURL, _ := url.Parse("https://fakesignalrpeer.com")

    //basic config
    cfg := signalr.Config{
      ConnectionURL: peerURL
    }

The config exposes fields allowing you to set a non-default `*http.Client` and `http.Header` if special work is required to connect to the original endpoint, and `...Path` fields to override the default endpoints for negotiation, connection, or reconnection if necessary.  I imagine most implementers won't need this, but it doesn't hurt.  The constructor takes a value, not a reference, so that if it needs defaults it doesn't mutate your input in a way that you might not want.

    client := signalr.New(cfg)

client is of type signalr.Connection, which is an `interface` type.  This should make mocking it out in your application tests easier.  (and also gives me an easier way to ensure the external interface is sufficient for user needs)

### Everything is done with channels!

Before you connect, you're going to want start your listeners:

    errChan := client.ListenToErrors()
    dataChan := client.ListenToHubResponses()

The channels returned are buffered channels, so that rather than hanging, the code will intentionally be placed into a potential `panic` condition once they fill up.

### Okay, not QUITE everything...

The one exception to the above rule is scenarios where calls to `CallHub` result in an immediate response, detected when the response payload from the signalr peer has a matching identifier to a sent message.  In that scenario, the result message is sent back as a return fromm `CallHub`... unless it's an error.

### There's two ways to track most errors.

That errChan above?  It gives ALL the errors from the lib, whether or not they're from the signalr peer.  You might be wondering if that makes the application more difficult to debug, but I've tried to cover that front too.  The error chan will NEVER output *just* an error.  It will be one of the error types defined in this lib's `errors.go` file.  If you're not sure which one you've got, you can do a type switch, or alternately parse the resulting string (each type's implementation of the Error interface indicates its own type).
Also any method that should return an error (when one happens) will do so, enabling you to tie errors to
specific calls as necessary.

### Miscellaneous

The websocket library used under the hood is github.com/gorilla/websocket.

Due to my own personal requirements using this lib, I've made efforts to have instances of the connection client be threadsafe, as far as being able to send messages from or read messages into any number of goroutines.

## TODOs

* MORE TESTING (especially related to connection resiliency).

## Contributions

Make a Pull Request (or "Merge Request" as Gitlab calls it).  I'm actively using this library, so any pull requests will receive prompt attention from me.
Fork the project and make it your own!  I only ask that if you do that, lemme know!  If a fork includes featuers I don't have time or desire to implement, I'll put a link to the forked repo with full credit!

Happy coding!

repository: technicalviking/signalr

repo_name: technicalviking/signalr


text:
# GeoCAT-viz

The GeoCAT-viz repo contains tools to help plot data, primarily convenience functions that are used
to facilitate plotting geosciences data with Matplotlib, Cartopy, and possibly other Python ecosystem
plotting packages. GeoCAT-viz functionality is mainly used by
[GeoCAT-examples](https://github.com/NCAR/geocat-examples) and is of possible use for other GeoCAT components.

The repo provides several convenience functions under:

    `geocat.viz.` namespace

which are implemented in `$GEOCAT_VIZ/src/util.py`.

# Documentation

[GeoCAT Homepage](https://geocat.ucar.edu/)

[GeoCAT Contributor's Guide](https://geocat.ucar.edu/pages/contributing.html)

[GeoCAT-Examples Gallery](https://geocat-examples.readthedocs.io)

# Installation instructions

Please see our documentation for [installation instructions](https://github.com/NCAR/geocat-viz/blob/master/INSTALLATION.md).

repository: atmospheli/geocat-viz

repo_name: atmospheli/geocat-viz


text:
## `~littel-ponnys`
Today, I completed the clay integration by making clay just give us dates in
`%wris`. I also then went and implemented `%dude` and a stripped down version
of `%hood` which can't deal with `+crane`s.

~rovnys finished implementing the `%path` schematic.

The next thing to do is to implement the basic version of `%core`, which is how
we compile hoon files to real Urbit executables. From there, we can add imports
and other `+crane`s.

repository: urbit/proposals

repo_name: urbit/proposals


text:
# Windows Manager

StumpWM is a windows manager which is very customizable and really helps speed things up (much less mouse clicking).

Sharing some settings which could help others get started.

# File Descriptions

`stumpwmrc` -- copy this to `~/.stumpwmrc` it has sensible keybindings and example of browser + terminal default setting
`stump_desk` -- copy this to `~/.stump_desk` and overwrite as described in the ~/.stumpwmrc file, keeps memory of physical layout of things
`stump_window` -- copy this to `~/.stump_window` and overwrite as described in the ~/.stumpwmrc file, keeps record of where your windows (e.g. browser and terminal) were placed

# Key bindings

Movements commonly used:

`C-t C-o` -- cycle through frames -- if only 2 or 3 applications open, this is great for navigation
`C-t C-f C-h` -- you can alter the keybinding, essentially moves in direction of hjkl bindings (in this case `h` for left)
`C-t ;` -- enter a command -- such as `loadrc` or `quit` or `reload`
`C-t f` -- for lots of windows, numbers appear and you can select them by number
`C-t k` -- kills a frame
`C-t R` -- removes a split from a frame
`C-t S` -- splits vertically
`C-t s` -- splits horizontally
`C-t <space>` -- cycles through windows in frame
`C-t t` -- switches between last window in frame and back

## groups

`C-t g c` -- create a new group
`C-t g o` -- goes to last group accessed
`C-t g <space>` -- goes to next group in list
`C-t g k` -- kill current group
`C-t g r` -- rename current group

gha_language: C