text:
# react modal play

Issues relating to [react refs](https://facebook.github.io/react/docs/more-about-refs.html)

## unmount issue

### Reproduction:

* click show modal
* click close child modal

### Result:

```javascript
Uncaught TypeError: node.removeAttribute is not a function
```

### Problem:

```javascript
var setMountNode = function setMountNode(ref) {
    return _this.mountNode = !ref || ref.getMountNode();
};
```

setMountNode is called with null and returns a boolean which doesn't work so well with ```node.removeAttribute('aria-hidden');```

### Potential Fix:

```javascript
var setMountNode = function setMountNode(ref) {
    if(ref && ref.getMountNode) {
        _this.mountNode = ref.getMountNode();
    }
};
```

## ref issue

### Reproduction:

* click show modal
* click show grand child

### Result:

```
ReactRef.detachRefs(internalInstance, prevElement);
```

this code is unnecessarily run

### Potential Fix:

move setMountNode to the class instance so the refs are the same

repository: craigbilner/react-modal-play

repo_name: craigbilner/react-modal-play


text:
---
title: Blog roundup, week of October 13
date: 2014-10-20 10:31:53
author: rbowen
---

Here's the blog posts that came out of the RDO community last week.

If you're writing about RDO, or about OpenStack on CentOS, Fedora or RHEL, and you're not on my list, please let me know!

**Who can sign for what?** by Adam Young

> In my last post, I discussed how to extract the signing information out of a token. But just because the signature on a document is valid does not mean that the user who signed it was authorized to do so. How can we got from a signature to validating a token? Can we use that same mechanism to sign other OpenStack messages?

... More at http://tm3.org/blog42

**LinuxCon/KVMForum/CloudOpen Eu 2014** by Kashyap Chamarthy

> While the Linux Foundation’s colocated events (LinuxCon/KVMForum/CloudOpen, Plumbers and a bunch of others) are still in progress (Düsseldorf, Germany), thought I’d quickly write a note here.

... More at http://tm3.org/blog43

**OpenStack Instance HA Proposal** by Russell Bryant

> In a perfect world, every workload that runs on OpenStack would be a cloud native application that is horizontally scalable and fault tolerant to anything that may cause a VM to go down.  However, the reality is quite different.

... More at http://tm3.org/blog44

license: MIT

repository: gbraad/redhat-openstack-website

branch_name: refs/heads/master

extension: md

gha_language: HTML

gha_license_id: NOASSERTION

license_type: permissive

repo_name: gbraad/redhat-openstack-website


text:
1

# TAG Teleconference

2

#### 5-7 June 2023

3

4

---

5

6

## Agenda:

7

8

### Breakout A (Europe / US) - [2023-06-05](https://www.timeanddate.com/worldclock/converter.html?iso=20230605T160000&p1=224&p2=43&p3=136&p4=195&p5=26&p6=33&p7=248&p8=235)

9

10

* [Classes (WebIDL interfaces) should only be used when you have both data and behavior](https://github.com/w3ctag/design-principles/issues/11) - @cynthia, @LeaVerou, @atanassov

11

* [New principle: Guidance on when to use a child element vs an attribute](https://github.com/w3ctag/design-principles/issues/270) - @hober, @LeaVerou

12

* [Guidance about which state properties should be reflected as HTML attributes](https://github.com/w3ctag/design-principles/issues/289) - @hober, @LeaVerou, @plinss

13

* PR [New text re: balancing concerns between interoperability and implementability](https://github.com/w3ctag/design-principles/pull/290)

14

* PR [First pass on backwards compatibility principle](https://github.com/w3ctag/design-principles/pull/354)

15

* [New principle: Discourage overloading (in HTML)](https://github.com/w3ctag/design-principles/issues/370) - @hober

16

* [New principle: Guidance on options dictionaries and default values](https://github.com/w3ctag/design-principles/issues/391) - @LeaVerou

17

* PR [First pass at #11, lots of TBDs](https://github.com/w3ctag/design-principles/pull/403)

18

* [Web platform features that augment HTML elements en masse](https://github.com/w3ctag/design-principles/issues/423) - @LeaVerou

19

* [New principle: Avoid adding (non-constructor) functions to the global scope](https://github.com/w3ctag/design-principles/issues/426)

20

* PR [Make 6.1 more inclusive of non-Web JS APIs](https://github.com/w3ctag/design-principles/pull/435)

21

* PR [Fix link to live-vs-static](https://github.com/w3ctag/design-principles/pull/439)

22

* PR [Give more guidance about how to monkeypatch well.](https://github.com/w3ctag/design-principles/pull/441)

23

24

25

### Breakout C (APAC / Europe) - [2023-06-06](https://www.timeanddate.com/worldclock/converter.html?iso=20230606T070000&p1=224&p2=43&p3=136&p4=195&p5=26&p6=33&p7=248&p8=235)

26

27

* [General principle around time measurement units/formats for various domains (JS, HTTP, HTML, etc)?](https://github.com/w3ctag/design-principles/issues/344) - @cynthia, @torgo

28

* PR [Restrictions](https://github.com/w3ctag/design-principles/pull/363)

29

* [New principle: Naming of factory methods](https://github.com/w3ctag/design-principles/issues/378) - @cynthia

30

* PR [New principle: Identity on the web](https://github.com/w3ctag/design-principles/pull/396)

31

* [New principle: Data Minimization](https://github.com/w3ctag/design-principles/issues/399) - @torgo

32

* [Request for design principle clarification: Warn explicitly against getters throwing exceptions](https://github.com/w3ctag/design-principles/issues/400)

33

* PR [Warn against getter throwing exception since it is a side effect](https://github.com/w3ctag/design-principles/pull/408)

34

35

### Plenary Session - [2023-06-07](https://www.timeanddate.com/worldclock/converter.html?iso=20230607T150000&p1=224&p2=43&p3=136&p4=195&p5=26&p6=33&p7=248&p8=235)

36

37

* How are we doing on this: [[Meta] Tackling design problems earlier than design review / A Q&A section for API design](https://github.com/w3ctag/design-principles/issues/319)

38

* Likewise: PR [Start developer version](https://github.com/w3ctag/design-principles/pull/386)

39

40

* Breakout Rollup

41

* [Issue Triage](https://github.com/w3ctag/design-reviews/issues?q=is%3Aissue+is%3Aopen+label%3A%22Progress%3A+untriaged%22)

42

43

-----

44

45

46

## Breakout A

47

48

Present: Peter, Amy, Tess, Lea, Yves, Rossen

49

50

Regrets: Dan

51

52

53

### [Classes (WebIDL interfaces) should only be used when you have both data and behavior](https://github.com/w3ctag/design-principles/issues/11) - @cynthia, @LeaVerou, @atanassov

54

55

PR [First pass at #11, lots of TBDs](https://github.com/w3ctag/design-principles/pull/403)

56

57

Lea: discussed at f2f. We got some TC39 input. PR 403 is way outdated.

58

59

Peter: can we close this, or use it as a starting point?

60

61

Lea: closing it.. we've discussed this extensively with Sangwhan in the meeting and it seems there is something to tweak the principles, but there's way more nuance than just don't have classes when you have both data and behaviour. There are a [bunch of ideas](https://github.com/w3ctag/design-principles/issues/11#issuecomment-1515585583) .. and some responses from TC39 people. Converting between objects and data-centric classes should be simple. Having properties on the APIs classes are associated with, needs further discussion.

62

63

Tess: something Anne and Dominic didn't agree with?

64

65

Lea: ..namespacing. Anything here we have consensus on that we could write?

66

67

Peter: I don't disagree with any of it. Comment about math.. doesn't seem to be a problem, but still worth documenting so it never becomes a problem.

68

69

Lea: fine with that. Pushback in the past about documenting principles that haven't come up as problems in reviews or apis.

70

71

Peter: lots of things that haven't been issues because everybody knows not to do this, and that should be documented. Common knowledge like that can get lost; documenting this stuff is our job.

72

73

Lea: some fluctuation around this if tc39 is discussing.. and about native modules that didn't really go anywhere that seems related. If we are going to document this I'd probably deprioritise it compared to other things.

74

75

Peter: we can refer to tc39 documentation

76

77

Lea: they don't have principles, but discussions about starting something

78

79

Peter: guidence .. as long as it's written down somewhere. Action to write a new PR?

TAG Teleconference
5-7 June 2023
Agenda:
Breakout A (Europe / US) - 2023-06-05

    Classes (WebIDL interfaces) should only be used when you have both data and behavior - @cynthia, @LeaVerou, @atanassov
    New principle: Guidance on when to use a child element vs an attribute - @hober, @LeaVerou
    Guidance about which state properties should be reflected as HTML attributes - @hober, @LeaVerou, @plinss
    PR New text re: balancing concerns between interoperability and implementability
    PR First pass on backwards compatibility principle
    New principle: Discourage overloading (in HTML) - @hober
    New principle: Guidance on options dictionaries and default values - @LeaVerou
    PR First pass at #11, lots of TBDs
    Web platform features that augment HTML elements en masse - @LeaVerou
    New principle: Avoid adding (non-constructor) functions to the global scope
    PR Make 6.1 more inclusive of non-Web JS APIs
    PR Fix link to live-vs-static
    PR Give more guidance about how to monkeypatch well.

Breakout C (APAC / Europe) - 2023-06-06

    General principle around time measurement units/formats for various domains (JS, HTTP, HTML, etc)? - @cynthia, @torgo
    PR Restrictions
    New principle: Naming of factory methods - @cynthia
    PR New principle: Identity on the web
    New principle: Data Minimization - @torgo
    Request for design principle clarification: Warn explicitly against getters throwing exceptions
    PR Warn against getter throwing exception since it is a side effect

Plenary Session - 2023-06-07

    How are we doing on this: [Meta] Tackling design problems earlier than design review / A Q&A section for API design

    Likewise: PR Start developer version

    Breakout Rollup

    Issue Triage

Breakout A

Present: Peter, Amy, Tess, Lea, Yves, Rossen

Regrets: Dan
Classes (WebIDL interfaces) should only be used when you have both data and behavior - @cynthia, @LeaVerou, @atanassov

PR First pass at #11, lots of TBDs

Lea: discussed at f2f. We got some TC39 input. PR 403 is way outdated.

Peter: can we close this, or use it as a starting point?

Lea: closing it.. we've discussed this extensively with Sangwhan in the meeting and it seems there is something to tweak the principles, but there's way more nuance than just don't have classes when you have both data and behaviour.  Converting between objects and data-centric classes should be simple. Having properties on the APIs classes are associated with, needs further discussion.

Tess: something Anne and Dominic didn't agree with?

Lea: ..namespacing. Anything here we have consensus on that we could write?

Peter: I don't disagree with any of it. Comment about math.. doesn't seem to be a problem, but still worth documenting so it never becomes a problem.

Lea: fine with that. Pushback in the past about documenting principles that haven't come up as problems in reviews or apis.

Peter: lots of things that haven't been issues because everybody knows not to do this, and that should be documented. Common knowledge like that can get lost; documenting this stuff is our job.

Lea: some fluctuation around this if tc39 is discussing.. and about native modules that didn't really go anywhere that seems related. If we are going to document this I'd probably deprioritise it compared to other things.

Peter: we can refer to tc39 documentation

Lea: they don't have principles, but discussions about starting something

Peter: guidence .. as long as it's written down somewhere. Action to write a new PR?

Lea: I've written what came out of the breakout. Need to hear from others about what needs to be written and how it should be prioritised.
Meta

Lea: reoccurring problem about where certain design principles should live. CSS in particular.

Tess: if CSS produced principles and wanted to own it, we can link to it. They're welcome to.

Peter: we shouldn't be writing principles for other standards bodies like tc39

Lea: WHATWG and TC39 are both creating javascript apis, according to different principles. We shouldn't favour one over the other.

Tess: with both we need to work with them. It's easy with WHATWG because of shared history and way of working. TC39 is pretty distinct. We should work with them, but be careful not to step on toes.

Peter: tc39 do other things than for the web

Lea: value for everyone of the js apis are consistent, whether for the web or not. Fine to make this an explicit goal. Be great to have a process that applies to w3c groups and non-w3c groups. A task force? Where we collaborate with the group on the principles that apply. It would mean splitting out the CSS design principles to be separate from the rest, or separate JS API design principles. I think it's worth it to get more input for these groups. Better than fragmentation between different principles documents. Last bullet contentious. First bullet not relevent. Middle three something we can write about?

Peter: yes

Rossen: I don't see agreement on the middle three. But not pushing back?

Lea: yeah, same assumption. Ask explicitly?

Rossen: ask through a PR

Peter: we can add all the points and settle contention in a PR. Just needs someone to write.

Lea: it's already to-write for me. Could see two principles coming out of this.
New principle: Guidance on when to use a child element vs an attribute - @hober, @LeaVerou

Tess: I'll attempt to do this this week
Guidance about which state properties should be reflected as HTML attributes - @hober, @LeaVerou, @plinss

Lea: On me, but can't do it this week. Doable for next month.
PR New text re: balancing concerns between interoperability and implementability

Tess: Dan and I worked on it in Tokyo. Things we didn't get to. Need to re-read. Many rounds of edits took us away from the original point - documenting tradeoffs in a failure case. Text doesn't make it clear that it's bad that we're here, but here are ways forward (which are differently bad). Sangwhan had feedback that it ought to be more positive. That would stop it communicating the right thing, that we dont' want to end up in this situation. Not ready to merge. Also doesn't hit Alice's lead with the conclusion. There isn't a singular conclusion/takeaway - it's "please don't end up in this state". Hard to summarise. Also looking at Dan's suggestions. I'd like Alice's review before merging even when it's ready.
PR First pass on backwards compatibility principle

Tess: unresolved comments.. Comment from dbaron, might need a new paragraph.

    I think another question worth considering is something like "is the feature specified well enough and open enough that implementations that don't already implement it can do so". (If the answer is no, I think that's an argument in favor of either (a) removal or (b) doing the work to change the answer to yes.)

New principle: Discourage overloading (in HTML) - @hober

On Tess to write. She'll try to set aside time this week for this.
New principle: Guidance on options dictionaries and default values - @LeaVerou
Web platform features that augment HTML elements en masse - @LeaVerou
New principle: Avoid adding (non-constructor) functions to the global scope
PR Make 6.1 more inclusive of non-Web JS APIs
PR Fix link to live-vs-static

merge
PR Give more guidance about how to monkeypatch well.

Lea: we had some feedback. Some edits I haven't reviewed yet. Some tc39 folks have weighed in.

Rossen: who added the CSS one?

Lea: Jeffrey, with feedback from CSS folks.
Breakout C

Present: Amy, Dan, Max, Yves, Sangwhan

Regrets:
General principle around time measurement units/formats for various domains (JS, HTTP, HTML, etc)? - @cynthia, @torgo
PR Restrictions

Sangwhan: needs editorial changes. Needs guidence on roughly what to use when. What would be the best choice by default. Need to spend some time on this. Noninteroperable stuff should be thrown out.

"Do this; if your design does this, use this, if your design does this, use this, otherwise ..."

Sangwhan: what we're trying to do here is - for majority of cases use our guidance...

Max: I can work on this. There's also a TODO note - should do this first?

Sangwhan: and check if the interoperability has changed in the last year. Permission Policy is now in TR. Secure Contexts is interoperable, think Document Policy isn't yet but it might have changed.

Max: interoperable means if there is a published standard?

Sangwhan: if there's at least one implementation.. some are not implemented at all. Ideally two. Two engine implementations as the gate for putting it in a principle. Or if it's in TR space it's formal enough, unless it would break things.
New principle: Naming of factory methods - @cynthia
PR New principle: Identity on the web

Amy: No update
New principle: Data Minimization - @torgo
Request for design principle clarification: Warn explicitly against getters throwing exceptions
PR Warn against getter throwing exception since it is a side effect

Dan: raised by somebody in the community on the basis of #400. Been some discussion, work by Tess and Lea. What's the story?

Sangwhan: we need to merge. Main blocker was bikeshed errors.

Dan: one outstanding suggestion not marked as resolved

Sangwhan: Lea wants it to be setters, not sure if I agree with that.

Dan: leave a comment and let's try to merge this at the plenary call.

Amy: merge without lea's change and..?

Sangwhan: lea can add another PR if she disagrees.

Dan: we can merge and talk about it on the plenary call

Sangwhan: to incorporate this we'd need to make other changes too, so happy with that

Dan: [comment and merge]
Societal Impacts Questionnaire

Dan: Web of Things filled this out recently. They've done a good job. They've talked about general internet of things, rather than spcific features of their spec

Amy: they have written that many of the questions assume a web browser but that was not my intent so that's another feedback point.

Dan: we should get some wide review

Dan: good feedback from Rick Byers

Amy: good feedback from AC

Sangwhan: some redundancies with S&P questionnaire... technical questions... opt out.

Amy: not only a technical question. Need to make that more clear. I'd like to draw that out - if the reaction is "there is a tech solution" but actually not. Also this not a test you pass or fail. Intended to get people thinking about this. Right now it's difficult to fill out.

Dan: key part of the purpose, to get people thinking about the impacts, similar to security & privacy questionnaire. Simplifying would be a good way to help. Crisp but nuanced.

Yves: maybe something like adding examples, eg. q2 has one. We can add more. Eg. battery sensors - was used to raise the price of something so people had to decide quickly. Bad examples of features added wth intent to be useful, but were misused or lead to privacy invasive things.

Sangwhan: battery sensor not a great example. Attack was theoretical, not much in the wild, mitigated before there was wide adoption.

Dan: geolocation. Introduced early on, but started to appear more and more on the front page of things..

Amy: there's an issue for adding examples - suggestions would be good there

Sangwhan: brings the bar very high for people bringing us reviews. Uncomfortable making this compulsory.

Amy: agree, concerned about that too. we don't know how we would use it - we don't want to increase the bar - point to make that people building powerful features on the web platform should perhaps slow & think about these issues.

Sangwhan: I like the intent of making people think about it. Similar to the intend with the a11y questionnaire. Making it a lean process could make it easier for people to go through it.

Dan: trying to think of wording we could put in issue template - encourage you to take a look, optional. What we do with BFCache - item in the design principles. We could add something that is something like do not cause harm to society.. already in ethical principles.. something more design princple-y that riffs off that, with a link to the additional document.

Amy: optional considerations - and we could bring it out for particularly contentious design reviews....

Sangwhan: we should use it for powerful features...

more discussion of how this fits into TAG

Dan: let's figure out how to make it visible - whole point is to raise awareness to engineers creating new features but may not have been thinking about this or be incentivised to think about these issues. Similar to privacy principles and priority of constituencies. Point of wide review. But also don't want to overwhelm them with too many things or feel like they're being preached to or that it's adversarial. We've got to have the right balance.

Sangwhan: we want to be careful about mandating... e.g. some CSS features might not have any societal impacts...
Plenary Session

Present: Peter, Amy, Yves, Rossen, Hadley, Max

Regrets: Dan
DPUB ARIA

Okay to close?

Rossen: looked through this, familiar with ARIA and mapping. One part that wasn't super clear was what was in scope for our review. First CR? Fine with this.

closed
How are we doing on this: [Meta] Tackling design problems earlier than design review / A Q&A section for API design

Lea: there have been some discussions. People dont' know yet what kind of questions to post. I think we should seed it ourselves to demonstrate. I tried to do when I was editing color api spec. If any of you are working on specs where api design questions come up that are too small for review it would be good for you to post them. Or when people reach out, direct them there to ask. We need to push it a little bit.

Peter: and we need to make sure we're paying attention to give answers

Lea: so far every question has discussion. Broader TAG community is fine, not just us

Peter: do we have enough visibility to know these conversations are happening - not on our agenda yet.

Lea: motivation was that we wouldn't be bringing them up on our agenda.

Peter: how do we get people on the TAG to pay attention?

Amy: we could just check on it monthly in design review week like we are right now

Lea: lots of questions may spark a design principles issue that will go on the agenda

Peter: standing item to review discussions. Chicken and egg - if people do post questions and don't get useful questions it's not an incentive. We do also need to fill the pipeline. The last comment on our issue was that Rossen was going to reach out to blink-dev and Tess was going to follow up with webkit. Did that happen?

Lea: I got useful responses about the color api from anne and dominic.  Just to try to have it more top of mind. Do people get these questions? Sometimes people reach out to me and ask things. I have tried to direct people here.
Likewise: PR Start developer version

Lea: Sangwhan and I need to sit down and work on it. Hoping for in f2f but there was no time. Nice to prioritise this next time - assign to a breakout with me and Sangwhan. It's a lot of work, not difficult.
Next f2f

Nothing scheduled until TPAC.

Lea: CSS WG meeting in California - 4 of us in CSSWG - could do it at the end of that. July 18-21.

Peter: could do a split f2f - Europe and CA. We typically don't get a lot of TAG time at TPAC so usually have extra time before or after.

discussion about how great Edinburgh is

Pencil in: week of 10th July (Hadley can't do before 26th). Rossen can't do week before CSS. We could do them separate weeks. Lea to ask for more feedback in Slack.
Breakout Rollup
Breakout A

Committments to write things up from Tess and Lea. Alice's feedback needed for one PR.

Did anyone ping Alice about feedback?

Update on monkeypatching - ready to merge?

Lea: change seems good to me. Can nitpick - change assumes different communities, but monkeypatching can happen in the same community. But it's clear enough.

Peter: Concern is groups patching other people's stuff.

consensus to merge
Breakout C

Max agreed to work on a PR. We merged a PR 400 without incorporating feedback from Lea, Lea may want to follow up with Sangwhan. Talked about societal immpact questionnaire.
Issue Triage

branch_name: refs/heads/gh-pages


text:
# VTU MARKS DOWNLOADER

Python bot to automatically download marks and parse the results.

* The current working file is stored into current.py

## REQUIREMENTS
Using pip, please install the following-
- bs4
- requests

These are url parsing and downloading libraries, also available in requirements.txt file

## CODING
Please do not change any system initializations and only change those under the SET AS NECCASSRY PARTS

## TROUBLESHOOTING
If there are numerous skipping usn without results, it probably means that there are either internet problems, vtu server is slow or they changed the website thus making my current scripts useless.

repository: bhatshravan/VTU

gha_language: Python

repo_name: bhatshravan/VTU


text:
The standard  `<Divider>` component is used to separate distinct segments of content.

If the divider is collapsible, pass in a callback function that sets the state, and include the state in your component.

**Example**:
```
state {
    open: false
}

const toggle = () => {
    this.setState({ open: !this.state.open });
};

return(
    <div>
        <Divider
            label="Collapsible Label"
            collapsible
            open={ this.state.open }
            callback= { this.toggle }
        />
        this.state.open && <div>Content to show when toggled open</div>
    </div>
)
```

repository: asifsha/gumdrops

gha_language: JavaScript

gha_license_id: MIT

repo_name: asifsha/gumdrops


text:
DISCONTINUATION OF PROJECT

This project will no longer be maintained by Intel.

Intel has ceased development and contributions including, but not limited to, maintenance, bug fixes, new releases, or updates, to this project.

Intel no longer accepts patches to this project.

If you have an ongoing need to use this project, are interested in independently developing it, or would like to maintain patches for the open source software community, please create your own fork of this project.

Contact<EMAIL_ADDRESS>Pystache
========

<!-- Since PyPI rejects reST long descriptions that contain HTML, -->
<!-- HTML comments must be removed when converting this file to reST. -->
<!-- For more information on PyPI's behavior in this regard, see: -->
<!-- http://docs.python.org/distutils/uploading.html#pypi-package-display -->
<!-- The Pystache setup script strips 1-line HTML comments prior -->
<!-- to converting to reST, so all HTML comments should be one line. -->
<!-- -->
<!-- We leave the leading brackets empty here.  Otherwise, unwanted -->
<!-- caption text shows up in the reST version converted by pandoc. -->
![](http://defunkt.github.com/pystache/images/logo_phillips.png "mustachioed, monocled snake by David Phillips")

![](https://secure.travis-ci.org/defunkt/pystache.png "Travis CI current build status")

[Pystache](http://defunkt.github.com/pystache) is a Python
implementation of [Mustache](http://mustache.github.com/). Mustache is a
framework-agnostic, logic-free templating system inspired by
[ctemplate](http://code.google.com/p/google-ctemplate/) and
[et](http://www.ivan.fomichev.name/2008/05/erlang-template-engine-prototype.html).
Like ctemplate, Mustache "emphasizes separating logic from presentation:
it is impossible to embed application logic in this template language."

The [mustache(5)](http://mustache.github.com/mustache.5.html) man page
provides a good introduction to Mustache's syntax. For a more complete
(and more current) description of Mustache's behavior, see the official
[Mustache spec](https://github.com/mustache/spec).

Pystache is [semantically versioned](http://semver.org) and can be found
on [PyPI](http://pypi.python.org/pypi/pystache). This version of
Pystache passes all tests in [version
1.1.2](https://github.com/mustache/spec/tree/v1.1.2) of the spec.

Requirements
------------

Pystache is tested with--

-   Python 2.4 (requires simplejson [version
    2.0.9](http://pypi.python.org/pypi/simplejson/2.0.9) or earlier)
-   Python 2.5 (requires
    [simplejson](http://pypi.python.org/pypi/simplejson/))
-   Python 2.6
-   Python 2.7
-   Python 3.1
-   Python 3.2
-   Python 3.3
-   [PyPy](http://pypy.org/)

[Distribute](http://packages.python.org/distribute/) (the setuptools fork)
is recommended over [setuptools](http://pypi.python.org/pypi/setuptools),
and is required in some cases (e.g. for Python 3 support).
If you use [pip](http://www.pip-installer.org/), you probably already satisfy
this requirement.

JSON support is needed only for the command-line interface and to run
the spec tests. We require simplejson for earlier versions of Python
since Python's [json](http://docs.python.org/library/json.html) module
was added in Python 2.6.

For Python 2.4 we require an earlier version of simplejson since
simplejson stopped officially supporting Python 2.4 in simplejson
version 2.1.0. Earlier versions of simplejson can be installed manually,
as follows:

    pip install 'simplejson<2.1.0'

Official support for Python 2.4 will end with Pystache version 0.6.0.

Install It
----------

    pip install pystache

And test it--

    pystache-test

To install and test from source (e.g. from GitHub), see the Develop
section.

Use It
------

    >>> import pystache
    >>> print pystache.render('Hi {{person}}!', {'person': 'Mom'})
    Hi Mom!

You can also create dedicated view classes to hold your view logic.

Here's your view class (in .../examples/readme.py):

    class SayHello(object):
        def to(self):
            return "Pizza"

Instantiating like so:

    >>> from pystache.tests.examples.readme import SayHello
    >>> hello = SayHello()

Then your template, say\_hello.mustache (by default in the same
directory as your class definition):

    Hello, {{to}}!

Pull it together:

    >>> renderer = pystache.Renderer()
    >>> print renderer.render(hello)
    Hello, Pizza!

For greater control over rendering (e.g. to specify a custom template
directory), use the `Renderer` class like above. One can pass attributes
to the Renderer class constructor or set them on a Renderer instance. To
customize template loading on a per-view basis, subclass `TemplateSpec`.
See the docstrings of the
[Renderer](https://github.com/defunkt/pystache/blob/master/pystache/renderer.py)
class and
[TemplateSpec](https://github.com/defunkt/pystache/blob/master/pystache/template_spec.py)
class for more information.

You can also pre-parse a template:

    >>> parsed = pystache.parse(u"Hey {{#who}}{{.}}!{{/who}}")
    >>> print parsed
    [u'Hey ', _SectionNode(key=u'who', index_begin=12, index_end=18, parsed=[_EscapeNode(key=u'.'), u'!'])]

Python 3
--------

Pystache has supported Python 3 since version 0.5.1. Pystache behaves
slightly differently between Python 2 and 3, as follows:

-   In Python 2, the default html-escape function `cgi.escape()` does
    not escape single quotes.  In Python 3, the default escape function
    `html.escape()` does escape single quotes.
-   In both Python 2 and 3, the string and file encodings default to
    `sys.getdefaultencoding()`. However, this function can return
    different values under Python 2 and 3, even when run from the same
    system. Check your own system for the behavior on your system, or do
    not rely on the defaults by passing in the encodings explicitly
    (e.g. to the `Renderer` class).

Unicode
-------

This section describes how Pystache handles unicode, strings, and
encodings.

Internally, Pystache uses [only unicode
strings](http://docs.python.org/howto/unicode.html#tips-for-writing-unicode-aware-programs)
(`str` in Python 3 and `unicode` in Python 2). For input, Pystache
accepts both unicode strings and byte strings (`bytes` in Python 3 and
`str` in Python 2). For output, Pystache's template rendering methods
return only unicode.

Pystache's `Renderer` class supports a number of attributes to control
how Pystache converts byte strings to unicode on input. These include
the `file_encoding`, `string_encoding`, and `decode_errors` attributes.

The `file_encoding` attribute is the encoding the renderer uses to
convert to unicode any files read from the file system. Similarly,
`string_encoding` is the encoding the renderer uses to convert any other
byte strings encountered during the rendering process into unicode (e.g.
context values that are encoded byte strings).

The `decode_errors` attribute is what the renderer passes as the
`errors` argument to Python's built-in unicode-decoding function
(`str()` in Python 3 and `unicode()` in Python 2). The valid values for
this argument are `strict`, `ignore`, and `replace`.

Each of these attributes can be set via the `Renderer` class's
constructor using a keyword argument of the same name. See the Renderer
class's docstrings for further details. In addition, the `file_encoding`
attribute can be controlled on a per-view basis by subclassing the
`TemplateSpec` class. When not specified explicitly, these attributes
default to values set in Pystache's `defaults` module.

Develop
-------

To test from a source distribution (without installing)--

    python test_pystache.py

To test Pystache with multiple versions of Python (with a single
command!), you can use [tox](http://pypi.python.org/pypi/tox):

    pip install 'virtualenv<1.8'  # Version 1.8 dropped support for Python 2.4.
    pip install 'tox<1.4'  # Version 1.4 dropped support for Python 2.4.
    tox

If you do not have all Python versions listed in `tox.ini`--

    tox -e py26,py32  # for example

The source distribution tests also include doctests and tests from the
Mustache spec. To include tests from the Mustache spec in your test
runs:

    git submodule init
    git submodule update

The test harness parses the spec's (more human-readable) yaml files if
[PyYAML](http://pypi.python.org/pypi/PyYAML) is present. Otherwise, it
parses the json files. To install PyYAML--

    pip install pyyaml

To run a subset of the tests, you can use
[nose](http://somethingaboutorange.com/mrl/projects/nose/0.11.1/testing.html):

    pip install nose
    nosetests --tests pystache/tests/test_context.py:GetValueTests.test_dictionary__key_present

### Using Python 3 with Pystache from source

Pystache is written in Python 2 and must be converted to Python 3 prior to
using it with Python 3.  The installation process (and tox) do this
automatically.

To convert the code to Python 3 manually (while using Python 3)--

    python setup.py build

This writes the converted code to a subdirectory called `build`.
By design, Python 3 builds
[cannot](https://bitbucket.org/tarek/distribute/issue/292/allow-use_2to3-with-python-2)
be created from Python 2.

To convert the code without using setup.py, you can use
[2to3](http://docs.python.org/library/2to3.html) as follows (two steps)--

    2to3 --write --nobackups --no-diffs --doctests_only pystache
    2to3 --write --nobackups --no-diffs pystache

This converts the code (and doctests) in place.

To `import pystache` from a source distribution while using Python 3, be
sure that you are importing from a directory containing a converted
version of the code (e.g. from the `build` directory after converting),
and not from the original (unconverted) source directory.  Otherwise, you will
get a syntax error.  You can help prevent this by not running the Python
IDE from the project directory when importing Pystache while using Python 3.

Mailing List
------------

There is a [mailing list](http://librelist.com/browser/pystache/). Note
that there is a bit of a delay between posting a message and seeing it
appear in the mailing list archive.

Credits
-------

    >>> context = { 'author': 'Chris Wanstrath', 'maintainer': 'Chris Jerdonek' }
    >>> print pystache.render("Author: {{author}}\nMaintainer: {{maintainer}}", context)
    Author: Chris Wanstrath
    Maintainer: Chris Jerdonek


text:
Role Name
=========

japanese

Installs tools to help with studying and using Japanese

Requirements
------------

None.

Role Variables
--------------

None.

Dependencies
------------

None.

Example Playbook
----------------

    - hosts: all
      roles:
         - role: japanese

License
-------

Apache License v2.0

Author Information
------------------

<EMAIL_ADDRESS>

repository: AntonioCarlini/ansible

repo_name: AntonioCarlini/ansible


text:
# Roboconf Web Administration

A web application to interact with Roboconf's Deployment Manager.

## Install

You will need node, npm and bower to be available on your system to install the web application.

*from the npm repository* (not available for now)

    npm install roboconf-web-administration

*from the sources*

    git clone https://github.com/roboconf/roboconf-web-administration.git
		npm install

## Running

Run the application with node as node and open your browser on http://localhost:8000

    node server.js
    # or
    npm start

## License

Copyright 2012-2014 Linagora, Université Joseph Fourier

This product includes software developed under the Apache License v2.0
(visit the Apache Software Foundation at http://www.apache.org/).

repository: chamerling/roboconf-web-administration

repo_name: chamerling/roboconf-web-administration


text:
---
layout: post
title: Ohce Kata
categories: [Starter, Mocks, TDD, Pair-Programming]
image: default.jpg
---

{% include credits.md name='Manuel Rivero' url='http://garajeando.blogspot.com/2016/05/the-ohce-kata-short-and-simple-exercise.html' %}

## Goal

A short and simple exercise to practice outside-in TDD using test doubles.

## Description

<script src="https://gist.github.com/trikitrok/34ea4433bb88659ec4c557839c83aa26.js"></script>

{% include starting_points.md %}

license: Unlicense

repository: drpicox/kata-log

gha_license_id: Unlicense

repo_name: drpicox/kata-log


text:
# ClientIndex

## Properties
Name | Type | Description | Notes
------------ | ------------- | ------------- | -------------
**Id** | **int** | The unique ID of the client index. | [optional]
**Name** | **string** | The name of the client index. | [optional]
**RequiredBusinessMode** | **bool** | When `true`, indicates that the index is required when creating profiles in business mode. | [optional]
**RequiredConsumerMode** | **bool** | When `true`, indicates that the index is required when creating profiles in consumer mode. | [optional]
**Values** | [**\Nlocascio\Mindbody\Model\ClientIndexValue[]**](ClientIndexValue.md) | Contains information about the index's possible values. | [optional]
**Action** | **string** | The action performed on this object. | [optional]

[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md)

repository: ranitham/mindbody-laravel

repo_name: ranitham/mindbody-laravel


text:
# pdfHelper
 This is a facility script file for you to download and rename the paper with  the paper title.

Dependencies:
1. pdftitle
2. requests

Basic Usage：
 python pdfhelper.py -l link_paper

repository: eefengwei/pdfHelper

repo_name: eefengwei/pdfHelper


text:
---
layout: default
---

# 1997-01-29 - Re: Libel & the 1st Amendment

## Header Data

From<EMAIL_ADDRESS>(Dr.Dimitri Vulis KOTM)

To<EMAIL_ADDRESS>Message Hash: 38ad54221ca213509b32b1d314d8a35d5f1c6d2364bd6d59c8064532a518b5ce

Message ID<EMAIL_ADDRESS>Reply To<EMAIL_ADDRESS>UTC Datetime: 1997-01-29 21:47:32 UTC

Raw Date: Wed, 29 Jan 1997 13:47:32 -0800 (PST)

## Raw message

```
{% raw  %}From<EMAIL_ADDRESS>(Dr.Dimitri Vulis KOTM)
Date: Wed, 29 Jan 1997 13:47:32 -0800 (PST)
To<EMAIL_ADDRESS>Subject: Re: Libel & the 1st Amendment
In-Reply-To<EMAIL_ADDRESS>Message-ID<EMAIL_ADDRESS>MIME-Version: 1.0
Content-Type: text/plain

<EMAIL_ADDRESS>(Huge Cajones Remailer) writes:

> At 10:46 AM 1/29/1997, Declan McCullagh wrote:
> > * Many 1st Amendment experts don't believe in the legal concept of
> > libel.  It is, they say, a rich man's game -- if I'm libeled by the
> > NYT, I'm probably not going t be able to sue them, but Donald Trump
> > can. Moreover, if I don't have the resources to sue but the
> > statement is libelous, it creates a *presumption* in the minds of
> > the readers that the article is certainly true. (If it were not, I
> > would have sued, right?)
>
> The wealthy also use libel suits to suppress dissent.  Greg's point
> that poor people aren't worth suing is only true if the motivation is
> financial.  Often it is not.  Conveniently, many of those whose
> silence is desired are among the petty bourgeouis and have a net worth
> of roughly $50,000.  Enough to make the suit appear legitimate, but
> not enough to allow the target to brush off the legal fees, if they
> win the case.
>
> Consider also the artificial distinction between private and public
> figures.  It is easier for a private figure to sue for libel.  Yet,
> the most influential people in the country are private figures.
> Reporters must tread very carefully when covering the activities of
> these people.  Thus, we hear little of them.
>
> It would be interesting to know when libel law was first introduced to
> the United States.  Does anybody know?
>
> John Peter Zenger

Libel laws were inherited from good old England together with most of common
law.  When I was studying con law, I remember the very interesting precedent
establishing that truth is a defense in a libel suit. Anyone remember the name?

---

Dr.Dimitri Vulis KOTM
Brighton Beach Boardwalk BBS, Forest Hills, N.Y.: +1-718-261-2013, 14.4Kbps

{% endraw %}
```

## Thread

+ Return to [January 1997](/archive/1997/01)

+ Return to<EMAIL_ADDRESS>(Dr.Dimitri Vulis KOTM)](/authors/dlv_at_bwalk_dm_com_dr_dimitri_vulis_kotm_)"
+ Return to<EMAIL_ADDRESS>(Huge Cajones Remailer)](/authors/nobody_at_huge_cajones_com_huge_cajones_remailer_)"

+ 1997-01-29 (Wed, 29 Jan 1997 10:05:31 -0800 (PST)) - [Re: Libel & the 1st Amendment](/archive/1997/01/ee4df636bfea9c719c6e2782b7a400f50e442b61c44e4db9270625af56e0b652) -<EMAIL_ADDRESS>(Huge Cajones Remailer)_
  + 1997-01-29 (Wed, 29 Jan 1997 13:47:32 -0800 (PST)) - Re: Libel & the 1st Amendment -<EMAIL_ADDRESS>(Dr.Dimitri Vulis KOTM)_


text:
---
number: 409
title: Github Co-pilot is Gonna Take ur Job
date:<PHONE_NUMBER>902
url: https://traffic.libsyn.com/syntax/Syntax_-_409.mp3
---

In this Hasty Treat, Wes and Scott talk about their experiences using Github Co-pilot.

## Sponsor - LogRocket

LogRocket lets you replay what users do on your site, helping you reproduce bugs and fix issues faster. It's an exception tracker, a session re-player and a performance monitor. Get 14 days free at [logrocket.com/syntax](https://logrocket.com/syntax).

## Sponsor - Freshbooks

Get a 30 day free trial of Freshbooks at [freshbooks.com/syntax](https://freshbooks.com/syntax) and put SYNTAX in the "How did you hear about us?" section.

## Show Notes

* **[00:58](#t=00:58)** Wake up early and let's go
* **[02:19](#t=02:19)** Sponsor: LogRocket
* **[03:21](#t=03:21)** Sponsor: Freshbooks
* **[03:56](#t=03:56)** What is Github Co-Pilot?
* [GitHub Co-Pilot](https://copilot.github.com)
* **[06:01](#t=06:01)** Scott is a GitHub Star
* **[07:03](#t=07:03)** Examples of GitHub Co-Pilot usage
* **[09:43](#t=09:43)** Writing pseudo code
* [Emmet](https://www.emmet.io)
* **[12:51](#t=12:51)** Using it for loop callbacks
* **[13:52](#t=13:52)** What langauges does GitHub Co-Pilot work with?
* **[14:54](#t=14:54)** It plays nice with HTML files
* **[15:48](#t=15:48)** Svelte component example
* **[16:31](#t=16:31)** Benefits for course creators
* **[17:35](#t=17:35)** Some scary things
* **[21:04](#t=21:04)** Could GitHub start charging for this?
* **[22:30](#t=22:30)** Good at writing types
* **[23:59](#t=23:59)** Gripes
* **[24:54](#t=24:54)** Converting code to Parcel 2
* [Parcel](https://parceljs.org)

## Tweet us your tasty treats

* [Scott's Instagram](https://www.instagram.com/stolinski/)
* [LevelUpTutorials Instagram](https://www.instagram.com/LevelUpTutorials/)
* [Wes' Instagram](https://www.instagram.com/wesbos/)
* [Wes' Twitter](https://twitter.com/wesbos)
* [Wes' Facebook](https://www.facebook.com/wesbos.developer)
* [Scott's Twitter](https://twitter.com/stolinski)
* Make sure to include [@SyntaxFM](https://twitter.com/SyntaxFM) in your tweets

url: https://raw.githubusercontent.com/barrymcgee/Syntax/2b236a550ab54aea5639cb37b052e88eb74b402b/shows/409 - Github Co-pilot is Gonna Take ur Job.md

repository: barrymcgee/Syntax

repo_name: barrymcgee/Syntax


text:
# ConvertMatrixToString

This module prints the contents of a matrix into a string.

**Detailed Description**

For a dense matrix it outputs all the rows and columns of the matrix. For a sparse matrix only the non zero elements are printed.


text:
epkg(1) -- A friendly wrapper for Gentoo package managment commands.
====================================================================

## SYNOPSIS

`epkg` COMMAND [PACKAGE]

## DESCRIPTION

Run COMMAND optionally against PACKAGE(s).

## COMMANDS

  * `install`:
  Install a package (or packages).
  * `remove`:
  Remove a package (or packages).
  * `uninstall`:
  Alias for remove.
  * `search`:
  Search all enabled repositories for PACKAGE.
  * `update`:
  Update package listing and package search database.
  * `upgrade`:
  Check all packages on system for available upgrades.
  * `dist-upgrade`:
  Alias for upgrade.
  * `autoclean`:
  Remove unneeded distfiles.
  * `clean`:
  Remove ALL distfiles. Take care when using this command.
  * `forceremove`:
  Forcibly uninstall a package. Take care when using this command as reverse dependencies are NOT checked.
  * `listfiles`:
  List all files installed by a given PACKAGE.
  * `listinstalled`:
  List all packages currently installed matching a given pattern.
  * `provides`:
  List what package a provides a given filepath.
  * `verify`:
  Verify integrity of installed files for a given installed package.
  * `verifyall`:
  Verify integrity of all files on the system installed from the package manager.
  * `sysinfo`:
  Display some system information useful for debugging and support.

## EXAMPLES

`epkg install firefox-bin`:
  Install the firefox-bin package.

`epkg autoclean`

## SEE ALSO

emerge(1), eix(1), equery(1)

repository: jdhore/epkg

gha_language: Shell

repo_name: jdhore/epkg


text:
# _Sample project_

(See the README.md file in the upper level 'examples' directory for more information about examples.)

This is the simplest buildable example. The example is used by command `idf.py create-project`
that copies the project to user specified path and set it's name. For more information follow the [docs page](https://docs.espressif.com/projects/esp-idf/en/latest/api-guides/build-system.html#start-a-new-project)

## How to use example
We encourage the users to use the example as a template for the new projects.
A recommended way is to follow the instructions on a [docs page](https://docs.espressif.com/projects/esp-idf/en/latest/api-guides/build-system.html#start-a-new-project).

## Example folder contents

The project **sample_project** contains one source file in C language [main.c](main/main.c). The file is located in folder [main](main).

ESP-IDF projects are built using CMake. The project build configuration is contained in `CMakeLists.txt`
files that provide set of directives and instructions describing the project's source files and targets
(executable, library, or both).

Below is short explanation of remaining files in the project folder.

```
├── CMakeLists.txt
├── main
│   ├── CMakeLists.txt
│   └── main.c
└── README.md                  This is the file you are currently reading
```
Additionally, the sample project contains Makefile and component.mk files, used for the legacy Make based build system.
They are not used or needed when building with CMake and idf.py.

repository: espressif/vscode-esp-idf-extension

gha_language: TypeScript

repo_name: espressif/vscode-esp-idf-extension


text:
eslint-config-fixable-all
=========================
[![Build Status](https://travis-ci.org/rhysd/eslint-config-fixable-all.svg?branch=master)](https://travis-ci.org/rhysd/eslint-config-fixable-all)

This is a list of [eslint](http://eslint.org/) rules which can be fixed automatically by `eslint --fix`.  This configuration specifies all fixable rules as 'error'. So all the fixable rules violation causes linter error and we need to fix them. With this configuration it ensures all the fixable problems should be fixed.

## Installation

```
$ npm install --save-dev eslint eslint-config-fixable-all
```

## Usage

At first, extend this config to your `.eslintrc`

```diff
 {
-    "extends": ["eslint:recommended"]
+    "extends": ["eslint:recommended", "fixable-all"]
 }
```

And then, after adding your changes, try `eslint` command

```sh
$ git add -A
$ "$(npm bin)/eslint" .
```

If some error occurred, try `eslint --fix` to fix code and see the result

```sh
$ "$(npm bin)/eslint" --fix .
$ git diff
```

If you don't want to fix or change the fixing behavior, please overwrite the rule in your configuration.
For example, if you don't want to add semicolon, overwrite the configuration.

```diff
 {
     "extends": ["eslint:recommended", "fixable"],
+    "rules": {
+        "semi": ["error", "never"]
+    }
 }
```

Or if you don't want to fix semicolon, you can off the configuration.

```diff
 {
     "extends": ["eslint:recommended", "fixable"],
+    "rules": {
+        "semi": "off"
+    }
 }
```

When you want to rollback the fixes, you can simply `git checkout`.

```sh
$ git checkout . # Rollback all fixes in current directory
```

After you can accept the fixes, `git add -A` to add them to Git index.

## Versioning

Major version and minor version are synchronized with eslint. For example, eslint-config-fixable-all v3.9.x is compatible with eslint v3.9.x. eslint-config-fixable-all's patch version is not compatible with eslint. But you need not to care about it because eslint follows semantic versioning.

## License

[MIT License](./LICENSE)

repository: rhysd/eslint-config-fixable-all

repo_name: rhysd/eslint-config-fixable-all


text:
---
layout: default
---

# 1994-04-28 - Re: Directory of 'punks

## Header Data

From<EMAIL_ADDRESS>(no depression)

To<EMAIL_ADDRESS>Message Hash: 2f62d2fe99506e1b31976b3a66df49bf27383ef916837e9adb81d72d4a2c3a6e

Message ID<EMAIL_ADDRESS>Reply To<EMAIL_ADDRESS>UTC Datetime: 1994-04-28 18:28:01 UTC

Raw Date: Thu, 28 Apr 94 11:28:01 PDT

## Raw message

```
{% raw  %}From<EMAIL_ADDRESS>(no depression)
Date: Thu, 28 Apr 94 11:28:01 PDT
To<EMAIL_ADDRESS>Subject: Re: Directory of 'punks
In-Reply-To<EMAIL_ADDRESS>Message-ID<EMAIL_ADDRESS>MIME-Version: 1.0
Content-Type: text

"Jim Sewell" says:
>
>  Thank you for the preliminary (<2 hrs) response to the posting.  I have
>  not gotten a "that's a bad idea" letter yet of the 7 replies so I will
>  assume this is a "Good Thing" tm.

Oooh.  I don't know about a good idea.  I was never much in favor
of giving my name out for free.  I mean if someone want's to read this
list and find my affiliation from the sporadic posts that I enter and
then make random associations about me that is one thing.

But to do it for them?  Nahhh, that is part of the reason I entertain
ideas like cryptography, and practices like only withdrawing my money
from one bank in person while writing out of state checks for all
mail purposes.  I'd just rather that people didn't know my business.
Thus, personally, I think it is "a bad idea".

Andrew Prock
<EMAIL_ADDRESS>

{% endraw %}
```

## Thread

+ Return to [April 1994](/archive/1994/04)

+ Return to "["Jim Sewell" <jims@Central.KeyWest.MPGN.COM>](/authors/jim_sewell_jims_at_central_keywest_mpgn_com_)"
+ Return to<EMAIL_ADDRESS>(Lefty)](/authors/lefty_at_apple_com_lefty_)"
+ Return to<EMAIL_ADDRESS>(no depression)](/authors/prock_at_teetot_acusd_edu_no_depression_)"
+ Return to "["Robert A. Hayden" <hayden@krypton.mankato.msus.edu>](/authors/robert_a_hayden_hayden_at_krypton_mankato_msus_edu_)"

+ 1994-04-28 (Thu, 28 Apr 94 10:53:32 PDT) - [Re: Directory of 'punks](/archive/1994/04/d766508fccce3b137adad5f121b1ca96c131a62a6584392f6143fc30d2e2a1c2) -<EMAIL_ADDRESS>(Lefty)_
  + 1994-04-28 (Thu, 28 Apr 94 11:28:01 PDT) - Re: Directory of 'punks -<EMAIL_ADDRESS>(no depression)_
    + 1994-04-28 (Thu, 28 Apr 94 11:59:29 PDT) - [Re: Directory of 'punks](/archive/1994/04/008e8af34743f4563475d70e30914bc192b0e8ba63f140f0d9e9a83db3262c1a) - _"Robert A. Hayden"<EMAIL_ADDRESS>    + 1994-04-28 (Thu, 28 Apr 94 12:19:13 PDT) - [Re: Directory of 'punks](/archive/1994/04/e8dbddd9e005aa8374a6571f3e534328d851a5ec2fe2d4a191d9b6a080382be0) - _"Jim Sewell"<EMAIL_ADDRESS>


text:
---
layout: default
---

# 1998-08-04 - No Subject

## Header Data

From: Anonymous<EMAIL_ADDRESS>To<EMAIL_ADDRESS>Message Hash: b708a9b46cf97d9dc2a6b9cf6875ab859cf998356291560960b5e7569ee9ac8a

Message ID<EMAIL_ADDRESS>Reply To: _N/A_

UTC Datetime: 1998-08-04 02:06:09 UTC

Raw Date: Mon, 3 Aug 1998 19:06:09 -0700 (PDT)

## Raw message

```
{% raw  %}From: Anonymous<EMAIL_ADDRESS>Date: Mon, 3 Aug 1998 19:06:09 -0700 (PDT)
To<EMAIL_ADDRESS>Subject: No Subject
Message-ID<EMAIL_ADDRESS>MIME-Version: 1.0
Content-Type: text/plain

> 	Actually, Hamre said that US companies have no Gawd-Given Right to
> _export_ strong crypto. See:
> http://www.wired.com/news/news/technology/story/14098.html

Oh, it's sick anyhow...

A couple excerpts from jya's transcript:

On the EFF DES cracker: Now, I need to explain first of all, that the
government is currently permitting the export of 56 bit encryption
algorithms.  Now, I know that there's some huffing and puffing about
whether that's strong encryption or not. But again, I say let's put this
in context.  There was a flap here the other day when, ta-da, somebody
invented a computer that could break 56 bit encryption in 30 hours or 40
hours or whatever the time was, right.  You took 40 hours to decrypt a
two-second message.  And it was good only for that one message.  You've
got to start all over again on the next two-second message.  Tell me that
that isn't strong encryption.

[Secretary Hamre, that isn't strong encryption. Weak enough that cracking
DES keys for two grand each -- reasonable price considering some of the
applications using DES -- can be a viable business for the shady hacker
type, in fact. Pays for your parts in ten months, pocket most everything
else until the machine breaks.]

On export controls: "...I'd also ask American business not to make a
campaign out of just trying to bust through export controls as though
somehow there was a God-given, inherent right to send the strongest
encryption to anybody in the world, no matter who they are.  I don't agree
with that.  I will never agree with that."

["I will never agree with that" -- I'd say we're talking to an open-minded
individual who's really trying to work things out, eh?]

>
> 	Which, despite all the damage control and spin waves that followed
> the initial report in WiRed, does not mean that the NSA and DoD believe
> that anyone has been granted some privilege to speak in confidence that
> they, being reverent and religious fellows, should and must respect.
>
> 	Much ado about nothing, here!
>
> 	The first (perhaps literally erroneous) WiRed News report -- that
> senior DoD officials do not believe that any two people anywhere in the
> world have a perfect and unassailable right to speak in confidence and
> secrecy -- was spot on accurate and true.
>
>
> -----
> "Cryptography is like literacy in the Dark Ages. Infinitely potent, for
> good and ill... yet basically an intellectual construct, an idea, which by
> its nature will resist efforts to restrict it to bureaucrats and others who
> deem only themselves worthy of such Privilege."
> _ A Thinking man's Creed for Crypto _vbm.
>
>  *     Vin McLellan + The Privacy Guild +<EMAIL_ADDRESS>  *
>       53 Nichols St., Chelsea, MA 02150 USA <617> 884-5548

{% endraw %}
```

## Thread

+ Return to [August 1998](/archive/1998/08)

+ Return to "[Anonymous <nobody@replay.com>](/authors/anonymous_nobody_at_replay_com_)"

+ 1998-08-04 (Mon, 3 Aug 1998 19:06:09 -0700 (PDT)) - No Subject - _Anonymous<EMAIL_ADDRESS>


text:
# graphx

Basic object graph utilities for Haxe

## Features

- Graph creation for nodes of the same type
- Depth-first search
- Breadth-first search (TODO)
- Cycle detection (TODO)
- Topological sort

## Examples

```Haxe
var graph : Graph<String> = new Graph({
  equals: function(a, b) return a == b,
  getKey: function(a) return a
});
graph.addEdgesFrom("eat breakfast", ["take out trash"]);
graph.addEdgesFrom("brush teeth", ["shave"]);
graph.addEdgesFrom("get dressed", ["eat breakfast", "read paper"]);
graph.addEdgesFrom("shave", ["get dressed"]);
graph.addEdgesFrom("wake up", ["brush teeth", "take shower"]);
graph.addEdgesFrom("take out trash", ["go to work"]);

var results = graph.topologicalSort();
trace(results);
// ["wake up", "take shower", "brush teeth", "shave", "get dressed",
//  "read paper", "eat breakfast", "take out trash", "go to work"]
```

## API

TODO


text:
# photo-collage-app

This is a photo collage app developed using jQuery and jQuery UI widgets. It has the following features:

Drag/Drop: You can drag/drop the images in the gallery onto the workspace. You can drag as many images as you want. An HTML5 droppable provided to add more images to gallery

Select: Selecting an image would create a blue border and resize/rotate handles around the image.

Move: Dragging an already placed image on the workspace would move it around.

Resize: Dragging the resize handles on the image would resize the image.

Rotate: Dragging the rotate handle (on the top edge) will rotate the image in the dragged direction.

Delete: When an image is selected, pressing the "Delete" key on the keyboard would remove it.

Package manager used: Bower

Task runner for automating the build used: Gulp

Download the zip and Enjoy!!

repository: sankalplakhina/photo-collage

repo_name: sankalplakhina/photo-collage


text:
### Description

Example to demonstrate an actor that draws 2D data.

The object vtkActor2D is similar to vtkActor, but it is made to be used with two dimensional images and annotation.

vtkActor2D object has a position but does not use a transformation matrix like vtkActor and it has a reference to a vtkMapper2D object which does the rendering.

repository: Kitware/vtk-examples

repo_name: Kitware/vtk-examples


text:
### Cerberus image

Container image gets automatically built by quay.io at [Cerberus image](https://quay.io/repository/openshift-scale/cerberus). The builds will be triggered by any commit pushed to this repository.

### Run containerized version
Refer to the [instructions](https://github.com/openshift-scale/cerberus#Run-containerized-version) for information on how to build and run the containerized version of cerberus.

repository: worsco/cerberus

repo_name: worsco/cerberus


text:
---
hrs_structure:
  division: '1'
  volume: '1'
  title: '1'
  chapter: '1'
  section: 1-17
type: hrs_section
tags:
  - Government
menu:
  hrs:
    identifier: HRS_0001-0017
    parent: HRS0001
    name: 1-17 Number and gender
weight: 2095
title: Number and gender
full_title: 1-17 Number and gender
---
**§1**-**17 Number and gender.** Words in the masculine gender signify both the masculine and feminine gender, those in the singular or plural number signify both the singular and plural number, and words importing adults include youths or children. [PC 1869, c 1, §5; RL 1925, §14; RL 1935, §15; RL 1945, §14; am L 1945, c 233, §1; RL 1955, §1-22; [HRS §1-17](/title-1/chapter-1/section-1-17/)]

Case Notes

Singular read as plural where more than one office to be filled. 22 H. 520, 523.

"Sureties" read as "surety". 33 H. 265, 266.

repository: SamMade/BlueAndKrabby

repo_name: SamMade/BlueAndKrabby


text:
# arm-embedded-elf
Basic ELF shared object library loader for ARM embedded systems

# Usage #

Compile elf/elf.c and include elf/elf.h in your project.

An ELF file can be loaded from memory with:
```c
void * const handle = elf_dlmemopen( elf_file_in_memory, ELF_RTLD_DEFAULT );
error = elf_dlerror( handle );
if ( error ) {
  // Load error
} else {
  // Load success
}

// ELF must be closed even if load error occurs
elf_dlclose( handle );
```

Unresolved symbols must be added before linking:
```c
void my_function() {}
int my_integer = 32;

// Add function
elf_mapsym( handle, "my_function", ( void * )my_function );
error = elf_dlerror( handle );
if ( error ) {
  // ...
}

// Add int
elf_mapsym( handle, "my_integer", ( void * )&my_integer );
error = elf_dlerror( handle );
if ( error ) {
  // ...
}
```

Linking must be done into already allocated memory:
```c
void * memory = malloc( elf_lbounds( handle ) );

elf_link( handle, memory );
error = elf_dlerror( handle );
if ( error ) {
  // ...
}

// After ELF is used
elf_dlclose( handle );
free( memory );
```

After linking, symbols can be retrieved and used:
```c
typedef void ( * func_t )( void );

func_t func = ( func_t )elf_dlsym( handle, "elf_function" );

if ( !func ) {
  // Failed to find symbol
  error = elf_dlerror( handle );
  // ...
} else {
  // Use function
  ( *func )();
}
```

# Known issues #

## Limited implementation ##

This is a very basic implementation for ARM architecture.
Not all the ARM resolution types are implemented (only 3).
A lot of the ELF spec is not implemented, specifically classic init/fini support (modern arrays only).

## Unlinked Thumb functions need -mlong-calls ##

For some reason, without mlong-calls, calling Thumb functions from a Thumb or ARM compiled ELF results in attempting to run the Thumb function in an ARM context.
ELF shared objects that are likely to use Thumb functions must be compiled with -mlong-calls.

This does not affect ARM functions, so another work-around is to wrap Thumb functions with ARM and use that with elf_mapsym instead.

## Memory only ##

File stream sources are not currently supported, but adding this shouldn't be too difficult.

With fmemopen the default system can likely be changed to expect file streams.

## No lazy loading ##

Link resolution happens for all symbols immediately, even if they are never used.

repository: felixjones/arm-embedded-elf

repo_name: felixjones/arm-embedded-elf


text:
# MuditaTheme

MuditaTheme is a plugin for Mudita community theme

## Installation

Follow [Install a Plugin](https://meta.discourse.org/t/install-a-plugin/19157)
how-to from the official Discourse Meta, using `git clone https://github.com/mkurczewski/mudita-theme.git`
as the plugin command.

repository: Appnroll/mudita-discourse-plugin

repo_name: Appnroll/mudita-discourse-plugin


text:
# Common-Dialog

Common Dialog used to any activity directly with Reusability.

## Installation Process

Please understand the below Classes.

```bash
• CommonDialog.java
-> This is the main Common Class for this functionality.
-> Create a new java file named "CommonDialog.java " in any package or "Utils/Common" package.
```

## Usage

```bash
In Any class,
You want to use this Common Dialog then follow the below steps:
1) In Any Class implements CommonDialog.CommonDialogListener
like: "public class LoginActivity extends AppCompatActivity implements CommonDialog.CommonDialogListener"

2) You already got 2 Overridden methods after successfully implemented
@Override
    public void onYesClicked() {
      // Write down Your Logics for Yes Button Clicked
    }

    @Override
    public void onNoClicked() {
      // Write down Your Logics for No Button Clicked
    }

3) Whenever you have to show dialog then use below sample code:
 final CommonDialog dialog =
                new CommonDialog("Close App",
                        getString("Are you Sure You want to close app?",
                        android.R.drawable.ic_dialog_alert);
        dialog.show(getSupportFragmentManager(), "example dialog");
```

## Contributing
Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.

Please make sure to update tests as appropriate.

## License
[MIT](https://choosealicense.com/licenses/mit/)

repository: DivyamOza/Common-Dialog

branch_name: refs/heads/main

repo_name: DivyamOza/Common-Dialog


text:
---
layout: docs
title: Scope API
description: declare scoped instances in Koin
group: quick-references
toc: true
---

### What's a scope?
A scope is a fixed duration of time in which an object exists. When the scope context ends, any objects bound under that scope cannot be injected again (they are dropped from the container).

### Declare a scoped definition

By default in Koin, we have 3 kind of scopes:

- `single` definition, create an object that persistent with the entire container lifetime (can't be dropped).
- `factory` definition, create a new object each time. No persistence in the container (can't be shared).
- `scoped` definition, create an object that persistent tied to the associated scope lifetime.

To declare a scope definition, use the `scoped` function:

{% highlight kotlin %}
module {
    scoped { Presenter() }
}
{% endhighlight %}

### Declare and use a scope

A scope is a logical unit of scoped definitions.

For the given classes:

{% highlight kotlin %}
class ComponentA
class ComponentB(val a : class ComponentA)
{% endhighlight %}

We can write the following scope:

{% highlight kotlin %}
module {
    // define the scope with its qualifier "MY_SCOPE"
    scope(named("MY_SCOPE") {
        scoped { ComponentA() }
        scoped { ComponentB(get()) }
    }
}
{% endhighlight %}

### Create and use a scope instance

From any `Koin` instance or also available from your `KoinComponent` with `getKoin()`, the following functions allows to handle scope instances:

{% highlight kotlin %}
// create scope instance with ScopeID "myScope" for scope naled "MY_SCOPE"
val myScope : Scope = koin.createScope("myScope", named("MY_SCOPE")

// get instance ComponentA from scope
val a = myScope.get<ComponentA>()
// get instance ComponentB from scope and retrieve instance ComponentA from same scope
val b = myScope.get<ComponentB>()

// if you need, you can retrieve your scope instance by its id
val myScope : Scope = koin.getScope("myScope")

// close the scope when needed
myScope.close()
{% endhighlight %}

## More about

Below are some further readings:

repository: droid-dev-ganesh/koin

repo_name: droid-dev-ganesh/koin


text:
# Contribution guide

## Description
We build `demisto-sdk` to support python 3.7 and 3.8.

## Getting started

1. [Clone demisto-sdk repository](#1-clone-demisto-sdk-repository)
2. [Install demisto sdk dev environment](#2-install-demisto-sdk-dev-environment)
3. [Pre-commit hooks setup](#3-pre-commit-hooks-setup)
4. [DemistoContentPython Library](#4-demistocontentpython-library)
5. [Develop new command](#5-develop-new-command)
6. [Running unit-tests using tox](#6-running-unit-tests-using-tox)
7. [Push changes to GitHub (External PRs)](#7-push-changes-to-github-relevant-only-for-external-prs)
8. [Review Process](#8-review-process)
9. [Contributor License Agreement (External PRs)](#9-contributor-license-agreement-relevant-only-for-external-prs)

---

### 1. Clone demisto-sdk repository
Perform the following command in the path you want the repository to be cloned:

```shell
git clone https://github.com/demisto/demisto-sdk.git
```

---

### 2. Install demisto sdk dev environment

We will now setup a quick virtualenv in which we will install the `demisto-sdk` version you are currently working on.
This will be used as your testing environment, you do not need to update it again or re-run in any way.

1. Make sure you have python3 installed.

2. Make sure you have [Poetry](https://python-poetry.org/) installed.

3. run `poetry install``

4. For further reading about Poetry, you can refer to [Poetry documentation](https://python-poetry.org/).

You have now setup the your `demisto-sdk` dev environment!

To activate it simply run: `poetry shell`.
   * Check that the demisto-sdk installed is your local version by running `demisto-sdk -v` - you will should see something similar to `demisto-sdk 1.X.X.dev`.

To deactivate the virtual environment and return simply run: `exit`.
   * Note that your local `demisto-sdk` version should remain unchanged.

---

### 3. Pre-commit hooks setup
We use are using [pre-commit](https://pre-commit.com/) to run hooks on our build. Before using the hooks make sure you have pre-commit insalled (you can check it by running `which pre-commit`, if it does not exist install it via pip: `pip install pre-commit`).

To use pre-commit, run:
1. Install hook to be performed as a hook before commit changes - `pre-commit install`
2. Enable auto update of pre-commit hooks - `pre-commit autoupdate`
3. In order to run pre-commit without commit- `pre-commit run -a` (on all files), `pre-commit run` (on staged files)

---

### 4. DemistoContentPython Library
ContentPython is a python library used to interact with Demisto Content repository, high-level abstraction.
For more information read the following [guide](demisto_sdk/commands/common/content/README.md).

---

### 5. Develop new command
1. Create package for your command in the following path: `<repo>/demisto_sdk/commands/<your_new_command>`.
2. Create the following in the above path:
    1.  **CLI arguments parsing** - Add CLI parsing in `<repo>/demisto_sdk/__main__` using [click](https://click.palletsprojects.com/en/7.x/) package.
    2. **commands_module** - The modules suppose to return `0` if **succeed** else `1`, common `print` function can  import from `<repo>/demisto_sdk/commands/common/tools.py`
    3. **unit-tests** -

        1. Unit-tests should be located for each command in the following path-

            ```shell
            <repo>/demisto_sdk/commands/<your_new_command>/tests
            ```

        2. data files tests - Usually its shared data files for all commands which located in:

            ```shell
            <repo>/demisto_sdk/tests/test_files
            ```

            >  (you can use constants for right path in `<repo>/demisto_sdk/tests/constants_test.py`)

        3. check build influence on CircleCI -

            1. Test your functionality on CircleCI build of `Content` repository by changing requirements in `Content` repository:
                1.  Perform the following in `<content_repo>/dev-requirements-py3.txt`:
                    1. Delete `demisto-sdk` requirement.

                    2. Add the following requirement in new line -

                       ```
                        git+https://github.com/demisto/demisto-sdk@<branch>
                       ```

                2. Remove cache using in CircleCI build config, perform the following in file

                    ```shell
                    <content_repo>/.circleci/config.yml
                    ```

                    1. Remove the following string form the following key `restore_cache:`: `-{{ checksum "dev-requirements-py3.txt" }}`

---

### 6. Running unit-tests using Pytest

We use [pytest](https://github.com/pytest-dev/pytest) to run unit tests.

Simply use `poetry` to run your tests on a relevant folder. For example:
```
poetry run pytest -v demisto_sdk/commands/lint/tests/test_linter/
```

If you want to run with a specific python version (see the [demisto-sdk PyPi page](https://pypi.org/project/demisto-sdk/) for the current supported versions), use [poetry environments](https://python-poetry.org/docs/managing-environments/) to switch to a different env with a different python version.

---

### 7. Push changes to GitHub (Relevant only for External PRs)

The Demisto SDK is MIT Licensed and accepts contributions via GitHub pull requests.
If you are a first time GitHub contributor, please look at these links explaining on how to create a Pull Request to a GitHub repo:
* https://guides.github.com/activities/forking/
* https://help.github.com/articles/creating-a-pull-request-from-a-fork/

**Working on your first Pull Request?** You can learn how from this *free* series [How to Contribute to an Open Source Project on GitHub](https://egghead.io/courses/how-to-contribute-to-an-open-source-project-on-github)

---

### 8. Review Process
A member of the team will be assigned to review the pull request. Comments will be provided by the team member as the review process progresses.

You will see a few [GitHub Status Checks](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/about-status-checks) that help validate that your pull request is according to our standards:

* **ci/circleci: build**: We use [CircleCI](https://circleci.com/gh/demisto/demisto-sdk) to run a full build on each commit of your pull request. The build will run our content validation hooks, linting and unit test. We require that the build pass (green build). Follow the `details` link of the status to see the full build UI of CircleCI.
* **LGTM analysis: Python**: We use [LGTM](https://lgtm.com) for continues code analysis. If your PR introduces new LGTM alerts, the LGTM bot will add a comment with links for more details. Usually, these alerts are valid and you should try to fix them. If the alert is a false positive, specify this in a comment of the PR.
* **license/cla**: Status check that all contributors have signed our contributor license agreement (see below).

---

### 9. Contributor License Agreement (Relevant only for External PRs)

Before merging any PRs, we need all contributors to sign a contributor license agreement. By signing a contributor license agreement, we ensure that the community is free to use your contributions.

When you contribute a new pull request, a bot will evaluate whether you have signed the CLA. If required, the bot will comment on the pull request, including a link to accept the agreement. The CLA document is available for review as a [PDF](docs/cla.pdf).

If the `license/cla` status check remains on *Pending*, even though all contributors have accepted the CLA, you can recheck the CLA status by visiting the following link (replace **[PRID]** with the ID of your PR): https://cla-assistant.io/check/demisto/demisto-sdk?pullRequest=[PRID] .

---

If you have a suggestion or an opportunity for improvement that you've identified, please open an issue in this repo.
Enjoy and feel free to reach out to us on the [DFIR Community Slack channel](http://go.demisto.com/join-our-slack-community), or at [info@demisto.com](mailto:info@demisto.com).

repository: demisto/demisto-sdk

repo_name: demisto/demisto-sdk


text:
##Trouble shooting for  mexBBFMM2D
==========
####__mexBBFMM2D__ has been tested on the following platform:

- OS X Yosemite (10.10.5) with MATLAB R2015b
- Windows 7 with MATLAB R2014b

Report any additional issues to<EMAIL_ADDRESS>if the error you've got is not covered in this trouble shooting guide.

####Understanding your error messages
See [here](http://www.mathworks.com/help/matlab/matlab_external/understanding-mex-file-problems.html) for a general guide for MEX troubleshooting.
- Can you compile and run the `arraySize.c` example? If no check out if your compiler is supported by MATLAB, see question __How do I find the correct C/C++ compiler__.
- Can you compile and run the `compilemex.m`? If you have no trouble running `arraySize.c` but have trouble run `compilemex.m` shoot us an email

####How do I find the correct C/C++ compiler?
See [here](http://www.mathworks.com/support/sysreq/previous_releases.html) for a list of supported C/C++ compiler for different MATLAB version. Type `mex.getCompilerConfigurations` to get details of your compilers.

__Microsoft Windows SDK 7.1__ is a free compiler supported by most MATLAB version and across platform. If you have trouble installing SDK 7.1, or have trouble running it on Windows see [here](http://www.mathworks.com/matlabcentral/answers/95039-why-does-the-sdk-7-1-installation-fail-with-an-installation-failed-message-on-my-windows-system)

###Errors related to SDK compiler
#### __For Mac:__ If you get an error saying that SDK files are missing, e.g.,

```
Looking for folder '/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk' ...No.
```

you can find the sdk files here https://github.com/phracker/MacOSX-SDKs/releases. Download those that are missing and place them in the appropriate directories based on the error message you get.

#### __For PC:__ If you get an error related to 'ammintrin.h':
```
Building with 'Microsoft Windows SDK 7.1 (C++)'.
Error using mex
mexFMM2D.cpp
c:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\INCLUDE\intrin.h(26) : fatal error C1083: Cannot open
include file: 'ammintrin.h': No such file or directory

Error in make (line 38)
mex('-O','mexFMM2D.cpp',src1,src2,src3,'-largeArrayDims',['-I',eigenDIR],['-I',fmmDIR],'-output',filename)

Error in compilemex (line 5)
make(r,kernel,outputfile);
```
See [here](http://www.mathworks.com/matlabcentral/answers/90383-fix-problem-when-mex-cpp-file) or copy `ammintrin.h` from elsewhere in your computer (usually you will have multiple versions of `ammintrih.h`) and put it in the directory shown up in the error message, e.g., `c:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\INCLUDE\`

#### Error related to "mex -largeArrayDims"

mexBBFMM2D package use `mex -largeArrayDims`. `largeArrayDims` is a MEX flag that add after MATLAB version 7.3., see more details [here](http://www.mathworks.com/matlabcentral/answers/99144-how-do-i-update-mex-files-to-use-the-large-array-handling-api-largearraydims)


text:
Installation
============

A quick step to install Tuum framework.

Quick Step
---

Use starter repository on gitHub and composer to install Tuum framework.

```sh
git clone https://github.com/TuumPHP/tuum
cd tuum
composer install
```

> please make the ```var/``` directory writable to the server.

To use PHP's internal server,

```
cd public
php -S localhost:8888 index.php
```

and access http://localhost:8888 in a browser.

Directories
-----

Installation process will produce 4 directories as;

*   app/ : configuration and application scripts.
*   public/ : web public directory.
*   src/ : classes for your application.
*   var/ : to store data, log, caches, etc. that are not version controlled.
*   vendor/ : composer's installation directory.

repository: TuumPHP/tuum

repo_name: TuumPHP/tuum


text:
# Arfaxad

Arfaxad is a song lyric projection program, developed primarily to be a useful tool for churches.

## Design goals

* Songs should be stored in a format which is suited for version control.
* Everything should be accessible quickly via keyboard, which is the expected peripheral of choice for power users.
  In particular, with practice it should be possible to jump to any slide in the current song with minimal keystrokes.
* Mouse interaction should also be supported for casual users.

## Configuration

Arfaxad supports multiple profiles, which can be useful if the same computer is shared by people who use different
localisations, or if you want to have different song directories for meetings in English and Spanish. (Currently
there's no direct support for sharing songs between profiles, so that requires manual handling via symlinks).

To find the profiles, it looks in sequence at `/etc/arfaxad.conf`, `./arfaxad.conf`, and `~/.arfaxad/arfaxad.conf`.
(The second of those is a nod at Windows, although I'm sure the Windows support could be more idiomatic).
In each location it parses the file for a line like

    directory.profiles=~/.arfaxad/profiles

If none of the files exists, that value (`~/.arfaxad/profiles`) is the default.

It then looks in the named directory for files which can be parsed as a list of `key=value` pairs.
The supported keys are

* `name`: the name of the profile
* `directory.songs`: the directory from which to load songs
* `logo`: the path of the logo image
* `localisation`: the locale to use (e.g. `en-GB`, `es`, etc.)
* `log`: the path for the copyright log

This currently needs to be set up manually.

## Song markup

Songs are divided into slides, and there are various types of slide corresponding to the typical structure of a song.
By correctly identifying the slides you make it easy to jump to the correct one.
The four primary slide types are `Verse`, `Pre-chorus`, `Chorus`, and `Bridge`. There's also a general-purpose `Slide`,
but that doesn't support quick jumping.

When entering a song you should type the slide type before the slide on a single line with no whitespace. E.g.

The `Slide` type is for use when a single verse or chorus is too large for one slide and you want to split it in two
without affecting the numbering.

There isn't much markup supported within a slide, but you can put text in italics by wrapping it in `[i]...[/i]`
and in superscript by wrapping it in `[sup]...[/sup]`.

When a song is displayed, the font will be sized automatically. In the editor window, lines which are too long to
show at maximum size will be in a shade of blue, and lines which force the use of a font size smaller than the
(currently hard-coded) ideal minimum will be in a shade of red. This allows you to identify the line which is
limiting the font size. If the limit is vertical (due to the number of lines in a slide) then the slide type line
will be coloured thus instead.

## History

The original Arfaxad was written in January 2008 to replace an awful system which used a PowerPoint file per song.
The source was in Spanish. Prior to uploading it to GitHub, everything has been renamed to be in English; this is
one of the main reasons for adding it en masse without attempting to preserve the previous versioning.


text:
# Jest Snapshot Testing
When dealing with small presentational components, it's often sufficient to just take a snapshot of the HTML rendered with different props passed in. If there isn't any user interaciton with the component this type of testing will often get you 100% test coverage.

The general idea is that once the snapshot is generated, any future changes that affect the render of the HTML will cause a test failure that must be reviewed by the developer that caused the discrepency.

When dealing with Components that have a lot of non-primitive children, Jest snapshot tests are often not practical. When this is the case, it's best to do a shallow test using [enzyme](../enzyme/Overview.md).

# What should I use it for?
- Simple presentational components
- Test cases that don't require event handlers

# What should I not use it for?
- Components that have a deep component tree
- Test cases involving event handlers
- Lifecycle method tests

# Examples

## Example 1: No logic

Below we have a simple stateless component that required two props, a pick-up location, and a drop-off location. A single Jest snapshot test would be sufficient to get 100% coverage.

### Component Code
```jsx
// LocationInfo.js
import React from 'react'
import PropTypes from 'prop-types'
import { Text, Box, Flex } from 'pcln-design-system'

const propTypes = {
  pickUpLocation: PropTypes.string.isRequired,
  dropOffLocation: PropTypes.string.isRequired
}

const LocationInfo = (props) => {
  const {
    pickUpLocation,
    dropOffLocation
  } = props

  return (
    <Flex>
      <Box width={6 / 11}>
        <Text caps bold fontSize={0}>Pick-up</Text>
        <Text color='darkGray' fontSize={0}>
          {pickUpLocation}
        </Text>
      </Box>
      <Box width={5 / 11} pl={[0, 2]}>
        <Text caps bold fontSize={0}>Drop-off</Text>
        <Text color='darkGray' fontSize={0}>
          {dropOffLocation}
        </Text>
      </Box>
    </Flex>
  )
}

LocationInfo.propTypes = propTypes

export default LocationInfo

```

### Test Code
```jsx
// LocationInfo.spec.js
import React from 'react'
import renderer from 'react-test-renderer'
import LocationInfo from './LocationInfo'

i18next.init()

describe('CounterType', () => {
  it('should render the pick up and drop off locations', () => {
    // `renderer.create().toJSON()` will generate a JSON representation
    // of the component that will be used as output for the snapshot.
    // Simply put the JSX invocation of the component you wish
    // to test as the argument to the `.create()` method.
    const test = renderer.create(
      <LocationInfo
        pickUpLocation='Portland International Airport (PDX)'
        dropOffLocation='The Moon (MUN)' />
    ).toJSON()

    // Here is the assertion where we check if the snapshots match.
    // If no snapshot exists, once is generated and you should review
    // the generated snapshot to make sure it looks as you would expect.
    expect(test).toMatchSnapshot()
  })
})
```

## Example 2: A little bit of logic

This time, the drop-off location is optional, and if it's not present we're going to
display 'Same as Pickup'. In this case, we need two different tests in order to get 100% coverage.

```jsx
// LocationInfo.js
import React from 'react'
import PropTypes from 'prop-types'
import { Text, Box, Flex } from 'pcln-design-system'

const propTypes = {
  pickUpLocation: PropTypes.string.isRequired,
  dropOffLocation: PropTypes.string
}

const isOneWay = pickUpLocation !== dropOffLocation

const LocationInfo = (props) => {
  const {
    pickUpLocation,
    dropOffLocation
  } = props

  return (
    <Flex>
      <Box width={6 / 11}>
        <Text caps bold fontSize={0}>Pick-up</Text>
        <Text color='darkGray' fontSize={0}>{pickUpLocation}</Text>
      </Box>
      <Box width={5 / 11} pl={[0, 2]}>
        <Text caps bold fontSize={0}>Drop-off</Text>
        <Text color='darkGray' fontSize={0}>
        {/* Now there is some logic in the JSX that we need to test. */}
        {(isOneWay && dropOffLocation) || 'Same as Pickup'}
        </Text>
      </Box>
    </Flex>
  )
}

LocationInfo.propTypes = propTypes

export default LocationInfo

```

### Test Code

Now we need two test cases, one in which we have a drop-off location, and, since drop-off location is now optional, one without a drop-off location.

```jsx
// LocationInfo.spec.js
import React from 'react'
import renderer from 'react-test-renderer'
import LocationInfo from './LocationInfo'

i18next.init()

describe('CounterType', () => {
  it('should render with no drop off location', () => {
    const test = renderer.create(
      <LocationInfo pickUpLocation='Portland International Airport (PDX)' />
    ).toJSON()
    expect(test).toMatchSnapshot()
  })

  it('should render with with a drop off location provided', () => {
    const test = renderer.create(
      <LocationInfo
        pickUpLocation='Portland International Airport (PDX)'
        dropOffLocation='The Moon (MUN)' />
    ).toJSON()
    expect(test).toMatchSnapshot()
  })
})
```

repository: byrekt/react-testing-notes

repo_name: byrekt/react-testing-notes


text:
# Async Closure

Alter the function below to perform as expected, with each console statement printing i as it increments from 0 to 4. Currently, the function logs the number 5, five times.

Not working function:
```javascript
var delayedConsole = function() {
    var iTest = [];
    for (var i = 0; i < 5; i++) {
        setTimeout(function() {
            console.log(i);
            iTest.push(i);
        }, 1000);
    }
};
delayedConsole();
```

repository: kevinhamiltonsmith/code-challenges

repo_name: kevinhamiltonsmith/code-challenges


text:
# TreeWalker property handlers

Simple handlers to access prefixed properties via [TreeWalker](https://github.com/burdiuz/js-tree-walker) wrappers.

### Demo
Demo is available at [jsfiddle.net](https://jsfiddle.net/actualwave/6kw7z4xj/).

repository: burdiuz/js-walker-property-handlers

repo_name: burdiuz/js-walker-property-handlers


text:
---
id: react-relay-upload-s3
title: React Relay Upload S3
---

# [React Relay Upload S3](https://github.com/morrys/react-relay-appsync)
Middleware for Relay Modern Network Layer for upload file to AWS S3

## Installation

Install react-relay-upload-s3 using yarn or npm:

```
yarn add react-relay-upload-s3
```

## Usage

How to create the RelayNetworkLayer

```typescript
import {uploadS3Middleware} from 'react-relay-upload-s3';
```

```typescript
const network = new RelayNetworkLayer(
  [
    urlMiddleware(...),
    uploadS3Middleware({credentials: complexObjectsCredentials}),
    authMiddleware(...),
  ],
  {}
);
```

How to use in commitMutation

```typescript

    //single file
    const file:any = {
      bucket: bucket,
      key: key,
      region: region,
      file: selectedFile
    };

    commitMutation(
        ...
        uploadables: {
          file
        },
    );

    //multiple files
    const file1:any = {
      bucket: bucket,
      key: key1,
      region: region,
      file: selectedFile1
    };

    const file2:any = {
      bucket: bucket,
      key: key2,
      region: region,
      file: selectedFile2
    };

    commitMutation(
        ...
        uploadables: {
          file1,
          file2
        },
    );
```

repository: morrys/react-relay-appsync

repo_name: morrys/react-relay-appsync


text:
# Status
[![Project Status: Unsupported – The project has reached a stable, usable state but the author(s) have ceased all work on it. A new maintainer may be desired.](https://www.repostatus.org/badges/latest/unsupported.svg)](https://www.repostatus.org/#unsupported)

# ui-loadscript-viewer
An extension object for viewing (not editing) a Qlik Sense load script in a published app.

The Load Script Viewer is a simple extension that displays the load script of a Qlik Sense application without having to go into the data load editor.  The extension is read-only and does not allow copying or pasting.  It does **NOT** write back to the load script of an app.  It's meant to give developers an easy way to look at a script without lots of clicks.  And... theming!

### Screenshots

![Extension Props](https://github.com/eapowertools/ui-loadscript-viewer/wiki/imgs/extensionDesc.png)

![Extension Screenshot](https://github.com/eapowertools/ui-loadscript-viewer/wiki/imgs/loadscriptViewer.png)

### Installation
To install the load script viewer, **[download the zip file from here](https://github.com/eapowertools/ui-loadscript-viewer/blob/master/ui-loadscript-viewer/build/latest/ui-loadscript-viewer.zip)**.

Upload the zip file to Qlik Sense Server through the QMC or unzip and place in the extensions folder of Qlik Sense Desktop (located in My Documents\Qlik\Sense).

Happy Script Viewing!

### License
[MIT](https://github.com/eapowertools/ui-loadscript-viewer/blob/master/LICENSE)


text:
# Initials-avatar [![Build Status](https://travis-ci.org/freshbooks/initials-avatar.svg?branch=master)](https://travis-ci.org/freshbooks/initials-avatar)

An Ember CLI Addon that generates an avatar based on the initials of someone
with a first and last name.

## Usage

Initials-avatar is intended to be a "default" avatar when an actual image is not
present.

If neither first or last names are present, a single initial for the company
will be displayed:

```hbs
{{initials-avatar
  firstName=userGivenName
  lastName=userFamilyName
  company=userCompany
  email=userEmail
  image=userProfileImageUrl
}}
```

There are also color classes that you can leverage to control the styling of
your different initials avatars:

```hbs
{{initials-avatar
  firstName=userGivenName
  lastName=userFamilyName
  company=userCompany
  email=userEmail
  image=userProfileImageUrl
  colorIndex=userid
  maxColorIndex=3 {{!-- you only have 3 color classes defined --}}
}}
```

## Installation

* `git clone` this repository
* `npm install`
* `bower install`

## Running

* `ember server`
* Visit your app at http://localhost:4200.

## Running Tests

* `ember test`
* `ember test --server`

## Building

* `ember build`

For more information on using ember-cli, visit [http://www.ember-cli.com/](http://www.ember-cli.com/).

repository: calvinlough/initials-avatar

repo_name: calvinlough/initials-avatar


text:
## Sample realFB Prototype
<hr >

[![image](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT)
![GitHub repo size](https://img.shields.io/github/repo-size/OkomoJacob/realFB?color=green-yellow&logo=github&logoColor=blue) ![GitHub language count](https://img.shields.io/github/languages/count/OkomoJacob/realFB?logo=visual-studio-code) ![GitHub last commit](https://img.shields.io/github/last-commit/OkomoJacob/realFB?style=plastic&color=brightgreen)
![Forks](https://img.shields.io/github/forks/OkomoJacob/realFB?style=social) ![Hackage-Deps](https://img.shields.io/hackage-deps/v/lens) ![GitHub top language](https://img.shields.io/github/languages/top/okomojacob/realFB)

#### Find Me On Twitter
[![image](https://img.shields.io/twitter/follow/okomojacob?style=social)](https://twitter.com/okomojacob)

Building my own Social Media Platform, from Scratch
#### Tech tracks, tools used in this Build
 - [React](https://reactjs.org/) + [React HOOKs](https://reactjs.org/docs/hooks-intro.html)
 - [React context API](https://reactjs.org/docs/context.html) this will be used to capture the usr's Details when they login -> REDUX Pattern
 - [MATERIAL UI](https://material-ui.com/) -For nice and cool icons
 - [FLEXBOX](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Flexible_Box_Layout/Basic_Concepts_of_Flexbox) -To make our whole design responsive, The Flexible Box Module, designed as a method that could offer space distribution between items in an interface and powerful alignment capabilities.
 - [Firebase's Firestore](https://firebase.google.com/docs/firestore) Realtime DB
 - [Firebase Hosting platform](https://firebase.google.com/docs/firestore)
 - [Firebase Google Authentication](https://firebase.google.com/docs/auth) (FULL LOGIN)
 - [React Flip Move](https://joshwcomeau.github.io/react-flip-move/examples/#/?_k=3qe4wa) - For animations
 - [IFrames](https://medium.com/@ryanseddon/rendering-to-iframes-in-react-d1cb92274f86) - For Live Feed data rendering and dynamic display of Data in Realtime.

### Builds and Commands
`npx create-react-app realFB` To create your new react aapp.

repository: OkomoJacob/realFB

repo_name: OkomoJacob/realFB


text:
# Raygun4Xamarin-samples

## Raygun4Xamarin.Forms Sample App

A sample Xamarin Forms (4.0) application integrated with the Raygun4Xamarin.Forms provider.

# Raygun4Xamarin.Forms provider

## Where is my app API key?
When sending exceptions to the Raygun service, an app API key is required to map the messages to your application.

When you create a new application in your Raygun dashboard, your app API key is displayed within the instructions page. You can also find the API key by clicking the "Application Settings" button in the side bar of the Raygun dashboard.

## Installation

The provider targets .NET Standard 2.0 and is available through NuGet packages, found [here](https://www.nuget.org/packages/raygun4xamarin.forms/).

The currently supported platforms are Android and iOS with the following versions or newer:

 * Xamarin.Android 8.0
 * Xamarin.iOS 10.0

## Initialize RaygunClient

In the constructor of the `App` class in your base project, call the static `RaygunClient.Init()` method with your app API key. Using the static `Init` method will ensure a shared `RaygunClient` instance is available through the static property `Current`.

In `App.xaml.cs:`

``` csharp
public partial class App : Application
{
  public App()
  {
    InitializeComponent();

    // Initialising the Raygun client
    RaygunClient.Init("YOUR_API_KEY");

    // Enable Raygun Products
    RaygunClient.Current.EnableCrashReporting();
    RaygunClient.Current.EnableRealUserMonitoring();

    // Remaining application setup logic
    MainPage = new MainPage();
  }
}
```

## Configure Raygun for your platform

Each platform being targeted requires an additional configuration step using the `RaygunPlatform` class in the following places.

### For Android:

In `MainActivity.cs:`

``` csharp
public class MainActivity : global::Xamarin.Forms.Platform.Android.FormsAppCompatActivity
{
  protected override void OnCreate(Bundle savedInstanceState)
  {
    // MainActivity startup logic
    base.OnCreate(savedInstanceState);
    global::Xamarin.Forms.Forms.Init(this, savedInstanceState);
    LoadApplication(new App());

    // Configure Raygun for the current platform
    RaygunPlatform.Configure(this);
  }
}
```

**Android Troubleshooting**

You may need to install the `Xamarin.Android.Support.LocalBroadcastManager` package if you are having troubles getting Raygun working in your Android project.
You may also need to set the minimum SDK version of your project to Android 9.

### For iOS:

In `AppDelegate.cs:`

``` csharp
public partial class AppDelegate : global::Xamarin.Forms.Platform.iOS.FormsApplicationDelegate
{
  public override bool FinishedLaunching(UIApplication app, NSDictionary options)
  {
    // AppDelegate startup logic
    global::Xamarin.Forms.Forms.Init();
    LoadApplication(new App());

    // Configure Raygun for the current platform
    RaygunPlatform.Configure();

    return base.FinishedLaunching(app, options);
  }
}
```

See the [Raygun4Xamarin](https://github.com/MindscapeHQ/raygun4xamarin) repository for more details on using this provider.

gha_language: C#


text:
# Log sink for inclusion in SCDF stream

## Prior to running the build on this project, do the following:
1. in `../twitter/`, ensure you have pushed the twitter app (e.g. `cf push` in that directory)
1. Edit `../twitter/scripts/cf_create_twitter_service.sh` as required, then run that
1. Once that service is created, bind it to a running app, so you can run `cf env [that app name]` to get the `VCAP_SERVICES`
   value out, and store that in an environment variable (`VCAP_SERVICES`)
1. After you're deployed the SCDF stream where this `offer-sink` app is a sink:
* Bind the app to the delivery service `cf bs dataflow-server-hf30QYI-socialmedia-offer-sink twitter-service`
* Restage the app so that binding takes effect `cf restage dataflow-server-hf30QYI-socialmedia-offer-sink`

## TODO
Remove the Twitter specific parts of this, as it doesn't currently handle the Twitter interactions.

repository: lulzzz/oss-pcf-gcp-retail-demo

repo_name: lulzzz/oss-pcf-gcp-retail-demo