text:
> [Go to French version](/fr/Règlements/Décrets,%20ordonnances%20et%20règlements%20statutaires/2002/164.md)

# National Capital Commission Animal Regulations

**SOR/2002-164**

Enabling authorities:
- [NATIONAL CAPITAL ACT](/en/Acts/Revised%20Statutes%20of%20Canada/N/N-4.md)

Date registered: 25 April 2002

----------

Her Excellency the Governor General in Council, on the recommendation of the Minister of Canadian Heritage, pursuant to subsection 20(1) of the [National Capital Act](/en/Acts/Revised%20Statutes%20of%20Canada/N/N-4.md), hereby makes the annexed National Capital Commission Animal Regulations.

## Interpretation

**1** The following definitions apply in these Regulations.

***Capital Pathway*** means a mixed use recreational pathway on Commission land that has a paved or stone dust surface and has been marked by the Commission at access points maintained by the Commission and at intersections with signs or surface markings bearing the pictogram in the form set out in Schedule 2. (*sentier de la capitale*)

***Commission land*** means real property or immovables owned by the Commission or under the control and management of the Commission. (*terrain de la Commission*)

***domestic animal*** means an animal of a species of vertebrates, other than fish, that has been domesticated by humans so as to live in a tame condition and depend on humans for survival. (*animal domestique*)

***keeper*** means the owner of an animal or the person having charge of the animal, except where the owner or the person is a minor, in which case ***keeper*** means the father or mother of the minor or another adult responsible for the minor. (*responsable*)

***leased agricultural property*** means Commission land, of which the Commission is the lessor, that is leased for commercial or non-commercial agricultural purposes, and includes any residence on the land. (*propriété agricole louée*)

***leased land*** means leased agricultural property or leased residential property. (*terrain loué*)

***leased residential property*** means Commission land, of which the Commission is the lessor, that is leased strictly for residential purposes. (*propriété résidentielle louée*)

***off-leash area*** means an area on unleased land referred to in section 9. (*aire pour animaux en liberté*)

***organized event*** means a temporary activity or a seasonal program that is organized or authorized by the Commission. (*événement organisé*)

***peace officer*** means
- **(a)** a member of the Royal Canadian Mounted Police who is a peace officer;
- **(b)** a person who is employed by the Commission as a conservation officer and who has been designated as a peace officer under paragraph 7(1)(d) of the [Royal Canadian Mounted Police Act](/en/Acts/Revised%20Statutes%20of%20Canada/R/R-10.md); or
- **(c)** a police officer of the municipality in which the Commission land is situated. (*agent de la paix*)

***picnic area*** means an area that contains a group of picnic tables that are permanently affixed or chained to the ground, or that is identified by signs as a picnic area. (*terrain de pique-nique*)

***shoreline*** means the high-water mark. (*ligne de rive*)

***trail*** means a mixed use trail, other than a Capital Pathway, on Commission land that has been marked by the Commission at entry points and intersections with signs bearing the trail name or number or a pictogram. (*sentier*)

***unleased land*** means Commission land that is not subject to a lease between the Commission as lessor and another party as lessee. (*terrain non loué*)

## Application

**2** These Regulations apply
- **(a)** on all unleased land; and
- **(b)** on all leased land that is subject to
	- **(i)** a lease entered into on or after the day on which these Regulations come into force that states that the lease is subject to these Regulations as amended from time to time, or
	- **(ii)** a lease that has been renewed or amended on or after the day on which these Regulations come into force that states that the lease, as renewed or amended, is subject to these Regulations as amended from time to time.

**3**

- **(1)** Sections 4 to 8 and subsection 10(2) do not apply to
	- **(a)** peace officers in the exercise of their duties;
	- **(b)** Commission employees in the exercise of their duties; or
	- **(c)** persons who are assisting a peace officer or a Commission employee in the exercise of the officer’s or employee’s duties.

- **(2)** Subsections 6(1) and (2), section 8 and paragraph 20(1)(a) do not apply to a blind or visually impaired keeper of a guide dog, or to a physically disabled keeper of an assistance dog, while they are being accompanied by that dog.

## Unleased Land — Prohibitions and Restrictions

### General

**4**

- **(1)** No person shall have an animal other than a domestic animal on unleased land.

- **(2)** No person shall have more than two domestic animals on unleased land at any one time.

- **(3)** The prohibition in subsection (1) shall not have the effect of preventing the Commission from having, on Commission lands, wildlife indigenous to those lands.

### Domestic Animals Other Than Hoofed Animals

**5** Sections 6 to 9 apply only to keepers of domestic animals other than hoofed animals.

**6**

- **(1)** Subject to subsection (2), no person shall have a domestic animal on unleased land except in the locations set out in Schedule 1.

- **(2)** In the locations set out in Schedule 1, no person shall have a domestic animal in any of the following areas:
	- **(a)** a beach and its immediate environs, the boundaries of which are clearly identified by signs;
	- **(b)** a building;
	- **(c)** the campground located at LeBreton Flats;
	- **(d)** a picnic area, food concession area or outdoor restaurant;
	- **(e)** a play structure area;
	- **(f)** subject to subsection (3), within three metres of the shoreline of a body of water of a permanent nature;
	- **(g)** an area in which an organized event is being held; or
	- **(h)** any area of unleased land that is marked, in accordance with subsection 27(1), by signs as an area where domestic animals are prohibited.

- **(3)** The prohibition contained in paragraph (2)(f) does not apply to the Queen Elizabeth Driveway corridor land or the Colonel By Drive corridor land.

- **(4)** No person shall have a domestic animal referred to in section 5 in any area of unleased land that is marked, in accordance with subsection 27(2), by signs as a location where hoofed animals are permitted.

- **(5)** Despite any other provision of these Regulations, the keeper of a domestic animal is authorized to cross, with their animal, any area of unleased land where such an animal is otherwise prohibited under these Regulations if the animal is restrained in accordance with subsection 7(1) and the animal is on a Capital Pathway or trail where the presence of that animal is permitted.

**7**

- **(1)** No person shall have a domestic animal on unleased land where domestic animals are permitted unless the animal is restrained in one of the following ways:
	- **(a)** subject to subsection (2), it is restrained on a leash or by the handle of a harness
		- **(i)** that is held by a person, or is securely attached to an object that cannot be displaced by the animal, and
		- **(ii)** that is not more than two metres (6.5 feet) long;
	- **(b)** it is in a container from which it cannot escape; or
	- **(c)** it is in a vehicle.

- **(2)** No person shall, on unleased land,
	- **(a)** ski, rollerskate or rollerblade while having a domestic animal on a leash; or
	- **(b)** ride a bicycle, scooter or any other non-motorized vehicle — other than a wheelchair — while having a domestic animal on a leash or while having a domestic animal attached in some manner to the vehicle.

**8** Every keeper of a domestic animal shall immediately pick up any fecal matter deposited by the animal and shall remove the matter from unleased land.

**9**

- **(1)** Despite any other provision of these Regulations, the keeper of a domestic animal may allow the animal to run free on a portion of unleased land that the Commission has marked by signs as an off-leash area.

- **(2)** The keeper of a domestic animal shall have the animal under control within the off-leash area.

- **(3)** For the purposes of subsection (2), the keeper of a domestic animal is considered to have the animal under control if the animal, following a voice command or hand signal given by the keeper, obeys immediately and, as the case may be,
	- **(a)** stops attacking or chasing another animal or a person;
	- **(b)** stops any display of aggression toward another animal or a person;
	- **(c)** stops any behaviour toward a person that a reasonable person would find harassing or disturbing; and
	- **(d)** comes to and stays with the keeper.

- **(4)** Despite any other provision of these Regulations, the keeper of a domestic animal is authorized, for the purpose of accessing an off-leash area, to cross, with their animal, any parking lot of the Commission adjacent to the area if the animal is restrained in accordance with subsection 7(1).

### Hoofed Animals

**10**

- **(1)** This section applies only to keepers of hoofed animals.

- **(2)** No person shall have a hoofed animal on any area of unleased land except in a location that the Commission has, in accordance with subsection 27(2), marked by signs as a location where hoofed animals are permitted.

- **(3)** No person shall have a hoofed animal in a location referred to in subsection (2) unless it is restrained in one of the following ways:
	- **(a)** it is restrained by reins that are held by a person;
	- **(b)** it is restrained by a lead
		- **(i)** that is held by a person, or is securely attached to an object that cannot be displaced by the animal, and
		- **(ii)** that is not more than two metres (6.5 feet) long; or
	- **(c)** it is in a container from which it cannot escape.

- **(4)** Despite any other provision of these Regulations, the keeper of a hoofed animal is authorized to cross, with their hoofed animal, any area of unleased land where a hoofed animal is otherwise prohibited under these Regulations if the animal is restrained in accordance with subsection (3) and the animal is on a trail where the presence of that animal is permitted.

### Domestic Animals

**11** Sections 12 to 14 apply to keepers of all domestic animals.

**12**

- **(1)** No person shall use a domestic animal in an organized event on unleased land without the authorization of the Commission under subsection 28(1).

- **(2)** No person shall use a domestic animal to pull a sled, wagon or other conveyance on unleased land except as part of an organized event in respect of which an authorization has been issued by the Commission under subsection 28(1).

**13** The keeper of a domestic animal shall not allow the animal, while on unleased land, to
- **(a)** chase, attack, bite or injure a person or another animal or fight with another animal;
- **(b)** damage property of the Commission;
- **(c)** make noise for more than 15 minutes between the hours of 10:00 p.m. and 7:00 a.m.; or
- **(d)** drink from, or get on or into, an ornamental or drinking fountain, or a body of water of a permanent nature surrounded by Commission land.

**14** The keeper of a domestic animal shall not, on unleased land, leave the animal unattended in a vehicle or container in excessive heat or cold that could endanger the health of the animal.

## Leased Land — Prohibitions and Restrictions

### General

**15**

- **(1)** No lessee shall have an animal other than a domestic animal on leased land.

- **(2)** The keeper of a domestic animal shall not allow the animal, while on leased land, to
	- **(a)** chase, attack, bite or injure a person or another animal or fight with another animal;
	- **(b)** damage property of the Commission; or
	- **(c)** enter any body of water of a permanent nature surrounded by Commission land or drink from that body of water.

- **(3)** The keeper of a domestic animal shall not, on leased land, leave the animal unattended in a vehicle or container in excessive heat or cold that could endanger the health of the animal.

- **(4)** The keeper of a domestic animal shall not, on leased land, have the animal within three metres of the shoreline of any body of water of a permanent nature.

### Leased Residential Property

**16** No person shall have a hoofed animal on leased residential property.

**17**

- **(1)** No lessee shall allow more than three domestic animals to be on the lessee’s leased residential property at one time, except if the additional animals are unweaned young of any of the three permitted animals.

- **(2)** No lessee shall allow a domestic animal that is on the lessee’s leased residential property to make noise for more than 15 minutes between the hours of 10:00 p.m. and 7:00 a.m.

- **(3)** Every lessee shall pick up and dispose of fecal matter deposited by a domestic animal on the lessee’s leased residential property.

**18** No person shall have a domestic animal on leased residential property unless it is restrained in one of the following ways:
- **(a)** it is in the residence;
- **(b)** it is restrained on a leash or by the handle of a harness
	- **(i)** that is held by a person, or is securely attached to an object that cannot be displaced by the animal, and
	- **(ii)** that is not more than two metres (6.5 feet) long;
- **(c)** it is in a container from which it cannot escape;
- **(d)** it is in an enclosure or behind a fence that is of a construction and dimensions sufficient to keep it within the limits of the property; or
- **(e)** it is in a location on the property controlled by an invisible electronic fencing system.

### Leased Agricultural Property

**19** A lessee of leased agricultural property who is the keeper of a domestic animal shall use effective measures to keep it within the limits of the property.

## Powers of Peace Officers

**20**

- **(1)** A peace officer shall order the keeper of an animal to remove the animal from Commission land if
	- **(a)** the animal is on Commission land in a location where the keeper is prohibited from having the animal without the authorization of the Commission under subsection 28(1) and the keeper has not obtained that authorization; or
	- **(b)** the peace officer believes, on reasonable grounds, that the animal is acting in a dangerous or destructive fashion.

- **(2)** Every person to whom an order is given under subsection (1) shall comply with that order.

**21**

- **(1)** A peace officer is authorized to capture an animal that is unrestrained on Commission land in contravention of these Regulations if the keeper of the animal is not present or is unable or unwilling to capture the animal.

- **(2)** When the keeper of the animal is not present, the peace officer is authorized to impound the animal at the expense of the owner.

- **(3)** When the keeper of the animal is present, the peace officer shall order the keeper
	- **(a)** in the case of a domestic animal, to restrain the animal as described in section 7 or 10, as applicable, or, if it is not possible to restrain the animal in such a fashion, to remove the animal from Commission land; and
	- **(b)** in the case of an animal other than a domestic animal, to remove the animal from Commission land.

- **(4)** Every person to whom an order is given under subsection (3) shall comply with that order.

**22**

- **(1)** Subject to subsection (3), a peace officer is authorized to take any injured animal that they find or capture pursuant to subsection 21(1) to a veterinarian for medical care at the expense of the owner.

- **(2)** Subject to subsection (3), if the peace officer believes, on reasonable grounds, that the animal is so severely injured that the most humane action would be to destroy the animal, the peace officer is authorized to destroy it.

- **(3)** Before taking any action under subsection (1) or (2), the peace officer shall
	- **(a)** if the keeper of the animal is not present, use reasonable efforts to locate the keeper; and
	- **(b)** if the keeper is present or is located, obtain their consent to the action proposed.

**23**

- **(1)** Subject to subsection (2), if, on unleased land, a peace officer finds an animal unattended in a vehicle or container in excessive heat or cold that could endanger the health of the animal, the peace officer is authorized to take reasonable measures to remove the animal from the vehicle or container.

- **(2)** Before taking any action under subsection (1), the peace officer shall
	- **(a)** use reasonable efforts to locate the keeper of the animal; and
	- **(b)** if the keeper is present or is located, obtain their consent to the action proposed.

- **(3)** When a peace officer removes an animal from a vehicle or container pursuant to subsection (1) and the keeper of the animal is not present, the peace officer is authorized to impound the animal at the expense of the owner.

**24**

- **(1)** After having taken all reasonable measures to stop the animal, a peace officer is authorized to destroy an animal that is attacking the peace officer or another person on Commission land if the peace officer believes, on reasonable grounds, that it would be too dangerous for the peace officer or the keeper of the animal, if present, to attempt to capture the animal.

- **(2)** After having taken all reasonable measures to stop the animal, a peace officer is authorized to destroy an animal that is attacking another animal on Commission land if the peace officer believes, on reasonable grounds, that
	- **(a)** the animal being attacked may suffer serious injury or death; and
	- **(b)** it would be too dangerous for the peace officer or the keeper of the animal, if present, to attempt to capture the animal.

**25**

- **(1)** Subject to subsection (2), after having taken all reasonable measures to stop the animal, a peace officer is authorized to destroy an animal that is at large on Commission land if the peace officer believes, on reasonable grounds, that
	- **(a)** the continued presence of the animal will
		- **(i)** damage property of the Commission, or
		- **(ii)** pose a threat to public safety; and
	- **(b)** it would be too dangerous for the peace officer to attempt to capture the animal.

- **(2)** Before destroying an animal under subsection (1), the peace officer shall use reasonable efforts to locate the keeper of the animal.

- **(3)** If the keeper of the animal is present or is located, the peace officer shall warn the keeper that the animal will be destroyed unless it is controlled or captured.

**26** When a peace officer impounds an animal, takes an animal to a veterinarian or destroys an animal pursuant to any of sections 21 to 25, the peace officer shall, as soon as possible, inform the owner of the animal of the peace officer’s actions, if the name and the address, phone number or other indicators of the whereabouts of the owner can be readily ascertained from
- **(a)** tags or other identification worn by the animal;
- **(b)** any tattoo or other marking on the animal; or
- **(c)** any other source of information readily available.

## Powers of the Commission

**27**

- **(1)** In locations on unleased land where domestic animals are otherwise permitted under these Regulations, the Commission may, by signs, mark an area where domestic animals are prohibited, if such a prohibition is necessary for reasons of public safety or for protection of property of the Commission.

- **(2)** In areas of unleased land where hoofed animals are not otherwise permitted under these Regulations, the Commission may, by signs, mark an area where hoofed animals are permitted, if the presence of hoofed animals does not pose a threat to public safety or to property of the Commission.

**28**

- **(1)** If the presence of an animal does not pose a threat to public safety or property of the Commission, the Commission shall, on application, issue a written authorization to a person to use the animal in an organized event on Commission land.

- **(2)** The keeper of an animal shall, while the animal is on Commission land pursuant to an authorization issued under subsection (1), control the animal at all times in accordance with the terms of the authorization.

**29**

- **(1)** An authorization issued pursuant to subsection 28(1) shall, at a minimum, specify the duration of the authorization, the description of Commission land to which the authorization applies and any special animal restraining measures or public health and safety requirements.

- **(2)** No person contravenes these Regulations by virtue only of the fact that the person does anything permitted in an authorization issued pursuant to subsection 28(1) while that authorization remains in effect.

- **(3)** An authorization issued pursuant to subsection 28(1) is no longer in effect if the person to whom it was issued fails to comply with any term or condition of the authorization.

## Penalties

**30** Every person who contravenes these Regulations is liable on summary conviction to a fine of not more than $500 or to imprisonment for a term of not more than six months, or to both.

## Coming into Force

**31** These Regulations come into force on the day on which they are registered.

### **SCHEDULE 1**
**(Subsections 6(1) and (2))**

**PART 1**
## Quebec

**DIVISION 1**
### Urban Lands

#### Parks

Brébeuf Park: Park within the boundaries of the City of Gatineau and bounded

**(a)** on the north by Boudria Street, Maricourt Street and Bourget Street;

**(b)** on the south by the Ottawa River;

**(c)** on the east by Hydro-Québec lands; and

**(d)** on the west by Moussette Park.

Des Chars de Combat Park: Park within the boundaries of the City of Gatineau and bounded

**(a)** on the north by parking lots and the baseball diamond immediately south of St-Jean-Bosco Street;

**(b)** on the south by the Salaberry Armoury parking lot;

**(c)** on the east by a fence and the Canadian Pacific railway line; and

**(d)** on the west by St-Joseph Boulevard.

Jacques Cartier Park: Park within the boundaries of the City of Gatineau and bounded

**(a)** on the north by Brewery Creek;

**(b)** on the south by the Alexandra Bridge and the western approach to the bridge;

**(c)** on the east by the Ottawa River; and

**(d)** on the west by Laurier Street, Dussault Street and Fournier Boulevard.

Leamy Lake Park: Park within the boundaries of the City of Gatineau and bounded

**(a)** on the north by the Gatineau River and a residential area;

**(b)** on the south by Brewery Creek;

**(c)** on the east by the Ottawa River; and

**(d)** on the west by the Casino du Lac-Leamy, de la Carrière Boulevard and Parc industriel Richelieu de Gatineau.

Montcalm Taché Park: Park within the boundaries of the City of Gatineau and bounded

**(a)** on the north by a stone wall;

**(b)** on the south by Alexandre-Taché Boulevard;

**(c)** on the east by Montcalm Street; and

**(d)** on the west by Brewery Creek.

Portageurs Park: Park within the boundaries of the City of Gatineau and bounded

**(a)** on the north by the Canadian Pacific railway line;

**(b)** on the south by the Ottawa River;

**(c)** on the east by the Domtar Inc. lands; and

**(d)** on the west by Hydro-Québec lands.

Sentier de l’île Park: Park within the boundaries of the City of Gatineau and bounded

**(a)** on the north and the south by a residential area;

**(b)** on the east by Laurier Street; and

**(c)** on the west by St-Rédempteur Street.

#### Corridor Lands

Lac des Fées Parkway corridor land: Land within the boundaries of the City of Gatineau, adjacent to and east of Lac des Fées Parkway and bounded

**(a)** on the north by Gamelin Street;

**(b)** on the south by Scott Street; and

**(c)** on the east by a residential area.

Philemon-Wright corridor land: Land within the boundaries of the City of Gatineau, adjacent to and on both sides of the Leamy Creek Pathway and bounded

**(a)** on the north by a residential area and Highway 5;

**(b)** on the south by a residential area and Parc industriel Richelieu de Gatineau;

**(c)** on the east by St-Joseph Boulevard; and

**(d)** on the west by Cité-des-Jeunes Boulevard.

Voyageurs corridor land/Des Rapides-Deschênes Park: Land within the boundaries of the City of Gatineau, adjacent to and on both sides of the Voyageurs Pathway and bounded

**(a)** on the north by Lucerne Boulevard and Brunet Boulevard;

**(b)** on the south by the Ottawa River;

**(c)** on the east by one of the City of Gatineau filtration plants; and

**(d)** on the west by Martel Street, Rosenes Street and Gibeault Street.

#### Capital Pathways

- De l’île Pathway
- Gatineau River Pathway
- Lac-des-Fées Pathway
- Leamy Creek Pathway
- Leamy Lake Pathway
- Pionniers Pathway
- Ruisseau-de-la-Brasserie Pathway
- Voyageurs Pathway

#### Sidewalks

- Champlain Bridge sidewalk: Sidewalk within the boundaries of the City of Gatineau on the east and west sides of the Champlain Bridge, including its northern approaches.
- Confederation Boulevard Esplanade: Sidewalk on the south and east sides of Laurier Street within the boundaries of the City of Gatineau from the Portage Bridge to the Alexandra Bridge including the boardwalk on the south side of the Alexandra Bridge in the City of Gatineau.
- Portage Bridge sidewalk: Sidewalk within the boundaries of the City of Gatineau on the east and west sides of the Portage Bridge, including its northern approaches.

**DIVISION 2**
### Gatineau Park

#### Access from April 15 to November 30

##### Trails

- Champlain Trail
- Hanggliding Trail
- Hickory Trail
- Lac des Fées Trail
- Lusk Cave Trail
- Wolf Trail
- Trails 1, 1B, 2, 3, 4, 5, 6, 7, 8, 9, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 24, 25, 26, 28, 29, 30, 31, 32, 33, 34, 35, 36, 38, 40, 50, 51, 52, 53, 54, 55, 56, 57 and 58

##### Capital Pathway

- Gatineau Park Pathway

##### Corridor Lands

(Corridor lands are mown strips of land adjacent to and on both sides of the parkways or roads to which reference is made.)

- Champlain Parkway corridor land
- Fortune Parkway corridor land
- Gatineau Parkway corridor land
- Lac La Pêche Road corridor land
- Lac Philippe Parkway corridor land
- Lac Taylor Road corridor land
- Pointe Pellerin Road corridor land

##### Other Site

- Mackenzie King Estate

#### Year-round Access

##### Trails

- Larriault Trail/Waterfall Trail
- Pionniers Trail
- Sugarbush Trail

**PART 2**
## Ontario

**DIVISION 1**
### Urban Lands

#### Parks

Commissioner’s Park: Land within the boundaries of the City of Ottawa and bounded

**(a)** on the north by Carling Avenue;

**(b)** on the south by Queen Elizabeth Driveway corridor land;

**(c)** on the east by Lakeview Terrace and Opeongo Road; and

**(d)** on the west by Preston Street.

Confederation Park: Land within the boundaries of the City of Ottawa and bounded

**(a)** on the north by the western approaches to the Mackenzie King Bridge;

**(b)** on the south by Laurier Avenue and the western approaches to the Laurier Avenue Bridge;

**(c)** on the east by Queen Elizabeth Driveway corridor land; and

**(d)** on the west by Elgin Street.

Garden of the Provinces: Land within the boundaries of the City of Ottawa and bounded

**(a)** on the north by Wellington Street;

**(b)** on the south by the Sparks Street escarpment;

**(c)** on the east by Bay Street; and

**(d)** on the west by Wellington Street.

Hampton Park: Land within the boundaries of the City of Ottawa and bounded

**(a)** on the north by a residential area;

**(b)** on the south by the Queensway;

**(c)** on the east by Island Park Drive corridor land; and

**(d)** on the west by a residential area.

Hog’s Back Park: Land within the boundaries of the City of Ottawa and bounded

**(a)** on the north by Heron Road;

**(b)** on the south by Hog’s Back Road;

**(c)** on the east by Riverside Drive; and

**(d)** on the west by Hog’s Back Falls and the Rideau River.

King Edward Park: Land within the boundaries of the City of Ottawa and bounded

**(a)** on the north by the Minto Bridges;

**(b)** on the south by Cathcart Street;

**(c)** on the east by the Rideau River; and

**(d)** on the west by King Edward Avenue.

Kingsview Park: Land within the boundaries of the City of Ottawa and bounded

**(a)** on the north by Beechwood Avenue and Vanier Parkway;

**(b)** on the south by Montreal Road;

**(c)** on the east by River Road; and

**(d)** on the west by the Rideau River.

Linear Park: Land within the boundaries of the City of Ottawa and bounded

**(a)** on the north by Young Street;

**(b)** on the south by Carling Avenue;

**(c)** on the east by a residential area; and

**(d)** on the west by the Canadian Pacific railway line.

Major’s Hill Park: Land within the boundaries of the City of Ottawa and bounded

**(a)** on the north by St. Patrick Street and the eastern approach to the Alexandra Bridge;

**(b)** on the south by the Château Laurier;

**(c)** on the east by Mackenzie Avenue; and

**(d)** on the west by the Rideau Canal and the Ottawa River.

Rideau Falls Park: Land within the boundaries of the City of Ottawa and bounded

**(a)** on the north by John Street;

**(b)** on the south by the National Research Council lands;

**(c)** on the east by Sussex Drive; and

**(d)** on the west by the Ottawa River.

River Road Park: Land within the boundaries of the City of Ottawa and bounded

**(a)** on the north by Donald Street;

**(b)** on the south by the Queensway;

**(c)** on the east by River Road; and

**(d)** on the west by the Rideau River.

Rockcliffe Park: Land within the boundaries of the City of Ottawa and bounded

**(a)** on the north by Teahouse Road;

**(b)** on the south by Princess Road;

**(c)** on the east by Lisgar Road; and

**(d)** on the west by the Ottawa River.

Stanley Park: Land within the boundaries of the City of Ottawa and bounded

**(a)** on the north by Stanley Avenue;

**(b)** on the south by the Rideau River;

**(c)** on the east by New Edinburgh Park; and

**(d)** on the west by Sussex Drive.

#### Corridor Lands

Aviation Parkway corridor land: Land within the boundaries of the City of Ottawa, adjacent to and on both sides of the Aviation Parkway, and bounded

**(a)** on the north by the Rockcliffe Parkway;

**(b)** on the south by the Queensway; and

**(c)** on the east and west by a residential area.

Colonel By Drive corridor land: Land within the boundaries of the City of Ottawa, adjacent to and on both sides of Colonel By Drive, and bounded

**(a)** on the north by Sussex Drive and DND Road;

**(b)** on the south by Hog’s Back Road;

**(c)** on the east by the Rideau Centre, the National Defence Headquarters, Nicholas Street, a residential area, Carleton University and the Rideau River; and

**(d)** on the west by the Rideau Canal.

Island Park Drive corridor land: Land within the boundaries of the City of Ottawa, adjacent to and on both sides of Island Park Drive, and bounded

**(a)** on the north by the Ottawa River Parkway corridor land;

**(b)** on the south by Carling Avenue; and

**(c)** on the east and west by a residential area.

Ottawa River Parkway corridor land: Land within the boundaries of the City of Ottawa, adjacent to and on both sides of the Ottawa River Parkway, and bounded

**(a)** on the north by the Ottawa River;

**(b)** on the south by LeBreton Flats, Tunney’s Pasture and a residential area;

**(c)** on the east by the Portage Bridge; and

**(d)** on the west by Carling Avenue.

Patterson Creek corridor land: Land within the boundaries of the City of Ottawa, adjacent to and on both sides of Patterson Creek, and bounded

**(a)** on the north by Linden Terrace;

**(b)** on the south by a residential area;

**(c)** on the east by Queen Elizabeth Driveway corridor land; and

**(d)** on the west by O’Connor Street.

Queen Elizabeth Driveway corridor land: Land within the boundaries of the City of Ottawa, adjacent to and on both sides of Queen Elizabeth Driveway, and bounded

**(a)** on the north by the National Arts Centre;

**(b)** on the south by Preston Street;

**(c)** on the east by the Rideau Canal; and

**(d)** on the west by Confederation Park, the Cartier Street Drill Hall, Lisgar Collegiate Institute, Lansdowne Park, Commissioner’s Park and a residential area.

Rockcliffe Parkway corridor land: Land within the boundaries of the City of Ottawa, adjacent to and on both sides of the Rockcliffe Parkway, and bounded

**(a)** on the north by the Ottawa River;

**(b)** on the south by a residential area, the Royal Canadian Mounted Police Training Centre, the Terry Fox Centre, the National Aeronautical Collection, a residential area, a sewage disposal plant and Green’s Creek Conservation Area;

**(c)** on the east by St. Joseph Boulevard; and

**(d)** on the west by Rockcliffe Park.

South-West Transitway corridor land: Land within the boundaries of the City of Ottawa, adjacent to and on both sides of the Pinecrest Creek Pathway, and bounded

**(a)** on the north by Carling Avenue;

**(b)** on the south by the Canadian Pacific railway line;

**(c)** on the east by a residential area and Woodroffe Avenue; and

**(d)** on the west by a residential area.

#### Other Sites

Albion Road lands: Lands within the boundaries of the City of Ottawa and bounded

**(a)** on the north by Walkley Road;

**(b)** on the south by Kitchener Avenue;

**(c)** on the east by Albion Road; and

**(d)** on the west by Jasper Avenue.

Alta Vista lands: Lands within the boundaries of the City of Ottawa and bounded

**(a)** on the north by Heron Road;

**(b)** on the south by Walkley Road;

**(c)** on the east by a residential area; and

**(d)** on the west by the Jim Durrell Recreation Centre and the Walkley Arena.

Beaux-Arts Courtyard: Land within the boundaries of the City of Ottawa and bounded

**(a)** on the north by St. Patrick Street;

**(b)** on the south by Murray Street;

**(c)** on the east by a residential area; and

**(d)** on the west by the buildings at 419, 425 and 431 Sussex Drive;

Capital Infocentre Plaza: Land within the boundaries of the City of Ottawa and bounded

**(a)** on the north by Wellington Street;

**(b)** on the south by the Capital Infocentre and the building at 101 Sparks Street;

**(c)** on the east by Metcalfe Street; and

**(d)** on the west by the building at 100 Wellington Street.

Château Laurier Terrace: Land within the boundaries of the City of Ottawa and bounded

**(a)** on the north by Major’s Hill Park;

**(b)** on the south by Wellington Street;

**(c)** on the east by the Château Laurier; and

**(d)** on the west by the Rideau Locks lands.

Clarendon Courtyard: Land within the boundaries of the City of Ottawa and bounded

**(a)** on the north by the building at 21 George Street;

**(b)** on the south by the buildings at 11, 15 and 25 George Street;

**(c)** on the east by the building at 33 George Street; and

**(d)** on the west by the buildings at 537, 539 and 541 Sussex Drive.

Confederation Square: A triangular-shaped piece of land within the boundaries of the City of Ottawa and bounded

**(a)** on the north by Wellington Street;

**(b)** on the east by Elgin Street and the Plaza Bridge; and

**(c)** on the west by Elgin Street.

Jeanne d’Arc Courtyard: Land within the boundaries of the City of Ottawa and bounded

**(a)** on the north by the building at 22 Clarence Street;

**(b)** on the south by the buildings at 9, 11 and 15 York Street;

**(c)** on the east by the buildings at 24 Clarence Street and 17 York Street; and

**(d)** on the west by the building at 489 Sussex Drive.

LeBreton Flats: Land within the boundaries of the City of Ottawa and bounded

**(a)** on the north by the Ottawa River Parkway corridor land and the western approach to the Portage Bridge;

**(b)** on the south by Scott Street, Wellington Street and Albert Street;

**(c)** on the east by Wellington Street; and

**(d)** on the west by the Ottawa River Parkway corridor land.

Ledbury Street lands: Lands within the boundaries of the City of Ottawa and bounded

**(a)** on the north by Ledbury Street and vacant lands;

**(b)** on the south by the Canadian National railway yard;

**(c)** on the east by Albion Road; and

**(d)** on the west by a residential area and vacant lands.

McCarthy Woods lands: Lands within the boundaries of the City of Ottawa, and bounded

**(a)** on the north and south by a residential area;

**(b)** on the east by the Airport Parkway; and

**(c)** on the west by the Rideau River.

Nepean Point — Astrolabe Theatre: Land within the boundaries of the City of Ottawa and bounded

**(a)** on the north and west by the Ottawa River;

**(b)** on the south by the St. Patrick Street approach to the Alexandra Bridge; and

**(c)** on the east by the National Gallery of Canada and the Canadian War Museum.

Plaza Bridge East Archway: Land within the boundaries of the City of Ottawa located beneath the Plaza Bridge and bounded

**(a)** on the north by the Canadian Museum of Contemporary Photography;

**(b)** on the south by the Government Conference Centre;

**(c)** on the east by the eastern abutment to the Plaza Bridge; and

**(d)** on the west by the Rideau Canal.

Plaza Bridge West Archway: Land within the boundaries of the City of Ottawa located beneath the Plaza Bridge and bounded

**(a)** on the north by the Rideau Locks lands;

**(b)** on the south by the National Arts Centre;

**(c)** on the east by the Rideau Canal; and

**(d)** on the west by the staircase to the Plaza Bridge and the staircase to Confederation Square.

Prince of Wales Drive lands: Lands within the boundaries of the City of Ottawa, between the Rideau River and Prince of Wales Drive, and bounded

**(a)** on the north by the inlet from the Rideau River immediately north of Melfa Circle;

**(b)** on the south and east by the Rideau River; and

**(c)** on the west by a residential area and Prince of Wales Drive.

Sparks Street Lookout: Land within the boundaries of the City of Ottawa and bounded

**(a)** on the north and west by a fence;

**(b)** on the south by the building at 100 Bronson Avenue; and

**(c)** on the east by Bronson Avenue.

Tin House Courtyard: Land within the boundaries of the City of Ottawa and bounded

**(a)** on the north by Murray Street;

**(b)** on the south by Clarence Street;

**(c)** on the east by the buildings at 81 Murray Street and 17-25 Clarence Street; and

**(d)** on the west by the buildings at 445, 447, 449, 453, 457, 459, 461, 463 and 465 Sussex Drive.

York Courtyard: Land within the boundaries of the City of Ottawa and bounded

**(a)** on the north by the buildings at 12 and 18 York Street;

**(b)** on the south by the building at 21 George Street;

**(c)** on the east by the building at 20 York Street; and

**(d)** on the west by the buildings at 519, 521, 527, 529 and 531 Sussex Drive.

#### Sidewalks

- Champlain Bridge sidewalk: Sidewalk within the boundaries of the City of Ottawa on the west and east sides of the Champlain Bridge, including its southern approaches.
- Confederation Boulevard Esplanade: Boardwalk on the south side of the Alexandra Bridge within the boundaries of the City of Ottawa, continuing as a sidewalk on the south side of the eastern approach to the Alexandra Bridge and St. Patrick Street to Mackenzie Avenue, and on the west side of Mackenzie Avenue to the Château Laurier.
- Portage Bridge sidewalk: Sidewalk within the boundaries of the City of Ottawa on the west and east sides of the Portage Bridge, including its southern approaches.

#### Islands

- Bate Island
- Green Island
- Victoria Island

#### Capital Pathways

- Aviation Pathway
- Experimental Farm Pathway
- Ottawa River Pathway
- Pinecrest Creek Pathway
- Rideau Canal Eastern Pathway
- Rideau Canal Western Pathway
- Rideau River Eastern Pathway
- Watts Creek Pathway

**DIVISION 2**
### Greenbelt

#### Access from April 15 to November 30

##### Trails

- Main Rideau Trail marked by orange triangles
- Trails 10, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 41, 42, 43, 44, 45, 46, 50, 51, 52, 53, 60, 61, 62 and 63

##### Capital Pathway

- Greenbelt Pathway

#### Year-round access

##### Capital Pathways

- Ottawa River Pathway
- Watts Creek Pathway

### **SCHEDULE 2 / ** ANNEXE 2
**(Section 1 / *article 1*)**
> Image: Pictogram showing a pathway leading to a maple leaf on the horizon flanked by hills on the left side and the Parliament building and other buildings on the right side.

repository: TravisMadill/CanadianLaws

path: /en/Regulations/Statutory Orders and Regulations/2002/164.md

repo_name: TravisMadill/CanadianLaws


text:
# Collage
## A web application and api for creating collages from user uploaded photos
#### Developed by: The PHP Group for The Ohio State University's Honors & Scholars House

### Getting Setup

Before you start setting up your environment to run this application you must
get Symfony working.  So, please check out the [README for Symfony](https://github.com/OSU-Android-PHP-Group/Collage-Web/blob/master/SYMFONY-README.md).

Once Symfony says its alright you can continue with the following steps:

    1.  Set up a Virtual Host pointed to `web/` or change Apache's
        `DocumentRoot`.
    2.  Create a database and user and set up `app/config/parameters.ini`.
    3.  Set the proper permissions on `app/cache` and `app/logs`.
    4.  Install vendor plugins.
    5.  Pull in git submodules (specifically the OSUBundle).

#### Steps 1 and 2

Figure out step 1 on your own. It is not specific to this project at all.
Creating the database and user should also be something to figure out on your
own. This project is only tested with PostgreSQL but since we use Doctrine as an
intermediate you should be able to use other RDBMS's.

To set up the `parameters.ini` file you should start by copying the sample:

    cd app/config
    cp parameters.ini.sample parameters.ini

Then open up `parameters.ini` and edit it to fit the connection information for
your database.

#### Step 3

The http server needs to be able to write to `app/cache` and `app/logs`.  To
allow this you need to have the proper permissions set up.

You can do this in many ways. If the server runs as your user then it should
work out of the box.  Typically what happens for me is I add myself to the group
that apache is running in and then execute something like this:

    cd app
    sudo chown -R $USER:http cache/ logs/
    sudo chmod -R g+w cache/ logs/

#### Step 4

Install the vendor plugins:

    php bin/vendors install

#### Step 5

Lastly, we have to pull in the git submodules (specifically the OSU bundle).

    git submodule update --init

---

### Deployment

To deploy you must use *capifony*.

    gem install capifony

Once it is installed you can deploy using the command:

    cap deploy

license: MIT

repository: OSU-Android-PHP-Group/Collage-Web

branch_name: refs/heads/master

extension: md

license_type: permissive

repo_name: OSU-Android-PHP-Group/Collage-Web


text:
# Auto_EAP

## Introduction
-----
######Published Sepetember 15, 2016

Auto_EAP.py is a script designed to perform automated brute-force authentication attacks against various types of EAP networks. These types of wireless networks provide an interface to facilitate password guessing of domain credentials as radius servers check authentication against Active Directory. Using the python library wpaspy, created by [Jouni Malinen<EMAIL_ADDRESS>(https://github.com/jmalinen/hostap/tree/master/wpaspy)
to interact with the wpa_supplicant daemon, automated authentication attacks can be preformed with the intent of not causing account lock-outs.

## Demo
-----

```
./Auto_EAP.py -s HoneyPot -K WPA-EAP -E PEAP -U test.txt -p Summer2016 -i wlan0
Initialized...
Trying Username Alice with Password test: SUCCESS
Trying Username Bob with Password test: FAILED
Trying Username Charles with Password test: FAILED
Trying Username David with Password test: SUCCESS
Completed

```

## Installation
-----

Run 'RunMeFirst.py' within the root directory of Auto_EAP. This will compile the wpaspy library as well as setup a stand alone wpa_supplicant.conf file that Auto_EAP.py will use for testing, leaving the system’s wpa_supplicant config file untouched.

## Help
-----

```
./Auto_EAP.py -h
usage: Auto_EAP.py [-h] -i Interface -s SSID -U Usernamefile -p Password -K
                   Key_mgmt -E Eap_type

optional arguments:
  -h, --help            show this help message and exit
  -i Interface, --interface Interface
                        The Interface to use
  -s SSID, --ssid SSID  The SSID to attack
  -U Usernamefile, --User Usernamefile
                        Path to username file
  -p Password, --password Password
                        Password to use
  -K Key_mgmt, --key_mgmt Key_mgmt
                        Key_Management type to use
  -E Eap_type, --eap_type Eap_type
                        Eap type to use

```

## Todo list
-----
* [✓] Resoved bug  with .a type wireless cards (Shout out to [Havok0x90] (https://twitter.com/havok0x90) for his help in resolving this issue)
* [-] Add multi-threading functionality
* [-] Add support for password lists

repository: wytshadow/SniffAir

gha_license_id: MIT

repo_name: wytshadow/SniffAir


text:
# Xamarin-PixateFreesytle

Pixate Freestyle is a native iOS (and [Android](https://github.com/pixate/pixate-freestyle-android)) library that styles native controls with CSS. With Freestyle, you can replace many complicated lines of code with a few lines of CSS. This simplifies and centralizes your styling code, and [offers other benefits](http://www.pixate.com/) as well.

This repo contains the iOS and Android (coming soon) modules for Xamarin.iOS and Xamarin.Android.

## Getting Started

### Quick Start

The fastest way to get started is to download the latest pre-compiled DLL from the [releases section](https://github.com/Pixate/Xamarin-PixateFreestyle/releases) of this repo. You can now clone this repo and run the [HelloWorld example project](https://github.com/Pixate/Xamarin-PixateFreestyle/tree/master/Examples). Be sure to **update the location of the PixateFreestyle.dll** in the sample project to wherever you placed your downloaded copy.

## Creating a Sample Project

Let's get started by creating a new solution. We'll start with creating a C# -> iOS -> Single View Application solution:

![Single View Application](https://raw.github.com/Pixate/Xamarin-PixateFreestyle/master/Screenshots/single_view_application.png)

Name your project and click 'OK'.

## Adding the Pixate Freestyle Library

Now right-click on your project's References folder in the Solution view and select 'Edit References...'.

![Add Native Ref](https://raw.github.com/Pixate/Xamarin-PixateFreestyle/master/Screenshots/edit_reference.png)

Now add the `PixateFreestyle.dll` file that you can get from [releases section](https://github.com/Pixate/Xamarin-PixateFreestyle/releases) of this repo if you don't already have it. You can also [build the DLL](#pixatedll-build-instructions) yourself.

The dialog should look something like this:

![Add Pixate Freestyle DLL](https://raw.github.com/Pixate/Xamarin-PixateFreestyle/master/Screenshots/add_pixate_dll.png)

## Adding a CSS File

Now right-click on your project again in the Solution view and select Add -> New File. Choose 'Misc' from the list on the left, and 'Empty Text File' from the list in the middle. Name your file 'default.css'.

![Add CSS File](https://raw.github.com/Pixate/Xamarin-PixateFreestyle/master/Screenshots/add_css_file.png)

Right-click on the `default.css` file you added and select the 'Properties' menu item. Over on the Properties panel, change 'Build action' to be 'Content'.

![Default to Content](https://raw.github.com/Pixate/Xamarin-PixateFreestyle/master/Screenshots/default_to_content.png)

## Setting up for Styling

At this point, let's add a button or two to our application. Double-click on the .xib file for your project (e.g. <ProjectName>ViewController.xib). Add a couple of buttons like the following:

![Two Buttons](https://raw.github.com/Pixate/Xamarin-PixateFreestyle/master/Screenshots/two_buttons.png)

With each of the new buttons you added, select one, activate the Identity Inspector in the Utilities View.

Now we need to give the buttons a "styleId" so that you can reference it from your CSS. We'll add a Runtime Attribute. Click the small '+' and add an entry with a key path of `styleId`, a type of `String`, and a value of `button1`. For the second button add a `styleId`, a type of `String`, and a value of `button2`.

![Runtime Attribute](https://raw.github.com/Pixate/Xamarin-PixateFreestyle/master/Screenshots/styleId.png)

Now save and close Xcode. In your **Main.cs** file, be sure to add the following line:

```csharp
	PixateFreestyleLib.PixateFreestyle.InitializePixateFreestyle ();
```

Your Main() would look something like this:

```csharp
	// This is the main entry point of the application.
	static void Main (string[] args)
	{
		// This is not strictly required right now, but a good practice to add for future feature support
		PixateFreestyleLib.PixateFreestyle.InitializePixateFreestyle ();

		// if you want to use a different Application Delegate class from "AppDelegate"
		// you can specify it here.
		UIApplication.Main (args, null, "AppDelegate");
	}
```

Before we style the buttons, go ahead and run the project in Xamarin Studio. It should look something like this:

![Buttons Runs](https://raw.github.com/Pixate/Xamarin-PixateFreestyle/master/Screenshots/buttons_run.png)

## Styling the Buttons

Now comes the easy part, just open your default.css file and add some CSS. For our two buttons, let's try something simple:

```css
	#button1 {
		background-color : yellow;
		border-width     : 2px;
		border-color     : black;
		border-radius    : 8px;
		border-style     : solid;
	}
	#button2 {
		background-color : gray;
		border-width     : 2px;
		border-color     : black;
		border-radius    : 8px;
		border-style     : solid;
	}
```

## First Styled App

Now Run your project. Your buttons should look like this:

![Styled Buttons](https://raw.github.com/Pixate/Xamarin-PixateFreestyle/master/Screenshots/styled_buttons.png)

Here's some slightly fancier styling you can try:

```css
	#button1 {
	  border-radius    : 5px;
	  font-family      : "American Typewriter";
	  font-size        : 13px;
	  font-weight      : bold;
	  text-transform   : uppercase;
	  letter-spacing   : 0.75px;
	  color            : #ffffff;
	  background-color : #008ed4;
	}
	#button2 {
	  color            : #446620;
	  background-color : linear-gradient(#87c44a, #b4da77);
	  border-width     : 1px;
	  border-color     : #84a254;
	  border-style     : solid;
	  border-radius    : 10px;
	  font-size        : 13px;
	}
```

Now you'll get pretty buttons like this:

![Pretty Buttons](https://raw.github.com/Pixate/Xamarin-PixateFreestyle/master/Screenshots/pretty_buttons.png)

Coding Your UI
--------------

For any code you write that needs to use some of the Pixate Freestyle API, be sure to add the using line:

```csharp
using PixateFreestyleLib;
```

To learn about the API that is exposed, be sure to look over the source code for your platform in this repo to see what is currently supported. In addition, the following five methods are provided to set ID, Class, and CSS on your controls/views:

```csharp
	view.SetStyleId("StyleID");
	view.SetStyleCSS("StyleCSS");
	view.SetStyleClass("StyleClass");
	view.AddStyleClass("AClassName");
	view.RemoveStyleClass("AClassName");
```

For example, here's some code that creates 3 buttons, each with a unique ID, all three with the same Class, and the third styled inline with CSS:

```csharp
	button1 = UIButton.FromType(UIButtonType.RoundedRect);
	button1.Frame = new RectangleF(50, 20, 200, 40);
	button1.SetTitle("#myButton1 .allButtons", UIControlState.Normal);
	button1.SetStyleId("myButton1");
	button1.SetStyleClass("allButtons");

	button2 = UIButton.FromType(UIButtonType.RoundedRect);
	button2.Frame = new RectangleF(50, 70, 200, 40);
	button2.SetTitle("#myButton2 .allButtons", UIControlState.Normal);
	button2.SetStyleId("myButton2");
	button2.SetStyleClass("allButtons");

	button3 = UIButton.FromType(UIButtonType.RoundedRect);
	button3.Frame = new RectangleF(50, 120, 200, 40);
	button3.SetTitle("#myButton3 .allButtons", UIControlState.Normal);
	button3.SetStyleId("myButton3");
	button3.SetStyleClass("allButtons");

	button3.SetStyleCSS("background-color: green; border-radius: 5;");
```

The CSS for these three buttons could be:

```css
	.allButtons {
	 border-radius: 5;
	}

	#myButton1 {
	 background-color: yellow;
	 border-color: black;
	 border-width: 2;
	 border-style: solid;
	}

	#myButton2 {
	 background-color: blue;
	 border-color: yellow;
	 border-width: 2;
	 border-style: solid;
	}

```

And you would get something like this:

![](https://raw.github.com/Pixate/Xamarin-PixateFreestyle/master/Screenshots/monotouch-sample1.png)

## Making changes in real-time

To turn on real-time monitoring of your CSS for live editing, first you'll need to turn on file monitoring in your AppDelegate, anywhere in the FinishedLaunching method. Add the following:

```csharp
	PixateFreestyle.CurrentApplicationStylesheet().MonitorChanges = true;
```

You may want to print out the location of the CSS file Pixate is using so you can edit it (by default your default.css will be loaded out of your app's resources). Use the following to get the temporary CSS file location:

```csharp
	string path = PixateFreestyle.CurrentApplicationStylesheet().FilePath;
```

You'll want to print this location out to the console and then edit it. Be sure to save your changes to another file before you run your app again, otherwise your changes will be overwritten. Alternetaively, you can load your CSS from a location on your file system during development (i.e. a DropBox folder) to easier editing:

```csharp
	PixateFreestyle.StyleSheetFromFilePathWithOrigin("/some/path/myStyle.css", PXStylesheetOrigin.PXStylesheetOriginApplication);
```

## PixateFreestyle.dll Build Instructions

If you'd like to build the DLL yourself, this is the simple process.
After cloning this project, start by creating a symbolic link to the PixateFreestyle file from your Pixate Freestyle distribution in the Source folder. For example:

    cd Source/iOS/PixateFreestyle
	ln -s ~/Desktop/Pixate/Frameworks/PixateFreestyle.framework/PixateFreestyle   .

Make sure the path to the MonoTouch BTOUCH tool is properly set at the top of the Makefile:

	BTOUCH=/Developer/MonoTouch/usr/bin/btouch

Now just type make:

	make

The resulting `PixateFreestyle.dll` file can now be added to your Xamarin Studio project.

## Mailing List & Twitter

Keep up with notifications and announcements by joining Pixate's [mailing list](http://pixatesurvey.herokuapp.com) and [follow us](http://twitter.com/Pixate) on Twitter.

## License

License for the included source is available in the accompanying [LICENSE](https://github.com/Pixate/Xamarin-PixateFreestyle/blob/master/LICENSE) file.


text:
![opencensus](https://i.imgur.com/tZzo80e.png)

### Usage

    docker-compose up -d
    docker-compose logs --follow

Open Jaeger in your browser

    http://localhost:16686/

### references

* https://opencensus.io/guides/http/go/net_http/client/
* https://opencensus.io/guides/http/go/net_http/server/
* https://github.com/jaegertracing/jaeger/blob/master/examples/hotrod/docker-compose.yml
* https://medium.com/faun/docker-multi-stage-build-for-go-a6821eabde1a

repository: juanpabloaj/opencensus-go-example

repo_name: juanpabloaj/opencensus-go-example


text:
# Astragalus harringtonii (Rydb.) Hulten SPECIES

#### Status
SYNONYM

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

#### Published in
Acta Univ. Lund. , 2, 43:1087. 1946 (Fl. Alaska & Yukon 7:1087. )

#### Original name
null

### Remarks
null

repository: mdoering/backbone

path: /life/Plantae/Magnoliophyta/Magnoliopsida/Fabales/Fabaceae/Astragalus/Astragalus robbinsii/ Syn. Astragalus harringtonii/README.md

repo_name: mdoering/backbone


text:
## 2.7.2
- Update native iOS dependency
- Update native Android dependency
- Remove dependency on JCenter

## 2.7.1
- Update native iOS dependency

## 2.7.0
- Update native dependencies
- Fix notification opens from cold app start

## 2.7.0-beta.2
- Target Android 12
- Fix bluetooth check in native Android

## 2.7.0-beta.1
- Update native Android dependency to 2.7.0-beta.4
- Update native iOS dependency to 2.7-beta2
- Update plugin gradle file
- Add handled flags for openUrl and continueUserActivity

##### BREAKING CHANGE: ANDROID NOTIFICATION TRAMPOLINE
Add the following to your `Manifest.xml`:

```xml
<activity android:name=".MainActivity">

    <!-- existing intent filters  -->

    <intent-filter>
        <action android:name="re.notifica.intent.action.RemoteMessageOpened" />
        <category android:name="android.intent.category.DEFAULT" />
    </intent-filter>

</activity>
```

For more information about this subject please take a look at [this](https://github.com/Notificare/notificare-push-lib-android-src/blob/2.7-dev/UPGRADE.md#breaking-change-trampoline-intents) section.

##### BREAKING CHANGE: ANDROID BLUETOOTH PERMISSION
From Android 12 and up, bluetooth scanning permissions have to be requested at runtime. This impacts the geofencing functionality of our library.

## 2.6.1
- Prevent the native Android module from breaking the React Native Linking module

## 2.6.0
- Update native Android dependency
- Update native iOS dependency
- Handle test device registration

## 2.5.5
- Update native iOS dependency
- Improve present notifications, inbox items & scannables transition & styling

## 2.5.4
- Update native Android dependency

## 2.5.3
- Prevent crash on mapping inbox items without a notification
- Update native iOS dependency

## 2.5.2
- Prevent crash on inbox updates after un-launching

## 2.5.1
- Add `extra` to assets
- Allow nullable asset URLs

## 2.5.0
- Update native Android SDK to 2.5.0
- Update native iOS SDK to 2.5.0
- Add beacon scanning foreground service

## 2.4.1
- Update dependencies
- Fix logkitty & lodash vulnerabilities

## 2.4.0-beta.2
- Add `targetContentIdentifier` to `NotificareNotification`
- Update native iOS SDK to v2.4.0-beta.7

## 2.4.0-beta.1
- update native SDKs to v2.4.0-beta
- refactor Billing Manager integration
- add `unknownNotificationReceivedInBackground` and `unknownNotificationReceivedInForeground` events on iOS
- add `markAllAsRead` method
- add `accuracy` to `NotificareDevice`
- add support for Dynamic Links
- add 'ephemeral' authorization status
- add `requestAlwaysAuthorizationForLocationUpdates` and `requestTemporaryFullAccuracyAuthorization` methods

2.3.2 03-09-2020
- Fix `updateUserData` method consistency between platforms

2.3.1 28-08-2020
- Add `urlOpened` event to Android

2.3.0 25-06-2020
- Fix `doCloudHostOperation` invocations
- Add `accessToken` to `NotificareUser`
- Fix user preferences parsing
- Fix ranging beacons payload
- Update Android SDK to v2.3.0
- Update iOS SDK to v2.3.2
- Allow `carPlay` in authorization options

2.2.6 29-04-2020
- Updated to Android SDK 2.2.3

2.2.5 15-04-2020
- Updated to Android SDK 2.2.2

2.2.4 27-02-2020
- Check partially fetched notifications when fetching inbox items

2.2.3 19-02-2020
- Updated to iOS SDK 2.2.6
- Updated to React Native 0.61.5

2.2.2 20-11-2019
- Updated to iOS SDK 2.2.4
- Changes to isViewController method

2.2.1 12-11-2019
- Updated to Android SDK 2.2.1
- Updated to iOS SDK 2.2.3

2.2.0 30-10-2019
- Updated to Android SDK 2.2.0

2.1.3 29-10-2019
- Guard against passing NaN values in Android device location

2.1.2 28-10-2019
- Added no-op for Android-only methods in iOS
- Updated podspec to use iOS lib 2.2.2
- Updated Android 2.1.2

2.1.1 14-10-2019
- Added event queue to iOS

2.1.0 01-10-2019
- Updated to use ReactNative 0.60+
- Updated to Android SDK 2.1.0
- Updated to iOS SDK 2.2.0

2.0.12 01-10-2019
- Added missing properties to Android inbox item

2.0.10 23-09-2019
- Start inbox observing on main thread

2.0.9 23-09-2019
- Fixed registerDevice in Android
- Fixed updateUserData in Android

2.0.8 18-09-2019
- Fixed crash in delegate didDetermineState when a beacon region was found

2.0.7 13-09-2019
- Updated to latest iOS library and necessary changes in handling launch options

2.0.6 09-09-2019
- Updated to latest iOS library

2.0.5 05-08-2019
- Updated to latest iOS and Android native libs

2.0.4 18-07-2019
- Updated to iOS 2.1.2
- Fixed crash when launch options contains a UIApplicationLaunchOptionsURLKey

2.0.3 15-07-2019
- Updated to Notificare Android SDK 2.0.7
- Made sure all UI presentation methods run in main thread

2.0.2 11-07-2019
- Added aliases for isRemoteNotificationsEnabled and isAllowedUIEnabled and isLocationServicesEnabled
- Updated iOS lib to latest version

2.0.1 05-07-2019
- Removed location permissions by default

2.0.0 21-06-2019
- Release 2.0.0

gha_language: Objective-C


text:
## Code Climate

[![Maintainability](https://api.codeclimate.com/v1/badges/b1dd2400d00d1957047b/maintainability)](https://codeclimate.com/github/ThiagoBarradas/jsonmasking/maintainability)
[![Test Coverage](https://api.codeclimate.com/v1/badges/b1dd2400d00d1957047b/test_coverage)](https://codeclimate.com/github/ThiagoBarradas/jsonmasking/test_coverage)

## Codacy

[![Codacy Badge](https://api.codacy.com/project/badge/Grade/a1c03f81731447218e44c17f2595e496)](https://www.codacy.com/app/ThiagoBarradas/jsonmasking)
[![Test Coverage](https://img.shields.io/codacy/coverage/a1c03f81731447218e44c17f2595e496.svg)](https://www.codacy.com/app/ThiagoBarradas/jsonmasking)

## Sonarqube

[![Quality Gate Status](https://sonarcloud.io/api/project_badges/measure?project=ThiagoBarradas_jsonmasking&metric=alert_status)](https://sonarcloud.io/dashboard?id=ThiagoBarradas_jsonmasking)
[![Coverage](https://sonarcloud.io/api/project_badges/measure?project=ThiagoBarradas_jsonmasking&metric=coverage)](https://sonarcloud.io/dashboard?id=ThiagoBarradas_jsonmasking)

repository: edrmonteiro/dio-csharp

branch_name: refs/heads/main

repo_name: edrmonteiro/dio-csharp


text:
---
title: 'Google I/O talk: Building Sourcegraph, a large-scale code search & cross-reference engine in Go'
author: 'Beyang Liu'
publishDate: 2016-05-30T00:00-07:00
tags: [
  "blog"
]
slug: google-i-o-talk-building-sourcegraph
heroImage: https://images.ctfassets.net/le3mxztn6yoo/3ayCsUlsBiAM2wsu0Ioc6M/93ceb6323af51a6c0eb49d1e2c8422ae/0_DJYjK6JTlwcaMvH4.png
published: true
---

_This was originally a talk at_ [_Google I/O 2014_](https://www.google.com/events/io)_. Check out the_ [_slides_](http://go-talks.appspot.com/github.com/sourcegraph/talks/google-io-2014/gio2014.slide#1) _and_ [_YouTube video_](https://www.youtube.com/watch?v=-DpKaoPz8l8)_. Thanks to the_ [_Go team_](http://golang.org/) _for inviting us!_

#### What is Sourcegraph?

[Sourcegraph](https://sourcegraph.com/) is a large-scale, multi-language code search and cross-reference engine that indexes hundreds of thousands of open source repositories. Sourcegraph lets developers:

*   Search for functions, types, and other definitions across code on the web
*   See real usage examples for any function (taken from other projects that use it)
*   Browse source code files, with jump-to-definition and instant mouseover docs

![0*DJYjK6JTlwcaMvH4](//images.contentful.com/le3mxztn6yoo/3ayCsUlsBiAM2wsu0Ioc6M/93ceb6323af51a6c0eb49d1e2c8422ae/0_DJYjK6JTlwcaMvH4.png)

Unlike other code search engines, Sourcegraph actually analyzes and understands code like a compiler, instead of just indexing the raw text of the code. (This is what enables the features above.)

**If you haven’t used** [**Sourcegraph**](https://sourcegraph.com)**,** check out [the homepage](https://sourcegraph.com/) and then come back here. Since the rest of this post is about how we built Sourcegraph, it’s important for you to know what it is.

### Building Sourcegraph with Go

Sourcegraph has two main parts:

1.  A large Go web app with an HTML frontend, JSON API, and SQL DB
2.  A language analysis toolchain that uses Docker to build and analyze projects

We’ll start with the web app. Next week we’ll cover Part 2 and discuss how we designed and built our language analysis toolchain.

### Part 1: Structure of a large Go web app

Our web app has 3 layers:

*   the web frontend, which returns HTML;
*   the HTTP API, which returns JSON; and
*   the data store, which runs SQL queries against our database and returns the results as Go structs or slices.

Basically, our frontend is just another API client to our own API. (We dogfood our own API.)

Here’s what it looks like:

![1*M99o63WSIzIzh86uZdTveA](//images.contentful.com/le3mxztn6yoo/7riB8h6i2cu8SyAAIKY40Y/d2231703aa0ae3d6de4aae9516e9ec9a/1_M99o63WSIzIzh86uZdTveA.png)

For example, if you go to a [repository’s page on Sourcegraph](https://sourcegraph.com/github.com/gorilla/mux), our web frontend will make a bunch of calls to our API to gather the data it needs. The API will in turn call into the data store, which queries the database. The API turns the results into JSON and sends them back to the web frontend, which renders an HTML template using the data.

This structure is pretty common for large web apps, and there are some nice ways Go makes it super simple to implement.

### Implementing our web app: avoiding complexity and repetition

We made several deliberate choices that have helped simplify the development of our web app:

*   No web framework
*   Unified interfaces for API client and data store
*   Unified URL routing and generation
*   Shared parameter structs

Our goal, based on our experience with similar systems, was to avoid complexity and repetition. Large web apps can easily become complex because they almost always need to twist the abstractions of whatever framework you’re using. And “service-oriented” architectures can require lots of repetitive code because not only do you have a client and server implementation for each service, but you often find yourself representing the same concepts at multiple levels of abstraction.

Fortunately, Go and a few libraries make it relatively simple to avoid these issues. Let’s run through each point and see how we achieve it and how it helps us.

(Side note: When we were thinking about how to build our web app, we looked around for examples of large Go web apps and couldn’t find many good examples. One notable good example was [godoc.org’s source code](https://github.com/golang/gddo), which we learned a lot from.)

### No web framework

We don’t use a web framework because we found we didn't need one in Go. Go’s [net/http](https://sourcegraph.com/github.com/golang/go/-/def/GoPackage/net/http/-/DefaultClient) and a few wrapper/helper functions suffice for us. Here are the techniques and glue code we use to make it all work in the absence of a framework.

**Handler functions:** We define our handlers with an error return value, and we use a simple wrapper function to make them implement [http.Handler](https://sourcegraph.com/github.com/golang/go/-/def/GoPackage/net/http/-/Handler). This means we can centralize error handling instead of having to format error messages and pass them to the [http.Error](https://sourcegraph.com/github.com/golang/go/-/def/GoPackage/net/http/-/Error) func for each possible error. Our handler functions look like:

func serveXYZ(w http.ResponseWriter, r *http.Request) error { ... }

**Global variables:** For virtually all request “context”, such as DB connections, config, etc., we use global variables. We chose this simple solution instead of relying on a framework to inject context for the request.

**Router:** We use [gorilla/mux](https://sourcegraph.com/github.com/gorilla/mux) for routing.

**Rendering HTML:** We use html/template and a simpler helper function to render the template:

func executeTemplate(req *http.Request, resp http.ResponseWriter, tmplName string, status int, header http.Header, tmplData interface{}) error { ... }

**Returning JSON:** We just use a simpler helper function:

// writeJSON writes a JSON Content-Type header and a JSON-encoded object to the
// http.ResponseWriter.
func writeJSON(w http.ResponseWriter, v interface{}) error {
	data, err := json.MarshalIndent(v, "", "  ")
	if err != nil {
		return &httpError{http.StatusInternalServerError, err}
	}

	w.Header().Set("content-type", "application/json; charset=utf-8")
	_, err = w.Write(data)
	return err
}

### Unified API client and data store interfaces

We have one “service” interface for each noun in our system: repositories, users, code definitions, etc. Our HTTP API client and data store both implement the same interfaces. That is:

*   API client methods fetch from HTTP API
*   Data store methods fetch from the DB

Here’s a simplified version of our repositories interface.

type RepositoriesService interface {
    Get(name string) (*Repo, error)
    List() ([]*Repo, error)
    Search(opt *SearchOptions) ([]*Repo, error)
    // ...
}

When we began, the client and data store implementations were a bit different, but they basically accomplished the same thing. They accepted different (but similar) parameters and returned different types that represented the same nouns. These differences were initially motivated by the need for greater performance (in the data store) and user-friendliness (in the API client). For example, the API client methods returned structs with some additional fields populated (which required a few additional queries), for greater convenience.

Unifying the sets of interfaces took away a tiny bit of performance and user-friendliness but made our API way cleaner and simpler overall. We now have a single set of interfaces that runs through our entire system, with a single set of method behaviors, parameters, return values, error behaviors, etc., no matter whether you’re using our API client or data store.

#### An example data store method

Here’s a (simplified) example of one of those data store methods, to make it concrete. This method implements the RepositoriesService.Get method described above.

type repoStore struct{ db *db }

func (s *repoStore) Get(name string) (*Repo, error) {
    var repo *Repo
    return repo, s.db.Select(&repo, "SELECT * FROM repo WHERE name=$1", name)
}

#### An example API client method

And here’s a (simplified) example of a method implementation in our HTTP API client library. Again, this is the same RepositoriesService.Get method.

type repoClient struct{ baseURL string }

func (s *repoClient) Get(name string) (*Repo, error) {
    resp, err := http.Get(fmt.Sprintf("%s/api/repos/%s", s.baseURL, name))
    if err != nil {
  return nil, err
    }
    defer resp.Body.Close()

    var repo Repo
    return &repo, json.NewDecoder(resp.Body).Decode(&repo)
}

(Notice that we’ve hardcoded the URL here. We’ll revisit that soon and find a better solution.)

#### Frontend and API http.Handlers

Initially our frontend web app just called the data store functions directly. This meant that each handler mixed HTTP and database code in ad-hoc ways. It was messy. This messiness made it hard to correctly implement HTTP caching and authorization because our handlers were already very complex.

Now our handlers have very clearly delineated responsibilities. The frontend handlers do HTML templating and call an API client method. The API handlers do HTTP authentication/authorization/caching and then call a data store method. In all cases, our HTTP handlers are concerned with HTTP (which is exactly as it should be) and they delegate the rest of the work.

For example, here’s what a (simplified) frontend handler looks like. It reads the HTTP request parameters, calls the API client (to do the real work), and renders the HTTP (HTML) response.

var repoAPIClient RepositoriesService = &repoClient{"http://localhost:7777"}

func handleRepoPage(w http.ResponseWriter, r *http.Request) {
    name := mux.Vars(r)["Name"]
    repo, _ := repoAPIClient.Get(name)
    fmt.Fprintf(w, "
%s

Clone URL: %s
", repo.Name, repo.CloneURL)
}

And here’s what a (simplified) API handler looks like. Again, it reads the HTTP request parameters, calls the data store (to do the real work), and renders the HTTP (JSON) response with a cache header.

var repoStore RepositoriesService = &repoStore{dbh}

func serveRepository(w http.ResponseWriter, r *http.Request) error {
    repo := mux.Vars(r)["Repo"]
    rp, err := repoStore.Get(repo)
    if err != nil {
  return repositoryError(err)
    }
    writeLastModifiedHeader(rp.UpdatedAt)
    return writeJSON(w, rp)
}

The key point here is that our HTTP handlers are concerned with handling HTTP, and they call out to implementations of our API to do the real work. This greatly simplifies our HTTP handling code.

#### Other benefits of a separate, dogfooded API

*   Dogfooding our API means it will probably be higher quality since we’re forced to use it 24/7.
*   We can use standard HTTP load balancing, caching, and authorization schemes in our API when communicating between layers. We don’t need to invent our own RPC protocol and schema.

### Unifying URL routing and generation

Remember back to our API client implementation? We used Sprintf to construct the URL string. And here in the router definition (below), we repeat the same URL pattern. This is bad because we have more than 75 routes, some with fairly complex matching logic, and it’s easy to get them out of sync.

To solve this, we use a router package (such as [gorilla/mux](https://sourcegraph.com/github.com/gorilla/mux)) that lets us define routes and mount handlers separately. Our server mounts handlers by looking up named routes we’ve defined, but our API client will just use the route definitions to generate URLs.

const (
    RepoGetRoute    = "repo"
    RepoListRoute   = "repo.list"
)

func NewAPIRouter() *mux.Router {
    // Define the routes but don't attach handlers.
    m := mux.NewRouter()
    m.Path("/api/repos/{Name:.*}").Name(RepoGetRoute)
    m.Path("/api/repos").Name(RepoListRoute)
    return m
}

// init is called at server startup.
func init() {
    m := NewAPIRouter()
    // Attach handlers to the routes.
    m.Get(RepoGetRoute).HandlerFunc(handleRepoGet)
    m.Get(RepoListRoute).HandlerFunc(handleRepoList)
    m.Get(RepoSearchRoute).HandlerFunc(handleRepoSearch)
    http.Handle("/api/", m)
}

Then to generate URLs in our HTTP API client using the router, we use the existing route definition:

var apiRouter = NewAPIRouter()

func (s *repoClient) List() ([]*Repo, error) {
    url, _ := apiRouter.Get(RepoListRoute).URL()
    resp, err := http.Get(s.baseURL + url.String())
    if err != nil {
  return nil, err
    }
    defer resp.Body.Close()

    var repos []*Repo
    return repos, json.NewDecoder(resp.Body).Decode(&repos)
}

Notice that we’re no longer hardcoding URLs, so if we update the route definitions, our generated URLs will automatically be updated as well.

We’ve actually made our route definitions open source, as part of our open source client library. Our API server imports the client library, which is where the route definitions live, and just mounts handlers as we saw on the previous slide. So, it’s much easier for us to keep our API client library in sync with our servers. (In fact, we think all web services should open source their routing! It would make building API clients much easier.)

### Sharing parameter structs

Most of the methods in our API take some main arguments and some extra parameters. In URLs, the parameters are encoded in the querystring; in Go function calls, they’re just a final struct pointer argument.

Initially we had 3 different parameter sets for each logical interface method:

1.  the frontend querystring parameters: /repos?Owner=alice&Language=go
2.  the API querystring parameters: /api/repos?OwnerUserID=123&Lang=go
3.  the data store method parameters: SearchOptions{123, “go”}

This was needlessly complex and required a lot of code to convert among the various forms. Thankfully, because the structs were very similar, it was easy to agree on a single struct that all implementations could use. Doing this simplified our code quite a bit.

To do this, we defined the querystring as a Go struct, like SearchOptions here. In each HTTP handler, we use [gorilla/schema](https://sourcegraph.com/github.com/gorilla/schema) to decode the querystring into the Go struct. And in the API client, we use Will Norris’ [go-querystring](https://sourcegraph.com/github.com/google/go-querystring) to convert a Go struct back into a querystring. These two libraries perform essentially the inverse operations. And in our data store, of course, we still get the parameters as a Go struct.

Having a single definition of each parameter set is much simpler _and_ it lets us rely on the Go compiler’s type checker to warn us if we make mistakes (unlike the non-type-checked querystring map[string]strings we used to use).

Here’s an example parameter struct that is shared by all implementations (frontend and backend):

// this is the options struct for the method: Search(opt *SearchOptions) ([]*Repo, error)
type SearchOptions struct {
    Owner    string
    Language string
}

To decode the parameter struct from a querystring like ?Owner=alice&Language=go, in the API HTTP handler:

import ["github.com/gorilla/schema"](https://sourcegraph.com/github.com/gorilla/schema)

var d = schema.NewDecoder()

func handleRepoSearch(w http.ResponseWriter, r *http.Request) {
    var opt SearchOptions
    d.[Decode](https://sourcegraph.com/github.com/gorilla/schema/.GoPackage/github.com/gorilla/schema/.def/Decoder/Decode)(&opt, r.URL.Query()) // decode querystring with github.com/gorilla/schema
    // now opt is populated with values from the querystring

And to encode a parameter struct like SearchOptions{“alice”, “go”} back into ?Owner=alice&Language=go, in the HTTP API client:

import ["github.com/google/go-querystring/query"](https://sourcegraph.com/github.com/google/go-querystring)

func (s *repoClient) Search(opt *SearchOptions) ([]*Repo, error) {
    url, _ := apiRouter.Get(RepoSearchRoute).URL()
    q, _ := query.[Values](https://sourcegraph.com/github.com/google/go-querystring/.GoPackage/github.com/google/go-querystring/query/.def/Values)(opt)
    resp, err := http.Get(s.baseURL + url.String() + "?" + q.Encode())
    // ...
}

### Other things we did

We do a few other things to make it easier to build our web app:

*   Instrument http.Handlers and API client http.Transports to track timing info using [Appdash](https://github.com/sourcegraph/appdash)
*   Pass along typed error values from the data store to the frontend
*   Define a common interface for response pagination
*   Consolidate caching logic in the API
*   Make test mocks of the interfaces

### Conclusion

We’ve used Go to build a large-scale code search engine that compiles and indexes hundreds of thousands of repositories. We hope that we’ve conveyed some of the ways we use Go’s features and that these patterns will be useful you when building large Go apps.

#### Questions/comments?

Follow [me (@sqs)](https://twitter.com/sqs) and [@sourcegraph](https://twitter.com/sourcegraph) on Twitter. And **check out** [**Sourcegraph**](https://sourcegraph.com)!

repository: zag/about

repo_name: zag/about


text:
# Landing

This page contains the content in which spreads out (like a tree) all of what Benkyou offers. We broadcast the information in which people can learn from and link to them where said content can be accessed. Also gives a great place for the contact/social links for the Benkyou community/team.

## Installation

```sh
$ npm install gulp-cli --global
```

### 2. Install gulp and dependencies:
```sh
$ npm install gulp gulp-jade gulp-sass
```

### 3. Run gulpfile
```sh
$ gulp
```

# Contribute

1. Fork repo.
2. Edit code.
3. Make a PR.
4. Submit said PR.

# License

A copy of the MIT license can be found in `LICENSE.md`


text:
# Change Log - @azure-tools/extension

This log was last generated on Wed, 07 Dec 2022 22:24:34 GMT and should not be manually modified.

## 3.6.1
Wed, 07 Dec 2022 22:24:34 GMT

### Patches

- Update dependencies

## 3.6.0
Tue, 19 Jul 2022 15:09:55 GMT

### Minor changes

- Extracted system-requirements into own package `@autorest/system-requirements`
- Update dependencies(npm)

## 3.5.0
Tue, 15 Mar 2022 16:00:38 GMT

### Minor changes

- Stop using shell call to `yarn` or `npm` to resolve list of available version and use `pactote` library. Improving reliability and performance.
- Reimplement locking mechanism causing ghost promise to be left hanging

## 3.4.0
Fri, 19 Nov 2021 04:23:43 GMT

### Minor changes

- **Added** Progress tracking for installation and imrpvoed error reporting

## 3.3.1
Mon, 19 Jul 2021 18:08:46 GMT

### Patches

- **Fix** Using `fs/promises` imort not supported on node 12

## 3.3.0
Mon, 19 Jul 2021 15:15:42 GMT

### Minor changes

- Drop support for node 10

### Patches

- **Fix** Installing extension when parent directory to ~/.autorest had a package.json

## 3.2.7
Wed, 26 May 2021 18:31:17 GMT

### Patches

- **Export** fetchPackageMetadata for use without depending on local package manager

## 3.2.6
Tue, 27 Apr 2021 17:48:43 GMT

### Patches

- **Fix** Fallback to github release when version doesn't exists broken if using version range

## 3.2.5
Thu, 01 Apr 2021 15:46:41 GMT

### Patches

- **Add** Logging when fail to fetch pacakge metadata

## 3.2.4
Tue, 16 Mar 2021 15:52:56 GMT

### Patches

- Bump dependencies versions

## 3.2.3
Fri, 05 Mar 2021 16:31:29 GMT

### Patches

- **Revert** not using global yarnrc and change to prevent yarn from loading alternate version

## 3.2.2
Fri, 26 Feb 2021 21:50:13 GMT

### Patches

- Prevent single-file yarn from loading user config and changing version

## 3.2.1
Wed, 24 Feb 2021 00:33:50 GMT

### Patches

- **Fix** updatePythonPath wasn't patching array inplace.

## 3.2.0
Fri, 19 Feb 2021 21:42:09 GMT

### Minor changes

- **Feature**: Add option to set the path to the yarn cli in the ExtensionManager. This enable webpack compatibility.
- **Feature** Added new "systemRequirements" validation for extensions. Extension are able to provide a list of system requirements which autorest will validate before starting.

### Patches

- **Update** various dependencies and moved package source from Azure/perks -> Azure/autorest
- **Update** copy yarn file on build from node dependency.

repository: Azure/autorest

gha_language: TypeScript

repo_name: Azure/autorest


text:
![](prints/preview.gif)

# 🎈 About
This is a React web interface for converting Youtube videos to mp3 files with metadata (tags) and album cover art using **youtube-dl** and **ffmpeg**. Please use alongside with [@brunight/youtube-dl-api](https://github.com/brunight/youtube-dl-api).

Allows cropping the video's thumbnail, image file ou image url and send it to the API to be set as album cover art, as well as set a specific duration to audio.

# 📝 Requirements
- NodeJS and NPM or Yarn;
- [YouTube Data API](https://developers.google.com/youtube/v3) key;

# 🛠 Installation
You'll need to set your API key to an Environment Variable. See [Configuration](#configuration).

With npm do:
```bash
npm install
```
Or with yarn do:
```bash
yarn install
```

# ⚙ Configuration
Create a file named **.env** in project root and put there your configuration. At the time there are two variables:
- REACT_APP_YOUTUBE_API_KEY - your YouTube Data API key.
- REACT_APP_SERVER_ADDRESS - optional - [youtube-dl-api](https://github.com/brunight/youtube-dl-api) address. If not present, *localhost:3333* will be used.

For examples, check **.env.example** file.

# 🚀 Usage
To start with npm do:
```bash
npm run start
```
Or with yarn do:
```bash
yarn start
```

And that's it. Simply paste an Youtube video link, set the data you want for audio file and press **Download**. Some videos can return a *mpd* manifest/dash file to youtube-dl, causing the overall process to get a bit slower since there more than one stream on it.

When done, you'll be moved back to the homepage and there'll be a Toast with the link for the audio file.

Remember, you should avoid setting the same album name for multiple files with different cover art to avoid conflicts.

# 👨💻 Technologies
- TypeScript;
- Context API;
- Axios;
- Styled Components;
- Polished;
- Date-fns and Moment;
- [Unform](https://github.com/Rocketseat/unform);
- [CropperJS](https://github.com/fengyuanchen/cropperjs) and [React Cropper](https://github.com/react-cropper/react-cropper);
- [React Slider](https://github.com/zillow/react-slider);
- React Icons;
- React Spring;
- uuidv4;
- ESLint;
- Prettier;
- DotEnv;
- Color scheme based on [Omni Theme](https://github.com/getomni);

# 📜 Planned features
- Set volume;
- Show process progress;
- Download video;
- Upload files and change their metadata without changing format, codec, sample rate and bitrate;
- Drag and drop image to load in Cropper canvas;
- Support other plataforms such as Soundcloud;
- Improve UI responsivity for mobile users;
- Download history (with database);
- Solve some Cors Policy problems;
- Suggest album name and cover art by song title and artist;
- Playlist support;

- **Mix this interface and the API into an independent ElectronJS application;**

# 📃 License
MIT. Not recommended to use with copyrighted content. Developed by [Bruno Rodrigues](https://github.com/brunight/).

repository: Brunight/youtube-dl-web

repo_name: Brunight/youtube-dl-web


text:
# A PHP nano framework for making REST API services

[![Total Downloads](https://poser.pugx.org/nofuzz/framework/downloads)](https://packagist.org/packages/nofuzz/framework)
[![License](https://poser.pugx.org/nofuzz/framework/license)](https://packagist.org/packages/nofuzz/framework)
[![Build Status](https://travis-ci.org/Celarius/nofuzz-framework.svg)](https://travis-ci.org/Celarius/nofuzz-framework)
[![PHP7 Ready](https://img.shields.io/badge/PHP7-ready-green.svg)](https://packagist.org/packages/nofuzz/framework)

Nofuzz is a nano-framework that enables rapid development of REST API services in PHP.

Designed to be PSR compliant, very small and lightweight, but still have enough muscle to power complex API's.

Nofuzz is built around a routing engine and the Controller principle. Built in are features such as Caches, multiple Database drivers and a myriad of other often needed features in API's (like JWT).

---
## Installing
```txt
$ composer require nofuzz/framework
```

---
## Documentation
* [Documentation](doc/documentation.md)
* [Installing](doc/installing.md)
* [Changelog](doc/changelog.md)
* [Roadmap](doc/roadmap.md)

---
# Author
Kim Sandell -<EMAIL_ADDRESS>- http://celarius.com

---
# License
Nofuzz is licensed under the MIT License - see the [License](LICENSE) for details

repository: Celarius/nofuzz-framework

gha_language: PHP

repo_name: Celarius/nofuzz-framework


text:
# Js Lib Boilerplate
[![GitHub license](https://img.shields.io/badge/license-MIT-blue.svg)](https://github.com/felippemauricio/js-lib-boilerplate/blob/master/LICENSE.md)
[![Build Status](https://travis-ci.org/felippemauricio/js-lib-boilerplate.svg?branch=master)](https://travis-ci.org/felippemauricio/js-lib-boilerplate)
[![devDependencies Status](https://david-dm.org/felippemauricio/js-lib-boilerplate/dev-status.svg)](https://david-dm.org/felippemauricio/js-lib-boilerplate?type=dev)
[![Coverage Status](https://coveralls.io/repos/github/felippemauricio/js-lib-boilerplate/badge.svg?branch=master)](https://coveralls.io/github/felippemauricio/js-lib-boilerplate?branch=master)
[![Code Style](https://badgen.net/badge/code%20style/airbnb/fd5c63)](https://github.com/airbnb/javascript)
[![Tested with Jest](https://img.shields.io/badge/tested_with-jest-99424f.svg)](https://github.com/facebook/jest)
[![PRs Welcome](https://img.shields.io/badge/PRs-welcome-brightgreen.svg)](https://github.com/felippemauricio/js-lib-boilerplate/pulls)

A boilerplate to create js libs and publish on npm.

## Motivation

When I started to create libs to facilitate my job, I noticed that many settings were repeated, like transpilers, tests, files to ignore... So I created this project to don\`t repeat this confs on new libs and facilitate the work of new developers.

## Usage

To use this boilerplate, simply follow the following steps:

1. Clone this repository.
2. Run the [script-name-replace](https://github.com/felippemauricio/js-lib-boilerplate/blob/master/docs/script-name-replace.md) to change project name.
3. Write your code on `src`;
4. Write your tests on `tests`;

## Confs in this project

- Transpiler with Babel
- Editor Config to IDEs
- Lint
- Tests with Jest

## Public Projects created with this boilerplate

- [promise-fn-retry](https://github.com/felippemauricio/promise-fn-retry)
- [string-interpolation-parser](https://github.com/felippemauricio/string-interpolation-parser)

## License

Licensed under the MIT License, Copyright © 2019-present Felippe Maurício.

repository: felippemauricio/js-lib-boilerplate

gha_language: JavaScript

repo_name: felippemauricio/js-lib-boilerplate


text:
# 2. Task Cache Volumes

Date: 17 September 2018

## Context

Concourse has [task caches](https://concourse-ci.org/tasks.html#task-caches) to save state between runs of the same task on the same worker. This can greatly speed up tasks - making users happy, and reduce load - making operators happy. win win.

## Decision

Change halfpipe to provide one directory `/var/halfpipe/cache` instead of a list of directories specific to common build tools.

This will allow users to configure any build tool to use the cache instead of the onus being on halfpipe to add support.

Also there is a small overhead to mounting each cache volume, so one volume is better than n.

## Consequences

Users will have to point their build tool  at `/var/halfpipe/cache` instead of `/root/.sbt` for example.

repository: springernature/halfpipe

gha_language: Go

repo_name: springernature/halfpipe


text:
---
description: A generic First Appeal application format in English
---

# First Appeal

To
First Appellate Authority under RTI Act
**\[Address of Public Authority\]**
**\[Date\]**

Subject: First Appeal under the RTI Act 2005

Dear FAA,

As I am aggrieved by decision/no decision of the Public Information Officer, I hereby file this appeal for your kind decision.

#### 1. Details of Appellant:

* Full Name:
* Full Address:
* Phone/Cell No:
* Email ID:

#### 2. Details of Central/State Public Information Officer:

* Name/Designation:
* Name of Public Authority:
* Full Address:
* Date RTI application was sent on:
* Date on which the PIO received RTI:
* Reference No of PIO Decision:
* Date of PIO Decision:
* Date of receipt of decision by myself:

#### 3. Particulars of Payment of Fee:

Application Fee of Rs.10 was remitted as **\[IPO/DD/Banker’s Cheque\]** numbered **\[IPO/DD/Banker’s Cheque Number\]** dated **\[Date of payment\]**

#### 4. Details of information sought under RTI Act:

#### 5. Brief facts of the case leading to appeal:

####

####

#### 6. Reasons/grounds for this appeal:

|  | Only tick the reason which is applicable |  |
| :--- | :--- | :--- |
| i | PIO did not send reply |  |
| ii | Reply refused, without due justification |  |
| iii | Reply is incorrect / misleading / false |  |
| iv | Reply is partial or incomplete  |  |
| v | Any other reason written below |  |

#### 7. Any other information in support of appeal:

#### 8. Prayer/relief sought for:

#### 9. Personal Presence at hearing:

YES / NO / ONLINE

#### Enclosures:

Photocopies of original RTI application with its enclosures, postal proof of mailing and delivery confirmation, acknowledgement of PIO, decision letter of PIO.

#### Declaration:

I hereby state that the information and particulars given above are true to the best of my knowledge and belief. I also declare that this matter is not previously filed with this commission nor is pending with any Court or tribunal or authority.

**Place**:

**Date**:

**Signature of Appellant**

{% hint style="info" %}
Strike out whichever is not applicable
{% endhint %}

{% file src="../.gitbook/assets/first-appeal.docx" caption="DOCX" %}

{% file src="../.gitbook/assets/first-appeal.pdf" caption="PDF" %}

repository: exotonorg/RTILikho

repo_name: exotonorg/RTILikho