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
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
ed0cc3a3d10c989fc1d4cef682664b4c7ae352fe | 4,863 | md | Markdown | .docs/use-cases/01-Incident.md | Korkmatik/IRem | cbcf8ed241988b74e0cf5d71daf50e139d7b4512 | [
"MIT"
] | null | null | null | .docs/use-cases/01-Incident.md | Korkmatik/IRem | cbcf8ed241988b74e0cf5d71daf50e139d7b4512 | [
"MIT"
] | 10 | 2021-04-11T20:26:29.000Z | 2021-04-11T20:29:23.000Z | .docs/use-cases/01-Incident.md | Korkmatik/IRem | cbcf8ed241988b74e0cf5d71daf50e139d7b4512 | [
"MIT"
] | null | null | null | # /UC01.1/ Incident erstellen
## Übersicht
|||
---------------|---------------------------------------------------------------
Ziel | Erstellen eines Incident, damit alle Daten, die zu einem Incident Response dazu gehören gemanaged werden können
Vorbedingung | Der Nutzer ist angemeldet
Resultat | Ein Incident ist erstellt und eingestellt
Nutzer | Incident Owner
Auslöser | Funktion "Create Incident" ausgewählt
------------------------------------------------------------------------------
## Detailbeschreibung
**Kurzbeschreibung**: Ein Incident Owner kann ein Incident erstellen und Basis Einstellungen während des Erstellungsvorgangs einstellen.
**Akteure**:
* Angemeldeter User
* Web API
**Eingehende Daten**:
* Nutzer der den Incident erstellt
* Name für den Incident
* Teilnehmer
* Auslöser
* Kunde
* Optionale Beschreibung
**Essentielle Schritte**:
1. Nutzer wählt Funktion "Create Incident" aus
2. Dialog für das Erstellen eines Incidents wird angezeigt
3. Nutzer gibt erforderliche Daten ein und bestätigt
4. Daten werden in die Datenbank gespeichert und ein Incident wird erstellt
**Ausnahmen**:
- zu 3.) (a) Falls die Daten fehlerhaft sind, wird eine Fehlermeldung angezeigt (b) Weitere Schritte werden abgebrochen
**Änderungshistorie**
* 24.04.2021; Korkmatik; Use Case angelegt
* 25.04.2021; Korkmatik; Case zu Incident umbenannt
# /UC01.2/ Incident löschen
## Übersicht
|||
---------------|---------------------------------------------------------------
Ziel | Löschen eines Incidents
Vorbedingung | Der Nutzer ist angemeldet und ein Incident wurde erstellt
Resultat | Ein Incident zuvor erstellter Incident wird von der Datenbank gelöscht
Nutzer | Incident Owner
Auslöser | Funktion "Delete Incident" ausgewählt
------------------------------------------------------------------------------
## Detailbeschreibung
**Kurzbeschreibung**: Ein Incident Owner kann ein bereits erstelltes Incident wieder löschen
**Akteure**:
* Angemeldeter User
* Web API
**Eingehende Daten**:
* Incident ID
* Nutzerdaten
**Essentielle Schritte**:
1. Nutzer wählt das Incident aus
2. Nutzer geht in die Projekt Einstellungen
3. Nutzer wählt "Delete Incident" aus
4. Das System zeigt ein confirmation dialog
5. Nutzer bestätigt, dass er den Incident löschen möchte
6. Incident Daten werden aus der Datenbank gelöscht
**Ausnahmen**:
- zu 5.) (a) Falls Nutzer dies nicht bestätigt, werden alle folgenden Schritte abgebrochen.
**Änderungshistorie**
* 24.04.2021; Korkmatik; Use Case angelegt
* 25.04.2021; Korkmatik; Case zu Incident umbenannt
# /UC01.3/ Incident bearbeiten
## Übersicht
|||
---------------|---------------------------------------------------------------
Ziel | Bearbeiten der Einstellungen eines Incidents
Vorbedingung | Der Nutzer ist angemeldet und ein Incident wurde erstellt
Resultat | Ein Incident hat neue Einstellungen
Nutzer | Incident Owner
Auslöser | Funktion "Settings" ausgewählt
------------------------------------------------------------------------------
## Detailbeschreibung
**Kurzbeschreibung**: Ein Incident Owner kann Einstellungen eines bereits erstellten Incidents wieder ändern.
**Akteure**:
* Angemeldeter User
* Web API
**Eingehende Daten**:
* Incident ID
* Incident Settings
* Nutzer ID
**Essentielle Schritte**:
1. Nutzer wählt das Incident aus
2. Nutzer geht in die Projekt Einstellungen
3. Nutzer ändert die Einstellungen
4. Nutzer speichert die Einstellungen
5. Neue Incident Einstellungen werden in der Datenbank gespeichert
**Ausnahmen**:
- zu 4.) (a) Falls die eingegebenen Daten ungültig sind, wird eine Fehlermeldung angezeigt (b) Weitere Schritte werden abgebrochen
**Änderungshistorie**
* 24.04.2021; Korkmatik; Use Case angelegt
* 25.04.2021; Korkmatik; Case zu Incident umbenannt
# /UC01.4/ Incidents anzeigen
## Übersicht
|||
---------------|---------------------------------------------------------------
Ziel | Incidents zu dem ein Nutzer zugeteilt wurde, werden auf der Home Page angezeigt
Vorbedingung | Der Nutzer ist angemeldet und ist auf der Home Page
Resultat | Nutzer sieht seine Incidents
Nutzer | Angemeldeter User
Auslöser | Funktion "Show Home Page" ausgewählt
------------------------------------------------------------------------------
## Detailbeschreibung
**Kurzbeschreibung**: Ein Nutzer kann auf seiner Home Page sehen, zu welchen Incidents er zugeteilt wurde.
**Akteure**:
* Angemeldeter User
* Web API
**Eingehende Daten**:
* Nutzer ID
**Essentielle Schritte**:
1. Nutzer öffnet die "Home Page"
2. Incidents werden in kompakter Darstellung aufgelistet
**Ausnahmen**:
**Änderungshistorie**
* 24.04.2021; Korkmatik; Use Case angelegt
* 25.04.2021; Korkmatik; Case zu Incident umbenannt | 31.374194 | 136 | 0.648982 | deu_Latn | 0.988774 |
ed0dc12c40cdccbf40a9f205376e462d254d38b2 | 4,490 | md | Markdown | _posts/2021-10-18-Week-2.md | Al-0/Encora-Apprenticeship | 0083cfe2ed0ad423351e873ed418af47e3ad9a85 | [
"MIT"
] | null | null | null | _posts/2021-10-18-Week-2.md | Al-0/Encora-Apprenticeship | 0083cfe2ed0ad423351e873ed418af47e3ad9a85 | [
"MIT"
] | null | null | null | _posts/2021-10-18-Week-2.md | Al-0/Encora-Apprenticeship | 0083cfe2ed0ad423351e873ed418af47e3ad9a85 | [
"MIT"
] | null | null | null | ---
theme: post
title: Polyglot Programming, Week 2
tags: secondweek polyglotprogramming
categories: Weeklyessay
---
Teamwork makes the dreamwork. Cheesy, but alas, that is my main takeaway from this week. The polyglot programming week gave us the challenge of solving the qualification round of the Google Code Jam 2021 in 5 different programming languages. The whole apprentice team needed to coordinate in order to ensure each of the 5 problems was solves in each language. This was an awesome experience, on one hand because I was able to learn about a whole new programming language, Kotlin; but also, because this gave me the unique opportunity to solve programming challenges alongside my peers. I had never done this before, and while unfortunately I didn’t have the insight to ask for help and start cooperating sooner (I waste 2 days trying to solve it on my own), at the end we worked together to figure out a solution, share our ideas and finally fulfilled our responsibility. Lesson learned, swallow your pride and ask for help sooner, programming together was quite a joyful experience.
Continuing on the more technical side, this week we learned though a couple of videos about the basic (and advanced) theory behind the compression algorithms we use. We continued the missing semester of the bash shell, on which we continued to learn more advanced tools, commands and scripts.
Regarding technical talks, we took a bunch of talks from the Google I/O developer conference form the charismatic duo of Brian Fitzpatrick and Ben Collins-Sussman. These talks were incredibly inspirational, as they allowed me to see a broader picture of what it means to be a developer in a company, the roles it takes to be one and the incredible importance of having the right social skills in order to effectively work with other people. Other videos I saw this week talked about the adoption of a “best” programming language (it really depends, but aim for variety), as well as the concept of the Dreyfus Model, an interesting concept that tracks the journey from novice to expert in a quite interesting manner, as it gives insight into what each step of the way requires to make the best out of its position.
Finally, on the social side, we had some very interesting talks from Linda Rising, a chemist, mathematician and computer scientist (at 50 years of age!) with some rather thoughtful insights into the agile mindset and the plasticity of the brain. Her talks also touched on stereotypes and trust, the experiments about the Muslim and Christian boys in Beirut and the influence of stereotypes on people were very interesting to me, it also reminded me of a [study on this topic](https://econtent.hogrefe.com/doi/10.1027/1864-9335/a000184) about Asian American women and the power of both harmful and positive stereotypes on their math ability. The last series of videos was about the idea of remixing, copying and transforming. These videos were honestly a treat, and they made me rethink what creativity is really all about.
In conclusion, this was a very intense but very insightful week, I hope the next ones can be as exciting as this one! Here are my notes for the week.
.jpeg)
.jpeg)
.jpeg)
.jpeg)
.jpeg)
.jpeg)
| 132.058824 | 984 | 0.799555 | eng_Latn | 0.993586 |
ed0e358c97ecc59b409b19358047d7d1b1dc2558 | 1,028 | md | Markdown | text/15/data-presentation.md | pmean/build-website | b721ad2b1b4589ac517535dd29ee6654381354ee | [
"CC0-1.0"
] | null | null | null | text/15/data-presentation.md | pmean/build-website | b721ad2b1b4589ac517535dd29ee6654381354ee | [
"CC0-1.0"
] | null | null | null | text/15/data-presentation.md | pmean/build-website | b721ad2b1b4589ac517535dd29ee6654381354ee | [
"CC0-1.0"
] | null | null | null | ---
title: "Beyond Bar and Line Graphs: Time for a New Data Presentation Paradigm"
author: "Steve Simon"
source: "http://blog.pmean.com/data-presentation/"
date: "2015-04-30"
categories:
- Recommendation
tags:
- Graphical display
output: html_document
---
Many scientists rely on bar graphs and line graphs that effectively
reduce your data to a single mean per group. Even with the addition of
error bars, the whole process tends to hide important information. These
authors suggest that scatterplots that show every data point would be a
better way to present your research data.
<!---More--->
Weissgerber TL, Milic NM, Winham SJ, Garovic VD. Beyond Bar and Line
Graphs: Time for a New Data Presentation Paradigm. PLoS Biol.
2015;13(4):e1002128. doi:10.1371/journal.pbio.1002128. Available at
[journals.plos.org/plosbiology/article?id=10.1371/journal.pbio.1002128](http://journals.plos.org/plosbiology/article?id=10.1371/journal.pbio.1002128).
<U+00A0>
| 31.151515 | 150 | 0.769455 | eng_Latn | 0.641176 |
ed0e98211ac2c3bea730ba12712419a9dd3ef438 | 7,202 | md | Markdown | docs/framework/winforms/controls/how-to-add-buttons-to-a-toolbar-control.md | emrekas/docs.tr-tr | 027bd2c6c93900a75cac7ac42531c89085f87888 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-01-06T07:30:24.000Z | 2020-01-06T07:30:24.000Z | docs/framework/winforms/controls/how-to-add-buttons-to-a-toolbar-control.md | emrekas/docs.tr-tr | 027bd2c6c93900a75cac7ac42531c89085f87888 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/winforms/controls/how-to-add-buttons-to-a-toolbar-control.md | emrekas/docs.tr-tr | 027bd2c6c93900a75cac7ac42531c89085f87888 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: 'Nasıl yapılır: Bir ToolBar Denetimine Düğme Ekleme'
ms.date: 03/30/2017
dev_langs:
- csharp
- vb
- cpp
helpviewer_keywords:
- toolbars [Windows Forms], adding buttons
- ToolBar control [Windows Forms], adding buttons
- ToolBar control [Windows Forms], adding separators
- examples [Windows Forms], toolbars
- ToolBar control [Windows Forms], adding drop-down menus
ms.assetid: 78a58a8d-1041-4e38-9219-4096fa6a5c5c
ms.openlocfilehash: 8ab1fa8fc163ed50e51801769d40e61483e8ed5b
ms.sourcegitcommit: 68653db98c5ea7744fd438710248935f70020dfb
ms.translationtype: MT
ms.contentlocale: tr-TR
ms.lasthandoff: 08/22/2019
ms.locfileid: "69912638"
---
# <a name="how-to-add-buttons-to-a-toolbar-control"></a>Nasıl yapılır: Bir ToolBar Denetimine Düğme Ekleme
> [!NOTE]
> Denetim yerini alır ve <xref:System.Windows.Forms.ToolBar> <xref:System.Windows.Forms.ToolBar> denetime işlevsellik ekler; ancak, isterseniz denetim hem geri uyumluluk hem de gelecekteki kullanım için korunur. <xref:System.Windows.Forms.ToolStrip>
<xref:System.Windows.Forms.ToolBar> Denetimin integral bir bölümü, ona eklediğiniz düğmelerdir. Bunlar menü komutlarına kolay erişim sağlamak için kullanılabilir veya alternatif olarak, menü yapısında kullanılamayan kullanıcılarınıza komutları göstermek için uygulamanızın kullanıcı arabiriminin başka bir alanına yerleştirilebilecek.
Aşağıdaki örneklerde, bir denetimin bir <xref:System.Windows.Forms.ToolBar> Windows formuna (`Form1`) eklendiğini varsaymaktadır.
### <a name="to-add-buttons-programmatically"></a>Program aracılığıyla düğme eklemek için
1. Bir yordamda, bunları <xref:System.Windows.Forms.ToolBar.Buttons%2A?displayProperty=nameWithType> koleksiyona ekleyerek araç çubuğu düğmeleri oluşturun.
2. Düğme dizinini <xref:System.Windows.Forms.ToolBar.Buttons%2A> özelliği aracılığıyla geçirerek tek bir düğme için özellik ayarlarını belirtin.
Aşağıdaki örnekte, bir <xref:System.Windows.Forms.ToolBar> denetimin zaten eklendiği bir form varsayılır.
> [!NOTE]
> <xref:System.Windows.Forms.ToolBar.Buttons%2A?displayProperty=nameWithType> Koleksiyon sıfır tabanlı bir koleksiyondur, bu nedenle kod buna uygun şekilde devam etmelidir.
```vb
Public Sub CreateToolBarButtons()
' Create buttons and set text property.
ToolBar1.Buttons.Add("One")
ToolBar1.Buttons.Add("Two")
ToolBar1.Buttons.Add("Three")
ToolBar1.Buttons.Add("Four")
' Set properties of StatusBar panels.
' Set Style property.
ToolBar1.Buttons(0).Style = ToolBarButtonStyle.PushButton
ToolBar1.Buttons(1).Style = ToolBarButtonStyle.Separator
ToolBar1.Buttons(2).Style = ToolBarButtonStyle.ToggleButton
ToolBar1.Buttons(3).Style = ToolBarButtonStyle.DropDownButton
' Set the ToggleButton's PartialPush property.
ToolBar1.Buttons(2).PartialPush = True
' Instantiate a ContextMenu component and menu items.
' Set the DropDownButton's DropDownMenu property to the context menu.
Dim cm As New ContextMenu()
Dim miOne As New MenuItem("One")
Dim miTwo As New MenuItem("Two")
Dim miThree As New MenuItem("Three")
cm.MenuItems.Add(miOne)
cm.MenuItems.Add(miTwo)
cm.MenuItems.Add(miThree)
ToolBar1.Buttons(3).DropDownMenu = cm
' Set the PushButton's Pushed property.
ToolBar1.Buttons(0).Pushed = True
' Set the ToolTipText property of one of the buttons.
ToolBar1.Buttons(1).ToolTipText = "Button 2"
End Sub
```
```csharp
public void CreateToolBarButtons()
{
// Create buttons and set text property.
toolBar1.Buttons.Add("One");
toolBar1.Buttons.Add("Two");
toolBar1.Buttons.Add("Three");
toolBar1.Buttons.Add("Four");
// Set properties of StatusBar panels.
// Set Style property.
toolBar1.Buttons[0].Style = ToolBarButtonStyle.PushButton;
toolBar1.Buttons[1].Style = ToolBarButtonStyle.Separator;
toolBar1.Buttons[2].Style = ToolBarButtonStyle.ToggleButton;
toolBar1.Buttons[3].Style = ToolBarButtonStyle.DropDownButton;
// Set the ToggleButton's PartialPush property.
toolBar1.Buttons[2].PartialPush = true;
// Instantiate a ContextMenu component and menu items.
// Set the DropDownButton's DropDownMenu property to
// the context menu.
ContextMenu cm = new ContextMenu();
MenuItem miOne = new MenuItem("One");
MenuItem miTwo = new MenuItem("Two");
MenuItem miThree = new MenuItem("Three");
cm.MenuItems.Add(miOne);
cm.MenuItems.Add(miTwo);
cm.MenuItems.Add(miThree);
toolBar1.Buttons[3].DropDownMenu = cm;
// Set the PushButton's Pushed property.
toolBar1.Buttons[0].Pushed = true;
// Set the ToolTipText property of 1 of the buttons.
toolBar1.Buttons[1].ToolTipText = "Button 2";
}
```
```cpp
public:
void CreateToolBarButtons()
{
// Create buttons and set text property.
toolBar1->Buttons->Add( "One" );
toolBar1->Buttons->Add( "Two" );
toolBar1->Buttons->Add( "Three" );
toolBar1->Buttons->Add( "Four" );
// Set properties of StatusBar panels.
// Set Style property.
toolBar1->Buttons[0]->Style = ToolBarButtonStyle::PushButton;
toolBar1->Buttons[1]->Style = ToolBarButtonStyle::Separator;
toolBar1->Buttons[2]->Style = ToolBarButtonStyle::ToggleButton;
toolBar1->Buttons[3]->Style = ToolBarButtonStyle::DropDownButton;
// Set the ToggleButton's PartialPush property.
toolBar1->Buttons[2]->PartialPush = true;
// Instantiate a ContextMenu component and menu items.
// Set the DropDownButton's DropDownMenu property to
// the context menu.
System::Windows::Forms::ContextMenu^ cm = gcnew System::Windows::Forms::ContextMenu;
MenuItem^ miOne = gcnew MenuItem( "One" );
MenuItem^ miTwo = gcnew MenuItem( "Two" );
MenuItem^ miThree = gcnew MenuItem( "Three" );
cm->MenuItems->Add( miOne );
cm->MenuItems->Add( miTwo );
cm->MenuItems->Add( miThree );
toolBar1->Buttons[3]->DropDownMenu = cm;
// Set the PushButton's Pushed property.
toolBar1->Buttons[0]->Pushed = true;
// Set the ToolTipText property of 1 of the buttons.
toolBar1->Buttons[1]->ToolTipText = "Button 2";
}
```
## <a name="see-also"></a>Ayrıca bkz.
- <xref:System.Windows.Forms.ToolBar>
- [Nasıl yapılır: Bir araç çubuğu düğmesi için simge tanımlama](how-to-define-an-icon-for-a-toolbar-button.md)
- [Nasıl yapılır: Araç çubuğu düğmeleri için tetikleyici menü olayları](how-to-trigger-menu-events-for-toolbar-buttons.md)
- [ToolBar Denetimine Genel Bakış](toolbar-control-overview-windows-forms.md)
- [ToolBar Denetimi](toolbar-control-windows-forms.md)
| 45.582278 | 337 | 0.673285 | tur_Latn | 0.513269 |
ed0fec148103b008e21c435a0d18183ec29e5a84 | 728 | md | Markdown | fc-git/3.GIT-WORKFLOW.md | teachmesomething2580/TIL | 81769609ae6b22074c1db5265aef716c23b566a1 | [
"MIT"
] | null | null | null | fc-git/3.GIT-WORKFLOW.md | teachmesomething2580/TIL | 81769609ae6b22074c1db5265aef716c23b566a1 | [
"MIT"
] | null | null | null | fc-git/3.GIT-WORKFLOW.md | teachmesomething2580/TIL | 81769609ae6b22074c1db5265aef716c23b566a1 | [
"MIT"
] | null | null | null | # Git을 이용한 협업 워크플로우
깃을 사용하는 방식
1. Centralized Workflow
여러명이 하나의 중앙 저장소를 사용하는 것(MASTER BRANCH만을 사용하는 것)
분산버전관리의 이점을 사용할 수 없다. 언제든지 모든 내용을 동기화 시켜야한다.
2. Feature Branch Workflow
Master , Feature의 브랜치를 생성
병합 시 권한을 가진 사용자만이 PULL Request를 사용할 수 있다.
3. Gitflow workflow
중앙 저장소를 사용
Master, Develop(개발), Feature(기능), Release(DEVELOP에서 릴리즈에 필요한 기능을 추가해야할때),Hot fix
4. Forking Workflow
다른 워크플로우와는 다르다.
저장소를 한개만 쓰는게 아니라, 작업자마다 저장소를 가진다.
일반적인 오픈소스 프로젝트의 경우에는 수많은 기여자들이 FORK 하여 자신의 저장소에 저장한 다음 오픈소스 제작자에게 PULL-REQUEST를 보내서 오픈소스 내부로 넣을 수 있다.
**문제점**은 업데이트 된 것을 내 저장소에 반영할 수 없다. 포크해온 저장소의 원본 저장소의 이름을 upstream이라고 한다. 이것을 로컬 저장소의 remote를 추가한다.
```
> git remote add upstream [LINK]
```
#### pull Request
base fork : 원본 <- 추가한 브랜치
| 19.675676 | 101 | 0.722527 | kor_Hang | 1.00001 |
ed100c24cc4f460ae9f14e1c3c4d1f3b7f4d13be | 12,466 | md | Markdown | closed/Alibaba/scripts/autotune/README.md | ctuning/inference_results_v1.1 | d9176eca28fcf6d7a05ccb97994362a76a1eb5ab | [
"Apache-2.0"
] | 12 | 2021-09-23T08:05:57.000Z | 2022-03-21T03:52:11.000Z | closed/Alibaba/scripts/autotune/README.md | ctuning/inference_results_v1.1 | d9176eca28fcf6d7a05ccb97994362a76a1eb5ab | [
"Apache-2.0"
] | 11 | 2021-09-23T20:34:06.000Z | 2022-01-22T07:58:02.000Z | closed/Alibaba/scripts/autotune/README.md | ctuning/inference_results_v1.1 | d9176eca28fcf6d7a05ccb97994362a76a1eb5ab | [
"Apache-2.0"
] | 16 | 2021-09-23T20:26:38.000Z | 2022-03-09T12:59:56.000Z | It would be nice to have an automated, scenario/benchmark agnostic means of getting timings for a variety of parameters.
Immediately, this is useful for knob-heavy benchmarks like RNN-T, but will also be useful in the future as MLPerf becomes more system-focused (thereby increasing the number of potential parameters needing to be tuned).
[[_TOC_]]
# Usage
Requires that the given scenario, benchmark, and system have a present baseline configuration in `configs/` (the typical usage pattern for a new system, is to copy-and-paste an already-tuned system's config entry, and use the autotuner to find a more suitable parameter set).
See
scripts/autotune/grid.py --help
for arguments.
For "simple" jobs (run all possible combinations of all parameters), it is suggested to use JSON input.
For more complex jobs (where certain combinations shouldn't be executed, special properties are known about the parameters to optimize scheduling, etc), it is suggested to use Python input.
Refer to [Config Schema](#Config-Schema) for additional information.
# Config Schema
## JSON
As seen in `scripts/autotune/example.json`, the expected format is a flat object whose properties are parameter names, and whose values are arrays of non-object, non-array items. Practically, this is bools, numbers, or strings; identical to the python case.
## Python
As seen in `scripts/autotune/example.py`, the expected format is variables with no leading underscores declared at the global namespace which are arrays of primitive, non-dict, non-array type. Practically this is bools, int, float, and str; identical to the JSON case.
Special functions prefixed by `META_` define special hooks into the scheduling process. They are described below:
### META_get_no_rebuild_params()
A function which takes no arguments and returns a list of strings. These strings MUST correspond to variable names in the same Python file (and these strings must also therefore describe valid parameters for the given benchmark/scenario) whose values can be changed by the autotuner without rebuilding the engine.
The scheduler will use the variable names returned by this function to order runs in such a manner to reduce the number of rebuilds (`make generate_engines`) required to fully execute the job.
#### Example
Take the following pathological case:
audio_batch_size = [128,256,512] # A runtime parameter (doesn't require rebuilding engines)
gpu_batch_size = [128,256] # A buildtime AND runtime parameter (requires rebuilding engines)
A naive scheduling of these parameters could produce
audio_batch_size = 128; gpu_batch_size = 128;
# Rebuild!
audio_batch_size = 128; gpu_batch_size = 256;
# Rebuild!
audio_batch_size = 256; gpu_batch_size = 128;
# Rebuild!
audio_batch_size = 256; gpu_batch_size = 256;
# Rebuild!
audio_batch_size = 512; gpu_batch_size = 128;
# Rebuild
audio_batch_size = 512; gpu_batch_size = 256;
Requiring 5 rebuilds because a build-time parameter changes at each step
If we defined
def META_get_no_rebuild_params():
return ['audio_batch_size']
Our scheduler can produce the following intelligent ordering:
audio_batch_size = 128; gpu_batch_size = 128;
audio_batch_size = 256; gpu_batch_size = 128;
audio_batch_size = 512; gpu_batch_size = 128;
# Rebuild!
audio_batch_size = 128; gpu_batch_size = 256;
audio_batch_size = 256; gpu_batch_size = 256;
audio_batch_size = 512; gpu_batch_size = 256;
Doing only one rebuild instead! (Potentially reducing our tuning time by an equal order of magnitude for some benchmarks)
### META_is_config_valid()
A callback which takes a "full parameter config dict" (the default config from `configs/benchmark/scenario` updated/overlayed with values from the configuration file), and returns whether or not this configuration is valid.
If this callback is not defined, the default behavior is to treat all configs as valid
#### Example
Take the following parameter lists:
audio_batch_size = [128, 256, 512, 1024]
dali_pipeline_depth = [1,2,3]
audio_buffer_num_lines = [128, 256, 512, 1024, 2048, 4096]
And we know that due to the nature of our benchmark, if `audio_batch_size * dali_pipeline_depth` is ever greater than `audio_buffer_num_lines`, our benchmark will crash.
So, the following is true:
audio_batch_size = 256; dali_pipeline_depth=1; audio_buffer_num_lines = 1024 # Works okay
audio_batch_size = 512; dali_pipeline_depth=1; audio_buffer_num_lines = 1024 # Works okay
audio_batch_size = 512; dali_pipeline_depth=2; audio_buffer_num_lines = 1024 # Works okay
audio_batch_size = 1024; dali_pipeline_depth=2; audio_buffer_num_lines = 1024 # CRASH!
Instead of manually specifying all legal configurations (the exact problem that autotuning solves). What would be nice is if the autotuner could just not run certain configurations based on a predicate. As it turns out, the autotuner script has this interface! It's presents a callback which states if is a configuration is legal before launching work (`generate_engines` and `run_harness`).
So, we can specify:
```python
def META_is_config_valid(config):
if config['dali_pipeline_depth'] * config['audio_batch_size'] > config['audio_buffer_num_lines']:
return False
return True
```
And now the failing cases will not be executed.
### META_search_callback()
A function which takes no arguments and returns an object which implements `SearcherInterface`. Examples of concrete implementations include `Step`, `CartesianProduct` (default search behavior), `Bisect`, and `Composer`.
This should be used when the default behavior of exhaustively iterating through all parameter combinations is not desired.
#### `SearcherInterface`
An interface containing an abstract method `generate()` and an abstract property `is_dynamic`. `generate()` is a [generator function](https://docs.python.org/3/glossary.html#term-generator), which can optionally accept incremental results in the form of `Run` (see `Bisect::generate()` for client usage, see [send](https://docs.python.org/3/reference/expressions.html?#generator.send) for language documentation) to influence searching. `is_dynamic` should be set to `True` if `generate()` uses incremental results.
#### Helpers
Refer to `library.py` which provides many utilities. For example, `Step` can be imported with `from library import Step` (note that package lookup is relative to `grid.py`, not the configuration py file, so no fancy relative pathing or `sys.path.insert(foo)` needed.)
##### Example: Binary Search with `Bisect`
Suppose we want to perform a binary search to find an optimal QPS value given default parameters in the QPS range: `(500, 2500)` in step-sizes of 100. We can use `Bisect` to make the following
```python
from library import Bisect
def META_search_callback(past_runs):
return Bisect(search_param="server_target_qps",
lower_bound=3000,
upper_bound=4650,
step_size=50,
predicate=lambda r: r.stats['result_validity'] == "VALID"))
# We know QPS is a runtime-only parameter, so we don't need to rebuild in between runs:
def META_get_no_rebuild_params():
return ["server_target_qps"]
```
##### `Composer`
As a reference implementation of a `SearcherInterface` which non-trivially utilizes incremental results, `Composer` is a searcher which composes multiple SearcherInterface objects composed by optional predicates.
The logic which `Composer` takes is as follows:
1. Ask all searchers for their initial search term and run inference
2. Ask the first searcher if it "wants" to yield its next object given the past run
3. If it does, ask the first searcher for its next search term
4. If not, repeat #2-3 for all searchers until we find one that wants to give us a search term, and ask for its next search term
5. If no searchers "want" to yield the next search term, force all searchers, backwards, to give us a term. We stop querying once a searcher gives us a term
6. If no searchers gave us a term when forced, we're done.
Note that we separate "asking what a searcher _wants_ to do" and "asking a searcher for its next search term" because calling `next`/`send` is destructive, and it's quite a headache to manually rebuild state after each query to a generator.
Refer to the following diagram for a pictoral representation of the aforementioned logic.
```plantuml
start
!pragma useVerticalIf on
while (timeout?)
:Run and acquire RunArtifact;
if (predicate1(RunArtifact)) then (True)
:search_term = get(Searcher1) ;
elseif (predicate2(RunArtifact)) then (True)
:search_term = get(Searcher2) ;
endif
if (search_term == NULL) then (True)
:Normal consultation has failed, now force each searcher to give us a term
search_term = get(Searcher2) || get(Searcher1);
endif
if (search_term == NULL) then (True)
:We searched through everything
break!;
endif
:++NumRuns;
endwhile (Yes)
:Finish;
end
```
##### Example: Somewhat intelligent server tuning. With and without Composer
One such application, would be to tune `server_target_qps` at a top level using `Bisect` , but also schmoo other knobs such as `gpu_inference_streams` and `gpu_batch_size` before we take a negative step in our binary search. This can be implemented as follows:
```python
def META_search_callback():
return Composer([Bisect(search_param="server_target_qps",
lower_bound=3000,
upper_bound=4650,
step_size=50,
predicate=lambda r: r.stats['result_validity'] == "VALID"), # Composer will use Bisect's predicate
(Step(search_param="gpu_inference_streams",
start=1,
end=4,
update=lambda x: x + 1),
lambda x: True), # Redundant, but demonstrates how we can have an arbitrary predicate for Composer's logic
Step(search_param="gpu_batch_size",
start=200,
end=100,
update=lambda x: x - 50)], # By default, we always return True.
timeout=10)
```
If one were to manually implement this logic as a bespoke SearcherInterface, it would look something like:
```python
class Bespoke(SearcherInterface):
is_dynamic = True
def __init__(self, timeout=10):
self.timeout=timeout
def generate(self):
b = Bisect(search_param="server_target_qps",
lower_bound=3000,
upper_bound=4650,
step_size=50,
predicate=lambda p: p.stats['result_validity'] == "VALID")
qps_gen = b.generate()
is_gen = Step(search_param="gpu_inference_streams",
start=1,
end=4,
update=lambda x: x + 1).generate()
bs_gen = Step(search_param="gpu_batch_size",
start=200,
end=100,
update=lambda x: x - 50).generate()
curr_cross = {}
# Generate first run cross:
curr_cross = do_send(qps_gen)
curr_cross.update(do_send(is_gen))
curr_cross.update(do_send(bs_gen))
num_runs=0
while num_runs != self.timeout:
past_run = yield curr_cross
num_runs += 1
past_cross = curr_cross.copy()
if b.was_good(past_run):
# First run done, we can increase server_target_qps
partial = do_send(qps_gen, past_run)
else:
# We want to decrease server_target_qps, but let's try other stuff first:
partial = do_send(is_gen)
if partial is None:
# That was exhausted, let's try another:
partial = do_send(bs_gen)
if partial is None:
# We must do the qps reduction:
partial = do_send(qps_gen, past_run)
if partial is None:
# If either branch of qps_gen gave us None, catch it here:
break
else:
curr_cross.update(partial)
```
| 45.49635 | 515 | 0.695091 | eng_Latn | 0.990091 |
ed107588eb2c836419e745f7bac8080c8964192d | 9,743 | md | Markdown | CHANGELOG.md | mohsinalimat/ADUtils | 1049f789f44ec38db349644711ce2df514f91064 | [
"MIT"
] | 1 | 2020-02-12T04:30:36.000Z | 2020-02-12T04:30:36.000Z | CHANGELOG.md | mohsinalimat/ADUtils | 1049f789f44ec38db349644711ce2df514f91064 | [
"MIT"
] | null | null | null | CHANGELOG.md | mohsinalimat/ADUtils | 1049f789f44ec38db349644711ce2df514f91064 | [
"MIT"
] | null | null | null | # Change Log
All notable changes to this project will be documented in this file.
`ADUtils` adheres to [Semantic Versioning](http://semver.org/).
## [10.1.0]
### Added
- Utils: create `ad_removeAllArrangedSubviews` and `ad_addArrangedSubviews` methods on `UIStackView`
### Update
- Project now asks for swift 5.0
### Fixed
- Fixed some warnings regarding missing imports
- Fixed some warnings using @unknown default in enums
- Fixed possible retain cycles on `NavigationControllerObserver`
## [10.0.1]
### Fixed
- `attributedString(arguments:defaultAttributes:differentFormatAttributes:)` handles correctly variable-width unicode characters (like emojis) in the string format
## [10.0.0]
### Updated
- Set minimal requirements to iOS 10.0
### Fixed
- `DynamicFont` is now compliant with App Extensions
## [9.4.0]
### Created
- `MKMapView`: add `dequeueAnnotationView<U: MKAnnotationView>(annotationView:, annotation:) -> U` to dequeue `MKAnnotationView`s similarly to cells and headers in `Table|CollectionView`
### Updated
- Dequeuing methods for `UITableView` and `UICollectionView` now have an optional parameter to indicate the class of the dequeued element, allowing to write for instance `let cell = tableView.dequeue(SomeTableViewCell.self, at: indexPath)` instead of `let cell: SomeTableViewCell = tableView.dequeue(at: indexPath)`
## [9.3.0]
### Created
- `JSONDecoder` and `PropertyListDecoder`: add `ad_safelyDecodeArray<T>(of type: T.Type, from data: Data)` to decode a top-level array of values of the given type from the given JSON representation. If the decoding of a value fails, it is ignored and will not be present in the final array
- `KeyedDecodingContainer`: add `ad_safelyDecodeArray<T>(of type: T.Type, forKey key: KeyedDecodingContainer.Key)` to decode an array of values of the given type for the given key. If the decoding of a value fails, it is ignored and will not be present in the final array
- `Collection` of `NSLayoutConstraint`: add `activate()` which activate each constraint in the collection
- `Collection` of `NSLayoutConstraint`: add `deactivate()` which deactivate each constraint in the collection
## [9.2.0]
### Created
- `UIViewController`: add `ad_insert(child:in:)` to insert a child viewController in a layoutGuide instead of a view
- `NSLayoutConstraint`: add `priority(_:)` that returns the constraint with the given priority
- `UILayoutPriority`: add `applyIfPossible` which is `.required - 1`
- `UITableViewHeaderFooterView`: add `ad_preferredContentViewLayoutHeight(fittingWidth:)`
- `UILayoutGuide`: add `ad_pinTo(_: edges: UIRectEdge, insets: UIEdgeInsets, priority: UILayoutPriority)`
- `UILayoutGuide`: add `ad_center(in: along axis: NSLayoutConstraint.Axis, priority: UILayoutPriority)`
- `UILayoutGuide`: add `ad_constrain(in: edges: UIRectEdge, insets: UIEdgeInsets, priority: UILayoutPriority)`
- `UILayoutGuide`: add `ad_constrain(to size: CGSize, priority: UILayoutPriority)`
### Fixed
- Update pods for Xcode 10.2
## [9.1.0]
### Created
- `UIView`: Add missing method `ad_pinToLayoutGuide:insets:priority:`
- `UILayoutGuide`: add `ad_pinToOwningView(edges: UIRectEdge, insets: UIEdgeInsets, priority: UILayoutPriority)`
- `UILayoutGuide`: add `ad_centerInOwningView(along axis: NSLayoutConstraint.Axis, priority: UILayoutPriority)`
- `UILayoutGuide`: add `ad_constrainInOwningView(edges: UIRectEdge, insets: UIEdgeInsets, priority: UILayoutPriority)`
- `UILayoutGuide`: add `ad_constrain(to size: CGSize, priority: UILayoutPriority)`
### Updated
- Layout: method creating constraints now return an array containing thoses constraints as `@discardableResult`
## [9.0.0]
### Created
- Layout: create `ad_constrainInSuperview(edges:insets:priority:)`
- LayoutGuide: create `ad_pin(to:edges:insets:priority:)`, `ad_center(in:along:priority:)`, `ad_center(in:priority:)`, `ad_constrain(in:edges:insets:priority:)`
- `UIEdgeInsets`: add `init(top:)`, `init(bottom:)`, `init(left:)`, `init(right:)`
- Utils: create `ad_isBlank` method on `String?`
- `Sequence`: create `ad_groupedBy(grouping:)` method
### Updated
- `DeselectableView`: rename `smoothlyDeselectItems` to `ad_smoothlyDeselectItems` and make `DeselectableView` protocol private
- Layout: rename `ad_constraint(to:with:)` to `ad_constrain(to:priority:)`
- Layout: rename `ad_centerInSuperview(with:)` to `ad_centerInSuperview(priority:)` and `ad_centerInSuperview(along:with:)` to `ad_centerInSuperview(along:priority:)`
- `UIEdgeInsets`: rename `horizontal` and `vertical` properties to `totalHorizontal` and `totalVertical`
### Fixed
- Add missing unit tests (Swift & ObjC)
## [8.0.0]
### Created
- Create `UICollectionViewCell.ad_preferredCellLayoutHeight(fittingWidth:)`
### Updated
- Swift 4.2 support
### Removed
- Remove `EnumCollection` with Swift 4.2
### Fixed
- Fix layout tests
## [7.2.1]
### Fixed
- `ad_filter(query:keyPath:)` now performs search insensitively to diacritics on iOS9+
## [7.2.0]
- `NavigationControllerObserver`: add methods to stop observing view controllers
## [7.1.0]
### Added
- Add objc methods from DeselectableView UITableView and UICollectionView implementations.
- Create subspecs to be used in application extension, removing application related code.
## [7.0.2]
### Added
- Add documentation, readme, licence for opensource purpose.
### Updated
- Pod source is now on Github.
## [7.0.1]
### Fixed
- `attributedString(arguments:defaultAttributes:differentFormatAttributes:)` handles array of arguments bigger than 9 elements
## [7.0.0]
### Updated
- `ad_fromNib` is not optional anymore, meaning we do not have to specify the return type
## [6.0.0]
### Updated
- `ad_fromNib` type inference comes from the calling class instead of the generic return type
## [5.2.0]
### Added
- Utils: `ad_filter(query: String, for keyPaths: [KeyPath<Element, String>])` to filter an array with a query (e.g search bar content) for specified keypaths.
## [5.1.1]
### Updated
- Fixed some deprecation warnings
## [5.1.0]
### Added
- PropertyListArchiver: the PropertyListArchiver enables to set primitive types values for a given key and read them as well
## [5.0.1]
### Fixed
- Layout: `ad_constraint(to size: CGSize)` second item is now nil as supposed to for height and width constraints
- Layout: `ad_constraint(to size: CGSize)` second attribute is now notAnAttribute as supposed to for height and width constraint
## [5.0.0]
### Added
- Layout: `UITableViewCell.ad_preferredCellLayoutHeight(fittingWidth: CGFloat)` calculates the height of the cell content view
- Layout: `UIView.ad_preferredLayoutHeight(fittingWidth:)` and `UIView.ad_preferredLayoutWidth(fittingHeight:)`
### Removed
- `UIView.ad_preferredLayoutSize(fittingSize:lockDirections:)`
## [4.5.1]
### Added
- `DynamicFont` is now able to use system font inside `FontDescription`
## [4.5.0]
### Added
- Add `ad_localizedUppercaseString` and `localized` for Objective-C files
## [4.4.0]
### Added
- Layout: `ad_centerInSuperview(along axis:UILayoutConstraintAxis)` creates a constraint between centerX/Y anchors of a view and its superView
- Layout: `ad_centerInSuperView()` creates constraints to center a view in its superview along both axes
- Layout: `ad_constraint(to size:CGSize)` constraints a view width and height with the provided size
- Layout: All method that create constraints now enable to take a priorityLayout parameter (default is `UILayoutPriority.required`)
- `PropertyListArchiver`: `array(for key: String)` decodes data for key and returns an empty array if no data is found
- Unit tests are run to validate every commit
### Removed
### Fixed
- Unit tests: Fix `PropertyListArchiver` unit tests
- Do not notify proxy on simulator
- `NavigationControllerObserver`: fix a bug where bookeeping was done too late and view controller was not observed anymore
## [4.3.0]
### Added
- Use `Decodable` instead of `PropertyListReadable` in `PropertyListArchiver`
- Add `center` to `CGRect`
### Removed
### Fixed
## [4.2.0]
### Added
- `DynamicFontProvider`: an helper to provide dynamic type with custom font before iOS 11
### Updated
### Removed
### Fixed
## [4.1.0]
### Added
- `ProxyDetector`: Provide a way to notify the user if a proxy is running on the phone
### Updated
- `ad_localizedUppercaseString` is now deprecated after iOS 9
### Removed
### Fixed
## [4.0.0]
### Added
### Updated
- Swift 4 support
### Removed
### Fixed
## [3.6.0]
### Added
- `NavigationControllerObserver`: The `NavigationControllerObserver` class provides a simple API to observe the pop transitions that occur in a navigationController stack.
One drawback of `UINavigationController` is that its delegate is shared among multiple view controllers and this requires a lot of bookkeeping to register multiple delegates.
`NavigationControllerObserver` allows to register a delegate per viewController we want to observe.
What's more the class provides a navigationControllerDelegate property used to forward all the `UINavigationControllerDelegate` methods to another navigationController delegate if need be.
- important: The `NavigationControllerObserver` will observe only *animated* pop transitions. Indeed, if you call `popViewController(animated: false)` you won't be notified.
### Updated
### Removed
### Fixed
## [3.5.0]
### Added
- UIView + preferred layout size: Provides the preferred layout size for the view, this is the smallest size the view and its content can fit. You should populate the view before calling this method
- Optional + unwrap: Provides syntactic sugar to unwrap and execute a closure with an optional
- Add parameters owner and bundle in `ad_fromNib` method
### Updated
### Removed
### Fixed
| 32.804714 | 315 | 0.753669 | eng_Latn | 0.937802 |
ed1078b69921790e02448d72c76b5a28c3677d57 | 721 | md | Markdown | filters/README.md | rainbow-mind-machine/russian-rainbow-mind-machine | 6d63c8037956f1b2c733dc6ce3ea4aa0b882777e | [
"Apache-2.0"
] | 3 | 2018-05-17T03:01:01.000Z | 2018-05-21T11:53:17.000Z | filters/README.md | rainbow-mind-machine/russian-rainbow-mind-machine | 6d63c8037956f1b2c733dc6ce3ea4aa0b882777e | [
"Apache-2.0"
] | null | null | null | filters/README.md | rainbow-mind-machine/russian-rainbow-mind-machine | 6d63c8037956f1b2c733dc6ce3ea4aa0b882777e | [
"Apache-2.0"
] | null | null | null | # Pandoc filters
This directory contains Python scripts to apply filters to pandoc documents.
## Translation
Pandoc turns English Markdown documents into JSON.
These filters extract plain text from JSON, and use the Google Cloud Translate API
to translate the text from English to Russian.
The filters also extract links before the translation is carried out
and re-insert them at a similar location when the translation is done.
Pandoc then turns the JSON back into Russian Markdown.
## Authentication
To perform this task, you need to authenticate with Google Cloud.
Your authentication key should be set up with `gcloud` (see [../Setup.md](../Setup.md))
and should not need to be stored in this repository.
| 30.041667 | 87 | 0.787795 | eng_Latn | 0.998195 |
ed107de6c3fa9b0764565213d7e4601ab09426d2 | 427 | md | Markdown | README.md | swt83/php-october-janitor | 795edc84e6c041dfb6a536ea8f450ac420b98e7a | [
"MIT"
] | null | null | null | README.md | swt83/php-october-janitor | 795edc84e6c041dfb6a536ea8f450ac420b98e7a | [
"MIT"
] | null | null | null | README.md | swt83/php-october-janitor | 795edc84e6c041dfb6a536ea8f450ac420b98e7a | [
"MIT"
] | null | null | null | # Janitor for October
An OctoberCMS plugin for adding a "clear cache" button to the backend.
With help from [FlynsArmy](https://github.com/Flynsarmy/oc-dashboardcachewidget-plugin).
## Install
Add as a submodule to your project:
```bash
$ git submodule add [email protected]:swt83/php-october-janitor.git plugins/travis/janitor
```
## Usage
Just go to the Janitor page of the backend and click the button.
| 23.722222 | 89 | 0.730679 | eng_Latn | 0.782574 |
ed10babf89f2df18af8855cc4b8e86f5b9c4c525 | 541 | md | Markdown | docs/ja/api_reference/data/display/auditlogservicepage.md | yahoojp-marketing/yahoo-japan-ads-script-documents | 1a969cb840b96a4d0ae4c753bbb8249ed3736bb3 | [
"MIT"
] | 2 | 2021-10-01T04:41:21.000Z | 2021-10-12T00:39:09.000Z | docs/ja/api_reference/data/display/auditlogservicepage.md | yahoojp-marketing/yahoo-japan-ads-script-documents | 1a969cb840b96a4d0ae4c753bbb8249ed3736bb3 | [
"MIT"
] | null | null | null | docs/ja/api_reference/data/display/auditlogservicepage.md | yahoojp-marketing/yahoo-japan-ads-script-documents | 1a969cb840b96a4d0ae4c753bbb8249ed3736bb3 | [
"MIT"
] | 1 | 2022-01-11T05:58:25.000Z | 2022-01-11T05:58:25.000Z | # AuditLogServicePage
<div lang=\"ja\">AuditLogServicePage、getメソッドの実行結果（全Entityのリスト）を保持します。</div>
## Table of contents
### Properties
- [totalNumEntries](auditlogservicepage.md#totalnumentries)
- [values](auditlogservicepage.md#values)
## Properties
### totalNumEntries
• `Optional` **totalNumEntries**: *number*
<div lang=\"ja\">取得される項目の総件数です。</div>
**`memberof`** AuditLogServicePage
___
### values
• `Optional` **values**: ``null`` \| [*AuditLogServiceValue*](auditlogservicevalue.md)[]
**`memberof`** AuditLogServicePage
| 18.033333 | 88 | 0.720887 | yue_Hant | 0.624485 |
ed1229bbf7cff19fd676fe34709d2e2048bf95a3 | 4,326 | md | Markdown | articles/devtest-labs/devtest-lab-scale-lab.md | tsunami416604/azure-docs.hu-hu | aeba852f59e773e1c58a4392d035334681ab7058 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/devtest-labs/devtest-lab-scale-lab.md | tsunami416604/azure-docs.hu-hu | aeba852f59e773e1c58a4392d035334681ab7058 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/devtest-labs/devtest-lab-scale-lab.md | tsunami416604/azure-docs.hu-hu | aeba852f59e773e1c58a4392d035334681ab7058 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Kvóták és korlátok méretezése a laborban Azure DevTest Labsban | Microsoft Docs
description: Ez a cikk bemutatja, hogyan méretezheti a labort Azure DevTest Labsban. Megtekintheti a használati kvótákat és korlátozásokat, és megnövelheti a kérést.
ms.topic: article
ms.date: 06/26/2020
ms.openlocfilehash: 2166eaab073e2abc24ca24494ae13eb876db1fcf
ms.sourcegitcommit: 829d951d5c90442a38012daaf77e86046018e5b9
ms.translationtype: MT
ms.contentlocale: hu-HU
ms.lasthandoff: 10/09/2020
ms.locfileid: "87533954"
---
# <a name="scale-quotas-and-limits-in-devtest-labs"></a>Kvóták és korlátozások méretezése a DevTest Labs szolgáltatásban
A DevTest Labs szolgáltatásban végzett munka során észreveheti, hogy egyes Azure-erőforrások esetében bizonyos alapértelmezett korlátozások vannak érvényben, ami hatással lehet a DevTest Labs szolgáltatásra. Ezeket a korlátokat **kvótáknak**nevezzük.
> [!NOTE]
> A DevTest Labs szolgáltatás nem kényszeríti ki a kvótákat. Az esetlegesen felmerülő kvóták a teljes Azure-előfizetés alapértelmezett korlátai.
Minden Azure-erőforrást használhat, amíg el nem éri a kvótáját. Minden előfizetéshez külön kvóta tartozik, a felhasználás pedig előfizetésenként van nyilvántartva.
Például minden előfizetéshez tartozik egy 20 maggal alapértelmezett kvóta. Így ha a laborban virtuális gépeket hoz létre négy maggal, akkor csak öt virtuális gépet hozhat létre.
Az [Azure-előfizetések és-szolgáltatások korlátai](../azure-resource-manager/management/azure-subscription-service-limits.md) az Azure-erőforrások leggyakoribb kvótáit sorolja fel. A laborban leggyakrabban használt erőforrások, amelyek esetében kvóták merülhetnek fel, a virtuálisgép-magok, a nyilvános IP-címek, a hálózati adapterek, a felügyelt lemezek, az Azure szerepkör-hozzárendelések és a ExpressRoute-áramkörök is.
## <a name="view-your-usage-and-quotas"></a>A használat és a kvóták megtekintése
Ezek a lépések bemutatják, hogyan tekintheti meg az előfizetéshez tartozó aktuális kvótákat adott Azure-erőforrásokhoz, és megtekintheti az egyes felhasznált kvóták százalékos arányát.
1. Jelentkezzen be az [Azure Portalra](https://go.microsoft.com/fwlink/p/?LinkID=525040).
1. Válassza a **További szolgáltatások**lehetőséget, majd válassza a **számlázás** lehetőséget a listából.
1. A számlázás panelen válasszon egy előfizetést.
4. Válassza a **használat + kvóták**lehetőséget.
Megjelenik a használat + kvóták panel, amely felsorolja az előfizetésben elérhető különböző erőforrásokat, valamint az erőforrásként használt kvóta százalékos arányát.
## <a name="requesting-more-resources-in-your-subscription"></a>További erőforrások igénylése az előfizetésben
Ha eléri a kvóta korlátját, az előfizetésben lévő erőforrások alapértelmezett korlátja az [Azure-előfizetés és a szolgáltatás korlátaiban](../azure-resource-manager/management/azure-subscription-service-limits.md)leírtak szerint legfeljebb egy maximális korlátra növelhető.
Ezek a lépések bemutatják, hogyan kérheti a kvóta növelését a [Azure Portal](https://go.microsoft.com/fwlink/p/?LinkID=525040).
1. Válassza a **További szolgáltatások**lehetőséget, válassza a **számlázás**, majd a **használat + kvóták**lehetőséget.
1. A használat + kvóták panelen válassza a **kérés növelése** gombot.
1. A kérelem elvégzéséhez és elküldéséhez adja meg a szükséges információkat az **új támogatási kérelem** űrlapjának mindhárom lapján.
Az [Azure-korlátok és-növekedések megismerése](https://azure.microsoft.com/blog/azure-limits-quotas-increase-requests/) további információkat biztosít az Azure-támogatással kapcsolatban a kvóta növelésének meghívásához.
[!INCLUDE [devtest-lab-try-it-out](../../includes/devtest-lab-try-it-out.md)]
### <a name="next-steps"></a>További lépések
* Ismerkedjen meg a [DevTest Labs Azure Resource Manager a rövid útmutató sablonjának galériájában](https://github.com/Azure/azure-devtestlab/tree/master/samples/DevTestLabs/QuickStartTemplates).
| 70.918033 | 422 | 0.809524 | hun_Latn | 1.000002 |
ed126e7f52dad9e3af9aa17ab3cb7b9fc66d998e | 11 | md | Markdown | README.md | LIFLIYLI/tiana | bbffa3ab7185eedb57ba7f0553df01f245657da0 | [
"MIT"
] | null | null | null | README.md | LIFLIYLI/tiana | bbffa3ab7185eedb57ba7f0553df01f245657da0 | [
"MIT"
] | null | null | null | README.md | LIFLIYLI/tiana | bbffa3ab7185eedb57ba7f0553df01f245657da0 | [
"MIT"
] | null | null | null | # tiana
天啊
| 3.666667 | 7 | 0.636364 | vie_Latn | 0.775868 |
ed1275ce9375c4d508b54d634fe44c6a5e90398a | 1,416 | md | Markdown | curriculum/challenges/ukrainian/02-javascript-algorithms-and-data-structures/intermediate-algorithm-scripting/spinal-tap-case.md | fcastillo-serempre/freeCodeCamp | 43496432d659bac8323ab2580ba09fa7bf9b73f2 | [
"BSD-3-Clause"
] | 172,317 | 2017-01-11T05:26:18.000Z | 2022-03-31T23:30:16.000Z | curriculum/challenges/ukrainian/02-javascript-algorithms-and-data-structures/intermediate-algorithm-scripting/spinal-tap-case.md | fcastillo-serempre/freeCodeCamp | 43496432d659bac8323ab2580ba09fa7bf9b73f2 | [
"BSD-3-Clause"
] | 26,252 | 2017-01-11T06:19:09.000Z | 2022-03-31T23:18:31.000Z | curriculum/challenges/ukrainian/02-javascript-algorithms-and-data-structures/intermediate-algorithm-scripting/spinal-tap-case.md | fcastillo-serempre/freeCodeCamp | 43496432d659bac8323ab2580ba09fa7bf9b73f2 | [
"BSD-3-Clause"
] | 27,418 | 2017-01-11T06:31:22.000Z | 2022-03-31T20:44:38.000Z | ---
id: a103376db3ba46b2d50db289
title: Spinal Tap Case
challengeType: 5
forumTopicId: 16078
dashedName: spinal-tap-case
---
# --description--
Перетворити рядок в spinal case. У spinal case усі-слова-в-нижньому-регістрі-і-розділені-тире.
# --hints--
`spinalCase("This Is Spinal Tap")` повинен повертати рядок `this-is-spinal-tap`.
```js
assert.deepEqual(spinalCase('This Is Spinal Tap'), 'this-is-spinal-tap');
```
`spinalCase("thisIsSpinalTap")` повинен повертати рядок `this-is-spinal-tap`.
```js
assert.strictEqual(spinalCase('thisIsSpinalTap'), 'this-is-spinal-tap');
```
`spinalCase("The_Andy_Griffith_Show")` повинен повертати рядок `the-andy-griffith-show`.
```js
assert.strictEqual(
spinalCase('The_Andy_Griffith_Show'),
'the-andy-griffith-show'
);
```
`spinalCase("Teletubbies say Eh-oh")` повинен повертати рядок `teletubbies-say-eh-oh`.
```js
assert.strictEqual(
spinalCase('Teletubbies say Eh-oh'),
'teletubbies-say-eh-oh'
);
```
`spinalCase("AllThe-small Things")` повинен повертати рядок `all-the-small-things`.
```js
assert.strictEqual(spinalCase('AllThe-small Things'), 'all-the-small-things');
```
# --seed--
## --seed-contents--
```js
function spinalCase(str) {
return str;
}
spinalCase('This Is Spinal Tap');
```
# --solutions--
```js
function spinalCase(str) {
str = str.replace(/([a-z](?=[A-Z]))/g, '$1 ');
return str.toLowerCase().replace(/\ |\_/g, '-');
}
```
| 19.943662 | 94 | 0.694915 | yue_Hant | 0.119049 |
ed136fda5a2bf28839fa0d01dfa0367a1af4dd04 | 4,780 | md | Markdown | docs/sdk/crashes/includes/apple-common-methods-2.md | alexandrborisovyg/appcenter-docs | f03d8705d8b8131a5f238a9f1accf48f2407fdd3 | [
"CC-BY-4.0",
"MIT"
] | 132 | 2018-02-21T15:24:05.000Z | 2022-03-24T10:47:47.000Z | docs/sdk/crashes/includes/apple-common-methods-2.md | alexandrborisovyg/appcenter-docs | f03d8705d8b8131a5f238a9f1accf48f2407fdd3 | [
"CC-BY-4.0",
"MIT"
] | 1,236 | 2018-01-27T00:35:28.000Z | 2022-03-31T10:01:16.000Z | docs/sdk/crashes/includes/apple-common-methods-2.md | alexandrborisovyg/appcenter-docs | f03d8705d8b8131a5f238a9f1accf48f2407fdd3 | [
"CC-BY-4.0",
"MIT"
] | 377 | 2018-01-27T00:39:29.000Z | 2022-03-29T13:14:39.000Z | ---
title: Shared docs for Apple Crashes SDK
description: Shared docs for Apple Crashes SDK
keywords: sdk, crash
author: lucen-ms
ms.author: lucen
ms.date: 10/22/2020
ms.topic: include
ms.assetid: 1c1391e4-0c39-4141-893e-766ad22266d7
ms.custom: sdk
ms.tgt_pltfrm: apple
dev_langs:
- swift
- objc
---
### Get information about the sending status for a crash log
At times, you want to know the status of your app crash. A common use case is that you might want to show UI that tells the users that your app is submitting a crash report, or, in case your app is crashing quickly after the launch, you want to adjust the behavior of the app to make sure the crash logs can be submitted. The `CrashesDelegate`-protocol defines three different callbacks that you can use in your app to be notified of what's going on:
#### The following callback will be invoked before the SDK sends a crash log
```objc
- (void)crashes:(MSACCrashes *)crashes willSendErrorReport:(MSACErrorReport *)errorReport {
// Your code, e.g. to present a custom UI.
}
```
```swift
func crashes(_ crashes: Crashes, willSend errorReport: ErrorReport) {
// Your code, e.g. to present a custom UI.
}
```
In case we have network issues or an outage on the endpoint, and you restart the app, `willSendErrorReport` is triggered again after process restart.
#### The following callback will be invoked after the SDK sent a crash log successfully
```objc
- (void)crashes:(MSACCrashes *)crashes didSucceedSendingErrorReport:(MSACErrorReport *)errorReport {
// Your code, e.g. to hide the custom UI.
}
```
```swift
func crashes(_ crashes: Crashes, didSucceedSending errorReport: ErrorReport) {
// Your code goes here.
}
```
#### The following callback will be invoked if the SDK failed to send a crash log
```objc
- (void)crashes:(MSACCrashes *)crashes didFailSendingErrorReport:(MSACErrorReport *)errorReport withError:(NSError *)error {
// Your code goes here.
}
```
```swift
func crashes(_ crashes: Crashes, didFailSending errorReport: ErrorReport, withError error: Error) {
// Your code goes here.
}
```
Receiving `didFailSendingErrorReport` means a non-recoverable error such as a **4xx** code occurred. For example, **401** means the `appSecret` is wrong.
This callback isn't triggered if it's a network issue. In this case, the SDK keeps retrying (and also pauses retries while the network connection is down).
### Add attachments to a crash report
You can add binary and text attachments to a crash report. The SDK will send them along with the crash so that you can see them in App Center portal. The following callback will be invoked right before sending the stored crash from previous application launches. It won't be invoked when the crash happens. Here is an example of how to attach text and an image to a crash:
```objc
- (NSArray<MSACErrorAttachmentLog *> *)attachmentsWithCrashes:(MSACCrashes *)crashes
forErrorReport:(MSACErrorReport *)errorReport {
MSACErrorAttachmentLog *attachment1 = [MSACErrorAttachmentLog attachmentWithText:@"Hello world!" filename:@"hello.txt"];
MSACErrorAttachmentLog *attachment2 = [MSACErrorAttachmentLog attachmentWithBinary:[@"Fake image" dataUsingEncoding:NSUTF8StringEncoding] filename:@"fake_image.jpeg" contentType:@"image/jpeg"];
return @[ attachment1, attachment2 ];
}
```
```swift
func attachments(with crashes: Crashes, for errorReport: ErrorReport) -> [ErrorAttachmentLog]? {
let attachment1 = ErrorAttachmentLog.attachment(withText: "Hello world!", filename: "hello.txt")
let attachment2 = ErrorAttachmentLog.attachment(withBinary: "Fake image".data(using: String.Encoding.utf8), filename: nil, contentType: "image/jpeg")
return [attachment1!, attachment2!]
}
```
> [!NOTE]
> The size limit is currently 7 MB. Attempting to send a larger attachment will trigger an error.
## Enable or disable App Center Crashes at runtime
You can enable and disable App Center Crashes at runtime. If you disable it, the SDK won't do any crash reporting for the app.
```objc
[MSACCrashes setEnabled:NO];
```
```swift
Crashes.enabled = false
```
To enable App Center Crashes again, use the same API but pass `YES`/`true` as a parameter.
```objc
[MSACCrashes setEnabled:YES];
```
```swift
Crashes.enabled = true
```
The state is persisted in the device's storage across application launches.
> [!NOTE]
> This method must only be used after `Crashes` has been started.
## Check if App Center Crashes is enabled
You can also check if App Center Crashes is enabled or not:
```objc
BOOL enabled = [MSACCrashes isEnabled];
```
```swift
var enabled = Crashes.enabled
```
> [!NOTE]
> This method must only be used after `Crashes` has been started, it will always return `false` before start.
| 37.936508 | 450 | 0.74728 | eng_Latn | 0.978952 |
ed13af61b7f063265fc9822113c3cce676556abb | 4,589 | md | Markdown | README.md | puppetlabs/trapperkeeper-rpc | fe7b71743f3548001b9d3352ae819d5794e20fcd | [
"Apache-2.0"
] | 3 | 2015-04-20T21:27:57.000Z | 2016-12-11T22:30:42.000Z | README.md | puppetlabs/trapperkeeper-rpc | fe7b71743f3548001b9d3352ae819d5794e20fcd | [
"Apache-2.0"
] | 12 | 2015-01-16T19:28:14.000Z | 2018-02-14T23:44:35.000Z | README.md | puppetlabs/trapperkeeper-rpc | fe7b71743f3548001b9d3352ae819d5794e20fcd | [
"Apache-2.0"
] | 3 | 2015-01-16T19:38:06.000Z | 2021-03-26T12:14:10.000Z | [](https://travis-ci.org/puppetlabs/trapperkeeper-rpc)
# trapperkeeper-rpc
This library enables transparent RPC implementation for [TrapperKeeper](https://github.com/puppetlabs/trapperkeeper)
services. It provides two things:
* A `call-remote-svc-fn` function used to implement a proxied version
of a given TK service protocol
* An RPC server service
(`puppetlabs.trapperkeeper.rpc.services.rpc-server-service`) that
exposes proxied service implementations over HTTP.
[](http://clojars.org/puppetlabs/trapperkeeper-rpc)
## Feature Overview
* Uses [transit](https://github.com/cognitect/transit-clj) to do
(de)serialization. Choice of JSON or msgpack as the underlying wire
format (the latter being the default).
* Optional Per-service certificate whitelisting
* HTTP or HTTPS
* Per-service endpoints
* Robust error reporting
Planned features:
* basic API for adding custom (de|en)coders
* support for ignoring (defn-) defined functions
## Example usage
```clojure
(ns gnarlytimes.services
(:require [puppetlabs.trapperkeeper.core :refer [defservice]]
[puppetlabs.trapperkeeper.rpc.core :refer [defremoteservice]]))
;; (note: TK best practices are eschewed for the sake of brevity)
;; A service protocol
(defprotocol MathService
(add [this x y])
(divide [this x y]))
;; The traditional (or "concrete") implementation of the MathService protocol
(defservice math-service
MathService
[]
(add [this x y] (+ x y))
(divide [this x y] (/ x y)))
;; A proxied implementation of MathService for use via RPC
(defremoteservice remote-math-service
MathService
(add [this x y])
(divide [this x y]))
```
Given the following config:
```clojure
{:rpc {;; currently supported: :msgpack and :json, both via transit
:wire-format :msgpack
;; settings for making signed requests to the rpc server
:ssl {:client-cert "dev-resources/ssl/client-cert.pem"
:client-key "dev-resources/ssl/client-key.pem"
:client-ca "dev-resources/ssl/ca.pem"}
;; This maps service IDs to RPC settings used by both the RPC
;; client and server components.
:services {:MathService
{;; used by the RPC server service to find service functions
:protocol-ns "gnarlytimes.services"
;; each service's RPC endpoint can have its own cert whitelist
:certificate-whitelist "dev-resources/ssl/math-service-cert-whitelist"
;; the client uses this to issue RPC calls
:endpoint "https://localhost:9002/rpc/call"}}}
;; a webserver that will listen for RPC calls.
:webserver {:rpc {:ssl-host "0.0.0.0"
:ssl-port 9002
:ssl-key "dev-resources/ssl/key.pem"
:ssl-cert "dev-resources/ssl/cert.pem"
:ssl-ca-cert "dev-resources/ssl/ca.pem"})}
```
and two TK stacks, one with a bootstrap.cfg like this:
```
puppetlabs.trapperkeeper.rpc.services/rpc-server-service
gnarlytimes.services/math-service
```
and another like this:
```
gnarlytimes.services/remote-math-service
```
The latter can issue calls to the functions defined by `MathService`
as if the service was defined locally.
## Error handling
There are three classes of exceptions thrown by this library during an
RPC call. An **RPCConnectionException** is thrown when a given service's
endpoint is unreachable or otherwise uncommunicative. An
**RPCAuthenticationException** is thrown if the calling client's
certificate is not on the whitelist for that service on the server
side.
Should the remotely called service function throw an exception, the
stack trace from the remote server is returned as part of an
**RPCException**. This exception is also used for cases of
misconfiguration (ie trying to call a function that does not exist in
the RPC server's TK stack).
## Running the tests
`lein test`
## Author
Nathaniel Smith <[email protected]>
## Contributors
* Justin Holguin
## Support
To file a bug, please open a Github issue against this project. Bugs and PRs are
addressed on a best-effort basis. Puppet Labs does not guarantee support for
this project.
## License
Copyright © 2015 Puppet Labs
Distributed under the [Apache License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.html)
| 32.090909 | 139 | 0.70255 | eng_Latn | 0.938322 |
ed14dbacec268bc26e6fe26dc501573550b54815 | 1,038 | md | Markdown | readme.md | jackalyst/subxml | a391742eb06d4a968dbfc876adf3736f3eaa4a42 | [
"MIT"
] | 3 | 2021-11-21T23:49:29.000Z | 2021-11-22T00:50:04.000Z | readme.md | jackalyst/subxml | a391742eb06d4a968dbfc876adf3736f3eaa4a42 | [
"MIT"
] | null | null | null | readme.md | jackalyst/subxml | a391742eb06d4a968dbfc876adf3736f3eaa4a42 | [
"MIT"
] | 1 | 2021-11-21T23:49:50.000Z | 2021-11-21T23:49:50.000Z | # function subxml
Based loosely on the implementation of substr(), but instead of a string it's able to take the inner text of HTML/XML and truncate that instead. It's useful for trimming
## Overview
There are three parameters
```php
@param string
The input string/xml.
@param int
The length to trim.
@param string (optional)
Boundary type ['char', 'sentence', 'word']
Default 'char'
```
## Usage
The default is to truncate the inner XML to a set *character length*.
```php
$string = "<p>This is a long string</p>";
$string = subxml($string, 4);
echo $string; // Result: <p>This</p>
```
The other is to truncate it to a *word length*.
```php
$string = "<p>This is a long string</p>";
$string = subxml($string, 2, 'word');
echo $string; // Result: <p>This is</p>
```
And how about to *sentence length*?
```php
$string = "<p>This is a long string!! With multiple sentences.</p>";
$string = subxml($string, 1, 'sentence');
echo $string; // Result: <p>This is a long string!!</p>
```
## Todo
- Don't trim script and style's. | 22.085106 | 170 | 0.668593 | eng_Latn | 0.978712 |
ed15e333325a687ed8c7d2548d10fdf0a2967a08 | 1,047 | md | Markdown | actix-files/README.md | actix/actix-web | c09ec6af4cb74366108d359357196b0e23b2f94d | [
"Apache-2.0",
"MIT"
] | 14,650 | 2017-10-24T01:14:36.000Z | 2022-03-31T20:08:09.000Z | actix-files/README.md | actix/actix-web | c09ec6af4cb74366108d359357196b0e23b2f94d | [
"Apache-2.0",
"MIT"
] | 2,180 | 2017-10-30T02:38:32.000Z | 2022-03-30T22:40:52.000Z | actix-files/README.md | actix/actix-web | c09ec6af4cb74366108d359357196b0e23b2f94d | [
"Apache-2.0",
"MIT"
] | 1,455 | 2017-10-24T01:31:49.000Z | 2022-03-30T05:31:00.000Z | # actix-files
> Static file serving for Actix Web
[](https://crates.io/crates/actix-files)
[](https://docs.rs/actix-files/0.6.0-beta.7)
[](https://blog.rust-lang.org/2021/05/06/Rust-1.52.0.html)
<br />
[](https://deps.rs/crate/actix-files/0.6.0-beta.7)
[](https://crates.io/crates/actix-files)
[](https://discord.gg/NWpN5mmg3x)
## Documentation & Resources
- [API Documentation](https://docs.rs/actix-files/)
- [Example Project](https://github.com/actix/examples/tree/master/basics/static_index)
- Minimum Supported Rust Version (MSRV): 1.52
| 55.105263 | 129 | 0.731614 | yue_Hant | 0.586385 |
ed16949cdce1ce15e104013101e44e4f64bbe2de | 3,355 | md | Markdown | source/_posts/this_amazonloved_wakeup_light_alarm_clock_is_under_22_right_now.md | soumyadipdas37/finescoop.github.io | 0346d6175a2c36d4054083c144b7f8364db73f2f | [
"MIT"
] | null | null | null | source/_posts/this_amazonloved_wakeup_light_alarm_clock_is_under_22_right_now.md | soumyadipdas37/finescoop.github.io | 0346d6175a2c36d4054083c144b7f8364db73f2f | [
"MIT"
] | null | null | null | source/_posts/this_amazonloved_wakeup_light_alarm_clock_is_under_22_right_now.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/25/13/26324588-0-image-a-2_1601036188684.jpg
title: This Amazon-loved wake-up light alarm clock is under £22 right now
description: The clocks are set to go back Sunday, October 25, signalling the end of British Summer Time and those extra hours of sunlight.
date: 2020-09-25-13-44-07
categories: [latest, female]
featured: true
---
The clocks are set to go back Sunday, October 25, signalling the end of British Summer Time and those extra hours of sunlight.
Getting out of bed in the morning can be a challenge on those cold, dark mornings. But thankfully there's a solution. Hundreds of shoppers have deemed the FITFORT Alarm Clock Wake Up Light their favourite sunrise simulating alarm clock and it's just what you need to combat seasonal affective disorder.
Better yet: You don't have to fork out loads of money to bag this bedside gadget, as it's currently just £21.24 on Amazon - that's 15 per cent off.
A light-based alarm clock will help you on your way to becoming a morning person, or at the very least ensure that your morning gets off to the best start
Not only is the top-rated wake-up alarm clock from FITFORT incredibly sleek, but it's super functional, too. With the sunrise and sunset simulation, this clock gradually brightens and dims, so users can wake up with natural and gradual light and wind down with ease in the evening.
More than 2,000 reviewers have given the clock a perfect star rating, claiming it helps improve their mood and boost their energy levels.
Earning itself the number one top spot in Amazon's Wake-Up Lights category, shoppers say this clock is 'straightforward to set up' and 'an excellent buy', describing it a must-have 'for waking up and not feeling groggy'.
'I bought this wake-up light alarm clock in conjunction with a SAD lamp as I really suffer from low mood during the dark winter months,' wrote one five-star reviewer.
'I was somewhat cynical about the alarm clock to begin with, but I am now waking up nice and early in a well-lit room (which then helps me to get my morning coffee and sit in front of my SAD lamp).'
The FITFORT alarm clock (left) not only helps you wake up, but it has a sunset feature that helps guide you to a restful natural sleep (right, stock picture)
'This alarm clock is amazing for anyone who wants a more peaceful way to wake up than your typical beeping alarm,' another shopper wrote, adding, 'Waking up to the sunrise light feature has really changed how anxious I used to feel when waking up. Now, I wake up much calmer and more gradual than before. It really helped my body clock.'
A third shopper agreed adding: 'Changed my sleeping pattern for the better. Very impressed with this gadget. I've always struggled to get up in the morning but with the gradual light and then alarm I've been jumping out of bed feeling ready to tackle the day.'
The FITFORT Alarm Clock Wake Up Light has buttons to adjust brightness and the duration of sunsets and sunrises.
It boasts multiple light colour options and six natural and soothing sounds such as piano, waves, violin, croak and the traditional beep. Even better? It has additional features like FM radio, which you can set as an alarm too.
MailOnline may earn commission on sales from the links on this page.
| 81.829268 | 337 | 0.782712 | eng_Latn | 0.999343 |
ed16a68b504ce441e7337c9bb375f5cf7825da8c | 10,422 | md | Markdown | articles/azure-monitor/visualizations.md | jayv-ops/azure-docs.de-de | 6be2304cfbe5fd0bf0d4ed0fbdf4a6a4d11ac6e0 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/azure-monitor/visualizations.md | jayv-ops/azure-docs.de-de | 6be2304cfbe5fd0bf0d4ed0fbdf4a6a4d11ac6e0 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/azure-monitor/visualizations.md | jayv-ops/azure-docs.de-de | 6be2304cfbe5fd0bf0d4ed0fbdf4a6a4d11ac6e0 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Visualisieren von Daten aus Azure Monitor | Microsoft-Dokumentation
description: Enthält eine Zusammenfassung der verfügbaren Methoden zum Visualisieren von in Azure Monitor gespeicherten Metrik- und Protokolldaten.
ms.topic: conceptual
author: bwren
ms.author: bwren
ms.date: 01/25/2021
ms.openlocfilehash: b90d628f0d24e43d7b9f2e3fa87e74d426648c6e
ms.sourcegitcommit: 867cb1b7a1f3a1f0b427282c648d411d0ca4f81f
ms.translationtype: HT
ms.contentlocale: de-DE
ms.lasthandoff: 03/20/2021
ms.locfileid: "102048572"
---
# <a name="visualizing-data-from-azure-monitor"></a>Visualisieren von Daten aus Azure Monitor
Dieser Artikel enthält eine Zusammenfassung der verfügbaren Methoden zum Visualisieren von in Azure Monitor gespeicherten Metrik- und Protokolldaten.
Visualisierungen wie Diagramme und Grafiken können Ihnen die Analyse Ihrer Überwachungsdaten zur Anzeige von Detailinformationen zu Problemen und zum Identifizieren von Mustern erleichtern. Je nach dem Tool, das Sie verwenden, haben Sie vielleicht auch die Möglichkeit, Visualisierungen für andere Benutzer innerhalb und außerhalb Ihrer Organisation freizugeben.
## <a name="workbooks"></a>Arbeitsmappen
[Arbeitsmappen](./visualize/workbooks-overview.md) sind interaktive Dokumente, die umfassende Einblicke in Ihre Daten, Untersuchungen und die Zusammenarbeit innerhalb des Teams bereitstellen. Spezifische Beispiele, wo Arbeitsmappen hilfreich sind, sind Anleitungen zur Problembehandlung und Nachbesprechungen zu Incidents.
### <a name="advantages"></a>Vorteile
- Sowohl Metriken als auch Protokolle werden unterstützt.
- Unterstützt Parameter, die interaktive Berichte ermöglichen, wobei durch die Auswahl eines Elements in einer Tabelle zugeordnete Diagramme und Visualisierungen dynamisch aktualisiert werden.
- Dokumentähnlicher Ablauf.
- Option für persönliche oder freigegebene Arbeitsmappen.
- Einfache und zusammenarbeitsfreundliche Benutzeroberfläche für die Erstellung.
- Die Vorlagen unterstützen den öffentlichen Vorlagenkatalog auf GitHub-Basis.
### <a name="limitations"></a>Einschränkungen
- Keine automatische Aktualisierung.
- Kein dichtes Layout wie bei Dashboards, sodass Arbeitsmappen weniger als zentrale Konsole geeignet sind. Eher für tiefere Einblicke vorgesehen.
## <a name="azure-dashboards"></a>Azure-Dashboards
[Azure-Dashboards](../azure-portal/azure-portal-dashboards.md) sind die primäre Dashboardtechnologie für Azure. Sie sind besonders nützlich zur Bereitstellung einer zentralen Konsole für Ihre Azure-Infrastruktur und Dienste, sodass Sie wichtige Probleme schnell identifizieren können.
Im Folgenden finden Sie eine Videoanleitung zum Erstellen von Dashboards.
> [!VIDEO https://www.microsoft.com/en-us/videoplayer/embed/RE4AslH]
### <a name="advantages"></a>Vorteile
- Enge Integration in Azure. Visualisierungen von mehreren Azure-Seiten (einschließlich [Metrik-Explorer](essentials/metrics-charts.md), [Log Analytics](logs/log-analytics-overview.md) und [Application Insights](app/app-insights-overview.md)) können an Dashboards angeheftet werden.
- Sowohl Metriken als auch Protokolle werden unterstützt.
- Daten aus mehreren Quellen (einschließlich der Ausgabe des [Metrik-Explorers](essentials/metrics-charts.md)) können mit [Protokollabfragen](logs/log-query-overview.md), [Karten](app/app-map.md) und Verfügbarkeit in [Application Insights](app/app-insights-overview.md) kombiniert werden.
- Option für persönliche oder freigegebene Dashboards. Integriert in [Azure RBAC (Role-Based Access Control, rollenbasierte Zugriffssteuerung in Azure)](../role-based-access-control/overview.md).
- Automatische Aktualisierung. Metriken werden abhängig vom Zeitbereich mindestens alle fünf Minuten aktualisiert. Protokolle werden stündlich aktualisiert, können mit einer Option für die manuelle Aktualisierung bei Bedarf aktualisiert werden (durch Klicken auf das Symbol „Aktualisieren“ für eine bestimmte Visualisierung) oder werden durch eine Aktualisierung des gesamten Dashboards aktualisiert.
- Dashboards mit parametrisierten Metriken mit Zeitstempel und benutzerdefinierten Parametern.
- Flexible Layoutoptionen.
- Vollbildmodus.
### <a name="limitations"></a>Einschränkungen
- Eingeschränkte Kontrolle über Protokollvisualisierungen ohne Unterstützung für Datentabellen. Die Gesamtanzahl von Datenreihen ist auf 50 begrenzt, wobei weitere Datenreihen unter einem _anderen_ Bucket gruppiert sind.
- Benutzerdefinierte Parameter für Protokolldiagramme werden nicht unterstützt.
- Protokolldiagramme sind auf die letzten 30 Tage beschränkt.
- Protokolldiagramme können nur in freigegebenen Dashboards angeheftet werden.
- Keine Interaktivität mit Dashboarddaten.
- Eingeschränkte kontextbezogene Anzeige von Detailinformationen.
## <a name="power-bi"></a>Power BI
[Power BI](https://powerbi.microsoft.com/documentation/powerbi-service-get-started/) ist besonders nützlich zum Erstellen von geschäftskritischen Dashboards und Berichten sowie Berichten, die langfristige KPI-Trends analysieren. Sie können [die Ergebnisse einer Protokollabfrage in ein Power BI-Dataset importieren](visualize/powerbi.md), damit Sie dessen Features wie das Kombinieren von Daten aus verschiedenen Quellen und das Freigeben von Berichten im Web und auf mobilen Geräten nutzen können.
### <a name="advantages"></a>Vorteile
- Umfassende Visualisierungen.
- Umfassende Interaktivität einschließlich Zoomen und Kreuzfilterung.
- Mühelose Freigabe in Ihrer gesamten Organisation.
- Integration in andere Daten aus mehreren Datenquellen.
- Bessere Leistung mit Ergebnissen, die in einem Cube zwischengespeichert werden.
### <a name="limitations"></a>Einschränkungen
- Unterstützt Protokolle, jedoch keine Metriken.
- Keine Azure-Integration. Dashboards und Modelle können nicht über Azure Resource Manager verwaltet werden.
- Abfrageergebnisse müssen zum Konfigurieren in ein Power BI-Modell importiert werden. Einschränkung der Ergebnisgröße und Aktualisierung.
- Einschränkung der Datenaktualisierung auf acht Mal pro Tag.
## <a name="grafana"></a>Grafana
[Grafana](https://grafana.com/) ist eine offene Plattform, die für operationale Dashboards ideal ist. Sie ist besonders nützlich zum Erkennen, Isolieren und Selektieren von Betriebsincidents. Sie können das [Grafana Azure Monitor-Datenquellen-Plug-in](visualize/grafana-plugin.md) Ihrem Azure-Abonnement hinzufügen, damit es Ihre Azure-Metrikdaten visualisiert.
### <a name="advantages"></a>Vorteile
- Umfassende Visualisierungen.
- Umfangreiches Datenquellenökosystem.
- Dateninteraktivität inklusive Zoomen.
- Unterstützt Parameter.
### <a name="limitations"></a>Einschränkungen
- Keine Azure-Integration. Dashboards und Modelle können nicht über Azure Resource Manager verwaltet werden.
- Kosten zur Unterstützung zusätzlicher Grafana-Infrastruktur oder zusätzliche Kosten für Grafana-Cloud.
## <a name="build-your-own-custom-application"></a>Erstellen Sie Ihre eigene benutzerdefinierte Anwendung
Sie können auf Protokoll- und Metrikdaten in Azure Monitor mit einem beliebigen REST-Client über die zugehörige API zugreifen, sodass Sie Ihre eigenen benutzerdefinierten Websites und Anwendungen erstellen können.
### <a name="advantages"></a>Vorteile
- Vollständige Flexibilität bei Benutzeroberfläche, Visualisierung, Interaktivität und Funktionen.
- Kombinieren von Metriken und Protokolldaten mit anderen Datenquellen.
### <a name="disadvantages"></a>Nachteile
- Großer Entwicklungsaufwand erforderlich.
## <a name="azure-monitor-views"></a>Azure Monitor-Ansichten
> [!IMPORTANT]
> Ansichten werden zurzeit ausgesondert. Anleitungen zum Umwandeln von Ansichten in Arbeitsmappen finden Sie im [Handbuch für den Übergang vom Azure Monitor-Ansicht-Designer zu Arbeitsmappen](visualize/view-designer-conversion-overview.md).
Mit [Ansichten in Azure Monitor](visualize/view-designer.md) erstellen Sie benutzerdefinierte Visualisierungen mit Protokolldaten. Sie werden von [Überwachungslösungen](insights/solutions.md) zur Präsentation der Daten verwendet, die sie sammeln.
### <a name="advantages"></a>Vorteile
- Umfangreiche Visualisierungen für die Protokolldaten.
- Exportieren und Importieren von Ansichten, um sie in andere Ressourcengruppen und Abonnements zu übertragen.
- Integriert in das Azure Monitor-Verwaltungsmodell mit Arbeitsbereichen und Überwachungslösungen.
- [Filtern](visualize/view-designer-filters.md) nach benutzerdefinierten Parametern.
- Interaktiv, unterstützt Drill-In (Sicht, die Detailinformationen einer anderen Ansicht zeigt) mit mehreren Ebenen.
### <a name="limitations"></a>Einschränkungen
- Unterstützt Protokolle, jedoch keine Metriken.
- Keine persönlichen Ansichten. Für alle Benutzer mit Zugriff auf den Arbeitsbereich verfügbar.
- Keine automatische Aktualisierung.
- Begrenzte Layoutoptionen.
- Keine Unterstützung von Abfragen über mehrere Arbeitsbereiche oder Application Insights-Anwendungen hinweg.
- Die Antwortgröße für Abfragen ist auf 8MB und die Abfrageausführungszeit auf 110 Sekunden beschränkt.
## <a name="next-steps"></a>Nächste Schritte
- Weitere Informationen zum [Sammeln von Daten in Azure Monitor](data-platform.md).
- Weitere Informationen zum [Erstellen und Freigeben von Dashboards im Azure-Portal](../azure-portal/azure-portal-dashboards.md).
- [Weitere Informationen zum Metrik-Explorer](essentials/metrics-getting-started.md)
- Weitere Informationen zu [Arbeitsmappen](./visualize/workbooks-overview.md).
- Weitere Informationen zum [Importieren von Log Analytics-Daten in Power BI](./visualize/powerbi.md).
- Weitere Informationen zum [Überwachen Ihrer Azure-Dienste in Grafana](./visualize/grafana-plugin.md).
- Weitere Informationen zum [Erstellen benutzerdefinierter Ansichten mithilfe des Ansicht-Designers in Log Analytics](visualize/view-designer.md).
| 70.418919 | 498 | 0.821435 | deu_Latn | 0.994443 |
ed16aac7658d0a4b4fc7440dcf4c54f544ae3640 | 4,681 | md | Markdown | README.md | JackieZzh/tianshi | b72daf3f71ae580a4982301465db588ea2ef32f4 | [
"Apache-2.0"
] | null | null | null | README.md | JackieZzh/tianshi | b72daf3f71ae580a4982301465db588ea2ef32f4 | [
"Apache-2.0"
] | null | null | null | README.md | JackieZzh/tianshi | b72daf3f71ae580a4982301465db588ea2ef32f4 | [
"Apache-2.0"
] | null | null | null | <<<<<<< HEAD
# 微信小程序商城
微信小程序商城，微信小程序微店，长期维护版本，欢迎大家踊跃提交贡献代码；
使用说明和常见问题，可参阅下面的说明，如还有疑问，可访问工厂官网 [https://www.it120.cc/](https://www.it120.cc/) 寻求帮助！
## 扫码体验
<p>
<img src="https://cdn.it120.cc/apifactory/2017/09/15/487409738ebb80c44eda01c46d59b20c.jpg" width="200px">
</p>
## 其他开源模板
### TianguoguoXiaopu
<p>
<img src="https://cdn.it120.cc/apifactory/2018/04/01/b7b8f5a0fcfc72454ade8510ab929717.jpg" width="200px">
</p>
[Github地址](https://github.com/qindiandadudu/TianguoguoXiaopu)
## 接口 & 后台声明
本项目为小程序商城纯前端项目，由于人力和精力所限，本项目并未有开发配套的后台系统，而是直接使用了 [api 工厂](https://www.it120.cc/) 提供的免费接口和后台，可以完全满足本项目的所有功能需求。
- [接口 SDK](https://github.com/gooking/wxapi)
- [免费后台](https://www.it120.cc/user)
- [WeUI](https://github.com/Tencent/weui-wxss/)
## 关于分类页面
感谢 @yrx0910 编写并提交了分类页面；
不过新增的分类页面视觉美观度上稍欠缺，所以，项目模块并未开启分类页面；
期待后面可以有朋友协助美化~
如果您先体验分类页面，可以在 app.json 中放开分类底部菜单的入口:
```java
{
"pagePath": "pages/category/category",
"iconPath": "images/nav/ic_catefory_normal.png",
"selectedIconPath": "images/nav/ic_catefory_pressed.png",
"text": "分类"
}
```
## 使用说明
1、申请后台账号/获取专属域名
2、开通商城模块
<img src="https://cdn.it120.cc/apifactory/2018/11/14/b61fe6ffb2460f7e4554758b394814f5.png">
3、修改根目录下 config.js 文件
```javascript
module.exports = {
version: "5.0",
note: "优化接口调用流程",
subDomain: "tz", // 如果你的域名是： https://api.it120.cc/abcd 那么这里只要填写 abcd
appid: "wxa46b09d413fbcaff", // 您的小程序的appid，购物单功能需要使用
shareProfile: "百款精品商品，总有一款适合您" // 首页转发的时候话术
};
/*
根据自己需要修改下单时候的模板消息内容设置，可增加关闭订单、收货时候模板消息提醒；
1、/pages/to-pay-order/index.js 中已添加关闭订单、商家发货后提醒消费者；
2、/pages/order-details/index.js 中已添加用户确认收货后提供用户参与评价；评价后提醒消费者好评奖励积分已到账；
3、请自行修改上面几处的模板消息ID，参数为您自己的变量设置即可。
*/
```
4、[设置小程序合法服务器域名](https://www.it120.cc/info/faq/10469)
5、重启您的小程序开发工具，完成
6、如何在后台管理小程序启动图和首页头部的轮播 banner 图片
```javascript
这两个功能都是使用后台 “系统设置” --> “banner” 管理功能来实现的；
后台发布banner的时候，自定义类型请分别填写 app 和 index；
小程序会自动读取类型为 app 的banner图片作为启动展示图片；
小程序会自动读取类型为 new 的banner图片作为首页分类下的轮播图；
```
## 常见问题
- [如何修改小程序商城的标题？](https://www.it120.cc/info/wechat-app-mall/10478)
- “无法登录” / Token 无效 ？
1. config.js 里面的 subDomain 改成你自己的，保存；
2. 登录你的小程序后台（MP 那个地址），Request 域名处增加 api.it120.cc
3. 确保小程序后台（MP 那个地址） 的 appid，工厂后台填写的 appid ，开发工具右上角 “项目详情” 打开后显示的 appid ，这 3 个 appid 是一模一样的；
4. 开发工具上点击 “清除缓存” —> “编译”
- 登录后台发布您自己的商品
- [如何给 Banner 增加链接，点击打开某个商品？](https://www.it120.cc/info/wechat-app-mall/10477)
- 工厂后台设置 appid、secret、微信支付商户号和秘钥时候的 token 怎么填？
**不要填！**
**不要填！**
**不要填！**
**重要的事情说三遍，这个小程序用不到，是给服务号使用的，所以大家空着不要填**
- 微信支付时候，提示 50000 错误，不能获取到预支付 id
> 这个错误是无法获取到微信支付的预支付信息
- 可能是你没有在后台配置您的微信支付商户号和秘钥，或者配置错误
- 可能是你配置的微信支付不是当前小程序申请的（微信支付目前无法跨小程序调用）
- 确保微信开发工具上面登录的 APPID 和你在后台配置的 APPID 是同一个
- 能否帮我免费添加功能？
可以！
<img src="https://cdn.it120.cc/apifactory/2017/07/29/18ae9b8aaedcd747fc5f1c3fa8bc0fe4.png" width="300px">
1. 点击页面顶部的 Star ，关注后，项目有最新动态 github 会提醒您，不错过重要更新；
2. 点击页面顶部的 Fork， 将您需要增加的功能完成 小程序 端界面的调整，然后在 github 上请求将您的代码合并到 EastWorld；
3. 您的代码合并请求审核通过后，我们将会为您完善配套的后台功能；
4. 开源项目离不开您的支持和代码共享，我们一起把 EastWorld 项目长期维护下去；
- 下单的时候没有地方填写收货地址？
1. 添加一个“物流模板”，只有需要快递的商品才会提示用户填写收货地址
2. 发布商品的时候，选择刚才添加的“物流模板”
3. 重新下单，将会需要用户输入收货地址
- 后台设置 appid 和 secret 的时候提示不正确？
1. 请确认您填写的 appid 和 secret 是否正确
2. 输入的时候确保没有空格（复制的时候可能会多复制了空格）
3. 在微信后台设置服务器 IP 地址白名单（106.14.43.122）
- 如何使用退款功能？
1. 后台支持针对订单指定退款多少金额；
2. 可选择退款至用户可用余额或者按照用户支付原路退还第三方或者银行卡；
3. 如果选用原路退还，需要在商户号和秘钥设置的地方上传您的微信支付证书文件（PK12 格式文件）
- 如何设置满多少包邮？
1. 后台系统设置 -- 系统参数，增加系统参数；
2. 参数名 free_shipping_for_purchases （注意不要有空格）
3. 参数值填写您希望的买满金额即可
- 如何修改或者关闭订单超过 30 分钟未付款自动关闭？
1. 创建订单接口增加 expireMinutes 参数；
2. 代表多少分钟未支付自动关闭本订单，传 0 不自动关闭订单；
- [更多问题？](https://www.it120.cc/info/all)
## 如何升级到最新版
- 小程序程序的修改和您后台的数据是独立的，所以不用担心您会丢失数据
- 先把你开发工具下的现有版本程序备份
- 下载最新版的程序，直接覆盖您本地的程序
- 用开发工具修改域名 mall 为你自己的域名
- 开发工具里面上传代码提交微信审核
- 审核通过后，小程序后台去发布新版本即可
- 用户无需重新扫码，关闭小程序重新打开就是新版本了
=======
# jackiestest
#### 介绍
{**以下是码云平台说明，您可以替换此简介**
码云是开源中国推出的基于 Git 的代码托管平台（同时支持 SVN）。专为开发者提供稳定、高效、安全的云端软件开发协作平台
无论是个人、团队、或是企业，都能够用码云实现代码托管、项目管理、协作开发。企业项目请看 [https://gitee.com/enterprises](https://gitee.com/enterprises)}
#### 软件架构
软件架构说明
#### 安装教程
1. xxxx
2. xxxx
3. xxxx
#### 使用说明
1. xxxx
2. xxxx
3. xxxx
#### 参与贡献
1. Fork 本仓库
2. 新建 Feat_xxx 分支
3. 提交代码
4. 新建 Pull Request
#### 码云特技
1. 使用 Readme\_XXX.md 来支持不同的语言，例如 Readme\_en.md, Readme\_zh.md
2. 码云官方博客 [blog.gitee.com](https://blog.gitee.com)
3. 你可以 [https://gitee.com/explore](https://gitee.com/explore) 这个地址来了解码云上的优秀开源项目
4. [GVP](https://gitee.com/gvp) 全称是码云最有价值开源项目，是码云综合评定出的优秀开源项目
5. 码云官方提供的使用手册 [https://gitee.com/help](https://gitee.com/help)
6. 码云封面人物是一档用来展示码云会员风采的栏目 [https://gitee.com/gitee-stars/](https://gitee.com/gitee-stars/)
>>>>>>> b6f0d41389b61c82d2de646477dbc1897700789b
| 21.571429 | 109 | 0.734031 | yue_Hant | 0.748025 |
ed1716874c551390a74636236260c6625a04ed87 | 497 | md | Markdown | docs/SECURITY.md | SLey3/Python-Image-and-Video-Tools | 2748ef824851b3b6e38c0b02eec46638d372cdc3 | [
"Apache-2.0"
] | 1 | 2020-09-05T17:38:36.000Z | 2020-09-05T17:38:36.000Z | docs/SECURITY.md | SLey3/Python-Image-and-Video-Tools | 2748ef824851b3b6e38c0b02eec46638d372cdc3 | [
"Apache-2.0"
] | 2 | 2020-09-03T19:45:21.000Z | 2020-09-19T18:10:12.000Z | docs/SECURITY.md | SLey3/Python-Image-and-Video-Tools | 2748ef824851b3b6e38c0b02eec46638d372cdc3 | [
"Apache-2.0"
] | 1 | 2020-09-03T18:56:17.000Z | 2020-09-03T18:56:17.000Z | # Security Policy
## Supported Versions
Use this section to tell people about which versions of your project are
currently being supported with security updates.
| Version | Supported |
| ------- | ------------------ |
| 1.0.0 | :white_check_mark: |
## Reporting a Vulnerability
**Steps:**
1. Open an Issue at [issues](https://github.com/SLey3/Python-Image-and-Video-Tools/issues)
2. Title your Issue: *SECURITY ISSUE: (insert the filename of where the vulenrability is located)*
| 29.235294 | 98 | 0.688129 | eng_Latn | 0.985269 |
ed1831d67ffaede48f539dbd566a3e7b00729f89 | 2,114 | md | Markdown | _posts/2021-03-12-googleduplex.md | Seungmi122/GoGL3.github.io | 76149561b89414b3bebaaa2fd4bbab35660d37f3 | [
"MIT"
] | null | null | null | _posts/2021-03-12-googleduplex.md | Seungmi122/GoGL3.github.io | 76149561b89414b3bebaaa2fd4bbab35660d37f3 | [
"MIT"
] | null | null | null | _posts/2021-03-12-googleduplex.md | Seungmi122/GoGL3.github.io | 76149561b89414b3bebaaa2fd4bbab35660d37f3 | [
"MIT"
] | null | null | null | ---
title: "[NLP] Google Duplex - 'Jarvis' comes true?"
date: 2021-03-12 10:000 -0400
author : 정여진
categories :
- paper-review
- NLP
tags :
- NLP
- deep-learning
---
You wake up and it's 8:00 a.m. You have to hurry to get to work on time. You get ready, grab some sandwiches, and rush to your car. While driving, you realize that you have a date tonight and need to make a reservation at some fancy restaurant. But remember, you are on a rush and you have no time to make a call. Google Assistant can help you. You can say, "Hey Google, make a reservation for two at 6:00p.m. at Sushi-in." Then Boom! Google Assistant **calls** the restaturant, **generates** human voice and makes a reservation.
Google Duplex is a name for the technology supporting Google Assistant. This service was first introduced in 2018 and has been mainly used in _booking_ with human-like phone calls.
## Technology
Of course, some insanely high quality NLP is used in Duplex. First, the device has to understand what the person is saying even with some background noise (speech-to-text). Next, the context of the complex sentences needs to be analyzed and correct responses need to be generated (natural language understanding). Finally, this response has to be transformed into human-like voice (text-to-speech). Google Duplex trained the models **separately** for each task (one for business appointment, one for reservation etc). Models used are recurrent neural network (RNN) combined with Google’s Automatic Speech Recognition (ASR) technology, parameters of the conversation (e.g., desired time, names), and a text-to-speech (TTS) system.
### Further reading:
- Google AI [blog](https://ai.googleblog.com/2018/05/duplex-ai-system-for-natural-conversation.html)
- Google's natural language understanding [post](https://blog.google/products/search/search-language-understanding-bert/)
### References
- [NLP in the Real World: Google Duplex](https://towardsdatascience.com/nlp-in-the-real-world-google-duplex-d96160d3770b)
| 64.060606 | 730 | 0.760643 | eng_Latn | 0.981362 |
ed186316a21f2bee446f31bbc85ae14b257a481e | 50,049 | md | Markdown | translations/pt-BR/content/site-policy/privacy-policies/github-privacy-statement.md | RahmaNiftaliyev/docs | 4e1ee81587e95617e25aa51c9d761289b193bd37 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2021-10-19T07:53:43.000Z | 2021-10-19T08:09:24.000Z | translations/pt-BR/content/site-policy/privacy-policies/github-privacy-statement.md | RahmaNiftaliyev/docs | 4e1ee81587e95617e25aa51c9d761289b193bd37 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-10-19T17:33:53.000Z | 2021-10-19T17:33:53.000Z | translations/pt-BR/content/site-policy/privacy-policies/github-privacy-statement.md | RahmaNiftaliyev/docs | 4e1ee81587e95617e25aa51c9d761289b193bd37 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Declaração de Privacidade do GitHub
redirect_from:
- /privacy
- /privacy-policy
- /privacy-statement
- /github-privacy-policy
- /articles/github-privacy-policy
- /articles/github-privacy-statement
- /github/site-policy/github-privacy-statement
versions:
fpt: '*'
topics:
- Policy
- Legal
---
Data de vigência: 31 de maio de 2022
Thanks for entrusting GitHub Inc. or GitHub B.V. (“GitHub”, “we”, "us" or "our") with your source code, your projects, and your personal data. This Privacy Statement explains our practices regarding the collection, use, and disclosure of your data, including any personal data we collect and process in connection with our website and any applications, software, products, and services provided by GitHub, including any Beta Previews (collectively “Service”).
Todos os termos em maiúsculas estão definidos nos [Termos de Serviço do GitHub](/github/site-policy/github-terms-of-service), salvo observações em contrário.
## Resumo
Usamos suas informações pessoais conforme descrito nesta Declaração de Privacidade. Não importa onde estiver, onde morar, ou qual for a sua cidadania, fornecemos os mesmos elevados padrões de proteção da privacidade a todos os nossos usuários em todo o mundo, independentemente do seu país de origem ou localização.
To see our Privacy Notice to residents of California, please go to [GitHub's Notice about the California Consumer Privacy Act](#githubs-notice-to-california-residents) or scroll down.
## Sumário
| Seção | Conteúdo |
| --------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Who is responsible for the processing of your information](#who-is-responsible-for-the-processing-of-your-information) | Subject to limited exceptions, GitHub is the controller and entity responsible for the processing of your Personal Data in connection with the Website or Service. |
| [Que tipo de informação o GitHub coleta](#what-information-github-collects) | O GitHub coleta informações diretamente de você para fins de registro, pagamento, transações e perfil de usuário. Também coletamos automaticamente cookies e informações do dispositivo das suas informações de uso, sujeito, quando necessário, ao seu consentimento. GitHub may also collect Personal Data from third parties. We only collect the minimum amount of Personal Data necessary from you, unless you choose to provide more. |
| [Como o GitHub usa suas informações](#how-github-uses-your-information) | In this section, we describe the ways in which we use your information, including to provide you the Service, to communicate with you, for security and compliance purposes, and to improve our Website or Service or develop new features and functionality of our Website or Service. A seção também descreve a base jurídica na qual processamos suas informações quando tal processamento for exigido por lei. |
| [Como compartilhamos as informações obtidas](#how-we-share-the-information-we-collect) | Podemos compartilhar suas informações com terceiros diante de uma das seguintes circunstâncias: com seu consentimento, com nossos prestadores de serviços para fins de segurança, para cumprir as nossas obrigações legais, ou quando houver mudança de controle ou venda de entidades corporativas ou unidades de negócios. Não vendemos suas informações pessoais e não hospedamos anúncios no GitHub. |
| [Your choices regarding our processing of your personal data](#your-choices-regarding-our-processing-of-your-personal-data) | Propomos algumas medidas para você acessar, alterar ou excluir suas informações pessoais. |
| [Cookies](#cookies) | We only use strictly necessary cookies to provide, secure, and improve our Website or Service or develop new features and functionality of our Website or Service. Temos uma página que torna o processo bastante transparente. We do not send any information to third-party analytics services. |
| [Como o GitHub protege suas informações](#how-github-secures-your-information) | We take all measures reasonably necessary to protect the confidentiality, integrity, and availability of your Personal Data on GitHub and to protect the resilience of our servers. |
| [Communication preferences](#communication-preferences) | Nossa comunicação com você ocorrerá por e-mail. É possível controlar os nossos meios de contato com você nas configurações da sua conta. |
| [Resolução de conflitos](#resolving-complaints) | Na hipótese improvável de sermos incapazes de resolver um problema de privacidade de dados de forma rápida e detalhada, indicaremos um caminho para a resolução de litígios. |
| [Mudanças nesta Declaração de Privacidade](#changes-to-our-privacy-statement) | Você receberá notificações sobre mudanças concretas nesta Declaração de Privacidade 30 dias antes de tais mudanças entrarem em vigor. Também é possível acompanhar as mudanças no nosso repositório da Política do Site. |
| [Licença](#license) | Esta Declaração de Privacidade é licenciada sob a [licença Creative Commons Zero](https://creativecommons.org/publicdomain/zero/1.0/). |
| [Contato com a GitHub](#contacting-github) | Entre em contato em caso de dúvidas sobre a nossa Declaração de Privacidade. |
| [Traduções](#translations) | Acesse os links para consultar algumas traduções da Declaração de Privacidade. |
## Declaração de Privacidade do GitHub
## Who is responsible for the processing of your information?
The data controller of your personal data is GitHub, Inc. For individuals outside North America, the data controller is GitHub B.V.
This privacy statement does not apply to personal data we process as a service provider or data processor on behalf of our enterprise customers. Our data processing activities as service processor or data processor is governed by our [Data Protection Agreement](https://github.com/customer-terms/github-data-protection-agreement). If you are a consumer end-user of one of those organizations, you should read that organization’s privacy statement and direct any privacy inquiries to that organization.
## GitHub acting on your behalf
In some cases, GitHub is acting only on your behalf for the personal data we collect and process in connection with our Service (for example, for the Personal Data added to a repository by the contributors to such repository). In such cases, GitHub will only process the data in order to provide the Service requested by you. Please note that subject to our [Private Information Removal Policy](/site-policy/content-removal-policies/github-private-information-removal-policy) contributors’ requests to remove Personal Data generally require notice to and action from the repository owner.
## Que tipo de informação o GitHub coleta
The personal data we collect depends on how you interact with us, the services you use, and the choices you make. We collect information about you from different sources and in various ways when you use our Service, including information you provide directly, information collected automatically, third-party data sources, and data we infer or generate from other data.
### Informações enviadas pelos usuários diretamente ao GitHub
We collect personal data you provide to us. Por exemplo:
#### Informações de registro
We collect information such as your username, email address, and password during account creation.
#### Demographic information
In some cases, we request that you provide age, gender, and similar demographic details.
#### Payment and billing information
If you make a purchase or other financial transaction, we collect credit card numbers, financial account information, and other payment details.
#### Content and files
We collect any photographs, documents, or other files you upload to our Service; and if you send us email messages or other communications, we collect and retain those communications. For example, you may choose to give us more information for your Account profile, such as your full name, an avatar which may include a photograph, your biography, your location, your company, and a URL to a third-party website. Observe que as suas informações de perfil podem ficar visíveis para outros Usuários do nosso Serviço.
### Information GitHub automatically collects.
When you visit or use our Service, we collect some information automatically. Por exemplo:
#### Transaction information
If you have a paid Account with us, or make a purchase or sale using our Service, we automatically collect certain information about your transactions on the Service, such as your full name, address, region, state, country, zip code, the date, time, and amount charged.
#### Informações de uso
If you're accessing or using our Service, we may automatically collect information about how you use the Service, such as the pages you view, the referring site, your IP address and information about your device, session information, the date and time of each request, information contained in or relating to your contributions to individual repositories, and telemetry data (i.e., information about how a specific feature or service is performing) regarding your use of other features and functionality of the Service.
#### Cookies
As further described below, we automatically collect information from cookies (such as cookie ID and settings) in connection with our Service.
#### Informações do dispositivo
We may collect information about your device, such as its IP address, browser or client application information, language preference, operating system and application version, device type and ID, and device model and manufacturer.
#### Geolocation information
In connection with certain features and depending on the functionality of the Service, we collect geolocation information such as through IP addresses or the location information you choose to provide in your Account profile.
### Information we create or generate
We infer new information from other data we collect, including using automated means to generate information about your likely preferences or other characteristics (“inferences”). For example, we infer your general geographic location (such as city, state, and country) based on your IP address.
### Informações coletadas de terceiros
Other companies with whom you choose to engage. GitHub may collect Personal Data about you from third parties. Por exemplo, isso pode acontecer caso você se inscreva em treinamentos ou solicite informações sobre o GitHub via um de nossos fornecedores, parceiros ou afiliados. GitHub does not purchase Personal Data from third-party data brokers.
Service Providers. We may also receive information from processors or service providers who process the data on our behalf, such as our payment processor who process payment and billing information in connection with our Service.
Content you post on our Service. Information you store in, or contribute to, a public repository, provide for use in connection with a Community Feature or make otherwise publicly available through the Service will be collected by GitHub as described in this Privacy Statement. Such information may also be available to the GitHub user community as well as the general public. For more information, please review details regarding public repositories and community features [here](/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/about-your-profile).
Co-branding/marketing partners. We may receive information from partners with which we offer co-branded services or engage in joint marketing activities.
Publicly available sources. We may also obtain information from publicly available sources as GitHub repositories.
When you are asked to provide Personal Data, you may decline. And you may use web browser or operating system controls to prevent certain types of automatic data collection. But if you choose not to provide or allow information that is necessary for certain services or features, those services or features may not be available or fully functional.
## Como o GitHub usa suas informações
We may use your information to provide, administer, analyze, manage, and operate our Service. For example, we use your information for the following purposes:
- Provide our products and deliver our services including troubleshooting, improving, and personalizing the features on the Service.
- Business operations such as billing, accounting, improving our internal operations, securing our systems, detecting fraudulent or illegal activity, and meeting our legal obligations.
- Improve and develop our products and services including to develop new services or features, and conduct research.
- Personalization of our Service by understanding you and your preferences to enhance your experience and enjoyment using our Service.
- Provide customer support and respond to your questions.
- Deliver promotional communications with you about new services, features, offers, promotions, and other information about our Service.
- Send you information, including confirmations, invoices, technical notices, updates, security alerts, support and administrative messages.
We combine data we collect from different sources for these purposes and to give you a more seamless, consistent, and personalized experience.
## Como compartilhamos as informações obtidas
We share Personal Data with your consent or as necessary to complete your transactions or provide the services you have requested or authorized. In addition, we may share each of the categories of your Personal Data described above with the types of third parties described below for the following business purposes:
### Public information
You may select options available through our Service to publicly display and share your name and/or username and certain other information, such as your profile, demographic data, content and files, or geolocation data. For example, if you would like your email address to remain private, even when you’re commenting on public repositories, [you can adjust your setting for your email address to be private in your user profile](https://github.com/settings/emails). You can also [update your local Git configuration to use your private email address](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address). Saiba mais sobre endereços de e-mail em mensagens de commit [aqui](/github/setting-up-and-managing-your-github-user-account/setting-your-commit-email-address).
Please note that if you would like to compile GitHub data, you must comply with our [Terms of Service](/site-policy/github-terms/github-terms-of-service) regarding information usage and privacy, and you may only use any public-facing information you gather for the purpose for which our user authorized it. For example, where a GitHub user has made an email address public-facing for the purpose of identification and attribution, do not use that email address for the purposes of sending unsolicited emails to users or selling personal information, such as to recruiters, headhunters, and job boards, or for commercial advertising. We expect you to reasonably secure information you have gathered from GitHub, and to respond promptly to complaints, removal requests, and "do not contact" requests from GitHub or GitHub users.
### Aplicativos de terceiros
We share your Personal Data with third parties when you tell us to do so. For example, if you purchase an application listed on our Marketplace, we share your username to allow the application developer to provide you with services. Additionally, you may direct us through your actions on GitHub to share your Personal Data. Por exemplo, ao ingressar em uma Organização, você indica que o proprietário da Organização poderá visualizar a sua atividade no log de acesso da Organização.
You can enable or add third-party applications, known as "Developer Products" to your Account. Esses Produtos de Desenvolvedor não são necessários para o uso do GitHub. We will share your Personal Data with such third-party applications when you ask us to; however, you are responsible for your use of the third-party Developer Product and for the amount of Personal Data you choose to share with it. You can check our [API documentation](/rest/reference/users) to see what information is provided when you authenticate into a Developer Product using your GitHub profile.
### Organizations with which you engage
You may indicate, through your actions on GitHub, that you are willing to share your Personal Data. If you collaborate on or become a member of an organization, then its Account owners may receive your Personal Data. When you accept an invitation to an organization, you will be notified of the types of information owners may be able to see (for more information, see [About Organization Membership](/github/setting-up-and-managing-your-github-user-account/about-organization-membership)). Please contact the Account owners for more information about how they might process your Personal Data in their Organization and the ways for you to access, update, alter, or delete your Personal Data stored in the Account.
### Provedores de serviço
We share your Personal Data with service providers who process the information on our behalf to provide or improve our Service. For example, our service providers may perform payment processing, customer support ticketing, network data transmission, security, and other similar services. While GitHub processes all Personal Data in the United States, our service providers may process data outside of the United States or the European Union. Such processing by service providers will be in compliance with applicable law including any relevant transfer mechanism.
### Affiliates We enable access to Personal Data across our subsidiaries, affiliates, and related companies, for example, where we share common data systems or where access is needed to operate and provide the Service.
### Por motivos de segurança
We will disclose Personal Data if we believe it is necessary to:
- protect our customers and others, for example to prevent spam or attempts to commit fraud, or to help prevent the loss of life or serious injury of anyone;
- operate and maintain the security of the Service, including to prevent or stop an attack on our systems or networks; or
- protect the rights or property or ourselves or others, including enforcing our agreements, terms, and policies.
### Para divulgação legal
GitHub may disclose Personal Data or other information we collect about you to law enforcement or other governmental agencies if required in response to a valid legal process. Para obter mais informações sobre a nossa transparência em resposta a solicitações legais, consulte nossas [Diretrizes para Solicitações Legais de Dados do Usuário](/github/site-policy/guidelines-for-legal-requests-of-user-data).
### Mudança de controle ou venda
We may share your Personal Data if we are involved in a merger, sale, or acquisition of corporate entities or business units as described in this Privacy Statement.
Please note that some of the features on our Service include integrations, references, or links to services provided by third parties whose privacy practices differ from ours. If you provide Personal Data to any of those third parties, or allow us to share Personal Data with them, that data is governed by their privacy statements.
Finally, we may share de-identified information in accordance with applicable law.
### No Selling of Personal Data
We *do not* sell your Personal Data for monetary or other consideration as defined under California and Nevada state laws. You can learn more about the CCPA and how we comply with it [here](#githubs-notice-to-california-residents).
## Your choices regarding our processing of your personal data
We provide choices about the Personal Data we collect about you. The choices you make will not apply to any Personal Data associated with an Organization under your Account.
Access, correction, and deletion. If you're a GitHub user, you may access, update, alter, or delete your basic user profile information by [editing your user profile](https://github.com/settings/profile) or contacting [GitHub Support](https://support.github.com/contact) or [GitHub Premium Support](https://enterprise.githubsupport.com/hc/en-us). Você pode controlar as informações que coletamos sobre você ao limitar as informações do seu perfil, manter suas informações atualizadas ou entrar em contato com o [Suporte do GitHub](https://support.github.com/contact) ou o [Suporte Premium do GitHub](https://enterprise.githubsupport.com/hc/en-us).
We retain and use your information as described in this Privacy Statement, but barring legal requirements, we will delete your full profile within 90 days of your request. Alguns dados permanecerão após a exclusão de uma conta, como contribuições em repositórios de outros Usuários e comentários em problemas de outrem. However, we will delete or de-identify your Personal Data, including your username and email address, from the author field of issues, pull requests, and comments by associating them with a ghost user. That said, the email address you have provided via your Git commit settings will always be associated with your commits in the Git system. Se decidir tornar seu endereço de e-mail privado, você também deverá atualizar suas configurações de commit do Git. Não podemos alterar ou excluir dados no histórico de commit do Git; o software Git foi desenvolvido para manter um registro, mas você pode controlar as informações que insere nesse registro.
If GitHub processes Personal Data other than your profile information, such as information about you GitHub receives from [third parties](/github/site-policy/github-privacy-statement#information-we-collect-from-third-parties), then you may, subject to applicable law, access, update, alter, delete, object to or restrict the processing of your Personal Data by contacting [GitHub Support](https://support.github.com/contact) or [GitHub Premium Support](https://enterprise.githubsupport.com/hc/en-us).
You can adjust the settings on your Account regarding the display of your Personal Data in private or public repositories or Personal Data processed in connection with Community Features (such as the GitHub Feed, the GitHub Globe, GitHub Explore, the GitHub Discussion Leaderboard) through [profile settings](https://github.com/settings/profile).
Additionally, if you are unable to access certain Personal Data we have via the means described above, you can request access by contacting us as described at the bottom of this privacy statement.
### Portabilidade de dados
Como usuário do GitHub, você sempre pode levar seus dados com você. You can [clone your repositories to your desktop](/desktop/contributing-to-projects/cloning-a-repository-from-github-to-github-desktop), for example, or you can use our [Data Portability tools](https://developer.github.com/changes/2018-05-24-user-migration-api/) to download information we have about you.
### Communication preferences
We use your email address to communicate with you, if you've said that's okay, and only for the reasons you’ve said that’s okay. Por exemplo, se você comunicar alguma solicitação à nossa equipe de Suporte, responderemos por e-mail. You have control over how your email address is used and shared on and through our Service. You may manage your communication preferences in your [profile](https://github.com/settings/emails).
Pela natureza de seu design, o sistema de controle de versões do Git associa várias ações ao endereço de e-mail do usuário, como mensagens de commit. See more details regarding [setting your commit email address](https://github.com/settings/emails).
Depending on your [email settings](https://github.com/settings/emails), GitHub may occasionally send notification emails, for example, about changes in a repository you’re watching, new features, requests for feedback, important policy changes, or to offer customer support. We may also send marketing emails, based on your choices and in accordance with applicable laws and regulations. Na parte inferior de cada e-mail de marketing que enviamos, há um link de cancelamento do recebimento desse tipo de mensagem.
Observe que você não pode deixar de receber nossas comunicações importantes, como mensagens da nossa equipe de suporte ou mensagens do sistema, mas é possível definir suas configurações de notificação no seu perfil para cancelar o recebimento de outras mensagens.
### European Data Protection Rights
If the processing of Personal Data about you is subject to European Union data protection law, you have certain rights with respect to that data:
You can request access to, and rectification or erasure of, Personal Data; If any automated processing of Personal Data is based on your consent or a contract with you, you have a right to transfer or receive a copy of the Personal Data in a usable and portable format; If the processing of Personal Data is based on your consent, you can withdraw consent at any time for future processing; You can to object to, or obtain a restriction of, the processing of Personal Data under certain circumstances; and For residents of France, you can send us specific instructions regarding the use of your data after your death.
To make such requests, please use the contact information at the bottom of this statement. When we are processing data on behalf of another party (i.e., where GitHub is acting as a data processor) you should direct your request to that party. You also have the right to lodge a complaint with a supervisory authority, but we encourage you to first contact us with any questions or concerns.
We rely on different lawful bases for collecting and processing Personal Data about you, for example, with your consent and/or as necessary to provide the services you use, operate our business, meet our contractual and legal obligations, protect the security of our systems and our customers, or fulfill other legitimate interests.
## Our use of cookies and tracking technologies
### Cookies and tracking technologies
GitHub uses cookies to provide, secure and improve our Service or to develop new features and functionality of our Service. For example, we use them to keep you logged in, remember your preferences, identify your device for security purposes, compile statistical reports, and provide information for future development of GitHub. We use our own cookies and do not use any third-party service providers in this context. If you disable your browser or device’s ability to accept these cookies, you will not be able to log in or use our Service. Fornecemos mais informações sobre [cookies no GitHub](/github/site-policy/github-subprocessors-and-cookies#cookies-on-github) na nossa página [Subprocessadores e Cookies do GitHub](/github/site-policy/github-subprocessors-and-cookies) que descreve os cookies que definimos, a necessidade que temos para esses cookies e a expiração desses cookies.
Our emails to users may contain a pixel tag, which is a small, clear image that can tell us whether or not you have opened an email and what your IP address is. We use this pixel tag to make our email communications more effective and to make sure we are not sending you unwanted email.
### DNT
"[Não rastrear](https://www.eff.org/issues/do-not-track)" (DNT) é uma preferência de privacidade que você pode definir no seu navegador se não quiser que os serviços on-line coletem e compartilhem certos tipos de informações sobre a sua atividade on-line de serviços de rastreamento de terceiros. O GitHub responde aos sinais de DNT dos navegadores e segue o [padrão do W3C de resposta aos sinais de DNT](https://www.w3.org/TR/tracking-dnt/). Se você deseja configurar seu navegador para sinalizar que não gostaria de ser rastreado, verifique a documentação do seu navegador para saber como habilitar essa sinalização. Há também bons aplicativos que bloqueiam o rastreamento on-line, como [Badger de Privacidade](https://privacybadger.org/).
## Retention of Personal Data
We retain Personal Data for as long as necessary to provide the services and fulfill the transactions you have requested, comply with our legal obligations, resolve disputes, enforce our agreements, and other legitimate and lawful business purposes. Because these needs can vary for different data types in the context of different services, actual retention periods can vary significantly based on criteria such as user expectations or consent, the sensitivity of the data, the availability of automated controls that enable users to delete data, and our legal or contractual obligations. For example, we may retain your Personal Data for longer periods, where necessary, subject to applicable law, for security purposes.
## Como o GitHub protege suas informações
GitHub takes reasonable measures necessary to protect your Personal Data from unauthorized access, alteration, or destruction; maintain data accuracy; and help ensure the appropriate use of your Personal Data. To help us protect personal data, we request that you use a strong password and never share your password with anyone or use the same password with other sites or accounts.
In addition, if your account has private repositories, you control the access to that Content. GitHub personnel does not access private repository content except for
- security purposes,
- automated scanning for known vulnerabilities, active malware, or other content known to violate our Terms of Service
- para auxiliar o proprietário do repositório com uma questão de suporte
- para manter a integridade do Serviço
- to comply with our legal obligations if we have reason to believe the contents are in violation of the law,
- or with your consent.
Github will provide notice regarding private repository access where not prohibited by law or if in response to a security threat or other risk to security.
### Transferência internacional de dados
GitHub processes Personal Data both inside and outside of the United States and relies on legal mechanisms such as Standard Contractual Clauses to lawfully transfer data from the European Economic Area, the United Kingdom, and Switzerland to the United States. You may request a copy of the Standard Contractual Clauses using the contact details provided in the section entitled “Contacting GitHub” below.
### Resolução de conflitos
If you have concerns about the way GitHub is handling your Personal Data, please let us know immediately. Estamos à sua disposição para ajudar no que for necessário. Entre em contato conosco preenchendo o [formulário de contato de Privacidade](https://support.github.com/contact/privacy). You may also email us directly at **(privacy [at] github [dot] com)** with the subject line "Privacy Concerns." Responderemos sua solicitação o quanto antes, no máximo em 45 dias.
Você também pode entrar em contato diretamente com o nosso Departamento de Proteção de Dados.
| Sede nos Estados Unidos | Filial na UE |
| ------------------------------------------- | --------------------------------- |
| Departamento de Proteção de dados do GitHub | GitHub BV |
| 88 Colin P. Kelly Jr. St. | Vijzelstraat 68-72 |
| San Francisco, CA 94107 | 1017 HL Amsterdam |
| Estados Unidos | Holanda |
| **privacy [at] github [dot] com** | **privacy [at] github [dot] com** |
### Processo de resolução de conflitos
No caso improvável de conflito entre você e o GitHub sobre a manipulação das suas Informações Pessoais de Usuário, não mediremos esforços para resolver a situação. Além disso, se você for residente de um estado-membro da UE, você tem o direito de apresentar uma reclamação junto às suas autoridades locais de supervisão, e poderá ter mais [opções](/github/site-policy/global-privacy-practices#dispute-resolution-process).
## Mudanças nesta Declaração de Privacidade
Embora grande parte das alterações sejam secundárias, o GitHub pode alterar esta Declaração de Privacidade ocasionalmente. Publicaremos uma notificação para os usuários no site sobre mudanças concretas feitas nesta Declaração de Privacidade pelo menos 30 dias antes de sua entrada em vigor. A notificação será exibida em nossa página inicial ou enviada por e-mail para o endereço de e-mail principal especificado na sua conta do GitHub. Também atualizaremos nosso [repositório da Política do Site](https://github.com/github/site-policy/), que registra e monitora todas as alterações feitas a esta política. Para outras mudanças nesta Declaração de Privacidade, incentivamos os usuários a [observar](/github/managing-subscriptions-and-notifications-on-github/configuring-notifications#configuring-your-watch-settings-for-an-individual-repository) ou verificar o nosso repositório de Política de Site com frequência.
## Licença
Esta Declaração de Privacidade é licenciada sob a [licença Creative Commons Zero](https://creativecommons.org/publicdomain/zero/1.0/). Para ver os detalhes, consulte nosso [repositório da Política do Site](https://github.com/github/site-policy#license).
## Contato com a GitHub
Envie suas perguntas sobre nossas práticas de coleta de informações ou a Declaração de Privacidade do GitHub pelo [formulário de contato de Privacidade](https://support.github.com/contact/privacy).
## Traduções
Consulte abaixo este documento traduzido para outros idiomas. Em caso de conflito, incerteza ou aparente incoerência entre quaisquer versões traduzidas e a versão original em inglês, o documento em inglês prevalecerá.
### French
Cliquez ici pour obtenir la version française: [Déclaration de confidentialité de GitHub](/assets/images/help/site-policy/github-privacy-statement(07.22.20)(FR).pdf)
### Outras traduções
Para traduções desta declaração para outros idiomas, acesse [https://docs.github.com/](/) e selecione um idioma no menu suspenso abaixo de "Inglês".
## GitHub's notice to California residents
A [Lei de Privacidade do Consumidor da Califórnia](https://leginfo.legislature.ca.gov/faces/billCompareClient.xhtml?bill_id=201720180AB375) de 2018, (Cal. Civ. Código §1798.100 et seq., conforme alterado, "CCPA") dá aos residentes da Califórnia direitos e controle sobre suas informações pessoais. GitHub, Inc. ("GitHub", "nós") fornece esta declaração aos residentes ("você") de acordo com os requisitos da CCPA para fazer certas divulgações sobre a coleta e o processamento de suas informações pessoais. Esta é a descrição específica do GitHub dos direitos de privacidade dos consumidores para a Califórnia, sob a CCPA. Para obter informações sobre como estendemos os direitos fundamentais da CCPA para controle de informações pessoais a todos os nossos usuários nos Estados Unidos, consulte nossa [Declaração de Privacidade](/github/site-policy/github-privacy-statement).
### Our handling of personal information
While the table below contains information about the categories of personal information we collect, process, and share, please see the [GitHub Privacy Statement](/github/site-policy/github-privacy-statement) for full details.
| Categoria de informações pessoais coletadas nos últimos 12 meses | Categoria de fontes das quais as informações pessoais foram coletadas |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Identificadores (como nome real, pseudônimo, endereço postal, identificador pessoal exclusivo, endereço do Protocolo da Internet do identificador on-line, endereço de e-mail, nome da conta ou outros identificadores semelhantes) | Information consumer provides directly or automatically through their interaction with our Service and/or Website or GitHub’s vendors, partners, or affiliates |
| Personal information described in Cal. Civ. Code §1798.80 (e) such as name, address, credit card or debit card number) | Information consumer may choose to provide directly, through service providers |
| Characteristics of protected classifications under California or federal law (such as gender) | Informações que o consumidor pode optar por fornecer diretamente |
| Informações comerciais (tais como informações sobre produtos ou serviços comprados, obtidos ou tomados, ou outros históricos ou tendências de compra ou consumo) | Informação que o consumidor fornece direta ou automaticamente através da interação com os nossos Serviços |
| Geolocation data (such as any information collected after giving users the opportunity to opt-in to location-based services, which rely upon a device’s precise location services. ) | Information consumer provides automatically through their interaction with our Services |
| Audio, electronic, visual, or similar information such as content and files uploaded to the Service. | Informações que o consumidor pode optar por fornecer diretamente |
| Professional or employment information | Informações que o consumidor pode optar por fornecer diretamente |
| Inferences drawn from any of the information identified in this table to create a profile about a consumer reflecting the consumer’s preferences | Informação que o consumidor fornece direta ou automaticamente através da interação com os nossos Serviços |
We use the categories of personal information described above for the purposes listed in the [“How GitHub uses your information”](/github/site-policy/github-privacy-statement#how-github-uses-your-information) section of our Privacy Statement. We also disclose the categories of personal information listed above for business purposes. Please see the [“How we share the information we collect”](/github/site-policy/github-privacy-statement#how-we-share-the-information-we-collect) section of our Privacy Statement for additional details.
### Não vendemos suas informações pessoais
De acordo com a CCPA, um negócio que consiste na venda de informações pessoais de residentes da Califórnia para outros: 1) deve avisar os residentes da Califórnia antes de vender suas informações pessoais para outros; e 2) deve fornecer o direito de opt-out (autoexclusão) pela venda de suas informações pessoais. GitHub does not sell personal information, including personal information of anyone under 16 years old.
### Seus direitos sob a CCPA
A CCPA fornece aos residentes da Califórnia certos direitos relacionados às suas informações pessoais. Para enviar uma solicitação com base nesses direitos, entre em contato conosco por meio do nosso [formulário de contato](https://support.github.com/contact?tags=docs-policy).
Ao receber uma solicitação, verificaremos se o indivíduo que fez a solicitação é o residente a quem pertencem as informações pessoais sujeitas à solicitação. California residents may exercise their rights themselves or may use an authorized agent, designated in writing or through a power of attorney, to make requests on their behalf. If you use an authorized agent to submit a request, we may require that you provide us additional information demonstrating that the agent is acting on your behalf, and we may need you to verify your identity directly with us. With respect to your personal information, California residents may exercise the rights described below.
#### Right to Know.
You have a right to request that we disclose to you the personal information we have collected about you. You also have a right to request additional information about our collection, use, disclosure, or sale of such personal information. Note that we have provided much of this information in this privacy statement. You can use GitHub’s User Migration API to access and download your data. Learn more here. You may also make such a “request to know” by contacting us here.
#### Right to Request Deletion.
You also have a right to request that we delete personal information under certain circumstances, subject to a number of exceptions. To make a request to delete, You can use GitHub’s User Migration API to access and download your data. Learn more here. You may also make such a “request to delete” by contacting us here.
#### Right to Opt-Out.
You have a right to opt-out from future “sales” of personal information. Note that we do not “sell” personal information as defined by the CCPA and have not done so in the past 12 months.
#### Right to Non-Discrimination.
You have a right to not be discriminated against for exercising your CCPA rights. We will not discriminate against you for exercising your CCPA rights.
You may designate, in writing or through a power of attorney, an authorized agent to make requests on your behalf to exercise your rights under the CCPA. Before accepting such a request from an agent, we will require the agent to provide proof you have authorized it to act on your behalf, and we may need you to verify your identity directly with us. Further, to provide or delete specific pieces of personal information we will need to verify your identity to the degree of certainty required by law. We will verify your request by asking you to submit the request from the email address associated with your account or requiring you to provide information necessary to verify your account. [Please note that you may use two-factor authentication with your GitHub account.](/authentication/securing-your-account-with-two-factor-authentication-2fa/accessing-github-using-two-factor-authentication)
Finally, you have a right to receive notice of our practices at or before collection of personal information.
Additionally, under California Civil Code section 1798.83, also known as the “Shine the Light” law, California residents who have provided personal information to a business with which the individual has established a business relationship for personal, family, or household purposes (“California Customers”) may request information about whether the business has disclosed personal information to any third parties for the third parties’ direct marketing purposes. Please be aware that we do not disclose personal information to any third parties for their direct marketing purposes as defined by this law. California Customers may request further information about our compliance with this law by emailing **(privacy [at] github [dot] com)**. Please note that businesses are required to respond to one request per California Customer each year and may not be required to respond to requests made by means other than through the designated email address.
California residents under the age of 18 who are registered users of online sites, services, or applications have a right under California Business and Professions Code Section 22581 to remove, or request and obtain removal of, content or information they have publicly posted. To remove content or information you have publicly posted, [please submit a Private Information Removal request](https://support.github.com/contact/private-information). Alternatively, to request that we remove such content or information, please send a detailed description of the specific content or information you wish to have removed to [GitHub support](https://support.github.com/contact). Please be aware that your request does not guarantee complete or comprehensive removal of content or information posted online and that the law may not permit or require removal in certain circumstances. If you have any questions about our privacy practices with respect to California residents, please contact us via our [contact form](https://support.github.com/contact?tags=docs-policy).
| 154.950464 | 1,064 | 0.697357 | eng_Latn | 0.944518 |
ed18941df676736ac6b45aed4a823cf9caa5a031 | 2,515 | md | Markdown | docs/windows/how-to-change-the-language-or-condition-of-a-resource-while-copying.md | FlorianHaupt/cpp-docs.de-de | 0ccd351cf627f1a41b14514c746f729b778d87e3 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/windows/how-to-change-the-language-or-condition-of-a-resource-while-copying.md | FlorianHaupt/cpp-docs.de-de | 0ccd351cf627f1a41b14514c746f729b778d87e3 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/windows/how-to-change-the-language-or-condition-of-a-resource-while-copying.md | FlorianHaupt/cpp-docs.de-de | 0ccd351cf627f1a41b14514c746f729b778d87e3 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: 'Vorgehensweise: Ändern von Sprache oder Bedingung einer Ressource während des Kopiervorgangs (C++)'
ms.date: 11/04/2016
f1_keywords:
- vc.resvw.resource.changing
helpviewer_keywords:
- Language property [C++]
ms.assetid: 8f622ab0-bac2-468f-ae70-78911afc4759
ms.openlocfilehash: 42d8fb36dcbd243b0a99f2dbc597bdf352f47266
ms.sourcegitcommit: 6052185696adca270bc9bdbec45a626dd89cdcdd
ms.translationtype: MT
ms.contentlocale: de-DE
ms.lasthandoff: 10/31/2018
ms.locfileid: "50642519"
---
# <a name="how-to-change-the-language-or-condition-of-a-resource-while-copying-c"></a>Vorgehensweise: Ändern von Sprache oder Bedingung einer Ressource während des Kopiervorgangs (C++)
Beim Kopieren in eine Ressource können Sie ihre Sprachen- und/oder Bedingungseigenschaft ändern.
- Die Ressourcensprache ermittelt lediglich die Sprache für die Ressource. Dies dient der [FindResource](/windows/desktop/api/winbase/nf-winbase-findresourcea) können Sie die Ressource zu identifizieren, für die Sie suchen. (Ressourcen können für jede Sprache Unterschiede aufweisen, die nicht mit dem Text zusammenhängen, z. B. Tastenkombinationen, die nur auf einer japanischen Tastatur funktionieren, oder eine Bitmap, die nur für Builds in Chinesisch gilt usw.)
- Die Bedingung einer Ressource stellt ein definiertes Symbol dar, das eine Bedingung angibt, unter der diese bestimmte Ressourcenkopie zu verwenden ist.
Sprache und Bedingung einer Ressource werden im Arbeitsbereichsfenster nach dem Ressourcennamen in Klammern angezeigt. In diesem Beispiel verwendet die Ressource mit dem Namen „IDD_AboutBox“ Finnisch als Sprache und „XX33“ als Bedingung.
```cpp
IDD_AboutBox (Finnish - XX33)
```
### <a name="to-copy-an-existing-resource-and-change-its-language-or-condition"></a>So kopieren Sie eine vorhandene Ressource und ändern die Sprache oder Bedingung
1. In der RC-Datei oder in der [Ressourcenansicht](../windows/resource-view-window.md) Fenster mit der rechten Maustaste in der Ressource, die Sie kopieren möchten.
2. Wählen Sie **Kopie einfügen** aus dem Kontextmenü.
3. In der **Ressourcenkopie** Dialogfeld:
- Für die **Sprache** Listenfeld, wählen Sie die Sprache.
- In der **Bedingung** geben die Bedingung.
## <a name="requirements"></a>Anforderungen
Win32
## <a name="see-also"></a>Siehe auch
[Vorgehensweise: Kopieren von Ressourcen](../windows/how-to-copy-resources.md)<br/>
[Ressourcendateien](../windows/resource-files-visual-studio.md)<br/>
[Ressourcen-Editor](../windows/resource-editors.md) | 50.3 | 465 | 0.79006 | deu_Latn | 0.984709 |
ed189c6d93bc8ca5854c293ee77a93b1feb3f287 | 6,833 | md | Markdown | _posts/2021-08-25-spotify-now-playing-azure.md | joshspicer/joshspicer.github.io | d5b32cd368b07a14e4b27982a3240b013f6a1873 | [
"Unlicense",
"CC-BY-4.0",
"MIT"
] | 1 | 2020-08-26T07:11:19.000Z | 2020-08-26T07:11:19.000Z | _posts/2021-08-25-spotify-now-playing-azure.md | joshspicer/joshspicer.github.io | d5b32cd368b07a14e4b27982a3240b013f6a1873 | [
"Unlicense",
"CC-BY-4.0",
"MIT"
] | 8 | 2020-07-12T02:32:28.000Z | 2021-09-07T19:48:23.000Z | _posts/2021-08-25-spotify-now-playing-azure.md | joshspicer/joshspicer.github.io | d5b32cd368b07a14e4b27982a3240b013f6a1873 | [
"Unlicense",
"CC-BY-4.0",
"MIT"
] | 14 | 2019-10-15T17:37:50.000Z | 2022-02-06T21:56:44.000Z | ---
layout: post
title: "Spotify \"Now Playing\" v2"
date: 2021-08-25
permalink: spotify-now-playing-azure
tags: spotify azure music
---
<!--  -->
> The most astute readers of this blog would've noticed that for the past couple months, its homepage has been missing its characteristic [Josh is listening to "XXX" on Spotify]({{site.url}}/spotify-now-playing). As the last of my student AWS credits expired, I decided it was time to move this script over to a new home.
## Goal
To show a simple message on the front page of a website/blog/etc (or even on some embedded device like a smart mirror - anything that can send a GET and read some JSON!) with the current song you're listening to on Spotify. If you aren't currently listening, the API will fetch your last listened to song, as reported by the Spotify API.
The end result (on my blog) looks like this:
## Usage
Once deployed - fetching your currently playing music is as easy as making a GET request.
```bash
[~]$ curl https://api.joshspicer.com/api/spotify | jq
{
"artistName": "Bombay Bicycle Club",
"isPlaying": false,
"response": "Josh last listened to Home By Now by Bombay Bicycle Club on spotify.",
"songName": "Home By Now"
}
```
On my website i'm reusing my old [piece of javascript](https://github.com/joshspicer/joshspicer.github.io/blob/master/js/pollLambdaAPI.js#L52) that parses this JSON string and writes the HTML to `<span>` on the front page of my website. Easy!
## AWS Lambda to Azure Functions
For whatever reason (the challenge?), I decided to implement my function in typescript instead of my previous implemention language of python.
The [entrypoint](https://github.com/joshspicer/spotify-now-playing-azure/blob/main/spotify/index.ts#L140-L162) for my Azure function listens for HTTP triggers in (a GET request to my endpoint), and on execution reads in state that I store in a Table.
```typescript
const httpTrigger: AzureFunction = async function (context: Context, req: HttpRequest, cachedAuth: any): Promise<void> {
let accessToken = cachedAuth.Token;
const expiry = new Date(cachedAuth.Expiry)
const now = new Date()
if (expiry <= now) {
accessToken = await refreshToken(context)
}
const nowPlaying: NowPlaying = await getNowPlaying(accessToken, context);
context.res = {
body: JSON.stringify(nowPlaying),
};
};
export default httpTrigger;
```
Since Spotify access tokens last for 1 hour, I cache the token and only refresh it when the expiry i've stored is nearing an hour. In that case, I invoke `refreshToken`, which then creates a service connection to the same database, refreshes my Spotify token, and then places the token in storage (and returns it to the caller)
```typescript
...
// Create table service with azure-storage SDK
var tableSvc = azure.createTableService(storageAccountName, storageKey);
// ~ fetch updated token from Spotify ~ //
var updatedTask = {
PartitionKey: { '_': 'primary' },
RowKey: { '_': 'auth' },
Token: { '_': authPayload.access_token },
// Right before this token will expire
Expiry: {'_': date.minutesFromNow(55) }
};
tableSvc.insertOrReplaceEntity(tableName, updatedTask, function(error, result, response){
if(error
context.res.status = 400;
}
// Success
});
```
You map each argument to the entrypoint **in order** in the [function.json](https://github.com/joshspicer/spotify-now-playing-azure/blob/main/spotify/function.json). As I explain below, you have to pre-create the table (`database` in my case) in your created storage account (which the Azure Function extension will do for you on your first deploy).
```jsonc
{
"bindings": [
{
"authLevel": "anonymous",
"type": "httpTrigger",
"direction": "in",
"name": "req",
"methods": [
"get"
]
},
{
"type": "http",
"direction": "out",
"name": "res"
},
{
"name": "cachedAuth",
"type": "table",
"tableName": "database",
"partitionKey": "primary",
"rowKey": "auth",
"connection": "AzureWebJobsStorage",
"direction": "in"
}
],
"scriptFile": "../dist/spotify/index.js"
}
```
## Setup
The setup for this project is very straightforward, and essentially boils down to collecting the following environment variable. This time around I'm hosting this script on an Azure Function.
The following example outlines the contents of a `local.settings.json`, which you can place untracked in the root of the project repo for local development. You'll also need to upload these to your function's `Configuration` on the Azure portal.
```jsonc
{
"IsEncrypted": false,
"Values": {
"AzureWebJobsStorage": "DefaultEndpointsProtocol=https;AccountName=.....",
"FUNCTIONS_WORKER_RUNTIME": "node",
"StorageKey": "...", // Same key embedded in your AzureWebJobsStorage
"RefreshToken": "...", // From Spotify, see spcr.me/spotify-now-playing
"ClientIdSecret": "...", // From Spotify, see spcr.me/spotify-now-playing
"StorageAccountName": "...", // The generated storage account name when you first deploy your Azure Function via the extension
"TableName": "..." // Manually added table name in the "Tables" section of your storage account
}
}
```
These variables are injected into our function as environment variables, which I then use to authenticate with the Spotify API and with the Azure Storage API.
Do check out my [older guide]({{site.url}}/spotify-now-playing) for how to generate those Spotify secrets.
### Running the code
This project has a [devcontainer](https://github.com/joshspicer/spotify-now-playing-azure/tree/main/.devcontainer), which will automatically launch into a pre-built container when opened in a [Codespace](https://codespace.new) or with the VSCode Remote Containers extension. You'll then have all the necessary VSCode extensions (Azure Functions), required tooling (func), and runtime (node).
### Custom Domains
In the Azure portal I followed the "custom domain" prompts, resulting in me setting `api.joshspicer.com`, as a CNAME for `spotify-now-playing.azurewebsites.net`. Following the guided setup in the portal will also generate you a free SSL certificate.
### Cors
Again in the Azure portal, be sure to modify your CORS settings if any other webpage is going to invoke your API cross-domain. My website `https://joshspicer.com` invokes this domain, so I simply added that entire URI to the cors list, and it instantly worked. This was _so_ much easier to fix than it was on AWS 3+ years ago.
| 39.959064 | 392 | 0.705108 | eng_Latn | 0.978348 |
ed198be3a45b92a67098142d3ba7feb71ec84f01 | 7,092 | md | Markdown | docs/ide/reference/accessibility-tips-and-tricks.md | tommorris/visualstudio-docs.tr-tr | 11f1d23025c44a834e451a92828b7078fdc68a7c | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/ide/reference/accessibility-tips-and-tricks.md | tommorris/visualstudio-docs.tr-tr | 11f1d23025c44a834e451a92828b7078fdc68a7c | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/ide/reference/accessibility-tips-and-tricks.md | tommorris/visualstudio-docs.tr-tr | 11f1d23025c44a834e451a92828b7078fdc68a7c | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Erişilebilirlik ipuçları ve püf noktaları Visual Studio için
description: İpuçları ve Visual Studio tümleşik geliştirme ortamı (IDE) kullanmak, herkes için daha erişilebilir hale gelmesine yardımcı olabilecek öneriler hakkında daha fazla engelli kişiler de dahil olmak üzere öğrenin.
ms.date: 09/15/2017
ms.prod: visual-studio-dev15
ms.technology: vs-ide-general
ms.topic: conceptual
helpviewer_keywords:
- accessibility [Visual Studio]
ms.assetid: 6b491d88-f79e-4686-8841-857624bdcfda
author: TerryGLee
ms.author: tglee
manager: douge
ms.workload:
- multiple
ms.openlocfilehash: 7cff1eb98dd76f8b594193b2e768987b4e2a441d
ms.sourcegitcommit: 58052c29fc61c9a1ca55a64a63a7fdcde34668a4
ms.translationtype: MT
ms.contentlocale: tr-TR
ms.lasthandoff: 06/04/2018
ms.locfileid: "34747462"
---
# <a name="accessibility-tips-and-tricks-for-visual-studio"></a>Erişilebilirlik ipuçları ve püf noktaları Visual Studio için
> [!TIP]
> Son erişilebilirlik güncelleştirmeleri hakkında daha fazla bilgi için bkz: [Visual Studio 2017 sürüm 15.3 erişilebilirlik geliştirmeleri](https://blogs.msdn.microsoft.com/visualstudio/2017/08/14/accessibility-improvements-in-visual-studio-2017-version-15-3/) blog postası.
Visual Studio, ekran okuyucuların ve diğer yardımcı teknolojiler ile uyumlu erişilebilirlik özelliğine sahiptir. Bu konu yalnızca klavye görevleri gerçekleştirmek için kullanabilirsiniz ve görünürlüğünü artırmak için yüksek karşıtlıklı tema kullanma hakkında bilgi içeren ortak kısayol tuş birleşimleri listeler. De ek açıklamaları kodunuzu hakkında yararlı bilgiler ortaya çıkarmak için nasıl kullanılacağını gösterir ve ses ayarlama yapı ve kesme olayları Desteleri.
## <a name="save-your-ide-settings"></a>IDE ayarlarınızı kaydedin
Pencere düzeninizi, klavye kısayol düzenini ve diğer tercihlerinizi kaydederek IDE deneyiminizi özelleştirebilirsiniz. Daha fazla bilgi için bkz: [Visual Studio IDE'yi kişiselleştirme](../../ide/personalizing-the-visual-studio-ide.md).
## <a name="modify-your-ide-for-high-contrast-viewing"></a>Yüksek karşıtlıklı görüntülemek için IDE değiştirme
Bazı çok kişi bazı renkler görmek daha zordur. Daha fazla Karşıtlık, kod olarak istiyor, ancak tipik "Yüksek Karşıtlık" temaları kullanmak istemediğiniz şimdi "Mavi (ek Karşıtlık)" tema sunuyoruz.
## <a name="use-annotations-to-reveal-useful-information-about-your-code"></a>Kodunuzu hakkında yararlı bilgiler ortaya çıkarmak için ek açıklamalarını kullanma
Visual Studio düzenleyicisinde "vb. yer işaretleri, özellikleri ve bir satıra lightbulbs, hata ve uyarı"dalgalı çizgiler", gibi kodunun belirli noktalarda özellikleri hakkında bilmeniz sağlayan birçok metin adornments" içerir. Bulabilir ve bu adornments arasında gezinmek yardımcı olması için ayarlama "Satırı ek açıklamaları Göster" komutunu kullanabilirsiniz.
## <a name="access-toolbars-by-using-shortcut-key-combinations"></a>Kısayol tuş birleşimleri kullanarak erişim araç çubukları
Birçok aracı windows yapmak gibi Visual Studio IDE araç çubukları vardır. Aşağıdaki kısayol tuş birleşimleri bunları erişmenize yardımcı olur.
|Özellik|Açıklama|Tuş bileşimini|
|-------------|-----------------|---------------------|
|IDE araç çubukları|Standart araç çubuğundaki ilk düğmesini seçin.|**ALT**, **CTRL** + **SEKMESİ**|
|Araç penceresi araç çubukları|Araç çubukları araç penceresinde odağı taşır. <br> <br> **Not:** bu çoğu aracı windows için ancak yalnızca odağı araç penceresinde olduğunda çalışır. Ayrıca, ALT tuşu önce SHIFT tuşunu seçmeniz gerekir. Takım Gezgini gibi bazı aracı Windows ALT anahtar seçilmeden önce bir süre için SHIFT tuşuna basılı gerekir.|**SHIFT** + **ALT**|
|Araç Çubukları|Listedeki ilk öğe sonraki araç çubuğunu (araç çubuğu odağa sahip olduğunda) gidin.|**CTRL** + **SEKMESİ**|
### <a name="other-useful-shortcut-key-combinations"></a>Diğer kullanışlı kısayol tuş birleşimleri
Bazı diğer yararlı bir kısayol tuş bileşimlerini arasında şunlar yer alır.
|Özellik|Açıklama|Tuş bileşimini|
|-------------|-----------------|---------------------|
|IDE|Yüksek Karşıtlık kapatabilirsiniz. <br> <br> **Not:** standart Windows kısayolu|**Sol ALT + sol üst karakter + yazdırma EKRANI**|
|İletişim kutusu|İletişim kutusunda onay kutusunu seçeneğinin işaretini kaldırın veya seçin. <br> <br> **Not:** standart Windows kısayolu|**BOŞLUK ÇUBUĞU**|
|Bağlam menüleri|Bir içerik (sağ tıklatma) menüsünü açın. <br> <br> **Not:** standart Windows kısayolu|**SHIFT** + **F10**|
|Menüler|Kısayol tuşlarını kullanarak hızlı bir şekilde bir menü öğesine erişin. Seçin **ALT** menü komutu etkinleştirmek için altı çizili harfler arkasından anahtarı. Örneğin, Visual Studio Proje Aç iletişim kutusu görüntülemek için seçmeniz **ALT** + **F** + **O** + **P**. <br><br> **Not:** standart Windows kısayolu|**ALT** + **[harfi]**|
|Araç penceresi|Araç kutusu sekmeler arasında taşıyın.|**CTRL** + **UPARROW**<br /><br /> and<br /><br /> **CTRL** + **DOWNARROW**|
|Araç penceresi|Bir denetimi, bir form veya tasarımcıya Araç Kutusu'ndan ekleyin.|**GİRİN**|
|Klavye, ortam, Seçenekler iletişim kutusu|Girilen bir tuş bileşimini silme **basın kısayol tuşları** seçeneği.|**GERİ AL**|
> [!NOTE]
> Gördüğünüz iletişim kutuları ve menü komutları, etkin ayarlarınıza ve ürün sürümüne bağlı olarak Yardım menüsünde açıklanana göre farklılık gösterebilir.
## <a name="use-the-sound-applet-to-set-build-and-breakpoint-cues"></a>Ses uygulaması derleme ve kesme noktası yardımlar ayarlamak için kullanın
Visual Studio program olaylarına ses atamak için Windows Ses uygulamasını kullanabilirsiniz. Özellikle, aşağıdaki program olaylarına ses atayabilirsiniz:
* Kesme noktası isabet
* Derleme iptal edildi
* Oluşturma başarısız oldu
* Yapı başarılı oldu
İşte nasıl.
1. İçinde **arama** kutusunu türü olan Windows 10 çalıştıran bir bilgisayarda **değiştirmek sistem sesleri**.
(Alternatif olarak, etkin Cortana varsa, "Hey Cortana" deyin ve "Sistem seslerini Değiştir" komutunu verin.)
2. Çift **değiştirmek sistem sesleri**.
3. İçinde **ses** iletişim kutusu, tıklatın **ses** sekmesi. <br><br>
Ardından **Program olayları**, kaydırın **Microsoft Visual Studio**, seçtiğiniz olaylara uygulamak istediğiniz ses seçin.
4. **Tamam**'ı tıklatın.
## <a name="see-also"></a>Ayrıca bkz.
* [Visual Studio'nun erişilebilirlik özellikleri](../../ide/reference/accessibility-features-of-visual-studio.md)
* [Nasıl yapılır: menüleri ve Visual Studio içinde araç çubuklarını özelleştirme](../../ide/how-to-customize-menus-and-toolbars-in-visual-studio.md)
* [Visual Studio IDE'yi kişiselleştirme](../../ide/personalizing-the-visual-studio-ide.md)
* [Microsoft Erişilebilirlik](https://www.microsoft.com/Accessibility)
| 66.280374 | 468 | 0.772702 | tur_Latn | 0.999561 |
ed19c281b5e4a31b7e716697c9c5ef41ceea05d8 | 5,853 | md | Markdown | docs/atl/reference/cadapt-class.md | jmittert/cpp-docs | cea5a8ee2b4764b2bac4afe5d386362ffd64e55a | [
"CC-BY-4.0",
"MIT"
] | 1 | 2019-02-10T10:38:37.000Z | 2019-02-10T10:38:37.000Z | docs/atl/reference/cadapt-class.md | jmittert/cpp-docs | cea5a8ee2b4764b2bac4afe5d386362ffd64e55a | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/atl/reference/cadapt-class.md | jmittert/cpp-docs | cea5a8ee2b4764b2bac4afe5d386362ffd64e55a | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-06-14T03:42:31.000Z | 2020-06-14T03:42:31.000Z | ---
title: "CAdapt Class"
ms.date: "11/04/2016"
f1_keywords: ["CAdapt", "ATLCOMCLI/ATL::CAdapt", "ATLCOMCLI/ATL::CAdapt::CAdapt", "ATLCOMCLI/ATL::CAdapt::m_T"]
helpviewer_keywords: ["address-of operator", "adapter objects", "& operator, address-of operator", "CAdapt class"]
ms.assetid: 0bb695a5-72fe-43d1-8f39-7e4da6e34765
---
# CAdapt Class
This template is used to wrap classes that redefine the address-of operator to return something other than the address of the object.
## Syntax
```
template <class T>
class CAdapt
```
#### Parameters
*T*<br/>
The adapted type.
## Members
### Public Constructors
|Name|Description|
|----------|-----------------|
|[CAdapt::CAdapt](#cadapt)|The constructor.|
### Public Operators
|Name|Description|
|----------|-----------------|
|[CAdapt::operator const T&](#operator_const_t_amp)|Returns a **const** reference to `m_T`.|
|[CAdapt::operator T&](#operator_t_amp)|Returns a reference to `m_T`.|
|[CAdapt::operator <](#operator_lt)|Compares an object of the adapted type with `m_T`.|
|[CAdapt::operator =](#operator_eq)|Assigns an object of the adapted type to `m_T`.|
|[CAdapt::operator ==](#operator_eq_eq)|Compares an object of the adapted type with `m_T`.|
### Public Data Members
|Name|Description|
|----------|-----------------|
|[CAdapt::m_T](#m_t)|The data being adapted.|
## Remarks
`CAdapt` is a simple template used to wrap classes that redefine the address-of operator (`operator &`) to return something other than the address of the object. Examples of such classes include ATL's `CComBSTR`, `CComPtr`, and `CComQIPtr` classes, and the compiler COM support class, `_com_ptr_t`. These classes all redefine the address-of operator to return the address of one of their data members (a BSTR in the case of `CComBSTR`, and an interface pointer in the case of the other classes).
`CAdapt`'s primary role is to hide the address-of operator defined by class *T*, yet still retain the characteristics of the adapted class. `CAdapt` fulfils this role by holding a public member, [m_T](#m_t), of type *T*, and by defining conversion operators, comparison operators, and a copy constructor to allow specializations of `CAdapt` to be treated as if they are objects of type *T*.
The adapter class `CAdapt` is useful because some container-style classes expect to be able to obtain the addresses of their contained objects using the address-of operator. The redefinition of the address-of operator can confound this requirement, typically causing compilation errors and preventing the use of the non-adapted type with classes that expect it to "just work". `CAdapt` provides a way around those problems.
Typically, you will use `CAdapt` when you want to store `CComBSTR`, `CComPtr`, `CComQIPtr`, or `_com_ptr_t` objects in a container-style class. This was most commonly necessary for C++ Standard Library containers prior to support for the C++11 Standard, but C++11 Standard Library containers automatically work with types that have overloaded `operator&()`. The Standard Library achieves this by internally using [std::addressof](../../standard-library/memory-functions.md#addressof) to get the true addresses of objects.
## Requirements
**Header:** atlcomcli.h
## <a name="cadapt"></a> CAdapt::CAdapt
The constructors allow an adapter object to be default constructed, copied from an object of the adapted type, or copied from another adapter object.
```
CAdapt();
CAdapt(const T& rSrc);
CAdapt(const CAdapt& rSrCA);
CAdapt(T&& rSrCA); // (Visual Studio 2017)
CAdapt(CAdapt<T>&& rSrCA) noexcept; // (Visual Studio 2017)
```
### Parameters
*rSrc*<br/>
A variable of the type being adapted to be copied into the newly constructed adapter object.
*rSrCA*<br/>
An adapter object whose contained data should be copied (or moved) into the newly constructed adapter object.
## <a name="m_t"></a> CAdapt::m_T
Holds the data being adapted.
```
T m_T;
```
### Remarks
This **public** data member can be accessed directly or indirectly with [operator const T&](#operator_const_t_amp) and [operator T&](#operator_t_amp).
## <a name="operator_const_t_amp"></a> CAdapt::operator const T&
Returns a **const** reference to the [m_T](#m_t) member, allowing the adapter object to be treated as if it were an object of type *T*.
```
operator const T&() const;
```
### Return Value
A **const** reference to `m_T`.
## <a name="operator_t_amp"></a> CAdapt::operator T&
Returns a reference to the [m_T](#m_t) member, allowing the adapter object to be treated as if it were an object of type *T*.
```
operator T&();
```
### Return Value
A reference to `m_T`.
## <a name="operator_lt"></a> CAdapt::operator <
Compares an object of the adapted type with [m_T](#m_t).
```
bool operator<(const T& rSrc) const;
```
### Parameters
*rSrc*<br/>
A reference to the object to be compared.
### Return Value
The result of the comparison between `m_T` and *rSrc*.
## <a name="operator_eq"></a> CAdapt::operator =
The assignment operator assigns the argument, *rSrc*, to the data member [m_T](#m_t) and returns the current adapter object.
```
CAdapt& operator= (const T& rSrc);
CAdapt& operator= (T&& rSrCA); // (Visual Studio 2017)
CAdapt& operator= (CAdapt<T>&& rSrCA) noexcept; // (Visual Studio 2017)
```
### Parameters
*rSrc*<br/>
A reference to an object of the adapted type to be copied.
*rSrCA*<br/>
A reference to an object to be moved.
### Return Value
A reference to the current object.
## <a name="operator_eq_eq"></a> CAdapt::operator ==
Compares an object of the adapted type with [m_T](#m_t).
```
bool operator== (const T& rSrc) const;
```
### Parameters
*rSrc*<br/>
A reference to the object to be compared.
### Return Value
The result of the comparison between *m_T* and *rSrc*.
## See Also
[Class Overview](../../atl/atl-class-overview.md)
| 33.067797 | 521 | 0.713993 | eng_Latn | 0.982754 |
ed19d492f400928a860ac8986e76391658b40b9e | 9,900 | md | Markdown | source/nodejs/adaptivecards/docs/classes/backgroundimage.md | asseco-see/AdaptiveCards | e7f0d0ded03456133d4ab91efd7e912a41440132 | [
"MIT"
] | null | null | null | source/nodejs/adaptivecards/docs/classes/backgroundimage.md | asseco-see/AdaptiveCards | e7f0d0ded03456133d4ab91efd7e912a41440132 | [
"MIT"
] | 21 | 2021-12-15T15:27:04.000Z | 2022-02-28T01:29:33.000Z | source/nodejs/adaptivecards/docs/classes/backgroundimage.md | asseco-see/AdaptiveCards | 676c754e856daf672740c7db88940a51e405bc47 | [
"MIT"
] | 2 | 2020-11-24T15:58:32.000Z | 2022-02-02T11:57:48.000Z | [Adaptive Cards Javascript SDK](../README.md) › [BackgroundImage](backgroundimage.md)
# Class: BackgroundImage
## Hierarchy
* [SerializableObject](serializableobject.md)
↳ **BackgroundImage**
## Index
### Constructors
* [constructor](backgroundimage.md#constructor)
### Properties
* [fillMode](backgroundimage.md#fillmode)
* [horizontalAlignment](backgroundimage.md#horizontalalignment)
* [maxVersion](backgroundimage.md#maxversion)
* [url](backgroundimage.md#optional-url)
* [verticalAlignment](backgroundimage.md#verticalalignment)
* [fillModeProperty](backgroundimage.md#static-readonly-fillmodeproperty)
* [horizontalAlignmentProperty](backgroundimage.md#static-readonly-horizontalalignmentproperty)
* [onRegisterCustomProperties](backgroundimage.md#static-optional-onregistercustomproperties)
* [urlProperty](backgroundimage.md#static-readonly-urlproperty)
* [verticalAlignmentProperty](backgroundimage.md#static-readonly-verticalalignmentproperty)
### Methods
* [apply](backgroundimage.md#apply)
* [getCustomProperty](backgroundimage.md#getcustomproperty)
* [getDefaultSerializationContext](backgroundimage.md#protected-getdefaultserializationcontext)
* [getSchema](backgroundimage.md#getschema)
* [getSchemaKey](backgroundimage.md#protected-getschemakey)
* [getValue](backgroundimage.md#protected-getvalue)
* [hasAllDefaultValues](backgroundimage.md#hasalldefaultvalues)
* [hasDefaultValue](backgroundimage.md#hasdefaultvalue)
* [internalParse](backgroundimage.md#protected-internalparse)
* [internalToJSON](backgroundimage.md#protected-internaltojson)
* [isValid](backgroundimage.md#isvalid)
* [parse](backgroundimage.md#parse)
* [populateSchema](backgroundimage.md#protected-populateschema)
* [resetDefaultValues](backgroundimage.md#resetdefaultvalues)
* [setCustomProperty](backgroundimage.md#setcustomproperty)
* [setValue](backgroundimage.md#protected-setvalue)
* [shouldSerialize](backgroundimage.md#protected-shouldserialize)
* [toJSON](backgroundimage.md#tojson)
## Constructors
### constructor
\+ **new BackgroundImage**(): *[BackgroundImage](backgroundimage.md)*
*Inherited from [HostCapabilities](hostcapabilities.md).[constructor](hostcapabilities.md#constructor)*
**Returns:** *[BackgroundImage](backgroundimage.md)*
## Properties
### fillMode
• **fillMode**: *[FillMode](../enums/fillmode.md)*
___
### horizontalAlignment
• **horizontalAlignment**: *[HorizontalAlignment](../enums/horizontalalignment.md)*
___
### maxVersion
• **maxVersion**: *[Version](version.md)* = Versions.v1_3
*Inherited from [HostCapabilities](hostcapabilities.md).[maxVersion](hostcapabilities.md#maxversion)*
___
### `Optional` url
• **url**? : *undefined | string*
___
### verticalAlignment
• **verticalAlignment**: *[VerticalAlignment](../enums/verticalalignment.md)*
___
### `Static` `Readonly` fillModeProperty
▪ **fillModeProperty**: *[EnumProperty](enumproperty.md)‹[FillMode](../enums/fillmode.md)›* = new EnumProperty(Versions.v1_2, "fillMode", Enums.FillMode, Enums.FillMode.Cover)
___
### `Static` `Readonly` horizontalAlignmentProperty
▪ **horizontalAlignmentProperty**: *[EnumProperty](enumproperty.md)‹[HorizontalAlignment](../enums/horizontalalignment.md)›* = new EnumProperty(Versions.v1_2, "horizontalAlignment", Enums.HorizontalAlignment, Enums.HorizontalAlignment.Left)
___
### `Static` `Optional` onRegisterCustomProperties
▪ **onRegisterCustomProperties**? : *undefined | function*
*Inherited from [HostCapabilities](hostcapabilities.md).[onRegisterCustomProperties](hostcapabilities.md#static-optional-onregistercustomproperties)*
___
### `Static` `Readonly` urlProperty
▪ **urlProperty**: *[StringProperty](stringproperty.md)‹›* = new StringProperty(Versions.v1_0, "url")
___
### `Static` `Readonly` verticalAlignmentProperty
▪ **verticalAlignmentProperty**: *[EnumProperty](enumproperty.md)‹[VerticalAlignment](../enums/verticalalignment.md)›* = new EnumProperty(Versions.v1_2, "verticalAlignment", Enums.VerticalAlignment, Enums.VerticalAlignment.Top)
## Methods
### apply
▸ **apply**(`element`: [CardElement](cardelement.md)): *void*
**Parameters:**
Name | Type |
------ | ------ |
`element` | [CardElement](cardelement.md) |
**Returns:** *void*
___
### getCustomProperty
▸ **getCustomProperty**(`name`: string): *any*
*Inherited from [HostCapabilities](hostcapabilities.md).[getCustomProperty](hostcapabilities.md#getcustomproperty)*
**Parameters:**
Name | Type |
------ | ------ |
`name` | string |
**Returns:** *any*
___
### `Protected` getDefaultSerializationContext
▸ **getDefaultSerializationContext**(): *[BaseSerializationContext](baseserializationcontext.md)*
*Inherited from [HostCapabilities](hostcapabilities.md).[getDefaultSerializationContext](hostcapabilities.md#protected-getdefaultserializationcontext)*
**Returns:** *[BaseSerializationContext](baseserializationcontext.md)*
___
### getSchema
▸ **getSchema**(): *[SerializableObjectSchema](serializableobjectschema.md)*
*Inherited from [HostCapabilities](hostcapabilities.md).[getSchema](hostcapabilities.md#getschema)*
**Returns:** *[SerializableObjectSchema](serializableobjectschema.md)*
___
### `Protected` getSchemaKey
▸ **getSchemaKey**(): *string*
*Overrides [SerializableObject](serializableobject.md).[getSchemaKey](serializableobject.md#protected-abstract-getschemakey)*
**Returns:** *string*
___
### `Protected` getValue
▸ **getValue**(`property`: [PropertyDefinition](propertydefinition.md)): *any*
*Inherited from [HostCapabilities](hostcapabilities.md).[getValue](hostcapabilities.md#protected-getvalue)*
**Parameters:**
Name | Type |
------ | ------ |
`property` | [PropertyDefinition](propertydefinition.md) |
**Returns:** *any*
___
### hasAllDefaultValues
▸ **hasAllDefaultValues**(): *boolean*
*Inherited from [HostCapabilities](hostcapabilities.md).[hasAllDefaultValues](hostcapabilities.md#hasalldefaultvalues)*
**Returns:** *boolean*
___
### hasDefaultValue
▸ **hasDefaultValue**(`property`: [PropertyDefinition](propertydefinition.md)): *boolean*
*Inherited from [HostCapabilities](hostcapabilities.md).[hasDefaultValue](hostcapabilities.md#hasdefaultvalue)*
**Parameters:**
Name | Type |
------ | ------ |
`property` | [PropertyDefinition](propertydefinition.md) |
**Returns:** *boolean*
___
### `Protected` internalParse
▸ **internalParse**(`source`: any, `context`: [BaseSerializationContext](baseserializationcontext.md)): *void*
*Overrides [SerializableObject](serializableobject.md).[internalParse](serializableobject.md#protected-internalparse)*
**Parameters:**
Name | Type |
------ | ------ |
`source` | any |
`context` | [BaseSerializationContext](baseserializationcontext.md) |
**Returns:** *void*
___
### `Protected` internalToJSON
▸ **internalToJSON**(`target`: [PropertyBag](../README.md#propertybag), `context`: [BaseSerializationContext](baseserializationcontext.md)): *void*
*Inherited from [SerializableObject](serializableobject.md).[internalToJSON](serializableobject.md#protected-internaltojson)*
**Parameters:**
Name | Type |
------ | ------ |
`target` | [PropertyBag](../README.md#propertybag) |
`context` | [BaseSerializationContext](baseserializationcontext.md) |
**Returns:** *void*
___
### isValid
▸ **isValid**(): *boolean*
**Returns:** *boolean*
___
### parse
▸ **parse**(`source`: [PropertyBag](../README.md#propertybag), `context?`: [BaseSerializationContext](baseserializationcontext.md)): *void*
*Inherited from [HostCapabilities](hostcapabilities.md).[parse](hostcapabilities.md#parse)*
**Parameters:**
Name | Type |
------ | ------ |
`source` | [PropertyBag](../README.md#propertybag) |
`context?` | [BaseSerializationContext](baseserializationcontext.md) |
**Returns:** *void*
___
### `Protected` populateSchema
▸ **populateSchema**(`schema`: [SerializableObjectSchema](serializableobjectschema.md)): *void*
*Inherited from [HostCapabilities](hostcapabilities.md).[populateSchema](hostcapabilities.md#protected-populateschema)*
**Parameters:**
Name | Type |
------ | ------ |
`schema` | [SerializableObjectSchema](serializableobjectschema.md) |
**Returns:** *void*
___
### resetDefaultValues
▸ **resetDefaultValues**(): *void*
*Inherited from [HostCapabilities](hostcapabilities.md).[resetDefaultValues](hostcapabilities.md#resetdefaultvalues)*
**Returns:** *void*
___
### setCustomProperty
▸ **setCustomProperty**(`name`: string, `value`: any): *void*
*Inherited from [HostCapabilities](hostcapabilities.md).[setCustomProperty](hostcapabilities.md#setcustomproperty)*
**Parameters:**
Name | Type |
------ | ------ |
`name` | string |
`value` | any |
**Returns:** *void*
___
### `Protected` setValue
▸ **setValue**(`property`: [PropertyDefinition](propertydefinition.md), `value`: any): *void*
*Inherited from [HostCapabilities](hostcapabilities.md).[setValue](hostcapabilities.md#protected-setvalue)*
**Parameters:**
Name | Type |
------ | ------ |
`property` | [PropertyDefinition](propertydefinition.md) |
`value` | any |
**Returns:** *void*
___
### `Protected` shouldSerialize
▸ **shouldSerialize**(`context`: [BaseSerializationContext](baseserializationcontext.md)): *boolean*
*Inherited from [HostCapabilities](hostcapabilities.md).[shouldSerialize](hostcapabilities.md#protected-shouldserialize)*
**Parameters:**
Name | Type |
------ | ------ |
`context` | [BaseSerializationContext](baseserializationcontext.md) |
**Returns:** *boolean*
___
### toJSON
▸ **toJSON**(`context?`: [BaseSerializationContext](baseserializationcontext.md)): *[PropertyBag](../README.md#propertybag) | undefined*
*Inherited from [HostCapabilities](hostcapabilities.md).[toJSON](hostcapabilities.md#tojson)*
**Parameters:**
Name | Type |
------ | ------ |
`context?` | [BaseSerializationContext](baseserializationcontext.md) |
**Returns:** *[PropertyBag](../README.md#propertybag) | undefined*
| 26.259947 | 240 | 0.741818 | yue_Hant | 0.290826 |
ed1a8d50bda7df94207a62a18d3dee05bc67301e | 264 | md | Markdown | _notes/Public/Orks/Warlord Traits/Beast Snagga/Half Chewed.md | seefrye/waaaaagh-list | 789af35af074e4ba1cb772e6ebc8859405275875 | [
"MIT"
] | null | null | null | _notes/Public/Orks/Warlord Traits/Beast Snagga/Half Chewed.md | seefrye/waaaaagh-list | 789af35af074e4ba1cb772e6ebc8859405275875 | [
"MIT"
] | null | null | null | _notes/Public/Orks/Warlord Traits/Beast Snagga/Half Chewed.md | seefrye/waaaaagh-list | 789af35af074e4ba1cb772e6ebc8859405275875 | [
"MIT"
] | null | null | null | ---
title: Half Chewed
notetype : nofeed
date: 24-10-2021
---
# Half-Chewed
## Description
While this WARLORD is within Engagement Range of an enemy CHARACTER or MONSTER unit, each time this model would lose a wound, roll one D6: on a 4+, that wound is not lost. | 26.4 | 171 | 0.738636 | eng_Latn | 0.998605 |
ed1ae250fd8cad9cdfb6039a0f84c76fc562edc1 | 308 | md | Markdown | index.md | metalcanine/futch | 0031da7e9a21acf633884119fa0f07215fcca923 | [
"BSD-3-Clause"
] | null | null | null | index.md | metalcanine/futch | 0031da7e9a21acf633884119fa0f07215fcca923 | [
"BSD-3-Clause"
] | 3 | 2020-03-01T04:55:18.000Z | 2020-03-02T05:07:24.000Z | index.md | metalcanine/futch | 0031da7e9a21acf633884119fa0f07215fcca923 | [
"BSD-3-Clause"
] | 1 | 2020-02-24T00:18:32.000Z | 2020-02-24T00:18:32.000Z | ---
layout: page
---
---
# welcome!
---
#### this is my home page on the internet!
#### i use it for sharing updates about projects and to write about things i love
#### that usually means programming, computers, obsolete technology, and dogs
#### i hope you enjoy my writing and also find it useful!
| 17.111111 | 81 | 0.681818 | eng_Latn | 0.999932 |
ed1b274d508af28fc4759dfcd38a1aed8f05b0e1 | 1,637 | md | Markdown | src/mngr/mngr039.md | pomu0325/kinokobooks | fe499a847a2469dccbadfbac11569035f4c88e7a | [
"CC-BY-2.0",
"CC-BY-3.0",
"CC0-1.0"
] | 21 | 2020-09-15T05:55:43.000Z | 2022-03-29T07:48:11.000Z | src/mngr/mngr039.md | pomu0325/kinokobooks | fe499a847a2469dccbadfbac11569035f4c88e7a | [
"CC-BY-2.0",
"CC-BY-3.0",
"CC0-1.0"
] | 5 | 2020-05-05T03:59:20.000Z | 2021-05-18T21:14:55.000Z | src/mngr/mngr039.md | pomu0325/kinokobooks | fe499a847a2469dccbadfbac11569035f4c88e7a | [
"CC-BY-2.0",
"CC-BY-3.0",
"CC0-1.0"
] | 1 | 2021-05-18T17:40:55.000Z | 2021-05-18T17:40:55.000Z | # 【39】変化のための道筋を描く{#e39}
<div class="author">キャシー・マクドゥガル（Kathy MacDougall）</div>
<div class="author_address">アメリカ、コロラド州エリー</div>
新しいソフトウェアは仕事のやり方を変えます。これは組織にとってよいことかもしれませんが、そこで仕事をしている人は必ずしも変化を受け入れる準備ができているわけではありません。この現実を認めましょう。新しいソフトウェアを使うよう説得できなかったり、なだめられなかったり、指示できなければ、それは時間とお金の大きなムダになります。
仕事のやり方を変えさせるときには、ムチ（罰）よりもアメ（報酬）の方がはるかに有効です。たとえ新しいソフトウェアを導入せざるを得なくなったとしても、ユーザーが理解して習得するに値する大きな利益が見い出せなければ、彼らはあらゆる手段を駆使して使わずに済ませようとするでしょう。（1）この変化が関係者にどんな影響を及ぼすのかを理解し、（2）彼らが変化を受け入れられるような変更管理計画を整備するためには、適切なケアが必要になります。
変化がどんな影響を及ぼすのかを理解するために重要なのは、みんなが現在どのように仕事をしているのか、新しいソフトウェアはそのプロセスをどのように変えるのかを理解することです。そうすれば新しいソフトウェアがユーザーのニーズに合致することを保証でき、ユーザーが新しいシステムを導入する可能性が高まり、最終商品の設計も改善されます。
変更管理の重要性を過小評価してはいけません。これはプロジェクトの初期にプロジェクト・マネジャーが注力すべきところです。変化がユーザーにどんな影響を及ぼすのか判断するために、まずはソフトウェアプロジェクトにまつわる現在のあらゆる（そのままの）プロセスをドキュメント化しましょう。毎日のタスクを列挙したプロセスフローダイアグラムとデータの入出力を図示しましょう。
次に、新しいソフトウェアを展開することによって、これらのプロセスがどのように変化するのかをドキュメント化しましょう。新しいソフトウェアのターゲットユーザーと率直に話し、その変化がどのような影響を及ぼすのか議論しましょう。彼らの声に注意深く耳を傾けて、フィーチャー変更の影響とそのコストを評価して、ソフトウェア設計を徐々に整えていきましょう。変化がターゲットユーザーと彼らのマネジメントに受け入れられているか確認してください。ターゲットユーザーのマネジャーを、早期に頻繁に巻き込みましょう。彼らは変化に対する重要な支持者となります。エンドユーザーに切り替えを勧めたり指示したりすることにより、彼らは新しいシステムへの移行を実施もしくは中断できます。彼らは新しいソフトウェア展開に伴う障害を取り除き、不測の問題を解決するための貴重なパートナーなのです。
変化のための計画を作りましょう。プロジェクト立ち上げ前にやっておく必要のあるトレーニングやチーム作りのためのリストを決めて、ユーザーのスケジュールに組み込んでおきましょう。変更管理計画を作るときには、マネジメントからの支援を仰ぎましょう。少なくとも彼らが、そのコンセプト、実行およびトレーニング方法、スケジュールについて心から賛同していなければなりません。彼らからのアプローチに対する反対意見や警告には、注意深く耳を傾けましょう。
結局のところ、ユーザーとそのマネジメントはビジネス目標を果たすことに正面から注力し続けることに関心があります。新しいプロセス、ツール、システムへの移行は、彼らの目標達成にとって潜在的脅威になり得ます。きっちり事前に計画しておきましょう。そうすれば、新しいシステムへスムーズに移行でき、賛同と受け入れのための道を開き、長期的な利用の機会を高めることができるでしょう。
| 86.157895 | 375 | 0.919976 | jpn_Jpan | 0.964637 |
ed1b55fe41fc7fdc56fae7c12dcdf9c31401e1ce | 136 | md | Markdown | README.md | Puzzo116/ECommerce-web-app | 907e1589d6b666aeb399ee4f2b187bae43271774 | [
"MIT"
] | null | null | null | README.md | Puzzo116/ECommerce-web-app | 907e1589d6b666aeb399ee4f2b187bae43271774 | [
"MIT"
] | null | null | null | README.md | Puzzo116/ECommerce-web-app | 907e1589d6b666aeb399ee4f2b187bae43271774 | [
"MIT"
] | null | null | null | # ECommerce-web-app
an MVC web app built using C#, Entity Framework, Asp.Net Identity, Html, Css, Bootstrap, Javascript, JQuery and Css
| 45.333333 | 115 | 0.764706 | eng_Latn | 0.410686 |
ed1c9705cfa6233f8e46514c2bac84c78b265a22 | 817 | md | Markdown | docs/content/stable/yugabyte-platform/upgrade/_index.md | bllewell/yugabyte-db | b757f8d8c0c10854754a17f63db007a0874eaf1f | [
"Apache-2.0",
"CC0-1.0"
] | 4 | 2019-07-19T12:55:40.000Z | 2021-03-25T15:59:09.000Z | docs/content/stable/yugabyte-platform/upgrade/_index.md | bllewell/yugabyte-db | b757f8d8c0c10854754a17f63db007a0874eaf1f | [
"Apache-2.0",
"CC0-1.0"
] | 10 | 2021-09-16T08:38:50.000Z | 2022-03-01T09:48:44.000Z | docs/content/stable/yugabyte-platform/upgrade/_index.md | bllewell/yugabyte-db | b757f8d8c0c10854754a17f63db007a0874eaf1f | [
"Apache-2.0",
"CC0-1.0"
] | 1 | 2021-08-04T12:10:20.000Z | 2021-08-04T12:10:20.000Z | ---
title: Upgrade Yugabyte Platform
headerTitle: Upgrade Yugabyte Platform
linkTitle: Upgrade Yugabyte Platform
description: Upgrade Yugabyte Platform.
image: /images/section_icons/manage/enterprise.png
menu:
stable:
identifier: upgrade
parent: yugabyte-platform
weight: 649
---
You can upgrade Yugabyte Platform to a newer version.
<div class="row">
<div class="col-12 col-md-6 col-lg-12 col-xl-6">
<a class="section-link icon-offset" href="upgrade-yp-replicated/">
<div class="head">
<img class="icon" src="/images/section_icons/manage/backup.png" aria-hidden="true" />
<div class="title">Upgrade Yugabyte Platform using Replicated</div>
</div>
<div class="body">
Use Replicated to upgrade Yugabyte Platform
</div>
</a>
</div>
</div>
| 25.53125 | 93 | 0.682987 | eng_Latn | 0.454257 |
ed1d33bfe7c7da8f41ed5dbfdcd5eb6ec67e5542 | 2,493 | md | Markdown | desktop-src/Direct2D/how-to-create-a-bitmap-brush.md | citelao/win32 | bf61803ccb0071d99eee158c7416b9270a83b3e4 | [
"CC-BY-4.0",
"MIT"
] | 552 | 2019-08-20T00:08:40.000Z | 2022-03-30T18:25:35.000Z | desktop-src/Direct2D/how-to-create-a-bitmap-brush.md | citelao/win32 | bf61803ccb0071d99eee158c7416b9270a83b3e4 | [
"CC-BY-4.0",
"MIT"
] | 1,143 | 2019-08-21T20:17:47.000Z | 2022-03-31T20:24:39.000Z | desktop-src/Direct2D/how-to-create-a-bitmap-brush.md | citelao/win32 | bf61803ccb0071d99eee158c7416b9270a83b3e4 | [
"CC-BY-4.0",
"MIT"
] | 1,287 | 2019-08-20T05:37:48.000Z | 2022-03-31T20:22:06.000Z | ---
title: How to Create a Bitmap Brush
description: Shows how to create a bitmap brush using Direct2D.
ms.assetid: 8f78b30a-7507-4dd8-b6f4-12d88e3c9a1d
ms.topic: article
ms.date: 05/31/2018
---
# How to Create a Bitmap Brush
To create a bitmap brush, use the [**ID2D1RenderTarget::CreateBitmapBrush**](id2d1rendertarget-createbitmapbrush.md) method and specify the bitmap brush properties. Some overloads enable you to specify the brush properties. The following code shows how to create a bitmap brush to fill a square, and a solid black brush to draw the outline of the square. The code produces the output shown in the following screen shot.
> [!Note]
> Starting with Windows 8, you can use the [**CreateBitmapBrush**](/windows/win32/api/d2d1_1/nf-d2d1_1-id2d1devicecontext-createbitmapbrush(id2d1bitmap_constd2d1_bitmap_brush_properties1_constd2d1_brush_properties_id2d1bitmapbrush1)) method on the [**ID2D1DeviceContext**](/windows/win32/api/d2d1_1/nn-d2d1_1-id2d1devicecontext) interface to create a [**ID2D1BitmapBrush1**](/windows/win32/api/d2d1_1/nn-d2d1_1-id2d1bitmapbrush1) instead of a **ID2D1BitmapBrush**. **ID2D1BitmapBrush1** adds high-quality scaling modes to the bitmap brush.
1. Declare a variable of type [**ID2D1BitmapBrush**](/windows/win32/api/d2d1/nn-d2d1-id2d1bitmapbrush).
```C++
ID2D1BitmapBrush *m_pBitmapBrush;
```
2. Load a bitmap from a resource. For more information, see [How to Load a Bitmap from a Resource](how-to-load-a-bitmap-from-a-resource.md).
```C++
// Create the bitmap to be used by the bitmap brush.
if (SUCCEEDED(hr))
{
hr = LoadResourceBitmap(
m_pRenderTarget,
m_pWICFactory,
L"FERN",
L"Image",
&m_pBitmap
);
```
3. Choose the extend modes ([**D2D1\_EXTEND\_MODE**](/windows/desktop/api/d2d1/ne-d2d1-d2d1_extend_mode)) and interpolation mode ([**D2D1\_BITMAP\_INTERPOLATION\_MODE**](/windows/desktop/api/d2d1/ne-d2d1-d2d1_bitmap_interpolation_mode)) of the bitmap brush and then call the [**CreateBitmapBrush**](id2d1rendertarget-createbitmapbrush.md) method to create a brush, as shown in the following code.
```C++
hr = m_pRenderTarget->CreateBitmapBrush(
m_pBitmap,
&m_pBitmapBrush
);
```
## Related topics
<dl> <dt>
[Direct2D Reference](reference.md)
</dt> </dl>
| 40.209677 | 539 | 0.71801 | eng_Latn | 0.567856 |
ed1dcba7babf40281f7a32af34dc68a36202b218 | 44 | md | Markdown | _tag/linode.md | Kromey/Kromey.github.io | 7725b800fb529abc4deba9a1aeaa981210c97c88 | [
"CC-BY-4.0"
] | null | null | null | _tag/linode.md | Kromey/Kromey.github.io | 7725b800fb529abc4deba9a1aeaa981210c97c88 | [
"CC-BY-4.0"
] | 2 | 2020-02-26T00:37:50.000Z | 2022-02-26T05:26:00.000Z | _tag/linode.md | Kromey/Kromey.github.io | 7725b800fb529abc4deba9a1aeaa981210c97c88 | [
"CC-BY-4.0"
] | null | null | null | ---
tag: linode
permalink: /tag/linode/
---
| 8.8 | 23 | 0.613636 | epo_Latn | 0.101001 |
ed1f0b228c27bffbb730affbd7dacd55a8745cb0 | 4,131 | md | Markdown | README.md | ibrahimelhadeg/backend-tech-assignment | c5ae1c7959f69fa4188bcaec30ea84f9800e8d26 | [
"MIT"
] | null | null | null | README.md | ibrahimelhadeg/backend-tech-assignment | c5ae1c7959f69fa4188bcaec30ea84f9800e8d26 | [
"MIT"
] | null | null | null | README.md | ibrahimelhadeg/backend-tech-assignment | c5ae1c7959f69fa4188bcaec30ea84f9800e8d26 | [
"MIT"
] | null | null | null | # VEHICLE ADVERTISING
a REST service for managing listings for online advertising service.
## Terminology
- **Listing** - a vehicle ad, usually consists of information about a vehicle and some other information, like who is selling a car, price, posting date, etc. Listing can be in one of two possible states:
- published - available online or
- draft - not available online.
- **Car Dealer** - a business that sells new or used cars.
- **Tier Limit** - a number of published listings a dealer can have online.
## Requirements
Service should implement following functionality:
- Create a listing. All the created listings should have state `draft` by default;
- Update a listing;
- Get all listings of a dealer with a given state;
- Publish a listing;
- Unpublish a listing.
Please note that the number of published listings for a dealer should be less or equal to the dealer's tier limit. When publishing a listing, client should be able to choose how to deal with situation when tier limit is reached - either
- return an error to the client, or
- publish a listing, but unpublish the oldest listing of a dealer to conform to the tier limit.
Come up with an additional functionality of your choice that could give value to the service.
# INSTRUCTIONS
These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.
### Prerequisites
Building or running this project requires that [Java 16 or newer](https://jdk.java.net/java-se-ri/16) be available on your machine.
## Development
### Setup
After installing Java, you should be able to run the following command to install project dependencies.
./mvnw dependency:resolve
You will only need run this command when dependencies change in [pom.xml](pom.xml).
To compile the sources, use :
./mvnw clean install
Run the following command in a terminal to start the application on the development mode.
./mvnw spring-boot:run -Dspring-boot.run.profiles=local -pl api
## Testing
To compile then run the tests, use :
./mvnw clean test
## Building for production
To prepare the splitter application for production, run:
./mvnw clean package
This will produce a JAR file on the `target` directory. To ensure everything worked, run:
java -jar target/*.jar
Then you can use the program from your terminal.
## Deployment
TODO
## Troubleshooting
If you get the message `permission denied: ./mvnw`, when trying to run the commands,
execute the following command (to ask your system to attribute the permission to the file [mvnw](mvnw)):
chmod +x mvnw
In case of error when running the provided commands, try to add the arguments `-e` or `-X` to get detailed error messages
If your Java version is older than 16, and you've encountered problems running any of the commands, try to run it by appending at beginning `export JAVA_HOME="/path/to/java/16/jdk" && `
export JAVA_HOME="/path/to/java/16/jdk" && ./mvnw clean test
## Built with
* [Java](https://jdk.java.net/) - The programming language
* [JUnit](https://junit.org/) and [Mockito](https://site.mockito.org/) - Used to create tests
* [Spring Boot](https://spring.io/projects/spring-boot) - Spring Framework
* [Maven](https://maven.apache.org/) and [Maven Wrapper](https://github.com/takari/maven-wrapper) - Dependency Management
* [Git](https://git-scm.com/) - as version-control system
### Reference Documentation
For further reference, please consider the following sections:
* [Official Apache Maven documentation](https://maven.apache.org/guides/index.html)
* [Spring Boot Maven Plugin Reference Guide](https://docs.spring.io/spring-boot/docs/2.5.1/maven-plugin/reference/html/)
* [Create an OCI image](https://docs.spring.io/spring-boot/docs/2.5.1/maven-plugin/reference/html/#build-image)
## Versioning
We use [SemVer](http://semver.org/) for versioning.
## Author
* **Ibrahim El Hadeg**
## License
This project is licensed under the MIT License - see the [LICENSE.md](LICENSE.md) file for details
| 35.307692 | 236 | 0.747035 | eng_Latn | 0.989514 |
ed1f24cfbec25e7b9b2b7a4dc908375cc48587ff | 3,378 | md | Markdown | docs/csharp/language-reference/builtin-types/bool.md | Jonatandb/docs.es-es | c18663ce8a09607fe195571492cad602bc2f01bb | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/csharp/language-reference/builtin-types/bool.md | Jonatandb/docs.es-es | c18663ce8a09607fe195571492cad602bc2f01bb | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/csharp/language-reference/builtin-types/bool.md | Jonatandb/docs.es-es | c18663ce8a09607fe195571492cad602bc2f01bb | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: 'bool (tipo): Referencia de C#'
ms.date: 11/26/2019
f1_keywords:
- bool
- bool_CSharpKeyword
helpviewer_keywords:
- bool data type [C#]
- Boolean [C#]
ms.assetid: 551cfe35-2632-4343-af49-33ad12da08e2
ms.openlocfilehash: 2ba2e54a6b0f24402fc3728dfe19b548a2368830
ms.sourcegitcommit: 7588136e355e10cbc2582f389c90c127363c02a5
ms.translationtype: HT
ms.contentlocale: es-ES
ms.lasthandoff: 03/14/2020
ms.locfileid: "78846450"
---
# <a name="bool-c-reference"></a>bool (Referencia de C#)
La palabra clave de tipo `bool` es un alias para el tipo de estructura de .NET <xref:System.Boolean?displayProperty=nameWithType> que representa un valor booleano que puede ser `true` o `false`.
Para realizar operaciones lógicas con valores del tipo `bool`, use operadores [lógicos booleanos](../operators/boolean-logical-operators.md). El tipo `bool` es el tipo de resultado de los operadores de [comparación](../operators/comparison-operators.md) e [igualdad](../operators/equality-operators.md). Una expresión `bool` puede ser una expresión condicional de control en las instrucciones [if](../keywords/if-else.md), [do](../keywords/do.md), [while](../keywords/while.md) y [for](../keywords/for.md), así como en el [operador condicional `?:`](../operators/conditional-operator.md).
El valor predeterminado del tipo `bool` es `false`.
## <a name="literals"></a>Literales
Puede usar los literales `true` y `false` para inicializar una variable `bool` o para pasar un valor `bool`:
[!code-csharp-interactive[bool literals](snippets/BoolType.cs#Literals)]
## <a name="three-valued-boolean-logic"></a>Lógica booleana de tres valores
Use el tipo `bool?` que acepta valores NULL si tiene que admitir la lógica de tres valores (por ejemplo, si trabaja con bases de datos que admiten un tipo booleano de tres valores). En el caso de los operandos `bool?`, los operadores predefinidos `&` y `|` admiten la lógica de tres valores. Para más información, consulte la sección [Operadores lógicos booleanos que aceptan valores NULL](../operators/boolean-logical-operators.md#nullable-boolean-logical-operators) del artículo [Operadores lógicos booleanos](../operators/boolean-logical-operators.md).
Para más información sobre los tipos de valor que admiten un valor NULL, consulte [Tipos de valor que admiten un valor NULL](nullable-value-types.md).
## <a name="conversions"></a>Conversiones
C# solo proporciona dos conversiones que implican al tipo `bool`. Son una conversión implícita al tipo `bool?` que acepta valores NULL correspondiente y una conversión explícita del tipo `bool?`. Sin embargo, .NET proporciona métodos adicionales que se pueden usar para realizar una conversión al tipo `bool`, o bien revertirla. Para obtener más información, vea la sección [Convertir a y desde valores booleanos](/dotnet/api/system.boolean#converting-to-and-from-boolean-values) de la página de referencia de la API <xref:System.Boolean?displayProperty=nameWithType>.
## <a name="c-language-specification"></a>especificación del lenguaje C#
Para obtener más información, vea la sección [Tipo bool](~/_csharplang/spec/types.md#the-bool-type) de la [especificación del lenguaje C#](~/_csharplang/spec/introduction.md).
## <a name="see-also"></a>Vea también
- [Referencia de C#](../index.md)
- [Tipos de valor](value-types.md)
- [Operadores true y false](../operators/true-false-operators.md)
| 66.235294 | 588 | 0.767022 | spa_Latn | 0.914249 |
ed1f2e5d71eb4bfcb82bb4f118ab803b52eba55f | 790 | md | Markdown | node_modules/@firebase/remote-config/CHANGELOG.md | KevinD-UP/Bibliotheque | 61447f151b78c139051b843458cc212ac98d9a6f | [
"MIT"
] | 19 | 2020-10-05T17:05:19.000Z | 2020-11-23T16:07:49.000Z | node_modules/@firebase/remote-config/CHANGELOG.md | KevinD-UP/Bibliotheque | 61447f151b78c139051b843458cc212ac98d9a6f | [
"MIT"
] | 4 | 2020-08-27T11:23:53.000Z | 2020-09-09T09:17:34.000Z | node_modules/@firebase/remote-config/CHANGELOG.md | KevinD-UP/Bibliotheque | 61447f151b78c139051b843458cc212ac98d9a6f | [
"MIT"
] | 1 | 2020-10-09T02:24:52.000Z | 2020-10-09T02:24:52.000Z | # @firebase/remote-config
## 0.1.27
### Patch Changes
- Updated dependencies [[`d4ca3da0`](https://github.com/firebase/firebase-js-sdk/commit/d4ca3da0a59fcea1261ba69d7eb663bba38d3089)]:
- @firebase/[email protected]
- @firebase/[email protected]
- @firebase/[email protected]
## 0.1.26
### Patch Changes
- Updated dependencies [[`a87676b8`](https://github.com/firebase/firebase-js-sdk/commit/a87676b84b78ccc2f057a22eb947a5d13402949c)]:
- @firebase/[email protected]
- @firebase/[email protected]
- @firebase/[email protected]
## 0.1.25
### Patch Changes
- Updated dependencies [[`a754645e`](https://github.com/firebase/firebase-js-sdk/commit/a754645ec2be1b8c205f25f510196eee298b0d6e)]:
- @firebase/[email protected]
- @firebase/[email protected]
- @firebase/[email protected]
| 27.241379 | 131 | 0.73038 | yue_Hant | 0.253874 |
ed1fb5695b632bfee6a646f3485ec4ff3218adeb | 428 | md | Markdown | content/projects/budget.md | JipFr/website-2021 | f62ae368df951178e2b337be673a443a17b10a26 | [
"MIT"
] | null | null | null | content/projects/budget.md | JipFr/website-2021 | f62ae368df951178e2b337be673a443a17b10a26 | [
"MIT"
] | null | null | null | content/projects/budget.md | JipFr/website-2021 | f62ae368df951178e2b337be673a443a17b10a26 | [
"MIT"
] | null | null | null | ---
title: Budget
description: I made my own app to keep track of finances
color: "#457461"
date: 2021-02-02T23:00:00Z
icon: "/uploads/icon-full-white.png"
icon-background: "#457461"
tech: Nuxt, Vue, SCSS, Node.js, MongoDB
---
I wanted an easy way to keep track of my finances with manual control. I figured nothing existed that was exactly like I wanted it, so I built it!
 | 32.923077 | 146 | 0.731308 | eng_Latn | 0.978422 |
ed201fed70803c4777c4d250c6b73f00fcdc64e8 | 98 | md | Markdown | README.md | Toughee/Pymodoro | c32655743a2cb3122e78321ff5fb4178fd7cd995 | [
"MIT"
] | null | null | null | README.md | Toughee/Pymodoro | c32655743a2cb3122e78321ff5fb4178fd7cd995 | [
"MIT"
] | null | null | null | README.md | Toughee/Pymodoro | c32655743a2cb3122e78321ff5fb4178fd7cd995 | [
"MIT"
] | null | null | null | 
# Pymodoro
Pomodoro Stopwatch created entirely in React
| 16.333333 | 44 | 0.795918 | eng_Latn | 0.606994 |
ed20c237aeb4c4e5d4f633d97b06ae8de12bc312 | 2,923 | md | Markdown | docs/2014/integration-services/expressions/divide-ssis-expression.md | bartfastiel/sql-docs.de-de | 6eb40df24a369fd59fc9afceccaf81c5d275ece9 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/2014/integration-services/expressions/divide-ssis-expression.md | bartfastiel/sql-docs.de-de | 6eb40df24a369fd59fc9afceccaf81c5d275ece9 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/2014/integration-services/expressions/divide-ssis-expression.md | bartfastiel/sql-docs.de-de | 6eb40df24a369fd59fc9afceccaf81c5d275ece9 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: (Division) (SSIS-Ausdruck) | Microsoft-Dokumentation
ms.custom: ''
ms.date: 06/13/2017
ms.prod: sql-server-2014
ms.reviewer: ''
ms.technology: integration-services
ms.topic: conceptual
helpviewer_keywords:
- / (divide)
- divide operator (/)
ms.assetid: 5bde9223-872d-443e-8a27-57735e1d8f3d
author: douglaslMS
ms.author: douglasl
manager: craigg
ms.openlocfilehash: bf72606d04d02cda0ec656509f56fc636ee1f6e5
ms.sourcegitcommit: ceb7e1b9e29e02bb0c6ca400a36e0fa9cf010fca
ms.translationtype: MT
ms.contentlocale: de-DE
ms.lasthandoff: 12/03/2018
ms.locfileid: "52810192"
---
# <a name="divide-ssis-expression"></a>(Division) (SSIS-Ausdruck)
Dividiert den ersten numerischen Ausdruck durch den zweiten numerischen Ausdruck.
## <a name="syntax"></a>Syntax
```
dividend / divisor
```
## <a name="arguments"></a>Argumente
*dividend*
Der zu dividierende numerische Ausdruck. *dividend* kann ein beliebiger numerischer Ausdruck sein. Weitere Informationen finden Sie unter [Integration Services Data Types](../data-flow/integration-services-data-types.md).
*divisor*
Der numerische Ausdruck, durch den der Dividend geteilt werden soll. *divisor* kann ein beliebiger numerischer Ausdruck außer Null sein.
## <a name="result-types"></a>Ergebnistypen
Die Ergebnistypen werden von den Datentypen der beiden Argumente bestimmt. Weitere Informationen finden Sie unter [Integration Services Data Types in Expressions](integration-services-data-types-in-expressions.md).
## <a name="remarks"></a>Hinweise
Wenn einer der Operanden NULL ist, ist das Ergebnis NULL.
Division durch Null ist nicht zulässig. Je nachdem, wie der *divisor* -Teilausdruck ausgewertet wird, wird einer der folgenden Fehler gemeldet:
- Falls der zu Null ausgewertete *divisor* -Teilausdruck eine Konstante ist, wird der Fehler zur Entwurfszeit angezeigt, und der Ausdruck kann deshalb nicht überprüft werden.
- Falls der zu Null ausgewertete *divisor* -Teilausdruck Variablen, aber keine Eingabespalten enthält, wird für die zugehörige Komponente bei der Überprüfung vor der Ausführung (die vor der Ausführung des Pakets erfolgt) ein Fehler gemeldet.
- Falls der zu 0 (null) ausgewertete *divisor* -Teilausdruck Eingabespalten enthält, wird der Fehler zur Laufzeit gemeldet und gemäß den Fehlerflussregeln der Datenflusskomponente behandelt.
## <a name="expression-examples"></a>Beispiele für Ausdrücke
In diesem Beispiel werden zwei numerische Literale dividiert.
```
25 / 5
```
In diesem Beispiel werden Werte in der **ListPrice** -Spalte durch die Werte in der **StandardCost** -Spalte dividiert.
```
ListPrice / StandardCost
```
## <a name="see-also"></a>Siehe auch
[Operatorenrangfolge und -assoziativität](operator-precedence-and-associativity.md)
[Operatoren (SSIS-Ausdruck)](operators-ssis-expression.md)
| 40.041096 | 245 | 0.75402 | deu_Latn | 0.977647 |
ed21adeab778c4fa77c3380f05c1a56581b2faad | 4,021 | md | Markdown | articles/python/tutorial-deploy-containers-02.md | mikaelkrief/azure-dev-docs | 035f485f182405fdf3e274ec4f70abfcf5fc9641 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/python/tutorial-deploy-containers-02.md | mikaelkrief/azure-dev-docs | 035f485f182405fdf3e274ec4f70abfcf5fc9641 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/python/tutorial-deploy-containers-02.md | mikaelkrief/azure-dev-docs | 035f485f182405fdf3e274ec4f70abfcf5fc9641 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: "Step 2: Deploy a container image to Azure App Service with Visual Studio Code"
description: Tutorial step 2, deploying the actual Docker image to Azure App Service from a container registry.
ms.topic: conceptual
ms.date: 09/12/2019
ms.custom: devx-track-python, seo-python-october2019
---
# 2: Deploy a container image to Azure App Service
[Previous step: prerequisites](tutorial-deploy-containers-01.md)
With a container image in a registry, you can use the Docker extension in VS Code to easily set up an Azure App Service running the container.
1. In the **Docker** explorer, expand **Registries**, expand the node for your registry (such as **Azure**), then expand the node for your image name until you see the image with the `:latest` tag.
1. Right-click the image and select **Deploy Image to Azure App Service**.
1. Follow the prompts to select an Azure subscription, select or specify a resource group, specify a region, configure an App Service Plan (B1 is the least expensive), and specify a name for the site. The animation below illustrates the process.
A **Resource Group** is a named collection the different resources that make up an app. By assigning all the app's resources to a single group, you can easily manage those resources as a single unit. (For more information, see the [Azure Resource Manager overview](https://docs.microsoft.com/azure/azure-resource-manager/resource-group-overview) in the Azure documentation.)
An **App Service Plan** defines the physical resources (an underlying virtual machine) that hosts the running container. For this tutorial, B1 is the least expensive plan that supports Docker containers. (For more information, see [App Service plan overview](https://docs.microsoft.com/azure/app-service/azure-web-sites-web-hosting-plans-in-depth-overview) in the Azure documentation.)
The name of the App Service must be unique across all of Azure, so you typically use a company or personal name. For production sites, you typically configure the App Service with a separately registered domain name.
1. Creating the app service takes a few minutes, and you see progress in VS Code's Output panel.
1. Once completed, you **must** also add a setting named `WEBSITES_PORT` (notice the plural "WEBSITES") to the App Service to specify the port on which the container is listening. (If you're using an image from the [Create a Python container in VS Code](https://code.visualstudio.com/docs/python/tutorial-create-containers) tutorial, for example, the port is 5000 for Flask and 8000 for Django ). To set `WEBSITES_PORT`, switch to the **Azure: App Service** explorer, expand the node for your new App Service (refresh if necessary), then right-click **Application Settings** and select **Add New Setting**. At the prompts, enter `WEBSITES_PORT` as the key and the port number for the value.
1. The App Service restarts automatically when you change settings. You can also right-click the App Service and select **Restart** at any time.
1. After the service has restarted, browse the site at `http://<name>.azurewebsites.net`. You can use **Ctrl**+ click (or **Cmd** + click on macOS) on the URL in the Output panel, or right-click the App Service in the **Azure: App Service** explorer and select **Browse Website**.
> [!div class="nextstepaction"]
> [I deployed the image - continue to step 3 >>>](tutorial-deploy-containers-03.md)
Issues? Submit a GitHub issue using the "This page" feedback at the bottom of the page.
| 85.553191 | 690 | 0.768714 | eng_Latn | 0.983168 |
ed21d2ee343bc68fa7d87efb3968b29b055ff042 | 12,167 | md | Markdown | docs/get-started/tutorials/stacklayout/includes/alignment-expansion.md | viveknatarajan/xamarin-docs.fr-fr | e97f4cb64b16aea9d477738420123779c08a793d | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/get-started/tutorials/stacklayout/includes/alignment-expansion.md | viveknatarajan/xamarin-docs.fr-fr | e97f4cb64b16aea9d477738420123779c08a793d | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/get-started/tutorials/stacklayout/includes/alignment-expansion.md | viveknatarajan/xamarin-docs.fr-fr | e97f4cb64b16aea9d477738420123779c08a793d | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
ms.openlocfilehash: d6dbc82e56959399c2befb6a12f0a2cf3793ee5b
ms.sourcegitcommit: 4b402d1c508fa84e4fc3171a6e43b811323948fc
ms.translationtype: HT
ms.contentlocale: fr-FR
ms.lasthandoff: 04/23/2019
ms.locfileid: "61382517"
---
La taille et la position des affichages enfants dans [`StackLayout`](xref:Xamarin.Forms.StackLayout) varient selon les valeurs des propriétés [`HeightRequest`](xref:Xamarin.Forms.VisualElement.HeightRequest) et [`WidthRequest`](xref:Xamarin.Forms.VisualElement.WidthRequest) des affichages enfants et selon les valeurs des propriétés [`HorizontalOptions`](xref:Xamarin.Forms.View.HorizontalOptions) et [`VerticalOptions`](xref:Xamarin.Forms.View.VerticalOptions).
Les propriétés [`HorizontalOptions`](xref:Xamarin.Forms.View.HorizontalOptions) et [`VerticalOptions`](xref:Xamarin.Forms.View.VerticalOptions) peuvent être définies sur des champs à partir de la struct [`LayoutOptions`](xref:Xamarin.Forms.LayoutOptions), qui encapsule deux préférences de mise en page :
- **Alignement** : les préférences d’alignement de l’affichage enfant, qui déterminent sa position et da taille au sein dans sa mise en page parente.
- **Extension** : indique si l’affichage enfant doit utiliser un espace supplémentaire, s’il est disponible (utilisé uniquement par [`StackLayout`](xref:Xamarin.Forms.StackLayout)).
# <a name="visual-studiotabvswin"></a>[Visual Studio](#tab/vswin)
1. Dans **MainPage.xaml**, modifiez la déclaration [`StackLayout`](xref:Xamarin.Forms.StackLayout) pour définir les options d’alignement et d’extension pour chaque [`Label`](xref:Xamarin.Forms.Label) :
```xaml
<StackLayout Margin="20,35,20,25">
<Label Text="Start"
HorizontalOptions="Start"
BackgroundColor="Gray" />
<Label Text="Center"
HorizontalOptions="Center"
BackgroundColor="Gray" />
<Label Text="End"
HorizontalOptions="End"
BackgroundColor="Gray" />
<Label Text="Fill"
HorizontalOptions="Fill"
BackgroundColor="Gray" />
<Label Text="StartAndExpand"
VerticalOptions="StartAndExpand"
BackgroundColor="Gray" />
<Label Text="CenterAndExpand"
VerticalOptions="CenterAndExpand"
BackgroundColor="Gray" />
<Label Text="EndAndExpand"
VerticalOptions="EndAndExpand"
BackgroundColor="Gray" />
<Label Text="FillAndExpand"
VerticalOptions="FillAndExpand"
BackgroundColor="Gray" />
</StackLayout>
```
Ce code définit les préférences d’alignement sur les quatre premières instances [`Label`](xref:Xamarin.Forms.Label) ainsi que les préférences d’extension sur les quatre dernières instances `Label`. Les champs [`Start`](xref:Xamarin.Forms.LayoutOptions.Start), [`Center`](xref:Xamarin.Forms.LayoutOptions.Center), [`End`](xref:Xamarin.Forms.LayoutOptions.End) et [`Fill`](xref:Xamarin.Forms.LayoutOptions.Fill) sont utilisés pour définir l’alignement des instances [`Label`](xref:Xamarin.Forms.Label) dans le [`StackLayout`](xref:Xamarin.Forms.StackLayout) parent. Les champs [`StartAndExpand`](xref:Xamarin.Forms.LayoutOptions.StartAndExpand), [`CenterAndExpand`](xref:Xamarin.Forms.LayoutOptions.CenterAndExpand), [`EndAndExpand`](xref:Xamarin.Forms.LayoutOptions.EndAndExpand) et [`FillAndExpand`](xref:Xamarin.Forms.LayoutOptions.FillAndExpand) sont utilisés pour définir les préférences d’alignement et indiquent si l’affichage occupe plus d’espace que la quantité disponible dans le `StackLayout` parent.
> [!NOTE]
> La valeur par défaut des propriétés [`HorizontalOptions`](xref:Xamarin.Forms.View.HorizontalOptions) et [`VerticalOptions`](xref:Xamarin.Forms.View.VerticalOptions) d’un affichage est [`Fill`](xref:Xamarin.Forms.LayoutOptions.Fill).
1. Dans la barre d’outils Visual Studio, appuyez sur le bouton **Démarrer** (le bouton triangulaire qui ressemble à un bouton de lecture) pour lancer l’application à l’intérieur du simulateur iOS distant ou de l’émulateur Android de votre choix :
[](../images/alignment-expansion-large.png#lightbox "StackLayout contenant des instances Label, avec option d’alignement et d’extension définie")
Un [`StackLayout`](xref:Xamarin.Forms.StackLayout) respecte uniquement les préférences d’alignement sur les affichages enfants qui se trouvent dans la direction opposée à l’orientation `StackLayout`. Par conséquent, les affichages enfants [`Label`](xref:Xamarin.Forms.Label) dans `StackLayout` orienté verticalement définissent leurs propriétés [`HorizontalOptions`](xref:Xamarin.Forms.View.HorizontalOptions) sur l’un des champs d’alignement :
- [`Start`](xref:Xamarin.Forms.LayoutOptions.Start), qui positionne [`Label`](xref:Xamarin.Forms.Label) à gauche de [`StackLayout`](xref:Xamarin.Forms.StackLayout).
- [`Center`](xref:Xamarin.Forms.LayoutOptions.Center), qui centre [`Label`](xref:Xamarin.Forms.Label) dans [`StackLayout`](xref:Xamarin.Forms.StackLayout).
- [`End`](xref:Xamarin.Forms.LayoutOptions.End), qui positionne [`Label`](xref:Xamarin.Forms.Label) à droite de [`StackLayout`](xref:Xamarin.Forms.StackLayout).
- [`Fill`](xref:Xamarin.Forms.LayoutOptions.Fill), qui garantit que [`Label`](xref:Xamarin.Forms.Label) remplit la largeur de [`StackLayout`](xref:Xamarin.Forms.StackLayout).
Un [`StackLayout`](xref:Xamarin.Forms.StackLayout) peut uniquement développer les affichages enfants dans le sens de son orientation. Par conséquent, le `StackLayout` orienté verticalement peut développer les affichages enfants [`Label`](xref:Xamarin.Forms.Label) qui définissent leurs propriétés [`VerticalOptions`](xref:Xamarin.Forms.View.VerticalOptions) sur l’un des champs d’extension. Cela signifie que, pour l’alignement vertical, chaque `Label` occupe la même quantité d’espace dans `StackLayout`. En revanche, seule la dernière instance `Label`, qui définit sa propriété [`VerticalOptions`](xref:Xamarin.Forms.View.VerticalOptions) sur [`FillAndExpand`](xref:Xamarin.Forms.LayoutOptions.FillAndExpand) a une taille différente.
> [!IMPORTANT]
> Lorsque tout l’espace de [`StackLayout`](xref:Xamarin.Forms.StackLayout) est utilisé, les préférences d’extension n’ont aucun effet.
Pour plus d’informations sur l’alignement et l’extension, consultez [Options de mise en page dans Xamarin.Forms](~/xamarin-forms/user-interface/layouts/layout-options.md).
# <a name="visual-studio-for-mactabvsmac"></a>[Visual Studio pour Mac](#tab/vsmac)
1. Dans **MainPage.xaml**, modifiez la déclaration [`StackLayout`](xref:Xamarin.Forms.StackLayout) pour définir les options d’alignement et d’extension pour chaque [`Label`](xref:Xamarin.Forms.Label) :
```xaml
<StackLayout Margin="20,35,20,25">
<Label Text="Start"
HorizontalOptions="Start"
BackgroundColor="Gray" />
<Label Text="Center"
HorizontalOptions="Center"
BackgroundColor="Gray" />
<Label Text="End"
HorizontalOptions="End"
BackgroundColor="Gray" />
<Label Text="Fill"
HorizontalOptions="Fill"
BackgroundColor="Gray" />
<Label Text="StartAndExpand"
VerticalOptions="StartAndExpand"
BackgroundColor="Gray" />
<Label Text="CenterAndExpand"
VerticalOptions="CenterAndExpand"
BackgroundColor="Gray" />
<Label Text="EndAndExpand"
VerticalOptions="EndAndExpand"
BackgroundColor="Gray" />
<Label Text="FillAndExpand"
VerticalOptions="FillAndExpand"
BackgroundColor="Gray" />
</StackLayout>
```
Ce code définit les préférences d’alignement sur les quatre premières instances [`Label`](xref:Xamarin.Forms.Label) ainsi que les préférences d’extension sur les quatre dernières instances `Label`. Les champs [`Start`](xref:Xamarin.Forms.LayoutOptions.Start), [`Center`](xref:Xamarin.Forms.LayoutOptions.Center), [`End`](xref:Xamarin.Forms.LayoutOptions.End) et [`Fill`](xref:Xamarin.Forms.LayoutOptions.Fill) sont utilisés pour définir l’alignement des instances [`Label`](xref:Xamarin.Forms.Label) dans le [`StackLayout`](xref:Xamarin.Forms.StackLayout) parent. Les champs [`StartAndExpand`](xref:Xamarin.Forms.LayoutOptions.StartAndExpand), [`CenterAndExpand`](xref:Xamarin.Forms.LayoutOptions.CenterAndExpand), [`EndAndExpand`](xref:Xamarin.Forms.LayoutOptions.EndAndExpand) et [`FillAndExpand`](xref:Xamarin.Forms.LayoutOptions.FillAndExpand) sont utilisés pour définir les préférences d’alignement et indiquent si l’affichage occupe plus d’espace que la quantité disponible dans le `StackLayout` parent.
> [!NOTE]
> La valeur par défaut des propriétés [`HorizontalOptions`](xref:Xamarin.Forms.View.HorizontalOptions) et [`VerticalOptions`](xref:Xamarin.Forms.View.VerticalOptions) d’un affichage est [`Fill`](xref:Xamarin.Forms.LayoutOptions.Fill).
1. Dans la barre d’outils Visual Studio pour Mac, appuyez sur le bouton **Démarrer** (le bouton triangulaire qui ressemble à un bouton de lecture) pour lancer l’application dans le simulateur iOS ou dans l’émulateur Android de votre choix :
[](../images/alignment-expansion-large.png#lightbox "StackLayout contenant des instances Label, avec option d’alignement et d’extension définie")
Un [`StackLayout`](xref:Xamarin.Forms.StackLayout) respecte uniquement les préférences d’alignement sur les affichages enfants qui se trouvent dans la direction opposée à l’orientation `StackLayout`. Par conséquent, les affichages enfants [`Label`](xref:Xamarin.Forms.Label) dans `StackLayout` orienté verticalement définissent leurs propriétés [`HorizontalOptions`](xref:Xamarin.Forms.View.HorizontalOptions) sur l’un des champs d’alignement :
- [`Start`](xref:Xamarin.Forms.LayoutOptions.Start), qui positionne [`Label`](xref:Xamarin.Forms.Label) à gauche de [`StackLayout`](xref:Xamarin.Forms.StackLayout).
- [`Center`](xref:Xamarin.Forms.LayoutOptions.Center), qui centre [`Label`](xref:Xamarin.Forms.Label) dans [`StackLayout`](xref:Xamarin.Forms.StackLayout).
- [`End`](xref:Xamarin.Forms.LayoutOptions.End), qui positionne [`Label`](xref:Xamarin.Forms.Label) à droite de [`StackLayout`](xref:Xamarin.Forms.StackLayout).
- [`Fill`](xref:Xamarin.Forms.LayoutOptions.Fill), qui garantit que [`Label`](xref:Xamarin.Forms.Label) remplit la largeur de [`StackLayout`](xref:Xamarin.Forms.StackLayout).
Un [`StackLayout`](xref:Xamarin.Forms.StackLayout) peut uniquement développer les affichages enfants dans le sens de son orientation. Par conséquent, le `StackLayout` orienté verticalement peut développer les affichages enfants [`Label`](xref:Xamarin.Forms.Label) qui définissent leurs propriétés [`VerticalOptions`](xref:Xamarin.Forms.View.VerticalOptions) sur l’un des champs d’extension. Cela signifie que, pour l’alignement vertical, chaque `Label` occupe la même quantité d’espace dans `StackLayout`. En revanche, seule la dernière instance `Label`, qui définit sa propriété [`VerticalOptions`](xref:Xamarin.Forms.View.VerticalOptions) sur [`FillAndExpand`](xref:Xamarin.Forms.LayoutOptions.FillAndExpand) a une taille différente.
> [!IMPORTANT]
> Lorsque tout l’espace de [`StackLayout`](xref:Xamarin.Forms.StackLayout) est utilisé, les préférences d’extension n’ont aucun effet.
Pour plus d’informations sur l’alignement et l’extension, consultez [Options de mise en page dans Xamarin.Forms](~/xamarin-forms/user-interface/layouts/layout-options.md).
| 95.80315 | 1,013 | 0.743404 | fra_Latn | 0.714417 |
ed22186000c52fafabfe0293d49f4286cb8e72fc | 291 | md | Markdown | README.md | kylewm/quiettime | 51eb82d60d38f5ad9bccaffbb490c8467a758acf | [
"CC0-1.0"
] | 5 | 2016-05-04T13:32:11.000Z | 2016-06-13T16:41:19.000Z | README.md | kylewm/quiettime | 51eb82d60d38f5ad9bccaffbb490c8467a758acf | [
"CC0-1.0"
] | 1 | 2016-10-10T06:57:42.000Z | 2016-10-10T14:50:16.000Z | README.md | kylewm/quiettime | 51eb82d60d38f5ad9bccaffbb490c8467a758acf | [
"CC0-1.0"
] | 1 | 2020-01-09T21:30:20.000Z | 2020-01-09T21:30:20.000Z | # Quiet Time
Mute Twitter friends with an automatic unmute after a little while
# License
Source code is released into the public domain under CC0 (see LICENSE for details).
Yoga pose icon is licensed under the iconfinder.com [Basic License](https://www.iconfinder.com/licenses/basic).
| 26.454545 | 111 | 0.783505 | eng_Latn | 0.983592 |
ed231b5e4aee8e65c888fe68eb374b02f376e8ed | 679 | md | Markdown | docs/api/@remirror/core/core.extension.inputrules.md | jankeromnes/remirror | 95306cee4c76ee9fd7271a0ab6069f0a0a6803d9 | [
"MIT"
] | 1 | 2021-05-22T06:22:01.000Z | 2021-05-22T06:22:01.000Z | docs/api/@remirror/core/core.extension.inputrules.md | jankeromnes/remirror | 95306cee4c76ee9fd7271a0ab6069f0a0a6803d9 | [
"MIT"
] | null | null | null | docs/api/@remirror/core/core.extension.inputrules.md | jankeromnes/remirror | 95306cee4c76ee9fd7271a0ab6069f0a0a6803d9 | [
"MIT"
] | null | null | null | <!-- Do not edit this file. It is automatically generated by API Documenter. -->
[Home](./index.md) > [@remirror/core](./core.md) > [Extension](./core.extension.md) > [inputRules](./core.extension.inputrules.md)
## Extension.inputRules() method
Register input rules which are activated if the regex matches as a user is typing.
<b>Signature:</b>
```typescript
inputRules?(params: ExtensionManagerTypeParams<GType>): InputRule[];
```
## Parameters
| Parameter | Type | Description |
| --- | --- | --- |
| params | <code>ExtensionManagerTypeParams<GType></code> | schema params with type included |
<b>Returns:</b>
`InputRule[]`
| 27.16 | 140 | 0.662739 | eng_Latn | 0.781395 |
ed2356e5a8614fbc954c4c8f86dcb5017dc26029 | 17,839 | md | Markdown | windows-apps-src/xaml-platform/x-bind-markup-extension.md | vladimp/windows-uwp | 0f1bf8e1aa56cb4b9ad70c437224ada5e46a1d5a | [
"CC-BY-4.0",
"MIT"
] | null | null | null | windows-apps-src/xaml-platform/x-bind-markup-extension.md | vladimp/windows-uwp | 0f1bf8e1aa56cb4b9ad70c437224ada5e46a1d5a | [
"CC-BY-4.0",
"MIT"
] | null | null | null | windows-apps-src/xaml-platform/x-bind-markup-extension.md | vladimp/windows-uwp | 0f1bf8e1aa56cb4b9ad70c437224ada5e46a1d5a | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
author: jwmsft
description: The xBind markup extension is a high performance alternative to Binding. xBind - new for Windows 10 - runs in less time and less memory than Binding and supports better debugging.
title: xBind markup extension
ms.assetid: 529FBEB5-E589-486F-A204-B310ACDC5C06
ms.author: jimwalk
ms.date: 02/08/2017
ms.topic: article
keywords: windows 10, uwp
ms.localizationpriority: medium
---
# {x:Bind} markup extension
**Note** For general info about using data binding in your app with **{x:Bind}** (and for an all-up comparison between **{x:Bind}** and **{Binding}**), see [Data binding in depth](https://msdn.microsoft.com/library/windows/apps/mt210946).
The **{x:Bind}** markup extension—new for Windows 10—is an alternative to **{Binding}**. **{x:Bind}** runs in less time and less memory than **{Binding}** and supports better debugging.
At XAML compile time, **{x:Bind}** is converted into code that will get a value from a property on a data source, and set it on the property specified in markup. The binding object can optionally be configured to observe changes in the value of the data source property and refresh itself based on those changes (`Mode="OneWay"`). It can also optionally be configured to push changes in its own value back to the source property (`Mode="TwoWay"`).
The binding objects created by **{x:Bind}** and **{Binding}** are largely functionally equivalent. But **{x:Bind}** executes special-purpose code, which it generates at compile-time, and **{Binding}** uses general-purpose runtime object inspection. Consequently, **{x:Bind}** bindings (often referred-to as compiled bindings) have great performance, provide compile-time validation of your binding expressions, and support debugging by enabling you to set breakpoints in the code files that are generated as the partial class for your page. These files can be found in your `obj` folder, with names like (for C#) `<view name>.g.cs`.
> [!TIP]
> **{x:Bind}** has a default mode of **OneTime**, unlike **{Binding}**, which has a default mode of **OneWay**. This was chosen for performance reasons, as using **OneWay** causes more code to be generated to hookup and handle change detection. You can explicitly specify a mode to use OneWay or TwoWay binding. You can also use [x:DefaultBindMode](x-defaultbindmode-attribute.md) to change the default mode for **{x:Bind}** for a specific segment of the markup tree. The specified mode applies to any **{x:Bind}** expressions on that element and its children, that do not explicitly specify a mode as part of the binding.
**Sample apps that demonstrate {x:Bind}**
- [{x:Bind} sample](http://go.microsoft.com/fwlink/p/?linkid=619989)
- [QuizGame](https://github.com/Microsoft/Windows-appsample-quizgame)
- [XAML UI Basics sample](http://go.microsoft.com/fwlink/p/?linkid=619992)
## XAML attribute usage
``` syntax
<object property="{x:Bind}" .../>
-or-
<object property="{x:Bind propertyPath}" .../>
-or-
<object property="{x:Bind bindingProperties}" .../>
-or-
<object property="{x:Bind propertyPath, bindingProperties}" .../>
-or-
<object property="{x:Bind pathToFunction.functionName(functionParameter1, functionParameter2, ...), bindingProperties}" .../>
```
| Term | Description |
|------|-------------|
| _propertyPath_ | A string that specifies the property path for the binding. More info is in the [Property path](#property-path) section below. |
| _bindingProperties_ |
| _propName_=_value_\[, _propName_=_value_\]* | One or more binding properties that are specified using a name/value pair syntax. |
| _propName_ | The string name of the property to set on the binding object. For example, "Converter". |
| _value_ | The value to set the property to. The syntax of the argument depends on the property being set. Here's an example of a _propName_=_value_ usage where the value is itself a markup extension: `Converter={StaticResource myConverterClass}`. For more info, see [Properties that you can set with {x:Bind}](#properties-you-can-set) section below. |
## Examples
```XAML
<Page x:Class="QuizGame.View.HostView" ... >
<Button Content="{x:Bind Path=ViewModel.NextButtonText, Mode=OneWay}" ... />
</Page>
```
This example XAML uses **{x:Bind}** with a **ListView.ItemTemplate** property. Note the declaration of an **x:DataType** value.
```XAML
<DataTemplate x:Key="SimpleItemTemplate" x:DataType="data:SampleDataGroup">
<StackPanel Orientation="Vertical" Height="50">
<TextBlock Text="{x:Bind Title}"/>
<TextBlock Text="{x:Bind Description}"/>
</StackPanel>
</DataTemplate>
```
## Property path
*PropertyPath* sets the **Path** for an **{x:Bind}** expression. **Path** is a property path specifying the value of the property, sub-property, field, or method that you're binding to (the source). You can mention the name of the **Path** property explicitly: `{Binding Path=...}`. Or you can omit it: `{Binding ...}`.
### Property path resolution
**{x:Bind}** does not use the **DataContext** as a default source—instead, it uses the page or user control itself. So it will look in the code-behind of your page or user control for properties, fields, and methods. To expose your view model to **{x:Bind}**, you will typically want to add new fields or properties to the code behind for your page or user control. Steps in a property path are delimited by dots (.), and you can include multiple delimiters to traverse successive sub-properties. Use the dot delimiter regardless of the programming language used to implement the object being bound to.
For example: in a page, **Text="{x:Bind Employee.FirstName}"** will look for an **Employee** member on the page and then a **FirstName** member on the object returned by **Employee**. If you are binding an items control to a property that contains an employee's dependents, your property path might be "Employee.Dependents", and the item template of the items control would take care of displaying the items in "Dependents".
For C++/CX, **{x:Bind}** cannot bind to private fields and properties in the page or data model – you will need to have a public property for it to be bindable. The surface area for binding needs to be exposed as CX classes/interfaces so that we can get the relevant metadata. The **\[Bindable\]** attribute should not be needed.
With **x:Bind**, you do not need to use **ElementName=xxx** as part of the binding expression. Instead, you can use the name of the element as the first part of the path for the binding because named elements become fields within the page or user control that represents the root binding source.
### Collections
If the data source is a collection, then a property path can specify items in the collection by their position or index. For example, "Teams\[0\].Players", where the literal "\[\]" encloses the "0" that requests the first item in a zero-indexed collection.
To use an indexer, the model needs to implement **IList<T>** or **IVector<T>** on the type of the property that is going to be indexed. If the type of the indexed property supports **INotifyCollectionChanged** or **IObservableVector** and the binding is OneWay or TwoWay, then it will register and listen for change notifications on those interfaces. The change detection logic will update based on all collection changes, even if that doesn’t affect the specific indexed value. This is because the listening logic is common across all instances of the collection.
If the data source is a Dictionary or Map, then a property path can specify items in the collection by their string name. For example **<TextBlock Text="{x:Bind Players\['John Smith'\]" />** will look for an item in the dictionary named "John Smith". The name needs to be enclosed in quotes, and either single or double quotes can be used. Hat (^) can be used to escape quotes in strings. Its usually easiest to use alternate quotes from those used for the XAML attribute.
To use an string indexer, the model needs to implement **IDictionary<string, T>** or **IMap<string, T>** on the type of the property that is going to be indexed. If the type of the indexed property supports **IObservableMap** and the binding is OneWay or TwoWay, then it will register and listen for change notifications on those interfaces. The change detection logic will update based on all collection changes, even if that doesn’t affect the specific indexed value. This is because the listening logic is common across all instances of the collection.
### Attached Properties
To bind to attached properties, you need to put the class and property name into parentheses after the dot. For example **Text="{x:Bind Button22.(Grid.Row)}"**. If the property is not declared in a Xaml namespace, then you will need to prefix it with a xml namespace, which you should map to a code namespace at the head of the document.
### Casting
Compiled bindings are strongly typed, and will resolve the type of each step in a path. If the type returned doesn’t have the member, it will fail at compile time. You can specify a cast to tell binding the real type of the object. In the following case, **obj** is a property of type object, but contains a text box, so we can use either **Text="{x:Bind ((TextBox)obj).Text}"** or **Text="{x:Bind obj.(TextBox.Text)}"**.
The **groups3** field in **Text="{x:Bind ((data:SampleDataGroup)groups3\[0\]).Title}"** is a dictionary of objects, so you must cast it to **data:SampleDataGroup**. Note the use of the xml **data:** namespace prefix for mapping the object type to a code namespace that isn't part of the default XAML namespace.
_Note: The C#-style cast syntax is more flexible than the attached property syntax, and is the recommended syntax going forward._
## Functions in binding paths
Starting in Windows 10, version 1607, **{x:Bind}** supports using a function as the leaf step of the binding path. This is a powerful feature for databinding that enables several scenarios in markup. See [function bindings](../data-binding/function-bindings.md) for details.
## Event Binding
Event binding is a unique feature for compiled binding. It enables you to specify the handler for an event using a binding, rather than it having to be a method on the code behind. For example: **Click="{x:Bind rootFrame.GoForward}"**.
For events, the target method must not be overloaded and must also:
- Match the signature of the event.
- OR have no parameters.
- OR have the same number of parameters of types that are assignable from the types of the event parameters.
In generated code-behind, compiled binding handles the event and routes it to the method on the model, evaluating the path of the binding expression when the event occurs. This means that, unlike property bindings, it doesn’t track changes to the model.
For more info about the string syntax for a property path, see [Property-path syntax](property-path-syntax.md), keeping in mind the differences described here for **{x:Bind}**.
## Properties that you can set with {x:Bind}
**{x:Bind}** is illustrated with the *bindingProperties* placeholder syntax because there are multiple read/write properties that can be set in the markup extension. The properties can be set in any order with comma-separated *propName*=*value* pairs. Note that you cannot include line breaks in the binding expression. Some of the properties require types that don't have a type conversion, so these require markup extensions of their own nested within the **{x:Bind}**.
These properties work in much the same way as the properties of the [**Binding**](https://msdn.microsoft.com/library/windows/apps/br209820) class.
| Property | Description |
|----------|-------------|
| **Path** | See the [Property path](#property-path) section above. |
| **Converter** | Specifies the converter object that is called by the binding engine. The converter can be set in XAML, but only if you refer to an object instance that you've assigned in a [{StaticResource} markup extension](staticresource-markup-extension.md) reference to that object in the resource dictionary. |
| **ConverterLanguage** | Specifies the culture to be used by the converter. (If you're setting **ConverterLanguage** you should also be setting **Converter**.) The culture is set as a standards-based identifier. For more info, see [**ConverterLanguage**](https://msdn.microsoft.com/library/windows/apps/hh701880). |
| **ConverterParameter** | Specifies the converter parameter that can be used in converter logic. (If you're setting **ConverterParameter** you should also be setting **Converter**.) Most converters use simple logic that get all the info they need from the passed value to convert, and don't need a **ConverterParameter** value. The **ConverterParameter** parameter is for moderately advanced converter implementations that have more than one logic that keys off what's passed in **ConverterParameter**. You can write a converter that uses values other than strings but this is uncommon, see Remarks in [**ConverterParameter**](https://msdn.microsoft.com/library/windows/apps/br209827) for more info. |
| **FallbackValue** | Specifies a value to display when the source or path cannot be resolved. |
| **Mode** | Specifies the binding mode, as one of these strings: "OneTime", "OneWay", or "TwoWay". The default is "OneTime". Note that this differs from the default for **{Binding}**, which is "OneWay" in most cases. |
| **TargetNullValue** | Specifies a value to display when the source value resolves but is explicitly **null**. |
| **BindBack** | Specifies a function to use for the reverse direction of a two-way binding. |
| **UpdateSourceTrigger** | Specifies when to push changes back from the control to the model in TwoWay bindings. The default for all properties except TextBox.Text is PropertyChanged, TextBox.Text is LostFocus.|
> [!NOTE]
> If you're converting markup from **{Binding}** to **{x:Bind}**, then be aware of the differences in default values for the **Mode** property.
> [**x:DefaultBindMode**](https://docs.microsoft.com/windows/uwp/xaml-platform/x-defaultbindmode-attribute) can be used to change the default mode for x:Bind for a specific segment of the markup tree. The mode selected will apply any x:Bind expressions on that element and its children, that do not explicitly specify a mode as part of the binding. OneTime is more performant than OneWay as using OneWay will cause more code to be generated to hookup and handle the change detection.
## Remarks
Because **{x:Bind}** uses generated code to achieve its benefits, it requires type information at compile time. This means that you cannot bind to properties where you do not know the type ahead of time. Because of this, you cannot use **{x:Bind}** with the **DataContext** property, which is of type **Object**, and is also subject to change at run time.
When using **{x:Bind}** with data templates, you must indicate the type being bound to by setting an **x:DataType** value, as shown in the example below. You can also set the type to an interface or base class type, and then use casts if necessary to formulate a full expression.
Compiled bindings depend on code generation. So if you use **{x:Bind}** in a resource dictionary then the resource dictionary needs to have a code-behind class. See [Resource dictionaries with {x:Bind}](../data-binding/data-binding-in-depth.md#resource-dictionaries-with-x-bind) for a code example.
Pages and user controls that include Compiled bindings will have a "Bindings" property in the generated code. This includes the following methods:
- **Update()** - This will update the values of all compiled bindings. Any one-way/Two-Way bindings will have the listeners hooked up to detect changes.
- **Initialize()** - If the bindings have not already been initialized, then it will call Update() to initialize the bindings
- **StopTracking()** - This will unhook all listeners created for one-way and two-way bindings. They can be re-initialized using the Update() method.
> [!NOTE]
> Starting in Windows 10, version 1607, the XAML framework provides a built in Boolean to Visibility converter. The converter maps **true** to the **Visible** enumeration value and **false** to **Collapsed** so you can bind a Visibility property to a Boolean without creating a converter. Note that this is not a feature of function binding, only property binding. To use the built in converter, your app's minimum target SDK version must be 14393 or later. You can't use it when your app targets earlier versions of Windows 10. For more info about target versions, see [Version adaptive code](https://msdn.microsoft.com/windows/uwp/debug-test-perf/version-adaptive-code).
**Tip** If you need to specify a single curly brace for a value, such as in [**Path**](https://msdn.microsoft.com/library/windows/apps/br209830) or [**ConverterParameter**](https://msdn.microsoft.com/library/windows/apps/br209827), precede it with a backslash: `\{`. Alternatively, enclose the entire string that contains the braces that need escaping in a secondary quotation set, for example `ConverterParameter='{Mix}'`.
[**Converter**](https://msdn.microsoft.com/library/windows/apps/br209826), [**ConverterLanguage**](https://msdn.microsoft.com/library/windows/apps/hh701880) and **ConverterLanguage** are all related to the scenario of converting a value or type from the binding source into a type or value that is compatible with the binding target property. For more info and examples, see the "Data conversions" section of [Data binding in depth](https://msdn.microsoft.com/library/windows/apps/mt210946).
**{x:Bind}** is a markup extension only, with no way to create or manipulate such bindings programmatically. For more info about markup extensions, see [XAML overview](xaml-overview.md).
| 101.937143 | 702 | 0.756545 | eng_Latn | 0.996747 |
ed247ea95664df81f24c84c21071516102fced0d | 2,055 | md | Markdown | snippets/bouncing-loader.md | webop/30-seconds-of-css | 2bd18cb876116719199b091d69d7076f0678021e | [
"CC0-1.0"
] | 2 | 2018-10-19T00:38:32.000Z | 2020-08-04T02:41:07.000Z | snippets/bouncing-loader.md | webop/30-seconds-of-css | 2bd18cb876116719199b091d69d7076f0678021e | [
"CC0-1.0"
] | null | null | null | snippets/bouncing-loader.md | webop/30-seconds-of-css | 2bd18cb876116719199b091d69d7076f0678021e | [
"CC0-1.0"
] | 2 | 2020-01-06T11:32:22.000Z | 2020-03-31T03:16:59.000Z | ### Bouncing loader
Creates a bouncing loader animation.
#### HTML
```html
<div class="bouncing-loader">
<div></div>
<div></div>
<div></div>
</div>
```
#### CSS
```css
@keyframes bouncing-loader {
from {
opacity: 1;
transform: translateY(0);
}
to {
opacity: 0.1;
transform: translateY(-1rem);
}
}
.bouncing-loader {
display: flex;
justify-content: center;
}
.bouncing-loader > div {
width: 1rem;
height: 1rem;
margin: 3rem 0.2rem;
background: #8385aa;
border-radius: 50%;
animation: bouncing-loader 0.6s infinite alternate;
}
.bouncing-loader > div:nth-child(2) {
animation-delay: 0.2s;
}
.bouncing-loader > div:nth-child(3) {
animation-delay: 0.4s;
}
```
#### Demo
#### Explanation
Note: `1rem` is usually `16px`.
1. `@keyframes` defines an animation that has two states, where the element changes `opacity` and is translated up on the 2D plane using `transform: translateY()`.
2. `.bouncing-loader` is the parent container of the bouncing circles and uses `display: flex`
and `justify-content: center` to position them in the center.
3. `.bouncing-loader > div`, targets the three child `div`s of the parent to be styled. The `div`s are given a width and height of `1rem`, using `border-radius: 50%` to turn them from squares to circles.
4. `margin: 3rem 0.2rem` specifies that each circle has a top/bottom margin of `3rem` and left/right margin
of `0.2rem` so that they do not directly touch each other, giving them some breathing room.
5. `animation` is a shorthand property for the various animation properties: `animation-name`, `animation-duration`, `animation-iteration-count`, `animation-direction` are used.
6. `nth-child(n)` targets the element which is the nth child of its parent.
7. `animation-delay` is used on the second and third `div` respectively, so that each element does not start the animation at the same time.
#### Browser support
<span class="snippet__support-note">✅ No caveats.</span>
- https://caniuse.com/#feat=css-animation
<!-- tags: animation -->
| 26.688312 | 203 | 0.698297 | eng_Latn | 0.966626 |
ed24b3638aebe018006b0eafa892d32b87082917 | 4,466 | md | Markdown | articles/openshift/oshift-ref-deploy-app-into-service-mesh.md | dtomkinscloud/documentation | 99c7eb6697e6864b0c547e49973bef4bfd45651f | [
"MIT"
] | 12 | 2019-03-08T09:58:48.000Z | 2021-11-08T14:45:59.000Z | articles/openshift/oshift-ref-deploy-app-into-service-mesh.md | dtomkinscloud/documentation | 99c7eb6697e6864b0c547e49973bef4bfd45651f | [
"MIT"
] | 999 | 2018-07-26T10:29:32.000Z | 2022-03-31T13:02:26.000Z | articles/openshift/oshift-ref-deploy-app-into-service-mesh.md | dtomkinscloud/documentation | 99c7eb6697e6864b0c547e49973bef4bfd45651f | [
"MIT"
] | 56 | 2018-07-20T11:42:16.000Z | 2022-03-02T14:51:40.000Z | ---
title: Deploying an application into OpenShift Service Mesh
description:
services: openshift
author: Andrew Garner
reviewer: Andrew Garner
lastreviewed: 13/07/2021
toc_rootlink: Reference
toc_sub1: OpenShift v4.x
toc_sub2:
toc_sub3:
toc_sub4:
toc_title: Deploying an application into OpenShift Service Mesh
toc_fullpath: Reference/v4/oshift-ref-deploy-app-into-service-mesh.md
toc_mdlink: oshift-ref-deploy-app-into-service-mesh.md
---
# Deploying an application into OpenShift Service Mesh
## Overview
Red Hat OpenShift Service Mesh (OSM) provides an easy way to create a network of deployed services that provides discovery, load balancing, service-to-service authentication, failure recovery, metrics and monitoring. OSM is based on the open source [Istio](https://istio.io/) project.
This article explains how to deploy a cloud-native sample application into OSM and highlights some key differences with using OSM compared to Istio.
### Intended audience
This article is intended for teams familiar with OpenShift, microservices and the service mesh concept who are preparing to deploy microservices into OpenShift Service Mesh.
### Prerequisites
- Familiarity with the concepts involved in a Service Mesh.
- The OpenShift Service Mesh (OSM) Operator is installed into your OpenShift cluster. See the [OpenShift documentation](https://docs.openshift.com/container-platform/4.7/service_mesh/v2x/preparing-ossm-installation.html) for an installation guide.
- The istio-system project exists and the target project for the sample application deployment has been added to the OSM `ServiceMeshMemberRole` configuration.
## Preparing services for deployment
### Sidecar injection
The OSM uses the same Envoy proxy sidecar container as Istio does to manage traffic within the service mesh. OSM requires deployments to specify the annotation `sidecar.istio.io/inject: "true"` to opt-in to the sidecar injection.
### Traffic ingress
Incoming traffic must enter the Service Mesh via a route that the Service Mesh has created. A route will be automatically created for every instance of a gateway. Replace any explicit route creation with gateways.
When using the istio-system as a multi-tenant control plane, each ingress needs a VirtualService instance, which defines the traffic routing at the point of ingress. As a minimum, the traffic must be routed to the correct VirtualService based on the traffic's incoming DNS name.
### Services
Kiali can access the Service Mesh components configuration and will report on configuration errors. While not required for functionality, all services should be labelled and ports should have a name and protocol defined to avoid Kiali reporting configuration errors.
### Internal traffic routing
Destination rules for each service must exist for traffic to be routed to the pods. In the most basic example, all traffic is routed to all pods in a service. The destination rules typically use the version label on pods to route traffic accordingly.
### Pods
Pods must have specific labels for Pilot to manage traffic routing and for Kiali to display the service mesh correctly. Pods must have metadata labels called `app` and `version`, which identify the microservice application and the version of the application code running in the pod.
## Example application
Weaveworks has a sample microservice-based application called the Sock Shop that UKCloud has modified to run inside OSM v1. See the sample code on GitHub at https://github.com/UKCloud/sock-shop-service-mesh.
With the release of OSM v2, Red Hat has documented how to install a sample application into OSM v2. You can find more details in the [Red Hat Service Mesh documentation](https://docs.openshift.com/container-platform/4.7/service_mesh/v2x/ossm-create-mesh.html#ossm-tutorial-bookinfo-overview_ossm-create-mesh).
## References
- Weaveworks Sock Shop project - https://microservices-demo.github.io/
- UKCloud Sock Shop for OSM v1 - https://github.com/UKCloud/sock-shop-service-mesh
- Deploying applications on Red Hat OpenShift Service Mesh v2 - https://docs.openshift.com/container-platform/4.7/service_mesh/v2x/ossm-create-mesh.html
## Feedback
If you find a problem with this article, click **Improve this Doc** to make the change yourself or raise an [issue](https://github.com/UKCloud/documentation/issues) in GitHub. If you have an idea for how we could improve any of our services, send an email to <[email protected]>.
| 55.825 | 309 | 0.802284 | eng_Latn | 0.989977 |
ed2583da2c5470a3be3d1991341149efc6e7f20a | 717 | md | Markdown | questions/0073.md | ova777/zce | a20f9c68d0500d0fb29234da39e731d9c14ff38c | [
"MIT"
] | null | null | null | questions/0073.md | ova777/zce | a20f9c68d0500d0fb29234da39e731d9c14ff38c | [
"MIT"
] | null | null | null | questions/0073.md | ova777/zce | a20f9c68d0500d0fb29234da39e731d9c14ff38c | [
"MIT"
] | null | null | null | [<<< Previous question <<<](0072.md) Question ID#0073.md [>>> Next question >>>](0074.md)
Consider the following PHP script:
```php
$base_array = array("red", "green", "yellow", "white");
$replacements_array = array(0 => "orange", 4 => "blue");
$result = array_replace($base_array, $replacements_array);
print_r($result);
```
What will be the output of the script?
- [x] A
```php
Array ( [0] => orange [1] => green [2] => yellow [3] => white [4] => blue )
```
- [ ] B
```php
# Script will throw an error message.
```
- [ ] C
```php
Array ( [0] => blue [1] => white [2] => yellow [3] => green [4] => orange )
```
- [ ] D
```php
Array ( [0] => yellow [1] => white [2] => blue [3] => green [4] => orange )
```
| 22.40625 | 92 | 0.559275 | eng_Latn | 0.810366 |
ed25adfc9e25b6461163f03cb6c73832d573a7ab | 816 | md | Markdown | _feats/snap-shot.md | tynansdtm/pathminder.github.io | 9a0cb763af82c13804def4197e0535ee54453581 | [
"OML",
"RSA-MD"
] | 8 | 2016-07-24T04:27:04.000Z | 2019-10-03T21:31:23.000Z | _feats/snap-shot.md | tynansdtm/pathminder.github.io | 9a0cb763af82c13804def4197e0535ee54453581 | [
"OML",
"RSA-MD"
] | 11 | 2016-07-11T11:41:13.000Z | 2022-02-26T02:55:19.000Z | _feats/snap-shot.md | tynansdtm/pathminder.github.io | 9a0cb763af82c13804def4197e0535ee54453581 | [
"OML",
"RSA-MD"
] | 8 | 2016-04-03T17:58:13.000Z | 2020-08-01T03:01:11.000Z | ---
title: Snap Shot
tags:
- Combat
sources:
- Pathfinder Roleplaying Game Ultimate Combat
flavor_text: With a ranged weapon, you can take advantage of any opening in your opponent's defenses.
prerequisites:
- Dex 13
- "[Point-Blank Shot](/feats/point-blank-shot/)"
- "[Rapid Shot](/feats/rapid-shot/)"
- "[Weapon Focus](/feats/weapon-focus/)"
- base attack bonus +6
benefit: |
While wielding a ranged weapon with which you have [Weapon Focus](/feats/weapon-focus/), you threaten squares within 5 feet of you. You can make attacks of opportunity with that ranged weapon. You do not provoke attacks of opportunity when making a ranged attack as an attack of opportunity.
normal: |
While wielding a ranged weapon, you threaten no squares and can make no attacks of opportunity with that weapon.
---
| 40.8 | 293 | 0.743873 | eng_Latn | 0.99518 |
ed25ca00e6acafbafe2fdb5694979330c0754969 | 138 | md | Markdown | ed/f/less/README.md | cn007b/stash | bae604d3056f09b9b6c6b3e0282f02c829801f5c | [
"MIT"
] | null | null | null | ed/f/less/README.md | cn007b/stash | bae604d3056f09b9b6c6b3e0282f02c829801f5c | [
"MIT"
] | null | null | null | ed/f/less/README.md | cn007b/stash | bae604d3056f09b9b6c6b3e0282f02c829801f5c | [
"MIT"
] | 1 | 2021-11-26T05:40:08.000Z | 2021-11-26T05:40:08.000Z | less (CSS pre-processor)
-
````sh
node_modules/less/bin/lessc ./web/static/less/style.less > ./web/static/css/style.css --clean-css
````
| 19.714286 | 97 | 0.688406 | eng_Latn | 0.203181 |
ed277b77014654affd19573b65b0ea048180ec4d | 14,473 | md | Markdown | articles/notification-hubs/notification-hubs-windows-store-dotnet-get-started-wns-push-notification.md | jglixon/azure-content | c2efc0483bfaaf14e3f8eb9a4d8545854023f625 | [
"CC-BY-3.0"
] | 1 | 2018-07-19T04:45:17.000Z | 2018-07-19T04:45:17.000Z | articles/notification-hubs/notification-hubs-windows-store-dotnet-get-started-wns-push-notification.md | jglixon/azure-content | c2efc0483bfaaf14e3f8eb9a4d8545854023f625 | [
"CC-BY-3.0"
] | null | null | null | articles/notification-hubs/notification-hubs-windows-store-dotnet-get-started-wns-push-notification.md | jglixon/azure-content | c2efc0483bfaaf14e3f8eb9a4d8545854023f625 | [
"CC-BY-3.0"
] | 1 | 2019-09-26T15:53:25.000Z | 2019-09-26T15:53:25.000Z | <properties
pageTitle="Get started with Azure Notification Hubs for Windows Universal Platform Apps | Microsoft Azure"
description="In this tutorial, you learn how to use Azure Notification Hubs to push notifications to a Windows Universal Platform application."
services="notification-hubs"
documentationCenter="windows"
authors="wesmc7777"
manager="erikre"
editor="erikre"/>
<tags
ms.service="notification-hubs"
ms.workload="mobile"
ms.tgt_pltfrm="mobile-windows"
ms.devlang="dotnet"
ms.topic="hero-article"
ms.date="07/21/2016"
ms.author="wesmc"/>
# Getting started with Notification Hubs for Windows Universal Platform Apps
[AZURE.INCLUDE [notification-hubs-selector-get-started](../../includes/notification-hubs-selector-get-started.md)]
##Overview
This tutorial shows you how to use Azure Notification Hubs to send push notifications to a Universal Windows Platform (UWP) app.
In this tutorial, you create a blank Windows Store app that receives push notifications by using the Windows Push Notification Service (WNS). When you're finished, you'll be able to use your notification hub to broadcast push notifications to all the devices running your app.
## Before you begin
[AZURE.INCLUDE [notification-hubs-hero-slug](../../includes/notification-hubs-hero-slug.md)]
The completed code for this tutorial can be found on GitHub [here](https://github.com/Azure/azure-notificationhubs-samples/tree/master/dotnet/GetStartedWindowsUniversal).
##Prerequisites
This tutorial requires the following:
+ [Microsoft Visual Studio Community 2015](https://www.visualstudio.com/products/visual-studio-community-vs) or later
+ [Universal Windows App Development Tools installed](https://msdn.microsoft.com/windows/uwp/get-started/get-set-up)
+ An active Azure account <br/>If you don't have an account, you can create a free trial account in just a couple of minutes. For details, see [Azure Free Trial](https://azure.microsoft.com/pricing/free-trial/?WT.mc_id=A0E0E5C02&returnurl=http%3A%2F%2Fazure.microsoft.com%2Fen-us%2Fdocumentation%2Farticles%2Fnotification-hubs-windows-store-dotnet-get-started%2F).
+ An active Windows Store account
Completing this tutorial is a prerequisite for all other Notification Hubs tutorials for Windows Universal Platform apps.
##Register your app for the Windows Store
To send push notifications to UWP apps, you must associate your app to the Windows Store. You must then configure your notification hub to integrate with WNS.
1. If you have not already registered your app, navigate to the [Windows Dev Center](https://dev.windows.com/overview), sign in with your Microsoft account, and then click **Create a new app**.
2. Type a name for your app and click **Reserve app name**.
This creates a new Windows Store registration for your app.
3. In Visual Studio, create a new Visual C# Store Apps project by using the **Blank App** template and click **OK**.
4. Accept the defaults for the target and minimum platform versions.
5. In Solution Explorer, right-click the Windows Store app project, click **Store**, and then click **Associate App with the Store...**.
The **Associate Your App with the Windows Store** wizard appears.
6. In the wizard, click **Sign in** and then sign in with your Microsoft account.
7. Click the app that you registered in step 2, click **Next**, and then click **Associate**.
This adds the required Windows Store registration information to the application manifest.
8. Back on the [Windows Dev Center](http://go.microsoft.com/fwlink/p/?LinkID=266582) page for your new app, click **Services**, click **Push notifications**, and then click **Live Services site** under **Windows Push Notification Services (WNS) and Microsoft Azure Mobile Apps**.
9. On the registration page for your app, make a note of the **Application Secret** password and the **Package security identifier (SID)** located in the **Windows Store** platform settings.
> [AZURE.WARNING]
The application secret and package SID are important security credentials. Do not share these values with anyone or distribute them with your app.
##Configure your notification hub
[AZURE.INCLUDE [notification-hubs-portal-create-new-hub](../../includes/notification-hubs-portal-create-new-hub.md)]
<ol start="6">
<li><p>Select the <b>Notification Services</b> option and the <b>Windows (WNS)</b> option. Then enter the <b>Application secret</b> password in the <b>Security Key</b> field. Enter your <b>Package SID</b> value that you obtained from WNS in the previous section, and then click <b>Save</b>.</p>
</li>
</ol>
  
Your notification hub is now configured to work with WNS, and you have the connection strings to register your app and send notifications.
##Connect your app to the notification hub
1. In Visual Studio, right-click the solution, and then click **Manage NuGet Packages**.
This displays the **Manage NuGet Packages** dialog box.
2. Search for `WindowsAzure.Messaging.Managed` and click **Install**, and accept the terms of use.
![][20]
This downloads, installs, and adds a reference to the Azure Messaging library for Windows by using the <a href="http://nuget.org/packages/WindowsAzure.Messaging.Managed/">WindowsAzure.Messaging.Managed NuGet package</a>.
3. Open the App.xaml.cs project file and add the following `using` statements.
using Windows.Networking.PushNotifications;
using Microsoft.WindowsAzure.Messaging;
using Windows.UI.Popups;
4. Also in App.xaml.cs, add the following **InitNotificationsAsync** method definition to the **App** class:
private async void InitNotificationsAsync()
{
var channel = await PushNotificationChannelManager.CreatePushNotificationChannelForApplicationAsync();
var hub = new NotificationHub("< your hub name>", "<Your DefaultListenSharedAccessSignature connection string>");
var result = await hub.RegisterNativeAsync(channel.Uri);
// Displays the registration ID so you know it was successful
if (result.RegistrationId != null)
{
var dialog = new MessageDialog("Registration successful: " + result.RegistrationId);
dialog.Commands.Add(new UICommand("OK"));
await dialog.ShowAsync();
}
}
This code retrieves the channel URI for the app from WNS, and then registers that channel URI with your notification hub.
>[AZURE.NOTE] Make sure to replace the "your hub name" placeholder with the name of the notification hub that appears in the Azure Portal. Also replace the connection string placeholder with the **DefaultListenSharedAccessSignature** connection string that you obtained from the **Access Polices** page of your Notification Hub in a previous section.
5. At the top of the **OnLaunched** event handler in App.xaml.cs, add the following call to the new **InitNotificationsAsync** method:
InitNotificationsAsync();
This guarantees that the channel URI is registered in your notification hub each time the application is launched.
6. Press the **F5** key to run the app. A pop-up dialog that contains the registration key is displayed.
![][19]
Your app is now ready to receive toast notifications.
##Send notifications
You can quickly test receiving notifications in your app by sending notifications in the [Azure Portal](https://portal.azure.com/) using the **Test Send** button on the notification hub, as shown in the screen below.
Push notifications are normally sent in a back-end service like Mobile Services or ASP.NET using a compatible library. You can also use the REST API directly to send notification messages if a library is not available for your back-end.
In this tutorial, we will keep it simple and just demonstrate testing your client app by sending notifications using the .NET SDK for notification hubs in a console application instead of a backend service. We recommend the [Use Notification Hubs to push notifications to users] tutorial as the next step for sending notifications from an ASP.NET backend. However, the following approaches can be used for sending notifications:
* **REST Interface**: You can support notification on any backend platform using the [REST interface](http://msdn.microsoft.com/library/windowsazure/dn223264.aspx).
* **Microsoft Azure Notification Hubs .NET SDK**: In the Nuget Package Manager for Visual Studio, run [Install-Package Microsoft.Azure.NotificationHubs](https://www.nuget.org/packages/Microsoft.Azure.NotificationHubs/).
* **Node.js** : [How to use Notification Hubs from Node.js](notification-hubs-nodejs-push-notification-tutorial.md).
* **Azure Mobile Apps**: For an example of how to send notifications from an Azure Mobile App that's integrated with Notification Hubs, see [Add push notifications for Mobile Apps](../app-service-mobile/app-service-mobile-windows-store-dotnet-get-started-push.md).
* **Java / PHP**: For an example of how to send notifications by using the REST APIs, see "How to use Notification Hubs from Java/PHP" ([Java](notification-hubs-java-push-notification-tutorial.md) | [PHP](notification-hubs-php-push-notification-tutorial.md)).
## (Optional) Send notifications from a console app
To send notifications by using a .NET console application follow these steps.
1. Right-click the solution, select **Add** and **New Project...**, and then under **Visual C#**, click **Windows** and **Console Application**, and click **OK**.
![][13]
This adds a new Visual C# console application to the solution. You can also do this in a separate solution.
2. In Visual Studio, click **Tools**, click **NuGet Package Manager**, and then click **Package Manager Console**.
This displays the Package Manager Console in Visual Studio.
3. In the Package Manager Console window, set the **Default project** to your new console application project, and then in the console window, execute the following command:
Install-Package Microsoft.Azure.NotificationHubs
This adds a reference to the Azure Notification Hubs SDK using the <a href="http://www.nuget.org/packages/Microsoft.Azure.NotificationHubs/">Microsoft.Azure.Notification Hubs NuGet package</a>.
4. Open the Program.cs file and add the following `using` statement:
using Microsoft.Azure.NotificationHubs;
5. In the **Program** class, add the following method:
private static async void SendNotificationAsync()
{
NotificationHubClient hub = NotificationHubClient
.CreateClientFromConnectionString("<connection string with full access>", "<hub name>");
var toast = @"<toast><visual><binding template=""ToastText01""><text id=""1"">Hello from a .NET App!</text></binding></visual></toast>";
await hub.SendWindowsNativeNotificationAsync(toast);
}
Make sure to replace the "hub name" placeholder with the name of the notification hub that as it appears in the Azure Portal. Also, replace the connection string placeholder with the **DefaultFullSharedAccessSignature** connection string that you obtained from the **Access Policies** page of your Notification Hub in the section called "Configure your notification hub."
>[AZURE.NOTE]Make sure that you use the connection string that has **Full** access, not **Listen** access. The listen-access string does not have permissions to send notifications.
6. Add the following lines in the **Main** method:
SendNotificationAsync();
Console.ReadLine();
7. Right-click the console application project in Visual Studio, and click **Set as StartUp Project** to set it as the startup project. Then press the **F5** key to run the application.
![][14]
You will receive a toast notification on all registered devices. Clicking or tapping the toast banner loads the app.
You can find all the supported payloads in the [toast catalog], [tile catalog], and [badge overview] topics on MSDN.
##Next steps
In this simple example, you sent broadcast notifications to all your Windows devices using the portal or a console app. We recommend the [Use Notification Hubs to push notifications to users] tutorial as the next step. It will show you how to send notifications from an ASP.NET backend using tags to target specific users.
If you want to segment your users by interest groups, see [Use Notification Hubs to send breaking news].
To learn more general information about Notification Hubs, see [Notification Hubs Guidance](notification-hubs-push-notification-overview.md).
<!-- Images. -->
[13]: ./media/notification-hubs-windows-store-dotnet-get-started/notification-hub-create-console-app.png
[14]: ./media/notification-hubs-windows-store-dotnet-get-started/notification-hub-windows-toast.png
[19]: ./media/notification-hubs-windows-store-dotnet-get-started/notification-hub-windows-reg.png
[20]: ./media/notification-hubs-windows-store-dotnet-get-started/notification-hub-windows-universal-app-install-package.png
<!-- URLs. -->
[Use Notification Hubs to push notifications to users]: notification-hubs-aspnet-backend-windows-dotnet-notify-users.md
[Use Notification Hubs to send breaking news]: notification-hubs-windows-store-dotnet-send-breaking-news.md
[toast catalog]: http://msdn.microsoft.com/library/windows/apps/hh761494.aspx
[tile catalog]: http://msdn.microsoft.com/library/windows/apps/hh761491.aspx
[badge overview]: http://msdn.microsoft.com/library/windows/apps/hh779719.aspx
| 52.438406 | 428 | 0.759967 | eng_Latn | 0.907299 |
ed2804ba238c9ac3a2f63b054dfbe1d4368e61a8 | 370 | md | Markdown | data/README.md | CHAMA18/project-pneumonia | 2673b8630b9fbf392a57f1fef16be3652ef9d6fa | [
"Apache-2.0"
] | 3 | 2021-01-22T23:37:44.000Z | 2022-02-13T10:16:24.000Z | data/README.md | CHAMA18/project-pneumonia | 2673b8630b9fbf392a57f1fef16be3652ef9d6fa | [
"Apache-2.0"
] | 1 | 2021-10-05T04:44:26.000Z | 2021-10-05T12:57:54.000Z | data/README.md | CHAMA18/project-pneumonia | 2673b8630b9fbf392a57f1fef16be3652ef9d6fa | [
"Apache-2.0"
] | 5 | 2021-02-06T01:48:34.000Z | 2021-12-22T09:22:23.000Z | # Pneumonia Detection Data Source
The dataset can be downloaded from [kaggle](https://www.kaggle.com/paultimothymooney/chest-xray-pneumonia/download).
## Instructions to follow
* Extract the archive
* You will find several directories in it
* Copy the `chest-xray` directory contents to this folder
* Alternatively copy the `train`, `test` and `val` directories here
| 33.636364 | 116 | 0.778378 | eng_Latn | 0.970992 |
ed28f280df3b65bd00231be5a632069aae02f27e | 378 | md | Markdown | _bagby/gbby-45g439.md | jpmantica/wax-sandbox | 96a80a692203a1972d13c30b5a00823d8b2234d0 | [
"MIT"
] | null | null | null | _bagby/gbby-45g439.md | jpmantica/wax-sandbox | 96a80a692203a1972d13c30b5a00823d8b2234d0 | [
"MIT"
] | null | null | null | _bagby/gbby-45g439.md | jpmantica/wax-sandbox | 96a80a692203a1972d13c30b5a00823d8b2234d0 | [
"MIT"
] | 1 | 2021-11-09T15:37:25.000Z | 2021-11-09T15:37:25.000Z | ---
pid: gbby-45g439
order: '416'
file_name: gbby-45g439.jpg
label: 'GBBY 45G/439: Baseball Game Scene - Unidentified - c1928-1934'
_date: 1928-1934
object_type: glass plate negative
source: http://archives.nd.edu/Bagby/GBBY-45g439.jpg
thumbnail: "/_data/raw_images/bagby/gbby-45g439.jpg"
full: "/_data/raw_images/bagby/gbby-45g439.jpg"
layout: bagby_item
collection: bagby
---
| 27 | 70 | 0.76455 | kor_Hang | 0.103498 |
ed292a3f0138235c5080b63e2db7c463d7be1db6 | 19,143 | md | Markdown | docs/xamarin-forms/app-fundamentals/data-binding/converters.md | cozyplanes/xamarin-docs.ko-kr | fef8d2951f8409717c63113a4c3301656f9a8ce6 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/xamarin-forms/app-fundamentals/data-binding/converters.md | cozyplanes/xamarin-docs.ko-kr | fef8d2951f8409717c63113a4c3301656f9a8ce6 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/xamarin-forms/app-fundamentals/data-binding/converters.md | cozyplanes/xamarin-docs.ko-kr | fef8d2951f8409717c63113a4c3301656f9a8ce6 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-03-08T02:25:40.000Z | 2021-03-08T02:25:40.000Z | ---
title: Xamarin.Forms 바인딩 값 변환기
description: 이 문서에는 캐스팅 되거나 (임 라고도 바인딩 변환기 또는 바인딩 값 변환기)는 값 변환기를 구현 하 여 Xamarin.Forms 데이터 바인딩에 대 한 값을 변환 하는 방법을 설명 합니다.
ms.prod: xamarin
ms.assetid: 02B1BBE6-D804-490D-BDD4-8ACED8B70C92
ms.technology: xamarin-forms
author: davidbritch
ms.author: dabritch
ms.date: 01/05/2018
ms.openlocfilehash: 28892692133020de1fa5a6eb007bb3f9bcf2612b
ms.sourcegitcommit: 6e955f6851794d58334d41f7a550d93a47e834d2
ms.translationtype: MT
ms.contentlocale: ko-KR
ms.lasthandoff: 07/12/2018
ms.locfileid: "38997486"
---
# <a name="xamarinforms-binding-value-converters"></a>Xamarin.Forms 바인딩 값 변환기
데이터 바인딩을 일반적으로 송수신 데이터 원본 속성의 대상 속성을 소스 속성에 대상 속성에서 일부 경우에 합니다. 이 전송을 간단 하 게 원본 및 대상 속성을 동일한 형식의 경우 형식 변환 하는 암시적 변환을 통해 다른 유형으로 변환할 수 있습니다. 대/소문자는 없는 경우 형식 변환을 수행 해야 합니다.
에 [ **문자열 서식 지정** ](string-formatting.md) 문서를 사용 하는 방법을 살펴보았습니다는 `StringFormat` 모든 형식을 문자열로 변환에 대 한 데이터 바인딩의 속성입니다. 다른 유형의 변환 구현 하는 클래스에서 일부 특수 한 코드를 작성 해야 합니다 [ `IValueConverter` ](xref:Xamarin.Forms.IValueConverter) 인터페이스입니다. (유사한 클래스를 포함 하는 유니버설 Windows 플랫폼 [ `IValueConverter` ](/uwp/api/Windows.UI.Xaml.Data.IValueConverter/) 에 `Windows.UI.Xaml.Data` 이 네임 스페이스 `IValueConverter` 에 `Xamarin.Forms` 네임 스페이스입니다.) 구현 하는 클래스 `IValueConverter` 이라고 *값 변환기*에 종종 라고 하지만 *바인딩 변환기* 또는 *바인딩 값 변환기*합니다.
## <a name="the-ivalueconverter-interface"></a>IValueConverter 인터페이스
형식의 원본 속성은 데이터 바인딩을 정의 하기를 원한다고 가정 `int` 는 대상 속성을 `bool`입니다. 이 데이터 바인딩이 생성 하려는 `false` 정수 원본이 0 인 경우 값 및 `true` 그렇지 않은 경우.
구현 하는 클래스를 사용 하 여이 수행할 수는 `IValueConverter` 인터페이스:
```csharp
public class IntToBoolConverter : IValueConverter
{
public object Convert(object value, Type targetType, object parameter, CultureInfo culture)
{
return (int)value != 0;
}
public object ConvertBack(object value, Type targetType, object parameter, CultureInfo culture)
{
return (bool)value ? 1 : 0;
}
}
```
이 클래스의 인스턴스를 설정 합니다 [ `Converter` ](xref:Xamarin.Forms.Binding.Converter) 의 속성을 `Binding` 클래스 또는 [ `Converter` ](xref:Xamarin.Forms.Xaml.BindingExtension.Converter) 속성은 `Binding` 태그 확장. 이 클래스에는 데이터 바인딩의 일부가 됩니다.
합니다 `Convert` 메서드는 원본에서 대상의 데이터 이동 `OneWay` 또는 `TwoWay` 바인딩. `value` 개체 또는 데이터 바인딩 원본의 값 매개 변수입니다. 메서드는 데이터 바인딩된 대상 형식의 값을 반환 해야 합니다. 캐스트 여기 표시 된 메서드를 `value` 매개 변수를는 `int` 과 0을 사용 하 여 비교를 `bool` 값을 반환 합니다.
합니다 `ConvertBack` 메서드는 소스에 대상에서 데이터 이동 `TwoWay` 또는 `OneWayToSource` 바인딩. `ConvertBack` 변환 수행: 것으로 가정 합니다 `value` 매개 변수는를 `bool` 대상에서으로 변환 하 고는 `int` 원본에 대 한 값을 반환 합니다.
데이터 바인딩에 포함 된 경우는 `StringFormat` 설정, 값 변환기는 전에 호출 결과 문자열로 서식이 지정 된 합니다.
합니다 **단추를 사용 하도록 설정** 페이지에 [ **데이터 바인딩 데모** ](https://developer.xamarin.com/samples/xamarin-forms/DataBindingDemos/) 샘플 데이터 바인딩에이 값 변환기를 사용 하는 방법을 보여 줍니다. `IntToBoolConverter` 페이지의 리소스 사전에 인스턴스화됩니다. 사용 하 여 다음 참조를 `StaticResource` 태그 확장을 설정 하는 `Converter` 두 데이터 바인딩에서 속성. 것은 매우 일반적인 페이지의 여러 데이터 바인딩 간에 데이터 변환기를 공유 하려면:
```xaml
<ContentPage xmlns="http://xamarin.com/schemas/2014/forms"
xmlns:x="http://schemas.microsoft.com/winfx/2009/xaml"
xmlns:local="clr-namespace:DataBindingDemos"
x:Class="DataBindingDemos.EnableButtonsPage"
Title="Enable Buttons">
<ContentPage.Resources>
<ResourceDictionary>
<local:IntToBoolConverter x:Key="intToBool" />
</ResourceDictionary>
</ContentPage.Resources>
<StackLayout Padding="10, 0">
<Entry x:Name="entry1"
Text=""
Placeholder="enter search term"
VerticalOptions="CenterAndExpand" />
<Button Text="Search"
HorizontalOptions="Center"
VerticalOptions="CenterAndExpand"
IsEnabled="{Binding Source={x:Reference entry1},
Path=Text.Length,
Converter={StaticResource intToBool}}" />
<Entry x:Name="entry2"
Text=""
Placeholder="enter destination"
VerticalOptions="CenterAndExpand" />
<Button Text="Submit"
HorizontalOptions="Center"
VerticalOptions="CenterAndExpand"
IsEnabled="{Binding Source={x:Reference entry2},
Path=Text.Length,
Converter={StaticResource intToBool}}" />
</StackLayout>
</ContentPage>
```
값 변환기를 응용 프로그램의 여러 페이지에서 사용 하는 경우의 리소스 사전에 인스턴스화할 수 있습니다 합니다 **App.xaml** 파일입니다.
합니다 **단추를 사용 하도록 설정** 페이지 일반적인 경우 해야 하는 방법을 보여 줍니다는 `Button` 에 사용자가 텍스트에 따라 작업을 수행을 `Entry` 보기. 에 입력 된 아무 작업도 수행 하는 경우는 `Entry`, `Button` 수 없게 됩니다. 각 `Button` 에 데이터 바인딩이 포함 해당 `IsEnabled` 속성입니다. 데이터 바인딩 원본이 합니다 `Length` 의 속성을 `Text` 해당 속성 `Entry`. 있는지 `Length` 속성은 0, 값 변환기를 반환 합니다 `true` 하며 `Button` 사용 가능:
[](converters-images/enablebuttons-large.png#lightbox "단추를 사용 하도록 설정")
다음에 유의 합니다 `Text` 각 속성 `Entry` 빈 문자열로 초기화 됩니다. 합니다 `Text` 속성은 `null` 기본적으로 데이터 바인딩은 작동 하지 것입니다 경우.
일부 값 변환기는 다른 일반화 하는 동안 특정 응용 프로그램만 위한 기록 됩니다. 값 변환기에만 사용할 수는 알고 있는 경우 `OneWay` 바인딩, 해당 `ConvertBack` 메서드를 반환할 수 있습니다 `null`합니다.
`Convert` 가정 암시적으로 위에 나와 있는 메서드에 `value` 형식의 인수가 `int` 반환 값 형식 이어야 하 고 `bool`. 마찬가지로,는 `ConvertBack` 가정 메서드는 `value` 형식의 인수가 `bool` 및 반환 값은 `int`. 하지 않은 경우 런타임 예외가 발생 합니다.
값 변환기 보다 일반화 및 여러 다른 유형의 데이터를 허용 하도록 작성할 수 있습니다. `Convert` 및 `ConvertBack` 메서드를 사용할 수는 `as` 또는 `is` 연산자를 합니다 `value` 매개 변수를 하거나 호출할 수 `GetType` 해당 유형 및 다음 작업 항목 확인 하려면 해당 매개 변수에 적절 한 합니다. 각 메서드의 반환 값의 예상된 형식을 지정 하 여는 `targetType` 매개 변수입니다. 값 변환기 다양 한 대상 유형에;의 데이터 바인딩과 함께 사용 되는 경우에 따라 값 변환기를 사용할 수는 `targetType` 올바른 형식에 대 한 변환을 수행 하는 인수입니다.
사용 하 여 변환이 수행 되 고 다른 문화권에 대 한 다른 경우는 `culture` 이 목적을 위해 매개 변수입니다. 합니다 `parameter` 인수를 `Convert` 및 `ConvertBack` 이 문서의 뒷부분에서 설명 됩니다.
## <a name="binding-converter-properties"></a>바인딩 변환기 속성
속성 및 일반 매개 변수 값 변환기 클래스가 있을 수 있습니다. 이 특정 값 변환기에서 변환 된 `bool` 형식의 개체를 원본에서 `T` 대상:
```csharp
public class BoolToObjectConverter<T> : IValueConverter
{
public T TrueObject { set; get; }
public T FalseObject { set; get; }
public object Convert(object value, Type targetType, object parameter, CultureInfo culture)
{
return (bool)value ? TrueObject : FalseObject;
}
public object ConvertBack(object value, Type targetType, object parameter, CultureInfo culture)
{
return ((T)value).Equals(TrueObject);
}
}
```
합니다 **스위치 표시기** 페이지의 값을 표시 하 고 있습니다 사용 하는 방법을 보여 줍니다는 `Switch` 보기. 이 페이지는 대체 방법을 보여 줍니다 일반적인 리소스 사전에 리소스로 값 변환기를 인스턴스화하는 아니지만: 각 값 변환기 간에 인스턴스화됩니다 `Binding.Converter` 속성 요소 태그입니다. 합니다 `x:TypeArguments` 제네릭 인수를 나타냅니다 및 `TrueObject` 및 `FalseObject` 해당 형식의 개체에 설정 됩니다.
```xaml
<ContentPage xmlns="http://xamarin.com/schemas/2014/forms"
xmlns:x="http://schemas.microsoft.com/winfx/2009/xaml"
xmlns:local="clr-namespace:DataBindingDemos"
x:Class="DataBindingDemos.SwitchIndicatorsPage"
Title="Switch Indicators">
<ContentPage.Resources>
<ResourceDictionary>
<Style TargetType="Label">
<Setter Property="FontSize" Value="18" />
<Setter Property="VerticalOptions" Value="Center" />
</Style>
<Style TargetType="Switch">
<Setter Property="VerticalOptions" Value="Center" />
</Style>
</ResourceDictionary>
</ContentPage.Resources>
<StackLayout Padding="10, 0">
<StackLayout Orientation="Horizontal"
VerticalOptions="CenterAndExpand">
<Label Text="Subscribe?" />
<Switch x:Name="switch1" />
<Label>
<Label.Text>
<Binding Source="{x:Reference switch1}"
Path="IsToggled">
<Binding.Converter>
<local:BoolToObjectConverter x:TypeArguments="x:String"
TrueObject="Of course!"
FalseObject="No way!" />
</Binding.Converter>
</Binding>
</Label.Text>
</Label>
</StackLayout>
<StackLayout Orientation="Horizontal"
VerticalOptions="CenterAndExpand">
<Label Text="Allow popups?" />
<Switch x:Name="switch2" />
<Label>
<Label.Text>
<Binding Source="{x:Reference switch2}"
Path="IsToggled">
<Binding.Converter>
<local:BoolToObjectConverter x:TypeArguments="x:String"
TrueObject="Yes"
FalseObject="No" />
</Binding.Converter>
</Binding>
</Label.Text>
<Label.TextColor>
<Binding Source="{x:Reference switch2}"
Path="IsToggled">
<Binding.Converter>
<local:BoolToObjectConverter x:TypeArguments="Color"
TrueObject="Green"
FalseObject="Red" />
</Binding.Converter>
</Binding>
</Label.TextColor>
</Label>
</StackLayout>
<StackLayout Orientation="Horizontal"
VerticalOptions="CenterAndExpand">
<Label Text="Learn more?" />
<Switch x:Name="switch3" />
<Label FontSize="18"
VerticalOptions="Center">
<Label.Style>
<Binding Source="{x:Reference switch3}"
Path="IsToggled">
<Binding.Converter>
<local:BoolToObjectConverter x:TypeArguments="Style">
<local:BoolToObjectConverter.TrueObject>
<Style TargetType="Label">
<Setter Property="Text" Value="Indubitably!" />
<Setter Property="FontAttributes" Value="Italic, Bold" />
<Setter Property="TextColor" Value="Green" />
</Style>
</local:BoolToObjectConverter.TrueObject>
<local:BoolToObjectConverter.FalseObject>
<Style TargetType="Label">
<Setter Property="Text" Value="Maybe later" />
<Setter Property="FontAttributes" Value="None" />
<Setter Property="TextColor" Value="Red" />
</Style>
</local:BoolToObjectConverter.FalseObject>
</local:BoolToObjectConverter>
</Binding.Converter>
</Binding>
</Label.Style>
</Label>
</StackLayout>
</StackLayout>
</ContentPage>
```
마지막에서 세 가지 `Switch` 및 `Label` 쌍 제네릭 인수 설정할지 `Style`, 전체 `Style` 개체의 값에 대해 제공 됩니다 `TrueObject` 및 `FalseObject`합니다. 이러한 재정의 대 한 암시적 스타일 `Label` 리소스 사전에 설정 되므로 해당 스타일의 속성을 명시적으로 할당 된는 `Label`합니다. 설정/해제 합니다 `Switch` 해당 하면 `Label` 변경 내용을 반영 하려면:
[](converters-images/switchindicators-large.png#lightbox "지표를 전환 합니다.")
사용할 수 이기도 [ `Triggers` ](~/xamarin-forms/app-fundamentals/triggers.md) 다른 뷰를 기반으로 사용자 인터페이스에 비슷한 변경을 구현 합니다.
## <a name="binding-converter-parameters"></a>변환기 매개 변수 바인딩
`Binding` 클래스 정의 [ `ConverterParameter` ](xref:Xamarin.Forms.Binding.ConverterParameter) 속성 및 `Binding` 태그 확장도 정의 [ `ConverterParameter` ](xref:Xamarin.Forms.Xaml.BindingExtension.ConverterParameter) 속성입니다. 이 속성이 설정 되어 있으면 값이 전달 되는 `Convert` 하 고 `ConvertBack` 메서드를 `parameter` 인수. 여러 데이터 바인딩 값 변환기 인스턴스의 공유 하는 경우에는 `ConverterParameter` 약간 다른 변환을 수행 하는 다를 수 있습니다.
사용 `ConverterParameter` 색 선택 영역 프로그램을 사용 하 여 보여 줍니다. 이 경우에 `RgbColorViewModel` 형식의 세 가지 속성이 있습니다 `double` 라는 `Red`를 `Green`, 및 `Blue` 생성 하는 데 사용 하는 `Color` 값:
```csharp
public class RgbColorViewModel : INotifyPropertyChanged
{
Color color;
string name;
public event PropertyChangedEventHandler PropertyChanged;
public double Red
{
set
{
if (color.R != value)
{
Color = new Color(value, color.G, color.B);
}
}
get
{
return color.R;
}
}
public double Green
{
set
{
if (color.G != value)
{
Color = new Color(color.R, value, color.B);
}
}
get
{
return color.G;
}
}
public double Blue
{
set
{
if (color.B != value)
{
Color = new Color(color.R, color.G, value);
}
}
get
{
return color.B;
}
}
public Color Color
{
set
{
if (color != value)
{
color = value;
PropertyChanged?.Invoke(this, new PropertyChangedEventArgs("Red"));
PropertyChanged?.Invoke(this, new PropertyChangedEventArgs("Green"));
PropertyChanged?.Invoke(this, new PropertyChangedEventArgs("Blue"));
PropertyChanged?.Invoke(this, new PropertyChangedEventArgs("Color"));
Name = NamedColor.GetNearestColorName(color);
}
}
get
{
return color;
}
}
public string Name
{
private set
{
if (name != value)
{
name = value;
PropertyChanged?.Invoke(this, new PropertyChangedEventArgs("Name"));
}
}
get
{
return name;
}
}
}
```
합니다 `Red`, `Green`, 및 `Blue` 0과 1 사이의 속성 범위입니다. 그러나 두 자리 16 진수 값으로 구성 요소를 표시 하도록 하는 것이 좋습니다.
16 진수 값으로이 XAML에 표시 하려면 이러한 여야 255를 곱하고, 정수로 변환 하며 다음에서 "X2"의 사양으로 형식이 지정 된 `StringFormat` 속성입니다. 값 변환기에서 처음 두 작업 (255를 곱하여 및 정수 변환)를 처리할 수 있습니다. 최대한 일반화 된 것으로 값 변환기가 하도록 곱하기 비율을 지정할 수 있습니다는 `ConverterParameter` 가 해당 의미 하는 속성을 `Convert` 및 `ConvertBack` 메서드를 `parameter` 인수:
```csharp
public class DoubleToIntConverter : IValueConverter
{
public object Convert(object value, Type targetType, object parameter, CultureInfo culture)
{
return (int)Math.Round((double)value * GetParameter(parameter));
}
public object ConvertBack(object value, Type targetType, object parameter, CultureInfo culture)
{
return (int)value / GetParameter(parameter);
}
double GetParameter(object parameter)
{
if (parameter is double)
return (double)parameter;
else if (parameter is int)
return (int)parameter;
else if (parameter is string)
return double.Parse((string)parameter);
return 1;
}
}
```
`Convert` 에서 변환를 `double` 를 `int` 곱하여 하는 동안를 `parameter` ; 값를 `ConvertBack` 정수를 나누고 `value` 인수를 `parameter` 반환을 `double` 결과. (아래에 표시 된 프로그램에서 값 변환기는만 관련 하 여 문자열 서식 지정, 따라서 `ConvertBack` 사용 되지 않습니다.)
형식의 `parameter` 인수는 코드 또는 XAML 데이터 바인딩을 정의 여부에 따라 다를 수 있습니다. 경우는 `ConverterParameter` 속성의 `Binding` 설정 된 코드에서 숫자 값으로 설정할 수는:
```csharp
binding.ConverterParameter = 255;
```
합니다 `ConverterParameter` 형식의 속성이 `Object`이므로 C# 컴파일러는 정수 리터럴 255를 해석 하 고 해당 값으로 속성을 설정 합니다.
그러나 XAML에는 `ConverterParameter` 다음과 같이 설정할 수:
```xaml
<Label Text="{Binding Red,
Converter={StaticResource doubleToInt},
ConverterParameter=255,
StringFormat='Red = {0:X2}'}" />
```
255 같습니다 number, 하지만 때문에 `ConverterParameter` 유형의 `Object`, XAML 파서를 문자열로 255를 처리 합니다.
따라서 위의 값 변환기는 별도 포함 `GetParameter` 에 대 한 사례를 처리 하는 메서드 `parameter` 형식의 `double`를 `int`, 또는 `string`합니다.
합니다 **RGB 색 선택기** 페이지를 인스턴스화하고 `DoubleToIntConverter` 두 암시적 스타일의 정의 다음 해당 리소스 사전에:
```xaml
<ContentPage xmlns="http://xamarin.com/schemas/2014/forms"
xmlns:x="http://schemas.microsoft.com/winfx/2009/xaml"
xmlns:local="clr-namespace:DataBindingDemos"
x:Class="DataBindingDemos.RgbColorSelectorPage"
Title="RGB Color Selector">
<ContentPage.Resources>
<ResourceDictionary>
<Style TargetType="Slider">
<Setter Property="VerticalOptions" Value="CenterAndExpand" />
</Style>
<Style TargetType="Label">
<Setter Property="HorizontalTextAlignment" Value="Center" />
</Style>
<local:DoubleToIntConverter x:Key="doubleToInt" />
</ResourceDictionary>
</ContentPage.Resources>
<StackLayout>
<StackLayout.BindingContext>
<local:RgbColorViewModel Color="Gray" />
</StackLayout.BindingContext>
<BoxView Color="{Binding Color}"
VerticalOptions="FillAndExpand" />
<StackLayout Margin="10, 0">
<Label Text="{Binding Name}" />
<Slider Value="{Binding Red}" />
<Label Text="{Binding Red,
Converter={StaticResource doubleToInt},
ConverterParameter=255,
StringFormat='Red = {0:X2}'}" />
<Slider Value="{Binding Green}" />
<Label Text="{Binding Green,
Converter={StaticResource doubleToInt},
ConverterParameter=255,
StringFormat='Green = {0:X2}'}" />
<Slider Value="{Binding Blue}" />
<Label>
<Label.Text>
<Binding Path="Blue"
StringFormat="Blue = {0:X2}"
Converter="{StaticResource doubleToInt}">
<Binding.ConverterParameter>
<x:Double>255</x:Double>
</Binding.ConverterParameter>
</Binding>
</Label.Text>
</Label>
</StackLayout>
</StackLayout>
</ContentPage>
```
값을 `Red` 및 `Green` 속성으로 표시 됩니다는 `Binding` 태그 확장 합니다. 그러나 `Blue` 속성인 인스턴스화하는 `Binding` 명시적 방법을 보여 주기 위해 클래스 `double` 값 설정할 수 있습니다 `ConverterParameter` 속성입니다.
결과 다음과 같습니다.
[](converters-images/rgbcolorselector-large.png#lightbox "RGB 색 선택기")
## <a name="related-links"></a>관련 링크
- [데이터 바인딩 데모 (샘플)](https://developer.xamarin.com/samples/xamarin-forms/DataBindingDemos/)
- [Xamarin.Forms 책에서 데이터 바인딩 장](~/xamarin-forms/creating-mobile-apps-xamarin-forms/summaries/chapter16.md)
| 40.729787 | 494 | 0.570235 | kor_Hang | 0.999879 |
ed29b195b06170bc54c30791a82fb5ef6a0f8d07 | 2,223 | md | Markdown | README.md | npmdoc/node-npmdoc-cordova-plugin-google-analytics | bfb7372c4148d16c61801a1bc7753060003c1ec4 | [
"MIT"
] | null | null | null | README.md | npmdoc/node-npmdoc-cordova-plugin-google-analytics | bfb7372c4148d16c61801a1bc7753060003c1ec4 | [
"MIT"
] | null | null | null | README.md | npmdoc/node-npmdoc-cordova-plugin-google-analytics | bfb7372c4148d16c61801a1bc7753060003c1ec4 | [
"MIT"
] | null | null | null | # npmdoc-cordova-plugin-google-analytics
#### api documentation for cordova-plugin-google-analytics (v1.7.11) [](https://www.npmjs.org/package/npmdoc-cordova-plugin-google-analytics) [](https://travis-ci.org/npmdoc/node-npmdoc-cordova-plugin-google-analytics)
#### Google Universal Analytics Plugin
[](https://www.npmjs.com/package/cordova-plugin-google-analytics)
- [https://npmdoc.github.io/node-npmdoc-cordova-plugin-google-analytics/build/apidoc.html](https://npmdoc.github.io/node-npmdoc-cordova-plugin-google-analytics/build/apidoc.html)
[](https://npmdoc.github.io/node-npmdoc-cordova-plugin-google-analytics/build/apidoc.html)
# package.json
```json
{
"name": "cordova-plugin-google-analytics",
"version": "1.7.11",
"description": "Google Universal Analytics Plugin",
"cordova": {
"id": "cordova-plugin-google-analytics",
"platforms": [
"android",
"ios"
]
},
"repository": {
"type": "git",
"url": "https://github.com/danwilson/google-analytics-plugin.git"
},
"keywords": [
"cordova",
"googleanalytics",
"ecosystem:cordova",
"cordova-android",
"cordova-ios",
"analytics",
"google",
"universal",
"universalanalytics"
],
"author": "Dan Wilson",
"license": "MIT"
}
```
# misc
- this document was created with [utility2](https://github.com/kaizhu256/node-utility2)
| 38.327586 | 436 | 0.699955 | kor_Hang | 0.127233 |
ed29e368650219e1b75601c509764158458982c2 | 7,590 | md | Markdown | _includes/docs/user-guide/tenant-profiles.md | OKhalkov/thingsboard.github.io | 7fbe960cefa1e5d67ed94b622c3e4f8fb48e9d06 | [
"Apache-2.0"
] | 105 | 2016-12-06T12:44:29.000Z | 2022-03-20T10:29:49.000Z | _includes/docs/user-guide/tenant-profiles.md | OKhalkov/thingsboard.github.io | 7fbe960cefa1e5d67ed94b622c3e4f8fb48e9d06 | [
"Apache-2.0"
] | 190 | 2016-12-12T09:35:51.000Z | 2022-03-27T13:18:09.000Z | _includes/docs/user-guide/tenant-profiles.md | OKhalkov/thingsboard.github.io | 7fbe960cefa1e5d67ed94b622c3e4f8fb48e9d06 | [
"Apache-2.0"
] | 287 | 2016-12-07T22:12:02.000Z | 2022-03-25T01:33:58.000Z |
* TOC
{:toc}
## Overview
Since ThingsBoard 3.2, a System Administrator is able to configure common settings for multiple tenants using Tenant Profiles.
Each Tenant has the one and only profile at a single point in time.
Let's review the settings available in the tenant profile, one-by-one.
## Entity Limits
This group of settings allows the System Administrator to configure a maximum number of entities that each Tenant is able to create.
**ThingsBoard Community** edition supports limits for the following entities: devices, assets, customers, users, dashboards, and rule chains.
**ThingsBoard Professional** edition supports limits for everything listed above and as well additional constraint support for the following entities: integrations, converters, and scheduler events.
{% include images-gallery.html imageCollection="entityLimits" %}
## API Limits & Usage
This group of settings allows a System Administrator to configure a maximum number of messages, API calls, etc., per month that each Tenant would like to perform.
ThingsBoard constantly collects and analyzes statistics about API Usage. The typical update interval of the statistics is 1 minute
ThingsBoard tracks API usage for six main components: Transport, Rule Engine, JS functions, Telemetry persistence, Email, and SMS services. The platform will disable the component if one of the related API Limits reaches a threshold.
For example, if Tenant devices produce more than 100M messages per a month, the platform will disable all connections for devices that belong to this Tenant.
When the API usage is disabled or reaches a certain threshold (typically 80%) ThingsBoard will notify the Tenant Administrator via email.
Let's review each limit separately:
**Transport Messages** means any message that your device sends to the server. This may be telemetry, attribute update, RPC call, etc.
**Transport Data Points** means a number of the Key-Value pairs that your telemetry or attribute messages contain.
For example, the message listed below contains 5 data points, because the “jsonKey” corresponds to one data point.
```json
{
"stringKey":"value1",
"booleanKey":true,
"doubleKey":42.0,
"longKey":73,
"jsonKey": {
"someNumber": 42,
"someArray": [1,2,3],
"someNestedObject": {"key": "value"}
}
}
```
**Note**: If the value of a String or JSON key is larger than 512 characters, the platform will count it as multiple data points.
**Rule Engine executions** mean any execution of the rule node that belongs to the current Tenant. Processing of a single telemetry message may cause multiple Rule Engine executions.
The platform will also count periodic messages produced by Generator nodes, etc.
**JavaScript executions** mean any execution of the custom function defined by Tenant Administrators. For example, processing of the “Script” filter or a transformation node, an invocation of the data converter, etc.
**Data points storage days** are calculated for all time-series data points that are stored in the database.
Platform multiplies the number of data points by the number of days those data points will be stored. The TTL parameter is used to extract the number of days to store the data.
For example, if you store 3 data points for 30 days, this is 90 storage data point days.
A System Administrator is able to configure default TTL using the "**Default Storage TTL Days**" parameter in the tenant profile.
A Tenant Administrator is able to overwrite default TTL using the "**Save Timeseries**" ule node configuration or using the “TTL” parameter in the post telemetry request.
**Alarms TTL** means how many days to store alarms in the database.
**Alarms sent** means the total number of alarms created per the period (one month by default).
**Emails sent** means the number of emails that are sent from the rule engine using system SMTP provider (settings).
Please note that the Tenant Administrator is able to define custom SMTP settings in both Community and Professional Editions of the platform.
Emails sent with custom SMTP settings do not affect API limits.
**SMS sent** means the number of SMSes that are sent from the rule engine using the system SMS provider.
Please note that the Tenant Administrator is able to define custom SMS provider settings in both Community and Professional Editions of the platform.
SMS sent with custom SMTP settings do not affect API limits.
### API Usage dashboard
As a Tenant Administrator, you can review the API Usage dashboard.
The dashboard below allows Tenant Administrators to learn more about their hourly/daily/monthly API usage and instantly review the status of the API limits.
{% include images-gallery.html imageCollection="apiLimitsDashboard" %}
## Rate Limits
This group of settings allows a System Administrator to configure a maximum number of
requests the platform should process for a specific device (device-level) or for all devices belonging to a single tenant (tenant-level).
The implementation of rate limits is based on the [token bucket](https://en.wikipedia.org/wiki/Token_bucket) algorithm.
The rate limit definition consists of the value and time interval. For example, "1000:60" means "no more than 1000 messages per 60 seconds".
You can define multiple intervals with ",". For example, "100:1,1000:60" means "bursts of 100 messages per second but no more than 1000 times per 60 seconds".
{% include images-gallery.html imageCollection="rateLimits" %}
## Processing in isolated ThingsBoard Core and Rule Engine containers
Isolated processing should be disabled by default. These options are only useful in rare cases of a [microservices](/docs/{{docsPrefix}}reference/msa/) deployment.
Experienced DevOps / System Administrators are required to configure the ThingsBoard cluster to use these settings.
Misconfiguration may cause issues with the processing of incoming messages.
ThingsBoard team is working to simplify the configuration process and expect to provide improvements in ThingsBoard 3.3 release.
Starting ThingsBoard 2.5 you may deploy isolated Core and Rule Engine [microservices](/docs/{{docsPrefix}}reference/msa/) for each or specific tenants.
ThingsBoard Core is responsible for handling WebSocket subscriptions, tracking device connectivity, and other calculations that are not directly related to message processing.
ThingsBoard Rule Engine is the main "worker" in the cluster and is responsible for processing incoming messages.
By default, all messages (such as telemetry, connectivity, and lifecycle events) are pushed to the same message queue/topic (powered by Kafka, RabbitMQ, AWS SQS, Azure Service Bus, Goole Pub/Sub).
ThingsBoard pushes messages for all Tenants to a common queue when isolated processing is disabled (default).
This requires fewer processing resources and allows data from multiple Tenants to be processed under a single Rule Engine.
This way, you don't need to host a separate container or VM per Tenant.
ThingsBoard pushes messages to a separate queue when you select processing to be isolated for a particular tenant.
This provides a better level of isolation for those tenants. However, this also requires you to launch separate microservices for a particular Tenant.
In order to do this, you should specify the TB_SERVICE_TENANT_ID environment variable for that microservice. The value should be set to the isolated Tenant Id.
This will instruct Rule Engine / Core microservice to subscribe to specific message queue topics that contain data for that particular Tenant.
| 62.213115 | 234 | 0.789723 | eng_Latn | 0.997595 |
ed2a147a38fa210efded077fe67b47393def7269 | 1,365 | md | Markdown | mercury/README.md | lixmk/Concierge | 32151679217ab5117b5b6fb43d6f54eac1e09861 | [
"MIT"
] | 108 | 2016-06-08T00:33:19.000Z | 2022-02-08T17:37:02.000Z | mercury/README.md | W00t3k/Concierge | 32151679217ab5117b5b6fb43d6f54eac1e09861 | [
"MIT"
] | 4 | 2017-11-04T16:20:24.000Z | 2018-06-09T15:48:21.000Z | mercury/README.md | W00t3k/Concierge | 32151679217ab5117b5b6fb43d6f54eac1e09861 | [
"MIT"
] | 24 | 2016-06-22T12:07:36.000Z | 2021-09-26T01:10:16.000Z | # Concierge: Mercury
Various scripts (well, script) to discover and exploit Mercury Security OEM systems. Several vendors rebrand Mercury devices or use Mercury firmware on their own hardware.
## ep-discover-snmp.py
Makes an SNMP calls and parses responses to identify Mercury Security OEM door controllers. This script is known to identify EP-1501 and EP-1502 (and their many vanity names) door controllers but may also work for other Mercury OEM systems.
**Usage:** `./ep-discover-snmp.py -r 10.0.0.1/24`
**Note:** This script is slow. The preferred method of discovery is using the nmap NSE script in the utils/nse/ directory.
## ./nse/mercury-ep-snmp-discover.nse
**Usage:** `nmap -sU -p 161 --script=mercury-ep-snmp-discover.nse <target(s)>`
Leverages SNMP to identify door controllers manufactured by, or using firmware from, Mercury Security. Mercury door controllers often rebranded by several other vendors including: Lenel, Honeywell, Premisys. Additionally, other manufactures use Mercury Security's firmware on their devices (such as KeriSystems' NXT series).
**Output:**
```
Nmap scan report 10.0.0.1
Host is up (0.12s latency).
PORT STATE SERVICE
161/udp open snmp
| mercury-ep-snmp-discover:
| Description: EP-1502 Configuration Manager
| Device Type: EP-1502
| Firmware Verison: 1.19.4
|_ Build Number: 415
```
| 50.555556 | 324 | 0.750183 | eng_Latn | 0.976352 |
ed2bb89b5e27996e4e2864cfec095396fddf5718 | 1,951 | md | Markdown | docs/web-service-reference/documentsharinglocationcollectionsetting-soap.md | MicrosoftDocs/office-developer-exchange-docs.zh-CN | b44770dea40f3ad4bed87d827b1a7e3a964a1250 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-05-19T18:54:06.000Z | 2020-05-19T18:54:06.000Z | docs/web-service-reference/documentsharinglocationcollectionsetting-soap.md | MicrosoftDocs/office-developer-exchange-docs.zh-CN | b44770dea40f3ad4bed87d827b1a7e3a964a1250 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2021-12-08T02:37:03.000Z | 2021-12-08T02:37:33.000Z | docs/web-service-reference/documentsharinglocationcollectionsetting-soap.md | MicrosoftDocs/office-developer-exchange-docs.zh-CN | b44770dea40f3ad4bed87d827b1a7e3a964a1250 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: DocumentSharingLocationCollectionSetting (SOAP)
manager: sethgros
ms.date: 09/17/2015
ms.audience: Developer
ms.topic: reference
ms.localizationpriority: medium
ms.assetid: 0e3346f9-7a55-4e87-b121-9b1ee7f227f4
description: DocumentSharingLocationCollectionSetting 元素表示一个用户设置，该设置是文档共享位置和元数据的集合。
ms.openlocfilehash: 75c420deae5dfd9b441c7f73bf3565018d3bfbd6
ms.sourcegitcommit: 54f6cd5a704b36b76d110ee53a6d6c1c3e15f5a9
ms.translationtype: MT
ms.contentlocale: zh-CN
ms.lasthandoff: 09/24/2021
ms.locfileid: "59538364"
---
# <a name="documentsharinglocationcollectionsetting-soap"></a>DocumentSharingLocationCollectionSetting (SOAP)
**DocumentSharingLocationCollectionSetting** 元素表示一个用户设置，该设置是文档共享位置和元数据的集合。
[DocumentSharingLocationCollectionSetting (SOAP)](documentsharinglocationcollectionsetting-soap.md)
```XML
<DocumentSharingLocationCollectionSetting>
<DocumentSharingLocations />
</DocumentSharingLocationCollectionSetting>
```
**DocumentSharingLocationCollectionSetting**
## <a name="attributes-and-elements"></a>属性和元素
下面各部分介绍了属性、子元素和父元素。
### <a name="attributes"></a>Attributes
无。
### <a name="child-elements"></a>子元素
|**元素**|**说明**|
|:-----|:-----|
|[DocumentSharingLocations (SOAP)](documentsharinglocations-soap.md) <br/> |表示文档共享位置列表的位置和元数据。 <br/> |
### <a name="parent-elements"></a>父元素
|**元素**|**说明**|
|:-----|:-----|
|[UserSettings (SOAP)](usersettings-soap.md) <br/> |表示用户设置的集合。 <br/> |
## <a name="element-information"></a>元素信息
|||
|:-----|:-----|
|命名空间 <br/> |https://schemas.microsoft.com/exchange/2010/Autodiscover <br/> |
|架构名称 <br/> |自动发现架构 <br/> |
|验证文件 <br/> |Messages.xsd <br/> |
|可以为空 <br/> |True <br/> |
## <a name="see-also"></a>另请参阅
- [GetUserSettings 操作 (SOAP)](getusersettings-operation-soap.md)
- [自动发现 Web 服务引用Exchange](autodiscover-web-service-reference-for-exchange.md)
- [Exchange 2013 的 SOAP 自动发现 XML 元素](soap-autodiscover-xml-elements-for-exchange-2013.md)
| 30.015385 | 109 | 0.73552 | yue_Hant | 0.696405 |
ed2c3a9533126f210bd0ef5772d2006f858a7224 | 1,926 | md | Markdown | guide/english/certifications/javascript-algorithms-and-data-structures/es6/set-default-parameters-for-your-functions/index.md | smonem/freeCodeCamp | f03f05d53de38fbc84ba50f1b6ee156e77959698 | [
"BSD-3-Clause"
] | 2 | 2020-04-05T02:41:29.000Z | 2021-01-30T12:01:55.000Z | guide/english/certifications/javascript-algorithms-and-data-structures/es6/set-default-parameters-for-your-functions/index.md | smonem/freeCodeCamp | f03f05d53de38fbc84ba50f1b6ee156e77959698 | [
"BSD-3-Clause"
] | 12 | 2020-09-06T12:45:38.000Z | 2022-01-22T08:11:07.000Z | guide/english/certifications/javascript-algorithms-and-data-structures/es6/set-default-parameters-for-your-functions/index.md | smonem/freeCodeCamp | f03f05d53de38fbc84ba50f1b6ee156e77959698 | [
"BSD-3-Clause"
] | null | null | null | ---
title: Set Default Parameters for Your Functions
---
## Set Default Parameters for Your Functions
Remember to use Read-Search-Ask if you get stuck. Try to pair program and write your own code.
### Problem Explanation:
```javascript
const increment = (function() {
"use strict";
return function increment(number, value) {
return number + value;
};
})();
console.log(increment(5, 2)); // returns 7
console.log(increment(5)); // returns NaN
```
We'll be modifying the increment function so that the **number** parameter is incremented by 1 by default, by setting **value** to 1 if a value for **value** is not passed to the increment function.
### Hint: 1
Let's identify where the parameter **value** is in JS function
try to solve the problem now
### Hint: 2
Set **value** equal to something so that it is that value by default
try to solve the problem now
### Spoiler Alert!
Solution ahead!
## Basic Code Solution:
```javascript
const increment = (function() {
"use strict";
return function increment(number, value = 1) {
return number + value;
};
})();
console.log(increment(5, 2)); // returns 7
console.log(increment(5)); // returns NaN
```
### Code Explanation
* This section is pretty straightforward. Pass this section by setting the **value** parameter equal to 1. When the function comes across test cases where **value** has not been passed anything, then **value** will be assigned one by default.
Relevant Links:
[JavaScript default parameters](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Functions/Default_parameters)
## NOTES FOR CONTRIBUTIONS:
* DO NOT add solutions that are similar to any existing solutions. If you think it is similar but better, then try to merge (or replace) the existing similar solution.
* Add an explanation of your solution.
* Categorize the solution in one of the following categories — Basic, Intermediate and Advanced.
| 29.630769 | 242 | 0.728972 | eng_Latn | 0.992042 |
ed2c5e573e26ae0971ea48a85c52bde58069f576 | 4,060 | md | Markdown | docs/guides/DialogFlow.md | Palem1988/nlp-gauntlet | ef4f235f2ef1a61c5b55b13d799b69b4ca166351 | [
"BSD-3-Clause"
] | null | null | null | docs/guides/DialogFlow.md | Palem1988/nlp-gauntlet | ef4f235f2ef1a61c5b55b13d799b69b4ca166351 | [
"BSD-3-Clause"
] | null | null | null | docs/guides/DialogFlow.md | Palem1988/nlp-gauntlet | ef4f235f2ef1a61c5b55b13d799b69b4ca166351 | [
"BSD-3-Clause"
] | 1 | 2019-10-09T13:18:43.000Z | 2019-10-09T13:18:43.000Z | 1- Create an account with Google
2- Sign in to Dialog Flow using your Google Account (https://dialogflow.com (https://dialogflow.com/))
3- Create a new Agent and configure with intents
- [This tutorial](https://dialogflow.com/docs/tutorial-build-an-agent/create-customize-agent) is a good place to start with dialogflow.
- *NOTE: Since we only care about the NLP part of Dialogflow, there’s no need to create responses under each intent.*
4- Go to the google cloud project attached to the service account for this project
5- Create a new service account with the following parameters
6- Give it a name
7- Select the Dialogflow API Admin role
8- Create a private key in P12 format
9- Note the secret and save the key in your local file system
10- Create a java key store file to import the key provided by google into your salesforce org.
Open a terminal and type the following command:
`keytool -importkeystore -srckeystore <private-key-from-google.p12> -destkeystore keystorefile.jks -srcstoretype pkcs12 -srcstorepass notasecret -deststorepass notasecret -deststoretype jks -destalias google_cloud -srcalias privatekey`
This will create a java keystore file with name keystorefile.jks with a certificate named google_cloud, and password notasecret (what Google exports)
11- Next, go to Setup > Security > Certificate and Key Management and click "Import from Keystore“
12- Select the keystorefile you just created and enter the password (notasecret)
13- You should see a new self-signed cert called “google_cloud” after you save
14- Next, create a Named Credential for Google Dialog Flow API that uses the certificate that you just uploaded
Go to Setup > Administer > Security Controls > Named Credentials
- URL : https://dialogflow.googleapis.com
- Identity Type : Named Principal
- Authentication Protocol : JWT
- Issuer & Named Principal Subject : < your google cloud service account >
- Audiences: https://dialogflow.googleapis.com/google.cloud.dialogflow.v2.Sessions
- JWT Signing Certificate : < select the cert you previously created for this integration >
- Generate Authorization Header : Checked
- Allow Merge Fields in HTTP Header : Un-Checked
- Allow Merge Fields in HTTP Body : Un-Checked
15 - Next, we can try out the service integration by launching the Nlp Gauntlet Workbench in `/apex/ExternalNlpWorkbench`
Set the following parameters in the workbench and click the `Test` button :
- Type : `DIALOG_FLOW`
- Additional Parameters : Dialog flow requires a sessionId, by default this sessionID is set to the current timestamp, to override set this field to `sessionId=12345`
- Intent Confidence Threshold : Set to a value between 0 and 1, if empty it defaults to 0.7
- NER Confidence Threshold : Set to a value between 0 and 1, if empty it defaults to 0.7
- Named Credential : The Name of the Named Credential you created for this integration
- Model Id : The Project id for your dialog flow agent
- Language : Your desired language
- Time Zone : Your desired timezone
- Input Text : The text you would like to get predictions on. | 43.191489 | 235 | 0.778818 | eng_Latn | 0.853272 |
ed2de3044001b162629bcd70e9772d243e5ca1e5 | 852 | markdown | Markdown | _posts/2019-09-24-security-SymmetricCiper.markdown | rawk415/rawk415.github.io | 68b5364c03f434e64a5f536641b90551db9d1dad | [
"MIT"
] | null | null | null | _posts/2019-09-24-security-SymmetricCiper.markdown | rawk415/rawk415.github.io | 68b5364c03f434e64a5f536641b90551db9d1dad | [
"MIT"
] | null | null | null | _posts/2019-09-24-security-SymmetricCiper.markdown | rawk415/rawk415.github.io | 68b5364c03f434e64a5f536641b90551db9d1dad | [
"MIT"
] | null | null | null | ---
layout: post
title: "대칭키 암호"
subtitle: "현대 암호"
categories: devlog
tags: security
---
## 대칭키 암호
암호화와 복호화 과정에서 사용하는 키가 동일한 경우를 대칭키 암호방식이라고 한다.
예를 들어 과거의 암호방식은 모두 대칭키 암호이다. (스키테일, 단일치환, 시저, 비제네르)
## 대칭키 암호의 다양한 이름
### 공통키 암호
공통으로 같은 키를 사용하기 때문에 공통키 암호라고 부른다.
### 관용 암호
기원전부터 관용적으로 해왔던 암호다.
### 비밀키 암호
송 수신자가 안전하게 메시지를 주고 바드여면 키를 비밀리에 간직해야한다.
### 공유키 암호
송 수신자가 공유해야한다.
---
## DES(Data Encryption Standard)
1977년 미국의 연방정보처리표준규격(FIPS)으로 채택한 대칭형 블록암호
64비트의 블록(평문을 64비트 단위로 나눈다)이다.
이중 8비트는 패러티 비트이고 56비트를 암호화에 사용한다.
`페이스텔 구조` (Feistel Structure)이다.(그물망 구조)
### round
64비트를 절반으로 쪼갠다.
왼쪽 32비트는 subkey의 round함수의 출력값과 xor연산을 하고
오른족 32비트는 그대로 둔다.
한 라운드가 끝나면 좌, 우를 변경한다.
### Sub Key
56비트의 키를 키모듈에 넣으면 16개의 서브키를 만들어낸다.
### 페이스텔 구조
16번의 라운드를 반복 수행해서 암호화한다.
### spn 구조
substitution : 치환
permutation : 순열(전치)
Network
전치와 치환을 모두 사용한 암호화 방식 | 16.075472 | 51 | 0.678404 | kor_Hang | 1.00001 |
ed2e186dfb509acb944b54689fefd41fec48a1d4 | 3,136 | md | Markdown | README.md | alexanderswerdlow/dotfiles | 8994813e849bb7706321049d6b20916e04ab3dd9 | [
"MIT"
] | null | null | null | README.md | alexanderswerdlow/dotfiles | 8994813e849bb7706321049d6b20916e04ab3dd9 | [
"MIT"
] | null | null | null | README.md | alexanderswerdlow/dotfiles | 8994813e849bb7706321049d6b20916e04ab3dd9 | [
"MIT"
] | null | null | null | # Alex's Dotfiles
### Before you re-install
First, go through the checklist below to make sure you didn't forget anything before you wipe your hard drive.
- Did you commit and push any changes/branches to your git repositories?
- Did you remember to save all important documents from non-iCloud directories?
- Did you save all of your work from apps which aren't synced through iCloud?
- Did you remember to export important data from your local database?
- Did you update [mackup](https://github.com/lra/mackup) to the latest version and ran `mackup backup`?
### Installing macOS cleanly
After going to our checklist above and making sure you backed everything up, we're going to cleanly install macOS with the latest release. Follow [this article](https://www.imore.com/how-do-clean-install-macos) to cleanly install the latest macOS version.
### Setting up your Mac
If you did all of the above you may now follow these install instructions to setup a new Mac.
1.
For macOS:
```
xcode-select --install
sh -c "$(curl -fsSL https://raw.githubusercontent.com/alexanderswerdlow/dotfiles/master/install.sh)"
```
For Ubuntu:
```
wget --no-check-certificate --no-cache --no-cookies -O - https://raw.githubusercontent.com/alexanderswerdlow/dotfiles/master/install.sh | sh
```
2. After mackup is synced with your cloud storage, restore preferences by running `mackup restore`
3. Restart your computer to finalize the process
Your Mac is now ready to use!
> Note: you can use a different location than `~/.dotfiles` if you want. Just make sure you also update the reference in the [`.zshrc`](./.zshrc) file.
### Non-automated Setup (Dangerous!!!)
The commands below disable important macOS security features and should not be taken lightly. They will make it much easier for malware to break things and/or be more invasive. I decide to disable these features both for convinience (i.e. macOS doesn't need to verify the signature of every program, make it diffcult to open some programs etc.) and because I've run into several programs (specifically for development) that require SIP to be disabled anyway.
I've taken these commands from [here](https://www.naut.ca/blog/2020/11/13/forbidden-commands-to-liberate-macos/)
- Disable GateKeeper: `sudo spctl --master-disable`
- Disable Library Validation: `sudo defaults write /Library/Preferences/com.apple.security.libraryvalidation.plist DisableLibraryValidation -bool true`
The following commands must be executed from recovery mode:
- Disable SIP: `csrutil disable`
- Disable Apple Mobile File Integrity: `nvram boot-args="amfi_get_out_of_my_way=1"`
If you want to disable any Apple programs from bypassing the Network Extensions API, see [here](https://tinyapps.org/blog/202010210700_whose_computer_is_it.html)
### More Info
Installs iTerm2, oh-my-zsh, and the [Powerlevel10k theme](https://github.com/romkatv/powerlevel10k)
### Additional Programs
- Wolfram Desktop
- PDF Expert
- Texpad
- Forklift
- Numi
- Alfred
- WiFi Explorer Pro
- Wireguard
- Matlab
## Thanks To...
[Dries's Dotfiles](https://github.com/driesvints/dotfiles) for the initial setup of the repo.
| 42.378378 | 458 | 0.770727 | eng_Latn | 0.968972 |
ed2e54d5143fc72780071ee4889774dc08bd616a | 3,038 | md | Markdown | content/ruby/place_order_vlan.rb.md | FernandoOjeda/githubio_source | 5b764714f4fc1e4de41f247305705b9b2c8d4251 | [
"Apache-2.0"
] | null | null | null | content/ruby/place_order_vlan.rb.md | FernandoOjeda/githubio_source | 5b764714f4fc1e4de41f247305705b9b2c8d4251 | [
"Apache-2.0"
] | null | null | null | content/ruby/place_order_vlan.rb.md | FernandoOjeda/githubio_source | 5b764714f4fc1e4de41f247305705b9b2c8d4251 | [
"Apache-2.0"
] | null | null | null | ---
title: "place_order_vlan.rb"
description: "place_order_vlan.rb"
date: "2017-11-23"
classes:
- "SoftLayer_Product_Item_Price"
- "SoftLayer_Account"
- "SoftLayer_Product_Package"
- "SoftLayer_Product_Order"
- "SoftLayer_Container_Product_Order_Network_Vlan"
tags:
- "vlans"
---
```
# Example to create a new VLAN
# the script uses the placeOrder method to order
# a new VLAN with 32 static IP address
#
# Important manual page
# http://sldn.softlayer.com/reference/services/SoftLayer_Product_Order
# http://sldn.softlayer.com/reference/services/SoftLayer_Product_Order/placeOrder
# http://sldn.softlayer.com/reference/services/SoftLayer_Product_Order/verifyOrder
# http://sldn.softlayer.com/reference/datatypes/SoftLayer_Container_Product_Order_Network_Vlan
# http://sldn.softlayer.com/reference/datatypes/SoftLayer_Product_Item_Price
#
# License: http://sldn.softlayer.com/article/License
# Author: SoftLayer Technologies, Inc. <[email protected]>
require 'softlayer_api'
require 'pp'
# Your SoftLayer API username and key.
USERNAME = 'set me'
API_KEY = 'set me'
# Build a skeleton SoftLayer_Container_Product_Order_Network_Vlan object
# to model the order for the new VLAN
order_data = {
'complexType' => 'SoftLayer_Container_Product_Order_Network_Vlan',
'location' => 'AMSTERDAM',
'packageId' => 0,
# Build a skeleton SoftLayer_Product_Item_Price objects. These objects contain
# much more than Ids, but SoftLayer's ordering system only needs the price's id
# to know what you want to order.
# to get the list of valid prices for the package
# use the SoftLayer_Product_Package:getItems method
# e.g.
# productPackageService = client['SoftLayer_Product_Package']
# prices = productPackageService.getItems(id = packageID)
'prices' => [
{
'complexType' => 'SoftLayer_Product_Item_Price',
# The price for the new Public Network Vlan
'id' => 201_8
},
{
'complexType' => 'SoftLayer_Product_Item_Price',
# The price for 32 Static Public IP Addresses
'id' => 367_16
}
],
'quantity' => 1,
'sendQuoteEmailFlag' => true,
'name' => 'myVLANnew',
# The router ID where the VLAN will be created
# to get the list of routers in your account
# use the SoftLayer_Account::getRouters method
'routerId' => 117_960
}
# Declaring the API client
client = SoftLayer::Client.new(username: USERNAME, api_key: API_KEY)
product_order_service = client.service_named('SoftLayer_Product_Order')
begin
# verifyOrder() will check your order for errors. Replace this with a call
# to placeOrder() when you're ready to order. Both calls return a receipt
# object that you can use for your records.
# Once your order is placed it'll go through SoftLayer's approval and
# provisioning process.
response = product_order_service.verifyOrder(order_data)
pp response
rescue StandardError => exception
puts "Unable to place the order. : #{exception}"
end
```
| 33.384615 | 95 | 0.724819 | eng_Latn | 0.660406 |
ed2ebbb3631368e609e6d0bd8b198612f95850d0 | 10,944 | md | Markdown | README.md | sunset1995/pytorch-layoutnet | 35dfb25592bfa9765709db1e90d2a8637f11c157 | [
"MIT"
] | 155 | 2018-08-13T05:26:35.000Z | 2022-03-26T13:13:24.000Z | README.md | sunset1995/pytorch-layoutnet | 35dfb25592bfa9765709db1e90d2a8637f11c157 | [
"MIT"
] | 25 | 2018-08-17T08:39:51.000Z | 2022-01-11T01:08:37.000Z | README.md | sunset1995/pytorch-layoutnet | 35dfb25592bfa9765709db1e90d2a8637f11c157 | [
"MIT"
] | 44 | 2018-08-17T19:53:05.000Z | 2022-03-31T06:25:37.000Z | # pytorch-layoutnet
**News: Check out our new project [HoHoNet](https://github.com/sunset1995/HoHoNet) on this task and more!**\
**News: Check out our new project [HorizonNet](https://github.com/sunset1995/HorizonNet) on this task.**
This is an unofficial implementation of CVPR 18 [paper](https://arxiv.org/abs/1803.08999) "LayoutNet: Reconstructing the 3D Room Layout from a Single RGB Image". [Official](https://github.com/zouchuhang/LayoutNet) layout dataset are all converted to `.png` and pretrained models are converted to pytorch `state-dict`.
What difference from official:
- **Architecture**: Only joint *bounday branch* and *corner branch* are implemented as the paper states that "Training with 3D regressor has a small impact".
- **Pre-processing**: Implementation of *line segment detector* and *pano image alignment* are converted from matlab to python in `pano.py` and `pano_lsd_align.py`.
- **Post-processing**: No 3D layout optimization. Alternatively, this repo implement a gradient ascent optimizing the similar loss. (see below for more detail)
Overview of the pipeline:
Use this repo, you can:
- extract/visualize layout of your own 360 images with my trained network
- reproduce official experiments
- train on your own dataset
- quantitative evaluatation (3D IoU, Corner Error, Pixel Error)
## Requirements
- Python 3
- pytorch>=0.4.1
- numpy
- scipy
- Pillow
- torchfile
- opencv-python>=3.1 (for pre-processing)
- open3d (for layout 3D viewer)
- shapely (for layout 3D viewer)
## Visualization
### 1. Preparation
- Get your fasinated 360 room images. I will use `assert/demo.png` for example.
- 
- Prepare the enviroment to run the python scripts.
- Download the trained model from [here (350M)](https://drive.google.com/file/d/1ZlXc4DLgOrkDLW6kQbCY-wOJ8bw4DYu2/view?usp=sharing). Put the 3 files extracted from the downloaded zip under `ckpt/` folder.
- So you will get `ckpt/epoch_30_*.pth`
### 2. Pre-processing (Align camera pose with floor)
- Pre-process the above `assert/demo.png` by firing below command. See `python visual_preprocess.py -h` for more detailed script description.
```
python visual_preprocess.py --img_glob assert/demo.png --output_dir assert/output_preprocess/
```
- Arguments explanation:
- `--img_glob` telling the path to your fasinated 360 room image(s).
- `--output_dir` telling the path to the directory for dumping the results.
- *Hint*: you can use shell-style wildcards with quote (e.g. "my_fasinated_img_dir/\*png") to process multiple images in one shot.
- Under the given `--output_dir`, you will get results like below and prefix with source image basename.
- The aligned rgb images `[SOURCE BASENAME]_aligned_rgb.png` and line segments images `[SOURCE BASENAME]_aligned_line.png`
- `demo_aligned_rgb.png` | `demo_aligned_line.png`
:--------------------: | :---------------------:
 | 
- The detected vanishing points `[SOURCE BASENAME]_VP.txt` (Here `demo_VP.txt`)
```
-0.006676 -0.499807 0.866111
0.000622 0.866128 0.499821
0.999992 -0.002519 0.003119
```
### 3. Layout Prediction with LayoutNet
- Predict the layout from above aligned image and line segments by firing below command.
```
python visual.py --path_prefix ckpt/epoch_30 --img_glob assert/output_preprocess/demo_aligned_rgb.png --line_glob assert/output_preprocess/demo_aligned_line.png --output_dir assert/output
```
- Arguments explanation:
- `--path_prefix` prefix path to the trained model.
- `--img_glob` path to the VP aligned image.
- `--line_glob` path to the corresponding line segment image of the VP aligned image.
- `--output_dir` path to the directory to dump the results.
- *Hint*: for the two glob, you can use wildcards with quote
- *Hint*: for better result, you can add `--flip`, `--rotate 0.25 0.5 0.75`, `--post_optimization`
- you will get results like below and prefix with source image basename.
- The model's output corner/edge probability map `[SOURCE BASENAME]_[cor|edg].png`
- `demo_aligned_rgb_cor.png` | `demo_aligned_rgb_edg.png`
:------------------------: | :------------------------:
 | 
- The extracted layout and all in one image `[SOURCE BASENAME]_[bon|all].png`
- `demo_aligned_rgb_bon.png` | `demo_aligned_rgb_all.png`
:------------------------: | :------------------------:
 | 
- The extracted corners of the layout `[SOURCE BASENAME]_cor_id.txt`
```
104.928192 186.603119
104.928192 337.168579
378.994934 177.796646
378.994934 346.994629
649.976440 183.446518
649.976440 340.711731
898.234619 190.629089
898.234619 332.616364
```
### 4. Layout 3D Viewer
- A pure python script to visualize the predicted layout in 3D using points cloud. Below command will visualize the result store in `assert/`
```
python visual_3d_layout.py --ignore_ceiling --img assert/output_preprocess/demo_aligned_rgb.png --layout assert/output/demo_aligned_rgb_cor_id.txt
```
- Arguements explanationL
- `--img` path to aligned 360 image
- `--layout` path to the txt stroing the `cor_id` (predicted or ground truth)
- `--ignore_ceiling` prevent rendering ceiling
- for more arguments, see `python visual_3d_layout.py -h`
- 
- In the window, you can use mouse and scroll to change the viewport
## Preparation for Training
- Download offical [data](https://github.com/zouchuhang/LayoutNet#data) and [pretrained model](https://github.com/zouchuhang/LayoutNet#pretrained-model) as below
```
/pytorch-layoutnet
/data
| /origin
| /data (download and extract from official)
| /gt (download and extract from official)
/ckpt
/panofull_*_pretrained.t7 (download and extract from official)
```
- Execute `python torch2pytorch_data.py` to convert `data/origin/**/*` to `data/train`, `data/valid` and `data/test` for pytorch data loader. Under these folder, `img/` contains all raw rgb `.png` while `line/`, `edge/`, `cor/` contain preprocessed Manhattan line segment, ground truth boundary and ground truth corner respectively.
- [optional] Use `torch2pytorch_pretrained_weight.py` to convert official pretrained pano model to `encoder`, `edg_decoder`, `cor_decoder` pytorch `state_dict` (see `python torch2pytorch_pretrained_weight.py -h` for more detailed). examples:
- to convert layout pretrained only
```
python torch2pytorch_pretrained_weight.py --torch_pretrained ckpt/panofull_joint_box_pretrained.t7 --encoder ckpt/pre_full_encoder.pth --edg_decoder ckpt/pre_full_edg_decoder.pth --cor_decoder ckpt/pre_full_cor_decoder.pth
```
- to convert full pretrained (layout regressor branch will be ignored)
```
python torch2pytorch_pretrained_weight.py --torch_pretrained ckpt/panofull_joint_box_pretrained.t7 --encoder ckpt/pre_full_encoder.pth --edg_decoder ckpt/pre_full_edg_decoder.pth --cor_decoder ckpt/pre_full_cor_decoder.pth
```
## Training
See `python train.py -h` for detailed arguments explanation.
The default training strategy is the same as official. To launch experiments as official "corner+boundary" setting (`--id` is used to identified the experiment and can be named youself):
```
python train.py --id exp_default
```
To train only using RGB channels as input (no Manhattan line segment):
```
python train.py --id exp_rgb --input_cat img --input_channels 3
```
## Gradient Ascent Post Optimization
Instead of offical 3D layout optimization with sampling strategy, this repo implement a gradient ascent optimization algorithm to minimize the similar loss of official.
The process abstract below:
1. greedily extract the cuboid parameter from corner/edge probability map
- The cuboid are consist of the 6 parameters (`cx`, `cy`, `dx`, `dy`, `theta`, `h`)
- `corner probability map` | `edge probability map`
:------------------------: | :------------------------:
 | 
2. sample points alone the cuboid boundary and project them to equirectangular formatted corner/edge probability map
- The sample projected points are visualized as green dot
- <img src="assert/output/demo_aligned_rgb_all.png" width=300>
3. for each projected sample point, getting value by bilinear interpolation from nearest 4 neighbor pixel on the corner/edge probability map
4. all the sampled values are reduced to a single scalar called score
5. compute the gradient for the 6 cuboid parameter to maximize the score
6. Iterative apply gradient ascent (step 2 through 6)
It take less than 2 seconds on CPU and found slightly better result than offical reported.
## Quantitative Evaluation
See `python eval.py -h` for more detailed arguments explanation. To get the result from my trained network (link above):
```
python eval.py --path_prefix ckpt/epoch_30 --flip --rotate 0.333 0.666
```
To evaluate with gradient ascent post optimization:
```
python eval.py --path_prefix ckpt/epoch_30 --flip --rotate 0.333 0.666 --post_optimization
```
#### Dataset - PanoContext
| exp | 3D IoU(%) | Corner error(%) | Pixel error(%) |
| :-: | :------: | :------: | :--------------: |
| Official best | `75.12` | `1.02` | `3.18` |
| ours rgb only | `71.42` | `1.30` | `3.83` |
| ours rgb only <br> w/ gd opt | `72.52` | `1.50` | `3.66` |
| ours | `75.11` | `1.04` | `3.16` |
| ours <br> w/ gd opt | **`76.90`** | **`0.93`** | **`2.81`** |
#### Dataset - Stanford 2D-3D
| exp | 3D IoU(%) | Corner error(%) | Pixel error(%) |
| :-: | :------: | :------: | :--------------: |
| Official best | `77.51` | `0.92` | **`2.42`** |
| ours rgb only | `70.39` | `1.50` | `4.28` |
| ours rgb only <br> w/ gd opt | `71.90` | `1.35` | `4.25` |
| ours | `75.49` | `0.96` | `3.07` |
| ours <br> w/ gd opt | **`78.90`** | **`0.88`** | `2.78` |
## References
- [LayoutNet: Reconstructing the 3D Room Layout from a Single RGB Image](https://arxiv.org/abs/1803.08999)
- Chuhang Zou, Alex Colburn, Qi Shan, Derek Hoiem
- CVPR2018
```
@inproceedings{zou2018layoutnet,
title={LayoutNet: Reconstructing the 3D Room Layout from a Single RGB Image},
author={Zou, Chuhang and Colburn, Alex and Shan, Qi and Hoiem, Derek},
booktitle={Proceedings of the IEEE Conference on Computer Vision and Pattern Recognition},
pages={2051--2059},
year={2018}
}
```
- [Official torch implementation](https://github.com/zouchuhang/LayoutNet)
| 52.869565 | 332 | 0.695815 | eng_Latn | 0.892319 |
ed2ec5faabc5e2c43cd6c7d89d44f9419a455fad | 866 | md | Markdown | _pages/about.md | ssun32/ssun32.github.io | 0acc72170abeea1bcb1be1554f04f5b9189e321f | [
"MIT"
] | null | null | null | _pages/about.md | ssun32/ssun32.github.io | 0acc72170abeea1bcb1be1554f04f5b9189e321f | [
"MIT"
] | null | null | null | _pages/about.md | ssun32/ssun32.github.io | 0acc72170abeea1bcb1be1554f04f5b9189e321f | [
"MIT"
] | null | null | null | ---
permalink: /
title: "About me"
excerpt: "About me"
author_profile: true
redirect_from:
- /about/
- /about.html
---
I am a Ph.D. student (2017-2022) in Department of Computer Science at Johns Hopkins University (JHU) and also a member of the Center for Language and Speech Processing (CLSP). I am fortunately advised by [Kevin Duh](https://www.cs.jhu.edu/~kevinduh/).
Before joining JHU-CLSP, I was a research engineer at Baidu-I2R Research Center (BIRC), Singapore, and did research in Relation Extraction and Sentiment Analysis with [Jian Su](https://colips.org/~sujian/).
Prior to that, I obtained a B.S. in Electrical Engineering and Computer Science from University of California, Berkeley.
My research interests focus in natural language processing, particularly in cross-lingual information retrieval and quality estimation for machine translation.
| 54.125 | 251 | 0.773672 | eng_Latn | 0.968746 |
ed2f5bfb7931150f993cb9715160c9cd1b13b6f5 | 1,646 | md | Markdown | docs/2014/database-engine/configure-windows/check-the-odbc-sql-server-driver-version-windows.md | bingenortuzar/sql-docs.es-es | 9e13730ffa0f3ce461cce71bebf1a3ce188c80ad | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-04-26T21:26:08.000Z | 2021-04-26T21:26:08.000Z | docs/2014/database-engine/configure-windows/check-the-odbc-sql-server-driver-version-windows.md | jlporatti/sql-docs.es-es | 9b35d3acbb48253e1f299815df975f9ddaa5e9c7 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/2014/database-engine/configure-windows/check-the-odbc-sql-server-driver-version-windows.md | jlporatti/sql-docs.es-es | 9b35d3acbb48253e1f299815df975f9ddaa5e9c7 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Comprobar la versión del controlador ODBC de SQL Server (Windows) | Microsoft Docs
ms.custom: ''
ms.date: 06/13/2017
ms.prod: sql-server-2014
ms.reviewer: ''
ms.technology: configuration
ms.topic: conceptual
helpviewer_keywords:
- driver version number [ODBC]
- ODBC drivers, version number
ms.assetid: 43451080-a562-4231-b1d4-1ba35ca0ea79
author: MikeRayMSFT
ms.author: mikeray
manager: craigg
ms.openlocfilehash: dbb275d8ced2855b1842bba9a1c11e5543d6a838
ms.sourcegitcommit: 3026c22b7fba19059a769ea5f367c4f51efaf286
ms.translationtype: MT
ms.contentlocale: es-ES
ms.lasthandoff: 06/15/2019
ms.locfileid: "62786664"
---
# <a name="check-the-odbc-sql-server-driver-version-windows"></a>Comprobar la versión del controlador ODBC de SQL Server (Windows)
Su equipo puede contener varios controladores ODBC, de [!INCLUDE[msCoName](../../includes/msconame-md.md)] y de otras empresas. En este tema se describe cómo usar el **Administrador de orígenes de datos ODBC** de Windows para comprobar la versión de los controladores ODBC instalados.
## <a name="SSMSProcedure"></a>
#### <a name="to-check-the-odbc-sql-server-driver-version-32-bit-odbc"></a>Para comprobar la versión del controlador ODBC de SQL Server (ODBC de 32 bits)
- En el **Administrador de origen de datos ODBC**, haga clic en la pestaña **Controladores** .
La información de la entrada de Microsoft [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] se muestra en la columna **Versión** .
## <a name="see-also"></a>Vea también
[Abrir el Administrador de orígenes de datos ODBC](open-the-odbc-data-source-administrator.md)
| 43.315789 | 288 | 0.752126 | spa_Latn | 0.60717 |
ed2f5da2577fb3486f65ee6bd10220decff0ee37 | 898 | md | Markdown | README.md | sdobber/BallroomSkatingSystem.jl | 76d6ca9182a3bff5fc92a1941242030842abbe7a | [
"MIT"
] | null | null | null | README.md | sdobber/BallroomSkatingSystem.jl | 76d6ca9182a3bff5fc92a1941242030842abbe7a | [
"MIT"
] | 1 | 2022-02-17T19:11:19.000Z | 2022-02-17T19:11:21.000Z | README.md | sdobber/BallroomSkatingSystem.jl | 76d6ca9182a3bff5fc92a1941242030842abbe7a | [
"MIT"
] | null | null | null | # BallroomSkatingSystem
[](https://sdobber.github.io/BallroomSkatingSystem.jl/dev)
[](https://github.com/sdobber/BallroomSkatingSystem.jl/actions)
[](https://codecov.io/gh/sdobber/BallroomSkatingSystem.jl)
This package implements the skating system of compiling scores in ballroom dance competitions. See the documentation for usage and examples.
## :warning: Disclaimer
This package has not been tested against all corner cases that might emerge in real dancing tournaments.
## Installation
BallroomSkatingSystem.jl is a registered package. To install, type `]` at the Julia REPL to enter package mode, and type
```
add BallroomSkatingSystem
```
| 42.761905 | 155 | 0.790646 | eng_Latn | 0.598314 |
ed2f7543853bf5637ed357f5dbc7857220c8a7d9 | 3,884 | md | Markdown | docs/writing-types.md | joewalker/gcli | 672ddac06402c82c44b4e45fe9336347b9c810bb | [
"Apache-2.0"
] | 173 | 2015-01-03T12:39:59.000Z | 2021-11-08T10:22:09.000Z | docs/writing-types.md | mozilla/gcli | 37c52edaf2c924b238bffc0b355fb78a01b860a5 | [
"Apache-2.0"
] | 2 | 2015-02-10T14:12:04.000Z | 2015-03-26T14:15:15.000Z | docs/writing-types.md | enterstudio/gcli | 672ddac06402c82c44b4e45fe9336347b9c810bb | [
"Apache-2.0"
] | 28 | 2015-02-09T12:53:28.000Z | 2020-03-06T22:56:48.000Z |
# Writing Types
Commands are a fundamental building block because they are what the users
directly interacts with, however they are built on ``Type``s. There are a
number of built in types:
* string. This is a JavaScript string
* number. A JavaScript number
* boolean. A JavaScript boolean
* selection. This is an selection from a number of alternatives
* delegate. This type could change depending on other factors, but is well
defined when one of the conversion routines is called.
There are a number of additional types defined by Pilot and GCLI as
extensions to the ``selection`` and ``delegate`` types
* setting. One of the defined settings
* settingValue. A value that can be applied to an associated setting.
* command. One of the defined commands
Most of our types are 'static' e.g. there is only one type of 'string', however
some types like 'selection' and 'delegate' are customizable.
All types must inherit from Type and have the following methods:
/**
* Convert the given <tt>value</tt> to a string representation.
* Where possible, there should be round-tripping between values and their
* string representations.
*/
stringify: function(value) { return 'string version of value'; },
/**
* Convert the given <tt>str</tt> to an instance of this type.
* Where possible, there should be round-tripping between values and their
* string representations.
* @return Conversion
*/
parse: function(str) { return new Conversion(...); },
/**
* The plug-in system, and other things need to know what this type is
* called. The name alone is not enough to fully specify a type. Types like
* 'selection' and 'delegate' need extra data, however this function returns
* only the name, not the extra data.
* <p>In old bespin, equality was based on the name. This may turn out to be
* important in Ace too.
*/
name: 'example',
In addition, defining the following function can be helpful, although Type
contains default implementations:
* nudge(value, by)
Type, Conversion and Status are all declared by commands.js.
The values produced by the parse function can be of any type, but if you are
producing your own, you are strongly encouraged to include properties called
``name`` and ``description`` where it makes sense. There are a number of
places in GCLI where the UI will be able to provide better help to users if
your values include these properties.
# Writing Fields
Fields are visual representations of types. For simple types like string it is
enough to use ``<input type=...>``, however more complex types we may wish to
provide a custom widget to allow the user to enter values of the given type.
This is an example of a very simple new password field type:
function PasswordField(doc) {
this.doc = doc;
}
PasswordField.prototype = Object.create(Field.prototype);
PasswordField.prototype.createElement = function(assignment) {
this.assignment = assignment;
this.input = dom.createElement(this.doc, 'input');
this.input.type = 'password';
this.input.value = assignment.arg ? assignment.arg.text : '';
this.onKeyup = function() {
this.assignment.setValue(this.input.value);
}.bind(this);
this.input.addEventListener('keyup', this.onKeyup, false);
this.onChange = function() {
this.input.value = this.assignment.arg.text;
};
this.assignment.onAssignmentChange.add(this.onChange, this);
return this.input;
};
PasswordField.prototype.destroy = function() {
this.input.removeEventListener('keyup', this.onKeyup, false);
this.assignment.onAssignmentChange.remove(this.onChange, this);
};
PasswordField.claim = function(type) {
return type.name === 'password' ? Field.claim.MATCH : Field.claim.NO_MATCH;
};
| 36.299065 | 81 | 0.710608 | eng_Latn | 0.998468 |
ed305520d80cc98de671c85e2ae3b339c5e32c8f | 3,160 | md | Markdown | 05_models/03_saving.md | UnionOfRAD/manual | 7e8d6f582d7e52444760d9e115578361864f7173 | [
"BSD-3-Clause"
] | 8 | 2015-04-08T14:42:27.000Z | 2022-01-08T23:07:15.000Z | 05_models/03_saving.md | UnionOfRAD/manual | 7e8d6f582d7e52444760d9e115578361864f7173 | [
"BSD-3-Clause"
] | 26 | 2015-01-29T22:50:50.000Z | 2020-05-05T21:44:42.000Z | 05_models/03_saving.md | UnionOfRAD/manual | 7e8d6f582d7e52444760d9e115578361864f7173 | [
"BSD-3-Clause"
] | 18 | 2015-03-01T20:05:01.000Z | 2021-09-05T13:29:51.000Z | # Saving Entities
Persisting data means that new data is being stored or updated. Before you can save your data, you have to initialize a `Model`. This can either be done with the `find()` methods shown earlier or—if you want to create a new entity with the static `create()` method. `save()` is a method (called on record and document objects) to create or update the record or document in the database that corresponds to `$entity`.
```php
// Create a new post, add title and author, then save.
$post = Posts::create();
$post->title = 'My first blog post.';
$post->author = 'Michael';
$post->save();
// Same as above.
$post = Posts::create([
'title' => 'My first blog post.',
'author' => 'Michael'
]);
$post->save();
// Find the first blog post and change the author
$post = Posts::first();
$post->author = 'John';
$post->save();
```
Note that `save()` also validates your data if you have any validation rules defined in your model. It returns either `true` or `false`, depending on the success of the validation and saving process. You'll normally use this in your controller like so:
```php
public function add() {
$post = Posts::create();
if($this->request->data && $post->save($this->request->data)) {
$this->redirect('Posts::index');
}
return compact('post');
}
```
This redirects the user only to the `index` action if the saving process was successful. If not, the form is rendered again and errors are shown in the view.
To override the validation checks and save anyway, you can pass the `'validate'` option:
```php
$post->title = "We Don't Need No Stinkin' Validation";
$post->body = "I know what I'm doing.";
$post->save(null, ['validate' => false]);
```
<div class="note note-hint">
There is more information about validation and how to use the
<code>validates()</code> in the <a href="./validation">Validation</a> chapter.
</div>
The `$entity` parameter is the record or document object to be saved in the database. This parameter is implicit and should not be passed under normal circumstances. In the above example, the call to `save()` on the `$post` object is transparently proxied through to the `Posts` model class, and `$post` is passed in as the `$entity` parameter. The `$data` parameter is for any data that should be assigned to the record before it is saved.
There is also an `$options` parameter that has the following settable elements.
* `'callbacks'` _boolean_: If `false`, all callbacks will be disabled before executing. Defaults to `true`.
* `'validate'` _mixed_: If `false`, validation will be skipped, and the record will be immediately saved. Defaults to `true`. May also be specified as an array, in which case it will replace the default validation rules specified in the `$validates` property of the model.
* `'events'` _mixed_: A string or array defining one or more validation _events_. Events are different contexts in which data events can occur, and correspond to the optional `'on'` key in validation rules. They will be passed to the validates() method if `'validate'` is not `false`.
* `'whitelist'` _array_: An array of fields that are allowed to be saved to this record.
| 50.967742 | 441 | 0.721835 | eng_Latn | 0.998547 |
ed305d8aeaa68f829a15afa2e5b056185dc0ddf8 | 7,155 | md | Markdown | docs/web/content/development/recipes/recipe_tutorial.md | rameshpolishetti/mashling | 31ed5b62067a79555c5aa53bea9b583a97f978a1 | [
"BSD-3-Clause"
] | 82 | 2017-10-01T16:30:54.000Z | 2021-01-22T02:08:18.000Z | docs/web/content/development/recipes/recipe_tutorial.md | rameshpolishetti/mashling | 31ed5b62067a79555c5aa53bea9b583a97f978a1 | [
"BSD-3-Clause"
] | 128 | 2017-10-06T06:42:15.000Z | 2022-01-12T18:21:57.000Z | docs/web/content/development/recipes/recipe_tutorial.md | rameshpolishetti/mashling | 31ed5b62067a79555c5aa53bea9b583a97f978a1 | [
"BSD-3-Clause"
] | 17 | 2017-10-23T19:41:51.000Z | 2019-06-29T14:28:48.000Z | ---
title: Build recipe example
weight: 4210
pre: "<i class=\"fa fa-asterisk\" aria-hidden=\"true\"></i> "
---
In this example we will create a mashling gateway recipe that conditionally invokes a PetStore API.
The recipe will either register or retrieve pet data. The scenario assumes that only pets with a category name of **DOG** or **CAT** are supported. If an attempt is made to register any other kind of pet the gateway responds with an error message without hitting the PetStore backend.
Open an editor and define event triggers like the following:
```json
{
"mashling_schema": "1.0",
"gateway": {
"name": "MyProxy",
"version": "1.0.0",
"description": "This is a simple proxy.",
"triggers": [
{
"name": "MyProxy",
"description": "Animals rest trigger - PUT animal details",
"type": "github.com/TIBCOSoftware/mashling/ext/flogo/trigger/gorillamuxtrigger",
"settings": {
"port": "9096"
},
"handlers": [
{
"dispatch": "Retrieve",
"settings": {
"autoIdReply": "false",
"method": "GET",
"path": "/pets/{petId}",
"useReplyHandler": "false"
}
},
{
"dispatch": "Register",
"settings": {
"autoIdReply": "false",
"method": "PUT",
"path": "/pets",
"useReplyHandler": "false"
}
}
]
}
],
```
There are two handlers created for this HTTP trigger. One for retrieving the pet data through an HTTP GET operation and the other for registering a pet through an HTTP PUT operation. For the details of the handler configuration, see the documentation at https://github.com/TIBCOSoftware/mashling/tree/master/ext/flogo/trigger/gorillamuxtrigger
Add a dispatches section:
```json
"dispatches": [
{
"name": "Retrieve",
"routes": [
{
"steps": [
{
"service": "GetPet",
"input": {
"method": "GET",
"pathParams.id": "${payload.pathParams.petId}"
}
}
],
"responses": [
{
"if": "GetPet.response.body.status != 'available'",
"error": true,
"output": {
"code": 404,
"data": {"error": "Pet is not available."}
}
},
{
"if": "GetPet.response.body.status == 'available'",
"error": false,
"output": {
"code": 200,
"data": "${GetPet.response.body}"
}
}
]
}
]
},
{
"name": "Register",
"routes": [
{
"if": "payload.content.category.name == 'DOG' || payload.content.category.name == 'CAT'",
"steps": [
{
"service": "PutPet",
"input": {
"inputs.content": "${payload.content}"
}
}
],
"responses": [
{
"if": "PutPet.response.outputs.code != 200",
"error": true,
"output": {
"code": 400,
"data": { "error": "Pet is not registered."}
}
},
{
"if": "PutPet.response.outputs.code == 200",
"error": false,
"output": {
"code": 200,
"data": "${PutPet.response.outputs.data}"
}
}
]
},
{
"steps": [
{
"service": "InvalidAnimal",
"input": {
"parameters.content": "${payload.content}"
}
}
],
"responses": [
{
"error": false,
"output": {
"code": 400,
"data": {"error": "${InvalidAnimal.response.result.msg}"}
}
}
]
}
]
}
],
```
Both **Retrieve** and **Register** routes have their own steps and their own response handling defined. Note that **Register** has a step which is executed only when a dog or cat is registered.
If no condition is defined for a set of steps it is considered the default route. Only one route is executed. Thus, in the **Register** route, the InvalidAnimal service is executed only when the request is for an animal other than a dog or a cat.
Add the services section below, which defines each service reference used in the dispatch section above:
```json
"services": [
{
"name": "GetPet",
"description": "Make GET calls against a remote HTTP service using http endpoint.",
"type": "http",
"settings": {
"url": "http://petstore.swagger.io/v2/pet/:id"
}
},
{
"name": "PutPet",
"description": "Make PUT calls against a remote HTTP service using a Flogo flow.",
"type": "flogoFlow",
"settings": {
"reference": "github.com/TIBCOSoftware/mashling/lib/flow/RestTriggerToRestPutActivity.json"
}
},
{
"name": "InvalidAnimal",
"description": "Message for an invalid animal",
"type": "js",
"settings": {
"script": "result.msg = 'Unsupported animal: ' + parameters.content.category.name;"
}
}
]
}
}
```
The services section above illustrates 3 different types of service suported.
The first service which handles the GET request invokes https endpoint directly. The second service invokes a flogo flow to execute the pet store backend API to handle the PUT request. InvalidAnimal service executes a javascript service to produce a message that the request is invalid. This avoids invoking the backend API if the request is invalid.
Save the recipe file created and validate it with mashling-cli in a terminal:
```
mashling-cli -validate recipe_tutorial.json
```
Start the recipe with mashling-gateway:
```
mashling-gateway -c recipe_tutorial.json
```
In another terminal, register a pet with
```
curl -X PUT "http://localhost:9096/pets" -H "Content-Type: application/json" -d '{"category":{"id":1,"name":"DOG"},"id":16,"name":"Olive","photoUrls":["unavailable"],"status":"sold","tags":[{"id":76543,"name":"Olive"}]}'
```
Now, retrieve the pet data with
```
curl -X GET http://localhost:9096/pets/16
```
The pet data just registered should be returned.
Try registering a pet with unsupported type
```
curl -X PUT "http://localhost:9096/pets" -H "Content-Type: application/json" -d '{"category":{"id":3,"name":"BIRD"},"id":17,"name":"Birdie","photoUrls":["unavailable"],"status":"sold","tags":[{"id":87654,"name":"Birdie"}]}'
```
An error message is returned like the following:
```
{
"error": "Unsupported animal: BIRD"
}
```
| 32.085202 | 350 | 0.520056 | eng_Latn | 0.841877 |
ed30e0a1616e4432a055ad6542d1e4fd5fa0cffb | 1,756 | md | Markdown | README.md | StefanoSaffran/gobarber-web | 8a5dea82c4c8c6f41bb6f5c7badd522c7b86eefb | [
"MIT"
] | 1 | 2021-07-07T11:22:39.000Z | 2021-07-07T11:22:39.000Z | README.md | StefanoSaffran/gobarber-web | 8a5dea82c4c8c6f41bb6f5c7badd522c7b86eefb | [
"MIT"
] | 5 | 2021-03-10T00:36:58.000Z | 2022-02-26T20:45:56.000Z | README.md | StefanoSaffran/gobarber-web | 8a5dea82c4c8c6f41bb6f5c7badd522c7b86eefb | [
"MIT"
] | 1 | 2021-01-25T04:39:34.000Z | 2021-01-25T04:39:34.000Z | <h1 align="center">
<img src="https://res.cloudinary.com/stefanosaffran/image/upload/v1572880763/pmar6a1wwlckclgnwenb.png" />
<br>
GoBarber WEB
</h1>
<h4 align="center">
A barber scheduling app where users can choose from a list of barbers and barbers can track their appointments
</h4>
<p align="center">
[](https://app.netlify.com/sites/hungry-archimedes-7bb155/deploys)
<img alt="GitHub license" src="https://img.shields.io/github/license/StefanoSaffran/gobarber-web?color=7159c1">
<p>
## :rocket: Built with
This project was developed with the following technologies:
- [ReactJS](https://reactjs.org/)
- [Redux](https://redux.js.org/)
- [Redux-Saga](https://redux-saga.js.org/)
- [Redux-persist](https://github.com/rt2zz/redux-persist)
- [@rocketseat/unform](https://github.com/Rocketseat/unform)
- [Styled-components](https://www.styled-components.com/)
- [React-toastify](https://github.com/fkhadra/react-toastify)
- [Axios](https://github.com/axios/axios)
- [React-icons](https://react-icons.netlify.com/)
- [Reactotron](https://infinite.red/reactotron)
- [Immer](https://github.com/immerjs/immer)
- [Polished](https://polished.js.org/)
- [Yup](https://www.npmjs.com/package/yup)
- [Date-fns](https://date-fns.org/)
- [Prop-types](https://www.npmjs.com/package/prop-types)
- [React-perfect-scrollbar](https://github.com/goldenyz/react-perfect-scrollbar)
- [ESLint](https://eslint.org/)
- [Prettier](https://prettier.io/)
- [VS Code](https://code.visualstudio.com/)
## :mailbox_with_mail: Get in touch!
[LinkedIn](https://www.linkedin.com/in/stefanosaffran/) | [Website](https://stefanosaffran.com)
| 39.022222 | 175 | 0.71754 | yue_Hant | 0.431287 |
ed3233ecca178907e57c22e643bd831152ae66cd | 2,901 | md | Markdown | articles/analysis-services/analysis-services-vnet-gateway.md | ebarbosahsi/azure-docs.es-es | b6dbec832e5dccd7118e05208730a561103b357e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/analysis-services/analysis-services-vnet-gateway.md | ebarbosahsi/azure-docs.es-es | b6dbec832e5dccd7118e05208730a561103b357e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/analysis-services/analysis-services-vnet-gateway.md | ebarbosahsi/azure-docs.es-es | b6dbec832e5dccd7118e05208730a561103b357e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Configuración de Azure Analysis Services para orígenes de datos de red virtual | Microsoft Docs
description: Aprenda a configurar un servidor de Azure Analysis Services para que use una puerta de enlace para orígenes de datos en Azure Virtual Network (VNet).
author: minewiskan
ms.service: azure-analysis-services
ms.topic: conceptual
ms.date: 05/19/2020
ms.author: owend
ms.reviewer: minewiskan
ms.openlocfilehash: 912dab16cd854ae940b7bbdfe88a8da7adf1c5e0
ms.sourcegitcommit: f28ebb95ae9aaaff3f87d8388a09b41e0b3445b5
ms.translationtype: HT
ms.contentlocale: es-ES
ms.lasthandoff: 03/29/2021
ms.locfileid: "84197195"
---
# <a name="use-gateway-for-data-sources-on-an-azure-virtual-network-vnet"></a>Uso de la puerta de enlace para orígenes de datos en una red virtual de Azure (VNet)
En este artículo se describe la propiedad **AlwaysUseGateway** del servidor de Azure Analysis Services que se usa cuando los orígenes de datos se encuentran en una [red virtual de Azure (VNET)](../virtual-network/virtual-networks-overview.md).
## <a name="server-access-to-vnet-data-sources"></a>Acceso del servidor a los orígenes de datos de una red virtual
Si el acceso a sus orígenes de datos se realiza a través de una red virtual, el servidor de Azure Analysis Services debe conectarse, en su propio entorno, a esos orígenes de datos como si estuvieran en el entorno local. Puede configurar la propiedad de servidor **AlwaysUseGateway** para especificar el servidor y acceder a todos los datos de orígenes de datos mediante una [puerta de enlace local](analysis-services-gateway.md).
Los orígenes de datos de Instancia administrada de Azure SQL se ejecutan dentro de la red virtual de Azure con una dirección IP privada. Si el punto de conexión público está habilitado en la instancia, no se requiere una puerta de enlace. Si el punto de conexión público no está habilitado, se requiere una puerta de enlace de datos local y la propiedad AlwaysUseGateway debe establecerse en true.
> [!NOTE]
> Esta propiedad es efectiva únicamente cuando se instala y configura una [puerta de enlace de datos local](analysis-services-gateway.md). La puerta de enlace puede estar en la red virtual.
## <a name="configure-alwaysusegateway-property"></a>Configuración de la propiedad AlwaysUseGateway
1. En SSMS > servidor > **Propiedades** > **General**, seleccione **Show Advanced (All) Properties** (Mostrar propiedades avanzadas [todas]).
2. En **ASPaaS\AlwaysUseGateway**, seleccione **true**.
## <a name="see-also"></a>Consulte también
[Conexión a orígenes de datos locales](analysis-services-gateway.md)
[Instalación y configuración de una puerta de enlace de datos local](analysis-services-gateway-install.md)
[Azure Virtual Network (VNET)](../virtual-network/virtual-networks-overview.md)
| 67.465116 | 430 | 0.788004 | spa_Latn | 0.967421 |
ed32fff624a80fc151c4fda2da7688767c73669b | 497 | md | Markdown | README.md | soujava/cars-pagination-sample | b0224ae7f6139f170eaa246f69b503dd5f39ebf5 | [
"Apache-2.0"
] | 1 | 2019-08-04T22:29:07.000Z | 2019-08-04T22:29:07.000Z | README.md | soujava/cars-pagination-sample | b0224ae7f6139f170eaa246f69b503dd5f39ebf5 | [
"Apache-2.0"
] | null | null | null | README.md | soujava/cars-pagination-sample | b0224ae7f6139f170eaa246f69b503dd5f39ebf5 | [
"Apache-2.0"
] | null | null | null | # Cars Services
A JAX-RS with MongoDB pagination demo
A JAX-RS sample using [Payara Micro](https://www.payara.fish/software/payara-server/payara-micro/) implementation.
To run:
* `mvn -DskipTests clean package payara-micro:bundle`
* `java -jar target/cars-microbundle.jar`
### execute the script
`sh cars.sh`
#### Enjoy the queries
* http://localhost:8080/resource/cars
* http://localhost:8080/resource/cars?page=2
* http://localhost:8080/resource/cars?page=4&size=5
| 22.590909 | 115 | 0.710262 | kor_Hang | 0.460798 |
ed33538676cab0c449d643fb86b920d26ed0a0f5 | 890 | md | Markdown | docs/doc/03-reference/03-sql/01-ddl/04-stage/index.md | mrhamburg/databend | 9e4c5ae43de9a77d47cd39cc98ef0aa7a5e29337 | [
"Apache-2.0"
] | 1,556 | 2021-09-13T07:52:14.000Z | 2022-03-31T23:06:26.000Z | docs/doc/03-reference/03-sql/01-ddl/04-stage/index.md | mrhamburg/databend | 9e4c5ae43de9a77d47cd39cc98ef0aa7a5e29337 | [
"Apache-2.0"
] | 2,705 | 2021-09-13T07:28:33.000Z | 2022-03-31T23:15:53.000Z | docs/doc/03-reference/03-sql/01-ddl/04-stage/index.md | mrhamburg/databend | 9e4c5ae43de9a77d47cd39cc98ef0aa7a5e29337 | [
"Apache-2.0"
] | 204 | 2021-09-13T11:27:25.000Z | 2022-03-31T06:30:29.000Z | ---
title: What are Databend Stages
sidebar_position: 1
slug: ./
---
## What are Databend Stages?
Databend can both store data locally(Fuse engine) and access data stored in other storage systems, the location where data is saved or from is known as a **Stage**.
## What are the Types of Databend Stages?
Databend's data can be stored internally or externally, based on this, the Databend Stages are categorized into two types:
* Internal Stages
* External Stages
### Internal Stages
In Internal Databend Stages, the data is stored internally, the data location likes:
`/<bucket>/<tenant_id>/stage/<stage_name>/<stage_file>`
:::tip
Databend table data path:
`/<bucket>/<tenant_id>/<database_id>/<table_id>/`
:::
### External Stages
**External Stages** are storage in another external location that is not part of the Databend, this might be Amazon S3 Storage or MySQL/HDFS.
| 26.969697 | 164 | 0.744944 | eng_Latn | 0.995691 |
ed3374042299e0dd9b18066f39f8fbdbb466f65b | 577 | md | Markdown | join/join.cn.md | ShanghaiTechARLab/shanghaitecharlab.github.io | 3f243610d0379d8f50d217bf56afa3cf88e8e7e8 | [
"MIT"
] | null | null | null | join/join.cn.md | ShanghaiTechARLab/shanghaitecharlab.github.io | 3f243610d0379d8f50d217bf56afa3cf88e8e7e8 | [
"MIT"
] | 4 | 2020-02-25T13:42:17.000Z | 2022-02-26T04:19:54.000Z | join/join.cn.md | ShanghaiTechARLab/shanghaitecharlab.github.io | 3f243610d0379d8f50d217bf56afa3cf88e8e7e8 | [
"MIT"
] | null | null | null | ---
layout: page
title: Join AR Lab
permalink: /join/
subtitle: 招募人才
---
上海科技大学创业与管理学院杨丽凤博士研究组态度研究实验室（<a href="http://sem.shanghaitech.edu.cn/2018/0702/c3525a28655/page.htm">杨丽凤博士个人主页</a>）现诚聘全职研究助理1名，岗位汇报对象为研究组PI。杨丽凤博士主要研究人们对品牌，市场，企业，以及政府在信息推广中涉及的各种营销推广行为的态度，心理，及行为表现。杨博士当前侧重于研究各种品牌策略，说服(Persuasion)策略，广告措辞(Framing)效应，人喜好与厌恶并存(Ambivalence)的矛盾态度， 以及赞助营销行为(Cause-Related Marketing)效应。
<br>
<h3><b>一、主要职责</h3></b>
1. 从事PI分配的课题研究；搜索，整理，归纳各种课题相关数据。
2. 协助PI进行实验材料制作，制定，管理。协助PI进行实验室管理。
3. 协助PI撰写课题研究及案例分析报告。
4. 协助PI完成教学材料设计，开发，管理，批阅。
5. 完成研究组PI交办的其他工作。
<br>
<h3><b>二、招聘条件</h3></b>
| 32.055556 | 310 | 0.769497 | yue_Hant | 0.907234 |
ed338ff3c0c0136b5514e59a491c37b59d0c46eb | 867 | md | Markdown | api/Word.Paragraphs.SpaceAfter.md | ahkon/VBA-Docs | c047d7975de2b0949b496af150d279c505a8595b | [
"CC-BY-4.0",
"MIT"
] | 4 | 2019-09-07T04:44:48.000Z | 2021-12-16T15:05:50.000Z | api/Word.Paragraphs.SpaceAfter.md | ahkon/VBA-Docs | c047d7975de2b0949b496af150d279c505a8595b | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-06-13T09:32:15.000Z | 2021-06-13T09:32:15.000Z | api/Word.Paragraphs.SpaceAfter.md | ahkon/VBA-Docs | c047d7975de2b0949b496af150d279c505a8595b | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-06-23T03:40:08.000Z | 2021-06-23T03:40:08.000Z | ---
title: Paragraphs.SpaceAfter property (Word)
keywords: vbawd10.chm156762224
f1_keywords:
- vbawd10.chm156762224
ms.prod: word
api_name:
- Word.Paragraphs.SpaceAfter
ms.assetid: 78a75278-acca-a588-0fef-01511cf67a20
ms.date: 06/08/2017
localization_priority: Normal
---
# Paragraphs.SpaceAfter property (Word)
Returns or sets the amount of spacing (in points) after the specified paragraph or text column. Read/write **Single**.
## Syntax
_expression_. `SpaceAfter`
_expression_ Required. A variable that represents a '[Paragraphs](Word.paragraphs.md)' collection.
## Example
This example sets the spacing after all paragraphs in the active document to 12 points.
```vb
ActiveDocument.Paragraphs.SpaceAfter = 12
```
## See also
[Paragraphs Collection Object](Word.paragraphs.md)
[!include[Support and feedback](~/includes/feedback-boilerplate.md)] | 20.642857 | 119 | 0.77278 | eng_Latn | 0.855676 |
ed35b8358fa491a339ee0d38080e950918e39d79 | 3,170 | md | Markdown | wdk-ddi-src/content/namcache/nf-namcache-rxnamecachefinalize.md | jazzdelightsme/windows-driver-docs-ddi | 793b0c96e117b1658144ba8b3939fdc31a49f6b6 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | wdk-ddi-src/content/namcache/nf-namcache-rxnamecachefinalize.md | jazzdelightsme/windows-driver-docs-ddi | 793b0c96e117b1658144ba8b3939fdc31a49f6b6 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | wdk-ddi-src/content/namcache/nf-namcache-rxnamecachefinalize.md | jazzdelightsme/windows-driver-docs-ddi | 793b0c96e117b1658144ba8b3939fdc31a49f6b6 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
UID: NF:namcache.RxNameCacheFinalize
title: RxNameCacheFinalize function (namcache.h)
description: RxNameCacheFinalize releases the storage for all of the NAME_CACHE entries associated with a NAME_CACHE_CONTROL structure.
old-location: ifsk\rxnamecachefinalize.htm
tech.root: ifsk
ms.assetid: e40ac123-86a9-4a69-bb13-a118f2fd42f1
ms.date: 04/16/2018
ms.keywords: RxNameCacheFinalize, RxNameCacheFinalize function [Installable File System Drivers], ifsk.rxnamecachefinalize, namcache/RxNameCacheFinalize, rxref_34ec3c3b-20b2-425a-8d12-4a2d685ffb2f.xml
ms.topic: function
req.header: namcache.h
req.include-header: Namcache.h
req.target-type: Desktop
req.target-min-winverclnt:
req.target-min-winversvr:
req.kmdf-ver:
req.umdf-ver:
req.ddi-compliance:
req.unicode-ansi:
req.idl:
req.max-support:
req.namespace:
req.assembly:
req.type-library:
req.lib:
req.dll:
req.irql: "<= APC_LEVEL"
topic_type:
- APIRef
- kbSyntax
api_type:
- HeaderDef
api_location:
- namcache.h
api_name:
- RxNameCacheFinalize
product:
- Windows
targetos: Windows
req.typenames:
---
# RxNameCacheFinalize function
## -description
<b>RxNameCacheFinalize</b> releases the storage for all of the NAME_CACHE entries associated with a NAME_CACHE_CONTROL structure.
## -parameters
### -param NameCacheCtl [in]
A pointer to the NAME_CACHE_CONTROL structure for the name cache.
## -returns
None
## -remarks
The <b>RxNameCacheFinalize </b>routine acquires the lock on the name cache to scan the free list and remove entries from the active list.
On checked builds, this routine causes the system to ASSERT if after releasing all of the active and free entries a reference count still remains on the name cache. This indicates a memory leak where some caller did not call <a href="https://docs.microsoft.com/windows-hardware/drivers/ddi/content/namcache/nf-namcache-rxnamecachefreeentry">RxNameCacheFreeEntry</a> when done with an entry.
## -see-also
<a href="https://docs.microsoft.com/windows-hardware/drivers/ddi/content/namcache/nf-namcache-rxnamecacheactivateentry">RxNameCacheActivateEntry</a>
<a href="https://docs.microsoft.com/windows-hardware/drivers/ddi/content/namcache/nf-namcache-rxnamecachecheckentry">RxNameCacheCheckEntry</a>
<a href="https://docs.microsoft.com/windows-hardware/drivers/ddi/content/namcache/nf-namcache-rxnamecachecreateentry">RxNameCacheCreateEntry</a>
<a href="https://docs.microsoft.com/windows-hardware/drivers/ddi/content/namcache/nf-namcache-rxnamecacheexpireentry">RxNameCacheExpireEntry</a>
<a href="https://docs.microsoft.com/windows-hardware/drivers/ddi/content/namcache/nf-namcache-rxnamecacheexpireentrywithshortname">RxNameCacheExpireEntryWithShortName</a>
<a href="https://docs.microsoft.com/windows-hardware/drivers/ddi/content/namcache/nf-namcache-rxnamecachefetchentry">RxNameCacheFetchEntry</a>
<a href="https://docs.microsoft.com/windows-hardware/drivers/ddi/content/namcache/nf-namcache-rxnamecachefreeentry">RxNameCacheFreeEntry</a>
<a href="https://docs.microsoft.com/windows-hardware/drivers/ddi/content/namcache/nf-namcache-rxnamecacheinitialize">RxNameCacheInitialize</a>
| 26.416667 | 390 | 0.797476 | yue_Hant | 0.69581 |
ed361e158a7594e8d88a311b905f3c50bbe989ca | 71 | md | Markdown | _posts/2000-01-01-intro.md | kristofkalocsai/kristofkalocsai.github.io | 7a7325935a92b01f6025f31cd20f4c4e8618ec33 | [
"MIT",
"BSD-3-Clause"
] | null | null | null | _posts/2000-01-01-intro.md | kristofkalocsai/kristofkalocsai.github.io | 7a7325935a92b01f6025f31cd20f4c4e8618ec33 | [
"MIT",
"BSD-3-Clause"
] | null | null | null | _posts/2000-01-01-intro.md | kristofkalocsai/kristofkalocsai.github.io | 7a7325935a92b01f6025f31cd20f4c4e8618ec33 | [
"MIT",
"BSD-3-Clause"
] | null | null | null | ---
title: "home"
bg: green
color: white
style: center
---
# Projects
| 7.888889 | 13 | 0.633803 | eng_Latn | 0.987122 |
ed36a60681e6dc7b44b78bf16641007f2783e5f1 | 276 | md | Markdown | docs/README.md | projek-xyz/template | 7888f3ad7e2668f741808761208c6bd36ef8a397 | [
"MIT"
] | null | null | null | docs/README.md | projek-xyz/template | 7888f3ad7e2668f741808761208c6bd36ef8a397 | [
"MIT"
] | 2 | 2020-06-25T01:03:03.000Z | 2020-06-25T01:03:07.000Z | docs/README.md | projek-xyz/template | 7888f3ad7e2668f741808761208c6bd36ef8a397 | [
"MIT"
] | null | null | null | # Project Headline [](https://packagist.org/packages/projek-xyz/template)
Some descriptive project description.
## Requirements
- List of the requirements.
## Installation
How to install
| 23 | 157 | 0.771739 | eng_Latn | 0.441807 |
ed38d51c42e6ee8ceb971ae67b767196b4770fdb | 509 | md | Markdown | README.md | mingzhu0527/MASHQA | b7d1e775e9fd96d78fb512ab02357aa2f8177d9b | [
"Apache-2.0"
] | 12 | 2020-11-27T02:20:23.000Z | 2022-01-18T07:04:21.000Z | README.md | mingzhu0527/MASHQA | b7d1e775e9fd96d78fb512ab02357aa2f8177d9b | [
"Apache-2.0"
] | 7 | 2021-03-07T07:36:04.000Z | 2022-01-22T16:27:26.000Z | README.md | mingzhu0527/MASHQA | b7d1e775e9fd96d78fb512ab02357aa2f8177d9b | [
"Apache-2.0"
] | 3 | 2021-06-28T14:26:59.000Z | 2022-01-17T18:38:45.000Z | # MASHQA
This is the repo for EMNLP Findings paper "[Question Answering with Long Multiple-Span Answers](https://people.cs.vt.edu/mingzhu/papers/conf/emnlp2020.pdf)"<br />
The dataset can be found [here](https://drive.google.com/file/d/1YJ5Pw7CoBcwKv2YYCguqLF2HQDcPMd8G/view?usp=sharing)<br />
(If you have problem accessing the data, please email the author: mingzhu[at]vt.edu) <br />
To preprocess the data:<br />
sh scripts/prepro_sentqa.sh<br />
To train the model:<br />
sh scripts/sentqa_GPU.sh<br />
| 46.272727 | 162 | 0.756385 | eng_Latn | 0.754524 |
ed39667f0f30f1d0cf5b02fe1d01dc33d9a245cd | 3,228 | md | Markdown | _posts/2016-05-24-empezando-temporada-triatlon.md | psanxiao/psanxiao.github.com | 638fbfc1ea5c7270e6a80619911cd442091310b4 | [
"MIT"
] | null | null | null | _posts/2016-05-24-empezando-temporada-triatlon.md | psanxiao/psanxiao.github.com | 638fbfc1ea5c7270e6a80619911cd442091310b4 | [
"MIT"
] | null | null | null | _posts/2016-05-24-empezando-temporada-triatlon.md | psanxiao/psanxiao.github.com | 638fbfc1ea5c7270e6a80619911cd442091310b4 | [
"MIT"
] | null | null | null | ---
layout: post
title: "Empezando la temporada de triatlones"
description: ""
category:
- Triathlon
tags: [triatlón, debutar, experiencias]
---
{% include JB/setup %}
Pues como dice el título, estamos empezando ya la temporada de triatlones, la primera en mi caso así que todo son debuts y cosas nuevas. De momento ya van dos, en distancia sprint (750m-20km-5km), y uno fallido en distancia olímpica (1500m-40km-10km) que como ya [salió en la prensa](http://www.lavozdegalicia.es/noticia/pontevedra/sanxenxo/2016/05/16/concello-vilagarcia-organizacion-enzarzan-fiasco-triatlon-rias-baixas/0003_201605P16C3991.htm) no le voy a dar mucho más bombo. Hay pruebas mejor organizadas y peores, y en las mejores siempre hay detalles que salen mal o que se pueden mejorar, pero que una prueba no se pueda llegar a celebrar por culpa de la mala organización... en fin, sin comentarios.
Mi debut fue en el triatlón de Oleiros, un clásico en el calendario y que este año abría la temporada. Muy pendiente de todo lo que hay que hacer, algo lento en las transiciones y con muchas dudas en el agua pero objetivo cumplido que era acabar el primer triatlón e ir cogiendo experiencia.
En la natación algo mejor de lo esperado pero igualmente saliendo del agua muy atrás, en la bici pude recuperar bastante terreno, era un circuito con algo de dureza y eso me viene bien, aunque 20 kms son pocos para recuperar. Los últimos 5 corriendo también con buenas sensaciones, para ser el primero no estuvo mal.
En el segundo de la temporada tocaba jugar en casa, después del fiasco de Villagarcía y sólo dos días después apetecía mucho. Triatlón de riazor, en casa y con muchos conocidos animando y [NoSportLimit](http://nosportlimit.com) volcado, ya que eramos el club más numeroso. Animarse unos a otros, sentir el apoyo de los compañeros y cruzarte siempre con algún nosporlimit no tiene precio.
 
En lo que se refiere a la competición, un poco parecido a Oleiros, retrasado en el agua, pero esta vez sin poder recuperar tanto en la bici. Circuito super rápido, muy llano y que tuve que hacer prácticamente sólo. Corriendo de nuevo buenas sensaciones y terminando con fuerza.
#### Lecciones aprendidas
Salir tan retrasado del agua me pasa factura, aunque en bici y corriendo voy bien, salgo ya con un handicap importante y en triatlones cortos se nota. Creo que distancias más largas como la olímpica o la larga distancia me irá mejor, cuanto más tiempo sobre la bici para mí mejor.
Pero la mejor lección de todo esto es que voy muy mal en el agua y lo sabía. Nunca fui especialmente rápido nadando y lo cierto es que esta temporada fue lo que menos entrené. Error. Aunque la natación en un triatlón parece un mero trámite porque es lo primero, lo cierto es que salir muy atrás perjudica y mucho, no sólo por empezar ya retrasado sino porque te impide coger un buen grupo en la bici para ir más cómodo por ejemplo. Así que toca entrenar y duro la natación para mejorar.
Próxima estación Baiona, distancia olímpica y sin drafting, al menos no tendré que sufrir por no pillar grupo en la bici ya que estaremos cada uno por nuestra cuenta.
| 111.310345 | 708 | 0.792441 | spa_Latn | 0.999096 |
ed396700e0e48362140549e31200482dadcfeb9d | 3,930 | md | Markdown | translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account.md | Hardik-Ghori/docs | a1910a7f8cedd4485962ad0f0c3c93d7348709a5 | [
"CC-BY-4.0",
"MIT"
] | 20 | 2021-02-17T16:18:11.000Z | 2022-03-16T08:30:36.000Z | translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account.md | 0954011723/docs | d51685810027d8071e54237bbfd1a9fb7971941d | [
"CC-BY-4.0",
"MIT"
] | 40 | 2020-10-21T12:54:07.000Z | 2021-07-23T06:10:46.000Z | translations/de-DE/content/github/setting-up-and-managing-your-github-user-account/deleting-your-user-account.md | 0954011723/docs | d51685810027d8071e54237bbfd1a9fb7971941d | [
"CC-BY-4.0",
"MIT"
] | 3 | 2021-03-31T18:21:34.000Z | 2021-04-10T21:07:53.000Z | ---
title: Dein Benutzerkonto löschen
intro: 'Du kannst Dein {% data variables.product.product_name %}-Benutzerkonto jederzeit löschen.'
redirect_from:
- /articles/deleting-a-user-account/
- /articles/deleting-your-user-account
versions:
free-pro-team: '*'
enterprise-server: '*'
---
Wenn Du Dein Benutzerkonto löschst, werden alle dazugehörigen Repositorys, Forks von privaten Repositorys, Wikis, Issues, Pull Requests und Seiten Deines Kontos ebenfalls gelöscht. {% if currentVersion == "free-pro-team@latest" %} Deine Issues, Pull Requests und Kommentare in Repositorys von anderen Benutzern werden nicht gelöscht, sondern mit unserem [Ghost user](https://github.com/ghost) (Geisterbenutzer) verknüpft.{% else %}Deine Issues, Pull Requests und Kommentare in Repositorys von anderen Benutzern werden nicht gelöscht.{% endif %}
{% if currentVersion == "free-pro-team@latest" %} Außerdem steht der Name Deines Kontos wieder für andere Benutzer zur Verfügung, und Deine Abrechnung wird beendet. Die mit dem Konto verknüpfte E-Mail-Adresse wird für die Nutzung mit einem anderen {% data variables.product.product_name %}-Konto frei. {% endif %}
Wenn Du der alleinige Inhaber einer Organisation bist, musst Du die Inhaberschaft auf eine andere Person übertragen oder die Organisation löschen, bevor Du Dein Benutzerkonto löschen kannst. Wenn es noch weitere Inhaber Deiner Organisation gibt, musst Du Dich selbst aus der Organisation löschen, bevor Du Dein Benutzerkonto löschen kannst.
Weitere Informationen findest Du unter:
- „[Inhaberschaft an einer Organisation übertragen](/articles/transferring-organization-ownership)“
- „[Ein Organisationskonto löschen](/articles/deleting-an-organization-account)“
- „[Dich selbst aus einer Organisation entfernen](/articles/removing-yourself-from-an-organization/)“
### Deine Kontoinformationen sichern
Bevor Du Dein Benutzerkonto löschst, erstelle Kopien aller Repositorys, privaten Forks, Wikis, Issues und Pull Requests Deines Kontos.
{% warning %}
**Warnung:** Sobald Dein Benutzerkonto gelöscht wurde, kann GitHub Deine Inhalte nicht wiederherstellen.
{% endwarning %}
### Dein Benutzerkonto löschen
{% data reusables.user_settings.access_settings %}
{% data reusables.user_settings.account_settings %}
3. Klicke unten auf der Seite mit den Kontoeinstellungen unter „Delete account“ (Konto löschen) auf **Delete your account** (Dein Konto löschen). Vor dem Löschen Deines Benutzerkontos musst Du Folgendes tun:
- Wenn Du der alleinige Inhaber einer Organisation bist, musst Du die Inhaberschaft auf eine andere Person übertragen oder die Organisation löschen.
- Wenn es andere Inhaber der Organisation gibt, musst Du Dich selbst aus der Organisation entfernen. 
4. Fülle das Dialogfeld „Are you sure you want to do this?“ (Möchtest Du das wirklich tun?) aus, um zu bestätigen, dass Du die Folgen der Kontolöschung verstanden hast: 
{% if currentVersion == "free-pro-team@latest" %}– Denke daran, dass alle Repositorys, Forks von privaten Repositorys, Wikis, Issues, Pull Requests und Seiten von Deinem Konto ebenfalls gelöscht werden, dass Deine Abrechnung beendet wird und Dein Benutzername wieder für die Verwendung auf {% data variables.product.product_name %} freigegeben wird.
{% else %}– Denke daran, dass alle Repositorys, Forks von privaten Repositorys, Wikis, Issues, Pull Requests und Seiten von Deinem Konto ebenfalls gelöscht werden und Dein Benutzername wieder für die Verwendung auf {% data variables.product.product_name %} freigegeben wird.
{% endif %}– Gib im ersten Feld Deinen {% data variables.product.product_name %}-Benutzernamen oder Deine E-Mail-Adresse ein.
- Gib im zweiten Feld den Text von der Aufforderung ein.
| 87.333333 | 544 | 0.790585 | deu_Latn | 0.975965 |
ed396c4d94e91c1c3cc2585b46f92fe1bcfa8b2a | 7,136 | md | Markdown | articles/active-directory/managed-identities-azure-resources/tutorial-linux-vm-access-arm.md | marcobrunodev/azure-docs.pt-br | 0fff07f85663724745ac15ce05b4570890d108d9 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/active-directory/managed-identities-azure-resources/tutorial-linux-vm-access-arm.md | marcobrunodev/azure-docs.pt-br | 0fff07f85663724745ac15ce05b4570890d108d9 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/active-directory/managed-identities-azure-resources/tutorial-linux-vm-access-arm.md | marcobrunodev/azure-docs.pt-br | 0fff07f85663724745ac15ce05b4570890d108d9 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: 'Início rápido`:`: usar uma identidade gerenciada para acessar o Azure Resource Manager – Azure AD'
description: Um início rápido que o conduz pelo processo de usar uma identidade gerenciada atribuída pelo sistema da VM do Linux para acessar o Azure Resource Manager.
services: active-directory
documentationcenter: ''
author: barclayn
manager: daveba
editor: bryanla
ms.service: active-directory
ms.subservice: msi
ms.devlang: na
ms.topic: quickstart
ms.tgt_pltfrm: na
ms.workload: identity
ms.date: 11/03/2020
ms.author: barclayn
ms.collection: M365-identity-device-management
ms.openlocfilehash: 653159c2e40d3375a422f0da14274f57130de1fe
ms.sourcegitcommit: 6a902230296a78da21fbc68c365698709c579093
ms.translationtype: HT
ms.contentlocale: pt-BR
ms.lasthandoff: 11/05/2020
ms.locfileid: "93359673"
---
# <a name="use-a-linux-vm-system-assigned-managed-identity-to-access-azure-resource-manager"></a>Usar uma identidade gerenciada atribuída pelo sistema da VM do Linux para acessar o Azure Resource Manager
[!INCLUDE [preview-notice](../../../includes/active-directory-msi-preview-notice.md)]
Este tutorial mostra como usar uma identidade atribuída pelo sistema para uma VM (máquina virtual) do Linux para acessar a API do Azure Resource Manager. As identidades gerenciadas para recursos do Azure são gerenciadas automaticamente pelo Azure e permitem a você autenticar os serviços que dão suporte à autenticação do Azure AD sem necessidade de inserir as credenciais em seu código. Você aprenderá como:
> [!div class="checklist"]
> * Conceder o acesso da VM a um Grupo de Recursos no Azure Resource Manager
> * Obter um token de acesso usando a identidade da máquina virtual e usá-la para chamar o Azure Resource Manager
## <a name="prerequisites"></a>Pré-requisitos
- Conhecimento sobre Identidades Gerenciadas. Se você não estiver familiarizado com as identidades gerenciadas para funcionalidades de recursos do Azure, veja esta [visão geral](overview.md).
- Uma conta do Azure, [inscreva-se para obter uma conta gratuita](https://azure.microsoft.com/free/).
- Você também precisa de uma Máquina Virtual do Linux com as identidades gerenciadas atribuídas ao sistema habilitadas.
- Se você precisar criar uma máquina virtual para este tutorial, siga o artigo intitulado [Criar uma máquina virtual do Linux com o portal do Azure](../../virtual-machines/linux/quick-create-portal.md#create-virtual-machine)
## <a name="grant-access"></a>Conceder acesso
Usando a identidades gerenciadas para recursos do Azure, seu código pode obter tokens de acesso para autenticar para recursos que oferecem suporte à autenticação do Azure AD. A API do Azure Resource Manager oferece suporte à autenticação do Azure AD. Primeiro, é preciso conceder acesso de identidade desta VM a um recurso no Azure Resource Manager, neste caso, o Grupo de Recursos no qual a VM está contida.
1. Navegue até a guia para **Grupos de Recursos**.
2. Selecione o **Grupo de Recursos** específico usado para máquina virtual.
3. Vá para **Controle de acesso (IAM)** no painel esquerdo.
4. Clique para **Adicionar** uma nova atribuição de função para sua VM. Escolha **Função** como **Leitor**.
5. No menu suspenso seguinte, **Atribuir acesso a** ao recurso **Máquina Virtual**.
6. Em seguida, certifique-se de que a assinatura correta está listada na lista suspensa **Assinatura**. E para **Grupo de Recursos**, selecione **Todos os grupos de recursos**.
7. Por fim, em **Selecionar** escolha sua Máquina Virtual do Linux na lista suspensa e clique em **Salvar**.
## <a name="get-an-access-token-using-the-vms-system-assigned-managed-identity-and-use-it-to-call-resource-manager"></a>Obter um token de acesso usando a identidade gerenciada atribuída pelo sistema da VM e usá-lo para chamar o Resource Manager
Para concluir essas etapas, você precisará de cliente SSH. Se você estiver usando o Windows, poderá usar o cliente SSH no [Subsistema do Windows para Linux](/windows/wsl/about). Se precisar de ajuda para configurar as chaves do cliente SSH, confira [Como usar chaves SSH com o Windows no Azure](../../virtual-machines/linux/ssh-from-windows.md), ou [Como criar e usar um par de chaves SSH pública e privada para VMs Linux no Azure](../../virtual-machines/linux/mac-create-ssh-keys.md).
1. No portal, navegue até a VM do Linux e em **Visão geral**, clique em **Conectar**.
2. **Conecte-se** à VM com um cliente SSH de sua escolha.
3. Na janela do terminal, usando o `curl`, faça uma solicitação às identidades gerenciadas locais do ponto de extremidade de recursos do Azure para obter um token de acesso para o Azure Resource Manager.
A solicitação do `curl` para o token de acesso é mostrada abaixo.
```bash
curl 'http://169.254.169.254/metadata/identity/oauth2/token?api-version=2018-02-01&resource=https://management.azure.com/' -H Metadata:true
```
> [!NOTE]
> O valor do parâmetro "resource" deve ser uma correspondência exata para o que é esperado pelo Azure AD. No caso da ID de recurso do Gerenciador de Recursos, você deve incluir a barra à direita no URI.
A resposta inclui o token de acesso que você precisa para acessar o Azure Resource Manager.
Resposta:
```bash
{"access_token":"eyJ0eXAiOi...",
"refresh_token":"",
"expires_in":"3599",
"expires_on":"1504130527",
"not_before":"1504126627",
"resource":"https://management.azure.com",
"token_type":"Bearer"}
```
Você pode usar esse token de acesso para acessar o Azure Resource Manager, por exemplo, para ler os detalhes do Grupo de Recursos ao qual você concedeu acesso anteriormente para essa VM. Substitua os valores de \<SUBSCRIPTION ID\>, \<RESOURCE GROUP\> e \<ACCESS TOKEN\> por aqueles que você criou anteriormente.
> [!NOTE]
> A URL diferencia maiúsculas de minúsculas, portanto, verifique se você está usando letras maiúsculas e minúsculas exatamente da mesma forma que você usou anteriormente ao nomear o Grupo de Recursos e a letra maiúscula “G” em “resourceGroup”.
```bash
curl https://management.azure.com/subscriptions/<SUBSCRIPTION ID>/resourceGroups/<RESOURCE GROUP>?api-version=2016-09-01 -H "Authorization: Bearer <ACCESS TOKEN>"
```
A resposta de volta com as informações do Grupo de Recursos específicas:
```bash
{"id":"/subscriptions/98f51385-2edc-4b79-bed9-7718de4cb861/resourceGroups/DevTest","name":"DevTest","location":"westus","properties":{"provisioningState":"Succeeded"}}
```
## <a name="next-steps"></a>Próximas etapas
Neste início rápido, você aprendeu a usar uma identidade gerenciada atribuída pelo sistema para acessar a API do Azure Resource Manager. Para saber mais sobre o Azure Resource Manager, confira:
> [!div class="nextstepaction"]
>[Azure Resource Manager](../../azure-resource-manager/management/overview.md)
>[Criar, listar ou excluir uma identidade gerenciada atribuída ao usuário usando o Azure PowerShell](how-to-manage-ua-identity-powershell.md) | 66.074074 | 485 | 0.757427 | por_Latn | 0.995371 |
ed399143cafdd2a9516b967fc73d855a7bf21549 | 561 | md | Markdown | bot/resources/tags/precedence.md | hugovk/bot | 46d3f877b569a8a6db8a50fbd80ff49c90ba04cf | [
"MIT",
"BSD-3-Clause"
] | 1,003 | 2018-11-17T21:10:01.000Z | 2022-03-31T22:50:39.000Z | bot/resources/tags/precedence.md | hugovk/bot | 46d3f877b569a8a6db8a50fbd80ff49c90ba04cf | [
"MIT",
"BSD-3-Clause"
] | 1,474 | 2018-11-17T10:18:14.000Z | 2022-03-31T18:01:39.000Z | bot/resources/tags/precedence.md | hugovk/bot | 46d3f877b569a8a6db8a50fbd80ff49c90ba04cf | [
"MIT",
"BSD-3-Clause"
] | 771 | 2018-11-21T08:36:07.000Z | 2022-03-31T14:56:39.000Z | **Operator Precedence**
Operator precedence is essentially like an order of operations for python's operators.
**Example 1** (arithmetic)
`2 * 3 + 1` is `7` because multiplication is first
`2 * (3 + 1)` is `8` because the parenthesis change the precedence allowing the sum to be first
**Example 2** (logic)
`not True or True` is `True` because the `not` is first
`not (True or True)` is `False` because the `or` is first
The full table of precedence from lowest to highest is [here](https://docs.python.org/3/reference/expressions.html#operator-precedence)
| 40.071429 | 135 | 0.736185 | eng_Latn | 0.999069 |
ed39e32fa9c22c9ec35e38a36996207d7a1f2410 | 21,550 | md | Markdown | MenaionLambertsenApril/chapters/0429363.md | typiconman/english-md | 1d19b0b27ce8e36ed4d0ec9f2b836bab52cdfd33 | [
"MIT"
] | 2 | 2020-11-23T12:26:50.000Z | 2021-04-09T22:26:42.000Z | MenaionLambertsenApril/chapters/0429363.md | typiconman/english-md | 1d19b0b27ce8e36ed4d0ec9f2b836bab52cdfd33 | [
"MIT"
] | null | null | null | MenaionLambertsenApril/chapters/0429363.md | typiconman/english-md | 1d19b0b27ce8e36ed4d0ec9f2b836bab52cdfd33 | [
"MIT"
] | null | null | null | The 29th Day of the MONTH OF APRIL
Commemoration of the 9 Holy Martyrs of Cyzicus
Commemoration of the Venerable
Memnon the Wonder-worker
AT VESPERS
On “Lord, I have cried…”, 6 stichera: 3 of the martyrs, in Tone VIII: Spec. Mel.: “O all-glorious wonder…”—
O all-praised martyrs of Christ, when once the mindlessness of the Greeks held sway and drew all into the pit of iniquity, ye did not leave the straight path and did not join yourselves to ungodliness, but suffered with valor of character and, slain by the sword, have inherited life.
Celebrating with gladness their sacred memory, with faith let us honor and with hymns let us bless Theognes, Rufus and Antipater, Theostichus and Artemas, Magnus and Theodotus, the glorious Thaumasius and the godly Philemon, who shone forth splendidly in their sufferings and have enlightened those in darkness.
O beautiful flowers of the martyrs, ye sacred legion, company assembled by God, excellent congregation, divinely chosen assembly, holy choir, blessed council, who struggled for the Trinity: entreat the Trinity, beseech the Trinity for us, that we may receive remission of sins.
And 3 stichera of the venerable one, in the same tone & melody—
O blessed and venerable Memnon, having first purified thy soul by ascetic labor, thou becamest the pure and beautiful abode of the Spirit; wherefore, thou dost expel evil spirits and ever healest the infirmities of those who have recourse to thee. Pray thou to Christ in behalf of us who praise thee.
O glorious and venerable Memnon, having gained control over the passions of thy soul, thou didst train a legion of monks, zealously anointing them for labors of asceticism, and thou didst present them before the Word Who seeth all things; and having lived a blessed life and been unsullied by defilements, with them be thou ever mindful of us who praise thee.
O venerable Memnon who art most rich, of old thou didst cause a spring of water to pour forth, unto the praise of the Lord and for the preservation of souls. Thou hast saved ships from the depths of the sea, by thy supplications hast preserved men from a plague of locusts, and dost ever work countless miracles. Pray thou to Christ in behalf of us who praise thee.
Glory…, Now & ever…: Doxasticon from the Pentecostarion, or this Theotokion, in the same tone & melody—
The preëternal God, receiving flesh from thy blood, showed thee to be an intercessor for men, O pure one. Wherefore, deliver thy servants from every misfortune and evil circumstance and from the snares of the wicked enemy, and vouchsafe that all who glorify and do thee homage may partake of the effulgence of the elect.
Stavrotheotokion—
Beholding Thee nailed to the Cross and accepting suffering of Thine own will, O Master Jesus, Thy Virgin Mother cried aloud: “Woe is me, O my sweet Child! How is it that thou dost unjustly endure wounds, O Physician Who hast healed the infirmity of men and hast delivered all from corruption in Thy loving-kindness?”
AT MATINS
Ode I
Canon of the martyrs, in Tone IV—
*Irmos:* O Thou Who wast born of the Virgin, drown Thou, I pray Thee, the three parts of my soul in the depths of dispassion, as of old Thou didst drown the mounted captains of Pharaoh; that, in the mortality of my body, as on a timbrel, I may chant a hymn of victory.
Delighting together in divine beauty, partaking abundantly of a torrent of sustenance, and deified by communion, O crown-bearing martyrs, from cruel misfortunes deliver those who call you blessed.
Having shone forth like rays of the sun, O athletes, with the beams of your steadfast struggles ye enlighten all with the effulgence of miracles, dispel the night of the passions and drive away the gloom of the demons.
Having been slain on earth with painful wounds, ye have passed over together to the life devoid of pain, O youths who suffered greatly; wherefore, ye pour forth healings, easing all pain by your God-pleasing supplications, O ye who are all-rich.
*Theotokion:* Through thy precious blood thou gavest birth to God, Who became incarnate in manner past understanding and assumed an appearance like unto ours, O all-immaculate Mother. Wherefore, all of us, the generations of generations, call thee blessed, thou confirmation of the holy martyrs.
Canon of the venerable one, in the same tone—
*Irmos:* Having traversed the depths of the Red Sea with dryshod feet, Israel of old vanquished the might of Amalek in the wilderness by Moses’ arms stretched out in the form of the Cross.
Shining with the divine grace of the all-holy Spirit, O life-bearing Memnon, by thy radiant supplication purge the gloom of the passions from those who celebrate thine honored repose.
O venerable one, taking up thy cross, thou didst follow after the Word Who was crucified for our sake, and by abstinence and lying on the ground thou didst mortify the movements of the flesh, O venerable one.
Uniting thyself to God by fasting, prayers and tears, thou didst receive from Him the grace to heal infirmities and to expel evil spirits, O all-blessed and divinely wise Memnon.
*Theotokion:* Clothing Himself in man in His goodness, O pure and all-holy one, God issued forth from thee twofold in activity and nature. Him do thou ever beseech, that He enlighten those who hymn thee.
Ode III
Canon of the Martyrs
*Irmos:* Neither in wisdom, nor in power, nor yet in riches do we boast, but in Thee, O Christ, the hypostatic Wisdom of the Father; for none is holy save Thee, O Thou Who lovest mankind.
In nowise consenting to sacrifice to lifeless graven images, ye offered yourselves as living sacrifices to Him Who was sacrificed for our sake, O all-comely youths, O holy martyrs.
Strengthened by the power of the Spirit, with the divine laws ye cast down the counsels and pursuits of the iniquitous; and having suffered lawfully, ye have received glory.
Let those of great renown be praised: Artemas and Philemon, Theostichus and Magnus, the glorious Rufus, Antipater and Thaumasius, Theognes and Theodotus.
*Theotokion:* All the weaponry of the enemy hath now been made of no account, O most immaculate one who gavest birth to Christ Who was wounded by the spear, for Whom the martyrs, being wounded, did suffer.
Canon of the Venerable One
*Irmos:* Thy Church rejoiceth in Thee, O Christ, crying aloud: Thou art my strength, O Lord, my refuge and my consolation!
With the enlightenment of the virtues didst thou shine forth on the earth like the sun, O venerable one, illumining the souls of all with the grace of the Spirit.
Thy loins girded, clothed in dispassions, O venerable Memnon, thou didst manifestly wield thy staff for the mortification of the passions.
Having been compassionate to the poor, O venerable one, thou didst receive from God the great grace to heal incurable suffering.
*Theotokion:* The Word of God made His abode within thine undefiled womb, O all-pure one, and hath taken all sin away from mortals.
Sessional hymn of the martyrs, in Tone I: Spec. Mel.: “Thy tomb, O Savior…”—
The radiant choir of sacred athletes, the beautiful company, the divinely assembled council, the band ten in number, having suffered mightily and trampled the tyranny of the enemy underfoot, have been numbered with the choirs of the angels and stand before the Lord.
Glory…: Sessional hymn of the venerable one, in Tone VIII: Spec. Mel.: “Of the Wisdom…”—
We all praise thee, O blessed one, as a radiant star illumining the world with virtues and rays of miracles; for thou wast a partaker of divine radiance, O Memnon, and hast passed over to the never-waning effulgence. Wherefore, we ever honor thy luminous and holy memory, glorifying the Savior, and we cry out to thee with faith: Entreat Christ God, that He grant remission of sins unto those who honor thy holy memory with love.
Now & ever…: Theotokion—
Having fallen into the most subtle temptations of enemies, visible and invisible, stuck fast in the tempest of my countless offenses I flee to the haven of thy goodness, O pure one, as to my fervent assistance and protection. Wherefore, O all-pure one, do thou earnestly entreat Him Who became incarnate of thee without seed, in behalf of all thy servants who unceasingly pray to thee, O all-pure Theotokos, ever beseeching Him to grant remission of our offenses unto us who hymn thy glory as is meet.
Stavrotheotokion—
The ewe-lamb, beholding the Lamb, Shepherd and Deliverer upon the Cross, exclaimed, weeping, and bitterly lamenting, cried out: “The world rejoiceth, receiving deliverance through Thee, but my womb doth burn, beholding Thy crucifixion, which Thou endurest in the loving-kindness of Thy mercy. O long-suffering Lord, Thou abyss and inexhaustible well-spring of mercy, take pity and grant remission of transgressions unto those who hymn Thy divine sufferings with faith!”
Ode IV
Canon of the Martyrs
*Irmos:* Seated in glory upon the throne of the Godhead, Jesus most divine hath come on a light cloud, and with His incorrupt arm hath saved those who cry: Glory to Thy power, O Christ!
Unto Him Who of His own will was sacrificed and hath slain death did ye offer yourselves as wholeburnt offerings, divinely slain victims, a perfect holocaust and acceptable sacrifices, O athletes. Wherefore, we call you blessed.
Showing forth a great miracle, O athletes, ye straightened bent arms and delivered from dropsy a prominent man who had recourse with love to your shrine, O right wondrous ones.
As is meet let those who suffered be blessed: Artemas and Antipater, Theostichus and Rufus, Magnus, Philemon and Theognes, with the glorious Theodotus, for they cry: Glory to Thy power, O Christ!
*Theotokion:* He Who sitteth ineffably in the bosom of the Father sitteth as a babe in thine embrace, O Virgin; and the right victorious youths, emulating His blessed passion, elected to die.
Canon of the Venerable One
*Irmos:* Beholding Thee lifted up upon the Cross, O Sun of righteousness, the Church stood rooted in place, crying out as is meet: Glory to Thy power, O Lord!
Having purified thy heart with streams of tears, O venerable one, thou didst cause waters to flow forth in a waterless place, O Memnon, God glorifying thee as His favorite.
Shining forth like a star through thine all-glorious life, O blessed one, by thy sacred wonders thou wast shown to be another heaven for those who cry out with faith: Glory to Thy power, O Lord!
Submitting to the laws of the Master, O venerable one, as a shepherd thou didst guide those under thee to Him Who gave thee the talant which, as a dutiful servant, thou didst greatly increase.
*Theotokion:* My mind, which is drawn to the pleasures of the body, do thou make steadfast through thy mediation, I pray, O Theotokos who alone gavest birth to God, the Bestower of good things.
Ode V
Canon of the Martyrs
*Irmos:* The ungodly perceive not Thy glory, O Christ; but, waking at dawn out of the night, we hymn Thee, O Only-begotten One Who lovest mankind, Thou effulgence of the glory of the Father’s divinity.
Setting fire to your minds like a noetic coal, ye truly consumed all the tinder of falsehood, O blessed ones, and quenched the conflagration of idolatry with the dew of faith.
Going forth to suffer for the indivisible Trinity, O athletes, it was as though ye were not separated into many bodies; wherefore, ye destroyed the whole legion of the devil.
He who with zeal went to your precious reliquaries and was freed from the legion of the evil one hymneth your wonders, O godly martyrs.
*Theotokion:* Thou hast been shown to us as one who delivereth those who hymn thee from misfortunes and corrupting transgressions, passions, sorrows and evil circumstances, O Ever-virgin Theotokos.
Canon of the Venerable One
*Irmos:* Thou hast come, O my Lord, as a light into the world: a holy light turning from the darkness of ignorance those who hymn Thee with faith.
Thy mind fixing its pure gaze upon God, O blessed of God, thou wast shown to be above the pleasures of the flesh.
As a physician of bodies, O thou who art most rich, with the grace of the Spirit drive away the bestial passions of men’s souls.
Blessed art thou, and well is it with thee, O all-blessed one, for thou hast vanquished the malice of the enemy and mortified the passions.
*Theotokion:* Thou gavest birth to God, yet remained a Virgin, O Bride of God; wherefore, the whole tribe of man calleth thee blessed, rejoicing.
Ode VI
Canon of the Martyrs
*Irmos:* I have come unto the depths of the sea, and the tempest of my many sins hath engulfed me; but, as God, lead up my life from the abyss, O greatly Merciful One.
The death of the divine athletes hath been shown to be precious in Thy sight, O God of all, and honoring them now, Thou hast revealed them as healing for the sick which is without cost.
Lifting up your hands and hearts to the highest with lofty intent and manly mind, O God-bearing martyrs, ye put down the assaults of the wicked one.
*Theotokion:* Thy womb was shown to be like a granary holding the Grain of immortality, Who feedeth the souls of all the faithful and enlighteneth the martyrs.
Canon of the Venerable One
*Irmos:* I will sacrifice to Thee with a voice of praise, O Lord, the Church crieth unto Thee, cleansed of the blood of demons by the blood which, for mercy’s sake, flowed from Thy side.
At the mere utterance of thy name the locusts and all the malignancy of the demons are driven away, O Memnon, for thou wast known to be pleasing unto God, Who hath greatly glorified thee, O father.
Having vanquished the assault of carnal knowledge, thou didst receive the grace of the Spirit, to dispel infirmities and to heal souls sick with sin, O right wondrous one.
O the wonder! How at the mere invocation of thee, O all-glorious Memnon, are the faithful saved who sail the seas, beholding thee hastening to still the tumult of the waves?
*Theotokion:* Mortify the wisdom of my flesh, O Virgin, in that thou didst conceive the Slayer of death and Bestower of life and gavest birth to Him in manner past recounting and comprehension, O all-pure one.
Kontakion, in Tone II: Spec. Mel.: “Seeking the highest…”—
The steadfast and most splendid choir of the ten martyrs, who confessed the three-Sunned Godhead, cried out to Him at the tribunal: “O Master, we offer our blood, souls and bodies to Thee as an unblemished sacrifice! Number us among Thy heavenly choirs, in that thou art our merciful God!”
Ode VII
Canon of the Martyrs
*Irmos:* The three youths in Babylon, having put to mockery the tyrant’s command, cried out amid the flames: Blessed art Thou, O Lord God of our fathers!
Your labors ever pour forth divine streams of healings, O right wondrous martyrs, drying up rivers of pain and washing away all the defilement of the passions.
The athletes rejoiced with ineffable joy when they suffered, and, cut down by the sword, they chanted: Blessed art Thou, O Lord God of our fathers!
O glorious athletes, ease for us the heavy weight of infirmities, the sufferings of our hearts, the pangs of our bodies and every sorrow which besetteth us.
*Theotokion:* Having been shown forth as the great might of all the martyrs, O pure Mother of God, thou hast shown thyself to be the help of men who ever hymn thee with sacred songs.
Canon of the Venerable One
*Irmos:* The children of Abraham in the Persian furnace, afire with love of piety more than with the flame, cried out: Blessed art Thou in the temple of Thy glory, O Lord!
With showers of tears thou didst extinguish the furnace of the passions, O blessed one, and now, with the fire of thy miracles and grace, thou dost truly consume the material bane of infirmities.
Thou didst love thy Creator with all thy heart, O blessed and wise Memnon; wherefore, thou didst stand aloof from the flesh and the world, crying: Blessed art Thou in the temple of Thy glory, O Lord!
Planted like a tree by the waters of abstinence, O father Memnon who art most rich, in due season thou didst produce the working of miracles as fruit in abundance.
Thou didst cause the damage wrought by the locusts to cease by thy divine commands, O wise Memnon, and didst halt the waters of the river, crying and saying: Blessed art Thou, O my God!
*Theotokion:* Deliver me from the tempest of innumerable offenses, O Maiden, thou only mighty help of the lowly and cleansing of transgressions. Blessed art thou among women, O most immaculate Mistress!
Ode VIII
Canon of the Martyrs
*Irmos:* O Almighty Deliverer of all, descending into the midst of the flame Thou didst bedew the pious youths and didst teach them to chant: Bless and hymn the Lord, all ye works!
O passion-bearing martyrs, we offer joyous laudation unto Him Who hath given you as great helpers to us who cry: O all ye works of the Lord, bless ye the Lord!
Rooted well like branches on the rock of faith, the martyrs have brought forth the fruits of suffering for us who chant with faith: O all ye works of the Lord, bless ye the Lord!
O greatly renowned physicians of the passions, heal the suffering of my soul and, beseeching Christ our God, deliver me from Gehenna and the outermost darkness thereof.
*Theotokion:* Thou gavest birth to Christ the Bestower of life Who hath crowned the passion-bearing martyrs who suffered lawfully. Him do thou entreat, O Maiden, that He heal me who am vanquished by the law of sin.
Canon of the Venerable One
*Irmos:* Stretching forth his hands, Daniel shut the lions’ mouths in the pit; and the young lovers of piety, girded about with virtue, quenched the power of the fire, crying out: Bless the Lord, all ye works of the Lord!
Thou didst shine forth like the dawn, like a star, like the great sun, O divinely inspired Memnon, and hast illumined with grace the souls of those who have set thee forth as an excellent guide, a sacred teacher and a wondrous instructor, who dost cry: Bless the Lord, all ye works of the Lord!
When thou didst acquire humble wisdom through the grace of the Spirit, O all-blessed one, thou didst deal a deep wound to the enemy who gave rise to death, casting his arrogant mind down to the earth and trampling his soul-corrupting snares underfoot.
Having lived a good life, O holy one, thou wast vouchsafed to behold the blessedness and everlasting delight of heaven and the splendors of the saints; and thou now criest out with joy: Bless the Lord, all ye works of the Lord!
The place which before was waterless and now is full of water proclaimeth thy faith in the Lord, O venerable one, and the grace of the miracles which thou didst perform, crying out to the Bestower of good things: Bless the Lord, all ye works of the Lord!
*Theotokion:* Vouchsafe visitation unto my lowly soul, which is afflicted with the weight of evils and is drowning, O Mistress full of the grace of God, and show it forth as utterly restored to health, crying: Bless the Lord, all ye works of the Lord!
Ode IX
Canon of the Martyrs
*Irmos:* Eve, through weakness, abode under the curse of disobedience; but thou, O Virgin Theotokos, hast put forth blessing for the world through the Offspring of thy child-bearing. Wherefore, we all magnify thee.
“Lo! the gates of heaven have been opened for you who have suffered!” Christ said to the passion-bearers; “Enter in and, rejoicing, receive for your pangs everlasting rewards fit for those who have fought bravely!”
Ye were beautiful in the wounds of your bodies and emulated the angels; and now ye stand before the Beauty of all, ever rejoicing and manifestly adorned with the communion of beautiful things, O most honored ones.
Let us stand in the house of God, praising the sufferings of Antipater and Theostichus, Rufus and Philemon, and the wonders of the divine Thaumasius, Magnus and Artemas, and the invincibility of Theognes and Theodotus.
Today hath the festival of the saints shone forth salvation for us. And, celebrating it with supplication, let us cry out to them with faith: O radiant summit of the martyrs, illumine the hearts of us all!
*Theotokion:* Clothed by thee in the purple robe of the body, the King issued forth, all adorned, from thy womb: and He hath vanquished all enemies and given victory to the athletes, O only pure Ever-virgin.
Canon of the Venerable One
*Irmos:* Christ, the Chief Cornerstone uncut by human hands, Who united the two disparate natures, was cut from thee, the unquarried mountain, O Virgin. Wherefore, in gladness we magnify thee, O Theotokos.
Strengthened by the might of the Godhead, O divinely wise Memnon, thou wast able to overcome all the power of the enemy; wherefore, having received a crown as a victor, pray thou to Christ in our behalf.
Streams of healings pour forth from thy shrine as from a well-spring, O venerable one, and they wash away pain and defilement by the power of the divine Spirit and give drink to the minds of those who honor thee.
Today thy memorial doth enlighten every age and mind like the sun, O father Memnon, for thou didst do the works of the Light; and having now departed unto the never-waning Light, thou hast made thine abode with Him.
Thou wast taken up into the eternal mansions, and beholding God as is meet, thou hast been numbered among the flocks of the venerable, O blessed Memnon. With them be thou ever mindful of those who commemorate thee on earth.
*Theotokion:* O Virgin, we joyously declare to thee the cry of the archangel: Rejoice, O annulment of the curse, glory of the venerable, boast of the martyrs, preaching of the prophets and salvation of men!
| 79.520295 | 501 | 0.786497 | eng_Latn | 0.999592 |
ed3a4488908d59b9223ad436a4b732753898705e | 517 | md | Markdown | README.md | think-js/vue-istanbul-reports | 3e3df24c09d0e80821baced6040133df0a8124ba | [
"BSD-3-Clause"
] | null | null | null | README.md | think-js/vue-istanbul-reports | 3e3df24c09d0e80821baced6040133df0a8124ba | [
"BSD-3-Clause"
] | null | null | null | README.md | think-js/vue-istanbul-reports | 3e3df24c09d0e80821baced6040133df0a8124ba | [
"BSD-3-Clause"
] | null | null | null | # istanbul-reports - with fix for lcov html report
[](https://greenkeeper.io/)
[](https://travis-ci.org/istanbuljs/istanbul-reports)
- node.getRelativeName
- context.getSource(filePath)
- context.classForPercent(type, percent)
- context.console.colorize(str, class)
- context.writer
- context.console.write
- context.console.println
| 36.928571 | 137 | 0.758221 | yue_Hant | 0.490292 |
ed3a70123ffab7b01366a38b6620dc5729106e9b | 26 | md | Markdown | README.md | zddgit/novelServer | 26b9b84e3be920dd3ddea2cf8ba9d8f725f51d1b | [
"Apache-2.0"
] | null | null | null | README.md | zddgit/novelServer | 26b9b84e3be920dd3ddea2cf8ba9d8f725f51d1b | [
"Apache-2.0"
] | null | null | null | README.md | zddgit/novelServer | 26b9b84e3be920dd3ddea2cf8ba9d8f725f51d1b | [
"Apache-2.0"
] | null | null | null | # novelServer
novelServer
| 8.666667 | 13 | 0.846154 | cat_Latn | 0.464582 |
ed3af0b28abf78ebe23fd74ce92d5ba9a36e55ea | 1,485 | md | Markdown | content/en/docs/12.0/overview/supported-databases.md | ABlueCy/website | ae2ee57bb49b2026996174faab8bf1ef99fe5574 | [
"Apache-2.0"
] | null | null | null | content/en/docs/12.0/overview/supported-databases.md | ABlueCy/website | ae2ee57bb49b2026996174faab8bf1ef99fe5574 | [
"Apache-2.0"
] | 3 | 2021-10-30T19:13:29.000Z | 2021-11-01T19:12:51.000Z | content/en/docs/12.0/overview/supported-databases.md | doeg/vitess-website | 4aaea07ca2e176042815dec0d7f250076ce317a6 | [
"Apache-2.0"
] | null | null | null | ---
title: Supported Databases
weight: 2
featured: true
---
Vitess deploys, scales and manages clusters of open-source SQL database instances. Currently, Vitess supports the [MySQL](https://www.mysql.com/), [Percona Server for MySQL](https://www.percona.com/software/mysql-database/percona-server), and to a limited extent [MariaDB](https://mariadb.org) databases.
The [VTGate](../../concepts/vtgate/) proxy server advertises its version as MySQL 5.7.
## MySQL versions 5.6 to 8.0
Vitess supports the core features of MySQL versions 5.6 to 8.0, with [some limitations](../../reference/compatibility/mysql-compatibility/). Vitess also supports [Percona Server for MySQL](https://www.percona.com/software/mysql-database/percona-server) versions 5.6 to 8.0.
{{< info >}}For new Vitess installations, MySQL or Percona Server for MySQL version 8 are recommended.{{< /info >}}
{{< warning >}}
MySQL and Percona Server for MySQL 5.6 are no longer supported in Vitess 13.0 and later.
{{< /warning >}}
## MariaDB versions 10.0 to 10.3
Vitess supports the core features of MariaDB versions 10.0 to 10.3. Vitess [does not yet](https://github.com/vitessio/vitess/issues/5362) support later versions of MariaDB.
{{< warning >}}MariaDB support is likely to end in the future. You can view and comment on [the relevant proposal here](https://github.com/vitessio/vitess/issues/9518).{{< /warning >}}
## See also
+ [MySQL Compatibility](../../reference/compatibility/mysql-compatibility/)
| 49.5 | 304 | 0.743434 | eng_Latn | 0.880381 |
ed3b613ee663f23e7f6d34f11b186e6832a8c04e | 2,643 | md | Markdown | articles/data-factory/connector-overview.md | zer0big/azure-docs.ko-kr | cf9888afefeb065cb30a49deba730f39142f118a | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/data-factory/connector-overview.md | zer0big/azure-docs.ko-kr | cf9888afefeb065cb30a49deba730f39142f118a | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/data-factory/connector-overview.md | zer0big/azure-docs.ko-kr | cf9888afefeb065cb30a49deba730f39142f118a | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Azure Data Factory 커넥터 개요
description: Data Factory에서 지원 되는 커넥터에 대해 알아봅니다.
services: data-factory
author: linda33wj
ms.service: data-factory
ms.workload: data-services
ms.topic: conceptual
ms.date: 09/28/2020
ms.author: jingwang
ms.reviewer: craigg
ms.openlocfilehash: 9b346c24b6a363e66e56f6c16b70058df3864c88
ms.sourcegitcommit: ba7fafe5b3f84b053ecbeeddfb0d3ff07e509e40
ms.translationtype: MT
ms.contentlocale: ko-KR
ms.lasthandoff: 10/12/2020
ms.locfileid: "91945834"
---
# <a name="azure-data-factory-connector-overview"></a>Azure Data Factory 커넥터 개요
[!INCLUDE[appliesto-adf-asa-md](includes/appliesto-adf-asa-md.md)]
Azure Data Factory는 복사, 데이터 흐름, 조회, 메타 데이터 가져오기 및 삭제 작업을 통해 다음과 같은 데이터 저장소와 형식을 지원 합니다. 각 데이터 저장소를 클릭 하 여 지원 되는 기능 및 해당 구성에 대해 자세히 알아보세요.
## <a name="supported-data-stores"></a>지원되는 데이터 저장소
[!INCLUDE [Connector overview](../../includes/data-factory-v2-connector-overview.md)]
## <a name="integrate-with-more-data-stores"></a>추가 데이터 저장소와 통합
Azure Data Factory은 위에서 언급 한 목록 보다 더 광범위 한 데이터 저장소 집합에 도달할 수 있습니다. Azure Data Factory 기본 제공 커넥터 목록에 없는 데이터 저장소에서/로 데이터를 이동 해야 하는 경우 다음과 같은 몇 가지 확장 가능 옵션을 사용할 수 있습니다.
- 데이터베이스 및 데이터 웨어하우스의 경우 일반적으로 [일반 odbc 커넥터](connector-odbc.md)를 사용할 수 있는 해당 odbc 드라이버를 찾을 수 있습니다.
- SaaS 응용 프로그램:
- RESTful Api를 제공 하는 경우 [일반 REST 커넥터](connector-rest.md)를 사용할 수 있습니다.
- OData 피드가 있는 경우 [일반 odata 커넥터](connector-odata.md)를 사용할 수 있습니다.
- SOAP Api를 제공 하는 경우 [일반 HTTP 커넥터](connector-http.md)를 사용할 수 있습니다.
- ODBC 드라이버가 있는 경우 [일반 odbc 커넥터](connector-odbc.md)를 사용할 수 있습니다.
- 다른 경우에는 데이터를 ADF 지원 되는 데이터 저장소 (예: Azure Blob/File/FTP/SFTP/등)로 로드 하거나 표시할 수 있는지 확인 한 다음 ADF를 선택 합니다. [Azure Function](control-flow-azure-function-activity.md), [custom activity](transform-data-using-dotnet-custom-activity.md), [Databricks](transform-data-databricks-notebook.md) / [HDInsight](transform-data-using-hadoop-hive.md), [웹 활동](control-flow-web-activity.md)등을 통해 사용자 지정 데이터 로드 메커니즘을 호출할 수 있습니다.
## <a name="supported-file-formats"></a>지원되는 파일 형식
Azure Data Factory는 다음과 같은 파일 형식을 지원합니다. 형식 기반 설정에 대한 각 문서를 참조하세요.
- [Avro 형식](format-avro.md)
- [이진 형식](format-binary.md)
- [Common Data Model 형식](format-common-data-model.md)
- [구분된 텍스트 형식](format-delimited-text.md)
- [델타 형식](format-delta.md)
- [Excel 형식](format-excel.md)
- [JSON 형식](format-json.md)
- [ORC 형식](format-orc.md)
- [Parquet 형식](format-parquet.md)
- [XML 형식](format-xml.md)
## <a name="next-steps"></a>다음 단계
- [복사 활동](copy-activity-overview.md)
- [매핑 데이터 흐름](concepts-data-flow-overview.md)
- [조회 작업](control-flow-lookup-activity.md)
- [메타데이터 작업 가져오기](control-flow-get-metadata-activity.md)
- [활동 삭제](delete-activity.md)
| 42.629032 | 407 | 0.726826 | kor_Hang | 0.999923 |
ed3c4cec4041476b1946a8380dfc0777437ffc64 | 3,039 | md | Markdown | _publications/2019-01-08-partial_replanning_for_decentralized_dynamic_task_allocation.md | noambuckman/noambuckman.github.io | 37088eff5a33e82e509f796af185e1de5540a1ab | [
"MIT"
] | null | null | null | _publications/2019-01-08-partial_replanning_for_decentralized_dynamic_task_allocation.md | noambuckman/noambuckman.github.io | 37088eff5a33e82e509f796af185e1de5540a1ab | [
"MIT"
] | null | null | null | _publications/2019-01-08-partial_replanning_for_decentralized_dynamic_task_allocation.md | noambuckman/noambuckman.github.io | 37088eff5a33e82e509f796af185e1de5540a1ab | [
"MIT"
] | null | null | null | ---
title: "Partial Replanning for Decentralized Dynamic Task Allocation"
collection: publications
permalink: /publication/2019-01-08-partial_replanning_for_decentralized_dynamic_task_allocation
excerpt: 'In time-sensitive and dynamic missions, multi-UAV teams must respond quickly to new
information and objectives. This paper presents a dynamic decentralized task allocation algorithm for allocating new tasks that appear online during the solving of the task allocation
problem. Our algorithm extends the Consensus-Based Bundle Algorithm (CBBA), a decentralized task allocation algorithm, allowing for the fast allocation of new tasks without a full
reallocation of existing tasks. CBBA with Partial Replanning (CBBA-PR) enables the team to
trade-off between convergence time and increased coordination by resetting a portion of their
previous allocation at every round of bidding on tasks. By resetting the last tasks allocated
by each agent, we are able to ensure the convergence of the team to a conflict-free solution.
CBBA-PR can be further improved by reducing the team size involved in the replanning, further
reducing the communication burden of the team and runtime of CBBA-PR. Finally, we validate
the faster convergence and improved solution quality of CBBA-PR in multi-UAV simulations.'
date: 2019-1-06
venue: 'AIAA Guidance, Navigation & Control'
paperurl: 'https://arc.aiaa.org/doi/10.2514/6.2019-0915'
citation: 'Buckman, N., Choi, H. L., & How, J. P. (2019). Partial Replanning for Decentralized Dynamic Task Allocation. In <i>AIAA Scitech 2019 Forum</i>.'
---
[Download paper here](http://noambuckman.github.io/files/2019_01_08_scitech_final.pdf)
Abstract:
In time-sensitive and dynamic missions, multi-UAV teams must respond quickly to new
information and objectives. This paper presents a dynamic decentralized task allocation algorithm for allocating new tasks that appear online during the solving of the task allocation
problem. Our algorithm extends the Consensus-Based Bundle Algorithm (CBBA), a decentralized task allocation algorithm, allowing for the fast allocation of new tasks without a full
reallocation of existing tasks. CBBA with Partial Replanning (CBBA-PR) enables the team to
trade-off between convergence time and increased coordination by resetting a portion of their
previous allocation at every round of bidding on tasks. By resetting the last tasks allocated
by each agent, we are able to ensure the convergence of the team to a conflict-free solution.
CBBA-PR can be further improved by reducing the team size involved in the replanning, further
reducing the communication burden of the team and runtime of CBBA-PR. Finally, we validate
the faster convergence and improved solution quality of CBBA-PR in multi-UAV simulations.
Recommended citation: 'Buckman, N., Choi, H. L., & How, J. P. (2019). Partial Replanning for Decentralized Dynamic Task Allocation. In <i>AIAA Scitech 2019 Forum</i>'.
| 75.975 | 183 | 0.809477 | eng_Latn | 0.994277 |
ed3c9257dbe3da59621fcb3c1c358c2c98035e77 | 1,264 | md | Markdown | _posts/2017-XX-XX-Creating-a-Simple-Xamarin-Android-Splash-Screen.md | adamzucchi/adamzucchi.github.io | 9d8ed49d039e9d9a2fcb95a71125005eee034a61 | [
"MIT"
] | null | null | null | _posts/2017-XX-XX-Creating-a-Simple-Xamarin-Android-Splash-Screen.md | adamzucchi/adamzucchi.github.io | 9d8ed49d039e9d9a2fcb95a71125005eee034a61 | [
"MIT"
] | null | null | null | _posts/2017-XX-XX-Creating-a-Simple-Xamarin-Android-Splash-Screen.md | adamzucchi/adamzucchi.github.io | 9d8ed49d039e9d9a2fcb95a71125005eee034a61 | [
"MIT"
] | null | null | null | ---
published: false
layout: post
title: Creating a Simple Xamarin.Android Splash Screen
date: 2017-01-21 12:23
comments: true
tags: [Xamarin, Xamarin.Android, Android]
---
Creating a splash screen for your app is not usually priority number 1, but at some point you or your client during the development phase is going to get sick of seeing a blank screen upon app launch. Creating a splash screen for your Xamarin.Android app is quite different from how it's done on your Xamarin.iOS application. In this post I am going to review how I create a simple splash screen on my Xamarin.Android applications.
First is coming up with an idea of what you want displayed on the splash screen. Keep in mind that the splash screen is only shown for a matter of seconds, this means don't put paragraphs of text or very detailed artwork. Typically I will show only a couple assets, such as an app/brand icon and the app title. This artwork is static and will be shipped with the application bundle to the store. Don't plan on including any dynamic text or images from a web service, because this screen is shown prior to any of your app's code actually executing, and as soon as the app is ready the splash screen is removed and your app's first screen is displayed. | 114.909091 | 654 | 0.786392 | eng_Latn | 0.999753 |
ed3c9728497843fe344d61e9a6bc32126ba2005b | 2,073 | md | Markdown | docs/advanced-use/permissions.md | zefixlluja/flagsmith-docs | e24a2c1de14e83c3d764ca958b4b9b7c7661fdca | [
"BSD-3-Clause"
] | null | null | null | docs/advanced-use/permissions.md | zefixlluja/flagsmith-docs | e24a2c1de14e83c3d764ca958b4b9b7c7661fdca | [
"BSD-3-Clause"
] | null | null | null | docs/advanced-use/permissions.md | zefixlluja/flagsmith-docs | e24a2c1de14e83c3d764ca958b4b9b7c7661fdca | [
"BSD-3-Clause"
] | null | null | null | ---
title: Permissions
description: Team member and group permissions.
---
Flagsmith provides fine-grained permissions to help larger teams manage access and roles across projects and
environments.
Permissions are assigned to individual team members or to groups.
## Groups
Groups are a convenient way to manage permissions for multiple team members. Groups can contain any number of team
members. You can create groups with the Organisation Settings page.
## Organisations
Team members can be defined as Organisation Administrators. This is effectively a super-user role, and gives full
read/write access to every Project, Environment, Flag, Remote Config and Segment within that organisation.
## Projects
Team Members and Groups can be given individual roles at a Project level.
| **Role** | **Ability** |
| ------------------ | ------------------------------------------------------------------------------------- |
| Administrator | Full Read/Write over all Environments, Feature Flag, Remote Config and Segment values |
| View Project | Can view the Project within their account |
| Create Environment | Can create new Environments within the Project |
| Create Feature | Can create a new Feature / Remote Config |
| Delete Feature | Can remove an existing Feature / Remote Config entirely from the Project |
## Environments
Team Members and Groups can be given individual roles at an Environment level.
| **Role** | **Ability** |
| ---------------- | --------------------------------------------------------- |
| Administrator | Can modify Feature Flag, Remote Config and Segment values |
| View Environment | Can see the Environment within their account |
| 46.066667 | 114 | 0.586589 | eng_Latn | 0.991539 |
ed3cc3a8ce2ebcaeb2f5c398ce80e6906edb1b3a | 6,394 | md | Markdown | _posts/2020-11-17-home-assistant-doorbell.md | PhilippMundhenk/PhilippMundhenk.github.io | 0b3212ccc7f3c718bfd71e3d1a89c7ea3afc03b8 | [
"MIT"
] | null | null | null | _posts/2020-11-17-home-assistant-doorbell.md | PhilippMundhenk/PhilippMundhenk.github.io | 0b3212ccc7f3c718bfd71e3d1a89c7ea3afc03b8 | [
"MIT"
] | null | null | null | _posts/2020-11-17-home-assistant-doorbell.md | PhilippMundhenk/PhilippMundhenk.github.io | 0b3212ccc7f3c718bfd71e3d1a89c7ea3afc03b8 | [
"MIT"
] | null | null | null | ---
layout: post
title: Doorbell & Home Assistant
categories: [home]
---
I live in an almost 100 year old rental flat. I don't have a smart doorbell and do not have the option to install one. Nevertheless, I would like to reap the benefits of a smart doorbell, especially being notified on multiple devices. This is e.g., useful when wearing headphones alone in home office and the post is outside, trying to deliver a parcel. I have missed that more than once.
## Problem Statement
With a simple, wired, "ding-dong-style" doorbell, it is not easily possible to add this to your home automation network. These are wired directly from the switch at the door/gate to the actual bell making the sound. Looking at one of these old doorbells, you will discover that they are working by a spring and coil mechanism, that when activated moves a clapper, which in turn sounds an actual bell. In the one direction it goes "ding", in the other, it goes "dong". This is ridiculously cheap to build and lasts for decades or more.
## Setup
The big advantage of this setup is that the rather strong magnetic field used to move the clapper extends beyond casing, at least if this is made of plastic, which is usually the case. We can pick up this signal with a door/window sensor. These are also magnetic and easily pick up on the magnetic field of the doorbell. You might have to try out a few different positions for the sensor, but likely you will find one that works. I am using an Aqara sensor on my 60+ year old doorbell:
## Wrapping the sensor
Note that the magnetic field might cause multiple on/off cycles and we will need to debounce this. I will take a slightly different approach to my [motion sensor](/tradfri-motion-sensor/), but some of the configuration below might look familiar. We will also wrap the open/close sensor with a new binary sensor that we can name accordingly and assign a new device class with states that fit a little nicer to a doorbell than "open" and "close". However, the delay can be realized a little simpler than for the [motion sensor](/tradfri-motion-sensor/).
### Configuration
{% raw %}
```yaml
input_boolean:
doorbell_raw:
name: Doorbell Raw
initial: off
binary_sensor:
- platform: template
sensors:
doorbell:
friendly_name: "Doorbell"
value_template: >-
{% if is_state("input_boolean.doorbell_raw", "on") %}
on
{% else %}
off
{% endif %}
```
{% endraw %}
Since HA does not allow us to directly set the state of the sensor, which is generally a good idea, we need to use an input_boolean instead. It would be possible to set the sensor values via a [Python script](https://github.com/rodpayne/home-assistant/blob/master/python_scripts/set_state.py), but I try to avoid third-party plugins, if I can. Maintenance can be an issue, especially with fast-moving software like HA.
I declare an input_boolean, which in turn is wrapped around by a binary_sensor, the "virtual" doorbell sensor. Technically, the input_boolean is enough for everything we do here. However, declaring a binary_sensor allows us to easily look and act like a sound sensor, when changing the device class the customizations:
### Customization
```yaml
binary_sensor.doorbell:
device_class: sound
```
Here, I set the device class, making sure that states are named on/off, the icon is adjusted, etc.
### Automation
Now the new input_boolean needs to be connected to the original sensor, in my case binary_sensor.openclose_29. This is done via automations.
```yaml
- id: doorbell_pressed
alias: Doorbell Pressed
trigger:
- entity_id: binary_sensor.openclose_29
platform: state
to: 'on'
action:
- service: input_boolean.turn_on
data:
entity_id: input_boolean.doorbell_raw
- delay: 00:00:02
- service: input_boolean.turn_off
data:
entity_id: input_boolean.doorbell_raw
```
There is one little trick in here: The turning off of the sensor is ignored and the input_boolean is turned off only after a delay, in this case 2 seconds. Thus, if within two seconds, the on/off cycle is detected multiple times, this has no effect, as an additional trigger on a running automation is by default ignored. The input_boolean.doorbell_raw will remain on. This debounces the clapper moving, and also rapid doorbell pressing.
## Usages
The doorbell can be used for many applications. The first thing that comes to my mind is of course a notification, so I am alerted also when I don't hear the doorbell, e.g., when wearing headphones:
```yaml
- id: doorbell_notification
alias: Doorbell Notification
trigger:
- entity_id: binary_sensor.doorbell
platform: state
to: 'on'
action:
- service: notify.all
data:
message: Open the door
title: Doorbell rings!
```
If you have a webcam and a Raspberry Pi or some similar setup, you could point the webcam to the door and take a photo of your entrance, whenever the doorbell is pressed. You could of course also show a livestream from the camera on one or all of your media players. Make sure you follow your countries data protection policy when doing this. Not everyone is allowed to record public spaces everywhere at all times.
You could also alert a little stronger by flashing some lights or changing their color, rather than just via a notification. For me, the notification is sufficient.
In case I am currently watching TV or a movie, I don't want to have to deal with that first, but rather quickly rush to the door, the post does not wait long. So I just pause the TV, Kodi timeshift will take care that I don't miss anything, even when watching broadcast TV:
```yaml
- id: doorbell_pause_tv
alias: Doorbell Pause TV
trigger:
- entity_id: binary_sensor.doorbell
platform: state
to: 'on'
action:
- service: media_player.media_pause
entity_id: media_player.kodi
```
## Conclusion
It is not always necessary to buy a new "smart" doorbell. Aside from the cost, many of these run over the internet and one has to rely on the company offering the service and keeping the device secure. Often enough that has proven to not work. Instead, I just my old doorbell and make it smart. This is ideal for me, as a door/window sensor is less than 10 Euros and I am not relying on any online services. | 53.283333 | 551 | 0.754457 | eng_Latn | 0.999403 |
ed3cf64843667a6414ea5a535ffe1275275ae6d3 | 1,389 | md | Markdown | README.md | Webklex/tiny-file-visitor-counter | b1aaf152225413ad2812260ee6ab54a2868b6492 | [
"MIT"
] | null | null | null | README.md | Webklex/tiny-file-visitor-counter | b1aaf152225413ad2812260ee6ab54a2868b6492 | [
"MIT"
] | null | null | null | README.md | Webklex/tiny-file-visitor-counter | b1aaf152225413ad2812260ee6ab54a2868b6492 | [
"MIT"
] | null | null | null | # TF Counter
### Tiny File based visitor counter plugin for Wordpress
Contributors: Webklex
Donate link: http://webklex.com
Tags: visitor, counter
Requires at least: 3.0.1
Tested up to: 3.4
Stable tag: 4.3
License: GPLv2 or later
License URI: http://www.gnu.org/licenses/gpl-2.0.html
This Plugin provides you with some very basic and simple visitor counter for your Wordpress site.
## Description
There isn't much to say about this plugin. Just give it a try and find out ;)
## Installation
1. Upload the unziped content of `tiny-file-visitor-counter.zip` to the `/wp-content/plugins/tiny-file-visitor-counter` directory
2. Activate the plugin through the 'Plugins' menu in WordPress
3. Head over to the settings section and push at least once the save button
## Usage
After you activated the plugin you can access the plugin anywhere at any time you want.
Just place some of the following HTML code right there where you want the statistics displayed:
```
Now Online: <js-counter-online></js-counter-online>
Last day: <js-counter-day></js-counter-day>
Last week: <js-counter-day7></js-counter-day7>
Last month: <js-counter-day30></js-counter-day30>
Last year: <js-counter-year></js-counter-year>
```
An example could be a text widget which might be placed somewhere in the sidebar or footer section.
## Screenshots
Havn't done any jet..
## Changelog
#### 0.01a
* INIT
| 30.866667 | 129 | 0.7509 | eng_Latn | 0.973527 |
ed3d002d458b72ac431c2dfe76466554d961a785 | 8,487 | md | Markdown | rfcs/function-root-field-customisation.md | eazyfin/graphql-engine | 72cc73826b37bfb05bde505fe21f8a60201855cb | [
"Apache-2.0",
"MIT"
] | 27,416 | 2018-07-10T09:22:08.000Z | 2022-03-31T18:26:49.000Z | rfcs/function-root-field-customisation.md | eazyfin/graphql-engine | 72cc73826b37bfb05bde505fe21f8a60201855cb | [
"Apache-2.0",
"MIT"
] | 7,682 | 2018-07-10T08:31:19.000Z | 2022-03-31T18:07:44.000Z | rfcs/function-root-field-customisation.md | eazyfin/graphql-engine | 72cc73826b37bfb05bde505fe21f8a60201855cb | [
"Apache-2.0",
"MIT"
] | 2,753 | 2018-07-10T09:21:30.000Z | 2022-03-31T16:00:06.000Z | # Customising Function Root Field Names
## Metadata
```
---
authors:
Vamshi Surabhi <[email protected]>,
Gil Mizrahi <[email protected],
Evie Ciobanu <[email protected]>,
Philip Lykke Carlsen <[email protected]>
discussion:
https://github.com/hasura/graphql-engine/issues/7405
state: published
---
```
## Description
We should let users customise the GraphQL name that appears in the schema of SQL
Functions tracked by The GraphQL Engine.
### Problem
Being able to customise the names that _tables_ are exposed under in the GraphQL
schema is already supported by The GraphQL Engine, since
[PR-5719](https://github.com/hasura/graphql-engine/pull/5719).
Citing the above PR for motivation:
> .. The identifier can be useful to use when tracking tables with non GraphQL
> compliant names or it can be useful if the nodes that are generated should not
> be dependent on the table name i.e when a table is tracked with an identifier
> and if the table has been renamed, the node names will not be changed due to
> the identifier.
The same motivation applies for functions that are exposed in the GraphQL Schema.
### Success
This feature will have been implemented fully when a user is able to, through the Console:
* Track a function
* Set a custom name for it
* Use that name in queries
Similarly, the server-specific part will have been implemented once there is an
integration test that performs the above steps via the server API.
## What
The server part should add new metadata API endpoint(s) that allows a user, for
some given tracked function, to specify a custom name that is used to query
this function in the GraphQL Schema. In the absence of this feature, the name of
the tracked function is just directly exposed in the GraphQL schema
<a name="footnote-1-ref"></a>[[1]](#footnote-1-def).
The console part should include a tab within the tracked function page that lets
users specify the customised name, similarly to how custom table names are
specified.
It's important to note that this change only affects the GraphQL frontend,
leaving SQL generation untouched.
Also note that, since the Postgres backend is the only one that supports
functions, the change described in this document is only in scope for Postgres.
In the longer perspective, the query abstraction feature that will be
implemented across backends will not be SQL Functions directly, but rather
_Stored Queries_, which as of this writing have yet to be specified. (See [Slack
Discussion](https://hasurahq.slack.com/archives/C01RZPEPF0W/p1627580823109200))
### Effects and Interactions
This will require work on both Server and Console. Once the Server parts have
been implemented the Console parts can be implemented.
This adds new metadata API endpoints. We don't perceive this feature to
interfere with any other features.
### Unresolved Questions
None. See linked discussion for historically unresolved questions.
## How
Functions already have a `configuration` section - we can add two top level
fields called `custom_name` and `custom_root_fields` as follows:
```yaml
functions:
- function: function_name
configuration:
session_argument: ...
exposed_as: ...
custom_name: a custom graphql compliant name
custom_root_fields:
function: FunctionName
function_aggregate: SomeOtherName
permissions: ...
```
Console will require an equivalent of `set_table_customization`, maybe
`set_function_configuration` to allow modifying this configuration after a
function is tracked.
The `configuration` section of a function (`FunctionMetadata b`) needs two new
options:
1. `custom_name` is optional and expects a GraphQL name. `custom_name` should be
used in place of the function's name when generating GraphQL fields or types
for the function.
1. `custom_root_fields` is optional and expects an object with the following two
fields (both should be GraphQL names):
1. `function`: This name should be used for the field name which exposes the
function in the appropriate operation root (query/mutation/subscription).
When this not specified, we use `<custom_name/function_name>` as the field
name.
1. `function_aggregate`: This name should be used for the aggregate operation
that is exposed on the function. In the absence of this option, we use
`<custom_name/function_name>_aggregate` as the field name.
Note that both `function` and `function_name` take precedence over
`custom_name`.
We do not expect functions support on other databases, so this is only expected
to work on Postgres databases.
(These are equivalent to `custom_name` and `custom_root_fields` in a table's
`configuration` section (`TableConfig b`))
In addition, we need an API for updating this configuration from the console.
For table configuration, it is done through `set_table_customization` so we need
something similar to that for functions too. I'm wondering if it makes sense to
just add `replace_if_exists` key to `track_function` API instead of a
`set_function_customization` API.
### Examples
Example, consider the following schema:
```sql
create table article (
id serial primary key,
title text not null,
content text not null
);
create function search_articles(key text)
returns setof articles AS $$
select * from article
where
title ilike ('%' || key || '%')
OR content ilike ('%' || key || '%')
$$ language sql stable;
```
with this metadata:
```yaml
version: 3
sources:
- name: wb
kind: postgres
configuration:
connection_info:
database_url:
from_env: WORKBENCH_URL
tables:
- table: article
functions:
- function: search_articles
```
We would have the following fields in `query_root` (considering only the fields
of function `search_articles`):
```graphql
search_articles(
args: search_articles_args!
distinct_on: [article_select_column!]
limit: Int
offset: Int
order_by: [article_order_by!]
where: article_bool_exp
): [article!]!
search_articles_aggregate(
args: search_articles_args!
distinct_on: [article_select_column!]
limit: Int
offset: Int
order_by: [article_order_by!]
where: article_bool_exp
): article_aggregate!
```
If `custom_name` is specified as follows:
```yaml
version: 3
sources:
- name: wb
kind: postgres
configuration:
connection_info:
database_url:
from_env: WORKBENCH_URL
tables:
- table: article
functions:
- function: search_articles
configuration:
custom_name: find_articles
```
the root fields would have the following schema:
```graphql
find_articles(
args: find_articles_args!
distinct_on: [article_select_column!]
limit: Int
offset: Int
order_by: [article_order_by!]
where: article_bool_exp
): [article!]!
find_articles_aggregate(
args: find_articles_args!
distinct_on: [article_select_column!]
limit: Int
offset: Int
order_by: [article_order_by!]
where: article_bool_exp
): article_aggregate!
```
The changes are:
```
search_articles -> find_articles (root field name)
search_articles_aggregate -> find_articles_aggregate (root field name)
search_articles_args -> find_articles_args (input type name)
```
Instead, if `custom_root_fields` are specified as follows:
```yaml
version: 3
sources:
- name: wb
kind: postgres
configuration:
connection_info:
database_url:
from_env: WORKBENCH_URL
tables:
- table: article
functions:
- function: search_articles
configuration:
custom_name: find_articles
custom_root_fields:
function: FindArticles
function_aggregate: FindArticlesAggregate
```
the generated schema should be:
```graphql
FindArticles(
args: find_articles_args!
distinct_on: [article_select_column!]
limit: Int
offset: Int
order_by: [article_order_by!]
where: article_bool_exp
): [article!]!
FindArticlesAggregate(
args: find_articles_args!
distinct_on: [article_select_column!]
limit: Int
offset: Int
order_by: [article_order_by!]
where: article_bool_exp
): article_aggregate!
```
The changes are:
```
find_articles -> FindArticles (root field name)
find_articles_aggregate -> FindArticlesAggregate (root field name)
```
## Future work
In general maybe we can extend most of our
`track_*/create_*` APIs with `replace_if_exists` similar to `CREATE OR REPLACE`
in Postgres?
## Footnotes
<a name="footnote-1-def"></a>[1][^](#footnote-1-ref): Subject to the name being made into a valid GraphQL identifier.
| 27.735294 | 117 | 0.752798 | eng_Latn | 0.992073 |
ed3d98adf38cad84456495b32ff5241f3bd4c60f | 3,973 | md | Markdown | docs/_posts/2018-11-26-MR合成用のexternalcamera.cfgの作成.md | sh-akira/VirtualMotionCapture | 50401303a850a010d6d28075ae12f31f8d740828 | [
"MIT"
] | 563 | 2018-07-09T19:31:41.000Z | 2022-03-31T09:14:15.000Z | docs/_posts/2018-11-26-MR合成用のexternalcamera.cfgの作成.md | sh-akira/VirtualMotionCapture | 50401303a850a010d6d28075ae12f31f8d740828 | [
"MIT"
] | 46 | 2018-12-19T20:12:05.000Z | 2022-03-26T15:02:14.000Z | docs/_posts/2018-11-26-MR合成用のexternalcamera.cfgの作成.md | sh-akira/VirtualMotionCapture | 50401303a850a010d6d28075ae12f31f8d740828 | [
"MIT"
] | 111 | 2018-07-18T17:18:51.000Z | 2022-03-31T09:14:17.000Z | ---
weight: 600
date: 2018-11-26
title: MR合成用のexternalcamera.cfgの作成
categories:
- manual
author_staff_member: sh_akira
---
MR合成用のexternalcamera.cfgの作成
<span style="color: red;">この手順書は古い情報です。LIVを使ってVRゲーム内合成を行いたい場合は</span>[LIVとVMTでVRゲーム内合成](https://vmc.info/manual/LIV%E3%81%A8VMT%E3%81%A7VR%E3%82%B2%E3%83%BC%E3%83%A0%E5%86%85%E5%90%88%E6%88%90.html)<span style="color: red;">をご覧ください</span>
## externalcamera.cfgとは
ゲーム内に入ったような撮影(MR合成)を行うには、ゲーム側とバーチャルモーションキャプチャーのカメラの向きを合わせるためのファイル、externalcamera.cfgファイルが必要になります。
externalcamera.cfgファイルには"3本目"のコントローラーからカメラまでのオフセット位置が入っています。本来この機能は、ビデオカメラでVRゲームをしている人をグリーンバックでゲーム内に合成させるために用意された機能です。
ビデオカメラにコントローラーを取り付けて、現実世界で撮影した、VRをプレイしている人とゲームの位置を合わせて合成することが出来るというものです。
バーチャルモーションキャプチャーではこの機能を利用して、実際のビデオカメラの代わりに、3Dモデルを同じ位置に表示してゲーム内合成を行うための機能が搭載されています。
SteamVRの一部のゲームや、LIVに対応したゲームでこのファイルを使って合成処理を行うことが出来ます。
[基本のキャリブレーション](https://vmc.info/manual/%E5%9F%BA%E6%9C%AC%E3%81%AE%E6%93%8D%E4%BD%9C%E6%96%B9%E6%B3%95.html)を完了して、バーチャルモーションキャプチャー単体でモデルの動きを確認出来た状態から説明をします。
externalcamera.cfgを出力するためには基準となる3本目のコントローラーもしくは、仮想コントローラーを先に用意する必要があります。仮想コントローラーの作成方法は次のページをご覧ください。
・[LIVの初期設定](https://vmc.info/manual/LIV%E3%81%AE%E5%88%9D%E6%9C%9F%E8%A8%AD%E5%AE%9A.html)
・MixedRealityTwoControllerのインストール(執筆中)
## MR合成用のキャリブレーションを行う
コントロールパネルの設定タブからキャリブレーションを押します。
キャリブレーションはMR合成モードの二つのうちどちらかを選択します。
・MR合成モード(手の位置をなるべく合わせて足は真っ直ぐ延ばす)を選択すると、足が長いモデルの場合地面に足が刺さります。
BeatSaberのように地面が透明な場合は特に問題ありません
・MR合成モード(手の位置をなるべく合わせて足は地面に合わせて曲げる)を選択すると、足が長いモデルの場合膝を曲げて地面に立つようにします。
H3VRのように地面があるゲームの場合、足が貫通するのを防ぎます。
※通常モード(体の動きをなるべく再現する)を選択すると、プレイエリアの中心にいる場合は問題ありませんが、移動すると手からコントローラーがずれていくため、基本的には上二つのMR合成モードを使用してください。
## カメラの向きを決める
コントロールパネルのカメラタブからフリーカメラを選択します。
バーチャルモーションキャプチャーのメイン画面(モデルが表示されている画面)上でマウス操作でカメラを動かします。
マウスのホイールクリックでドラッグすることでカメラの移動
マウスの右クリックでドラッグすることでカメラの回転
モデルを180度後ろに回転させたい場合は、同じ方向にホイールドラッグと右クリックドラッグを交互に行うことで回転します。
## externalcamera.cfgを出力する
コントロールパネルの設定タブから詳細設定を開きます
externalcamera.cfg(フリーカメラ座標を設定)のコントローラー番号でカメラに使用したい3本目のコントローラーを設定します。
LIVを使用する場合はコントローラー(LIV Virtual Camera (Controller))を
MixedRealityTwoControllerを使用する場合はコントローラー(Virtual Controller)を選択してください。
コントローラーを選択したらexternalcamera.cfgをファイルに出力します。
externalcamera.cfgを出力ボタンを押してください。
ファイルを保存する画面が表示されるのでファイル名を変えずに(externalcamera.cfgのまま)お好きなフォルダに保存してください。
このファイルをこの後合成時に使用します。
<span style="color:red">**externalcamera.cfgをVirtualMotionCapture.exeと同じフォルダに保存しないでください！**</span>
<span style="color:red">**バーチャルモーションキャプチャーの画面が4分割されてしまい正常に動作しなくなります。**</span>
## 実際にゲームと合成する
・[LIVとバーチャルモーションキャプチャーでMR合成](https://vmc.info/manual/LIV%E3%81%A8%E3%83%90%E3%83%BC%E3%83%81%E3%83%A3%E3%83%AB%E3%83%A2%E3%83%BC%E3%82%B7%E3%83%A7%E3%83%B3%E3%82%AD%E3%83%A3%E3%83%97%E3%83%81%E3%83%A3%E3%83%BC%E3%81%A7MR%E5%90%88%E6%88%90.html)
・externalcamera.cfgを直接ゲームフォルダに置いてMR合成する(執筆中)
| 44.144444 | 246 | 0.830607 | yue_Hant | 0.432307 |
ed3e7e8945f1436ef13f502ccd4d249429b3afbb | 5,780 | md | Markdown | docs/2014/reporting-services/general-properties-page-reports-report-manager.md | dirceuresende/sql-docs.pt-br | 023b1c4ae887bc1ed6a45cb3134f33a800e5e01e | [
"CC-BY-4.0",
"MIT"
] | 2 | 2021-10-12T00:50:30.000Z | 2021-10-12T00:53:51.000Z | docs/2014/reporting-services/general-properties-page-reports-report-manager.md | dirceuresende/sql-docs.pt-br | 023b1c4ae887bc1ed6a45cb3134f33a800e5e01e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/2014/reporting-services/general-properties-page-reports-report-manager.md | dirceuresende/sql-docs.pt-br | 023b1c4ae887bc1ed6a45cb3134f33a800e5e01e | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-06-25T13:33:56.000Z | 2020-06-25T13:33:56.000Z | ---
title: Página Propriedades gerais, relatórios (Gerenciador de relatórios) | Microsoft Docs
ms.custom: ''
ms.date: 03/06/2017
ms.prod: sql-server-2014
ms.reviewer: ''
ms.suite: ''
ms.technology:
- reporting-services-native
ms.tgt_pltfrm: ''
ms.topic: conceptual
ms.assetid: 66c99d28-ab41-45f0-bf02-ed560293595d
caps.latest.revision: 29
author: markingmyname
ms.author: maghan
manager: craigg
ms.openlocfilehash: 7d4b9885c1dc28d7786296a220d76f56e24a43e1
ms.sourcegitcommit: c8f7e9f05043ac10af8a742153e81ab81aa6a3c3
ms.translationtype: MT
ms.contentlocale: pt-BR
ms.lasthandoff: 07/17/2018
ms.locfileid: "39084648"
---
# <a name="general-properties-page-reports-report-manager"></a>Página Propriedades Gerais, Relatórios (Gerenciador de Relatórios)
Use a página Propriedades Gerais para que os relatórios renomeiem, excluam, movam ou substituam a definição do relatório. Você também pode usar essa página para criar um relatório vinculado. Detalhes sobre quem criou ou modificou o relatório e quando as alterações ocorreram são indicados na parte superior da página.
## <a name="navigation"></a>Navegação
Use o procedimento a seguir para navegar para este local na interface do usuário.
###### <a name="to-open-the-general-properties-page-for-a-report"></a>Para abrir a página Propriedades gerais de um relatório
1. Abra o Gerenciador de Relatórios e localize o relatório cujas propriedades você deseja exibir ou configurar.
2. Focalize o relatório e clique na seta do menu suspenso.
3. No menu suspenso, clique em **Gerenciar**. Esse procedimento abre a página de propriedades Geral do relatório.
## <a name="options"></a>Opções
**Nome**
Especifique um nome para o relatório. Um nome deve conter pelo menos um caractere alfanumérico. Também pode conter espaços e certos símbolos. Não use os caracteres ; ? : \@ & = +, $ * \< >
" ou / ao especificar um nome.
**Descrição**
Digite uma descrição do relatório. Essa descrição aparece na página Conteúdo para usuários com permissão para acessar o relatório.
**Ocultar na exibição de lista**
Selecione essa opção para ocultar o relatório de usuários que estão usando modo de exibição de lista no Gerenciador de Relatórios. O modo de exibição de lista é o formato de exibição padrão quando se navega na hierarquia de pastas do servidor de relatórios. Na exibição de lista, os nomes de itens e as descrições fluem pela página. O formato alternativo é o modo de exibição de detalhes. A exibição de detalhes omite descrições, mas contém outras informações sobre o item. Embora seja possível ocultar um item na exibição de lista, você não pode ocultá-lo na exibição de detalhes. Se quiser restringir o acesso a um item, você precisará criar uma atribuição de função.
**Aplicar**
Clique para salvar as alterações.
**Delete (excluir)**
Clique para remover o relatório do banco de dados do servidor de relatório. A exclusão de um relatório exclui todo o histórico de relatório associado e agendas e assinaturas específicas de relatório. Se o relatório for associado com relatórios vinculados, os relatórios vinculados serão invalidados.
**Migrar**
Clique para realocar um relatório na hierarquia de pasta do servidor de relatório. O clique nesse botão abre a página Mover Itens, na qual você pode navegar até um novo local de pasta. Para obter mais informações, consulte [página Mover itens (Gerenciador de relatórios)](../../2014/reporting-services/move-items-page-report-manager.md).
**Criar relatório vinculado**
Clique para abrir a página Novo Relatório Vinculado. Para obter mais informações sobre essa página e relatórios vinculados, consulte [página novo relatório vinculado (Gerenciador de relatórios)](../../2014/reporting-services/new-linked-report-page-report-manager.md).
**Salvar**
Clique para extrair uma cópia somente leitura da definição do relatório. Dependendo das associações de arquivo definidas no computador, o arquivo abrirá no [!INCLUDE[vsprvs](../includes/vsprvs-md.md)] ou em um aplicativo diferente. Na maioria dos casos, o relatório é aberto como um arquivo XML.
A cópia que você abre é idêntica à definição do relatório original inicialmente publicado no servidor de relatórios. Quaisquer propriedades definidas no relatório após sua publicação (como parâmetros e fonte de dados) não se refletem no arquivo que você abre.
Você pode modificar a definição do relatório e salvá-lo em um novo arquivo em uma pasta compartilhada e carregar a definição do relatório para o servidor de relatório como um novo item. As modificações feitas à definição de relatório enquanto ele está aberto no [!INCLUDE[vsprvs](../includes/vsprvs-md.md)] (ou outro aplicativo) não são salvas diretamente no servidor de relatório. Você deve carregar o arquivo para publicar o relatório modificado no servidor de relatório.
**Substituir**
Clique para substituir a definição do relatório usada no relatório atual por uma diferente de um arquivo .rdl localizado no sistema de arquivos. Se você atualizar uma definição do relatório, deve reajustar as configurações de fonte de dados quando a atualização for concluída.
**Alterar Link**
Clique para selecionar uma definição de relatório diferente para o relatório vinculado. Essa opção será exibida se o relatório for um relatório vinculado. Se o relatório for vinculado, você poderá definir essa propriedade para substituir a definição do relatório.
## <a name="see-also"></a>Consulte também
[O Gerenciador de relatórios (modo nativo do SSRS)](../../2014/reporting-services/report-manager-ssrs-native-mode.md)
[Ajuda F1 do Gerenciador de Relatórios](../../2014/reporting-services/report-manager-f1-help.md)
| 72.25 | 672 | 0.774567 | por_Latn | 0.999972 |
ed3f19e6c2b8334d4a60f5ec263f97cb861c5098 | 1,380 | md | Markdown | content/legacy/rest-interface/error-handling.md | PaytrailTech/documentation | e0bd92da27ee9532773d985b302467261315a0ae | [
"MIT"
] | 4 | 2020-03-06T16:22:14.000Z | 2020-10-21T16:52:07.000Z | content/legacy/rest-interface/error-handling.md | PaytrailTech/documentation | e0bd92da27ee9532773d985b302467261315a0ae | [
"MIT"
] | 138 | 2020-03-20T16:38:30.000Z | 2022-02-15T06:01:38.000Z | content/legacy/rest-interface/error-handling.md | nikoheikkila/documentation | ef947eedb4eb4f2c30109cfd57a3fef70df526fa | [
"MIT"
] | 7 | 2020-03-03T16:06:24.000Z | 2021-03-25T08:45:52.000Z | ---
title: "Error Handling"
draft: false
weight: 2
---
If the sent request is incorrect or there is an error in the interface usage, the interface returns an error message. The error message is in _XML_ or _JSON_ format depending on the request data type (`Content-Type` header). If the data type is incorrect or it was not read, the error message is returned in XML format. Return message for an incorrect request is returned with HTTP error code 400.
Error message XML root element is called `<error>`. Error message returns the following records:
- `errorCode` (character string) \
Error code. Error code is an unambiguous character string that describes the error. Possible error codes are listed in table [error codes][errors].
- `errorMessage` (character string) \
Error description. This is a description of the error in chosen localisation. The error description is not to be shown to customers using the service.
**Example: REST service error message in XML format**
```xml
<?xml version="1.0" encoding="UTF-8"?>
<error>
<errorCode>invalid-order-number</errorCode>
<errorMessage>Missing or invalid order number</errorMessage>
</error>
```
**Example: REST service error message in JSON format**
```json
{
errorCode: 'invalid-order-number',
errorMessage: 'Missing or invalid order number'
}
```
[errors]: {{< ref "legacy/rest-interface/error-codes" >}}
| 38.333333 | 397 | 0.751449 | eng_Latn | 0.987605 |
ed3fb18d0915a4caae15cec3ff1931936443e7fd | 677 | md | Markdown | artic/README.md | kellylab/genomic-surveillance-of-the-bronx | 14a58b89e99946c92287387c6ac1fb34c6c0cde4 | [
"Unlicense"
] | null | null | null | artic/README.md | kellylab/genomic-surveillance-of-the-bronx | 14a58b89e99946c92287387c6ac1fb34c6c0cde4 | [
"Unlicense"
] | null | null | null | artic/README.md | kellylab/genomic-surveillance-of-the-bronx | 14a58b89e99946c92287387c6ac1fb34c6c0cde4 | [
"Unlicense"
] | 1 | 2021-09-15T16:49:38.000Z | 2021-09-15T16:49:38.000Z | These are scripts for running the Artic sequencing pipeline using the [Argo Workflows tool](https://github.com/argoproj).
The file artic.yaml contains the template for running the Artic pipeline itself. The templates in final/ were for reassembling genomes for instances where we sequenced a sample multiple times for higher coverage. The scripts/ folder contains the python scripts which run during each step of the pipeline.
The scripts are configured to run using data in our lab's private Google Cloud Storage bucket and also rely on a Docker image containing sequencing tools. We are unfortunately unable to share the Dockerfile due to restrictions by Oxford Nanopore.
| 96.714286 | 304 | 0.818316 | eng_Latn | 0.999042 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.