hexsha
stringlengths 40
40
| size
int64 5
1.04M
| ext
stringclasses 6
values | lang
stringclasses 1
value | max_stars_repo_path
stringlengths 3
344
| max_stars_repo_name
stringlengths 5
125
| max_stars_repo_head_hexsha
stringlengths 40
78
| max_stars_repo_licenses
sequencelengths 1
11
| max_stars_count
int64 1
368k
⌀ | max_stars_repo_stars_event_min_datetime
stringlengths 24
24
⌀ | max_stars_repo_stars_event_max_datetime
stringlengths 24
24
⌀ | max_issues_repo_path
stringlengths 3
344
| max_issues_repo_name
stringlengths 5
125
| max_issues_repo_head_hexsha
stringlengths 40
78
| max_issues_repo_licenses
sequencelengths 1
11
| max_issues_count
int64 1
116k
⌀ | max_issues_repo_issues_event_min_datetime
stringlengths 24
24
⌀ | max_issues_repo_issues_event_max_datetime
stringlengths 24
24
⌀ | max_forks_repo_path
stringlengths 3
344
| max_forks_repo_name
stringlengths 5
125
| max_forks_repo_head_hexsha
stringlengths 40
78
| max_forks_repo_licenses
sequencelengths 1
11
| max_forks_count
int64 1
105k
⌀ | max_forks_repo_forks_event_min_datetime
stringlengths 24
24
⌀ | max_forks_repo_forks_event_max_datetime
stringlengths 24
24
⌀ | content
stringlengths 5
1.04M
| avg_line_length
float64 1.14
851k
| max_line_length
int64 1
1.03M
| alphanum_fraction
float64 0
1
| lid
stringclasses 191
values | lid_prob
float64 0.01
1
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
22bf62becaecdcb8ff220d2c57c7592fcea6a628 | 153 | md | Markdown | README.md | IHunelI/-Prototype-ArrowFest | 75cb9f2ace5c7efe6e47729628696ed15254f093 | [
"MIT"
] | null | null | null | README.md | IHunelI/-Prototype-ArrowFest | 75cb9f2ace5c7efe6e47729628696ed15254f093 | [
"MIT"
] | null | null | null | README.md | IHunelI/-Prototype-ArrowFest | 75cb9f2ace5c7efe6e47729628696ed15254f093 | [
"MIT"
] | null | null | null | # -Prototype-ArrowFest
| 51 | 129 | 0.797386 | yue_Hant | 0.108159 |
22c01f876396905af4e56bcbbb4d0fdff26d9413 | 655 | md | Markdown | README.md | Smeiling/mynote | 6bb72877d2dee9008cd831d3ca03b3fe715aa5ec | [
"Apache-2.0"
] | null | null | null | README.md | Smeiling/mynote | 6bb72877d2dee9008cd831d3ca03b3fe715aa5ec | [
"Apache-2.0"
] | null | null | null | README.md | Smeiling/mynote | 6bb72877d2dee9008cd831d3ca03b3fe715aa5ec | [
"Apache-2.0"
] | null | null | null | # mynote
This is my first android application.
# screenshot
| 59.545455 | 98 | 0.777099 | yue_Hant | 0.102842 |
22c18f0fbadda71132e862834fdb11c7eb463bb8 | 969 | md | Markdown | README.md | eosti/remote-stm32 | 2f5f548f4a90d932072a6b0095df05d084b9f7a5 | [
"MIT"
] | null | null | null | README.md | eosti/remote-stm32 | 2f5f548f4a90d932072a6b0095df05d084b9f7a5 | [
"MIT"
] | 8 | 2021-01-07T07:05:25.000Z | 2021-06-03T19:23:37.000Z | README.md | eosti/remote-stm32 | 2f5f548f4a90d932072a6b0095df05d084b9f7a5 | [
"MIT"
] | null | null | null | # remote-stm32 #
A remote programming configuration for flashing/debugging an STM32 MCU from anywhere in the world!
This consists of two parts: a Raspberry Pi that is physically connected to the target ST-LINK, and a client connected to that server via a VPN.
The Pi runs a GDB server for uploading and debugging code, as well as a serial port forwarder, so that the client can view and interact with the output of a UART interface on the STM32.
The client can use STM32CubeIDE to connect to both of these services, so that they can debug as if the STM32 was sitting right next to them.
Tested and working on MacOS and Windows 10 clients, with STM32H7 and STM32F3 targets. All boards that are supported by [stlink-tools](https://github.com/stlink-org/stlink/blob/develop/doc/devices_boards.md) should be supported here as well.
## Installation ##
[Server Configuration](server.md)
[Client Configuration](client.md)
| 51 | 240 | 0.784314 | eng_Latn | 0.998225 |
22c2ae49dbda41382af2c6f335dc6a2c3d0ecbd2 | 6,058 | md | Markdown | content/posts/2012-05-18-morron-y-cuenta-nueva.md | impronunciable/los-rayos.com | 2be3d1fdcfb6e5dc5b5a9ba0f999e63db763f78d | [
"MIT"
] | null | null | null | content/posts/2012-05-18-morron-y-cuenta-nueva.md | impronunciable/los-rayos.com | 2be3d1fdcfb6e5dc5b5a9ba0f999e63db763f78d | [
"MIT"
] | null | null | null | content/posts/2012-05-18-morron-y-cuenta-nueva.md | impronunciable/los-rayos.com | 2be3d1fdcfb6e5dc5b5a9ba0f999e63db763f78d | [
"MIT"
] | null | null | null | ---
id: 1020
title: Morrón y cuenta nueva
date: 2012-05-18T03:59:10-03:00
author: Lende
template: post
draft: false
description: ""
guid: http://los-rayos.com.ar/?p=1020
slug: /morron-y-cuenta-nueva/
has_been_twittered:
- 'yes'
category: La cocina de Los Rayos
tags:
- Los Rayos
- Morrón
- ratatouille
- Recetas
- Rouille
---
Y como el título lo indica, hoy les voy a pasar un par de recetas con morrón. Y la idea surgió porque me preguntaron qué pasaría si en vez de tocar el timbre en el colectivo, pido la cuenta. Y me quedé pensando. Un largo rato. Hasta que un día salí de casa y decidí probarlo cuando me bajara del bondi. Y resulta que venía leyendo muy tranquilo en el colectivo hasta que llegó el momento de bajarme, entonces guardé mi libro y me acerqué a la puerta de bajada. Miré para adelante, hice contacto visual con el conductor, y con el clásico gesto, gesticulando las palabras, pronunciándolas por lo bajo, como para que las escuche solo yo, le pedí la cuenta.
Y hete aquí la gran grata sorpresa. ¿Vos sos un **Rayo**? Me preguntó desde su asiento. La verdad, me quedé helado, no pude ni bajarme, me pasé. ¿Vos sos un **Rayo**? Volvió a preguntarme, y esta vez me le acerqué y le dije que si, que claro que era un **Rayo**, quién más podría pedir la cuenta en el colectivo. Intercambiamos un par de palabras, grandilocuentes, algunas onomatopeyas, y gestos varios, y al final me pidió alguna receta con morrones.
<div style="width: 310px" class="wp-caption alignleft">
<img src="https://www.uauau.com.ar/img/productos/abe165fc939adc7183970d4a9bbf0a3f-gr-76_large.jpg" alt="" width="300" height="312" />
<p class="wp-caption-text">
Morrón amigo!
</p>
</div>
Así que, querido Colectivero del 39, acá te dejo un par de recetas con morrón. Controvertido vegetal, sin dudas, con muchas variantes y colores, usado casi como comodín en muchas recetas, como mero ingrediente, pero hoy no, hoy sos protagonista.
Vamos a empezar por una clásica y muy rica salsa que se ha de llamar Rouille. Para esto, tenes que asar un morrón rojo en el horno (con un poco de aceite), después lo pelas (para que te sea más fácil de pelar, cuando lo sacas del horno lo envolvés en film un rato) y le sacas las semillas. Después, procesas con una yema, una punta de ajo (un cuarto de diente sería), sal y pimienta de cayena (puede ser ají molido) y un poco de papa cocida (es para darle un poco de cuerpo). También podes ponerle un puñadito de hojas de perejil, no mucho. Sin dejar de procesar, vas agregando aceite de oliva, como si estuvieras haciendo una mayonesa. Tiene que quedar fluida, pero no líquida, debe tener un poco de consistencia. Queda muy bien con pescados.
Ahora vamos a pasar a hacer un sabayón de morrón, que encima rima. Empezamos igual, asando 2 morrones rojos, pelándolos y procesándolos. En este caso, también vas a necesitar unos 7 gramos de gelatina sin sabor (es la cantidad que viene en los sobrecitos individuales), la cual vas a hidratar con 35 gr de agua (es importante que respetes esta proporción, y para hacerlo, vas a ir vertiendo la gelatina en forma de lluvia sobre el agua sin dejar de revolver); unos 200 cc de crema de leche batida a medio punto (es cuando al batir quedan las marcas y se borran con cierta rapidez); 100 cc de vino blanco y 2 yemas.
En un bol a baño maría, vas a batir las yemas junto con el vino hasta que tome cuerpo (no tiene que pasar los 63°, si ves que no tiene cuerpo y que está tomando mucha temperatura, batí fuera del fuego un rato), tiene que verse el fondo cuando pasas el batidor, deben quedar las marcas del mismo. Cuando lo tenés, agrega el morrón procesado, con movimientos envolventes. Podes consumirlo así, caliente, o sino, agregas la gelatina y llevas al frío. Cuando esta empieza a tomar cuerpo, agregas la crema batida con movimientos envolventes y volves a llevar todo al frío.
<div id="attachment_1021" style="width: 310px" class="wp-caption alignright">
<a href="http://los-rayos.com/wp-content/uploads/2012/05/foto-villar-rojo-pasion.jpg"><img aria-describedby="caption-attachment-1021" class="size-medium wp-image-1021" title="foto-villar-rojo-pasion" src="https://los-rayos.com/wp-content/uploads/2012/05/foto-villar-rojo-pasion-300x243.jpg" alt="" width="300" height="243" srcset="https://los-rayos.com/wp-content/uploads/2012/05/foto-villar-rojo-pasion-300x243.jpg 300w, https://los-rayos.com/wp-content/uploads/2012/05/foto-villar-rojo-pasion-369x300.jpg 369w, https://los-rayos.com/wp-content/uploads/2012/05/foto-villar-rojo-pasion.jpg 431w" sizes="(max-width: 300px) 100vw, 300px" /></a>
<p id="caption-attachment-1021" class="wp-caption-text">
Morrón abastracto
</p>
</div>
Morrones en escabeche, rápido y fácil. 4 morrones cortados en tiras de un par de cm de ancho (es importante que le saques las fibras blancas), unos 8 dientes de ajo (o depende de cuanto te guste), laurel, una o dos hojas, pimentón, sal, pimienta, orégano, 200 cc de agua, 250 cc de vinagre y 250 cc de aceite neutro. Lleva todo a hervor en una olla y luego baja el fuego y dejas cocinar hasta que los morrones estén tiernos. Una vez que está listo, lo pasas a un frasco de vidrio que esterilizaste hirviéndolo una media hora y el cual rociaste con un poco de alcohol, y cerras herméticamente. Guárdalo en la heladera.
Y por último, ratatouille. Berenjena, cebolla, zuccini, tomate y, no podía faltar, Morrón. Hay varias formas de hacerlo. Excepto el morrón, que vas a usar medio, del resto una unidad. Podés cortar todo en cuadraditos, y en una sartén con aceite de oliva y un poco de romero, cocinas la cebolla y el morrón salpimentados. Después, agregas la berenjena y cocinas un rato. Por último, incoporás el tomate sin cáscara y sin semillas. Por último, espolvoreas con perejil picado. Podes usarlo como guarnición, relleno para tartas o empanadas, medialunas y facturas.
<img class="aligncenter" src="https://img53.imageshack.us/img53/6648/e5r7ye45u7yr3rj7.jpg" alt="" width="640" height="192" />
Morrón rojo. Rojo pasión. **Los Rayos** pasión. | 110.145455 | 743 | 0.765434 | spa_Latn | 0.988998 |
22c2f159d784fd019a0b5b843b1f65a174a60bf4 | 699 | md | Markdown | CHANGELOG.md | cptroot/hashbrown | a12b490a3227022e08a455d6b4c680d1e8dc9430 | [
"Apache-2.0",
"MIT"
] | null | null | null | CHANGELOG.md | cptroot/hashbrown | a12b490a3227022e08a455d6b4c680d1e8dc9430 | [
"Apache-2.0",
"MIT"
] | null | null | null | CHANGELOG.md | cptroot/hashbrown | a12b490a3227022e08a455d6b4c680d1e8dc9430 | [
"Apache-2.0",
"MIT"
] | null | null | null | # Change Log
All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](http://keepachangelog.com/)
and this project adheres to [Semantic Versioning](http://semver.org/).
## [Unreleased]
## v0.1.2 - 2018-10-31
### Fixed
- `clear` segfaults when called on an empty table. (#13)
## v0.1.1 - 2018-10-30
### Fixed
- `erase_no_drop` optimization not triggering in the SSE2 implementation. (#3)
- Missing `Send` and `Sync` for hash map and iterator types. (#7)
- Bug when inserting into a table smaller than the group width. (#5)
## v0.1.0 - 2018-10-29
- Initial release
[Unreleased]: https://github.com/japaric/heapless/compare/v0.1.0...HEAD
| 25.888889 | 78 | 0.706724 | eng_Latn | 0.958532 |
22c531b443fb44f4ede01cebac876db1d89b9877 | 1,803 | md | Markdown | docs/units/_unit02/unit02-02_kartenkonstruktion.md | GeoMOER/moer-digitale-kartographie | 3e983cfd32fdb6ab5d50718e81b4ad612ac3c3dc | [
"MIT"
] | null | null | null | docs/units/_unit02/unit02-02_kartenkonstruktion.md | GeoMOER/moer-digitale-kartographie | 3e983cfd32fdb6ab5d50718e81b4ad612ac3c3dc | [
"MIT"
] | null | null | null | docs/units/_unit02/unit02-02_kartenkonstruktion.md | GeoMOER/moer-digitale-kartographie | 3e983cfd32fdb6ab5d50718e81b4ad612ac3c3dc | [
"MIT"
] | null | null | null | ---
title: Modellierung | Kartenkonstruktion
toc: true
header:
image: /assets/images/02-splash.jpg
image_description: "Blick ins Lahntal mit Grünlandwirtschaft, Baustelle für Stromtrassen und Regenbogen."
caption: "Foto: T. Nauss / CC0"
---
***Konstruktion von Karten und Diskussion deren Eigenschaften.***
Nach der Bearbeitung dieser Modellierungsaufgabe sollen Sie in der Lage sein,
* die Erde mittels einfacher Kartenkonstruktionen abzubilden,
* die Eigenschaften der Konstruktion zu beschreiben.
Für die Bearbeitung benötigen Sie Stifte, Geodreieck, Zirkel und Milimeterpapier.
## Konstruktion einer Karte
Konstruieren Sie eine stereographische polständige Azimutalprojektion im Maßstab 1:100.000.000.
Die Karte soll den Bereich zwischen 30° östlicher Länge und 150° westlicherLänge mit Breiten- und Längengradintervallen von 10° abdecken. Verwenden Sie einen Erdradius von 6370 km.
Vergleichen Sie das Gradnetz Ihrer Karte mit dem auf einem Globus. Welche Verzerrungen treten in Ihrer Karte auf?
## Messen in der Karte
Zeichnen Sie die folgenden Orte in die Karte ein:
1. *Seattle (Washington, USA): 47° 36′ 22″ N, 122° 19′ 55″ W*
2. *St. John's (Neufundland, Kanada): 47° 33′ 59″ N, 52° 42′ 19″ W*
3. *Winnipeg (Manitoba, Kanada): 49° 53′ 46″ N, 97° 8′ 34″ W*
4. *Mexico-City (Mexiko): 19° 26′ 0″ N, 99° 8′ 0″ W*
Messen Sie den Abstand zwischen den Orten 1 und 2 sowie 3 und 4 und berechnen Sie die hierdurch gegebene Distanz unter Berücksichtigung des oben angegebenen Nennmaßstabs.
Diskutieren Sie mit Ihren Kommiliton/innen das Ergebnis der Messung im Vergleich zum tatsächlichen Abstand der Orte entlang der Luftlinie, den Sie im Internet recherchiert haben. Welche Rolle spielt die Projektion? Was bedeutet Nennmaßstab und was ist der wahre Maßstab Ihrer Karte? | 47.447368 | 282 | 0.772601 | deu_Latn | 0.997697 |
22c71e156bf7ff4a284fec7c9cbcd4c0fac2db1f | 3,694 | md | Markdown | source/_posts/louisville_qb_malik_cunningham_carted_off_the_field_after_crashing_into_empty_stands_during_a_game.md | soumyadipdas37/finescoop.github.io | 0346d6175a2c36d4054083c144b7f8364db73f2f | [
"MIT"
] | null | null | null | source/_posts/louisville_qb_malik_cunningham_carted_off_the_field_after_crashing_into_empty_stands_during_a_game.md | soumyadipdas37/finescoop.github.io | 0346d6175a2c36d4054083c144b7f8364db73f2f | [
"MIT"
] | null | null | null | source/_posts/louisville_qb_malik_cunningham_carted_off_the_field_after_crashing_into_empty_stands_during_a_game.md | soumyadipdas37/finescoop.github.io | 0346d6175a2c36d4054083c144b7f8364db73f2f | [
"MIT"
] | 2 | 2021-09-18T12:06:26.000Z | 2021-11-14T15:17:34.000Z | ---
extends: _layouts.post
section: content
image: https://i.dailymail.co.uk/1s/2020/09/26/23/33664128-0-image-a-4_1601158641299.jpg
title: Louisville QB Malik Cunningham carted off the field after crashing into empty stands during a game
description: A frightening scene broke out during Saturdays Louisville-Pittsburgh game, as Quarterback Malik Cunningham had to be carted off the field with a neck brace.
date: 2020-09-26-23-53-59
categories: [latest, news]
featured: true
---
Malik Cunningham, a quarterback for Louisville ended up having to be stretchered off the field on Saturday with what appeared to be some sort of head or neck injury.
Cunningham was injured late in the game and was hit as he threw the ball. As he landed he appeared to hit his head hard on the turf.
He had to be attended to on the field and was taken off on a stretcher and cart wearing a neck brace, but he managed to give a thumbs up in a 23-20 loss to Pittsburgh.
Quarterback Malik Cunningham was hit while throwing the ball during Louisville's game against Pittsburgh
Malik Cunningham #3 of the Louisville Cardinals throws an interception as he is hit by Calijah Kancey #8 of the Pittsburgh Panthers in the fourth quarter during the game at Heinz Field
Cunningham ended up hitting the ground hard and stayed down
Cunningham was seen lying face down on the turf at Heinz Field for nearly 10 minutes, as emergency medical staff removed his jersey and pads before strapping him to a backboard.
He was eventually rolled over onto his back. As he was being taken off the field, Cunningham gave a 'thumbs up' to fans as he left.
'That's the soldier mentality in him. He gave it his all and he got twisted up. He put his thumb up to let us know he was good so we are going to get back and get better,' running back Javian Hawkins said to the Courier Journal.
Early indications are that Cunningham was expected to make a full recovery according to AL.com.
Hassan Hall #19 of the Louisville Cardinals checks on injured teammate Malik Cunningham #3 in the fourth quarter during the game against the Pittsburgh Panthers
Trainers tend to Louisville quarterback Malik Cunningham (3) after he was injured
Cunningham is carted off the field by paramedics after being injured on a play in the fourth quarter
While he was being carted off, Cunningham gave a thumbs-up to his team and fans
A look at the hit that resulted in #Louisville QB Malik Cunningham being carted off the field. pic.twitter.com/DeG5MeKYGF
The Louisville Cardinals later tweeted in support of their player: 'He's a fighter. #3 with the thumbs up.'
The head coach Scott Satterfield did not describe the exact nature of Cunningham's injury but noted that he was moving all of his limbs while on the ground.
'He stepped up on that play. They had some pass rushers there, and it looked like he got his feet caught up under a couple of their defenders. He got twisted a little bit,' Satterfield said.
'It looks like he's going to be fine,' he continued. 'I don't want to speculate. Obviously they are doing everything precautionary, but he was moving everything.
'The medical team takes every precaution. That's why they took him in to further evaluate him. I have not gotten an update on that, so anything else would be speculation. He did have feeling in his body and his extremities, so that's positive.'
Louisville QB Malik Cunningham gives the thumbs up as he leaves the field in the cart. pic.twitter.com/5wCq0Qrj0F
Malik Cunningham #3 of the Louisville Cardinals is loaded onto a stretcher after being injured on a play in the fourth quarter during the game against the Pittsburgh Panthers at Heinz Field
| 67.163636 | 244 | 0.788305 | eng_Latn | 0.999937 |
22c9d1233245c7428253f94b09b9dc534b0eee3e | 2,312 | md | Markdown | README.md | aryanbaburajan/Lifetree | 706b7c4e1d5fd895637db328d31e034191f747a0 | [
"MIT"
] | 1 | 2021-08-31T11:15:31.000Z | 2021-08-31T11:15:31.000Z | README.md | aryanbaburajan/Lifetree | 706b7c4e1d5fd895637db328d31e034191f747a0 | [
"MIT"
] | null | null | null | README.md | aryanbaburajan/Lifetree | 706b7c4e1d5fd895637db328d31e034191f747a0 | [
"MIT"
] | null | null | null | # LifeTree
[](https://github.com/FOSS-Cell-GECPKD/Lifetree/blob/master/LICENSE)
[](https://github.com/FOSS-Cell-GECPKD/Lifetree/issues)
[](https://gitter.im/FOSS-Cell-GECPKD/Lifetree?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
## About
The project lets you create a beautiful visualisation of a person's life as a tree allowing the users to create new branches, merge branches, commit, etc.
## Setup
#### Clone this repo!
First things first. Make a local clone of this repo so you can work on it from your own computer.
```
git clone https://github.com/FOSS-Cell-GECPKD/Lifetree.git
cd Lifetree
```
#### Running the React App
- open terminal at the repo
```
cd Lifetree
npm start
```
## Instructions
- "Add a branch" -> To create a branch with a name of your choice
- "Commit on" -> To commit on a specific branch
- "Clear" -> To remove all the branchs and the commits
[W.I.P], will update as the project's work progresses
## Contributing to LifeTree
Thanks for checking out our contribution guide. We greatly appreciate any work contributed, no matter how small!
### How to Contribute
When you are ready to start work on an issue:
- Let us know by leaving a comment on the issue. (Also let us know later if you are no longer working on it.)
- Once you are assigned the issue (or once you have claimed the issue) only then proceed to make the Pull Request. This will help avoid multiple PRs pertaining to the same issue.
If you don't see your idea listed, do one of the following:
* **If your contribution is minor,** such as a typo fix, open a pull request.
* **If your contribution is major,** such as a new feature/enhancement, start by opening an issue first. This way, other people can be also involved in the discussion before you do any work.
### Community
Discussions about LifeTree take place on our Gitter Chat. Anyone is welcome to join the conversations.
## License
This project is licensed under the [MIT License](LICENSE).
| 52.545455 | 256 | 0.759083 | eng_Latn | 0.985724 |
22c9df70a70e68972bb0904ebfc8af9f3986b7b2 | 2,018 | md | Markdown | _posts/2020-11-12-change_as_tire.md | hanjae-jeong/hanjae-jeong.github.io | d9aa184c307026469edcee9dd0f8bd9461429aa0 | [
"MIT"
] | null | null | null | _posts/2020-11-12-change_as_tire.md | hanjae-jeong/hanjae-jeong.github.io | d9aa184c307026469edcee9dd0f8bd9461429aa0 | [
"MIT"
] | 1 | 2021-09-28T05:40:39.000Z | 2021-09-28T05:40:39.000Z | _posts/2020-11-12-change_as_tire.md | hanjae-jeong/hanjae-jeong.github.io | d9aa184c307026469edcee9dd0f8bd9461429aa0 | [
"MIT"
] | null | null | null | ---
layout: post
date: 2020-11-12 16:00:00 +0900
title: "사계절 타이어로 교체"
tags: ['아우디', 'suv', '전기차', 'e-트론', '이트론', '코스트코타이어', '휠스타', '사계절타이어', '금호타이어', '크루젠hp71', 'audi', 'e-tron', 'costco', 'whellstar', 'kumhotire', 'cruzenhp71']
category: ['전기차/e-트론']
image: /assets/img/as_tire.jpg
---
입동(11/7)이 지나고 날이 부쩍 추워짐에 따라 타이어를 교체해야 겠다는 생각을 부쩍하게되었다. 그리고 드디어 코스트코에서 타이어 행사를 한다길래 지금이구나! 싶어 타이어 재고를 확인하고자 가장 가까운 코스트코 공세점에 전화를 했다.
> "타이어 재고 확인하려고 전화했습니다. 금호타이어 크루젠 hp71.."
>> "저희는 금호 타이어 취급 안 합니다"
> "앗! 네..."
코스트코 타이어 행사만 기다리고 있었는데, 망했다. 그 다음 가까운 코스트코인 양재점, 광명점에 전화를 했다. 아! 우선 코스트코 고객센터 번호는 1899-9900 이다. 그러나 타이어 재고 확인을 위해서는 타이어 센터 직통 전화로 해야한다. 고객센터에 물어보면 알려주긴 하는데, 구글에 검색하면 아래처림 누군가 찍어놓은 사진들이 있다.
양재점, 광명점은 금호타이어를 취급한다고 했다. e-트론 출고 타이어 사이즈인 255/50R20을 얘기했더니 재고가 없다고 한다. 직접 와서 주문을 넣고 입고되면 방문하여 교체하면 된다고 한다.
광명, 양재점을 두 번이나 방문할 생각을 하니 굳이? 라는 생각이 들었다. 8만원 코스트코 상품권이 생기고 교체에 대해 믿음이 간다는 장점이 있지만 동네 평점 좋은 곳에 방문하는 게 낫겠다는 생각이 들었다.
그렇게 해서 찾아보니 집 근처에 **휠스타** 에 대한 평이 괜찮았다. 출근하면서 매일 보던 곳이다. 외관이 오래되어서 크게 신경을 안 썼는데 나름 오래된 곳이고 잘 본다고 한다.
블로그에 가격을 모두 공개했고, 현금/카드 동일인 것도 마음에 들었다.
[http://blog.daum.net/wheelstar/6591763?category=1669185](http://blog.daum.net/wheelstar/6591763?category=1669185){:target="_blank"}
내가 바꾸려는 금호 크루젠HP71, 255/50R20 은 개당 16만원이었다. 휠 얼라이먼트는 별도 비용이라 했는데 아직은 할 필요가 없어서 찾아보지 않았다.
[사계절 타이어]({% post_url 2020-10-17-as_tire %})
카카오톡("휠스타" 검색)으로 재고 확인 후 예약을 하고 예약금 10만원을 송금했다. 예약한 시간에 방문하여 타이어 교체를 했다. 이젠 뭐 익숙하지만 e-트론 버추얼 미러에 대한 관심을 보이셨다. 그리고 가격이 얼마인지 충전이 불편하진 않은지 물어보셨다.
타이어 교체는 30분 걸렸다. 모든 것을 다 볼 수 있었고, 옆에 있어도 개의치 않는 것도 마음에 들었다. 요즘 들어 타이어가게들이 문제가 많은데 왠지 믿음이 갔다. 기존 타이어는 가지고 간다고 얘기했었고, 하나하나 비닐에 포장해주셨다. 타이어를 트렁크에 그냥 넣으면 좀 지저분해지지 않을 까 했었는데 다행이었다.
남은 잔금 54만원은 카드로 계산을 했다. 집에 돌아오는 길에 혹시나 기존 타이어 대비 이질감이 느껴지면 어떠나 했었는데 기우였다. 5분만 주행을 해서 잘 모르겠지만 최소한 기존 타이어와 이질감은 느껴지지 않았다.
기존 타이어들을 창고에 넣어놓고 당근마켓에 판매글을 올렸다. 윈터타이어로 교체하는 이 시기에 서머타이어(여름타이어)가 팔릴 지 모르겠지만 좋은 주인을 만났으면 좋겠다. | 28.422535 | 188 | 0.673935 | kor_Hang | 1.00001 |
22c9fc18f40281b0ce50177705ef2be9735c8beb | 2,814 | md | Markdown | README.md | aushe02/SensorFusionSimulinkIntro | 39fffe128436228d2fcf47f3eb0457fe72f02b6f | [
"MIT"
] | null | null | null | README.md | aushe02/SensorFusionSimulinkIntro | 39fffe128436228d2fcf47f3eb0457fe72f02b6f | [
"MIT"
] | null | null | null | README.md | aushe02/SensorFusionSimulinkIntro | 39fffe128436228d2fcf47f3eb0457fe72f02b6f | [
"MIT"
] | null | null | null | # SensorFusionSimulinkIntro
## [Video 1](https://www.youtube.com/watch?v=6qV3YjFppuc&list=PL8z3JLwN_PhGPR0FMGy1xcl_kja2HBIQV&index=1&t=2s)
* Sensor Fusion - Combinding two or more data sources in a way that generates a better understanding of the system
* Physical World -> Sense -> Percieve -> Plan -> Act
* Sense
* Percieve
* self-awareness: localization and positioning
* situational awareness: detection and tracking
* Plan
* Act
* 4 Applications for sensor fustion
* Increase the quality of the data
* Sensor data is noisy ex use two accel and fuse data together 4 sensors = 1/2 noise
* Reduce noise with two different sensor types ex gyro and mag (Common filter ex Kalman Filter)
* Increase Relibility
* Backup if a sensor fails
* Could use three sensors have to be careful of single failure that can happen to all sensors (GPS, wind model)
* It can be used to estimate unmeasured states
* Gyro and Accel to measure distance
* Used to increase coverage areas
* Cars with multiple proximity sensors
## [Video 2](https://www.youtube.com/watch?v=0rlvvYgmTvI&list=PL8z3JLwN_PhGPR0FMGy1xcl_kja2HBIQV&index=2)
* Focus on using magnetometer, accelerometer, gyro
* Orientation is decribed as a rotation
* Referance frame
* Specify rotation
* Roll, pitch yaw
* Direction cosine matrix (DCM)
* Quaternion
* Represent a 3d rotation between two coordinate frames
* North, East, Down
* Mag
* Hard iron source - generates own magnetic field
* Magnet
* Coil
* Distortion circle
* Soft iron source - does not generate it's own magnetic field is magnetic
* Nail
* Structural elements
* Distortion oval
* Mag Calibration
* Perfect system would be a cirlce correct by finding offset using transformation matrix and bias
* Phone move in circle before using compass
* Fix corrupting linear acceleration
* Run through model to extimate linear acceleration
* Drone
* ignore outside of threshold
* Add a gyro to measure angular rate of system
* Mag, accel, and gyro packed together as IMU
* Gryo Measurment
* equation
* Dead reckoning
* Downsides
* Need to know inital orientation
* Sensors aren't perfect still have noise (need more than 2 sensors)
* Use sensor fusion to combind accel + mag + gryo
* Algorithms
* Complementary
* Kalman
* Madgwick
* Mahony
* Initalize Altitude
* Use mag field and gravity to correct gryo drift
* Accel + mag |-----------------------------------------------------------| gyro
## [Video 3](https://www.youtube.com/watch?v=hN8dL55rP5I&t=0s)
## [Video 4](https://www.youtube.com/watch?v=hJG08iWlres&t=0s)
## [Video 5](https://www.youtube.com/watch?v=IIt1LHIHYc4&t=0s)
| 38.547945 | 115 | 0.690476 | eng_Latn | 0.944893 |
22cb06334a25f809dbbace95df93932ca3ef91a6 | 1,033 | markdown | Markdown | content/post/2007-08-12-prejudice.markdown | tomslee/academic-kickstart | ae06f20427c85560713f5abab4ce938ce78cd474 | [
"MIT"
] | null | null | null | content/post/2007-08-12-prejudice.markdown | tomslee/academic-kickstart | ae06f20427c85560713f5abab4ce938ce78cd474 | [
"MIT"
] | null | null | null | content/post/2007-08-12-prejudice.markdown | tomslee/academic-kickstart | ae06f20427c85560713f5abab4ce938ce78cd474 | [
"MIT"
] | null | null | null | ---
author: Tom Slee
comments: true
date: 2007-08-12 17:43:05+00:00
excerpt: "\n\t\t\t\t\t\t"
layout: post
link: http://tomslee.net/2007/08/prejudice.html
slug: prejudice
title: "\n\t\t\t\tPreconceptions\t\t"
wordpress_id: 204
---
If you read this paragraph about Kanye West [from today's Observer](http://observer.guardian.co.uk/omm/story/0,,2144021,00.html) and don't do a double take, you have fewer preconceptions than I.
<blockquote>An only child ('Kanye' is an Ethiopian name which means 'the only
one'), whose parents split before he was a year old and who divorced
when he was four, Kanye was mainly raised by his doting mother, Donda.
They are still extremely close; he wrote a song for her on his last
album, 'Hey Mama', which, sweetly, she now has as the ringtone on her
cellphone. When Kanye was still a young child, they moved from Atlanta,
Georgia, to Chicago, where she became the chair of the English
department at Chicago State University before latterly taking over as
his manager.
>
> </blockquote>
| 32.28125 | 194 | 0.747338 | eng_Latn | 0.998736 |
22cbc07bc8ba82f1dd09a88e0462aa47c3549c7e | 41 | md | Markdown | add/metadata/ns-System.Windows.Forms.Design.meta.md | ferdeen/dotnet-api-docs | 233109a79714842b6ce02e919ad1cb078267f434 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-06-16T22:24:36.000Z | 2020-06-16T22:24:36.000Z | add/metadata/ns-System.Windows.Forms.Design.meta.md | ferdeen/dotnet-api-docs | 233109a79714842b6ce02e919ad1cb078267f434 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | add/metadata/ns-System.Windows.Forms.Design.meta.md | ferdeen/dotnet-api-docs | 233109a79714842b6ce02e919ad1cb078267f434 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-05-02T13:31:28.000Z | 2020-05-02T13:31:28.000Z | ---
uid: System.Windows.Forms.Design
---
| 10.25 | 32 | 0.658537 | yue_Hant | 0.842455 |
22ced956015ea3f62eb238a5b134d504cfb4bdbf | 61 | md | Markdown | README.md | ratadune/Damedesu | ef627a2b5ae163cbf44c6ec9b2092ee618c42108 | [
"Unlicense"
] | null | null | null | README.md | ratadune/Damedesu | ef627a2b5ae163cbf44c6ec9b2092ee618c42108 | [
"Unlicense"
] | null | null | null | README.md | ratadune/Damedesu | ef627a2b5ae163cbf44c6ec9b2092ee618c42108 | [
"Unlicense"
] | null | null | null | # Damedesu
memo desu
Now, you can see me.
Soon, you won't.
| 10.166667 | 20 | 0.672131 | eng_Latn | 0.991647 |
22cf2ef91ebcb0ea0d0ef8e75f5123d7d52f25a3 | 3,192 | md | Markdown | readme.md | ZitRos/edu-text-analysis | a03f22f9c6e72e4cac4d38b9e963d1554cae35d0 | [
"MIT"
] | 9 | 2017-11-28T22:42:06.000Z | 2021-01-27T05:05:52.000Z | readme.md | ZitRos/edu-text-analysis | a03f22f9c6e72e4cac4d38b9e963d1554cae35d0 | [
"MIT"
] | null | null | null | readme.md | ZitRos/edu-text-analysis | a03f22f9c6e72e4cac4d38b9e963d1554cae35d0 | [
"MIT"
] | 1 | 2022-02-08T21:55:29.000Z | 2022-02-08T21:55:29.000Z | # TF-IDF, Sigma and Other (Experimental) Texts Analysing Tools
[TF-IDF](https://en.wikipedia.org/wiki/Tf%E2%80%93idf) and Sigma analysis written in Python, which
outputs results to the convenient *.xlsx spreadsheets for detailed analysis.
TF-IDF analysis allows to detect the most "important" words in the given text of some text corpus
(set of articles, etc). These "important" words are those which occur in the particular document
more than in any other document of the same text corpus.
While TF-IDF analysis is useful for a set of articles, Sigma analysis is useful to analyze the most
"important" words in a single, usually large text (books, documents, etc).
There are a couple of more advanced scripts:
+ Matrix output for Gephi in `gephi.py`. Sample output file is `gephi.csv` in this repository.
+ Horizontal visibility graph building with `hor-vis-graph.py`. A couple of sample files are included in `hor-vis-graph/` directory.
+ Other experiments (see below)
Preview / Examples
------------------
Experimental semantic network builder (main concepts from [this article](http://news.bbc.co.uk/2/hi/technology/4276125.stm)):
TF-IDF applied to some news articles text corpus:
Sigma method applied to the book "The Hunger Games":
Analysis of [article about Putin](http://news.bbc.co.uk/2/hi/business/4120339.stm) with horizontal visibility graph and other articles text corpus:
Usage
-----
1. Install Python 3, clone the repository, enter repository directory with `cd edu-tf-idf`.
2. Install required dependencies: `pip3 install -r requirements.txt`.
3. Place texts to analyze in `/texts` directory (there are a couple already).
4. Run the analyzer with `py tf-idf.py` command (there are many!).
Example
-------
##### TF-IDF: Run the program (by default, picks texts from `texts/news`):
```bash
py tf-idf.py
```
Result:
```text
Reading texts...
Done! Computing TF-IDF ranks...
Progressing text 2225/2225
Done! Writing results...
Writing worksheet 2225/2225
Done!
```
Output goes to `tf-idf.xlsx` file ready for analysis.
##### Sigma method (by default, picks texts from `texts/books`):
```bash
py sigma.py
```
Result goes to `sigma.xlsx` file.
##### Horizontal Visibility Graph (exports to `hor-vis-graph/` directory, picks from `texts/news`):
```bash
py hor-vis-graph.py
```
Check the result in `hor-vis-graph/` directory, visualize it using [Gephi](https://gephi.org/).
##### Individual Text Analysis
Run experimental semantic network builder with
```bash
py analyze_text.py texts/news/tech/001.txt
```
Check the result in `analyzed/<text-title>` directory, visualize it using [Gephi](https://gephi.org/).
License
-------
[MIT](license) © [Nikita Savchenko](https://nikita.tk)
| 32.571429 | 147 | 0.745301 | eng_Latn | 0.816731 |
22cf3c53d935a973568285a68a1df5a3032399ae | 5,463 | md | Markdown | src/packages/__VUE/category/doc.en-US.md | zys-contrib/nutui | 470e0a473353944781a6581582aa9f22617047b4 | [
"MIT"
] | null | null | null | src/packages/__VUE/category/doc.en-US.md | zys-contrib/nutui | 470e0a473353944781a6581582aa9f22617047b4 | [
"MIT"
] | null | null | null | src/packages/__VUE/category/doc.en-US.md | zys-contrib/nutui | 470e0a473353944781a6581582aa9f22617047b4 | [
"MIT"
] | null | null | null | # Category
### Intro
Component for displaying product categories.
### Install
```javascript
import { createApp } from "vue";
import { Category, CategoryPane } from "@nutui/nutui";
const app = createApp();
app.use(Category);
app.use(CategoryPane);
```
### Classic Classification Mod
:::demo
```html
<template>
<nut-category :category="category" @change="change">
<nut-categorypane :categoryChild="categoryChild" @onChange="onChange">
</nut-categorypane>
</nut-category>
</template>
<script lang="ts">
import { reactive, toRefs, onMounted } from 'vue';
export default {
setup() {
const data = reactive({
categoryInfo: {},
category: [{}],
categoryChild: [{}]
});
onMounted(() => {
setTimeout(() => {
getData();
}, 500);
});
const getData = () => {
fetch('//storage.360buyimg.com/nutui/3x/categoryData.js')
.then((response) => response.json())
.then((res) => {
const { categoryInfo, categoryChild } = res;
data.categoryInfo = categoryInfo;
data.category = categoryInfo.category;
data.categoryChild = categoryChild;
})
.catch((err) => console.log('Oh, error', err));
};
const change = (index: any) => {
data.categoryChild = [].concat(data.categoryInfo.category[index + 1].children as any);
};
const onChange =()=>{
console.log("Click on current category data");
}
return {
onChange,
change,
...toRefs(data)
}
}
};
</script>
```
:::
### Show Text Only
:::demo
```html
<template>
<nut-category :category="category" @change="changeText">
<nut-categorypane
type="text"
:categoryChild="categoryChild"
@onChange="onChange"
>
</nut-categorypane
></nut-category>
</template>
<script lang="ts">
import { reactive, toRefs, onMounted } from 'vue';
export default {
setup() {
const data = reactive({
categoryInfo: {},
category: [{}],
categoryChild: [{}]
});
onMounted(() => {
setTimeout(() => {
getData();
}, 500);
});
const getData = () => {
fetch('//storage.360buyimg.com/nutui/3x/categoryData.js')
.then((response) => response.json())
.then((res) => {
console.log('res', res)
const { categoryInfo, categoryChild } = res;
data.categoryInfo = categoryInfo;
data.category = categoryInfo.category;
data.categoryChild = categoryChild;
})
.catch((err) => console.log('Oh, error', err));
};
const changeText = (index: any) => {
data.categoryChild = [].concat(data.categoryInfo.category[index + 1].children as any);
};
const onChange =()=>{
console.log("Click on current category data");
}
return {
changeText,
onChange,
...toRefs(data)
}
}
};
</script>
```
:::
### Custom taxonomy
:::demo
```html
<template>
<nut-category @change="changeCustom"
><nut-categorypane
type="custom"
:customCategory="customCategory"
@onChange="changeCustom"
>
</nut-categorypane
></nut-category>
</template>
<script lang="ts">
import { reactive, toRefs, onMounted } from 'vue';
export default {
setup() {
const data = reactive({
customCategory: [{}],
});
onMounted(() => {
setTimeout(() => {
getData();
}, 500);
});
const getData = () => {
fetch('//storage.360buyimg.com/nutui/3x/categoryData.js')
.then((response) => response.json())
.then((res) => {
const { customCategory } = res;
data.customCategory = customCategory;
})
.catch((err) => console.log('Oh, error', err));
};
const changeCustom = () => {
console.log('Click to categorize data')
};
return {
changeCustom,
...toRefs(data)
}
}
};
</script>
```
:::
## API
### Category Props
| Attribute | Description | Type | Default |
| -------- | -------------------------------- | ------ | -------- |
| type | Classification mode: `classify`, `text`, `custom` | String | classify |
| category | Left navigation bar data list | Array | [] |
### Category Events
| Event | Description | Arguments |
| ------------- | ------------------------------------------------ | ---------- |
| change | Classic classification, click on the left navigation bar to get the data list on the right | Clicked data |
| change-text | In text classification mode, click on the left navigation bar to get the data list on the right | Input data |
| change-custom | Customize, click the left navigation bar to get the data list on the right | Current quantity |
### CategoryPane Props
| Attribute | Description | Type | Default |
| --------------- | -------------------- | ----- | ------ |
| category-child | The current classification data is displayed on the right | Array | [] |
| custom-category | Custom categorical data | Array | [] |
### CategoryPane Events
| Event | Description | Arguments |
| --------- | -------------------- | ---------- |
| on-change | Click on the right classified data trigger | Clicked data |
## CategoryPane Slots
| Name | Description |
| ------- | ---------- |
| default | Custom content |
| 24.831818 | 131 | 0.540545 | eng_Latn | 0.260218 |
22cf63057ab2aebea9be6bd6322907b54757bb21 | 222 | md | Markdown | README.md | 1Gokul/where-is-the-iss | f1e5c534453bf6b5d44a3700a0ccc8036558be56 | [
"MIT"
] | null | null | null | README.md | 1Gokul/where-is-the-iss | f1e5c534453bf6b5d44a3700a0ccc8036558be56 | [
"MIT"
] | null | null | null | README.md | 1Gokul/where-is-the-iss | f1e5c534453bf6b5d44a3700a0ccc8036558be56 | [
"MIT"
] | null | null | null | # Where is the ISS right now?
A simple web app that finds and displays the current location of the International Space Station.
Check it out at [iss-position-finder.netlify.app](https://iss-position-finder.netlify.app).
| 37 | 97 | 0.779279 | eng_Latn | 0.95839 |
22cfb0b4644785bc0af98785712691a8a9bbfddc | 2,082 | md | Markdown | content/authors/admin/_index.md | jp-godfrey/starter-academic-jgodfrey | be710de8005c64e38437fb9d587540b89f10768c | [
"MIT"
] | null | null | null | content/authors/admin/_index.md | jp-godfrey/starter-academic-jgodfrey | be710de8005c64e38437fb9d587540b89f10768c | [
"MIT"
] | null | null | null | content/authors/admin/_index.md | jp-godfrey/starter-academic-jgodfrey | be710de8005c64e38437fb9d587540b89f10768c | [
"MIT"
] | null | null | null | ---
title: Jammieca Godfrey
role: Ph.D. Student
avatar_filename: headshot.jpeg
bio: ""
interests:
- Data Analysis
- Project Management
- Programming
- Research
- Evaluation
social:
- icon: envelope
icon_pack: fas
link: /#contact
- icon: twitter
icon_pack: fab
link: https://twitter.com/JammiecaGodfrey
- icon: linkedin
icon_pack: fab
link: https://www.linkedin.com/in/jammieca-godfrey-20798940/
organizations:
- name: University of Southern Mississippi
url: https://www.usm.edu/
education:
courses:
- course: PhD Education- Research, Evaluation, Statistics, and Assessment
institution: University of Southern Mississippi
year: 2020
- course: "M.Ed. Education Administration "
institution: Liberty Univeristy
year: 2011
- course: BS Business-Finance
institution: Liberty University
year: 2007
email: [email protected]
superuser: true
user_groups: []
highlight_name: false
---
I am a PhD student in the Education Department (RESA) at the University of Southern Mississippi. I have served as an educator in multiple capacities such as Day Treatment Educator, Edgenuity facilitator, and an Independent Educational Consultant. My research centers on various aspects of STEM with a particular focus on diversity as it relates to women and minorities and campus climate specifically inclusion, support, and transition into the workforce. My research agenda includes statistical techniques and data analysis. Those specific techniques and analysis include predictive models, Kitagawa–Blinder–Oaxaca (KBO) decompositions, and quantitative analysis. Another line of inquiry that peaks my interest centers around programming languages such as R, SAS, and SPSS. I envision my approach to research as examination of the data. Although the background is important, I would like to focus on telling a story with the data that is collected or presented to me.
{{< icon name="download" pack="fas" >}} Download my {{< staticref "uploads/JPGodfrey ResumeR.pdf" "newtab" >}}resumé{{< /staticref >}}.
| 47.318182 | 968 | 0.756484 | eng_Latn | 0.964929 |
22d04bce0471794123945548f3053093a3a5b49a | 105 | md | Markdown | Help/Features/Click_Tray_Icon_To_Restore_Main_Window_From_Tray.md | DrCopyPaste/RecNForget | 12b613b1779809d1bf62d934823143c65045b805 | [
"Apache-2.0"
] | 3 | 2019-12-16T20:11:49.000Z | 2020-04-14T17:03:12.000Z | Help/Features/Click_Tray_Icon_To_Restore_Main_Window_From_Tray.md | DrCopyPaste/RecNForget | 12b613b1779809d1bf62d934823143c65045b805 | [
"Apache-2.0"
] | 77 | 2019-12-27T12:16:01.000Z | 2021-11-03T18:04:54.000Z | Help/Features/Click_Tray_Icon_To_Restore_Main_Window_From_Tray.md | DrCopyPaste/RecNForget | 12b613b1779809d1bf62d934823143c65045b805 | [
"Apache-2.0"
] | null | null | null | When RecNForget is running in the background, you can double-click its tray icon to show the main window. | 105 | 105 | 0.809524 | eng_Latn | 0.999879 |
22d21f64136b06aa0a27f2bfb7933158f241148b | 1,538 | md | Markdown | docs/standard/data/xml/extending-xslt-style-sheets.md | adamsitnik/docs.pl-pl | c83da3ae45af087f6611635c348088ba35234d49 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/standard/data/xml/extending-xslt-style-sheets.md | adamsitnik/docs.pl-pl | c83da3ae45af087f6611635c348088ba35234d49 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/standard/data/xml/extending-xslt-style-sheets.md | adamsitnik/docs.pl-pl | c83da3ae45af087f6611635c348088ba35234d49 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Rozszerzanie arkuszy stylów XSLT
ms.date: 03/30/2017
ms.technology: dotnet-standard
ms.assetid: df4ba2bf-a99e-4d22-bbf3-04fc67669dbc
author: mairaw
ms.author: mairaw
ms.openlocfilehash: ff952df59dc8291b12df2b238052d4c40c834e2a
ms.sourcegitcommit: 9b552addadfb57fab0b9e7852ed4f1f1b8a42f8e
ms.translationtype: MT
ms.contentlocale: pl-PL
ms.lasthandoff: 04/23/2019
ms.locfileid: "61966494"
---
# <a name="extending-xslt-style-sheets"></a>Rozszerzanie arkuszy stylów XSLT
W tej sekcji opisano różne metody rozszerzania funkcji XSLT. Możesz dodać obiekty rozszerzeń lub parametrów przy użyciu <xref:System.Xml.Xsl.XsltArgumentList> klasy. Następnie można wywołać obiekty rozszerzeń lub parametrów z arkusza stylów. Ponadto można również osadzić Bloki skryptu do arkusza stylów za pomocą `msxsl:script` elementu.
## <a name="in-this-section"></a>W tej sekcji
[Obiekty rozszerzeń XSLT](../../../../docs/standard/data/xml/xslt-extension-objects.md)
Omawia przy użyciu <xref:System.Xml.Xsl.XsltArgumentList> klasy obiekty rozszerzeń XSLT procesu.
[Parametry XSLT](../../../../docs/standard/data/xml/xslt-parameters.md)
Omawia przy użyciu <xref:System.Xml.Xsl.XsltArgumentList> klas z parametrami XSLT procesu.
[Bloki skryptów i element msxsl:script](../../../../docs/standard/data/xml/script-blocks-using-msxsl-script.md)
Omawia przy użyciu `msxsl:script` elementu.
## <a name="related-sections"></a>Sekcje pokrewne
[Przekształcenia XSLT](../../../../docs/standard/data/xml/xslt-transformations.md)
| 51.266667 | 340 | 0.76788 | pol_Latn | 0.97197 |
22d270ef788bfae0e523f979f71a664afd45b714 | 65 | md | Markdown | README.md | mneumann/expression-rs | 683cea802aff940a732dc06c7b78ecfc098a1a67 | [
"MIT"
] | 1 | 2015-12-27T06:33:33.000Z | 2015-12-27T06:33:33.000Z | README.md | mneumann/expression-rs | 683cea802aff940a732dc06c7b78ecfc098a1a67 | [
"MIT"
] | null | null | null | README.md | mneumann/expression-rs | 683cea802aff940a732dc06c7b78ecfc098a1a67 | [
"MIT"
] | null | null | null | # expression-rs
Represenation of expression terms and conditions
| 21.666667 | 48 | 0.846154 | eng_Latn | 0.99243 |
22d3d4d8a8d45aa9271cb86399eafeb2137f292c | 204,603 | md | Markdown | resources/docs/source/.compare.md | DRC-COVID19/stopcoronavirus.cd | e9a7cd22d2a066124082d483bcf53e49a67b49ef | [
"MIT"
] | 7 | 2021-01-23T20:58:02.000Z | 2022-01-24T14:08:17.000Z | resources/docs/source/.compare.md | DRC-COVID19/stopcoronavirus.cd | e9a7cd22d2a066124082d483bcf53e49a67b49ef | [
"MIT"
] | 26 | 2020-05-08T19:30:15.000Z | 2022-03-07T12:00:29.000Z | resources/docs/source/.compare.md | DRC-COVID19/stopcoronavirus.cd | e9a7cd22d2a066124082d483bcf53e49a67b49ef | [
"MIT"
] | 6 | 2020-04-30T15:56:12.000Z | 2021-11-16T14:07:23.000Z | ---
title: API Reference
language_tabs:
- javascript
includes:
search: true
toc_footers:
- <a href='http://github.com/mpociot/documentarian'>Documentation Powered by Documentarian</a>
---
<!-- START_INFO -->
# Info
Welcome to the generated API reference.
<!-- END_INFO -->
#AdminiRole management
<!-- START_6b710b60044785af19560ab9f91fd740 -->
## Display a listing of the admin_roles.
<br><small style="padding: 1px 9px 2px;font-weight: bold;white-space: nowrap;color: #ffffff;-webkit-border-radius: 9px;-moz-border-radius: 9px;border-radius: 9px;background-color: #3a87ad;">Requires authentication</small>
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/admin_roles"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (200):
```json
[
{
"id": 1,
"name": "Administrator",
"slug": "administrator",
"created_at": "2020-03-24T17:17:05.000000Z",
"updated_at": "2020-03-24T17:17:05.000000Z"
}
]
```
### HTTP Request
`GET api/admin_roles`
<!-- END_6b710b60044785af19560ab9f91fd740 -->
<!-- START_593ce68eea712cf6757763a71b641cb1 -->
## Store a newly created resource in storage.
<br><small style="padding: 1px 9px 2px;font-weight: bold;white-space: nowrap;color: #ffffff;-webkit-border-radius: 9px;-moz-border-radius: 9px;border-radius: 9px;background-color: #3a87ad;">Requires authentication</small>
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/admin_roles"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "POST",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
### HTTP Request
`POST api/admin_roles`
<!-- END_593ce68eea712cf6757763a71b641cb1 -->
<!-- START_72bec43a5269d7f1743ded7b03c40336 -->
## Display the specified resource.
<br><small style="padding: 1px 9px 2px;font-weight: bold;white-space: nowrap;color: #ffffff;-webkit-border-radius: 9px;-moz-border-radius: 9px;border-radius: 9px;background-color: #3a87ad;">Requires authentication</small>
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/admin_roles/1"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (401):
```json
{
"message": "Unauthenticated."
}
```
### HTTP Request
`GET api/admin_roles/{admin_role}`
<!-- END_72bec43a5269d7f1743ded7b03c40336 -->
<!-- START_b3719d13e4f86b02bfbe6bb88ffcaff3 -->
## Update the specified resource in storage.
<br><small style="padding: 1px 9px 2px;font-weight: bold;white-space: nowrap;color: #ffffff;-webkit-border-radius: 9px;-moz-border-radius: 9px;border-radius: 9px;background-color: #3a87ad;">Requires authentication</small>
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/admin_roles/1"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "PUT",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
### HTTP Request
`PUT api/admin_roles/{admin_role}`
`PATCH api/admin_roles/{admin_role}`
<!-- END_b3719d13e4f86b02bfbe6bb88ffcaff3 -->
<!-- START_c7b622488e9e39d56ee3808da74537a8 -->
## Remove the specified resource from storage.
<br><small style="padding: 1px 9px 2px;font-weight: bold;white-space: nowrap;color: #ffffff;-webkit-border-radius: 9px;-moz-border-radius: 9px;border-radius: 9px;background-color: #3a87ad;">Requires authentication</small>
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/admin_roles/1"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "DELETE",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
### HTTP Request
`DELETE api/admin_roles/{admin_role}`
<!-- END_c7b622488e9e39d56ee3808da74537a8 -->
#Administrator management
<!-- START_7e2b7a1ebbd3335d2dab3468cd7b48ef -->
## Display a listing of the admin_users paginate by 15.
<br><small style="padding: 1px 9px 2px;font-weight: bold;white-space: nowrap;color: #ffffff;-webkit-border-radius: 9px;-moz-border-radius: 9px;border-radius: 9px;background-color: #3a87ad;">Requires authentication</small>
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/admin_users"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (200):
```json
{
"data": [
{
"id": 1,
"name": "Admin",
"email": "[email protected]",
"usernmae": "admin",
"avatar": "http:\/\/localhost:8000\/img\/admin\/avatar_placeholder.png",
"roles": [
{
"id": 1,
"name": "Adm",
"slug": "adm",
"created_at": "2020-03-24 17:17:05",
"updated_at": "2020-03-24 17:17:05",
"pivot": {
"user_id": 1,
"role_id": 1
}
}
],
"isAdmin": true,
"isHospitalManager": false,
"hospital": null,
"isHospitalAdmin": false
}
],
"links": {
"first": "http:\/\/localhost\/api\/admin_users?page=1",
"last": "http:\/\/localhost\/api\/admin_users?page=7",
"prev": null,
"next": "http:\/\/localhost\/api\/admin_users?page=2"
},
"meta": {
"current_page": 1,
"from": 1,
"last_page": 7,
"path": "http:\/\/localhost\/api\/admin_users",
"per_page": 15,
"to": 15,
"total": 95
}
}
```
### HTTP Request
`GET api/admin_users`
<!-- END_7e2b7a1ebbd3335d2dab3468cd7b48ef -->
<!-- START_2c7c40eba56e473f8e40f6f212c7db36 -->
## Store a newly created admin_users in storage.
<br><small style="padding: 1px 9px 2px;font-weight: bold;white-space: nowrap;color: #ffffff;-webkit-border-radius: 9px;-moz-border-radius: 9px;border-radius: 9px;background-color: #3a87ad;">Requires authentication</small>
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/admin_users"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
let body = {
"username": "architecto",
"password": "vero",
"password_confirmation": "aut",
"name": "quibusdam",
"email": "temporibus",
"roles_id": []
}
fetch(url, {
method: "POST",
headers: headers,
body: body
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (201):
```json
null
```
> Example response (401):
```json
{
"message": "Unauthenticated"
}
```
### HTTP Request
`POST api/admin_users`
#### Body Parameters
Parameter | Type | Status | Description
--------- | ------- | ------- | ------- | -----------
`username` | string | required | username.
`password` | string | required | password
`password_confirmation` | string | required | password_confirmation
`name` | string | required | name
`email` | email | required | email
`roles_id` | array | required | roles_id
<!-- END_2c7c40eba56e473f8e40f6f212c7db36 -->
<!-- START_77d0a2d5bb8f4587de5f705abe169e91 -->
## Display a admin_users by id.
<br><small style="padding: 1px 9px 2px;font-weight: bold;white-space: nowrap;color: #ffffff;-webkit-border-radius: 9px;-moz-border-radius: 9px;border-radius: 9px;background-color: #3a87ad;">Requires authentication</small>
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/admin_users/1"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (200):
```json
{
"id": 1,
"name": "Admin",
"email": "[email protected]",
"usernmae": "admin",
"avatar": "http:\/\/localhost:8000\/img\/admin\/avatar_placeholder.png",
"roles": [
{
"id": 1,
"name": "Adm",
"slug": "adm",
"created_at": "2020-03-24 17:17:05",
"updated_at": "2020-03-24 17:17:05",
"pivot": {
"user_id": 1,
"role_id": 1
}
}
],
"isAdmin": true,
"isHospitalManager": false,
"hospital": null,
"isHospitalAdmin": false
}
```
### HTTP Request
`GET api/admin_users/{admin_user}`
#### URL Parameters
Parameter | Status | Description
--------- | ------- | ------- | -------
`admin_users` | required | The ID of the admin_users
<!-- END_77d0a2d5bb8f4587de5f705abe169e91 -->
<!-- START_5153b8bc63349e63de278397894ab00f -->
## Update the specified admin_user by id in storage.
<br><small style="padding: 1px 9px 2px;font-weight: bold;white-space: nowrap;color: #ffffff;-webkit-border-radius: 9px;-moz-border-radius: 9px;border-radius: 9px;background-color: #3a87ad;">Requires authentication</small>
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/admin_users/1"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
let body = {
"username": "labore",
"password": "ut",
"name": "praesentium",
"email": "illum",
"roles_id": []
}
fetch(url, {
method: "PUT",
headers: headers,
body: body
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (200):
```json
{
"id": 1,
"name": "Admin",
"email": "[email protected]",
"usernmae": "admin",
"avatar": "http:\/\/localhost:8000\/img\/admin\/avatar_placeholder.png",
"roles": [
{
"id": 1,
"name": "Adm",
"slug": "adm",
"created_at": "2020-03-24 17:17:05",
"updated_at": "2020-03-24 17:17:05",
"pivot": {
"user_id": 1,
"role_id": 1
}
}
],
"isAdmin": true,
"isHospitalManager": false,
"hospital": null,
"isHospitalAdmin": false
}
```
> Example response (401):
```json
{
"message": "Unauthenticated"
}
```
### HTTP Request
`PUT api/admin_users/{admin_user}`
`PATCH api/admin_users/{admin_user}`
#### URL Parameters
Parameter | Status | Description
--------- | ------- | ------- | -------
`admin_users` | required | The ID of the admin_users.
#### Body Parameters
Parameter | Type | Status | Description
--------- | ------- | ------- | ------- | -----------
`username` | string | required | username.
`password` | string | required | password
`name` | string | required | name
`email` | email | required | email
`roles_id` | array | required | roles_id
<!-- END_5153b8bc63349e63de278397894ab00f -->
<!-- START_3c2aaa798572fdf62053d5cf4eb65ace -->
## Remove the specified resource by id from storage.
<br><small style="padding: 1px 9px 2px;font-weight: bold;white-space: nowrap;color: #ffffff;-webkit-border-radius: 9px;-moz-border-radius: 9px;border-radius: 9px;background-color: #3a87ad;">Requires authentication</small>
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/admin_users/1"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "DELETE",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (200):
```json
null
```
> Example response (401):
```json
{
"message": "Unauthenticated"
}
```
### HTTP Request
`DELETE api/admin_users/{admin_user}`
#### URL Parameters
Parameter | Status | Description
--------- | ------- | ------- | -------
`admin_users` | required | The ID of the admin_users
<!-- END_3c2aaa798572fdf62053d5cf4eb65ace -->
#Auth management
APIs for managing users Auth
<!-- START_3ec94b50b1c8c9ba798a36fdfacd3fef -->
## Get a JWT token via given credentials.
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/auth/login"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "POST",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
### HTTP Request
`POST api/dashboard/auth/login`
<!-- END_3ec94b50b1c8c9ba798a36fdfacd3fef -->
<!-- START_c06cffaa29eb1a4afb4762c6f9371f54 -->
## Log the user out (Invalidate the token)
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/auth/logout"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "POST",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
### HTTP Request
`POST api/dashboard/auth/logout`
<!-- END_c06cffaa29eb1a4afb4762c6f9371f54 -->
<!-- START_cc5e781c890dcdb5df9a044e41b6d046 -->
## Refresh a token.
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/auth/refresh"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "POST",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
### HTTP Request
`POST api/dashboard/auth/refresh`
<!-- END_cc5e781c890dcdb5df9a044e41b6d046 -->
<!-- START_a42a29c08e1a8f12410ef29926b9cf37 -->
## Get the authenticated User
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/auth/me"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "POST",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
### HTTP Request
`POST api/dashboard/auth/me`
<!-- END_a42a29c08e1a8f12410ef29926b9cf37 -->
<!-- START_e01b76a41eaf415c2592c091d5cbceac -->
## api/dashboard/auth/lost-password
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/auth/lost-password"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "POST",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
### HTTP Request
`POST api/dashboard/auth/lost-password`
<!-- END_e01b76a41eaf415c2592c091d5cbceac -->
<!-- START_26d65dc82ba5f697509288fb8771a15c -->
## api/dashboard/auth/check-token/{token}
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/auth/check-token/1"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (410):
```json
{
"response": "Resource not found"
}
```
### HTTP Request
`GET api/dashboard/auth/check-token/{token}`
<!-- END_26d65dc82ba5f697509288fb8771a15c -->
<!-- START_0f4c99b97ea7c2a47962807aca43f9e8 -->
## api/dashboard/auth/reset-password/{user_id}
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/auth/reset-password/1"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "POST",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
### HTTP Request
`POST api/dashboard/auth/reset-password/{user_id}`
<!-- END_0f4c99b97ea7c2a47962807aca43f9e8 -->
#PandemicStat management
<!-- START_899a7c38cc8e101353d8be8601041afe -->
## api/pandemic-stats
<br><small style="padding: 1px 9px 2px;font-weight: bold;white-space: nowrap;color: #ffffff;-webkit-border-radius: 9px;-moz-border-radius: 9px;border-radius: 9px;background-color: #3a87ad;">Requires authentication</small>
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/pandemic-stats"
);
let params = {
"order": "exercitationem",
};
Object.keys(params)
.forEach(key => url.searchParams.append(key, params[key]));
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (200):
```json
{
"data": [
{
"id": 6,
"confirmed": 1,
"sick": null,
"seriously": null,
"healed": null,
"dead": null,
"imported": null,
"local": null,
"last_update": "2020-03-10 00:00:00",
"created_at": "2020-03-27T01:53:25.000000Z",
"updated_at": "2020-03-27T01:53:25.000000Z"
}
],
"links": {
"first": "http:\/\/localhost:8000\/api\/pandemic-stats?page=1",
"last": "http:\/\/localhost:8000\/api\/pandemic-stats?page=19",
"prev": null,
"next": "http:\/\/localhost:8000\/api\/pandemic-stats?page=2"
},
"meta": {
"current_page": 1,
"from": 1,
"last_page": 19,
"path": "http:\/\/localhost:8000\/api\/pandemic-stats",
"per_page": 15,
"to": 15,
"total": 281
}
}
```
### HTTP Request
`GET api/pandemic-stats`
#### Query Parameters
Parameter | Status | Description
--------- | ------- | ------- | -----------
`order` | optional | optional default ASC last_update order
<!-- END_899a7c38cc8e101353d8be8601041afe -->
<!-- START_93c494ef5765386d61f789a6744ac5d4 -->
## Store a newly created admin_users in storage.
<br><small style="padding: 1px 9px 2px;font-weight: bold;white-space: nowrap;color: #ffffff;-webkit-border-radius: 9px;-moz-border-radius: 9px;border-radius: 9px;background-color: #3a87ad;">Requires authentication</small>
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/pandemic-stats"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
let body = {
"confirmed": 19,
"local": 11,
"imported": 15,
"sick": 13,
"seriously": 7,
"healed": 18,
"dead": 6,
"last_update": "inventore"
}
fetch(url, {
method: "POST",
headers: headers,
body: body
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (201):
```json
null
```
> Example response (422):
```json
{
"message": "The given data was invalid.",
"errors": {
"last_update": [
"La valeur du champ last update est déjà utilisée."
]
}
}
```
### HTTP Request
`POST api/pandemic-stats`
#### Body Parameters
Parameter | Type | Status | Description
--------- | ------- | ------- | ------- | -----------
`confirmed` | integer | optional | optional confirmed.
`local` | integer | optional | optional local
`imported` | integer | optional | optional imported
`sick` | integer | optional | optional sick
`seriously` | integer | optional | optional seriously
`healed` | integer | optional | optional healed
`dead` | integer | optional | optional dead
`last_update` | Date | optional | required|unique last_update
<!-- END_93c494ef5765386d61f789a6744ac5d4 -->
<!-- START_565517e1afaf7d3185e01454eb9bf3c0 -->
## Display a PandemicStat by id.
<br><small style="padding: 1px 9px 2px;font-weight: bold;white-space: nowrap;color: #ffffff;-webkit-border-radius: 9px;-moz-border-radius: 9px;border-radius: 9px;background-color: #3a87ad;">Requires authentication</small>
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/pandemic-stats/consequatur"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (200):
```json
{
"id": 17,
"confirmed": 109,
"sick": 97,
"seriously": null,
"healed": 3,
"dead": 9,
"imported": null,
"local": null,
"last_update": "2020-03-31 00:00:00",
"created_at": "2020-04-01T01:27:03.000000Z",
"updated_at": "2020-04-01T01:27:03.000000Z"
}
```
### HTTP Request
`GET api/pandemic-stats/{pandemic_stat_id}`
#### URL Parameters
Parameter | Status | Description
--------- | ------- | ------- | -------
`pandemic_stat_id` | required | The ID of the PandemicStat
<!-- END_565517e1afaf7d3185e01454eb9bf3c0 -->
<!-- START_0e45a5f5869b888ad069efe157a92dff -->
## Update a PandemicStat in storage.
<br><small style="padding: 1px 9px 2px;font-weight: bold;white-space: nowrap;color: #ffffff;-webkit-border-radius: 9px;-moz-border-radius: 9px;border-radius: 9px;background-color: #3a87ad;">Requires authentication</small>
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/pandemic-stats/qui"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
let body = {
"confirmed": 12,
"local": 2,
"imported": 12,
"sick": 1,
"seriously": 9,
"healed": 14,
"dead": 6,
"last_update": "ut"
}
fetch(url, {
method: "PUT",
headers: headers,
body: body
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (200):
```json
{
"id": 17,
"confirmed": 109,
"sick": 97,
"seriously": null,
"healed": 3,
"dead": 9,
"imported": null,
"local": null,
"last_update": "2020-03-31 00:00:00",
"created_at": "2020-04-01T01:27:03.000000Z",
"updated_at": "2020-04-01T01:27:03.000000Z"
}
```
### HTTP Request
`PUT api/pandemic-stats/{pandemic_stat_id}`
#### URL Parameters
Parameter | Status | Description
--------- | ------- | ------- | -------
`pandemic_stat_id` | required | The ID of the PandemicStat
#### Body Parameters
Parameter | Type | Status | Description
--------- | ------- | ------- | ------- | -----------
`confirmed` | integer | optional | optional confirmed.
`local` | integer | optional | optional local
`imported` | integer | optional | optional imported
`sick` | integer | optional | optional sick
`seriously` | integer | optional | optional seriously
`healed` | integer | optional | optional healed
`dead` | integer | optional | optional dead
`last_update` | Date | optional | required|unique last_update
<!-- END_0e45a5f5869b888ad069efe157a92dff -->
#User management
APIs for managing users
<!-- START_60fdb642281a006b32553e18909d0533 -->
## Test diagnostic covid-19
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/self-test"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
let body = {
"temperature_cat": 6,
"cough": 17,
"agueusia_anosmia": 11,
"sore_throat_aches": 9,
"diarrhea": 2,
"tiredness": 1,
"tiredness_details": 1,
"feeding_day": 8,
"breathlessness": 9,
"age": 11,
"size": 1,
"weight": 8,
"heart_disease": 1,
"diabetes": 12,
"cancer": 17,
"breathing_disease": 9,
"kidney_disease": 4,
"liver_disease": 3,
"pregnant": 7,
"immunosuppressant_disease": 19,
"immunosuppressant_drug": 6,
"province": "eius",
"town": "deleniti",
"township": "dolorem",
"longitude": "quia",
"latitude": "similique"
}
fetch(url, {
method: "POST",
headers: headers,
body: body
})
.then(response => response.json())
.then(json => console.log(json));
```
### HTTP Request
`POST api/self-test`
#### Body Parameters
Parameter | Type | Status | Description
--------- | ------- | ------- | ------- | -----------
`temperature_cat` | integer | required | between:1,5 Pensez-vous avoir ou avoir eu de la fièvre ces 48 dernières heures (frissons, sueurs) ?
`cough` | integer | required | between:0,1 Ces derniers jours, avez-vous une toux ou une augmentation de votre toux habituelle ?
`agueusia_anosmia` | integer | required | between:0,1 Ces derniers jours, avez-vous noté une forte diminution ou perte de votre goût ou de votre odorat ?
`sore_throat_aches` | integer | required | between:0,1 Ces derniers jours, avez-vous eu un mal de gorge et/ou des douleurs musculaires et/ou des courbatures inhabituelles ?
`diarrhea` | integer | required | between:0,1 Ces dernières 24 heures, avez-vous de la diarrhée ? Avec au moins 3 selles molles"
`tiredness` | integer | required | between:0,1 Ces derniers jours, avez-vous une fatigue inhabituelle ?"
`tiredness_details` | integer | required | between:0,1 Cette fatigue vous oblige-t-elle à vous reposer plus de la moitié de la journée ?
`feeding_day` | integer | required | between:0,1 Êtes vous dans l'impossibilité de vous alimenter ou de boire DEPUIS 24 HEURES OU PLUS ?
`breathlessness` | integer | required | between:0,1 Dans les dernières 24 heures, avez-vous noté un manque de souffle INHABITUEL lorsque vous parlez ou faites un petit effort ?
`age` | integer | required | between:1,120 Quel est votre âge ? Ceci, afin de calculer un facteur de risque spécifique.
`size` | integer | required | between:80,250 Quel est votre taille ? Afin de calculer l’indice de masse corporelle qui est un facteur influençant le risque de complications de l’infection.
`weight` | integer | required | between:20,250 Quel est votre poids ? Afin de calculer l’indice de masse corporelle qui est un facteur influençant le risque de complications de l’infection.
`heart_disease` | integer | required | between:0,2 Avez-vous de l’hypertension artérielle mal équilibrée ? Ou avez-vous une maladie cardiaque ou vasculaire ? Ou prenez vous un traitement à visée cardiologique ?
`diabetes` | integer | required | between:0,1 Êtes-vous diabétique ?
`cancer` | integer | required | between:0,1 Avez-vous ou avez-vous eu un cancer ces trois dernières années ?
`breathing_disease` | integer | required | between:0,1 Avez-vous une maladie respiratoire ? Ou êtes-vous suivi par un pneumologue ?
`kidney_disease` | integer | required | between:0,1 Avez-vous une insuffisance rénale chronique dialysée ?
`liver_disease` | integer | required | between:0,1 Avez-vous une maladie chronique du foie ?
`pregnant` | integer | required | between:0,2 Êtes-vous enceinte ?
`immunosuppressant_disease` | integer | required | between:0,2 Avez-vous une maladie connue pour diminuer vos défenses immunitaires ?
`immunosuppressant_drug` | integer | required | between:0,2 Prenez-vous un traitement immunosuppresseur ? C’est un traitement qui diminue vos défenses contre les infections. Voici quelques exemples : corticoïdes, méthotrexate, ciclosporine, tacrolimus, azathioprine, cyclophosphamide (liste non exhaustive)
`province` | string | optional | Quel est votre Province ? Cette information nous permet de réaliser un suivi épidémiologique.
`town` | string | optional | Quel est votre ville ? Cette information nous permet de réaliser un suivi épidémiologique.
`township` | string | optional | Quel est votre commune ? Cette information nous permet de réaliser un suivi épidémiologique.
`longitude` | longitude, | optional | Cette information nous permet de réaliser un suivi épidémiologique.
`latitude` | latitude, | optional | Cette information nous permet de réaliser un suivi épidémiologique.
<!-- END_60fdb642281a006b32553e18909d0533 -->
#general
<!-- START_d6261f926c26d068ce14643c8bb66ab1 -->
## Store a newly created resource in storage.
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/medicale-orientation"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "POST",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
### HTTP Request
`POST api/medicale-orientation`
<!-- END_d6261f926c26d068ce14643c8bb66ab1 -->
<!-- START_a5638ea523c7896e9ddba59f1d631c74 -->
## Display a listing of the resource.
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/flux/africell/health-zone"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (401):
```json
{
"message": "Unauthenticated."
}
```
### HTTP Request
`GET api/dashboard/flux/africell/health-zone`
<!-- END_a5638ea523c7896e9ddba59f1d631c74 -->
<!-- START_a5a559225335a0534cb5858a2448816e -->
## api/dashboard/flux/africell/presence/provinces
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/flux/africell/presence/provinces"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (422):
```json
{
"message": "The given data was invalid.",
"errors": {
"fluxGeoOptions": [
"Le champ flux geo options est obligatoire."
],
"observation_start": [
"Le champ observation start est obligatoire."
],
"observation_end": [
"Le champ observation end est obligatoire."
]
}
}
```
### HTTP Request
`GET api/dashboard/flux/africell/presence/provinces`
<!-- END_a5a559225335a0534cb5858a2448816e -->
<!-- START_c0a626b2dad640b864bd26d4862f6934 -->
## api/dashboard/flux/africell/presence/zones
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/flux/africell/presence/zones"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (422):
```json
{
"message": "The given data was invalid.",
"errors": {
"fluxGeoOptions": [
"Le champ flux geo options est obligatoire."
],
"observation_start": [
"Le champ observation start est obligatoire."
],
"observation_end": [
"Le champ observation end est obligatoire."
]
}
}
```
### HTTP Request
`GET api/dashboard/flux/africell/presence/zones`
<!-- END_c0a626b2dad640b864bd26d4862f6934 -->
<!-- START_262c3b29e4a6764190590b3308d86b32 -->
## api/dashboard/flux/africell/hors-zone/zones
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/flux/africell/hors-zone/zones"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (422):
```json
{
"message": "The given data was invalid.",
"errors": {
"fluxGeoOptions": [
"Le champ flux geo options est obligatoire."
],
"observation_start": [
"Le champ observation start est obligatoire."
],
"observation_end": [
"Le champ observation end est obligatoire."
]
}
}
```
### HTTP Request
`GET api/dashboard/flux/africell/hors-zone/zones`
<!-- END_262c3b29e4a6764190590b3308d86b32 -->
<!-- START_2bc61c8e8b0d6c9823bc053cdf9775b8 -->
## api/dashboard/flux/africell/in-out/zones
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/flux/africell/in-out/zones"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (422):
```json
{
"message": "The given data was invalid.",
"errors": {
"fluxGeoOptions": [
"Le champ flux geo options est obligatoire."
],
"observation_start": [
"Le champ observation start est obligatoire."
],
"observation_end": [
"Le champ observation end est obligatoire."
]
}
}
```
### HTTP Request
`GET api/dashboard/flux/africell/in-out/zones`
<!-- END_2bc61c8e8b0d6c9823bc053cdf9775b8 -->
<!-- START_6a2525c49abcbf48442b3c101ab7d8da -->
## api/dashboard/flux/predefined/zones/h-24
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/flux/predefined/zones/h-24"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (401):
```json
{
"message": "Unauthenticated."
}
```
### HTTP Request
`GET api/dashboard/flux/predefined/zones/h-24`
<!-- END_6a2525c49abcbf48442b3c101ab7d8da -->
<!-- START_000dbfc8b1531adc7aded98e5279b8da -->
## api/dashboard/flux/predefined/zones/h-24/daily
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/flux/predefined/zones/h-24/daily"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (401):
```json
{
"message": "Unauthenticated."
}
```
### HTTP Request
`GET api/dashboard/flux/predefined/zones/h-24/daily`
<!-- END_000dbfc8b1531adc7aded98e5279b8da -->
<!-- START_1be4594974b5a905881e6b8c4e4f7f6e -->
## api/dashboard/flux/predefined/zones/h-24/daily-compare
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/flux/predefined/zones/h-24/daily-compare"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (401):
```json
{
"message": "Unauthenticated."
}
```
### HTTP Request
`GET api/dashboard/flux/predefined/zones/h-24/daily-compare`
<!-- END_1be4594974b5a905881e6b8c4e4f7f6e -->
<!-- START_486e8a162349f460091b87f1bf95fcdd -->
## api/dashboard/flux/predefined/zones/h-24/daily-in
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/flux/predefined/zones/h-24/daily-in"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (401):
```json
{
"message": "Unauthenticated."
}
```
### HTTP Request
`GET api/dashboard/flux/predefined/zones/h-24/daily-in`
<!-- END_486e8a162349f460091b87f1bf95fcdd -->
<!-- START_fdffde34b554d7948ee195e19d543fd4 -->
## api/dashboard/flux/predefined/zones/h-24/daily-out
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/flux/predefined/zones/h-24/daily-out"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (401):
```json
{
"message": "Unauthenticated."
}
```
### HTTP Request
`GET api/dashboard/flux/predefined/zones/h-24/daily-out`
<!-- END_fdffde34b554d7948ee195e19d543fd4 -->
<!-- START_5364843de6936b05dbc20b180cfe4589 -->
## api/dashboard/flux/origin/zones/h-24
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/flux/origin/zones/h-24"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (422):
```json
{
"message": "The given data was invalid.",
"errors": {
"fluxGeoOptions": [
"Le champ flux geo options est obligatoire."
],
"observation_start": [
"Le champ observation start est obligatoire."
],
"observation_end": [
"Le champ observation end est obligatoire."
]
}
}
```
### HTTP Request
`GET api/dashboard/flux/origin/zones/h-24`
<!-- END_5364843de6936b05dbc20b180cfe4589 -->
<!-- START_f8fbe4d5ce379e129e8eba5985fb22df -->
## api/dashboard/flux/origin/zones/h-24/daily
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/flux/origin/zones/h-24/daily"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (422):
```json
{
"message": "The given data was invalid.",
"errors": {
"fluxGeoOptions": [
"Le champ flux geo options est obligatoire."
],
"observation_start": [
"Le champ observation start est obligatoire."
],
"observation_end": [
"Le champ observation end est obligatoire."
]
}
}
```
### HTTP Request
`GET api/dashboard/flux/origin/zones/h-24/daily`
<!-- END_f8fbe4d5ce379e129e8eba5985fb22df -->
<!-- START_03802abdb7f036f49433ee24e09477e5 -->
## api/dashboard/flux/origin/zones/h-24/daily-compare
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/flux/origin/zones/h-24/daily-compare"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (422):
```json
{
"message": "The given data was invalid.",
"errors": {
"fluxGeoOptions": [
"Le champ flux geo options est obligatoire."
],
"observation_start": [
"Le champ observation start est obligatoire."
],
"observation_end": [
"Le champ observation end est obligatoire."
]
}
}
```
### HTTP Request
`GET api/dashboard/flux/origin/zones/h-24/daily-compare`
<!-- END_03802abdb7f036f49433ee24e09477e5 -->
<!-- START_f9751b867e2d1df8cbb881833e4d444d -->
## api/dashboard/flux/origin/zones/h-24/daily-in
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/flux/origin/zones/h-24/daily-in"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (422):
```json
{
"message": "The given data was invalid.",
"errors": {
"fluxGeoOptions": [
"Le champ flux geo options est obligatoire."
],
"observation_start": [
"Le champ observation start est obligatoire."
],
"observation_end": [
"Le champ observation end est obligatoire."
]
}
}
```
### HTTP Request
`GET api/dashboard/flux/origin/zones/h-24/daily-in`
<!-- END_f9751b867e2d1df8cbb881833e4d444d -->
<!-- START_8d5adf4f7ec9f65f7b4d6a91fac9101d -->
## api/dashboard/flux/origin/zones/h-24/daily-out
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/flux/origin/zones/h-24/daily-out"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (422):
```json
{
"message": "The given data was invalid.",
"errors": {
"fluxGeoOptions": [
"Le champ flux geo options est obligatoire."
],
"observation_start": [
"Le champ observation start est obligatoire."
],
"observation_end": [
"Le champ observation end est obligatoire."
]
}
}
```
### HTTP Request
`GET api/dashboard/flux/origin/zones/h-24/daily-out`
<!-- END_8d5adf4f7ec9f65f7b4d6a91fac9101d -->
<!-- START_6f89b7bb585666c0f21534b713abd065 -->
## api/dashboard/flux/origin/zones/h-24/global-in/province
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/flux/origin/zones/h-24/global-in/province"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (422):
```json
{
"message": "The given data was invalid.",
"errors": {
"fluxGeoOptions": [
"Le champ flux geo options est obligatoire."
],
"observation_start": [
"Le champ observation start est obligatoire."
],
"observation_end": [
"Le champ observation end est obligatoire."
]
}
}
```
### HTTP Request
`GET api/dashboard/flux/origin/zones/h-24/global-in/province`
<!-- END_6f89b7bb585666c0f21534b713abd065 -->
<!-- START_fa35a9c1161bf86912a7edf2ec613406 -->
## api/dashboard/flux/origin/zones/h-24/global-out/province
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/flux/origin/zones/h-24/global-out/province"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (422):
```json
{
"message": "The given data was invalid.",
"errors": {
"fluxGeoOptions": [
"Le champ flux geo options est obligatoire."
],
"observation_start": [
"Le champ observation start est obligatoire."
],
"observation_end": [
"Le champ observation end est obligatoire."
]
}
}
```
### HTTP Request
`GET api/dashboard/flux/origin/zones/h-24/global-out/province`
<!-- END_fa35a9c1161bf86912a7edf2ec613406 -->
<!-- START_1b63356dee84de87122967c64756ecd4 -->
## api/dashboard/flux/origin/zones/m-30
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/flux/origin/zones/m-30"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (401):
```json
{
"message": "Unauthenticated."
}
```
### HTTP Request
`GET api/dashboard/flux/origin/zones/m-30`
<!-- END_1b63356dee84de87122967c64756ecd4 -->
<!-- START_8c58af349ae17c522c2e2776ae2fa29a -->
## api/dashboard/flux/origin/zones/m-30/daily-compare
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/flux/origin/zones/m-30/daily-compare"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (401):
```json
{
"message": "Unauthenticated."
}
```
### HTTP Request
`GET api/dashboard/flux/origin/zones/m-30/daily-compare`
<!-- END_8c58af349ae17c522c2e2776ae2fa29a -->
<!-- START_689cb04dcb76ec8689c87fc57e6dd3c2 -->
## api/dashboard/flux/origin/zones/m-30/daily
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/flux/origin/zones/m-30/daily"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (401):
```json
{
"message": "Unauthenticated."
}
```
### HTTP Request
`GET api/dashboard/flux/origin/zones/m-30/daily`
<!-- END_689cb04dcb76ec8689c87fc57e6dd3c2 -->
<!-- START_77e42f65ee0b3499e6679ae5d63ad0ee -->
## api/dashboard/flux/origin/zones/m-30/daily-in
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/flux/origin/zones/m-30/daily-in"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (401):
```json
{
"message": "Unauthenticated."
}
```
### HTTP Request
`GET api/dashboard/flux/origin/zones/m-30/daily-in`
<!-- END_77e42f65ee0b3499e6679ae5d63ad0ee -->
<!-- START_c9959fdcb9dab5eab56e42c446eb957d -->
## api/dashboard/flux/origin/zones/m-30/daily-out
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/flux/origin/zones/m-30/daily-out"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (401):
```json
{
"message": "Unauthenticated."
}
```
### HTTP Request
`GET api/dashboard/flux/origin/zones/m-30/daily-out`
<!-- END_c9959fdcb9dab5eab56e42c446eb957d -->
<!-- START_8ecbb8b195e3c5ac6067120bcdeea82b -->
## api/dashboard/flux/origin/zones/presence/h-24
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/flux/origin/zones/presence/h-24"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (401):
```json
{
"message": "Unauthenticated."
}
```
### HTTP Request
`GET api/dashboard/flux/origin/zones/presence/h-24`
<!-- END_8ecbb8b195e3c5ac6067120bcdeea82b -->
<!-- START_fc4451eaeb39b0a7a9ad7fe88fc2081c -->
## api/dashboard/flux/origin/zones/presence/h-24/daily
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/flux/origin/zones/presence/h-24/daily"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (401):
```json
{
"message": "Unauthenticated."
}
```
### HTTP Request
`GET api/dashboard/flux/origin/zones/presence/h-24/daily`
<!-- END_fc4451eaeb39b0a7a9ad7fe88fc2081c -->
<!-- START_1748656ff3a79479501b5a2f4496d466 -->
## api/dashboard/flux/origin/zones/presence/h-24/daily-in
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/flux/origin/zones/presence/h-24/daily-in"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (422):
```json
{
"message": "The given data was invalid.",
"errors": {
"fluxGeoOptions": [
"Le champ flux geo options est obligatoire."
],
"observation_start": [
"Le champ observation start est obligatoire."
],
"observation_end": [
"Le champ observation end est obligatoire."
]
}
}
```
### HTTP Request
`GET api/dashboard/flux/origin/zones/presence/h-24/daily-in`
<!-- END_1748656ff3a79479501b5a2f4496d466 -->
<!-- START_828bfc4c29c8d96150f437eb1fcc65b6 -->
## api/dashboard/flux/origin/provinces/h-24
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/flux/origin/provinces/h-24"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (422):
```json
{
"message": "The given data was invalid.",
"errors": {
"fluxGeoOptions": [
"Le champ flux geo options est obligatoire."
],
"observation_start": [
"Le champ observation start est obligatoire."
],
"observation_end": [
"Le champ observation end est obligatoire."
]
}
}
```
### HTTP Request
`GET api/dashboard/flux/origin/provinces/h-24`
<!-- END_828bfc4c29c8d96150f437eb1fcc65b6 -->
<!-- START_9bf08575078436d688451b9d973a8bd4 -->
## api/dashboard/flux/origin/provinces/h-24/daily
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/flux/origin/provinces/h-24/daily"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (422):
```json
{
"message": "The given data was invalid.",
"errors": {
"fluxGeoOptions": [
"Le champ flux geo options est obligatoire."
],
"observation_start": [
"Le champ observation start est obligatoire."
],
"observation_end": [
"Le champ observation end est obligatoire."
]
}
}
```
### HTTP Request
`GET api/dashboard/flux/origin/provinces/h-24/daily`
<!-- END_9bf08575078436d688451b9d973a8bd4 -->
<!-- START_c836423c68d0d7cdb12e4f80fab52d66 -->
## api/dashboard/flux/origin/provinces/h-24/daily-compare
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/flux/origin/provinces/h-24/daily-compare"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (422):
```json
{
"message": "The given data was invalid.",
"errors": {
"fluxGeoOptions": [
"Le champ flux geo options est obligatoire."
],
"observation_start": [
"Le champ observation start est obligatoire."
],
"observation_end": [
"Le champ observation end est obligatoire."
]
}
}
```
### HTTP Request
`GET api/dashboard/flux/origin/provinces/h-24/daily-compare`
<!-- END_c836423c68d0d7cdb12e4f80fab52d66 -->
<!-- START_8f4e77268c1c25aeade9284e8efcfbf2 -->
## api/dashboard/flux/origin/provinces/h-24/daily-in
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/flux/origin/provinces/h-24/daily-in"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (422):
```json
{
"message": "The given data was invalid.",
"errors": {
"fluxGeoOptions": [
"Le champ flux geo options est obligatoire."
],
"observation_start": [
"Le champ observation start est obligatoire."
],
"observation_end": [
"Le champ observation end est obligatoire."
]
}
}
```
### HTTP Request
`GET api/dashboard/flux/origin/provinces/h-24/daily-in`
<!-- END_8f4e77268c1c25aeade9284e8efcfbf2 -->
<!-- START_090e9ac136af6b9f87eaf94e7e69075e -->
## api/dashboard/flux/origin/provinces/h-24/daily-out
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/flux/origin/provinces/h-24/daily-out"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (422):
```json
{
"message": "The given data was invalid.",
"errors": {
"fluxGeoOptions": [
"Le champ flux geo options est obligatoire."
],
"observation_start": [
"Le champ observation start est obligatoire."
],
"observation_end": [
"Le champ observation end est obligatoire."
]
}
}
```
### HTTP Request
`GET api/dashboard/flux/origin/provinces/h-24/daily-out`
<!-- END_090e9ac136af6b9f87eaf94e7e69075e -->
<!-- START_60316c24765f2362603d53e82f220f90 -->
## api/dashboard/flux/origin/provinces/h-24/global-in
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/flux/origin/provinces/h-24/global-in"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (422):
```json
{
"message": "The given data was invalid.",
"errors": {
"observation_start": [
"Le champ observation start est obligatoire."
],
"observation_end": [
"Le champ observation end est obligatoire."
]
}
}
```
### HTTP Request
`GET api/dashboard/flux/origin/provinces/h-24/global-in`
<!-- END_60316c24765f2362603d53e82f220f90 -->
<!-- START_a262e264fb04610474ea74e8f19609b5 -->
## api/dashboard/flux/origin/provinces/h-24/global-out
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/flux/origin/provinces/h-24/global-out"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (422):
```json
{
"message": "The given data was invalid.",
"errors": {
"observation_start": [
"Le champ observation start est obligatoire."
],
"observation_end": [
"Le champ observation end est obligatoire."
]
}
}
```
### HTTP Request
`GET api/dashboard/flux/origin/provinces/h-24/global-out`
<!-- END_a262e264fb04610474ea74e8f19609b5 -->
<!-- START_5c3804f48ac6741dcfbadff92bbf5e82 -->
## api/dashboard/flux/origin/provinces/m-30
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/flux/origin/provinces/m-30"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (422):
```json
{
"message": "The given data was invalid.",
"errors": {
"fluxGeoOptions": [
"Le champ flux geo options est obligatoire."
],
"observation_start": [
"Le champ observation start est obligatoire."
]
}
}
```
### HTTP Request
`GET api/dashboard/flux/origin/provinces/m-30`
<!-- END_5c3804f48ac6741dcfbadff92bbf5e82 -->
<!-- START_46719746661518ecdcbe467aef294dfe -->
## api/dashboard/flux/origin/provinces/m-30/daily
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/flux/origin/provinces/m-30/daily"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (422):
```json
{
"message": "The given data was invalid.",
"errors": {
"fluxGeoOptions": [
"Le champ flux geo options est obligatoire."
],
"observation_start": [
"Le champ observation start est obligatoire."
]
}
}
```
### HTTP Request
`GET api/dashboard/flux/origin/provinces/m-30/daily`
<!-- END_46719746661518ecdcbe467aef294dfe -->
<!-- START_06daa2d154f22f9a451e20c46d84ce09 -->
## api/dashboard/flux/origin/provinces/m-30/daily-in
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/flux/origin/provinces/m-30/daily-in"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (422):
```json
{
"message": "The given data was invalid.",
"errors": {
"fluxGeoOptions": [
"Le champ flux geo options est obligatoire."
],
"observation_start": [
"Le champ observation start est obligatoire."
]
}
}
```
### HTTP Request
`GET api/dashboard/flux/origin/provinces/m-30/daily-in`
<!-- END_06daa2d154f22f9a451e20c46d84ce09 -->
<!-- START_4198ab63a10e383fa69b21ddf7d0708d -->
## api/dashboard/flux/origin/provinces/m-30/daily-out
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/flux/origin/provinces/m-30/daily-out"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (422):
```json
{
"message": "The given data was invalid.",
"errors": {
"fluxGeoOptions": [
"Le champ flux geo options est obligatoire."
],
"observation_start": [
"Le champ observation start est obligatoire."
]
}
}
```
### HTTP Request
`GET api/dashboard/flux/origin/provinces/m-30/daily-out`
<!-- END_4198ab63a10e383fa69b21ddf7d0708d -->
<!-- START_5ca0cf248735b710c51c91eb602d5487 -->
## api/dashboard/flux/origin/provinces/presence/h-24
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/flux/origin/provinces/presence/h-24"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (401):
```json
{
"message": "Unauthenticated."
}
```
### HTTP Request
`GET api/dashboard/flux/origin/provinces/presence/h-24`
<!-- END_5ca0cf248735b710c51c91eb602d5487 -->
<!-- START_ba8c8ad24e2c756b27f47914dbbb55a7 -->
## api/dashboard/flux/origin/provinces/presence/h-24/daily
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/flux/origin/provinces/presence/h-24/daily"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (401):
```json
{
"message": "Unauthenticated."
}
```
### HTTP Request
`GET api/dashboard/flux/origin/provinces/presence/h-24/daily`
<!-- END_ba8c8ad24e2c756b27f47914dbbb55a7 -->
<!-- START_f90bba3387315f2542178f9be214307c -->
## api/dashboard/flux/origin/provinces/presence/h-24/daily-in
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/flux/origin/provinces/presence/h-24/daily-in"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (422):
```json
{
"message": "The given data was invalid.",
"errors": {
"fluxGeoOptions": [
"Le champ flux geo options est obligatoire."
],
"observation_start": [
"Le champ observation start est obligatoire."
],
"observation_end": [
"Le champ observation end est obligatoire."
]
}
}
```
### HTTP Request
`GET api/dashboard/flux/origin/provinces/presence/h-24/daily-in`
<!-- END_f90bba3387315f2542178f9be214307c -->
<!-- START_4f2ecc8520adc7566b65dd9191ec6204 -->
## Display a listing of the resource.
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/flux/hotspots/list"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (200):
```json
[
{
"id": 103,
"name": "Aéroport Ndjili",
"created_at": null,
"updated_at": "2020-12-23T14:47:16.000000Z",
"min_date": "2020-07-01",
"type": "Aéroport"
},
{
"id": 102,
"name": "Aéroport Ndolo",
"created_at": null,
"updated_at": "2020-12-23T14:47:15.000000Z",
"min_date": "2020-07-01",
"type": "Aéroport"
},
{
"id": 10,
"name": "Arret Bakayaou",
"created_at": null,
"updated_at": "2020-12-16T11:13:00.000000Z",
"min_date": "2020-05-17",
"type": "ArretTransport"
},
{
"id": 7,
"name": "Arret Centre hospitalier de Kintambo",
"created_at": null,
"updated_at": "2020-12-16T11:13:53.000000Z",
"min_date": "2020-05-17",
"type": "ArretTransport"
},
{
"id": 40,
"name": "Arret moulard",
"created_at": null,
"updated_at": "2020-12-16T11:14:21.000000Z",
"min_date": "2020-05-17",
"type": "ArretTransport"
},
{
"id": 80,
"name": "Arret Socimat",
"created_at": null,
"updated_at": "2020-12-16T11:13:46.000000Z",
"min_date": "2020-05-17",
"type": "ArretTransport"
},
{
"id": 8,
"name": "Arret Stade Velodrome",
"created_at": null,
"updated_at": "2020-12-16T11:13:31.000000Z",
"min_date": "2020-05-17",
"type": "Commerces"
},
{
"id": 90,
"name": "Arret Station Centre Superieur",
"created_at": null,
"updated_at": "2020-12-16T11:12:55.000000Z",
"min_date": "2020-05-17",
"type": "Supermarche"
},
{
"id": 17,
"name": "Arret Station Macampagne (ML)",
"created_at": null,
"updated_at": "2020-12-16T11:13:39.000000Z",
"min_date": "2020-05-17",
"type": "ArretTransport"
},
{
"id": 78,
"name": "ASSANEF",
"created_at": null,
"updated_at": "2020-12-16T11:13:14.000000Z",
"min_date": "2020-05-17",
"type": "ArretTransport"
},
{
"id": 75,
"name": "Avenue du Commerce et Kasa vubu",
"created_at": null,
"updated_at": "2020-12-16T11:13:12.000000Z",
"min_date": "2020-05-17",
"type": "ArretTransport"
},
{
"id": 29,
"name": "Baruti Tabernacle",
"created_at": null,
"updated_at": "2020-12-16T11:14:07.000000Z",
"min_date": "2020-05-17",
"type": "Eglises"
},
{
"id": 81,
"name": "BATETELA",
"created_at": null,
"updated_at": "2020-12-16T11:13:50.000000Z",
"min_date": "2020-05-17",
"type": "BureauAdmin"
},
{
"id": 20,
"name": "Benseke Nouvelle Cite",
"created_at": null,
"updated_at": "2020-12-16T11:14:04.000000Z",
"min_date": "2020-05-17",
"type": "Cimetiere"
},
{
"id": 31,
"name": "Binza Arret Maternite",
"created_at": null,
"updated_at": "2020-12-16T11:13:58.000000Z",
"min_date": "2020-05-17",
"type": "ArretTransport"
},
{
"id": 61,
"name": "Carrigres",
"created_at": null,
"updated_at": "2020-12-16T11:13:56.000000Z",
"min_date": "2020-05-17",
"type": "Supermarche"
},
{
"id": 12,
"name": "CE TRINITE",
"created_at": null,
"updated_at": "2020-12-16T11:14:08.000000Z",
"min_date": "2020-05-17",
"type": "Eglises"
},
{
"id": 34,
"name": "Centre d'Evangelisation Peniel CEPE",
"created_at": null,
"updated_at": "2020-12-16T11:13:24.000000Z",
"min_date": "2020-05-17",
"type": "Eglises"
},
{
"id": 76,
"name": "Centre Evangelique Emmanuel Langa-langa",
"created_at": null,
"updated_at": "2020-12-16T11:13:23.000000Z",
"min_date": "2020-05-17",
"type": "Eglises"
},
{
"id": 56,
"name": "Cimetiere Kimbanseke",
"created_at": null,
"updated_at": "2020-12-16T11:14:02.000000Z",
"min_date": "2020-05-17",
"type": "Cimetiere"
},
{
"id": 9,
"name": "Cimetiere Kintambo",
"created_at": null,
"updated_at": "2020-12-16T11:14:21.000000Z",
"min_date": "2020-05-17",
"type": "Cimetiere"
},
{
"id": 95,
"name": "Cimetiere Mingadi",
"created_at": null,
"updated_at": "2020-12-16T11:14:03.000000Z",
"min_date": "2020-05-17",
"type": "Cimetiere"
},
{
"id": 69,
"name": "Cimetiere Ndjili Brasserie",
"created_at": null,
"updated_at": "2020-12-16T11:14:05.000000Z",
"min_date": "2020-05-17",
"type": "Cimetiere"
},
{
"id": 21,
"name": "Cimetiere sans fil",
"created_at": null,
"updated_at": "2020-12-16T11:13:52.000000Z",
"min_date": "2020-05-17",
"type": "Cimetiere"
},
{
"id": 11,
"name": "Croissement Kianza et Universite",
"created_at": null,
"updated_at": "2020-12-16T11:13:30.000000Z",
"min_date": "2020-05-17",
"type": "ArretTransport"
},
{
"id": 3,
"name": "DGC barre",
"created_at": null,
"updated_at": "2020-12-16T11:13:37.000000Z",
"min_date": "2020-05-17",
"type": "ArretTransport"
},
{
"id": 101,
"name": "Dvin",
"created_at": null,
"updated_at": "2020-12-16T11:13:02.000000Z",
"min_date": "2020-05-18",
"type": "Restaurants"
},
{
"id": 42,
"name": "ECC\/CEC\/BUMBU",
"created_at": null,
"updated_at": "2020-12-16T11:13:32.000000Z",
"min_date": "2020-05-17",
"type": "Eglises"
},
{
"id": 37,
"name": "Eglise Catholique Divin Maître",
"created_at": null,
"updated_at": "2020-12-16T11:12:59.000000Z",
"min_date": "2020-05-17",
"type": "Eglises"
},
{
"id": 72,
"name": "Eglise des assemblées de dieu",
"created_at": null,
"updated_at": "2020-12-16T11:13:02.000000Z",
"min_date": "2020-05-17",
"type": "Eglises"
},
{
"id": 55,
"name": "Eglise Francophone Ecole de Tyrannus",
"created_at": null,
"updated_at": "2020-12-16T11:13:18.000000Z",
"min_date": "2020-05-17",
"type": "Eglises"
},
{
"id": 53,
"name": "Eglise Kimbanguiste",
"created_at": null,
"updated_at": "2020-12-16T11:13:29.000000Z",
"min_date": "2020-05-17",
"type": "Eglises"
},
{
"id": 27,
"name": "Eglise locale Cbfc Itaga",
"created_at": null,
"updated_at": "2020-12-16T11:13:20.000000Z",
"min_date": "2020-05-17",
"type": "Eglises"
},
{
"id": 83,
"name": "Eglise Notre Dame de Fatima",
"created_at": null,
"updated_at": "2020-12-16T11:13:11.000000Z",
"min_date": "2020-05-17",
"type": "Eglises"
},
{
"id": 30,
"name": "eglise protestante de lemba",
"created_at": null,
"updated_at": "2020-12-16T11:13:40.000000Z",
"min_date": "2020-05-17",
"type": "Eglises"
},
{
"id": 23,
"name": "Eglise Saint Paul",
"created_at": null,
"updated_at": "2020-12-16T11:13:19.000000Z",
"min_date": "2020-05-17",
"type": "Eglises"
},
{
"id": 35,
"name": "Ejcev Nouvelle Alliance Bima",
"created_at": null,
"updated_at": "2020-12-16T11:13:25.000000Z",
"min_date": "2020-05-17",
"type": "Eglises"
},
{
"id": 84,
"name": "FIKIN",
"created_at": null,
"updated_at": "2020-12-16T11:13:27.000000Z",
"min_date": "2020-05-17",
"type": "Commerces"
},
{
"id": 22,
"name": "Food Market Macampagne",
"created_at": null,
"updated_at": "2020-12-16T11:13:38.000000Z",
"min_date": "2020-05-17",
"type": "Restaurants"
},
{
"id": 66,
"name": "Gabriella",
"created_at": null,
"updated_at": "2020-12-16T11:13:43.000000Z",
"min_date": "2020-05-17",
"type": "Restaurants"
},
{
"id": 97,
"name": "Hall de la Gombe",
"created_at": null,
"updated_at": "2020-12-16T11:13:15.000000Z",
"min_date": "2020-05-17",
"type": "Commerces"
},
{
"id": 71,
"name": "Hopital Biamba Marie Mutombo",
"created_at": null,
"updated_at": "2020-12-16T11:14:13.000000Z",
"min_date": "2020-05-17",
"type": "Hopitaux"
},
{
"id": 24,
"name": "Hopital general de Kintambo",
"created_at": null,
"updated_at": "2020-12-16T11:13:41.000000Z",
"min_date": "2020-05-17",
"type": "Hopitaux"
},
{
"id": 91,
"name": "Hotel du Fleuve",
"created_at": null,
"updated_at": "2020-12-16T11:14:19.000000Z",
"min_date": "2020-05-17",
"type": "Hotels"
},
{
"id": 100,
"name": "HOTEL DU GOUVERNEMENT",
"created_at": null,
"updated_at": "2020-12-16T11:13:46.000000Z",
"min_date": "2020-05-17",
"type": "Supermarche"
},
{
"id": 89,
"name": "Hotel Memling",
"created_at": null,
"updated_at": "2020-12-16T11:12:57.000000Z",
"min_date": "2020-05-17",
"type": "Hotels"
},
{
"id": 73,
"name": "Hotel Sultani",
"created_at": null,
"updated_at": "2020-12-16T11:13:10.000000Z",
"min_date": "2020-05-17",
"type": "Hotels"
},
{
"id": 5,
"name": "Huillerie",
"created_at": null,
"updated_at": "2020-12-16T11:13:04.000000Z",
"min_date": "2020-05-17",
"type": "ArretTransport"
},
{
"id": 82,
"name": "Immeuble CNSS",
"created_at": null,
"updated_at": "2020-12-16T11:13:07.000000Z",
"min_date": "2020-05-17",
"type": "BureauAdmin"
},
{
"id": 93,
"name": "Immeuble Cosmos",
"created_at": null,
"updated_at": "2020-12-16T11:13:37.000000Z",
"min_date": "2020-05-17",
"type": "Commerces"
},
{
"id": 44,
"name": "INA et ORCA",
"created_at": null,
"updated_at": "2020-12-16T11:12:54.000000Z",
"min_date": "2020-05-17",
"type": "Commerces"
},
{
"id": 15,
"name": "INBTP",
"created_at": null,
"updated_at": "2020-12-16T11:14:18.000000Z",
"min_date": "2020-05-17",
"type": "BureauAdmin"
},
{
"id": 1,
"name": "Inconnue",
"created_at": null,
"updated_at": "2020-12-14T10:00:28.000000Z",
"min_date": "2020-05-17",
"type": null
},
{
"id": 14,
"name": "Kinkole",
"created_at": null,
"updated_at": "2020-12-16T11:14:15.000000Z",
"min_date": "2020-05-17",
"type": "Cimetiere"
},
{
"id": 38,
"name": "Kinsuka",
"created_at": null,
"updated_at": "2020-12-16T11:13:57.000000Z",
"min_date": "2020-05-17",
"type": "Cimetiere"
},
{
"id": 86,
"name": "La voix du fleuve",
"created_at": null,
"updated_at": "2020-12-16T11:14:20.000000Z",
"min_date": "2020-05-17",
"type": "Restaurants"
},
{
"id": 18,
"name": "Le cerlce gourmand",
"created_at": null,
"updated_at": "2020-12-16T11:13:10.000000Z",
"min_date": "2020-05-17",
"type": "Restaurants"
},
{
"id": 62,
"name": "le pain de vie",
"created_at": null,
"updated_at": "2020-12-16T11:13:22.000000Z",
"min_date": "2020-05-17",
"type": "Eglises"
},
{
"id": 98,
"name": "Le premier Shopping Mall",
"created_at": null,
"updated_at": "2020-12-16T11:13:09.000000Z",
"min_date": "2020-05-17",
"type": "Commerces"
},
{
"id": 64,
"name": "Lemba Terminus",
"created_at": null,
"updated_at": "2020-12-16T11:14:09.000000Z",
"min_date": "2020-05-17",
"type": "ArretTransport"
},
{
"id": 74,
"name": "Maché De Kadi",
"created_at": null,
"updated_at": "2020-12-16T11:14:17.000000Z",
"min_date": "2020-05-17",
"type": "Marché"
},
{
"id": 41,
"name": "Marché BAYAKA",
"created_at": null,
"updated_at": "2020-12-16T11:12:56.000000Z",
"min_date": "2020-05-17",
"type": "Marché"
},
{
"id": 28,
"name": "Marché central",
"created_at": null,
"updated_at": "2020-12-16T11:13:20.000000Z",
"min_date": "2020-05-17",
"type": "Marché"
},
{
"id": 49,
"name": "Marché de la Liberté",
"created_at": null,
"updated_at": "2020-12-16T11:14:12.000000Z",
"min_date": "2020-05-17",
"type": "ArretTransport"
},
{
"id": 46,
"name": "Marché de Mbanza Lemba",
"created_at": null,
"updated_at": "2020-12-16T11:13:08.000000Z",
"min_date": "2020-05-17",
"type": "Marché"
},
{
"id": 32,
"name": "Marché Delvaux",
"created_at": null,
"updated_at": "2020-12-16T11:13:35.000000Z",
"min_date": "2020-05-17",
"type": "Marché"
},
{
"id": 50,
"name": "Marché Mangobo",
"created_at": null,
"updated_at": "2020-12-16T11:13:55.000000Z",
"min_date": "2020-05-17",
"type": "Marché"
},
{
"id": 68,
"name": "Marché Matete",
"created_at": null,
"updated_at": "2020-12-16T11:14:11.000000Z",
"min_date": "2020-05-17",
"type": "Marché"
},
{
"id": 52,
"name": "Marché Mbika",
"created_at": null,
"updated_at": "2020-12-16T11:14:00.000000Z",
"min_date": "2020-05-17",
"type": "Marché"
},
{
"id": 43,
"name": "Marché selembao",
"created_at": null,
"updated_at": "2020-12-16T11:13:34.000000Z",
"min_date": "2020-05-17",
"type": "Marché"
},
{
"id": 39,
"name": "Matadi Kibala",
"created_at": null,
"updated_at": "2020-12-16T11:13:47.000000Z",
"min_date": "2020-05-17",
"type": "Marché"
},
{
"id": 77,
"name": "Mbudi Nature",
"created_at": null,
"updated_at": "2020-12-16T11:13:56.000000Z",
"min_date": "2020-05-17",
"type": "Commerces"
},
{
"id": 96,
"name": "Mimoza plaza",
"created_at": null,
"updated_at": "2020-12-16T11:13:51.000000Z",
"min_date": "2020-05-17",
"type": "Restaurants"
},
{
"id": 63,
"name": "Ministere combat spirituel",
"created_at": null,
"updated_at": "2020-12-16T11:13:29.000000Z",
"min_date": "2020-05-17",
"type": "Eglises"
},
{
"id": 19,
"name": "Ministere des affaires etrangeres",
"created_at": null,
"updated_at": "2020-12-16T11:13:48.000000Z",
"min_date": "2020-05-17",
"type": "BureauAdmin"
},
{
"id": 58,
"name": "Mosqué Bon Marche",
"created_at": null,
"updated_at": "2020-12-16T11:13:16.000000Z",
"min_date": "2020-05-17",
"type": "Eglises"
},
{
"id": 6,
"name": "Mosqué Centrale Usoke",
"created_at": null,
"updated_at": "2020-12-16T11:13:13.000000Z",
"min_date": "2020-05-17",
"type": "Eglises"
},
{
"id": 88,
"name": "Mosqué Kingabwa",
"created_at": null,
"updated_at": "2020-12-16T11:13:21.000000Z",
"min_date": "2020-05-17",
"type": "Eglises"
},
{
"id": 94,
"name": "Necropole entre ciel et terre",
"created_at": null,
"updated_at": "2020-12-16T11:14:16.000000Z",
"min_date": "2020-05-17",
"type": "Cimetiere"
},
{
"id": 85,
"name": "O'Poeta",
"created_at": null,
"updated_at": "2020-12-16T11:13:42.000000Z",
"min_date": "2020-05-17",
"type": "Restaurants"
},
{
"id": 70,
"name": "ONATRA",
"created_at": null,
"updated_at": "2020-12-16T11:12:52.000000Z",
"min_date": "2020-05-17",
"type": "BureauAdmin"
},
{
"id": 16,
"name": "Parc Mont Ngaliema",
"created_at": null,
"updated_at": "2020-12-16T11:13:01.000000Z",
"min_date": "2020-05-17",
"type": "Commerces"
},
{
"id": 67,
"name": "Paroisse Notre-Dame d'Afrique",
"created_at": null,
"updated_at": "2020-12-16T11:13:28.000000Z",
"min_date": "2020-05-17",
"type": "Eglises"
},
{
"id": 99,
"name": "Paroisse Sacre Coeur",
"created_at": null,
"updated_at": "2020-12-16T11:12:53.000000Z",
"min_date": "2020-05-17",
"type": "Eglises"
},
{
"id": 65,
"name": "Paroisse Saint Eloi",
"created_at": null,
"updated_at": "2020-12-16T11:13:17.000000Z",
"min_date": "2020-05-17",
"type": "Supermarche"
},
{
"id": 36,
"name": "Paroisse saint François-Xavier",
"created_at": null,
"updated_at": "2020-12-16T11:13:26.000000Z",
"min_date": "2020-05-17",
"type": "Eglises"
},
{
"id": 33,
"name": "Peloustore KIVU",
"created_at": null,
"updated_at": "2020-12-16T11:13:59.000000Z",
"min_date": "2020-05-17",
"type": "Supermarche"
},
{
"id": 13,
"name": "Place Commercial de limete(7e rue)",
"created_at": null,
"updated_at": "2020-12-16T11:14:22.000000Z",
"min_date": "2020-05-17",
"type": "Hopitaux"
},
{
"id": 54,
"name": "Place de la gare centrale",
"created_at": null,
"updated_at": "2020-12-16T11:12:58.000000Z",
"min_date": "2020-05-17",
"type": "Hotels"
},
{
"id": 48,
"name": "Place sainte therese",
"created_at": null,
"updated_at": "2020-12-16T11:14:06.000000Z",
"min_date": "2020-05-17",
"type": "ArretTransport"
},
{
"id": 47,
"name": "Pont Matete",
"created_at": null,
"updated_at": "2020-12-16T11:14:10.000000Z",
"min_date": "2020-05-17",
"type": "ArretTransport"
},
{
"id": 87,
"name": "Poste",
"created_at": null,
"updated_at": "2020-12-16T11:13:05.000000Z",
"min_date": "2020-05-17",
"type": "BureauAdmin"
},
{
"id": 57,
"name": "Quartier 1 (croissement Boulevard Lumumba)",
"created_at": null,
"updated_at": "2020-12-16T11:14:14.000000Z",
"min_date": "2020-05-17",
"type": "ArretTransport"
},
{
"id": 51,
"name": "Rond Point Forescom",
"created_at": null,
"updated_at": "2020-12-16T11:13:03.000000Z",
"min_date": "2020-05-17",
"type": "BureauAdmin"
},
{
"id": 45,
"name": "Rond Point Ngaba",
"created_at": null,
"updated_at": "2020-12-16T11:14:05.000000Z",
"min_date": "2020-05-17",
"type": "ArretTransport"
},
{
"id": 60,
"name": "ROND POINT SAFRICAS",
"created_at": null,
"updated_at": "2020-12-16T11:13:45.000000Z",
"min_date": "2020-05-17",
"type": "Restaurants"
},
{
"id": 25,
"name": "Salle de fete de la Rotonde Binza",
"created_at": null,
"updated_at": "2020-12-16T11:13:36.000000Z",
"min_date": "2020-05-17",
"type": "Restaurants"
},
{
"id": 79,
"name": "Shark Club",
"created_at": null,
"updated_at": "2020-12-16T11:13:49.000000Z",
"min_date": "2020-05-17",
"type": "Commerces"
},
{
"id": 92,
"name": "Shoprite",
"created_at": null,
"updated_at": "2020-12-16T11:13:44.000000Z",
"min_date": "2020-05-17",
"type": "Supermarche"
},
{
"id": 59,
"name": "SONAS",
"created_at": null,
"updated_at": "2020-12-16T11:13:06.000000Z",
"min_date": "2020-05-17",
"type": "Supermarche"
},
{
"id": 26,
"name": "TASOK",
"created_at": null,
"updated_at": "2020-12-16T11:13:54.000000Z",
"min_date": "2020-05-17",
"type": "BureauAdmin"
},
{
"id": 2,
"name": "UPN Djelo",
"created_at": null,
"updated_at": "2020-12-16T11:14:01.000000Z",
"min_date": "2020-05-17",
"type": "ArretTransport"
},
{
"id": 4,
"name": "Wenze Muselu\/Gambela",
"created_at": null,
"updated_at": "2020-12-16T11:13:33.000000Z",
"min_date": "2020-05-17",
"type": "Marché"
}
]
```
### HTTP Request
`GET api/dashboard/flux/hotspots/list`
<!-- END_4f2ecc8520adc7566b65dd9191ec6204 -->
<!-- START_c104c649fbcac1cd1fae93452c683367 -->
## api/dashboard/flux/hotspots/maps
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/flux/hotspots/maps"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (401):
```json
{
"message": "Unauthenticated."
}
```
### HTTP Request
`GET api/dashboard/flux/hotspots/maps`
<!-- END_c104c649fbcac1cd1fae93452c683367 -->
<!-- START_8b52af129fda3aa4bffd3f9bd77fbdb1 -->
## api/dashboard/flux/hotspots/tendance
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/flux/hotspots/tendance"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (401):
```json
{
"message": "Unauthenticated."
}
```
### HTTP Request
`GET api/dashboard/flux/hotspots/tendance`
<!-- END_8b52af129fda3aa4bffd3f9bd77fbdb1 -->
<!-- START_a5b8ffe49997637b4872d999a1308a04 -->
## api/dashboard/flux/hotspots/daily
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/flux/hotspots/daily"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (401):
```json
{
"message": "Unauthenticated."
}
```
### HTTP Request
`GET api/dashboard/flux/hotspots/daily`
<!-- END_a5b8ffe49997637b4872d999a1308a04 -->
<!-- START_385228fd442def1591f20fc6edd4e290 -->
## api/dashboard/flux/hotspots/general
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/flux/hotspots/general"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (401):
```json
{
"message": "Unauthenticated."
}
```
### HTTP Request
`GET api/dashboard/flux/hotspots/general`
<!-- END_385228fd442def1591f20fc6edd4e290 -->
<!-- START_8147aa86fe300c9db9e6fd2ed830af64 -->
## Display a listing of the resource.
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/flux/hotspots/types/list"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (200):
```json
[
{
"id": 103,
"name": "Aéroport Ndjili",
"created_at": null,
"updated_at": "2020-12-23T14:47:16.000000Z",
"min_date": "2020-07-01",
"type": "Aéroport"
},
{
"id": 102,
"name": "Aéroport Ndolo",
"created_at": null,
"updated_at": "2020-12-23T14:47:15.000000Z",
"min_date": "2020-07-01",
"type": "Aéroport"
},
{
"id": 10,
"name": "Arret Bakayaou",
"created_at": null,
"updated_at": "2020-12-16T11:13:00.000000Z",
"min_date": "2020-05-17",
"type": "ArretTransport"
},
{
"id": 7,
"name": "Arret Centre hospitalier de Kintambo",
"created_at": null,
"updated_at": "2020-12-16T11:13:53.000000Z",
"min_date": "2020-05-17",
"type": "ArretTransport"
},
{
"id": 40,
"name": "Arret moulard",
"created_at": null,
"updated_at": "2020-12-16T11:14:21.000000Z",
"min_date": "2020-05-17",
"type": "ArretTransport"
},
{
"id": 80,
"name": "Arret Socimat",
"created_at": null,
"updated_at": "2020-12-16T11:13:46.000000Z",
"min_date": "2020-05-17",
"type": "ArretTransport"
},
{
"id": 8,
"name": "Arret Stade Velodrome",
"created_at": null,
"updated_at": "2020-12-16T11:13:31.000000Z",
"min_date": "2020-05-17",
"type": "Commerces"
},
{
"id": 90,
"name": "Arret Station Centre Superieur",
"created_at": null,
"updated_at": "2020-12-16T11:12:55.000000Z",
"min_date": "2020-05-17",
"type": "Supermarche"
},
{
"id": 17,
"name": "Arret Station Macampagne (ML)",
"created_at": null,
"updated_at": "2020-12-16T11:13:39.000000Z",
"min_date": "2020-05-17",
"type": "ArretTransport"
},
{
"id": 78,
"name": "ASSANEF",
"created_at": null,
"updated_at": "2020-12-16T11:13:14.000000Z",
"min_date": "2020-05-17",
"type": "ArretTransport"
},
{
"id": 75,
"name": "Avenue du Commerce et Kasa vubu",
"created_at": null,
"updated_at": "2020-12-16T11:13:12.000000Z",
"min_date": "2020-05-17",
"type": "ArretTransport"
},
{
"id": 29,
"name": "Baruti Tabernacle",
"created_at": null,
"updated_at": "2020-12-16T11:14:07.000000Z",
"min_date": "2020-05-17",
"type": "Eglises"
},
{
"id": 81,
"name": "BATETELA",
"created_at": null,
"updated_at": "2020-12-16T11:13:50.000000Z",
"min_date": "2020-05-17",
"type": "BureauAdmin"
},
{
"id": 20,
"name": "Benseke Nouvelle Cite",
"created_at": null,
"updated_at": "2020-12-16T11:14:04.000000Z",
"min_date": "2020-05-17",
"type": "Cimetiere"
},
{
"id": 31,
"name": "Binza Arret Maternite",
"created_at": null,
"updated_at": "2020-12-16T11:13:58.000000Z",
"min_date": "2020-05-17",
"type": "ArretTransport"
},
{
"id": 61,
"name": "Carrigres",
"created_at": null,
"updated_at": "2020-12-16T11:13:56.000000Z",
"min_date": "2020-05-17",
"type": "Supermarche"
},
{
"id": 12,
"name": "CE TRINITE",
"created_at": null,
"updated_at": "2020-12-16T11:14:08.000000Z",
"min_date": "2020-05-17",
"type": "Eglises"
},
{
"id": 34,
"name": "Centre d'Evangelisation Peniel CEPE",
"created_at": null,
"updated_at": "2020-12-16T11:13:24.000000Z",
"min_date": "2020-05-17",
"type": "Eglises"
},
{
"id": 76,
"name": "Centre Evangelique Emmanuel Langa-langa",
"created_at": null,
"updated_at": "2020-12-16T11:13:23.000000Z",
"min_date": "2020-05-17",
"type": "Eglises"
},
{
"id": 56,
"name": "Cimetiere Kimbanseke",
"created_at": null,
"updated_at": "2020-12-16T11:14:02.000000Z",
"min_date": "2020-05-17",
"type": "Cimetiere"
},
{
"id": 9,
"name": "Cimetiere Kintambo",
"created_at": null,
"updated_at": "2020-12-16T11:14:21.000000Z",
"min_date": "2020-05-17",
"type": "Cimetiere"
},
{
"id": 95,
"name": "Cimetiere Mingadi",
"created_at": null,
"updated_at": "2020-12-16T11:14:03.000000Z",
"min_date": "2020-05-17",
"type": "Cimetiere"
},
{
"id": 69,
"name": "Cimetiere Ndjili Brasserie",
"created_at": null,
"updated_at": "2020-12-16T11:14:05.000000Z",
"min_date": "2020-05-17",
"type": "Cimetiere"
},
{
"id": 21,
"name": "Cimetiere sans fil",
"created_at": null,
"updated_at": "2020-12-16T11:13:52.000000Z",
"min_date": "2020-05-17",
"type": "Cimetiere"
},
{
"id": 11,
"name": "Croissement Kianza et Universite",
"created_at": null,
"updated_at": "2020-12-16T11:13:30.000000Z",
"min_date": "2020-05-17",
"type": "ArretTransport"
},
{
"id": 3,
"name": "DGC barre",
"created_at": null,
"updated_at": "2020-12-16T11:13:37.000000Z",
"min_date": "2020-05-17",
"type": "ArretTransport"
},
{
"id": 101,
"name": "Dvin",
"created_at": null,
"updated_at": "2020-12-16T11:13:02.000000Z",
"min_date": "2020-05-18",
"type": "Restaurants"
},
{
"id": 42,
"name": "ECC\/CEC\/BUMBU",
"created_at": null,
"updated_at": "2020-12-16T11:13:32.000000Z",
"min_date": "2020-05-17",
"type": "Eglises"
},
{
"id": 37,
"name": "Eglise Catholique Divin Maître",
"created_at": null,
"updated_at": "2020-12-16T11:12:59.000000Z",
"min_date": "2020-05-17",
"type": "Eglises"
},
{
"id": 72,
"name": "Eglise des assemblées de dieu",
"created_at": null,
"updated_at": "2020-12-16T11:13:02.000000Z",
"min_date": "2020-05-17",
"type": "Eglises"
},
{
"id": 55,
"name": "Eglise Francophone Ecole de Tyrannus",
"created_at": null,
"updated_at": "2020-12-16T11:13:18.000000Z",
"min_date": "2020-05-17",
"type": "Eglises"
},
{
"id": 53,
"name": "Eglise Kimbanguiste",
"created_at": null,
"updated_at": "2020-12-16T11:13:29.000000Z",
"min_date": "2020-05-17",
"type": "Eglises"
},
{
"id": 27,
"name": "Eglise locale Cbfc Itaga",
"created_at": null,
"updated_at": "2020-12-16T11:13:20.000000Z",
"min_date": "2020-05-17",
"type": "Eglises"
},
{
"id": 83,
"name": "Eglise Notre Dame de Fatima",
"created_at": null,
"updated_at": "2020-12-16T11:13:11.000000Z",
"min_date": "2020-05-17",
"type": "Eglises"
},
{
"id": 30,
"name": "eglise protestante de lemba",
"created_at": null,
"updated_at": "2020-12-16T11:13:40.000000Z",
"min_date": "2020-05-17",
"type": "Eglises"
},
{
"id": 23,
"name": "Eglise Saint Paul",
"created_at": null,
"updated_at": "2020-12-16T11:13:19.000000Z",
"min_date": "2020-05-17",
"type": "Eglises"
},
{
"id": 35,
"name": "Ejcev Nouvelle Alliance Bima",
"created_at": null,
"updated_at": "2020-12-16T11:13:25.000000Z",
"min_date": "2020-05-17",
"type": "Eglises"
},
{
"id": 84,
"name": "FIKIN",
"created_at": null,
"updated_at": "2020-12-16T11:13:27.000000Z",
"min_date": "2020-05-17",
"type": "Commerces"
},
{
"id": 22,
"name": "Food Market Macampagne",
"created_at": null,
"updated_at": "2020-12-16T11:13:38.000000Z",
"min_date": "2020-05-17",
"type": "Restaurants"
},
{
"id": 66,
"name": "Gabriella",
"created_at": null,
"updated_at": "2020-12-16T11:13:43.000000Z",
"min_date": "2020-05-17",
"type": "Restaurants"
},
{
"id": 97,
"name": "Hall de la Gombe",
"created_at": null,
"updated_at": "2020-12-16T11:13:15.000000Z",
"min_date": "2020-05-17",
"type": "Commerces"
},
{
"id": 71,
"name": "Hopital Biamba Marie Mutombo",
"created_at": null,
"updated_at": "2020-12-16T11:14:13.000000Z",
"min_date": "2020-05-17",
"type": "Hopitaux"
},
{
"id": 24,
"name": "Hopital general de Kintambo",
"created_at": null,
"updated_at": "2020-12-16T11:13:41.000000Z",
"min_date": "2020-05-17",
"type": "Hopitaux"
},
{
"id": 91,
"name": "Hotel du Fleuve",
"created_at": null,
"updated_at": "2020-12-16T11:14:19.000000Z",
"min_date": "2020-05-17",
"type": "Hotels"
},
{
"id": 100,
"name": "HOTEL DU GOUVERNEMENT",
"created_at": null,
"updated_at": "2020-12-16T11:13:46.000000Z",
"min_date": "2020-05-17",
"type": "Supermarche"
},
{
"id": 89,
"name": "Hotel Memling",
"created_at": null,
"updated_at": "2020-12-16T11:12:57.000000Z",
"min_date": "2020-05-17",
"type": "Hotels"
},
{
"id": 73,
"name": "Hotel Sultani",
"created_at": null,
"updated_at": "2020-12-16T11:13:10.000000Z",
"min_date": "2020-05-17",
"type": "Hotels"
},
{
"id": 5,
"name": "Huillerie",
"created_at": null,
"updated_at": "2020-12-16T11:13:04.000000Z",
"min_date": "2020-05-17",
"type": "ArretTransport"
},
{
"id": 82,
"name": "Immeuble CNSS",
"created_at": null,
"updated_at": "2020-12-16T11:13:07.000000Z",
"min_date": "2020-05-17",
"type": "BureauAdmin"
},
{
"id": 93,
"name": "Immeuble Cosmos",
"created_at": null,
"updated_at": "2020-12-16T11:13:37.000000Z",
"min_date": "2020-05-17",
"type": "Commerces"
},
{
"id": 44,
"name": "INA et ORCA",
"created_at": null,
"updated_at": "2020-12-16T11:12:54.000000Z",
"min_date": "2020-05-17",
"type": "Commerces"
},
{
"id": 15,
"name": "INBTP",
"created_at": null,
"updated_at": "2020-12-16T11:14:18.000000Z",
"min_date": "2020-05-17",
"type": "BureauAdmin"
},
{
"id": 1,
"name": "Inconnue",
"created_at": null,
"updated_at": "2020-12-14T10:00:28.000000Z",
"min_date": "2020-05-17",
"type": null
},
{
"id": 14,
"name": "Kinkole",
"created_at": null,
"updated_at": "2020-12-16T11:14:15.000000Z",
"min_date": "2020-05-17",
"type": "Cimetiere"
},
{
"id": 38,
"name": "Kinsuka",
"created_at": null,
"updated_at": "2020-12-16T11:13:57.000000Z",
"min_date": "2020-05-17",
"type": "Cimetiere"
},
{
"id": 86,
"name": "La voix du fleuve",
"created_at": null,
"updated_at": "2020-12-16T11:14:20.000000Z",
"min_date": "2020-05-17",
"type": "Restaurants"
},
{
"id": 18,
"name": "Le cerlce gourmand",
"created_at": null,
"updated_at": "2020-12-16T11:13:10.000000Z",
"min_date": "2020-05-17",
"type": "Restaurants"
},
{
"id": 62,
"name": "le pain de vie",
"created_at": null,
"updated_at": "2020-12-16T11:13:22.000000Z",
"min_date": "2020-05-17",
"type": "Eglises"
},
{
"id": 98,
"name": "Le premier Shopping Mall",
"created_at": null,
"updated_at": "2020-12-16T11:13:09.000000Z",
"min_date": "2020-05-17",
"type": "Commerces"
},
{
"id": 64,
"name": "Lemba Terminus",
"created_at": null,
"updated_at": "2020-12-16T11:14:09.000000Z",
"min_date": "2020-05-17",
"type": "ArretTransport"
},
{
"id": 74,
"name": "Maché De Kadi",
"created_at": null,
"updated_at": "2020-12-16T11:14:17.000000Z",
"min_date": "2020-05-17",
"type": "Marché"
},
{
"id": 41,
"name": "Marché BAYAKA",
"created_at": null,
"updated_at": "2020-12-16T11:12:56.000000Z",
"min_date": "2020-05-17",
"type": "Marché"
},
{
"id": 28,
"name": "Marché central",
"created_at": null,
"updated_at": "2020-12-16T11:13:20.000000Z",
"min_date": "2020-05-17",
"type": "Marché"
},
{
"id": 49,
"name": "Marché de la Liberté",
"created_at": null,
"updated_at": "2020-12-16T11:14:12.000000Z",
"min_date": "2020-05-17",
"type": "ArretTransport"
},
{
"id": 46,
"name": "Marché de Mbanza Lemba",
"created_at": null,
"updated_at": "2020-12-16T11:13:08.000000Z",
"min_date": "2020-05-17",
"type": "Marché"
},
{
"id": 32,
"name": "Marché Delvaux",
"created_at": null,
"updated_at": "2020-12-16T11:13:35.000000Z",
"min_date": "2020-05-17",
"type": "Marché"
},
{
"id": 50,
"name": "Marché Mangobo",
"created_at": null,
"updated_at": "2020-12-16T11:13:55.000000Z",
"min_date": "2020-05-17",
"type": "Marché"
},
{
"id": 68,
"name": "Marché Matete",
"created_at": null,
"updated_at": "2020-12-16T11:14:11.000000Z",
"min_date": "2020-05-17",
"type": "Marché"
},
{
"id": 52,
"name": "Marché Mbika",
"created_at": null,
"updated_at": "2020-12-16T11:14:00.000000Z",
"min_date": "2020-05-17",
"type": "Marché"
},
{
"id": 43,
"name": "Marché selembao",
"created_at": null,
"updated_at": "2020-12-16T11:13:34.000000Z",
"min_date": "2020-05-17",
"type": "Marché"
},
{
"id": 39,
"name": "Matadi Kibala",
"created_at": null,
"updated_at": "2020-12-16T11:13:47.000000Z",
"min_date": "2020-05-17",
"type": "Marché"
},
{
"id": 77,
"name": "Mbudi Nature",
"created_at": null,
"updated_at": "2020-12-16T11:13:56.000000Z",
"min_date": "2020-05-17",
"type": "Commerces"
},
{
"id": 96,
"name": "Mimoza plaza",
"created_at": null,
"updated_at": "2020-12-16T11:13:51.000000Z",
"min_date": "2020-05-17",
"type": "Restaurants"
},
{
"id": 63,
"name": "Ministere combat spirituel",
"created_at": null,
"updated_at": "2020-12-16T11:13:29.000000Z",
"min_date": "2020-05-17",
"type": "Eglises"
},
{
"id": 19,
"name": "Ministere des affaires etrangeres",
"created_at": null,
"updated_at": "2020-12-16T11:13:48.000000Z",
"min_date": "2020-05-17",
"type": "BureauAdmin"
},
{
"id": 58,
"name": "Mosqué Bon Marche",
"created_at": null,
"updated_at": "2020-12-16T11:13:16.000000Z",
"min_date": "2020-05-17",
"type": "Eglises"
},
{
"id": 6,
"name": "Mosqué Centrale Usoke",
"created_at": null,
"updated_at": "2020-12-16T11:13:13.000000Z",
"min_date": "2020-05-17",
"type": "Eglises"
},
{
"id": 88,
"name": "Mosqué Kingabwa",
"created_at": null,
"updated_at": "2020-12-16T11:13:21.000000Z",
"min_date": "2020-05-17",
"type": "Eglises"
},
{
"id": 94,
"name": "Necropole entre ciel et terre",
"created_at": null,
"updated_at": "2020-12-16T11:14:16.000000Z",
"min_date": "2020-05-17",
"type": "Cimetiere"
},
{
"id": 85,
"name": "O'Poeta",
"created_at": null,
"updated_at": "2020-12-16T11:13:42.000000Z",
"min_date": "2020-05-17",
"type": "Restaurants"
},
{
"id": 70,
"name": "ONATRA",
"created_at": null,
"updated_at": "2020-12-16T11:12:52.000000Z",
"min_date": "2020-05-17",
"type": "BureauAdmin"
},
{
"id": 16,
"name": "Parc Mont Ngaliema",
"created_at": null,
"updated_at": "2020-12-16T11:13:01.000000Z",
"min_date": "2020-05-17",
"type": "Commerces"
},
{
"id": 67,
"name": "Paroisse Notre-Dame d'Afrique",
"created_at": null,
"updated_at": "2020-12-16T11:13:28.000000Z",
"min_date": "2020-05-17",
"type": "Eglises"
},
{
"id": 99,
"name": "Paroisse Sacre Coeur",
"created_at": null,
"updated_at": "2020-12-16T11:12:53.000000Z",
"min_date": "2020-05-17",
"type": "Eglises"
},
{
"id": 65,
"name": "Paroisse Saint Eloi",
"created_at": null,
"updated_at": "2020-12-16T11:13:17.000000Z",
"min_date": "2020-05-17",
"type": "Supermarche"
},
{
"id": 36,
"name": "Paroisse saint François-Xavier",
"created_at": null,
"updated_at": "2020-12-16T11:13:26.000000Z",
"min_date": "2020-05-17",
"type": "Eglises"
},
{
"id": 33,
"name": "Peloustore KIVU",
"created_at": null,
"updated_at": "2020-12-16T11:13:59.000000Z",
"min_date": "2020-05-17",
"type": "Supermarche"
},
{
"id": 13,
"name": "Place Commercial de limete(7e rue)",
"created_at": null,
"updated_at": "2020-12-16T11:14:22.000000Z",
"min_date": "2020-05-17",
"type": "Hopitaux"
},
{
"id": 54,
"name": "Place de la gare centrale",
"created_at": null,
"updated_at": "2020-12-16T11:12:58.000000Z",
"min_date": "2020-05-17",
"type": "Hotels"
},
{
"id": 48,
"name": "Place sainte therese",
"created_at": null,
"updated_at": "2020-12-16T11:14:06.000000Z",
"min_date": "2020-05-17",
"type": "ArretTransport"
},
{
"id": 47,
"name": "Pont Matete",
"created_at": null,
"updated_at": "2020-12-16T11:14:10.000000Z",
"min_date": "2020-05-17",
"type": "ArretTransport"
},
{
"id": 87,
"name": "Poste",
"created_at": null,
"updated_at": "2020-12-16T11:13:05.000000Z",
"min_date": "2020-05-17",
"type": "BureauAdmin"
},
{
"id": 57,
"name": "Quartier 1 (croissement Boulevard Lumumba)",
"created_at": null,
"updated_at": "2020-12-16T11:14:14.000000Z",
"min_date": "2020-05-17",
"type": "ArretTransport"
},
{
"id": 51,
"name": "Rond Point Forescom",
"created_at": null,
"updated_at": "2020-12-16T11:13:03.000000Z",
"min_date": "2020-05-17",
"type": "BureauAdmin"
},
{
"id": 45,
"name": "Rond Point Ngaba",
"created_at": null,
"updated_at": "2020-12-16T11:14:05.000000Z",
"min_date": "2020-05-17",
"type": "ArretTransport"
},
{
"id": 60,
"name": "ROND POINT SAFRICAS",
"created_at": null,
"updated_at": "2020-12-16T11:13:45.000000Z",
"min_date": "2020-05-17",
"type": "Restaurants"
},
{
"id": 25,
"name": "Salle de fete de la Rotonde Binza",
"created_at": null,
"updated_at": "2020-12-16T11:13:36.000000Z",
"min_date": "2020-05-17",
"type": "Restaurants"
},
{
"id": 79,
"name": "Shark Club",
"created_at": null,
"updated_at": "2020-12-16T11:13:49.000000Z",
"min_date": "2020-05-17",
"type": "Commerces"
},
{
"id": 92,
"name": "Shoprite",
"created_at": null,
"updated_at": "2020-12-16T11:13:44.000000Z",
"min_date": "2020-05-17",
"type": "Supermarche"
},
{
"id": 59,
"name": "SONAS",
"created_at": null,
"updated_at": "2020-12-16T11:13:06.000000Z",
"min_date": "2020-05-17",
"type": "Supermarche"
},
{
"id": 26,
"name": "TASOK",
"created_at": null,
"updated_at": "2020-12-16T11:13:54.000000Z",
"min_date": "2020-05-17",
"type": "BureauAdmin"
},
{
"id": 2,
"name": "UPN Djelo",
"created_at": null,
"updated_at": "2020-12-16T11:14:01.000000Z",
"min_date": "2020-05-17",
"type": "ArretTransport"
},
{
"id": 4,
"name": "Wenze Muselu\/Gambela",
"created_at": null,
"updated_at": "2020-12-16T11:13:33.000000Z",
"min_date": "2020-05-17",
"type": "Marché"
}
]
```
### HTTP Request
`GET api/dashboard/flux/hotspots/types/list`
<!-- END_8147aa86fe300c9db9e6fd2ed830af64 -->
<!-- START_4427912b3b4a5e8a64d9d2731137f12e -->
## api/dashboard/flux/hotspots/types/maps
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/flux/hotspots/types/maps"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (401):
```json
{
"message": "Unauthenticated."
}
```
### HTTP Request
`GET api/dashboard/flux/hotspots/types/maps`
<!-- END_4427912b3b4a5e8a64d9d2731137f12e -->
<!-- START_b4d41abb78d5917d1bf6f8d91c804c1f -->
## api/dashboard/flux/hotspots/types/tendance
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/flux/hotspots/types/tendance"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (401):
```json
{
"message": "Unauthenticated."
}
```
### HTTP Request
`GET api/dashboard/flux/hotspots/types/tendance`
<!-- END_b4d41abb78d5917d1bf6f8d91c804c1f -->
<!-- START_93e27becee6623b46abfcea59b375e49 -->
## api/dashboard/flux/hotspots/types/daily
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/flux/hotspots/types/daily"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (401):
```json
{
"message": "Unauthenticated."
}
```
### HTTP Request
`GET api/dashboard/flux/hotspots/types/daily`
<!-- END_93e27becee6623b46abfcea59b375e49 -->
<!-- START_b49a0dc609d79960c8765399fee4e1a3 -->
## api/dashboard/flux/hotspots/types/general
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/flux/hotspots/types/general"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (401):
```json
{
"message": "Unauthenticated."
}
```
### HTTP Request
`GET api/dashboard/flux/hotspots/types/general`
<!-- END_b49a0dc609d79960c8765399fee4e1a3 -->
<!-- START_70750654f1ddb3eee06bcbacd62d9301 -->
## api/dashboard/hospital-situations/by-hospital/{hospital_id}
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/hospital-situations/by-hospital/1"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (200):
```json
{
"data": [
{
"id": 337,
"confirmed_cumul": 119,
"sick": 4,
"healed_cumul": 15,
"dead_cumul": 0,
"confirmed": 4,
"healed": 1,
"dead": 0,
"occupied_Beds": 0,
"occupied_respirators": 0,
"masks": 0,
"occupied_foam_beds": 4,
"occupied_resuscitation_beds": 0,
"individual_protection_equipment": 0,
"gel_hydro_alcoolique": 0,
"resuscitation_ventilator": 0,
"oxygenator": 2,
"rapid_screening": 500,
"automate_genexpert": 1,
"x_ray": 0,
"check_point": 1,
"chloroquine": 0,
"hydrochloroquine": 2100,
"azytromicine": 300,
"Vitamince_c": 5100,
"last_update": "2020-08-28 00:00:00",
"updated_manager_name": null,
"created_manager_name": "Dr Kibwana"
},
{
"id": 317,
"confirmed_cumul": 119,
"sick": 5,
"healed_cumul": 15,
"dead_cumul": 0,
"confirmed": 4,
"healed": 0,
"dead": 0,
"occupied_Beds": 0,
"occupied_respirators": 2,
"masks": 100,
"occupied_foam_beds": 5,
"occupied_resuscitation_beds": 0,
"individual_protection_equipment": 120,
"gel_hydro_alcoolique": 0,
"resuscitation_ventilator": 0,
"oxygenator": 0,
"rapid_screening": 123,
"automate_genexpert": 98,
"x_ray": 0,
"check_point": 1,
"chloroquine": 0,
"hydrochloroquine": 3310,
"azytromicine": 520,
"Vitamince_c": 5820,
"last_update": "2020-08-26 00:00:00",
"updated_manager_name": null,
"created_manager_name": "DR KIBWANA"
},
{
"id": 253,
"confirmed_cumul": 119,
"sick": 3,
"healed_cumul": 15,
"dead_cumul": 0,
"confirmed": 3,
"healed": 0,
"dead": 0,
"occupied_Beds": 0,
"occupied_respirators": 0,
"masks": 1100,
"occupied_foam_beds": 3,
"occupied_resuscitation_beds": 0,
"individual_protection_equipment": 50,
"gel_hydro_alcoolique": 0,
"resuscitation_ventilator": 0,
"oxygenator": 2,
"rapid_screening": 1038,
"automate_genexpert": 1,
"x_ray": 0,
"check_point": 1,
"chloroquine": 0,
"hydrochloroquine": 3360,
"azytromicine": 550,
"Vitamince_c": 5830,
"last_update": "2020-08-14 00:00:00",
"updated_manager_name": null,
"created_manager_name": "Freddy kibwana"
},
{
"id": 247,
"confirmed_cumul": 119,
"sick": 2,
"healed_cumul": 15,
"dead_cumul": 0,
"confirmed": 2,
"healed": 1,
"dead": 0,
"occupied_Beds": 0,
"occupied_respirators": 0,
"masks": 7,
"occupied_foam_beds": 2,
"occupied_resuscitation_beds": 0,
"individual_protection_equipment": 23,
"gel_hydro_alcoolique": 0,
"resuscitation_ventilator": 0,
"oxygenator": 2,
"rapid_screening": 1048,
"automate_genexpert": 1,
"x_ray": 0,
"check_point": 1,
"chloroquine": 0,
"hydrochloroquine": 3380,
"azytromicine": 580,
"Vitamince_c": 5870,
"last_update": "2020-08-12 00:00:00",
"updated_manager_name": null,
"created_manager_name": "Freddy kibwana"
},
{
"id": 239,
"confirmed_cumul": 119,
"sick": 3,
"healed_cumul": 15,
"dead_cumul": 0,
"confirmed": 3,
"healed": 0,
"dead": 0,
"occupied_Beds": 0,
"occupied_respirators": 0,
"masks": 8,
"occupied_foam_beds": 3,
"occupied_resuscitation_beds": 0,
"individual_protection_equipment": 62,
"gel_hydro_alcoolique": 0,
"resuscitation_ventilator": 0,
"oxygenator": 2,
"rapid_screening": 1053,
"automate_genexpert": 1,
"x_ray": 0,
"check_point": 1,
"chloroquine": 0,
"hydrochloroquine": 3380,
"azytromicine": 590,
"Vitamince_c": 5880,
"last_update": "2020-08-10 00:00:00",
"updated_manager_name": null,
"created_manager_name": "Freddy kibwana"
},
{
"id": 238,
"confirmed_cumul": 119,
"sick": 2,
"healed_cumul": 15,
"dead_cumul": 0,
"confirmed": 2,
"healed": 0,
"dead": 0,
"occupied_Beds": 0,
"occupied_respirators": 0,
"masks": 30,
"occupied_foam_beds": 2,
"occupied_resuscitation_beds": 0,
"individual_protection_equipment": 80,
"gel_hydro_alcoolique": null,
"resuscitation_ventilator": 0,
"oxygenator": 2,
"rapid_screening": 1059,
"automate_genexpert": 1,
"x_ray": 0,
"check_point": 1,
"chloroquine": 0,
"hydrochloroquine": 3400,
"azytromicine": 600,
"Vitamince_c": 5900,
"last_update": "2020-08-09 00:00:00",
"updated_manager_name": null,
"created_manager_name": "Freddy kibwana"
},
{
"id": 221,
"confirmed_cumul": 119,
"sick": 2,
"healed_cumul": 15,
"dead_cumul": 0,
"confirmed": 2,
"healed": 1,
"dead": 0,
"occupied_Beds": 0,
"occupied_respirators": 0,
"masks": 57,
"occupied_foam_beds": 2,
"occupied_resuscitation_beds": 0,
"individual_protection_equipment": 95,
"gel_hydro_alcoolique": 0,
"resuscitation_ventilator": 0,
"oxygenator": 2,
"rapid_screening": 1060,
"automate_genexpert": 1,
"x_ray": 0,
"check_point": 1,
"chloroquine": 0,
"hydrochloroquine": 3400,
"azytromicine": 600,
"Vitamince_c": 5900,
"last_update": "2020-08-05 00:00:00",
"updated_manager_name": null,
"created_manager_name": "Freddy kibwana"
},
{
"id": 208,
"confirmed_cumul": 119,
"sick": 3,
"healed_cumul": 15,
"dead_cumul": 0,
"confirmed": 3,
"healed": 0,
"dead": 0,
"occupied_Beds": 0,
"occupied_respirators": 0,
"masks": 80,
"occupied_foam_beds": 3,
"occupied_resuscitation_beds": 0,
"individual_protection_equipment": 107,
"gel_hydro_alcoolique": 0,
"resuscitation_ventilator": 0,
"oxygenator": 2,
"rapid_screening": 1066,
"automate_genexpert": 173,
"x_ray": 0,
"check_point": 1,
"chloroquine": 0,
"hydrochloroquine": 3400,
"azytromicine": 600,
"Vitamince_c": 5900,
"last_update": "2020-08-04 00:00:00",
"updated_manager_name": null,
"created_manager_name": "Freddy kibwana"
},
{
"id": 111,
"confirmed_cumul": 119,
"sick": 8,
"healed_cumul": 15,
"dead_cumul": 0,
"confirmed": 8,
"healed": 2,
"dead": 0,
"occupied_Beds": 0,
"occupied_respirators": 0,
"masks": 430,
"occupied_foam_beds": 8,
"occupied_resuscitation_beds": 0,
"individual_protection_equipment": 21,
"gel_hydro_alcoolique": 0,
"resuscitation_ventilator": 0,
"oxygenator": 2,
"rapid_screening": 224,
"automate_genexpert": 1,
"x_ray": 1,
"check_point": 1,
"chloroquine": 0,
"hydrochloroquine": 0,
"azytromicine": 0,
"Vitamince_c": 0,
"last_update": "2020-07-16 00:00:00",
"updated_manager_name": null,
"created_manager_name": "Freddy kibwana"
},
{
"id": 96,
"confirmed_cumul": 119,
"sick": 10,
"healed_cumul": 15,
"dead_cumul": 0,
"confirmed": 10,
"healed": 2,
"dead": 0,
"occupied_Beds": 0,
"occupied_respirators": 0,
"masks": 480,
"occupied_foam_beds": 10,
"occupied_resuscitation_beds": 0,
"individual_protection_equipment": 22,
"gel_hydro_alcoolique": 5,
"resuscitation_ventilator": 0,
"oxygenator": 2,
"rapid_screening": 250,
"automate_genexpert": 1,
"x_ray": 1,
"check_point": 1,
"chloroquine": 0,
"hydrochloroquine": 0,
"azytromicine": 0,
"Vitamince_c": 0,
"last_update": "2020-07-15 00:00:00",
"updated_manager_name": null,
"created_manager_name": "Freddy kibwana"
},
{
"id": 90,
"confirmed_cumul": 119,
"sick": 12,
"healed_cumul": 15,
"dead_cumul": 0,
"confirmed": 34,
"healed": 3,
"dead": 0,
"occupied_Beds": 0,
"occupied_respirators": 0,
"masks": 0,
"occupied_foam_beds": 14,
"occupied_resuscitation_beds": 0,
"individual_protection_equipment": 0,
"gel_hydro_alcoolique": 5,
"resuscitation_ventilator": 0,
"oxygenator": 2,
"rapid_screening": 1002,
"automate_genexpert": 1,
"x_ray": 1,
"check_point": 1,
"chloroquine": 0,
"hydrochloroquine": 0,
"azytromicine": 0,
"Vitamince_c": 0,
"last_update": "2020-07-14 00:00:00",
"updated_manager_name": null,
"created_manager_name": "Freddy kibwana"
},
{
"id": 89,
"confirmed_cumul": 119,
"sick": 12,
"healed_cumul": 15,
"dead_cumul": 0,
"confirmed": 12,
"healed": 0,
"dead": 0,
"occupied_Beds": 0,
"occupied_respirators": 0,
"masks": 0,
"occupied_foam_beds": 14,
"occupied_resuscitation_beds": 0,
"individual_protection_equipment": 0,
"gel_hydro_alcoolique": 5,
"resuscitation_ventilator": 0,
"oxygenator": 2,
"rapid_screening": 1002,
"automate_genexpert": 1,
"x_ray": 1,
"check_point": 1,
"chloroquine": 0,
"hydrochloroquine": 0,
"azytromicine": 0,
"Vitamince_c": 0,
"last_update": "2020-07-14 00:00:00",
"updated_manager_name": null,
"created_manager_name": "Freddy kibwana"
},
{
"id": 81,
"confirmed_cumul": 119,
"sick": 14,
"healed_cumul": 15,
"dead_cumul": 0,
"confirmed": 11,
"healed": 0,
"dead": 0,
"occupied_Beds": 0,
"occupied_respirators": 0,
"masks": 34,
"occupied_foam_beds": 30,
"occupied_resuscitation_beds": 0,
"individual_protection_equipment": 30,
"gel_hydro_alcoolique": 5,
"resuscitation_ventilator": 0,
"oxygenator": 2,
"rapid_screening": 0,
"automate_genexpert": 1,
"x_ray": 0,
"check_point": 1,
"chloroquine": 0,
"hydrochloroquine": 0,
"azytromicine": 0,
"Vitamince_c": 0,
"last_update": "2020-07-13 00:00:00",
"updated_manager_name": null,
"created_manager_name": "Freddy kibwana"
},
{
"id": 70,
"confirmed_cumul": 119,
"sick": 13,
"healed_cumul": 15,
"dead_cumul": 0,
"confirmed": 11,
"healed": 3,
"dead": 0,
"occupied_Beds": 0,
"occupied_respirators": 0,
"masks": 0,
"occupied_foam_beds": 13,
"occupied_resuscitation_beds": 0,
"individual_protection_equipment": 0,
"gel_hydro_alcoolique": 0,
"resuscitation_ventilator": 0,
"oxygenator": 2,
"rapid_screening": 0,
"automate_genexpert": 1,
"x_ray": 1,
"check_point": 1,
"chloroquine": 0,
"hydrochloroquine": 0,
"azytromicine": 0,
"Vitamince_c": 0,
"last_update": "2020-07-11 00:00:00",
"updated_manager_name": null,
"created_manager_name": "Freddy kibwana"
},
{
"id": 95,
"confirmed_cumul": 119,
"sick": 10,
"healed_cumul": 15,
"dead_cumul": 0,
"confirmed": 10,
"healed": 2,
"dead": 0,
"occupied_Beds": 0,
"occupied_respirators": 0,
"masks": 480,
"occupied_foam_beds": 0,
"occupied_resuscitation_beds": 0,
"individual_protection_equipment": 22,
"gel_hydro_alcoolique": 5,
"resuscitation_ventilator": 0,
"oxygenator": 2,
"rapid_screening": 250,
"automate_genexpert": 1,
"x_ray": 1,
"check_point": 1,
"chloroquine": 0,
"hydrochloroquine": 0,
"azytromicine": 0,
"Vitamince_c": 0,
"last_update": "2020-07-08 00:00:00",
"updated_manager_name": null,
"created_manager_name": "Freddy kibwana"
}
],
"links": {
"first": "http:\/\/localhost\/api\/dashboard\/hospital-situations\/by-hospital\/1?page=1",
"last": "http:\/\/localhost\/api\/dashboard\/hospital-situations\/by-hospital\/1?page=1",
"prev": null,
"next": null
},
"meta": {
"current_page": 1,
"from": 1,
"last_page": 1,
"path": "http:\/\/localhost\/api\/dashboard\/hospital-situations\/by-hospital\/1",
"per_page": 15,
"to": 15,
"total": 15
}
}
```
### HTTP Request
`GET api/dashboard/hospital-situations/by-hospital/{hospital_id}`
<!-- END_70750654f1ddb3eee06bcbacd62d9301 -->
<!-- START_f607cdd631b29975e82e7b3fce539609 -->
## api/dashboard/hospital-situations/agent-last-update
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/hospital-situations/agent-last-update"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (200):
```json
[
{
"hospital_id": 6,
"name": "VIJANA",
"last_update": "2020-12-15 00:00:00",
"confirmed": 320
},
{
"hospital_id": 11,
"name": "HASC",
"last_update": "2020-10-12 00:00:00",
"confirmed": 120
},
{
"hospital_id": 10,
"name": "KINKOLE",
"last_update": "2020-10-08 00:00:00",
"confirmed": 52
},
{
"hospital_id": 4,
"name": "SAINT JOSEPH",
"last_update": "2020-10-08 00:00:00",
"confirmed": 759
},
{
"hospital_id": 3,
"name": "MONKOLE",
"last_update": "2020-09-11 00:00:00",
"confirmed": 430
},
{
"hospital_id": 7,
"name": "ZONE DE SANTE STADE DE MARTYRS",
"last_update": "2020-09-02 00:00:00",
"confirmed": 754
},
{
"hospital_id": 12,
"name": "CMK",
"last_update": "2020-09-02 00:00:00",
"confirmed": 1
},
{
"hospital_id": 5,
"name": "CUK",
"last_update": "2020-08-28 00:00:00",
"confirmed": 60
},
{
"hospital_id": 1,
"name": "NGALIEMA",
"last_update": "2020-08-28 00:00:00",
"confirmed": 119
},
{
"hospital_id": 2,
"name": "DIAMANT",
"last_update": "2020-08-28 00:00:00",
"confirmed": 8
}
]
```
### HTTP Request
`GET api/dashboard/hospital-situations/agent-last-update`
<!-- END_f607cdd631b29975e82e7b3fce539609 -->
<!-- START_ce9a88f8d8c1d0ee8eb8fd59910bb7cd -->
## api/dashboard/health-zones
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/health-zones"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (200):
```json
[
{
"zone": "Kintambo",
"province": "Kinshasa"
},
{
"zone": "Bena Tshiadi",
"province": "Kasaï-Central"
},
{
"zone": "Ndjili",
"province": "Kinshasa"
},
{
"zone": "Mutena",
"province": "Kasaï"
},
{
"zone": "Boto",
"province": "Sud-Ubangi"
},
{
"zone": "Masuika",
"province": "Kasaï-Central"
},
{
"zone": "Ndesha",
"province": "Kasaï-Central"
},
{
"zone": "Mulumba",
"province": "Lomami"
},
{
"zone": "Mubumbano",
"province": "Sud-Kivu"
},
{
"zone": "Penjwa",
"province": "Maï-Ndombe"
},
{
"zone": "Nsele",
"province": "Kinshasa"
},
{
"zone": "Binza",
"province": "Nord-Kivu"
},
{
"zone": "Popokabaka",
"province": "Kwango"
},
{
"zone": "Panzi",
"province": "Kwango"
},
{
"zone": "Lemera",
"province": "Sud-Kivu"
},
{
"zone": "Alimbongo",
"province": "Nord-Kivu"
},
{
"zone": "Pangi",
"province": "Maniema"
},
{
"zone": "Mont-Ngafula I",
"province": "Kinshasa"
},
{
"zone": "Vangu",
"province": "Haut-Katanga"
},
{
"zone": "Maluku II",
"province": "Kinshasa"
},
{
"zone": "Monga",
"province": "Bas-Uele"
},
{
"zone": "Bomongo",
"province": "Equateur"
},
{
"zone": "Diulu",
"province": "Kasaï-Oriental"
},
{
"zone": "Laybo",
"province": "Ituri"
},
{
"zone": "Nia-Nia",
"province": "Ituri"
},
{
"zone": "Manono",
"province": "Tanganyika"
},
{
"zone": "Makiso-Kisangani",
"province": "Tshopo"
},
{
"zone": "Demba",
"province": "Kasaï-Central"
},
{
"zone": "Luozi",
"province": "Kongo-Central"
},
{
"zone": "Kalole",
"province": "Sud-Kivu"
},
{
"zone": "Kabinda",
"province": "Lomami"
},
{
"zone": "Biringi",
"province": "Ituri"
},
{
"zone": "N'djili",
"province": "Kinshasa"
},
{
"zone": "Ruzizi",
"province": "Sud-Kivu"
},
{
"zone": "Kongolo",
"province": "Tanganyika"
},
{
"zone": "Bokungu",
"province": "Tshuapa"
},
{
"zone": "Saramabila",
"province": "Maniema"
},
{
"zone": "Kajiji",
"province": "Kwango"
},
{
"zone": "Binza Ozone",
"province": "Kinshasa"
},
{
"zone": "Lisala",
"province": "Mongala"
},
{
"zone": "Mitwaba",
"province": "Haut-Katanga"
},
{
"zone": "Mwenga",
"province": "Sud-Kivu"
},
{
"zone": "Bolenge",
"province": "Equateur"
},
{
"zone": "Lubero",
"province": "Nord-Kivu"
},
{
"zone": "Bikoro",
"province": "Equateur"
},
{
"zone": "Yasa-Bonga",
"province": "Kwilu"
},
{
"zone": "Kansele",
"province": "Kasaï-Oriental"
},
{
"zone": "Tshilenge",
"province": "Kasaï-Oriental"
},
{
"zone": "Wangata",
"province": "Equateur"
},
{
"zone": "Isangi",
"province": "Tshopo"
},
{
"zone": "Drodro",
"province": "Ituri"
},
{
"zone": "Walikale",
"province": "Nord-Kivu"
},
{
"zone": "Malemba Nkulu",
"province": "Haut-Lomami"
},
{
"zone": "Lubumbashi",
"province": "Haut-Katanga"
},
{
"zone": "Bongandanga",
"province": "Mongala"
},
{
"zone": "Wapinda",
"province": "Nord-Ubangi"
},
{
"zone": "Bwamanda",
"province": "Sud-Ubangi"
},
{
"zone": "Bonzola",
"province": "Kasaï-Oriental"
},
{
"zone": "Rwashi",
"province": "Haut-Katanga"
},
{
"zone": "Mbaya",
"province": "Sud-Ubangi"
},
{
"zone": "Nyemba",
"province": "Tanganyika"
},
{
"zone": "Niangara",
"province": "Haut-Uele"
},
{
"zone": "Tshishimbi",
"province": "Kasaï-Oriental"
},
{
"zone": "Katuba",
"province": "Haut-Katanga"
},
{
"zone": "Ango",
"province": "Bas-Uele"
},
{
"zone": "Luputa",
"province": "Lomami"
},
{
"zone": "Kafakumba",
"province": "Lualaba"
},
{
"zone": "Seke-Banza",
"province": "Kongo-Central"
},
{
"zone": "Dekese",
"province": "Kasaï"
},
{
"zone": "Lukelenge",
"province": "Kasaï-Oriental"
},
{
"zone": "Mukedi",
"province": "Kwilu"
},
{
"zone": "Kanzenze",
"province": "Lualaba"
},
{
"zone": "Mangembo",
"province": "Kongo-Central"
},
{
"zone": "Gombari",
"province": "Haut-Uele"
},
{
"zone": "Kabondo Dianda",
"province": "Haut-Lomami"
},
{
"zone": "Binga",
"province": "Mongala"
},
{
"zone": "Rimba",
"province": "Ituri"
},
{
"zone": "Kilwa",
"province": "Haut-Katanga"
},
{
"zone": "Kikwit-Sud",
"province": "Kwilu"
},
{
"zone": "Kamiji",
"province": "Lomami"
},
{
"zone": "Inga",
"province": "Kongo-Central"
},
{
"zone": "Boende",
"province": "Tshuapa"
},
{
"zone": "Moanza",
"province": "Kwilu"
},
{
"zone": "Bibanga",
"province": "Kasaï-Oriental"
},
{
"zone": "Birambizo",
"province": "Nord-Kivu"
},
{
"zone": "Mangobo",
"province": "Tshopo"
},
{
"zone": "Bilomba",
"province": "Kasaï-Central"
},
{
"zone": "Bili",
"province": "Bas-Uele"
},
{
"zone": "Tchomia",
"province": "Ituri"
},
{
"zone": "Bonga Yasa",
"province": "Kwilu"
},
{
"zone": "Kungu",
"province": "Sud-Ubangi"
},
{
"zone": "Befale",
"province": "Tshuapa"
},
{
"zone": "Kasansa",
"province": "Kasaï-Oriental"
},
{
"zone": "Wamba",
"province": "Haut-Uele"
},
{
"zone": "Kakenge",
"province": "Kasaï"
},
{
"zone": "Kasa-vubu",
"province": "Kinshasa"
},
{
"zone": "Kisanji",
"province": "Kwango"
},
{
"zone": "Rwampara",
"province": "Ituri"
},
{
"zone": "Inongo",
"province": "Maï-Ndombe"
},
{
"zone": "Lubondaie",
"province": "Kasaï-Central"
},
{
"zone": "Kinkonzi",
"province": "Kongo-Central"
},
{
"zone": "Vanga Kete",
"province": "Sankuru"
},
{
"zone": "Mvuzi",
"province": "Haut-Katanga"
},
{
"zone": "Ikela",
"province": "Tshuapa"
},
{
"zone": "Lubudi",
"province": "Lualaba"
},
{
"zone": "Bumba",
"province": "Mongala"
},
{
"zone": "Kuimba",
"province": "Kongo-Central"
},
{
"zone": "Mimia",
"province": "Maï-Ndombe"
},
{
"zone": "Kitenge",
"province": "Haut-Lomami"
},
{
"zone": "Gbadolite",
"province": "Nord-Ubangi"
},
{
"zone": "Pinga",
"province": "Nord-Kivu"
},
{
"zone": "Djolu",
"province": "Tshuapa"
},
{
"zone": "Bagata",
"province": "Kwilu"
},
{
"zone": "Barumbu",
"province": "Kinshasa"
},
{
"zone": "Banjow Moke",
"province": "Maï-Ndombe"
},
{
"zone": "Katoka",
"province": "Kasaï-Central"
},
{
"zone": "Mutuanga",
"province": "Nord-Kivu"
},
{
"zone": "Matadi",
"province": "Kongo-Central"
},
{
"zone": "Lwamba",
"province": "Haut-Lomami"
},
{
"zone": "Ntandembelo",
"province": "Maï-Ndombe"
},
{
"zone": "Banga Lubaka",
"province": "Kasaï"
},
{
"zone": "Kabondo",
"province": "Tshopo"
},
{
"zone": "Luiza",
"province": "Kasaï-Central"
},
{
"zone": "Mulongo",
"province": "Haut-Lomami"
},
{
"zone": "Kalonda Ouest",
"province": "Kasaï"
},
{
"zone": "Nioki",
"province": "Maï-Ndombe"
},
{
"zone": "Lubutu",
"province": "Maniema"
},
{
"zone": "Pay Kongila",
"province": "Kwilu"
},
{
"zone": "Bengamisa",
"province": "Tshopo"
},
{
"zone": "Boma-Mangbetu",
"province": "Haut-Uele"
},
{
"zone": "Bambu",
"province": "Ituri"
},
{
"zone": "Kaziba",
"province": "Sud-Kivu"
},
{
"zone": "Mobayi Mbongo",
"province": "Nord-Ubangi"
},
{
"zone": "Kwilu Ngongo",
"province": "Kongo-Central"
},
{
"zone": "Mosango",
"province": "Kwilu"
},
{
"zone": "Rwanguba",
"province": "Nord-Kivu"
},
{
"zone": "Mabalako",
"province": "Nord-Kivu"
},
{
"zone": "Wembo Nyama",
"province": "Sankuru"
},
{
"zone": "Kanzala",
"province": "Kasaï"
},
{
"zone": "Bafwagbogbo",
"province": "Tshopo"
},
{
"zone": "Kashobwe",
"province": "Haut-Katanga"
},
{
"zone": "Mushenge",
"province": "Kasaï"
},
{
"zone": "Basoko",
"province": "Tshopo"
},
{
"zone": "Kangu",
"province": "Kongo-Central"
},
{
"zone": "Mangala",
"province": "Ituri"
},
{
"zone": "N'sele",
"province": "Kinshasa"
},
{
"zone": "Libenge",
"province": "Sud-Ubangi"
},
{
"zone": "Opienge",
"province": "Tshopo"
},
{
"zone": "Yalimbongo",
"province": "Tshopo"
},
{
"zone": "Kalima",
"province": "Maniema"
},
{
"zone": "Kapolowe",
"province": "Haut-Katanga"
},
{
"zone": "Pweto",
"province": "Haut-Katanga"
},
{
"zone": "Lomela",
"province": "Sankuru"
},
{
"zone": "Kasindi",
"province": "Nord-Kivu"
},
{
"zone": "Lolo",
"province": "Mongala"
},
{
"zone": "Lusambo",
"province": "Sankuru"
},
{
"zone": "Kitangwa",
"province": "Kasaï"
},
{
"zone": "Boko-Kivulu",
"province": "Kongo-Central"
},
{
"zone": "Omendjadi",
"province": "Sankuru"
},
{
"zone": "Bolobo",
"province": "Maï-Ndombe"
},
{
"zone": "Gungu",
"province": "Kwilu"
},
{
"zone": "Wema",
"province": "Tshuapa"
},
{
"zone": "Yaleko",
"province": "Tshopo"
},
{
"zone": "Bandalungwa",
"province": "Kinshasa"
},
{
"zone": "Lita",
"province": "Ituri"
},
{
"zone": "Kibirizi",
"province": "Nord-Kivu"
},
{
"zone": "Kabalo",
"province": "Tanganyika"
},
{
"zone": "Moba",
"province": "Tanganyika"
},
{
"zone": "Ludimbi Lukula",
"province": "Lomami"
},
{
"zone": "Budjala",
"province": "Sud-Ubangi"
},
{
"zone": "Kingandu",
"province": "Kwilu"
},
{
"zone": "Kindu",
"province": "Maniema"
},
{
"zone": "Tshopo",
"province": "Tshopo"
},
{
"zone": "Kyondo",
"province": "Nord-Kivu"
},
{
"zone": "Basali",
"province": "Tshopo"
},
{
"zone": "Butembo",
"province": "Nord-Kivu"
},
{
"zone": "Masereka",
"province": "Nord-Kivu"
},
{
"zone": "Kabare",
"province": "Sud-Kivu"
},
{
"zone": "Bunia",
"province": "Ituri"
},
{
"zone": "Luambo",
"province": "Kasaï-Central"
},
{
"zone": "Bobozo",
"province": "Kasaï-Central"
},
{
"zone": "Sia",
"province": "Kwilu"
},
{
"zone": "Zongo",
"province": "Sud-Ubangi"
},
{
"zone": "Ubundu",
"province": "Tshopo"
},
{
"zone": "Lukafu",
"province": "Haut-Katanga"
},
{
"zone": "Bokonzi",
"province": "Sud-Ubangi"
},
{
"zone": "Mbandaka",
"province": "Equateur"
},
{
"zone": "Koshibanda",
"province": "Kwilu"
},
{
"zone": "Tunda",
"province": "Maniema"
},
{
"zone": "Wanierukula",
"province": "Tshopo"
},
{
"zone": "Tshitenge",
"province": "Kasaï-Oriental"
},
{
"zone": "Kalehe",
"province": "Sud-Kivu"
},
{
"zone": "Ferekeni",
"province": "Maniema"
},
{
"zone": "Baka",
"province": "Haut-Lomami"
},
{
"zone": "Kambove",
"province": "Haut-Katanga"
},
{
"zone": "Kisenso",
"province": "Kinshasa"
},
{
"zone": "Wikong",
"province": "Lomami"
},
{
"zone": "Gemena",
"province": "Sud-Ubangi"
},
{
"zone": "Aru",
"province": "Ituri"
},
{
"zone": "Doruma",
"province": "Haut-Uele"
},
{
"zone": "Hauts-Plateaux",
"province": "Sud-Kivu"
},
{
"zone": "Kalamba",
"province": "Lualaba"
},
{
"zone": "Lowa",
"province": "Tshopo"
},
{
"zone": "Kisanga",
"province": "Haut-Katanga"
},
{
"zone": "Katoyi",
"province": "Nord-Kivu"
},
{
"zone": "Ototo",
"province": "Sankuru"
},
{
"zone": "Kingasani",
"province": "Kinshasa"
},
{
"zone": "Boga",
"province": "Ituri"
},
{
"zone": "Bunkonde",
"province": "Kasaï-Central"
},
{
"zone": "Lingomo",
"province": "Tshuapa"
},
{
"zone": "Ngandajika",
"province": "Lomami"
},
{
"zone": "Basankusu",
"province": "Equateur"
},
{
"zone": "Musienene",
"province": "Nord-Kivu"
},
{
"zone": "Kasaji",
"province": "Lualaba"
},
{
"zone": "Lodja",
"province": "Sankuru"
},
{
"zone": "Kamalondo",
"province": "Haut-Katanga"
},
{
"zone": "Nyanga",
"province": "Kasaï"
},
{
"zone": "Loko",
"province": "Nord-Ubangi"
},
{
"zone": "Butumba",
"province": "Haut-Lomami"
},
{
"zone": "Boko Kivula",
"province": "Kongo-Central"
},
{
"zone": "Kenge",
"province": "Kwango"
},
{
"zone": "Masina II",
"province": "Kinshasa"
},
{
"zone": "Bena Dibele",
"province": "Sankuru"
},
{
"zone": "Banalia",
"province": "Tshopo"
},
{
"zone": "Dikungu",
"province": "Sankuru"
},
{
"zone": "Iboko",
"province": "Equateur"
},
{
"zone": "Minembwe",
"province": "Sud-Kivu"
},
{
"zone": "Lubunga",
"province": "Tshopo"
},
{
"zone": "Kaniama",
"province": "Haut-Lomami"
},
{
"zone": "Kitutu",
"province": "Sud-Kivu"
},
{
"zone": "Kirotshe",
"province": "Nord-Kivu"
},
{
"zone": "Kipushi",
"province": "Haut-Katanga"
},
{
"zone": "Mufunga Sampwe",
"province": "Haut-Katanga"
},
{
"zone": "Ngidinga",
"province": "Kongo-Central"
},
{
"zone": "Kowe",
"province": "Haut-Katanga"
},
{
"zone": "Kimpese",
"province": "Kongo-Central"
},
{
"zone": "Samba",
"province": "Maniema"
},
{
"zone": "Kikwit-Nord",
"province": "Kwilu"
},
{
"zone": "Miti Murhesa",
"province": "Sud-Kivu"
},
{
"zone": "Bagira",
"province": "Sud-Kivu"
},
{
"zone": "Yahuma",
"province": "Tshopo"
},
{
"zone": "Irebu",
"province": "Equateur"
},
{
"zone": "Yakusu",
"province": "Tshopo"
},
{
"zone": "Mokala",
"province": "Kwilu"
},
{
"zone": "Gombe",
"province": "Kinshasa"
},
{
"zone": "Kwilu-Ngongo",
"province": "Kongo-Central"
},
{
"zone": "Tshofa",
"province": "Lomami"
},
{
"zone": "Dibaya",
"province": "Kasaï-Central"
},
{
"zone": "Mulungu",
"province": "Sud-Kivu"
},
{
"zone": "Mahagi",
"province": "Ituri"
},
{
"zone": "Kimvula",
"province": "Kongo-Central"
},
{
"zone": "Fungurume",
"province": "Lualaba"
},
{
"zone": "Bominenge",
"province": "Sud-Ubangi"
},
{
"zone": "Tshudi Loto",
"province": "Sankuru"
},
{
"zone": "Lubilanji",
"province": "Kasaï-Oriental"
},
{
"zone": "Kikula",
"province": "Haut-Katanga"
},
{
"zone": "Nzanza",
"province": "Kongo-Central"
},
{
"zone": "Songa",
"province": "Haut-Lomami"
},
{
"zone": "Mikope",
"province": "Kasaï"
},
{
"zone": "Kampemba",
"province": "Haut-Katanga"
},
{
"zone": "Nundu",
"province": "Sud-Kivu"
},
{
"zone": "Yamaluka",
"province": "Mongala"
},
{
"zone": "Alunguli",
"province": "Maniema"
},
{
"zone": "Ganga",
"province": "Bas-Uele"
},
{
"zone": "Oshwe",
"province": "Maï-Ndombe"
},
{
"zone": "Matete",
"province": "Kinshasa"
},
{
"zone": "Kalambayi Kabanga",
"province": "Lomami"
},
{
"zone": "Yamongili",
"province": "Mongala"
},
{
"zone": "Mweka",
"province": "Kasaï"
},
{
"zone": "Kunda",
"province": "Maniema"
},
{
"zone": "Lulingu",
"province": "Sud-Kivu"
},
{
"zone": "Itebero",
"province": "Nord-Kivu"
},
{
"zone": "Mambasa",
"province": "Ituri"
},
{
"zone": "Idjwi",
"province": "Sud-Kivu"
},
{
"zone": "Viadana",
"province": "Bas-Uele"
},
{
"zone": "Lingwala",
"province": "Kinshasa"
},
{
"zone": "Mikalayi",
"province": "Kasaï-Central"
},
{
"zone": "Kikongo",
"province": "Kwilu"
},
{
"zone": "Kalomba",
"province": "Kasaï-Central"
},
{
"zone": "Sandoa",
"province": "Lualaba"
},
{
"zone": "Dilolo",
"province": "Lualaba"
},
{
"zone": "Logo",
"province": "Ituri"
},
{
"zone": "Nsona-Mpangu",
"province": "Kongo-Central"
},
{
"zone": "Boko",
"province": "Kwango"
},
{
"zone": "Mwela Lembwa",
"province": "Kwango"
},
{
"zone": "Manika",
"province": "Haut-Katanga"
},
{
"zone": "Kimbanseke",
"province": "Kinshasa"
},
{
"zone": "Bokoro",
"province": "Maï-Ndombe"
},
{
"zone": "Kinda",
"province": "Haut-Lomami"
},
{
"zone": "Kole",
"province": "Sankuru"
},
{
"zone": "Tshikula",
"province": "Kasaï-Central"
},
{
"zone": "Mutshatsha",
"province": "Lualaba"
},
{
"zone": "Abuzi",
"province": "Nord-Ubangi"
},
{
"zone": "Komanda",
"province": "Ituri"
},
{
"zone": "Kabeya Kamuanga",
"province": "Kasaï-Oriental"
},
{
"zone": "Masisi",
"province": "Nord-Kivu"
},
{
"zone": "Opala",
"province": "Tshopo"
},
{
"zone": "Buta",
"province": "Bas-Uele"
},
{
"zone": "Mongbalu",
"province": "Ituri"
},
{
"zone": "Himbi",
"province": "Nord-Kivu"
},
{
"zone": "Obokote",
"province": "Maniema"
},
{
"zone": "Vuhovi",
"province": "Nord-Kivu"
},
{
"zone": "Uvira",
"province": "Sud-Kivu"
},
{
"zone": "Minga",
"province": "Sankuru"
},
{
"zone": "Tshibala",
"province": "Kasaï-Central"
},
{
"zone": "Oicha",
"province": "Nord-Kivu"
},
{
"zone": "Kamana",
"province": "Lomami"
},
{
"zone": "Shabunda",
"province": "Sud-Kivu"
},
{
"zone": "Katende",
"province": "Kasaï-Central"
},
{
"zone": "Bulape",
"province": "Kasaï"
},
{
"zone": "Yalifafo",
"province": "Tshuapa"
},
{
"zone": "Makoro",
"province": "Haut-Uele"
},
{
"zone": "Bipemba",
"province": "Kasaï-Oriental"
},
{
"zone": "Sonabata",
"province": "Kongo-Central"
},
{
"zone": "Kanda Kanda",
"province": "Lomami"
},
{
"zone": "Titule",
"province": "Bas-Uele"
},
{
"zone": "Ipamu",
"province": "Kwilu"
},
{
"zone": "Tshamilemba",
"province": "Haut-Katanga"
},
{
"zone": "Tshikaji",
"province": "Kasaï-Central"
},
{
"zone": "Lukala",
"province": "Kongo-Central"
},
{
"zone": "Kiyambi",
"province": "Tanganyika"
},
{
"zone": "Nyarambe",
"province": "Ituri"
},
{
"zone": "Binza Méteo",
"province": "Kinshasa"
},
{
"zone": "Mumbunda",
"province": "Haut-Katanga"
},
{
"zone": "Fizi",
"province": "Sud-Kivu"
},
{
"zone": "Mbanza-Ngungu",
"province": "Kongo-Central"
},
{
"zone": "Aungba",
"province": "Ituri"
},
{
"zone": "Kamwesha",
"province": "Kasaï"
},
{
"zone": "Gethy",
"province": "Ituri"
},
{
"zone": "Nyangezi",
"province": "Sud-Kivu"
},
{
"zone": "Kalamu I",
"province": "Kinshasa"
},
{
"zone": "Kokolo",
"province": "Kinshasa"
},
{
"zone": "Nyiragongo",
"province": "Nord-Kivu"
},
{
"zone": "Muya",
"province": "Kasaï-Oriental"
},
{
"zone": "Kabambare",
"province": "Maniema"
},
{
"zone": "Jiba",
"province": "Ituri"
},
{
"zone": "Nselo",
"province": "Kongo-Central"
},
{
"zone": "Kabongo",
"province": "Haut-Lomami"
},
{
"zone": "Fataki",
"province": "Ituri"
},
{
"zone": "Tshikapa",
"province": "Kasaï"
},
{
"zone": "Kasenga",
"province": "Haut-Katanga"
},
{
"zone": "Gombe-Matadi",
"province": "Kongo-Central"
},
{
"zone": "Idiofa",
"province": "Kwilu"
},
{
"zone": "Ndjoko-Mpunda",
"province": "Kasaï"
},
{
"zone": "Kitona",
"province": "Kongo-Central"
},
{
"zone": "Kalonda Est",
"province": "Lomami"
},
{
"zone": "Faradje",
"province": "Haut-Uele"
},
{
"zone": "Kansimba",
"province": "Tanganyika"
},
{
"zone": "Muanda",
"province": "Kongo-Central"
},
{
"zone": "Dibindi",
"province": "Kasaï-Oriental"
},
{
"zone": "Aketi",
"province": "Bas-Uele"
},
{
"zone": "Kiri",
"province": "Maï-Ndombe"
},
{
"zone": "Yabaondo",
"province": "Tshopo"
},
{
"zone": "Djalo Djeka",
"province": "Sankuru"
},
{
"zone": "Limete",
"province": "Kinshasa"
},
{
"zone": "Lusanga",
"province": "Kwilu"
},
{
"zone": "Aba",
"province": "Haut-Uele"
},
{
"zone": "Mwana",
"province": "Sud-Kivu"
},
{
"zone": "Mukumbi",
"province": "Kasaï-Oriental"
},
{
"zone": "Punia",
"province": "Maniema"
},
{
"zone": "Selembao",
"province": "Kinshasa"
},
{
"zone": "Kapanga",
"province": "Lualaba"
},
{
"zone": "Makala",
"province": "Kinshasa"
},
{
"zone": "Kapemba",
"province": "Haut-Katanga"
},
{
"zone": "Adja",
"province": "Ituri"
},
{
"zone": "Mweso",
"province": "Nord-Kivu"
},
{
"zone": "Kampene",
"province": "Maniema"
},
{
"zone": "Bunkeya",
"province": "Lualaba"
},
{
"zone": "Djombo",
"province": "Equateur"
},
{
"zone": "Kamina",
"province": "Haut-Lomami"
},
{
"zone": "Lolwa",
"province": "Ituri"
},
{
"zone": "Mont-Ngafula II",
"province": "Kinshasa"
},
{
"zone": "Bukama",
"province": "Haut-Lomami"
},
{
"zone": "Lukolela",
"province": "Equateur"
},
{
"zone": "Sakania",
"province": "Haut-Katanga"
},
{
"zone": "Masi-Manimba",
"province": "Kwilu"
},
{
"zone": "Masina I",
"province": "Kinshasa"
},
{
"zone": "Kinshasa",
"province": "Kinshasa"
},
{
"zone": "Katako Kombe",
"province": "Sankuru"
},
{
"zone": "Kamituga",
"province": "Sud-Kivu"
},
{
"zone": "Tembo",
"province": "Kwango"
},
{
"zone": "Vanga",
"province": "Kwilu"
},
{
"zone": "Biyela",
"province": "Kinshasa"
},
{
"zone": "Ntondo",
"province": "Equateur"
},
{
"zone": "Kilo",
"province": "Ituri"
},
{
"zone": "Angumu",
"province": "Ituri"
},
{
"zone": "Yambuku",
"province": "Mongala"
},
{
"zone": "Likati",
"province": "Bas-Uele"
},
{
"zone": "Tshela",
"province": "Kongo-Central"
},
{
"zone": "Bolomba",
"province": "Equateur"
},
{
"zone": "Businga",
"province": "Nord-Ubangi"
},
{
"zone": "Kinkondja",
"province": "Haut-Lomami"
},
{
"zone": "Bulungu",
"province": "Kwilu"
},
{
"zone": "Nyatende",
"province": "Sud-Kivu"
},
{
"zone": "Kenya",
"province": "Haut-Katanga"
},
{
"zone": "Kibombo",
"province": "Maniema"
},
{
"zone": "Mbanza Ngungu",
"province": "Kongo-Central"
},
{
"zone": "Lilanga Bobangi",
"province": "Equateur"
},
{
"zone": "Boso Manzi",
"province": "Mongala"
},
{
"zone": "Isiro",
"province": "Haut-Uele"
},
{
"zone": "Malemba",
"province": "Haut-Lomami"
},
{
"zone": "Bunyakiri",
"province": "Sud-Kivu"
},
{
"zone": "Kibunzi",
"province": "Kongo-Central"
},
{
"zone": "Bosondjo",
"province": "Mongala"
},
{
"zone": "Mandima",
"province": "Ituri"
},
{
"zone": "Kilela Balanda",
"province": "Haut-Katanga"
},
{
"zone": "Yumbi",
"province": "Maï-Ndombe"
},
{
"zone": "Mutwanga",
"province": "Nord-Kivu"
},
{
"zone": "Bosanga",
"province": "Tshuapa"
},
{
"zone": "Goma",
"province": "Nord-Kivu"
},
{
"zone": "Ilebo",
"province": "Kasaï"
},
{
"zone": "Makota",
"province": "Lomami"
},
{
"zone": "Dungu",
"province": "Haut-Uele"
},
{
"zone": "Damas",
"province": "Ituri"
},
{
"zone": "Wamba Lwadi",
"province": "Kwango"
},
{
"zone": "Pimu",
"province": "Mongala"
},
{
"zone": "Djuma",
"province": "Kwilu"
},
{
"zone": "Boma Bungu",
"province": "Kongo-Central"
},
{
"zone": "Bogosenubia",
"province": "Sud-Ubangi"
},
{
"zone": "Minova",
"province": "Sud-Kivu"
},
{
"zone": "Kaniola",
"province": "Sud-Kivu"
},
{
"zone": "Bosobolo",
"province": "Nord-Ubangi"
},
{
"zone": "Kasongo",
"province": "Maniema"
},
{
"zone": "Nizi",
"province": "Ituri"
},
{
"zone": "Kimputu",
"province": "Kwilu"
},
{
"zone": "Mompono",
"province": "Tshuapa"
},
{
"zone": "Kibua",
"province": "Nord-Kivu"
},
{
"zone": "Ariwara",
"province": "Ituri"
},
{
"zone": "Sona-Bata",
"province": "Kongo-Central"
},
{
"zone": "Sekebanza",
"province": "Kongo-Central"
},
{
"zone": "Bandundu",
"province": "Kwilu"
},
{
"zone": "Karisimbi",
"province": "Nord-Kivu"
},
{
"zone": "Adi",
"province": "Ituri"
},
{
"zone": "Kafubu",
"province": "Haut-Katanga"
},
{
"zone": "Kalonge",
"province": "Sud-Kivu"
},
{
"zone": "Kambala",
"province": "Ituri"
},
{
"zone": "Bafwasende",
"province": "Tshopo"
},
{
"zone": "Nyakunde",
"province": "Ituri"
},
{
"zone": "Masa",
"province": "Kongo-Central"
},
{
"zone": "Feshi",
"province": "Kwango"
},
{
"zone": "Muetshi",
"province": "Kasaï-Central"
},
{
"zone": "Kalenda",
"province": "Lomami"
},
{
"zone": "Mpokolo",
"province": "Kasaï-Oriental"
},
{
"zone": "Kalamu II",
"province": "Kinshasa"
},
{
"zone": "Lusangi",
"province": "Maniema"
},
{
"zone": "Ndage",
"province": "Sud-Ubangi"
},
{
"zone": "Miabi",
"province": "Kasaï-Oriental"
},
{
"zone": "Kalemie",
"province": "Tanganyika"
},
{
"zone": "Mungindu",
"province": "Kwilu"
},
{
"zone": "Mutoto",
"province": "Kasaï-Central"
},
{
"zone": "Kamango",
"province": "Nord-Kivu"
},
{
"zone": "Biena",
"province": "Nord-Kivu"
},
{
"zone": "Mondombe",
"province": "Tshuapa"
},
{
"zone": "Miti-Murhesa",
"province": "Sud-Kivu"
},
{
"zone": "Katwa",
"province": "Nord-Kivu"
},
{
"zone": "Watsa",
"province": "Haut-Uele"
},
{
"zone": "Boso Mondanda",
"province": "Mongala"
},
{
"zone": "Ingende",
"province": "Equateur"
},
{
"zone": "Kamonia",
"province": "Kasaï"
},
{
"zone": "Pawa",
"province": "Haut-Uele"
},
{
"zone": "Rungu",
"province": "Haut-Uele"
},
{
"zone": "Lubao",
"province": "Lomami"
},
{
"zone": "Bangabola",
"province": "Sud-Ubangi"
},
{
"zone": "Linga",
"province": "Ituri"
},
{
"zone": "Yakoma",
"province": "Nord-Ubangi"
},
{
"zone": "Bena Leka",
"province": "Kasaï-Central"
},
{
"zone": "Bulu",
"province": "Sud-Ubangi"
},
{
"zone": "Panda",
"province": "Haut-Katanga"
},
{
"zone": "Ngaba",
"province": "Kinshasa"
},
{
"zone": "Kayamba",
"province": "Haut-Lomami"
},
{
"zone": "Lotumbe",
"province": "Equateur"
},
{
"zone": "Nzaba",
"province": "Kasaï-Oriental"
},
{
"zone": "Kisantu",
"province": "Kongo-Central"
},
{
"zone": "Nyunzu",
"province": "Tanganyika"
},
{
"zone": "Rethy",
"province": "Ituri"
},
{
"zone": "Boma",
"province": "Kongo-Central"
},
{
"zone": "Bumbu",
"province": "Kinshasa"
},
{
"zone": "Kasumbalesa",
"province": "Haut-Katanga"
},
{
"zone": "Dilala",
"province": "Lualaba"
},
{
"zone": "Pania Mutombo",
"province": "Sankuru"
},
{
"zone": "Mukanga",
"province": "Haut-Lomami"
},
{
"zone": "Walungu",
"province": "Sud-Kivu"
},
{
"zone": "Kingabwa",
"province": "Kinshasa"
},
{
"zone": "Mwene Ditu",
"province": "Lomami"
},
{
"zone": "Ibanda",
"province": "Sud-Kivu"
},
{
"zone": "Kananga",
"province": "Kasaï-Central"
},
{
"zone": "Ngiri-Ngiri",
"province": "Kinshasa"
},
{
"zone": "Makanza",
"province": "Equateur"
},
{
"zone": "Kayna",
"province": "Nord-Kivu"
},
{
"zone": "Mbulula",
"province": "Tanganyika"
},
{
"zone": "Lualaba",
"province": "Lualaba"
},
{
"zone": "Rutshuru",
"province": "Nord-Kivu"
},
{
"zone": "Kimbau",
"province": "Kwango"
},
{
"zone": "Lolanga Mampoko",
"province": "Equateur"
},
{
"zone": "Yangala",
"province": "Kasaï-Central"
},
{
"zone": "Bambo",
"province": "Nord-Kivu"
},
{
"zone": "Nyantende",
"province": "Sud-Kivu"
},
{
"zone": "Kimpangu",
"province": "Kongo-Central"
},
{
"zone": "Kimbi Lulenge",
"province": "Sud-Kivu"
},
{
"zone": "Katana",
"province": "Sud-Kivu"
},
{
"zone": "Wasolo",
"province": "Nord-Ubangi"
},
{
"zone": "Kikimi",
"province": "Kinshasa"
},
{
"zone": "Karawa",
"province": "Nord-Ubangi"
},
{
"zone": "Poko",
"province": "Bas-Uele"
},
{
"zone": "Lukula",
"province": "Kongo-Central"
},
{
"zone": "Manguredjipa",
"province": "Nord-Kivu"
},
{
"zone": "Bondo",
"province": "Bas-Uele"
},
{
"zone": "Bukavu",
"province": "Sud-Kivu"
},
{
"zone": "Tshumbe",
"province": "Sankuru"
},
{
"zone": "Kasongo Lunda",
"province": "Kwango"
},
{
"zone": "Lukonga",
"province": "Kasaï-Central"
},
{
"zone": "Itombwe",
"province": "Sud-Kivu"
},
{
"zone": "Maluku I",
"province": "Kinshasa"
},
{
"zone": "Vaku",
"province": "Kongo-Central"
},
{
"zone": "Kwamouth",
"province": "Maï-Ndombe"
},
{
"zone": "Monieka",
"province": "Equateur"
},
{
"zone": "Monkoto",
"province": "Tshuapa"
},
{
"zone": "Mushie",
"province": "Maï-Ndombe"
},
{
"zone": "Ankoro",
"province": "Tanganyika"
},
{
"zone": "Kalunguta",
"province": "Nord-Kivu"
},
{
"zone": "Luebo",
"province": "Kasaï"
},
{
"zone": "Mawuya",
"province": "Sud-Ubangi"
},
{
"zone": "Beni",
"province": "Nord-Kivu"
},
{
"zone": "Kahemba",
"province": "Kwango"
},
{
"zone": "Police",
"province": "Kinshasa"
},
{
"zone": "Makiso",
"province": "Bas-Uele"
},
{
"zone": "Kizu",
"province": "Kongo-Central"
},
{
"zone": "Likasi",
"province": "Haut-Katanga"
},
{
"zone": "Bosobe",
"province": "Maï-Ndombe"
},
{
"zone": "Cilundu",
"province": "Kasaï-Oriental"
},
{
"zone": "Kailo",
"province": "Maniema"
},
{
"zone": "Lemba",
"province": "Kinshasa"
},
{
"zone": "Tandala",
"province": "Sud-Ubangi"
},
{
"zone": "Kadutu",
"province": "Sud-Kivu"
},
{
"zone": "Yahisuli",
"province": "Tshopo"
},
{
"zone": "Ndekesha",
"province": "Kasaï-Central"
},
{
"zone": "Mambunda",
"province": "Haut-Katanga"
},
{
"zone": "Kitenda",
"province": "Kwango"
},
{
"zone": "Moanda",
"province": "Kongo-Central"
}
]
```
### HTTP Request
`GET api/dashboard/health-zones`
<!-- END_ce9a88f8d8c1d0ee8eb8fd59910bb7cd -->
<!-- START_ca595fbc25ffe036df8883e27f96ca70 -->
## Display a listing of the resource.
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/hospital-situations"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (500):
```json
{
"message": "Server Error"
}
```
### HTTP Request
`GET api/dashboard/hospital-situations`
<!-- END_ca595fbc25ffe036df8883e27f96ca70 -->
<!-- START_957f11ff0b3df14a2d886ac1fdcd08a9 -->
## Store a newly created resource in storage.
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/hospital-situations"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "POST",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
### HTTP Request
`POST api/dashboard/hospital-situations`
<!-- END_957f11ff0b3df14a2d886ac1fdcd08a9 -->
<!-- START_33e8bd496ef56f16f170f43ed1dc11c0 -->
## Display the specified resource.
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/hospital-situations/1"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (404):
```json
{
"message": "No query results for model [App\\HospitalSituation] 1"
}
```
### HTTP Request
`GET api/dashboard/hospital-situations/{hospital_situation}`
<!-- END_33e8bd496ef56f16f170f43ed1dc11c0 -->
<!-- START_dcf7600e95986882b6e59636642971ba -->
## Update the specified resource in storage.
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/hospital-situations/1"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "PUT",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
### HTTP Request
`PUT api/dashboard/hospital-situations/{hospital_situation}`
`PATCH api/dashboard/hospital-situations/{hospital_situation}`
<!-- END_dcf7600e95986882b6e59636642971ba -->
<!-- START_0b970c309ab0229e808aa38a74fc84a8 -->
## Remove the specified resource from storage.
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/hospital-situations/1"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "DELETE",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
### HTTP Request
`DELETE api/dashboard/hospital-situations/{hospital_situation}`
<!-- END_0b970c309ab0229e808aa38a74fc84a8 -->
<!-- START_de8cce562755cf4fdcc198710d40a5a8 -->
## Display a listing of the resource.
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/hospitals-data"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
### HTTP Request
`GET api/dashboard/hospitals-data`
<!-- END_de8cce562755cf4fdcc198710d40a5a8 -->
<!-- START_645864c0263b5836f5893134dacdd87d -->
## Store a newly created resource in storage.
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/hospitals-data"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "POST",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
### HTTP Request
`POST api/dashboard/hospitals-data`
<!-- END_645864c0263b5836f5893134dacdd87d -->
<!-- START_403a4862a31e5e5a6cdbfbea275340a7 -->
## Display the specified resource.
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/hospitals-data/1"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (200):
```json
{
"id": 1,
"created_at": null,
"updated_at": "2020-08-26T20:19:26.000000Z",
"name": "NGALIEMA",
"address": "Ngaliema",
"beds": 0,
"respirators": 2,
"masks": 0,
"latitude": "-4.31435",
"longitude": "15.27123",
"foam_beds": 30,
"resuscitation_beds": 0,
"doctors": 17,
"nurses": 39,
"para_medicals": 17,
"agent_id": 28,
"township_id": 21
}
```
### HTTP Request
`GET api/dashboard/hospitals-data/{hospitals_datum}`
<!-- END_403a4862a31e5e5a6cdbfbea275340a7 -->
<!-- START_10eed1b858a87363223ad70ef62d727b -->
## Update the specified resource in storage.
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/hospitals-data/1"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "PUT",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
### HTTP Request
`PUT api/dashboard/hospitals-data/{hospitals_datum}`
`PATCH api/dashboard/hospitals-data/{hospitals_datum}`
<!-- END_10eed1b858a87363223ad70ef62d727b -->
<!-- START_33b36d6b54cd47ecf6e072e1a030e79f -->
## Remove the specified resource from storage.
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/hospitals-data/1"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "DELETE",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
### HTTP Request
`DELETE api/dashboard/hospitals-data/{hospitals_datum}`
<!-- END_33b36d6b54cd47ecf6e072e1a030e79f -->
<!-- START_1b8aef954674d784e0b63a36cfb82cae -->
## api/dashboard/hospitals
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/hospitals"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (200):
```json
[]
```
### HTTP Request
`GET api/dashboard/hospitals`
<!-- END_1b8aef954674d784e0b63a36cfb82cae -->
<!-- START_6d9b14ea14a0c32ad5c3fafe8c939bc5 -->
## api/dashboard/hospitals/evolution/{hospital?}
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/hospitals/evolution/"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (200):
```json
{
"last_update": [],
"occupied_respirators": [],
"occupied_resuscitation_beds": [],
"respirators": [],
"resuscitation_beds": []
}
```
### HTTP Request
`GET api/dashboard/hospitals/evolution/{hospital?}`
<!-- END_6d9b14ea14a0c32ad5c3fafe8c939bc5 -->
<!-- START_06607724e5312805e02e892542fb6fcd -->
## api/dashboard/hospitals/totaux
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/hospitals/totaux"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (200):
```json
{
"beds": 0,
"respirators": 0,
"foam_beds": 0,
"resuscitation_beds": 0,
"doctors": 0,
"nurses": 0,
"para_medicals": 0,
"occupied_foam_beds": null,
"occupied_resuscitation_beds": null,
"occupied_respirators": null,
"resuscitation_ventilator": null,
"oxygenator": null,
"confirmed": null,
"healed": null,
"dead": null,
"sick": null
}
```
### HTTP Request
`GET api/dashboard/hospitals/totaux`
<!-- END_06607724e5312805e02e892542fb6fcd -->
<!-- START_8679f7d39354383993193c6430007af1 -->
## api/dashboard/indicators/zones
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/indicators/zones"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (422):
```json
{
"message": "The given data was invalid.",
"errors": {
"x": [
"Le champ x est obligatoire."
],
"y": [
"Le champ y est obligatoire."
],
"geoOptions": [
"Le champ geo options est obligatoire."
],
"observation_start": [
"Le champ observation start est obligatoire."
],
"observation_end": [
"Le champ observation end est obligatoire."
]
}
}
```
### HTTP Request
`GET api/dashboard/indicators/zones`
<!-- END_8679f7d39354383993193c6430007af1 -->
<!-- START_ee8ca687d21553b08355eba89aa3ad80 -->
## api/dashboard/orientation-medical-result
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/orientation-medical-result"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (401):
```json
{
"message": "Unauthenticated."
}
```
### HTTP Request
`GET api/dashboard/orientation-medical-result`
<!-- END_ee8ca687d21553b08355eba89aa3ad80 -->
<!-- START_ce9bdf13f8013c328effc5cbbbf0f160 -->
## api/dashboard/orientation-medical-stats
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/orientation-medical-stats"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (401):
```json
{
"message": "Unauthenticated."
}
```
### HTTP Request
`GET api/dashboard/orientation-medical-stats`
<!-- END_ce9bdf13f8013c328effc5cbbbf0f160 -->
<!-- START_eb417f60c80d04047308bcc7d63940b7 -->
## api/dashboard/sondages
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/sondages"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (401):
```json
{
"message": "Unauthenticated."
}
```
### HTTP Request
`GET api/dashboard/sondages`
<!-- END_eb417f60c80d04047308bcc7d63940b7 -->
<!-- START_291357dbc409969f13556bc458e7bf4a -->
## api/dashboard/cavid-cases
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/cavid-cases"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (401):
```json
{
"message": "Unauthenticated."
}
```
### HTTP Request
`GET api/dashboard/cavid-cases`
<!-- END_291357dbc409969f13556bc458e7bf4a -->
<!-- START_43243d39fc6c165664d70135c73c6d37 -->
## api/dashboard/cavid-cases/statistics
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/cavid-cases/statistics"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (401):
```json
{
"message": "Unauthenticated."
}
```
### HTTP Request
`GET api/dashboard/cavid-cases/statistics`
<!-- END_43243d39fc6c165664d70135c73c6d37 -->
<!-- START_5741b81535e88b26744143bb531f5696 -->
## api/dashboard/cavid-cases/statistics/daily
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/cavid-cases/statistics/daily"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (401):
```json
{
"message": "Unauthenticated."
}
```
### HTTP Request
`GET api/dashboard/cavid-cases/statistics/daily`
<!-- END_5741b81535e88b26744143bb531f5696 -->
<!-- START_501198afdc35c7405e31e9ddc276f946 -->
## api/dashboard/flux-24
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/flux-24"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "POST",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
### HTTP Request
`POST api/dashboard/flux-24`
<!-- END_501198afdc35c7405e31e9ddc276f946 -->
<!-- START_cf56dfdb4e0db197c92d3c976f80810f -->
## api/dashboard/flux-24-daily
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/flux-24-daily"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "POST",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
### HTTP Request
`POST api/dashboard/flux-24-daily`
<!-- END_cf56dfdb4e0db197c92d3c976f80810f -->
<!-- START_5a331bf23fdf209fdc70a74055426e6d -->
## Display a listing of the resource.
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/flux-zone"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (200):
```json
[
{
"origin": "Aba"
},
{
"origin": "Adi"
},
{
"origin": "Alimbongo"
},
{
"origin": "Angumu"
},
{
"origin": "Ankoro"
},
{
"origin": "Ariwara"
},
{
"origin": "Bafwasende"
},
{
"origin": "Baka"
},
{
"origin": "Banalia"
},
{
"origin": "Barumbu"
},
{
"origin": "Basoko"
},
{
"origin": "Bena Leka"
},
{
"origin": "Bena Tshiadi"
},
{
"origin": "Bengamisa"
},
{
"origin": "Beni"
},
{
"origin": "Bibanga"
},
{
"origin": "Biena"
},
{
"origin": "Bikoro"
},
{
"origin": "Bilomba"
},
{
"origin": "Binga"
},
{
"origin": "Binza"
},
{
"origin": "Binza Meteo"
},
{
"origin": "Binza Ozone"
},
{
"origin": "Birambizo"
},
{
"origin": "Boko"
},
{
"origin": "Boko-Kivulu"
},
{
"origin": "Bokoro"
},
{
"origin": "Bolobo"
},
{
"origin": "Bolomba"
},
{
"origin": "Boma"
},
{
"origin": "Boma Bungu"
},
{
"origin": "Bominenge"
},
{
"origin": "Bosondjo"
},
{
"origin": "Bukama"
},
{
"origin": "Bulungu"
},
{
"origin": "Bumba"
},
{
"origin": "Bumbu"
},
{
"origin": "Bunia"
},
{
"origin": "Bunkeya"
},
{
"origin": "Bunkonde"
},
{
"origin": "Bunyakiri"
},
{
"origin": "Businga"
},
{
"origin": "Buta"
},
{
"origin": "Cilundu"
},
{
"origin": "Demba"
},
{
"origin": "Dibaya"
},
{
"origin": "Dilala"
},
{
"origin": "Dilolo"
},
{
"origin": "Diulu"
},
{
"origin": "Djalo Djeka"
},
{
"origin": "Djuma"
},
{
"origin": "Drodro"
},
{
"origin": "Fizi"
},
{
"origin": "Fungurume"
},
{
"origin": "Gbadolite"
},
{
"origin": "Gemena"
},
{
"origin": "Gethy"
},
{
"origin": "Gombari"
},
{
"origin": "Gombe"
},
{
"origin": "Hauts-Plateaux"
},
{
"origin": "Hors_Zone"
},
{
"origin": "Ibanda"
},
{
"origin": "Idiofa"
},
{
"origin": "Idjwi"
},
{
"origin": "Ilebo"
},
{
"origin": "Inga"
},
{
"origin": "Isangi"
},
{
"origin": "Isiro"
},
{
"origin": "Itebero"
},
{
"origin": "Itombwe"
},
{
"origin": "Kabambare"
},
{
"origin": "Kabare"
},
{
"origin": "Kabeya Kamuanga"
},
{
"origin": "Kabinda"
},
{
"origin": "Kabondo"
},
{
"origin": "Kabondo Dianda"
},
{
"origin": "Kabongo"
},
{
"origin": "Kahemba"
},
{
"origin": "Kalamba"
},
{
"origin": "Kalamu I"
},
{
"origin": "Kalamu II"
},
{
"origin": "Kalemie"
},
{
"origin": "Kalenda"
},
{
"origin": "Kalima"
},
{
"origin": "Kalole"
},
{
"origin": "Kalonda Ouest"
},
{
"origin": "Kalonge"
},
{
"origin": "Kamango"
},
{
"origin": "Kamiji"
},
{
"origin": "Kamina"
},
{
"origin": "Kamituga"
},
{
"origin": "Kamonia"
},
{
"origin": "Kampemba"
},
{
"origin": "Kampene"
},
{
"origin": "Kamwesha"
},
{
"origin": "Kananga"
},
{
"origin": "Kanda Kanda"
},
{
"origin": "Kangu"
},
{
"origin": "Kaniama"
},
{
"origin": "Kanzenze"
},
{
"origin": "Kapolowe"
},
{
"origin": "Karawa"
},
{
"origin": "Karisimbi"
},
{
"origin": "Kasa-Vubu"
},
{
"origin": "Kasaji"
},
{
"origin": "Kasansa"
},
{
"origin": "Kashobwe"
},
{
"origin": "Kasongo"
},
{
"origin": "Katako Kombe"
},
{
"origin": "Katana"
},
{
"origin": "Katwa"
},
{
"origin": "Kayna"
},
{
"origin": "Kenge"
},
{
"origin": "Kibirizi"
},
{
"origin": "Kibunzi"
},
{
"origin": "Kikimi"
},
{
"origin": "Kikongo"
},
{
"origin": "Kikula"
},
{
"origin": "Kikwit-Sud"
},
{
"origin": "Kilwa"
},
{
"origin": "Kimbanseke"
},
{
"origin": "Kimpangu"
},
{
"origin": "Kimpese"
},
{
"origin": "Kinda"
},
{
"origin": "Kindu"
},
{
"origin": "Kingabwa"
},
{
"origin": "Kinkonzi"
},
{
"origin": "Kinshasa"
},
{
"origin": "Kintambo"
},
{
"origin": "Kipushi"
},
{
"origin": "Kirotshe"
},
{
"origin": "Kisantu"
},
{
"origin": "Kisenso"
},
{
"origin": "Kitangwa"
},
{
"origin": "Kitenda"
},
{
"origin": "Kitenge"
},
{
"origin": "Kitona"
},
{
"origin": "Kokolo"
},
{
"origin": "Kole"
},
{
"origin": "Komanda"
},
{
"origin": "Kuimba"
},
{
"origin": "Kwilu-Ngongo"
},
{
"origin": "Kyondo"
},
{
"origin": "Lemba"
},
{
"origin": "Lemera"
},
{
"origin": "Likasi"
},
{
"origin": "Limete"
},
{
"origin": "Lisala"
},
{
"origin": "Lodja"
},
{
"origin": "Logo"
},
{
"origin": "Loko"
},
{
"origin": "Lualaba"
},
{
"origin": "Luambo"
},
{
"origin": "Lubero"
},
{
"origin": "Lubondaie"
},
{
"origin": "Lubudi"
},
{
"origin": "Lubumbashi"
},
{
"origin": "Lubunga"
},
{
"origin": "Ludimbi Lukula"
},
{
"origin": "Luebo"
},
{
"origin": "Luiza"
},
{
"origin": "Lukula"
},
{
"origin": "Luozi"
},
{
"origin": "Luputa"
},
{
"origin": "Lusangi"
},
{
"origin": "Lwamba"
},
{
"origin": "Mahagi"
},
{
"origin": "Makala"
},
{
"origin": "Makiso-Kisangani"
},
{
"origin": "Malemba Nkulu"
},
{
"origin": "Maluku I"
},
{
"origin": "Mambasa"
},
{
"origin": "Mangembo"
},
{
"origin": "Manguredjipa"
},
{
"origin": "Manika"
},
{
"origin": "Masa"
},
{
"origin": "Masereka"
},
{
"origin": "Masina I"
},
{
"origin": "Masina II"
},
{
"origin": "Masisi"
},
{
"origin": "Masuika"
},
{
"origin": "Matadi"
},
{
"origin": "Matete"
},
{
"origin": "Mbanza-Ngungu"
},
{
"origin": "Miabi"
},
{
"origin": "Mikalayi"
},
{
"origin": "Minembwe"
},
{
"origin": "Minova"
},
{
"origin": "Moanda"
},
{
"origin": "Mokala"
},
{
"origin": "Monga"
},
{
"origin": "Mongbalu"
},
{
"origin": "Mont Ngafula I"
},
{
"origin": "Mont Ngafula II"
},
{
"origin": "Mukanga"
},
{
"origin": "Mukumbi"
},
{
"origin": "Mulongo"
},
{
"origin": "Mulumba"
},
{
"origin": "Mushie"
},
{
"origin": "Musienene"
},
{
"origin": "Mutena"
},
{
"origin": "Mutoto"
},
{
"origin": "Mutshatsha"
},
{
"origin": "Mutwanga"
},
{
"origin": "Mweka"
},
{
"origin": "Mwene Ditu"
},
{
"origin": "Mwenga"
},
{
"origin": "Mweso"
},
{
"origin": "Ndage"
},
{
"origin": "Ndekesha"
},
{
"origin": "Ndjili"
},
{
"origin": "Ngandajika"
},
{
"origin": "Ngidinga"
},
{
"origin": "Ngiri-Ngiri"
},
{
"origin": "Nia-Nia"
},
{
"origin": "Niangara"
},
{
"origin": "Nioki"
},
{
"origin": "Nsele"
},
{
"origin": "Nsona-Mpangu"
},
{
"origin": "Nundu"
},
{
"origin": "Nyakunde"
},
{
"origin": "Nyangezi"
},
{
"origin": "Nyarambe"
},
{
"origin": "Nyemba"
},
{
"origin": "Nyiragongo"
},
{
"origin": "Oicha"
},
{
"origin": "Omendjadi"
},
{
"origin": "Pimu"
},
{
"origin": "Poko"
},
{
"origin": "Police"
},
{
"origin": "Pweto"
},
{
"origin": "Rungu"
},
{
"origin": "Rutshuru"
},
{
"origin": "Ruzizi"
},
{
"origin": "Rwanguba"
},
{
"origin": "Rwashi"
},
{
"origin": "Sakania"
},
{
"origin": "Samba"
},
{
"origin": "Sandoa"
},
{
"origin": "Saramabila"
},
{
"origin": "Seke-Banza"
},
{
"origin": "Selembao"
},
{
"origin": "Shabunda"
},
{
"origin": "Sona-Bata"
},
{
"origin": "Tandala"
},
{
"origin": "Tembo"
},
{
"origin": "Tshamilemba"
},
{
"origin": "Tshela"
},
{
"origin": "Tshikapa"
},
{
"origin": "Tshilenge"
},
{
"origin": "Tshishimbi"
},
{
"origin": "Ubundu"
},
{
"origin": "Uvira"
},
{
"origin": "Vaku"
},
{
"origin": "Vanga"
},
{
"origin": "Vanga Kete"
},
{
"origin": "Vuhovi"
},
{
"origin": "Walungu"
},
{
"origin": "Wamba"
},
{
"origin": "Wangata"
},
{
"origin": "Wanierukula"
},
{
"origin": "Watsa"
},
{
"origin": "Yabaondo"
},
{
"origin": "Yahuma"
},
{
"origin": "Yakusu"
},
{
"origin": "Yambuku"
},
{
"origin": "Yangala"
},
{
"origin": "Zongo"
},
{
"origin": "Aru"
},
{
"origin": "Boende"
},
{
"origin": "Bondo"
},
{
"origin": "Bongandanga"
},
{
"origin": "Dungu"
},
{
"origin": "Feshi"
},
{
"origin": "Gungu"
},
{
"origin": "Kafakumba"
},
{
"origin": "Kongolo"
},
{
"origin": "Kunda"
},
{
"origin": "Likati"
},
{
"origin": "Lolo"
},
{
"origin": "Lubao"
},
{
"origin": "Mangala"
},
{
"origin": "Manono"
},
{
"origin": "Moba"
},
{
"origin": "Mufunga Sampwe"
},
{
"origin": "Ototo"
},
{
"origin": "Punia"
},
{
"origin": "Tshofa"
},
{
"origin": "Yaleko"
},
{
"origin": "Kasongo Lunda"
},
{
"origin": "Kabalo"
},
{
"origin": "Lomela"
},
{
"origin": "Yamongili"
},
{
"origin": "Minga"
},
{
"origin": "Tshumbe"
},
{
"origin": "Kapanga"
},
{
"origin": "Dikungu"
},
{
"origin": "Wembo Nyama"
},
{
"origin": "Mikope"
},
{
"origin": "Banga Lubaka"
},
{
"origin": "Lubutu"
},
{
"origin": "Kalonda Est"
},
{
"origin": "Kitutu"
},
{
"origin": "Bangabola"
},
{
"origin": "Kinkondja"
}
]
```
### HTTP Request
`GET api/dashboard/flux-zone`
<!-- END_5a331bf23fdf209fdc70a74055426e6d -->
<!-- START_771172e71e1b6cb6de6e8fd7e84f8518 -->
## api/dashboard/flux-provinces
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/flux-provinces"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (200):
```json
[
{
"origin": "Bas-Uele"
},
{
"origin": "Equateur"
},
{
"origin": "Haut-Katanga"
},
{
"origin": "Haut-Lomami"
},
{
"origin": "Haut-Uele"
},
{
"origin": "Hors_Zone"
},
{
"origin": "Ituri"
},
{
"origin": "Kasai"
},
{
"origin": "Kasai-Central"
},
{
"origin": "Kasai-Oriental"
},
{
"origin": "Kinshasa"
},
{
"origin": "Kongo-Central"
},
{
"origin": "Kwango"
},
{
"origin": "Kwilu"
},
{
"origin": "Lomami"
},
{
"origin": "Lualaba"
},
{
"origin": "Mai-Ndombe"
},
{
"origin": "Maniema"
},
{
"origin": "Mongala"
},
{
"origin": "Nord-Kivu"
},
{
"origin": "Nord-Ubangi"
},
{
"origin": "Sankuru"
},
{
"origin": "Sud-Kivu"
},
{
"origin": "Sud-Ubangi"
},
{
"origin": "Tanganyika"
},
{
"origin": "Tshopo"
},
{
"origin": "Tshuapa"
}
]
```
### HTTP Request
`GET api/dashboard/flux-provinces`
<!-- END_771172e71e1b6cb6de6e8fd7e84f8518 -->
<!-- START_f21495e53b04eb565efa059fc92eaf02 -->
## api/dashboard/townships
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/townships"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (401):
```json
{
"message": "Unauthenticated."
}
```
### HTTP Request
`GET api/dashboard/townships`
<!-- END_f21495e53b04eb565efa059fc92eaf02 -->
<!-- START_92726ed280897baec1fa2f410d062622 -->
## api/dashboard/pandemics/top-confirmed
> Example request:
```javascript
const url = new URL(
"http://localhost:8000/api/dashboard/pandemics/top-confirmed"
);
let headers = {
"Content-Type": "application/json",
"Accept": "application/json",
"Authorization": "Bearer {token}",
};
fetch(url, {
method: "GET",
headers: headers,
})
.then(response => response.json())
.then(json => console.log(json));
```
> Example response (422):
```json
{
"message": "The given data was invalid.",
"errors": {
"fluxGeoOptions": [
"Le champ flux geo options est obligatoire."
]
}
}
```
### HTTP Request
`GET api/dashboard/pandemics/top-confirmed`
<!-- END_92726ed280897baec1fa2f410d062622 -->
| 20.969868 | 316 | 0.514342 | yue_Hant | 0.152775 |
22d47543e26fa5b1fdeeca805e90831d8dbea9fe | 102 | md | Markdown | README.md | jaiswalanshul/Azure-Data-Factory-For-Data-Engineers---Project-on-Covid19 | f5f5dc77457970f31421f3c3f90ba04db4d57a72 | [
"MIT"
] | null | null | null | README.md | jaiswalanshul/Azure-Data-Factory-For-Data-Engineers---Project-on-Covid19 | f5f5dc77457970f31421f3c3f90ba04db4d57a72 | [
"MIT"
] | null | null | null | README.md | jaiswalanshul/Azure-Data-Factory-For-Data-Engineers---Project-on-Covid19 | f5f5dc77457970f31421f3c3f90ba04db4d57a72 | [
"MIT"
] | 1 | 2021-03-04T20:05:17.000Z | 2021-03-04T20:05:17.000Z | # Azure Data Factory - Project on Covid19
Azure Data Factory For Data Engineers - Project on Covid19
| 34 | 59 | 0.784314 | kor_Hang | 0.815452 |
22d58d8d2fad3c1cc3191ca6be4e4a187eec874c | 199 | md | Markdown | README.md | siglite/pseudo-httpd-errors | 6c5f1a4be3f8bdb6111759fb2fa77bdaf2942c7a | [
"Apache-2.0"
] | null | null | null | README.md | siglite/pseudo-httpd-errors | 6c5f1a4be3f8bdb6111759fb2fa77bdaf2942c7a | [
"Apache-2.0"
] | null | null | null | README.md | siglite/pseudo-httpd-errors | 6c5f1a4be3f8bdb6111759fb2fa77bdaf2942c7a | [
"Apache-2.0"
] | null | null | null | Pseudo-httpd-errors
===================
Nginx custom error pages like Apache.
## Requirements
- Nginx with SSI module
## Authors
- Shun Ishihara <<[email protected]>>
## License
Apache License 2.0
| 14.214286 | 37 | 0.663317 | kor_Hang | 0.423499 |
22d5acecdf89b766e4458d659e882e91b117c14e | 2,167 | md | Markdown | source/includes/authorization/_027-verify-connection.md | ibnc/plugin-api.go.cd | 158ffbfe4e4e9c0fa8066859458db86c012f2683 | [
"Apache-2.0"
] | 9 | 2017-03-22T00:48:41.000Z | 2020-04-13T09:23:04.000Z | source/includes/authorization/_027-verify-connection.md | ibnc/plugin-api.go.cd | 158ffbfe4e4e9c0fa8066859458db86c012f2683 | [
"Apache-2.0"
] | 564 | 2016-04-08T14:29:39.000Z | 2021-12-24T12:41:50.000Z | source/includes/authorization/_027-verify-connection.md | ibnc/plugin-api.go.cd | 158ffbfe4e4e9c0fa8066859458db86c012f2683 | [
"Apache-2.0"
] | 42 | 2016-03-17T11:32:28.000Z | 2020-01-03T10:36:58.000Z | ## Verify Connection
The plugin must implement this message in order to verify if a connection can be established with the authorization server using the authorization configuration.
The plugin is expected to validate the configuration before trying to check connection.
<p class='request-name-heading'>Request name</p>
`go.cd.authorization.auth-config.verify-connection`
<p class='request-body-heading'>Request body</p>
> An example LDAP plugin authorization configuration request body to verify connection
```json
{
"Url": "ldap://foo.bar.com:389",
"SearchBase": "ou=users,ou=system",
"ManagerDN": "Dummy manager dn",
"UserLoginFilter": "(uid={0})",
"Password": "secret",
"DisplayNameAttribute": "displayName",
"EmailAttribute": "mail"
}
```
The request body will contain the authorization configuration for which verify connection is executed.
<p class='response-code-heading'>Response code</p>
The plugin is expected to return status `200` if it can understand the request.
<p class='response-body-heading'>Response Body</p>
> Example response body based on successful verification
```json
{
"status": "success",
"message": "Check connection passed"
}
```
> Example response body based on verification failed
```json
{
"status": "failure",
"message": "Check connection failed, unable to reach ldap://my_ldap_server"
}
```
> Example response body based on validation failed
```json
{
"status": "validation-failed",
"message": "Validation failed for the given authorization config",
"errors": [
{
"key": "ManagerDN",
"message": "Manager dn is invalid."
}
]
}
```
The response body will contain the following JSON elements:
<p class='attributes-table-follows'></p>
| Key | Type | Description |
|-----------|----------|-------------|
| `status` | `String` | Status of verify connection call, can be eithe of `success` or `failure` or `validation-failure` |
| `message` | `String` | Message corresponding to the verify connection status. |
| `errors` | `Object` | In case of validation errors plugin should return a list of [validation error objects](#the-validation-error-object).|
| 28.513158 | 161 | 0.703276 | eng_Latn | 0.92947 |
22d67f26c7d0e1b3b55c841b259749a43bd6de96 | 301 | md | Markdown | README.md | Mathman628/find-close-meteorites | 6fd9f9284bf966d341817e10fca1b7220565a87d | [
"MIT"
] | null | null | null | README.md | Mathman628/find-close-meteorites | 6fd9f9284bf966d341817e10fca1b7220565a87d | [
"MIT"
] | null | null | null | README.md | Mathman628/find-close-meteorites | 6fd9f9284bf966d341817e10fca1b7220565a87d | [
"MIT"
] | null | null | null | # find-close-meteorites
A demo project that uses Python and NASA data to find meteor landing sites. From a tutorial on A Cloud Guru.
## Running
This projectrequires Python 3 and the requests package.
First, install pipenv. Then:
```
pipenv install
pipenv run "python meteors/find_meteors.py"
```
| 21.5 | 108 | 0.76412 | eng_Latn | 0.909128 |
22d78c554e0377f5beffd8d4e5fc629a43286e5b | 495 | md | Markdown | chrome-cordova/plugins/chrome.alarms/README.md | michilu/mobile-chrome-apps | 4a54d3178292e6c6f5db7cc904d34ac90d110a36 | [
"BSD-3-Clause"
] | 1 | 2018-05-29T15:41:41.000Z | 2018-05-29T15:41:41.000Z | plugins/org.chromium.alarms/README.md | simonkoennecke/zzZwitscherwecker | 363b3e66ded0a0da6f02126d4941ee3ac824abae | [
"Unlicense",
"MIT"
] | null | null | null | plugins/org.chromium.alarms/README.md | simonkoennecke/zzZwitscherwecker | 363b3e66ded0a0da6f02126d4941ee3ac824abae | [
"Unlicense",
"MIT"
] | null | null | null | # chrome.alarms Plugin
This plugin allows apps to register alarms.
## Status
Stable on Android; not supported on iOS.
## Caveats
### Android
You have to manually change the theme to translucent in `platforms/android/AndroidManifest.xml` by changing `"Theme.Black.NoTitleBar"` to `"Theme.Translucent"` inside your `<activity>` tag.
## Reference
The API reference is [here](http://developer.chrome.com/apps/alarms.html).
# Release Notes
## 1.0.1 (March 10, 2014)
- Documentation updates.
| 22.5 | 189 | 0.741414 | eng_Latn | 0.704259 |
22d833dbad3b4c1b7dc9c6c2354f0d2e17bec941 | 441 | md | Markdown | README.md | richardwlb/primelofts-web | 8653ad2cdfe1978f084226df72f52dc56fd7222d | [
"MIT"
] | null | null | null | README.md | richardwlb/primelofts-web | 8653ad2cdfe1978f084226df72f52dc56fd7222d | [
"MIT"
] | null | null | null | README.md | richardwlb/primelofts-web | 8653ad2cdfe1978f084226df72f52dc56fd7222d | [
"MIT"
] | null | null | null | # Prime Lofts
<p>
<img src="https://img.shields.io/badge/made%20by-RICHARD%20BREHMER-04D361?style=flat-square">
<a href="https://opensource.org/licenses/MIT">
<img alt="License" src="https://img.shields.io/badge/license-MIT-04D361?style=flat-square">
</a>
</p>
## About Prime Lofts
This is the web part of the project. This will be used to manage an apartments for rental.
## Technologies
- Node
- React
- React native
- Mysql | 23.210526 | 95 | 0.707483 | eng_Latn | 0.541434 |
22d9b6c95d4f5c99e76ffc9796e9f32e8bcdac32 | 51 | md | Markdown | README.md | schultek/connect-utils | d6e0cac89afdf89aee97464319637a410783aaf4 | [
"MIT"
] | null | null | null | README.md | schultek/connect-utils | d6e0cac89afdf89aee97464319637a410783aaf4 | [
"MIT"
] | 1 | 2021-05-11T03:22:00.000Z | 2021-05-11T03:22:00.000Z | README.md | schultek/connect-utils | d6e0cac89afdf89aee97464319637a410783aaf4 | [
"MIT"
] | null | null | null | # connect-utils
Utility Nodes for Connect Platform | 17 | 34 | 0.823529 | eng_Latn | 0.993776 |
22dab6fdd0b413b06337b0adbbbf485f7ce5af95 | 421 | md | Markdown | content/alldata/tabuk_doner-1.md | abdulkadirakyildiz/netlify-gatsby-md | 3a1ecf4836da7a171d761ea3681776c24f99788f | [
"RSA-MD"
] | null | null | null | content/alldata/tabuk_doner-1.md | abdulkadirakyildiz/netlify-gatsby-md | 3a1ecf4836da7a171d761ea3681776c24f99788f | [
"RSA-MD"
] | null | null | null | content/alldata/tabuk_doner-1.md | abdulkadirakyildiz/netlify-gatsby-md | 3a1ecf4836da7a171d761ea3681776c24f99788f | [
"RSA-MD"
] | null | null | null | ---
title: tabuk_doner
name: Tavuk Döner
price: 8
description: Tavuk Döner ........Özel sinisi içerisinde, el açma hamuru ile usta
ellerde hazırlanan, cevizi bol, kesimi özel, şerbeti taze olarak verilmiş
olarak hazırlanır. Her bir porsiyonda 4 adet servis edilir.
rating: 5
currency: ₺
image: content/images/chicken-food.png
categories:
- all
- fast-foot
related_products:
- cevizli-baklaca
- salata-rus
---
| 23.388889 | 80 | 0.743468 | tur_Latn | 0.991896 |
22db3172fd3f78d9230de609d820f6dac6dee9b8 | 4,106 | md | Markdown | README.md | cod-e-ash/FindSource | ffda5eb3405ba259cc6d1a6b6c92b14e9588804b | [
"Apache-2.0"
] | 4 | 2018-11-13T08:07:49.000Z | 2019-11-18T20:29:45.000Z | README.md | cod-e-ash/FindSource | ffda5eb3405ba259cc6d1a6b6c92b14e9588804b | [
"Apache-2.0"
] | null | null | null | README.md | cod-e-ash/FindSource | ffda5eb3405ba259cc6d1a6b6c92b14e9588804b | [
"Apache-2.0"
] | 1 | 2019-11-18T20:30:28.000Z | 2019-11-18T20:30:28.000Z | # RPG Find Source
This is part of my **`RPG Utils`** series to help overcome some of the day-to-day activities which can be automated.
Developers, QA, Analyst or anyone who wants to access source code in RPG _rejoice_. This will help you to find any source within many libraries with just one command. Just set the library list once and enjoy.
## Getting Started
These instructions will get you a copy of the project up and running on your local machine for development and testing purposes.
### Prerequisites
You need to have AS400 Machine access (duh!)
Create a RPGUtils Source File to store the files.
```
CRTSRCPF RPGUTILS
```
### Program and Object Descriptions
* `LIBLISTF`
This is a PF source which will hold the library list data.
* `LIBLISTP`
This is the program to maintain library list.
* `LIBLISTD`
Display file required for library list program.
* `LIBLISTCMD`
Command source file.
* `VALLSRCC`
Driver CL program.
* `VALLSRCCMD`
Driver command source file.
* `VALLSRCD`
Display file used by main program.
* `VALLSRCP`
Main program.
* `CPYBK`
A copybook to store prototype definitions and other. If you use any other library that RPGUTILS, please change the path in above RPG program/s for this copy book.
### Installing
**Step 1.**
Upload all files to AS400 server, use ftp. <em>DO NOT CHANGE THE MODE TO BINARY</em>.
```
open pub400.com
username
password
cd /QSYS.LIB
cd YOURLIB.LIB
cd RPGUTILS.FILE
mput *.MBR
disconnect
quit
```
**Step 2.**
Change the attribute type accordingly once uploaded.
```
LIBLISTCMD CMD
LIBLISTD DSPF
LIBLISTF PF
LIBLISTP SQLRPGLE
VALLSRCC CLLE
VALLSRCCMD CMD
VALLSRCD DSPF
VALLSRCP SQLRPGLE
CPYBK CPY
```
**Step3.**
Use below command to compile.
```
DSPOBJD OBJ(YOURLIB) OBJTYPE(*LIB) OUTPUT(*OUTFILE) OUTFILE(QTEMP/LIBINFOF)
CRTPF FILE(YOURLIB/LIBLISTF) SRCFILE(YOURLIB/RPGUTILS) SRCMBR(LIBLISTF)
CRTDSPF FILE(YOURLIB/LIBLISTD) SRCFILE(YOURLIB/RPGUTILS) SRCMBR(LIBLISTD) REPLACE(*YES)
CRTDSPF FILE(YOURLIB/VALLSRCD) SRCFILE(YOURLIB/RPGUTILS) SRCMBR(LIBLISTD) REPLACE(*YES)
CRTSQLRPGI OBJ(YOURLIB/LIBLISTP) SRCFILE((YOURLIB/RPGUTILS) SRCMBR(LIBLISTP) OBJTYPE(*PGM) REPLACE(*YES)
CRTSQLRPGI OBJ(YOURLIB/VALLSRCP) SRCFILE((YOURLIB/RPGUTILS) SRCMBR(VALLSRCP) OBJTYPE(*PGM) REPLACE(*YES)
CRTBNDCL PGM(YOURLIB/VALLSRCC) SRCFILE((YOURLIB/RPGUTILS) SRCMBR(VALLSRCC) REPLACE(*NO)
CRTCMD CMD(YOURLIB/LIBLIST) PGM(*LIBL/LIBLISTP) SRCFILE(YOURLIB/RPGUTILS) SRCMBR(LIBLISTCMD) REPLACE(*YES)
CRTCMD CMD(YOURLIB/FA) PGM(*LIBL/VALLSRCC) SRCFILE(YOURLIB/RPGUTILS) SRCMBR(VALLSRCCMD) REPLACE(*YES)
```
**Step 4.**
Add libraries to library list using below command.
```
LIBLIST
```
This would ask for following things:
```
LIBRARY......:
SEQUENCE.....:
OBJECT/SOURCE: (O/S/B)
PROGRAM/DATA.: (P/D/B)
```
Library is the library you want to add. Leave the sequence blank for now. Used for search sequence of libraries.
**O**bject or **S**ource or **B**oth. Since library list is used by my other utilities, this is some extra information for now.
Object library would be library which contains objects only. Source would be for source. Both for Both :)
You can enter 'B'.
**Programs** or **Data** or **Both**. If library is object library, then whether it holds only programs or files or both.
You can enter 'B'.
## Running
```
FA <source member name>
```
E.g. Now, if we want to find all the places (libraries that we added in library list) where source for LIBLISTP is present, we would:
FA LIBLISTP (this will show the source from all the libraries, if present in that library)
You can the then position the cursor on select line and press enter to view the source.
## Authors
Ashish Bagaddeo
## License
This project is licensed under the Apache License v2.0 - see the [LICENSE.md](LICENSE.md) file for details
## Acknowledgments
Thanks www.PUB400.com for hosting a public server.
| 28.915493 | 208 | 0.707501 | eng_Latn | 0.824174 |
22db351781d7929fa55a56bc99a1f5748b4acf5a | 1,181 | md | Markdown | _submissions/round-12/1/2015-02-24-mutable-immutable-python-concept-map.md | kbroman/SWC_training_course | a2881f1544c0bcfe35539a571ac0aff5efeca0a7 | [
"CC-BY-4.0"
] | 13 | 2015-02-06T16:35:46.000Z | 2021-02-14T22:36:41.000Z | _submissions/round-12/1/2015-02-24-mutable-immutable-python-concept-map.md | kbroman/SWC_training_course | a2881f1544c0bcfe35539a571ac0aff5efeca0a7 | [
"CC-BY-4.0"
] | 111 | 2015-01-25T18:52:36.000Z | 2017-02-06T14:11:36.000Z | _submissions/round-12/1/2015-02-24-mutable-immutable-python-concept-map.md | kbroman/SWC_training_course | a2881f1544c0bcfe35539a571ac0aff5efeca0a7 | [
"CC-BY-4.0"
] | 124 | 2015-01-22T00:06:47.000Z | 2021-08-09T12:19:36.000Z | ---
date: 2015-02-26
round: Round 12
title: Python Mutable vs Immutable Concept Map
author: Francisco Navarro
permalink: /2015/02/mutable-immutable-python-concept-map/
tags:
- Python
- Mutable
- Immutable
- Concept Map
---
Although simple, I think that this concept map might be useful for non-programmers.
I have found that these to variable types are often confused and can lead to important bugs not easy to find. I think that the example shown provides a context where this can easily be understood. Adding or removing dimensions "redefine" your system (notice the reference the classic book Flatland). Python also reallocates the memory address when you execute `coordinates +=(z)` whereas it does not when using a list.
This concept map links with [this lesson](http://software-carpentry.org/v5/novice/python/04-cond.html) which explains the similarities and differences between tuples and lists.
Any comment is more than welcome ;)
P.S.: I’ve got inspired by [this answer in SO](http://stackoverflow.com/questions/1708510/python-list-vs-tuple-when-to-use-each#comment22973344_1708610)
| 47.24 | 418 | 0.779848 | eng_Latn | 0.994942 |
22dc28ca7f937cf108976aefcf328e6ec3e6b18e | 1,793 | md | Markdown | AlchemyInsights/commercial-dialogues/conditional-access-with-intune.md | isabella232/OfficeDocs-AlchemyInsights-pr.pt-BR | 61447e6f79e6a5ca40e5e50168da971230d5f9b7 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-05-19T19:07:30.000Z | 2020-05-19T19:07:30.000Z | AlchemyInsights/commercial-dialogues/conditional-access-with-intune.md | isabella232/OfficeDocs-AlchemyInsights-pr.pt-BR | 61447e6f79e6a5ca40e5e50168da971230d5f9b7 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2022-02-09T06:58:01.000Z | 2022-02-09T06:58:58.000Z | AlchemyInsights/commercial-dialogues/conditional-access-with-intune.md | isabella232/OfficeDocs-AlchemyInsights-pr.pt-BR | 61447e6f79e6a5ca40e5e50168da971230d5f9b7 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2019-10-11T19:14:27.000Z | 2021-10-13T10:06:06.000Z | ---
title: Usando o Acesso Condicional com o Intune
ms.author: v-jmathew
author: v-jmathew
manager: dansimp
audience: Admin
ms.topic: article
ms.service: o365-administration
ROBOTS: NOINDEX, NOFOLLOW
localization_priority: Normal
ms.collection: Adm_O365
ms.custom:
- "6700002"
- "7680"
ms.openlocfilehash: 23afea21668191093d612d68ca6e9ab2a844f4a14977631d33f4fd956fc3c4e7
ms.sourcegitcommit: b5f7da89a650d2915dc652449623c78be6247175
ms.translationtype: MT
ms.contentlocale: pt-BR
ms.lasthandoff: 08/05/2021
ms.locfileid: "54005762"
---
# <a name="using-conditional-access-with-intune"></a>Usando o Acesso Condicional com o Intune
O uso do Acesso Condicional com o Intune requer três etapas:
- [Crie uma Política de Conformidade para definir as configurações que devem ser atendidas antes que o dispositivo seja considerado compatível. Por exemplo, um dispositivo deve ter um pino de pelo menos 6 dígitos antes de ser considerado compatível.](https://docs.microsoft.com/mem/intune/protect/create-compliance-policy)
- [Crie uma Política de Acesso Condicional que define quais recursos estão sendo protegidos e quais condições precisam ser atendidas para acessar esses recursos. Por exemplo, um dispositivo deve estar em conformidade antes de acessar emails corporativos.](https://docs.microsoft.com/mem/intune/protect/tutorial-protect-email-on-unmanaged-devices#create-conditional-access-policies)
- [Verifique se as Políticas de Conformidade e as Políticas de Acesso Condicional são direcionadas aos grupos de usuários desejados. Isso pode exigir a criação de grupos específicos de usuários Azure Active Directory.](https://docs.microsoft.com/troubleshoot/mem/intune/troubleshoot-conditional-access)
[Leia mais...](https://docs.microsoft.com/mem/intune/protect/device-compliance-get-started)
| 57.83871 | 381 | 0.81874 | por_Latn | 0.977257 |
22ddc0d807db701b86adfdba46fe64c6e263887f | 113,289 | md | Markdown | security-updates/SecurityBulletins/2012/ms12-070.md | MicrosoftDocs/security-updates.pt-br | 41600ce6b74586b6e44b480e21ffcd62b9524fcb | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-05-19T20:16:43.000Z | 2020-05-19T20:16:43.000Z | security-updates/SecurityBulletins/2012/ms12-070.md | MicrosoftDocs/security-updates.pt-br | 41600ce6b74586b6e44b480e21ffcd62b9524fcb | [
"CC-BY-4.0",
"MIT"
] | 216 | 2017-12-12T22:09:38.000Z | 2018-12-10T00:42:52.000Z | security-updates/SecurityBulletins/2012/ms12-070.md | MicrosoftDocs/security-updates.pt-br | 41600ce6b74586b6e44b480e21ffcd62b9524fcb | [
"CC-BY-4.0",
"MIT"
] | 2 | 2018-01-15T07:03:29.000Z | 2021-11-18T13:14:23.000Z | ---
TOCTitle: 'MS12-070'
Title: 'Microsoft Security Bulletin MS12-070 - Importante'
ms:assetid: 'ms12-070'
ms:contentKeyID: 61234592
ms:mtpsurl: 'https://technet.microsoft.com/pt-BR/library/ms12-070(v=Security.10)'
---
Microsoft Security Bulletin MS12-070 - Importante
=================================================
Vulnerabilidade no SQL Server pode permitir a elevação de privilégio (2754849)
------------------------------------------------------------------------------
Publicado: terça-feira, 9 de outubro de 2012
**Versão:** 1.0
### Informações Gerais
#### Sinopse
Esta atualização de segurança resolve uma vulnerabilidade relatada em particular no Microsoft SQL Server em sistemas que executam o SQL Server Reporting Services (SSRS). A vulnerabilidade é um scripting entre sites (XSS) que pode permitir elevação de privilégio, possibilitando que um invasor execute comandos arbitrários no site SSRS no contexto do usuário de destino. O invasor pode explorar essa vulnerabilidade enviando um link especialmente criado ao usuário e convencendo-o a clicar no link. O invasor também pode hospedar um site que contém uma página da Web projetada para explorar a vulnerabilidade. Além disso, sites comprometidos e sites que aceitem ou hospedem conteúdo fornecido pelo usuário ou anúncios podem conter conteúdo especialmente criado que pode explorar esta vulnerabilidade.
Esta atualização de segurança é classificada como Importante para o Microsoft SQL Server 2000 Reporting Services Service Pack 2 e para sistemas que executam o SQL Server Reporting Services (SSRS) no Microsoft SQL Server 2005 Service Pack 4, Microsoft SQL Server 2008 Service Pack 2, Microsoft SQL Server 2008 Service Pack 3, Microsoft SQL Server 2008 R2 Service Pack 1 e Microsoft SQL Server 2012. Para obter mais informações, consulte a subseção **Softwares afetados e não afetados**, nesta seção.
A atualização de segurança elimina a vulnerabilidade, corrigindo a maneira como o SQL Server Report Manager valida os parâmetros de entrada. Para obter mais informações sobre a vulnerabilidade, consulte a subseção Perguntas frequentes relacionada à entrada da vulnerabilidade específica presente na próxima seção, **Informações sobre a vulnerabilidade**.
**Recomendação.** A Microsoft recomenda que os clientes instalem a atualização o mais rápido possível.
**Problemas conhecidos.** O [artigo 2754849 (em inglês) da Microsoft Knowledge Base](http://support.microsoft.com/kb/2754849) documenta os problemas atualmente conhecidos que os clientes podem enfrentar ao instalar esta atualização de segurança. O artigo também documenta as soluções recomendadas para esses problemas.
#### Softwares afetados e não afetados
Os softwares a seguir foram testados para determinar quais versões ou edições foram afetadas. O ciclo de vida do suporte das outras versões ou edições já terminou ou elas não são afetadas. Para determinar o ciclo de vida do suporte para sua versão ou edição de software, visite o site [Ciclo de vida do suporte Microsoft.](http://go.microsoft.com/fwlink/?linkid=21742)
**Microsoft SQL Server**
Dependendo da edição ou versão do seu software, você pode ter que escolher entre os links de atualização de GDR e QFE abaixo para instalar manualmente sua atualização do Centro de Download da Microsoft. Para mais informações sobre como determinar qual atualização deve ser instalada em seu sistema, consulte a subseção **Perguntas frequentes relacionadas a esta atualização de segurança** nesta seção.
<p> </p>
<table style="border:1px solid black;">
<tr class="thead">
<th style="border:1px solid black;" >
Atualizações de software GDR
</th>
<th style="border:1px solid black;" >
Atualizações de software QFE
</th>
<th style="border:1px solid black;" >
Impacto máximo à segurança
</th>
<th style="border:1px solid black;" >
Avaliação de gravidade agregada
</th>
<th style="border:1px solid black;" >
Atualizações substituídas
</th>
</tr>
<tr>
<th style="border:1px solid black;" colspan="5">
SQL Server 2000
</th>
</tr>
<tr>
<td style="border:1px solid black;">
Não Aplicável
</td>
<td style="border:1px solid black;">
[Microsoft SQL Server 2000 Reporting Services Service Pack 2](http://www.microsoft.com/downloads/details.aspx?familyid=1c70a2cb-e8a9-439f-b34a-7d1641daf325)
(KB983814)
</td>
<td style="border:1px solid black;">
Elevação de privilégio
</td>
<td style="border:1px solid black;">
Importante
</td>
<td style="border:1px solid black;">
KB970899 no [MS09-062](http://technet.microsoft.com/pt-br/security/bulletin/ms09-062) substituído pelo boletim KB983814
</td>
</tr>
<tr>
<th style="border:1px solid black;" colspan="5">
SQL Server 2005
</th>
</tr>
<tr class="alternateRow">
<td style="border:1px solid black;">
[Microsoft SQL Server 2005 Express Edition com Advanced Services Service Pack 4](http://www.microsoft.com/downloads/details.aspx?familyid=623841cc-06f7-4475-b2c0-531aed9972a3)<sup>[1]</sup>
(KB2716429)
</td>
<td style="border:1px solid black;">
[Microsoft SQL Server 2005 Express Edition com Advanced Services Service Pack 4](http://www.microsoft.com/downloads/details.aspx?familyid=16cc7b80-ea4c-4b17-9ac2-250b771a569a)<sup>[1]</sup>
(KB2716427)
</td>
<td style="border:1px solid black;">
Elevação de privilégio
</td>
<td style="border:1px solid black;">
Importante
</td>
<td style="border:1px solid black;">
KB2494120 e KB2546869, no [MS11-049](http://technet.microsoft.com/pt-br/security/bulletin/ms11-049), substituídos pelo boletim KB2716429
KB2494123 no [MS11-049](http://technet.microsoft.com/pt-br/security/bulletin/ms11-049) substituído pelo boletim KB2716427
</td>
</tr>
<tr>
<td style="border:1px solid black;">
[Microsoft SQL Server 2005 para sistemas de 32 bits Service Pack](http://www.microsoft.com/downloads/details.aspx?familyid=623841cc-06f7-4475-b2c0-531aed9972a3)4<sup>[1]</sup>
(KB2716429)
</td>
<td style="border:1px solid black;">
[Microsoft SQL Server 2005 para sistemas de 32 bits Service Pack](http://www.microsoft.com/downloads/details.aspx?familyid=16cc7b80-ea4c-4b17-9ac2-250b771a569a)4<sup>[1]</sup>
(KB2716427)
</td>
<td style="border:1px solid black;">
Elevação de privilégio
</td>
<td style="border:1px solid black;">
Importante
</td>
<td style="border:1px solid black;">
KB2494120 e KB2546869, no [MS11-049](http://technet.microsoft.com/pt-br/security/bulletin/ms11-049), substituídos pelo boletim KB2716429
KB2494123 no [MS11-049](http://technet.microsoft.com/pt-br/security/bulletin/ms11-049) substituído pelo boletim KB2716427
</td>
</tr>
<tr class="alternateRow">
<td style="border:1px solid black;">
[Microsoft SQL Server 2005 para sistemas baseados em x64 Service Pack 4](http://www.microsoft.com/downloads/details.aspx?familyid=623841cc-06f7-4475-b2c0-531aed9972a3)<sup>[1]</sup>
(KB2716429)
</td>
<td style="border:1px solid black;">
[Microsoft SQL Server 2005 para sistemas baseados em x64 Service Pack 4](http://www.microsoft.com/downloads/details.aspx?familyid=16cc7b80-ea4c-4b17-9ac2-250b771a569a)\[***1\]***
(KB2716427)
</td>
<td style="border:1px solid black;">
Elevação de privilégio
</td>
<td style="border:1px solid black;">
Importante
</td>
<td style="border:1px solid black;">
KB2494120 e KB2546869, no [MS11-049](http://technet.microsoft.com/pt-br/security/bulletin/ms11-049), substituídos pelo boletim KB2716429
KB2494123 no [MS11-049](http://technet.microsoft.com/pt-br/security/bulletin/ms11-049) substituído pelo boletim KB2716427
</td>
</tr>
<tr>
<td style="border:1px solid black;">
[Microsoft SQL Server 2005 para sistemas baseados em Itanium Service Pack](http://www.microsoft.com/downloads/details.aspx?familyid=623841cc-06f7-4475-b2c0-531aed9972a3)4<sup>[1]</sup>
(KB2716429)
</td>
<td style="border:1px solid black;">
[Microsoft SQL Server 2005 para sistemas baseados em Itanium Service Pack](http://www.microsoft.com/downloads/details.aspx?familyid=16cc7b80-ea4c-4b17-9ac2-250b771a569a)4<sup>[1]</sup>
(KB2716427)
</td>
<td style="border:1px solid black;">
Elevação de privilégio
</td>
<td style="border:1px solid black;">
Importante
</td>
<td style="border:1px solid black;">
KB2494120 e KB2546869, no [MS11-049](http://technet.microsoft.com/pt-br/security/bulletin/ms11-049), substituídos pelo boletim KB2716429
KB2494123 no [MS11-049](http://technet.microsoft.com/pt-br/security/bulletin/ms11-049) substituído pelo boletim KB2716427
</td>
</tr>
<tr>
<th style="border:1px solid black;" colspan="5">
SQL Server 2008
</th>
</tr>
<tr class="alternateRow">
<td style="border:1px solid black;">
[Microsoft SQL Server 2008 para sistemas de 32 bits Service Pack 2](http://www.microsoft.com/downloads/details.aspx?familyid=1bf8dc30-2a90-4196-814c-717ccd74ea13)<sup>[1]</sup>
(KB2716434)
</td>
<td style="border:1px solid black;">
[Microsoft SQL Server 2008 para sistemas de 32 bits Service Pack 2](http://www.microsoft.com/downloads/details.aspx?familyid=7d8b1b25-45ad-4f19-ba50-e77debf2b463)<sup>[1]</sup>
(KB2716433)
</td>
<td style="border:1px solid black;">
Elevação de privilégio
</td>
<td style="border:1px solid black;">
Importante
</td>
<td style="border:1px solid black;">
KB2494089 no [MS11-049](http://technet.microsoft.com/pt-br/security/bulletin/ms11-049) substituído pelo boletim KB2716434
KB2494094 no [MS11-049](http://technet.microsoft.com/pt-br/security/bulletin/ms11-049) substituído pelo boletim KB2716433
</td>
</tr>
<tr>
<td style="border:1px solid black;">
[Microsoft SQL Server 2008 para sistemas de 32 bits Service Pack 3](http://www.microsoft.com/downloads/details.aspx?familyid=04621a83-c2e2-4a60-9198-10104372b120)<sup>[1]</sup>
(KB2716436)
</td>
<td style="border:1px solid black;">
[Microsoft SQL Server 2008 para sistemas de 32 bits Service Pack 3](http://www.microsoft.com/downloads/details.aspx?familyid=4c4597d2-dea0-49b9-a5a9-a7771a3d64c0)<sup>[1]</sup>
(KB2716435)
</td>
<td style="border:1px solid black;">
Elevação de privilégio
</td>
<td style="border:1px solid black;">
Importante
</td>
<td style="border:1px solid black;">
Nenhuma
</td>
</tr>
<tr class="alternateRow">
<td style="border:1px solid black;">
[Microsoft SQL Server 2008 para sistemas baseados em x64 Service Pack 2](http://www.microsoft.com/downloads/details.aspx?familyid=1bf8dc30-2a90-4196-814c-717ccd74ea13)<sup>[1]</sup>
(KB2716434)
</td>
<td style="border:1px solid black;">
[Microsoft SQL Server 2008 para sistemas baseados em x64 Service Pack 2](http://www.microsoft.com/downloads/details.aspx?familyid=7d8b1b25-45ad-4f19-ba50-e77debf2b463)<sup>[1]</sup>
(KB2716433)
</td>
<td style="border:1px solid black;">
Elevação de privilégio
</td>
<td style="border:1px solid black;">
Importante
</td>
<td style="border:1px solid black;">
KB2494089 no [MS11-049](http://technet.microsoft.com/pt-br/security/bulletin/ms11-049) substituído pelo boletim KB2716434
KB2494094 no [MS11-049](http://technet.microsoft.com/pt-br/security/bulletin/ms11-049) substituído pelo boletim KB2716433
</td>
</tr>
<tr>
<td style="border:1px solid black;">
[Microsoft SQL Server 2008 para sistemas baseados em x64 Service Pack 3](http://www.microsoft.com/downloads/details.aspx?familyid=04621a83-c2e2-4a60-9198-10104372b120)<sup>[1]</sup>
(KB2716436)
</td>
<td style="border:1px solid black;">
[Microsoft SQL Server 2008 para sistemas baseados em x64 Service Pack 3](http://www.microsoft.com/downloads/details.aspx?familyid=4c4597d2-dea0-49b9-a5a9-a7771a3d64c0)<sup>[1]</sup>
(KB2716435)
</td>
<td style="border:1px solid black;">
Elevação de privilégio
</td>
<td style="border:1px solid black;">
Importante
</td>
<td style="border:1px solid black;">
Nenhuma
</td>
</tr>
<tr class="alternateRow">
<td style="border:1px solid black;">
[Microsoft SQL Server 2008 para sistemas baseados em Itanium Service Pack 2](http://www.microsoft.com/downloads/details.aspx?familyid=1bf8dc30-2a90-4196-814c-717ccd74ea13)<sup>[1]</sup>
(KB2716434)
</td>
<td style="border:1px solid black;">
[Microsoft SQL Server 2008 para sistemas baseados em Itanium Service Pack 2](http://www.microsoft.com/downloads/details.aspx?familyid=7d8b1b25-45ad-4f19-ba50-e77debf2b463)<sup>[1]</sup>
(KB2716433)
</td>
<td style="border:1px solid black;">
Elevação de privilégio
</td>
<td style="border:1px solid black;">
Importante
</td>
<td style="border:1px solid black;">
KB2494089 no [MS11-049](http://technet.microsoft.com/pt-br/security/bulletin/ms11-049) substituído pelo boletim KB2716434
KB2494094 no [MS11-049](http://technet.microsoft.com/pt-br/security/bulletin/ms11-049) substituído pelo boletim KB2716433
</td>
</tr>
<tr>
<td style="border:1px solid black;">
[Microsoft SQL Server 2008 para sistemas baseados em Itanium Service Pack 3](http://www.microsoft.com/downloads/details.aspx?familyid=04621a83-c2e2-4a60-9198-10104372b120)<sup>[1]</sup>
(KB2716436)
</td>
<td style="border:1px solid black;">
[Microsoft SQL Server 2008 para sistemas baseados em Itanium Service Pack 3](http://www.microsoft.com/downloads/details.aspx?familyid=4c4597d2-dea0-49b9-a5a9-a7771a3d64c0)<sup>[1]</sup>
(KB2716435)
</td>
<td style="border:1px solid black;">
Elevação de privilégio
</td>
<td style="border:1px solid black;">
Importante
</td>
<td style="border:1px solid black;">
Nenhuma
</td>
</tr>
<tr>
<th style="border:1px solid black;" colspan="5">
SQL Server 2008 R2
</th>
</tr>
<tr class="alternateRow">
<td style="border:1px solid black;">
[Microsoft SQL Server 2008 R2 para sistemas de 32 bits Service Pack 1](http://www.microsoft.com/downloads/details.aspx?familyid=215a9184-71c5-41e6-b4d5-03602182a88f)<sup>[1]</sup>
(KB2716440)
</td>
<td style="border:1px solid black;">
[Microsoft SQL Server 2008 R2 para sistemas de 32 bits Service Pack 1](http://www.microsoft.com/downloads/details.aspx?familyid=cdc4fc03-dfba-41d4-b651-d7967a067eea)<sup>[1]</sup>
(KB2716439)
</td>
<td style="border:1px solid black;">
Elevação de privilégio
</td>
<td style="border:1px solid black;">
Importante
</td>
<td style="border:1px solid black;">
Nenhuma
</td>
</tr>
<tr>
<td style="border:1px solid black;">
[Microsoft SQL Server 2008 R2 para sistemas baseados em x64 Service Pack 1](http://www.microsoft.com/downloads/details.aspx?familyid=215a9184-71c5-41e6-b4d5-03602182a88f)<sup>[1]</sup>
(KB2716440)
</td>
<td style="border:1px solid black;">
[Microsoft SQL Server 2008 R2 para sistemas baseados em x64 Service Pack 1](http://www.microsoft.com/downloads/details.aspx?familyid=cdc4fc03-dfba-41d4-b651-d7967a067eea)<sup>[1]</sup>
(KB2716439)
</td>
<td style="border:1px solid black;">
Elevação de privilégio
</td>
<td style="border:1px solid black;">
Importante
</td>
<td style="border:1px solid black;">
Nenhuma
</td>
</tr>
<tr class="alternateRow">
<td style="border:1px solid black;">
[Microsoft SQL Server 2008 R2 para sistemas baseados em Itanium Service Pack 1](http://www.microsoft.com/downloads/details.aspx?familyid=215a9184-71c5-41e6-b4d5-03602182a88f)<sup>[1]</sup>
(KB2716440)
</td>
<td style="border:1px solid black;">
[Microsoft SQL Server 2008 R2 para sistemas baseados em Itanium Service Pack 1](http://www.microsoft.com/downloads/details.aspx?familyid=cdc4fc03-dfba-41d4-b651-d7967a067eea)<sup>[1]</sup>
(KB2716439)
</td>
<td style="border:1px solid black;">
Elevação de privilégio
</td>
<td style="border:1px solid black;">
Importante
</td>
<td style="border:1px solid black;">
Nenhuma
</td>
</tr>
<tr>
<th style="border:1px solid black;" colspan="5">
SQL Server 2012
</th>
</tr>
<tr>
<td style="border:1px solid black;">
[Microsoft SQL Server 2012 para sistemas de 32 bits](http://www.microsoft.com/downloads/details.aspx?familyid=e79b4e5b-1549-4e76-afef-b771b432365b)<sup>[1]</sup>
(KB2716442)
</td>
<td style="border:1px solid black;">
[Microsoft SQL Server 2012 para sistemas de 32 bits](http://www.microsoft.com/downloads/details.aspx?familyid=ebfcb341-e240-4107-92f1-ab75cc28151a)<sup>[1]</sup>
(KB2716441)
</td>
<td style="border:1px solid black;">
Elevação de privilégio
</td>
<td style="border:1px solid black;">
Importante
</td>
<td style="border:1px solid black;">
Nenhuma
</td>
</tr>
<tr class="alternateRow">
<td style="border:1px solid black;">
[Microsoft SQL Server 2012 para sistemas x64](http://www.microsoft.com/downloads/details.aspx?familyid=e79b4e5b-1549-4e76-afef-b771b432365b)<sup>[1]</sup>
(KB2716442)\*
</td>
<td style="border:1px solid black;">
[Microsoft SQL Server 2012 para sistemas x64](http://www.microsoft.com/downloads/details.aspx?familyid=ebfcb341-e240-4107-92f1-ab75cc28151a)<sup>[1]</sup>
(KB2716441)
</td>
<td style="border:1px solid black;">
Elevação de privilégio
</td>
<td style="border:1px solid black;">
Importante
</td>
<td style="border:1px solid black;">
Nenhuma
</td>
</tr>
</table>
<sup>[1]</sup>Esta atualização somente é oferecida a clientes que executam o SQL Server Reporting Services (SSRS).
**Softwaresnãoafetados**
| Software Microsoft SQL Server |
|-------------------------------------------------------------------------------------------------|
| Microsoft SQL Server 2000 Service Pack 4 |
| Microsoft SQL Server 2000 Itanium Edition Service Pack 4 |
| Microsoft SQL Server 2000 Analysis Services Service Pack 4 |
| Microsoft SQL Server 2000 Desktop Engine (MSDE) no Microsoft Windows Server 2003 Service Pack 2 |
| Microsoft SQL Server 2000 Desktop Engine (MSDE 2000) Service Pack 4 |
| Microsoft SQL Server 2005 Express Edition Service Pack 4 |
| Microsoft SQL Server Management Studio Express (SSMSE) 2005 |
| Microsoft SQL Server 2008 R2 para sistemas de 32 bits Service Pack 2 |
| Microsoft SQL Server 2008 R2 para sistemas baseados em x64 Service Pack 2 |
| Microsoft SQL Server 2008 R2 para sistemas baseados em Itanium Service Pack 2 |
| Microsoft Data Engine (MSDE) 1.0 |
| Microsoft Data Engine (MSDE) 1.0 Service Pack 4 |
| Microsoft Data Engine 1.0 |
Perguntas frequentes relacionadas a esta atualização de segurança
-----------------------------------------------------------------
**Onde estão os detalhes das informações sobre o arquivo?**
Consulte as tabelas de referência na seção **Implantação de atualização de segurança** para o local dos detalhes de informações sobre o arquivo.
**On de** estão os hashes das atualizações de segurança?
Os hashes SHA1 e SHA2 das atualizações de segurança podem ser usados para verificar a autenticidade de pacotes de atualização de segurança baixados. Para informações sobre hashes pertencentes a esta atualização, consulte [artigo 2754849 (em inglês) da Microsoft Knowledge Base](http://support.microsoft.com/kb/2754849).
**Há tanto atualizações GDR quantoQFE para a minha versão do SQL. Como sei qual atualização devo usar?**
Primeiro, determine o número da versão de seu SQL Server. Para obter mais informações sobre como determinar o número da versão do SQL Server, consulte o [artigo 321185 da Microsoft Knowledge Base](http://support.microsoft.com/kb/321185).
Segundo, na tabela abaixo, localize o intervalo de versões a que o número de versão de seu SQL Server pertence. A atualização correspondente é a que você precisa instalar.
**Observação** Se o número da sua versão do SQL Server não pertence a nenhum dos intervalos na tabela a seguir, não há mais suporte para sua versão do SQL Server. Atualize para o Service Pack ou produto SQL Server mais recente para aplicar esta e futuras atualizações de segurança.
Para o SQL Server 2000:
<p> </p>
<table style="border:1px solid black;">
<caption>
Intervalo de versões do SQL Server
</caption>
<tr>
<td style="border:1px solid black;">
</td>
<td style="border:1px solid black;">
**8.0.1038.0-8.0.1076.0**
</td>
</tr>
<tr>
<th style="border:1px solid black;" colspan="2">
Atualização do SQL Server
</th>
</tr>
<tr class="alternateRow">
<td style="border:1px solid black;">
Não Aplicável
</td>
<td style="border:1px solid black;">
Microsoft SQL Server 2000 Reporting Services Service Pack 2
(KB983814)
</td>
</tr>
</table>
Para SQL Server 2005:
<p> </p>
<table style="border:1px solid black;">
<caption>
Intervalo de versões do SQL Server
</caption>
<tr>
<td style="border:1px solid black;">
**9.0.5000-9.0.5068**
</td>
<td style="border:1px solid black;">
**9.0.5200-9.0.5323**
</td>
</tr>
<tr>
<th style="border:1px solid black;" colspan="2">
Atualização do SQL Server
</th>
</tr>
<tr class="alternateRow">
<td style="border:1px solid black;">
SQL Server 2005 Service Pack 4 GDR
(KB2716429)
</td>
<td style="border:1px solid black;">
SQL Server 2005 Service Pack 4 QFE
(KB2716427)
</td>
</tr>
</table>
Para SQL Server 2008:
<p> </p>
<table style="border:1px solid black;">
<caption>
Intervalo de versões do SQL Server
</caption>
<tr>
<td style="border:1px solid black;">
**10.00.4000-10.00.4066**
</td>
<td style="border:1px solid black;">
**10.00.4260-10.00.4370**
</td>
<td style="border:1px solid black;">
**10.00.5500-10.00.5511**
</td>
<td style="border:1px solid black;">
**10.00.5750-10.00.5825**
</td>
</tr>
<tr>
<th style="border:1px solid black;" colspan="4">
Atualização do SQL Server
</th>
</tr>
<tr class="alternateRow">
<td style="border:1px solid black;">
SQL Server 2008 Service Pack 2 GDR
(KB2716434)
</td>
<td style="border:1px solid black;">
SQL Server 2005 Service Pack 2 QFE
(KB2716433)
</td>
<td style="border:1px solid black;">
SQL Server 2008 Service Pack 3 GDR
(KB2716436)
</td>
<td style="border:1px solid black;">
SQL Server 2005 Service Pack 3 QFE
(KB2716435)
</td>
</tr>
</table>
Para SQL Server 2008 R2:
<p> </p>
<table style="border:1px solid black;">
<caption>
Intervalo de versões do SQL Server
</caption>
<tr>
<td style="border:1px solid black;">
**10. 50.2500-10.50.2549**
</td>
<td style="border:1px solid black;">
**10.50.2750- 10.50.2860**
</td>
</tr>
<tr>
<th style="border:1px solid black;" colspan="2">
Atualização do SQL Server
</th>
</tr>
<tr class="alternateRow">
<td style="border:1px solid black;">
SQL Server 2008 R2 Service Pack 1 GDR
(KB2716440)
</td>
<td style="border:1px solid black;">
SQL Server 2008 R2 Service Pack 1 QFE
(KB2716439)
</td>
</tr>
</table>
Para SQL Server 2012:
<p> </p>
<table style="border:1px solid black;">
<caption>
Intervalo de versões do SQL Server
</caption>
<tr>
<td style="border:1px solid black;">
**11.0.2100- 11.0.2217**
</td>
<td style="border:1px solid black;">
**11.0.2300-11.0.2375**
</td>
</tr>
<tr>
<th style="border:1px solid black;" colspan="2">
Atualização do SQL Server
</th>
</tr>
<tr class="alternateRow">
<td style="border:1px solid black;">
SQL Server 2012GDR
(KB2716442)
</td>
<td style="border:1px solid black;">
SQL Server 2012 QFE
(KB2716441)
</td>
</tr>
</table>
Para obter instruções adicionais de instalação, consulte a subseção Informações de atualização de segurança para sua edição do SQL Server na seção **Informações da atualização**.
**A atualização também será oferecida para clusters do SQL Server?**
Sim. A atualização também será oferecida às instâncias do SQL Server 2005, SQL Server 2008, SQL Server 2008 R2 e SQL Server 2012 com cluster. As atualizações para clusters do SQL Server exigirão a interação do usuário. O SQL Server 2000 Reporting Services não aceita clusters do SQL Server.
Se o cluster do SQL Server 2005, SQL Server 2008, SQL Server 2008 R2 ou SQL Server 2012 tiver um nó passivo, a Microsoft recomenda que você faça a varredura e aplique a atualização primeiro ao nó ativo e depois faça o mesmo ao nó passivo. Quando todos os componentes tiverem sido atualizados no nó passivo, a atualização não será mais oferecida.
**As tabelas de referência do SQL Server 2000Reporting Services na seção Informações de Atualização de Segurança indicam que algumas atualizações podem exigir uma reinicialização. Como posso saber se a minha atualização precisará de uma reinicialização?**
Para SQL Server 2000 Reporting Services, é possível ter serviços dependentes. Os serviços dependentes não devem ser reiniciados depois que o serviço do qual eles dependem for interrompido e reiniciado. Por esse motivo, uma reinicialização deve ser executada após uma instalação bem-sucedida, a fim de garantir a inicialização dos serviços dependentes. Para obter mais informações sobre como determinar se você está executando serviços dependentes, consulte o [artigo 953741 (em inglês) da Microsoft Knowledge Base](http://support.microsoft.com/kb/953741).
**As atualizações serão aplicadas a instâncias desabilitadas doSQL Server 2005, SQL Server 2008, SQL Server 2008 R2 e SQL Server 2012?**
Não. Somente as instâncias do SQL Server 2005, SQL Server 2008, SQL Server 2008 R2 e SQL Server 2012 que não têm um tipo de inicialização **desabilitado** serão atualizadas pelo instalador. Para obter mais informações sobre serviços desabilitados, consulte o [Artigo 953740 (em inglês) da Microsoft Knowledge Base](http://support.microsoft.com/kb/953740).
**Uso uma versão mais antiga do software discutido neste boletim de segurança. O que devo fazer?**
Os softwares afetados listados neste boletim foram testados para determinar que versões são afetadas. Outras versões passaram seu ciclo de vida de suporte. Para obter mais informações sobre o ciclo de vida do produto, visite o site [Ciclo de vida do suporte Microsoft](http://go.microsoft.com/fwlink/?linkid=21742).
Os clientes que possuem versões anteriores do software devem priorizar a migração para as versões com suporte, a fim de evitar uma possível exposição a vulnerabilidades. Para determinar o ciclo de vida do suporte para sua versão de software, consulte [Selecione um Produto para Obter Informações do Ciclo de Vida](http://go.microsoft.com/fwlink/?linkid=169555). Para obter mais informações sobre service packs para essas versões de software, consulte [Política de Suporte do Ciclo de Vida do Service Pack](http://go.microsoft.com/fwlink/?linkid=89213).
Os clientes que precisarem de suporte adicional para software mais antigo deverão entrar em contato com o representante da equipe de contas da Microsoft, o gerente técnico da conta ou o representante do parceiro Microsoft apropriado para obter opções de suporte personalizadas. Os clientes sem um contrato Alliance, Premier ou Authorized podem entrar em contato com o escritório de vendas local da Microsoft. Para obter informações de contato, visite o site de [Informações internacionais da Microsoft](http://go.microsoft.com/fwlink/?linkid=33329), selecione o país na lista de informações de contato e, em seguida, clique em **Ir** para ver uma lista de telefones. Ao ligar, peça para falar com o gerente de vendas local de Suporte Premier. Para obter mais informações, consulte as [Perguntas Frequentes sobre a Política do Ciclo de Vida do Suporte da Microsoft](http://go.microsoft.com/fwlink/?linkid=169557).
### **Informações sobre a vulnerabilidade**
Classificação de gravidade e Identificadores de vulnerabilidade
---------------------------------------------------------------
As classificações de gravidade a seguir pressupõem o impacto máximo possível da vulnerabilidade. Para obter informações referentes à probabilidade de exploração da vulnerabilidade em relação à sua classificação de gravidade e ao impacto à segurança, em até 30 dias a partir do lançamento deste boletim de segurança, consulte o Índice de exploração no [resumo de boletins de outubro](http://technet.microsoft.com/pt-br/security/bulletin/ms12-oct). Para obter mais informações, consulte o [Índice de exploração da Microsoft](http://technet.microsoft.com/pt-br/security/cc998259.aspx).
<p> </p>
<table style="border:1px solid black;">
<caption>
A Classificação de gravidade de vulnerabilidade e Impacto máximo de segurança por software afetado
</caption>
<tr class="thead">
<th style="border:1px solid black;" >
Softwares afetados
</th>
<th style="border:1px solid black;" >
Vulnerabilidade de XSS refletida - CVE-2012-2552
</th>
<th style="border:1px solid black;" >
Avaliação de gravidade agregada
</th>
</tr>
<tr>
<th style="border:1px solid black;" colspan="3">
SQL Server 2000
</th>
</tr>
<tr>
<td style="border:1px solid black;">
Microsoft SQL Server 2000 Reporting Services Service Pack 2
</td>
<td style="border:1px solid black;">
**Importante**
Elevação de privilégio
</td>
<td style="border:1px solid black;">
**Importante**
</td>
</tr>
<tr>
<th style="border:1px solid black;" colspan="3">
SQL Server 2005
</th>
</tr>
<tr class="alternateRow">
<td style="border:1px solid black;">
Microsoft SQL Server 2005 Express Edition com Advanced Services Service Pack 4
</td>
<td style="border:1px solid black;">
**Importante**
Elevação de privilégio
</td>
<td style="border:1px solid black;">
**Importante**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Microsoft SQL Server 2005 para sistemas de 32 bits Service Pack 4
</td>
<td style="border:1px solid black;">
**Importante**
Elevação de privilégio
</td>
<td style="border:1px solid black;">
**Importante**
</td>
</tr>
<tr class="alternateRow">
<td style="border:1px solid black;">
Microsoft SQL Server 2005 para sistemas baseados em x64 Service Pack 4
</td>
<td style="border:1px solid black;">
**Importante**
Elevação de privilégio
</td>
<td style="border:1px solid black;">
**Importante**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Microsoft SQL Server 2005 para sistemas baseados em Itanium Service Pack 4
</td>
<td style="border:1px solid black;">
**Importante**
Elevação de privilégio
</td>
<td style="border:1px solid black;">
**Importante**
</td>
</tr>
<tr>
<th style="border:1px solid black;" colspan="3">
SQL Server 2008
</th>
</tr>
<tr class="alternateRow">
<td style="border:1px solid black;">
Microsoft SQL Server 2008 para sistemas de 32 bits Service Pack 2
</td>
<td style="border:1px solid black;">
**Importante**
Elevação de privilégio
</td>
<td style="border:1px solid black;">
**Importante**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Microsoft SQL Server 2008 para sistemas de 32 bits Service Pack 3
</td>
<td style="border:1px solid black;">
**Importante**
Elevação de privilégio
</td>
<td style="border:1px solid black;">
**Importante**
</td>
</tr>
<tr class="alternateRow">
<td style="border:1px solid black;">
Microsoft SQL Server 2008 para sistemas baseados em x64 Service Pack 2
</td>
<td style="border:1px solid black;">
**Importante**
Elevação de privilégio
</td>
<td style="border:1px solid black;">
**Importante**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Microsoft SQL Server 2008 para sistemas baseados em x64 Service Pack 3
</td>
<td style="border:1px solid black;">
**Importante**
Elevação de privilégio
</td>
<td style="border:1px solid black;">
**Importante**
</td>
</tr>
<tr class="alternateRow">
<td style="border:1px solid black;">
Microsoft SQL Server 2008 para sistemas baseados em Itanium Service Pack 2
</td>
<td style="border:1px solid black;">
**Importante**
Elevação de privilégio
</td>
<td style="border:1px solid black;">
**Importante**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Microsoft SQL Server 2008 para sistemas baseados em Itanium Service Pack 3
</td>
<td style="border:1px solid black;">
**Importante**
Elevação de privilégio
</td>
<td style="border:1px solid black;">
**Importante**
</td>
</tr>
<tr>
<th style="border:1px solid black;" colspan="3">
SQL Server 2008 R2
</th>
</tr>
<tr class="alternateRow">
<td style="border:1px solid black;">
Microsoft SQL Server 2008 R2 para sistemas de 32 bits Service Pack 1
</td>
<td style="border:1px solid black;">
**Importante**
Elevação de privilégio
</td>
<td style="border:1px solid black;">
**Importante**
</td>
</tr>
<tr>
<td style="border:1px solid black;">
Microsoft SQL Server 2008 R2 para sistemas baseados em Itanium Service Pack 1
</td>
<td style="border:1px solid black;">
**Importante**
Elevação de privilégio
</td>
<td style="border:1px solid black;">
**Importante**
</td>
</tr>
<tr class="alternateRow">
<td style="border:1px solid black;">
Microsoft SQL Server 2008 R2 para sistemas baseados em x64 Service Pack 1
</td>
<td style="border:1px solid black;">
**Importante**
Elevação de privilégio
</td>
<td style="border:1px solid black;">
**Importante**
</td>
</tr>
<tr>
<th style="border:1px solid black;" colspan="3">
SQL Server 2012
</th>
</tr>
<tr>
<td style="border:1px solid black;">
Microsoft SQL Server 2012 para sistemas de 32 bits
</td>
<td style="border:1px solid black;">
**Importante**
Elevação de privilégio
</td>
<td style="border:1px solid black;">
**Importante**
</td>
</tr>
<tr class="alternateRow">
<td style="border:1px solid black;">
Microsoft SQL Server 2012 para sistemas baseados em x64
</td>
<td style="border:1px solid black;">
**Importante**
Elevação de privilégio
</td>
<td style="border:1px solid black;">
**Importante**
</td>
</tr>
</table>
Vulnerabilidade de XSS refletida - CVE-2012-2552
------------------------------------------------
Uma vulnerabilidade refletida no XSS existe no SQL Server Report Manager e pode permitir que um invasor injete um script do lado cliente na instância do usuário do Internet Explorer. O script poderia falsificar conteúdo, divulgar informações ou realizar todas as ações que o usuário pode realizar no site afetado, em nome do usuário visado.
Para exibir esta vulnerabilidade como uma entrada padrão na lista Common Vulnerabilities and Exposures, consulte [CVE-2012-2552](http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=cve-2012-2552).
#### Fatores atenuantes para Vulnerabilidade de XSS refletida - CVE-2012-2552
A atenuação refere-se a uma configuração, configuração comum ou prática recomendada geral, existindo num estado padrão, que possa reduzir a gravidade de exploração de uma vulnerabilidade. Os fatores de atenuação a seguir podem ser úteis em sua situação:
- Em um cenário de ataque baseado na Web, o invasor pode hospedar um site que contenha uma página da Web usada para explorar essa vulnerabilidade. Além disso, sites comprometidos e sites que aceitem ou hospedem conteúdo fornecido pelo usuário ou anúncios podem conter conteúdo especialmente criado que pode explorar esta vulnerabilidade. Em todos os casos, entretanto, o invasor não tem como forçar os usuários a visitar esses sites. Em vez disso, o invasor teria que convencer os usuários a visitar o site, geralmente fazendo com que eles cliquem em um link em um e-mail ou mensagem do Instant Messenger que leva o usuário ao site do invasor.
- O Filtro de XSS no Internet Explorer 8, 9 e 10 evita este ataque a usuários do Internet Explorer 8, 9 e 10 ao procurar um site na zona da Internet. O Filtro de XSS no Internet Explorer 8, Internet Explorer 9 e Internet Explorer 10 é ativado por padrão na zona da Internet, mas não é ativado por padrão na Zona da Intranet.
#### Soluções alternativas para Vulnerabilidade de XSS refletida - CVE-2012-2552
A solução alternativa refere-se a uma configuração ou alteração de configuração que não corrige a vulnerabilidade subjacente mas que ajudaria a bloquear vetores de ataque conhecidos antes de aplicar a atualização. A Microsoft testou as soluções alternativas e estados a seguir como parte do cenário que implica se uma solução alternativa reduziria funcionalidade:
- **Habilite o filtro de XSS do Internet Explorer 8, Internet Explorer 9 e Internet Explorer 10 XSS na zona da Intranet**
Você pode ajudar a impedir a exploração desta vulnerabilidade alterando suas configurações para permitir o filtro XSS na zona de segurança da Intranet local. (O filtro XSS é ativado por padrão na zona de segurança da Internet.) Para isso, execute as seguintes etapas:
1. No Internet Explorer 8, 9 ou 10, clique em **Opções da Internet** no menu **Ferramentas**.
2. Clique na guia **Segurança**.
3. Clique em **Intranet local** e, em seguida, clique em **Nível personalizado**.
4. Em **Configurações**, na seção **Scripts**, sob **Habilitar filtro XSS**, clique **Habilitar** e, em seguida, clique em **OK**.
5. Clique em **OK** duas vezes para retornar ao Internet Explorer.
**Impacto da solução alternativa**. Sites internos não sinalizados anteriormente como riscos de XSS poderiam ser sinalizados.
**Como desfazer a solução alternativa**.
Para desfazer esta solução alternativa, execute as seguintes etapas.
1. No Internet Explorer 8, 9 ou 10, clique em **Opções da Internet** no menu **Ferramentas**.
2. Clique na guia **Segurança**.
3. Clique em **Intranet local** e, em seguida, clique em **Nível personalizado**.
4. Em **Configurações**, na seção **Scripts** em **Habilitar Filtro de XSS**, clique em **Desabilitar** e, em seguida, clique em **OK**.
5. Clique em **OK** duas vezes para retornar ao Internet Explorer.
#### Perguntas frequentes sobre a Vulnerabilidade de XSS refletida - CVE-2012-2552
**Qual é o escopo da vulnerabilidade?**
É uma vulnerabilidade de XSS refletida que poderia permitir uma elevação de privilégio.
**O que provoca a vulnerabilidade?**
A vulnerabilidade é causada quando o SQL Server Report Manager não valida adequadamente um parâmetro de solicitação no site do SQL Server Report Manager.
**O que é scriptentre sites (XSS)?**
O Script entre sites (XSS) é uma vulnerabilidade de classe de segurança que pode permitir que um invasor injete scripts na resposta a uma solicitação de página da Web. Este script é executado pelo aplicativo solicitante, geralmente um navegador da Web. O script pode falsificar conteúdo, divulgar informações ou efetuar todas as ações que o usuário pode realizar no site afetado, em nome do usuário visado.
**Para que um invasor pode usar a vulnerabilidade?**
Um invasor que explorar a vulnerabilidade com êxito poderá injetar um script do lado do cliente na instância do Internet Explorer do usuário. O script poderia falsificar conteúdo, divulgar informações ou realizar todas as ações que o usuário pode realizar no site afetado, em nome do usuário visado.
**De que forma o invasor pode explorar avulnerabilidade?**
O invasor pode explorar a vulnerabilidade enviando um link especialmente criado ao usuário e convencendo-o a clicar no link. O invasor também pode hospedar um site que contém uma página da Web projetada para explorar essa vulnerabilidade. Além disso, sites comprometidos e sites que aceitem ou hospedem conteúdo fornecido pelo usuário ou anúncios podem conter conteúdo especialmente criado que pode explorar esta vulnerabilidade.
**Quais são os principais sistemas que correm riscos com a vulnerabilidade?**
Os servidores que executam edições afetadas do Microsoft SQL Server são os que mais correm risco. Os sistemas de SQL Server que não têm o SQL Server Reporting Services instalado não estão em risco com esta vulnerabilidade e não receberão a atualização.
**O que a atualização faz?**
A atualização elimina a vulnerabilidade, corrigindo a maneira como o SQL Server Report Manager valida os parâmetros de entrada.
**Quando esse boletim de segurança foi lançado, essa vulnerabilidade já tinha sido divulgada publicamente?**
Não. A Microsoft recebeu informações sobre esta vulnerabilidade por meio da divulgação coordenada de vulnerabilidades.
**Quando este boletim de segurança foi lançado, a Microsoft tinha recebido algum relatório informando que essa vulnerabilidade estava sendo explorada?**
Não. A Microsoft não recebeu nenhuma informação indicando que essa vulnerabilidade tinha sido usada publicamente para atacar clientes quando este boletim de segurança foi lançado pela primeira vez.
### Informações da atualização
Orientação e ferramentas de detecção e implantação
--------------------------------------------------
**Central de Segurança**
Gerencie as atualizações de software e segurança que você precisa instalar em servidores, computadores desktop e notebooks em sua organização. Para obter mais informações, consulte o [Centro de Gerenciamento de Atualização do Technet](http://go.microsoft.com/fwlink/?linkid=69903). O site [Microsoft TechNet Security](http://go.microsoft.com/fwlink/?linkid=21132) fornece informações adicionais sobre segurança em produtos da Microsoft.
As atualizações de segurança estão disponíveis no [Microsoft Update](http://go.microsoft.com/fwlink/?linkid=40747) e no [Windows Update](http://go.microsoft.com/fwlink/?linkid=21130). As atualizações de segurança também estão disponíveis no [Centro de Download da Microsoft](http://go.microsoft.com/fwlink/?linkid=21129). Você poderá encontrá-las com mais facilidade executando uma pesquisa com a palavra-chave "atualização de segurança".
Por fim, as atualizações de segurança podem ser baixadas do [Microsoft Update Catalog](http://go.microsoft.com/fwlink/?linkid=96155). O Microsoft Update Catalog fornece um catálogo pesquisável de conteúdo disponibilizado por meio do Windows Update e Microsoft Update, incluindo atualizações de segurança, drivers e service packs. Ao pesquisar usando o número do boletim de segurança (como "MS12-001"), é possível adicionar todas as atualizações aplicáveis à sua cesta (incluindo idiomas diferentes para uma atualização) e baixá-las na pasta de sua escolha. Para obter mais informações sobre o Microsoft Update Catalog, consulte as [Perguntas Frequentes sobre Microsoft Update Catalog.](http://go.microsoft.com/fwlink/?linkid=97900)
**Orientação de detecção e implantação:**
A Microsoft oferece orientações de detecção e implantação de atualizações de segurança. Essas orientações contêm recomendações e informações que podem ajudar os profissionais de TI a entender como usar várias ferramentas para detecção e implantação de atualizações de segurança. Para obter mais informações, consulte o [Artigo 961747 (em inglês) da Microsoft Knowledge Base](http://support.microsoft.com/kb/961747).
**Microsoft Baseline Security Analyzer**
O MBSA (Microsoft Baseline Security Analyzer) permite aos administradores pesquisar, em sistemas locais e remotos, atualizações de segurança ausentes e problemas de configuração de segurança comuns. Para obter mais informações, consulte o [Microsoft Baseline Security Analyzer](http://go.microsoft.com/fwlink/?linkid=20567).
A tabela a seguir fornece o resumo de detecção do MBSA para esta atualização de segurança.
| Software | MBSA |
|--------------------------------------------------------------------------------|------|
| Microsoft SQL Server 2000 Reporting Services Service Pack 2 | Sim |
| Microsoft SQL Server 2005 Express Edition com Advanced Services Service Pack 4 | Sim |
| Microsoft SQL Server 2005 para sistemas de 32 bits Service Pack 4 | Sim |
| Microsoft SQL Server 2005 para sistemas baseados em x64 Service Pack 4 | Sim |
| Microsoft SQL Server 2005 para sistemas baseados em Itanium Service Pack 4 | Sim |
| Microsoft SQL Server 2008 para sistemas de 32 bits Service Pack 2 | Sim |
| Microsoft SQL Server 2008 para sistemas de 32 bits Service Pack 3 | Sim |
| Microsoft SQL Server 2008 para sistemas baseados em x64 Service Pack 2 | Sim |
| Microsoft SQL Server 2008 para sistemas baseados em x64 Service Pack 3 | Sim |
| Microsoft SQL Server 2008 para sistemas baseados em Itanium Service Pack 2 | Sim |
| Microsoft SQL Server 2008 para sistemas baseados em Itanium Service Pack 3 | Sim |
| Microsoft SQL Server 2008 R2 para sistemas de 32 bits Service Pack 1 | Sim |
| Microsoft SQL Server 2008 R2 para sistemas baseados em x64 Service Pack 1 | Sim |
| Microsoft SQL Server 2008 R2 para sistemas baseados em Itanium Service Pack 1 | Sim |
| Microsoft SQL Server 2012 para sistemas de 32 bits | Sim |
| Microsoft SQL Server 2012 para sistemas baseados em x64 | Sim |
**Observação** Para os clientes que usam software herdado sem suporte pela versão mais recente do MBSA, Microsoft Update e Windows Server Update Services: consulte o [Microsoft Baseline Security Analyzer](http://go.microsoft.com/fwlink/?linkid=20567) e consulte a seção Suporte ao produto herdado sobre como criar a detecção de atualização de segurança abrangente com ferramentas herdadas.
**Windows Server Update Services**
O WSUS (Windows Server Update Services) permite que administradores de tecnologia da informação implantem as mais recentes atualizações de produtos Microsoft em computadores que executem o sistema operacional Windows. Para obter mais informações sobre como implantar atualizações de segurança usando o recurso Windows Server Update Services, consulte o artigo da TechNet [Windows Server Update Services](http://technet.microsoft.com/wsus/default.aspx) (em inglês).
**Systems Management Server**
A tabela a seguir fornece o resumo de detecção de SMS para esta atualização de segurança.
| Software | SMS 2003 com ITMU | System Center Configuration Manager |
|--------------------------------------------------------------------------------|-------------------|-------------------------------------|
| Microsoft SQL Server 2000 Reporting Services Service Pack 2 | Sim | Sim |
| Microsoft SQL Server 2005 Express Edition com Advanced Services Service Pack 4 | Sim | Sim |
| Microsoft SQL Server 2005 para sistemas de 32 bits Service Pack 4 | Sim | Sim |
| Microsoft SQL Server 2005 para sistemas baseados em x64 Service Pack 4 | Sim | Sim |
| Microsoft SQL Server 2005 para sistemas baseados em Itanium Service Pack 4 | Sim | Sim |
| Microsoft SQL Server 2008 para sistemas de 32 bits Service Pack 2 | Sim | Sim |
| Microsoft SQL Server 2008 para sistemas de 32 bits Service Pack 3 | Sim | Sim |
| Microsoft SQL Server 2008 para sistemas baseados em x64 Service Pack 2 | Sim | Sim |
| Microsoft SQL Server 2008 para sistemas baseados em x64 Service Pack 3 | Sim | Sim |
| Microsoft SQL Server 2008 para sistemas baseados em Itanium Service Pack 2 | Sim | Sim |
| Microsoft SQL Server 2008 para sistemas baseados em Itanium Service Pack 3 | Sim | Sim |
| Microsoft SQL Server 2008 R2 para sistemas de 32 bits Service Pack 1 | Sim | Sim |
| Microsoft SQL Server 2008 R2 para sistemas baseados em x64 Service Pack 1 | Sim | Sim |
| Microsoft SQL Server 2008 R2 para sistemas baseados em Itanium Service Pack 1 | Sim | Sim |
| Microsoft SQL Server 2012 para sistemas de 32 bits | Sim | Sim |
| Microsoft SQL Server 2012 para sistemas baseados em x64 | Sim | Sim |
**Observação** a Microsoft descontinuou o suporte para SMS 2.0 em 12 de abril de 2011. Para SMS 2003, a Microsoft também descontinuou o suporte da Ferramenta de inventário de atualização de segurança (SUIT) em 12 de abril de 2011. Os clientes devem atualizar o [System Center Configuration Manager](http://technet.microsoft.com/systemcenter/bb980621). Para clientes que permanecem com SMS 2003 Service Pack 3, a [Ferramenta de inventário para atualizações da Microsoft](http://technet.microsoft.com/sms/bb676783.aspx) (ITMU) é também uma opção.
Para o SMS 2003, a ferramenta Inventário do SMS 2003 para Microsoft Updates pode ser usada pelo SMS para detectar as atualizações de segurança oferecidas pelo [Microsoft Update](http://update.microsoft.com/microsoftupdate) e que tenham suporte do [Windows Server Update Services](http://go.microsoft.com/fwlink/?linkid=50120). Para obter mais informações sobre a ITMU do SMS 2003, consulte [Inventory Tool do SMS 2003 para Microsoft Updates](http://technet.microsoft.com/sms/bb676783.aspx). Para obter mais informações sobre as ferramentas de varredura de SMS, consulte [SMS 2003 Software Update Scanning Tools](http://technet.microsoft.com/sms/bb676786.aspx). Consulte também [Downloads para Systems Management Server 2003.](http://technet.microsoft.com/sms/bb676766.aspx)
O System Center Configuration Manager usa WSUS 3.0 para detectar atualizações. Para obter mais informações, consulte o [System Center](http://technet.microsoft.com/systemcenter/bb980621).
Para obter mais informações, consulte o [Artigo 910723 (em inglês) da Microsoft Knowledge Base](http://support.microsoft.com/kb/910723). Lista de resumo de detecção mensal e os artigos de diretrizes de implantação.
**Avaliador de compatibilidade com atualizações e Kit de ferramentas de compatibilidade de aplicativos**
As atualizações frequentemente gravam nos mesmos arquivos e configurações do Registro necessários à execução dos aplicativos. Isto pode gerar incompatibilidades e aumentar o tempo necessário à implantação de atualizações de segurança. É possível usar os componentes do [Avaliador de compatibilidade com atualizações](http://technet.microsoft.com/library/cc749197) incluídos no [Kit de ferramentas de compatibilidade de aplicativos](http://www.microsoft.com/downloads/details.aspx?familyid=24da89e9-b581-47b0-b45e-492dd6da2971) para agilizar o teste e a validação de atualizações do Windows com relação aos aplicativos instalados.
O Application Compatibility Toolkit (ACT) contém as ferramentas e a documentação necessárias para avaliar e atenuar problemas de compatibilidade com aplicativos antes da implantação do Microsoft Windows Vista, de uma atualização do Windows, de uma atualização de segurança da Microsoft ou de uma nova versão do Windows Internet Explorer em seu ambiente.
Implantação de atualização de segurança
---------------------------------------
**Softwares afetados**
Para obter informações sobre uma atualização de segurança específica para seu software afetado, clique no link apropriado:
#### SQL Server 2000 Reporting Services
**Tabela de referência**
A tabela a seguir contém as informações de atualização de segurança desse software. Você pode encontrar informações adicionais na subseção **Informações de implantação**, nesta seção.
<p> </p>
<table style="border:1px solid black;">
<tbody>
<tr class="odd">
<td style="border:1px solid black;"><strong>Inclusão em Service Packs futuros</strong></td>
<td style="border:1px solid black;">Nenhum Service Pack futuro planejado</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"><strong>Implantação</strong></td>
<td style="border:1px solid black;"></td>
</tr>
<tr class="odd">
<td style="border:1px solid black;">Instalar sem intervenção do usuário</td>
<td style="border:1px solid black;">Para SQL Server 2000 Reporting Services Service Pack 2:<br />
SQL2000.RS-KB983814-v8.00.1077.00-ENG.exe /quiet</td>
</tr>
<tr class="even">
<td style="border:1px solid black;">Instalar sem reinicializar</td>
<td style="border:1px solid black;">Para SQL Server 2000 Reporting Services Service Pack 2:<br />
SQL2000.RS-KB983814-v8.00.1077.00-ENG.exe /norestart</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;">Instalando uma única instância</td>
<td style="border:1px solid black;">Para SQL Server 2000 Reporting Services Service Pack 2:<br />
SQL2000.RS-KB983814-v8.00.1077.00-ENG.exe /quiet /InstanceName={instance}</td>
</tr>
<tr class="even">
<td style="border:1px solid black;">Arquivo de log de atualização</td>
<td style="border:1px solid black;">SQL2000.RS-KB983814-v8.00.1077.00-<language>.log</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;">Mais informações</td>
<td style="border:1px solid black;">Consulte a subseção <strong>Orientação e ferramentas de detecção e implantação</strong></td>
</tr>
<tr class="even">
<td style="border:1px solid black;"><strong>Requisitos</strong> <strong>de</strong> <strong>reinicialização</strong></td>
<td style="border:1px solid black;"></td>
</tr>
<tr class="odd">
<td style="border:1px solid black;">Reinicialização necessária</td>
<td style="border:1px solid black;">Para SQL Server 2000 Reporting Services Service Pack 2:<br />
<br />
Recomendamos uma reinicialização após a instalação da atualização para que os serviços dependentes também sejam reinicializados. Para mais informações, consulte "Como posso saber se a minha atualização precisará de uma reinicialização?" na seção de perguntas frequentes de atualização deste boletim. Se uma reinicialização for necessária, o instalador a solicitará ou retornará o código de saída 3010.</td>
</tr>
<tr class="even">
<td style="border:1px solid black;">HotPatching</td>
<td style="border:1px solid black;">Não Aplicável</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"><strong>Informações sobre remoção</strong></td>
<td style="border:1px solid black;">Use a ferramenta <strong>Adicionar ou Remover Programas</strong> no Painel de controle.</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"><strong>Informaçõessobre</strong> <strong>o</strong> <strong>arquivo</strong></td>
<td style="border:1px solid black;">Consulte o <a href="http://support.microsoft.com/kb/983814">Artigo 983814 (em inglês) da Microsoft Knowledge Base</a></td>
</tr>
</tbody>
</table>
#### Informações de implantação
**Instalando a atualização**
Quando você instala esta atualização de segurança, o instalador verifica se alguns dos arquivos que estão sendo atualizados no computador foram anteriormente atualizados por um hotfix da Microsoft.
Para obter mais informações sobre a terminologia que aparece neste boletim, como *hotfix*, consulte o [Artigo 824684 (em inglês) da Microsoft Knowledge Base](http://support.microsoft.com/kb/824684).
Esta atualização de segurança oferece suporte às seguintes opções de instalação:
<p> </p>
<table style="border:1px solid black;">
<caption>
Opções de instalação da atualização de segurança para as quais há suporte
</caption>
<tr class="thead">
<th style="border:1px solid black;" >
Opção
</th>
<th style="border:1px solid black;" >
Descrição
</th>
</tr>
<tr>
<td style="border:1px solid black;">
**/help**
</td>
<td style="border:1px solid black;">
Exibe as opções de linha de comando
</td>
</tr>
<tr>
<th style="border:1px solid black;" colspan="2">
Modos de instalação
</th>
</tr>
<tr class="alternateRow">
<td style="border:1px solid black;">
**/passive**
</td>
<td style="border:1px solid black;">
Modo de instalação autônomo. Não é necessária a interação do usuário, mas o status da instalação é exibido. Se a reinicialização for necessária no fim da instalação, uma caixa de diálogo será apresentada para o usuário com um timer avisando que o computador será reiniciado em 30 segundos.
</td>
</tr>
<tr>
<td style="border:1px solid black;">
**/quiet**
</td>
<td style="border:1px solid black;">
Modo silencioso. O mesmo que modo autônomo, mas nenhuma mensagem de status ou de erro é exibida.
</td>
</tr>
<tr>
<th style="border:1px solid black;" colspan="2">
Opções de reinicialização
</th>
</tr>
<tr class="alternateRow">
<td style="border:1px solid black;">
**/norestart**
</td>
<td style="border:1px solid black;">
Não reinicia quando a instalação é concluída
</td>
</tr>
<tr>
<td style="border:1px solid black;">
**/forcerestart**
</td>
<td style="border:1px solid black;">
Reinicia o computador após a instalação e força o fechamento de outros aplicativos no desligamento sem antes salvar os arquivos abertos.
</td>
</tr>
<tr class="alternateRow">
<td style="border:1px solid black;">
**/warnrestart\[:x\]**
</td>
<td style="border:1px solid black;">
Apresenta uma caixa de diálogo com um timer avisando ao usuário que o computador será reiniciado em *x* segundos. (A configuração padrão é 30 segundos.) Destina-se ao uso com as opções **/quiet** ou **/passive**.
</td>
</tr>
<tr>
<td style="border:1px solid black;">
**/promptrestart**
</td>
<td style="border:1px solid black;">
Exibe uma caixa de diálogo solicitando que o usuário local permita a reinicialização
</td>
</tr>
<tr>
<th style="border:1px solid black;" colspan="2">
Opções especiais
</th>
</tr>
<tr class="alternateRow">
<td style="border:1px solid black;">
**/overwriteoem**
</td>
<td style="border:1px solid black;">
Sobrescreve arquivos OEM sem notificação
</td>
</tr>
<tr>
<td style="border:1px solid black;">
**/nobackup**
</td>
<td style="border:1px solid black;">
Não faz backup de arquivos necessários à desinstalação
</td>
</tr>
<tr class="alternateRow">
<td style="border:1px solid black;">
**/forceappsclose**
</td>
<td style="border:1px solid black;">
Força o encerramento de outros programas quando o computador é desligado
</td>
</tr>
<tr>
<td style="border:1px solid black;">
**/log:path**
</td>
<td style="border:1px solid black;">
Permite o redirecionamento dos arquivos de log da instalação
</td>
</tr>
<tr class="alternateRow">
<td style="border:1px solid black;">
**/integrate:path**
</td>
<td style="border:1px solid black;">
Integra a atualização nos arquivos-fonte do Windows. Esses arquivos se encontram no caminho especificado na opção.
</td>
</tr>
</table>
**Observação** É possível combinar essas opções em uma única linha de comando. Para obter compatibilidade com versões anteriores, a atualização de segurança também oferece suporte a várias opções de instalação utilizadas por versões anteriores do programa de instalação. Para obter mais informações sobre as opções de instalação suportadas, consulte o [Artigo 262841 (em inglês) da Microsoft Knowledge Base](http://support.microsoft.com/kb/262841).
**Removendo a atualização**
Use a ferramenta **Adicionar ou Remover Programas** no Painel de controle.
**Verificandoaaplicação da atualização**
- **Microsoft Baseline Security Analyzer**
Para verificar se uma atualização de segurança foi aplicada em um sistema afetado, é possível utilizar a ferramenta MBSA (Microsoft Baseline Security Analyzer). Consulte a seção **Orientação e ferramentas de detecção e implantação** neste boletim para obter mais informações.
- **Verificação de versão de arquivo**
Como existem várias versões do Microsoft Windows, as etapas a seguir podem ser diferentes no seu computador. Se isso acontecer, consulte a documentação do produto para completar estas etapas.
1. Clique em **Iniciar** e, em seguida, clique em **Pesquisar**.
2. No painel **Resultados da Pesquisa**, clique em **Todos os arquivos e pastas**, em **Search Companion**.
3. Na caixa **Todo ou parte do nome do arquivo** , digite um nome de arquivo da tabela de informações de arquivo correta e clique em **Pesquisar**.
4. Na lista de arquivos, clique com o botão direito do mouse em um nome de arquivo da tabela de informações de arquivo correta e clique em **Propriedades**.**Observação**
5. Na guia **Versão**, determine a versão do arquivo instalado no sistema, comparando-o com a versão documentada na tabela de informações de arquivos correta.**Observação**
#### SQL Server 2005 (todas as edições)
**Tabela de referência**
A tabela a seguir contém as informações de atualização de segurança desse software. Você pode encontrar informações adicionais na subseção **Informações de implantação**, nesta seção.
<p> </p>
<table style="border:1px solid black;">
<tbody>
<tr class="odd">
<td style="border:1px solid black;"><strong>Inclusão em Service Packs futuros</strong></td>
<td style="border:1px solid black;">Nenhum Service Pack futuro planejado</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"><strong>Implantação</strong></td>
<td style="border:1px solid black;"></td>
</tr>
<tr class="odd">
<td style="border:1px solid black;">Instalar sem intervenção do usuário</td>
<td style="border:1px solid black;">Para atualização do GDR do SQL Server 2005 Express Edition com Advanced Services Service Pack 4:<br />
SQLServer2005-KB2716429-x86-ENU.exe /quiet /allinstances</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização do GDR do SQL Server 2005 para sistemas de 32 bits Service Pack 4:<br />
SQLServer2005-KB2716429-x86-ENU.exe /quiet /allinstances</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização do GDR do SQL Server 2005 para sistemas x64 Service Pack 4:<br />
SQLServer2005-KB2716429-x64-ENU.exe /quiet /allinstances</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização do GDR do SQL Server 2005 para sistemas Itanium Service Pack 4:<br />
SQLServer2005-KB2716429-IA64-ENU.exe /quiet /allinstances</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização do QFE do SQL Server 2005 Express Edition com Advanced Services Service Pack 4:<br />
SQLServer2005-KB2716427-x86-ENU.exe /quiet /allinstances</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização do QFE do SQL Server 2005 para sistemas de 32 bits Service Pack 4:<br />
SQLServer2005-KB2716427-x86-ENU.exe /quiet /allinstances</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização do QFE do SQL Server 2005 para sistemas x64 Service Pack 4:<br />
SQLServer2005-KB2716427-x64-ENU.exe /quiet /allinstances</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização do QFE do SQL Server 2005 para sistemas Itanium Service Pack 4:<br />
SQLServer2005-KB2716427-IA64-ENU.exe /quiet /allinstances</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;">Instalando uma única instância</td>
<td style="border:1px solid black;">Para atualização do GDR do SQL Server 2005 Express Edition com Advanced Services Service Pack 4:<br />
SQLServer2005-KB2716429-x86-ENU.exe /quiet /InstanceName={instance}</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização do GDR do SQL Server 2005 para sistemas de 32 bits Service Pack 4:<br />
SQLServer2005-KB2716429-x86-ENU.exe /quiet /InstanceName={instance}</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização do GDR do SQL Server 2005 para sistemas x64 Service Pack 4:<br />
SQLServer2005-KB2716429-x64-ENU.exe /quiet /InstanceName={instance}</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização do GDR do SQL Server 2005 para sistemas Itanium Service Pack 4:<br />
SQLServer2005-KB2716429-IA64-ENU.exe /quiet /InstanceName={instance}</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização do QFE do SQL Server 2005 Express Edition com Advanced Services Service Pack 4:<br />
SQLServer2005-KB2716427-x86-ENU.exe /quiet /InstanceName={instance}</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização do QFE do SQL Server 2005 para sistemas de 32 bits Service Pack 4:<br />
SQLServer2005-KB2716427-x86-ENU.exe /quiet /InstanceName={instance}</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização do QFE do SQL Server 2005 para sistemas x64 Service Pack 4:<br />
SQLServer2005-KB2716427-x64-ENU.exe /quiet /InstanceName={instance}</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização do QFE do SQL Server 2005 para sistemas Itanium Service Pack 4:<br />
SQLServer2005-KB2716427-IA64-ENU.exe /quiet /quiet /InstanceName={instance}</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;">Arquivo de log de atualização</td>
<td style="border:1px solid black;">%programfiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Summary.log</td>
</tr>
<tr class="even">
<td style="border:1px solid black;">Instruções especiais</td>
<td style="border:1px solid black;">A atualização também será oferecida às instâncias do SQL Server 2005 com cluster. As atualizações para clusters do SQL Server 2005 exigirão a interação do usuário.<br />
<br />
Se seu cluster do SQL Server 2005 tiver um nó passivo, a Microsoft recomenda que você faça a varredura e aplique a atualização primeiro ao nó ativo e depois faça o mesmo ao nó passivo. Quando todos os componentes tiverem sido atualizados no nó passivo, a atualização não será mais oferecida.</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;">Mais informações</td>
<td style="border:1px solid black;">Consulte a subseção <strong>Orientação e ferramentas de detecção e implantação</strong></td>
</tr>
<tr class="even">
<td style="border:1px solid black;"><strong>Requisitos</strong> <strong>de</strong> <strong>reinicialização</strong></td>
<td style="border:1px solid black;"></td>
</tr>
<tr class="odd">
<td style="border:1px solid black;">Reinicialização necessária?</td>
<td style="border:1px solid black;">Se uma reinicialização for necessária, o instalador a solicitará ou retornará o código de saída 3010.</td>
</tr>
<tr class="even">
<td style="border:1px solid black;">HotPatching</td>
<td style="border:1px solid black;">Esta atualização de segurança não oferece suporte a HotPatching. Para obter mais informações sobre HotPatching, consulte o <a href="http://support.microsoft.com/kb/897341">Artigo 897341 (em inglês) da Microsoft Knowledge Base</a>.</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"><strong>Informações sobre remoção</strong></td>
<td style="border:1px solid black;">Para todas as edições com suporte do SQL Server 2005, exceto o SQL Server 2005 para sistemas baseados em x64 Service Pack 4:<br />
Use a ferramenta <strong>Adicionar ou Remover Programas</strong> no Painel de controle.<br />
<br />
<strong>Observação</strong> Existe um problema de desinstalação no SQL Server 2005 para sistemas baseados em x64 Service Pack 4. Consulte o <a href="http://support.microsoft.com/kb/2754849">Artigo 2754849 da Microsoft Knowledge Base</a> para obter mais informações.</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"><strong>Informaçõessobre</strong> <strong>o</strong> <strong>arquivo</strong></td>
<td style="border:1px solid black;">Para atualização de GDR do SQL Server 2005 Service Pack 4:<br />
Consulte o <a href="http://support.microsoft.com/kb/2716429">Artigo 2716429 (em inglês) da Microsoft Knowledge Base</a></td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização de QFE do SQL Server 2005 Service Pack 4:<br />
Consulte o <a href="http://support.microsoft.com/kb/2716427">Artigo 2716427 (em inglês) da Microsoft Knowledge Base</a></td>
</tr>
</tbody>
</table>
#### Informações de implantação
**Instalando a atualização**
Quando você instala esta atualização de segurança, o instalador verifica se alguns dos arquivos que estão sendo atualizados no computador foram anteriormente atualizados por um hotfix da Microsoft.
Para obter mais informações sobre a terminologia que aparece neste boletim, como *hotfix*, consulte o [Artigo 824684 (em inglês) da Microsoft Knowledge Base](http://support.microsoft.com/kb/824684).
Esta atualização de segurança oferece suporte às seguintes opções de instalação:
Opções de instalação da atualização de segurança para as quais há suporte
| Opção | Descrição |
|-------------------------------|----------------------------------------------------------------------------------------------------|
| **/?** | Exibe a caixa de diálogo de Ajuda |
| **/quiet** | Executa o programa de instalação no modo silencioso |
| **/reportonly** | Exibe os recursos que este pacote pode atualizar |
| **/allinstances** | Atualiza todas as instâncias do SQL Server e todos os componentes compartilhados |
| **/instancename** | Atualiza uma instância específica do SQL Server e todos os componentes compartilhados |
| **/sapwd** | Senha para execução de scripts pela conta sa do SQL Server |
| **/user** | Conta de usuário para conexão a um nó de cluster remoto |
| **/password** | Senha para conexão a um nó de cluster remoto |
| **/rsupgradedatabaseaccount** | Conta de usuário para atualização dos Reporting Services |
| **/rsupgradepassword** | Senha da conta de usuário para atualização dos Reporting Services |
| **/rsupgradedatabase** | Evita que o banco de dados dos Reporting Services seja atualizado quando o parâmetro for igual a 0 |
| **/allinstances** | Aplica a atualização a todas as instâncias |
| **/InstanceName={instance}** | Aplica a atualização a uma instância especificada |
**Observação** É possível combinar essas opções em uma única linha de comando. Para obter compatibilidade com versões anteriores, a atualização de segurança também oferece suporte a várias opções de instalação utilizadas por versões anteriores do programa de instalação. Para obter mais informações sobre as opções de instalação suportadas, consulte o [Artigo 262841 (em inglês) da Microsoft Knowledge Base](http://support.microsoft.com/kb/262841).
**Removendo a atualização**
Exemplo de como remover o QFE de uma única instância:
```
%windir%\\SQL9\_KB960090\_ENU\\hotfix.exe /quiet /uninstall /instancename=foo
```
Exemplo de como remover o QFE de todas as instâncias:
```
%windir%\\SQL9\_KB960090\_ENU\\hotfix.exe /quiet /uninstall /allinstances
```
**Verificando a aplicação da atualização**
- **Microsoft Baseline Security Analyzer**
Para verificar se uma atualização de segurança foi aplicada em um sistema afetado, é possível utilizar a ferramenta MBSA (Microsoft Baseline Security Analyzer). Consulte a seção Orientação e ferramentas de detecção e implantação neste boletim para obter mais informações.
- **Verificação de versão de arquivo**
Como existem várias versões do Microsoft Windows, as etapas a seguir podem ser diferentes no seu computador. Se isso acontecer, consulte a documentação do produto para completar estas etapas.
1. Clique em **Iniciar** e, em seguida, clique em **Pesquisar**.
2. No painel **Resultados da Pesquisa**, clique em **Todos os arquivos e pastas**, em **Search Companion**.
3. Na caixa **Todo ou parte do nome do arquivo** , digite um nome de arquivo da tabela de informações de arquivo correta e clique em **Pesquisar**.
4. Na lista de arquivos, clique com o botão direito do mouse em um nome de arquivo da tabela de informações de arquivo correta e clique em **Propriedades**.
**Observação** Dependendo da versão do sistema operacional ou dos programas instalados, alguns dos arquivos listados na tabela de informações de arquivos talvez não estejam instalados.
5. Na guia **Versão**, determine a versão do arquivo instalado no computador comparando-o com a versão documentada na tabela de informações de arquivos correta.
**Observação** Atributos que não sejam a versão do arquivo podem ser alterados durante a instalação. A comparação de outros atributos de arquivo com as informações na tabela não é um método suportado para verificar se a atualização foi aplicada. Além disso, em alguns casos, arquivos podem ser renomeados durante a instalação. Se as informações sobre o arquivo ou a versão não estiverem presentes, use um dos outros métodos disponíveis para verificar a instalação da atualização.
#### SQL Server 2008 (todas as edições)
**Tabela de referência**
A tabela a seguir contém as informações de atualização de segurança desse software. Você pode encontrar informações adicionais na subseção **Informações de implantação**, nesta seção.
<p> </p>
<table style="border:1px solid black;">
<tbody>
<tr class="odd">
<td style="border:1px solid black;"><strong>Inclusão em Service Packs futuros</strong></td>
<td style="border:1px solid black;">SQL Server 2008 Service Pack 4</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"><strong>Implantação</strong></td>
<td style="border:1px solid black;"></td>
</tr>
<tr class="odd">
<td style="border:1px solid black;">Instalar sem intervenção do usuário</td>
<td style="border:1px solid black;">Para atualização do GDR do SQL Server 2008 para sistemas de 32 bits Service Pack 2:<br />
SQLServer2008-KB2716434-x86.exe /quiet /allinstances</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização do GDR do SQL Server 2008 para sistemas x64 Service Pack 2:<br />
SQLServer2008-KB2716434-x64.exe /quiet /allinstances</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização de GDR do SQL Server 2008 para sistemas baseados no Itanium Service Pack 2:<br />
SQLServer2008-KB2716434-IA64.exe /quiet /allinstances</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização do QFE do SQL Server 2008 para sistemas de 32 bits Service Pack 2:<br />
SQLServer2008-KB2716433-x86.exe /quiet /allinstances</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização do QFE do SQL Server 2008 para sistemas x64 Service Pack 2:<br />
SQLServer2008-KB2716433-x64.exe /quiet /allinstances</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização de QFE do SQL Server 2008 para sistemas baseados no Itanium Service Pack 2:<br />
SQLServer2008-KB2716433-IA64.exe /quiet /allinstances</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização do GDR do SQL Server 2008 para sistemas de 32 bits Service Pack 3:<br />
SQLServer2008-KB2716436-x86.exe /quiet /allinstances</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização do GDR do SQL Server 2008 para sistemas x64 Service Pack 3:<br />
SQLServer2008-KB2716436-x64.exe /quiet /allinstances</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização do GDR do SQL Server 2008 para sistemas baseados no Itanium Service Pack 3:<br />
SQLServer2008-KB2716436-IA64.exe /quiet /allinstances</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização do QFE do SQL Server 2008 para sistemas de 32 bits Service Pack 3:<br />
SQLServer2008-KB2716435-x86.exe /quiet /allinstances</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização do QFE do SQL Server 2008 para sistemas x64 Service Pack 3:<br />
SQLServer2008-KB2716435-x64.exe /quiet /allinstances</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização do QFE do SQL Server 2008 para sistemas baseados no Itanium Service Pack 3:<br />
SQLServer2008-KB2716435-IA64.exe /quiet /allinstances</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;">Instalando uma única instância</td>
<td style="border:1px solid black;">Para atualização do GDR do SQL Server 2008 para sistemas de 32 bits Service Pack 2:<br />
SQLServer2008-KB2716434-x86.exe /quiet /InstanceName={instance}</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização do GDR do SQL Server 2008 para sistemas x64 Service Pack 2:<br />
SQLServer2008-KB2716434-x64.exe /quiet /InstanceName={instance}</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização de GDR do SQL Server 2008 para sistemas baseados no Itanium Service Pack 2:<br />
SQLServer2008-KB2716434-IA64.exe /quiet /InstanceName={instance}</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização do QFE do SQL Server 2008 para sistemas de 32 bits Service Pack 2:<br />
SQLServer2008-KB2716433-x86.exe /quiet /InstanceName={instance}</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização do QFE do SQL Server 2008 para sistemas x64 Service Pack 2:<br />
SQLServer2008-KB2716433-x64.exe /quiet /InstanceName={instance}</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização de QFE do SQL Server 2008 para sistemas baseados no Itanium Service Pack 2:<br />
SQLServer2008-KB2716433-IA64.exe /quiet /InstanceName={instance}</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização do GDR do SQL Server 2008 para sistemas de 32 bits Service Pack 3:<br />
SQLServer2008-KB2716436-x86.exe /quiet /InstanceName={instance}</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização do GDR do SQL Server 2008 para sistemas x64 Service Pack 3:<br />
SQLServer2008-KB2716436-x64.exe /quiet /InstanceName={instance}</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização do GDR do SQL Server 2008 para sistemas baseados no Itanium Service Pack 3:<br />
SQLServer2008-KB2716436-IA64.exe /quiet /InstanceName={instance}</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização do QFE do SQL Server 2008 Service Pack 3:<br />
SQLServer2008-KB2716435-x86.exe /quiet /InstanceName={instance}</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização do QFE do SQL Server 2008 para sistemas x64 Service Pack 3:<br />
SQLServer2008-KB2716435-x64.exe /quiet /InstanceName={instance}</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização do QFE do SQL Server 2008 para sistemas baseados no Itanium Service Pack 3:<br />
SQLServer2008-KB2716435-IA64.exe /quiet /InstanceName={instance}</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;">Arquivo de log de atualização</td>
<td style="border:1px solid black;">%programfiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Summary.log</td>
</tr>
<tr class="even">
<td style="border:1px solid black;">Instruções especiais</td>
<td style="border:1px solid black;">A atualização também será oferecida às instâncias do SQL Server 2008 com cluster.<br />
<br />
Se seu cluster do SQL Server 2008 tiver um nó passivo, a Microsoft recomenda que você faça a varredura e aplique a atualização primeiro ao nó ativo e depois faça o mesmo ao nó passivo. Quando todos os componentes tiverem sido atualizados no nó passivo, a atualização não será mais oferecida.</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;">Mais informações</td>
<td style="border:1px solid black;">Consulte a subseção <strong>Orientação e ferramentas de detecção e implantação</strong></td>
</tr>
<tr class="even">
<td style="border:1px solid black;"><strong>Requisitos</strong> <strong>de</strong> <strong>reinicialização</strong></td>
<td style="border:1px solid black;"></td>
</tr>
<tr class="odd">
<td style="border:1px solid black;">Reinicialização necessária?</td>
<td style="border:1px solid black;">Se uma reinicialização for necessária, o instalador a solicitará ou retornará o código de saída 3010.</td>
</tr>
<tr class="even">
<td style="border:1px solid black;">HotPatching</td>
<td style="border:1px solid black;">Esta atualização de segurança não oferece suporte a HotPatching. Para obter mais informações sobre HotPatching, consulte o <a href="http://support.microsoft.com/kb/897341">Artigo 897341 (em inglês) da Microsoft Knowledge Base</a>.</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"><strong>Informações sobre remoção</strong></td>
<td style="border:1px solid black;">Para todas as edições com suporte do SQL Server 2008:<br />
Use a ferramenta <strong>Adicionar ou Remover Programas</strong> no Painel de controle.</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"><strong>Informaçõessobre</strong> <strong>o</strong> <strong>arquivo</strong></td>
<td style="border:1px solid black;">Para atualização de GDR do SQL Server 2008 Service Pack 2:<br />
consulte o <a href="http://support.microsoft.com/kb/2716434">Artigo 2716434 da Microsoft Knowledge Base</a></td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização de QFE do SQL Server 2008 Service Pack 2:<br />
consulte o <a href="http://support.microsoft.com/kb/2716433">Artigo 2716433 da Microsoft Knowledge Base</a></td>
</tr>
<tr class="even">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização do GDR do SQL Server 2008 Service Pack 3:<br />
consulte o <a href="http://support.microsoft.com/kb/2716436">Artigo 2716436 da Microsoft Knowledge Base</a></td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização do QFE do SQL Server 2008 Service Pack 3:<br />
consulte o <a href="http://support.microsoft.com/kb/2716435">Artigo 2494094 da Microsoft Knowledge Base</a></td>
</tr>
</tbody>
</table>
#### Informações de implantação
**Instalando a atualização**
Quando você instala esta atualização de segurança, o instalador verifica se alguns dos arquivos que estão sendo atualizados no computador foram anteriormente atualizados por um hotfix da Microsoft.
Para obter mais informações sobre a terminologia que aparece neste boletim, como *hotfix*, consulte o [Artigo 824684 (em inglês) da Microsoft Knowledge Base](http://support.microsoft.com/kb/824684).
Esta atualização de segurança oferece suporte às seguintes opções de instalação:
Opções de instalação da atualização de segurança para as quais há suporte
| Opção | Descrição |
|-------------------------------|----------------------------------------------------------------------------------------------------|
| **/?** | Exibe a caixa de diálogo de Ajuda |
| **/quiet** | Executa o programa de instalação no modo silencioso |
| **/reportonly** | Exibe os recursos que este pacote pode atualizar |
| **/allinstances** | Atualiza todas as instâncias do SQL Server e todos os componentes compartilhados |
| **/instancename** | Atualiza uma instância específica do SQL Server e todos os componentes compartilhados |
| **/sapwd** | Senha para execução de scripts pela conta sa do SQL Server |
| **/user** | Conta de usuário para conexão a um nó de cluster remoto |
| **/password** | Senha para conexão a um nó de cluster remoto |
| **/rsupgradedatabaseaccount** | Conta de usuário para atualização dos Reporting Services |
| **/rsupgradepassword** | Senha da conta de usuário para atualização dos Reporting Services |
| **/rsupgradedatabase** | Evita que o banco de dados dos Reporting Services seja atualizado quando o parâmetro for igual a 0 |
| **/allinstances** | Aplica a atualização a todas as instâncias |
| **/InstanceName={instance}** | Aplica a atualização a uma instância especificada |
**Observação** É possível combinar essas opções em uma única linha de comando. Para obter compatibilidade com versões anteriores, a atualização de segurança também oferece suporte a várias opções de instalação utilizadas por versões anteriores do programa de instalação. Para obter mais informações sobre as opções de instalação suportadas, consulte o [Artigo 262841 (em inglês) da Microsoft Knowledge Base](http://support.microsoft.com/kb/262841).
**Removendo a atualização**
Exemplo de como remover o QFE de uma única instância:
```
% windir %\SQL9_KB960090_ENU\hotfix.exe /quiet /uninstall / instancename =foo
```
Exemplo de como remover o QFE de todas as instâncias:
```
% windir %\SQL9_KB960090_ENU\hotfix.ex e /quiet /uninstall / allinstances
```
**Verificando a aplicação da atualização**
- **Microsoft Baseline Security Analyzer**
Para verificar se uma atualização de segurança foi aplicada em um sistema afetado, é possível utilizar a ferramenta MBSA (Microsoft Baseline Security Analyzer). Consulte a seção Orientação e ferramentas de detecção e implantação neste boletim para obter mais informações.
- **Verificação de versão de arquivo**
Como existem várias versões do Microsoft Windows, as etapas a seguir podem ser diferentes no seu computador. Se isso acontecer, consulte a documentação do produto para completar estas etapas.
1. Clique em **Iniciar** e, em seguida, clique em **Pesquisar**.
2. No painel **Resultados da Pesquisa**, clique em **Todos os arquivos e pastas**, em **Search Companion**.
3. Na caixa **Todo ou parte do nome do arquivo** , digite um nome de arquivo da tabela de informações de arquivo correta e clique em **Pesquisar**.
4. Na lista de arquivos, clique com o botão direito do mouse em um nome de arquivo da tabela de informações de arquivo correta e clique em **Propriedades**.
**Observação** Dependendo da versão do sistema operacional ou dos programas instalados, alguns dos arquivos listados na tabela de informações de arquivos talvez não estejam instalados.
5. Na guia **Versão**, determine a versão do arquivo instalado no computador comparando-o com a versão documentada na tabela de informações de arquivos correta.
**Observação** Atributos que não sejam a versão do arquivo podem ser alterados durante a instalação. A comparação de outros atributos de arquivo com as informações na tabela não é um método suportado para verificar se a atualização foi aplicada. Além disso, em alguns casos, arquivos podem ser renomeados durante a instalação. Se as informações sobre o arquivo ou a versão não estiverem presentes, use um dos outros métodos disponíveis para verificar a instalação da atualização.
#### SQL Server 2008 R2
**Tabela de referência**
A tabela a seguir contém as informações de atualização de segurança desse software. Você pode encontrar informações adicionais na subseção **Informações de implantação**, nesta seção.
<p> </p>
<table style="border:1px solid black;">
<tbody>
<tr class="odd">
<td style="border:1px solid black;"><strong>Inclusão em Service Packs futuros</strong></td>
<td style="border:1px solid black;">SQL Server 2008 R2 Service Pack 2</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"><strong>Implantação</strong></td>
<td style="border:1px solid black;"></td>
</tr>
<tr class="odd">
<td style="border:1px solid black;">Instalar sem intervenção do usuário</td>
<td style="border:1px solid black;">Para atualização do GDR do SQL Server 2008 R2 para sistemas de 32 bits Service Pack 1:<br />
SQLServer2008R2-KB2716440-x86.exe /quiet /allinstances</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização do GDR do SQL Server 2008 R2 para sistemas x64 Service Pack 1:<br />
SQLServer2008R2-KB2716440-x64.exe /quiet /allinstances</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização do GDR do SQL Server 2008 R2 para sistemas Itanium Service Pack 1:<br />
SQLServer2008R2-KB2716440-IA64.exe /quiet /allinstances</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização do QFE do SQL Server 2008 R2 para sistemas de 32 bits Service Pack 1:<br />
SQLServer2008R2-KB2716439-x86.exe /quiet /allinstances</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização do QFE do SQL Server 2008 R2 para sistemas x64 Service Pack 1:<br />
SQLServer2008R2-KB2716439-x64.exe /quiet /allinstances</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização do QFE do SQL Server 2008 R2 para sistemas Itanium Service Pack 1:<br />
SQLServer2008R2-KB2716439-IA64.exe /quiet /allinstances</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;">Instalando uma única instância</td>
<td style="border:1px solid black;">Para atualização do GDR do SQL Server 2008 R2 para sistemas de 32 bits Service Pack 1:<br />
SQLServer2008R2-KB2716440-x86.exe /quiet /InstanceName={instance}</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização do GDR do SQL Server 2008 R2 para sistemas x64 Service Pack 1:<br />
SQLServer2008R2-KB2716440-x64.exe /quiet /InstanceName={instance}</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização do GDR do SQL Server 2008 R2 para sistemas Itanium Service Pack 1:<br />
SQLServer2008R2-KB2716440-IA64.exe /quiet /InstanceName={instance}</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização do QFE do SQL Server 2008 R2 para sistemas de 32 bits Service Pack 1:<br />
SQLServer2008R2-KB2716439-x86.exe /quiet /InstanceName={instance}</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização do QFE do SQL Server 2008 R2 para sistemas x64 Service Pack 1:<br />
SQLServer2008R2-KB2716439-x64.exe /quiet /InstanceName={instance}</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização do QFE do SQL Server 2008 R2 para sistemas Itanium Service Pack 1:<br />
SQLServer2008R2-KB2716439-IA64.exe /quiet /InstanceName={instance}</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;">Arquivo de log de atualização</td>
<td style="border:1px solid black;">%programfiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Summary.log</td>
</tr>
<tr class="even">
<td style="border:1px solid black;">Instruções especiais</td>
<td style="border:1px solid black;">A atualização também será oferecida às instâncias do SQL Server 2008 R2 com cluster.<br />
<br />
Se seu cluster do SQL Server 2008 R2 tiver um nó passivo, a Microsoft recomenda que você faça a varredura e aplique a atualização primeiro ao nó ativo e depois faça o mesmo ao nó passivo. Quando todos os componentes tiverem sido atualizados no nó passivo, a atualização não será mais oferecida.</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;">Mais informações</td>
<td style="border:1px solid black;">Consulte a subseção <strong>Orientação e ferramentas de detecção e implantação</strong></td>
</tr>
<tr class="even">
<td style="border:1px solid black;"><strong>Requisitos</strong> <strong>de</strong> <strong>reinicialização</strong></td>
<td style="border:1px solid black;"></td>
</tr>
<tr class="odd">
<td style="border:1px solid black;">Reinicialização necessária?</td>
<td style="border:1px solid black;">Se uma reinicialização for necessária, o instalador a solicitará ou retornará o código de saída 3010.</td>
</tr>
<tr class="even">
<td style="border:1px solid black;">HotPatching</td>
<td style="border:1px solid black;">Esta atualização de segurança não oferece suporte a HotPatching. Para obter mais informações sobre HotPatching, consulte o <a href="http://support.microsoft.com/kb/897341">Artigo 897341 (em inglês) da Microsoft Knowledge Base</a>.</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"><strong>Informações sobre remoção</strong></td>
<td style="border:1px solid black;">Para todas as edições com suporte do SQL Server 2008 R2:<br />
Use a ferramenta <strong>Adicionar ou Remover Programas</strong> no Painel de controle.</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"><strong>Informaçõessobre</strong> <strong>o</strong> <strong>arquivo</strong></td>
<td style="border:1px solid black;">Para atualização do GDR do SQL Server 2008 R2 Service Pack 1:<br />
consulte o <a href="http://support.microsoft.com/kb/2716440">Artigo 2716440 da Microsoft Knowledge Base</a></td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização do QFE do SQL Server 2008 R2 Service Pack 1:<br />
consulte o <a href="http://support.microsoft.com/kb/2716439">Artigo 2716439 da Microsoft Knowledge Base</a></td>
</tr>
</tbody>
</table>
#### Informações de implantação
**Instalando a atualização**
Quando você instala esta atualização de segurança, o instalador verifica se alguns dos arquivos que estão sendo atualizados no computador foram anteriormente atualizados por um hotfix da Microsoft.
Para obter mais informações sobre a terminologia que aparece neste boletim, como *hotfix*, consulte o [Artigo 824684 (em inglês) da Microsoft Knowledge Base](http://support.microsoft.com/kb/824684).
Esta atualização de segurança oferece suporte às seguintes opções de instalação:
Opções de instalação da atualização de segurança para as quais há suporte
| Opção | Descrição |
|-------------------------------|----------------------------------------------------------------------------------------------------|
| **/?** | Exibe a caixa de diálogo de Ajuda |
| **/quiet** | Executa o programa de instalação no modo silencioso |
| **/reportonly** | Exibe os recursos que este pacote pode atualizar |
| **/allinstances** | Atualiza todas as instâncias do SQL Server e todos os componentes compartilhados |
| **/instancename** | Atualiza uma instância específica do SQL Server e todos os componentes compartilhados |
| **/sapwd** | Senha para execução de scripts pela conta sa do SQL Server |
| **/user** | Conta de usuário para conexão a um nó de cluster remoto |
| **/password** | Senha para conexão a um nó de cluster remoto |
| **/rsupgradedatabaseaccount** | Conta de usuário para atualização dos Reporting Services |
| **/rsupgradepassword** | Senha da conta de usuário para atualização dos Reporting Services |
| **/rsupgradedatabase** | Evita que o banco de dados dos Reporting Services seja atualizado quando o parâmetro for igual a 0 |
| **/allinstances** | Aplica a atualização a todas as instâncias |
| **/InstanceName={instance}** | Aplica a atualização a uma instância especificada |
**Observação** É possível combinar essas opções em uma única linha de comando. Para obter compatibilidade com versões anteriores, a atualização de segurança também oferece suporte a várias opções de instalação utilizadas por versões anteriores do programa de instalação. Para obter mais informações sobre as opções de instalação suportadas, consulte o [Artigo 262841 (em inglês) da Microsoft Knowledge Base](http://support.microsoft.com/kb/262841).
**Removendo a atualização**
Exemplo de como remover o QFE de uma única instância:
```
%windir%\SQL9_KB960090_ENU\hotfix.exe /quiet /uninstall /instancename=foo
```
Exemplo de como remover o QFE de todas as instâncias:
```
%windir%\SQL9_KB960090_ENU\hotfix.exe /quiet /uninstall /allinstances
```
**Verificando a aplicação da atualização**
- **Microsoft Baseline Security Analyzer**
Para verificar se uma atualização de segurança foi aplicada em um sistema afetado, é possível utilizar a ferramenta MBSA (Microsoft Baseline Security Analyzer). Consulte a seção Orientação e ferramentas de detecção e implantação neste boletim para obter mais informações.
- **Verificação de versão de arquivo**
Como existem várias versões do Microsoft Windows, as etapas a seguir podem ser diferentes no seu computador. Se isso acontecer, consulte a documentação do produto para completar estas etapas.
1. Clique em **Iniciar** e, em seguida, clique em **Pesquisar**.
2. No painel **Resultados da Pesquisa**, clique em **Todos os arquivos e pastas**, em **Search Companion**.
3. Na caixa **Todo ou parte do nome do arquivo** , digite um nome de arquivo da tabela de informações de arquivo correta e clique em **Pesquisar**.
4. Na lista de arquivos, clique com o botão direito do mouse em um nome de arquivo da tabela de informações de arquivo correta e clique em **Propriedades**.
**Observação** Dependendo da versão do sistema operacional ou dos programas instalados, alguns dos arquivos listados na tabela de informações de arquivos talvez não estejam instalados.
5. Na guia **Versão**, determine a versão do arquivo instalado no computador comparando-o com a versão documentada na tabela de informações de arquivos correta.
**Observação** Atributos que não sejam a versão do arquivo podem ser alterados durante a instalação. A comparação de outros atributos de arquivo com as informações na tabela não é um método suportado para verificar se a atualização foi aplicada. Além disso, em alguns casos, arquivos podem ser renomeados durante a instalação. Se as informações sobre o arquivo ou a versão não estiverem presentes, use um dos outros métodos disponíveis para verificar a instalação da atualização.
#### SQL Server 2012
**Tabela de referência**
A tabela a seguir contém as informações de atualização de segurança desse software. Você pode encontrar informações adicionais na subseção **Informações de implantação**, nesta seção.
<p> </p>
<table style="border:1px solid black;">
<tbody>
<tr class="odd">
<td style="border:1px solid black;"><strong>Inclusão em Service Packs futuros</strong></td>
<td style="border:1px solid black;">SQL Server 2012 Service Pack 1</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"><strong>Implantação</strong></td>
<td style="border:1px solid black;"></td>
</tr>
<tr class="odd">
<td style="border:1px solid black;">Instalar sem intervenção do usuário</td>
<td style="border:1px solid black;">Para atualização do GDR do SQL Server 2012 para sistemas de 32 bits:<br />
SQLServer2012-KB2716442-x86.exe /quiet /allinstances</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização do GDR do SQL Server 2012 para sistemas x64:<br />
SQLServer2012-KB2716442-x64.exe /quiet /allinstances</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização do QFE do SQL Server 2012 para sistemas de 32 bits:<br />
SQLServer2012-KB2716441-x86.exe /quiet /allinstances</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização do QFE do SQL Server 2012 para sistemas x64:<br />
SQLServer2012-KB2716441-x64.exe /quiet /allinstances</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;">Instalando uma única instância</td>
<td style="border:1px solid black;">Para atualização do GDR do SQL Server 2012 para sistemas de 32 bits:<br />
SQLServer2012-KB2716442-x86.exe /quiet /InstanceName={instance}</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização do GDR do SQL Server 2012 para sistemas x64:<br />
SQLServer2012-KB2716442-x64.exe /quiet /InstanceName={instance}</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização do QFE do SQL Server 2012 para sistemas de 32 bits:<br />
SQLServer2012-KB2716441-x86.exe /quiet /InstanceName={instance}</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização do QFE do SQL Server 2012 para sistemas x64:<br />
SQLServer2012-KB2716441-x64.exe /quiet /InstanceName={instance}</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;">Arquivo de log de atualização</td>
<td style="border:1px solid black;">%programfiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Summary.log</td>
</tr>
<tr class="even">
<td style="border:1px solid black;">Instruções especiais</td>
<td style="border:1px solid black;">A atualização também será oferecida às instâncias do SQL Server 2012 com cluster.<br />
<br />
Se seu cluster do SQL Server 2012 tiver um nó passivo, a Microsoft recomenda que você faça a varredura e aplique a atualização primeiro ao nó ativo e depois faça o mesmo ao nó passivo. Quando todos os componentes tiverem sido atualizados no nó passivo, a atualização não será mais oferecida.</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;">Mais informações</td>
<td style="border:1px solid black;">Consulte a subseção <strong>Orientação e ferramentas de detecção e implantação</strong></td>
</tr>
<tr class="even">
<td style="border:1px solid black;"><strong>Requisitos</strong> <strong>de</strong> <strong>reinicialização</strong></td>
<td style="border:1px solid black;"></td>
</tr>
<tr class="odd">
<td style="border:1px solid black;">Reinicialização necessária?</td>
<td style="border:1px solid black;">Se uma reinicialização for necessária, o instalador a solicitará ou retornará o código de saída 3010.</td>
</tr>
<tr class="even">
<td style="border:1px solid black;">HotPatching</td>
<td style="border:1px solid black;">Esta atualização de segurança não oferece suporte a HotPatching. Para obter mais informações sobre HotPatching, consulte o <a href="http://support.microsoft.com/kb/897341">Artigo 897341 (em inglês) da Microsoft Knowledge Base</a>.</td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"><strong>Informações sobre remoção</strong></td>
<td style="border:1px solid black;">Para todas as edições com suporte do SQL Server 2008 R2:<br />
Use a ferramenta <strong>Adicionar ou Remover Programas</strong> no Painel de controle.</td>
</tr>
<tr class="even">
<td style="border:1px solid black;"><strong>Informaçõessobre</strong> <strong>o</strong> <strong>arquivo</strong></td>
<td style="border:1px solid black;">Para atualização do GDR de SQL Server 2012:<br />
consulte o <a href="http://support.microsoft.com/kb/2716442">Artigo 2716442 da Microsoft Knowledge Base</a></td>
</tr>
<tr class="odd">
<td style="border:1px solid black;"></td>
<td style="border:1px solid black;">Para atualização do QFE de SQL Server 2012:<br />
consulte o <a href="http://support.microsoft.com/kb/2716441">Artigo 2716441 da Microsoft Knowledge Base</a></td>
</tr>
</tbody>
</table>
#### Informações de implantação
**Instalando a atualização**
Quando você instala esta atualização de segurança, o instalador verifica se alguns dos arquivos que estão sendo atualizados no computador foram anteriormente atualizados por um hotfix da Microsoft.
Para obter mais informações sobre a terminologia que aparece neste boletim, como *hotfix*, consulte o [Artigo 824684 (em inglês) da Microsoft Knowledge Base](http://support.microsoft.com/kb/824684).
Esta atualização de segurança oferece suporte às seguintes opções de instalação:
Opções de instalação da atualização de segurança para as quais há suporte
| Opção | Descrição |
|-------------------------------|----------------------------------------------------------------------------------------------------|
| **/?** | Exibe a caixa de diálogo de Ajuda |
| **/quiet** | Executa o programa de instalação no modo silencioso |
| **/reportonly** | Exibe os recursos que este pacote pode atualizar |
| **/allinstances** | Atualiza todas as instâncias do SQL Server e todos os componentes compartilhados |
| **/instancename** | Atualiza uma instância específica do SQL Server e todos os componentes compartilhados |
| **/sapwd** | Senha para execução de scripts pela conta sa do SQL Server |
| **/user** | Conta de usuário para conexão a um nó de cluster remoto |
| **/password** | Senha para conexão a um nó de cluster remoto |
| **/rsupgradedatabaseaccount** | Conta de usuário para atualização dos Reporting Services |
| **/rsupgradepassword** | Senha da conta de usuário para atualização dos Reporting Services |
| **/rsupgradedatabase** | Evita que o banco de dados dos Reporting Services seja atualizado quando o parâmetro for igual a 0 |
| **/allinstances** | Aplica a atualização a todas as instâncias |
| **/InstanceName={instance}** | Aplica a atualização a uma instância especificada |
**Observação** É possível combinar essas opções em uma única linha de comando. Para obter compatibilidade com versões anteriores, a atualização de segurança também oferece suporte a várias opções de instalação utilizadas por versões anteriores do programa de instalação. Para obter mais informações sobre as opções de instalação suportadas, consulte o [Artigo 262841 (em inglês) da Microsoft Knowledge Base](http://support.microsoft.com/kb/262841).
**Removendo a atualização**
Exemplo de como remover o QFE de uma única instância:
```
% windir %\SQL9_KB960090_ENU\hotfix.exe /quiet /uninstall / instancename =foo
```
Exemplo de como remover o QFE de todas as instâncias:
```
% windir %\SQL9_KB960090_ENU\hotfix.ex e /quiet /uninstall / allinstances
```
**Verificando a aplicação da atualização**
- **Microsoft Baseline Security Analyzer**
Para verificar se uma atualização de segurança foi aplicada em um sistema afetado, é possível utilizar a ferramenta MBSA (Microsoft Baseline Security Analyzer). Consulte a seção Orientação e ferramentas de detecção e implantação neste boletim para obter mais informações.
- **Verificação de versão de arquivo**
Como existem várias versões do Microsoft Windows, as etapas a seguir podem ser diferentes no seu computador. Se isso acontecer, consulte a documentação do produto para completar estas etapas.
1. Clique em **Iniciar** e, em seguida, clique em **Pesquisar**.
2. No painel **Resultados da Pesquisa**, clique em **Todos os arquivos e pastas**, em **Search Companion**.
3. Na caixa **Todo ou parte do nome do arquivo** , digite um nome de arquivo da tabela de informações de arquivo correta e clique em **Pesquisar**.
4. Na lista de arquivos, clique com o botão direito do mouse em um nome de arquivo da tabela de informações de arquivo correta e clique em **Propriedades**.
**Observação** Dependendo da versão do sistema operacional ou dos programas instalados, alguns dos arquivos listados na tabela de informações de arquivos talvez não estejam instalados.
5. Na guia **Versão**, determine a versão do arquivo instalado no computador comparando-o com a versão documentada na tabela de informações de arquivos correta.
**Observação** Atributos que não sejam a versão do arquivo podem ser alterados durante a instalação. A comparação de outros atributos de arquivo com as informações na tabela não é um método suportado para verificar se a atualização foi aplicada. Além disso, em alguns casos, arquivos podem ser renomeados durante a instalação. Se as informações sobre o arquivo ou a versão não estiverem presentes, use um dos outros métodos disponíveis para verificar a instalação da atualização.
### Outras informações
#### Microsoft Active Protections Program (MAPP)
Para melhorar as proteções de segurança para os clientes, a Microsoft fornece informações sobre vulnerabilidades aos principais fornecedores de software de segurança antes do lançamento de cada atualização de segurança mensal. Assim, os fornecedores de software de segurança podem usar essas informações sobre vulnerabilidades para fornecer proteções atualizadas aos clientes por meio de seus softwares ou dispositivos de segurança, como antivírus, sistemas de detecção de invasões baseados em rede ou sistemas de prevenção de invasões baseados em host. Para determinar se os fornecedores de software de segurança estão disponibilizando proteções ativas, visite os sites de proteções ativas fornecidos pelos parceiros do programa, listados em [Parceiros do Microsoft Active Protections Program (MAPP)](http://go.microsoft.com/fwlink/?linkid=215201).
#### Suporte
**Como obter ajuda e suporte para esta atualização de segurança**
- Ajude a instalar atualizações: [Suporte para Microsoft Update](http://support.microsoft.com/ph/6527)
- Soluções de segurança para profissionais de TI: [Solução de problemas e suporte de segurança TechNet](http://technet.microsoft.com/security/bb980617,aspx)
- Ajuda a proteger seu computador Windows de vírus e malware: [Central de segurança e solução contra vírus](http://support.microsoft.com/contactus/cu_sc_virsec_master)
- Suporte local de acordo com seu país: [Suporte internacional](http://support.microsoft.com/common/international.aspx)
#### Aviso de isenção de responsabilidade
As informações fornecidas na Microsoft Knowledge Base são apresentadas "no estado em que se encontram", sem garantia de qualquer tipo. A Microsoft se isenta de todas as garantias, expressas ou implícitas, inclusive as garantias de comercialização e adequação a um propósito específico. Em hipótese alguma a Microsoft Corporation ou seus fornecedores serão responsáveis por quaisquer danos, inclusive danos diretos, indiretos, incidentais, consequenciais, danos por lucros cessantes ou danos especiais, mesmo que a Microsoft Corporation ou seus fornecedores tenham sido alertados da possibilidade dos referidos danos. Como alguns estados não permitem a exclusão ou limitação de responsabilidade por danos consequenciais ou indiretos, a limitação acima pode não ser aplicável a você.
#### Revisões
- V1.0 (9 de outubro de 2012): Boletim publicado.
*Built at 2014-04-18T01:50:00Z-07:00*
| 54.335252 | 912 | 0.716451 | por_Latn | 0.989221 |
22de36fbdbc9884dc6079b476682bc9e822b3665 | 33 | md | Markdown | README.md | DataSciencePythonSonerKurt/SanFrancisco-Airport-Clustering | 0ceb178615064b44989562585fa5675cb07aef8c | [
"MIT"
] | null | null | null | README.md | DataSciencePythonSonerKurt/SanFrancisco-Airport-Clustering | 0ceb178615064b44989562585fa5675cb07aef8c | [
"MIT"
] | null | null | null | README.md | DataSciencePythonSonerKurt/SanFrancisco-Airport-Clustering | 0ceb178615064b44989562585fa5675cb07aef8c | [
"MIT"
] | null | null | null | # SanFrancisco-Airport-Clustering | 33 | 33 | 0.878788 | eng_Latn | 0.729797 |
22df302500cb62a379a9c49777074ef4bb1c7f19 | 72 | md | Markdown | src/content/uspecifiers/importtype.md | UnrealisticDev/unrealistic | 4e0b85076e45426efb5d3d71eee854090c806be0 | [
"MIT"
] | 2 | 2021-03-23T08:29:25.000Z | 2021-06-30T08:46:06.000Z | src/content/uspecifiers/importtype.md | UnrealisticDev/Unrealistic | 4e0b85076e45426efb5d3d71eee854090c806be0 | [
"MIT"
] | null | null | null | src/content/uspecifiers/importtype.md | UnrealisticDev/Unrealistic | 4e0b85076e45426efb5d3d71eee854090c806be0 | [
"MIT"
] | null | null | null | ---
id: 4ZAHDwFz8GXDAAMK0n2hoe
title: ImportType
snippet:
values:
---
| 10.285714 | 26 | 0.722222 | kor_Hang | 0.121557 |
22e115313a69752f8d7f59845556cabb9c8245fa | 9,063 | markdown | Markdown | _posts/2020-04-02-untyped.markdown | xiazemin/MyBlog | a0bf678e052efd238a4eb694a27528ccc234c186 | [
"MIT"
] | 1 | 2021-08-14T12:11:15.000Z | 2021-08-14T12:11:15.000Z | _posts/2020-04-02-untyped.markdown | xiazemin/MyBlogSrc | cc55274b05e2a6fd414066b09f41dab26c3f7e75 | [
"MIT"
] | 2 | 2020-10-30T15:42:56.000Z | 2020-10-30T15:42:56.000Z | _posts/2020-04-02-untyped.markdown | xiazemin/MyBlog | a0bf678e052efd238a4eb694a27528ccc234c186 | [
"MIT"
] | 1 | 2018-12-11T13:49:13.000Z | 2018-12-11T13:49:13.000Z | ---
title: untyped
layout: post
category: golang
author: 夏泽民
---
https://mp.weixin.qq.com/s/L6ysPUCyYhAwL6PsKXykhQ
<!-- more -->
你为什么使用常量？
why_might_you_use_constants
你不想在代码中到处定义魔法数值[1]，于是使用常量来声明它们，并在代码中再次使用它们。
魔法数值是不安全的，你需要准确声明它们，因此，常量是一个安全的选择。除此之外，在代码中看到常量而不是魔法数值也是令人高兴的；人们可以更好地理解代码是怎样的。
我们希望我们可以在使用常量中获得运行速度上的收益，因为，使用常量能够使编译器能够进行更多的优化，它将知道常量的值永远不会改变。
我最喜欢的是非类型化常量。它真是个天才的想法。当使用非类型化常量时，你将获得更多的灵活性和高精度的计算。
类型常量
typed_constants.image
类型 →Boolean,rune,numerics,或者 string
值 → 编译期时在声明中分配值
地址 → 你无法得到它在内存中的地址（不像变量）
你无法在声明常量之后再改变它
你不能使用运行时的结构，例如变量，指针，数组，切片，map,结构体，接口，方法调用，或者方法的值。
类型化常量声明
image
图中定义了一个类型常量 Pi，它的类型为 float64，值为 3.14
运行并且尝试代码示例，请点击这里[2]
声明多个常量
image
运行图中的代码并且检验它的结果，请点击这里[3]
在一个代码块中声明多个具有不同类型不同值的常量
当一个常量的类型和值没有声明时，它将从上一个常量中得到它。在上面，pi2 从 pi 中获取其类型和值。
Age 常量在声明时有一个新的值。并且，它通过赋值为 10 获取默认的类型 int。
可以在同一行和多个变量[4]声明中定义多个常量。
非类型化常量
它们有很好的特性，比如高精度的计算以及在所有数值表达式中使用它们而不声明类型等。下面我将介绍这些特性。它们就像 Go 中的通配符。
iamge
理想类型 → 与 Go 通常类型不同的隐藏类型。
理想值 → 存在于理想值空间中，并且具有默认类型。
默认类型 → 取决于理想值。
非类型化常量的声明
image
声明了一个非类型化的常量 Pi，并且为它赋值为 3.14，那么它默认的类型就是 float。
image
当需要它的类型的时候，图片左侧（期望类型）将转化为右边的类型（预先声明的类型）
尝试代码，点击这里[5]
高精度计算
如果常量只停留在非类型化常量领域，那么它没有速度的限制！但是，当将常量赋值给变量进行使用时，速度就有限制了。
image
当你将其分配给变量时，非类型化常量的精度会降低，其默认类型会转换为 Go 的普通类型[6]。
运行代码示例，请点击这里[7]
灵活的表达方式
你可以使用非类型化常量临时从 Go 的强类型系统中逸出，直到它们在类型要求表达式中的计算为止。
我在代码中[8]一直使用它们时，会避免在不需要强类型时声明它们。所以，如果你不真正需要常量，就不要用它声明类型。
运行代码示例
Understand when and how to use untyped constants[9]
We can assign an untyped constant to any numeric-type variable[10]
常量作用范围
image
一个常量只能在它的声明的作用域内使用。如果你在更内部的作用域内以同样的名字再声明一个常量，那么这个常量仅仅在内部作用域内可以使用，并且在此作用域内将覆盖外部声明的常量。查看代码示例，请点击这里[11]
via: https://blog.learngoprogramming.com/learn-golang-typed-untyped-constants-70b4df443b61
作者：Inanc Gumus[12]译者：xmge[13]校对：polaris1119[14]
本文由 GCTT[15] 原创编译，Go 中文网[16] 荣誉推出
参考资料
[1]
魔法数值: https://en.wikipedia.org/wiki/Magic_number_%28programming%29
[2]
请点击这里: https://play.golang.org/p/mrnqxa8Kic
[3]
请点击这里: https://play.golang.org/p/mBoqG58z_e
[4]
多个变量: https://blog.learngoprogramming.com/learn-go-lang-variables-visual-tutorial-and-ebook-9a061d29babe#4176
[5]
这里: https://play.golang.org/p/L5UC3XgYFk
[6]
普通类型: https://golang.org/ref/spec#Boolean_types
[7]
请点击这里: https://play.golang.org/p/4ODv0n_stw
[8]
代码中: https://github.com/inancgumus/myhttp/blob/master/get.go#L12
[9]
Understand when and how to use untyped constants: https://play.golang.org/p/2cgFoB4rYD
[10]
We can assign an untyped constant to any numeric-type variable: https://play.golang.org/p/7-VMh5egC-
[11]
请点击这里: https://play.golang.org/p/c3-GF_a5iI
[12]
Inanc Gumus: https://www.activestate.com/blog/author/peteg/
[13]
xmge: https://github.com/xmge
[14]
polaris1119: https://github.com/polaris1119
[15]
GCTT: https://github.com/studygolang/GCTT
[16]
Go 中文网: https://studygolang.com/
When declaring two const variables (one typed and one untyped), and printing out the type of the second one, like:
const x float32 = 10000
const y = 1e8 / x
fmt.Printf("the type of y: %T
", y)
// or with reflect:
fmt.Println(reflect.TypeOf(y))
it tells me, that
y
is of type
float32
.
Well this doesn't come as a surprise, since the the untyped const variable
y
is defined as dividing an untyped float constant by a typed float constant and therefore the type might be inferred.
According to "Go by Example" (https://gobyexample.com/constants), constants never have a type, unless explicitly provided. However, according to the official Go blog documentation, untyped constants do have hidden types that get inferred, but let the constant remain untyped until a type is needed.
I would have assumed, that
y
would still be an untyped float constant. However, when using it for assigning a new variable, Goland's inspector tells me, that the type can be omitted:
const z float32 = y
// ^^^ type can be ommitted
So finally, my question would be:
Is it impossible to declare an untyped constant out of typed constant expressions?
在声明两个const变量（一个为类型，一个为非类型）并打印第二个const类型时，例如 ：</ p>
const x float32 = 10000
const y = 1e8 / x
fmt.Printf（“ y的类型：％T
”，y）
//或带有反射：
fmt.Println（reflect.TypeOf（y））
</ code> </ pre>
它告诉我， y </ code>是 输入 float32 </ code>。 </ p>
这并不奇怪，因为无类型的const变量 y </ code>被定义为将无类型的浮点常量除以有类型的浮点常量，因此
根据“按示例执行”（ https://gobyexample.com/constants < / a>），除非明确提供，否则常量永远不会具有类型。 但是，根据Go官方博客文档，未类型化的常量 do </ strong>具有可以推断出的隐藏类型，但是让该常量保持未类型化，直到需要一个类型为止。 </ p>
我会假设， y </ code>仍然是无类型的浮点常量。 但是，在使用它分配新变量时，Goland的检查员告诉我，可以省略该类型：</ p>
const z float32 = y
// ^^^ type 可以省略
</ code> </ pre>
所以最后，我的问题是：
是否无法从类型化常量表达式中声明未类型化常量？</ p>
</ div>
A const declaration gives names to constants, that is, values that are fixed at compile time. The value of a constant must be a number, string, or boolean.
const的值只能是数字，字符串或者布尔值。
A constant declaration may specify a type as well as a value, but in the absence of an explicit type, the type is inferred from the expression on the right-hand side.
当定义常量时没有指定其类型时，常量的类型将由等号右边的表达式来决定。
下面是如何定义一组constant：
When a sequence of constants is declared as a group, the right-hand side expression may be omitted for all but the first of the group, implying that the previous expression and its type should be used again. For example:
const (
a = 1
b
c = 2
d
)
fmt.Println(a, b, c, d) // “1 1 2 2”
A const declaration may use the constant generator iota, which is used to create a sequence of related values without spelling out each one explicitly. In a const declaration, the value of iota begins at zero and increments by one for each item in the sequence. For example:
type Weekday int
const (
Sunday Weekday = iota
Monday
Tuesday
Wednesday
Thursday
Friday
Saturday
) This declares Sunday to be 0, Monday to be 1, and so on.
另外，关于untyped constants的定义：
Constants in Go are a bit unusual. Although a constant can have any of the basic data types like int or float64, including named basic types like time.Duration, many constants are not committed to a particular type. The compiler represents these uncommitted constants with much greater numeric precision than values of basic types, and arithmetic on them is more precise than machine arithmetic; you may assume at least 256 bits of precision. There are six flavors of these uncommitted constants, called untyped boolean, untyped integer, untyped rune, untyped floating-point, untyped complex, and untyped string.
只有constant才可能是untyped，变量不可能是untyped。
Only constants can be untyped. When an untyped constant is assigned to a variable, as in the first statement below, or appears on the right-hand side of a variable declaration with an explicit type, as in the other three statements, the constant is implicitly converted to the type of that variable if possible.
var f float64 = 3 + 0i // untyped complex -> float64
f = 2 // untyped integer -> float64
f = 1e123 // untyped floating-point -> float64
f = ‘a’ // untyped rune -> float64
The statements above are thus equivalent to these:
var f float64 = float64(3 + 0i)
f = float64(2)
f = float64(1e123)
f = float64(‘a’)
constant之间转化要考虑是否有可能溢出：
Whether implicit or explicit, converting a constant from one type to another requires that the target type can represent the original value. Rounding is allowed for real and complex floating-point numbers:
const (
deadbeef = 0xdeadbeef // untyped int with value 3735928559
a = uint32(deadbeef) // uint32 with value 3735928559
b = float32(deadbeef) // float32 with value 3735928576 (rounded up)
c = float64(deadbeef) // float64 with value 3735928559 (exact)
d = int32(deadbeef) // compile error: constant overflows int32
e = float64(1e309) // compile error: constant overflows float64
f = uint(-1) // compile error: constant underflows uint )
要注意把untyped constant赋值给变量时，变量类型的选择。
In a variable declaration without an explicit type (including short variable declarations), the flavor of the untyped constant implicitly determines the default type of the variable, as in these examples:
i := 0 // untyped integer; implicit int(0)
r := ‘\000’ // untyped rune; implicit rune(‘\000’)
f := 0.0 // untyped floating-point; implicit float64(0.0)
c := 0i // untyped complex; implicit complex128(0i)
Note the asymmetry: untyped integers are converted to int, whose size is not guaranteed, but untyped floating-point and complex numbers are converted to the explicitly sized types float64 and complex128. The language has no unsized float and complex types analogous to unsized int, because it is very difficult to write correct numerical algorithms without knowing the size of one’s floating-point data types.
To give the variable a different type, we must explicitly convert the untyped constant to the desired type or state the desired type in the variable declaration, as in these examples:
var i = int8(0)
var i int8 = 0
These defaults are particularly important when converting an untyped constant to an interface value since they determine its dynamic type.
fmt.Printf(“%T\n”, 0) // “int”
fmt.Printf(“%T\n”, 0.0) // “float64”
fmt.Printf(“%T\n”, 0i) // “complex128”
fmt.Printf(“%T\n”, ‘\000’) // “int32” (rune)
| 27.715596 | 612 | 0.767075 | eng_Latn | 0.962676 |
22e20f032391de4d20b52bfd4909a851ad0a11f8 | 786 | md | Markdown | _posts/2016-12-17-Anna-Elyse-Pencil-Skirt-with-Simple-Tank-Bodice.md | hyperdressyou/hyperdressyou.github.io | 9849173bcaac57aa413f9b885975103e554300f1 | [
"MIT"
] | null | null | null | _posts/2016-12-17-Anna-Elyse-Pencil-Skirt-with-Simple-Tank-Bodice.md | hyperdressyou/hyperdressyou.github.io | 9849173bcaac57aa413f9b885975103e554300f1 | [
"MIT"
] | null | null | null | _posts/2016-12-17-Anna-Elyse-Pencil-Skirt-with-Simple-Tank-Bodice.md | hyperdressyou/hyperdressyou.github.io | 9849173bcaac57aa413f9b885975103e554300f1 | [
"MIT"
] | null | null | null | ---
layout: post
date: 2016-12-17
title: "Anna Elyse Pencil Skirt with Simple Tank Bodice"
category: Anna Elyse
tags: [Anna Elyse]
---
### Anna Elyse Pencil Skirt with Simple Tank Bodice
Just **$289.99**
###
<table><tr><td>BRANDS</td><td>Anna Elyse</td></tr></table>
<a href="https://www.readybrides.com/en/anna-elyse/86799-anna-elyse-pencil-skirt-with-simple-tank-bodice.html"><img src="//img.readybrides.com/225925/anna-elyse-pencil-skirt-with-simple-tank-bodice.jpg" alt="Anna Elyse Pencil Skirt with Simple Tank Bodice" style="width:100%;" /></a>
<!-- break -->
Buy it: [https://www.readybrides.com/en/anna-elyse/86799-anna-elyse-pencil-skirt-with-simple-tank-bodice.html](https://www.readybrides.com/en/anna-elyse/86799-anna-elyse-pencil-skirt-with-simple-tank-bodice.html)
| 49.125 | 283 | 0.729008 | kor_Hang | 0.147559 |
22e31e6dbc6979422e2ae2fc809ead6d06b07fc2 | 2,558 | md | Markdown | docs/outlook/mapi/imapiviewcontext-setadvisesink.md | MicrosoftDocs/office-developer-client-docs.pt-BR | 7b878649ac5b6a1113bf06b099adffa17c956c16 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2020-05-19T18:52:31.000Z | 2021-04-21T00:13:46.000Z | docs/outlook/mapi/imapiviewcontext-setadvisesink.md | MicrosoftDocs/office-developer-client-docs.pt-BR | 7b878649ac5b6a1113bf06b099adffa17c956c16 | [
"CC-BY-4.0",
"MIT"
] | 4 | 2021-12-08T02:35:59.000Z | 2021-12-08T02:53:43.000Z | docs/outlook/mapi/imapiviewcontext-setadvisesink.md | MicrosoftDocs/office-developer-client-docs.pt-BR | 7b878649ac5b6a1113bf06b099adffa17c956c16 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2019-10-13T18:19:41.000Z | 2021-11-25T00:39:27.000Z | ---
title: IMAPIViewContextSetAdviseSink
manager: soliver
ms.date: 03/09/2015
ms.audience: Developer
ms.topic: reference
ms.prod: office-online-server
ms.localizationpriority: medium
api_name:
- IMAPIViewContext.SetAdviseSink
api_type:
- COM
ms.assetid: 4799084a-b5d1-48c3-a889-b2f0e9d68c30
description: 'Última modificação: 9 de março de 2015'
ms.openlocfilehash: a62c3edce79349e748620d82e7b18d482dfdb187
ms.sourcegitcommit: a1d9041c20256616c9c183f7d1049142a7ac6991
ms.translationtype: MT
ms.contentlocale: pt-BR
ms.lasthandoff: 09/24/2021
ms.locfileid: "59625277"
---
# <a name="imapiviewcontextsetadvisesink"></a>IMAPIViewContext::SetAdviseSink
**Aplica-se a**: Outlook 2013 | Outlook 2016
Gerencia o registro de um formulário para receber notificações sobre alterações no visualizador.
```cpp
HRESULT SetAdviseSink(
LPMAPIFORMADVISESINK pmvns
);
```
## <a name="parameters"></a>Parâmetros
_pmvns_
> [in] Ponteiro para um formulário aconselha o objeto sink ou NULL.
## <a name="return-value"></a>Valor de retorno
S_OK
> O registro ou cancelamento para notificação de formulário foi bem-sucedido.
## <a name="remarks"></a>Comentários
Os objetos form chamam o método **IMAPIViewContext::SetAdviseSink** para registrar-se para saber mais sobre as alterações no visualizador de formulário ou cancelar um registro anterior. Quando _os pmvns_ são definidos como NULL, o formulário deseja cancelar um registro. Quando _os pmvns_ apontam para um pia de aviso de formulário válido, o formulário deseja registrar-se para notificações futuras.
## <a name="notes-to-implementers"></a>Observações para implementadores
Quando **SetAdviseSink** incluir um ponteiro do pia de aviso de formulário, mantenha uma referência a ele até que outra chamada **SetAdviseSink** seja feita para cancelar a notificação. Envie uma notificação quando ocorrer uma alteração no visualizador e quando você estiver carregando uma nova mensagem.
Para obter mais informações, consulte [Enviando e recebendo notificações de formulário.](sending-and-receiving-form-notifications.md)
## <a name="mfcmapi-reference"></a>Referência do MFCMAPI
Para ver códigos de exemplo do MFCMAPI, confira a tabela a seguir.
|**Arquivo**|**Função**|**Comentário**|
|:-----|:-----|:-----|
|MyMAPIFormViewer.cpp <br/> |CMyMAPIFormViewer::SetAdviseSink <br/> |MFCMAPI implementa o **método IMAPIViewContext::SetAdviseSink** nesta função. <br/> |
## <a name="see-also"></a>Confira também
[MFCMAPI como exemplo de código](mfcmapi-as-a-code-sample.md)
| 35.527778 | 402 | 0.767787 | por_Latn | 0.985113 |
22e33f17787c94a160bba12059193a8f3962e882 | 422 | md | Markdown | src/_posts/paperfaces/2012-12-10-a-farlow44-portrait.md | blogtips/blogtips.github.io | a442590c36da2fca8e409fb20f151e111154052e | [
"MIT"
] | null | null | null | src/_posts/paperfaces/2012-12-10-a-farlow44-portrait.md | blogtips/blogtips.github.io | a442590c36da2fca8e409fb20f151e111154052e | [
"MIT"
] | null | null | null | src/_posts/paperfaces/2012-12-10-a-farlow44-portrait.md | blogtips/blogtips.github.io | a442590c36da2fca8e409fb20f151e111154052e | [
"MIT"
] | null | null | null | ---
title: "High contrast blue and yellow composition"
excerpt: "PaperFaces portrait of @A_Farlow44 drawn with Paper by 53 on an iPad."
image:
feature: paperfaces-a-farlow44-twitter-lg.jpg
thumb: paperfaces-a-farlow44-twitter-150.jpg
tags: [portrait, illustration, Paper by 53, beard]
---
PaperFaces portrait of project donator [@A_Farlow44](http://twitter.com/A_Farlow44).
{% include boilerplate/paperfaces.html %} | 35.166667 | 84 | 0.763033 | eng_Latn | 0.798728 |
22e33f41977b1d33fc0d4ae9f6a97eb0569af413 | 778 | md | Markdown | README.md | thrillfall/SimpleBitcoinWidget | 35bf4e8a136cbfdc4167f3f4933a5df0cb29fdbb | [
"MIT"
] | 3 | 2018-08-08T20:03:11.000Z | 2019-04-22T11:45:14.000Z | README.md | thrillfall/SimpleBitcoinWidget | 35bf4e8a136cbfdc4167f3f4933a5df0cb29fdbb | [
"MIT"
] | null | null | null | README.md | thrillfall/SimpleBitcoinWidget | 35bf4e8a136cbfdc4167f3f4933a5df0cb29fdbb | [
"MIT"
] | null | null | null | # Simple Bitcoin Widget
Clean, simple cryptocurrency widget for Android.
<a href='https://play.google.com/store/apps/details?id=com.brentpanther.bitcoinwidget&pcampaignid=MKT-Other-global-all-co-prtnr-py-PartBadge-Mar2515-1'><img alt='Get it on Google Play' src='https://play.google.com/intl/en_us/badges/images/generic/en_badge_web_generic.png' height="80pt"/></a>
<a href="http://fdroid.org/packages/com.brentpanther.bitcoinwidget/">
<img src="https://f-droid.org/badge/get-it-on.png"
alt="Get it on F-Droid" height="80">
</a>
## License
This software has an MIT License. All forks of this codebase have my authorization to be released on Google Play and other app stores.
## Donations
Donation can be made by Bitcoin to 194QqhXirp21F5fJVaqviMeHkzZzkZKyi8
| 40.947368 | 292 | 0.758355 | eng_Latn | 0.469606 |
22e35752256b73cdfcdd0c135fc80b80d50d54b4 | 294 | md | Markdown | README.md | rychly/openwrt-packages | da17a9850997b53f65f47dbdf68d55ef6222d418 | [
"Apache-2.0"
] | null | null | null | README.md | rychly/openwrt-packages | da17a9850997b53f65f47dbdf68d55ef6222d418 | [
"Apache-2.0"
] | null | null | null | README.md | rychly/openwrt-packages | da17a9850997b53f65f47dbdf68d55ef6222d418 | [
"Apache-2.0"
] | null | null | null | # OpenWrt packages
https://rychly-edu.gitlab.io/openwrt-packages/
Custom packages for OpenWrt (source code and builds).
## Dependencies
For building the OpenWrt packages, it is recommended to use the [OpenWrt SDK in a Docker image](https://gitlab.com/rychly-edu/docker/docker-openwrt-sdk).
| 29.4 | 153 | 0.77551 | eng_Latn | 0.7454 |
22e501543d9edb3b1a50e73de5dc4998ff02f49b | 2,062 | md | Markdown | rules/customization-do-you-enable-your-contacts-to-have-more-than-the-default-3-email-addresses-and-phone-numbers/rule.md | chrishoogwerf/SSW.Rules.Content | 846d2c381dc9b1aabdf1a5bc41c5efd816699f09 | [
"CC0-1.0"
] | null | null | null | rules/customization-do-you-enable-your-contacts-to-have-more-than-the-default-3-email-addresses-and-phone-numbers/rule.md | chrishoogwerf/SSW.Rules.Content | 846d2c381dc9b1aabdf1a5bc41c5efd816699f09 | [
"CC0-1.0"
] | null | null | null | rules/customization-do-you-enable-your-contacts-to-have-more-than-the-default-3-email-addresses-and-phone-numbers/rule.md | chrishoogwerf/SSW.Rules.Content | 846d2c381dc9b1aabdf1a5bc41c5efd816699f09 | [
"CC0-1.0"
] | null | null | null | ---
type: rule
archivedreason:
title: Customization - Do you enable your contacts to have more than the default 3 email addresses and phone numbers?
guid: 8f91c1c2-5746-4142-b46a-11ef7d2d322b
uri: customization-do-you-enable-your-contacts-to-have-more-than-the-default-3-email-addresses-and-phone-numbers
created: 2012-12-10T20:02:07.0000000Z
authors:
- title: Adam Cogan
url: https://ssw.com.au/people/adam-cogan
related: []
redirects: []
---
Out of the box CRM4 only enables a contact to have 3 phone numbers (home, business and mobile) + 3 email addresses (but only one visible). A customization that almost everyone needs is to remove this limitation (to allow contacts to have an unlimited amount of phone numbers and email addresses).
<!--endintro-->
::: bad
:::
There are a few customizations needed to get the SSW Contact Makeover:
* Show some hidden fields
* Make some form changes to move to a new tab
* Make a CRM frame (to add in a subform)
* Add some entities
* Add some form java script to hide the core Contact Details? tab when a user is
entering a new contact
::: good
:::
::: good
:::
Q: So what is the end result?
A: The end user experience to add a phone number is ..
| 37.490909 | 297 | 0.706596 | eng_Latn | 0.988298 |
22e5d0086624a6d1845cc61e1f7ea0efd78686c2 | 63 | md | Markdown | CHANGELOG.md | joaolucasl/akka-kotlin | 8cf9ab5bf09add650910a1ca2b946708bb00017f | [
"Apache-2.0"
] | 22 | 2017-01-14T16:54:06.000Z | 2018-06-02T22:19:39.000Z | CHANGELOG.md | joaolucasl/akka-kotlin | 8cf9ab5bf09add650910a1ca2b946708bb00017f | [
"Apache-2.0"
] | null | null | null | CHANGELOG.md | joaolucasl/akka-kotlin | 8cf9ab5bf09add650910a1ca2b946708bb00017f | [
"Apache-2.0"
] | 6 | 2017-08-11T04:10:08.000Z | 2018-02-19T10:53:40.000Z | # 0.1
* Basic Extensions that covered Hello-World application. | 31.5 | 57 | 0.777778 | eng_Latn | 0.960356 |
22e60f5f000b3a9bda6a8e3ee055e5d9ed214014 | 4,989 | md | Markdown | README.md | saimj7/Video-Classification-in-Real-Time | 49215a74eaff6f476a14595498a4e54f0c05edf2 | [
"Apache-2.0"
] | 2 | 2020-10-31T11:16:36.000Z | 2021-09-03T03:28:51.000Z | README.md | saimj7/Video-Classification-in-Real-Time | 49215a74eaff6f476a14595498a4e54f0c05edf2 | [
"Apache-2.0"
] | 3 | 2020-11-02T22:49:00.000Z | 2021-06-03T13:28:49.000Z | README.md | saimj7/Video-Classification-in-Real-Time | 49215a74eaff6f476a14595498a4e54f0c05edf2 | [
"Apache-2.0"
] | 3 | 2020-11-02T22:48:23.000Z | 2022-01-17T21:40:08.000Z | # Video-Classification-in-Real-Time
Video classification using VGG16 as a feature extractor and seasoning with RNN. Dataset used is UCF101 (Cricket bowling and batting classes).
> A simple RNN is used to better classify temporal frame sequences from videos.
Cricket batting | Cricket batting/bowling
:-------------------------:|:-------------------------:
 | 
---
> Some of the use cases would be monitoring anomalies, suspicious human actions, alerting the staff/authorities.
## Table of Contents
* [Background Theory](#background-theory)
* [Running Inference](#running-inference)
* [Pipeline](#pipeline)
- [Preprocessing](#preprocessing)
- [Training](#training)
* [References](#references)
* [Next Steps](#next-steps)
## Background Theory
**Feature extraction:**
- Pretrained VGG16 is used as a feature extractor after fine tuning/unfreezing its 4 top layers.
- A simple classifier is then connected to VGG16 and trained to identify if the frame belongs to class1 or 2.
- Then the top classifier is disconnected and only dense layer with 1024 output size is used to obtain the sparse representations of each frame.
- **Data to lstm format:** For each video frame, the sparse representations are stacked into a tensor of size (NUM_FRAMES, LOOK_BACK, 1024).
<div align="center">
<img src="https://github.com/saimj7/Video-Classification-in-Real-Time/blob/master/mylib/misc/model.jpg" width=570>
<p>- Model architecture -</p>
</div>
---
**RNN:**
- A standard LSTM is used. Note that you need GPU/CUDA support if you would like to run CUDnnLSTM layers in the model.
- Finally, the LSTM network is trained to distinguish between your desired class1 and 2 videos.
## Running Inference
- Install all the required Python dependencies:
```
pip install -r requirements.txt
```
- To run inference either on a test video file or on webcam:
```
python run.py
```
- Note that the inference is set on the test video file by default.
- To change it, simply set ``` FROM_WEBCAM = True ``` in the config. options at mylib/Config.py
- Trained model weights (for this example) can be downloaded from [**here**](https://drive.google.com/file/d/1mGm9jnZhelskbSzYAWWQoNcGa3mz95OL/view?usp=drivesdk). Make sure you extract them into the folder 'weights'.
- The class probabilities and inference time per frames is also displayed:
```
[INFO] Frame acc. predictions: 0.91895014
Frame inference in 0.0030 seconds
```
- You can also chose to send prediction accuracies over the mail if desired. Follow the instructions in mylib>Mailer.py (to setup the sender mail).
- Enter the receiver mail in the config. options at mylib/Config.py
<div align="center">
<img src="https://github.com/saimj7/Video-Classification-in-Real-Time/blob/master/mylib/misc/alert.jpg" width=500>
<p>- Predictions alert -</p>
</div>
- In case of severe false positivies, make sure to optimize the threshold and positive_frames parameters to further narrow down the predictions. Please refer config.
```
Threshold = 0.50
if pred >= Threshold:
```
```
if total_frames > 5:
print('[INFO] Sending mail...')
```
## Pipeline
### Preprocessing:
- Some image processing is required before training on your own data!
- In 'Preprocessing.ipynb' file, the frames from each video classes are extracted and sorted into respective folders.
- Note that the frames are resized to 224x224 dimensions (which is VGG16 input layer size).
- The dataset can be downloaded from [**here**](https://www.crcv.ucf.edu/data/UCF101.php).
### Training:
- 'Train.ipynb', as the name implies trains your model.
- Training is visualized with the help of TensorBoard. Use the command:
```
tensorboard --logdir data/_training_logs/rnn
```
<div align="center">
<img src="https://github.com/saimj7/Video-Classification-in-Real-Time/blob/master/mylib/misc/train.jpg" width=470>
<p>- Training accuracy -</p>
</div>
- Make sure to review the parameters in config. options at mylib/Config.py
- You will come across the parameters in Train.ipynb, they must be same during the training and inference.
- If you would like to change them, simply do so in the training file and also in config. options.
## References
***Main:***
- VGG16 paper: https://arxiv.org/pdf/1409.1556.pdf
- UCF101 Action Recognition Data Set: https://www.crcv.ucf.edu/data/UCF101.php
***Optional:***
- TensorBoard: https://www.tensorflow.org/tensorboard
## Next steps
- Investigate and benchmark different RNN architectures for better classifying the temporal sequences.
<p> </p>
---
## Thanks for the read & have fun!
> To get started/contribute quickly (optional) ...
- **Option 1**
- 🍴 Fork this repo and pull request!
- **Option 2**
- 👯 Clone this repo:
```
$ git clone https://github.com/saimj7/Action-Recognition-in-Real-Time.git
```
- **Roll it!**
---
saimj7/ 06-09-2020 © <a href="http://saimj7.github.io" target="_blank">Sai_Mj</a>.
| 36.683824 | 216 | 0.7274 | eng_Latn | 0.952573 |
22e63d2ffd3d954a8afba945c46502fd9d644982 | 797 | md | Markdown | README.md | magesa/Simple-MEAN-App-With-User-Authentication | d93d6e59e2181bf62f7796ebb611de51c85145d7 | [
"MIT"
] | null | null | null | README.md | magesa/Simple-MEAN-App-With-User-Authentication | d93d6e59e2181bf62f7796ebb611de51c85145d7 | [
"MIT"
] | null | null | null | README.md | magesa/Simple-MEAN-App-With-User-Authentication | d93d6e59e2181bf62f7796ebb611de51c85145d7 | [
"MIT"
] | null | null | null | # Simple MEAN Stack App With User Authentication
This is an implementation of a Simple MEAN Stack App with user authentication.
This application consists of a the following pages.
- Home page.
- Registration page.
- Login page.
- Logout page.
Passport is used for user authentication, while express-handlebars is used as the template engine.
[](https://www.wikiwand.com/en/MEAN_(software_bundle))
| 46.882353 | 160 | 0.500627 | eng_Latn | 0.891322 |
22e694b7b344619365b10312f9f320b31dae3eb9 | 216 | md | Markdown | _drafts/Packages-Parameters-and-MsDeploy.md | jamescrowley/jamescrowley.net | 2cbd491229e2d655935a928cfcbab1e274a0a0fb | [
"MIT"
] | null | null | null | _drafts/Packages-Parameters-and-MsDeploy.md | jamescrowley/jamescrowley.net | 2cbd491229e2d655935a928cfcbab1e274a0a0fb | [
"MIT"
] | null | null | null | _drafts/Packages-Parameters-and-MsDeploy.md | jamescrowley/jamescrowley.net | 2cbd491229e2d655935a928cfcbab1e274a0a0fb | [
"MIT"
] | null | null | null | ---
id: 166
title: Packages, Parameters and MsDeploy
date: 2011-04-28T22:46:36+00:00
author: james.crowley
layout: post
guid: http://www.jamescrowley.co.uk/?p=166
permalink: /?p=166
categories:
- Uncategorized
---
| 18 | 42 | 0.726852 | eng_Latn | 0.195368 |
22e805c4fcfc85efc66d5fda7f5042279b6e9d78 | 38 | md | Markdown | README.md | Speculative/diary.py | 66c69982bb303c6d1aa72bfec437b0cac401a762 | [
"MIT"
] | null | null | null | README.md | Speculative/diary.py | 66c69982bb303c6d1aa72bfec437b0cac401a762 | [
"MIT"
] | null | null | null | README.md | Speculative/diary.py | 66c69982bb303c6d1aa72bfec437b0cac401a762 | [
"MIT"
] | null | null | null | diary.py
========
Command line diary
| 7.6 | 18 | 0.605263 | eng_Latn | 0.953517 |
22e8d854cec4254e250dc8490abde945a16f119b | 243 | md | Markdown | README.md | herpiko/enymind-liveresults | f4f224e81e8258c281815a47ce93a0b90174b358 | [
"MIT"
] | 1 | 2015-07-27T18:58:12.000Z | 2015-07-27T18:58:12.000Z | README.md | herpiko/enymind-liveresults | f4f224e81e8258c281815a47ce93a0b90174b358 | [
"MIT"
] | null | null | null | README.md | herpiko/enymind-liveresults | f4f224e81e8258c281815a47ce93a0b90174b358 | [
"MIT"
] | null | null | null | # enymind-liveresults
Third party client for enymind live result
http://wiki.enymind.fi/index.php/ChronoLive_API
To use the rest API, you should ask enymind's support to enable CORS on your own enymind's subdomain, for api.php and ajax.php.
| 34.714286 | 127 | 0.790123 | eng_Latn | 0.747581 |
22e903b35abb520c1bd30c02dda2ccf79e7a5c82 | 21,361 | md | Markdown | src/docs/privacy-policy.md | kubebuild/docs.kubebuild.com | 811cfb5b60204ffd50a14148a271caf38f92eece | [
"MIT"
] | 2 | 2018-10-23T06:58:38.000Z | 2018-12-06T15:50:08.000Z | src/docs/privacy-policy.md | kubebuild/docs.kubebuild.com | 811cfb5b60204ffd50a14148a271caf38f92eece | [
"MIT"
] | 1 | 2018-12-04T00:41:15.000Z | 2018-12-04T12:12:11.000Z | src/docs/privacy-policy.md | kubebuild/docs.kubebuild.com | 811cfb5b60204ffd50a14148a271caf38f92eece | [
"MIT"
] | null | null | null | ---
path: "/privacy-policy"
date: "2018-09-19"
title: "Privacy Policy"
---
1. Purpose Of Our Policy
---------------------
1. Meerkat Technologies Pty Ltd ABN 29 607 238 282 (**we**, **us** or **our**) has adopted this Privacy Policy to ensure that we have standards in place to protect the Personal Information that we collect about individuals that is necessary and incidental to:
1. Providing the system and services that we offer; and
2. The normal day-to-day operations of our business.
2. This Privacy Policy follows the standards of both:
1. The Australian Privacy Principles set by the Australian Government for the handling of Personal Information under the Privacy Act 1988 (Cth) (**Privacy Act**); and
2. The regulations and principles set by the European Union's General Data Protection Regulation (GDPR) for the handling of Personal Data.
3. By publishing this Privacy Policy we aim to make it easy for our customers and the public to understand what Personal Information we collect and store, why we do so, how we receive, obtain, store and/or use that information, and the rights of control an individual has with respect to their Personal Information in our possession.
2. Who And What This Policy Applies To
-----------------------------------
1. Our Privacy Policy deals with how we handle "personal information" and "personal data" as it is defined in the Privacy Act and the GDPR respectively (**Personal Information**).
2. We handle Personal Information in our own right and also for and on behalf of our customers and users.
3. Our Privacy Policy does not apply to information we collect about businesses or companies, however it does apply to information about the people in those businesses or companies which we store.
4. The Privacy Policy applies to all forms of information, physical and digital, whether collected or stored electronically or in hardcopy.
5. If, at any time, an individual provides Personal Information or other information about someone other than himself or herself, the individual warrants that they have that person's consent to provide such information for the purpose specified.
6. We consider the protection of privacy of children very important. Our services are not directed to children under the age of 16, and we do not knowingly collect personal data from children under the age of 16 without obtaining parental consent. If an individual is under 16 years of age, then they should not use or access the service at any time or in any manner. If we learn that Personal Information has been collected on the service from persons under 16 years of age and without verifiable parental consent, then we will take the appropriate steps to delete such information.
3. The Information We Collect
--------------------------
1. In the course of business it is necessary for us to collect Personal Information. This information allows us to identify who an individual is for the purposes of our business, share Personal Information when asked of us, contact the individual in the ordinary course of business and transact with the individual. Without limitation, the type of information we may collect is:
1. **Personal Information.** We may collect personal details such as an individual's name, location, date of birth, nationality, family details and other information defined as "Personal Information" in the Privacy Act that allows us to identify who the individual is;
2. **Contact Information.** We may collect information such as an individual's email address, telephone & fax number, third-party usernames, residential, business and postal address and other information that allows us to contact the individual;
3. **Financial Information.** We may collect financial information related to an individual such as any bank or credit card details used to transact with us and other information that allows us to transact with the individual and/or provide them with our services;
4. **Statistical Information.** We may collect information about an individual's online and offline preferences, habits, movements, trends, decisions, associations, memberships, finances, purchases and other information for statistical purposes; and
5. **Information an individual sends us.** We may collect any personal correspondence that an individual sends us, or that is sent to us by others about the individual's activities.
2. We may collect other Personal Information about an individual, which we will maintain in accordance with this Privacy Policy.
3. We may also collect non-Personal Information about an individual such as information regarding their computer, network and browser. This may include their IP address. Where non-Personal Information is collected the Australian Privacy Principles and the GDPR do not apply.
4. How Information Is Collected
----------------------------
1. Most information will be collected in association with an individual's use of Buildkite, an enquiry about Buildkite or generally dealing with us. However we may also receive Personal Information from sources such as advertising, an individual's own promotions, public records, mailing lists, contractors, staff, recruitment agencies and our business partners. In particular, information is likely to be collected as follows:
1. **Registrations/Subscriptions.** When an individual registers or subscribes for a service, list, account, connection or other process whereby they enter Personal Information details in order to receive or access something, including a transaction;
2. **Accounts/Memberships.** When an individual submits their details to open an account and/or become a member with us;
3. **Supply.** When an individual supplies us with goods or services;
4. **Contact.** When an individual contacts us in any way;
5. **Access.** When an individual accesses us physically we may require them to provide us with details for us to permit them such access. When an individual accesses us through the internet we may collect information using cookies (if relevant -- an individual can adjust their browser's setting to accept or reject cookies) or analytical services; and/or
6. **Pixel Tags.** Pixel tags enable us to send email messages in a format customers can read and they tell us whether mail has been opened.
2. As there are many circumstances in which we may collect information both electronically and physically, we will endeavour to ensure that an individual is always aware of when their Personal Information is being collected.
3. Where we obtain Personal Information without an individual's knowledge (such as by accidental acquisition from a client) we will either delete/destroy the information, or inform the individual that we hold such information, in accordance with the Australian Privacy Principles and the GDPR.
5. When Personal Information Is Used & Disclosed
---------------------------------------------
1. In general, the primary principle is that we will not use any Personal Information other than for the purpose for which it was collected other than with the individual's permission. The purpose of collection is determined by the circumstances in which the information was collected and/or submitted.
2. We will only process Personal Information when we can identify a lawful basis to do so. It is always our responsibility to ensure that we can demonstrate which lawful basis applies to the particular processing purpose.
3. The most common lawful bases relied upon are:
1. **Consent:** we will only rely upon express, clear and informed consent. Any consent provided may specify and/or restrict the purpose, and can be withdrawn at any time without penalty. We will keep a record of when and how we got consent from an individual.
2. **Legitimate interests:** we will only rely upon an identifiable legitimate interest where we can demonstrate that the processing of Personal Information is necessary to achieve it by balancing it against the individual's interests, rights and freedoms. We will keep a record of our legitimate interests assessments.
4. We will retain Personal Information for the period necessary to fulfil the purposes outlined in this Privacy Policy unless a longer retention period is required or permitted by law.
5. If it is necessary for us to disclose an individual's Personal Information to third parties in a manner compliant with the Australian Privacy Principles and the GDPR in the course of our business, we will inform you that we intend to do so, or have done so, as soon as practical.
6. We will not disclose or sell an individual's Personal Information to unrelated third parties under any circumstances, unless the prior written consent of the individual is obtained.
7. Information is used to enable us to operate our business, especially as it relates to an individual. This may include:
1. The provision of goods and services between an individual and us;
2. Verifying an individual's identity;
3. Communicating with an individual about:
4. Their relationship with us;
5. Our goods and services;
6. Our own marketing and promotions to customers and prospects;
7. Competitions, surveys and questionnaires;
8. Investigating any complaints about or made by an individual, or if we have reason to suspect that an individual is in breach of any of our terms and conditions or that an individual is or has been otherwise engaged in any unlawful activity; and/or
9. As required or permitted by any law (including the Privacy Act).
8. The individual shall have the right to object at any time to the processing of their Personal Information for direct marketing purposes, which includes profiling to the extent that it is related to such direct marketing. If we receive such a request, we will stop the processing of Personal Information for direct marketing purposes immediately without charge or penalty.
9. There are some circumstances in which we must disclose an individual's information:
1. Where we reasonably believe that an individual may be engaged in fraudulent, deceptive or unlawful activity that a governmental authority should be made aware of;
2. As required by any law (including the Privacy Act); and/or
3. In order to sell our business (in that we may need to transfer Personal Information to a new owner).
10. We will not disclose an individual's Personal Information to any entity outside of Australia that is in a jurisdiction that does not have a similar regime to the Australian Privacy Principles or an implemented and enforceable privacy policy similar to this Privacy Policy. We will take reasonable steps to ensure that any disclosure to an entity outside of Australia will not be made until that entity has agreed in writing with us to safeguard Personal Information as we do.
11. We may utilise third-pay service providers (such as Gmail from Google, Inc., and MailChimp from The Rocket Science Group LLC) to communicate with an individual and to store contact details about an individual. These service providers are located in the United States of America. No Health Information is stored in any third-party services in Australia or elsewhere.
12. An individual who uses Buildkite will be sending information (including Personal Information) to the United States of America where our servers are located. That information may then be transferred within the United States of America or back out of the United States of America to other countries outside of the individual's country of residence, depending on the type of information and how it is stored by us. These countries may not necessarily have data protection laws as comprehensive or protective as those in your country of residence, however our collection, storage and use of Personal Information will at all times continue to be governed by this Privacy Policy.
6. Opting "In" Or "Out"
--------------------
1. An individual may opt to not have us collect and/or process their Personal Information. This may prevent us from offering them some or all of our services and may terminate their access to some or all of the services they access with or through us. They will be aware of this when:
1. **Opt In.** Where relevant, the individual will have the right to choose to have information collected and/or receive information from us (for clarity, consent must involve an unambiguous positive action to opt in); or
2. **Opt Out.** Where relevant, the individual will have the right to choose to exclude himself or herself from some or all collection of information and/or receiving information from us.
2. If an individual believes that they have received information from us that they did not opt in or out to receive, they should contact us on the details below.
7. The Safety & Security Of Personal Information
---------------------------------------------
1. We have appointed a Data Protection Officer to oversee the management of this Privacy Policy and compliance with the Australian Privacy Principles and the Privacy Act and the GDPR. This officer may have other duties within our business and also be assisted by internal and external professionals and advisors.
2. We will take all reasonable precautions to protect an individual's Personal Information from unauthorised access. This includes appropriately securing our physical facilities and electronic networks.
3. Buildkite uses SSL encryption to store and transfer Personal Information. Despite this, the security of online transactions and the security of communications sent by electronic means or by post cannot be guaranteed. Each individual that provides information to us via the internet or by post does so at their own risk. We cannot accept responsibility for misuse or loss of, or unauthorised access to, Personal Information where the security of information is not within our control.
4. We are not responsible for the privacy or security practices of any third party (including third parties that we are permitted to disclose an individual's Personal Information to in accordance with this policy or any applicable laws), unless otherwise required by the Privacy Act and the GDPR. The collection and use of an individual's information by such third parties may be subject to separate privacy and security policies.
5. If an individual suspects any misuse or loss of, or unauthorised access to, their Personal Information, they should let us know immediately.
6. We are not liable for any loss, damage or claim arising out of another person's use of the Personal Information where we were authorised to provide that person with the Personal Information.
7. Where there is a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, Personal Information, then:
1. We will immediately establish the likelihood and severity of the resulting risk to wider rights and freedoms of natural persons;
2. If we determine there is a risk from the security breach, then we will immediately notify the relevant supervisory authority and provide all relevant information on the particular breach, and by no later than 72 hours after having first become aware of the breach;
3. If we determine there is a high risk from the security breach (a higher threshold than set for notifying supervisory authorities), we will immediately notify the affected individuals and provide all relevant information on the particular breach without undue delay.
8. We will document the facts relating to any security breach, its effects and the remedial action taken, and investigate the cause of the breach and how to prevent similar situations in the future.
8. How To Access, Update and/or Remove Information
-----------------------------------------------
1. Users of Buildkite can update their Personal Information from within Buildkite at any time to ensure it is accurate and complete.
2. Subject to the Australian Privacy Principles and the GDPR, an individual has the right to request from us the Personal Information that we have about them, and we have an obligation to provide them with such information as soon as practicable, and by no later than 28 days of receiving the written request. The individual is free to retain and reuse their Personal Information for their own purposes. We may be required to transmit the Personal Information directly to another organisation if this is technically feasible.
3. If an individual cannot update its own information, we will correct any errors in the Personal Information we hold about an individual within 28 days of receiving written notice from them about those errors, or two months where the request for rectification is complex.
4. It is an individual's responsibility to provide us with accurate and truthful Personal Information. We cannot be liable for any information that is provided to us that is incorrect.
5. Where a request to access Personal Information is manifestly unfounded, excessive and/or repetitive, we may refuse to respond or charge an individual a reasonable fee for our costs incurred in meeting any of their requests to disclose the Personal Information we hold about them. Where we refuse to respond to a request, we will explain why to the individual, informing them of their right to complain to the supervisory authority and to a judicial remedy without undue delay and at the latest within 28 days.
6. We may be required to delete or remove all Personal Information we have on an individual upon request in the following circumstances:
1. Where the Personal Information is no longer necessary in relation to the purpose for which it was originally collected and/or processed;
2. When the individual withdraws consent;
3. When the individual objects to the processing and there is no overriding legitimate interest for continuing the processing;
4. The processing of the Personal Information was otherwise in breach of the GDPR;
5. The Personal Information has to be erased in order to comply with a legal obligation; and/or
6. The Personal Information is in relation to a child.
7. We may refuse to delete or remove all Personal Information we have on an individual where the Personal Information was processed for the following reasons:
1. To exercise the right of freedom of expression and information;
2. To comply with a legal obligation for the performance of a public interest task or exercise of official authority.
3. For public health purposes in the public interest;
4. Archiving purposes in the public interest, scientific research historical research or statistical purposes; or
5. The exercise or defence of legal claims.
9. Complaints And Disputes
-----------------------
1. If an individual has a complaint about our handling of their Personal Information, they should address their complaint in writing to the details below.
2. If we have a dispute regarding an individual's Personal Information, we both must first attempt to resolve the issue directly between us.
3. An individual shall have the right to seek a judicial remedy where he or she considers that his or her rights under the GDPR have been infringed as a result of the processing of his or her Personal Information in non-compliance with the GDPR. Any proceedings should be commenced in Victoria, Australia, where we are established.
4. If we become aware of any unauthorised access to an individual's Personal Information we will inform them at the earliest practical opportunity once we have established what was accessed and how it was accessed.
10. Contacting Individuals
----------------------
1. From time to time, we may send an individual important notices, such as changes to our terms, conditions and policies. Where such information is materially important to the individual's interaction with us, they may not opt out of receiving these communications.
11. Contacting Us
-------------
1. All correspondence with regards to privacy should be addressed to:\
Data Protection Officer\
Meerkat Technologies Pty Ltd\
C/- General Standards\
GPO Box 3393\
Melbourne VIC 3000\
[email protected]\
You may contact the Data Protection Officer by email in the first instance.
12. Additions To This Policy
------------------------
1. If we decide to change this Privacy Policy, we will post the changes on our webpage at https://docs.kubebuild.com/privacy-policy. Please refer back to this Privacy Policy to review any amendments.
2. We may do things in addition to what is stated in this Privacy Policy to comply with the Australian Privacy Principles and the GDPR, and nothing in this Privacy Policy shall deem us to have not complied with the Australian Privacy Principles and the GDPR. | 145.312925 | 681 | 0.766958 | eng_Latn | 0.999836 |
22eb540bb9528cbcd311c4cb323bdf51c96b72dd | 172 | md | Markdown | README.md | KtoZ/sample-expressjs-sequelize-postgresql-heroku | d6fc14176c3f4287383738c15406d1caba382903 | [
"MIT"
] | null | null | null | README.md | KtoZ/sample-expressjs-sequelize-postgresql-heroku | d6fc14176c3f4287383738c15406d1caba382903 | [
"MIT"
] | null | null | null | README.md | KtoZ/sample-expressjs-sequelize-postgresql-heroku | d6fc14176c3f4287383738c15406d1caba382903 | [
"MIT"
] | 1 | 2021-05-01T10:45:13.000Z | 2021-05-01T10:45:13.000Z | # sample-expressjs-sequelize-postgresql-heroku
[Express.js + Sequelize ORM + PostgreSQL を使って Heroku にデプロイ - Qiita](https://qiita.com/KoKeCross/items/144949ba03e5138fc6d5)
| 43 | 123 | 0.802326 | kor_Hang | 0.267242 |
22eb754845152c40ace36f5465729c87fc04e914 | 208 | md | Markdown | README.md | dcortes92/do-you-even-fish | 09b6b4d6be32a46ec806181e962172d5cb243883 | [
"MIT"
] | null | null | null | README.md | dcortes92/do-you-even-fish | 09b6b4d6be32a46ec806181e962172d5cb243883 | [
"MIT"
] | null | null | null | README.md | dcortes92/do-you-even-fish | 09b6b4d6be32a46ec806181e962172d5cb243883 | [
"MIT"
] | null | null | null | # Do you even fish
React web app build following the http://reactforbeginners.com tutorial by @wesbos
# Urls
- [GH Pages](https://dcortes92.github.io/do-you-even-fish)
- [Now](https://ns-xmbwmlzakq.now.sh)
| 26 | 82 | 0.730769 | eng_Latn | 0.440282 |
22ebd9f9250a27524e94061b5f312e31f5032679 | 15,268 | md | Markdown | microsoft-edge/devtools-guide-chromium/memory-problems/memory-101.md | OfficeGlobal/edge-developer.de-DE | 07d6e2be46c2ca9fc98a715bf73af430084d91c3 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | microsoft-edge/devtools-guide-chromium/memory-problems/memory-101.md | OfficeGlobal/edge-developer.de-DE | 07d6e2be46c2ca9fc98a715bf73af430084d91c3 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | microsoft-edge/devtools-guide-chromium/memory-problems/memory-101.md | OfficeGlobal/edge-developer.de-DE | 07d6e2be46c2ca9fc98a715bf73af430084d91c3 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-11-23T12:06:38.000Z | 2021-11-23T12:06:38.000Z | ---
title: Speicher Terminologie
author: MSEdgeTeam
ms.author: msedgedevrel
ms.date: 04/03/2020
ms.topic: article
ms.prod: microsoft-edge
keywords: Microsoft Edge, Web-Entwicklung, F12-Tools, devtools
ms.openlocfilehash: e3373cf1475ec0eeaabcebf1a7f49505c7a3c1bb
ms.sourcegitcommit: 50991a04c18283a8890ae33fcc3491c0476c7684
ms.translationtype: MT
ms.contentlocale: de-DE
ms.lasthandoff: 04/30/2020
ms.locfileid: "10611727"
---
<!-- Copyright Meggin Kearney
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
https://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License. -->
# Speicher Terminologie
In diesem Abschnitt werden allgemeine Ausdrücke beschrieben, die in der Speicheranalyse verwendet werden, und Sie gelten für eine Vielzahl von Arbeitsspeicherprofil Tools für verschiedene Sprachen.
Die hier beschriebenen Begriffe und Begriffe beziehen sich auf das [Speicher Panel][DevtoolsMemoryProblemsHeapSnapshots]. Wenn Sie jemals mit dem Java-, .net-oder einem anderen Speicher Profiler gearbeitet haben, ist dies möglicherweise eine Auffrischung.
## Objektgrößen
Denken Sie an Arbeitsspeicher als ein Diagramm mit primitiven Typen \ (wie Zahlen und Zeichenfolgen \) und Objekten \ (assoziative Arrays \). Sie wird möglicherweise visuell als Diagramm mit einer Reihe von miteinander verbundenen Punkten wie folgt dargestellt:
> ##### Abbildung1
> Visuelle Darstellung des Arbeitsspeichers
>![Visuelle Darstellung des Arbeitsspeichers][ImageThinkGraph]
Ein Objekt kann Speicher auf zwei Arten enthalten:
* Direkt vom Objekt.
* Implizit durch Speichern von Verweisen auf andere Objekte, wodurch verhindert wird, dass diese Objekte automatisch von einem Garbage Collector entfernt werden \ (**GC** für Short \).
Bei der Arbeit mit dem [Speicherbereich][DevtoolsMemoryProblemsHeapSnapshots] in devtools \ (ein Tool zur Untersuchung von Speicherproblemen unter "Arbeitsspeicher" \) finden Sie möglicherweise einige verschiedene Informationsspalten. Zwei, die sich hervorheben, sind eine **flache Größe** und eine **Beibehaltungs Größe**, doch was stellen diese dar?
> ##### Abbildung2
> Flache und gespeicherte Größe
>![Flache und gespeicherte Größe][ImageShallowRetained]
### Flache Größe
Dies ist die Größe des Speichers, der vom Objekt gehalten wird.
Typische JavaScript-Objekte verfügen über einen Speicherplatz, der für die Beschreibung reserviert ist, und zum Speichern unmittelbarer Werte. In der Regel können nur Arrays und Zeichenfolgen eine beträchtliche flache Größe aufweisen. Zeichenfolgen und externe Arrays verfügen jedoch häufig über Ihren Hauptspeicher im rendererspeicher, wodurch nur ein kleines Wrapperobjekt auf dem JavaScript-Heap verfügbar gemacht wird.
Der Renderer-Arbeitsspeicher ist der gesamte Arbeitsspeicher des Prozesses, in dem eine geprüfte Seite gerendert wird: nativer Arbeitsspeicher + js-Heapspeicher des Page + js-Heapspeichers aller dedizierten Arbeitskräfte, die von der Seite gestartet wurden. Dennoch kann selbst ein kleines Objekt eine große Menge an Arbeitsspeicher indirekt aufnehmen, indem verhindert wird, dass andere Objekte vom automatischen Garbage Collection-Prozess verworfen werden.
### Beibehaltungs Größe
Hierbei handelt es sich um die Größe des Arbeitsspeichers, der freigegeben wird, sobald das Objekt zusammen mit den abhängigen Objekten gelöscht wird, die aus den **Garbage Collector-Stämmen** (GC-Stämme \) nicht erreichbar sind.
**Garbage Collector-Stämme** \ (GC-Stämme \) bestehen aus **Handles** , die \ (entweder lokal oder Global \) erstellt werden, wenn Sie einen Verweis vom systemeigenen Code auf ein JavaScript-Objekt außerhalb von V8 erstellen. Alle derartigen Handles befinden sich möglicherweise in einem Heap-Snapshot unter **GC-Roots** > -**Handles** und globalen **GC-Stamm** > **Handles**. Die Beschreibung der Handles in dieser Dokumentation, ohne die Details der Browser Implementierung zu untertauchen, ist möglicherweise verwirrend. Sowohl Garbage Collector (GC)-Stämme als auch die Ziehpunkte sind keine Grund zur Sorge.
Es gibt viele interne GC-Stämme, von denen die meisten nicht für die Benutzer interessant sind. Aus Sicht der Anwendungen gibt es folgende Arten von Stämmen:
* Globales Window-Objekt \ (in jedem IFRAME \). In den Heap-Schnappschüssen gibt es ein Entfernungs Feld, bei dem es sich um die Anzahl der Eigenschaftsverweise auf dem kürzesten Beibehaltungs Pfad aus dem Fenster handelt.
* Dokument-DOM-Struktur, bestehend aus allen systemeigenen DOM-Knoten, die durch Durchlaufen des Dokuments erreichbar sind. Nicht alle Knoten können js-Wrapper aufweisen, aber wenn ein Knoten über einen Wrapper verfügt, ist er lebendig, während das Dokument aktiv ist.
* Manchmal werden Objekte im Debugger-Kontext im **Quellen** Panel und in der **Konsole** (beispielsweise nach der Konsolen Auswertung \) gespeichert. Erstellen Sie Heap-Schnappschüsse mit einem gelöschten **Konsolen** Panel und keine aktiven Haltepunkte im Debugger im **Quellen** Panel.
>[!TIP]
> Deaktivieren Sie die **Konsolen** Leiste, indem Sie die `clear()` Haltepunkte im **Quellen** Panel ausführen und deaktivieren, bevor Sie einen Heap-Schnappschuss im [Speicher Panel][DevtoolsMemoryProblemsHeapSnapshots]aufnehmen.
Der Speicher Graph beginnt mit einem Stamm, der möglicherweise das `window` Objekt des Browsers oder das `Global` Objekt eines Node. js-Moduls ist. Sie steuern nicht, wie dieses Stammobjekt Garbage Collection (GGT) ist.
> ##### Abbildung 3
> Sie können nicht steuern, wie das Stammobjekt Garbage Collection ist \ (GGT \).
>![Sie können nicht steuern, wie das Stammobjekt Garbage Collection (GGT) ist.][ImageDontControl]
Was nicht über den Stamm erreichbar ist, erhält Garbage Collection \ (GGT \).
> [!NOTE]
> Die Spalten " [flache Größe](#shallow-size) " und " [Größe beibehalten](#retained-size) " stellen Daten in Bytes dar.
## Objekte, die die Struktur beibehalten
Der Heap ist ein Netzwerk von miteinander verbundenen Objekten. In der mathematischen Welt wird diese Struktur als **Diagramm** oder Speicher Diagramm bezeichnet. Ein Diagramm wird aus **Knoten** erstellt, die über **Kanten**verbunden sind, wobei beide Bezeichnungen angegeben werden.
* **Knoten** \ (oder **Objekte**\) werden mit dem Namen der **Konstruktorfunktion** gekennzeichnet, die zum Erstellen verwendet wurde.
* **Kanten** werden mit den Namen der **Eigenschaften**gekennzeichnet.
Erfahren Sie [, wie Sie ein Profil mit dem Heap Profiler aufzeichnen][DevtoolsMemoryProblemsHeapSnapshots]. Einige der auffälligen Elemente, die in der Heap-Snapshot-Aufzeichnung im [Speicher Panel][DevtoolsMemoryProblemsHeapSnapshots] in [Abbildung 4](#figure-4) angezeigt werden, umfassen Abstand: die Entfernung vom Garbage Collector \ (GC \)-Stamm. Wenn sich fast alle Objekte desselben Typs im gleichen Abstand befinden und einige wenige in größerer Entfernung sind, ist das eine Untersuchung Wert.
> ##### Abbildung4
> Abstand vom Stamm
>![Abstand vom Stamm][ImageRoot]
## Dominators
Dominator-Objekte bestehen aus einer Struktur, da jedes Objekt genau einen Dominator hat. Ein Dominator eines Objekts kann keine direkten Bezüge auf ein Objekt aufweisen, das es dominiert; Das bedeutet, dass die Struktur des Dominators keine Spanning-Struktur des Diagramms ist.
[Abbildung 5](#figure-5):
* Knoten 1 dominiert Knoten 2
* Knoten 2 dominiert die Knoten 3, 4 und 6
* Knoten 3 dominiert Knoten 5
* Knoten 5 dominiert Knoten 8
* Knoten 6 dominiert Knoten 7
> ##### Abbildung5
> Struktur des Dominators
>![Struktur des Dominators][ImageDominatorsSpanning]
In [Abbildung 6](#figure-6)ist Knoten `#3` der Dominator von `#10` , aber `#7` es gibt auch in jedem einfachen Pfad vom Garbage Collector \ (GC \) bis `#10` . Daher ist ein Objekt b ein Dominator eines Objekts a, wenn b in jedem einfachen Pfad vom Stamm zum Objekt a vorhanden ist.
> ##### Abbildung6
> Animierte Dominator-Illustration
>![Animierte Dominator-Illustration][ImageDominators]
## V8-Besonderheiten
Bei der Profilerstellung von Arbeitsspeicher ist es hilfreich zu verstehen, warum Heap Momentaufnahmen auf eine bestimmte Weise aussehen. In diesem Abschnitt werden einige speicherbezogene Themen beschrieben, die speziell der **virtuellen V8-JavaScript-Maschine** \ (V8 VM oder VM \) entsprechen.
### JavaScript-Objektdarstellung
Es gibt drei primitive Typen:
* Zahlen \ (Beispiel `3.14159...` : \)
* Boolesche Werte \ ( `true` oder `false` \)
* Zeichenfolgen \ (Beispiel `"Werner Heisenberg"` : \)
Primitive können nicht auf andere Werte verweisen und sind immer Blatt-oder Endpunkt Knoten.
**Nummern** können entweder wie folgt gespeichert werden:
* eine direkte 31-Bit-Ganzzahl, die als **kleine ganze Zahlen** (**SMI**s \) bezeichnet wird, oder
* Heap-Objekte, die als **Heap-Nummern**bezeichnet werden. Heap-Nummern werden zum Speichern von Werten verwendet, die nicht in das SMI-Formular passen, wie etwa **Doubles**, oder wenn ein Wert **geschachtelt**werden muss, wie beispielsweise das Festlegen von Eigenschaften.
**Zeichenfolgen** können entweder in folgendem gespeichert werden:
* der **VM-Heap**oder
* extern im **Speicher des Renderers**. Ein **Wrapperobjekt** wird erstellt und für den Zugriff auf externen Speicher verwendet, wenn beispielsweise Skript Quellen und andere Inhalte, die aus dem Web empfangen werden, gespeichert werden, anstatt auf den VM-Heap kopiert zu werden.
Der Arbeitsspeicher für neue JavaScript-Objekte wird von einem dedizierten JavaScript-Heap zugeordnet \ (oder **VM-Heap**\). Diese Objekte werden vom Garbage Collector in V8 verwaltet und bleiben daher so lange am Leben, wie es mindestens einen starken Bezug auf Sie gibt.
Alles, was sich nicht im JavaScript-Heap befindet, wird als **systemeigenes Objekt**bezeichnet. Systemeigene Objekte werden im Gegensatz zu Heap Objekten nicht vom V8-Garbage Collector während ihrer gesamten Lebensdauer verwaltet und können nur über JavaScript mit dem JavaScript-Wrapperobjekt aufgerufen werden.
**Cons String** ist ein Objekt, das aus Paaren von Zeichenfolgen besteht, die gespeichert und dann verknüpft sind und ein Ergebnis der Verkettung sind. Die Verknüpfung des **Cons-Zeichenfolgen** Inhalts erfolgt nur bei Bedarf. Ein Beispiel wäre, wenn eine Teilzeichenfolge einer verknüpften Zeichenfolge erstellt werden muss.
Wenn Sie beispielsweise verketten `a` und `b` erhalten Sie eine Zeichenfolge, die `(a, b)` das Ergebnis der Verkettung darstellt. Wenn Sie später `d` mit diesem Ergebnis verkettet haben, erhalten Sie eine weitere **Cons-Zeichenfolge**: `((a, b, d)` .
**Matrix** ist ein Objekt mit numerischen Schlüsseln. **Arrays** werden in der V8-VM umfassend verwendet, um große Datenmengen zu speichern. Sätze von Schlüssel-Wert-Paaren, wie Wörterbücher, werden von **Arrays**gesichert.
Ein typisches JavaScript-Objekt wird nur als einer von zwei **Array** Typen gespeichert:
* benannte Eigenschaften und
* numerische Elemente
Wenn eine geringe Anzahl von Eigenschaften vorhanden ist, werden die Eigenschaften intern im JavaScript-Objekt gespeichert.
**Map** ist ein Objekt, das sowohl die Art des Objekts als auch das Layout beschreibt. Karten werden beispielsweise verwendet, um implizite Objekthierarchien für den [schnellen Eigenschaftenzugriff][V8FastProperties]zu beschreiben.
### Objektgruppen
Jede Gruppe **systemeigene Objekte** besteht aus Objekten, die gegenseitige Bezüge aufeinander abhalten. Nehmen Sie beispielsweise eine DOM-Unterstruktur in Frage, bei der jeder Knoten über einen Link zum relativen übergeordneten Element und Links zum nächsten untergeordneten Element und zum nächsten nebengeordneten Element verfügt, wodurch ein verbundenes Diagramm entsteht. Beachten Sie, dass systemeigene Objekte nicht im JavaScript-Heap dargestellt werden, daher haben systemeigene Objekte die Größe 0 (null). Stattdessen werden Wrapper Objekte erstellt.
Jedes Wrapperobjekt enthält einen Verweis auf das entsprechende systemeigene Objekt für die Umleitung von Befehlen an ihn. Eine Objektgruppe enthält wiederum Wrapper Objekte. Dadurch wird jedoch kein nicht sammelbarer Zyklus erstellt, da der Garbage Collector \ (GC \) intelligent genug ist, Objektgruppen freizugeben, deren Wrapper nicht mehr referenziert werden. Aber zu vergessen, einen einzelnen Wrapper freizugeben, enthält die gesamte Gruppe und zugehörige Wrapper.
<!--## Feedback -->
<!-- image links -->
[ImageThinkGraph]: /microsoft-edge/devtools-guide-chromium/media/memory-problems-thinkgraph.msft.png "Abbildung 1: visuelle Darstellung des Arbeitsspeichers"
[ImageShallowRetained]: /microsoft-edge/devtools-guide-chromium/media/memory-problems-shallow-retained.msft.png "Abbildung 2: flache und gespeicherte Größe"
[ImageDontControl]: /microsoft-edge/devtools-guide-chromium/media/memory-problems-dontcontrol.msft.png "Abbildung 3: Sie können nicht steuern, wie das Stammobjekt als Garbage Collection (GGT) festgestellt wird."
[ImageRoot]: /microsoft-edge/devtools-guide-chromium/media/memory-problems-root.msft.png "Abbildung 4: Abstand vom Stamm"
[ImageDominatorsSpanning]: /microsoft-edge/devtools-guide-chromium/media/memory-problems-dominatorsspanning.msft.png "Abbildung 5: Dominator-Struktur"
[ImageDominators]: /microsoft-edge/devtools-guide-chromium/media/memory-problems-dominators.msft.gif "Abbildung 6: animierte Dominator-Abbildung"
<!-- links -->
[DevtoolsMemoryProblemsHeapSnapshots]: /microsoft-edge/devtools-guide-chromium/media/memory-problems/heap-snapshots "/microsoft-edge/devtools-guide-chromium/media/memory-problems"
[V8FastProperties]: https://v8.dev/blog/fast-properties "Fast-Eigenschaften in V8 | V8"
> [!NOTE]
> Teile dieser Seite sind Änderungen, die auf der [von Google erstellten und freigegebenen][GoogleSitePolicies] Arbeit basieren und gemäß den in der [Creative Commons Attribution 4,0 International-Lizenz][CCA4IL]beschriebenen Begriffen verwendet werden.
> Die ursprüngliche Seite wird [hier](https://developers.google.com/web/tools/chrome-devtools/memory-problems/memory-101) gefunden und von [Meggin Kearney][MegginKearney] (Technical Writer \) erstellt.
[![Creative Commons-Lizenz][CCby4Image]][CCA4IL]
Diese Arbeit unterliegt einer [Creative Commons Attribution 4.0 International License][CCA4IL].
[CCA4IL]: https://creativecommons.org/licenses/by/4.0
[CCby4Image]: https://i.creativecommons.org/l/by/4.0/88x31.png
[GoogleSitePolicies]: https://developers.google.com/terms/site-policies
[KayceBasques]: https://developers.google.com/web/resources/contributors/kaycebasques
[MegginKearney]: https://developers.google.com/web/resources/contributors/megginkearney
| 72.36019 | 621 | 0.783207 | deu_Latn | 0.996131 |
22ebed8a66e5a32d9137f6a9b8cd7efceea6eca3 | 15,103 | markdown | Markdown | source/articles/2018-09-23-tough-luck-young-buck.html.markdown | upperrapids/someparty | 4696771426b7c1c5c4ae30ea3e9de4131b55b4ec | [
"MIT"
] | 1 | 2021-11-15T09:16:48.000Z | 2021-11-15T09:16:48.000Z | source/articles/2018-09-23-tough-luck-young-buck.html.markdown | upperrapids/someparty | 4696771426b7c1c5c4ae30ea3e9de4131b55b4ec | [
"MIT"
] | 7 | 2020-04-01T13:21:27.000Z | 2021-05-26T03:14:12.000Z | source/articles/2018-09-23-tough-luck-young-buck.html.markdown | upperrapids/someparty | 4696771426b7c1c5c4ae30ea3e9de4131b55b4ec | [
"MIT"
] | null | null | null | ---
title: Tough Luck Young Buck
date: 2018-09-23
author: [email protected] (Adam White)
description: Music and news from Nick Ferrio, Kim Barlow, Jock Tears, Deathsticks, Zouz, Crumb, Bootlicker, Fly Pan Am, Rebuild/Repair, Ruby's Kiss and DA SLYME!
---
This week folk-rocker [Nick Ferrio](http://www.nickferrio.com/) will release *Have a Nice Day*, his follow-up to last year's *Soothsayer* LP. The Peterborough-based singer-songwriter recently unveiled a video for the song "How Will I Know," a reflective track that looks upon music as a source of wonder. It's an earnest and affecting tune from an artist who's made a career out of that sort of thing. This is the second preview we've seen from the record, following the gentrification screed "Don't Know How Long."
Ferrio commented on the song in a press release:
> "How Will I Know" is a philosophical song; it’s about my relationship with music and thinking about why I’m drawn to make it, especially in today’s day and age, with the music industry changing. We’ve all heard over and over again about how the music industry is in the pits and how culturally music isn’t as valuable as it once was. I guess the nagging question in this song is, is music still worth something? The answer to that is yes. Music has the power to transform, to give meaning, to create connection, to make change. Ultimately, music is powerful. And because of that, music will survive whatever happens to the music industry.
The [Have a Nice Day tour](https://www.facebook.com/tours/1689150844547354/) will kick off in late September with a POP Montreal show in support of Ferrio's fellow Sappyfest alum [Leanne Betasamosake Simpson](https://www.leannesimpson.ca/), followed by gigs in Ottawa, Kingston, Hamilton, Toronto, and Sudbury.
<iframe width="560" height="315" src="https://www.youtube.com/embed/tdZhmAAcM0s" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen></iframe>
[Watch: Nick Ferrio - "How Will I Know" @ YouTube](https://youtu.be/tdZhmAAcM0s "#")
While we're on a bit of an autumn folk kick, let's check in with [Kim Barlow](http://www.kimbarlow.ca/). The Nova Scotian musician will also release a new record this week titled *How To Let Go*. It features the singer/guitarist/banjo player backed by drummer Mark Adam and bassist Nicholas D'Amato, with guest appearances from Old Man Luedecke, among others.
Barlow previewed the new work with the single "Whitehorse," a biographical road trip that gradually builds in percussive energy as it clips along. This tune's been stuck in my head all week.
Now based in the Annapolis Valley, Barlow has six records out under her name along with a number of collaborative projects. These include a duo with Mathias Kom of [The Burning Hell](http://www.wearetheburninghell.com/) under the name Spring Breakup and the string band Ira Red with Gaspereau's Heather Kelday.
<iframe width="100%" height="166" scrolling="no" frameborder="no" allow="autoplay" src="https://w.soundcloud.com/player/?url=https%3A//api.soundcloud.com/tracks/495784584&color=%23ff5500&auto_play=false&hide_related=false&show_comments=true&show_user=true&show_reposts=false&show_teaser=true"></iframe>
[Listen: Kim Barlow: "Whitehorse" @ SoundCloud](https://soundcloud.com/user-124859170/whitehorse "#")
Vancouver punk act [Jock Tears](https://jocktears.bandcamp.com/) are finally ready to unveil their first full-length. The 12-song *Bad Boys* will debut this Friday on Inky Records. The set finds the band mixing attitude-driven Ramones-inspired numbers like "Boys With Bruises" alongside amusing twee tunes like the band's namesake jock-baiting mission statement "Jock Tears." The group recorded in Montreal at Value Sound with [Faith Healer](https://faithhealer.bandcamp.com/)'s [Renny Wilson](http://rennywilson.com/).
Vocalist Lauren Ray fronts Jock Tears. The quartet also features former [Tough Age](https://tough-age.bandcamp.com/) bassist Lauren Smith, guitarist Spencer Hargreaves ([Redrick Sultan](https://redricksultanband.bandcamp.com/)), and [Brutal Poodle](https://brutalpoodlevan.bandcamp.com/) drummer Dustin Bromley.
<iframe style="border: 0; width: 100%; height: 120px;" src="https://bandcamp.com/EmbeddedPlayer/album=1514218396/size=large/bgcol=ffffff/linkcol=0687f5/tracklist=false/artwork=small/track=1009150867/transparent=true/" seamless><a href="http://jocktears.bandcamp.com/album/bad-boys">bad boys by jock tears</a></iframe>
[Listen: Jock Tears - "Boys With Bruises" @ Bandcamp](https://jocktears.bandcamp.com/album/bad-boys "#")
Ottawa noise-duo [Deathsticks](https://buysomedeathsticks.bandcamp.com/) have returned with a new single titled "In The Motors." The galloping track is the first preview of the band's upcoming record *Funny Haha Cool*, an album that will launch the band's new label Not My Car. "In The Motors" has moments that you could almost squint and call poppy, which is a shift for a band that's otherwise consistently played and recorded as loud a racket as utterly possible. This is a relative observation.
This track will also appear on the upcoming [It's Trash Records](https://itstrashrecords.bandcamp.com/) compilation *Killed By Meth Vol 3*, which will also feature contributions from Toronto's [WLMRT](https://wlmrt.bandcamp.com/) and Hamilton's Sweet Milk along with a host of American garage punk groups.
<iframe style="border: 0; width: 100%; height: 120px;" src="https://bandcamp.com/EmbeddedPlayer/track=3731168423/size=large/bgcol=ffffff/linkcol=0687f5/tracklist=false/artwork=small/transparent=true/" seamless><a href="http://buysomedeathsticks.bandcamp.com/track/in-the-motors-single">In The Motors (Single) by Deathsticks</a></iframe>
[Listen: Deathsticks - "In The Motors" @ Bandcamp](https://buysomedeathsticks.bandcamp.com/track/in-the-motors-single "#")
I'm absolutely fascinated by the song "Saint-Fortunat," the first preview from the upcoming EP from Quebec's [Zouz](http://zouz.bandcamp.com/). The garage-psych track, which builds in intensity over a looping country riff, is one of six to appear on *EP2* when it arrives on October 12 on [Lazy at Work](https://lazyatwork.bandcamp.com/) (Galaxie, FUUDGE, Les Dales Hawerchuk). It follows up the band's 2017 EP, which was unsurprisingly titled *EP1*.
Zouz is a three-piece featuring vocalist/guitarist David Marchand, bass/synth player Étienne Dupré, and percussionist Francis Ledoux. The group has roots in Montreal's Cartierville neighbourhood and the cities of Sainte-Pie and Saint-Hyacinthe.
<iframe style="border: 0; width: 100%; height: 120px;" src="https://bandcamp.com/EmbeddedPlayer/album=4036871780/size=large/bgcol=ffffff/linkcol=0687f5/tracklist=false/artwork=small/transparent=true/" seamless><a href="http://zouz.bandcamp.com/album/ep2">EP2 by zouz</a></iframe>
[Listen: zouz - "Saint-Fortunat" @ Bandcamp](https://zouz.bandcamp.com/album/ep2 "#")
Vancouver's [Neon Taste](https://neontasterecords.bandcamp.com/) has a bunch of cool releases on the way this fall. First up is an extremely limited cassette from the now-defunct Vancouver punk act [Crumb](https://crumbvancouver.bandcamp.com/), collecting the band's *Community Service* EP. The five-piece released the four-song set digitally in early August. It was recorded, mixed, and mastered by JJ Heath at Rain City Recorders. Here's what the label had to say:
> Sometimes melodic and sometimes nauseating, Crumb were a Vancouver hardcore band that bridged the gap between The Faith and the swampy-effect, driven guitars of more modern sounds. Tempo changes and tough, metal influenced riffs with a vocalist that isn't hiding behind layers of verb and delay. Crumb were killer. This is their swan-song. 50 copies only. No more. This release is entirely about trying to make sure that bands this good manage to have at least something physical to leave behind in a city that swallows everything.
<iframe style="border: 0; width: 100%; height: 120px;" src="https://bandcamp.com/EmbeddedPlayer/album=481875697/size=large/bgcol=ffffff/linkcol=0687f5/tracklist=false/artwork=small/transparent=true/" seamless><a href="http://neontasterecords.bandcamp.com/album/crumb-community-service-e-p">Crumb - Community Service E.P. by Crumb</a></iframe>
[Listen: Crumb - *Community Service* @ Bandcamp](https://neontasterecords.bandcamp.com/album/crumb-community-service-e-p "#")
Neon Taste is also reissuing the debut record from BC's Oi-influenced hardcore group [Bootlicker](https://boot-licker.bandcamp.com/). Carrying the no-frills title of *6 Track E.P*, Bootlicker's blown-out six-song debut first arrived in September of 2017. On this record, the band featured vocalist/bassist Lewis Jay, guitarist Trevor Robson, and drummer Lucas. Lewis and Lucas have since reorganized the group as a four-piece. A follow-up EP titled *Who Do You Serve?* arrived this past June.
Label-head Josh Nickel commented, "This, along with Cheap Appeal, is some of the best hardcore this Province has EVER come up with."
<iframe style="border: 0; width: 100%; height: 120px;" src="https://bandcamp.com/EmbeddedPlayer/album=787109196/size=large/bgcol=ffffff/linkcol=0687f5/tracklist=false/artwork=small/transparent=true/" seamless><a href="http://neontasterecords.bandcamp.com/album/bootlicker-6-track-e-p">Bootlicker - 6 Track E.P. by Bootlicker</a></iframe>
[Listen: Bootlicker - *6 Track E.P.* @ Bandcamp](https://neontasterecords.bandcamp.com/album/bootlicker-6-track-e-p "#")
Edmonton's grim and gritty punk/sludge act [Rebuild/Repair](https://rebuildrepair.bandcamp.com) will release their third album, *There Is No Place Left For Me Here*, on September 28. You can preview the songs "Greybeard" and "On Self-Awareness and Being a Bastard" at Bandcamp now. The three-piece commented on the dark themes driving the record:
> The album is about struggling with mental illness and social isolation in a place you no longer feel connected to. It features artwork depicting the High Level Bridge, a "popular" suicide spot in Edmonton, AB.
Damn. Rebuild/Repair is a three-piece vocalist/guitarist Randall Graves, bassist Jason W. Goodall, and drummer Kelly Doiron. The band's following up a split from earlier this year with Medicine Hat's [OHMWAR](https://ohmwar.bandcamp.com/) and their 2016 LP *Above Ground Cemeteries*.
<iframe style="border: 0; width: 100%; height: 120px;" src="https://bandcamp.com/EmbeddedPlayer/album=2369978774/size=large/bgcol=ffffff/linkcol=0687f5/tracklist=false/artwork=small/transparent=true/" seamless><a href="http://rebuildrepair.bandcamp.com/album/there-is-no-place-left-for-me-here">There Is No Place Left For Me Here by Rebuild/Repair</a></iframe>
[Listen: Rebuild/Repair - "Graybeard" @ Bandcamp](https://rebuildrepair.bandcamp.com/album/there-is-no-place-left-for-me-here "#")
On the cheerier end of the spectrum, Toronto's laid back indie-pop act [Ruby's Kiss](https://www.facebook.com/RubysKissOfficial/) have an EP release show coming up this [Friday](https://www.facebook.com/events/607708576290856/). The band will take to Sneaky Dee's with support from Tilt Howl and Faiyaz and The Wasted Chances. The five-piece band recently previewed the song "FOMO" at YouTube, showcasing a sound that would have fit right in with the popular early-2000s garage rock revival.
<iframe width="560" height="315" src="https://www.youtube.com/embed/QQU2IRLjoYo" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen></iframe>
[Listen: Ruby's Kiss - "FOMO" @ YouTube](https://youtu.be/QQU2IRLjoYo "#")
Experimental post-rock group [Fly Pan Am](http://cstrecords.com/fly-pan-am/) have announced a reunion, with a single live show scheduled. The influential late-90s band will reconvene for a gig on [October 20](https://www.facebook.com/leflypanam/) with [Kee Avil](https://keeavil.bandcamp.com/) in their hometown of Montreal at Dazibao.
Fly Pan Am (or Le Fly Pan Am to be formal) formed in 1996 and were contemporaries of like-minded high-art bands like [Godspeed You! Black Emperor](http://www.brainwashed.com/godspeed/). The four-piece put out four records from 1998 through 2005 on Constellation Records before putting a halt to things in 2006. The group's founding lineup featured guitarists Roger Tellier-Craig and Jonathan Parant, bassist J.S. Truchy, and drummer Felix Morel, with all members credited for working on the electronics and tape effects the group became known for. Multi-instrumentalist Eric Gingras (guitars, organs, percussion) expanded the band's lineup in 2002.
<iframe width="560" height="315" src="https://www.youtube.com/embed/WV16tdpu2q0" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen></iframe>
[Listen: Fly Pan Am - *N'écoutez Pas* @ YouTube](https://www.youtube.com/watch?v=WV16tdpu2q0 "#")
A few weeks ago I shared some news about a [Supreme Echo](http://www.supremeecho.com/) reissue of material from first-wave St. John’s, Newfoundland punk band [The Reaction](http://citizenfreak.com/artists/101759-reaction-the). You couldn't read very far into that band's history without seeing numerous references to their contemporaries in [Da Slyme](http://www.abandonstream.net/slyme/). Aside from a few songs (like the killer scuzz-punk single "Piss Eyed Sleazoid") most of that band's material simply hadn't made it onto the Internet, officially or otherwise.
A few weeks ago that changed, with a full vinyl rip of Da Slyme's self-titled 1980 double LP showing up on YouTube with a ton of annotations. The heroic individual behind the rip commented on the record:
> This INSANELY RARE Double LP was self-released in the fall of 1980 by St. John’s, Newfoundland, Canada punk rock band DA SLYME - recorded in 1978 and 1979. Believed to be limited to 200 copies or less. The records came housed in random Thrift Store LP jackets - purchased in bulk for 25 cents each when the band ran out of money for professional record covers - with "DA SLYME" spray painted on the front covers in a stencil.
>
> Musically, its all over the place! Captain Beefheart is the most obvious influence on their sound, but there's also prog, psych, and even country influences that can be heard throughout the record - not to mention stand-up comedy (a portion of the live LP features their hype man doing stand-up before introducing the band) - all in a snotty, late 70s punk style.
>
> A true outsider record! Very few copies ever made it out of Newfoundland, and to date it has never been reissued - making it one of the rarest Canadian records of any music genre.
What are you waiting for? Long lost classics like "Truck Stop Nun" and "Trudeau Sucks" await.
<iframe width="560" height="315" src="https://www.youtube.com/embed/e4BjCQXwubU" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen></iframe>
[Listen: Da Slyme - 2xLP (1980) Sides A & B @ YouTube](https://youtu.be/e4BjCQXwubU "#")
<iframe width="560" height="315" src="https://www.youtube.com/embed/Q1FPdKeERsI" frameborder="0" allow="autoplay; encrypted-media" allowfullscreen></iframe>
[Listen: Da Slyme - 2xLP (1980) Sides C & D @ YouTube](https://youtu.be/Q1FPdKeERsI "#")
| 133.654867 | 648 | 0.776137 | eng_Latn | 0.975357 |
22ed1184c66fde8b60f16df02ef6aa269a057717 | 1,450 | md | Markdown | _posts/2015-07-25-Lafemme-Gigi-Prom-Dresses-Style-19695.md | queenosestyle/queenosestyle.github.io | 7b095a591cefe4e42cdeb7de71cfa87293a95b5c | [
"MIT"
] | null | null | null | _posts/2015-07-25-Lafemme-Gigi-Prom-Dresses-Style-19695.md | queenosestyle/queenosestyle.github.io | 7b095a591cefe4e42cdeb7de71cfa87293a95b5c | [
"MIT"
] | null | null | null | _posts/2015-07-25-Lafemme-Gigi-Prom-Dresses-Style-19695.md | queenosestyle/queenosestyle.github.io | 7b095a591cefe4e42cdeb7de71cfa87293a95b5c | [
"MIT"
] | null | null | null | ---
layout: post
date: 2015-07-25
title: "Lafemme Gigi Prom Dresses Style 19695"
category: Lafemme
tags: [Lafemme]
---
### Lafemme Gigi Prom Dresses Style 19695
Just **$539.99**
###
<table><tr><td>BRANDS</td><td>Lafemme</td></tr></table>
<a href="https://www.readybrides.com/en/lafemme/76802-lafemme-gigi-prom-dresses-style-19695.html"><img src="//img.readybrides.com/186419/lafemme-gigi-prom-dresses-style-19695.jpg" alt="Lafemme Gigi Prom Dresses Style 19695" style="width:100%;" /></a>
<!-- break --><a href="https://www.readybrides.com/en/lafemme/76802-lafemme-gigi-prom-dresses-style-19695.html"><img src="//img.readybrides.com/186420/lafemme-gigi-prom-dresses-style-19695.jpg" alt="Lafemme Gigi Prom Dresses Style 19695" style="width:100%;" /></a>
<a href="https://www.readybrides.com/en/lafemme/76802-lafemme-gigi-prom-dresses-style-19695.html"><img src="//img.readybrides.com/186421/lafemme-gigi-prom-dresses-style-19695.jpg" alt="Lafemme Gigi Prom Dresses Style 19695" style="width:100%;" /></a>
<a href="https://www.readybrides.com/en/lafemme/76802-lafemme-gigi-prom-dresses-style-19695.html"><img src="//img.readybrides.com/186418/lafemme-gigi-prom-dresses-style-19695.jpg" alt="Lafemme Gigi Prom Dresses Style 19695" style="width:100%;" /></a>
Buy it: [https://www.readybrides.com/en/lafemme/76802-lafemme-gigi-prom-dresses-style-19695.html](https://www.readybrides.com/en/lafemme/76802-lafemme-gigi-prom-dresses-style-19695.html)
| 80.555556 | 264 | 0.741379 | yue_Hant | 0.109788 |
22ee85d1cd5083dfc0478b97916b96b8a85c17d7 | 674 | md | Markdown | README.md | ebargtuo/hello_world | 31d7faaf2615b0f17b81ae9a473d2f295735ccff | [
"MIT"
] | null | null | null | README.md | ebargtuo/hello_world | 31d7faaf2615b0f17b81ae9a473d2f295735ccff | [
"MIT"
] | null | null | null | README.md | ebargtuo/hello_world | 31d7faaf2615b0f17b81ae9a473d2f295735ccff | [
"MIT"
] | null | null | null | # Hello World #
Simple "Hello World" examples in various technologies.
## Description ##
This project aims to provide simple "Hello World" projects as examples
of how to get started with various tools, language, frameworks, technologies...
See individual project `README`s for details.
Included examples:
* PHP
* Behat - a BDD testing framework for PHP
* Slim - a PHP micro framework (API example)
* Ruby
* Sinatra - a light-weight web framework (API example)
* Node
* Expressjs - a minimalist Node.js web framework (API example)
* hapijs - another Node.js web framework (API example)
## Licence ##
Copyright 2014 ebargtuo. Released under the MIT license.
| 21.741935 | 79 | 0.738872 | eng_Latn | 0.955976 |
22ee88268b5580b2974fee9cf286d04744b33897 | 2,294 | md | Markdown | readme.md | balthisar/JSDCocoaDemos | 234c41cb63147b25c9a813697cc84532f6a37aa1 | [
"Unlicense",
"MIT"
] | 5 | 2015-03-09T13:03:24.000Z | 2016-03-14T10:17:32.000Z | readme.md | balthisar/JSDCocoaDemos | 234c41cb63147b25c9a813697cc84532f6a37aa1 | [
"Unlicense",
"MIT"
] | null | null | null | readme.md | balthisar/JSDCocoaDemos | 234c41cb63147b25c9a813697cc84532f6a37aa1 | [
"Unlicense",
"MIT"
] | null | null | null | JSDCocoaDemos
=============
by Jim Derry <http://www.balthisar.com>
Copyright © 2013 by Jim Derry. All rights reserved.
See “Legal Stuff” below for license details.
About
-----
This project serves as an all-in-one project for various Cocoa classes and demonstrations put together by *balthisar.com*, and consists of several different themes with not a whole lot in common between them.
Current Contents Include:
- `ViewsFromNibs`
- A simple demonstrion of how to load and use Nib files dynamically instead of building them statically into your application.
- `NSTextView+JSDExtensions`
- An `NSTextView` category that implements wordwrap (or not), line number display, and simple line-character highlighting.
How to Use
----------
In XCode 5 or above the sample code is organized logically, as it is in the actual directory structure. Each demonstration code directory has its own readme.md file.
To run a demonstration program select the build target desired from the build scheme popup menu, which (as of XCode 5) is near the upper-left of the XCode main IDE window.
Legal Stuff
-----------
by Jim Derry <http://www.balthisar.com>
Copyright © 2013 by Jim Derry. All rights reserved.
*All files in this project are released according to the MIT license.*
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
| 55.95122 | 460 | 0.780732 | eng_Latn | 0.951087 |
22ef2589c067839f730a6108be8fbbd62556df60 | 1,269 | md | Markdown | get-statistics/README.md | singwin/sample-api-scripts | 30f69acbb69927be45e1132548beeacc4ecdb90b | [
"MIT"
] | 8 | 2020-10-30T09:59:18.000Z | 2022-02-04T21:16:24.000Z | get-statistics/README.md | singwin/sample-api-scripts | 30f69acbb69927be45e1132548beeacc4ecdb90b | [
"MIT"
] | 47 | 2020-10-04T03:01:24.000Z | 2022-03-30T10:18:08.000Z | get-statistics/README.md | singwin/sample-api-scripts | 30f69acbb69927be45e1132548beeacc4ecdb90b | [
"MIT"
] | 27 | 2020-10-22T07:31:46.000Z | 2022-03-31T09:12:05.000Z | [](https://gitpod.io/#https://github.com/vegaprotocol/sample-api-scripts)
# Sample API scripts - Vega statistics
These scripts talk to a Vega node and get the latest statistics.
Please see the documentation on Vega for further information.
## Shell + curl
Get the latest statistics using shell scripts and `curl` only [REST API]:
```bash
bash get-statistics/get-statistics.sh
```
## Python + requests
Get the latest statistics using python3 and the [requests](https://pypi.org/project/requests/) library [REST API]:
```bash
python3 get-statistics/get-statistics.py
```
## Python + Vega-API-client
Get the latest statistics using python3 and the [Vega-API-client](https://pypi.org/project/Vega-API-client/) library [gRPC API]:
```bash
python3 get-statistics/get-statistics-with-Vega-API-client.py
```
## GraphQL
[](https://www.graphqlbin.com/v2/g8LlIm)
Get the latest statistics using shell scripts and [graphqurl](https://github.com/hasura/graphqurl) only [GraphQL API]:
```bash
bash get-statistics/get-statistics-gql.sh
```
---
**[Home](../README.md)**
| 27.586957 | 166 | 0.738377 | kor_Hang | 0.321963 |
22f103dd9be584e621dd895fdc1af22ccdef4130 | 1,933 | md | Markdown | README.md | unix4fun/pemaead | 9bf1501fd92b8370fbc0999423979c68c8844f0d | [
"BSD-3-Clause"
] | 3 | 2018-07-30T14:15:35.000Z | 2018-08-20T08:34:35.000Z | README.md | unix4fun/pemaead | 9bf1501fd92b8370fbc0999423979c68c8844f0d | [
"BSD-3-Clause"
] | null | null | null | README.md | unix4fun/pemaead | 9bf1501fd92b8370fbc0999423979c68c8844f0d | [
"BSD-3-Clause"
] | null | null | null | # pemaead
A simple PEM enveloppe using AES AEAD encryption mode go package/library.
## Purpose
a simple io.ReadCloser / io.WriteCloser interface, to store and encrypt/tag a reasonnably small amount of data at rest,
an attempt to be reasonnably resistant to offline attacks as well as ensure data + header integrity using an "encrypt-then-MAC"
approach (thanks to AEAD and trying to avoid Encrypt-and-MAC and MAC-then-encrypt kind of schemes).
Relying on AEAD properties to ensure integrity of data + headers (+ CSRNG key derivation salt & AEAD nonce).
Key is derivated using strong derivation functions trying to slow down brute-force:
* Scrypt
* Argon2id
* PBKDF2 (if standard is needed)
Using AES-GCM-256 encryption mode & Argon2id key derivation by default, a random salt & nonce.
## Usage Examples
Important notes:
* Write() is only buffering, the call to Close() will actually write your data, keep that in mind.
* Close() will close the underlying fd provided to the Writer.
### Writer
...
fd, err := os.OpenFile(fileName, os.O_CREATE|os.O_WRONLY|os.O_EXCL|os.O_SYNC, 0700)
if err != nil {
return err
}
pemfd, err := pemaead.NewWriter(fd, password, pemaead.CipherAESGCM, pemaead.DerivateArgon2)
if err != nil {
return err
}
defer pemfd.Close()
...
_, err = pemfd.Write(data)
if err != nil {
return err
}
...
### Reader
...
fd, err := os.Open(fileName)
if err != nil {
return err
}
pemfd, err := pemaead.NewReader(fd, password)
if err != nil {
return err
}
defer pemfd.Close()
data, err := ioutil.ReadAll(pemfd)
if err != nil {
return err
}
## TODO
* go docs
* unit tests
* more clearly define limitations
* add PQ algorithms
* add other AEAD algorithms.
## ChangeLog
* 2018-07-20
* v0.1.0 : initial release/push outside the realm of my own usage to the world :)
| 26.479452 | 128 | 0.674599 | eng_Latn | 0.898052 |
22f1b7444e52f3d30efa38b5062271ac1e5a4c5b | 1,943 | md | Markdown | _posts/archives/2010-08-09-Hectic-and-enjoyable-weekend.....md | deeyum/deeyum.github.io | be2263202c5c1e89a14e54bd4fce9e5147a1aeb2 | [
"MIT"
] | null | null | null | _posts/archives/2010-08-09-Hectic-and-enjoyable-weekend.....md | deeyum/deeyum.github.io | be2263202c5c1e89a14e54bd4fce9e5147a1aeb2 | [
"MIT"
] | null | null | null | _posts/archives/2010-08-09-Hectic-and-enjoyable-weekend.....md | deeyum/deeyum.github.io | be2263202c5c1e89a14e54bd4fce9e5147a1aeb2 | [
"MIT"
] | null | null | null | ---
layout: post
date: 2010-08-09 15:52:00
title: Hectic and enjoyable weekend....
tags: [archived-posts]
categories: archives
permalink: /:categories/:year/:month/:day/:title/
---
Having seen, and enjoyed, "Elling" at Ranga Shankara on Friday evening (I walked alone to Ranga Shankara, but was joined there by Priya and Janaki, who seemed to get along like a house on fire!), I struggled with a recalcitrant internet, lost my entire review, finally re-posted it....
<a href="http://bangalore.citizenmatters.in/blogs/8-deepas-jottings"> here it is </a>
and then went off with Chandu to the Naturalists' Training Program happening at the Bannerghatta property of Jungle Lodges and Resorts.
After coming back out (the jeep normally takes me outside the gates before they close for the evening), Chandu and I decided that we'd do a bit more of birding before we left...and it was a good decision, because, as usual, birds of every sort gave their "darshan" to us! For Chandu, the sight of a Small Blue Kingfisher busy over the surface of the pond in the Zoo area made his day; we came home and then went to attend the QuizFamilies monthly quiz.
Having returned home and finally slept at nearly 2am, I was up again by 4am to cook something for the BULBs outing to Galibore...which did not last all day as earlier planned, due to it becoming rather muggy and hot...but for all that, it was a very enjoyable outing, especially as we drove home in pouring rain through the late afternoon, with Uma, Suma and I singing old Hindi songs that the men in the back seat had to put up with!
The entire morning, the internet connection has been playing truant, and I am just beginning the process of uploading the photos and video...so if I get to complete the process, I'll share my weekend in more detail...
I realize that most of my photography and writing is on the net, so a net connection that doesn't work wastes a lot of my time....grrrrr.
| 88.318182 | 453 | 0.768914 | eng_Latn | 0.999809 |
22f38a0c97f0228c60e772b56914c15c40bdc0ce | 67 | md | Markdown | README.md | almostengr/mkdocs-template | 540e97f44d295f23b17bbd240e443fbb5d17770d | [
"MIT"
] | null | null | null | README.md | almostengr/mkdocs-template | 540e97f44d295f23b17bbd240e443fbb5d17770d | [
"MIT"
] | 4 | 2020-12-29T17:20:51.000Z | 2021-07-15T23:32:26.000Z | README.md | almostengr/mkdocs-template | 540e97f44d295f23b17bbd240e443fbb5d17770d | [
"MIT"
] | null | null | null | # mkdocs-template
Template used for creating websites with mkdocs | 22.333333 | 48 | 0.820896 | eng_Latn | 0.958575 |
22f4f08e40a7d580a8dfe65ff447a512eed551a5 | 808 | md | Markdown | content/home/hero.md | dburkhardt/gruenlab | 14c0ba5e57d6139d13c67a7d433f01065ff8f881 | [
"MIT"
] | null | null | null | content/home/hero.md | dburkhardt/gruenlab | 14c0ba5e57d6139d13c67a7d433f01065ff8f881 | [
"MIT"
] | null | null | null | content/home/hero.md | dburkhardt/gruenlab | 14c0ba5e57d6139d13c67a7d433f01065ff8f881 | [
"MIT"
] | null | null | null | ---
# A Demo section created with the Blank widget.
# Any elements can be added in the body: https://wowchemy.com/docs/writing-markdown-latex/
# Add more sections by duplicating this file and customizing to your requirements.
widget: jumbotron # See https://wowchemy.com/docs/page-builder/
headless: true # This file represents a page section.
weight: 10 # Order that this section will appear.
active: false
title: "Gruen Laboratory"
subtitle: "Unravelling the genetics of reading"
design:
background:
image: heros/bike_group.color.jpeg
image_darken: 0.5
image_parallax: false
image_position: center
image_size: cover
image_blur: 3px
text_color_light: true
advanced:
css_style: "height: 100vh;" #56.25vw;"
css_class:
---
{{< button text="Learn more" url="#about-us">}}
| 29.925926 | 90 | 0.732673 | eng_Latn | 0.877218 |
22f5cc63371fa15dd9a1b85729bb8576a8a6023b | 1,179 | md | Markdown | README.md | andre000/cotabox-fullstack-challenge | 7e157d088c6ee7d2a2015102d8517ec96b6591ad | [
"MIT"
] | null | null | null | README.md | andre000/cotabox-fullstack-challenge | 7e157d088c6ee7d2a2015102d8517ec96b6591ad | [
"MIT"
] | null | null | null | README.md | andre000/cotabox-fullstack-challenge | 7e157d088c6ee7d2a2015102d8517ec96b6591ad | [
"MIT"
] | null | null | null | <h1>cotabox-challenge</h1>
<p>
<img alt="Version" src="https://img.shields.io/badge/version-1.0.0-blue.svg?cacheSeconds=2592000" />
<a href="#" target="_blank">
<img alt="License: MIT" src="https://img.shields.io/badge/License-MIT-yellow.svg" />
</a>
</p>
> Project made to fullfill the [Cotabox Full-Stack Challenge](https://github.com/Cotabox/fullstack-challenge)
## About
The following technologies were used to build this project:
- Typescript
- Lerna
- MongoDB
- Redis
- Winston
- GraphQL
- Express
- Jest
- Nuxt
- Chart.js
- Element UI
- SCSS
## Requirements
- Yarn
- Docker
## Install
```sh
yarn install
```
## Usage
Before running the project, run:
```sh
docker-compose up -d
```
then
```sh
yarn run dev
```
Links:
- Front-end: http://localhost:3001/
- Back-end: http://localhost:3000/graphql
## Run tests
Right now only unit test for the api are available
```sh
yarn run test
```
## Author
👤 **Andre L. Adriano**
* Github: [@andre000](https://github.com/andre000)
## Show your support
Give a ⭐️ if this project helped you!
***
_This README was generated with ❤️ by [readme-md-generator](https://github.com/kefranabg/readme-md-generator)_
| 15.513158 | 110 | 0.684478 | eng_Latn | 0.62482 |
22f6423ee06251d7d4f3f74930d134ec92eb1c3e | 2,454 | md | Markdown | _posts/2015-12-20-Lafemme-Gigi-Prom-Dresses-Style-18841.md | queenosestyle/queenosestyle.github.io | 7b095a591cefe4e42cdeb7de71cfa87293a95b5c | [
"MIT"
] | null | null | null | _posts/2015-12-20-Lafemme-Gigi-Prom-Dresses-Style-18841.md | queenosestyle/queenosestyle.github.io | 7b095a591cefe4e42cdeb7de71cfa87293a95b5c | [
"MIT"
] | null | null | null | _posts/2015-12-20-Lafemme-Gigi-Prom-Dresses-Style-18841.md | queenosestyle/queenosestyle.github.io | 7b095a591cefe4e42cdeb7de71cfa87293a95b5c | [
"MIT"
] | null | null | null | ---
layout: post
date: 2015-12-20
title: "Lafemme Gigi Prom Dresses Style 18841"
category: Lafemme
tags: [Lafemme]
---
### Lafemme Gigi Prom Dresses Style 18841
Just **$489.99**
###
<table><tr><td>BRANDS</td><td>Lafemme</td></tr></table>
<a href="https://www.readybrides.com/en/lafemme/76954-lafemme-gigi-prom-dresses-style-18841.html"><img src="//img.readybrides.com/187457/lafemme-gigi-prom-dresses-style-18841.jpg" alt="Lafemme Gigi Prom Dresses Style 18841" style="width:100%;" /></a>
<!-- break --><a href="https://www.readybrides.com/en/lafemme/76954-lafemme-gigi-prom-dresses-style-18841.html"><img src="//img.readybrides.com/187458/lafemme-gigi-prom-dresses-style-18841.jpg" alt="Lafemme Gigi Prom Dresses Style 18841" style="width:100%;" /></a>
<a href="https://www.readybrides.com/en/lafemme/76954-lafemme-gigi-prom-dresses-style-18841.html"><img src="//img.readybrides.com/187459/lafemme-gigi-prom-dresses-style-18841.jpg" alt="Lafemme Gigi Prom Dresses Style 18841" style="width:100%;" /></a>
<a href="https://www.readybrides.com/en/lafemme/76954-lafemme-gigi-prom-dresses-style-18841.html"><img src="//img.readybrides.com/187460/lafemme-gigi-prom-dresses-style-18841.jpg" alt="Lafemme Gigi Prom Dresses Style 18841" style="width:100%;" /></a>
<a href="https://www.readybrides.com/en/lafemme/76954-lafemme-gigi-prom-dresses-style-18841.html"><img src="//img.readybrides.com/187461/lafemme-gigi-prom-dresses-style-18841.jpg" alt="Lafemme Gigi Prom Dresses Style 18841" style="width:100%;" /></a>
<a href="https://www.readybrides.com/en/lafemme/76954-lafemme-gigi-prom-dresses-style-18841.html"><img src="//img.readybrides.com/187462/lafemme-gigi-prom-dresses-style-18841.jpg" alt="Lafemme Gigi Prom Dresses Style 18841" style="width:100%;" /></a>
<a href="https://www.readybrides.com/en/lafemme/76954-lafemme-gigi-prom-dresses-style-18841.html"><img src="//img.readybrides.com/187463/lafemme-gigi-prom-dresses-style-18841.jpg" alt="Lafemme Gigi Prom Dresses Style 18841" style="width:100%;" /></a>
<a href="https://www.readybrides.com/en/lafemme/76954-lafemme-gigi-prom-dresses-style-18841.html"><img src="//img.readybrides.com/187456/lafemme-gigi-prom-dresses-style-18841.jpg" alt="Lafemme Gigi Prom Dresses Style 18841" style="width:100%;" /></a>
Buy it: [https://www.readybrides.com/en/lafemme/76954-lafemme-gigi-prom-dresses-style-18841.html](https://www.readybrides.com/en/lafemme/76954-lafemme-gigi-prom-dresses-style-18841.html)
| 111.545455 | 264 | 0.747759 | yue_Hant | 0.125082 |
22f6f74e4544dfc63cf58889deaee8531bbdbef4 | 3,345 | md | Markdown | docs/internals/struct_merge_rope_chunks_info.md | fredericbonnet/colibri | ea3995f4c56a98762005a7962a24a93a5dca5ccd | [
"BSD-3-Clause"
] | 1 | 2019-11-25T15:17:11.000Z | 2019-11-25T15:17:11.000Z | docs/internals/struct_merge_rope_chunks_info.md | fredericbonnet/colibri | ea3995f4c56a98762005a7962a24a93a5dca5ccd | [
"BSD-3-Clause"
] | 3 | 2021-06-28T20:31:04.000Z | 2022-02-26T02:04:38.000Z | docs/internals/struct_merge_rope_chunks_info.md | fredericbonnet/colibri | ea3995f4c56a98762005a7962a24a93a5dca5ccd | [
"BSD-3-Clause"
] | null | null | null | <a id="struct_merge_rope_chunks_info"></a>
# Structure MergeRopeChunksInfo
![][C++]
![][private]
**Definition**: `src/colRope.c` (line 1996)
Structure used to collect data during the traversal of ropes when merged into one string.
**See also**: [MergeRopeChunksProc](col_rope_8c.md#group__rope__words_1ga33ffefe10088e23594b6f76a1d65e184)
## Members
* [byteLength](struct_merge_rope_chunks_info.md#struct_merge_rope_chunks_info_1a889f1160b5a99df78a69be735160ebc0)
* [data](struct_merge_rope_chunks_info.md#struct_merge_rope_chunks_info_1a6076ccd35f62ed7fc5331cee6e250f77)
* [format](struct_merge_rope_chunks_info.md#struct_merge_rope_chunks_info_1a625645c02156390018fde6af588ec907)
* [length](struct_merge_rope_chunks_info.md#struct_merge_rope_chunks_info_1ac2003de1c200f18c3bf5ab9a1bd12bd4)
## Public attributes
<a id="struct_merge_rope_chunks_info_1a625645c02156390018fde6af588ec907"></a>
### Variable format
![][public]
**Definition**: `src/colRope.c` (line 1997)
```cpp
Col_StringFormat MergeRopeChunksInfo::format
```
Character format in buffer.
**Type**: [Col\_StringFormat](colibri_8h.md#group__strings_1ga125054104f6260ea3902e6e46ebfdfa0)
**Referenced by**:
* [MergeRopeChunksProc](col_rope_8c.md#group__rope__words_1ga33ffefe10088e23594b6f76a1d65e184)
* [Col\_Subrope](col_rope_8h.md#group__rope__words_1ga688a99f26c500c1f65f4141e97de0335)
* [Col\_ConcatRopes](col_rope_8h.md#group__rope__words_1gaafab3ef159c0b11402cc50c91fc59700)
<a id="struct_merge_rope_chunks_info_1a6076ccd35f62ed7fc5331cee6e250f77"></a>
### Variable data
![][public]
**Definition**: `src/colRope.c` (line 1998)
```cpp
char MergeRopeChunksInfo::data[MAX_SHORT_LEAF_SIZE][MAX_SHORT_LEAF_SIZE]
```
Buffer storing the flattened data.
**Type**: char
**Referenced by**:
* [MergeRopeChunksProc](col_rope_8c.md#group__rope__words_1ga33ffefe10088e23594b6f76a1d65e184)
* [Col\_Subrope](col_rope_8h.md#group__rope__words_1ga688a99f26c500c1f65f4141e97de0335)
* [Col\_ConcatRopes](col_rope_8h.md#group__rope__words_1gaafab3ef159c0b11402cc50c91fc59700)
<a id="struct_merge_rope_chunks_info_1ac2003de1c200f18c3bf5ab9a1bd12bd4"></a>
### Variable length
![][public]
**Definition**: `src/colRope.c` (line 1999)
```cpp
size_t MergeRopeChunksInfo::length
```
Character length so far.
**Type**: size_t
**Referenced by**:
* [MergeRopeChunksProc](col_rope_8c.md#group__rope__words_1ga33ffefe10088e23594b6f76a1d65e184)
* [Col\_Subrope](col_rope_8h.md#group__rope__words_1ga688a99f26c500c1f65f4141e97de0335)
* [Col\_ConcatRopes](col_rope_8h.md#group__rope__words_1gaafab3ef159c0b11402cc50c91fc59700)
<a id="struct_merge_rope_chunks_info_1a889f1160b5a99df78a69be735160ebc0"></a>
### Variable byteLength
![][public]
**Definition**: `src/colRope.c` (line 2000)
```cpp
size_t MergeRopeChunksInfo::byteLength
```
Byte length so far.
**Type**: size_t
**Referenced by**:
* [MergeRopeChunksProc](col_rope_8c.md#group__rope__words_1ga33ffefe10088e23594b6f76a1d65e184)
* [Col\_Subrope](col_rope_8h.md#group__rope__words_1ga688a99f26c500c1f65f4141e97de0335)
* [Col\_ConcatRopes](col_rope_8h.md#group__rope__words_1gaafab3ef159c0b11402cc50c91fc59700)
[public]: https://img.shields.io/badge/-public-brightgreen (public)
[C++]: https://img.shields.io/badge/language-C%2B%2B-blue (C++)
[private]: https://img.shields.io/badge/-private-red (private) | 26.975806 | 113 | 0.811659 | yue_Hant | 0.310491 |
22f813210c46a9950d534615c2e1d9aab04eaada | 743 | md | Markdown | README.md | dagibu301/advice | 1c0a6ec79bebfe7a12afe5c90fe0c8d79b3b0a11 | [
"MIT"
] | null | null | null | README.md | dagibu301/advice | 1c0a6ec79bebfe7a12afe5c90fe0c8d79b3b0a11 | [
"MIT"
] | null | null | null | README.md | dagibu301/advice | 1c0a6ec79bebfe7a12afe5c90fe0c8d79b3b0a11 | [
"MIT"
] | null | null | null | # Advice App :notebook:
## :computer: Description
React application to get randomly advices from [Advice Slip JSON API](https://api.adviceslip.com/)
## :star: Live Preview :star:
Go to: [advice-dbg.netlify.app/](https://advice-dbg.netlify.app/)
## :space_invader: Technologies used
This project was developed using this technologies:
- [React](https://reactjs.org/)
- [TypeScript](https://www.typescriptlang.org/)
- [SASS](https://sass-lang.com/documentation/syntax)
## :memo: License
This project is under the license of MIT. See here the archive [LICENSE](LICENSE.md) for more details.
---
Done with :purple_heart: by David Giraldo :wave: | 28.576923 | 102 | 0.736205 | eng_Latn | 0.392466 |
22f8ec6fca1d7b94209612036b8b541b0bca7712 | 21 | md | Markdown | README.md | morajlab/registry | e4f375874872c1b3f8661777e662168ae864180a | [
"MIT"
] | null | null | null | README.md | morajlab/registry | e4f375874872c1b3f8661777e662168ae864180a | [
"MIT"
] | null | null | null | README.md | morajlab/registry | e4f375874872c1b3f8661777e662168ae864180a | [
"MIT"
] | null | null | null | # Moraj Lab registry
| 10.5 | 20 | 0.761905 | epo_Latn | 0.585242 |
22fa52925ff0947d75d58f071a59a0a6177ab800 | 350 | md | Markdown | README.md | r4b3rt/hisilicon-dvr-telnet | 82b0a92c6f05cb564ada1f7acd67bc3c1b9b6664 | [
"MIT"
] | 119 | 2020-02-04T14:34:29.000Z | 2022-03-18T21:48:29.000Z | README.md | r4b3rt/hisilicon-dvr-telnet | 82b0a92c6f05cb564ada1f7acd67bc3c1b9b6664 | [
"MIT"
] | 4 | 2020-02-06T17:04:53.000Z | 2020-12-16T04:23:26.000Z | README.md | r4b3rt/hisilicon-dvr-telnet | 82b0a92c6f05cb564ada1f7acd67bc3c1b9b6664 | [
"MIT"
] | 67 | 2020-02-05T03:29:15.000Z | 2022-02-04T22:16:14.000Z | # hisilicon-dvr-telnet
PoC materials for article https://habr.com/en/post/486856/
---
:heart: :heart: :heart:
You can say thanks to the author by donations to these wallets:
- ETH: `0xB71250010e8beC90C5f9ddF408251eBA9dD7320e`
- BTC:
- Legacy: `1N89PRvG1CSsUk9sxKwBwudN6TjTPQ1N8a`
- Segwit: `bc1qc0hcyxc000qf0ketv4r44ld7dlgmmu73rtlntw`
---
| 19.444444 | 63 | 0.76 | eng_Latn | 0.40152 |
22faa6c36f2ee01626ad9768a3ba67a04171a1ec | 3,033 | md | Markdown | content/article/2012/01/07.md | nuclear-power-engineering/nuclear-power-engineering | fd875dba1758419624d323edf299d0c314dc8365 | [
"MIT"
] | null | null | null | content/article/2012/01/07.md | nuclear-power-engineering/nuclear-power-engineering | fd875dba1758419624d323edf299d0c314dc8365 | [
"MIT"
] | 28 | 2016-07-18T20:07:55.000Z | 2021-05-26T08:05:30.000Z | content/article/2012/01/07.md | nuclear-power-engineering/nuclear-power-engineering | fd875dba1758419624d323edf299d0c314dc8365 | [
"MIT"
] | null | null | null | +++
categories="article"
date="2012-05-29T00:17:00+03:00"
issue="2012-01"
issue_name="2012 - №01"
number="7"
file = "https://static.nuclear-power-engineering.ru/articles/2012/01/07.pdf"
udc="621.039.58"
title="Прогнозирование ресурса оборудования АЭС в условиях эрозионно-коррозионного износа на основе эмпирической модели"
authors=["GulinaOM", "FrolovaOO"]
tags=["трубопровод", "толщина стенки", "скорость эрозионно-коррозионного износа", "коэффициент келлера", "химсостав"]
rubric = "safety"
rubric_name = "Безопасность, надежность и диагностика ЯЭУ"
doi="https://doi.org/10.26583/npe.2012.1.07"
+++
Для прогнозирования ресурса оборудования АЭС в условиях ЭКИ использована модель ЧексалаГурвица, реализованная в коде ЭКИ-02, включающая в себя 12 наиболее значимых параметров, в том числе коэффициент Келлера, характеризующий геометрию элемента. Известные значения этого коэффициента получены по данным лабораторных исследований и опыта эксплуатации зарубежных АЭС. В работе для расчета коэффициента Келлера и оценки его статистических характеристик по данным эксплуатации и материалам российских блоков разработана процедура, получены оценки скорости ЭКИ по данным оперативного контроля и на основании прогноза по эмпирической модели выполнена оценка вероятностных характеристик коэффициентов Келлера для различных элементов трубопроводов разных типоразмеров. Для оценки погрешности, связанной с влиянием химсостава на скорость ЭКИ, выполнена сравнительная оценка скорости ЭКИ по уравнению Дюрекса (с данными замеров химсостава) со скоростью ЭКИ, рассчитанной по ЭКИ-02.
### Ссылки
1. Бараненко В.И., Янченко Ю.А., Гулина О.М., Докукин Д.А. О расчете скорости эрозионно-коррозионного износа и остаточного ресурса трубопроводов АЭС//Известия вузов. Ядерная энергетика. – 2010. – № 3.
2. Бараненко В.И, Гулина О.М., Ампилогов М.О. О прогнозировании длительности эксплуатации элементов трубопроводных систем АЭС, подверженных эрозионно-коррозионному износу/ Сборник ВНИИАЭС «Основные работы, выполненные в ВНИИАЭС в 2010 г.». – М.: ВНИИАЭС. – С. 81-94.
3. Бараненко В.И., Янченко Ю.А., Гулина О.М. и др. Эксплуатационный контроль трубопроводов, подверженных эрозионно-коррозионному износу//Теплоэнергетика. 2009. – № 5. – С. 20-27.
4. Бараненко В.И., Олейник С.Г., Янченко Ю.А. и др. Использование программных средств для расчета эрозионно-коррозионного износа элементов трубопроводных систем АЭС//Теплоэнергетика. – 2003. – № 11. – С. 21-24.
5. Chexal V.K. (Bind), Horowitz J.S. Chexal-Horowitz Flow-Accelerated Corrosion Model-Parameter and Influences. Current perspective of Inter. Pressure Vessels and Piping: Codes and Standard. Book No. 409768. – 1995. – P. 231-243.
6. Регистрационный паспорт аттестации ПС ЭКИ-02 № 165 от 19.09.2003 г.
7. Регистрационный паспорт аттестации ПС ЭКИ-03 № 202 от 23.06.2005 г.
8. Zheng Y. A steady state FAC model in carbon steel and its application on practical geometries by means of CFD/FAC2010 International conference on Flow Accelerated Corrosion (May 4-7 2010, Lion, France). – 18 p. | 101.1 | 971 | 0.792615 | rus_Cyrl | 0.866818 |
22fad958da50089251008186dfa33eac6dee6604 | 2,371 | md | Markdown | _posts/2017/2017-11-11-knights-gp-free.md | BlogHolder/BlogHolder.github.io | 18fafe5e1fc910a314ba0b19550d5f9ae2aad45b | [
"MIT"
] | null | null | null | _posts/2017/2017-11-11-knights-gp-free.md | BlogHolder/BlogHolder.github.io | 18fafe5e1fc910a314ba0b19550d5f9ae2aad45b | [
"MIT"
] | null | null | null | _posts/2017/2017-11-11-knights-gp-free.md | BlogHolder/BlogHolder.github.io | 18fafe5e1fc910a314ba0b19550d5f9ae2aad45b | [
"MIT"
] | null | null | null | ---
id: 736
title: KNIGHTS (Android) Free For A Limited Time!
date: 2017-11-11T23:02:13+00:00
author: Arzola
layout: post
permalink: /knights-gp-free/
image: /wp-content/uploads/2017/11/KNIGHTS-Is-Temporarily-Free-On-Android.png
categories:
- Announcements
- "Arzola's Games"
- KNIGHTS
- Sales
tags:
- Android
- "Arzola's"
- Game
- Google Play
- Image
- KNIGHTS
- Sales
---
## You Heard It Right
For three days only, you can get the Google Play version of KNIGHTS **COMPLETELY FREE**! (Unlimited supplies, but still, a one-of-a-kind type of deal).
Want to play it later? Sure, go ahead, you only need to click install and it is yours forever. Just try not to miss it because it will hardly happen again.
<a href="https://play.google.com/store/apps/details?id=com.HeIsArzola.KNIGHTS" target="_blank" rel="noopener" data-elementor-open-lightbox="default"><br /> <img src="/images/posts/2017/11/Google-Play-Banner.png" /> </a>
## What? Never Heard Of The Game?
Not going to blame you, you can catch up <a href="/KNIGHTS/" target="_blank" rel="noopener">here</a>. Or just watch the trailer:
<span class="embed-youtube" style="text-align:center; display: block;"></span>
## What’s The Catch? Why So Chill About Giving It For Free?
Getting noticed with a premium app on Google Play is hard, especially when you don’t want to include micro-transactions or ads anywhere. If you want to keep your game pure these type of promotion boosts aren’t uncommon, but at the same time will never be frequent, so make use of it!
Of course, you can always _show your love_ for the game (or the developer \*wink wink\*) _**by leaving a rating for the app**_, or <a href="https://play.google.com/store/apps/details?id=com.heisarzola.PEG" target="_blank" rel="noopener">purchasing PEG</a>. Up to you really, but would be _**GREATLY APPRECIATED**_, TO unhealthy levels even!
## But regardless of what you do…
Thank you for showing interest for the game. Even if no “direct” support is received, it is still appreciated. And if you are one of those that bought and enjoyed the game then hey! Glad the work was worth it.
But like always, also thank you so much for reading my blog :3
<!-- AddThis Advanced Settings generic via filter on the_content -->
<!-- AddThis Share Buttons generic via filter on the_content --> | 44.735849 | 340 | 0.731759 | eng_Latn | 0.966114 |
22fafcacccc3ff164d49c00204d105d2a5efbc1d | 1,028 | md | Markdown | docs/en/release-note/previous-version/2.5.3_ReleaseNotes.md | DRL9/egret-core | 58dcfff6d3f58bfdcdf611dab27a3bb41d2ad2f6 | [
"BSD-3-Clause"
] | 3,677 | 2015-01-01T09:04:36.000Z | 2022-03-31T17:19:25.000Z | docs/en/release-note/previous-version/2.5.3_ReleaseNotes.md | eos3tion/egret-core | c36a663650f2f4825e37e24733c31b2033fbe0eb | [
"BSD-3-Clause"
] | 312 | 2015-01-07T03:57:55.000Z | 2022-03-31T04:56:43.000Z | docs/en/release-note/previous-version/2.5.3_ReleaseNotes.md | eos3tion/egret-core | c36a663650f2f4825e37e24733c31b2033fbe0eb | [
"BSD-3-Clause"
] | 847 | 2015-01-01T17:00:00.000Z | 2022-03-18T02:51:34.000Z | Egret 2.5.3 Release Note
===============================
Updated on: October, 23th, 2015
Welcome to Egret!
## Overview
In Egret Engine 2.5, we unify the frameworks of game and APP. The new layout would be a core library with third-party libraries so that Egret Engine can flexibly meet the different needs from developing games and APPs. This unification will substantially cut developing cost and improve efficiency. Please find below a detailed description.
## Updated items
This update aggregates all the changes from 2.5.2 to 2.5.3.
* Added wxLocalResource.
* Fixed DataGroup.itemRenderSkinName bug
* Fixed GUI&EUI default log error alert.
* Text input display anomaly under certain circumstances.
* EUI added BitmapLabel.
* Published project can display fps panel.
* Dirty rectangle’s drawing disorder caused by the inaccurate measurement of Bitmap and Graphics .
* Fixed the measuring problem of BitmapText.
* EUI can set null and use default skin.
#### Roadmap
* Add support for WebGL.
* Add filter function. | 31.151515 | 340 | 0.756809 | eng_Latn | 0.966458 |
22fc0596e97fc2d7186e6f6878e71d2c5fee47f4 | 27 | md | Markdown | readme.md | Zdeenal/cakeshop | bb702ace258ce5928c21a1c0fb268bb1a46e39f6 | [
"MIT"
] | null | null | null | readme.md | Zdeenal/cakeshop | bb702ace258ce5928c21a1c0fb268bb1a46e39f6 | [
"MIT"
] | null | null | null | readme.md | Zdeenal/cakeshop | bb702ace258ce5928c21a1c0fb268bb1a46e39f6 | [
"MIT"
] | null | null | null | Cake shop
================= | 13.5 | 17 | 0.296296 | oci_Latn | 0.953041 |
22fd6edfccca21d479b979a9621b7a33f38a982c | 14,534 | md | Markdown | articles/marketplace/cloud-partner-portal/azure-applications/cpp-skus-tab.md | salem84/azure-docs.it-it | 3ec6a13aebb82936591c7fc479f084be9bb8776d | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/marketplace/cloud-partner-portal/azure-applications/cpp-skus-tab.md | salem84/azure-docs.it-it | 3ec6a13aebb82936591c7fc479f084be9bb8776d | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/marketplace/cloud-partner-portal/azure-applications/cpp-skus-tab.md | salem84/azure-docs.it-it | 3ec6a13aebb82936591c7fc479f084be9bb8776d | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Configurare gli SKU per un'offerta di applicazione di Azure | Azure Marketplace
description: Come configurare gli SKU per un'applicazione gestita di Azure e un modello di soluzione di Azure.
services: Azure, Marketplace, Cloud Partner Portal,
author: dan-wesley
ms.service: marketplace
ms.topic: conceptual
ms.date: 04/23/2019
ms.author: pabutler
ms.openlocfilehash: ef4ea2419c64d0376023ea5d291460df48a51c63
ms.sourcegitcommit: d4dfbc34a1f03488e1b7bc5e711a11b72c717ada
ms.translationtype: MT
ms.contentlocale: it-IT
ms.lasthandoff: 06/13/2019
ms.locfileid: "64943423"
---
# <a name="azure-application-skus-tab"></a>Scheda SKU per un'applicazione Azure
Questo articolo descrive come usare la scheda SKU per creare gli SKU per l'applicazione Azure.
> [!IMPORTANT]
> La procedura per la configurazione di uno SKU è diversa per un'offerta di applicazione gestita e un'offerta di modello di soluzione. Queste differenze sono documentate in questo articolo.
## <a name="configure-azure-application-skus"></a>Configurare gli SKU per l'applicazione Azure
### <a name="create-a-new-sku"></a>Creare un nuovo SKU
Seguire questa procedura per creare un nuovo SKU:
1. Selezionare la scheda **SKU**.
2. In SKU selezionare **+ Nuovo SKU**.
3. Nella finestra popup Nuovo SKU digitare un **ID SKU**. Questo ID non può superare i 50 caratteri e deve contenere solo caratteri alfanumerici minuscoli, trattini o caratteri di sottolineatura. L'ID SKU non può terminare con un trattino.
4. L'ID SKU è visibile ai clienti negli URL dei prodotti, nei modelli di Resource Manager (se applicabile) e nei report di fatturazione. Dopo aver pubblicato l'offerta, non sarà possibile modificare questo ID.
### <a name="sku-details-for-a-solution-template"></a>Dettagli dello SKU per un modello di soluzione
La schermata successiva mostra il modulo dei dettagli dello SKU per un modello di soluzione.
Specificare i valori SKU seguenti. I campi aggiunti con un asterisco sono obbligatori.
| Campo | Descrizione |
| --------- | --------------- |
| **Titolo\*** | Un titolo per lo SKU. Questo titolo viene visualizzato nella raccolta di questo elemento. |
| **Riepilogo\*** | Una breve descrizione di riepilogo dello SKU. (La lunghezza massima consentita è di 100 caratteri.) |
| **Descrizione\*** | Una descrizione dettagliata dello SKU. Codice HTML di base è supportata. |
| **Tipo di SKU\*** | Tipo di soluzione di applicazione di Azure, selezionare ***modello di soluzione** per questo scenario. |
| **Disponibilità dei cloud\*** | La posizione dello SKU. Il valore predefinito è **Azure pubblico**. <b/> **Azure pubblico** -App potrà essere distribuito ai clienti in tutte le aree pubbliche di Azure che sono l'integrazione di marketplace. <b/> **Azure Government Cloud** -App verrà distribuita nel Cloud per enti pubblici di Azure. Prima della pubblicazione in [Azure per enti pubblici](https://docs.microsoft.com/azure/azure-government/documentation-government-manage-marketplace-partners), Microsoft consiglia di server di pubblicazione di test e convalidare il funzionamento della soluzione come previsto in questo ambiente. Per lo staging e il test, richiedere un [account di prova](https://azure.microsoft.com/offers/ms-azr-usgov-0044p/). |
| **Si tratta di uno SKU privato?\*** | Selezionare **Sì** se questo SKU è disponibile solo per un gruppo selezionato di clienti. |
| | |
> [!NOTE]
> Microsoft Azure per enti pubblici è una soluzione cloud della community di enti pubblici con accesso controllato per i clienti degli enti federali, statali e locali degli Stati Uniti E dei partner che forniscono servizi a tali enti.
### <a name="sku-details-for-managed-application"></a>Dettagli dello SKU per un'applicazione gestita
La schermata successiva mostra il modulo Dettagli SKU per un'applicazione gestita.
Configurare le impostazioni della SKU seguenti. I campi aggiunti con un asterisco sono obbligatori.
| Campo | Descrizione |
| --------- | --------------- |
| **Titolo\*** | Un titolo per lo SKU. Questo titolo viene visualizzato nella raccolta di questo elemento. |
| **Riepilogo\*** | Una breve descrizione di riepilogo dello SKU. (La lunghezza massima consentita è di 100 caratteri.) |
| **Descrizione\*** | Una descrizione dettagliata dello SKU. Codice HTML di base è supportata. |
| **Tipo di SKU\*** | Tipo di soluzione di applicazione di Azure, selezionare ***Managed Application** per questo scenario.
| **Disponibilità dei cloud\*** | La posizione dello SKU. Il valore predefinito è **Azure pubblico**. <b/> **Azure pubblico** -App potrà essere distribuito ai clienti in tutte le aree pubbliche di Azure che sono l'integrazione di marketplace. <b/> **Azure Government Cloud** -App verrà distribuita nel Cloud per enti pubblici di Azure. Prima della pubblicazione in [Azure per enti pubblici](https://docs.microsoft.com/azure/azure-government/documentation-government-manage-marketplace-partners), Microsoft consiglia di server di pubblicazione di test e convalidare il funzionamento della soluzione come previsto in questo ambiente. Per lo staging e il test, richiedere un [account di prova](https://azure.microsoft.com/offers/ms-azr-usgov-0044p/). Microsoft Azure per enti pubblici è una soluzione cloud della community di enti pubblici con accesso controllato per i clienti degli enti federali, statali e locali degli Stati Uniti E dei partner che forniscono servizi a tali enti. |
| **Si tratta di uno SKU privato?\*** | Selezionare **Sì** se questo SKU è disponibile solo per un gruppo selezionato di clienti. |
| **Disponibilità paese/area geografica\*** | Uso **selezionare le aree** per visualizzare l'elenco di paesi/aree geografiche disponibili. Selezionare ogni paese/area geografica e quindi scegliere **OK** per salvare le selezioni effettuate. <b/>  |
| **Prezzi precedente\*** | Il prezzo per lo SKU, in USD al mese. I prezzi sono impostati nella valuta locale in base ai tassi di cambio correnti al momento della configurazione. Si consiglia di verificarli trattandosi di impostazioni personali. Per impostare o visualizzare il prezzo di ogni paese/area geografica singolarmente, esportare il foglio di calcolo dei prezzi e importarlo con i prezzi personalizzati. È necessario salvare le modifiche ai prezzi per abilitare l'esportazione/importazione dei dati sui prezzi. |
| **Prezzi di valuta semplificata\*** | Il prezzo per lo SKU, in USD al mese. Deve corrispondere al prezzo precedente. Per altre informazioni, vedere [Prezzi di valuta semplificata](https://docs.microsoft.com/azure/marketplace/cloud-partner-portal-orig/cloud-partner-portal-update-existing-offer). |
| | |
### <a name="package-details-for-solution-template"></a>Dettagli del pacchetto per un modello di soluzione
Specificare le informazioni seguenti **dettagli del pacchetto** valori. I campi aggiunti con un asterisco sono obbligatori.
- **Versione\*** -la versione del pacchetto da caricare. I tag di versione devono essere nel formato X.Y.Z, dove X, Y e Z sono numeri interi.
- **File del pacchetto (zip)\*** -questo pacchetto contiene i file seguenti, salvati in un file con estensione zip.
- applianceMainTemplate.json: file del modello di distribuzione usato per distribuire la soluzione/applicazione e creare le risorse definite per la soluzione. Per altre informazioni, vedere [come creare i file del modello di distribuzione](https://docs.microsoft.com/azure/azure-resource-manager/resource-manager-create-first-template).
- createUIDefinition.json: questo file viene usato dal portale di Azure per generare l'interfaccia utente per il provisioning di questa soluzione/applicazione. Per altre informazioni, vedere [Creare l'interfaccia utente del portale di Azure per l'applicazione gestita](https://docs.microsoft.com/azure/azure-resource-manager/managed-application-createuidefinition-overview).
>[!IMPORTANT]
>Questo pacchetto deve contenere gli eventuali modelli annidati o gli script necessari per completare il provisioning di questa applicazione. Il file MainTemplate.json e il file createUIDefinition.json devono trovarsi nella cartella radice.
### <a name="package-details-for-managed-application"></a>Dettagli del pacchetto per un'applicazione gestita
Fornire i dettagli del pacchetto seguenti. I campi aggiunti con un asterisco sono obbligatori.
- **Versione\*** -la versione del pacchetto da caricare. I tag di versione devono essere nel formato X.Y.Z, dove X, Y e Z sono numeri interi.
- **File del pacchetto (zip)\*** -questo pacchetto contiene i file seguenti, salvati in un file con estensione zip.
- applianceMainTemplate.json: file del modello di distribuzione usato per distribuire la soluzione/applicazione e creare le risorse definite. Per altre informazioni, vedere [Avvio rapido: Creare e distribuire modelli di Azure Resource Manager con il portale di Azure](https://docs.microsoft.com/azure/azure-resource-manager/resource-manager-quickstart-create-templates-use-the-portal).
- applianceCreateUIDefinition.json: questo file viene usato dal portale di Azure per generare l'interfaccia utente per il provisioning di questa soluzione/applicazione. Per altre informazioni, vedere [Creare l'interfaccia utente del portale di Azure per l'applicazione gestita](https://docs.microsoft.com/azure/azure-resource-manager/managed-application-createuidefinition-overview).
- mainTemplate.json: file del modello contenente solo le risorse Microsoft.Solution/appliances. Per altre informazioni, vedere [Comprendere la struttura e la sintassi dei modelli di Azure Resource Manager](https://docs.microsoft.com/azure/azure-resource-manager/resource-group-authoring-templates). <br>
Prendere nota delle proprietà chiave seguenti di questa risorsa:
- “kind”: il valore deve essere "Marketplace" in caso di applicazione gestita di Marketplace.
- “ManagedResourceGroupId”: il gruppo di risorse nella sottoscrizione del cliente in cui vengono distribuite tutte le risorse definite nel file applianceMainTemplate.json.
- "PublisherPackageId": la stringa che identifica il pacchetto in modo univoco. Questo valore deve essere costruito nel modo seguente: si tratta di una concatenazione di [publisherId].[OfferId]-preview[SKUID].[PackageVersion].
>[!IMPORTANT]
>Questo pacchetto deve contenere gli eventuali modelli annidati o gli script necessari per completare il provisioning di questa applicazione. Questi file devono trovarsi nella cartella radice: MainTemplate.json, applianceMainTemplate.json e applianceCreateUIDefinition.json.
- **Id tenant\*** -id tenant di Azure Active Directory dell'organizzazione.
- **Abilitare l'accesso JIT? \*** -Selezionare **Sì** Just-In-Time di abilitare l'accesso di gestione per le distribuzioni dei clienti usando questa offerta.
>[!NOTE]
>Se si abilita JIT, è necessario aggiornare il file CreateUiDefinition.json per supportare l'accesso JIT.
Per un'applicazione gestita, è necessario configurare Autorizzazione e Impostazioni dei criteri.
#### <a name="authorization"></a>Authorization
Aggiungere l'identificatore di Azure Active Directory per l'utente, il gruppo o l'applicazione a cui si vuole concedere l'autorizzazione per il gruppo di risorse gestite. L'autorizzazione che viene concessa è indicata dall'ID di definizione del ruolo. Può trattarsi di un proprietario, collaboratore o un ruolo personalizzato.
#### <a name="policy-settings"></a>Impostazioni dei criteri
Aggiungere i criteri a cui l'app gestita è conforme. Per altre informazioni sui criteri delle risorse di Azure, vedere [Informazioni su Criteri di Azure](../../../governance/policy/overview.md).
**Per creare una nuova autorizzazione:**
1. In **Autorizzazione** selezionare **+ Nuova autorizzazione**.
2. Per **ID entità di sicurezza**, digitare l'identificatore di Azure Active Directory per l'utente, il gruppo o l'applicazione a cui si vuole concedere l'autorizzazione per il gruppo di risorse gestite. L'autorizzazione che viene concessa è indicata da Definizione ruolo.
3. Per **Definizione ruolo**, selezionare una di queste opzioni nell'elenco a discesa: Proprietario o Collaboratore. Per altre informazioni, vedere [Ruoli predefiniti per le risorse di Azure](https://docs.microsoft.com/azure/role-based-access-control/built-in-roles).
>[!NOTE]
>È possibile aggiungere più autorizzazioni. È tuttavia consigliabile creare un gruppo utenti di Active Directory e specificarne l'ID in "PrincipalId". Consentirà di aggiungere altri utenti al gruppo utenti senza dover aggiornare lo SKU.
**Per creare un nuovo criterio:**
1. In **Impostazioni dei criteri** selezionare **+ Nuovo criterio**.
2. Per **Nome criterio**, immettere un nome per il criterio. La lunghezza massima del nome è di 50 caratteri.
3. Per **Criteri**, selezionare una delle opzioni nell'elenco a discesa. Scegliere i criteri che il provider di dati vuole abilitare quando l'applicazione usa i dati. Per altre informazioni, vedere [Esempi di Criteri di Azure](https://docs.microsoft.com/azure/governance/policy/samples/index).
4. Per **SKU criteri**, selezionare Gratuito o Standard come tipo di SKU dei criteri. Lo SKU Standard è necessario per i criteri di controllo.
## <a name="next-steps"></a>Passaggi successivi
Verrà ulteriormente descrivere l'offerta e fornire gli asset di marketing nel [scheda Marketplace](./cpp-marketplace-tab.md).
| 91.408805 | 990 | 0.761938 | ita_Latn | 0.998711 |
22fdfae95241c27d765fc2feab6032d3b97bd63c | 6,988 | md | Markdown | _text/07/chap0710.md | Christ-Mind-Teachings/oe | 4badeac0bf1c5ad7006ea387ca53d728b4c26105 | [
"MIT"
] | 1 | 2020-08-11T06:56:45.000Z | 2020-08-11T06:56:45.000Z | _text/07/chap0710.md | Christ-Mind-Teachings/oe | 4badeac0bf1c5ad7006ea387ca53d728b4c26105 | [
"MIT"
] | 6 | 2020-11-13T00:30:29.000Z | 2022-03-10T00:53:32.000Z | _text/07/chap0710.md | Christ-Mind-Teachings/oe | 4badeac0bf1c5ad7006ea387ca53d728b4c26105 | [
"MIT"
] | 1 | 2020-08-11T23:30:19.000Z | 2020-08-11T23:30:19.000Z | ---
chapter: Seven
ctitle: The Consistency of the Kingdom
title: The Extension of the Kingdom
ref: Tx.7.X
---
<sup>91</sup> Only *you* can limit your creative power, but God wills to release
it. He no more wills you to deprive yourself of your creations than He
wills to deprive Himself of His. Do not withhold your gifts to the
Sonship, or you withhold yourself from God. Selfishness is of the ego,
but self-fullness is of the Soul, because that is how God created it.
The Holy Spirit is the part of the mind that lies between the ego and
the Soul, mediating between them *always* in favor of the Soul. To the
ego, this is partiality, and it therefore responds as if it were the
part that is being sided *against*. To the Soul, this is truth, because
it knows its fullness and cannot conceive of any part from which it is
excluded.
<sup>92</sup> The Soul *knows* that the consciousness of all its brothers is
included in its own, as *it* is included in God. The power of the whole
Sonship *and* of its Creator is therefore the Soul's own fullness,
rendering its creations equally whole and equal in perfection. The ego
cannot prevail against a totality which includes God, and any totality
*must* include God. Everything He created is given all His power,
because it is part of Him and shares His Being with Him. Creating is the
opposite of loss, as blessing is the opposite of sacrifice. Being *must*
be extended. That is how it retains the knowledge of *itself.*
<sup>93</sup> The Soul yearns to share its being as *its* Creator did. Created *by*
sharing, its will is to create. It does not wish to *contain* God but to
*extend* His Being. The extension of God's Being is the Soul's *only*
function. Its fullness cannot be contained any more than can the
fullness of its Creator. Fullness *is* extension. The ego's whole
thought system blocks extension and thus blocks your only function. It
therefore blocks your joy, and that is why you perceive yourselves as
unfulfilled. Unless you create, you *are* unfulfilled; but God does not
know of unfulfillment, and therefore you *must* create. *You* may not
know your own creations, but this can no more interfere with their
reality than your unawareness of your Soul can interfere with its being.
<sup>94</sup> The Kingdom is forever extending, because it is in the Mind of God.
You do not *know* your joy, because you do not know your own
self-fullness. Exclude *any* part of the Kingdom from yourself, and you
are *not* whole. A split mind cannot perceive its fullness and needs the
miracle of its wholeness to dawn upon it and heal it. This reawakens the
wholeness in it and restores it to the Kingdom because of its
*acceptance* of wholeness. The full appreciation of its self-fullness
makes selfishness impossible and extension inevitable. That is why there
is perfect peace in the Kingdom. Every Soul *is* fulfilling its
function, and only complete fulfillment *is* peace.
<sup>95</sup> Insanity *appears* to add to reality, but no one would claim that
what it adds is true. Insanity is therefore the *non*\-extension of
truth, which blocks joy because it blocks creation and thus blocks
self-fulfillment. The unfulfilled *must* be depressed, because their
self-fullness is unknown to them. Your creations are protected *for*
you, because the Holy Spirit, Who is in your mind, knows of them and can
bring them *into* your awareness whenever you will let Him. They are
there as part of your own being, because your fulfillment *includes*
them. The creations of every Son of God are yours since every creation
belongs to everyone, being created for the Sonship as a whole.
<sup>96</sup> You have *not* failed to add to the inheritance of the Sons of God
and thus have not failed to secure it for yourselves. If it was the Will
of God to give it to you, He gave it forever. If it was His Will that
you have it forever, He gave you the means for keeping it, *and you have
done so*. Disobeying God's Will is meaningful only to the insane. In
truth it is impossible. Your self-fullness is as boundless as God's.
Like His, it extends forever and in perfect peace. Its radiance is so
intense that it creates in perfect joy, and only the whole can be born
of its wholeness.
<sup>97</sup> Be confident that you have never lost your identity and the
extensions which maintain it in wholeness and peace. Miracles are an
*expression* of this confidence. They are reflections both of your own
proper identification with your brothers and of your own awareness that
your identification *is* maintained by extension. The miracle is a
*lesson in total perception*. By including *any* part of totality in the
lesson, you *have* included the whole. You have said that when you write
of the Kingdom and your creations which belong in it, you are describing
*what you do not know.* That is true in a sense, but no more true than
your failure to acknowledge the whole result of the ego's premises. The
Kingdom is the result of premises, just as this world is.
<sup>98</sup> You *have* carried the ego's reasoning to its logical conclusion,
which is *total confusion about everything*. Yet you do not really
*believe* this, or you could not possibly maintain it. If you really saw
this result, you could not *want* it. The only reason why you could
possibly want *any* part of it is because you do *not* see the whole of
it. You \[therefore\] are willing to look at the ego's premises but
*not* at their logical outcome. Is it not possible that you have done
the same thing with the premises of God?
<sup>99</sup> Your creations *are* the logical outcome of His premises. *His*
thinking has established them *for* you. They are therefore there,
*exactly* where they belong. They belong in your mind as part of your
identification with His, but your state of mind and your recognition of
what is *in* your mind depend at any given moment on what you believe
*about* your mind. Whatever these beliefs may be, they are the premises
which will determine what you accept *into* your mind. It is surely
clear that you can both accept into your mind what is not really there
and deny what *is*. Neither of these possibilities requires further
elaboration here, but both are clearly indefensible, even if you elect
to defend them.
<sup>100</sup> Yet the function which God Himself gave your minds through His you
may deny, but you cannot prevent. It is the logical outcome of what you
*are*. The ability to see a logical outcome depends on the *willingness*
to see it, but its truth has nothing to do with your willingness at all.
Truth is *God's* Will. *Share* His Will, and you share what He knows.
*Deny* His Will as yours, and you are denying His Kingdom *and* yours.
The Holy Spirit will direct you only so as to avoid pain. The undoing of
pain must obviously avoid pain. Surely no one would object to this goal
*if he recognized it*. The problem is not whether what the Holy Spirit
says is true, but whether you want to *listen* to what He says.
| 59.220339 | 83 | 0.775615 | eng_Latn | 0.999997 |
22fe62b44f7da0681b568be51fe59af808cffee6 | 16 | md | Markdown | README.md | phuyen/luu- | 40e84e2f62fb89b5c938ba9d579920864bd71c07 | [
"Apache-2.0"
] | null | null | null | README.md | phuyen/luu- | 40e84e2f62fb89b5c938ba9d579920864bd71c07 | [
"Apache-2.0"
] | null | null | null | README.md | phuyen/luu- | 40e84e2f62fb89b5c938ba9d579920864bd71c07 | [
"Apache-2.0"
] | null | null | null | # luu-
nhu tren
| 5.333333 | 8 | 0.625 | vie_Latn | 0.865422 |
22ff81b3c64b4157c4599e0c90cc242943a6aeb5 | 1,155 | md | Markdown | README.md | a24/Tween24 | a432a1b1d554113e0498be7666944095a57b4c8e | [
"MIT"
] | 10 | 2015-01-26T05:58:33.000Z | 2022-01-12T07:00:07.000Z | README.md | a24/Tween24 | a432a1b1d554113e0498be7666944095a57b4c8e | [
"MIT"
] | null | null | null | README.md | a24/Tween24 | a432a1b1d554113e0498be7666944095a57b4c8e | [
"MIT"
] | 1 | 2015-07-14T10:24:55.000Z | 2015-07-14T10:24:55.000Z | Tween24
=======
Tween24 is Tween library for ActionScript 3.
(MIT License)
**lastest version:** 2.0.1
[http://package.a24.cat/tween24/](http://package.a24.cat/tween24/)
Introduction
--------------------------
「思いついた演出をすぐに実装したい」
「頭の中ではできているのに、コーディングするのが面倒」
と、感じることはありませんか？
Flashコンテンツを作る上で欠かせないトゥイーンライブラリ。TweenerやBeTweenAS3など、使ったことのある方も多いと思います。私自身、使い慣れているという点でTweenerをよく使っていましたが、いくつかの不満点がありました。
* 機能が少ない。
* トゥイーンを単体でしか再生できない。
* フィルタ系のプロパティを扱うのが面倒。
* transitionをtransitoinにタイプミスする。
* そもそもタイピングするのが面倒。
などなど
これらの点を解消するために、新しいライブラリ「Tween24」を開発しました。
[download source code](https://github.com/a24/Tween24/archive/master.zip)
メソッドチェーンで、新感覚コーディング
----------------------------------------
```as3
// 例）Tweenerの場合
FilterShortcuts.init();
Tweener.addTween(target, { time:1, transition:"linear", x:100, y:200, _Blur_blurX:16, _Blur_blurY:16 } );
// 例）Tween24の場合
Tween24.tween(target, 1, Ease24._Linear).xy(100, 200).blur(16, 16).play();
```
メソッドチェーンで指定することにより、以下のようなメリットがあります。
* エディタのコード補完をフル活用できるので、タイピング数を劇的に減らします。
* 補完機能によりプロパティ名などを覚える必要がなく、タイプミスもなくなります。
* ASDocなどのドキュメントを読まなくても、補完リストで全ての機能を大体把握することができます。
* 一つのメソッドで複数のプロパティを設定できるので、コードを簡潔に書くことができます。
| 22.647059 | 120 | 0.744589 | yue_Hant | 0.381345 |
fe024644e03b3043e7888f5497da64076838c3fd | 1,121 | md | Markdown | user/pages/04.contact/contact.md | retsoced/camera-shop-theme | aecc3cf211ae7abb1f88ba37b1f09d34bfd1d696 | [
"MIT"
] | 1 | 2018-07-30T02:58:36.000Z | 2018-07-30T02:58:36.000Z | user/pages/04.contact/contact.md | retsoced/camera-shop-theme | aecc3cf211ae7abb1f88ba37b1f09d34bfd1d696 | [
"MIT"
] | 1 | 2020-04-30T16:14:38.000Z | 2020-04-30T16:14:38.000Z | user/pages/04.contact/contact.md | retsoced/camera-shop-theme | aecc3cf211ae7abb1f88ba37b1f09d34bfd1d696 | [
"MIT"
] | null | null | null | ---
title: How to find us
menu: Contact
in_menu: true
hide_submenu: true
og:
description: 'Lorem ipsum dolar set amet'
image: facebook-image.jpg
body_classes: contact
two_column: true
address: 'right'
hero_image: 'map.jpg'
recaptchacontact:
inject_template: false
form_legend: "Contact Us"
subject: "Website contact form submission"
recipient: "[email protected]"
fields:
name:
label: "Name:"
placeholder: "Enter your name"
email:
label: "Email:"
placeholder: "Enter your email address"
message:
label: "Type your message"
placeholder: "Let us know what's on your mind"
messages:
success: "Hurray! You did it!"
---
**Want to know how to find us?**
Bacon ipsum dolor amet ham chicken turkey, shankle sausage leberkas t-bone. Ground round tenderloin swine jowl cow kevin, meatloaf capicola. Venison doner short ribs beef pork cupim, alcatra corned beef. Turducken chicken prosciutto ham tenderloin drumstick shoulder pork loin kevin porchetta boudin short loin swine meatloaf hamburger. Salami buffalo cupim pastrami meatloaf pork beef ribs.
| 29.5 | 391 | 0.73149 | eng_Latn | 0.685799 |
fe031d67fb822138894b4df466d4b9e28075c35e | 330 | md | Markdown | _posts/2017-08-21-photos-partial-eclipse-2017.md | jonkit/jonkit.github.io | a667f7543c14f393f6af2078bf5284c74911c66d | [
"MIT"
] | null | null | null | _posts/2017-08-21-photos-partial-eclipse-2017.md | jonkit/jonkit.github.io | a667f7543c14f393f6af2078bf5284c74911c66d | [
"MIT"
] | null | null | null | _posts/2017-08-21-photos-partial-eclipse-2017.md | jonkit/jonkit.github.io | a667f7543c14f393f6af2078bf5284c74911c66d | [
"MIT"
] | null | null | null | ---
layout: photos
category: photos
hidden: true
date: 2017-08-21 15:31:58 -0400
permalink: partial-eclipse-2017
title: "Partial Eclipse 2017"
---
The sun is blown out and not in-focus but there’s a weird lens reflection showing the eclipse.
| 25.384615 | 95 | 0.751515 | eng_Latn | 0.863629 |
fe0375b55bf8c01e9094f65c4b77834f27916af1 | 1,336 | md | Markdown | _posts/2022-04-09-1st.md | alstjq9295/wassup.github.com | 7c8bd19d3eba6573e358e34e4170c1c4ebfae0e5 | [
"MIT"
] | null | null | null | _posts/2022-04-09-1st.md | alstjq9295/wassup.github.com | 7c8bd19d3eba6573e358e34e4170c1c4ebfae0e5 | [
"MIT"
] | null | null | null | _posts/2022-04-09-1st.md | alstjq9295/wassup.github.com | 7c8bd19d3eba6573e358e34e4170c1c4ebfae0e5 | [
"MIT"
] | null | null | null | ---
layout: default
title: "Install flutter & android studio"
description: "MBTI 관련 인스타그램 데이터 기반 서비스 만들기"
tags: [Blog, Flutter, Dart]
date: 2022-04-09
last_modified_at: 2022-04-09
---
```
* 2022 1Q DMK Study
- MBTI 관련 인스타그램 데이터 기반 서비스 만들기
```
## Install flutter
- `윈도우의 경우 사용자명이 한글이면 설치가 안되니 주의!`
- `한글명 사용자일 경우 영문명 사용자 추가 필요`
- [OS별 (stable version) URL](https://docs.flutter.dev/get-started/install?gclid=EAIaIQobChMIuO_w4qeG9wIVWnRgCh2WcAkDEAAYASAAEgLIDfD_BwE&gclsrc=aw.ds)
- [버전별 URL](https://docs.flutter.dev/development/tools/sdk/releases)
- 환경변수 설정 필요
- [Flutter Icon 찾아보기 URL](https://fonts.google.com/icons?selected=Material+Icons)
## Install android studio
- [공홈](https://developer.android.com/studio?gclid=EAIaIQobChMI-67Nqq2G9wIViSRgCh2g5g3yEAAYASAAEgK78PD_BwE&gclsrc=aw.ds)
- 필수 plugin: flutter
## Flutter sources
- 참조 URL: [코딩애플 유튜브](https://www.youtube.com/watch?v=usE9IKaogDU&list=PLfLgtT94nNq1izG4R2WDN517iPX4WXH3C)
- [2022-04-03 Study](https://github.com/alstjq9295/blog/blob/main/_sources/20220403_main.dart)
- [2022-04-09 Study](https://github.com/alstjq9295/blog/blob/main/_sources/20220409_main.dart)
- [2022-04-10 1st Study](https://github.com/alstjq9295/blog/blob/main/_sources/20220410_6th_main.dart)
- [2022-04-10 2nd Study](https://github.com/alstjq9295/blog/blob/main/_sources/20220410_7th_main.dart)
| 41.75 | 149 | 0.761976 | kor_Hang | 0.727628 |
fe048e6d5e5d301c625bb49f8ad3d613d93a3cfb | 477 | md | Markdown | docs/LV_client/tutorials/Weather.md | andresgonzalez2/monodrive-documentation | e459e803fc1ef6f87beaf2b1b6fea21f92ed6467 | [
"MIT"
] | 7 | 2020-06-11T21:35:15.000Z | 2021-04-19T03:45:33.000Z | docs/LV_client/tutorials/Weather.md | andresgonzalez2/monodrive-documentation | e459e803fc1ef6f87beaf2b1b6fea21f92ed6467 | [
"MIT"
] | 126 | 2020-03-03T22:30:40.000Z | 2021-07-30T16:08:24.000Z | docs/LV_client/tutorials/Weather.md | andresgonzalez2/monodrive-documentation | e459e803fc1ef6f87beaf2b1b6fea21f92ed6467 | [
"MIT"
] | 4 | 2018-09-11T09:52:10.000Z | 2019-09-26T06:35:41.000Z | ## Change Weather
Learn how to change the weather using the LabVIEW Client. The monoDrive simulator allows you to simulate any of the following weather conditions during the day or at sunset: sunny, cloudy, rain, fog, etc.
<div class="img_container">
<iframe width="750" height="400" src="https://www.youtube.com/embed/MPHjGZKyQMw" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
</div>
<p> </p>
| 53 | 204 | 0.765199 | eng_Latn | 0.921396 |
fe04d2966a0d68fd554e8cdc222c9b153bb95144 | 6,286 | md | Markdown | articles/azure-maps/map-add-tile-layer.md | changeworld/azure-docs.pl-pl | f97283ce868106fdb5236557ef827e56b43d803e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/azure-maps/map-add-tile-layer.md | changeworld/azure-docs.pl-pl | f97283ce868106fdb5236557ef827e56b43d803e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/azure-maps/map-add-tile-layer.md | changeworld/azure-docs.pl-pl | f97283ce868106fdb5236557ef827e56b43d803e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Dodawanie warstwy kafelków do mapy | Mapy platformy Microsoft Azure
description: W tym artykule dowiesz się, jak nakładać warstwę kafli na mapę przy użyciu zestawu SDK w sieci Web map platformy Microsoft Azure. Warstwy kafelków umożliwiają renderowanie obrazów na mapie.
author: rbrundritt
ms.author: richbrun
ms.date: 07/29/2019
ms.topic: conceptual
ms.service: azure-maps
services: azure-maps
manager: ''
ms.custom: codepen
ms.openlocfilehash: 61d7a11df499e6b740adb45968721b6a9bb1af22
ms.sourcegitcommit: 2ec4b3d0bad7dc0071400c2a2264399e4fe34897
ms.translationtype: MT
ms.contentlocale: pl-PL
ms.lasthandoff: 03/27/2020
ms.locfileid: "76988604"
---
# <a name="add-a-tile-layer-to-a-map"></a>Dodawanie warstwy kafelków do mapy
W tym artykule pokazano, jak nałożyć warstwę kafli na mapę. Warstwy kafelków umożliwiają nakładanie obrazów na kafelki map bazowych usługi Azure Maps. Aby uzyskać więcej informacji na temat systemu kafli usługi Azure Maps, zobacz [Poziomy powiększenia i siatka kafli](zoom-levels-and-tile-grid.md).
Warstwa kafli jest ładowana w kafelkach z serwera. Obrazy te mogą być wstępnie renderowane lub renderowane dynamicznie. Wstępnie renderowane obrazy są przechowywane jak każdy inny obraz na serwerze przy użyciu konwencji nazewnictwa, którą rozumie warstwa kafli. Dynamicznie renderowane obrazy używają usługi do ładowania obrazów w czasie zbliżonym do czasu rzeczywistego. Istnieją trzy różne konwencje nazewnictwa usługi kafelków obsługiwane przez klasę Azure Maps [TileLayer:](https://docs.microsoft.com/javascript/api/azure-maps-control/atlas.layer.tilelayer?view=azure-iot-typescript-latest)
* X, Y, Powiększenie notacji - X to kolumna, Y to położenie wiersza kafelka w siatce kafelków, a notacja Powiększenia jest wartością opartą na poziomie powiększenia.
* Notacja quadkey - Łączy informacje x, y i zoom do pojedynczej wartości ciągu. Ta wartość ciągu staje się unikatowym identyfikatorem pojedynczego kafelka.
* Obwiednia - Określ obraz w formacie `{west},{south},{east},{north}`współrzędnych obwiedni: . Ten format jest powszechnie używany przez [usługi mapowania sieci Web (WMS).](https://www.opengeospatial.org/standards/wms)
> [!TIP]
> A [TileLayer](https://docs.microsoft.com/javascript/api/azure-maps-control/atlas.layer.tilelayer?view=azure-iot-typescript-latest) to świetny sposób wizualizacji dużych zestawów danych na mapie. Nie tylko warstwa kafli może być generowana z obrazu, ale także dane wektorowe mogą być renderowane jako warstwa kafli. Renderowanie danych wektorowych jako warstwy kafelków musi tylko załadować kafelki o mniejszym rozmiarze pliku niż dane wektorowe, które reprezentują. Ta technika jest powszechnie używana do renderowania milionów wierszy danych na mapie.
Adres URL kafelka przekazany do warstwy kafelków musi być adresem URL http lub https do zasobu TileJSON lub szablonem adresu URL kafelka, który używa następujących parametrów:
* `{x}`- X położenie płytki. Również `{y}` potrzebuje `{z}`i .
* `{y}`- Pozycja Y płytki. Również `{x}` potrzebuje `{z}`i .
* `{z}`- Poziom powiększenia płytki. Również `{x}` potrzebuje `{y}`i .
* `{quadkey}`- Identyfikator poczwórki kafelków oparty na konwencji nazewnictwa systemu kafli Bing Maps.
* `{bbox-epsg-3857}`- Ciąg obwiedni z `{west},{south},{east},{north}` formatem w systemie odniesienia przestrzennego EPSG 3857.
* `{subdomain}`- Symbol zastępczy dla wartości poddomeny, jeśli określono `subdomain` zostanie dodany.
## <a name="add-a-tile-layer"></a>Dodawanie warstwy kafelków
W tym przykładzie pokazano, jak utworzyć warstwę kafli, która wskazuje zestaw kafelków. W tym przykładzie użyto systemu kafli x, y, zoom. Źródłem tej warstwy płytek jest nakładka radaru pogodowego z [Iowa Environmental Mesonet z Iowa State University.](https://mesonet.agron.iastate.edu/ogc/) Podczas przeglądania danych radarowych, najlepiej użytkownicy będą wyraźnie widzieć etykiety miast, gdy poruszają się po mapie. To zachowanie można zaimplementować, wstawiając warstwę kafli poniżej warstwy. `labels`
```javascript
//Create a tile layer and add it to the map below the label layer.
//Weather radar tiles from Iowa Environmental Mesonet of Iowa State University.
map.layers.add(new atlas.layer.TileLayer({
tileUrl: 'https://mesonet.agron.iastate.edu/cache/tile.py/1.0.0/nexrad-n0q-900913/{z}/{x}/{y}.png',
opacity: 0.8,
tileSize: 256
}), 'labels');
```
Poniżej znajduje się kompletny przykładowy kod uruchomiony powyższej funkcji.
<br/>
<iframe height='500' scrolling='no' title='Warstwa kafelków przy użyciu X, Y i Z' src='//codepen.io/azuremaps/embed/BGEQjG/?height=500&theme-id=0&default-tab=js,result&embed-version=2&editable=true' frameborder='no' allowtransparency='true' allowfullscreen='true' style='width: 100%;'>Zobacz <a href='https://codepen.io/azuremaps/pen/BGEQjG/'>warstwę kafelków pióra przy użyciu X, Y i Z</a> przez usługi Azure Maps (<a href='https://codepen.io/azuremaps'>@azuremaps</a>) na funkcji <a href='https://codepen.io'>CodePen</a>.
</iframe>
## <a name="customize-a-tile-layer"></a>Dostosowywanie warstwy kafli
Klasa warstwy kafli ma wiele opcji stylizacji. Oto narzędzie, aby je wypróbować.
<br/>
<iframe height='700' scrolling='no' title='Opcje warstwy kafelków' src='//codepen.io/azuremaps/embed/xQeRWX/?height=700&theme-id=0&default-tab=result' frameborder='no' allowtransparency='true' allowfullscreen='true' style='width: 100%;'>Zobacz <a href='https://codepen.io/azuremaps/pen/xQeRWX/'>opcje warstwy kafelków</a> <a href='https://codepen.io/azuremaps'>@azuremaps</a>pióra według usługi Azure Maps ( ) na <a href='https://codepen.io'>funkcji CodePen</a>.
</iframe>
## <a name="next-steps"></a>Następne kroki
Dowiedz się więcej o klasach i metodach użytych w tym artykule:
> [!div class="nextstepaction"]
> [Warstwa płytek](https://docs.microsoft.com/javascript/api/azure-maps-control/atlas.layer.tilelayer?view=azure-iot-typescript-latest)
> [!div class="nextstepaction"]
> [TileLayerOptions (TileLayerOptions)](https://docs.microsoft.com/javascript/api/azure-maps-control/atlas.tilelayeroptions?view=azure-iot-typescript-latest)
Aby uzyskać więcej przykładów kodu do dodania do map, zobacz następujące artykuły:
> [!div class="nextstepaction"]
> [Dodawanie warstwy obrazów](./map-add-image-layer.md)
| 73.952941 | 595 | 0.782533 | pol_Latn | 0.99844 |
fe05d4c1fd50a517b102e9fc1b84890863ec498e | 1,919 | md | Markdown | src/_movement/simple-pivot.md | simonwiles/noh | b959c8c114ea3291eed2ffcbc294c19e5d01c24a | [
"MIT"
] | 3 | 2018-11-28T22:48:33.000Z | 2020-06-16T17:54:42.000Z | src/_movement/simple-pivot.md | simonwiles/noh | b959c8c114ea3291eed2ffcbc294c19e5d01c24a | [
"MIT"
] | 317 | 2017-10-27T21:40:33.000Z | 2021-09-22T20:45:57.000Z | src/_movement/simple-pivot.md | simonwiles/noh | b959c8c114ea3291eed2ffcbc294c19e5d01c24a | [
"MIT"
] | 3 | 2020-03-10T20:50:12.000Z | 2021-09-21T22:20:47.000Z | ---
layout: website
name: simple-pivot
filter-act:
filter-type:
second-level-menu-active: movement
---
{% include second-menu-elements.html %}
<main class="page-content">
<div class="text-container">
<h4>
<a href="/movement/">Catalog of Patterns:</a> Structural Patterns / Foot
Motion: Turning
</h4>
<h2>Simple pivot (<em>nejiru</em>)</h2>
<p>
To perform a Simple pivot to the right (<em>migi nejiru</em>), the dancer
slides his right heel out, then slides his left foot parallel to the right
one. To turn left (<em>hidari nejiru</em>), the movement is reversed.
</p>
<p>
The Simple pivot produces a softer turn than the
<a href="/movement/step-pivot/">Step pivot</a>.
</p>
</div>
<div class="tabs-container">
<div class="tabs-container__links">
<div class="wrapper">
<div id="tabs"></div>
</div>
</div>
<div class="tabs-container__content">
<div class="wrapper">
<section id="tab-1" title="Feminine (Right)">
{% include video-no-background.html
src="https://d3msn78fivoryj.cloudfront.net/Dance_sl/Kata-Ona_migi_wo_nejiru.mp4"
%}
</section>
<section id="tab-2" title="Feminine (Left)">
{% include video-no-background.html
src="https://d3msn78fivoryj.cloudfront.net/Dance_sl/Kata-Ona_hidari_wo_nejiru.mp4"
%}
</section>
<section id="tab-3" title="Martial (Right)">
{% include video-no-background.html
src="https://d3msn78fivoryj.cloudfront.net/Dance_sl/Kata-Han_migi_wo_nejiru.mp4"
%}
</section>
<section id="tab-4" title="Martial (Left)">
{% include video-no-background.html
src="https://d3msn78fivoryj.cloudfront.net/Dance_sl/Kata-Han_hidari_wo_nejiru.mp4"
%}
</section>
</div>
</div>
</div>
</main>
| 29.075758 | 92 | 0.604482 | eng_Latn | 0.392701 |
fe06ef77c41f0f7cfd488b18ea4b363888c0a456 | 337 | md | Markdown | _posts/mohaeng/2021-06-28-course-view-design.md | iamcho2/iamcho2.github.io | d49ac0e5beed6ea55a2127b20c284e7c513b944e | [
"MIT"
] | 2 | 2021-04-08T04:37:59.000Z | 2021-07-06T01:25:23.000Z | _posts/mohaeng/2021-06-28-course-view-design.md | iamcho2/iamcho2.github.io | d49ac0e5beed6ea55a2127b20c284e7c513b944e | [
"MIT"
] | null | null | null | _posts/mohaeng/2021-06-28-course-view-design.md | iamcho2/iamcho2.github.io | d49ac0e5beed6ea55a2127b20c284e7c513b944e | [
"MIT"
] | null | null | null | ---
layout: post
title: "코스 뷰 설계"
date: 2021-06-28
category: read
excerpt: ""
---
# Course 뷰 설계
 | 24.071429 | 118 | 0.756677 | kor_Hang | 0.107811 |
fe07d55afad4d478233cafabcd6d361c000656ec | 209 | md | Markdown | README.md | tmarasco125/soundSling | a2a36db4f296bc242736861c9dc1db7d80f67152 | [
"MIT"
] | null | null | null | README.md | tmarasco125/soundSling | a2a36db4f296bc242736861c9dc1db7d80f67152 | [
"MIT"
] | null | null | null | README.md | tmarasco125/soundSling | a2a36db4f296bc242736861c9dc1db7d80f67152 | [
"MIT"
] | null | null | null | # SoundSling
SoundSling is a tool that allows for physics-based audio diffusion across many mobile devices.
Anthony T. Marasco
LSU Experimental Music & Digital Media (2018)
Still in a development phase....
| 23.222222 | 94 | 0.784689 | eng_Latn | 0.984097 |
fe0898ad3fb490694770b19559ab4f133f769edf | 1,481 | md | Markdown | README.md | moningisridhar/WeatherApp | ef7988946ab24c5f3a6f7887ebf901201bf74aca | [
"MIT"
] | null | null | null | README.md | moningisridhar/WeatherApp | ef7988946ab24c5f3a6f7887ebf901201bf74aca | [
"MIT"
] | null | null | null | README.md | moningisridhar/WeatherApp | ef7988946ab24c5f3a6f7887ebf901201bf74aca | [
"MIT"
] | null | null | null |
* Building an app with AngularJS (of course!)
* Building an app based on the [OpenWeatherMap API](http://openweathermap.org/API/)
* Bootstrapping an AngularJS app: Basic modules and view definition, ng-app, ng-view
* Defining a controller for handling the weather data in $scope
* Defining a service for fetching weather data from openweathermap.com via JSONP
* Defining a custom directive for instantly embedding sort of "weather data day panel"
* Setting up unit and e2e-tests with karma/jasmine
weatherapp uses:
* [AngularJS v1.5.9](https://github.com/angular/angular.js)
* [angular-seed](https://github.com/angular/angular-seed)
* [iso-3166-country-codes-angular](https://github.com/BluePyth/iso-3166-country-codes-angular)
* [Bootstrap v3.0.0](https://github.com/twbs/bootstrap)
## Installation
### Clone repository and install dependencies
via git and npm:
```
$ git clone https://github.com/moningisridhar/WeatherApp.git [my-app-name]
$ cd [my-app-name]
$ npm install
```
### Run application via server
You can pick one of these options:
1. serve this repository with a webserver of-your-choice
2. having installed node.js, you can run a script starting a simple web server:
```
$ ./scripts/web-server.js
```
Then navigate your browser to `http://localhost:<port>/app/index.html` to see the app running in
your browser.
### Run tests
To run unit and end-2-end tests with karma/jasmine, call these scripts:
```
$ ./scripts/test.sh
$ ./scripts/e2e-test.sh
```
| 28.480769 | 96 | 0.743417 | eng_Latn | 0.85448 |
fe08d72d57aa6debd7f48d5d4d62c3997beffa9b | 11,785 | md | Markdown | articles/cloud-services/cloud-services-nodejs-chat-app-socketio.md | marcduiker/azure-docs.nl-nl | 747ce1fb22d13d1e7c351e367c87810dd9eafa08 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/cloud-services/cloud-services-nodejs-chat-app-socketio.md | marcduiker/azure-docs.nl-nl | 747ce1fb22d13d1e7c351e367c87810dd9eafa08 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/cloud-services/cloud-services-nodejs-chat-app-socketio.md | marcduiker/azure-docs.nl-nl | 747ce1fb22d13d1e7c351e367c87810dd9eafa08 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Node.js-toepassing met Socket.io | Microsoft Docs
description: Informatie over het gebruik van socket.io in een node.js-toepassing die wordt gehost op Azure.
services: cloud-services
documentationcenter: nodejs
author: craigshoemaker
manager: routlaw
editor:
ms.assetid: 7f9435e0-7732-4aa1-a4df-ea0e894b847f
ms.service: cloud-services
ms.workload: tbd
ms.tgt_pltfrm: na
ms.devlang: nodejs
ms.topic: article
ms.date: 08/17/2017
ms.author: cshoe
ms.openlocfilehash: 0b4c3c540e27ba06a722cfec4f0c079f19ce7f67
ms.sourcegitcommit: e38120a5575ed35ebe7dccd4daf8d5673534626c
ms.translationtype: MT
ms.contentlocale: nl-NL
ms.lasthandoff: 11/13/2017
---
# <a name="build-a-nodejs-chat-application-with-socketio-on-an-azure-cloud-service"></a>Het bouwen van een Node.js-chattoepassing met Socket.IO op een Azure Cloudservice
Socket.IO biedt realtime-communicatie tussen tussen uw node.js-server en clients. Deze zelfstudie helpt u bij het hosten van een socket. I/o gebaseerd chatprogramma op Azure. Zie voor meer informatie over Socket.IO <http://socket.io/>.
Een schermopname van de voltooide toepassing lager is dan:
![Een browservenster met de service die wordt gehost op Azure][completed-app]
## <a name="prerequisites"></a>Vereisten
Zorg ervoor dat de volgende producten en versies zijn geïnstalleerd om te voltooien in het voorbeeld in dit artikel:
* [Visual Studio](https://www.visualstudio.com/en-us/downloads/download-visual-studio-vs.aspx) installeren
* [Node.js](https://nodejs.org/download/) installeren
* Installeer [Python versie 2.7.10](https://www.python.org/)
## <a name="create-a-cloud-service-project"></a>Een Cloud Service-Project maken
De volgende stappen uit maken het cloudserviceproject die als host voor de toepassing Socket.IO fungeert.
1. Van de **startmenu** of **startscherm**, zoeken naar **Windows PowerShell**. Ten slotte de met de rechtermuisknop op **Windows PowerShell** en selecteer **als Administrator uitvoeren**.
![Azure PowerShell-pictogram][powershell-menu]
2. Maak een map met de naam **c:\\knooppunt**.
PS C:\> md node
3. Wijzig de mappen op de **c:\\knooppunt** directory
PS C:\> cd node
4. Voer de volgende opdrachten voor het maken van een nieuwe oplossing met de naam **chatapp** en een werkrol toe met de naam **WorkerRole1**:
PS C:\node> New-AzureServiceProject chatapp
PS C:\Node> Add-AzureNodeWorkerRole
Hier ziet u het volgende antwoord:
## <a name="download-the-chat-example"></a>In het voorbeeld Chat downloaden
Voor dit project, gebruiken we het voorbeeld chat uit de [Socket.IO GitHub-opslagplaats]. Voer de volgende stappen uit om te downloaden van het voorbeeld en toe te voegen aan het project dat u eerder hebt gemaakt.
1. Maken van een lokale kopie van de opslagplaats via de **kloon** knop. U kunt ook de **ZIP** knop voor het downloaden van het project.
![Een browservenster https://github.com/LearnBoost/socket.io/tree/master/examples/chat, weergeven met het pictogram van het ZIP downloaden gemarkeerd][chat-example-view]
2. De mapstructuur van de lokale opslagplaats navigeren totdat u aankomt bij de **voorbeelden\\chat** directory. Kopieer de inhoud van deze map bij de **C:\\knooppunt\\chatapp\\WorkerRole1** directory eerder hebt gemaakt.
![Verkenner weergeven van de inhoud van de voorbeelden\\chat directory opgehaald uit het archief][chat-contents]
De gemarkeerde items in de bovenstaande schermafbeelding zijn de bestanden die zijn gekopieerd uit de **voorbeelden\\chat** directory
3. In de **C:\\knooppunt\\chatapp\\WorkerRole1** directory, verwijdert de **server.js** bestand en wijzig de naam van de **app.js** het bestand in **server.js**. Hiermee verwijdert u de standaard **server.js** bestand dat eerder is gemaakt door de **toevoegen AzureNodeWorkerRole** cmdlet en vervangen door het bestand van de toepassing uit het chat-voorbeeld.
### <a name="modify-serverjs-and-install-modules"></a>Wijzigen van Server.js en -Modules installeren
Voordat u de toepassing test in de Azure-emulator, maken we een aantal kleine wijzigingen. Voer de volgende stappen voor het bestand server.js:
1. Open de **server.js** -bestand in Visual Studio of een teksteditor.
2. Zoek de **Module afhankelijkheden** sectie aan het begin van server.js en wijzigt u de regel die **sio require('.. = //.. lib//socket.IO')** naar **sio require('socket.io') =** zoals hieronder wordt weergegeven:
var express = require('express')
, stylus = require('stylus')
, nib = require('nib')
//, sio = require('..//..//lib//socket.io'); //Original
, sio = require('socket.io'); //Updated
var port = process.env.PORT || 3000; //Updated
3. Om te controleren of de toepassing luistert op de juiste poort, server.js geopend in Kladblok of uw favoriete editor en wijzig vervolgens de volgende regel door te vervangen **3000** met **process.env.port** zoals hieronder wordt weergegeven:
//app.listen(3000, function () { //Original
app.listen(process.env.port, function () { //Updated
var addr = app.address();
console.log(' app listening on http://' + addr.address + ':' + addr.port);
});
Na het opslaan van de wijzigingen in **server.js**, gebruik de volgende stappen voor het installeren van vereiste modules en vervolgens de toepassing in de Azure-emulator te testen:
1. Met behulp van **Azure PowerShell**, wijzig de mappen op de **C:\\knooppunt\\chatapp\\WorkerRole1** directory en gebruik de volgende opdracht de modules installeren door deze toepassing vereist:
PS C:\node\chatapp\WorkerRole1> npm install
Hiermee installeert u de modules die worden vermeld in de package.json-bestand. Nadat u de opdracht is voltooid, ziet u uitvoer ziet er als volgt:
![De uitvoer van de npm-installatieopdracht][The-output-of-the-npm-install-command]
2. Aangezien dit voorbeeld oorspronkelijk een onderdeel van de Socket.IO GitHub-opslagplaats was en rechtstreeks verwijst naar de bibliotheek Socket.IO door relatief pad, Socket.IO is niet waarnaar wordt verwezen in de package.json-bestand, dus er moet worden geïnstalleerd door de volgende opdracht:
PS C:\node\chatapp\WorkerRole1> npm install socket.io --save
### <a name="test-and-deploy"></a>Testen en implementeren
1. Start de emulator door de volgende opdracht:
PS C:\node\chatapp\WorkerRole1> Start-AzureEmulator -Launch
> [!NOTE]
> Als u problemen ondervindt met bijvoorbeeld emulator te starten.: begin AzureEmulator: Er is een onverwachte fout opgetreden. Worden details: Aangetroffen is een onverwachte fout het communicatieobject, System.ServiceModel.Channels.ServiceChannel, kan niet gebruikt voor communicatie omdat het de status Faulted heeft.
Installeer AzureAuthoringTools v 2.7.1 en AzureComputeEmulator v 2.7: Zorg ervoor dat de versie die overeenkomt met.
>
>
2. Open een browser en Ga naar **http://127.0.0.1**.
3. Wanneer het browservenster wordt geopend, voer een bijnaam en klik vervolgens op ENTER drukken.
Hierdoor kunt u om berichten te posten als een specifieke bijnaam. Test de functionaliteit voor meerdere gebruikers, extra browservensters met dezelfde URL te openen en voer verschillende bijnaam.
4. Na de toepassing testen, stopt u de emulator door de volgende opdracht:
PS C:\node\chatapp\WorkerRole1> Stop-AzureEmulator
5. Gebruik voor de implementatie van de toepassing in Azure, de **Publish-AzureServiceProject** cmdlet. Bijvoorbeeld:
PS C:\node\chatapp\WorkerRole1> Publish-AzureServiceProject -ServiceName mychatapp -Location "East US" -Launch
> [!IMPORTANT]
> Zorg ervoor dat u een unieke naam, anders mislukt de het publicatieproces. Nadat de implementatie is voltooid, wordt de browser openen en navigeer naar de geïmplementeerde service.
>
> Als u een foutmelding weergegeven dat de naam van het opgegeven abonnement niet in de geïmporteerde publicatieprofiel bestaat ontvangt, moet u het downloaden en importeer het publicatieprofiel voor uw abonnement voordat u Azure implementeert. Zie de **implementeren van de toepassing in Azure** sectie van [bouwen en implementeren van een Node.js-toepassing naar een Azure Cloud Service](https://azure.microsoft.com/develop/nodejs/tutorials/getting-started/)
>
>
![Een browservenster met de service die wordt gehost op Azure][completed-app]
> [!NOTE]
> Als u een foutmelding weergegeven dat de naam van het opgegeven abonnement niet in de geïmporteerde publicatieprofiel bestaat ontvangt, moet u het downloaden en importeer het publicatieprofiel voor uw abonnement voordat u Azure implementeert. Zie de **implementeren van de toepassing in Azure** sectie van [bouwen en implementeren van een Node.js-toepassing naar een Azure Cloud Service](https://azure.microsoft.com/develop/nodejs/tutorials/getting-started/)
>
>
Uw toepassing wordt nu uitgevoerd in Azure, en kan chatberichten tussen verschillende clients met Socket.IO doorsturen.
> [!NOTE]
> Dit voorbeeld is voor het gemak, beperkt tot chatten tussen gebruikers verbonden met hetzelfde exemplaar. Dit betekent dat als de cloudservice twee exemplaren van worker-rol maakt, gebruikers is alleen mogelijk om te chatten met anderen verbonden met dezelfde worker rolinstantie. Als u wilt schalen van de toepassing met meerdere exemplaren van de functie werkt, kunt u een technologie zoals Service Bus gebruiken voor het delen van de status van de store Socket.IO over exemplaren. Zie voor voorbeelden van de Service Bus-wachtrijen en onderwerpen gebruik voorbeelden in de [Azure SDK voor Node.js GitHub-opslagplaats](https://github.com/WindowsAzure/azure-sdk-for-node).
>
>
## <a name="next-steps"></a>Volgende stappen
In deze zelfstudie hebt u geleerd het maken van een eenvoudige chattoepassing die wordt gehost in een Azure Cloud Service. Zie voor meer informatie over deze toepassing in een Azure-Website te hosten, [een Node.js-chattoepassing met Socket.IO op een Azure-website bouwen][chatwebsite].
Zie voor meer informatie, ook de [Node.js Developer Center](/develop/nodejs/).
[chatwebsite]: /develop/nodejs/tutorials/website-using-socketio/
[Azure SLA]: http://www.windowsazure.com/support/sla/
[Azure SDK for Node.js GitHub repository]: https://github.com/WindowsAzure/azure-sdk-for-node
[completed-app]: ./media/cloud-services-nodejs-chat-app-socketio/socketio-10.png
[Azure SDK for Node.js]: https://www.windowsazure.com/develop/nodejs/
[Node.js Web Application]: https://www.windowsazure.com/develop/nodejs/tutorials/getting-started/
[Socket.IO GitHub-opslagplaats]: https://github.com/LearnBoost/socket.io/tree/0.9.14
[Azure Considerations]: #windowsazureconsiderations
[Hosting the Chat Example in a Worker Role]: #hostingthechatexampleinawebrole
[Summary and Next Steps]: #summary
[powershell-menu]: ./media/cloud-services-nodejs-chat-app-socketio/azure-powershell-start.png
[chat example]: https://github.com/LearnBoost/socket.io/tree/master/examples/chat
[chat-example-view]: ./media/cloud-services-nodejs-chat-app-socketio/socketio-22.png
[chat-contents]: ./media/cloud-services-nodejs-chat-app-socketio/socketio-5.png
[The-output-of-the-npm-install-command]: ./media/cloud-services-nodejs-chat-app-socketio/socketio-7.png
[The output of the Publish-AzureService command]: ./media/cloud-services-nodejs-chat-app-socketio/socketio-9.png
| 66.581921 | 675 | 0.760289 | nld_Latn | 0.997408 |
fe0950a382f313b553b428b1e038331d6a1208d9 | 2,221 | md | Markdown | _posts/Ajax/2019-08-01-ajax+promise.md | Kyounghwan01/test | b42975ff1e2e4fda8bb1f6a4435c03e35f2a8bfc | [
"MIT"
] | 2 | 2019-04-26T13:42:36.000Z | 2019-09-17T10:57:19.000Z | _posts/Ajax/2019-08-01-ajax+promise.md | Kyounghwan01/test | b42975ff1e2e4fda8bb1f6a4435c03e35f2a8bfc | [
"MIT"
] | null | null | null | _posts/Ajax/2019-08-01-ajax+promise.md | Kyounghwan01/test | b42975ff1e2e4fda8bb1f6a4435c03e35f2a8bfc | [
"MIT"
] | 6 | 2019-09-08T06:00:47.000Z | 2021-05-05T17:26:30.000Z | ---
layout: post
title: "[Ajax] Promise + Ajax"
date: 2019-08-01
excerpt: "Ajax 응용 HeakerNes 카피하기"
tag:
- Ajax
category: [Ajax]
feature: https://kyounghwan01.github.io/lala/assets/img/title/bj_title.jpg
comments: false
---
## Ajax + Promise
### 목차
> 1. 해커뉴스 api를 통해 id(key값) 받아오기
> 2. id를 통해 render될 자료를 비동기로 받아와서 console에 id에 해당하는 정보 가져오기
### 1. 해커뉴스 api를 통해 id(key값) 받아오기
> promise를 사용하여 순차적으로 과정이 이루어지게 합니다.
> 그 첫번째로 id가 필요하므로 id를 가져오고 맨 하단의 구문으로 data가 비동기로 잘 가져오는지 확인합니다.
- 아래는 id를 가져오는 코드입니다.
```js
const hackerIdURL = `https://hacker-news.firebaseio.com/v0/topstories.json?print=pretty`;
let newsId;
let newsData = [];
Promise.request1 = () => {
return new Promise(function(resolve, reject) {
var xhr = new XMLHttpRequest();
xhr.open("GET", hackerIdURL, true);
xhr.onload = function() {
if (xhr.status === 200) {
newsId = JSON.parse(xhr.responseText);
resolve(newsId);
} else {
reject("request1 Error: " + xhr.status);
}
};
xhr.send(null);
});
};
Promise.request1().then(data => console.log(data));
```
### 2. id를 통해 render될 자료를 비동기로 받아와서 console에 id에 해당하는 정보 가져오기
> 1번 과정에서 가져온 id를 requset2함수의 인자로 넣어서 해당 id에 맞게 자료를 가져와서 `newsData`에 넣습니다. 비동기적으로 이루어져야 하니 함수를 이용하여 스코프를 만들고 배열이 완성되기 전까지 `resolve` 가 되지 않도록 합니다.
```js
Promise.request2 = param => {
return new Promise((resolve, reject) => {
var i = 0;
function cb() {
if (i < 30) {
var xhr = new XMLHttpRequest();
xhr.open(
"GET",
`https://hacker-news.firebaseio.com/v0/item/${param[i]}.json?print=pretty`,true
);
xhr.onload = function() {
if (xhr.status === 200) {
newsData.push(JSON.parse(xhr.responseText));
i++;
cb();
} else {
reject("request2 Error: " + xhr.status);
}
};
xhr.send(null);
} else {
resolve(newsData);
}
}
cb();
});
};
```
> 완성됬다면 promise pending 후에 `userData` 가 console에 찍히게 됩니다.
```js
Promise.request1().then(data => {
Promise.request2(data)
.then(function(userData) {
console.log(userData);
})
.catch(err => console.log(err));
});
```
| 19.654867 | 145 | 0.583971 | kor_Hang | 0.997522 |
fe0950d34665ea0181377cc4d8cfccf5df2d51f6 | 1,475 | md | Markdown | content/home/talks.md | syzhang/academic-kickstart | 19b3b979baddf17d075bdb5b0a6bc273860b0be2 | [
"MIT"
] | null | null | null | content/home/talks.md | syzhang/academic-kickstart | 19b3b979baddf17d075bdb5b0a6bc273860b0be2 | [
"MIT"
] | null | null | null | content/home/talks.md | syzhang/academic-kickstart | 19b3b979baddf17d075bdb5b0a6bc273860b0be2 | [
"MIT"
] | null | null | null | +++
# Accomplishments widget.
widget = "accomplishments" # See https://sourcethemes.com/academic/docs/page-builder/
headless = true # This file represents a page section.
active = true # Activate this widget? true/false
weight = 50 # Order that this section will appear.
title = "Recent Talks"
subtitle = ""
# Date format
# Refer to https://sourcethemes.com/academic/docs/customization/#date-format
date_format = "Jan-02-06"
# Accomplishments.
# Add/remove as many `[[item]]` blocks below as you like.
# `title`, `organization` and `date_start` are the required parameters.
# Leave other parameters empty if not required.
# Begin/end multi-line descriptions with 3 quotes `"""`.
[[item]]
organization = "International Symposium on Translational Research in Brain Stimulation"
organization_url = "https://tribs.ac.cn"
title = "Brain-machine interfaces for pain enhances endogenous modulation of experienced pain."
url = ""
date_start = "2019-11-09"
date_end = ""
description = "Invited talk as International Travel Award recipient."
[[item]]
organization = "The 11th Congress of the European Pain Federation (EFIC)"
organization_url = "https://efic-congress.org/"
title = "The Reinforcement Learning Model of Pain."
url = ""
date_start = "2019-09-05"
date_end = ""
description = "Invited talk for the symposium 'Avoidance Behaviour in Pain: Insights from Associative Learning, Computational Modelling and Brain Imaging'."
+++ | 36.875 | 158 | 0.728814 | eng_Latn | 0.872987 |
fe0b22fd624fae7960d91eb00f79edae51956f39 | 354 | md | Markdown | README.md | zztwo/ActiveMQ-JDBCAuthenticationPlugin | 6ab4eaaf3d563509291e219c97919de75acff47d | [
"Apache-2.0"
] | null | null | null | README.md | zztwo/ActiveMQ-JDBCAuthenticationPlugin | 6ab4eaaf3d563509291e219c97919de75acff47d | [
"Apache-2.0"
] | null | null | null | README.md | zztwo/ActiveMQ-JDBCAuthenticationPlugin | 6ab4eaaf3d563509291e219c97919de75acff47d | [
"Apache-2.0"
] | null | null | null | # ActiveMQ-JDBCAuthenticationPlugin
ActiveMQ使用JDBC进行连接安全验证的插件。
DB_INIT
CREATE TABLE `conn_users` (
`id` int(10) unsigned NOT NULL,
`username` varchar(45) DEFAULT NULL,
`password` varchar(45) DEFAULT NULL,
`groups` varchar(45) DEFAULT NULL,
PRIMARY KEY (`id`),
UNIQUE KEY `username_UNIQUE` (`username`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
| 25.285714 | 43 | 0.742938 | yue_Hant | 0.849297 |
fe0b318bf8c915178f0016738ae39848694ccbd9 | 147 | md | Markdown | README.md | avancemos/rep | 43523a8438c3b204469e1687f8b508cbceb3a74d | [
"Apache-2.0"
] | null | null | null | README.md | avancemos/rep | 43523a8438c3b204469e1687f8b508cbceb3a74d | [
"Apache-2.0"
] | null | null | null | README.md | avancemos/rep | 43523a8438c3b204469e1687f8b508cbceb3a74d | [
"Apache-2.0"
] | null | null | null | # main
This repo places ads into give images
If your here, your probably lost.
For full [AVAncemos repo](https://github.com/avancemos/AVAncemos)
| 21 | 65 | 0.768707 | eng_Latn | 0.898013 |
fe0cd8162d8bc1596495b5e318ba95d7e7994362 | 413 | md | Markdown | ASSOCIATIONS.md | andreaskdk/firkant | 31b2ac9a0f0fe328f41562474fb3a44d7e3cb0d4 | [
"Apache-2.0"
] | null | null | null | ASSOCIATIONS.md | andreaskdk/firkant | 31b2ac9a0f0fe328f41562474fb3a44d7e3cb0d4 | [
"Apache-2.0"
] | 7 | 2020-07-07T19:04:55.000Z | 2020-07-14T21:30:03.000Z | ASSOCIATIONS.md | andreaskdk/graph2table | 31b2ac9a0f0fe328f41562474fb3a44d7e3cb0d4 | [
"Apache-2.0"
] | null | null | null | # Associations
### Table data sources
#### Keys
- Full cardinality column
- Constrainted on value of another column
- Reduced cardinality column
- Reduced cardinality multiple columns
#### Columns
- Plain full cardinality
- Numerical mean, distribution, min, max, mode
#### Transformations
- URL to domain
- URL to filename
- URL to image
#### Sort
- Lexicographically
- Original order
- By other column
| 14.75 | 46 | 0.731235 | eng_Latn | 0.987572 |
fe0d216dc34b6a66f91011335470a9a314ae2cac | 15,845 | md | Markdown | notes/14-relative.md | DLibatique/LATN102-S20 | b71c37619ae120c6fff978223db1160d714bf498 | [
"CC-BY-3.0"
] | 1 | 2019-12-22T05:14:13.000Z | 2019-12-22T05:14:13.000Z | notes/14-relative.md | DLibatique/LATN102-S20 | b71c37619ae120c6fff978223db1160d714bf498 | [
"CC-BY-3.0"
] | 1 | 2021-07-13T14:51:20.000Z | 2021-07-13T14:51:20.000Z | notes/14-relative.md | DLibatique/LATN102-S20 | b71c37619ae120c6fff978223db1160d714bf498 | [
"CC-BY-3.0"
] | 3 | 2020-03-22T03:03:21.000Z | 2020-03-27T15:38:58.000Z | ---
layout: subpage
title: Module 14 - Relative Clauses
author: DL
permalink: relative
---
***
## Navigation
- [Relative Clauses - Overview](#relative-clauses---overview)
- [Identifying Relative Clauses](#identifying-relative-clauses)
- [Practice Opportunity 1](#practice-opportunity-1)
- [Gender, Number, and Case of Relative Pronouns](#gender-number-and-case-of-relative-pronouns)
- [Practice Opportunity 2](#practice-opportunity-2)
- [Locating the Antecedent](#locating-the-antecedent)
- [Practice Opportunity 3](#practice-opportunity-3)
- [Connecting Relative](#connecting-relative)
- [Relative Clause of Characteristic](#relative-clause-of-characteristic)
- [Practice Opportunity 4](#practice-opportunity-4)
***
## Relative Clauses - Overview
**Relative clauses** are dependent clauses that tell us more about an **antecedent**, which is often a noun or pronoun. Such clauses function adjectivally; they modify the antecedent. Take a look at the following examples:
- The students **who studied for the exam** did well.
- The girl **whom I love** does not love me back.
- The teacher **whose students did well on the exam** was proud.
- I want the chair **which is not broken**.
- The ship **that we can see** does not look seaworthy.
Note that each relative clause is introduced by the word **who** (or its related words, like **whom** or **whose**), **which**, or **that**. Each relative clause describes an **antecedent**: which students? The ones who studied for the exam. Which girl? The one whom I love.
***
## Identifying Relative Clauses
In Latin, relative clauses are introduced by the **relative pronoun, quī, quae, quod ("who, which, that")**. This should hopefully be familiar to you from last semester -- it's the exact same entry as for the **interrogative adjective**. Last semester, we learned that forms of **quī, quae, quod**, when used as an interrogative adjective, modify an explicit noun in the sentence and ask a question: *quī puer?* Which boy? *quae puella?* Which girl?
Here, **quī, quae, quod** as a **relative pronoun** stands on its own and introduces a subordinate clause that contains its own verb and whatever else the verb governs (objects, subjects, prepositional phrases, etc.).
You can find the paradigm chart for the relative pronoun [here](pronoun-chart#relative).
Note also some special translations. The **genitive** of the relative pronoun usually indicates possession, so we can translate it as **"whose"**. Also, when a relative pronoun refers to a person, translations of oblique cases that indicate object status, like an accusative direct object or dative indirect object, will often use the form **"whom"**, since that is the objective form of the relative pronoun in English ("who" is subjective!).
Take a look at the following examples, with the relative clause, introduced by the relative pronoun, in bold:
- vīdimus virōs **quī ā nāvibus veniēbant**. We saw the men **who were coming from the ships**.
- exempla **quae magister mihi dedit** cognoscō. I recognize the examples **that the teacher gave to me.** (magister, magistrī, m. - teacher)
- rex fēminae **ā quā doctus erat** crēdidit. The king trusted the woman **by whom he had been taught**.
Again, the relative clause is a **dependent, subordinate clause**. It is usually introduced by the **relative pronoun** or the preposition that governs it (e.g., **ā** of **ā quā** in the third example), and it usually ends at the first conjugated verb that follows the relative pronoun. It is extremely important to sequester the relative clause so that you translate what belongs to the clause within the clause, without letting the main sentence creep in or vice versa.
In the sentence:
- exempla **quae magister mihi dedit** cognoscō. I recognize the examples **that the teacher gave to me**.
note that the core of the sentence is **exempla cognoscō**, "I recognize the examples." We can extract the relative clause without affecting the coherence of the main sentence. The relative clause simply serves to tell us more information about its antecedent. Which examples do I recognize? The ones that the teacher gave to me.
### Practice Opportunity 1
Identify the relative clause in the following sentences. Do not translate (unless you're feeling adventurous!).
1. monstra nautās quōrum nāvēs vīdimus terruērunt. (terreō, -ēre, -uī, -itus, to terrify, frighten)
<button onclick="toggleDisplay('prac01')">Click here to toggle the answer:</button> <span style="display: none;" id="prac01">quōrum nāvēs vīdimus; The monsters terrified the sailors whose ships we saw.</span>
2. urbs quam regēs regunt septem portās habet. (porta, -ae, f. - gate)
<button onclick="toggleDisplay('prac02')">Click here to toggle the answer:</button> <span style="display: none;" id="prac02">quam regēs regunt; The city which the kings rule has seven gates.</span>
3. mīles ducibus quī ā flūmine veniunt epistulās dābit.
<button onclick="toggleDisplay('prac03')">Click here to toggle the answer:</button> <span style="display: none;" id="prac03">quī ā flūmine veniunt; The soldier will give the letters to the leaders who are coming from the river.</span>
4. verba quae mihi dicenda sunt dīcō.
<button onclick="toggleDisplay('prac04')">Click here to toggle the answer:</button> <span style="display: none;" id="prac04">quae mihi dicenda sunt; I am saying the words that must be said by me.</span>
[Back to top.](#top)
***
## Gender, Number, and Case of Relative Pronouns
This is the most important rule when it comes to using relative pronouns in Latin: **the relative pronoun takes its** ***gender and number*** **from its antecedent, but it takes its** ***case*** **from its use within the relative clause**. As an illustration, take a look at this sentence again:
- vīdimus virōs **quī ā nāvibus veniēbant**. We saw the men **who were coming from the ships**.
According to our chart, the relative pronoun **quī** can be either masculine nominative singular or masculine nominative plural. Either way, it has to be the subject of its clause (because nominative), and the clause contains the plural verb **veniēbant**; therefore, **quī** must be **masculine nominative plural**. Within the relative clause "...who were coming from the ships", "who" / **quī**, our relative pronoun, serves as the subject of "were coming" / **veniēbant**, so it makes sense that that pronoun is nominative. The pronoun takes its case from its function within its clause. To put it differently:
**The relative takes its CASE from its PLACE in its own SPACE.**
Notice, however, that the antecedent of **quī** is **virōs**, which is **masculine accusative plural**. **quī** takes its **gender and number** (masculine and plural) but **NOT its case** from **virōs**. **quī** serves as the subject of the relative clause, but its antecedent **virōs** serves as the direct object of the main clause. Relative pronoun and antecedent share gender and number but not necessarily case.
Another example to illustrate this idea:
- rex fēminae **ā quā doctus erat** crēdidit. The king trusted the woman **by whom he had been taught**.
Our relative pronoun **quā** can only be one thing: feminine ablative singular. It is ablative because it is being used in an ablative of agent construction within the relative clause: **ā quā** doctus erat, "...**by whom** he had been taught." Its gender and number, feminine and singular, come from its antecedent, **fēminae**, which is being used as a dative object of **crēdidit** in the main clause.
### Practice Opportunity 2
In each of the following English sentences, identify the relative clause, and determine what **case and use** the relative pronoun would be in Latin according to its use within the clause. Do not translate into Latin (unless you feel adventurous!).
5. We were attacked by the sailors who had come from the sea.
<button onclick="toggleDisplay('prac05')">Click here to toggle the answer:</button> <span style="display: none;" id="prac05">who had come from the sea; nominative, subject; ā nautīs quī ā marī vēnerant petitī sumus.</span>
6. The citizens to whom we gave peace nevertheless did not encourage us. (tamen - nevertheless)
<button onclick="toggleDisplay('prac06')">Click here to toggle the answer:</button> <span style="display: none;" id="prac06">to whom we gave peace; dative, indirect object; cīvēs quibus pacem dedimus tamen nōs nōn hortātī sunt.</span>
7. He slept near the river from which my family brought the water. (prope + acc. - near)
<button onclick="toggleDisplay('prac07')">Click here to toggle the answer:</button> <span style="display: none;" id="prac07">from which my family brought the water; ablative of motion from; prope flūmen ā quō familia mea aquam tulit dormīvit.</span>
8. I don't trust the woman whose husband we recognized.
<button onclick="toggleDisplay('prac08')">Click here to toggle the answer:</button> <span style="display: none;" id="prac08">whose husband we recognized; genitive of possession; fēminae cuius maritum cognōvimus nōn crēdō.</span>
[Back to top.](#top)
***
## Locating the Antecedent
The relative clause will often be located close to its antecedent, but sometimes it is not. For example, I could easily rewrite the sentence above as:
- rex fēminae crēdidit **ā quā doctus erat**.
When it isn't immediately clear what the antecedent of a relative pronoun is, you must use the **gender and number** of the relative pronoun to try to figure it out. **quā** is feminine singular, so we're looking for some noun, pronoun, or substantive adjective in the main clause that is feminine singular. The two nouns are **rex** and **fēminae**; of these two, the only possible choice is **fēminae** (as **rex** has to be masculine).
Even though the relative clause may be separated from its antecedent in Latin, in English, it makes more idiomatic sense to translate the relative clause immediately after its antecedent. For example, in the following Latin sentence:
- puer carmina cecinit quem docueram.
the relative clause **quem docueram** modifies the noun **puer**; antecedent and clause are separated by **carmina cecinit**. However, if we postpone the translation of the relative clause until the end, it sounds strange and, indeed, even confusing: "The boy sang songs **whom I had taught**." Because English relies on word order to make sense, we need to put the relative clause right after its antecedent: "The boy **whom I had taught** sang songs."
### Practice Opportunity 3
In each of the following sentences, parse the relative pronoun, identify and parse its antecedent, and then translate.
9. mīlitēs verba clamāvērunt quae nōs hortāta sunt. (clamō, -āre, -āvī, -ātus - to shout)
<button onclick="toggleDisplay('prac09')">Click here to toggle the answer:</button> <span style="display: none;" id="prac09">quae - neut. nom. pl.; verba - neut. acc. pl.; The soldiers shouted words which encouraged us.</span>
10. ā frātre sorōrēs creditae sunt quī hanc epistulam scripsit.
<button onclick="toggleDisplay('prac10')">Click here to toggle the answer:</button> <span style="display: none;" id="prac10">quī - masc. nom. sg.; frātre - masc. abl. sg.; The sisters were believed by the brother who wrote this letter.</span>
11. rēgina regnum rexit in quō nōmina nostra cognoscuntur.
<button onclick="toggleDisplay('prac11')">Click here to toggle the answer:</button> <span style="display: none;" id="prac11">quō - neut. abl. sg.; regnum - neut. acc. sg.; The queen ruled the kingdom in which our names are known.</span>
12. illī librī hīs puellīs legendī sunt quae discere volunt.
<button onclick="toggleDisplay('prac12')">Click here to toggle the answer:</button> <span style="display: none;" id="prac12">quae - fem. nom. pl.; puellīs - fem. dat. pl.; Those books must be read by these girls who want to learn.</span>
[Back to top.](#top)
***
## Connecting Relative
If a relative pronoun comes at the very beginning of a sentence, it is often being used as a **connecting relative**, an odd combination of a coordinating conjunction and a pronoun. Depending on the gender and number of the relative pronoun, it can be used to refer to an entity in the previous sentence or the whole idea encapsulated in the previous sentence, and it can sometimes be prefaced by "and", such that:
- **quī** = **et is**
- **quae** = **et ea**
- **quod** = **et id**
etc.
Take a look at the following examples:
- dux interfectus est. **quod** cum mīlitēs vīdissent, fūgērunt.
- The leader was killed. **(And)** when the soldiers had seen **this**, they fled.
- frātrēs patrem suum vidēre voluērunt; **quem** cum vidēre possent, laetī erant.
- The brothers wanted to see their father. **(And)** when they were able to see **him**, they were happy.
This **connecting relative** often, though not always, is used in a **cum** clause, and the **cum** is often postponed until after the connecting relative, as in the examples above. Note that the verbs in these examples are subjunctive because they are used in a **cum** clause to express the circumstances of the main verb; they are not subjunctive because of the relative pronoun. This is an important distinction to make once we consider in what circumstances a relative clause WOULD use a subjunctive verb, as in a relative clause of characteristic.
***
## Relative Clause of Characteristic
Most of the relative clauses that we've seen use indicative verbs because the clause is describing a definite antecedent. However, we can also use a **subjunctive verb** in the relative clause when the antecedent is **general, indefinite, interrogative, or negative**. This use of a relative clause with a subjunctive verb is called a **relative clause of characteristic**, because it defines a quality or characteristic of an antecedent that itself is general, indefinite, etc.
In translation, we can sometimes use the auxiliary verb "would" to render the subjunctive, and the antecedent can sometimes be prefaced by "the sort of" or "the kind of". We also often have to supply words in our translation based on, e.g., the gender and number of pronouns or nouns to help the translation make sense.
Take a look at the following examples:
- **quis est cui credāmus?** Who is there whom we would trust?
- **eī nōn sunt quī hoc faciant.** They are not the kind of people who would do this.
- **is erat quī veritātem dīceret**. He was the sort of guy who would speak the truth. (veritās, veritātis, f. - truth)
- **nēmō est quī hostem petere possit**. There is no one who can attack the enemy. (nēmō, neminis - nobody, no one)
### Practice Opportunity 4
Identify whether each of the following sentences uses a **relative clause of characteristic**, a **connecting relative**, or a straightforward **relative clause**. Then, translate.
13. haec est quae id putet.
<button onclick="toggleDisplay('prac13')">Click here to toggle the answer:</button> <span style="display: none;" id="prac13">relative clause of characteristic; This is the kind of woman who would think this.</span>
14. haec est quae id putat.
<button onclick="toggleDisplay('prac14')">Click here to toggle the answer:</button> <span style="display: none;" id="prac14">relative clause; This is the woman who thinks this.</span>
15. mīles pulcher est. quem cum vidērēmus, mirābāmur.
<button onclick="toggleDisplay('prac15')">Click here to toggle the answer:</button> <span style="display: none;" id="prac15">connecting relative; The soldier is handsome. When we saw him, we marveled.</span>
16. mīles est quem mirēmur.
<button onclick="toggleDisplay('prac16')">Click here to toggle the answer:</button> <span style="display: none;" id="prac16">relative clause of characteristic; The soldier is the kind of man whom we would marvel at.</span>
[Back to top.](#top)
***
| 76.545894 | 613 | 0.748249 | eng_Latn | 0.996377 |
fe0e0407db338f1cf432a97ff31d1a6ab3571c66 | 386 | md | Markdown | _drafts/nginx/stream-nginx-synology.md | lu4t/lu4t.github.io | b9d5f5851d3f6c150c441f1e822b0d4aeb687386 | [
"MIT"
] | null | null | null | _drafts/nginx/stream-nginx-synology.md | lu4t/lu4t.github.io | b9d5f5851d3f6c150c441f1e822b0d4aeb687386 | [
"MIT"
] | null | null | null | _drafts/nginx/stream-nginx-synology.md | lu4t/lu4t.github.io | b9d5f5851d3f6c150c441f1e822b0d4aeb687386 | [
"MIT"
] | null | null | null | ---
layout: post
title: Streaming con nginx.
subtitle: ...
cover-img: /assets/img/path.jpg
tags: [synology]
---
https://docs.peer5.com/guides/setting-up-hls-live-streaming-server-using-nginx/
nginx, streaming con 1 sólo proxy + web server
https://www.youtube.com/watch?v=Js1OlvRNsdI
nginx, streaming a 3 niveles proxy + web server + cdn
https://www.youtube.com/watch?v=xbFBjvUT-k0
| 21.444444 | 79 | 0.738342 | yue_Hant | 0.148437 |
fe0ef9f0875eac48e1f4b4ee0bfe01a14a8af419 | 500 | md | Markdown | Documents/Brainstorming.md | DayaneCordeiro/Financial_Manager | 9d1c0851265a49cd11a97471d8e6826fb1b30468 | [
"MIT"
] | null | null | null | Documents/Brainstorming.md | DayaneCordeiro/Financial_Manager | 9d1c0851265a49cd11a97471d8e6826fb1b30468 | [
"MIT"
] | null | null | null | Documents/Brainstorming.md | DayaneCordeiro/Financial_Manager | 9d1c0851265a49cd11a97471d8e6826fb1b30468 | [
"MIT"
] | null | null | null | # Brainstorming ⛈
- perguntar se a conta foi paga com o saldo do mês
- v2 ter um controle do valor que eu possuo ex: tenh 20k na minha conta, conseguir dizer que desses 20, 10k são pra orlando e eu não posso gastar
- ter um botão de pagar conta e nessa hora perguntar se teve algum desconto no pagamento
- vou deixar cadastrar uma data de vencimento no passado pra mostrar que está atrasado
- quando um endpoint não ta autenticado, ele não mostra direito que precisa do token, tem que corrigir isso
| 62.5 | 145 | 0.782 | por_Latn | 1.000006 |
fe101f5a723320a5d5ed7e443bcf1ec1e1a5aafa | 963 | md | Markdown | README.md | snailsnap/mollex | f1b345d8352a1eef19fbffd585bf52213fe52990 | [
"MIT"
] | 2 | 2018-06-02T21:52:20.000Z | 2018-06-10T10:49:12.000Z | README.md | snailsnap/mollex | f1b345d8352a1eef19fbffd585bf52213fe52990 | [
"MIT"
] | 5 | 2018-05-31T12:00:53.000Z | 2018-06-11T16:02:35.000Z | README.md | snailsnap/mollex | f1b345d8352a1eef19fbffd585bf52213fe52990 | [
"MIT"
] | 1 | 2018-07-02T10:06:52.000Z | 2018-07-02T10:06:52.000Z | # mollex: mollusc extractor
mollex extracts molluscoid shapes from images.
Mollusca is a phylum containing cephalopods (octopods etc.)
and gastropods (such as snails and slugs).
More precisely, the
_Museum für Naturkunde Berlin_ kindly provided us with a large
collection of molluscs as part of the [Coding da Vinci](https://codingdavinci.de)
hackathon.
mollex works by removing the background, performing some adaptive
prefiltering and finally finding contours that match typical
molluscoid shapes.
We tested mollex only on snail-like shapes.
## Daten
- [Coding da Vinci](https://codingdavinci.de/daten/#museum-f%C3%BCr-naturkunde-berlin)
- [Metadata](http://gbif.naturkundemuseum-berlin.de/CDV2018/Mollusken/Metadaten/)
- [Image Files](http://gbif.naturkundemuseum-berlin.de/CDV2018/Mollusken/)
- [Gallery View](http://gbif.naturkundemuseum-berlin.de/CDV2018/mollusken-gallery.html)
| 37.038462 | 89 | 0.780893 | eng_Latn | 0.74888 |
fe1056d20e43b7d0cab9a8acad322e6f1876acdd | 878 | md | Markdown | README.md | tlehman/manipulate-mediastream | f3280932de7d3d42be2a87e62c260d276d14dc48 | [
"MIT"
] | 2 | 2020-10-15T16:40:45.000Z | 2020-10-31T08:15:30.000Z | README.md | tlehman/manipulate-mediastream | f3280932de7d3d42be2a87e62c260d276d14dc48 | [
"MIT"
] | null | null | null | README.md | tlehman/manipulate-mediastream | f3280932de7d3d42be2a87e62c260d276d14dc48 | [
"MIT"
] | null | null | null | # Manipulating MediaStreams in HTML5
This is a working example of manipulating a video stream using HTML5 `<video>` elements, the `getUserMedia` method which returns a `Promise<MediaStream>` object.
The `MediaStream` object wraps the video stream from your webcam. Then, it attachs the stream to the input `<canvas>` element. This will allow us to pull the array of pixel data from the canvas.
Finally, the output `<canvas>` element is where we draw the manipulated pixel data.
## How to use
open index.html, click "Allow" to let your browser use your camera. Then click "Manipulate", that will stream the video into the canvases.
# Credits
This example was based on [this awesome tutorial from deepstream.io](https://deepstream.io/tutorials/webrtc/webrtc-video-manipulation/). Head over to DeepStream.io and check out their sweet website. | 58.533333 | 198 | 0.776765 | eng_Latn | 0.994927 |
fe105926c3b223e1624b6ae88097051357a62c67 | 1,099 | md | Markdown | content/tour/step.md | benzvan/docs | 5597dbf291fa26124071ee23ecf721b210f1ea6c | [
"Apache-2.0"
] | 15 | 2019-11-12T17:24:30.000Z | 2022-03-08T04:41:06.000Z | content/tour/step.md | benzvan/docs | 5597dbf291fa26124071ee23ecf721b210f1ea6c | [
"Apache-2.0"
] | 60 | 2019-11-15T15:54:44.000Z | 2022-03-08T15:08:04.000Z | content/tour/step.md | benzvan/docs | 5597dbf291fa26124071ee23ecf721b210f1ea6c | [
"Apache-2.0"
] | 28 | 2019-11-15T15:49:21.000Z | 2022-01-31T22:10:04.000Z | ---
title: "Step"
linkTitle: "Step"
weight: 1
description: >
Learn about step.
---
A step declaration allows you to provide execution instructions for a pipeline.
The following step is displaying an example of a minimal configuration for executing a simple echo linux command.
The `name:` tag is the unique identifier for the step throughout the lifecycle of the execution.
When `commands:` are provided they are converted to a shell script and executed as the Docker entrypoint for the container.
<!-- section break -->
```yaml
# In this step, commands are executed inside the container as the Entrypoint.
# If any command returns a non-zero exit code, the step fails and exits.
- name: Welcome
image: alpine
commands:
- echo "Welcome to the Vela docs"
```
```sh
#!/bin/sh
set -e
echo "Welcome to the Vela docs"
docker run --entrypoint=build.sh alpine:latest
```
<!-- section break -->
**Tag references:**
[`name:`](/docs/reference/yaml/steps/#the-name-tag), [`image:`](/docs/reference/yaml/steps/#the-image-tag), [`commands:`](/docs/reference/yaml/steps/#the-commands-tag), | 26.166667 | 169 | 0.724295 | eng_Latn | 0.990682 |
fe1121fca3ca75a46022f63a4989bb31a0e47801 | 201 | markdown | Markdown | _users/1173.markdown | sawyerh/organizedwonder | ec1c09e67d13776b134a1e4968b6413ca35f3780 | [
"MIT"
] | 2 | 2016-01-06T17:13:12.000Z | 2016-07-03T03:28:36.000Z | _users/1173.markdown | sawyerh/organizedwonder | ec1c09e67d13776b134a1e4968b6413ca35f3780 | [
"MIT"
] | null | null | null | _users/1173.markdown | sawyerh/organizedwonder | ec1c09e67d13776b134a1e4968b6413ca35f3780 | [
"MIT"
] | null | null | null | ---
title: "Joel Bews"
date: 2012-07-11 05:29:19 00:00
permalink: /jobbies
twitter: "jobbies"
likes: [1042,1097]
id: 1173
gravatar: "http://www.gravatar.com/avatar/211196d52cc72eb3a7c63dfea8eee62d"
--- | 22.333333 | 75 | 0.736318 | afr_Latn | 0.079547 |
fe119027be373aeaf621486fa5f4e311ba33b54b | 2,376 | md | Markdown | docs/visual-basic/language-reference/properties.md | turibbio/docs.it-it | 2212390575baa937d6ecea44d8a02e045bd9427c | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/visual-basic/language-reference/properties.md | turibbio/docs.it-it | 2212390575baa937d6ecea44d8a02e045bd9427c | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/visual-basic/language-reference/properties.md | turibbio/docs.it-it | 2212390575baa937d6ecea44d8a02e045bd9427c | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Proprietà
ms.date: 07/20/2015
helpviewer_keywords:
- properties [Visual Basic]
ms.assetid: c995caf9-8d0e-4fb8-ae02-e9e6087d7651
ms.openlocfilehash: 1e56be71c1841c202f08b64716e62b003bda4d97
ms.sourcegitcommit: f8c270376ed905f6a8896ce0fe25b4f4b38ff498
ms.translationtype: MT
ms.contentlocale: it-IT
ms.lasthandoff: 06/04/2020
ms.locfileid: "84406301"
---
# <a name="properties-visual-basic"></a>Proprietà (Visual Basic)
In questa pagina sono elencate le proprietà che sono membri dei moduli Visual Basic. Le altre proprietà che sono membri di oggetti Visual Basic specifici sono elencate in [oggetti](objects/index.md).
## <a name="visual-basic-properties"></a>Proprietà Visual Basic
|||
|---|---|
|<xref:Microsoft.VisualBasic.DateAndTime.DateString%2A>|Restituisce o imposta un `String` valore che rappresenta la data corrente in base al sistema.|
|<xref:Microsoft.VisualBasic.DateAndTime.Now%2A>|Restituisce un `Date` valore contenente la data e l'ora correnti in base al sistema.|
|<xref:Microsoft.VisualBasic.Globals.ScriptEngine%2A>|Restituisce un valore `String` che rappresenta il runtime correntemente in uso.|
|<xref:Microsoft.VisualBasic.Globals.ScriptEngineBuildVersion%2A>|Restituisce un oggetto `Integer` contenente il numero di versione della build del Runtime attualmente in uso.|
|<xref:Microsoft.VisualBasic.Globals.ScriptEngineMajorVersion%2A>|Restituisce un oggetto `Integer` contenente il numero di versione principale del Runtime attualmente in uso.|
|<xref:Microsoft.VisualBasic.Globals.ScriptEngineMinorVersion%2A>|Restituisce un oggetto `Integer` contenente il numero di versione secondario del Runtime attualmente in uso.|
|<xref:Microsoft.VisualBasic.DateAndTime.TimeOfDay%2A>|Restituisce o imposta un valore `Date` contenente l'ora corrente del sistema in uso.|
|<xref:Microsoft.VisualBasic.DateAndTime.Timer%2A>|Restituisce un valore `Double` che rappresenta il numero di secondi trascorsi dalla mezzanotte.|
|<xref:Microsoft.VisualBasic.DateAndTime.TimeString%2A>|Restituisce o imposta un `String` valore che rappresenta l'ora corrente del giorno in base al sistema.|
|<xref:Microsoft.VisualBasic.DateAndTime.Today%2A>|Restituisce o imposta un valore `Date` contenente la data corrente del sistema in uso.|
## <a name="see-also"></a>Vedere anche
- [Riferimenti al linguaggio Visual Basic](index.md)
| 66 | 201 | 0.793771 | ita_Latn | 0.952927 |
573c840de8c0fa7950b15e7f1feade4a201319e5 | 53 | md | Markdown | postgres/README.md | free-yushu/docker-compose | 0fa1736e13270c957e236a618035ed279a93c410 | [
"MIT"
] | 3 | 2018-10-28T01:42:03.000Z | 2019-03-11T06:33:34.000Z | postgres/README.md | free-yushu/docker-compose | 0fa1736e13270c957e236a618035ed279a93c410 | [
"MIT"
] | null | null | null | postgres/README.md | free-yushu/docker-compose | 0fa1736e13270c957e236a618035ed279a93c410 | [
"MIT"
] | 5 | 2019-05-12T18:24:06.000Z | 2021-06-25T03:28:49.000Z | # mongo
基础的单机版postgres数据库，默认用户名postgres 默认密码 123456
| 13.25 | 43 | 0.849057 | eng_Latn | 0.150245 |
573e5c06299c7da271d87ff7423216c0da5cbb86 | 105 | md | Markdown | README.md | DIWesser/dotfiles | a0507dd35662b92f4fca00045e75753837ec3864 | [
"MIT"
] | null | null | null | README.md | DIWesser/dotfiles | a0507dd35662b92f4fca00045e75753837ec3864 | [
"MIT"
] | null | null | null | README.md | DIWesser/dotfiles | a0507dd35662b92f4fca00045e75753837ec3864 | [
"MIT"
] | null | null | null | This project has moved to [gitlab](https://gitlab.com/diwesser/dotfiles).
# dotfiles
My public dotfiles
| 21 | 73 | 0.771429 | eng_Latn | 0.886096 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.