text:
# The Survey/Spreadsheet export scenario!

The guide present how to gather data from your customers, citizen, attendees, listener or any kind of people that might produce data or share their opinion or information.

To do so, it's convenient to use simple tools like online survey platforms, online spreadsheet platforms that as built-in CSV export feature, and finally get this data into OpenDataSoft to store, process, and provide advanced analytic dashboards to display it.

**The different steps explained :**

- A form will help users to fill in the requested information or data
- This form will automatically fill a spreadsheet with all the answers
- A first round of processing can be applied in the spreadsheet tool itself
- Then, the spreadsheet will be exported as a standard export form like CSV. In some tool we talk about publishing the spreadsheet publicly.
- This direct access link will be used as the remote source of an OpenDataSoft dataset.
- A more advance round of processing can be applied on the data.
- The data is published and is now ready to be visualized.

In this guide we will see how to do so with **Google Form** as the form tool. **Google Sheets** as the spreadsheet tool and CSV publisher.
We will finally apply some advanced processing and create a simple dashboard to analyse the results.

## Live example!

Share withs us your travel experiences! And see how it goes on the platform!

The form:
https://docs.google.com/forms/d/e/1FAIpQLScQw8zszuqt37pPN_wPZcLfhc50MMoI-_8P_AK-pYlBWQg2dw/viewform?usp=sf_link

The dataset:
https://discovery.opendatasoft.com/explore/dataset/travel-experience-survey/

## How to :

#### Create a from

Go to **Google Form** [here](https://docs.google.com/forms/u/0/), create a new form by adding some questions about your customer, or metadata that you'd like to collect.

In this example, we will create a database of public museums.
The aim is to create a database with the name of the musuem, a description, the type, a location and a picture.

1. A form with input fields:
![the form](1.png)

1. An URL input field to get an image:
![url input field](2.png)

1. Digit input field with content restrictions:
![postal code with digit verification](3.png)

1. Google Form propose different features like splitting your form in blocks to create several pages
![several blocks of inputs](3bis.png)

1. Once your form created, go to Responses, and click on the Google Sheets icon
![reponses](4.png)

1. Create a new spreadsheet
![create a spreadsheet](5.png)

1. Observe the spreadsheets column list
![spreadsheet columns](6.png)

1. It's now time to test the form and see the results
![preview](7.png)

1. Test
![first test](8.png)
![first test second part](9.png)

1. After a few tests, go back to the spreadsheet and see the first lines. It's the result of your submissions.
![first submissions](10.png)

1. It's now time to export this spreadsheet, go to File, Publish to the web...
![publish to the web](11.png)

1. Select the CSV format, and publish to get the export link. Copy it.
![copy the CSV publish link](12.png)

#### Time to go to OpenDataSoft :

1. Create a new dataset
![13_ODS_create_new_dataset](13_ODS_create_new_dataset.png)

1. Add a source, paste the url in the URL input field
![14_ODS_url](14_ODS_url.png)

1. See the preview that OpenDataSoft successfully got the data and understood the file format
![15_ODS_preview](15_ODS_preview.png)

1. Let's do the classic feature round table
    1. Add some facets
        ![16_ODS_facets](16_ODS_facets.png)
    1. Multiple text input fields can be set as multivalued facets
        ![17_ODS_multivalued](17_ODS_multivalued.png)
    1. Force columns types, specially for identifier as text
        ![18_ODS_text](18_ODS_text.png)
    1. The File processor is usefull to get the picture linked by the URL, add a File processor and select the corresponding field.
        ![19_ODS_file](19_ODS_file.png)

1. Time to save, publish and see the result ! The table view:
![20_ODS_table](20_ODS_table.png)

1. The image gallery:
![21_ODS_image](21_ODS_image.png)

Congratulation ! You have your first crowdsourced-ready dataset !

The final requirement will be to activated the scheduling !
- Go back to your back-office, go to your dataset, scheduling tab:
    - add some scheduling, for example 2 hourly scheduling at 00 and 30. (to get new data and publish it every 30 minutes)
- Submit some other tests, wait, and see how your new submits are processed and published automatically on your OpenDataSoft platform!

repository: opendatasoft/ods-cookbook

repo_name: opendatasoft/ods-cookbook


text:
# Sublime User Settings

For Sublime Text 3.

## Usage:

Open Sublime, then use the menu to open `Settings - User`.
Paste the contents of [`Preferences.sublime-settings`](https://github.com/cooperka/personal-settings/raw/master/sublime/Preferences.sublime-settings) there.

license: MIT

repository: cooperka/personal-settings

branch_name: refs/heads/main

extension: md

license_type: permissive

repo_name: cooperka/personal-settings


text:
### [CVE-2008-3289](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-3289)
![](https://img.shields.io/static/v1?label=Product&message=n%2Fa&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=n%2Fa&color=blue)
![](https://img.shields.io/static/v1?label=Vulnerability&message=n%2Fa&color=brighgreen)

### Description

EMC Dantz Retrospect Backup Client 7.5.116 sends the password hash in cleartext at an unspecified point, which allows remote attackers to obtain sensitive information via a crafted packet.

### POC

#### Reference
- http://securityreason.com/securityalert/4025

#### Github
No PoCs found on GitHub currently.

repository: trickest/cve

gha_language: HTML

gha_license_id: MIT

repo_name: trickest/cve


text:
This API enables the functionality to support the Inventory Linking Export process.  Inventory Linking controls and monitors cargo moving through temporary storage facilities, and allows the movement/transition through frontiers.

There are three functional areas;

-  **Consolidation**  This enables the combining of consignments into one master consignment, or splitting into multiple consignments.
-  **Movement**  Records the movement of consignments within Customs controlled storage facilities.
-  **Query**  The querying of data held within the Inventory Linking Export database.

Within each of these functional areas, there are multiple message types, each performing a specific activity.

repository: hmrc/customs-inventory-linking-exports

gha_language: Scala

repo_name: hmrc/customs-inventory-linking-exports


text:
# styled-x

[![npm](https://img.shields.io/npm/v/styled-x.svg)](https://www.npmjs.com/package/styled-x)
[![npm](https://img.shields.io/npm/dt/styled-x.svg)](https://www.npmjs.com/package/styled-x)
[![npm](https://img.shields.io/npm/l/styled-x.svg)](https://github.com/negativetwelve/styled-x/blob/master/LICENSE)
[![CircleCI](https://img.shields.io/circleci/project/github/negativetwelve/styled-x.svg?label=circle)](https://circleci.com/gh/negativetwelve/styled-x)
[![Travis](https://img.shields.io/travis/negativetwelve/styled-x.svg?label=travis)](https://travis-ci.org/negativetwelve/styled-x)
[![AppVeyor](https://img.shields.io/appveyor/ci/negativetwelve/styled-x/master.svg?label=appveyor)](https://ci.appveyor.com/project/negativetwelve/styled-x)
[![Coveralls](https://img.shields.io/coveralls/negativetwelve/styled-x.svg)](https://coveralls.io/github/negativetwelve/styled-x?branch=master)

Cross-platform component library built with react-x.

## Getting Started

Install `styled-x` using `yarn`:

```shell
yarn add styled-x
```

## Usage

```javascript
// You can import the entire component library as a single import:
import Styled from 'styled-x';

// Or you can import individual components:
import {Text, View} from 'styled-x';
```

## Components

Component | Version | Description
----------|---------|------------
[`styled-x-primitives`](/packages/styled-x-primitives) | [![npm](https://img.shields.io/npm/v/styled-x-primitives.svg)][npm-primitives] | Cross-platform Image, Text, and View components.

[npm-primitives]: https://www.npmjs.com/package/styled-x-primitives

## Contributing

If you have any ideas on how this module could be better, [create an Issue](https://github.com/negativetwelve/styled-x/issues) or [submit a PR](https://github.com/negativetwelve/styled-x/pulls).

repository: negativetwelve/styled-x

branch_name: refs/heads/master

gha_language: JavaScript

repo_name: negativetwelve/styled-x


text:
# Image Annotation Tools
*For the Flickr30k dataset*

This repository contains all the code you need to look through the
Flickr30k images and write notes about them, right in your browser.
There are two separate tools: one general tool that I made for the annotation of unwarranted inferences (but that you can also just use to page through the data), and one tool that I made to quickly add tags to a subset of the images. Both tools were made using Flask.

If you use this tool in your research, I'd appreciate it if you cite [this paper](https://arxiv.org/abs/1605.06083).

```
@inproceedings{miltenburg2016stereotyping,
Author = {Emiel van Miltenburg},
Booktitle = {Proceedings of Multimodal Corpora: Computer vision and language processing (MMC 2016)},
Date-Added = {2016-05-15 16:08:52 +0000},
Date-Modified = {2016-05-15 16:11:58 +0000},
Editor = {Jens Edlund and Dirk Heylen and Patrizia Paggio},
Keywords = {ulm2},
Pages = {1-4},
Title = {Stereotyping and Bias in the Flickr30k Dataset},
Url = {http://www.lrec-conf.org/proceedings/lrec2016/workshops/LREC2016Workshop-MCC-2016-proceedings.pdf},
pdf = {http://www.lrec-conf.org/proceedings/lrec2016/workshops/LREC2016Workshop-MCC-2016-proceedings.pdf},
Year = {2016}}
```

**Requirements**

* Flask
* Python 3 (the code may also work on Python 2, but I only tested it on 3)
* The Flickr30kEntities dataset (images + descriptions)

**Set-up**

* Clone this repository
* Copy the Flickr30k data to the relevant folders in `./static/`
* Install Flask

## General tool
The general tool is very versatile. It features navigation (so you can go to the first, previous, random, next, and last image), and several text boxes for annotation.

The top four input fields are easily modifiable through Javascript (see `templates/image_page.html`). I made them so that the annotations get written to the larger text area in a standardized (machine-readable) format. Just write down your thoughts in any of the four categories and press Enter. The text area contains everything that will be saved to an external file called `comments.txt`. When you're done annotating an image, press 'submit' and your annotations are appended to the comments file.

Start this tool by running `python image_viewer.py` on the command line. Python will then serve the image viewer at `http://<IP_ADDRESS>:5000/`.

## Subset tagger
This tool is useful if you want to quickly tag a portion of the data, for example a sample of the files that contain the word 'baby'. Here is how to use this tool:

1. Write all the relevant file IDs to a `.txt` file in the `noun_files` directory. E.g. `baby.txt`.

2. Start this tool by running `python annotate_selection.py` on the command line. Python will then serve the image viewer at `http://<IP_ADDRESS>:5000/`.

3. Enter the file name in the 'Submit file' window:

4. Start tagging. The tool will automatically add new tags that you enter in the 'other' text box.


text:
---
layout: kanji
v4: 302
v6: 324
kanji: 輝
keyword: radiance
elements: radiance, ray, small, little, human legs, army, chariot, crown, vehicle, car
strokes: 15
image: E8BC9D
on-yomi: キ
kun-yomi: かがや.く
permalink: /rtk/輝/
prev: 軍
next: 運
---

1) [dwhitman] 29-10-2007(197): Rays of light emitted from Apollo's chariot = radiance. Don't put the sun into this kanji. The rays are coming from the chariot directly!

2) [erlog] 18-7-2008(134): Radiance is an army of rays.

3) [anroo] 25-7-2009(59): Radiance isn't just a few rays, but a whole army of them.

4) [sethimayne] 25-10-2007(30): When I think of radiance I think of the greek god Zeus - picture him throwing rays of lightning (hence the extra jaggedness of the character) from atop his chariot riding through the heavens.

5) [brendanmacdonald] 21-4-2008(13): Ray's little legs joined the army - so Ray-did-a-dance (radiance).


text:
# Release Note
Sponsored Search API Ver.6.5

## Release version
6.5 (WSDL version : 6.5.0)

## Type of version up
Minor version up

## Main features enhancement on the release
∗Target Data Objects and Enumerations are referable on the list of Data Objects (Enumerations).

#### 1. Conversion tracking across different devices (Website and click-to-call)
Conversions is tracked based on the user login information along with the existing cookie information.

This enhancement will enable you to track conversions across different devices such as the case when the product was bought on smartphone after the ad was clicked on PC.

The following enhancements have been updated:
1. The flag to control conversions across different devices has been added.
1. The report field used for conversion tracking has been added.

##### Target Web Service
 * [ConversionTrackerService](/docs/en/api_reference/services/ConversionTrackerService.md)
 * [ReportDefinitionService](/docs/en/api_reference/services/ReportDefinitionService.md)

#### 2. Ad rotation setting by ad groups
Ad rotation setting has been changed from campaign level to ad group level.

The following enhancements have been updated:
1. The items for adGroupAdRotationMode were added.
The following two values are available for 'ad rotation' items.
    - OPTIMIZE：Optimizes and display ads
    - ROTATE_FOREVER：Always rotates ads evenly (not optimized)
1. The item for the campaign’s have become read-only.

    - On creating a new campaign, “OPTIMIZE” is evenly set to the 'ad rotation' item.
For this reason, if other enumeration besides "OPTIMIZE" is specified, it will be changed to "OPTIMIZE" when creating a new campaign.
    - On updating a campaign, even if you set a value when updating the campaign, the existing setting will be responded. It cannot be updated with any other enumuration.
1. The option "OPTIMIZE" is applied on ad distribution if the enumerations below have been set  for the item "adServingOptimizationStatus" on campaign.
    - ROTATE
    - CONVERSION_OPTIMIZE

*Above changes 2 and 3 have been applied to the lower versions (Ver.6.4.0/6.3.0) similarily.

##### Target Web Service
 * [CampaignService](/docs/en/api_reference/services/CampaignService.md)
 * [AdGroupService](/docs/en/api_reference/services/AdGroupService.md)

#### 3. App Conversion Tracking Settings
At the time of conversion tracking for Mobile app download campaigns, you cannot select “Include” (Use conversion for Auto Bidding) for both “Download” and “App First Open” for the same package.

The following enhancements have been updated:
1. A validation has been added so that an error occurs when the following two operations are performed.
    - The case if you select two settings below for the same ‘appId’ (application ID) at a time:

      App conversion types: “Download”, “Use for auto bidding”

      App conversion types: “App First Open”, “Use for auto bidding”
    - The case if you select “App First Open” AND “Use for auto bidding” for conversion setting without the settings both “Download” and “Do not use for auto budding” on App conversion type in advance for the same ‘appId’:
1. You are able to search the conversion settings of app using the ‘appId’.

*Above change 1 has been applied to the lower versions (Ver.6.4.0/6.3.0) similarily.

##### Target Web Service  You will be able to search the conversion settings of app using the ‘appId’.
 * [ConversionTrackerService](/docs/en/api_reference/services/ConversionTrackerService.md)

## Impact on each Version from the change of Services

Service

Ver.6.4 or before

Ver.6.5

 ConversionTrackerService
 No change in API IF.
*Error codes have been added.

  ・The flag 'CrossDeviceConversionFlag' to control conversions across different devices has been added.

  ・Conversion settings for app can be searched by application ID (appId).

  ・Error codes have been added.

 ReportDefinitionService
 No change in API IF.
*Report fields have been added.
 No change in API IF.
*Report fields have been added.

 CampaignService

  ・The item for the campaign’s ‘adServingOptimizationStatus’ has become read-only.

  ・On the request of ADD/SET, 'adServingOptimizationStatus' is 'Ignore'.

  ・On the response of ADD/SET, the responded enumuration to 'adServingOptimizationStatus' is 'OPTIMIZE' for ADD case, and the existing enumuration which has been already set is for SET case.

  ・The item for the campaign’s ‘adServingOptimizationStatus’ have become read-only.

  ・On the request of ADD/SET, 'adServingOptimizationStatus' is 'Ignore'.

  ・On the response of ADD/SET, the responded enumuration to 'adServingOptimizationStatus' is 'OPTIMIZE' for ADD case, and the existing enumuration which has been already set is for SET case.

 AdGroupService
 No change in API IF.
*Ad rotation (optimization) setting is not available for ADD/SET/GET.

  ・'AdGroupAdRotationMode' has been added.

  ・Ad rotation (optimization) setting by ad group is available for ADD/SET/GET.

 CampaignRetargetingListService
 No change in API IF.
*Error codes have been added.
 No change in API IF.
*Error codes have been added.

 AdGroupRetargetingListService
 No change in API IF.
*Error codes have been added.
 No change in API IF.
*Error codes have been added.

## The end scheduled date for Sponsored Search API 6.3
Sponsored Search API 6.3 is scheduled to sunset on the end of March, 2018

repository: nshinmen/sponsored-search-api-documents

repo_name: nshinmen/sponsored-search-api-documents


text:
---
title: Content length issue on 404 pages in Padrino 10.7
author: Rob
layout: post
permalink: /archives/content-length-issue-on-404-pages-in-padrino-10-7/
dsq_thread_id:
  - 888642001
categories:
  - AppDev
---
#

I've been tooling around with [PadrinoRB][1] lately. Personally, it has been a nice mix of [SinatraRB][2] and Rails. One of the annoying issues I've hit is that when I define a view for my 404 errors:

	error 404 do
  		response.status = 404
  		render 'errors/404', :layout=>:applayout
	end

It will only show 30 characters of the defined view. Luckily, in this day in age, Google has all the answers and I found out [here][3] that in my Gemfile I need to define a certain version of Sinatra for this to work. So I popped open my Gemfile and added the following:

	gem 'rake'
	gem 'sinatra', '1.3.2'
	gem 'sinatra-flash', :require => 'sinatra/flash'

Once I locked in 1.3.2 instead of the 1.3.3 version of sinatra I was using, it worked like a charm and I stopped looking like a complete idiot that doesn't now how to serve up error pages properly.

 [1]: http://www.padrinorb.com/ "PadrinoRB"
 [2]: http://www.sinatrarb.com/ "Sinatrarb"
 [3]: https://groups.google.com/forum/?fromgroups=#!topic/padrino/ThPy9U4sK4w "here"

branch_name: refs/heads/source

gha_language: Ruby


text:
Expand Descendants Command
==========================

Description
-----------
This module adds a command that allows the user to expand all descendants of an item from the Sitecore content tree.

References
------------
Blog: http://www.partechit.nl/nl/blog/2013/03/handy-sitecore-command-expand-descendants
GitHub: https://github.com/ParTech/Expand-Descendants-Command

Installation
------------
The Sitecore package *\Release\ParTech.Commands.ExpandsDescendants-1.0.0.zip* contains:
- Binary (release build).
- Configuration include file.
- Core items that are required for this module.

Use the Sitecore Installation Wizard to install the package.
After installation, the command will be available from the context menu in the Content Editor Tree.

It will not require any further configuration.

Release notes
-------------
*1.0.0*
- Initial release

Author
------
This solution was brought to you and supported by Ruud van Falier, ParTech IT

Twitter: @BrruuD / @ParTechIT
E-mail<EMAIL_ADDRESS>
Web: http://www.partechit.nl

repository: ParTech/Expand-Descendants-Command

repo_name: ParTech/Expand-Descendants-Command


text:
###Nuget Packages
####uPubDash

[![NuGet version](https://badge.fury.io/nu/uPubDash.svg)](http://badge.fury.io/nu/uPubDash)

Url : **http://www.nuget.org/packages/uPubDash/**

Cmd : ```PM> Install-Package uPubDash```

##README

###Installation
When installing via nuget the publication queue user control is copied into the umbraco folder within the solution.  The only thing left to do is add the control to the dashboard.config and when the application is started the database will be configured and you're all set up.

###Configuration
To add the publication queue user control to a dashboard tab add the following to dashboard.config

```XML
<tab caption="Publication Requests">
    <control addPanel="true">~/umbraco/uPubDash/UserControl/PublicationDashboard.ascx</control>
</tab>
```

repository: dev-mag/uPubDash

repo_name: dev-mag/uPubDash


text:
# Provision Govready Using CloudFormation

See https://govready.com/.

GovReady-Q Compliance Server simplifies and automates compliance for FISMA, the NIST Risk Management Framework, 800-53, and DFARS 800-171 (and more to come) with Compliance Apps that map security controls to your technology stack, an Automation API to update evidence and artifacts from live systems, and OpenControl repositories that provide re-suable control implementation descriptions.


text:
---
layout: post
title: "Starburst Jumbo Jelly Beans"
brand: Starburst
variety: Jumbo Jelly Beans
date: 2020-02-26
permalink: starburst-jumbo-jelly-beans
image: starburst-jumbo-jelly-beans.jpg
image-credit: upcitemdb.com
image-layout: float
---

Welcome back to A Boy and His Beans for
our fifth season of jelly bean reviews!
(Can you believe it?)

To kick things off for 2020,
we return to one of the most prolific – and most popular –
jelly bean brands of the day: Starburst.
How will their jumbo bean offering stack up against their classic beans?
Let's dive in!

## Size and shape

It feels a little bit unfair to judge this category as I would
any other set of jelly beans.
Given that they advertise themselves as "jumbo", it would seem wrong
to take them to task for being larger than my preferred size.
The size does indeed live up to the jumbo billing,
weighing in at three to four times as large as a standard Starburst jelly bean.

In another contrast to the standard Starburst jelly bean,
these beans have a very strong bean shape,
with a subtle but clear curve along the length of the bean
and a definite dimple on most of them.

I'll have to penalize a little bit for receiving a double bean
(a terrifying prospect when the beans are jumbo-sized to begin with)
and a bean where a significant chunk of the shell was missing.

**4 out of 5 beans**

## Chewability

The jumbo edition maintains Starburst's strong reputation
in the chewability department.
The only issue is that applying the same chewability attributes
to such a large bean results in something that
takes a little bit too long to masticate to the point of swallowability.

**4 out of 5 beans**

## Texture

Starburst Jumbo Jelly Beans seem to have the same sort of shell and insides
as the regular-sized Starburst beans, just on a larger scale.
The shell still cracks beautifully and the insides are still smooth enough.

I think a bit of a misstep was made in determining how thick the shells
on these jumbo beans should be, though.
When scaling up the bean, they seemed to scale up the shell:insides ratio
proportionally, and this resulted in a shell that is just a bit much.

In the world of typography, there is the concept of
["display" variant of a typeface](https://en.wikipedia.org/wiki/Typeface#Display_type),
which is intended for use at larger sizes and has more refined detailing than
you would see if you simply scaled up a typeface designed for regular body text.
These jumbo beans should have taken a page from that book
and let the shell be a little bit more subtle than it turned out to be.

**3 out of 5 beans**

## Taste and flavor

Flavors

:cherries: Cherry

:orange: Orange

:strawberry: Strawberry

:lemon: Lemon

:green_apple: Green Apple

:grapes: Grape

I won't spend a lot of time in this section, because the flavoring is
exactly the same as the classic Starburst Jelly Beans Original set.
[Take a look back at my thoughts on these flavors.](/starburst-jelly-beans)

**7 out of 10 beans**

## The one-of-each test

Perhaps the ultimate test of a bag of jelly beans is how enjoyable it is
to take one of each flavor and eat them all at the same time.[^1]

As with the [Brach's Giant Egg'Ruptions](/brachs-giant-egg-ruptions),
I will not attempt the one-of-each test with six of these jumbo beans.
They are exempt them from scoring in this category.

## Conclusion

Starburst never disappoints, and the jumbo edition is no exception.
While I found a couple minor tradeoffs for the larger beans,
they are still undeniably great beans, and even better than their
standard-sized progenitors in their shape.

Definitely pick some up if you like the original Starburst flavors
and don't mind eating only one big bean at a time.

Category         | Score
---------------- | ---------------
Size and shape   | **4**/5 beans
Chewability      | **4**/5 beans
Texture          | **3**/5 beans
Taste and flavor | **7**/10 beans
---------------- | ---------------
_Total_          | **18**/25 beans

---

[^1]: This test is specific to fruit flavors _only_. While non-fruit flavors like licorice or buttered popcorn may be welcome, they are exempt from this test. Because that's just nasty.

repository: Scotchester/jellybeans

branch_name: refs/heads/gh-pages

gha_language: CSS

repo_name: Scotchester/jellybeans


text:
---
layout: post
authors: ["Belinda Weaver"]
title: "Updating Library Carpentry"
date: 2016-06-06
time: "00:00:01"
tags: ["sprints", "hackathons", "Data Carpentry"]
redirect_from:
  - /blog/2016/06/LibrarCarpentrysprint.html
---
A global team worked to update the [Library Carpentry](https://github.com/LibraryCarpentry) curriculum and lesson material at
this year’s [Mozilla Science Lab Global sprint](https://science.mozilla.org/programs/events/global-sprint-2016).

The work kicked off in Brisbane, where [Clinton Roy](https://twitter.com/clinton_roy), [Natasha Simons](https://twitter.com/n_simons) and I worked with [Carmi Cronje](https://twitter.com/machinical) in Sydney to start the ball rolling.
[Matthias Liffers](https://twitter.com/mpfl) came online in Perth two hours later. At 5.30 pm our time, we handed over to teams in South Africa, the Netherlands, and the UK, led by [Anelda van der Walt](https://twitter.com/aneldavdw), [Mateusz Kuzak](https://twitter.com/matkuzak), and [James Baker](https://twitter.com/j_w_baker) respectively.

James, with his colleagues [Owen Stephens](https://github.com/ostephens) and [Daniel van Strien](https://github.com/davanstrien), were the original developers of the Library Carpentry material.

During the sprint, James developed a new regex quiz, while Owen helped update and migrate the OpenRefine material.
[Jez Cope](https://github.com/jezcope) volunteered as a maintainer for the git lesson.

Canadian and US teams began work as the sun moved around the globe. These included [Juliane Schneider](https://github.com/pitviper6) from UCSD working on OpenRefine and [Gail Clement](https://github.com/Repositorian) from Caltech, working on [Author Carpentry](https://github.com/Repositorian/AuthorCarpentry). [Laurel Narizny](https://github.com/lnarizny) and [Robert Doiel](https://github.com/rsdoiel) also signed on from Caltech.

[Cam Macdonell](https://twitter.com/cjmacdonell) seemed to be up all hours and was a key driver for getting the material migrated into `gh-pages` and the new lesson templates.

The original four-module lesson (covering shell, regular expressions, git, and OpenRefine) has now become seven,
with a new SQL module (based on the Data Carpentry lesson) being added, along with others for persistent
identifiers and computational thinking.

Draft learning objectives were created for most of the main lessons which are linked
from [here](https://github.com/data-lessons/librarycarpentry).

Material for five modules was migrated to the new Data Carpentry lesson template. Library-based datasets were
swapped in to make the lessons more relevant to librarians.

During the sprint, all the Library Carpentry action was co-ordinated through a
[dedicated chat room](https://gitter.im/weaverbel/LibraryCarpentry) and via daily evening Hangouts
where the day’s work was reported, before being handed over to the incoming team, rather like a baton being passed in a relay race. We hope to continue the conversation through the chat room as we continue to develop the material.

This was a really great experience, and I thank all the amazing people who dedicated their time to the project, and who
have volunteered as maintainers into the future. There is still a lot of work to be done, but we made huge progress.

I hope Anelda, Cam, James, Mateusz and some of the other participants will also chime in with their own stories and achievements. My take is only partial. Please also correct any errors I have made.

Thanks again all - what a fantastic effort.

repository: swcarpentry/website

repo_name: swcarpentry/website


text:
# Keith's Heading

Project notes here with original README below. Then I'll rewrite this if it works. Initially, I want to:
- deploy to Cloudflare Pages.
Then later:
- add PWA capabilities, including push notifications (OneSignal).
Amend this todo list as project progresses. Adding detailed notes below with latest changes first

## yymm02a Branch3

## yymmddb Branch2

## 210818b 1st Config
Usually, I create a 1st Config branch to get a working site with config changes as per original README instructions and note files changed with any additional notes. Most of this detail is deleted from final README but it serves to keep track of installation progress. I can't find any configuraton notes in the Smix code. But here's what I've found to change so far:
- /src/data/site.json - author info
- /src/layouts/default.liquid - not been personalized so not sure this is right place

So I'll deploy to Cloudflare now, and investigate live site for required changes.

## 210818a Preparation
Notes for my workflow instructions:
- Created new repo (not fork because that seems to imply a commitment to update original which is not my intention for my own starter. Not sure what best practise is)
- Imported https://github.com/hirusi/smix-eleventy-starter
- Renamed LICENSE to LICENSE-smix and used `Add file` to add a BSD-3 LICENSE (see commit notes for reasoning). Note: Github helpfully offers templates when the new filename is LICENSE.

## Original Smix README below...

***

# 🌻 Smix
__A gulp-based starter for Static Site Generators, preconfigured for Eleventy and Forestry CMS.__

## Framework

* __Eleventy__ 0.12.1 out of the box.
  * Date filters for a friendly version such as `10 March 2020`, and ISO8601 (also RFC822 compatible).
  * `getUrl` shortcode similar to Jekyll's `post_url` and `link` liquid tags.
  * Custom rendering engine for HTML files - `Liquid v9`.
    * Adds support for missing filters such as `where` and improves performance.
* __Preconfigured__ for [Forestry CMS](https://forestry.io/) _and_ [Netlify](https://netlify.com/). Find more [instructions in the docs](docs/publishing.md).
* __Indie__ publishing and reading experience.
  * microformats2 support for `h-card`, `h-entry`, and `h-feed` out of the box.
* Modern __JavaScript__.
  * Transpilation via Babel.
    * Support for __ES2015__ JavaScript syntax.
    * Support for __ES2017__ `async`/`await` syntax.
  * Module bundling via Browserify.
* __PostCSS__ as the choice of CSS transpiler.
  * Includes: imports, nesting, purge, minification, autoprefixer.
  * TailwindCSS (v1), configured to strip out unused classes from production builds.
  * Easily build a dark mode using the included `dm` screen type: `dm:bg-gray-900`.
* __SEO__ and other behind-the-scenes goodies.
  * Meta tags for social networks (Open Graph/Twitter).
  * Sitemap with `changeFrequency`; `robots.txt` (please also see [issue #7](https://github.com/hirusi/smix-eleventy-starter/issues/7)).
  * An Atom feed with support for both `published` and `updated` dates on articles.
  * Support for `content-description` meta tag.
* A sane __fonts__ setup.
  * The `font-sans` class is configured to use system-default fonts.
  * Include fonts locally for enhanced privacy of your visitors.
  * `typeset` for professional looking content.
* Minified assets on production.
* __Prettier and editorconfig__ for consistent formatting.
* __Modular gulp task files__ for easy configuration and modification.

## To-Do

* Reload automatically after our assets change (filed [issue here](https://github.com/11ty/eleventy/issues/1125), waiting for response/PR approval). Please reload manually for now.
* System default serif font class.
* Scheduled blog posts.
* Lazy-load images.
* Responsive images.

## How to Use

### Local Development

See [development docs](docs/development.md).

### Staging

`ELEVENTY_ENV` must be set to `staging`.

* `npm run staging`

### Production

`ELEVENTY_ENV` must be set to `production`.

* `npm run prod`

gha_license_id: NOASSERTION


text:
* A repository to easily clone all the repositories which were used to drive ODSC East 2019 sessions

# Pre-requisites:
* git
* requests module should be installed
    * pip install requests

# Running the script
* python get_oe2019_code.py

# Outcome
* A folder 'ODSC_EAST_2019_CODE' gets created in current directory.
* The code repositories get sequentially cloned to the above folder

# Improvement areas
* Add tests
* The repositories can be fetched in parallel


text:
## Available Functions

Available functions are:

-  Administration console:

   -  A convenient web based administration console is provided, through
      which the administrator can manage several features of BaasBox

-  Content management:

   -  Definition of "objects collection (AKA documents)"
   -  Creation, modification and deletion of objects
   -  Granting and revoking reading/modification/cancellation
      authorization on single objects
   -  Queries that allow specifying selection and
      ordering criteria
   -  Management of "special" contents called Assets, which may be files of any kind,
      to which you can associate arbitrary JSON data

-  Users management:

   -  Signup, Login, Logout, profile management (private features, public
      features and so on), forgotten password recovery, link and log-in
      through Facebook and Google+
   -  Role management: administrators, registered users, back-office
      users, creation of new roles.

-  File management:

   -  Create and fetch files
   -  Content and metadata extraction
   -  ACL
   -  Images resize

-  Push notifications:

   -  Push notifications for iOS and Android devices

-  DB management:

   -  Backup/restore and reset the integrated database

-  REST API Access management:

   - Enable/disable groups of REST endpoints from external access


text:
# ⚠⚠ This repo is no longer actively matinained. ⚠⚠

# express-conditionizr

A server-side collection of User Agent detects to let you know what's
looking at your page.  Based on and inspired by Conditionizr for the browser.

----------

**express-conditionizr** is based on Conditionizr, a project that digested user agents on the client-side.  Express has had some stale device detection middlewares, and I prefer the methodology of coniditionizr, that I made this "port" of parts of the library from client side to server side.

## Install / Download

`npm install express-conditionizr` or

`git clone git@github.com:clineamb/express-conditionizr.git`

## Using

You can check out the example directory for a quick express app setup.

**express-conditionizr** can be included as middleware on the entire app, on a router, or even on a specific route.

This middleware was made with Express 4 in mind, but has the same `function(req, res, next)` structure, so it can essentially be used with most other vesions of express (and connect).   Below are examples of how to incorporate into Express 4.

```js
var express         = require('express')
,   conditionizr    = require('conditionizr')
,   app             = express()
;

// ADD CONDITINIZER ON YOUR APP...
app.use(conditionizr);

app.get("/", function(req, res) {
    res.send(req.detects);
});

// setup the rest of your app...
```

**Setup on a route** (ex, router.js):

```js
var express         = require('express')
,   conditionizr    = require('conditionizr')
,   router          = express.Router()
;

// ADD CONDITINIZER On a whole route
router.use(conditionizr);

router.get("/example", function(req, res) {
    if(req.detects.mobile) {
        // render a mobile template, maybe!
    } else {
        // render other stuff
    }
});
```

... or add it on just a route ...

```js
// setup like before

router.route("/example2")
    .all(conditionizr)
    .get(function(req, res) {
        // do your route
    })
;
```

Two new variables appear in the `req` and `res` hashes: `req.detects` and `res.locals.detects`.  You'll get a hash of booleans like so:

**User Agent:** Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/40.0.2214.94 Safari/537
.36

```json
{
    "chrome": true,
    "opera": false,
    "firefox": false,
    "safari": false,
    "phantomjs": false,
    "ie11": false,
    "ie10": false,
    "ie10touch": false,
    "ie9": false,
    "ie8": false,
    "ie7": false,
    "android": false,
    "linux": false,
    "ios": false,
    "mac": false,
    "windows": true,
    "winPhone": false,
    "winPhone7": false,
    "winPhone75": false,
    "winPhone8": false,
    "localhost": true,
    "touch": false,
    "tablet": false,
    "phone": false,
    "mobile": false,
    "desktop": true
}
```

**Note:** Localhost is found using the `req.headers['host']` from `req.headers`.  This is the only test that uses this.

## Tests

**TODO**

----------

## License

Copyright (c) 2014, [Caroline<EMAIL_ADDRESS>
Permission to use, copy, modify, and/or distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies.

 IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

license: ISC

repository: clineamb/express-conditionizr

repo_name: clineamb/express-conditionizr


text:
# Documentation

This folder holds the documentation the IniParser.

## Usage

The usage is explained in detail in the [usage](/doc/usage.md) file.

Examples can be found in the [examples folder](/examples).

## API Reference

The API Reference is split into two parts:
* the [C API reference](/doc/c_api.md) and
* the [C++ API reference](/doc/c++_api.pdf).

The documentation can also be generated using doxygen.

The [uml folder](/doc/uml/) contains an image of a class diagram and a .cmi file which can be opened by an UML modeller like [Umbrello](https://umbrello.kde.org/).

### Class Diagram
![Class Diagram](/doc/uml/class_diagram.svg)

## The .INI format

The here implemented .INI format is explained in the [format](/doc/format.md) file.

Extra features and details on the concrete implementation can be found in the [feature](/doc/features.md) file.

repository: kloppstock/IniParser

repo_name: kloppstock/IniParser


text:
# [MeditationFacts](http://alexa.amazon.com/#skills/amzn1.echo-sdk-ams.app.2d942aef-a6e9-49a0-849b-ef88738da913)
![5 stars](../../images/ic_star_black_18dp_1x.png)![5 stars](../../images/ic_star_black_18dp_1x.png)![5 stars](../../images/ic_star_black_18dp_1x.png)![5 stars](../../images/ic_star_black_18dp_1x.png)![5 stars](../../images/ic_star_black_18dp_1x.png) 1

To use the MeditationFacts skill, try saying...

* *Alexa launch Meditation Facts.*

* *Alexa ask meditation facts to tell me a meditation trivia*

* *Alexa ask meditation facts to help.*

Meditation Facts Skill is about knowing the facts on benefits of doing regular meditation.

These facts came through studies and research from medical doctors and professionals from New York and New Jersey, on different people who does meditation versus those who don't.

It is a great and informative facts skill about meditation and its importance related to our health and wellness.

***

### Skill Details

* **Invocation Name:** meditation facts
* **Category:** null
* **ID:** amzn1.echo-sdk-ams.app.2d942aef-a6e9-49a0-849b-ef88738da913
* **ASIN:** B01ENLLKK0
* **Author:** Makarand Pande
* **Release Date:** May 6, 2016 @ 19:08:28
* **In-App Purchasing:** No


text:
# Stacks and Queues

* A stack is useful when we want to add elements inside a list into sequential order and remove the last element added. A queue is useful when we want the same behavior, but instead of removing the last added element, we want to remove the first element added to the list .

## code Challenge 11 :

Create a brand new PseudoQueue class. Do not use an existing Queue. Instead, this PseudoQueue class will implement our standard queue interface (the two methods listed below), but will internally only utilize 2 Stack objects. Ensure that you create your class with the following methods:

        enqueue(value) which inserts value into the PseudoQueue, using a first-in, first-out approach.
        dequeue() which extracts a value from the PseudoQueue, using a first-in, first-out approach.

## API :
- Stack :

1. Define a method called push which takes any value as an argument and adds a new node with that value to the top of the stack with an O(1) Time performance.

2. Define a method called pop that does not take any argument, removes the node from the top of the stack, and returns the node’s value, Should raise exception when called on empty stack .

3. Define a method called peek that does not take an argument and returns the value of the node located on top of the stack, without removing it from the stack,Should raise exception when called on empty stack .

4. Define a method called isEmpty that takes no argument, and returns a boolean indicating whether or not the stack is empty.

#  whiteboard :

![image](cc11.PNG)


text:
# Configuration: package.json and nx.json

There are two main types of configuration in every Nx workspace: [project configuration](#project-configuration)
and [the global Nx CLI configuration](#cli-configuration).

Projects can be configured in `package.json` (if you use npm scripts and not Nx executors) and `project.json` (if you
use Nx executors). Both `package.json` and `project.json` files are located in each project's folder. Nx merges the two
files to get each project's configuration. This guide covers the `package.json` case.

## Project Configuration

Every npm script defined in `package.json` is a target you can invoke via Nx. For instance, if your project has the
following `package.json`:

```jsonc
{
  "name": "mylib",
  "scripts": {
    "test": "jest",
    "build": "tsc -p tsconfig.lib.json" // the actual command here is arbitrary
  }
}
```

you can invoke `nx build mylib` or `nx test mylib` without any extra configuration.

You can add Nx-specific configuration as follows:

```jsonc
{
  "name": "mylib",
  "scripts": {
    "test: "jest",
    "build": "tsc -p tsconfig.lib.json" // the actual command here is arbitrary
  },
  "nx": {
    "namedInputs": {
      "default": [
        "{projectRoot}/**/*"
      ],
      "prod": [
        "!{projectRoot}/**/*.spec.tsx"
      ]
    },
    "targets": {
      "build": {
        "inputs": ["prod", "^prod"],
        "outputs": ["dist/libs/mylib"],
        "dependsOn": ["^build"]
      },
      "test": {
        "inputs": ["default", "^prod"],
        "outputs": [],
        "dependsOn": ["build"]
      }
    }
  }
}
```

### inputs & namedInputs

The `inputs` array tells Nx what to consider to determine whether a particular invocation of a script should be a cache
hit or not. There are three types of inputs:

_Filesets_

Examples:

- `{projectRoot}/**.*.ts`
- same as `{fileset: "{projectRoot}/**/*.ts"}`
- `{workspaceRoot}/jest.config.ts`
- same as `{fileset: "{workspaceRoot}/jest.config.ts}`

_Runtime Inputs_

Examples:

- `{runtime: "node -v"}`

Node the result value is hashed, so it is never displayed.

_Env Variables_

Examples:

- `{env: "MY_ENV_VAR"}`

Node the result value is hashed, so it is never displayed.

_Named Inputs_

Examples:

- `inputs: ["prod"]`
- same as `inputs: [{input: "prod", projects: "self"}]`

Often the same glob will appear in many places (e.g., prod fileset will exclude spec files for all projects). Because
keeping them in sync is error-prone, we recommend defining named inputs, which you can then reference in all of those
places.

#### Using ^

Examples:

- `inputs: ["^prod"]`
- same as `inputs: [{input: "prod", projects: "dependencies"}]`

Similar to `dependsOn`, the "^" symbols means "dependencies". This is a very important idea, so let's illustrate it with
an example.

```
"test": {
  "inputs": [ "default", "^prod" ]
}
```

The configuration above means that the test target depends on all source files of a given project and only prod
sources (non-test sources) of its dependencies. In other words, it treats test sources as private.

### outputs

Targets may define outputs to tell Nx where the target is going to create file artifacts that Nx should cache. `"outputs": ["dist/libs/mylib"]` tells Nx where the `build` target is going to create file artifacts.

This configuration is usually not needed. Nx comes with reasonable defaults (imported in `nx.json`) which implement the configuration above.

#### Basic Example

Usually, a target writes to a specific directory or a file. The following instructs Nx to cache `dist/libs/mylib` and `build/libs/mylib/main.js`:

```json
{
  "build": {
    "outputs": ["dist/libs/mylib", "build/libs/mylib/main.js"]
  }
}
```

#### Specifying Globs

Sometimes, multiple targets might write to the same directory. When possible it is recommended to direct these targets into separate directories.

```json
{
  "build-js": {
    "outputs": ["dist/libs/mylib/js"]
  },
  "build-css": {
    "outputs": ["dist/libs/mylib/css"]
  }
}
```

But if the above is not possible, globs can be specified as outputs to only cache a set of files rather than the whole directory.

```json
{
  "build-js": {
    "outputs": ["dist/libs/mylib/**/*.js"]
  },
  "build-css": {
    "outputs": ["dist/libs/mylib/**/*.css"]
  }
}
```

### dependsOn

Targets can depend on other targets. This is the relevant portion of the configuration file:

```json
"build": {
  "dependsOn": ["^build"]
},
"test": {
  "dependsOn": ["build"]
}
```

A common scenario is having to build dependencies of a project first before building the project. This is what
the `"dependsOn": ["^build"]` property of the `build` target configures. It tells Nx that before it can build `mylib` it
needs to make
sure that `mylib`'s dependencies are built as well. This doesn't mean Nx is going to rerun those builds. If the right
artifacts are already in the right place, Nx will do nothing. If they aren't in the right place, but they are available
in the cache, Nx will retrieve them from the cache.

Another common scenario is for a target to depend on another target of the same project. For
instance, `"dependsOn": ["build"]` of
the `test` target tells Nx that before it can test `mylib` it needs to make sure that `mylib` is built, which will
result in `mylib`'s dependencies being built as well.

You can also express the same configuration using:

```json
"build": {
  "dependsOn": [{ "projects": "dependencies", "target": "build" }]
},
"test": {
  "dependsOn": [{ "projects": "self", "target": "build" }]
}
```

With the expanded syntax, you also have a third option available to configure how to handle the params passed to the target
dependencies. You can either forward them to the dependency target, or you can ignore them (default).

```json
"build": {
   // forward params passed to this target to the dependency targets
  "dependsOn": [{ "projects": "dependencies", "target": "build", "params": "forward" }]
},
"test": {
  // ignore params passed to this target, won't be forwarded to the dependency targets
  "dependsOn": [{ "projects": "self", "target": "build", "params": "ignore" }]
}
"lint": {
  // ignore params passed to this target, won't be forwarded to the dependency targets
  "dependsOn": [{ "projects": "self", "target": "build" }]
}
```

This configuration is usually not needed. Nx comes with reasonable defaults (imported in `nx.json`) which implement the
configuration above.

### tags

You can annotate your projects with `tags` as follows:

```jsonc
{
  "name": "mylib",
  "nx": {
    "tags": ["scope:myteam"]
  }
}
```

You can [configure lint rules using these tags](/structure/monorepo-tags) to, for instance, ensure that libraries
belonging to `myteam` are not depended on by libraries belong to `theirteam`.

### implicitDependencies

Nx uses powerful source-code analysis to figure out your workspace's project graph. Some dependencies cannot be deduced
statically, so you can set them manually like this:

```jsonc
{
  "name": "mylib",
  "nx": {
    "implicitDependencies": ["anotherlib"]
  }
}
```

You can also remove a dependency as follows:

```jsonc
{
  "name": "mylib",
  "nx": {
    "implicitDependencies": ["!anotherlib"] # regardless of what Nx thinks, "mylib" doesn't depend on "anotherlib"
  }
}
```

### Ignoring a project

Nx will add every project with a `package.json` file in it to its project graph. If you want to ignore a particular
project, add the following to its `package.json`:

```jsonc
{
  "name": "mylib",
  "nx": {
    "ignore": true
  }
}
```

### workspace json

The `workspace.json` file in the root directory is optional. It's used if you want to list the projects in your
workspace explicitly instead of Nx scanning the file tree for all `project.json` and `package.json` files that match the
globs specified in the `workspaces` property of the root `package.json`.

```json
{
  "version": 2,
  "projects": {
    "myapp": "apps/myapp"
  }
}
```

- `"version": 2` tells Nx that we are using Nx's format for the `workspace.json` file.
- `projects` is a map of project names to their locations.

## CLI Configuration

The `nx.json` file configures the Nx CLI and project defaults.

The following is an expanded version showing all options. Your `nx.json` will likely be much shorter.

```json
{
  "npmScope": "happyorg",
  "affected": {
    "defaultBase": "main"
  },
  "workspaceLayout": {
    "appsDir": "demos",
    "libsDir": "packages"
  },
  "implicitDependencies": {
    "workspace.json": "*",
    "package.json": {
      "dependencies": "*",
      "devDependencies": "*"
    },
    "tsconfig.base.json": "*",
    "nx.json": "*"
  },
  "namedInputs": {
    "default": ["{projectRoot}/**/*"],
    "prod": ["!{projectRoot}/**/*.spec.tsx"]
  },
  "targetDefaults": {
    "build": {
      "inputs": ["prod", "^prod"],
      "dependsOn": ["^build"]
    }
  },
  "cli": {
    "defaultCollection": "@nrwl/js"
  },
  "generators": {
    "@nrwl/js:library": {
      "buildable": true
    }
  },
  "tasksRunnerOptions": {
    "default": {
      "runner": "nx/tasks-runners/default",
      "options": {
        "cacheableOperations": ["build", "lint", "test", "e2e"]
      }
    }
  }
}
```

### NPM Scope

Tells Nx what prefix to use when generating library imports.

### Affected

Tells Nx which branch and HEAD to use when calculating affected projects.

- `defaultBase` defines the default base branch, defaulted to `main`.

### Workspace Layout

You can add a `workspaceLayout` property to modify where libraries and apps are located.

```json
{
  "workspaceLayout": {
    "appsDir": "demos",
    "libsDir": "packages"
  }
}
```

These settings would store apps in `/demos/` and libraries in `/packages/`. The paths specified are relative to the
workspace root.

### Files & Implicit Dependencies

Nx performs advanced source-code analysis to figure out the project graph of the workspace. So when you make a change,
Nx can deduce what can be broken by this change. Some dependencies between projects and shared files cannot be inferred
statically. You can configure those using `implicitDependencies`.

```json
{
  "implicitDependencies": {
    "workspace.json": "*",
    "package.json": {
      "dependencies": "*",
      "devDependencies": {
        "mypackage": ["mylib"]
      },
      "scripts": {
        "check:*": "*"
      }
    },
    "globalFile": ["myapp"],
    "styles/**/*.css": ["myapp"]
  }
}
```

In the example above:

- Changing `workspace.json` affects every project.
- Changing the `dependencies` property in `package.json` affects every project.
- Changing the `mypackage` property in `package.json` only affects `mylib`.
- Changing any of the custom check `scripts` in `package.json` affects every project.
- Changing `globalFile` only affects `myapp`.
- Changing any CSS file inside the `styles` directory only affects `myapp`.

### inputs & namedInputs

Named inputs defined in `nx.json` are merged with the named inputs defined in each project's package.json.
In other words, every project has a set of named inputs, and it's defined as: `{...namedInputsFromNxJson, ...namedInputsFromProjectsPackageJson}`.

Defining `inputs` for a given target would replace the set of inputs for that target name defined in `nx.json`.
Using pseudocode `inputs = packageJson.targets.build.inputs || nxJson.targetDefaults.build.inputs`.

You can also define and redefine named inputs. This enables one key use case, where your `nx.json` can define things
like this (which applies to every project):

```
"test": {
  "inputs": [
    "default",
    "^prod"
  ]
}
```

And projects can define their prod fileset, without having to redefine the inputs for the `test` target.

```json title="package.json"
{
  "name": "parent",
  "scripts": {
    "build": "...",
    "test": "..."
  },
  "dependencies": {...},
  "nx": {
    "namedInputs": {
      "prod": [
        "!{projectRoot}/**/*.test.js",
        "{workspacRoot}/jest.config.js"
      ]
    }
  }
}
```

In this case Nx will use the right `prod` input for each project.

### Target Defaults

Targets can depend on other targets. A common scenario is having to build dependencies of a project first before
building the project. The `dependsOn` property in `package.json` can be used to define the list of dependencies of an
individual target.

Often the same `dependsOn` configuration has to be defined for every project in the repo, and that's when
defining `targetDefaults` in `nx.json` is helpful.

```json
{
  "targetDefaults": {
    "build": {
      "dependsOn": ["^build"]
    }
  }
}
```

The configuration above is identical to adding `{"dependsOn": ["^build"]}` to every build target of every project.

Another target default you can configure is `outputs`:

```json
{
  "targetDefaults": {
    "build": {
      "outputs": ["{projectRoot}/custom-dist"]
    }
  }
}
```

{% callout type="warning" title="Nx < 14.3.4" %}
Previous versions of Nx (before 14.3.4) supported `targetDependencies` to configure dependencies in `nx.json`
. `targetDefaults` is the same mechanism but generalized to support other properties.
{% /callout %}

### CLI Options

The following command generates a new library: `nx g @nrwl/js:lib mylib`. After setting the `defaultCollection`property,
the lib is generated without mentioning the plugin name: `nx g lib mylib`.

```json
{
  "cli": {
    "defaultCollection": "@nrwl/js"
  }
}
```

### Generators

Default generator options are configured in `nx.json` as well. For instance, the following tells Nx to always
pass `--buildable=true` when creating new libraries.

```json
{
  "generators": {
    "@nrwl/js:library": {
      "buildable": true
    }
  }
}
```

### Tasks Runner Options

> A task is an invocation of a target.

Tasks runners are invoked when you run `nx test`, `nx build`, `nx run-many`, `nx affected`, and so on. The tasks runner
named "default" is used by default. Specify a different one like
this `nx run-many --target=build --all --runner=another`.

Tasks runners can accept different options. The following are the options supported
by `"nx/tasks-runners/default"` and `"@nrwl/nx-cloud"`.

| Property                | Descrtipion                                                                                |
| ----------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| cacheableOperations     | defines the list of targets/operations that are cached by Nx                                                                                |
| parallel                | defines the max number of targets ran in parallel (in older versions of Nx you had to pass `--parallel --maxParallel=3` instead of `--parallel=3`)                                                                                |
| captureStderr           | defines whether the cache captures stderr or just stdout                                                                                |
| skipNxCache             | defines whether the Nx Cache should be skipped (defaults to `false`)                                                                                |
| cacheDirectory          | defines where the local cache is stored (defaults to `node_modules/.cache/nx`)                                                                                |
| encryptionKey           | (when using `"@nrwl/nx-cloud"` only) defines an encryption key to support end-to-end encryption of your cloud cache. You may also provide an environment variable with the key `NX_CLOUD_ENCRYPTION_KEY` that contains an encryption key as its value. The Nx Cloud task runner normalizes the key length, so any length of key is acceptable |
| runtimeCacheInputs      | defines the list of commands that are run by the runner to include into the computation hash value                                                                                |
| selectivelyHashTsConfig | only hash the path mapping of the active project in the `tsconfig.base.json` (e.g., adding/removing projects doesn't affect the hash of existing projects) (defaults to `false`)                                                                                |

`runtimeCacheInputs` are set as follows:

```json
{
  "tasksRunnerOptions": {
    "default": {
      "runner": "nx/tasks-runners/default",
      "options": {
        "cacheableOperations": ["build", "lint", "test", "e2e"],
        "runtimeCacheInputs": ["node -v"]
      }
    }
  }
}
```

You can configure `parallel` in `nx.json`, but you can also pass them in the
terminal `nx run-many --target=test --parallel=5`.

## .nxignore

You may optionally add an `.nxignore` file to the root. This file is used to specify files in your workspace that should
be completely ignored by Nx.

The syntax is the same as
a [`.gitignore` file](https://git-scm.com/book/en/v2/Git-Basics-Recording-Changes-to-the-Repository#_ignoring).

**When a file is specified in the `.nxignore` file:**

1. Changes to that file are not taken into account in the `affected` calculations.
2. Even if the file is outside an app or library, `nx workspace-lint` won't warn about it.

repository: matheo/nx

repo_name: matheo/nx


text:
# festis

A really simple python client library for Workforce Telestaff.

## Getting Started

These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.

### Prerequisites

This module is designed to work with `Python 3.4+`.  `Python 2` may work, your milage may very.  The `requirements.txt` file contains the required libraries.

```
python3.4+
$pip install -r requirements.txt
```

### Optional Prerequisites

The python [requests-ntlm](https://github.com/requests/requests-ntlm) module can optionally be used to authenticate with Workforce Telestaff installations behind a NTLM Challenge-Response authorization mechanizm.

```

pip install requests_ntlm

```

### Installation

This package can be installed from github:

```
$ git clone http://github.com/porcej/festis
$ cd festis
$ python3 setup.py install
```

### Removal

```
$ pip uninstall festis
```

### Usage

#### Using this module in your application

Import the telestaff class from the festis module
```
from festis import telestaff as ts
```

Initilize a telestaff object and request the desired data

```
telestaff = ts.Telestaff(host=current_app.config['TS_SERVER'],  \
                                    t_user=current_app.config['TS_USER'], \
                                    t_pass=current_app.config['TS_PASS'], \
                                    domain=current_app.config['TS_DOMAIN'],  \
                                    d_user=current_app.config['D_USER'], \
                                    d_pass=current_app.config['D_PASS'])

telestaff.getTelestaff(kind='roster', date=date, jsonExport=True)
```

### Sample applicaitons

#### sample.py

The sample applicaiton, `sample.py` demonstrates using a911 to pretty print alert data to the screen.

```
Usage: sample.py [options]

Options:
  -h, --help                show this help message and exit
  -q, --quiet               set logging to ERROR
  -d, --debug               set logging to DEBUG
  -v, --verbose             set logging to COMM
  -a AREG, --aid=AREG       Active911 Registration ID
```

#### samplefile.py
The example applicaiton, `samplefile.py` demonstrates using a911's Active911 class to save alert messages as json files in a predefined directory.

```
Usage: samplefile.py [options]

Options:
  -h, --help            show this help message and exit
  -q, --quiet           set logging to ERROR
  -d, --debug           set logging to DEBUG
  -v, --verbose         set logging to COMM
  -a AREG, --aid=AREG   Active911 Registration ID
  -p OPATH, --path=OPATH
                        Output directory
```

## Built With

* [Anaconda Python](https://conda.io/) - The python framework
* [Beautiful Soup](https://www.crummy.com/software/BeautifulSoup/) - Screen Scraping
* [Requests](http://docs.python-requests.org/en/master/) - Request and session handling

## Contributing

Please read [CONTRIBUTING.md](https://gist.github.com/porcej/cc71497a2b455f27bca8c879731e68dc) for details on our code of conduct, and the process for submitting pull requests to us.

## Versioning

We use [SemVer](http://semver.org/) for versioning. For the versions available, see the [tags on this repository](https://github.com/porcej/a911_bridge/tags).

## Authors

* **Joseph Porcelli** - *Initial work* - [porcej](https://github.com/porcej)

See also the list of [contributors](https://github.com/porcej/a911_bridge/contributors) who participated in this project.

## License

This project is licensed under the MIT License - see the [LICENSE.md](LICENSE.md) file for details

repository: porcej/festis

gha_language: Python

repo_name: porcej/festis


text:
Generate Triangle Face Ids {#sharedfeaturefacefilter}
============

## Group (Subgroup) ##
Surface Meshing (Connectivity/Arrangement)

## Description ##
This **Filter** assigns a unique Id to each **Triangle** in a **Triangle Geometry** that represents the _unique boundary_ on which that **Triangle** resides. For example, if there were only two **Features** that shared one boundary, then the **Triangles** on that boundary would be labeled with a single unique Id. This procedure creates _unique groups_ of **Triangles**, which themselves are a set of **Features**. Thus, this **Filter** also creates a **Feature Attribute Matrux** for this new set of **Features**, and creates **Attribute Arrays** for their Ids and number of **Triangles**.

---------------

![Example Surface Mesh Coloring By Feature Face Id](featureFaceIds.png)
@image latex featureFaceIds.png "Example Surface Mesh Coloring By Feature Face Id" width=6in

---------------

## Parameters ##
None

## Required Geometry ##
Triangle

## Required Objects ##
| Kind | Default Name | Type | Component Dimensions | Description |
|------|--------------|-------------|---------|-----|
| **Face Attribute Array** | FaceLabels | int32_t | (2) | Specifies which **Features** are on either side of each **Face** |

## Created Objects ##
| Kind | Default Name | Type | Component Dimensions | Description |
|------|--------------|-------------|---------|-----|
| **Face Attribute Array** | FeatureFaceId | int32_t | (1) | Specifies to which **Feature** each **Face** belongs |
| **Attribute Matrix** | FaceFeatureData | Face Feature | N/A | Created **Feature Attribute Matrix** name  |
| **Feature Attribute Array** | FaceLabels | int32_t | (2) | Specifies which _original_ **Features** are on either side of each _new_ **Feature** |
| **Feature Attribute Array** | NumTriangles | int32_t | (1) | Number of **Triangles** in each **Feature** |

## License & Copyright ##

Please see the description file distributed with this **Plugin**

## DREAM.3D Mailing Lists ##

If you need more help with a **Filter**, please consider asking your question on the [DREAM.3D Users Google group!](https://groups.google.com/forum/?hl=en#!forum/dream3d-users)

branch_name: refs/heads/develop


text:
# Sketch Dockpreview

A Sketch plugin that lets you preview your current artboard in the Dock.

## Installation

It's really easy. Just [download Dockpreview](https://github.com/fnky/sketch-dockpreview/releases) or clone the repository and put the Dockpreview `sketchplugin` file in your plugin folder. You can rename the folder if you'd like.

## Upgrade Notice

Sketch 3.3 changed plugin system from a folder/file system to a bundle-based approach. If you still use an older version of Sketch, you can still get older Dockpreview from [Releases](https://github.com/fnky/sketch-dockpreview/releases).

Older releases aren't maintained and Dockpreview keeps pushing the way forward.

##### Sketch 3

In Sketch 3 you can reveal your plugins folder in `Plugins > Reveal Plugins Folder...`

##### Sketch from App Store

Place the plugin in `~/Library/Containers/com.bohemiancoding.sketch/Data/Library/Application Support/Sketch/Plugins`

##### Sketch from Downloads

Place the plugin in `~/Library/Application Support/Sketch/Plugins`

## Usage

- `⇧⌘D` (*Shift + Command + D*) - Preview current artboard in Dock.

To restore the icon back to the default Sketch icon, go to `Plugins > Restore Sketch icon`. If you quit Sketch, the icon will automatically restore by itself.

If you'd like to change the shortcuts, you can change the `manifest.json` file in `Dockpreview.sketchplugin/Contents/Sketch` and change the `shortcut` to your liking.

> *Note:* When the plugin updates, this will overwrite the `manifest.json` because of versioning.

## Contributing

Found a bug? Perhaps have an idea for Dockpreview, you'd like to see? [Submit an issue or pull request
](wiki/Contributing) - all your help is needed.

## License

The MIT License (MIT)

repository: imagesuren/sketch-dockpreview

repo_name: imagesuren/sketch-dockpreview


text:
# bitwallet
A Bitcoin wallet management system

1. Installation

   * git clone
   * cd dirname
   * npm install --save

2.


text:
# springboot2-async-controllers

This project is a quite simple example to show the asynchronous capabilities of Spring 5 and Spring Boot 2 release versions.

There are two different classes showing different ways of building Async Controllers:

* `rekkeb.controller.HelloController`: Shows how to build an asynchronous controller using annotations
* `rekkeb.functional.Router`: Shows how to build an asynchronous controller using WebFlux Reactive Programming model

## Getting Started

Just clone the repository and run: ``mvn clean compile``

### Prerequisites

This project has been built using **Java Version**: 1.8.0_162

And **Maven Version**: 3.5.0

## Running the tests

Just run: ``mvn clean compile test``

Tests show how to use [WebClient](https://docs.spring.io/spring/docs/current/spring-framework-reference/web-reactive.html#webflux-client) to test asynchronous controllers

## Built With

* [Maven](https://maven.apache.org/) - Dependency Management

## References

* [Web On Reactive Stack](https://docs.spring.io/spring/docs/current/spring-framework-reference/web-reactive.html#spring-webflux) - Spring 5

## License

This project is licensed under the MIT License - see the [LICENSE.md](LICENSE.md) file for details


text:
!MENU_SKIP

# `@universal-adapter`

Like adapters for power outlet, but for JavaScript.

For now, there are only adapters for server frameworks (Express, Hapi, Koa).

## Server adapters

The server adapters allow you to write server code that can work with several server frameworks.

 - Express adapter: `@universal-adapter/express`
 - Hapi adapter: `@universal-adapter/hapi`
 - Koa adapter: `@universal-adapter/koa`

### Example

We define routes `/` and `/hello/{name}` that will work with Express, Hapi, and Koa:

~~~js
!INLINE ./example/helloPlug.js
~~~

We can now use `helloPlug` with either Express, Hapi, or Koa:

~~~js
!INLINE ./example/express
~~~
~~~js
!INLINE ./example/hapi
~~~
~~~js
!INLINE ./example/koa
~~~

repository: brillout/universal-adapter

repo_name: brillout/universal-adapter


text:
---
layout: layout.pug
navigationTitle: Fluentbit
title: Fluentbit
menuWeight: 11
excerpt: FluentBit is the Kommander choice of open-source log collection and forwarding tool.
beta: false
enterprise: false
---

[FluentBit](https://fluentbit.io/) is the DKP choice of open-source log collection and forwarding tool.

## Audit Log Collection

[Auditing](https://kubernetes.io/docs/tasks/debug-application-cluster/audit/) in Kubernetes provides a way to chronologically document the actions taken on a cluster. On Kommander, by default, audit logs are collected and stored for quick indexing. Viewing and accessing can be done via the Grafana logging UI.

## Related information

For information on related topics or procedures, refer to the following:

- [Logging](..)

repository: mesosphere/dcos-docs-site

gha_language: SCSS

repo_name: mesosphere/dcos-docs-site


text:
## Preparing 5-Node Kubernetes Cluster

To get started with Kubernetes, follow the below steps:

-  Open https://play-with-k8s.com on your browser

![Image](https://github.com/collabnix/dockerlabs/blob/master/kubernetes/workshop/img/pwk1.png)

Click on Add Instances to setup first k8s node cluster

## Cloning the Repository

```
git clone https://github.com/collabnix/dockerlabs/
cd dockerlabs/kubernetes/install

```

## Bootstrapping the First Node Cluster

```
sh bootstrap.sh
```

## Adding New K8s Cluster Node

Click on Add Instances to setup first k8s node cluster

Wait for 1 minute time till it gets completed.

Copy the command starting with ```kubeadm join ....```. We will need it to be run on the worker node.

## Setting up Worker Node

Click on "Add New Instance" and paste the last kubeadm command on this fresh new worker node.

```
[node2 ~]$ kubeadm join --token 4f924f.14eb7618a20d2ece <IP_ADDRESS>:6443 --discovery-token-ca-cert-hash  sha256:a5c25aa4573e06a0c11b11df23c8f85c95bae36cbb07d5e7879d9341a3ec67b3```
```

You will see the below output:

```
[kubeadm] WARNING: kubeadm is in beta, please do not use it for production clusters.
[preflight] Skipping pre-flight checks[discovery] Trying to connect to API Server "<IP_ADDRESS>:6443"
[discovery] Created cluster-info discovery client, requesting info from "https://<IP_ADDRESS>:6443"
[discovery] Requesting info from "https://<IP_ADDRESS>:6443" again to validate TLS against the pinned public key
[discovery] Cluster info signature and contents are valid and TLS certificate validates against pinned roots, will use API Server "<IP_ADDRESS>:6443"[discovery] Successfully established connection with API Server "<IP_ADDRESS>:6443"
[bootstrap] Detected server version: v1.8.15
[bootstrap] The server supports the Certificates API (certificates.k8s.io/v1beta1)
Node join complete:
* Certificate signing request sent to master and response
  received.
* Kubelet informed of new secure connection details.

repository: collabnix/dockerlabs

gha_language: PHP

repo_name: collabnix/dockerlabs


text:
# Laboratories

This repository contains (and is updated each university year):

 * content of each laboratory with detailed explanations, examples and exercises
 * media, such as photos or diagrams, that are used to better portrait examples as well as sources (where need-be - e.g. the UML diagrams can be exported to XML from [draw.io](https://www.draw.io/))
 * skeletons for laboratories which require a starting point

## Repository folder structure

The structure for a current laboratory is as follows:
```
laboratoare
|
|	--->	lab_name  [1]
|		|	--->	skel  [2]
|		|	--->	media [3]
|		|		|	---> image-source [4]
|		|	lab_name  [5]
|	--->	...
|	--->	...
```

The structure for an old or deprecated laboratory is as follows:
```
old
|
|	--->	old_lab_name  [1]
|		|	--->	skel  [2]
|		|	--->	media [3]
|		|		|	---> image-source [4]
|		|	old_lab_name  [5]
|	--->	...
|	--->	...
```

##### [1] - folder with the laboratory name and contents
##### [2] - folder with the skeleton code [if need-be]
##### [3] - folder with images and diagrams [if need-be]
##### [4] - folder with sources of the images/diagrams [if need-be]
##### [5] - file with laboratory details and exercises -- docuwiki code (**must** be the same as the folder name)

## Contributing

If you are interested in fixing issues, detailing laboratory content or just want to lend a helping hand,
please see the document [How to Contribute](CONTRIBUTING.md), which covers the following:

* [Coding Guidelines](CONTRIBUTING.md#coding-guidelines)
* [Submitting pull requests](CONTRIBUTING.md#pull-requests)

This organization has adopted the [Ethics regulation](http://wiki.cs.pub.ro/_media/studenti/licenta/regulament-comisie-de-etica-upb.pdf) and the [Code of Conduct for Students from the Faculty of Automation and Computers](http://wiki.cs.pub.ro/_media/studenti/licenta/cod-conduita-studenti-acs-.pdf). Failure to comply with or violate the rules set out in any of these documents will result in the sanctions imposed by UPB's internal regulations, such as reprimand, written warning, or expulsion from the University POLITEHNICA of Bucharest.

## Feedback

* Ask a question on [the Moodle instance of our university](http://cs.curs.pub.ro/).
* Request a new feature on [GitHub](CONTRIBUTING.md).
* File a bug in [GitHub Issues](https://github.com/oop-pub/laboratoare/issues).

## Related repositories

* [Homeworks](https://github.com/oop-pub/teme) -- content related to assignmnets
* [Wiki](https://github.com/oop-pub/wiki) - content from the [docuwiki instance](http://elf.cs.pub.ro/poo/)

## License

Licensed under the [MIT](LICENSE) License.

repository: Petruc-Rares/University

repo_name: Petruc-Rares/University


text:
---
title: "Data Wrangling with Pandas"
date: 2020-06-01
---

## Multi-index column headers
Having multi-index columns restricts what you can do in Pandas. For instance, we can't use pd.query, and writing functions for pd.apply, pd.groupby becomes complicated. Moving forward I would opt to temporarily join the rows with an appropriate delimiter, and expand when exporting. Or just select one row as header when possible.

## Exporting multi-index columns to CSV
I've encountered an occasion where Pandas dumped tuples instead of two/multiple rows of headers. Rounding before saving (df.round().to_csv()) somehow fixes it.

Code snippets and other tips to follow.


text:
# SPAN Rotator
Slide rotator for SPAN NYC and London 2015 conferences

**[Live link](http://romannurik.github.io/SPANRotator/)**

![Demo](https://raw.githubusercontent.com/romannurik/SPANRotator/master/art/demo.gif)

repository: romannurik/SPANRotator

repo_name: romannurik/SPANRotator


text:
# 228. Summary Ranges

Difficulty: Medium

https://leetcode.com/problems/summary-ranges/

Given a sorted integer array without duplicates, return the summary of its ranges.

**Example 1:**
```
Input:  [0,1,2,4,5,7]
Output: ["0->2","4->5","7"]
Explanation: 0,1,2 form a continuous range; 4,5 form a continuous range.
```

**Example 2:**
```
Input:  [0,2,3,4,6,8,9]
Output: ["0","2->4","6","8->9"]
Explanation: 2,3,4 form a continuous range; 8,9 form a continuous range.
```

repository: jiadaizhao/LeetCode

repo_name: jiadaizhao/LeetCode


text:
# S3 Account Search
This tool lets you find the account id an S3 bucket belongs too.

For this to work you need to have at least one of these permissions:

- Permission to download a known file from the bucket (`s3:getObject`).
- Permission to list the contents of the bucket (`s3:ListBucket`).

Additionally, you will need a role that you can assume with (one of) these permissions on the bucket
you're examining

Some more background can be found on the [Cloudar Blog](https://www.cloudar.be/awsblog/finding-the-accountid-of-any-public-s3-bucket/)

## Installation
This package is available on pypi, you can for example use on of these commands (pipx is recommended)
```shell
pipx install s3-account-search
pip install s3-account-search
```

## Usage Examples
```shell
# with a bucket
s3-account-search arn:aws:iam::123456789012:role/s3_read s3://my-bucket

# with an object
s3-account-search arn:aws:iam::123456789012:role/s3_read s3://my-bucket/path/to/object.ext

# You can also leave out the s3://
s3-account-search arn:aws:iam::123456789012:role/s3_read my-bucket

# Or start from a specified source profile
s3-account-search --profile source_profile arn:aws:iam::123456789012:role/s3_read s3://my-bucket
```

## How this works
There is an IAM policy condition `s3:ResourceAccount`, that is meant to be used to give access to S3
in specified (set of) account(s), but also supports wildcards. By constructing the right patterns,
and seeing which  ones will lead to a Deny or an Allow, we can determine the account id by
discovering it one digit at a time.

1. We verify that we can access the object or bucket with the provided role
2. We assume the same role again, but this time add a policy that restricts our access to S3 buckets
   that exist in an account starting with `0`. If our access is allowed we know that the account id
   has to start with `0`. If the request is denied, we try again with `1` as the first digit. We keep
   incrementing until our request is allowed, and we find the first digit
3. We repeat this process for every digit. Using the already discovered digits as a prefix. E.g. if
   the first digit was `8`, we test account ids starting with `80`, `81`, `82`, etc.

## Development
We use poetry to manage this project

1. Clone this repository
2. Run `poetry install`
3. Activate the virtualenvironment with `poetry shell` (you can also use `poetry run $command`)

### Releasing a new version to pypi
1. Edit pyproject.toml to update the version number
2. Commit the version number bump
3. Run `poetry publish --build`
4. Push to GitHub
5. Create a new release in GitHub

## Possible improvements
- Instead of checking one digit at a time, we could use a binary search-like algorithm. Eg. the
  following condition is equivalent to `s3:ResourceAccount <<PHONE_NUMBER>00`
  ```json
  "Condition": {
    "StringLike": {"s3:ResourceAccount": [
      "0*", "1*", "2*", "3*", "4*",
    ]},
  },
   ```
- Similarly, there is a speed improvement possible by checking multiple digits per position in
  parallel (There is a small risk of being rate limited by STS when using this approach)

In practice this tool should be fast enough in most cases.


text:
# GPD-bar-chart
A bar chart made with D3.js for national GDP of the USA

## This was done as a project for [Free Code Camp](https://www.freecodecamp.org)
This is the first project from the Data Visualization Projects of Free Code Camp
You need to build a bar chart for the US GDP-_Gross Domestic  Product_ using a preset dataset supplied by Free Code Camp here [https://raw.githubusercontent.com/freeCodeCamp/ProjectReferenceData/master/GDP-data.json](https://raw.githubusercontent.com/freeCodeCamp/ProjectReferenceData/master/GDP-data.json)

**Here are a list of the User Stories required**

* User Story #1: My chart should have a title with a corresponding `id="title"`
* User Story #2: My chart should have a g element x-axis with a corresponding `id="x-axis"`.
* User Story #3: My chart should have a g element y-axis with a corresponding `id="y-axis"`.
* User Story #4: Both axes should contain multiple tick labels, each with the corresponding `class="tick"`.
* User Story #5: My chart should have a `rect` element for each data point with a corresponding `class="bar"` displaying the data.
* User Story #6: Each bar should have the properties `data-date` and `data-gdp` containing date and GDP values.
* User Story #7: The bar elements' `data-date` properties should match the order of the provided data.
* User Story #8: The bar elements' `data-gdp` properties should match the order of the provided data.
* User Story #9: Each bar element's height should accurately represent the data's corresponding GDP.
* User Story #10: The `data-date` attribute and its corresponding bar element should align with the corresponding value on the x-axis.
* User Story #11: The `data-gdp` attribute and its corresponding bar element should align with the corresponding value on the y-axis.
* User Story #12: I can mouse over an area and see a tooltip with a corresponding `id="tooltip"` which displays more information about the area.
* User Story #13: My tooltip should have a `data-date` property that corresponds to the `data-date` of the active area.

### Link to the Testing Suite Script
Here's the link to the testing script provided by Free Code Camp
[https://cdn.freecodecamp.org/testable-projects-fcc/v1/bundle.js](https://cdn.freecodecamp.org/testable-projects-fcc/v1/bundle.js)

#### Contact Information
Thanks for taking a look at my project 😄
If you have any questions, please feel free to contact me by creating an issue here
Or on Twitter at [@PeteCapeCod](https://www.twitter.com/PeteCapeCod) 🐦 :+1:

repository: petercr/GDP-bar-chart

repo_name: petercr/GDP-bar-chart


text:
# Compute ETags and MD5s
The tool provides methods to calculate ETags for Objects on AWS S3, and also md5s, on local objects. It also allows comparing ETags or md5s to check the integrity of files, both locally and on AWS S3, given a list of files and their calculated ETags.
## Installation
```pip install compETAG```
## Usage
The following example will compute ETags for local files with the same chunk size used by AWS on S3:

```compute_etags -i <file1> <file2> .... -m etag -s 8MB -o out.txt```

Chunk size can be set to any desired value:

```compute_etags -i <file1> <file2> .... -m etag -s 1GB```

With mode fixed at `md5`, the resulting calculation will be md5 hashes:

```compute_etags -i <file1> <file2> .... -m md5```

To retrieve ETags from objects on AWS S3, setting mode to `s3uri` will redirect the tool to AWS S3, provided a bucket/s, key/s, and pattern/s (optional):

```compute_etags -m s3uri -b <bucket1> <bucket2> .. -k <key1> <key2> .. -p <pattern1> <pattern2> .. ```

To check the integrity of local files or AWS S3 objects, the following will calculate or retrieve ETags or md5s on the list of files provided in a text file, and compare the results to the provided hashings. Each row in the input text file represents a pair of ETag/md5 hash and a file name.

* Checking ETags of local files:

    ```compute_etags -c <input.txt> -m etags```

* Checking md5s of local files:

    ```compute_etags -c <input.txt> -m md5```

* Checking ETags of AWS S3 objects:

    ```compute_etags -c <input.txt> -m s3uri -b <bucket1> <bucket2> .. -k <key1> <key2> .. ```

repository: awnimo/compETAG

repo_name: awnimo/compETAG


text:
# SfsAdmin Documentation

[![Build Status](https://travis-ci.org/sfstarter/SfsAdminBundle.svg?branch=develop)](https://travis-ci.org/sfstarter/SfsAdminBundle)
[![SensioLabsInsight](https://insight.sensiolabs.com/projects/beb5d2ee-56d8-4801-899e-1a48afac4f46/mini.png)](https://insight.sensiolabs.com/projects/beb5d2ee-56d8-4801-899e-1a48afac4f46)

Administration bundle for Symfony2

## Overview
SfsAdmin is an entity-oriented back-office generator. It allows you to generate fastly a CRUD system for your whole website.

- Deploy easily your CRUD system for every entities of your project, with few configuration
- Doctrine ORM oriented only
- FOSUserBundle usage (required for now, should be removed in next version to allow the usage of any security system)
- Usage of native Symfony2 FormTypes for your create/update pages
- Filter mechanisms inside the listing pages: [LexikFormFilterBundle](https://github.com/lexik/LexikFormFilterBundle) does a great job for it, so it is natively supported
- Export system in JSON & CSV
- Add custom pages easily
- Only few dependencies

## Documentation

The online documentation is available in http://sfsadmin.solidlynx.com

## License
This project is under the terms of the MIT License (MIT)

repository: sfstarter/SfsAdminBundle

repo_name: sfstarter/SfsAdminBundle


text:
# Deployment

## Requirements

- Google Cloud SDK

  Instructions for installing and initializing the Google Cloud SDK are available at https://cloud.google.com/sdk/.

- Docker

  Instructions for installing Docker are available at https://docs.docker.com/get-docker/.

  To allow pushing images to GCR, register `gcloud` as a Docker credential helper with `gcloud auth configure-docker`.

- Python dependencies

  `pip install -r deploy/deployctl/requirements.txt`

## Configuration

Select a GCP project and zone to use.

```
./deployctl config set project $PROJECT
./deployctl config set zone $ZONE
```

To see other available configuration options, run `./deployctl config list`.

## Creating a new environment

### Configure project

- [Create a Cloud Monitoring workspace for the project](https://cloud.google.com/monitoring/workspaces/guide#single-project-ws).

### Create GCP resources

```
./deployctl setup
```

### Deploy on GKE

#### Prepare data

See [data-pipeline/README.md](../data-pipeline/README.md) for information on running data preparation pipelines.

#### Create Elasticsearch cluster

The setup step installs the [Elastic Cloud on Kubernetes (ECK)](https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-overview.html) operator.

To check if the operator is ready, run `kubectl -n elastic-system get statefulset.apps/elastic-operator`.

To create an Elasticsearch cluster, run `./deployctl elasticsearch apply`.

After creating the cluster, store the password in a secret so that Dataproc jobs can access it.

#### Create browser deployment

- Build Docker images and push to GCR.

  ```
  ./deployctl images build --push
  ```

- Create deployment manifests.

  ```
  ./deployctl deployments create
  ```

- Apply deployment.

  ```
  ./deployctl deployments apply <deployment-name>
  ```

#### Create reads deployment

- Build Docker images and push to GCR.

  ```
  ./deployctl reads-images build --push
  ```

- Create deployment manifests.

  ```
  ./deployctl reads-deployments create
  ```

- Apply deployment.

  ```
  ./deployctl reads-deployments apply <deployment-name>
  ```

#### Create blog deployment

- Create secrets.

  Fill in values from GitHub application.

  ```
  cat <<EOF > oauth-secrets.env
  client-id=
  client-secret=
  EOF
  ```

  ```
  kubectl create secret generic blog-oauth-secrets --from-env-file oauth-secrets.env
  ```

- Build Docker images and push to GCR.

  ```
  ./deployctl blog-images build --push
  ```

- Create deployment manifests.

  ```
  ./deployctl blog-deployment update
  ```

- Apply deployment.

  ```
  ./deployctl blog-deployment apply
  ```

#### Create ingress

- Create NodePort services for browser and reads, certificate, and Ingress.

  The SSL certificate can only be provisioned after DNS records for gnomad.broadinstitute.org are configured to
  point to the load balancer's IP address.

  See https://cloud.google.com/kubernetes-engine/docs/how-to/managed-certs for more information.

  ```
  ./deployctl production apply-ingress
  ```

## Updating an existing environment

### Updating browser deployment

- Follow steps above to create a new browser deployment.

- Switch over to the new deployment. This updates the `gnomad-browser` service's selector to point to the new deployment.

  ```
  ./deployctl production update --browser-deployment <new-deployment-name>
  ```

- Delete the old deployment.

  ```
  ./deployctl deployments delete <old-deployment-name>
  ```

### Updating reads deployment

- Follow steps above to create a new reads deployment.

- Switch over to the new deployment. This updates the `gnomad-reads` service's selector to point to the new deployment.

  ```
  ./deployctl production update --reads-deployment <new-deployment-name>
  ```

- Delete the old deployment.

  ```
  ./deployctl reads-deployments delete <old-deployment-name>
  ```

repository: c-BIG/gnomad-browser

repo_name: c-BIG/gnomad-browser


text:
# okcupidon
[![Codacy Badge](https://app.codacy.com/project/badge/Grade/2aefdc3b25e24cbf902abaf1013f22ee)](https://www.codacy.com/manual/Maxence-L/okcupidon/dashboard?utm_source=github.com&utm_medium=referral&utm_content=Maxence-L/okcupidon&utm_campaign=Badge_Grade)

An python scraper for Okcupid.

This scraper is still in development but works nonetheless already.

In your desired folder, you can import it the following way :

```bash
git clone https://github.com/Maxence-L/okcupidon
```

repository: usbku/okcupidon

repo_name: usbku/okcupidon


text:
---
layout: page
title: Misc stuff
---

Wonder how a PhD defense in the Netherlands looks like? [Here is mine](/defense).

I once entered a short story contest. [Here's my contribution](/misc/Shutdown.pdf) (in Italian). Spoiler alert: I did not win.

--

Graphic Design
==============

**Disclaimer:** I am **not** a trained graphic designer, by any
  means. Every work of design that is meant for publication should
  **always** be realized by professionals.

That said, this is a gallery of works made by me, mostly logos. I like
working on logos because it involves a good deal of conceptualization,
while keeping the actual illustration work to a manageable intensity.
The bare minimum material to ship a logo should include at least an
icon version, a monochromatic version, and a version for dark
background.

Some of these were made in collaboration with [Sara
Barcena](http://www.sarabarcena.com).

Logos
-----

![DeKO](deko.png)

DeKO (Default Knowledge about Objects) is a large database of common
knowledge about objects. The knowledge has been collected as part of
the work of the [ALOOF project](https://project.inria.fr/aloof/) and
it comes from several sources and techniques.

The shapes encased in the letters are highly abstract representations
of a knife and a glass of water.

[DeKO page](http://dekokg.org/)

- - -

![CREOL](creol.png)

Contextual Representation of Objects and Events in Language (CREOL
2017) is the first edition of an international venue focussed on
investigating the relationship between representations of objects and
events in ontological and linguistic resources, and their
interpretation in their context of occurrence.

The logo takes inspiration by a typical example used in the field,
that of an orange observed as food as opposed to as a child's toy.

[CREOL 2017 workshop](http://creol2017.di.unito.it/)

- - -

![WASABI](wasabi.png)

WASABI is a research project that aims at enriching the experience of
music listeners by providing additional information such as biography
or albums by the same artist, and offer suggestions to listen to other
artists or songs "similar". The technology involved in the project
includes the automatic analysis of music and lyrics, as well as
linking and reasoning on the Semantic Web.

The W of the logo resembles a waveform, while the color green is a
reference to the popular japanese sauce by the same name.

[WASABI project page](http://www.agence-nationale-recherche.fr/?Project=ANR-16-CE23-0017)

- - -

![KNEWS](knews.png)

KNEWS (Knowledge Extraction With Semantics) is a software that bridges
semantic parsing, word sense disambiguation, and entity linking to
produce a unified, LOD-compliant abstract representation of meaning.

Here I used a classic Bodoni font with some kerning adjustment that
playes with the serifs.

[KNEWS source code](https://github.com/valeriobasile/learningbyreading)

[KNEWS demo](http://gingerbeard.alwaysdata.net/knews/)

- - -

![JURIX](jurix.png)

The 29th International Conference on Legal Knowledge and Information Systems.

The symbol under the word Jurix is reminiscent of a [lambda
calculus](https://en.wikipedia.org/wiki/Lambda_calculus) expression,
with the lambda (λ) replaced by a scale, a typical symbol for
law and justice. The touch of color on the year tries to replicate the
beautiful blue of the Riviera seaside (venue of the conference).

[website](http://jurix2016.unice.fr/)

- - -

![Centre for Digital Humanities](cdh.png)

The Groningen Centre for Digital Humanities provides a vibrant
research climate for researchers working at the intersections of
computer science and the humanities. (from the website)

The logo uses a classical design and warm colors (including the RUG's
trademark red), while switching to a terminal-type font for the
initials C, D and H, for a subtle integration of digital and
humanities feel.

[website](http://www.rug.nl/research/research-let/expertisecentra/centre-for-digital-humanities/?lang=en)

- - -

![Open Game Benchmarks](ogb.png)

A platform to share benchmarks of videogames run on different
hardware configurations and operating systems.

The logo mixes a gamepad (a staple of gaming) with a stethoscope,
a typical medical examination tool.

[website](http://www.opengamebenchmarks.org/)

- - -

![PDRT Sandbox](pdrtsandbox.png)

Haskell library that implements Discourse Representation Theory (DRT),
and its extension Projective Discourse Representation Theory (PDRT).

The logo is simply a pictorial representation of a physical sandbox.

[website](http://hbrouwer.github.io/pdrt-sandbox/)

- - -

![Groningen Meaning Bank](gmb.png)

A free semantically annotated corpus that anyone can edit.

The logo hints at the logical formulas used in the project with the
logical symbols ∀ (universal quantifier) and ∃ (existential
quantifier). The font is of the typewriter type, which fit the idea of
a corpus of *written text*. The circle is a symbol of completeness
(even though it's open in the logo). Orange is the color of the
Netherlands.

[website](https://gmb.let.rug.nl)

- - -

![Parallel Meaning Bank](pmb.png)

A free semantically annotated **parallel** corpus (English, Dutch,
German, and Italian).

Derived from the GMB logo, the cirle is modified to symbolize the
parallelism (parallel bands, that was easy). The color is the inverse
of the GMB logo.

[website](https://pmb.let.rug.nl)

- - -

![TWITA](twita.png)

Collection of tweets identified as being written in the Italian
langauge.

The logo is inspired by the Twitter fonts and the colors hints at the
Italian flag.

[website](/twita/)

- - -

![Produce](produce.png)

Produce is a Python-powered automation tool geared towards management
of processes that deal with many files.

This logo plays on the
[homography](https://en.wikipedia.org/wiki/Homograph) of *produce* as
verb (create or manufacture) and *produce* as a noun (fresh fruits and
vegetable grown for the market). While the intended meaning of the
software is the former, the logo contains a stylized tomato.

[github page](https://github.com/texttheater/produce)

- - -

![Elephant logo](elephant.png)

Word and sentence boundary detection software (a *tokenizer*, that
is), based on supervised statistical methods.

The name of the software refers to the [elephant in the room
metaphor](https://en.wikipedia.org/wiki/Elephant_in_the_room). Accordingly,
the logo includes an elephant head.

[website](http://gmb.let.rug.nl/elephant)

- - -

![NLDB logo](nldb.png)

International conference on Applications of Natural Language
Processing to Information Systems.

The color scheme matches the one of the [University of
Groningen](http://www.rug.nl/), where the event was hosted. This logo
ended up on the conference bags as well.

[website](http://www.let.rug.nl/nldb12/home.php)
- - -

![Socialpros logo](socialpros.png)

Socialpros (Social Project Studio) is a startup focused on social
research software development. It somehow lose momentum.

The logo contains a representation of a network, a formalism to
represent many important phenomena in social sciences. It is also
shaped like a rising sun, as socialpros is a *new* company on
the horizon.

[website](http://socialpros.it)

- - -

Posters
-------

Posters for the [CLCG
Colloquium](http://www.rug.nl/research/clcg/about-the-institute/events/colloquia/)
series:

[![CLCG Colloquium Poster Minematsu](posters/minematsu.png)](posters/minematsu.pdf)
[![CLCG Colloquium Poster Kaiser](posters/kaiser.png)](posters/kaiser.pdf)
[![CLCG Colloquium Poster Shear](posters/shear.png)](posters/shear.pdf)
[![CLCG Colloquium Poster Clark](posters/clark.png)](posters/clark.pdf)

CLCG [Linguistic
Lunch](http://www.rug.nl/research/clcg/about-the-institute/events/linglunch/linguistics-lunches)
(just one example):

[![CLCG Linguistic Lunch Poster](posters/lunch.png)](posters/lunch.pdf)

The posters for conferences and workshops are in the
[presentations](/presentations/) page.