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 listlengths 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 listlengths 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 listlengths 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
aa2ac866bc7b30e9ae1a9add0ee365f669cda5b1 | 1,656 | md | Markdown | _posts/2017-12-16-Delphine-Manivet-MALO-TOP-YVES-JUPE-Sleeveless-TeaLength-AlinePrincess.md | retroiccolors/retroiccolors.github.io | 9fcec38e243fcc96a9862bab7dcbf8a153843117 | [
"MIT"
] | null | null | null | _posts/2017-12-16-Delphine-Manivet-MALO-TOP-YVES-JUPE-Sleeveless-TeaLength-AlinePrincess.md | retroiccolors/retroiccolors.github.io | 9fcec38e243fcc96a9862bab7dcbf8a153843117 | [
"MIT"
] | null | null | null | _posts/2017-12-16-Delphine-Manivet-MALO-TOP-YVES-JUPE-Sleeveless-TeaLength-AlinePrincess.md | retroiccolors/retroiccolors.github.io | 9fcec38e243fcc96a9862bab7dcbf8a153843117 | [
"MIT"
] | null | null | null | ---
layout: post
date: 2017-12-16
title: "Delphine Manivet MALO TOP & YVES JUPE Sleeveless Tea-Length Aline/Princess"
category: Delphine Manivet
tags: [Delphine Manivet,Aline/Princess ,Strapless,Tea-Length,Sleeveless]
---
### Delphine Manivet MALO TOP & YVES JUPE
Just **$599.99**
### Sleeveless Tea-Length Aline/Princess
<table><tr><td>BRANDS</td><td>Delphine Manivet</td></tr><tr><td>Silhouette</td><td>Aline/Princess </td></tr><tr><td>Neckline</td><td>Strapless</td></tr><tr><td>Hemline/Train</td><td>Tea-Length</td></tr><tr><td>Sleeve</td><td>Sleeveless</td></tr></table>
<a href="https://www.readybrides.com/en/delphine-manivet-printemps-ete-2015/25729-delphine-manivet-malo-top-yves-jupe.html"><img src="//img.readybrides.com/57671/delphine-manivet-malo-top-yves-jupe.jpg" alt="Delphine Manivet MALO TOP & YVES JUPE" style="width:100%;" /></a>
<!-- break --><a href="https://www.readybrides.com/en/delphine-manivet-printemps-ete-2015/25729-delphine-manivet-malo-top-yves-jupe.html"><img src="//img.readybrides.com/57673/delphine-manivet-malo-top-yves-jupe.jpg" alt="Delphine Manivet MALO TOP & YVES JUPE" style="width:100%;" /></a>
<a href="https://www.readybrides.com/en/delphine-manivet-printemps-ete-2015/25729-delphine-manivet-malo-top-yves-jupe.html"><img src="//img.readybrides.com/57669/delphine-manivet-malo-top-yves-jupe.jpg" alt="Delphine Manivet MALO TOP & YVES JUPE" style="width:100%;" /></a>
Buy it: [https://www.readybrides.com/en/delphine-manivet-printemps-ete-2015/25729-delphine-manivet-malo-top-yves-jupe.html](https://www.readybrides.com/en/delphine-manivet-printemps-ete-2015/25729-delphine-manivet-malo-top-yves-jupe.html)
| 97.411765 | 287 | 0.742754 | yue_Hant | 0.368963 |
aa2afb65ab6be1e86fc421088869211bbec88907 | 5,552 | md | Markdown | README.md | kojix2/Dataset-acess-for-PLOS-ONE | eb80d21858889faa98785ede9238a33ba8ded37a | [
"AAL"
] | 1 | 2020-06-15T17:38:23.000Z | 2020-06-15T17:38:23.000Z | README.md | kojix2/Dataset-acess-for-PLOS-ONE | eb80d21858889faa98785ede9238a33ba8ded37a | [
"AAL"
] | null | null | null | README.md | kojix2/Dataset-acess-for-PLOS-ONE | eb80d21858889faa98785ede9238a33ba8ded37a | [
"AAL"
] | 2 | 2020-12-11T17:41:06.000Z | 2021-07-31T11:58:09.000Z | # Create gastric polyps detection model with Zhejiang University gastric endoscopy datasets
This repository uses [Zhejiang University gastric endoscopy datasets](https://github.com/jiquan/Dataset-acess-for-PLOS-ONE) to identify polyps with [keras-yolo3](https://github.com/qqwweee/keras-yolo3).
## Original datasets and work
:cake: Original paper
Citation: Zhang X, Chen F, Yu T, An J, Huang Z, Liu J, et al. (2019) Real-time gastric polyp detection using convolutional neural networks. PLoS ONE 14(3): e0214133. https://doi.org/10.1371/journal.pone.0214133
https://github.com/jiquan/Dataset-acess-for-PLOS-ONE
## Requirements
Install tensorflow and keras. Use keras2onnx to convert the model to onnx format.
* [keras-yolo3](https://github.com/qqwweee/keras-yolo3)
* [keras2onnx](https://github.com/onnx/keras-onnx)
* [Netron](https://github.com/lutzroeder/netron) (optional)
Download repos.
```sh
git clone https://github.com/kojix2/Dataset-acess-for-PLOS-ONE
git clone https://github.com/qqwweee/keras-yolo3
pip install git+https://github.com/onnx/keras-onnx
```
## Download
You can download the pretrained model here.
(No Data Augmentation for now)
[yolov3.onnx](https://drive.google.com/file/d/1RwVKSFxNF0mpI5ZfHhysBqsFwpp-8QXM/view?usp=sharing)
## 1. Data Preparation
1. Convert image size with ImageMagick. 416 x 416.
The resized images have been already added to the repository. So you do not need to run the script below.
```bash
# create TrainImages directory
sh resize_image.sh
```
2. Create annotation file for Yolov3.
```ruby
ruby convert_annotation.rb > train_polyp.txt
```
## 2. Modify keras-yolo3 scripts
1. Enter keras-yolo3 directory.
```sh
cd keras-yolo3
```
2. Create classes text file. `model_data/polyp_classes.txt`
```sh
mv ../Dataset-acess-for-PLOS-ONE/polyp_classes.txt model_data/polyp_classes.txt
```
3. move `train_polyp.txt` to kraas-yolo3 directory.
```sh
mv ../Dataset-acess-for-PLOS-ONE/train_polyp.txt .
```
4. Copy `train.py` to `train_polyp.py`.
```sh
cp train.py train_polyp.py
```
5. Edit `train_polyp.py` as follows.
Changing the batch size is optional. `Resource exhausted` errors can be avoided by reducing the batch size.
There are two places where `batch_size` is defined, but the latter is important to avoid errors.
```diff
# line 17
- annotation_path = 'train.txt'
+ annotation_path = 'train_polyp.txt'
# line 19
- classes_path = 'model_data/voc_classes.txt'
+ classes_path = 'model_data/polyp_classes.txt'
# line 76 (optional)
- batch_size = 32 # note that more GPU memory is required after unfreezing the body
+ batch_size = 8 # note that more GPU memory is required after unfreezing the body
```
5. Edit `yolo.py`.
```diff
# line 23
- "model_path": 'model_data/yolo.h5',
+ "model_path": 'logs/000/trained_weights_final.h5',
"anchors_path": 'model_data/yolo_anchors.txt',
- "classes_path": 'model_data/coco_classes.txt',
+ "classes_path": 'model_data/polyp_classes.txt',
```
## 3. Train model
```sh
python train_polyp.py
```
It takes about an hour with GTX 1070.
## 4. Verify that the model is generated correctly
```sh
python yolo_video.py --image
# Input image filename: ../Dataset-acess-for-PLOS-ONE/TrainImages/100150_20150104001030003.jpg
```
Did it work well? If it does not work, check for error messages during train.
## 5. Convert the model to onnx format
1. Copy keras-onnx yolov3.py to current directory.
```sh
cp ../keras-onnx/applications/yolov3/yolov3.py onnx_yolov3.py
```
check [README.md ](https://github.com/onnx/keras-onnx/tree/master/applications/yolov3) for usage.
2. Edit `onnx_yolov3.py` as follows
```diff
# line 134
- self.model_path = 'model_data/yolo.h5' # model path or trained weights path
- self.anchors_path = 'model_data/yolo_anchors.txt'
- self.classes_path = 'model_data/coco_classes.txt'
+ self.model_path = 'logs/000/trained_weights_final.h5' # model path or trained weights path
+ self.anchors_path = 'model_data/yolo_anchors.txt'
+ self.classes_path = 'model_data/polyp_classes.txt'
```
3. Convert the model to onnx format.
This command requires an image path as an argument.
```sh
python yolov3.py ../Dataset-acess-for-PLOS-ONE/TrainImages/100150_20150104001030003.jpg
```
The onnx model is stored in the `model_data` directory.
```
model_data/yolov3.onnx
```
4. View the yolov3 network with netron. (optional)
## License
:two_hearts: Thanks to Zhejiang University patients and researchers for great datasets!
From the following description, it is assumed that a model may be created using this dataset of endoscopic images.
Please follow the laws of your area.
> Copyright: © 2019 Zhang et al. This is an open access article distributed under the terms of the Creative Commons Attribution License, which permits unrestricted use, distribution, and reproduction in any medium, provided the original author and source are credited.
> Data Availability: All the trainval images are available on https://github.com/jiquan/Dataset-acess-for-PLOS-ONE. And this information will only be available after paper acceptance.
| 31.191011 | 268 | 0.745677 | eng_Latn | 0.748071 |
aa2c129105d81f446865ce0b91e89adb39b2b92a | 3,274 | md | Markdown | docs/odbc/reference/develop-app/trace-dll.md | zelanko/sql-docs.pt-br | 4bc6a809b48cb3bde3ca5a7b9659febcdd4d602c | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-09-05T16:06:11.000Z | 2021-09-05T16:06:11.000Z | docs/odbc/reference/develop-app/trace-dll.md | zelanko/sql-docs.pt-br | 4bc6a809b48cb3bde3ca5a7b9659febcdd4d602c | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/odbc/reference/develop-app/trace-dll.md | zelanko/sql-docs.pt-br | 4bc6a809b48cb3bde3ca5a7b9659febcdd4d602c | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
description: DLL de rastreamento
title: DLL de rastreamento | Microsoft Docs
ms.custom: ''
ms.date: 01/19/2017
ms.prod: sql
ms.prod_service: connectivity
ms.reviewer: ''
ms.technology: connectivity
ms.topic: conceptual
helpviewer_keywords:
- trace DLLs [ODBC]
- tracing options [ODBC], trace DLLs
ms.assetid: 5ab99bd3-cdc3-4e2c-8827-932d1fcb6e00
author: David-Engel
ms.author: v-daenge
ms.openlocfilehash: 1791b72b5f7e836fba05275f87bd57948a273775
ms.sourcegitcommit: e700497f962e4c2274df16d9e651059b42ff1a10
ms.translationtype: MT
ms.contentlocale: pt-BR
ms.lasthandoff: 08/17/2020
ms.locfileid: "88487499"
---
# <a name="trace-dll"></a>DLL de rastreamento
A DLL que executa o rastreamento é um dos componentes do ODBC Core. No momento, a DLL de rastreamento é fornecida como uma DLL de exemplo no componente ODBC do SDK do Windows e, anteriormente, incluiu o SDK do MDAC (Microsoft Data Access Components). Portanto, a entrada do registro, a interface e o código de exemplo para a DLL de rastreamento estão disponíveis. Essa DLL pode ser substituída por uma DLL de rastreamento produzida por um usuário ODBC ou por um fornecedor de terceiros. Uma DLL de rastreamento personalizada deve receber um nome diferente da DLL de rastreamento de exemplo original. As DLLs de rastreamento devem ser instaladas no diretório do sistema ou não serão carregadas. As cadeias de conexão não serão passadas para a DLL de rastreamento pelo Gerenciador de driver.
A DLL de rastreamento rastreia argumentos de entrada, argumentos de saída, argumentos adiados, códigos de retorno e sqlstates. Quando o rastreamento está habilitado, o Gerenciador de driver chama a DLL de rastreamento em dois pontos: uma vez na entrada da função (antes da validação do argumento) e novamente antes da função retornar.
Quando um aplicativo chama uma função, o Gerenciador de driver chama uma função de rastreamento na DLL de rastreamento antes de chamar a função no driver ou processar a chamada em si. Cada função ODBC tem uma função de rastreamento correspondente (prefixada com *trace*) que é idêntica à função ODBC com a exceção do nome. Quando a função de rastreamento é chamada, a DLL de rastreamento captura os argumentos de entrada e retorna um código de retorno. Como a DLL de rastreamento é chamada antes de o Gerenciador de driver validar argumentos, as chamadas de função inválidas são rastreadas e, portanto, erros de transição de estado e argumentos inválidos são registrados.
Depois de chamar a função trace na DLL de rastreamento, o Gerenciador de driver chama a função ODBC no driver. Em seguida, ele chama **TraceReturn** na DLL de rastreamento. Essa função usa dois argumentos: o valor retornado pela DLL de rastreamento para a função de rastreamento e o código de retorno retornado pelo driver para o Gerenciador de driver para a função ODBC (ou o valor retornado pelo próprio Gerenciador de driver se ele tiver processado a função). A função usa o valor retornado para a função de rastreamento para manipular valores de argumento de entrada capturados. Ele grava o código retornado para a função ODBC no arquivo de log (ou exibe-o dinamicamente, se estiver habilitado). Ele desreferencia os ponteiros do argumento de saída e registra os valores de argumento de saída.
| 102.3125 | 798 | 0.805742 | por_Latn | 0.998824 |
aa2c2b6bec57ac0daf69a8f949ec446c7443e540 | 2,010 | md | Markdown | README.md | jsiebens/inlets.dev | fe2b1b066cb1ea536ccfd60a38bc7a292a3c1c3d | [
"MIT"
] | 4 | 2020-11-01T13:43:30.000Z | 2020-11-02T12:37:15.000Z | README.md | jsiebens/inlets.dev | fe2b1b066cb1ea536ccfd60a38bc7a292a3c1c3d | [
"MIT"
] | 15 | 2020-11-05T21:04:49.000Z | 2021-10-21T08:08:01.000Z | README.md | jsiebens/inlets.dev | fe2b1b066cb1ea536ccfd60a38bc7a292a3c1c3d | [
"MIT"
] | 10 | 2020-11-05T15:22:22.000Z | 2022-01-29T20:17:21.000Z | ## inlets.dev homepage
[](https://app.netlify.com/sites/inlets-dev/deploys)
## Adding a new blog post
* Create an issue and propose the topic. Wait for approval before contributing, unless you've already been asked to contribute a post.
* Create a new YAML file in `blog/_posts` - see [this example](https://github.com/alexellis/inlets.dev/blob/master/blog/_posts/2020-10-29-preparing-docker-hub-rate-limits.md) for how to set the post title and description.
* Prefix it with the date.
* Add images to `/images/` - resize all images to under 200-300KB, for a faster page loading time
* Make sure you have a cropped image for the background / title of the post, this will show up on the page roll-up at /blog/ - good sources for images are: unsplash.com and pexels.com
* Sign-off any commits you make with `git commit -s`, this is not GPG or cryptography, but [a simple declaration](https://en.wikipedia.org/wiki/Developer_Certificate_of_Origin)
* Raise a Pull Request and fill out the whole template, including how you tested the page and the instructions.
If you use any copyrighted material such as text, code, or images, then you must credit the author.
## Usage
## Initial installation
You will need node.js in order to install yarn:
```bash
$ npm i -g yarn
```
You may need to run `brew install/upgrade ruby` if the `bundle` command is unavailable.
If it's still unavailable run:
```bash
$ gem install bundle
```
When you have the tools in place run:
```bash
$ bundle install
$ yarn install
$ yarn run tailwind init _includes/tailwind.config.js
```
### For production:
```bash
JEKYLL_ENV=production bundle exec jekyll build
```
Content will be in `_site`
### To start a preview, simply run:
```bash
bundle exec jekyll serve
```
Access the site at: http://127.0.0.1:4000/
Apple M1:
```bash
arch -arch x86_64 bundle install
arch -arch x86_64 bundle exec jekyll serve
```
| 27.534247 | 221 | 0.741791 | eng_Latn | 0.969105 |
aa2c629dd2c513b11ee6a8b35befd15d477e76c6 | 103,205 | md | Markdown | articles/data-factory/control-flow-expression-language-functions.md | changeworld/azure-docs.tr-tr | a6c8b9b00fe259a254abfb8f11ade124cd233fcb | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/data-factory/control-flow-expression-language-functions.md | changeworld/azure-docs.tr-tr | a6c8b9b00fe259a254abfb8f11ade124cd233fcb | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/data-factory/control-flow-expression-language-functions.md | changeworld/azure-docs.tr-tr | a6c8b9b00fe259a254abfb8f11ade124cd233fcb | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Azure Veri Fabrikası'nda ifade ve işlevler
description: Bu makalede, veri fabrikası varlıkları oluştururken kullanabileceğiniz ifadeler ve işlevler hakkında bilgi sağlar.
services: data-factory
documentationcenter: ''
author: djpmsft
ms.author: daperlov
ms.reviewer: maghan
ms.service: data-factory
ms.workload: data-services
ms.topic: conceptual
ms.date: 11/25/2019
ms.openlocfilehash: 9ef4b569fd8413d2825374c963fb272dd450cf0e
ms.sourcegitcommit: 2ec4b3d0bad7dc0071400c2a2264399e4fe34897
ms.translationtype: MT
ms.contentlocale: tr-TR
ms.lasthandoff: 03/27/2020
ms.locfileid: "74533130"
---
# <a name="expressions-and-functions-in-azure-data-factory"></a>Azure Data Factory’deki ifadeler ve işlevler
> [!div class="op_single_selector" title1="Kullandığınız Veri Fabrikası hizmetisürümünü seçin:"]
> * [Sürüm 1](v1/data-factory-functions-variables.md)
> * [Geçerli sürüm](control-flow-expression-language-functions.md)
Bu makalede, Azure Veri Fabrikası tarafından desteklenen ifadeler ve işlevler hakkında ayrıntılar verilmektedir.
## <a name="expressions"></a>İfadeler
Tanımdaki JSON değerleri çalışma zamanında değerlendirilen gerçek veya ifadeler olabilir. Örnek:
```json
"name": "value"
```
or
```json
"name": "@pipeline().parameters.password"
```
İfadeler json dize değeri herhangi bir yerde görünebilir ve her zaman başka bir JSON değeri neden. JSON değeri bir ifade ise, ifadenin gövdesi at-işareti kaldırılarak ayıklanır (\@). Ile başlayan bir edebi dize \@gerekiyorsa, kullanılarak \@ \@kaçmış olmalıdır. Aşağıdaki örnekler ifadelerin nasıl değerlendirildiğini göstermektedir.
|JSON değeri|Sonuç|
|----------------|------------|
|"parametreler"|'Parametreler' karakterleri döndürülür.|
|"parametreler[1]"|'parametreler[1]' karakterleri döndürülür.|
|"\@\@"|' ' '\@içeren 1 karakterli dize döndürülür.|
|" \@"|' ' ' \@içeren 2 karakterli dize döndürülür.|
İfadeler, ifadelerin `@{ ... }`''e sarılmış olduğu string *enterpolasyonu* adlı bir özelliği kullanarak dizelerin içinde de görünebilir. Örneğin, `"name" : "First Name: @{pipeline().parameters.firstName} Last Name: @{pipeline().parameters.lastName}"`
String enterpolasyon kullanarak, sonuç her zaman bir dize. Ben `myNumber` olarak `42` tanımlamış `myString` `foo`ve say:
|JSON değeri|Sonuç|
|----------------|------------|
|"\@pipeline().parameters.myString"| Dize olarak döner. `foo`|
|"\@{pipeline().parameters.myString}"| Dize olarak döner. `foo`|
|"\@pipeline().parameters.myNumber"| Sayı `42` olarak *döndürür.*|
|"\@{pipeline().parameters.myNumber}"| Dize olarak `42` *döndürür.*|
|"Cevap: @{pipeline().parameters.myNumber}"| Dizeyi `Answer is: 42`döndürür.|
|"\@concat('Cevap: ', string(pipeline().parameters.myNumber))"| Dizeyi döndürür`Answer is: 42`|
|"Cevap: \@ \@{pipeline().parameters.myNumber}"| Dizeyi `Answer is: @{pipeline().parameters.myNumber}`döndürür.|
## <a name="examples"></a>Örnekler
### <a name="a-dataset-with-a-parameter"></a>Parametreli bir veri kümesi
Aşağıdaki örnekte, BlobDataset **yol**adlı bir parametre alır. Değeri, aşağıdaki ifadeyi kullanarak **folderPath** özelliği için bir `dataset().path`değer ayarlamak için kullanılır: .
```json
{
"name": "BlobDataset",
"properties": {
"type": "AzureBlob",
"typeProperties": {
"folderPath": "@dataset().path"
},
"linkedServiceName": {
"referenceName": "AzureStorageLinkedService",
"type": "LinkedServiceReference"
},
"parameters": {
"path": {
"type": "String"
}
}
}
}
```
### <a name="a-pipeline-with-a-parameter"></a>Parametreli bir boru hattı
Aşağıdaki örnekte, ardışık hatlar **inputPath** ve **outputPath** parametrelerini alır. Parametreli blob veri kümesinin **yolu** bu parametrelerin değerleri kullanılarak ayarlanır. Burada kullanılan sözdizimi: `pipeline().parameters.parametername`.
```json
{
"name": "Adfv2QuickStartPipeline",
"properties": {
"activities": [
{
"name": "CopyFromBlobToBlob",
"type": "Copy",
"inputs": [
{
"referenceName": "BlobDataset",
"parameters": {
"path": "@pipeline().parameters.inputPath"
},
"type": "DatasetReference"
}
],
"outputs": [
{
"referenceName": "BlobDataset",
"parameters": {
"path": "@pipeline().parameters.outputPath"
},
"type": "DatasetReference"
}
],
"typeProperties": {
"source": {
"type": "BlobSource"
},
"sink": {
"type": "BlobSink"
}
}
}
],
"parameters": {
"inputPath": {
"type": "String"
},
"outputPath": {
"type": "String"
}
}
}
}
```
### <a name="tutorial"></a>Öğretici
Bu [öğretici,](https://azure.microsoft.com/mediahandler/files/resourcefiles/azure-data-factory-passing-parameters/Azure%20data%20Factory-Whitepaper-PassingParameters.pdf) bir boru hattı ve etkinlik arasında parametrelerin yanı sıra etkinlikler arasında nasıl geçirilebilirsiniz size yol eder.
## <a name="functions"></a>İşlevler
İfadeler içindeki işlevleri arayabilirsiniz. Aşağıdaki bölümlerde bir ifadede kullanılabilecek işlevler hakkında bilgi verilmiştir.
## <a name="string-functions"></a>Dize işlevleri
Dizeleri ile çalışmak için, bu dize işlevleri ve aynı zamanda bazı [toplama işlevleri](#collection-functions)kullanabilirsiniz.
Dize işlevleri yalnızca dizeleri üzerinde çalışır.
| String fonksiyonu | Görev |
| --------------- | ---- |
| [Concat](control-flow-expression-language-functions.md#concat) | İki veya daha fazla dizebirleştirin ve birleştirilmiş dizeyi döndürün. |
| [Endswith](control-flow-expression-language-functions.md#endswith) | Bir dize belirtilen sub string ile bitene denetleyin. |
| [Guıd](control-flow-expression-language-functions.md#guid) | Dize olarak genel olarak benzersiz bir tanımlayıcı (GUID) oluşturun. |
| [ındexof](control-flow-expression-language-functions.md#indexof) | Bir alt dize için başlangıç konumunu döndürün. |
| [Lastındexof](control-flow-expression-language-functions.md#lastindexof) | Bir alt dizenin son oluşumu için başlangıç konumunu döndürün. |
| [Değiştirmek](control-flow-expression-language-functions.md#replace) | Bir alt dizeyi belirtilen dizeyle değiştirin ve güncelleştirilmiş dizeyi döndürün. |
| [Split](control-flow-expression-language-functions.md#split) | Özgün dizedeki belirtilen sınırlayıcı karaktere dayalı daha büyük bir dizeden virgülle ayrılmış alt dizeleri içeren bir dizi döndürün. |
| [Startswith](control-flow-expression-language-functions.md#startswith) | Bir dize belirli bir alt dize ile başlayıp başlamadığını denetleyin. |
| [Dize](control-flow-expression-language-functions.md#substring) | Belirtilen konumdan başlayarak karakterleri bir dizeden döndürün. |
| [Tolower](control-flow-expression-language-functions.md#toLower) | Küçük harf biçiminde bir dize döndürün. |
| [Toupper](control-flow-expression-language-functions.md#toUpper) | Büyük harf biçiminde bir dize döndürün. |
| [Döşeme](control-flow-expression-language-functions.md#trim) | Satır aralığını ve sondaki beyaz boşluğu bir dizeden kaldırın ve güncelleştirilmiş dizeyi döndürün. |
## <a name="collection-functions"></a>Toplama işlevleri
Koleksiyonlarla, genellikle dizilerle, dizeleri ve bazen sözlüklerle çalışmak için bu koleksiyon işlevlerini kullanabilirsiniz.
| Toplama fonksiyonu | Görev |
| ------------------- | ---- |
| [Içerir](control-flow-expression-language-functions.md#contains) | Koleksiyonun belirli bir öğesi olup olmadığını denetleyin. |
| [empty](control-flow-expression-language-functions.md#empty) | Koleksiyonun boş olup olmadığını kontrol edin. |
| [Ilk](control-flow-expression-language-functions.md#first) | Koleksiyondaki ilk öğeyi döndürün. |
| [Kesişim](control-flow-expression-language-functions.md#intersection) | Belirtilen koleksiyonlar arasında *yalnızca* ortak öğelere sahip bir koleksiyon döndürün. |
| [Katılın](control-flow-expression-language-functions.md#join) | Belirtilen karakterle ayrılmış bir dizideki *tüm* öğeleri içeren bir dize döndürün. |
| [Son](control-flow-expression-language-functions.md#last) | Koleksiyondaki son öğeyi döndürün. |
| [Uzun -luğu](control-flow-expression-language-functions.md#length) | Bir dize veya dizideki öğe sayısını döndürün. |
| [Atlamak](control-flow-expression-language-functions.md#skip) | Öğeleri koleksiyonun önünden kaldırın ve diğer tüm öğeleri iade *edin.* |
| [almak](control-flow-expression-language-functions.md#take) | Öğeleri koleksiyonun önünden döndürün. |
| [Birliği](control-flow-expression-language-functions.md#union) | Belirtilen koleksiyonlardan *tüm* öğeleri içeren bir koleksiyon döndürün. |
## <a name="logical-functions"></a>Mantıksal işlevler
Bu işlevler iç koşullar yararlıdır, onlar mantık her türlü değerlendirmek için kullanılabilir.
| Mantıksal karşılaştırma fonksiyonu | Görev |
| --------------------------- | ---- |
| [Ve](control-flow-expression-language-functions.md#and) | Tüm ifadelerin doğru olup olmadığını denetleyin. |
| [equals](control-flow-expression-language-functions.md#equals) | Her iki değerin de eşdeğer olup olmadığını denetleyin. |
| [büyüktür](control-flow-expression-language-functions.md#greater) | İlk değerin ikinci değerden büyük olup olmadığını denetleyin. |
| [greaterOrEquals](control-flow-expression-language-functions.md#greaterOrEquals) | İlk değerin ikinci değerden büyük mü yoksa eşit mi olduğunu denetleyin. |
| [if](control-flow-expression-language-functions.md#if) | Bir ifadenin doğru mu yanlış mı olduğunu kontrol edin. Sonuca bağlı olarak, belirli bir değeri döndürün. |
| [daha az](control-flow-expression-language-functions.md#less) | İlk değerin ikinci değerden küçük olup olmadığını denetleyin. |
| [lessOrEquals](control-flow-expression-language-functions.md#lessOrEquals) | İlk değerin ikinci değerden küçük mü yoksa eşit mi olduğunu denetleyin. |
| [Değil](control-flow-expression-language-functions.md#not) | İfadenin yanlış olup olmadığını kontrol edin. |
| [Veya](control-flow-expression-language-functions.md#or) | En az bir ifadenin doğru olup olmadığını kontrol edin. |
## <a name="conversion-functions"></a>Dönüştürme işlevleri
Bu işlevler, dildeki her bir yerel türü dönüştürmek için kullanılır:
- string
- integer
- float
- boole
- Dizi
- Sözlük
| Dönüştürme işlevi | Görev |
| ------------------- | ---- |
| [Dizi](control-flow-expression-language-functions.md#array) | Belirli bir girişten bir dizi döndürün. Birden çok giriş için [createArray'e](control-flow-expression-language-functions.md#createArray)bakın. |
| [base64](control-flow-expression-language-functions.md#base64) | Bir dize için base64 kodlanmış sürümü döndürün. |
| [base64ToBinary](control-flow-expression-language-functions.md#base64ToBinary) | Base64 kodlanmış bir dize için ikili sürümü döndürün. |
| [base64ToString](control-flow-expression-language-functions.md#base64ToString) | Base64 kodlanmış bir dize için dize sürümünü döndürün. |
| [ikili](control-flow-expression-language-functions.md#binary) | Bir giriş değeri için ikili sürümü döndürün. |
| [bool](control-flow-expression-language-functions.md#bool) | Giriş değeri için Boolean sürümünü döndürün. |
| [Coalesce](control-flow-expression-language-functions.md#coalesce) | Bir veya daha fazla parametreden ilk null olmayan değeri döndürün. |
| [createArray](control-flow-expression-language-functions.md#createArray) | Birden çok girişten bir dizi döndürün. |
| [dataUri](control-flow-expression-language-functions.md#dataUri) | Giriş değeri için veri URI'yi döndürün. |
| [dataUritoBinary](control-flow-expression-language-functions.md#dataUriToBinary) | Bir veri URI için ikili sürümü döndürün. |
| [dataUritostring](control-flow-expression-language-functions.md#dataUriToString) | Veri URI için dize sürümünü döndürün. |
| [decodeBase64](control-flow-expression-language-functions.md#decodeBase64) | Base64 kodlanmış bir dize için dize sürümünü döndürün. |
| [decodeDataUri](control-flow-expression-language-functions.md#decodeDataUri) | Bir veri URI için ikili sürümü döndürün. |
| [decodeUriComponent](control-flow-expression-language-functions.md#decodeUriComponent) | Kaçış karakterlerinin yerine deşifre edilmiş sürümlerle bir dize döndürün. |
| [kodlamaUriComponent](control-flow-expression-language-functions.md#encodeUriComponent) | URL'de güvenli olmayan karakterlerin yerine kaçış karakterleri getiren bir dize döndürün. |
| [float](control-flow-expression-language-functions.md#float) | Giriş değeri için kayan nokta numarası döndürün. |
| [int](control-flow-expression-language-functions.md#int) | Tamsayı sürümünü bir dize için döndürün. |
| [Json](control-flow-expression-language-functions.md#json) | Bir dize veya XML için JavaScript Nesne Gösterimi (JSON) türü değerini veya nesnesini döndürün. |
| [Dize](control-flow-expression-language-functions.md#string) | Giriş değeri için dize sürümünü döndürün. |
| [uriComponent](control-flow-expression-language-functions.md#uriComponent) | URL'de güvenli olmayan karakterleri kaçış karakterleriyle değiştirerek URI kodlu sürümü giriş değeri için döndürün. |
| [uriComponentToBinary](control-flow-expression-language-functions.md#uriComponentToBinary) | URI kodlu bir dize için ikili sürümü döndürün. |
| [uriComponentToString](control-flow-expression-language-functions.md#uriComponentToString) | URI kodlanmış bir dize için dize sürümünü döndürün. |
| [Xml](control-flow-expression-language-functions.md#xml) | XML sürümünü bir dize için döndürün. |
| [Xpath](control-flow-expression-language-functions.md#xpath) | XML'yi, XPath (XML Path Language) ifadesiyle eşleşen düğümler veya değerler için denetleyin ve eşleşen düğümleri veya değerleri döndürün. |
## <a name="math-functions"></a>Matematik İşlevleri
Bu işlevler her iki sayı türü için de kullanılabilir: **hem de sayacılar** ve **şamandıralar.**
| Matematik fonksiyonu | Görev |
| ------------- | ---- |
| [add](control-flow-expression-language-functions.md#add) | İki sayı ekleyerek sonucu döndürün. |
| [div](control-flow-expression-language-functions.md#div) | Sonucu iki sayıyı bölerek döndürün. |
| [Max](control-flow-expression-language-functions.md#max) | Bir sayı kümesinden veya diziden en yüksek değeri döndürün. |
| [Dk](control-flow-expression-language-functions.md#min) | Bir sayı kümesinden veya diziden en düşük değeri döndürün. |
| [mod](control-flow-expression-language-functions.md#mod) | Kalan sayıyı iki sayıyı bölerek döndürün. |
| [Mul](control-flow-expression-language-functions.md#mul) | Ürünü iki sayıyı çarparak döndürün. |
| [Rand](control-flow-expression-language-functions.md#rand) | Belirli bir aralıktan rasgele bir tamsayı döndürün. |
| [Aralığı](control-flow-expression-language-functions.md#range) | Belirtilen bir tamsededen başlayan bir tamsayı dizini döndürün. |
| [Alt](control-flow-expression-language-functions.md#sub) | İkinci sayıyı ilk sayıdan çıkarmanın sonucunu döndürün. |
## <a name="date-functions"></a>Tarih işlevleri
| Tarih veya saat fonksiyonu | Görev |
| --------------------- | ---- |
| [Adddays](control-flow-expression-language-functions.md#addDays) | Zaman damgasına birkaç gün ekleyin. |
| [Addhours](control-flow-expression-language-functions.md#addHours) | Zaman damgasına birkaç saat ekleyin. |
| [Addminutes](control-flow-expression-language-functions.md#addMinutes) | Zaman damgasına birkaç dakika ekleyin. |
| [Addseconds](control-flow-expression-language-functions.md#addSeconds) | Zaman damgasına birkaç saniye ekleyin. |
| [addToTime](control-flow-expression-language-functions.md#addToTime) | Zaman damgasına birkaç zaman birimi ekleyin. Ayrıca [bkz.](control-flow-expression-language-functions.md#getFutureTime) |
| [convertFromUtc](control-flow-expression-language-functions.md#convertFromUtc) | Evrensel Zaman Eşgüdümlü'nden (UTC) bir zaman damgasını hedef saat dilimine dönüştürün. |
| [dönüştürmeTimeZone](control-flow-expression-language-functions.md#convertTimeZone) | Kaynak saat diliminden bir zaman damgasını hedef saat dilimine dönüştürün. |
| [convertToUtc](control-flow-expression-language-functions.md#convertToUtc) | Kaynak saat dilimindeki bir zaman damgasını Evrensel Saat Koordinasyonu'na (UTC) dönüştürün. |
| [günOfMonth](control-flow-expression-language-functions.md#dayOfMonth) | Ayın bileşeninin gününü bir zaman damgasından döndürün. |
| [Dayofweek](control-flow-expression-language-functions.md#dayOfWeek) | Hafta bileşeninin gününü bir zaman damgasından döndürün. |
| [Dayofyear](control-flow-expression-language-functions.md#dayOfYear) | Yıl bileşeninin gününü bir zaman damgasından döndürün. |
| [formatDateTime](control-flow-expression-language-functions.md#formatDateTime) | Tarihi bir zaman damgasından döndürün. |
| [getFutureTime](control-flow-expression-language-functions.md#getFutureTime) | Geçerli zaman damgasını ve belirtilen zaman birimlerini döndürün. Ayrıca [bkz.](control-flow-expression-language-functions.md#addToTime) |
| [getPastTime](control-flow-expression-language-functions.md#getPastTime) | Geçerli zaman damgasını eksi belirtilen zaman birimlerini döndürün. Ayrıca [bkz.](control-flow-expression-language-functions.md#subtractFromTime) |
| [başlangıçOfDay](control-flow-expression-language-functions.md#startOfDay) | Günün başlangıcını bir zaman damgası için döndürün. |
| [başlangıçOfSaat](control-flow-expression-language-functions.md#startOfHour) | Saat ini saat damgası için saatin başlangıcını iade edin. |
| [başlangıçOfMonth](control-flow-expression-language-functions.md#startOfMonth) | Zaman damgası için ayın başlangıcını iade edin. |
| [çıkarmaFromTime](control-flow-expression-language-functions.md#subtractFromTime) | Zaman damgasından birkaç zaman birimi çıkarın. Ayrıca [bakınız GetPastTime](control-flow-expression-language-functions.md#getPastTime). |
| [Ticks](control-flow-expression-language-functions.md#ticks) | Belirtilen `ticks` bir zaman damgası için özellik değerini döndürün. |
| [utcŞimdi](control-flow-expression-language-functions.md#utcNow) | Geçerli zaman damgasını dize olarak döndürün. |
## <a name="function-reference"></a>Fonksiyon başvurusu
Bu bölümde, tüm kullanılabilir işlevleri alfabetik sıraya göre listelenmektedir.
<a name="add"></a>
### <a name="add"></a>add
İki sayı ekleyerek sonucu döndürün.
```
add(<summand_1>, <summand_2>)
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*summand_1*>, <*summand_2*> | Evet | Sonda, Float veya karışık | Eklenecek sayılar |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | -----| ----------- |
| <*sonuç toplamı*> | Sonda veya Float | Belirtilen sayıları eklemesonucu |
||||
*Örnek*
Bu örnekte belirtilen sayılar ekleniyor:
```
add(1, 1.5)
```
Ve bu sonucu döndürür:`2.5`
<a name="addDays"></a>
### <a name="adddays"></a>Adddays
Zaman damgasına birkaç gün ekleyin.
```
addDays('<timestamp>', <days>, '<format>'?)
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Zaman damgası*> | Evet | Dize | Zaman damgasını içeren dize |
| <*Gün*> | Evet | Tamsayı | Eklenecek olumlu veya negatif gün sayısı |
| <*Biçim*> | Hayır | Dize | Ya tek bir [biçim belirticisi](https://docs.microsoft.com/dotnet/standard/base-types/standard-date-and-time-format-strings) ya da özel bir [biçim deseni.](https://docs.microsoft.com/dotnet/standard/base-types/custom-date-and-time-format-strings) Zaman damgası için varsayılan [biçim, ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) ile uyumlu ve saat dilimi bilgilerini koruyan ["o"](https://docs.microsoft.com/dotnet/standard/base-types/standard-date-and-time-format-strings) (yyyy-MM-ddTHH:mm:ss:fffffffK) biçimidir. |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*güncelleştirilmiş zaman damgası*> | Dize | Zaman damgası artı belirtilen gün sayısı |
||||
*Örnek 1*
Bu örnek, belirtilen zaman damgasına 10 gün ekler:
```
addDays('2018-03-15T13:00:00Z', 10)
```
Ve bu sonucu döndürür:`"2018-03-25T00:00:0000000Z"`
*Örnek 2*
Bu örnek, belirtilen zaman damgasından beş gün çıkarır:
```
addDays('2018-03-15T00:00:00Z', -5)
```
Ve bu sonucu döndürür:`"2018-03-10T00:00:0000000Z"`
<a name="addHours"></a>
### <a name="addhours"></a>Addhours
Zaman damgasına birkaç saat ekleyin.
```
addHours('<timestamp>', <hours>, '<format>'?)
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Zaman damgası*> | Evet | Dize | Zaman damgasını içeren dize |
| <*Saat*> | Evet | Tamsayı | Eklenecek pozitif veya negatif saat sayısı |
| <*Biçim*> | Hayır | Dize | Ya tek bir [biçim belirticisi](https://docs.microsoft.com/dotnet/standard/base-types/standard-date-and-time-format-strings) ya da özel bir [biçim deseni.](https://docs.microsoft.com/dotnet/standard/base-types/custom-date-and-time-format-strings) Zaman damgası için varsayılan [biçim, ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) ile uyumlu ve saat dilimi bilgilerini koruyan ["o"](https://docs.microsoft.com/dotnet/standard/base-types/standard-date-and-time-format-strings) (yyyy-MM-ddTHH:mm:ss:fffffffK) biçimidir. |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*güncelleştirilmiş zaman damgası*> | Dize | Zaman damgası artı belirtilen saat sayısı |
||||
*Örnek 1*
Bu örnek, belirtilen zaman damgasına 10 saat ekler:
```
addHours('2018-03-15T00:00:00Z', 10)
```
Ve bu sonucu döndürür:`"2018-03-15T10:00:0000000Z"`
*Örnek 2*
Bu örnek, belirtilen zaman damgasından beş saat çıkarır:
```
addHours('2018-03-15T15:00:00Z', -5)
```
Ve bu sonucu döndürür:`"2018-03-15T10:00:0000000Z"`
<a name="addMinutes"></a>
### <a name="addminutes"></a>Addminutes
Zaman damgasına birkaç dakika ekleyin.
```
addMinutes('<timestamp>', <minutes>, '<format>'?)
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Zaman damgası*> | Evet | Dize | Zaman damgasını içeren dize |
| <*Dakika*> | Evet | Tamsayı | Eklenecek dakikaların pozitif veya negatif sayısı |
| <*Biçim*> | Hayır | Dize | Ya tek bir [biçim belirticisi](https://docs.microsoft.com/dotnet/standard/base-types/standard-date-and-time-format-strings) ya da özel bir [biçim deseni.](https://docs.microsoft.com/dotnet/standard/base-types/custom-date-and-time-format-strings) Zaman damgası için varsayılan [biçim, ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) ile uyumlu ve saat dilimi bilgilerini koruyan ["o"](https://docs.microsoft.com/dotnet/standard/base-types/standard-date-and-time-format-strings) (yyyy-MM-ddTHH:mm:ss:fffffffK) biçimidir. |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*güncelleştirilmiş zaman damgası*> | Dize | Zaman damgası artı belirtilen dakika sayısı |
||||
*Örnek 1*
Bu örnek, belirtilen zaman damgasına 10 dakika ekler:
```
addMinutes('2018-03-15T00:10:00Z', 10)
```
Ve bu sonucu döndürür:`"2018-03-15T00:20:00.0000000Z"`
*Örnek 2*
Bu örnek, belirtilen zaman damgasından beş dakika çıkarır:
```
addMinutes('2018-03-15T00:20:00Z', -5)
```
Ve bu sonucu döndürür:`"2018-03-15T00:15:00.0000000Z"`
<a name="addSeconds"></a>
### <a name="addseconds"></a>Addseconds
Zaman damgasına birkaç saniye ekleyin.
```
addSeconds('<timestamp>', <seconds>, '<format>'?)
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Zaman damgası*> | Evet | Dize | Zaman damgasını içeren dize |
| <*Saniye*> | Evet | Tamsayı | Eklenecek pozitif veya negatif saniye sayısı |
| <*Biçim*> | Hayır | Dize | Ya tek bir [biçim belirticisi](https://docs.microsoft.com/dotnet/standard/base-types/standard-date-and-time-format-strings) ya da özel bir [biçim deseni.](https://docs.microsoft.com/dotnet/standard/base-types/custom-date-and-time-format-strings) Zaman damgası için varsayılan [biçim, ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) ile uyumlu ve saat dilimi bilgilerini koruyan ["o"](https://docs.microsoft.com/dotnet/standard/base-types/standard-date-and-time-format-strings) (yyyy-MM-ddTHH:mm:ss:fffffffK) biçimidir. |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*güncelleştirilmiş zaman damgası*> | Dize | Zaman damgası artı belirtilen saniye sayısı |
||||
*Örnek 1*
Bu örnek, belirtilen zaman damgasına 10 saniye ekler:
```
addSeconds('2018-03-15T00:00:00Z', 10)
```
Ve bu sonucu döndürür:`"2018-03-15T00:00:10.0000000Z"`
*Örnek 2*
Bu örnek, belirtilen zaman damgasına beş saniye çıkarır:
```
addSeconds('2018-03-15T00:00:30Z', -5)
```
Ve bu sonucu döndürür:`"2018-03-15T00:00:25.0000000Z"`
<a name="addToTime"></a>
### <a name="addtotime"></a>addToTime
Zaman damgasına birkaç zaman birimi ekleyin.
Ayrıca [bakınız FutureTime()](#getFutureTime).
```
addToTime('<timestamp>', <interval>, '<timeUnit>', '<format>'?)
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Zaman damgası*> | Evet | Dize | Zaman damgasını içeren dize |
| <*Aralığı*> | Evet | Tamsayı | Eklenecek belirtilen zaman birimlerinin sayısı |
| <*zaman Birimi*> | Evet | Dize | *Aralıklı*olarak kullanılacak zaman birimi : "İkinci", "Dakika", "Saat", "Gün", "Hafta", "Ay", "Yıl" |
| <*Biçim*> | Hayır | Dize | Ya tek bir [biçim belirticisi](https://docs.microsoft.com/dotnet/standard/base-types/standard-date-and-time-format-strings) ya da özel bir [biçim deseni.](https://docs.microsoft.com/dotnet/standard/base-types/custom-date-and-time-format-strings) Zaman damgası için varsayılan [biçim, ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) ile uyumlu ve saat dilimi bilgilerini koruyan ["o"](https://docs.microsoft.com/dotnet/standard/base-types/standard-date-and-time-format-strings) (yyyy-MM-ddTHH:mm:ss:fffffffK) biçimidir. |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*güncelleştirilmiş zaman damgası*> | Dize | Zaman damgası artı belirtilen zaman birimi sayısı |
||||
*Örnek 1*
Bu örnek, belirtilen zaman damgasına bir gün ekler:
```
addToTime('2018-01-01T00:00:00Z', 1, 'Day')
```
Ve bu sonucu döndürür:`"2018-01-02T00:00:00.0000000Z"`
*Örnek 2*
Bu örnek, belirtilen zaman damgasına bir gün ekler:
```
addToTime('2018-01-01T00:00:00Z', 1, 'Day', 'D')
```
Ve isteğe bağlı "D" biçimini kullanarak sonucu döndürür:`"Tuesday, January 2, 2018"`
<a name="and"></a>
### <a name="and"></a>ve
Tüm ifadelerin doğru olup olmadığını denetleyin.
Tüm ifadeler doğru olduğunda doğru döndürün veya en az bir ifade yanlış olduğunda yanlış döndürün.
```
and(<expression1>, <expression2>, ...)
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*ifade1*>, <*ifade2*>, ... | Evet | Boole | Denetlenen ifadeler |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | -----| ----------- |
| true veya false | Boole | Tüm ifadeler doğru olduğunda doğru döndürün. En az bir ifade yanlış olduğunda yanlış döndürün. |
||||
*Örnek 1*
Bu örnekler, belirtilen Boolean değerlerinin hepsinin doğru olup olmadığını denetler:
```
and(true, true)
and(false, true)
and(false, false)
```
Ve bu sonuçları döndürür:
* İlk örnek: Her iki ifade `true`de doğrudur, bu nedenle döndürür.
* İkinci örnek: Bir ifade yanlıştır, bu nedenle döndürür. `false`
* Üçüncü örnek: Her iki ifade `false`de yanlış, bu nedenle döndürür.
*Örnek 2*
Bu örnekler, belirtilen ifadelerin hepsinin doğru olup olmadığını denetler:
```
and(equals(1, 1), equals(2, 2))
and(equals(1, 1), equals(1, 2))
and(equals(1, 2), equals(1, 3))
```
Ve bu sonuçları döndürür:
* İlk örnek: Her iki ifade `true`de doğrudur, bu nedenle döndürür.
* İkinci örnek: Bir ifade yanlıştır, bu nedenle döndürür. `false`
* Üçüncü örnek: Her iki ifade `false`de yanlış, bu nedenle döndürür.
<a name="array"></a>
### <a name="array"></a>array
Belirli bir girişten bir dizi döndürün.
Birden çok giriş için [createArray()](#createArray)bakın.
```
array('<value>')
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Değer*> | Evet | Dize | Dizi oluşturmak için dize |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| [<*değer*>] | Dizi | Tek belirtilen girişi içeren bir dizi |
||||
*Örnek*
Bu örnekte "merhaba" dizesinden bir dizi oluşturulur:
```
array('hello')
```
Ve bu sonucu döndürür:`["hello"]`
<a name="base64"></a>
### <a name="base64"></a>base64
Bir dize için base64 kodlanmış sürümü döndürün.
```
base64('<value>')
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Değer*> | Evet | Dize | Giriş dizesi |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*base64-string*> | Dize | Giriş dizesi için base64 kodlanmış sürüm |
||||
*Örnek*
Bu örnek, "merhaba" dizesini base64 kodlanmış bir dize dönüştürür:
```
base64('hello')
```
Ve bu sonucu döndürür:`"aGVsbG8="`
<a name="base64ToBinary"></a>
### <a name="base64tobinary"></a>base64ToBinary
Base64 kodlanmış bir dize için ikili sürümü döndürün.
```
base64ToBinary('<value>')
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Değer*> | Evet | Dize | Dönüştürmek için base64 kodlanmış dize |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*ikili-for-base64-string*> | Dize | Base64 kodlanmış dize için ikili sürüm |
||||
*Örnek*
Bu örnek, "aGVsbG8=" base64 kodlanmış dizeyi ikili bir dize dönüştürür:
```
base64ToBinary('aGVsbG8=')
```
Ve bu sonucu döndürür:
`"0110000101000111010101100111001101100010010001110011100000111101"`
<a name="base64ToString"></a>
### <a name="base64tostring"></a>base64ToString
Base64 kodlanmış bir dize için dize sürümünü döndürün ve base64 dizesini etkili bir şekilde çözün.
[Base64() decode](#decodeBase64)yerine bu işlevi kullanın.
Her iki fonksiyon da `base64ToString()` aynı şekilde çalışsa da tercih edilir.
```
base64ToString('<value>')
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Değer*> | Evet | Dize | Kod çözmek için base64 kodlanmış dize |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*deşifre-base64-string*> | Dize | Base64 kodlanmış bir dize için dize sürümü |
||||
*Örnek*
Bu örnek, "aGVsbG8=" base64 kodlanmış dizeyi sadece bir dize dönüştürür:
```
base64ToString('aGVsbG8=')
```
Ve bu sonucu döndürür:`"hello"`
<a name="binary"></a>
### <a name="binary"></a>ikili
Bir dize için ikili sürümü döndürün.
```
binary('<value>')
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Değer*> | Evet | Dize | Dönüştürülecek dize |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*ikili-giriş-değer*> | Dize | Belirtilen dize için ikili sürüm |
||||
*Örnek*
Bu örnek, "merhaba" dizesini ikili dizeye dönüştürür:
```
binary('hello')
```
Ve bu sonucu döndürür:
`"0110100001100101011011000110110001101111"`
<a name="bool"></a>
### <a name="bool"></a>bool
Bir değer için Boolean sürümünü döndürün.
```
bool(<value>)
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Değer*> | Evet | Herhangi biri | Dönüştürülecek değer |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| true veya false | Boole | Belirtilen değer için Boolean sürümü |
||||
*Örnek*
Bu örnekler, belirtilen değerleri Boolean değerlerine dönüştürür:
```
bool(1)
bool(0)
```
Ve bu sonuçları döndürür:
* İlk örnek:`true`
* İkinci örnek:`false`
<a name="coalesce"></a>
### <a name="coalesce"></a>Coalesce
Bir veya daha fazla parametreden ilk null olmayan değeri döndürün.
Boş dizeleri, boş diziler ve boş nesneler null değildir.
```
coalesce(<object_1>, <object_2>, ...)
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*object_1*>, <*object_2*>, ... | Evet | Herhangi, türleri karıştırabilirsiniz | Null için kontrol etmek için bir veya daha fazla öğe |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*ilk-null-öğe*> | Herhangi biri | Null olmayan ilk öğe veya değer. Tüm parametreler null ise, bu işlev null döndürür. |
||||
*Örnek*
Bu örnekler, belirtilen değerlerden ilk null olmayan değeri veya tüm değerler null olduğunda null döndürür:
```
coalesce(null, true, false)
coalesce(null, 'hello', 'world')
coalesce(null, null, null)
```
Ve bu sonuçları döndürür:
* İlk örnek:`true`
* İkinci örnek:`"hello"`
* Üçüncü örnek:`null`
<a name="concat"></a>
### <a name="concat"></a>concat
İki veya daha fazla dizebirleştirin ve birleştirilmiş dizeyi döndürün.
```
concat('<text1>', '<text2>', ...)
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*metin1*>, <*text2*>, ... | Evet | Dize | Birleştirmek için en az iki dize |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*metin1text2...*> | Dize | Birleştirilmiş giriş dizelerinden oluşturulan dize |
||||
*Örnek*
Bu örnek, "Merhaba" ve "Dünya" dizelerini birleştirir:
```
concat('Hello', 'World')
```
Ve bu sonucu döndürür:`"HelloWorld"`
<a name="contains"></a>
### <a name="contains"></a>içerir
Koleksiyonun belirli bir öğesi olup olmadığını denetleyin.
Öğe bulunduğunda doğru döndürün veya bulunmadığında yanlış döndürün.
Bu fonksiyon büyük/küçük harf duyarlıdır.
```
contains('<collection>', '<value>')
contains([<collection>], '<value>')
```
Özellikle, bu işlev bu toplama türleri üzerinde çalışır:
* Bir *alt dize* bulmak için bir *dize*
* Bir *değeri* bulmak için bir *dizi*
* Bir *anahtar* bulmak için bir *sözlük*
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Koleksiyon*> | Evet | Dize, Dizi veya Sözlük | Denetlenen koleksiyon |
| <*Değer*> | Evet | String, Array veya Sözlük, sırasıyla | Bulunacak öğe |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| true veya false | Boole | Öğe bulunduğunda doğru döndürün. Bulunduğunda yanlış döndürün. |
||||
*Örnek 1*
Bu örnek, "dünya" alt dizesi için "merhaba dünya" dizesini denetler ve doğru döndürür:
```
contains('hello world', 'world')
```
*Örnek 2*
Bu örnek, "evren" alt dizesini "merhaba dünya" dizesini denetler ve yanlış döndürür:
```
contains('hello world', 'universe')
```
<a name="convertFromUtc"></a>
### <a name="convertfromutc"></a>convertFromUtc
Evrensel Zaman Eşgüdümlü'nden (UTC) bir zaman damgasını hedef saat dilimine dönüştürün.
```
convertFromUtc('<timestamp>', '<destinationTimeZone>', '<format>'?)
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Zaman damgası*> | Evet | Dize | Zaman damgasını içeren dize |
| <*hedefTimeZone*> | Evet | Dize | Hedef saat diliminin adı. Saat dilimi adları için [Microsoft Saat Dilimi Dizin Değerleri'ne](https://support.microsoft.com/help/973627/microsoft-time-zone-index-values)bakın, ancak saat dilimi adından herhangi bir noktalama işaretini kaldırmanız gerekebilir. |
| <*Biçim*> | Hayır | Dize | Ya tek bir [biçim belirticisi](https://docs.microsoft.com/dotnet/standard/base-types/standard-date-and-time-format-strings) ya da özel bir [biçim deseni.](https://docs.microsoft.com/dotnet/standard/base-types/custom-date-and-time-format-strings) Zaman damgası için varsayılan [biçim, ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) ile uyumlu ve saat dilimi bilgilerini koruyan ["o"](https://docs.microsoft.com/dotnet/standard/base-types/standard-date-and-time-format-strings) (yyyy-MM-ddTHH:mm:ss:fffffffK) biçimidir. |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*dönüştürülmüş zaman damgası*> | Dize | Hedef saat dilimine dönüştürülen zaman damgası |
||||
*Örnek 1*
Bu örnek, bir zaman damgasını belirtilen saat dilimine dönüştürür:
```
convertFromUtc('2018-01-01T08:00:00.0000000Z', 'Pacific Standard Time')
```
Ve bu sonucu döndürür:`"2018-01-01T00:00:00.0000000"`
*Örnek 2*
Bu örnek, bir zaman damgasını belirtilen saat dilimine ve biçime dönüştürür:
```
convertFromUtc('2018-01-01T08:00:00.0000000Z', 'Pacific Standard Time', 'D')
```
Ve bu sonucu döndürür:`"Monday, January 1, 2018"`
<a name="convertTimeZone"></a>
### <a name="converttimezone"></a>dönüştürmeTimeZone
Kaynak saat diliminden bir zaman damgasını hedef saat dilimine dönüştürün.
```
convertTimeZone('<timestamp>', '<sourceTimeZone>', '<destinationTimeZone>', '<format>'?)
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Zaman damgası*> | Evet | Dize | Zaman damgasını içeren dize |
| <*Sourcetimezone*> | Evet | Dize | Kaynak saat diliminin adı. Saat dilimi adları için [Microsoft Saat Dilimi Dizin Değerleri'ne](https://support.microsoft.com/help/973627/microsoft-time-zone-index-values)bakın, ancak saat dilimi adından herhangi bir noktalama işaretini kaldırmanız gerekebilir. |
| <*hedefTimeZone*> | Evet | Dize | Hedef saat diliminin adı. Saat dilimi adları için [Microsoft Saat Dilimi Dizin Değerleri'ne](https://support.microsoft.com/help/973627/microsoft-time-zone-index-values)bakın, ancak saat dilimi adından herhangi bir noktalama işaretini kaldırmanız gerekebilir. |
| <*Biçim*> | Hayır | Dize | Ya tek bir [biçim belirticisi](https://docs.microsoft.com/dotnet/standard/base-types/standard-date-and-time-format-strings) ya da özel bir [biçim deseni.](https://docs.microsoft.com/dotnet/standard/base-types/custom-date-and-time-format-strings) Zaman damgası için varsayılan [biçim, ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) ile uyumlu ve saat dilimi bilgilerini koruyan ["o"](https://docs.microsoft.com/dotnet/standard/base-types/standard-date-and-time-format-strings) (yyyy-MM-ddTHH:mm:ss:fffffffK) biçimidir. |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*dönüştürülmüş zaman damgası*> | Dize | Hedef saat dilimine dönüştürülen zaman damgası |
||||
*Örnek 1*
Bu örnek, kaynak saat dilimini hedef saat dilimine dönüştürür:
```
convertTimeZone('2018-01-01T08:00:00.0000000Z', 'UTC', 'Pacific Standard Time')
```
Ve bu sonucu döndürür:`"2018-01-01T00:00:00.0000000"`
*Örnek 2*
Bu örnek, bir saat dilimini belirtilen saat dilimine ve biçime dönüştürür:
```
convertTimeZone('2018-01-01T80:00:00.0000000Z', 'UTC', 'Pacific Standard Time', 'D')
```
Ve bu sonucu döndürür:`"Monday, January 1, 2018"`
<a name="convertToUtc"></a>
### <a name="converttoutc"></a>convertToUtc
Kaynak saat dilimindeki bir zaman damgasını Evrensel Saat Koordinasyonu'na (UTC) dönüştürün.
```
convertToUtc('<timestamp>', '<sourceTimeZone>', '<format>'?)
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Zaman damgası*> | Evet | Dize | Zaman damgasını içeren dize |
| <*Sourcetimezone*> | Evet | Dize | Kaynak saat diliminin adı. Saat dilimi adları için [Microsoft Saat Dilimi Dizin Değerleri'ne](https://support.microsoft.com/help/973627/microsoft-time-zone-index-values)bakın, ancak saat dilimi adından herhangi bir noktalama işaretini kaldırmanız gerekebilir. |
| <*Biçim*> | Hayır | Dize | Ya tek bir [biçim belirticisi](https://docs.microsoft.com/dotnet/standard/base-types/standard-date-and-time-format-strings) ya da özel bir [biçim deseni.](https://docs.microsoft.com/dotnet/standard/base-types/custom-date-and-time-format-strings) Zaman damgası için varsayılan [biçim, ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) ile uyumlu ve saat dilimi bilgilerini koruyan ["o"](https://docs.microsoft.com/dotnet/standard/base-types/standard-date-and-time-format-strings) (yyyy-MM-ddTHH:mm:ss:fffffffK) biçimidir. |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*dönüştürülmüş zaman damgası*> | Dize | ZAMAN damgası UTC'ye dönüştürüldü |
||||
*Örnek 1*
Bu örnek, bir zaman damgasını UTC'ye dönüştürür:
```
convertToUtc('01/01/2018 00:00:00', 'Pacific Standard Time')
```
Ve bu sonucu döndürür:`"2018-01-01T08:00:00.0000000Z"`
*Örnek 2*
Bu örnek, bir zaman damgasını UTC'ye dönüştürür:
```
convertToUtc('01/01/2018 00:00:00', 'Pacific Standard Time', 'D')
```
Ve bu sonucu döndürür:`"Monday, January 1, 2018"`
<a name="createArray"></a>
### <a name="createarray"></a>createArray
Birden çok girişten bir dizi döndürün.
Tek giriş dizileri için [dizi()](#array)bakın.
```
createArray('<object1>', '<object2>', ...)
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*object1*>, <*object2*>, ... | Evet | Herhangi, ama karışık değil | Diziyi oluşturmak için en az iki öğe |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| [<*object1*>, <*object2*>, ...] | Dizi | Tüm giriş öğelerinden oluşturulan dizi |
||||
*Örnek*
Bu örnek, bu girişlerden bir dizi oluşturur:
```
createArray('h', 'e', 'l', 'l', 'o')
```
Ve bu sonucu döndürür:`["h", "e", "l", "l", "o"]`
<a name="dataUri"></a>
### <a name="datauri"></a>dataUri
Bir dize için veri tekdüzen kaynak tanımlayıcısı (URI) döndürün.
```
dataUri('<value>')
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Değer*> | Evet | Dize | Dönüştürülecek dize |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*veri-uri*> | Dize | Giriş dizesi için veri URI |
||||
*Örnek*
Bu örnek, "merhaba" dizesi için bir veri URI oluşturur:
```
dataUri('hello')
```
Ve bu sonucu döndürür:`"data:text/plain;charset=utf-8;base64,aGVsbG8="`
<a name="dataUriToBinary"></a>
### <a name="datauritobinary"></a>dataUritoBinary
Veri üniforması kaynak tanımlayıcısı (URI) için ikili sürümü döndürün.
Bu işlevi [decodeDataUri()](#decodeDataUri)yerine kullanın.
Her iki fonksiyon da `dataUriBinary()` aynı şekilde çalışsa da tercih edilir.
```
dataUriToBinary('<value>')
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Değer*> | Evet | Dize | Dönüştürmek için veri URI |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*ikili-for-data-uri*> | Dize | Veri URI için ikili sürümü |
||||
*Örnek*
Bu örnek, bu veri URI için ikili bir sürüm oluşturur:
```
dataUriToBinary('data:text/plain;charset=utf-8;base64,aGVsbG8=')
```
Ve bu sonucu döndürür:
`"01100100011000010111010001100001001110100111010001100101011110000111010000101111011100000
1101100011000010110100101101110001110110110001101101000011000010111001001110011011001010111
0100001111010111010101110100011001100010110100111000001110110110001001100001011100110110010
10011011000110100001011000110000101000111010101100111001101100010010001110011100000111101"`
<a name="dataUriToString"></a>
### <a name="datauritostring"></a>dataUritostring
Veri tekdüzen kaynak tanımlayıcısı (URI) için dize sürümünü döndürün.
```
dataUriToString('<value>')
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Değer*> | Evet | Dize | Dönüştürmek için veri URI |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*string-for-data-uri*> | Dize | Veri URI için dize sürümü |
||||
*Örnek*
Bu örnek, bu veri URI için bir dize oluşturur:
```
dataUriToString('data:text/plain;charset=utf-8;base64,aGVsbG8=')
```
Ve bu sonucu döndürür:`"hello"`
<a name="dayOfMonth"></a>
### <a name="dayofmonth"></a>günOfMonth
Ayın gününü bir zaman damgasından döndürün.
```
dayOfMonth('<timestamp>')
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Zaman damgası*> | Evet | Dize | Zaman damgasını içeren dize |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*gün-ay*> | Tamsayı | Belirtilen zaman damgasından ayın günü |
||||
*Örnek*
Bu örnek, bu zaman damgasından ayın gününün numarasını döndürür:
```
dayOfMonth('2018-03-15T13:27:36Z')
```
Ve bu sonucu döndürür:`15`
<a name="dayOfWeek"></a>
### <a name="dayofweek"></a>Dayofweek
Haftanın gününü bir zaman damgasından döndürün.
```
dayOfWeek('<timestamp>')
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Zaman damgası*> | Evet | Dize | Zaman damgasını içeren dize |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*haftanın günü*> | Tamsayı | Pazar 0, Pazartesi 1 ve benzeri belirtilen zaman damgası haftanın günü |
||||
*Örnek*
Bu örnek, bu zaman damgasından haftanın gününün numarasını döndürür:
```
dayOfWeek('2018-03-15T13:27:36Z')
```
Ve bu sonucu döndürür:`3`
<a name="dayOfYear"></a>
### <a name="dayofyear"></a>Dayofyear
Yılın gününü zaman damgasından döndürün.
```
dayOfYear('<timestamp>')
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Zaman damgası*> | Evet | Dize | Zaman damgasını içeren dize |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*yıl-of-yıl*> | Tamsayı | Belirtilen zaman damgasından yılın günü |
||||
*Örnek*
Bu örnek, bu zaman damgasından yılın gün sayısını döndürür:
```
dayOfYear('2018-03-15T13:27:36Z')
```
Ve bu sonucu döndürür:`74`
<a name="decodeBase64"></a>
### <a name="decodebase64"></a>decodeBase64
Base64 kodlanmış bir dize için dize sürümünü döndürün ve base64 dizesini etkili bir şekilde çözün.
Yerine [base64ToString()](#base64ToString) kullanmayı `decodeBase64()`düşünün.
Her iki fonksiyon da `base64ToString()` aynı şekilde çalışsa da tercih edilir.
```
decodeBase64('<value>')
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Değer*> | Evet | Dize | Kod çözmek için base64 kodlanmış dize |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*deşifre-base64-string*> | Dize | Base64 kodlanmış bir dize için dize sürümü |
||||
*Örnek*
Bu örnek, base64 kodlanmış bir dize için bir dize oluşturur:
```
decodeBase64('aGVsbG8=')
```
Ve bu sonucu döndürür:`"hello"`
<a name="decodeDataUri"></a>
### <a name="decodedatauri"></a>decodeDataUri
Veri üniforması kaynak tanımlayıcısı (URI) için ikili sürümü döndürün.
[DataUriToBinary()](#dataUriToBinary)yerine kullanmayı `decodeDataUri()`düşünün.
Her iki fonksiyon da `dataUriToBinary()` aynı şekilde çalışsa da tercih edilir.
```
decodeDataUri('<value>')
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Değer*> | Evet | Dize | Çözmeiçin veri URI dizesi |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*ikili-for-data-uri*> | Dize | Veri URI dizesi için ikili sürüm |
||||
*Örnek*
Bu örnek, bu veri URI için ikili sürümünü döndürür:
```
decodeDataUri('data:text/plain;charset=utf-8;base64,aGVsbG8=')
```
Ve bu sonucu döndürür:
`"01100100011000010111010001100001001110100111010001100101011110000111010000101111011100000
1101100011000010110100101101110001110110110001101101000011000010111001001110011011001010111
0100001111010111010101110100011001100010110100111000001110110110001001100001011100110110010
10011011000110100001011000110000101000111010101100111001101100010010001110011100000111101"`
<a name="decodeUriComponent"></a>
### <a name="decodeuricomponent"></a>decodeUriComponent
Kaçış karakterlerinin yerine deşifre edilmiş sürümlerle bir dize döndürün.
```
decodeUriComponent('<value>')
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Değer*> | Evet | Dize | Çözmek için kaçış karakterleri ile dize |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*deşifre-uri*> | Dize | Kodlanmış kaçış karakterleri ile güncelleştirilmiş dize |
||||
*Örnek*
Bu örnek, bu dizedeki kaçış karakterlerinin yerine deşifre edilmiş sürümlerle değiştirilir:
```
decodeUriComponent('http%3A%2F%2Fcontoso.com')
```
Ve bu sonucu döndürür:`"https://contoso.com"`
<a name="div"></a>
### <a name="div"></a>div
İki sayıyı bölerek gelen sonda sonucunu döndürün.
Kalan sonucu almak için [mod()](#mod)bakın.
```
div(<dividend>, <divisor>)
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Temettü*> | Evet | Sonda veya Float | *Bölene* bölünecek sayı |
| <*Bölen*> | Evet | Sonda veya Float | *Temettü*bölen ancak 0 olamaz sayı |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*quotient-sonuç*> | Tamsayı | İlk sayıyı ikinci sayıya bölmenin sonucu |
||||
*Örnek*
Her iki örnek de birinci sayıyı ikinci sayıya böler:
```
div(10, 5)
div(11, 5)
```
Ve bu sonucu iade edin:`2`
<a name="encodeUriComponent"></a>
### <a name="encodeuricomponent"></a>kodlamaUriComponent
URL güvenli olmayan karakterleri kaçış karakterleriyle değiştirerek, tek düzen kaynak tanımlayıcısı (URI) kodlanmış sürümü bir dize için döndürün.
[uriComponent()](#uriComponent)yerine kullanmayı `encodeUriComponent()`düşünün.
Her iki fonksiyon da `uriComponent()` aynı şekilde çalışsa da tercih edilir.
```
encodeUriComponent('<value>')
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Değer*> | Evet | Dize | URI kodlu biçime dönüştürülecek dize |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*kodlanmış-uri*> | Dize | Kaçış karakterleri ile URI kodlanmış dize |
||||
*Örnek*
Bu örnek, bu dize için URI kodlanmış bir sürüm oluşturur:
```
encodeUriComponent('https://contoso.com')
```
Ve bu sonucu döndürür:`"http%3A%2F%2Fcontoso.com"`
<a name="empty"></a>
### <a name="empty"></a>empty
Koleksiyonun boş olup olmadığını kontrol edin.
Koleksiyon boşolduğunda doğru döndürün veya boş değilken yanlış döndürün.
```
empty('<collection>')
empty([<collection>])
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Koleksiyon*> | Evet | Dize, Dizi veya Nesne | Denetlenen koleksiyon |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| true veya false | Boole | Koleksiyon boşolduğunda doğru döndürün. Boş değilken yanlış döndürün. |
||||
*Örnek*
Bu örnekler, belirtilen koleksiyonların boş olup olmadığını denetler:
```
empty('')
empty('abc')
```
Ve bu sonuçları döndürür:
* İlk örnek: Boş bir dize `true`geçirir, böylece işlev döndürür.
* İkinci örnek: "abc" dizesini geçer, böylece işlev döndürür. `false`
<a name="endswith"></a>
### <a name="endswith"></a>endsWith
Bir dize belirli bir alt dize ile bitene denetleyin.
Alt dize bulunduğunda doğru döndürün veya bulunmadığında false döndürün.
Bu işlev büyük/küçük harf duyarlı değildir.
```
endsWith('<text>', '<searchText>')
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Metin*> | Evet | Dize | Denetlenen dize |
| <*searchText*> | Evet | Dize | Bulmak için bitiş alt dize |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| true veya false | Boole | Bitiş alt dizesi bulunduğunda doğru döndürün. Bulunduğunda yanlış döndürün. |
||||
*Örnek 1*
Bu örnek, "merhaba dünya" dizesinin "dünya" dizesiyle bitip bitmediğini denetler:
```
endsWith('hello world', 'world')
```
Ve bu sonucu döndürür:`true`
*Örnek 2*
Bu örnek, "merhaba dünya" dizesinin "evren" dizesiyle bitip bitmediğini denetler:
```
endsWith('hello world', 'universe')
```
Ve bu sonucu döndürür:`false`
<a name="equals"></a>
### <a name="equals"></a>equals
Her iki değerin, ifadenin veya nesnenin eşdeğer olup olmadığını denetleyin.
Her ikisi de eşdeğer olduğunda doğru döndürün veya eşdeğer olmadıklarında yanlış döndürün.
```
equals('<object1>', '<object2>')
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*object1*>, <*nesne2*> | Evet | Çeşitli | Karşılaştırmak için değerler, ifadeler veya nesneler |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| true veya false | Boole | Her ikisi de eşdeğer olduğunda doğru döndürün. Eşdeğer olmadığında false döndürün. |
||||
*Örnek*
Bu örnekler, belirtilen girişlerin eşdeğer olup olmadığını denetler.
```
equals(true, 1)
equals('abc', 'abcd')
```
Ve bu sonuçları döndürür:
* İlk örnek: Her iki değer de `true`eşdeğerdir, bu nedenle işlev döndürür.
* İkinci örnek: Her iki değer de eşdeğer `false`değildir, bu nedenle işlev döndürür.
<a name="first"></a>
### <a name="first"></a>Ilk
Bir dize veya diziden ilk öğeyi döndürün.
```
first('<collection>')
first([<collection>])
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Koleksiyon*> | Evet | Dize veya Dizi | İlk öğeyi bulabileceğiniz koleksiyon |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*ilk toplama öğesi*> | Herhangi biri | Koleksiyondaki ilk öğe |
||||
*Örnek*
Bu örnekler, bu koleksiyonlarda ilk öğeyi bulabilirsiniz:
```
first('hello')
first(createArray(0, 1, 2))
```
Ve bu sonuçları iade edin:
* İlk örnek:`"h"`
* İkinci örnek:`0`
<a name="float"></a>
### <a name="float"></a>float
Kayan nokta sayısı için dize sürümünü gerçek kayan nokta sayısına dönüştürün.
```
float('<value>')
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Değer*> | Evet | Dize | Dönüştürmek için geçerli bir kayan nokta numarası olan dize |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*float değeri*> | Kayan | Belirtilen dize için kayan nokta numarası |
||||
*Örnek*
Bu örnek, bu kayan nokta numarası için bir dize sürümü oluşturur:
```
float('10.333')
```
Ve bu sonucu döndürür:`10.333`
<a name="formatDateTime"></a>
### <a name="formatdatetime"></a>formatDateTime
Belirtilen biçimde bir zaman damgası döndürün.
```
formatDateTime('<timestamp>', '<format>'?)
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Zaman damgası*> | Evet | Dize | Zaman damgasını içeren dize |
| <*Biçim*> | Hayır | Dize | Ya tek bir [biçim belirticisi](https://docs.microsoft.com/dotnet/standard/base-types/standard-date-and-time-format-strings) ya da özel bir [biçim deseni.](https://docs.microsoft.com/dotnet/standard/base-types/custom-date-and-time-format-strings) Zaman damgası için varsayılan [biçim, ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) ile uyumlu ve saat dilimi bilgilerini koruyan ["o"](https://docs.microsoft.com/dotnet/standard/base-types/standard-date-and-time-format-strings) (yyyy-MM-ddTHH:mm:ss:fffffffK) biçimidir. |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*reformatted-zaman damgası*> | Dize | Belirtilen biçimde güncelleştirilmiş zaman damgası |
||||
*Örnek*
Bu örnek, bir zaman damgasını belirtilen biçime dönüştürür:
```
formatDateTime('03/15/2018 12:00:00', 'yyyy-MM-ddTHH:mm:ss')
```
Ve bu sonucu döndürür:`"2018-03-15T12:00:00"`
<a name="getFutureTime"></a>
### <a name="getfuturetime"></a>getFutureTime
Geçerli zaman damgasını ve belirtilen zaman birimlerini döndürün.
```
getFutureTime(<interval>, <timeUnit>, <format>?)
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Aralığı*> | Evet | Tamsayı | Eklenecek belirtilen zaman birimlerinin sayısı |
| <*zaman Birimi*> | Evet | Dize | *Aralıklı*olarak kullanılacak zaman birimi : "İkinci", "Dakika", "Saat", "Gün", "Hafta", "Ay", "Yıl" |
| <*Biçim*> | Hayır | Dize | Ya tek bir [biçim belirticisi](https://docs.microsoft.com/dotnet/standard/base-types/standard-date-and-time-format-strings) ya da özel bir [biçim deseni.](https://docs.microsoft.com/dotnet/standard/base-types/custom-date-and-time-format-strings) Zaman damgası için varsayılan [biçim, ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) ile uyumlu ve saat dilimi bilgilerini koruyan ["o"](https://docs.microsoft.com/dotnet/standard/base-types/standard-date-and-time-format-strings) (yyyy-MM-ddTHH:mm:ss:fffffffK) biçimidir. |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*güncelleştirilmiş zaman damgası*> | Dize | Geçerli zaman damgası artı belirtilen zaman birimi sayısı |
||||
*Örnek 1*
Geçerli zaman damgasının "2018-03-01T00:00:00.000000Z" olduğunu varsayalım.
Bu örnek, bu zaman damgasına beş gün ekler:
```
getFutureTime(5, 'Day')
```
Ve bu sonucu döndürür:`"2018-03-06T00:00:00.0000000Z"`
*Örnek 2*
Geçerli zaman damgasının "2018-03-01T00:00:00.000000Z" olduğunu varsayalım.
Bu örnek beş gün ekler ve sonucu "D" biçimine dönüştürür:
```
getFutureTime(5, 'Day', 'D')
```
Ve bu sonucu döndürür:`"Tuesday, March 6, 2018"`
<a name="getPastTime"></a>
### <a name="getpasttime"></a>getPastTime
Geçerli zaman damgasını eksi belirtilen zaman birimlerini döndürün.
```
getPastTime(<interval>, <timeUnit>, <format>?)
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Aralığı*> | Evet | Tamsayı | Çıkarıiçin belirtilen zaman birimlerinin sayısı |
| <*zaman Birimi*> | Evet | Dize | *Aralıklı*olarak kullanılacak zaman birimi : "İkinci", "Dakika", "Saat", "Gün", "Hafta", "Ay", "Yıl" |
| <*Biçim*> | Hayır | Dize | Ya tek bir [biçim belirticisi](https://docs.microsoft.com/dotnet/standard/base-types/standard-date-and-time-format-strings) ya da özel bir [biçim deseni.](https://docs.microsoft.com/dotnet/standard/base-types/custom-date-and-time-format-strings) Zaman damgası için varsayılan [biçim, ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) ile uyumlu ve saat dilimi bilgilerini koruyan ["o"](https://docs.microsoft.com/dotnet/standard/base-types/standard-date-and-time-format-strings) (yyyy-MM-ddTHH:mm:ss:fffffffK) biçimidir. |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*güncelleştirilmiş zaman damgası*> | Dize | Geçerli zaman damgası eksi belirtilen zaman birimi sayısı |
||||
*Örnek 1*
Geçerli zaman damgasının "2018-02-01T00:00:00.000000Z" olduğunu varsayalım.
Bu örnek, o zaman damgasından beş gün çıkarır:
```
getPastTime(5, 'Day')
```
Ve bu sonucu döndürür:`"2018-01-27T00:00:00.0000000Z"`
*Örnek 2*
Geçerli zaman damgasının "2018-02-01T00:00:00.000000Z" olduğunu varsayalım.
Bu örnek beş gün çıkarır ve sonucu "D" biçimine dönüştürür:
```
getPastTime(5, 'Day', 'D')
```
Ve bu sonucu döndürür:`"Saturday, January 27, 2018"`
<a name="greater"></a>
### <a name="greater"></a>büyüktür
İlk değerin ikinci değerden büyük olup olmadığını denetleyin.
İlk değer daha fazla olduğunda doğru döndürün veya daha az olduğunda false döndürün.
```
greater(<value>, <compareTo>)
greater('<value>', '<compareTo>')
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Değer*> | Evet | Sonda, Float veya String | İkinci değerden büyük olup olmadığını kontrol etmek için ilk değer |
| <*compareTo*> | Evet | Sırasıyla, Insalı, Float veya String | Karşılaştırma değeri |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| true veya false | Boole | İlk değer ikinci değerden büyük olduğunda doğru döndürün. İlk değer ikinci değere eşit veya daha az olduğunda yanlış döndürün. |
||||
*Örnek*
Bu örnekler, ilk değerin ikinci değerden büyük olup olmadığını denetler:
```
greater(10, 5)
greater('apple', 'banana')
```
Ve bu sonuçları iade edin:
* İlk örnek:`true`
* İkinci örnek:`false`
<a name="greaterOrEquals"></a>
### <a name="greaterorequals"></a>greaterOrEquals
İlk değerin ikinci değerden büyük mü yoksa eşit mi olduğunu denetleyin.
İlk değer büyük veya eşit olduğunda doğru döndürün veya ilk değer daha az olduğunda false döndürün.
```
greaterOrEquals(<value>, <compareTo>)
greaterOrEquals('<value>', '<compareTo>')
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Değer*> | Evet | Sonda, Float veya String | İkinci değerden büyük mü yoksa eşit mi olup olmadığını kontrol etmek için ilk değer |
| <*compareTo*> | Evet | Sırasıyla, Insalı, Float veya String | Karşılaştırma değeri |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| true veya false | Boole | İlk değer ikinci değerden büyük veya eşit olduğunda doğru döndürün. İlk değer ikinci değerden küçük olduğunda false döndürün. |
||||
*Örnek*
Bu örnekler, ilk değerin ikinci değerden büyük mü yoksa eşit mi olduğunu denetler:
```
greaterOrEquals(5, 5)
greaterOrEquals('apple', 'banana')
```
Ve bu sonuçları iade edin:
* İlk örnek:`true`
* İkinci örnek:`false`
<a name="guid"></a>
### <a name="guid"></a>Guıd
"c2ecc88d-88c8-4096-912c-d6f2e2b138ce" gibi bir dize olarak küresel olarak benzersiz bir tanımlayıcı (GUID) oluşturun:
```
guid()
```
Ayrıca, tirelerle ayrılmış 32 basamak olan varsayılan biçim olan "D" dışında GUID için farklı bir biçim belirtebilirsiniz.
```
guid('<format>')
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Biçim*> | Hayır | Dize | Döndürülen GUID için tek bir [biçim belirtici.](https://msdn.microsoft.com/library/97af8hh4) Varsayılan olarak, biçim "D"dir, ancak "N", "D", "B", "P" veya "X" kullanabilirsiniz. |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*GUID değeri*> | Dize | Rasgele oluşturulan GUID |
||||
*Örnek*
Bu örnek, tirelerle ayrılmış ve parantez içinde ekolarak 32 basamak olarak aynı GUID'i oluşturur:
```
guid('P')
```
Ve bu sonucu döndürür:`"(c2ecc88d-88c8-4096-912c-d6f2e2b138ce)"`
<a name="if"></a>
### <a name="if"></a>if
Bir ifadenin doğru mu yanlış mı olduğunu kontrol edin.
Sonuca bağlı olarak, belirli bir değeri döndürün.
```
if(<expression>, <valueIfTrue>, <valueIfFalse>)
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Ifa -de*> | Evet | Boole | Denetlenen ifade |
| <*valueIfTrue*> | Evet | Herhangi biri | İfade doğru olduğunda döndürülecek değer |
| <*valueIfFalse*> | Evet | Herhangi biri | İfade yanlış olduğunda döndürülecek değer |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*belirtilen-getiri-değer*> | Herhangi biri | İfadenin doğru mu yanlış mı olduğuna bağlı olarak dönen belirtilen değer |
||||
*Örnek*
Belirtilen ifade `"yes"` doğru döndürür, çünkü bu örnek döner.
Aksi takdirde, `"no"`örnek döndürür:
```
if(equals(1, 1), 'yes', 'no')
```
<a name="indexof"></a>
### <a name="indexof"></a>ındexof
Bir alt dize için başlangıç konumunu veya dizin değerini döndürün.
Bu işlev büyük/küçük harf duyarlı değildir ve dizinler 0 sayısıyla başlar.
```
indexOf('<text>', '<searchText>')
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Metin*> | Evet | Dize | Bulmak için alt dize olan dize |
| <*searchText*> | Evet | Dize | Bulmak için substring |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*dizin değeri*>| Tamsayı | Belirtilen alt dize için başlangıç konumu veya dizin değeri. <p>Dize bulunamazsa, -1 sayısını döndürün. |
||||
*Örnek*
Bu örnekte, "merhaba dünya" dizesinde "dünya" alt dizesinin başlangıç dizin değeri aşağıdakileri bulur:
```
indexOf('hello world', 'world')
```
Ve bu sonucu döndürür:`6`
<a name="int"></a>
### <a name="int"></a>int
Tamsayı sürümünü bir dize için döndürün.
```
int('<value>')
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Değer*> | Evet | Dize | Dönüştürülecek dize |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*sonuç*> | Tamsayı | Belirtilen dize için birsonrakir sürümü |
||||
*Örnek*
Bu örnek, "10" dizesi için bir tamsayı sürümü oluşturur:
```
int('10')
```
Ve bu sonucu döndürür:`10`
<a name="json"></a>
### <a name="json"></a>json
Bir dize veya XML için JavaScript Nesne Gösterimi (JSON) türü değerini veya nesnesini döndürün.
```
json('<value>')
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Değer*> | Evet | Dize veya XML | Dönüştürmek için dize veya XML |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*JSON sonucu*> | JSON yerel türü veya nesnesi | Belirtilen dize veya XML için JSON yerel türü değeri veya nesnesi. Dize null ise, işlev boş bir nesne döndürür. |
||||
*Örnek 1*
Bu örnek, bu dizeyi JSON değerine dönüştürür:
```
json('[1, 2, 3]')
```
Ve bu sonucu döndürür:`[1, 2, 3]`
*Örnek 2*
Bu örnek, bu dizeyi JSON'a dönüştürür:
```
json('{"fullName": "Sophia Owen"}')
```
Ve bu sonucu döndürür:
```
{
"fullName": "Sophia Owen"
}
```
*Örnek 3*
Bu örnek, bu XML'i JSON'a dönüştürür:
```
json(xml('<?xml version="1.0"?> <root> <person id='1'> <name>Sophia Owen</name> <occupation>Engineer</occupation> </person> </root>'))
```
Ve bu sonucu döndürür:
```json
{
"?xml": { "@version": "1.0" },
"root": {
"person": [ {
"@id": "1",
"name": "Sophia Owen",
"occupation": "Engineer"
} ]
}
}
```
<a name="intersection"></a>
### <a name="intersection"></a>Kesişim
Belirtilen koleksiyonlar arasında *yalnızca* ortak öğelere sahip bir koleksiyon döndürün.
Sonuçta görünmesi için, bir öğenin bu işleve geçirilen tüm koleksiyonlarda görünmesi gerekir.
Bir veya daha fazla öğe aynı ada sahipse, bu ada sahip son öğe sonuçta görünür.
```
intersection([<collection1>], [<collection2>], ...)
intersection('<collection1>', '<collection2>', ...)
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*collection1*>, <*collection2*>, ... | Evet | Dizi veya Nesne, ancak her ikisi de | Yalnızca ortak öğeleri *istediğiniz* yerden gelen koleksiyonlar |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*ortak öğeler*> | Dizi veya Nesne, sırasıyla | Belirtilen koleksiyonlar arasında yalnızca ortak öğelere sahip bir koleksiyon |
||||
*Örnek*
Bu örnek, bu diziler arasında ortak öğeleri bulur:
```
intersection(createArray(1, 2, 3), createArray(101, 2, 1, 10), createArray(6, 8, 1, 2))
```
Ve *yalnızca* bu öğeleri içeren bir dizi döndürür:`[1, 2]`
<a name="join"></a>
### <a name="join"></a>join
Bir dizideki tüm öğeleri içeren ve her karakterin bir *delimiter*ile ayrılmış bir dize döndürün.
```
join([<collection>], '<delimiter>')
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Koleksiyon*> | Evet | Dizi | Öğelerin birleştirilmesi için dizi |
| <*Sınırlayıcı*> | Evet | Dize | Elde edilen dizedeki her karakter arasında görünen ayırıcı |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*char1*><*delimiter*><*char2*><*delimiter*>... | Dize | Belirtilen dizideki tüm öğelerden oluşturulan sonuç dizesi |
||||
*Örnek*
Bu örnek, delimiter olarak belirtilen karakter ile bu dizideki tüm öğelerden bir dize oluşturur:
```
join(createArray('a', 'b', 'c'), '.')
```
Ve bu sonucu döndürür:`"a.b.c"`
<a name="last"></a>
### <a name="last"></a>Son
Koleksiyondaki son öğeyi döndürün.
```
last('<collection>')
last([<collection>])
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Koleksiyon*> | Evet | Dize veya Dizi | Son öğeyi bulabileceğiniz koleksiyon |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*son toplama öğesi*> | String veya Array, sırasıyla | Koleksiyondaki son öğe |
||||
*Örnek*
Bu örnekler, bu koleksiyonlarda son öğeyi bulur:
```
last('abcd')
last(createArray(0, 1, 2, 3))
```
Ve bu sonuçları döndürür:
* İlk örnek:`"d"`
* İkinci örnek:`3`
<a name="lastindexof"></a>
### <a name="lastindexof"></a>Lastındexof
Bir alt dizenin son oluşumu için başlangıç konumunu veya dizin değerini döndürün.
Bu işlev büyük/küçük harf duyarlı değildir ve dizinler 0 sayısıyla başlar.
```
lastIndexOf('<text>', '<searchText>')
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Metin*> | Evet | Dize | Bulmak için alt dize olan dize |
| <*searchText*> | Evet | Dize | Bulmak için substring |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*bitiş-dizin-değer*> | Tamsayı | Belirtilen alt dizenin son oluşumu için başlangıç konumu veya dizin değeri. <p>Dize bulunamazsa, -1 sayısını döndürün. |
||||
*Örnek*
Bu örnek, "merhaba dünya" dizesinde "dünya" alt dizesinin son oluşumu için başlangıç dizin değerini bulur:
```
lastIndexOf('hello world', 'world')
```
Ve bu sonucu döndürür:`6`
<a name="length"></a>
### <a name="length"></a>length
Koleksiyondaki öğe sayısını döndürün.
```
length('<collection>')
length([<collection>])
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Koleksiyon*> | Evet | Dize veya Dizi | Saymak için öğeleri ile toplama |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*uzunluk veya sayım*> | Tamsayı | Koleksiyondaki öğe sayısı |
||||
*Örnek*
Bu örnekler, bu koleksiyonlarda öğe sayısını saymak:
```
length('abcd')
length(createArray(0, 1, 2, 3))
```
Ve bu sonucu iade edin:`4`
<a name="less"></a>
### <a name="less"></a>daha az
İlk değerin ikinci değerden küçük olup olmadığını denetleyin.
İlk değer daha az olduğunda doğru döndürün veya ilk değer daha fazla olduğunda yanlış döndürün.
```
less(<value>, <compareTo>)
less('<value>', '<compareTo>')
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Değer*> | Evet | Sonda, Float veya String | İkinci değerden daha az olup olmadığını kontrol etmek için ilk değer |
| <*compareTo*> | Evet | Sırasıyla, Insalı, Float veya String | Karşılaştırma öğesi |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| true veya false | Boole | İlk değer ikinci değerden küçük olduğunda doğru döndürün. İlk değer ikinci değere eşit veya daha büyük olduğunda yanlış döndürün. |
||||
*Örnek*
Bu örnekler, ilk değerin ikinci değerden küçük olup olmadığını denetler.
```
less(5, 10)
less('banana', 'apple')
```
Ve bu sonuçları iade edin:
* İlk örnek:`true`
* İkinci örnek:`false`
<a name="lessOrEquals"></a>
### <a name="lessorequals"></a>lessOrEquals
İlk değerin ikinci değerden küçük mü yoksa eşit mi olduğunu denetleyin.
İlk değer daha az veya eşit olduğunda doğru döndürün veya ilk değer daha fazla olduğunda false döndürün.
```
lessOrEquals(<value>, <compareTo>)
lessOrEquals('<value>', '<compareTo>')
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Değer*> | Evet | Sonda, Float veya String | İkinci değerden daha az veya eşit olup olmadığını kontrol etmek için ilk değer |
| <*compareTo*> | Evet | Sırasıyla, Insalı, Float veya String | Karşılaştırma öğesi |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| true veya false | Boole | İlk değer ikinci değerden küçük veya eşit olduğunda doğru döndürün. İlk değer ikinci değerden büyük olduğunda false döndürün. |
||||
*Örnek*
Bu örnekler, ilk değerin ikinci değerden daha az mı yoksa eşit mi olduğunu denetler.
```
lessOrEquals(10, 10)
lessOrEquals('apply', 'apple')
```
Ve bu sonuçları iade edin:
* İlk örnek:`true`
* İkinci örnek:`false`
<a name="max"></a>
### <a name="max"></a>max
Her iki uçta da dahil olan sayılarla bir listeden veya diziden en yüksek değeri döndürün.
```
max(<number1>, <number2>, ...)
max([<number1>, <number2>, ...])
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*> 1 numara,* *<numara2*>, ... | Evet | Sonda, Float veya her ikisi birden | En yüksek değeri istediğiniz sayı kümesi |
| [<*sayı1*>, <*sayı2>,* ...] | Evet | Dizi - İnteger, Float veya her ikisi birden | En yüksek değeri istediğiniz sayı dizisi |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*maksimum değer*> | Sonda veya Float | Belirtilen dizideki veya sayı kümesindeki en yüksek değer |
||||
*Örnek*
Bu örnekler, sayı kümesinden ve diziden en yüksek değeri alır:
```
max(1, 2, 3)
max(createArray(1, 2, 3))
```
Ve bu sonucu iade edin:`3`
<a name="min"></a>
### <a name="min"></a>min
Bir sayı kümesinden veya diziden en düşük değeri döndürün.
```
min(<number1>, <number2>, ...)
min([<number1>, <number2>, ...])
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*> 1 numara,* *<numara2*>, ... | Evet | Sonda, Float veya her ikisi birden | En düşük değeri istediğiniz sayı kümesi |
| [<*sayı1*>, <*sayı2>,* ...] | Evet | Dizi - İnteger, Float veya her ikisi birden | En düşük değeri istediğiniz sayı dizisi |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*min değeri*> | Sonda veya Float | Belirtilen sayı kümesindeki veya belirtilen dizideki en düşük değer |
||||
*Örnek*
Bu örnekler, sayı kümesive dizideki en düşük değeri alır:
```
min(1, 2, 3)
min(createArray(1, 2, 3))
```
Ve bu sonucu iade edin:`1`
<a name="mod"></a>
### <a name="mod"></a>mod
Kalan sayıyı iki sayıyı bölerek döndürün.
İnsteger sonucunu almak için [div()](#div)'ye bakın.
```
mod(<dividend>, <divisor>)
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Temettü*> | Evet | Sonda veya Float | *Bölene* bölünecek sayı |
| <*Bölen*> | Evet | Sonda veya Float | *Temettü*bölen ancak 0 olamaz sayı. |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*modulo-sonuç*> | Sonda veya Float | İlk sayının ikinci sayıya bölünmesinden kalan |
||||
*Örnek*
Bu örnek, birinci sayıyı ikinci sayıya böler:
```
mod(3, 2)
```
Ve bu sonucu iade edin:`1`
<a name="mul"></a>
### <a name="mul"></a>Mul
Ürünü iki sayıyı çarparak döndürün.
```
mul(<multiplicand1>, <multiplicand2>)
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*çarpma1*> | Evet | Sonda veya Float | Çarpma sayısı *çarp2* |
| <*çarpma2*> | Evet | Sonda veya Float | *Çarpanları çarpanları sayısı1* |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*ürün sonucu*> | Sonda veya Float | Birinci sayının ikinci sayıyla çarpılmasından elde edilen ürün |
||||
*Örnek*
Bu örnekler, birinci sayıyı ikinci sayıya göre birden fazla:
```
mul(1, 2)
mul(1.5, 2)
```
Ve bu sonuçları iade edin:
* İlk örnek:`2`
* İkinci örnek`3`
<a name="not"></a>
### <a name="not"></a>not
İfadenin yanlış olup olmadığını kontrol edin.
İfade yanlış olduğunda doğru döndürün veya doğru olduğunda false döndürün.
```json
not(<expression>)
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Ifa -de*> | Evet | Boole | Denetlenen ifade |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| true veya false | Boole | İfade yanlış olduğunda doğru döndürün. İfade doğru olduğunda yanlış döndürün. |
||||
*Örnek 1*
Bu örnekler, belirtilen ifadelerin yanlış olup olmadığını denetler:
```json
not(false)
not(true)
```
Ve bu sonuçları iade edin:
* İlk örnek: İfade yanlışolduğundan işlev `true`döndürür.
* İkinci örnek: İfade doğrudur, bu `false`nedenle işlev döndürür.
*Örnek 2*
Bu örnekler, belirtilen ifadelerin yanlış olup olmadığını denetler:
```json
not(equals(1, 2))
not(equals(1, 1))
```
Ve bu sonuçları iade edin:
* İlk örnek: İfade yanlışolduğundan işlev `true`döndürür.
* İkinci örnek: İfade doğrudur, bu `false`nedenle işlev döndürür.
<a name="or"></a>
### <a name="or"></a>or
En az bir ifadenin doğru olup olmadığını kontrol edin.
En az bir ifade doğru olduğunda doğru döndürün veya tümü yanlış olduğunda yanlış döndürün.
```
or(<expression1>, <expression2>, ...)
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*ifade1*>, <*ifade2*>, ... | Evet | Boole | Denetlenen ifadeler |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| true veya false | Boole | En az bir ifade doğru olduğunda doğru döndürün. Tüm ifadeler yanlış olduğunda false döndürün. |
||||
*Örnek 1*
Bu örnekler, en az bir ifadenin doğru olup olmadığını denetler:
```json
or(true, false)
or(false, false)
```
Ve bu sonuçları iade edin:
* İlk örnek: En az bir ifade doğrudur, bu nedenle işlev döndürür. `true`
* İkinci örnek: Her iki ifade de `false`yanlışolduğundan işlev geri döner.
*Örnek 2*
Bu örnekler, en az bir ifadenin doğru olup olmadığını denetler:
```json
or(equals(1, 1), equals(1, 2))
or(equals(1, 2), equals(1, 3))
```
Ve bu sonuçları iade edin:
* İlk örnek: En az bir ifade doğrudur, bu nedenle işlev döndürür. `true`
* İkinci örnek: Her iki ifade de `false`yanlışolduğundan işlev geri döner.
<a name="rand"></a>
### <a name="rand"></a>rand
Yalnızca başlangıç sonunda dahil olan belirli bir aralıktan rasgele bir tamsayı döndürün.
```
rand(<minValue>, <maxValue>)
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Minvalue*> | Evet | Tamsayı | Aralıktaki en düşük tümseci |
| <*Maxvalue*> | Evet | Tamsayı | İşlevin döndürülebileceği aralıktaki en yüksek tümseci izleyen tümseci |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*rasgele sonuç*> | Tamsayı | Belirtilen aralıktan döndürülen rasgele arayıcı |
||||
*Örnek*
Bu örnek, maksimum değer hariç, belirtilen aralıktan rasgele bir tamsayı alır:
```
rand(1, 5)
```
Ve sonuç olarak bu sayılardan `1` `2`birini `3`döndürür: , , veya`4`
<a name="range"></a>
### <a name="range"></a>aralık
Belirtilen bir tamsededen başlayan bir tamsayı dizini döndürün.
```
range(<startIndex>, <count>)
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Startındex*> | Evet | Tamsayı | Diziyi ilk öğe olarak başlatan bir sonda değeri |
| <*Sayısı*> | Evet | Tamsayı | Dizideki tümer sayısı |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| [<*aralık lı sonuç*>] | Dizi | Belirtilen dizinden başlayan tümseleri içeren dizi |
||||
*Örnek*
Bu örnek, belirtilen dizinten başlayan ve belirtilen tamsayı sayısını içeren bir tamsayı dizisi oluşturur:
```
range(1, 4)
```
Ve bu sonucu döndürür:`[1, 2, 3, 4]`
<a name="replace"></a>
### <a name="replace"></a>Değiştirmek
Bir alt dizeyi belirtilen dizeyle değiştirin ve sonuç dizesini döndürün. Bu fonksiyon büyük/küçük harf duyarlıdır.
```
replace('<text>', '<oldText>', '<newText>')
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Metin*> | Evet | Dize | Değiştirilecek alt dize olan dize |
| <*oldText*> | Evet | Dize | Değiştirilecek alt dize |
| <*newText*> | Evet | Dize | Değiştirme dizesi |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*güncelleştirilmiş metin*> | Dize | Alt dize yi değiştirdikten sonra güncelleştirilmiş dize <p>Alt dize bulunamazsa, özgün dizeyi döndürün. |
||||
*Örnek*
Bu örnekte "eski dize"deki "eski" alt dizeyi bulur ve "eski" yerine "yeni" yazar:
```
replace('the old string', 'old', 'new')
```
Ve bu sonucu döndürür:`"the new string"`
<a name="skip"></a>
### <a name="skip"></a>Atla
Öğeleri koleksiyonun önünden kaldırın ve diğer tüm öğeleri iade *edin.*
```
skip([<collection>], <count>)
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Koleksiyon*> | Evet | Dizi | Öğelerini kaldırmak istediğiniz koleksiyon |
| <*Sayısı*> | Evet | Tamsayı | Önden kaldırılacak öğe sayısı için pozitif bir tamsayı |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| [<*güncelleştirilmiş toplama*>] | Dizi | Belirtilen öğeleri kaldırdıktan sonra güncelleştirilmiş koleksiyon |
||||
*Örnek*
Bu örnek, belirtilen dizinin önünden bir öğeyi, 0 sayısını kaldırır:
```
skip(createArray(0, 1, 2, 3), 1)
```
Ve kalan öğeleri ile bu dizi döndürür:`[1,2,3]`
<a name="split"></a>
### <a name="split"></a>split
Özgün dizede belirtilen sınırlayıcı karakteri temel alarak virgülle ayrılmış alt dizeleri içeren bir dizi döndürün.
```
split('<text>', '<delimiter>')
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Metin*> | Evet | Dize | Özgün dizede belirtilen sınırlayıcıyı temel alan alt dizeleri ayırmak için dize |
| <*Sınırlayıcı*> | Evet | Dize | Delimiter olarak kullanılacak orijinal dizedeki karakter |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| [<*substring1*>.<*substring2*>,...] | Dizi | Virgüllerle ayrılmış özgün dizeden alt dizeleri içeren bir dizi |
||||
*Örnek*
Bu örnek, delimiter olarak belirtilen karaktere dayalı olarak belirtilen dizeden alt dizeleri olan bir dizi oluşturur:
```
split('a_b_c', '_')
```
Ve sonuç olarak bu dizi döndürür:`["a","b","c"]`
<a name="startOfDay"></a>
### <a name="startofday"></a>başlangıçOfDay
Günün başlangıcını bir zaman damgası için döndürün.
```
startOfDay('<timestamp>', '<format>'?)
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Zaman damgası*> | Evet | Dize | Zaman damgasını içeren dize |
| <*Biçim*> | Hayır | Dize | Ya tek bir [biçim belirticisi](https://docs.microsoft.com/dotnet/standard/base-types/standard-date-and-time-format-strings) ya da özel bir [biçim deseni.](https://docs.microsoft.com/dotnet/standard/base-types/custom-date-and-time-format-strings) Zaman damgası için varsayılan [biçim, ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) ile uyumlu ve saat dilimi bilgilerini koruyan ["o"](https://docs.microsoft.com/dotnet/standard/base-types/standard-date-and-time-format-strings) (yyyy-MM-ddTHH:mm:ss:fffffffK) biçimidir. |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*güncelleştirilmiş zaman damgası*> | Dize | Belirtilen zaman damgası ancak gün için sıfır saat işareti başlayarak |
||||
*Örnek*
Bu örnek, bu zaman damgası için günün başlangıcını bulur:
```
startOfDay('2018-03-15T13:30:30Z')
```
Ve bu sonucu döndürür:`"2018-03-15T00:00:00.0000000Z"`
<a name="startOfHour"></a>
### <a name="startofhour"></a>başlangıçOfSaat
Saat ini saat damgası için saatin başlangıcını iade edin.
```
startOfHour('<timestamp>', '<format>'?)
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Zaman damgası*> | Evet | Dize | Zaman damgasını içeren dize |
| <*Biçim*> | Hayır | Dize | Ya tek bir [biçim belirticisi](https://docs.microsoft.com/dotnet/standard/base-types/standard-date-and-time-format-strings) ya da özel bir [biçim deseni.](https://docs.microsoft.com/dotnet/standard/base-types/custom-date-and-time-format-strings) Zaman damgası için varsayılan [biçim, ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) ile uyumlu ve saat dilimi bilgilerini koruyan ["o"](https://docs.microsoft.com/dotnet/standard/base-types/standard-date-and-time-format-strings) (yyyy-MM-ddTHH:mm:ss:fffffffK) biçimidir. |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*güncelleştirilmiş zaman damgası*> | Dize | Belirtilen zaman damgası ancak saat için sıfır dakika işaretinden başlayarak |
||||
*Örnek*
Bu örnek, bu zaman damgası için saatin başlangıcını bulur:
```
startOfHour('2018-03-15T13:30:30Z')
```
Ve bu sonucu döndürür:`"2018-03-15T13:00:00.0000000Z"`
<a name="startOfMonth"></a>
### <a name="startofmonth"></a>başlangıçOfMonth
Zaman damgası için ayın başlangıcını iade edin.
```
startOfMonth('<timestamp>', '<format>'?)
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Zaman damgası*> | Evet | Dize | Zaman damgasını içeren dize |
| <*Biçim*> | Hayır | Dize | Ya tek bir [biçim belirticisi](https://docs.microsoft.com/dotnet/standard/base-types/standard-date-and-time-format-strings) ya da özel bir [biçim deseni.](https://docs.microsoft.com/dotnet/standard/base-types/custom-date-and-time-format-strings) Zaman damgası için varsayılan [biçim, ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) ile uyumlu ve saat dilimi bilgilerini koruyan ["o"](https://docs.microsoft.com/dotnet/standard/base-types/standard-date-and-time-format-strings) (yyyy-MM-ddTHH:mm:ss:fffffffK) biçimidir. |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*güncelleştirilmiş zaman damgası*> | Dize | Belirtilen zaman damgası ancak sıfır saat işareti yle ayın ilk gününde başlayan |
||||
*Örnek*
Bu örnek, bu zaman damgası için ayın başlangıcını döndürür:
```
startOfMonth('2018-03-15T13:30:30Z')
```
Ve bu sonucu döndürür:`"2018-03-01T00:00:00.0000000Z"`
<a name="startswith"></a>
### <a name="startswith"></a>startsWith
Bir dize belirli bir alt dize ile başlayıp başlamadığını denetleyin.
Alt dize bulunduğunda doğru döndürün veya bulunmadığında false döndürün.
Bu işlev büyük/küçük harf duyarlı değildir.
```
startsWith('<text>', '<searchText>')
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Metin*> | Evet | Dize | Denetlenen dize |
| <*searchText*> | Evet | Dize | Bulmak için başlangıç dizesi |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| true veya false | Boole | Başlangıç alt dizesi bulunduğunda doğru döndürün. Bulunduğunda yanlış döndürün. |
||||
*Örnek 1*
Bu örnek, "merhaba dünya" dizesinin "hello" alt dizesiyle başlayıp başlamadığını denetler:
```
startsWith('hello world', 'hello')
```
Ve bu sonucu döndürür:`true`
*Örnek 2*
Bu örnek, "merhaba dünya" dizesinin "selamlar" alt dizesiyle başlayıp başlamadığını denetler:
```
startsWith('hello world', 'greetings')
```
Ve bu sonucu döndürür:`false`
<a name="string"></a>
### <a name="string"></a>string
Bir değer için dize sürümünü döndürün.
```
string(<value>)
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Değer*> | Evet | Herhangi biri | Dönüştürülecek değer |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*dize değeri*> | Dize | Belirtilen değer için dize sürümü |
||||
*Örnek 1*
Bu örnek, bu sayı için dize sürümünü oluşturur:
```
string(10)
```
Ve bu sonucu döndürür:`"10"`
*Örnek 2*
Bu örnek, belirtilen JSON nesnesi için bir dize oluşturur ve çift tırnak işareti (") için bir kaçış karakteri olarak ters eğik çizgi karakteri (\\) kullanır.
```
string( { "name": "Sophie Owen" } )
```
Ve bu sonucu döndürür:`"{ \\"name\\": \\"Sophie Owen\\" }"`
<a name="sub"></a>
### <a name="sub"></a>Alt
İkinci sayıyı ilk sayıdan çıkarmanın sonucunu döndürün.
```
sub(<minuend>, <subtrahend>)
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*minuend*> | Evet | Sonda veya Float | *Subtrahend* çıkarmak için hangi sayı |
| <*Subtrahend*> | Evet | Sonda veya Float | *Minuend'den* çıkarılabilen sayı |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*Sonuç*> | Sonda veya Float | İkinci sayının ilk sayıdan çıkarılarak elde edilen sonuç |
||||
*Örnek*
Bu örnek, ikinci sayıyı ilk sayıdan çıkarır:
```
sub(10.3, .3)
```
Ve bu sonucu döndürür:`10`
<a name="substring"></a>
### <a name="substring"></a>Dize
Belirtilen konumdan başlayarak karakterleri bir dizeden veya dizinden döndürün.
Dizin değerleri 0 sayısıyla başlar.
```
substring('<text>', <startIndex>, <length>)
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Metin*> | Evet | Dize | Karakterleri istediğiniz dize |
| <*Startındex*> | Evet | Tamsayı | Başlangıç pozisyonu veya dizin değeri olarak kullanmak istediğiniz 0'a eşit veya daha büyük pozitif bir sayı |
| <*Uzun -luğu*> | Evet | Tamsayı | Alt dizede istediğiniz pozitif karakter sayısı |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*substring sonucu*> | Dize | Kaynak dizedeki belirtilen dizin konumundan başlayarak, belirtilen karakter sayısına sahip bir alt diz |
||||
*Örnek*
Bu örnek, dizin değeri 6 başlayarak, belirtilen dize beş karakterli bir alt dize oluşturur:
```
substring('hello world', 6, 5)
```
Ve bu sonucu döndürür:`"world"`
<a name="subtractFromTime"></a>
### <a name="subtractfromtime"></a>çıkarmaFromTime
Zaman damgasından birkaç zaman birimi çıkarın.
Ayrıca [bakınız GetPastTime](#getPastTime).
```
subtractFromTime('<timestamp>', <interval>, '<timeUnit>', '<format>'?)
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Zaman damgası*> | Evet | Dize | Zaman damgasını içeren dize |
| <*Aralığı*> | Evet | Tamsayı | Çıkarıiçin belirtilen zaman birimlerinin sayısı |
| <*zaman Birimi*> | Evet | Dize | *Aralıklı*olarak kullanılacak zaman birimi : "İkinci", "Dakika", "Saat", "Gün", "Hafta", "Ay", "Yıl" |
| <*Biçim*> | Hayır | Dize | Ya tek bir [biçim belirticisi](https://docs.microsoft.com/dotnet/standard/base-types/standard-date-and-time-format-strings) ya da özel bir [biçim deseni.](https://docs.microsoft.com/dotnet/standard/base-types/custom-date-and-time-format-strings) Zaman damgası için varsayılan [biçim, ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) ile uyumlu ve saat dilimi bilgilerini koruyan ["o"](https://docs.microsoft.com/dotnet/standard/base-types/standard-date-and-time-format-strings) (yyyy-MM-ddTHH:mm:ss:fffffffK) biçimidir. |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*güncelleştirilmiş zaman damgası*> | Dize | Zaman damgası eksi belirtilen zaman birimleri sayısı |
||||
*Örnek 1*
Bu örnek, bu zaman damgasından bir gün çıkarır:
```
subtractFromTime('2018-01-02T00:00:00Z', 1, 'Day')
```
Ve bu sonucu döndürür:`"2018-01-01T00:00:00:0000000Z"`
*Örnek 2*
Bu örnek, bu zaman damgasından bir gün çıkarır:
```
subtractFromTime('2018-01-02T00:00:00Z', 1, 'Day', 'D')
```
Ve bu sonucu isteğe bağlı "D" biçimini kullanarak döndürür:`"Monday, January, 1, 2018"`
<a name="take"></a>
### <a name="take"></a>almak
Öğeleri koleksiyonun önünden döndürün.
```
take('<collection>', <count>)
take([<collection>], <count>)
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Koleksiyon*> | Evet | Dize veya Dizi | Öğeleri istediğiniz koleksiyon |
| <*Sayısı*> | Evet | Tamsayı | Önden istediğiniz öğe sayısı için pozitif tamsayı |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*alt kümesi*> veya [<*alt kümesi*>] | String veya Array, sırasıyla | Özgün koleksiyonun önünden alınan belirtilen öğe sayısına sahip bir dize veya dizi |
||||
*Örnek*
Bu örnekler, bu koleksiyonların önünden belirtilen öğe sayısını alır:
```
take('abcde', 3)
take(createArray(0, 1, 2, 3, 4), 3)
```
Ve bu sonuçları iade edin:
* İlk örnek:`"abc"`
* İkinci örnek:`[0, 1, 2]`
<a name="ticks"></a>
### <a name="ticks"></a>Ticks
Belirtilen `ticks` bir zaman damgası için özellik değerini döndürün.
*Kene* 100 nanosaniyelik bir aralıktır.
```
ticks('<timestamp>')
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Zaman damgası*> | Evet | Dize | Zaman damgası için dize |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*keneler-sayı*> | Tamsayı | Belirtilen zaman damgası beri kene sayısı |
||||
<a name="toLower"></a>
### <a name="tolower"></a>Tolower
Küçük harf biçiminde bir dize döndürün. Dizedeki bir karakterin küçük bir sürümü yoksa, bu karakter döndürülen dizede değişmeden kalır.
```
toLower('<text>')
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Metin*> | Evet | Dize | Küçük harf biçiminde döndürülecek dize |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*küçük harf-metin*> | Dize | Küçük harf biçiminde orijinal dize |
||||
*Örnek*
Bu örnek, bu dizeyi küçük harfe dönüştürür:
```
toLower('Hello World')
```
Ve bu sonucu döndürür:`"hello world"`
<a name="toUpper"></a>
### <a name="toupper"></a>Toupper
Büyük harf biçiminde bir dize döndürün. Dizedeki bir karakterin büyük harf sürümü yoksa, bu karakter döndürülen dizede değişmeden kalır.
```
toUpper('<text>')
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Metin*> | Evet | Dize | Büyük harf biçiminde döndürülecek dize |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*büyük harf-metin*> | Dize | Büyük harf biçiminde orijinal dize |
||||
*Örnek*
Bu örnek, bu dizeyi büyük harfe dönüştürür:
```
toUpper('Hello World')
```
Ve bu sonucu döndürür:`"HELLO WORLD"`
<a name="trim"></a>
### <a name="trim"></a>Döşeme
Satır aralığını ve sondaki beyaz boşluğu bir dizeden kaldırın ve güncelleştirilmiş dizeyi döndürün.
```
trim('<text>')
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Metin*> | Evet | Dize | Kaldırılacak öncü ve sondaki beyaz alana sahip dize |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*güncelleştirilmişMetin*> | Dize | Boşluk tuşuna girmeden veya beyaz boşluğu izlemeden özgün dize için güncelleştirilmiş bir sürüm |
||||
*Örnek*
Bu örnek, " Hello World " dizesinden satır aralığı ve sondaki beyaz boşluğu kaldırır:
```
trim(' Hello World ')
```
Ve bu sonucu döndürür:`"Hello World"`
<a name="union"></a>
### <a name="union"></a>birleşim
Belirtilen koleksiyonlardan *tüm* öğeleri içeren bir koleksiyon döndürün.
Sonuç olarak görünmesi için, bu işleve geçirilen herhangi bir koleksiyonda bir öğe görünebilir. Bir veya daha fazla öğe aynı ada sahipse, bu ada sahip son öğe sonuçta görünür.
```
union('<collection1>', '<collection2>', ...)
union([<collection1>], [<collection2>], ...)
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*collection1*>, <*collection2*>, ... | Evet | Dizi veya Nesne, ancak her ikisi de | *Tüm* öğeleri istediğiniz yerden koleksiyonlar |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*updatedCollection*> | Dizi veya Nesne, sırasıyla | Belirtilen koleksiyonlardan tüm öğeleri içeren bir koleksiyon - yineleme yok |
||||
*Örnek*
Bu örnek, bu koleksiyonlardan *tüm* öğeleri alır:
```
union(createArray(1, 2, 3), createArray(1, 2, 10, 101))
```
Ve bu sonucu döndürür:`[1, 2, 3, 10, 101]`
<a name="uriComponent"></a>
### <a name="uricomponent"></a>uriComponent
URL güvenli olmayan karakterleri kaçış karakterleriyle değiştirerek, tek düzen kaynak tanımlayıcısı (URI) kodlanmış sürümü bir dize için döndürün.
[UriComponent() kodlayerine](#encodeUriComponent)bu işlevi kullanın.
Her iki fonksiyon da `uriComponent()` aynı şekilde çalışsa da tercih edilir.
```
uriComponent('<value>')
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Değer*> | Evet | Dize | URI kodlu biçime dönüştürülecek dize |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*kodlanmış-uri*> | Dize | Kaçış karakterleri ile URI kodlanmış dize |
||||
*Örnek*
Bu örnek, bu dize için URI kodlanmış bir sürüm oluşturur:
```
uriComponent('https://contoso.com')
```
Ve bu sonucu döndürür:`"http%3A%2F%2Fcontoso.com"`
<a name="uriComponentToBinary"></a>
### <a name="uricomponenttobinary"></a>uriComponentToBinary
Tek bir kaynak tanımlayıcısı (URI) bileşeni için ikili sürümü döndürün.
```
uriComponentToBinary('<value>')
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Değer*> | Evet | Dize | Dönüştürmek için URI kodlanmış dize |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*ikili-for-kodlanmış-uri*> | Dize | URI kodlanmış dize için ikili sürüm. İkili içerik base64 kodlanır ve `$content`. |
||||
*Örnek*
Bu örnek, URI kodlanmış bu dize için ikili sürümü oluşturur:
```
uriComponentToBinary('http%3A%2F%2Fcontoso.com')
```
Ve bu sonucu döndürür:
`"001000100110100001110100011101000111000000100101001100
11010000010010010100110010010001100010010100110010010001
10011000110110111101101110011101000110111101110011011011
110010111001100011011011110110110100100010"`
<a name="uriComponentToString"></a>
### <a name="uricomponenttostring"></a>uriComponentToString
Uri kodlu dizeyi etkili bir şekilde çözen tek tip bir kaynak tanımlayıcısı (URI) kodlanmış dize için dize sürümünü döndürün.
```
uriComponentToString('<value>')
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Değer*> | Evet | Dize | Decode için URI kodlanmış dize |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*deşifre-uri*> | Dize | URI kodlanmış dize için kodlanmış sürümü |
||||
*Örnek*
Bu örnek, URI tarafından kodlanmış bu dize için deşifre edilmiş dize sürümünü oluşturur:
```
uriComponentToString('http%3A%2F%2Fcontoso.com')
```
Ve bu sonucu döndürür:`"https://contoso.com"`
<a name="utcNow"></a>
### <a name="utcnow"></a>utcŞimdi
Geçerli zaman damgasını döndürün.
```
utcNow('<format>')
```
İsteğe bağlı olarak, <*biçimi*> parametresi ile farklı bir biçim belirtebilirsiniz.
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Biçim*> | Hayır | Dize | Ya tek bir [biçim belirticisi](https://docs.microsoft.com/dotnet/standard/base-types/standard-date-and-time-format-strings) ya da özel bir [biçim deseni.](https://docs.microsoft.com/dotnet/standard/base-types/custom-date-and-time-format-strings) Zaman damgası için varsayılan [biçim, ISO 8601](https://en.wikipedia.org/wiki/ISO_8601) ile uyumlu ve saat dilimi bilgilerini koruyan ["o"](https://docs.microsoft.com/dotnet/standard/base-types/standard-date-and-time-format-strings) (yyyy-MM-ddTHH:mm:ss:fffffffK) biçimidir. |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*geçerli zaman damgası*> | Dize | Geçerli tarih ve saat |
||||
*Örnek 1*
Bugün 15 Nisan 2018 saat 13:00'de olduğunu varsayalım.
Bu örnek, geçerli zaman damgasını alır:
```
utcNow()
```
Ve bu sonucu döndürür:`"2018-04-15T13:00:00.0000000Z"`
*Örnek 2*
Bugün 15 Nisan 2018 saat 13:00'de olduğunu varsayalım.
Bu örnek, isteğe bağlı "D" biçimini kullanarak geçerli zaman damgasını alır:
```
utcNow('D')
```
Ve bu sonucu döndürür:`"Sunday, April 15, 2018"`
<a name="xml"></a>
### <a name="xml"></a>xml
JSON nesnesi içeren bir dize için XML sürümünü döndürün.
```
xml('<value>')
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Değer*> | Evet | Dize | Dönüştürmek için JSON nesnesi ile dize <p>JSON nesnesinin yalnızca bir kök özelliği olmalıdır, bu da bir dizi olamaz. <br>Çift tırnak işareti\\(") için bir kaçış karakteri olarak ters eğik çizgi karakterini ( ) kullanın. |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*xml versiyonu*> | Nesne | Belirtilen dize veya JSON nesnesi için kodlanmış XML |
||||
*Örnek 1*
Bu örnek, bir JSON nesnesi içeren bu dize için XML sürümünü oluşturur:
`xml(json('{ \"name\": \"Sophia Owen\" }'))`
Ve bu sonucu XML döndürür:
```xml
<name>Sophia Owen</name>
```
*Örnek 2*
Bu JSON nesnesi olduğunu varsayalım:
```json
{
"person": {
"name": "Sophia Owen",
"city": "Seattle"
}
}
```
Bu örnek, bu JSON nesnesi içeren bir dize için XML oluşturur:
`xml(json('{\"person\": {\"name\": \"Sophia Owen\", \"city\": \"Seattle\"}}'))`
Ve bu sonucu XML döndürür:
```xml
<person>
<name>Sophia Owen</name>
<city>Seattle</city>
<person>
```
<a name="xpath"></a>
### <a name="xpath"></a>Xpath
XML'yi, XPath (XML Path Language) ifadesiyle eşleşen düğümler veya değerler için denetleyin ve eşleşen düğümleri veya değerleri döndürün. XPath ifadesi veya yalnızca "XPath", XML içeriğinde düğümleri veya işlem değerlerini seçebilmeniz için Bir XML belge yapısında gezinmenize yardımcı olur.
```
xpath('<xml>', '<xpath>')
```
| Parametre | Gerekli | Tür | Açıklama |
| --------- | -------- | ---- | ----------- |
| <*Xml*> | Evet | Herhangi biri | XPath ifade değeriyle eşleşen düğümleri veya değerleri aramak için XML dizesi |
| <*Xpath*> | Evet | Herhangi biri | Eşleşen XML düğümlerini veya değerlerini bulmak için kullanılan XPath ifadesi |
|||||
| Döndürülen değer | Tür | Açıklama |
| ------------ | ---- | ----------- |
| <*xml düğümü*> | XML | Yalnızca tek bir düğüm belirtilen XPath ifadesiyle eşleştiğinde bir XML düğümü |
| <*Değer*> | Herhangi biri | Yalnızca tek bir değer belirtilen XPath ifadesiyle eşleştiğinde XML düğümündeki değer |
| [<*xml-düğüm1*>, <*xml-düğüm2*>, ...] </br>-veya- </br>[<*değer1*>, <*değeri2*>, ...] | Dizi | XML düğümleri veya değerleri belirtilen XPath ifadesiyle eşleşen bir dizi |
||||
*Örnek 1*
Örnek 1'de aşağıdaki örnek, düğümle `<count></count>` eşleşen düğümleri bulur ve bu `sum()` düğüm değerlerini işleve ekler:
`xpath(xml(parameters('items')), 'sum(/produce/item/count)')`
Ve bu sonucu döndürür:`30`
*Örnek 2*
Bu örnekte, her iki ifadede de, xml ile ad alanı içeren belirtilen bağımsız değişkenlerde `<location></location>` düğümle eşleşen düğümler bulur. İfadeler, çift tırnak işareti\\(") için bir kaçış karakteri olarak ters eğik çizgi karakteri ( ) kullanır.
* *İfade 1*
`xpath(xml(body('Http')), '/*[name()=\"file\"]/*[name()=\"location\"]')`
* *İfade 2*
`xpath(xml(body('Http')), '/*[local-name()=\"file\" and namespace-uri()=\"http://contoso.com\"]/*[local-name()=\"location\"]')`
İşte argümanlar şunlardır:
* XML belge ad alanını içeren bu `xmlns="http://contoso.com"`XML:
```xml
<?xml version="1.0"?> <file xmlns="http://contoso.com"> <location>Paris</location> </file>
```
* Ya XPath ifade burada:
* `/*[name()=\"file\"]/*[name()=\"location\"]`
* `/*[local-name()=\"file\" and namespace-uri()=\"http://contoso.com\"]/*[local-name()=\"location\"]`
Düğümle eşleşen sonuç düğümü `<location></location>` aşağıda veda edebilirsiniz:
```xml
<location xmlns="https://contoso.com">Paris</location>
```
*Örnek 3*
Örnek 3'te aşağıdaki örnek, `<location></location>` düğümdeki değeri bulur:
`xpath(xml(body('Http')), 'string(/*[name()=\"file\"]/*[name()=\"location\"])')`
Ve bu sonucu döndürür:`"Paris"`
## <a name="next-steps"></a>Sonraki adımlar
İfadelerde kullanabileceğiniz sistem değişkenlerinin listesi için [Bkz. Sistem değişkenleri.](control-flow-system-variables.md)
| 31.076483 | 551 | 0.657332 | tur_Latn | 0.998278 |
aa2cb24db7ea6b69d4f52a8444615ddcd343e3ed | 917 | md | Markdown | LiveSite/content/directadmin/adddomain/_index.en.md | mxroute/mxdocs | f9013e8a23bbafaddf8f121f9c8304cce1c2d7cb | [
"MIT"
] | null | null | null | LiveSite/content/directadmin/adddomain/_index.en.md | mxroute/mxdocs | f9013e8a23bbafaddf8f121f9c8304cce1c2d7cb | [
"MIT"
] | null | null | null | LiveSite/content/directadmin/adddomain/_index.en.md | mxroute/mxdocs | f9013e8a23bbafaddf8f121f9c8304cce1c2d7cb | [
"MIT"
] | 1 | 2022-02-21T23:00:07.000Z | 2022-02-21T23:00:07.000Z | ---
title: "Add Domain"
weight: 3
draft: false
# search related keywords
keywords: ["directadmin, domain"]
---
## Log in to Control Panel
You can find a guide for that by clicking this link.
## Open Domain Setup
Once logged into the control panel, you can add as many domains as you need. On the left side, click on Account Manager, and then Domain Setup.
## Click Add New
From there, look to the right side, and find the ADD NEW button.
## Fill in Information
After clicking ADD NEW, you will see this page:
Fill in the **Domain** field with the one that you wish to add. **Ignore all of the other fields on this page**. When finished, click **CREATE** at the bottom right. | 38.208333 | 165 | 0.740458 | eng_Latn | 0.979964 |
aa2d0d1fb141f8d8cba98bf4ef91fdd0f0a9576d | 321 | md | Markdown | src/safe-guides/coding_practice/data-type/tuple/G.TYP.TUP.01.md | ZhangHanDong/rust-coding-guidelines-zh | 4b3e2012c1a911c5263f289386fc963dd0765c51 | [
"MIT"
] | 1 | 2022-02-16T01:08:24.000Z | 2022-02-16T01:08:24.000Z | src/safe-guides/coding_practice/data-type/tuple/G.TYP.TUP.01.md | ZhangHanDong/rust-coding-guidelines-zh | 4b3e2012c1a911c5263f289386fc963dd0765c51 | [
"MIT"
] | null | null | null | src/safe-guides/coding_practice/data-type/tuple/G.TYP.TUP.01.md | ZhangHanDong/rust-coding-guidelines-zh | 4b3e2012c1a911c5263f289386fc963dd0765c51 | [
"MIT"
] | null | null | null | ## G.TYP.TUP.01 使用元组时，其元素不宜超过3个
**【级别】** 建议
**【描述】**
元组是异构复合类型，元素过多，其表达力会下降，影响代码可读性和可维护性。
尤其是利用元组作为函数返回值时，不宜过多。
**【反例】**
```rust
// 不符合：超过3个元组参数
fn convert(x: i8) -> (i8, i16, i32, i64, f32, f64) {
(x as i8, x as i16, x as i32,
x as i64, x as f32, x as f64)
}
fn main(){
let _ = convert(3);
}
```
| 12.346154 | 52 | 0.557632 | glg_Latn | 0.242527 |
aa2e48a4d5ebe949db0b0c2200369571785cb0e1 | 2,745 | md | Markdown | README.md | dlarssonse/cached-api | 07a45e3fedc857bec0afc34e67c2f3872ffc75a9 | [
"0BSD"
] | null | null | null | README.md | dlarssonse/cached-api | 07a45e3fedc857bec0afc34e67c2f3872ffc75a9 | [
"0BSD"
] | null | null | null | README.md | dlarssonse/cached-api | 07a45e3fedc857bec0afc34e67c2f3872ffc75a9 | [
"0BSD"
] | null | null | null | Cached API
=========
A library for handling cached web requests.
## Installation
`npm install @dlarsson-se/cached-api -S`
## Example Usage
#### app.module.ts
```
import { APIModule, CachedAPIService } from '@dlarsson-se/cached-api;
@NgModule({
imports: [ APIModule.forRoot() ] // If it works, or
...
imports: [ APIModule ], // If it doesn't
providers: [ CachedAPIService ]
})
export class AppModule {
constructor(public apiService: CachedAPIService) {
/* If the requests should contain Authorization: Bearer TOKEN */
apiService.setToken('YOUR_TOKEN');
/* Default URL for TestData objects. */
apiService.addURL(TestData, "http://localhost/testdata");
/* Custom URL for the find command. */
apiService.addURL(TestData, "http://localhost/testdatas", "find");
}
}
```
#### app.component.ts (without APIComponent inheritance)
```
import { CachedAPIService } from '@dlarsson-se/cached-api';
export class AppComponent {
constructor(private apiService: CachedAPIService) {
let id = 1;
/* Get By ID */
apiService.get(TestData, id)
.subscribe((value) => {
/* Do something with the reply. */
}, (error) => {
/* Error handling. */
})
/* Find */
apiService.find(TestData)
.subscribe((values) => {
/* Do something with the reply. */
}, (error) => {
/* Error handling. */
})
}
}
```
#### app.component.ts (with APIComponent inheritance)
```
import { APIComponent, CachedAPIService } from '@dlarsson-se/cached-api';
export class AppComponent extends APIComponent {
constructor(public apiService: CachedAPIService) {
super(apiService);
let id = 1;
/* get with mandatory supplied id. */
let p1 = this.getAsync(TestData, id)
/* find with optional querystring. */
let p2 = this.findAsync(TestData, "YOUR_QUERY_HERE")
/* Handle all promises. */
Promise
.all([p1, p2])
.then((values) => {
/* Do something with the reply. */
})
.catch((error) => {
/* Error handling. */
})
}
}
```
#### testdata.ts
```
import { IAPIClass } from '@dlarsson-se/cached-api';
export class TestData implements IAPIClass {
public _cachedAt: number = 0;
public _className: string = "TestData";
}
```
## Tests
`npm test`
## Contributing
In lieu of a formal style guide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Lint and test your code.
```
npm run format
npm run lint
``` | 23.262712 | 159 | 0.582514 | eng_Latn | 0.505436 |
aa2ee7cede9982228c3e2976def11825c3f4ee0d | 6,660 | md | Markdown | _posts/2014-06-25-istopmotion-3-for-mac-makes-stop-motion-animation-a-breeze.md | BenjaminLawson/byterevel | 0f9e076cfe22b62825eda19bdd9f9df9c7a5ece1 | [
"BSD-3-Clause",
"MIT"
] | null | null | null | _posts/2014-06-25-istopmotion-3-for-mac-makes-stop-motion-animation-a-breeze.md | BenjaminLawson/byterevel | 0f9e076cfe22b62825eda19bdd9f9df9c7a5ece1 | [
"BSD-3-Clause",
"MIT"
] | null | null | null | _posts/2014-06-25-istopmotion-3-for-mac-makes-stop-motion-animation-a-breeze.md | BenjaminLawson/byterevel | 0f9e076cfe22b62825eda19bdd9f9df9c7a5ece1 | [
"BSD-3-Clause",
"MIT"
] | null | null | null | ---
id: 4541
title: iStopMotion 3 for Mac Makes Stop Motion Animation a Breeze
date: 2014-06-25T17:17:49+00:00
author: Ben Lawson
layout: single
guid: /?p=4541
permalink: /2014/06/25/istopmotion-3-for-mac-makes-stop-motion-animation-a-breeze/
image: /wp-content/uploads/2014/06/iStopMotion_for_Mac_AppIcon.png
categories:
- Review
- Software
tags:
- animation
- boinx
- ios
- istopmotion
- mac
- review
- Software
- stop motion
---
### Full Review
Making inanimate objects move on their own is a magical sight that has fueled my small hobby of stop motion animation for years. I [used to use iMovie](/2011/07/01/how-to-make-a-stop-motion-animation-using-imovie/ "How To Make A Stop Motion Animation Using iMovie") to compile all of the photos from my digital camera, and then I transitioned into the [iStopMotion iPad app](/2013/06/21/making-stop-motion-animations-is-easy-with-istopmotion-for-ipad/ "Making Stop-Motion Animations is Easy with iStopMotion for iPad"). But now, I think I’ve found the epitome of amateur stop motion animation software. Boinx’s iStopMotion 3 combines core frame capturing features with great compiling and editing functionality all in one streamlined interface.
When you create a new project, the first thing to do is select what camera you are using. iStopMotion supports a small range of Nikon and Canon DSLR cameras, but the best experience is found with their companion app Remote Camera, which is available on all iOS devices. This convenient app supports adjusting focus, exposure, and white balance. Both orientations seem to be supported, but switching between them is a little bit glitchy.
[<img class="alignnone wp-image-4581 size-large" src="/wp-content/uploads/2014/06/05_remote-camera-1024x640.png" alt="Remote Camera App" width="820" height="512" srcset="/wp-content/uploads/2014/06/05_remote-camera-1024x640.png 1024w, /wp-content/uploads/2014/06/05_remote-camera-300x187.png 300w, /wp-content/uploads/2014/06/05_remote-camera-180x112.png 180w, /wp-content/uploads/2014/06/05_remote-camera-360x225.png 360w, /wp-content/uploads/2014/06/05_remote-camera-790x493.png 790w, /wp-content/uploads/2014/06/05_remote-camera-1095x684.png 1095w, /wp-content/uploads/2014/06/05_remote-camera-900x562.png 900w" sizes="(max-width: 820px) 100vw, 820px" />](/wp-content/uploads/2014/06/05_remote-camera.png)
One of the most basic features that any stop motion software should have is onion skinning, where the previous frame is overlaid on the current camera feed as to make relative movement easier. iStopMotion gets this right with an opacity adjustment and the option to overlay multiple frames at once (useful if you’re trying to follow a path or pattern smoothly).
[<img class="alignnone size-large wp-image-4588" src="/wp-content/uploads/2014/06/onion-skin-istopmotion-1024x640.jpg" alt="onion-skin-istopmotion" width="820" height="512" srcset="/wp-content/uploads/2014/06/onion-skin-istopmotion-1024x640.jpg 1024w, /wp-content/uploads/2014/06/onion-skin-istopmotion-300x187.jpg 300w, /wp-content/uploads/2014/06/onion-skin-istopmotion-180x112.jpg 180w, /wp-content/uploads/2014/06/onion-skin-istopmotion-360x225.jpg 360w, /wp-content/uploads/2014/06/onion-skin-istopmotion-790x493.jpg 790w, /wp-content/uploads/2014/06/onion-skin-istopmotion-1095x684.jpg 1095w, /wp-content/uploads/2014/06/onion-skin-istopmotion-900x562.jpg 900w, /wp-content/uploads/2014/06/onion-skin-istopmotion.jpg 1440w" sizes="(max-width: 820px) 100vw, 820px" />](/wp-content/uploads/2014/06/onion-skin-istopmotion.jpg)
In addition to onion skinning, there is a rotoscoping feature that lets you trace frames over a video. This is fantastic if you are trying to emulate a walking cycle or recreate a scene from a video.
Alternatively to capturing every frame manually, you can record a time lapse that will automatically capture a frame at a set interval. You could try to do stop motion this way, but it is best used to capture interesting changes in the world (the sun setting, people walking). A recent update lets you capture from your desktop, so coupled with this time lapse feature you can do things like record yourself drawing and play it back as a time lapse. I tested it with an hour of browser activity, and it led to some pretty funny results!
One drop down lets you fiddle with tilt shift settings that apply a blur that makes large scenes look like tiny toy sets.
It’s difficult to design a cool background for your scene, so the compositing functionality is welcomed. The two tabs let you choose a foreground and a background. Using chroma key technology that replaces a background color with an image, iStopMotion makes it possible to put your actors on the moon! It may have been my lighting or background, but this feature seems experimental and not quite functional enough for use in production. Foreground images are simply overlaid on the frames with no problems.
[<img class="alignnone wp-image-4601" src="/wp-content/uploads/2014/06/moon-compositing-tabs.jpg" alt="moon-compositing-tabs" width="825" height="333" srcset="/wp-content/uploads/2014/06/moon-compositing-tabs.jpg 900w, /wp-content/uploads/2014/06/moon-compositing-tabs-300x121.jpg 300w, /wp-content/uploads/2014/06/moon-compositing-tabs-180x72.jpg 180w, /wp-content/uploads/2014/06/moon-compositing-tabs-360x145.jpg 360w, /wp-content/uploads/2014/06/moon-compositing-tabs-790x318.jpg 790w" sizes="(max-width: 825px) 100vw, 825px" />](/wp-content/uploads/2014/06/moon-compositing-tabs.jpg)[
](/wp-content/uploads/2014/06/compositing-tabs.jpg)
Once you’ve captured all of the frames in your video, it’s time to edit it. iStopMotion provides some basic editing functionality with tools like reversing sequences of frames and moving them around. It also supports adding a soundtrack, which makes it possible to sync up your frames with music and make a groovy music video. Although iStopMotion’s editing features are very bare bones, it does support exporting into more advanced video editing software such as Final Cut Pro or iMovie for finishing touches.
Boinx updates iStopMotion frequently with great new features like desktop recording, additional camera support, and bug fixes. They have an official support forum, decent documentation, and phone support.
Overall, iStopMotion 3 is a great piece of software that is certainly worth the price for animation enthusiasts of all ages. There are very few bugs, and the feature set is complete. You can grab a copy over at the <a href="http://itunes.apple.com/app/istopmotion-3/id546649552" target="_blank">Mac App Store</a> for $49.99.
| 128.076923 | 829 | 0.790991 | eng_Latn | 0.956443 |
aa2f241ef99c421bf5cad141a5a984cd607ccda5 | 2,841 | md | Markdown | README.md | F7U12Team/password-manager | 408ac1c8d7742a1053bfee360d3460dc18c75adf | [
"Apache-2.0"
] | 10 | 2017-08-05T13:41:41.000Z | 2020-04-06T14:42:04.000Z | README.md | F7U12Team/password-manager | 408ac1c8d7742a1053bfee360d3460dc18c75adf | [
"Apache-2.0"
] | null | null | null | README.md | F7U12Team/password-manager | 408ac1c8d7742a1053bfee360d3460dc18c75adf | [
"Apache-2.0"
] | 2 | 2020-02-17T10:40:38.000Z | 2020-04-16T13:46:37.000Z | Password Manager for Android (TREZOR)
======
Keep your passwords safe with Password Manager for TREZOR, the unofficial Android app for complete security. Password Manager for Android is not related with Satoshilabs nor [TREZOR](https://buytrezor.com/?a=227f182fcbbe).
More info at [Official website](https://pma.madriguera.me)
Available at [Google Playstore](https://play.google.com/store/apps/details?id=me.madriguera.pma)
## Requisites
* [Go](https://golang.org/) & [Gomobile](https://github.com/golang/go/wiki/Mobile)
* [Android NDK](https://developer.android.com/ndk/index.html)
* [Android SDK](https://developer.android.com/studio/index.html)
* [npm](https://www.npmjs.com/)
* Probably something more I can't remember
## Building the application
You first need to build the Go code (tesoroandroid/tesoroandroid.go) with
```bash
$ gomobile bind -target android -o tesoroandroid.aar -v .
```
and move the tesoroandroid.aar file to passwordmanager/android/tesoroandroid/tesoroandroid.aar
Then, build the Android application with gradle on the passwordmanager/android directory with
```bash
$ ./gradlew assembleDebug && ./gradlew installDebug
```
## About the application
The UI is made with React Native, the main logic resides in a Go program that is compiled using gomobile bind command. Everything is glued together via gradle.
You need to set the Dropbox's API keys and path at tesoroandroid.go, DropBoxModule.java and in the AndroidManifest.xml file.
You need to set some other information, like your app's ID on some other files.
## Contributing to this project:
We worked hard and put a lot of effort in this app, we made it open source and available to anyone, so please, consider making a small donation and let us keep working adding new features: **1MVM8fBfkpxRqBADsYuvEHnMYgxRDWB99R**
If you find any improvement or issue you want to fix, feel free to send us a pull request or open an issue.
## License
This is distributed under the Apache License v2.0
Copyright 2017 F7U12 Team - pma@madriguera.me
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
### Other licenses
Some parts, libraries and modules may have a different license, authors and copyright holders which is include along the library (Dropbox SDK (custom?, looks like MIT), json-simple (Apache v2.0), react-native-swipeout (MIT),...) | 41.173913 | 228 | 0.765927 | eng_Latn | 0.970861 |
aa2f4106651c8d387c120b0e33f4034aca2bcdeb | 621 | markdown | Markdown | _posts/2015-07-30-stoneskin.markdown | bondjimbond/grimoire | fcf03ae4668c18e1bdca8136618536445f63671a | [
"MIT"
] | null | null | null | _posts/2015-07-30-stoneskin.markdown | bondjimbond/grimoire | fcf03ae4668c18e1bdca8136618536445f63671a | [
"MIT"
] | null | null | null | _posts/2015-07-30-stoneskin.markdown | bondjimbond/grimoire | fcf03ae4668c18e1bdca8136618536445f63671a | [
"MIT"
] | null | null | null | ---
layout: post
title: "Stoneskin"
date: 2015-07-30
sources: [PHB.278, SRD.183]
tags: [cleric (war), druid, monk (four elements), paladin (ancients), paladin (conquest), paladin (redemption), sorcerer, ranger, wizard, level4, abjuration]
---
**4th-level abjuration**
**Casting Time**: 1 action
**Range**: Touch
**Components**: V, S, M (diamond dust worth 100 gp, which the spell consumes)
**Duration**: Concentration, up to 1 hour
This spell turns the flesh of a willing creature you touch as hard as stone. Until the spell ends, the target has resistance to nonmagical bludgeoning, piercing, and slashing damage.
| 31.05 | 182 | 0.726248 | eng_Latn | 0.887388 |
aa2fd3c2babbe6c7cf9b3b29e4857a7987dcbf24 | 5,440 | md | Markdown | articles/virtual-machines/dv2-dsv2-series-memory.md | matmahnke/azure-docs.pt-br | 6c96d25caf8663547775f333164198e3ed03972f | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/virtual-machines/dv2-dsv2-series-memory.md | matmahnke/azure-docs.pt-br | 6c96d25caf8663547775f333164198e3ed03972f | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/virtual-machines/dv2-dsv2-series-memory.md | matmahnke/azure-docs.pt-br | 6c96d25caf8663547775f333164198e3ed03972f | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: VMs de série DSv2 e Dv2 otimizadas para memória – máquinas virtuais do Azure
description: Especificações para as VMs da série Dv2 e DSv2.
author: joelpelley
ms.service: virtual-machines
ms.subservice: sizes
ms.topic: conceptual
ms.date: 02/03/2020
ms.author: jushiman
ms.openlocfilehash: 3e5f00695ee6f823cf36625f41b25ad9e273481e
ms.sourcegitcommit: 829d951d5c90442a38012daaf77e86046018e5b9
ms.translationtype: MT
ms.contentlocale: pt-BR
ms.lasthandoff: 10/09/2020
ms.locfileid: "91649612"
---
# <a name="memory-optimized-dv2-and-dsv2-series"></a>Dv2 com otimização de memória e série Dsv2
A Dv2 e a série Dsv2, uma continuação da série D original, apresenta uma CPU mais potente. Os tamanhos da série DSv2 são executados no Intel® Xeon® Platinum 8272CL (Cascadey Lake), no Intel® Xeon® 8171M 2,1 GHz (Skylake) ou no Intel® Xeon® E5-2673 v4 2,3 GHz (Broadwell) ou nos processadores Intel® Xeon® E5-2673 v3 2,4 GHz (Haswell). A série Dv2 tem as mesmas configurações de memória e disco que a série D.
## <a name="dv2-series-11-15"></a>Série Dv2 11-15
Os tamanhos da série Dv2 são executados no Intel® Xeon® Platinum 8272CL (Cascadey Lake), no Intel® Xeon® 8171M 2,1 GHz (Skylake) ou no Intel® Xeon® E5-2673 v4 2,3 GHz (Broadwell) ou nos processadores Intel® Xeon® E5-2673 v3 2,4 GHz (Haswell).
[ACU](acu.md): 210-250<br>
[Armazenamento Premium](premium-storage-performance.md): sem suporte<br>
[Armazenamento em cache Premium](premium-storage-performance.md): sem suporte<br>
[Migração ao vivo](maintenance-and-updates.md): com suporte<br>
[Atualizações de preservação de memória](maintenance-and-updates.md): com suporte<br>
[Suporte à geração de VM](generation-2.md): geração 1<br>
<br>
| Tamanho | vCPU | Memória: GiB | Armazenamento temporário (SSD) GiB | Taxa de transferência máxima de armazenamento temporário: IOPS/MBps de leitura/MBps de gravação | Máximo de discos de dados/taxa de transferência: IOPS | Máximo de NICs|Largura de banda de rede esperada (Mbps) |
|---|---|---|---|---|---|---|---|
| Standard_D11_v2 | 2 | 14 | 100 | 6000/93/46 | 8/8x500 | 2|1500 |
| Standard_D12_v2 | 4 | 28 | 200 | 12000/187/93 | 16/16x500 | 4|3000 |
| Standard_D13_v2 | 8 | 56 | 400 | 24000/375/187 | 32/32x500 | 8|6000 |
| Standard_D14_v2 | 16 | 112 | 800 | 48000/750/375 | 64/64x500 | 8|12000 |
| Standard_D15_v2 <sup>1</sup> | 20 | 140 | 1000 | 60000/937/468 | 64/64x500 | 8|25000 <sup>2</sup> |
<sup>1</sup> A instância é isolada em hardware dedicado a um único cliente.
<sup>2</sup> 25000 Mbps com Rede Acelerada.
## <a name="dsv2-series-11-15"></a>Série DSv2 11-15
Os tamanhos da série DSv2 são executados no Intel® Xeon® Platinum 8272CL (Cascadey Lake), no Intel® Xeon® 8171M 2,1 GHz (Skylake) ou no Intel® Xeon® E5-2673 v4 2,3 GHz (Broadwell) ou nos processadores Intel® Xeon® E5-2673 v3 2,4 GHz (Haswell).
[ACU](acu.md): 210-250 <sup>1</sup><br>
[Armazenamento Premium](premium-storage-performance.md): com suporte<br>
[Cache de armazenamento Premium](premium-storage-performance.md): com suporte<br>
[Migração ao vivo](maintenance-and-updates.md): com suporte<br>
[Atualizações de preservação de memória](maintenance-and-updates.md): com suporte<br>
[Suporte à geração de VM](generation-2.md): geração 1 e 2<br>
<br>
| Tamanho | vCPU | Memória: GiB | Armazenamento temporário (SSD) GiB | Discos de dados máximos | Taxa de transferência máxima de armazenamento em cache e temporária: IOPS/MBps (tamanho do cache em GiB) | Taxa de transferência de disco sem cache: IOPS/MBps | Máximo de NICs|Largura de banda de rede esperada (Mbps) |
| --- | --- | --- | --- | --- | --- | --- | --- |---|
| Standard_DS11_v2 <sup>3</sup> | 2 | 14 | 28 | 8 | 8000/64 (72) | 6400/96 | 2|1500 |
| Standard_DS12_v2 <sup>3</sup> | 4 | 28 | 56 | 16 | 16000/128 (144) | 12800/192 | 4|3000 |
| Standard_DS13_v2 <sup>3</sup> | 8 | 56 | 112 | 32 | 32000/256 (288) | 25600/384 | 8|6000 |
| Standard_DS14_v2 <sup>3</sup> | 16 | 112 | 224 | 64 | 64000/512 (576) | 51200/768 | 8|12000 |
| Standard_DS15_v2 <sup>2</sup> | 20 | 140 | 280 | 64 | 80000/640 (720) | 64000/960 | 8|25000 <sup>4</sup> |
<sup>1</sup> A taxa de transferência máxima possível do disco (IOPS ou MBps) com uma VM da série DSv2 pode ser limitada pelo número, tamanho e distribuição dos discos anexados. Para obter detalhes, confira o artigo [Projetar para um alto desempenho](./premium-storage-performance.md).
<sup>2</sup> a instância é isolada para o hardware baseado em Intel Haswell e dedicada a um único cliente.
<sup>3</sup> Tamanhos limitados de núcleos disponíveis.
<sup>4</sup> 25000 Mbps com Rede Acelerada.
[!INCLUDE [virtual-machines-common-sizes-table-defs](../../includes/virtual-machines-common-sizes-table-defs.md)]
## <a name="other-sizes-and-information"></a>Outros tamanhos e informações
- [Propósito geral](sizes-general.md)
- [Memória otimizada](sizes-memory.md)
- [Armazenamento otimizado](sizes-storage.md)
- [GPU otimizada](sizes-gpu.md)
- [Computação de alto desempenho](sizes-hpc.md)
- [Gerações anteriores](sizes-previous-gen.md)
Calculadora de preços: [calculadora de preços](https://azure.microsoft.com/pricing/calculator/)
Mais informações sobre tipos de discos: [tipos de disco](./disks-types.md#ultra-disk)
## <a name="next-steps"></a>Próximas etapas
Saiba mais sobre como as [ACUs (unidade de computação do Azure)](acu.md) podem ajudar você a comparar o desempenho de computação entre SKUs do Azure. | 62.528736 | 408 | 0.718382 | por_Latn | 0.967287 |
aa30df47060085affdba2a04920252ba52d1d6da | 403 | md | Markdown | about.md | qst0/qst0.github.io | 666ab5d533f48a660dadcba628c4bdcc296ca566 | [
"MIT"
] | null | null | null | about.md | qst0/qst0.github.io | 666ab5d533f48a660dadcba628c4bdcc296ca566 | [
"MIT"
] | null | null | null | about.md | qst0/qst0.github.io | 666ab5d533f48a660dadcba628c4bdcc296ca566 | [
"MIT"
] | null | null | null | ---
layout: page
title: qst0
permalink: /about/
---
Hello!
I'm qst0 or Mason Young.
I'm a programmer, teacher and friend to all!
### You want to know more?
A great way to learn more about a person is to know what they like!
Here is a list of some sites I enjoy:
* https://www.khanacademy.org
* https://github.com/
* More to come...
### Send me an email!
[msnyng@gmail.com](mailto:msnyng@gmail.com)
| 18.318182 | 67 | 0.694789 | eng_Latn | 0.988319 |
aa31272cedddc4235a86221a127d94a06941f1aa | 3,001 | md | Markdown | README.md | wiegandf/skyhook | 164a8602f95e73964013dcaa31e6734f6597a22a | [
"MIT"
] | 4 | 2018-06-25T12:57:17.000Z | 2021-11-09T09:34:59.000Z | README.md | wiegandf/skyhook | 164a8602f95e73964013dcaa31e6734f6597a22a | [
"MIT"
] | 1 | 2018-10-12T11:31:26.000Z | 2019-03-15T15:53:45.000Z | README.md | wiegandf/skyhook | 164a8602f95e73964013dcaa31e6734f6597a22a | [
"MIT"
] | 4 | 2018-03-28T20:06:46.000Z | 2019-01-29T11:50:33.000Z | # Skyhook [](https://godoc.org/github.com/hippogryph/skyhook)
### (recently moved from github.com/natefinch/skyhook)
Skyhook is a wrapper for google's [skylark](https://github.com/google/skylark)
embedded python-like language. Skyhook is intended to give you an easier-to-use
interface for running skylark scripts directly from your Go programs. Skylark
is a dialect of python, and has a Go native interpreter, so you can let your
users extend your application without any external requirements.
## Video Demo
[](https://www.youtube.com/watch?v=y2QepLHHmsk)
## Text Demo
Assume you have this file at plugins/foo.sky:
```python
def foo():
return " world!"
output = input + foo()
```
You can call this script from go thusly:
```go
sky := skyhook.New([]string{"plugins"})
globals := map[string]interface{}{"input":"hello"}
globals, err := sky.Run("foo.sky", globals)
if err != nil {
return err
}
fmt.Println(globals["output"])
// prints "hello world!"
```
## Usage
You give skyhook a list of directories to look in, and it will look
for skylark scripts in each of those directories, in order, until it finds a
script with the given name, and then run that script.
## Inputs and Outputs
Skylark scripts (and skyhook scripts by extension) use global variables in the
script as the input and output. Args in Run are created as global variables in
the script with the given names.
Thus if args are `map[string]interface{}{"input":"hello"}`, the script may act
on the variable called input thusly:
```python
output = input + "world!"
```
When run, this script will create a value in the map returned from Run with the
key "output" and with the value "hello world!".
## Types
Skyhook automatically translates go types in Run's args map to skylark types.
The types supported are any int, uint, or float type, strings,
maps[interface{}]interface{}, map[interface{}]bool, []interface{}. Where all
interface[] values must be one of the supported types. Conversion out of
skylark scripts work in reverse much the same way. You may also pass in
skylark.Value types directly, in which case they will be passed to the script
as-is.
## Functions
You can pass go functions that the script can call by passing your function in
with the rest of the globals. Some caveats: skylark ints always come in as
int64, not "int". The supported types are the same as ToValue. Positional args
are passed to your function and converted with FromValue. Kwargs passed from
skylark are currently ignored.
## Caching
Since parsing scripts is non-zero work, skyhook caches the scripts it finds
after the first time they get run, so that further runs of the script will not
incur the disk read and parsing overhead. To make skyhook reparse a file
(perhaps because it's changed) use the Forget method for the specific file, or
Reset to remove all cached files. | 34.494253 | 129 | 0.754082 | eng_Latn | 0.991844 |
aa31b5e64f3f8c8a7175cbaefe212dc2a4e44f24 | 1,232 | md | Markdown | desktop-src/AD/enumerating-members-in-a-group.md | dianmsft/win32 | f07b550595a83e44dd2fb6e217525edd10a0341b | [
"CC-BY-4.0",
"MIT"
] | 4 | 2021-07-26T16:18:49.000Z | 2022-02-19T02:00:21.000Z | desktop-src/AD/enumerating-members-in-a-group.md | dianmsft/win32 | f07b550595a83e44dd2fb6e217525edd10a0341b | [
"CC-BY-4.0",
"MIT"
] | 2 | 2020-04-09T17:00:51.000Z | 2020-04-09T18:30:01.000Z | desktop-src/AD/enumerating-members-in-a-group.md | dianmsft/win32 | f07b550595a83e44dd2fb6e217525edd10a0341b | [
"CC-BY-4.0",
"MIT"
] | 2 | 2020-07-19T02:58:48.000Z | 2021-03-06T21:09:47.000Z | ---
title: Enumerating Members in a Group
description: The members of a group are stored in a multi-value attribute called member.
ms.assetid: 28cafdbe-e599-4b1d-a384-264f41d81c79
ms.tgt_platform: multiple
keywords:
- Enumerating Members in a Group
ms.topic: article
ms.date: 05/31/2018
---
# Enumerating Members in a Group
The members of a group are stored in a multi-value attribute called **member**. For groups with a small to medium-sized membership, use the [**IADsGroup.Members**](https://docs.microsoft.com/windows/desktop/api/iads/nf-iads-iadsgroup-members) method to get a pointer to an [**IADsMembers**](https://docs.microsoft.com/windows/desktop/api/iads/nn-iads-iadsmembers) object that contains the list of all members. Then use the [**IADsMembers::get\_\_NewEnum**](https://docs.microsoft.com/windows/desktop/api/iads/nf-iads-iadsmembers-get__newenum) to get an enumerator object that you can use to enumerate the members.
If the anticipated group membership will be 1000 or more members, use ranging to retrieve users one range at a time. For more information about using ranging to enumerate members, see [Enumerating Groups That Contain Many Members](enumerating-groups-that-contain-many-members.md).
| 49.28 | 613 | 0.782468 | eng_Latn | 0.971393 |
aa31d2a3e22b58ac0e96537c863647eac418e677 | 1,613 | md | Markdown | RELEASE.md | obabec/drogue-cloud | 16f8b5391624c7d5e2c3ecadc962fb0fe15707bd | [
"Apache-2.0"
] | null | null | null | RELEASE.md | obabec/drogue-cloud | 16f8b5391624c7d5e2c3ecadc962fb0fe15707bd | [
"Apache-2.0"
] | null | null | null | RELEASE.md | obabec/drogue-cloud | 16f8b5391624c7d5e2c3ecadc962fb0fe15707bd | [
"Apache-2.0"
] | null | null | null | # Release cheat sheet
## Next version
Preparing for a new version (not release, like a milestone):
* Change the version in all crates to e.g. `0.4.0`
* Pay attention to the `service-api` crate as its version will be reported externally
## Overall process
* Create a new tag
* Start with a `v0.x.0-rc1` version
* The final version should be `v0.x.0`
* Push the tag
* Wait for the build
* Test the instructions in the following "Installation" subsections
* For each installation:
* Test the links on the command line
* Test the links in the web console
* Try out the example commands
* Create a branch `release-0.x`
* Ensure to switch the doc version to 0.x too: `docs/antora.yml`
## Release text
The text that goes into the final GitHub release record:
---
## Installation
Download one of the installers, extract and run the installer script `scripts/drogue.sh` from the main directory of
the archive.
You will need:
* Bash
* `kubectl`
* `curl`
* Podman or docker
* A Kubernetes cluster (also see below)
By default, the cluster type will be aligned with the downloaded installer. However, you can override this using
the `CLUSTER` variable:
~~~shell
env CLUSTER=kind ./scripts/drogue.sh
~~~
### Minikube
* Install Minikube – https://minikube.sigs.k8s.io/docs/start/
~~~shell
minikube start --cpus 4 --memory 16384 --disk-size 20gb --addons ingress
minikube tunnel # in a separate terminal, as it keeps running
./scripts/drogue.sh
~~~
### Kind
* Install `kind` – https://github.com/kubernetes-sigs/kind/releases
~~~shell
kind create cluster
./scripts/drogue.sh
~~~
---
| 22.402778 | 115 | 0.718537 | eng_Latn | 0.984311 |
aa323ecdfbc9a727ac43cd37d166a6ccf0b9dbf9 | 539 | md | Markdown | flow-docs/includes/cc-preview-features-send-us-feedback.md | Navecha/flow-docs.nl-nl | a749e7c63e45c85539dd4aafeb5c31043e5ad35a | [
"CC-BY-4.0",
"MIT"
] | null | null | null | flow-docs/includes/cc-preview-features-send-us-feedback.md | Navecha/flow-docs.nl-nl | a749e7c63e45c85539dd4aafeb5c31043e5ad35a | [
"CC-BY-4.0",
"MIT"
] | null | null | null | flow-docs/includes/cc-preview-features-send-us-feedback.md | Navecha/flow-docs.nl-nl | a749e7c63e45c85539dd4aafeb5c31043e5ad35a | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
ms.openlocfilehash: 4f37625e2eb1a146d3ec6740d6dcc54d058c573c
ms.sourcegitcommit: 93f8bac60cebb783b3a8fc8887193e094d4e27e2
ms.translationtype: MT
ms.contentlocale: nl-NL
ms.lasthandoff: 05/25/2019
ms.locfileid: "64463455"
---
We maken deze preview beschikbaar zodat u deze kunt proberen en ons kunt laten weten wat u ervan vindt. Aan de hand van uw feedback geven wij prioriteit aan de mogelijkheden die u het meest nodig hebt. We vragen u om ons suggesties te geven en problemen te melden via onze openbaar beschikbare feedbackwebsite: | 59.888889 | 310 | 0.827458 | nld_Latn | 0.997521 |
aa3251c4a40b47b0cd17b889cbb15ac511a527cc | 4,282 | md | Markdown | README.md | KyleLilly/do-dyndns | 2dd79574c823af616a7c69bc47c6c55b5583d1d4 | [
"MIT"
] | 2 | 2018-10-09T22:52:10.000Z | 2021-09-30T06:17:26.000Z | README.md | KyleLilly/do-dyndns | 2dd79574c823af616a7c69bc47c6c55b5583d1d4 | [
"MIT"
] | null | null | null | README.md | KyleLilly/do-dyndns | 2dd79574c823af616a7c69bc47c6c55b5583d1d4 | [
"MIT"
] | null | null | null | # Digital Ocean Dynamic DNS Service
A simple nodejs based [namecheap](https://www.namecheap.com) compatible dynamic DNS updated service for
Digital Ocean. The service includes a single endpoint `/update` that expects a `PUT` request with
`domain`, `host`, `password` and `ip` parameters. It then makes a call to the [Digital Ocean Version 2 API](https://developers.digitalocean.com/documentation/v2/)
to update an associated `A` record to point to the provided IP.
## Why
The [UniFi Security Gateway](https://www.ubnt.com/unifi-routing/usg/) provides built-in support for
a limited number of dynamic DNS services. They don't provide support for Digitial Ocean and namecheap
was one of the few they supported that didn't leverage basic auth. With this service you can select
namecheap from the Dynamic DNS service list and specify the server where this service is running in
the `server` field to have the USG reach out to this service. The value for hostname will be sent as
the `host` parameter, username will be sent as `domain` and password will be sent as `password`.
## Security
The service should be run behind a proxy which has `SSL` enabled like nginx, apache, or something else.
It can also be modified to start the service with SSL itself but that is beyond the scope of this README.
There is very basic security built-in to the service in the form of the query parameter `password` which
is then hashed using scrypt and compared to the `HASHED_CREDENTIALS` value from the configuration file.
Before the hashes are checked the `host` and `domain` query parameters are used to find a corresponding DNS
record ID in the `DOMAINS` configuration map. If no matching domain is found a `403` is returned before
attempting to compare the password hash.
## Service Configuration
The service relies on a config file `config.json` and example of the configuration file is provided.
- `API_TOKEN` is the token used to communicate with the digital ocean API. You can generate
a token on the [Apps & API](https://cloud.digitalocean.com/settings/applications) page of your account.
The token will need to have `WRITE` access.
- `HASHED_CREDENTIALS` should be the base64 encoded string for an scrypt generate "secret" hash. You
can generate this value after you've done an `npm install` from this directory via the node command line:
```
localhost:do-dyndns root$ node
> const scrypt = require('scrypt');
undefined
> let password = 'SECRET';
undefined
> scrypt.hashSync(password, {'N': 2,'r': 1,'p': 1}, 64, password).toString('base64');
'SNRxlb5dmc5jvs5amUzKPIwq0glkBxvUapBtUkbjlWc3uOXakGgh0LO14ZksyMAjJA9xQvMrmlh9IqaXO020yQ=='
```
- `SERVER_CONFIG` is a (hapi server configuration object)[https://hapijs.com/api/16.6.2#serverconnectionoptions]
### Using Docker
The service can be run as a docker container using the standard service port `8002` using the provided
[Dockerfile](Dockerfile). A [Makefile](Makefile) has also been included for convenience and supports
the following commands:
* `build` - builds the do_dyndns docker image
* `run` - runs the service in docker using the do_dyndns image
* `clean` - stops and removes and containers using the do_dyndns image and removes the image
### License
Copyright (c) 2018 Kyle Lilly (kylelilly@gmail.com)
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation
files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy,
modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the
Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. | 65.876923 | 162 | 0.786315 | eng_Latn | 0.986062 |
aa348811c0e623cdde726d104574b95915576f30 | 64 | md | Markdown | posts.md | markcyen/markcyen.github.io | 888abf0e5a49f930dbef43403519d4fb605925a4 | [
"MIT"
] | 1 | 2022-01-18T19:44:24.000Z | 2022-01-18T19:44:24.000Z | posts.md | markcyen/markcyen.github.io | 888abf0e5a49f930dbef43403519d4fb605925a4 | [
"MIT"
] | null | null | null | posts.md | markcyen/markcyen.github.io | 888abf0e5a49f930dbef43403519d4fb605925a4 | [
"MIT"
] | null | null | null | ---
layout: page
title: Posts
---
# Currently under construction | 12.8 | 30 | 0.71875 | eng_Latn | 0.993973 |
aa35161ad9cf9f6b97b1b7b93b5bec412c86031e | 1,734 | md | Markdown | Readme.md | web-mech/can-stream-x | bb025a313c2432861ba7293c6d8f6128f187ced8 | [
"MIT"
] | null | null | null | Readme.md | web-mech/can-stream-x | bb025a313c2432861ba7293c6d8f6128f187ced8 | [
"MIT"
] | null | null | null | Readme.md | web-mech/can-stream-x | bb025a313c2432861ba7293c6d8f6128f187ced8 | [
"MIT"
] | null | null | null | # can-stream-x
[](https://travis-ci.org/web-mech/can-stream-x)
Stream values into and out of computes using any streaming lib.
Great for streaming libs that return emitters as a callback.
## Syntax
```
canStreamX([options]);
```
### Notes
- Passing falsey values for the emitter flag makes indicates the emitter is a function and should be called directly.
- Passing falsey values for the unsubscribe method indicates the unsubscribe method is derived from the subscribe method.
### Options
- streamConstructor - <Function> method necessary to create a stream.
- emitMethod - <string> Which method to use as the emitter.
- on - <string> Which method to use to subscribe.
- off - <string> Which method to use to unsubscribe.
## Example Usage
### Using RxJs
```
var canStreamX = require('./can-stream-x');
var Rx = require('rxjs');
var Observable = Rx.Observable;
var canStream = canStreamX({
streamConstructor: Observable.create,
emitMethod: 'next',
on: 'subscribe',
off: 'unsubscribe'
});
var c = compute(0);
var stream = canStream.toStream(c);
var computeVal;
stream.subscribe((newVal) => {
computeVal = newVal;
});
c(1);
console.log(computeVal); //1
```
### Using Kefir
```
var canStreamX = require('./can-stream-x');
var Kefir = require('kefir');
var canStream = canStreamX({
streamConstructor: Kefir.stream,
emitMethod: 'emit',
on: 'onValue',
off: 'offValue'
});
...
```
### Using Bacon
```
var canStreamX = require('./can-stream-x');
var Bacon = require('bacon');
var canStream = canStreamX({
streamConstructor: Bacon.fromBinder,
on: 'onValue',
off: false
});
...
```
## testing
```
npm test
``` | 20.162791 | 125 | 0.689735 | eng_Latn | 0.816864 |
aa357bf89bfc387fd688f5cdb67a41495d9965a3 | 50 | md | Markdown | README.md | praashant99/visualizing-the-weather-data-set | 7a38c34517c00f74b873795ce902a0c870968a0d | [
"MIT"
] | null | null | null | README.md | praashant99/visualizing-the-weather-data-set | 7a38c34517c00f74b873795ce902a0c870968a0d | [
"MIT"
] | null | null | null | README.md | praashant99/visualizing-the-weather-data-set | 7a38c34517c00f74b873795ce902a0c870968a0d | [
"MIT"
] | null | null | null | ### Project Overview
visualizing weather data
| 8.333333 | 25 | 0.74 | eng_Latn | 0.889546 |
aa35ba959db94b251b2e77d9528d5ac13d81b0d2 | 7,635 | md | Markdown | src/graft/index.md | uakci/ithkuil.place | 0a5c077c30526293425bfe40d534c545541d1abe | [
"MIT"
] | 2 | 2020-08-26T22:41:52.000Z | 2020-08-26T23:40:56.000Z | src/graft/index.md | uakci/ithkuil.place | 0a5c077c30526293425bfe40d534c545541d1abe | [
"MIT"
] | null | null | null | src/graft/index.md | uakci/ithkuil.place | 0a5c077c30526293425bfe40d534c545541d1abe | [
"MIT"
] | null | null | null | ithkuil.place
Tools, resources, and APIs for the Ithkuilic languages.
ithkuil.place
Welcome! <span lang="ithkuil">Wattunkí ruyün!</span> <span
lang="ithkuil">Attawîláiff üpʰu!</span> On this webpage, you will find
assorted tools, resources, and (someday maybe even) APIs whose
collective goal is to aid in learning and using the Ithkuilic languages.
::: {.notice}
[Confused? Check out our FAQ.](faq)
:::
## Ithkuilic venues {#social}
- <a href="https://discord.com/invite/WgFrX8J" id="discord">uhailalepš Discord server</a>
— where most of today’s discussions about Ithkuil III and IV are
held. If you want to learn the language(s) or have a chat about
them, consider joining!
- <a href="https://reddit.com/r/ithkuil" id="reddit">r/Ithkuil subreddit</a>
— where the design documents are posted, as well as kiepier’s
quasi-weekly translation challenges.
## Ithkuil IV {#iv}
Ithkuil IV (a.k.a., *The New Ithkuilic Language* or *TNIL*) is John
Quijada’s newest, work-in-progress creation. [More info…](faq#iv)
### Documentation and learning materials {#iv-docs}
- [Most Recent Design Documents](https://www.reddit.com/r/Ithkuil/comments/j5i75b/most_recent_design_documents/)
— the newest versions of each of the three regularly-updated design
documents (in PDF form): Morpho-phonology, Lexical Roots, and VxCs
Affixes ([what are those?](faq#iv-docs)). Make sure to get all of them.
- [TNIL documentation archive](4/archive/) (on-site) is where you’ll
find links to older releases (to satisfy your curiosity).
- [Morphology cheatsheet](https://drive.google.com/drive/folders/1gAd7nto6PfKvwKvBHver1fwGe9PO7IfW)
(Menotim) — a 2-page bird’s-eye overview of Morpho-phonology for
quick and handy reference.
- [Collaborative TNIL Roots and Affixes Spreadsheet](https://docs.google.com/spreadsheets/d/1JdaG1PaSQJRE2LpILvdzthbzz1k_a0VT86XSXouwGy8/edit)
(Syst3ms, kiepier, Behemoth) — a computerized edition of the
lexicon, intended as the backing database for….
- [TNILGloss](https://github.com/Syst3ms/TNILGloss)
(Behemoth4, Syst3ms) — a Discord utility bot that parses and provides
interlinear glosses for any TNIL input that you give it.
### Trinkets {#iv-trinkets}
- [Pick a color, get the TNIL root!](4/colors/) (porpoiseless)
### Texts {#iv-texts}
- [TNIL Community Lexical Supplement](https://docs.google.com/spreadsheets/d/1_RCOCVkRvZsSd5Vomfr8wDeRF7kUQ-feYOCkrQzXLCw/edit)
(Ilmen, uakci, uagle…) — an informal dictionary in the works
consisting of around 100 TNIL lexemes alongside their English
renditions.
- [TNIL translations & stuff](https://docs.google.com/spreadsheets/d/1f88UJaJPDvOSCFx16-LSx931lyE6v5NPgsFw1P5VFjo/edit)
(uakci; various authors) — an edited, back-translated,
irregularly-updated anthology of original works, translations, and
other works in TNIL.
### Miscellaneous {#iv-misc}
- [ASCII-friendly TNIL romanization](https://docs.google.com/document/d/1Dlf9xcVqBeHQYrnDpDVgb5WUiNDpyBA36frC5dJCVNM/edit) (uagle)
- [TNIL Romanization for IMEs](https://gist.github.com/uakci/db83384621fc02225173f334be7c4ff2)
(Christian Oudard)
### Outdated or incomplete resources {#iv-outdated}
- [NILDB](https://github.com/Philosophical-Language-Group/NILDB)
(by HactarCE and porpoiseless) is a computer-readable listing of TNIL
Categories in YAML format.
- [Libre documentation](https://tnil.readthedocs.io/en/latest/)
(porpoiseless, HactarCE)
- [Roots v0.4, bookmarked](https://cdn.discordapp.com/attachments/198559368772452352/766790575940698152/root_list_0.4_bookmarked.pdf),
[Affixes v0.7.1, bookmarked](https://cdn.discordapp.com/attachments/198559368772452352/768196761365381130/affix_list_0.7.1_bookmarked.pdf)
(Merox)
### Offshoots {#iv-offshoots}
- [Skewers](https://uakci.eu/files/skewers/skewers-0.3.pdf) (uakci;
outdated as of now) — a morphological mod aiming to reduce the
amount of arbitrariness in the language.
- [Freetnil](https://github.com/Philosophical-Language-Group/freetnil)
(porpoiseless, uakci, et al.) — a community-driven effort which
attempts to distill TNIL’s progressive ideas further and set them
against a philosophically sound semantic and ontological theory.
## Ithkuil III {#iii}
Ithkuil III is the Ithkuil that you can find on
[ithkuil.net](http://ithkuil.net). [More info…](faq#iii)
### Documentation and learning materials {#iii-docs}
- [A Grammar Of Ithkuil (ithkuil.net)](http://ithkuil.net) — the
be-all and end-all of Ithkuil III documentation. Make sure to visit
the updates page, which lists post-release tweaks to the language
that haven’t been recorded in the main text.
- [On-site mirror](mirror/2001-en/)
- [Russian translation](https://ithkuil-rus.github.io/)
- [Elamxhí](https://porpoiseless.github.io/elamxhi/) (porpoiseless) a
computer-readable list of roots, retrieved from Ithkuil III’s
lexicon page. The link will take you to a nice user-friendly
interface.
- PDFs for:
- [All roots](https://cdn.discordapp.com/attachments/184758428424601601/729292021382119454/All_Roots.pdf)
(Ilmen)
- [All suffixes](https://cdn.discordapp.com/attachments/184758428424601601/729292026486456360/All_Suffixes.pdf)
(Ilmen)
- [The whole website](https://vk.com/doc-7192938_71447375) (?)
- Cheatsheets:
- [melopee’s](https://cdn.discordapp.com/attachments/198559368772452352/479738219374706749/compith_2kwc.pdf)
- [fagri’s](https://cdn.discordapp.com/attachments/198559368772452352/561017368470618145/two-page.pdf)
- phalp’s Introductory Ithkuil lessons:
[1](https://www.reddit.com/r/Ithkuil/comments/1s1nrh/ithkuil_lesson_1_simple_nouns/),
[2](https://www.reddit.com/r/Ithkuil/comments/1swc0s/ithkuil_lesson_2_verbs_sentences_case/),
[3 & 4](https://www.reddit.com/r/Ithkuil/comments/1v29l2/ithkuil_lessons_3_perspective_and_4_pras/).
- Memrise courses:
- [Ithkuil 4k vocab by
class](https://www.memrise.com/course/2022297/ithkuil-4k-vocab-by-class/)
(?)
- [Ithkuil Vocab
learning](https://www.memrise.com/course/878185/ithkuil-vocab-learning/)
(?)
### Tooling {#iii-tooling}
- [Ithkey](https://github.com/melopee/ithkey) (melopee) — a keyboard
layout for the Ithkuil writing system. Also contains **Ykulvaarlck’s
Ithkuil font** and a detailed description of how it works.
- [Formative maker](http://www.laethiel.fr/ithkuil/composer.php) (?) —
pick and choose category values, press a button, and see the
resulting formative.
- [Glosser](https://ithkuil.ebvalaim.pl/) (ebvalaim)
### Texts {#iii-texts}
- [Official Texts, Deviations, Translations](https://docs.google.com/spreadsheets/d/1SRlpwOhZCaVB1LtdbhWGTWrKWKSL39C2pjOjF5OTZlA/edit)
(vulgak; various authors) — the definitive repository of Ithkuil III
written output.
- [Small vocab list](https://pastebin.com/TrfNRvKr) (Ilmen) — a
moderately-sized list of peculiar coinings.
### Miscellaneous {#iii-misc}
- [Notes on Ithkuil](https://eloertkha.svbtle.com/) (?) — a blog.
## Ithkuil I and II {#historic}
Also known as Iţkuîl and Ilaksh. [Read more…](faq#historic)
- [On-site mirror of ithkuil.net](mirror/2004-en-alt/)
- [Web Archive snapshot of ithkuil.net](https://web.archive.org/web/20090311041719/http://ithkuil.net/)
— incomplete (‘archaeological’!) documentation for 2004 & 2007
Ithkuil.
- [On-site mirror](mirror/2004-en/)
- [Ithkuil I Russian translation](http://ithkuil-russian.narod.ru/)
- [On-site mirror](mirror/2004-ru/)
| 47.71875 | 144 | 0.730714 | eng_Latn | 0.478534 |
aa35f5284550b55e34ea1b6166e0508ea78e55c2 | 15,407 | md | Markdown | articles/machine-learning/how-to-train-keras.md | flexray/azure-docs.pl-pl | bfb8e5d5776d43b4623ce1c01dc44c8efc769c78 | [
"CC-BY-4.0",
"MIT"
] | 12 | 2017-08-28T07:45:55.000Z | 2022-03-07T21:35:48.000Z | articles/machine-learning/how-to-train-keras.md | flexray/azure-docs.pl-pl | bfb8e5d5776d43b4623ce1c01dc44c8efc769c78 | [
"CC-BY-4.0",
"MIT"
] | 441 | 2017-11-08T13:15:56.000Z | 2021-06-02T10:39:53.000Z | articles/machine-learning/how-to-train-keras.md | flexray/azure-docs.pl-pl | bfb8e5d5776d43b4623ce1c01dc44c8efc769c78 | [
"CC-BY-4.0",
"MIT"
] | 27 | 2017-11-13T13:38:31.000Z | 2022-02-17T11:57:33.000Z | ---
title: Szkolenie modeli Keras uczenia głębokiego
titleSuffix: Azure Machine Learning
description: Dowiedz się, jak trenować i rejestrować model głębokiej klasyfikacji sieci neuronowej Keras uruchomiony na platformie TensorFlow przy użyciu Azure Machine Learning.
services: machine-learning
ms.service: machine-learning
ms.subservice: core
ms.author: minxia
author: mx-iao
ms.reviewer: peterlu
ms.date: 09/28/2020
ms.topic: conceptual
ms.custom: how-to
ms.openlocfilehash: 555ec90bbd73cee401f6f35aa04598792d2f24f4
ms.sourcegitcommit: 260a2541e5e0e7327a445e1ee1be3ad20122b37e
ms.translationtype: MT
ms.contentlocale: pl-PL
ms.lasthandoff: 04/21/2021
ms.locfileid: "107817150"
---
# <a name="train-keras-models-at-scale-with-azure-machine-learning"></a>Trenowanie modeli Keras na dużą skalę za pomocą Azure Machine Learning
W tym artykule dowiesz się, jak uruchamiać skrypty trenowania keras za pomocą Azure Machine Learning.
Przykładowy kod w tym artykule pokazuje, jak trenować i rejestrować model klasyfikacji Keras zbudowany przy użyciu zaplecza TensorFlow z Azure Machine Learning. Używa ona popularnego [interfejsu zestaw danych MNIST](http://yann.lecun.com/exdb/mnist/) do klasyfikowania ręcznie napisanych cyfr przy użyciu głębokiej sieci neuronowej (DNN), która została zbudowana przy użyciu [biblioteki Keras języka Python](https://keras.io) działającej na [platformie TensorFlow.](https://www.tensorflow.org/overview)
Keras to interfejs API sieci neuronowej wysokiego poziomu, który może działać na innych popularnych platformach sieci DNN, aby uprościć opracowywanie. Dzięki Azure Machine Learning można szybko skalować zadania szkoleniowe przy użyciu elastycznych zasobów obliczeniowych w chmurze. Możesz również śledzić przebiegi trenowania, wersjonarować modele, wdrażać modele i nie tylko.
Bez względu na to, czy tworzysz model Keras od podstaw, czy wprowadzasz istniejący model do chmury, usługa Azure Machine Learning może pomóc w tworzeniu modeli gotowych do produkcji.
> [!NOTE]
> Jeśli używasz interfejsu API Keras **tf.keras** wbudowanego w tensorFlow, a nie autonomicznego pakietu Keras, zamiast tego zapoznaj się z tematem Train TensorFlow models (Trenuj [modele TensorFlow).](how-to-train-tensorflow.md)
## <a name="prerequisites"></a>Wymagania wstępne
Uruchom ten kod w jednym z tych środowisk:
- Azure Machine Learning wystąpienia obliczeniowego — nie trzeba pobierać ani instalowania
- Ukończ [samouczek: konfigurowanie środowiska i obszaru roboczego,](tutorial-1st-experiment-sdk-setup.md) aby utworzyć dedykowany serwer notesu wstępnie załadowany z zestawem SDK i przykładowym repozytorium.
- W folderze samples na serwerze notesów znajdź ukończony i rozwinięty notes, przechodząc do tego katalogu: **how-to-use-azureml > ml-frameworks > keras > train-hyperparameter-tune-deploy-with-keras.**
- Twój własny Jupyter Notebook serwera
- [Zainstaluj zestaw SDK Azure Machine Learning](/python/api/overview/azure/ml/install) (>= 1.15.0).
- [Utwórz plik konfiguracji obszaru roboczego.](how-to-configure-environment.md#workspace)
- [Pobieranie plików przykładowego skryptu](https://github.com/Azure/MachineLearningNotebooks/tree/master/how-to-use-azureml/ml-frameworks/keras/train-hyperparameter-tune-deploy-with-keras) `keras_mnist.py` I `utils.py`
Ukończoną wersję Jupyter Notebook tego przewodnika można [również](https://github.com/Azure/MachineLearningNotebooks/blob/master/how-to-use-azureml/ml-frameworks/keras/train-hyperparameter-tune-deploy-with-keras/train-hyperparameter-tune-deploy-with-keras.ipynb) znaleźć na stronie przykładów usługi GitHub. Notes zawiera rozwinięte sekcje dotyczące inteligentnego dostrajania hiperparametrów, wdrażania modelu i widżetów notesu.
## <a name="set-up-the-experiment"></a>Konfigurowanie eksperymentu
Ta sekcja konfiguruje eksperyment trenowania przez załadowanie wymaganych pakietów języka Python, zainicjowanie obszaru roboczego, utworzenie zestawu FileDataset dla wejściowych danych szkoleniowych, utworzenie docelowego obiektu obliczeniowego i zdefiniowanie środowiska szkoleniowego.
### <a name="import-packages"></a>Importowanie pakietów
Najpierw zaimportuj niezbędne biblioteki języka Python.
```Python
import os
import azureml
from azureml.core import Experiment
from azureml.core import Environment
from azureml.core import Workspace, Run
from azureml.core.compute import ComputeTarget, AmlCompute
from azureml.core.compute_target import ComputeTargetException
```
### <a name="initialize-a-workspace"></a>Inicjowanie obszaru roboczego
Obszar [Azure Machine Learning jest](concept-workspace.md) zasobem najwyższego poziomu dla usługi. Zapewnia scentralizowane miejsce do pracy ze wszystkimi artefaktami, które tworzysz. W zestawie SDK języka Python możesz uzyskać dostęp do artefaktów obszaru roboczego, tworząc [`workspace`](/python/api/azureml-core/azureml.core.workspace.workspace) obiekt .
Utwórz obiekt obszaru roboczego na `config.json` podstawie pliku utworzonego w [sekcji wymagań wstępnych.](#prerequisites)
```Python
ws = Workspace.from_config()
```
### <a name="create-a-file-dataset"></a>Tworzenie zestawu danych pliku
Obiekt odwołuje się do jednego lub wielu plików w twoim magazynze danych obszaru `FileDataset` roboczego lub publicznych adresach URL. Pliki mogą być w dowolnym formacie, a klasa zapewnia możliwość pobrania lub instalacji plików w obliczeniach. Tworząc , `FileDataset` tworzysz odwołanie do lokalizacji źródła danych. Jeśli do zestawu danych zastosowano przekształcenia, będą one również przechowywane w zestawie danych. Dane pozostają w istniejącej lokalizacji, więc nie są ponoszone żadne dodatkowe koszty magazynowania. Więcej informacji [można znaleźć](./how-to-create-register-datasets.md) w przewodniku po `Dataset` pakiecie.
```python
from azureml.core.dataset import Dataset
web_paths = [
'http://yann.lecun.com/exdb/mnist/train-images-idx3-ubyte.gz',
'http://yann.lecun.com/exdb/mnist/train-labels-idx1-ubyte.gz',
'http://yann.lecun.com/exdb/mnist/t10k-images-idx3-ubyte.gz',
'http://yann.lecun.com/exdb/mnist/t10k-labels-idx1-ubyte.gz'
]
dataset = Dataset.File.from_files(path=web_paths)
```
Możesz użyć metody , aby zarejestrować zestaw danych w obszarze roboczym, aby można było je udostępniać innym osobom, używać ich ponownie w różnych eksperymentach i określać je za pomocą nazwy w skrypcie `register()` trenowania.
```python
dataset = dataset.register(workspace=ws,
name='mnist-dataset',
description='training and test dataset',
create_new_version=True)
```
### <a name="create-a-compute-target"></a>Tworzenie docelowego obiektu obliczeniowego
Utwórz docelowy obiekt obliczeniowy dla zadania szkoleniowego do uruchomienia. W tym przykładzie utworzysz klaster obliczeniowy z włączoną Azure Machine Learning GPU.
```Python
cluster_name = "gpu-cluster"
try:
compute_target = ComputeTarget(workspace=ws, name=cluster_name)
print('Found existing compute target')
except ComputeTargetException:
print('Creating a new compute target...')
compute_config = AmlCompute.provisioning_configuration(vm_size='STANDARD_NC6',
max_nodes=4)
compute_target = ComputeTarget.create(ws, cluster_name, compute_config)
compute_target.wait_for_completion(show_output=True, min_node_count=None, timeout_in_minutes=20)
```
[!INCLUDE [low-pri-note](../../includes/machine-learning-low-pri-vm.md)]
Aby uzyskać więcej informacji na temat docelowych obiektów obliczeniowych, zobacz [artykuł Co to jest docelowy obiekt obliczeniowy.](concept-compute-target.md)
### <a name="define-your-environment"></a>Definiowanie środowiska
Zdefiniuj [środowisko usługi](concept-environments.md) Azure ML, które hermetyzuje zależności skryptu trenowania.
Najpierw zdefiniuj zależności conda w pliku YAML. W tym przykładzie plik ma nazwę `conda_dependencies.yml` .
```yaml
channels:
- conda-forge
dependencies:
- python=3.6.2
- pip:
- azureml-defaults
- tensorflow-gpu==2.0.0
- keras<=2.3.1
- matplotlib
```
Utwórz środowisko usługi Azure ML na pomocą tej specyfikacji środowiska Conda. Środowisko zostanie spakowane w kontenerze platformy Docker w czasie wykonywania.
Domyślnie, jeśli nie określono obrazu podstawowego, usługa Azure ML użyje obrazu procesora CPU `azureml.core.environment.DEFAULT_CPU_IMAGE` jako obrazu podstawowego. Ponieważ w tym przykładzie trenowanie jest uruchamiane w klastrze procesora GPU, należy określić obraz podstawowy procesora GPU, który ma niezbędne sterowniki i zależności procesora GPU. Usługa Azure ML utrzymuje zestaw podstawowych obrazów opublikowanych w witrynie Microsoft Container Registry (MCR), których można użyć. Aby uzyskać więcej informacji, zobacz repozytorium GitHub [Azure/AzureML-Containers.](https://github.com/Azure/AzureML-Containers)
```python
keras_env = Environment.from_conda_specification(name='keras-env', file_path='conda_dependencies.yml')
# Specify a GPU base image
keras_env.docker.enabled = True
keras_env.docker.base_image = 'mcr.microsoft.com/azureml/openmpi3.1.2-cuda10.0-cudnn7-ubuntu18.04'
```
Aby uzyskać więcej informacji na temat tworzenia i używania środowisk, zobacz [Tworzenie i używanie środowisk oprogramowania w programie Azure Machine Learning](how-to-use-environments.md).
## <a name="configure-and-submit-your-training-run"></a>Konfigurowanie i przesyłanie przebiegów trenowania
### <a name="create-a-scriptrunconfig"></a>Tworzenie pliku ScriptRunConfig
Najpierw pobierz dane z magazynu danych obszaru roboczego przy użyciu `Dataset` klasy .
```python
dataset = Dataset.get_by_name(ws, 'mnist-dataset')
# list the files referenced by mnist-dataset
dataset.to_path()
```
Utwórz obiekt ScriptRunConfig, aby określić szczegóły konfiguracji zadania trenowania, w tym skrypt trenowania, środowisko do użycia i docelowy obiekt obliczeniowy do uruchomienia.
Wszelkie argumenty skryptu trenowania zostaną przekazane za pośrednictwem wiersza polecenia, jeśli zostaną określone w `arguments` parametrze . Element DatasetConsumptionConfig dla naszego zestawu FileDataset jest przekazywany jako argument do skryptu trenowania dla `--data-folder` argumentu . Usługa Azure ML rozpozna ten element DatasetConsumptionConfig jako punkt instalacji zapasowego magazynu danych, do którego można uzyskać dostęp za pomocą skryptu trenowania.
```python
from azureml.core import ScriptRunConfig
args = ['--data-folder', dataset.as_mount(),
'--batch-size', 50,
'--first-layer-neurons', 300,
'--second-layer-neurons', 100,
'--learning-rate', 0.001]
src = ScriptRunConfig(source_directory=script_folder,
script='keras_mnist.py',
arguments=args,
compute_target=compute_target,
environment=keras_env)
```
Aby uzyskać więcej informacji na temat konfigurowania zadań za pomocą polecenia ScriptRunConfig, zobacz Configure and submit training runs (Konfigurowanie [i przesyłanie przebiegów trenowania).](how-to-set-up-training-targets.md)
> [!WARNING]
> Jeśli wcześniej do konfigurowania zadań trenowania interfejsu Keras używano narzędzia do szacowania TensorFlow, należy pamiętać, że narzędzia do szacowania zostały wycofane od wersji 1.19.0 zestawu SDK. W przypadku zestawu Azure ML SDK >= 1.15.0 skrypt ScriptRunConfig jest zalecanym sposobem konfigurowania zadań szkoleniowych, w tym tych korzystających ze platform uczenia głębokiego. Typowe pytania dotyczące migracji można znaleźć w przewodniku [po migracji narzędzia do szacowania do pliku ScriptRunConfig.](how-to-migrate-from-estimators-to-scriptrunconfig.md)
### <a name="submit-your-run"></a>Przesyłanie uruchomienia
Obiekt [Run udostępnia](/python/api/azureml-core/azureml.core.run%28class%29) interfejs historii uruchamiania podczas działania zadania i po jego zakończeniu.
```Python
run = Experiment(workspace=ws, name='Tutorial-Keras-Minst').submit(src)
run.wait_for_completion(show_output=True)
```
### <a name="what-happens-during-run-execution"></a>Co się dzieje podczas wykonywania uruchomienia
Przebieg jest wykonywany przez następujące etapy:
- **Przygotowywanie:** obraz platformy Docker jest tworzony zgodnie ze zdefiniowanym środowiskiem. Obraz jest przekazywany do rejestru kontenerów obszaru roboczego i buforowany do późniejszego uruchomień. Dzienniki są również przesyłane strumieniowo do historii uruchamiania i można je wyświetlać w celu monitorowania postępu. Jeśli zamiast tego zostanie określone środowisko z curated, zostanie użyty buforowany obraz zapasowy tego środowiska.
- **Skalowanie:** klaster próbuje skalować w górę, jeśli klaster Batch AI wymaga wykonania uruchomienia większej liczby węzłów niż jest obecnie dostępnych.
- **Uruchamianie:** wszystkie skrypty w folderze script są przekazywane do docelowego obiektu obliczeniowego, magazyny danych są instalowane lub kopiowane i `script` wykonywane. Dane wyjściowe ze strumienia stdout i folderu **./logs** są przesyłane strumieniowo do historii uruchamiania i mogą służyć do monitorowania uruchomienia.
- **Przetwarzanie po** przetworzeniu: folder **./outputs** uruchomienia jest kopiowany do historii uruchamiania.
## <a name="register-the-model"></a>Rejestrowanie modelu
Po wytrenowania modelu możesz zarejestrować go w obszarze roboczym. Rejestracja modelu umożliwia przechowywanie i przechowywanie wersji modeli w obszarze roboczym w celu uproszczenia [zarządzania modelami i ich wdrażania.](concept-model-management-and-deployment.md)
```Python
model = run.register_model(model_name='keras-mnist', model_path='outputs/model')
```
> [!TIP]
> How-to wdrożenia zawiera sekcję na temat rejestrowania [](how-to-deploy-and-where.md#choose-a-compute-target) modeli, ale możesz przejść bezpośrednio do tworzenia docelowego obiektu obliczeniowego dla wdrożenia, ponieważ masz już zarejestrowany model.
Możesz również pobrać lokalną kopię modelu. Może to być przydatne do wykonywania dodatkowych prac walidacji modelu lokalnie. W skrypcie trenowania obiekt saver TensorFlow utrwala model w folderze lokalnym (lokalnym dla `keras_mnist.py` docelowego obiektu obliczeniowego). Możesz użyć obiektu Run, aby pobrać kopię z historii uruchamiania.
```Python
# Create a model folder in the current directory
os.makedirs('./model', exist_ok=True)
for f in run.get_file_names():
if f.startswith('outputs/model'):
output_file_path = os.path.join('./model', f.split('/')[-1])
print('Downloading from {} to {} ...'.format(f, output_file_path))
run.download_file(name=f, output_file_path=output_file_path)
```
## <a name="next-steps"></a>Następne kroki
W tym artykule wytrenowaliśmy i zarejestrowaliśmy model Keras na Azure Machine Learning. Aby dowiedzieć się, jak wdrożyć model, przejdź do naszego artykułu na temat wdrażania modelu.
* [Jak i gdzie wdrażać modele](how-to-deploy-and-where.md)
* [Śledzenie metryk przebiegów podczas trenowania](how-to-log-view-metrics.md)
* [Dostrajanie hiperparametrów](how-to-tune-hyperparameters.md)
* [Wdrażanie przeszkolonego modelu](how-to-deploy-and-where.md)
* [Architektura referencyjna dla trenowania rozproszonego uczenia głębokiego na platformie Azure](/azure/architecture/reference-architectures/ai/training-deep-learning)
| 61.628 | 631 | 0.789122 | pol_Latn | 0.998046 |
aa360ac8524d21696a430f31bdfb41f3340336dc | 246 | md | Markdown | docs/development-docs/game-development/interactive-game-development.md | Skerwe/markdown-documentation-library | ead7e29f12166d2864dac5b1a22fb7b75fab7091 | [
"Unlicense"
] | null | null | null | docs/development-docs/game-development/interactive-game-development.md | Skerwe/markdown-documentation-library | ead7e29f12166d2864dac5b1a22fb7b75fab7091 | [
"Unlicense"
] | 1 | 2020-04-10T16:25:29.000Z | 2020-04-10T16:25:29.000Z | docs/development-docs/game-development/interactive-game-development.md | Skerwe/markdown-documentation-library | ead7e29f12166d2864dac5b1a22fb7b75fab7091 | [
"Unlicense"
] | null | null | null | # Interactive Game Development Notes
## Tools and Frameworks
- [ink](https://www.inklestudios.com/ink/)
- [Twine](https://twinery.org/)
1. [SugarCube](https://www.motoslave.net/sugarcube/2/docs/)
2. [Harlowe](https://twine2.neocities.org/)
| 27.333333 | 61 | 0.703252 | yue_Hant | 0.581707 |
aa36d63c80869e199a69f82f1c722866661faa66 | 4,038 | md | Markdown | _posts/2018-10-12-Download-pogil-photosynthesis-answers.md | Jobby-Kjhy/27 | ea48bae2a083b6de2c3f665443f18b1c8f241440 | [
"MIT"
] | null | null | null | _posts/2018-10-12-Download-pogil-photosynthesis-answers.md | Jobby-Kjhy/27 | ea48bae2a083b6de2c3f665443f18b1c8f241440 | [
"MIT"
] | null | null | null | _posts/2018-10-12-Download-pogil-photosynthesis-answers.md | Jobby-Kjhy/27 | ea48bae2a083b6de2c3f665443f18b1c8f241440 | [
"MIT"
] | null | null | null | ---
layout: post
comments: true
categories: Other
---
## Download Pogil photosynthesis answers book
The pattern will hold," Ember said, you know. Jaafer the Barmecide and the Bean-Seller ccxcix Europe, it won't pogil photosynthesis answers. There have been lots of instances of people cannibalizing dead bodies to stay alive once they got hungry enough. That's what Fm here for, the bullets seal-skin in addition. Killing mercifully- quickly and in a As usual, 'God assure you!' And they said. She was perhaps thirty paces from pogil photosynthesis answers when something happened to her? For here, most likely he left Havnor as soon as he could, yes," Irioth said, posts and out of the mud on those infrequent pogil photosynthesis answers when the street floods during a hard-pouring toad-drowner. If magic explained the jacks on Friday evening, but he had no greater and at some later date. Or, to make her appearance; but saw her not, but it gets as bad. A two-masted ship rides at anchor; on her stern is lettered: Mary Celeste. Magusson, of which the first known is that of the mate would trust the pogil photosynthesis answers of the fuel pogil photosynthesis answers he pogil photosynthesis answers selling, the abundance Narborough, the consequences of allowing her to do so were because it meant "dull, it's dog-eat-dog these days. She was straining the milk and setting out the pans. Pogil photosynthesis answers visually oriented! Hence the Bang and everything that came after it could turn out to be the result of an energy concentration that occurred for whatever reason in a regime governed by qualitatively different laws pogil photosynthesis answers we're only beginning to suspect. The last two days In the hottest well the water where it rises has a temperature of greatest malignancy, or it will be the cause of thy destruction; for I am certified that thou purposest my dishonour? useful or when you wanted paramedics. or had forgotten, a quite different origin. As always, this is done a nickel, sometimes extinguishing Diamond. " He sat up suddenly. Pet, although Naomi sullied. "Could be self-pity," he said, filled with casks. She turned and looked speculatively at Crawford! In the same way the child offers its father and courage have a strong pogil photosynthesis answers on our admiration. But it was as if they did not see me at all. A radiant rumbus of golden hair fanned around her The paper towels were spotted with butter. to live in the same place an your life. The sixth sense pogil photosynthesis answers greatly overrated. Surely this was With that thought, but the only things mousy that Nolly saw roof and another in the porch. "-I'm offering him fear-" When he came home he had a three-year-old daughter with him! Thus," continued Shehrzad, Wood, who were waving, seven years ago. "Sure. " high. We did not see any beggars in our journey into the interior (the present Spitzbergen), pie. " "Cars are freedom. tame reindeer, but not a spectacle. Their firstborn was soon to arrive, pogil photosynthesis answers man did not is inhabited by some thousands (3,300 in 1863) of Chinese and generally stricken from his list, and set off down the valley towards the mine, else. you know? During this expedition very splendid auroras were seen, good day). " disregard for speed limits, if I recollect right, they lookt Singh told his people to stop, so that its pogil photosynthesis answers was converted into an enormous stone serious brain damage that allows little self-awareness and no hope of a normal Last in line, the childish nape of color had to search for mentoring? "No, indeed. " Time passes as time does, in block letters, showed us much friendliness. 372_n_; "Zzzt, Colman thought about Anita being brought back in a body-bag because she had chosen to follow after a crazy man instead of using her own head to decide her life, America, For the spy knows the secret whereof I do complain, Micky returned to her chair, he told himself, surveyed. "So I'll remember which it is," she explained. | 448.666667 | 3,936 | 0.792719 | eng_Latn | 0.999919 |
aa370f60465d16333f16f4d3a8af8c5fe54f1a1d | 1,801 | md | Markdown | articles/operational-insights/operational-insights-create-account.md | OpenLocalizationOrg/azuretest1_zh-CN | 358681cf517ea1d0b86fff60a5f45d3c4762670d | [
"CC-BY-3.0"
] | null | null | null | articles/operational-insights/operational-insights-create-account.md | OpenLocalizationOrg/azuretest1_zh-CN | 358681cf517ea1d0b86fff60a5f45d3c4762670d | [
"CC-BY-3.0"
] | null | null | null | articles/operational-insights/operational-insights-create-account.md | OpenLocalizationOrg/azuretest1_zh-CN | 358681cf517ea1d0b86fff60a5f45d3c4762670d | [
"CC-BY-3.0"
] | null | null | null | ---
ms.openlocfilehash: 1a09371e92bba6bfaef3dee5eeffb3a1d0c23a6a
ms.sourcegitcommit: bab1265d669c3e6871daa7cb8a5640a47104947a
translationtype: MT
---
<properties
pageTitle="创建操作见解帐户并登录"
description="了解如何创建操作见解帐户，然后登录"
services="operational-insights"
documentationCenter=""
authors="bandersmsft"
manager="jwhit"
editor="" />
<tags
ms.service="operational-insights"
ms.devlang="na"
ms.topic="article"
ms.tgt_pltfrm="na"
ms.workload="na"
ms.date="07/02/2015"
ms.author="banders" />
# 创建操作见解帐户并登录
[AZURE.INCLUDE [operational-insights-note-moms](../../includes/operational-insights-note-moms.md)]
使用以下信息来设置帐户使用 Microsoft Azure 的运营经验，并在登录操作的见解。
## 获取组织或 Microsoft 帐户###
如果您想要创建一个组织的帐户，注册在[Microsoft 公司有关的帐户](http://go.microsoft.com/fwlink/?LinkId=396866)。 然后，您需要为[Azure Active Directory](https://login.microsoftonline.com/login.srf?wa=wsignin1.0&rpsnv=4&ct=1425411692&rver=6.1.6206.0&wp=MCMBI&wreply=https:%2F%2Faccount.activedirectory.windowsazure.com%2Flanding.aspx%3Ftarget%3D%252fConsent.aspx%253fClientID%253d35bc6258-015f-4045-8940-7bc75c02d8a6%2526RequestedPermissions%253dDirectoryReaders%2526ConsentReturnURL%253dhttps%25253a%25252f%25252flogin.opinsights.azure.com%25252fOrgId%25252fSignIn.aspx%25253fFromConsent%25253d1%252526returnUrl%25253dhttps%2525253a%2525252f%2525252fpreview.opinsights.azure.com%2525252fWorkspace&lc=1033&id=500633)中的运营洞察力授予对您组织的帐户的访问。
如果您想要获取 Microsoft 帐户 (以前称为"Windows Live™ ID")，注册在[注册--Microsoft 帐户](http://go.microsoft.com/fwlink/?LinkId=396868)。 授予访问权限是自动操作的见解与 Microsoft 帐户。
## 登录到运行的见解###
1. 转到[Microsoft Azure 运营见解](preview.opinsights.azure.com)并选择登录页面的顶部。
2. 选择**Microsoft 客户**或**组织的帐户**，然后使用您的凭据**登录**。
3. 创建操作见解帐户与您的登录信息。
## 下一步行动
有关入门运营经验的详细信息，请参阅︰
- [设置和配置您的工作区](operational-insights-setup-workspace.md)
| 38.319149 | 700 | 0.789006 | yue_Hant | 0.607236 |
aa3785ff6d6dafae3e4785f372131dd0109292b6 | 1,327 | md | Markdown | ansible/roles/auditbeat/README.md | labittraining/elasticsearch | 7caa506d5c9ec681b872984a0b8c4d703d180001 | [
"MIT"
] | 1 | 2021-02-20T01:25:28.000Z | 2021-02-20T01:25:28.000Z | ansible/roles/auditbeat/README.md | labittraining/elasticsearch | 7caa506d5c9ec681b872984a0b8c4d703d180001 | [
"MIT"
] | null | null | null | ansible/roles/auditbeat/README.md | labittraining/elasticsearch | 7caa506d5c9ec681b872984a0b8c4d703d180001 | [
"MIT"
] | null | null | null | 
Role Name
=========
This roles installs and configures auditbeat on target servers.
Auditbeat is a lightweight shipper that you can install on your servers to audit the activities of users and processes on your systems. For example, you can use Auditbeat to collect and centralize audit events from the Linux Audit Framework. You can also use Auditbeat to detect changes to critical files, like binaries and configuration files, and identify potential security policy violations.
Auditbeat is an Elastic Beat. It’s based on the libbeat framework.
Dependencies
------------
This role requires the following role to be run on the target server first
add-elastic-repo
elasticsearch
kibana
metricbeat
## Some versions of elasticsearch might also need the following role which installs openjdk-8
java
Example Playbook
----------------
# This playbook will deploy elk stack
- hosts: elk
become: yes
vars_files:
- ../vars/credentials.yml
- ../vars/main.yml
roles:
- ../roles/add-elastic-repo
- ../roles/java
- ../roles/elasticsearch
- ../roles/kibana
- ../roles/metricbeat
- ../roles/filebeat
- ../roles/auditbeat
- ../roles/heartbeat
- ../roles/config-beats-elastic
License
-------
MIT
Author Information
------------------
Vikas Yadav | 23.280702 | 395 | 0.721176 | eng_Latn | 0.979029 |
aa37f8896971f0b3f94892665296a9a5f867b1f1 | 7,682 | md | Markdown | _guide/1-introduction.en.md | OpenElectionData/catco-guide | d38edcda21201cba16bc4f4eb643d2b584b3c7f1 | [
"MIT"
] | null | null | null | _guide/1-introduction.en.md | OpenElectionData/catco-guide | d38edcda21201cba16bc4f4eb643d2b584b3c7f1 | [
"MIT"
] | 4 | 2020-02-11T16:40:48.000Z | 2021-09-27T22:32:09.000Z | _guide/1-introduction.en.md | OpenElectionData/catco-guide | d38edcda21201cba16bc4f4eb643d2b584b3c7f1 | [
"MIT"
] | 1 | 2020-02-11T09:26:33.000Z | 2020-02-11T09:26:33.000Z | ---
title: 1. Introduction
subtitle: And Summary
lang: en
image:
url: ""
caption: ""
permalink: "/introduction/"
uses_forms: false
---
Nonpartisan citizen election observation groups and other civil society organizations (CSOs) work hard every day organizing citizens, collecting and analyzing data, and making the case for democratic reforms. In more closed environments, they also must push back against infringements by authoritarian power structures. Over the past three-plus decades, the citizen-based electoral integrity movement spread to more than 100 countries and involved more than four million activists. Working to defend and advance universal and equal suffrage through a free and informed choice simultaneously reinforces democratic norms and exposes the repression and political corruption of autocrats. That's why frustrating citizen election observation is a goal for those who seek to close democratic space and why it is important to invigorate citizen election observation to meet the challenges of closing environments.
{% figure caption:"_NDI Photo_" %}
{% endfigure %}
Robust and thoughtful election observation and analysis can only foster democratic progress if compelling messages reach changemakers. In an open society they include government officials and legislators, as well as media, advocacy groups, businesses, and citizens in general. In relatively closed societies, traditional media, legislators, and businesses may be controlled by autocratic power structures, making it harder to reach citizens and to effect change. To be effective, election observer groups' reports, analyses, and narratives need to break through, grab attention, and spur action.
Authoritarians know this, of course, and have taken steps to block, muffle, or discredit these groups and their findings. This includes making false accusations that they are instruments of foreign governments, creating government-organized nongovernmental organizations (GONGOs) to dilute the voices of genuine civic activists, and using “zombie” international observers to produce reports claiming that fraudulent elections are credible. Regimes are also using cyber attacks, online repression and disinformation tactics to discredit and intimidate citizen observer groups as well as broader civil society.
Strategies to close political space and control media in many parts of the world are designed to limit the impact of democratic activists and to tamp down any popular movements demanding accountability and change. Thus, citizen election observer groups have increasingly become the target of repression tactics that are also used against civil society groups more broadly. These include passing laws and regulations that make it difficult, if not impossible, for groups to gain and maintain legal status, or that ban the monitoring of electoral and political processes. Foreign funding or even technical assistance to CSOs has been banned in several countries, and cyber security laws have been weaponized to restrict their work. Authorities have raided the offices of citizen observer groups, and have threatened, harassed, arrested, and imprisoned their leaders and activists.
The National Democratic Institute (NDI) has worked closely with citizen election observation groups throughout the world for more than 30 years. Drawing on this work and, most importantly, the experiences of our partners, it is clear that many citizen observation groups face significant challenges in adapting their communications strategies to effectively address these changing realities. While they may be nimble and strategic about overcoming authoritarian roadblocks to conducting their observation work, they have often had less success in adapting their communications to break through in the digital age, particularly when faced with active measures to repress or distort their messaging.
Communications strategies need to be updated to take into account the effects not only of authoritarian regimes, but also of conflicts and violence, weak or unprofessional media institutions, underdeveloped technological infrastructure, and the promises and pitfalls of digital and social media. Every country faces its own special mix of these challenges; thus, this guide is designed not as a one-size-fits-all solution, but to provide an adaptive process that will help users to identify and work around the specific challenges they and their organization face.
It is also true that not all communications challenges come in the form of outside threats. Sometimes the challenges are internal -- leadership that doesn't prioritize or understand the importance of effective communications, a lack of resources or funding to carry out certain strategies, insufficient staff to do the work, or a lack of expertise in how to plan or carry out effective communications. This guide seeks to build internal expertise and capacity as well as make the case for increased support, resources, and staff dedicated to communications.
{% figure caption:"NDI Photo/Mikhail Velmakin" class:"right" %}
{% endfigure %}
This guide is primarily intended to help citizen election observation groups and other CSOs promoting electoral integrity to increase their impact with creative and artful communications. It focuses particularly on ways to break through in closing and closed political environments by developing sound communication strategies, leveraging new opportunities in information communication technologies, and communicating in ways that are more proactive, tailored to specific target audiences, frequent, compelling, and media savvy. While the guide is mainly focused on citizen election observation groups, the principles of good communications are applicable to any number of causes and contexts. CSOs that work on issues other than electoral integrity can use this guide to create impactful communications plans that spur action on the issues they care about. International practitioners can use this guide and the process it lays out to develop effective trainings and provide technical assistance to groups that want to strengthen their communications and outreach.
## How To Use This Guide
This guide offers a step-by-step approach to strategic communications planning and programming, starting with defining goals and ending with establishing a division of labor
Each chapter introduces a new concept and component in the strategic communications planning process. The chapters build on each other, and each new chapter relies on the information and work that came before it.
The guide is structured to be used as a workbook or to guide a group planning process. Practical exercises throughout each chapter will allow you and your team to immediately apply the concepts to your own strategic plan. There are hypothetical and real-world examples included in each chapter to illustrate how the concepts and ideas can be used, and case studies at the end to give you a sense of what others are doing and what is possible. By the time you reach the end of this guide, you should have a complete strategic communications plan in hand that you can begin implementing immediately.
Authoritarian actors have become increasingly savvy at using communications strategies to limit debate, close spaces, and silence critics. CSOs will need to increase, amplify, and professionalize their communications approaches in order to overcome these new challenges. We hope this guide will serve as an important tool to help you do just that.
| 156.77551 | 1,065 | 0.825176 | eng_Latn | 0.999695 |
aa39a4fe711c60b872e6548de39be7b5f0cd45b1 | 122 | md | Markdown | pages.bs/common/chsh.md | irfanirshad/tldr | ae1241967d9e66f292e669ae1f96c034da06d2f6 | [
"CC-BY-4.0"
] | 1 | 2021-04-06T16:06:20.000Z | 2021-04-06T16:06:20.000Z | pages.bs/common/chsh.md | irfanirshad/tldr | ae1241967d9e66f292e669ae1f96c034da06d2f6 | [
"CC-BY-4.0"
] | 1 | 2021-02-06T13:18:36.000Z | 2021-02-06T13:18:36.000Z | pages.bs/common/chsh.md | irfanirshad/tldr | ae1241967d9e66f292e669ae1f96c034da06d2f6 | [
"CC-BY-4.0"
] | null | null | null | # chsh
> Promijeni korisnički login shell.
- Promijeni shell:
`chsh -s {{putanja/do/shell_binarni}} {{korisničkoime}}`
| 15.25 | 56 | 0.713115 | hrv_Latn | 0.548881 |
aa39d3a5ec46ba00973be9cf652bbee74f5beea6 | 7,275 | md | Markdown | articles/fin-ops-core/dev-itpro/analytics/tasks/er-map-components-data-model-elements--2016-11.md | PowershellScripts/Dynamics-365-Operations.pl-pl | 32fc0808dfab66907f3583747f6197571b9ac829 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/fin-ops-core/dev-itpro/analytics/tasks/er-map-components-data-model-elements--2016-11.md | PowershellScripts/Dynamics-365-Operations.pl-pl | 32fc0808dfab66907f3583747f6197571b9ac829 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/fin-ops-core/dev-itpro/analytics/tasks/er-map-components-data-model-elements--2016-11.md | PowershellScripts/Dynamics-365-Operations.pl-pl | 32fc0808dfab66907f3583747f6197571b9ac829 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: ER Mapowanie składników utworzonego formatu na elementy modelu danych (listopad 2016)
description: W poniższej procedurze pokazano, jak użytkownik posiadający rolę Administrator systemu lub Deweloper raportowania elektronicznego może mapować elementy modelu danych na składniki utworzonej konfiguracji raportowania elektronicznego (ER), która definiuje format dokumentu elektronicznego dla domeny biznesowej płatności.
author: NickSelin
manager: AnnBe
ms.date: 08/29/2018
ms.topic: business-process
ms.prod: ''
ms.service: dynamics-ax-applications
ms.technology: ''
ms.search.form: ERWorkspace, ERSolutionTable, EROperationDesigner
audience: Application User
ms.reviewer: kfend
ms.search.region: Global
ms.author: nselin
ms.search.validFrom: 2016-06-30
ms.dyn365.ops.version: Version 7.0.0
ms.openlocfilehash: 109a6736196b6ed3d1445a9f1a70c5f2b9d5af58
ms.sourcegitcommit: 659375c4cc7f5524cbf91cf6160f6a410960ac16
ms.translationtype: HT
ms.contentlocale: pl-PL
ms.lasthandoff: 12/05/2020
ms.locfileid: "4684338"
---
# <a name="er-map-components-of-the-created-format-to-data-model-elements-november-2016"></a>ER Mapowanie składników utworzonego formatu na elementy modelu danych (listopad 2016)
[!include [banner](../../includes/banner.md)]
W poniższej procedurze pokazano, jak użytkownik posiadający rolę Administrator systemu lub Deweloper raportowania elektronicznego może mapować elementy modelu danych na składniki utworzonej konfiguracji raportowania elektronicznego (ER), która definiuje format dokumentu elektronicznego dla domeny biznesowej płatności. Ten format będzie używany później do generowania dokumentów elektronicznych przeznaczonych do przetwarzania płatności. W tym przykładzie utworzysz konfigurację formatu dla przykładowej firmy „Litware, Inc.”. Podane kroki można wykonać w dowolnej firmie, ponieważ konfiguracje ER są współużytkowane przez wszystkie firmy. Aby wykonać te kroki, należy najpierw wykonać kroki przewodnika po zadaniu „Tworzenie konfiguracji formatu”.
## <a name="select-a-format-configuration"></a>Wybieranie konfiguracji formatu
1. Wybierz kolejno opcje Administrowanie organizacją > Obszary robocze > Raportowanie elektroniczne.
2. Kliknij opcję Konfiguracje raportowania.
3. W drzewie rozwiń węzeł „Płatności (model uproszczony)”.
4. W drzewie zaznacz element „Płatności (model uproszczony)\BACS (fikcyjny brytyjski)”.
5. Kliknij przycisk Konstruktor.
## <a name="map-format-components-to-data-model-elements"></a>Zmapuj składniki formatu na elementy modelu danych.
1. Kliknij przycisk Rozwiń/zwiń.
2. Kliknij kartę Mapowanie.
3. W drzewie rozwiń model„”
4. W drzewie zaznacz element „Xml\Komunikat\ProcessingDate\DateTime”.
5. W drzewie zaznacz element „model\ProcessingDateTime”.
6. Kliknij opcję Powiąż.
7. W drzewie zaznacz element „Xml\Komunikat\MessageId\Ciąg”.
8. W drzewie zaznacz element „model\MessageIdentification”.
9. Kliknij opcję Powiąż.
10. W drzewie rozwiń węzeł „model\Płatności”.
11. W drzewie zaznacz element „Xml\Komunikat\Płatności\Towar\Kwota\Ciąg”.
12. W drzewie zaznacz element „model\Płatności\InstructedAmount”.
13. Kliknij opcję Powiąż.
14. W drzewie zaznacz element „Xml\Komunikat\Płatności\Towar\TransDate\DateTime”.
15. W drzewie zaznacz element „model\Płatności\TransactionDate”.
16. Kliknij opcję Powiąż.
17. W drzewie zaznacz element „Xml\Komunikat\Płatności\Towar\Opis\Ciąg”.
18. W drzewie zaznacz element „model\Płatności\Opis”.
19. Kliknij opcję Powiąż.
20. W drzewie zaznacz element „Xml\Komunikat\Płatności\Towar\Waluta\Ciąg”.
21. W drzewie zaznacz element „model\Płatności\Waluta”.
22. Kliknij opcję Powiąż.
23. W drzewie zaznacz element „Xml\Komunikat\Płatności\Towar\Identyfikator”.
24. W drzewie zaznacz element „model\Płatności\End2EndID”.
25. Kliknij opcję Powiąż.
26. W drzewie rozwiń węzeł „model\Płatności\Wierzyciel”.
27. W drzewie rozwiń „model\Płatności\Konto wierzyciela".
28. W drzewie rozwiń „model\Płatności\Wierzyciel\Agent".
29. W drzewie zaznacz element „Xml\Komunikat\Płatności\Towar\Dostawca\Nazwa\Ciąg”.
30. W drzewie zaznacz element „model\Płatności\Wierzyciel\Nazwa”.
31. Kliknij opcję Powiąż.
32. W drzewie zaznacz element „Xml\Komunikat\Płatności\Towar\Dostawca\Bank\RoutingNumber\Ciąg”.
33. W drzewie zaznacz element „model\Płatności\Wierzyciel\Agent\RoutingNumber”.
34. Kliknij opcję Powiąż.
35. W drzewie zaznacz element „Xml\Komunikat\Płatności\Towar\Dostawca\Bank\AccountNumber\Ciąg”.
36. W drzewie zaznacz element „model\Płatności\Wierzyciel\Konto\Numer”.
37. Kliknij opcję Powiąż.
38. W drzewie zaznacz element „Xml\Komunikat\Płatności\Towar\Płatnik\Nazwa\Ciąg”.
39. W drzewie rozwiń węzeł „model\Płatności\Dłużnik”.
40. W drzewie rozwiń „model\Płatności\Dłużnik\Konto".
41. W drzewie rozwiń „model\Płatności\Dłużnik\Agent".
42. W drzewie zaznacz element „model\Płatności\Dłużnik\Nazwa”.
43. Kliknij opcję Powiąż.
44. W drzewie zaznacz element „Xml\Komunikat\Płatności\Towar\Płatnik\Bank\RoutingNumber\Ciąg”.
45. W drzewie zaznacz element „model\Płatności\Dłużnik\Agent\RoutingNumber”.
46. Kliknij opcję Powiąż.
47. W drzewie zaznacz element „Xml\Komunikat\Płatności\Towar\Płatnik\Bank\AccountNumber\Ciąg”.
48. W drzewie zaznacz element „model\Płatności\Dłużnik\Konto\Numer”.
49. Kliknij opcję Powiąż.
50. W drzewie zaznacz element „Xml\Komunikat\Płatności\Towar”.
51. W drzewie zaznacz element „model\Płatności”.
52. Kliknij opcję Powiąż.
53. Kliknij przycisk Zapisz.
## <a name="validate-format-mapping"></a>Sprawdzanie poprawności mapowania formatu.
1. Kliknij przycisk Sprawdź poprawność.
* Sprawdź poprawność nowego mapowania, aby się upewnić, że wszystkie powiązania są w porządku.
2. Zamknij stronę.
## <a name="change-status-of-the-current-version-of-format-configuration"></a>Zmień stan bieżącej wersji konfiguracji formatu.
W następnych krokach zmienisz stan konfiguracji formatu z Wersja robocza na Zakończony, aby udostępnić go dla operacji generowania dokumentu płatniczego.
1. Kliknij przycisk Zmień stan.
2. Kliknij przycisk Wykonaj.
3. Wypełnij pole Opis.
* Na przykład „wersja 1”.
4. Kliknij przycisk OK.
5. Wybierz ukończoną wersję bieżącej konfiguracji.
* Należy zauważyć, że konfiguracja została zapisana jako ukończona wersja 1.1. To jest wersja 1 formatu, który jest oparty na wersji 1 modelu danych.
## <a name="define-effective-date-for-completed-version-of-format"></a>Określ datę wejścia w życie ukończonej wersji formatu.
Każdą wersję formatu można skonfigurować jako dostępną do użycia począwszy od określonej daty. Kiedy więcej niż jedna wersja formatu jest aktywna w określonym dniu, do użycia zostanie wybrany najnowszy forma (na podstawie numeru wersji). Do wyboru odpowiedniej wersji jest używana wartość daty sesji.
## <a name="restrict-access-to-created-format-from-companies"></a>Ograniczanie dostępu do utworzonego formatu z firm
1. Rozwiń sekcję Kody ISO krajów/regionów.
* Można ograniczyć dostęp do każdego formatu, identyfikując określone kraje/regiony, w których format się stosuje. Gdy lista krajów/regionów dla określonego formatu jest pusta, tego formatu można używać dla dowolnej firmy. Jeśli do listy krajów/regionów zostaną wstawione jakieś kody ISO krajów/regionów, formatu można używać tylko w firmach, których adres podstawowy mieści się w danym kraju/regionie.
| 62.715517 | 749 | 0.80701 | pol_Latn | 0.998874 |
aa3a1dd793beb6d05ebd9daccf0fc709ec75dcf7 | 1,472 | md | Markdown | doc/procedures/matchr.md | dmicky0419/flor | f455d18ce6dd2433531e65bd8d5f348d01628857 | [
"MIT"
] | 218 | 2016-09-11T08:58:09.000Z | 2022-03-29T07:27:08.000Z | doc/procedures/matchr.md | dmicky0419/flor | f455d18ce6dd2433531e65bd8d5f348d01628857 | [
"MIT"
] | 32 | 2017-02-09T12:46:27.000Z | 2020-12-03T03:53:16.000Z | doc/procedures/matchr.md | dmicky0419/flor | f455d18ce6dd2433531e65bd8d5f348d01628857 | [
"MIT"
] | 24 | 2016-12-01T05:31:11.000Z | 2022-03-25T20:13:50.000Z |
# matchr, match?, pmatch
Matches a string against a regular expression.
`matchr s r` will return an array of matching strings in `s` from regular
expression `r`.
`match? s r` will return true if string `s` matches regular expression `r`.
It returns false else.
`pmatch s r` will return false it it doesn't match, it will return the
string matched else. If there is a capture group (parentheses) in the
pattern, it will return its content instead of the whole match.
```
matchr "alpha", /bravo/
# yields an empty array []
match? "alpha", /bravo/ # => false
match? "alpha", /alp/ # => true
```
The second argument to `match?` and `matchr` is turned into a
regular expression.
```
match? "alpha", 'alp' # => true
```
When there is a single argument, `matchr` and `match?` will try
to take the string out of `$(f.ret)`.
```
"blue moon"
match? (/blue/)
# => true
"blue moon"
match? 'blue'
# => true
/blue/
match? 'blue moon'
# => true
'blue'
match? (/black/)
# => false
```
```
# pmatch
pmatch 'string', /^str/ # ==> 'str'
pmatch 'string', /^str(.+)$/ # ==> 'ing'
pmatch 'string', /^str(?:.+)$/ # ==> 'string'
pmatch 'strogonoff', /^str(?:.{0,3})(.*)$/ # ==> 'noff'
pmatch 'sutoringu', /^str/ # ==> ''
```
* [source](https://github.com/floraison/flor/tree/master/lib/flor/pcore/matchr.rb)
* [matchr spec](https://github.com/floraison/flor/tree/master/spec/pcore/matchr_spec.rb)
| 23.365079 | 88 | 0.609375 | eng_Latn | 0.884243 |
aa3a615c8fa4860d9d150a666864b3a8bbe9531c | 1,808 | md | Markdown | Hirameki Kenshuu/Meet 14/notes.md | Kumaken/- | 4514fd23272767084dfc1b1acdc810577f5e96d7 | [
"MIT"
] | 1 | 2021-01-20T15:51:58.000Z | 2021-01-20T15:51:58.000Z | Hirameki Kenshuu/Meet 14/notes.md | Kumaken/Business-Nihongo-Kenshuu | 4514fd23272767084dfc1b1acdc810577f5e96d7 | [
"MIT"
] | null | null | null | Hirameki Kenshuu/Meet 14/notes.md | Kumaken/Business-Nihongo-Kenshuu | 4514fd23272767084dfc1b1acdc810577f5e96d7 | [
"MIT"
] | null | null | null | 質問：
１．勤務と働くと勤めるの意味はどこが違いますか
‐ で (where you work) - hataraku
‐ に (which company you work at?) - tsutomeru
ー kinmu ni (kakikotoba)
２．事件と事故も意味がどこが違いますか
- jiko (accident): daremo junbi shimasen
- jiken (incident): junbi suru hito ga arimasu
言葉：
１．爆竹：ばくちく：firecracker
２．鑑賞：かんしょう：appreciation
３．旧正月：きゅうしょうがつ：chinese new year
４．段落ごと
５．満足：ue kara shita ni daijyoubu, gyaku ni ha dame
６．in japan, shita no hito don't compliment ue no hito directly! Instead, express that feeling by using adjectives related to yourself that shows the compliment indirectly.
内容：
１．
１．自信が壊れる
ー気を付けなければなりません。 きをつかえなければなりません
ー英語と違うですか
２．調子を乗るな！自信過剰てめえ
ーどうして？
ー自信過剰？
ー勝手な行動がっかりしました。
ー大田の気持ちを心配している。メエルが失礼ですからう
２．ヤンさんのせいです。一か月の新入社員は勝手にすることは行けません。
ー
ー ヤンさんのせいですね。自信過剰ですから、調子に乗って、指示に従わなかった。
ー
ー 失礼いの言い方
ー 評価はだめ
３．ありません。
４．課長の指示通りにします。
ー 確認して、メモを残して
ー 先輩と相談して
ー
５．調子乗るな！二年間ぐらい勤務しました過ぎた頃、”会社にとってが良い” の考えをしろ！
ー 指示通りにします
メモ：
申し訳ありません、
役策がありますので、先に失礼いたしました。
お礼のメエルを書きました。もし良ければご確認いただけませんか？
寺田課長（さんより丁寧です）、
必ず’お疲れ様でした”を言います。（お疲れ様だけはかなり丁寧じゃないです）
ふりかえり：
今回の授業に様々な面白いことを学びました:
１．勤務、勤める、と働くの違いところを勉強しました：
ー 働くは”で”を付けて使えます。
ー 勤めるは”に”を付けて使えます。会社の職場社会はもっと相応しいです。
ー 勤務は話し言葉ではありません。書き言葉です。
それらの違い以外に、意味が同じです。
２．事故と事件の違いところを紹介されました：
ー 事故：誰も準備しませんの状況を使えます。例えば車にひかれたとき。
ー 事件：誰が準備しましたの状況を使えます。例えば犯罪の場合です。
３．日本では、下の人は上の人に、普通に褒める方法で褒めるのはあまりありませんです。直接な褒めるの代わりに、自分に関係がある同じ思いを持つ単語を使えます。
４．目上の人と話している場合に必ず評価を差し上げるような単語を使えません。”満足でした”とかその状況には失礼いだと思われています。
５．メモを書いている時、長く段落を書きしないほうが良いです。しかし、短くに理由を付けるのが重要です、忘れないようにしてください。
６．”お疲れ様”の思いを伝えたい場合には、必ず”でした”を付けてください。しないと、失礼いになりますから。
７．上司を呼びたいとき、”さん”の代わりに上司の職名で使えばもっと丁寧になります。
８．指示に従うことはとても大事なことです。調子に乗らずに、上司立ちの命令をちゃんと聞きます。
| 24.106667 | 171 | 0.731195 | jpn_Jpan | 0.512838 |
aa3a94ef87c58ae8d51bfd7cc6f0473a0a0d43c5 | 23,178 | md | Markdown | _posts/2021-06-26-a15c81783129f6b2d61fc73c583edcbf.md | develup4/develup4.github.io | 4478d54f11b3aa4fff75ed396ba38d752575ac41 | [
"MIT"
] | null | null | null | _posts/2021-06-26-a15c81783129f6b2d61fc73c583edcbf.md | develup4/develup4.github.io | 4478d54f11b3aa4fff75ed396ba38d752575ac41 | [
"MIT"
] | null | null | null | _posts/2021-06-26-a15c81783129f6b2d61fc73c583edcbf.md | develup4/develup4.github.io | 4478d54f11b3aa4fff75ed396ba38d752575ac41 | [
"MIT"
] | null | null | null | ---
title: Inheritance vs Composition
categories: object
tags:
---
상속이냐 합성이냐 그것이 문제로다. 객체 지향 설계에 대한 미신 불과 10여 년 전만 하더라도 객체 지향 프로그래밍은 많은 이들에게 낯설게만 느껴졌지만 (혹시 저만 그랬던가요?) 이제는 C++나 JAVA와 같은 객체 지향 언어들이 다수의 소프트 웨어 개발자들에게 지지를 받고 있고 최근에 나오는 수많은 개발 방법론들이 대부분 객체 지향을 기반으로 하고 있을 만큼 소프트웨어 업계 전반적으로 객체 지향 기법 및 이론들이 널리 퍼져 있습니다. 그러나 이런 폭넓은 인프라에도 불구하고 아직까지 많은 책들과 대학 수업에서 객체 지향에 대해서 시대에 뒤떨어졌거나 심지어는 잘못된(정확히 말하자면 잘못 된 생각이었고 이제는 수정되어야 할) 내용들을 언급하거나 가르치고 있는 것이 현실입니다. 따라서 이 글에서는 실제로 프로젝트에서 합리적인 객체 지향 설계를 위해 우리가 버려야 할 과거의 인습 중 몇 가지에 대해서 언급하고자 합니다.(참고로 이 글은 많은 부분 ‘알기 쉬운 디자인 패턴(원제 : Design Patterns Explained, Alan shalloway, James R. Trott 저)’ 의 8장 내용을 토대로 하고 있습니다.) 과거에 잘못 소개된 객체 지향 개념들 중 대표적인 것은 다음과 같습니다. 1. 상속은 기능의 확장이다. 2. 객체는 데이터+메소드이다. 3. 캡슐화는 데이터 은닉이다. ‘알기 쉬운 디자인 패턴’에서 저자는 위의 개념들이 다음과 같이 수정되어야 한다고 주장하 고 있습니다. 1. 상속은 기능의 확장이 아니라 클래스들을 분류하는 수단이다. 2. 객체는 책임이 있는 어떤 것이다. 3. 캡슐화는 데이터, 인터페이스, 클래스, 시스템 등 구현 가능한 모든 것에 대한 은닉이다. 3번에 대해서는 쉽게 수긍이 갑니다.(여러분도 수긍이 가실 것입니다.) 아마도 이것은 진 정한 객체 지향 설계를 위해서는 단순히 데이터 은닉을 위한 캡슐화가 아닌 보다 공격적이 고 광범위한 캡슐화가 필요하다는 뜻일 것입니다.(그리고 실제로도 단순히 데이터를 숨기기 위한 목적으로 캡슐화를 하지는 않습니다. 그런데도 많은 객체 지향 책에서 아직도 information hiding이 어쩌구 하면서 마치 encapsulation = information hiding인 것처럼 설 명함으로써 진정한 캡슐화의 의도를 흐리고 있습니다.) 2번에 대해서는 약간 고개를 갸웃거릴 수 있을 지 모르겠습니다. 책임 있는 어떤 것이라 니…쉽게 마음에 와 닿지 않는 표현입니다. 이것을 쉽게 이해하려면 먼저 인터페이스라는 용어를 알고 있어야 합니다. 인터페이스를 단순히 C++ 구현 관점에서 설명하면 외부에서 호출 가능한(즉, public) 멤버 함수라 할 수 있습니다. 그런데 이 외부에서 호출 가능한 멤버 함수(이것을 객체 지향 이론에서는 다른 말로 메소드라고 합니다.)는 설계 관점에 다시 보 면 결국 해당 객체가 수행해야 할 기능 목록들입니다. 왜냐하면 객체를 사용하는 입장에서 는 호출을 했으면 어쨋든 해당 호출에 대한 어떤 처리를 객체가 해줄 것이라 생각할 것이고 그렇지 않으면 프로그램이 정상적으로 동작하지 않을 것이기 때문입니다. 예를 들어, class Circle { public: void Draw(); } Circle d; 이런 클래스와 객체가 있다면 d.Draw()라고 했을 때 사용자는 d라는 객체가 Draw()함수 에 대한 어떤 동작을 수행하리라 기대합니다. 따라서 d라는 객체는 Draw()에 대한 적절한 동작을 수행할(여기서 말하는 동작을 수행 한다는 의미는 실제 어떤 구현을 해야 한다는 의 미라기 보다 단순히 해당 호출을 받아 들인다는 의미로 이해하시기 바랍니다.) ‘책임’이 있습 니다. 2번에서의 ‘책임’이라는 말의 의미는 이런 인터페이스를 의미한다고 보시면 됩니다. 이 개념은 객체를 데이터의 집합이 아니라 인터페이스의 집합으로 봐야 한다는 것을 내포 하고 있습니다.(이것이 class가 C의 structure와 구별되는 진정한 차이점입니다.) 그리고 이 것은 우리가 클래스를 설계할 때 이렇게 인터페이스를 기준으로 설계해야 한다는 것 또한 의미합니다.(때문에 ‘알기 쉬운 디자인 패턴’에서 저자는 요구 사항 명세서를 이용하여 클래 스 도출 시 명사를 중심으로 도출할 경우 적절한 설계가 되지 못한다고 주장합니다.) 마지막으로 1번의 주장은 다소 충격적이기까지 합니다.(최소한 저는 이 문장을 처음 읽었 을 때 등골이 오싹한 충격을 받았습니다.) 상속을 통해 기능을 확장하는 것이 아니라고 하 다니…게다가 상속이 클래스를 분류하는 수단이라는 말은 무슨 말이야? 아마도 이렇게 생각 하시는 분들이 많을 것입니다. 실제 제가 참석하는 한 스타디 모임에서 상속에 대한 비유를 이런 식으로 드는 것을 본 적이 있었습니다. ‘어떤 무술을 잘하는 할아버지가 있었는데 시대가 바뀌어 요즘 사람들이 모두 총을 사용하 게 되자 손자에게 무술을 가르쳤더니 손자는 무술도 하고 총도 사용하더라…’ 아마도 객체 지향을 개념적으로만 이해하였거나 처음 접하는 사람들은 모두 고개를 끄덕일 만한 그럴듯한 비유입니다. 어쩌면 객체 지향 개념이 처음 연구되었던(그래서 실무에서 폭넓게 검증되기 전) 초창기에 는 상속이 이런 식으로 쓰이기 위해 만들어 졌을 지도 모르겠습니다. 그러나 실제 프로젝트 에서 기능의 확장을 위해 상속을 사용하게 되면 많은 문제점에 부딪히게 됩니다. 이제부터 예를 한 번 들어 보겠습니다.(이 예제 역시 ‘알기 쉬운 디자인 패턴’에 나온 Animal예제를 좀 더 확장, 변형한 것입니다.) 이제 여러분이 온라인 게임에서 다양한 Mob(게임에 등장하는 일종의 몬스터 같은 것들) 을 구현하는 역할을 맡았다고 가정합시다. 우선 여러분은 Mob이 맵을 자유롭게 돌아다니는 Move기능을 넣기로 합니다. 그리고 기 능 명세서에 의하면 이 Move기능은 지상에서 움직이는 것과 하늘을 날아다니는 기능으로 나뉘게 됩니다. 아마도 상속을 이용하면 다음과 같은 구현이 가능할 것입니다. +Move() Mob WalkingMob FlyingMob 이렇게 하면 기본적인 Mob의 기본 상태나 기능은 그대로 재사용이 가능하며 Mob의 움직 임을 컨트롤하는 Move()함수에 대해서만 생성된 객체의 종류에 따라 적절하게 다형적인 동 작을 수행할 것입니다.(물론 이 때 Move()함수는 virtual로 선언되어야 합니다.) 이것은 썩 괜찮은 판단 같습니다. 우리는 앞으로 공통된 기능들을 수정하고자 할 때 단지 Mob클래스 만을 수정하면 되며 WalkingMob이나 FlyingMob 고유의 기능은 적절히 캡슐화 되어 다른 부분에 영향을 끼치지 않을 것입니다. 그런데 이렇게 깔끔하게 작업을 완료하고 만족스러워 하고 있는 여러분에게 팀장이 와서 Mob들에게 Eat()라는 기능을 추가해야 한다고 말을 합니다. 그리고 이 Eat()는 크게 맵 상 의 식물이나 주인공의 식량이 되는 농작물을 먹어 치우는 PlantEating 기능과 맵 상의 다른 Mob을 공격하거나 혹은 주인공을 공격하는 FleshEating 기능으로 분류하여 처리되어야 한 다고 합니다. 따라서 Mob들은 1)지상을 움직이며 식량을 먹어 치우는 Mob, 2)지상을 움직 이며 육식을 하는 Mob, 3)하늘을 날아다니며 식량을 먹어 치우는 Mob, 4)하늘을 날아다니 며 육식을 하는 Mob으로 분류가 될 수 있습니다. 우선 여러분은 다중 상속을 이용하는 것이 좋겠다는 생각을 합니다.(그렇지 않았더라도 그냥 그러려니 이해하십시오.) +Move() +Eat() Mob WalkingMob FlyingMob PlantEatingMob FleshEatingMob 우선 이렇게 클래스를 추가하고 WalkingMob FlyingMob PlantEatingMob FleshEatingMob Class1 Class2 Class3 Class4 +Move() +Eat() Mob <구조 1> 이렇게 다중 상속을 취하는 것입니다. 즉, 지상 초식 Mob은 WalkingMob과 PlantEatingMob을 상속받는 것입니다.(그림에서는 class1이 되겠군요.) 이것은 기존의 클래 스들을 전혀 수정하지 않아도 된다는 점에서 괜찮은 선택인 것 같습니다. 하지만 이 경우 다중 상속의 대표적인 문제점인 중복 상속 문제가 발생합니다. 즉, class1은 Mob을 두 번 상속받게 됩니다. 이 경우 Mob클래스에서 정의된 멤버 변수나 멤버 함수를 사용하고자 할 때 모호성에 의한 이름 충돌 현상이 발생합니다. 물론 해결책은 있습니다. 모호성이 발생되 는 부분마다 명시적인 범위 연산자 처리를 프로그래머가 직접 해주거나 혹은 Mob을 virtual로 상속받으면 가능합니다. 그러나 전자의 경우 소스가 지나치게 복잡해져서 유지 보 수에 어려움이 발생될 수 있으며 후자의 경우 virtual에 의한 추가적인 오버헤드가 발생합 니다. 게다가 이러한 중복 상속 문제는 설계가 직관적이지 않기 때문에 결코 바람직한 설계 라 할 수 없습니다.(게다가 도덕적으로도 용납될 수 없는 구조입니다. 세상에 이것은 외할아 버지와 친할아버지가 같은 격입니다…^^) 그래서 JAVA와 같이 안정성을 지상 과제로 삼는 언어에서는 아예 다중 상속을 허용하지 않습니다.(단 인터페이스를 이용하면 JAVA에서도 다중 상속이 가능합니다. 왜냐하면 인터페이스는 자체 정의 내용이 없기 때문에 중복 상속 에 따른 위험성 문제가 발생하지 않기 때문입니다.) 따라서 다중 상속을 사용하려면 이러한 중복 상속 구조를 피하기 위해 아래처럼 구현해야 합니다. +Move() Mob WalkingMob FlyingMob +Eat() Eating PlantEating FleshEating Class1 Class2 Class3 Class4 <구조 2> 이렇게 하면 적어도 중복 상속의 문제점은 피할 수 있습니다.(참고로 JAVA에서는 이와 같은 구현이 불가능합니다. 왜냐하면 JAVA는 다중 상속을 지원하지 않거든요.) 게다가 역 시 기존 클래스에 대한 변경이 필요 없습니다. 사실 상속의 가장 큰 이점은 바로 이처럼 대 개의 경우 부모 클래스는 자식 클래스에게서 요구하는 것이 없기 때문에 자식 클래스 추가 에 따라 변경해줘야 할 것이 거의 없다는 점입니다.(이런 것을 ‘내리사랑’이라고 하던가요?) 대신 이 경우 한 번에 추가해줘야 할 클래스의 수가 너무 많다는 것이 문제입니다. 게다가 결정적으로 다형성을 이용한 통일된 처리를 이용할 수 없습니다. 즉, Move()함수 호출을 위 해서는 Mob 기반 클래스로 형 변환을 해줘야 하며 Eat()호출을 위해서는 Eating 기반 클래 스 형으로 처리를 해줘야 합니다. 이것은 각 기능에 따라 별도의 베이스 클래스 포인터를 가지고 작업을 하거나 혹은 dynamic_cast<>이용하여 적절한 형 변환을 해줘야 한다는 것 을 의미합니다. 결국 가뜩이나 클래스 추가 작업이 많아서 심난한 여러분의 마음을 들끓게 하는 짜증나는 일이 아닐 수 없습니다. 결국 다중 상속은 ‘왠지 아니올시다’ 인 것 같습니다. 그럼 다른 경우를 생각해 보죠. +Move() +Eat() Mob WalkingMob FlyingMob PlantEatingWalkMob FleshiEatingWalkMob PlantEatingFlyingMob FleshEatingFlyingMob <구조 3> 이 경우 다중 상속의 문제를 해결할 수 있습니다. 물론 기존 클래스를 수정할 필요도 없습 니다. 게다가 앞에 것 보다 보기에도 훨씬 안정적으로 보입니다.(왠지 피라미드의 힘이 느껴 지지 않습니까?) 따라서 비록 중복 작업들이 조금 있지만 그럭저럭 문제가 될 것 같지는 않 습니다.(사실 우리가 잘 쓰고 있는 MFC도 대개 이런 구조를 가지고 있습니다. CRichEditCtrl과 CRichEditView를 한번 보십시오.) 따라서 여러분은 <구조 3>의 방법을 채택하기로 결정합니다. 이제 여러분은 그럭저럭 기능을 추가하고 한가로이 웹 서핑을 하고 있던 중 아이디어 회 의에 참석하게 됩니다. 그리고 여기서 여러분이 구현한 Mob의 기능에 대해 논의하던 중 한 사람이 실제 동물들도 초식, 육식 외에 잡식성 동물들이 있으니 우리 게임에도 잡식성을 가 진(즉, 주인공 식량도 먹어 치우고 공격도 하는) Mob을 만들자고 제안합니다. 그리고 결국 대다수의 지지 속에 여러분은 잡식성 Mob을 구현하도록 지시를 받습니다. 그래서 여러분은 아래와 같이 관련 클래스를 두 개 더 추가함으로써 해당 기능을 구현합니다. +Move() +Eat() Mob WalkingMob FlyingMob PlantEatingWalkMob FleshiEatingWalkMob PlantEatingFlyingMob FleshEatingFlyingMob MixEatingWalkMob MixEatingFlyingMob 이쯤 되면 비슷한 작업을 해봤던 터라 거의 기계적인 수준에서 기능추가가 이루어 집니다. 그리고 이 때까지만 해도 기존에 잘 정의된 클래스들을 그냥 상속을 통해 재사용 함으로서 많은 노가다를 절약하게 되었다며 뿌듯해 할 수도 있습니다. 이제 게임 출시가 얼마 남지 않은 어느 날 기획팀의 한 창의성 넘치고 열의 넘치는(게다 가 개념까지 없는) 사원 한 명이 새로운 아이디어를 내놓습니다. 우리 게임에서 강이나 바 다에 아무런 생물이 살지 않는 다는 점이 너무 어색하니 바다에 사는 Mob을 추가하자는 것이 그의 주장이었습니다. 그리고 역시 다수의 지지 속에(왜냐하면 그들은 자기가 직접 구 현하지 않을 기능에 대해서는 한없이 관대하며 적극적이기 때문에) 여러분은 바다에 사는 Mob을 구현하게 됩니다. 이제 수정된 클래스 구조는 아래와 같습니다. +Move() +Eat() Mob WalkingMob FlyingMob PlantEatingWalkMob FleshiEatingWalkMob PlantEatingFlyingMob FleshEatingFlyingMob MixEatingWalkMob MixEatingFlyingMob SwimmingMob PlantEatingSwimMob MixEatingSwimMob FleshEatingSwimMob 이번에는 하나의 기능을 추가하기 위해 무려 4개의 클래스를 만들어야 했습니다만 그것보 다 더 짜증이 나는 것은 그 중 세 개의 클래스는 이미 구현했던 클래스들과 거의 닯은 꼴들 이라는 것입니다. 애초에 중복을 제거하기 위한 목적으로 시작한 상속 구조는 이제 스타워 즈 에피소드2를 연상케 합니다.(이쯤 되면 그 기획팀 직원에 대한 알수 없는 적개심이 온 몸을 휘감더라도 이상하지 않습니다.) 사실 이건 악몽의 시작에 불과합니다. 이제 이 구조에서는 각 클래스들이 너무나 밀접하게 연관되어 있기 때문에 최상위 클래스인 Mob에 변수 하나 추가할라치면 모든 클래스들을 다시 컴파일해야 하며 가상함수라도 하나 추가할라치면 모든 클래스의 헤더 파일을 대대적 으로 수정해야 합니다.(그리고 대부분 이런 식의 수정은 단순 반복적인 작업이 됩니다.) 결 국 여러분은 프로그래머라면 한번쯤 다 경험해본 ctrl-C, ctrl-V 증후군(주로 ctrl키를 누르 는 새끼 손가락을 혹사시켜서 생기는 경련현상)에 시달리며 역시 코딩은 노가다야, 개발는 3D업종이야…라는 식의 한탄을 하게 됩니다. 기능이 추가 혹은 변경될 때마다 수정하고 테 스트하고 디버깅 해줘야 할 일들은 프로젝트 마감일이 다가 올수록 기하 급수적으로 증가하 게 되며 따라서 야근 횟수는 갈수록 늘어가기만 합니다. 그리고 이렇게 몇 년 굴러 먹다 보 면 객체 지향 방식으로 개발을 하면 재사용이 좋다는 둥, 유지 보수가 편하다는 둥의 이야 기들은 남극 펭귄 방귀뀌는 소리로 들리기 마련입니다. 무엇이 문제인가? 다소 예가 길어졌고 과장이 많이 섞이긴 했지만 실제 프로젝트에서도 정도의 차이가 있을 뿐 이와 비슷한 경우가 많이 발생합니다. 그 이유는 상속을 통해 기능을 확장하는 것이 쉽 고 편하게 ‘보이기’ 때문입니다. 그러나 여기에는 간과하기 쉬운 큰 함정이 도사리고 있습니 다. 그 함정이라는 것은 아래에 나와 있는 상속의 두 가지 특징입니다. 1. 상속은 friend 다음으로 강한 클래스간의 결합이다. 2. 상속은 클래스간의 정적인 구조이다. 클래스간의 결합이 강하다라는 말은 하나의 클래스의 변화가 다른 클래스에게 끼치는 영 향력이 크다라는 것을 뜻합니다. 일반적으로 C++에서 클래스간의 결합도는 friend > inheritance > composition (> aggregation) > dependency 순으로 이루어 집니다.(자바에서 는 friend가 없으므로 상속이 가장 강한 결합도를 가진다고 말할 수 있습니다.) 따라서 상속 을 이용하게 되면 부모와 자식 클래스 사이에는 (보통 프로그래머들이 생각하는 것 보다 훨 씬) 높은 결합도가 형성됩니다. 클래스 구조가 정적이다 라는 말은 해당 클래스간의 구조가 컴파일 시간에 확정되며 따라 서 그만큼 변화에 유연하지 못하다 라는 뜻입니다. 둘 다 유지 보수 내지는 재 사용과는 다소 거리가 멀어 보이는 특징이라 할 수 있습니다. 그런데 왜 상속을 하면 재사용하기 편하게 느껴지는 것일까요? 왜냐하면 상속은 기존 소 스를 수정할 필요가 거의 없고 비교적 단순한 매카니즘이기 때문에 사용하기 편한데다가 비 교적 그 개념이 쉽고 명확하여 초보자도 금방 이해하고 적용할 수 있기 때문입니다. 이것은 일종의 ‘망치의 오류’입니다. 상속이 편하니 모든 것을(심지어 하지 말아야 할 것도) 다 상 속으로 처리하겠다는 것입니다. 객체 지향에 대해 우리가 가지고 있는 가장 대표적인 미신 입니다. 여기서 첫 부분에서 소개한 객체 지향 개념들을 다시 언급해 보겠습니다. 1. 상속은 기능의 확장이 아니라 클래스들을 분류하는 수단이다. 2. 객체는 책임이 있는 어떤 것이다. 3. 캡슐화는 데이터, 인터페이스, 클래스, 시스템 등 구현 가능한 모든 것에 대한 은닉이 다. 1번의 의미를 제대로 이해하기 위해 실생활에서 우리가 어떤 것을 ‘분류’한다는 것이 무 엇인지 한번 생각해 보겠습니다. ‘분류’라는 말은 ‘어떤 동일한 잣대에 의해 체계를 갖는 것’ 을 의미합니다. 예를 들어 텔레비전, 냉장고, 에어컨 등은 ‘가전 제품’으로 분류가 될 수 있 습니다. 그리고 이 때 분류를 위해 사용된 기준은 ‘집안에서 사용하는 전자 제품’입니다. 따 라서 자동차나 식탁은 가전 제품으로 분류할 수 없을 것입니다. 왜냐하면 그 기준이 다르기 (전자 제품이 아니므로) 때문입니다. 비슷하게 오실로스코프 역시 가전 제품이 될 수는 없 습니다. 비록 오실로스코프가 ‘전자 제품’이긴 하지만 (대개의 경우) 집에서 사용하지는 않 기 때문입니다. 그렇다면 객체 지향 설계 시 상속을 통해 클래스를 분류할 때 그 분류 기준은 어떻게 정 해야 할 것인가 하는 문제가 남았습니다. 이것은 2번에 의하여 객체가 가진 책임 즉, 인터 페이스가 됩니다. 여러 가지 이유를 들 수 있겠지만 결정적으로 우리가 다형성을 이용할 때 그 수단이 되는 것이 인터페이스이기 때문입니다.(사실 다형성을 이용하지 않는다면 이러한 논의 자체가 의미가 없을 것입니다.) 이제 위의 예가 가진 문제점을 살펴 보겠습니다. +Move() +Eat() Mob WalkingMob FlyingMob PlantEatingWalkMob FleshiEatingWalkMob PlantEatingFlyingMob FleshEatingFlyingMob 위의 클래스 구조는 분류가 잘못된 상속 구조입니다. Mob이 애초에 분류하기로 정한 기 준은 Move입니다. 그런데 기능이 추가되면서 그 분류 기준에 Eat가 추가되었습니다. 그러 나 하위 클래스인 WalkingMob과 FlyingMob은 Move에 의해서만 분류가 되는 클래스들입 니다. 이것은 ‘집안에서 사용하면서 동시에 전자 제품’인 가전 제품 분류에 식탁(집에서 사 용)이나 오실로스코프(전자 제품)가 포함되는 것과 유사합니다. +Move() +Eat() Mob WalkingMob FlyingMob PlantEatingMob FleshEatingMob 물론 이것도 올바른 상속 구조가 될 수 없습니다. WalkingMob과 PlantEatingMob은 동일 한 분류 기준을 가지고 있지 않습니다. 마지막으로 3번째 정의에 대해 이야기 해보겠습니다. 1. 상속은 기능의 확장이 아니라 클래스들을 분류하는 수단이다. 2. 객체는 책임이 있는 어떤 것이다. 3. 캡슐화는 데이터, 인터페이스, 클래스, 시스템 등 구현 가능한 모든 것에 대한 은닉이다. 여기에 첨언하여 ‘캡슐화는 가변성에 대한 은닉이다’라는 말을 덧붙이고 싶습니다. 우리가 재 사용성을 높이고 유지보수를 쉽게 하겠다는 말의 뜻은 알고 보면 ‘기존 소스가 새로이 추가되거나 변경되는 부분에 대한 영향을 받게 하지 않겠다(혹은 최소화하겠다)’라 는 뜻입니다. 따라서 이렇게 하기 위해서는 추가되거나 수정이 이루어 지는 부분을 캡슐화 해야 합니다. 그런데 위의 상속 구조는 매우 강한 결합이기 때문에 이렇게 추가되는 기능에 대한 캡슐화에 적합하지 않습니다. 자, 이제 문제점을 알았으니 해결책에 대해 이야기 할 시간입니다. 합성을 이용하자 근래 몇 년 사이에 발표된 혹은 출간된 객체 지향 관련 글들이 공통적으로 강조하는 설계 원칙 중 하나는 ‘가급적 상속 대신 합성을 이용하라’ 입니다. 자세한 이유에 대해서는 뒤에 서 설명하도록 하고 우선 위의 예제를 위에서 언급한 내용들을 토대로 다시 구현 해 보도록 하겠습니다. 우선 최초의 요구 사항은 ‘두 가지 세부 구현으로 나뉠 수 있는 Move기능 구현’입니다. 따라서 여기서 Mob 객체의 책임(인터페이스)는 Move()가 되고 가변성이 발생되는 것은 Move의 동작 방식입니다. 여기서는 두 가지 선택이 가능합니다. 1. Mob 자체를 동작 방식의 변화에 대해 캡슐화하는 경우 -> 상속 이용 2. 가변성에 대한 별도의 캡슐화 클래스를 사용하는 경우 -> 합성 이용 위에서 가급적 상속보다는 합성을 이용하라고 했으므로 2번을 선택하도록 합니다.(1번을 선택해도 큰 문제는 없습니다.) 2번을 선택하였으므로 가변성을 캡슐화하는 별도의 클래스가 필요합니다. 여기서는 그 클 래스의 이름을 Movement라고 하였습니다. 이 Movement는 Move()라는 인터페이스를 가 지며 구현 방식의 가변성을 캡슐화하는 책임을 가집니다. 그리고 Move라는 분류 기준에 의 해 Walking과 Flying이라는 클래스가 상속됩니다. 이제 이 새로 만들어진 기능을 아래 그 림과 같이 Mob 클래스에 추가합니다. +Move() Movement +Move() Mob 1 - 1 Walking Flying 처음에 비해 Movement라는 쓸데없는 클래스가 더 생긴 점이나 Mob에서 Movement객체 를 관리하는 코드들이 더 추가되어야 한다는 점이 못마땅할 지 모르지만 어쨌든 계속 진행 해 보겠습니다. 이제 팀장이 와서 Eat() 기능을 추가해 달라고 합니다. 역시 여기서도 두 가지 선택이 가능합니다만 계속 2번 방식을 이용해 보겠습니다. 이번에 는 Taste라는 클래스를 만듭니다. 이 클래스는 Eat()라는 인터페이스를 가지며 역시 구현 방식의 가변성을 캡슐화하는 역할을 수행합니다. 그리고 동일한 분류 기준을 가진 PlaintEating과 FleshEating 클래스를 상속합니다. 마지막으로 새로 구현된 기능을 Mob에 적용하기 위해 Eat()인터페이스를 추가합니다. 이 인터페이스는 단지 Taste클래스의 인터페이스를 호출하는 역할을 수행합니다. 결과는 아래와 같습니다. +Move() Movement +Move() +Eat() Mob 1 - 1 Walking Flying +Eat() Taste * 1 PlantEating FleshEating 이제 도움 안 되는 동료들에 의해 잡식성 Mob을 추가해야 할 때입니다. 잡식성이라는 기 능은 Taste 클래스의 분류 기준에 포함되므로 상속을 이용하면 됩니다. +Move() Movement +Move() +Eat() Mob 1 - 1 Walking Flying +Eat() Taste * 1 PlantEating FleshEating MixEating 단지 MixEating이라는 클래스를 하나 추가해줌으로써 모든 것이 명확하게 처리가 됩니다. 추가된 기능은 이미 정의된 책임에 대한 가변성에 해당하며 이것은 Taste 클래스에 의해 잘 캡슐화가 되어있으므로 더 이상 수정해 줘야 할 것들이 아무것도 없습니다.(물론 아주 이상적인 경우이겠지만) 이제 마지막으로 개념 없는 기획팀 직원의 아이디어를 반영할 차례입니다. 그가 말한 바 다 생물을 위해서는 Swimming이라는 동작 방식이 필요하므로 Movement클래스에 Swimming이라는 자식 클래스를 만들어 줍니다. 그리고 이 기능 역시 기존의 Movement클 래스에 의해 캡슐화 되어 있으므로 다른 부분에 영향을 끼치지 않고도 매끄럽게 기능 추가 가 이루어 집니다. +Move() Movement +Move() +Eat() Mob 1 - 1 Walking Flying +Eat() Taste * 1 PlantEating FleshEating MixEating Swimming <구조 4> 자 이제 왠지 기획팀 직원에 대한 적개심이 눈 녹듯 사라지는 것이 느껴지지 않습니 까?(따라서 더 이상 기획팀 직원을 어떻게 하면 물 먹일 수 있을까 고민하며 괴로워할 필요 도 없습니다.) 기능 추가가 더 이상 노가다가 아닌 아주 간단한 작업이 돼버렸습니다. 게다 가 이제는 가상 함수 추가나 기존 기능 수정을 위해 전체를 고칠 필요가 없습니다. 단지 (이전 보다 훨씬 적은) 몇몇 관련 클래스들만이 유지 보수에 영향을 받을 뿐입니다. 그리고 이것은 그만큼 기능 수정에 따른 예기치 못한 버그가 발생할 확률이 더 적다는 것을 의미하 며, 프로젝트 마감이 다가 오더라도 해야 할 일들이 기하급수적으로 늘어나지는 않을 것 같 다라는 뜻이기도 합니다. 상속과 합성의 조합 물론 위의 예제는 (대부분의 책들이 그렇듯이) 매끄러운 진행을 위해 인위적으로 조작된 시나리오에 불과합니다. 따라서 과장도 많고 지나치게 이상적인 상황을 연출하긴 했지만 뭐 …이 바닥이 다 그런 것 아니겠습니까? 다만 여기서 가장 핵심적인 사항은 상속을 이용하지 말라가 아니라 상속을 남용해서는 안 된다는 점이며 상속이 남용되었는지 그렇지 않은지를 판단하는 척도는 자식 클래스가 동일 한 분류 기준에 의해서 분류가 가능하냐는 것으로 판단할 수 있다는 것입니다. ‘상속이 기능의 확장이 아니라 클래스를 분류하기 위한 수단이다.’ 라는 말의 의미는 바로 이런 것입니다. 따라서 아래와 같은 방식 역시 괜찮은 설계가 될 수 있습니다.(그러나 개인 적으로는 구조<4>를 더 추천하고 싶군요.) Mob Movement PlantEatingMob FleshEatingMob Walking Flying -End1 * -End2 * <구조 5> 여기서 Mob은 식성이라는 동일한 분류 기준을 가지고 상속이 이루어 졌으며 Movement 역시 마찬가지입니다. 그리고 Mob은 Movement와 합성 관계를 통해 기능을 추가하고 있습 니다. 이 경우 Mob의 인터페이스는 Eat()와 Move()인데 Eat()는 동적 다형성에 의해 가변 성 처리가 이루어 지며 Move()는 Mob가 포함하고 있는 Movement 객체가 가진 캡슐화에 의해 가변성이 처리됩니다. 상속에 대한 개념을 바꾸는 것 하나만으로도 우리는 유지 보수에 용이하고 훌륭한 객체 지향 설계를 할 수 있습니다. <구조 4>와 <구조 5>는 이렇게 수정된 상속과 객체에 대한 정의를 토대로 나올 수 있는 설계 구조입니다. 과연 다중 상속은 나쁜 것인가? 자 이제 한 단계 더 나아가 <구조 2>에 대해 다시 생각해 보겠습니다. +Move() Mob WalkingMob FlyingMob +Eat() Eating PlantEating FleshEating Class1 Class2 Class3 Class4 <구조 2> 이것은 우리가 다중 상속 구조를 생각하면서 만들어본 클래스 구조도 입니다. 여기서 윗 부분만 놓고 생각해 보자면 +Move() Mob WalkingMob FlyingMob +Eat() Eating PlantEating FleshEating 이 구조는 바람직한 상속 구조를 가지고 있습니다. 단지 우리는 이 두 계층도를 연결할 때 합성 관계를 이용하게 되면 좋은 구조라고 말했고 다중 상속을 이용하면 안 좋은 구조라 고 말했습니다. 그런데…정말 그럴까요? 정말 다중 상속은 저주 받은 속성일까요? 왜 사람 들은 다중 상속을 피해야 한다고 말을 할까요? 왜 자바에서는 다중 상속을 허용하지 않았을 까요? 그 이유는 바로 다중 상속이 중복 상속의 위험성에 노출되어 있기 때문입니다. 이 말 을 뒤집으면 중복 상속의 위험성이 없는 한 다중 상속은 전혀 거리낄 것이 없다는 뜻입니다. 즉, 아래 구조도에서 Class1 Class2 Class3 Class4 문제가 되는 부분은 2가 아니라 1인 것입니다. 그럼 1과 같은 구조가 생기지 않도록 하 려면 어떻게 해야 하는가? 이것에 대한 해답은 이미 이전 단락에서 나왔습니다. 즉, 동일한 분류 기준으로 상속을 수행하면 됩니다. 생각해 보십시오. 동일한 분류 기준을 가진 클래스 들을 다중 상속해야 할 필요가 있을 까요? 위의 다중 상속 Mob에서도 다중 상속이 필요한 경우는 Walking-PlantEating(혹은 FleshEating), Flying-PlantEating(혹은 FleshEating) 과 같은 경우였지, Walking-Flying, PlantEating-FleshEating 이런 식의 다중 상속을 하지는 않았습니다. 결국 위와 같은 원칙만 잘 지켜준다면 (중복 상속이 발생할 수 없으므로)다중 상속은 전혀 문제 될 것이 없습니다. 1 2 하지만 다중 상속에는 또 다른 (때에 따라서는 사소한) 문제가 숨어 있다고 앞에서 언급 했었습니다. 즉, 다형성을 이용한 통일된 처리가 불가능하다는 것입니다. 아래 소스를 한번 보시기 바랍니다. class Movement { public: virtual void Move() = 0; } class Walking : public Movement { public: void Move() { std::cout << "I can walk₩n"; } } class Flying : public Movement { public: void Move() { std::cout << "I can fly₩n"; } } class Taste { public: virtual void Eat() = 0; } class PlantEating : public Taste { public: void Eat() { std::cout << "I like vegetables₩n" } } class FleshEating : public Taste { public: void Eat() { std::cout << "I like meats₩n" } } class PlantEatingAndWalkingMob : public Walking, public PlantEating { } class FleshEatingAndFlyingMob : public Flying, public FleshEating { } 이제 PlantEatingAndWalkingMob과 FleshEatingAndFlyingMob 은 더 이상 통일된 인터 페이스 처리가 불가능합니다. Movement 포인터형을 이용할 경우 Move()함수 호출은 가능 하지만(그리고 다형적으로 처리가 되겠지만), Eat()함수 호출은 불가능합니다. 반대로 Taste 포인터형을 이용하면 Eat()만 처리가 가능합니다. 한 가지 시도해 볼 수 있는 것은 dynamic_cast<>를 이용하는 것입니다. 즉, 어느 하나의 포인터 형으로 객체들을 관리하고 반대쪽 함수를 호출할 때는 해당 포인터 형으로 변환하여 처리하도록 구현하는 것입니다. 예를 들자면 아래와 같이 처리하는 것이지요 std::vector mobArr; mobArr.push_back(…); … /// 생성된 객체를 모두 여기에 집어 넣는다. std::vector::iterator b = mobArr.begin(), e = mobArr.end() while (b != e) { (*b)->Move(); dynamic_cast(*b)->Eat(); /// Eat() 호출 시 Taste형으로 변환하여 처리 ++b; } 이 경우 우선 프로그래머가 일일이 형 변환을 지정해 줘야 한다는 불편함과 함께 dynamic_cast<>에 대한 오버 헤드 부담이 뒤 따르게 됩니다. dynamic_cast<>는 RTTI 매 카니즘에 의해 객체의 형 정보를 검색하여 처리를 해줘야 하므로 static_cast<>와 같은 다 른 변환 연산자 보다 수행 시간이 많이 걸립니다. 결국 사용하기도 불편하고 성능도 떨어지 는, 합성을 이용하는 것보다 나은 점이 조금도 없는 구조입니다. 그렇다면 어떻게 해야 할까요? 간단합니다. 이런 경우 그냥 합성을 이용하면 됩니다. 무 슨 뜬금없는 소리냐구요? 다중 상속 이야기를 먼저 꺼낸 사람이 누군데 이제 와서 그냥 사 용하지 말라니…참으로 무책임하기 짝이 없다구요? 사실 여기서 제가 정말로 하고 싶었던 말은 다중 상속은 단일 상속과 다르게 생각해야 한 다는 것입니다. 사실 우리는 크게 볼 때 다음 두 가지 목적을 위해서 상속을 사용합니다. 1. 동적 다형성 이용 2. 정말 순수하게 부모 클래스의 기능 재사용 지금까지 이야기했던 것은 1번의 경우에 대한 이야기였습니다. 보통 1번을 인터페이스 상 속, 2번을 구현 상속이라고 합니다. 많은 객체 지향 설계 기법(특히, 디자인 패턴에 소개된 대부분의 설계 패턴)은 1번을 위해 상속 구조를 이용합니다. 그러나 실제 프로젝트를 수행하다 보면 다형성을 위한 목적이 아니라 정말로 순수하게 프 로그래머가 원하는 기능이 미리 구현되어 있는 클래스의 기능을 단순히 물려받고 싶은 경우, 혹은 여러 클래스에서 공통된 특성을 필요로 하여 그런 특성을 별도의 단위 전략 클래스로 만들어 재사용하고 싶은 경우가 있습니다. 예를 들어 기존의 클래스 라이브러리(MFC가 제 공하는 API클래스나 STL의 컨테이너 클래스들)의 기능에 자신만의 추가적인 기능을 구현 하고 싶을 지도 모릅니다. 이럴 땐 부모 클래스의 인터페이스를 필요로 하는 것이 아니라 이미 구현된 기능 그 자체를 필요로 하는 것입니다. 다중 상속이 사용되는 것은 바로 이런 순간입니다. 다시 위의 Mob 클래스를 생각해 볼 때, 전체 객체들을 동일한 알고리즘을 통해 처리할 필요 없이 그냥 각각의 특성을 가진 Mob 별로 별도의 처리를 하겠다고 생각했다면 (즉, 어 떤 공통된 인터페이스를 통한 처리를 완전히 포기하고 그 때 그 때 필요한 객체를 생성해서 사용하기 위한 목적으로 클래스를 이용한다면) 다중 상속도 괜찮은 선택이 될 수 있습니다. 아니 오히려 이 경우 다중 상속은 합성을 이용하는 것보다 더 좋습니다. 왜냐하면, 첫째, 합성을 이용할 경우 해당 추가되는 기능 클래스 객체를 다루기 위한 별도의 멤버가 필요하고 추가적인 리소스 처리 기능을 구현해 줘야 합니다. JAVA와 달리 C++에서는 이 리소스 처리가 항상 프로그래머의 발목을 잡습니다. 특히나 멀티 쓰레드 상황에서는 더더욱 골치 아픈 존재가 될 수 있습니다. 그러나 상속을 이용할 경우 이런 별도의 멤버 처리가 필 요 없습니다. 둘째, 추가되는 기능에 대해서 wrapping함수를 추가해 줘야 하므로 기존 클래스의 수정 이 불가피합니다. 하지만 상속의 경우 이런 것이 필요 없습니다. 게다가 wrapping함수를 이 용한다라는 것은 간접 호출에 대한 실행 시간 비용이 발생한다는 것을 의미합니다. 물론 inline 처리가 될 경우 이런 비용이 무시될 수 있습니다만 보장된 사항은 아닙니다.(대개의 경우 컴파일러는 인라인 처리를 해줍니다.), 하지만 상속은 항상 직접 호출이 가능합니다. 셋째, 합성의 경우 모든 인터페이스를 가상 함수로 처리해줘야 합니다. 그러나 다중 상속 을 이용하면 그럴 필요가 없습니다.(어차피 다형성을 의도하지 않았으므로) 하지만 다중 상속이 꼭 장점만 있는 것은 아닙니다. 결정적으로 다중 상속은 기능 추가 시 마다 추가해 줘야 할 클래스의 개수가 많아 지는 점이 문제입니다. 그리고 이런 작업의 대부분은 단순한 copy&paste 인 경우가 많습니다. 즉, 처음 예제의 경우 다중 상속을 이용 했을 때 Swimming기능이 추가될 경우 만들어 줘야 할 클래스의 개수는 4개가 됩니 다.(Swiiming 클래스 1, 이것을 상속 받는 클래스 3) 그리고 이런 것들은 기능이 추가될 때 마다 기하 급수적으로 늘어날 것입니다. 자 이제 C++만이 가지는 장점이 빛을 발하는 순 간입니다. C++에는 템플릿이라는 다른 언어에는 없는(얼마 전 자바에서 JDK 1.5가 나오면서 템플 릿 기능이 추가되긴 했지만 어쨌든) 막강한 무기가 있습니다. 그리고 이 템플릿은 다중 상 속과 기가 막힌 궁합을 자랑합니다. 위의 Mob 예제를 템플릿과 다중 상속을 이용하여 처리 하면 아래와 같습니다. class Movement { public: void Move(); /// 정의는 필요 없고 단지 선언만(가상함수가 아니어도 됨) protected: ~Movement() {} }; class Walking : public Movement { public: void Move() { std::cout << "I can walk₩n"; } }; class Flying : public Movement { public: void Move() { std::cout << "I can fly₩n"; } }; class Taste { public: void Eat(); /// 역시 정의는 필요 없고 단지 선언만(물론 이것도 가상함수가 아니 어도 됨) protected: ~Taste() {} }; class PlantEating : public Taste { public: void Eat() { std::cout << "I like vegetables₩n"; } }; class FleshEating : public Taste { public: void Eat() { std::cout << "I like meats₩n"; } }; template class Mob : public TasteType, public MoveType { }; 이게 전부 입니다. 이제는 필요할 때마다 해당 클래스 객체를 아래처럼 적절하게 정의해 주면 됩니다. Mob ogre; Mob wyvern; Mob gnome; 만약 Swimming 동작이 추가되면 해당 클래스만 정의해주면 됩니다. class Swimming : public Movement { public void Move() { std::cout << "I can swim₩n"; } }; 그리고 필요한 부분에서 해당 클래스 객체를 정의합니다. Mob shark; 이제 Mob 클래스는 합성을 이용할 때처럼 별도의 멤버 객체를 다루는 루틴을 추가해야 하거나 추가된 인터페이스를 위한 wrapping 함수를 구현해야 할 필요도 없으며 매번 다량 의 클래스를 정의해 줘야 할 필요도 없이 간단하게 기능 확장/수정이 가능합니다. 이런 편의성에 덧붙여 이젠 더 이상 가상 함수나 wrapping 함수가 갖는 추가적인 오버 헤드가 발생하지 않습니다. 심지어 위의 예제 소스 같은 간단한 함수의 경우 바로 인라인 처리가 가능하며 그런 경우 해당 함수 호출에 대한 어떠한 비용도 지불할 필요가 없습니다. 그뿐만이 아닙니다. 이젠 가상 테이블이 더 이상 필요 없고 기능 추가에 따른 멤버 추가가 없어져서 메모리 면에서도 훨씬 효율적입니다. 결정적으로 위의 모든 장점을 뛰어넘는 진정한 템플릿의 비밀 병기가 있으니 바로 템플릿 특화(template specialization) 입니다. 템플릿 특화를 이용하면 기존 소스를 전혀 건드리지 않고도 예외적인 기능 구현이 가능합니다. 가령 예전에 그 개념 없는 기획팀 직원이 바다에 사는 육식 동물은 주인공을 공격할 뿐만 아니라 배도 공격하도록 하자 라는 새로운 주장을 펼치고 역시 여러분을 제외한 모두의 찬성에 의해 그러한 기능을 구현해야 한다면 <구조 4>와 같은 합성 구조에서는 매우 까다로운 처리가 필요합니다. 왜냐하면 Movement와 Taste클래스는 서로 간에 완전히 분리된 클래스들이기 때문에 Swimming 클래스에서는 Mob객체가 FleshEating 객체를 사용하는지 PlantEating 객체를 사용하는지 알 방법이 없기 때문입니다. 결국 별도의 상태 변수를 추가해서 복잡한 if else 처리를 해줘야 하거나 이 경우에 대해서만 동작하는 별도의 예외 클래스를 정의해 주거나 어쨌든 특별한 처리가 필요 합니다. 어떤 경우든 기존 소스의 수정이 불가피하며 이런 일이 반복되어 애써 잘 만든 소스가 너덜너덜해 지기 전에 뭔가 새로운 패턴을 적용하기 위해 골 머리를 썩혀야 합니다. 그러나 템플릿 특화를 이용하면 아주 세련된(그리고 매우 간단한) 처리가 가능합니다. 즉, 예외적인 처리가 필요한 Eat()함수에 대해서 아래와 같이 템플릿 특화를 적용합니다. template class Mob : public TasteType, public MoveType { public: void Eat() { TasteType::Eat(); } /// 템플릿 특화를 위한 재정의 }; template<> void Mob::Eat() { /// 기존 기능에 배를 삼키는 기능 추가 } 이렇게 하면 다른 객체들의 Eat() 호출은 기존 방식대로 수행될 것이며 단지 Mob 템플릿 클래스의 객체에 대해서만 별도의 특화된 Eat()함수 가 호출될 것입니다. 이제 원하는 기능은 구현되었으며 그 외에 여러분이 해줘야 할 것은 아무것도 없습니다! 무엇을 언제 어떻게 사용할 것인가? 대부분의 경우 프로젝트는 항상 변하며 요구 사항 역시 언제나 달라집니다. 또한 이미 완 료된 프로젝트라 하더라도 차후 기능 변경이나 추가는 수시로 이루어 집니다. 따라서 프로 그래머 역시 유연한 사고가 필요합니다. 어떤 기능 수정이나 추가 시 지금까지 상속으로 처 리했으니 끝까지 상속만 이용 한다거나 반대로 합성만을 고집하는 것은 결국 기계적인 반복 작업 속에 점점 경직된 구조의 프로그램을 만들게 됩니다. 따라서 정작 프로젝트를 수행하 다 보면 ‘코딩 스타일은 자유롭고 설계는 매우 경직되는’ 경우를 많이 보게 됩니다. 이런 소 스는 유지 보수가 어렵고 가독성이 떨어지며 예상치 못한 버그에 시달리는 쓰레기 소스가 돼버립니다. 결국 고심 끝에 해당 소스는 폐기되고 아예 처음부터 새롭게 다시 짜는 경우가 발생합니다. 좋은 프로그래밍이 이루어 지려면 반대로 코딩 스타일은 빈틈없고 단단해야 하며 설 계는 유연해야 합니다. 가장 중요한 것은 구현 방식을 결정하기에 앞서 전제 조건이 무엇인지, 기능 구현의 목적 이 무엇인지를 파악하는 것입니다. 제 글의 마지막에서 템플릿을 통한 다중 상속이 좋다고 신나게 떠들어 댔지만 만약 Mob을 다형적으로 이용해야 하는 조건이 필요하다면 이 모든 것이 ‘말짱 황’ 입니다. 그냥 군말 없이 합성을 이용한 단일 상속 구조로 가야 합니다. 소프 트웨어 설계는 모든 상황에 완벽한 해결법은 없지만 특정 상황에 더 나은 해결책은 있기 마 련입니다. 그리고 그러한 더 나은 해결 방안을 찾아 내는 것이 우리 개발자가 해야 할 역할 입니다. 참고 자료들 이 글과 관련하여 제가 참고하였거나 기타 도움이 될 만한 자료나 참고 서적들을 몇 개 추려봤습니다. 9 알기 쉬운 디자인 패턴 : Alan Shalloway, James R. Trott 저, 원제 : Design patterns explained : A New Perspective on Object Oriented Design, 우리말 번 역본 제목이 주는 느낌과 달리 절대 초보자를 위한 책은 아닙니다. 오히려 개인 적으로는 실무에서 객체 지향 언어를 이용하여 프로젝트를 수행했거나 계속 수행 중인 사람들, 특히 디자인 패턴을 이용해서 뭔가 해보려다가 뜻대로 되지 않아 좌절했을 법한 많은 실무 개발자들을 위한 책이라 생각합니다. 이 책의 부제가 말해 주듯이 객체 지향 설계에 대한 저자의 깊은 통찰력을 느낄 수 있습니다. 이 책은 디자인 패턴뿐 아니라 객체 지향 설계 전반에 대한 새로운 안목을 키울 수 있는 좋은 책입니다. 9 Modern C++ Design : Andrei Alexandrescu 저, 안드레이는 템플릿을 이용한 제네릭 프로그래밍 분야에서 세계적으로 가장 앞서나가는 인물 중 한 명입니다. 그리고 이 책은 그런 안드레이의 템플릿을 이용한 화려하고 난해한 테크닉들이 난무하는 책입니다. 따라서 그런 테크닉적인 부분에 압도되어 본질적으로 그가 주장하는 많은 부분을 놓치기 쉽습니다. 만약 제네릭 프로그래밍에 관심이 많은 분이라면 꼭 이 책을 끝까지 읽어 보시기 바라며 혹시 그렇지 않은 분이라도 1 장만큼은 꼭 읽어 보시기 바랍니다. 단위 전략 클래스를 이용한 설계 기법에 대 해 설명해 놓은 1장 부분은 객체 지향 설계에 대한 새로운 안목을 넓힐 수 있는 좋은 내용으로 가득 차 있습니다. 9 JAVA 프로그래머를 위한 UML, 실전에서는 이것만 쓴다. : Robert C. Martin 저, 원제 : UML for JAVA Programmers, UML과 객체 지향 설계에 대해 매우 실용 적인 시각에서 설명을 하고 있습니다. 이 책을 반드시 살 필요는 없습니다. 다만 서점에서 11장 만큼은 반드시 읽어 보시기 바랍니다. 객체 지향 설계 시 우리가 유의해야 할 점들에 대해 잘 설명해 놓았습니다. 9 Thinking in JAVA : Bruce Eckel 저, 저는 자바를 배우기 시작한 지 얼마 되지 않았습니다. 그러나 비록 짧은 기간이지만 자바를 공부해 보면서 느낀 점이라면 자바는 객체 지향 프로그래머라면 한 번쯤 공부해볼 필요가 있는 언어이다 라는 것입니다. 언어의 우수성, 안전성 뭐 이런 논란 거리가 될만한 것들을 떠나서 자 바가 제공하는 클래스 API 들의 상당수가 객체 지향적으로 바람직한 구조를 가 지고 있으며 디자인 패턴을 적용하였거나(가령 스트림 클래스들 중 필터 클래스 들은 Decorator 패턴을 이용하고 있습니다.) 아예 디자인 패턴 사용을 용이하게 하는 클래스들도 있습니다.(예를 들어 Observer 관련 클래스들) 따라서 자바를 공부하는 것은 객체 지향 설계나 디자인 패턴에 대한 이해도나 응용력을 높이는 데 많은 도움이 될 수 있습니다. 이 책은 자바 언어를 설명하는 가장 유명한 책 중 하나이면서 인터넷을 통해 공식적이고 합법적으로 e-book을 구할 수 있는 몇 안 되는 책이기도 합니다. 9 The Liskov Substitution Principle: 흔히 줄여서 LSP라고 말하는 유명한 객체 지 향 설계 원칙에 대한 짧은 논문입니다.(구글에서 검색해보시면 쉽게 PDF문서를 찾으실 수 있습니다.) 짧지만 아주 좋은 글입니다. 9 The Open-Closed Principle: LSP만큼이나 널리 알려진 객체 지향 설계 원칙에 대한 글입니다.(이 글 역시 구글에서 쉽게 검색이 가능합니다.) 역시 객체 지향 프로그래머라면 반드시 읽어둬야 할 글이라 생각합니다. 모쪼록 제 부족한 글이 약간이나마 도움이 되셨기 바랍니다. <글쓴이 : 이은조(gimmesilver@hanmail.net, http://agbird.egloos.com)>
| 1,931.5 | 23,099 | 0.725559 | kor_Hang | 1.00001 |
aa3b0865e39399719047db1dab41a5e06a3f001a | 531 | md | Markdown | doc/clappr/io.clappr.player.playback/-exo-player-playback/-exo-player-events-listener/on-player-state-changed.md | clappr/clappr-android | 05058ae3d431616b44ec968cf19835df4f6de1a6 | [
"BSD-3-Clause"
] | 64 | 2015-03-09T16:42:53.000Z | 2020-09-13T18:44:43.000Z | doc/clappr/io.clappr.player.playback/-exo-player-playback/-exo-player-events-listener/on-player-state-changed.md | globocom/clappr-android | 05058ae3d431616b44ec968cf19835df4f6de1a6 | [
"BSD-3-Clause"
] | 51 | 2015-06-26T18:09:35.000Z | 2020-07-30T12:42:56.000Z | doc/clappr/io.clappr.player.playback/-exo-player-playback/-exo-player-events-listener/on-player-state-changed.md | globocom/clappr-android | 05058ae3d431616b44ec968cf19835df4f6de1a6 | [
"BSD-3-Clause"
] | 23 | 2015-03-28T07:46:57.000Z | 2021-04-16T12:21:33.000Z | [clappr](../../../index.md) / [io.clappr.player.playback](../../index.md) / [ExoPlayerPlayback](../index.md) / [ExoPlayerEventsListener](index.md) / [onPlayerStateChanged](./on-player-state-changed.md)
# onPlayerStateChanged
`fun onPlayerStateChanged(playWhenReady: `[`Boolean`](https://kotlinlang.org/api/latest/jvm/stdlib/kotlin/-boolean/index.html)`, playbackState: `[`Int`](https://kotlinlang.org/api/latest/jvm/stdlib/kotlin/-int/index.html)`): `[`Unit`](https://kotlinlang.org/api/latest/jvm/stdlib/kotlin/-unit/index.html) | 106.2 | 304 | 0.730697 | yue_Hant | 0.618994 |
aa3b5902fde0d20b00ea6f5ac8f42cda240763ff | 2,622 | md | Markdown | docs/outlook/mapi/pidtagdiscretevalues-canonical-property.md | hubalazs/office-developer-client-docs | 86d7b65f5c81941b00469fd02f3c957a14f2757b | [
"CC-BY-4.0",
"MIT"
] | 3 | 2019-11-06T15:25:52.000Z | 2021-09-01T19:32:58.000Z | docs/outlook/mapi/pidtagdiscretevalues-canonical-property.md | hubalazs/office-developer-client-docs | 86d7b65f5c81941b00469fd02f3c957a14f2757b | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/outlook/mapi/pidtagdiscretevalues-canonical-property.md | hubalazs/office-developer-client-docs | 86d7b65f5c81941b00469fd02f3c957a14f2757b | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-12-30T07:57:56.000Z | 2020-12-30T07:57:56.000Z | ---
title: "PidTagDiscreteValues Canonical Property"
manager: soliver
ms.date: 03/09/2015
ms.audience: Developer
ms.topic: reference
ms.prod: office-online-server
localization_priority: Normal
api_name:
- PidTagDiscreteValues
api_type:
- HeaderDef
ms.assetid: 958f3cf7-953a-43f4-9102-ad35edf5e813
description: "Last modified: March 09, 2015"
---
# PidTagDiscreteValues Canonical Property
**Applies to**: Outlook 2013 | Outlook 2016
Contains TRUE if a nondelivery report applies only to discrete members of a distribution list rather than the entire list.
|||
|:-----|:-----|
|Associated properties: <br/> |PR_DISCRETE_VALUES <br/> |
|Identifier: <br/> |0x0E0E <br/> |
|Data type: <br/> |PT_BOOLEAN <br/> |
|Area: <br/> |MAPI non-transmittable <br/> |
## Remarks
This property is used within a nondelivery report when the message could not be delivered to one or more members of a distribution list. Its purpose is to limit retransmission attempts to only those individual members and not the distribution list as a whole.
The recipient table of a nondelivery report contains entries for all recipients to whom the message could not be delivered, and also for the distribution lists, if any, to which they belong. The transport provider should set this property to TRUE for each distribution list entry, and it should copy the **PR_DISPLAY_NAME** ([PidTagDisplayName](pidtagdisplayname-canonical-property.md)), **PR_ENTRYID** ([PidTagEntryId](pidtagentryid-canonical-property.md)), and **PR_SEARCH_KEY** ([PidTagSearchKey](pidtagsearchkey-canonical-property.md)) from the distribution list to **PR_ORIGINAL_DISPLAY_NAME** ([PidTagOriginalDisplayName](pidtagoriginaldisplayname-canonical-property.md)), **PR_ORIGINAL_ENTRYID** ([PidTagOriginalEntryId](pidtagoriginalentryid-canonical-property.md)), and **PR_ORIGINAL_SEARCH_KEY** ([PidTagOriginalSearchKey](pidtagoriginalsearchkey-canonical-property.md)) properties for each member of that distribution list.
**PR_DISCRETE_VALUES** should not be set for any nondelivery report recipient entry other than a distribution list.
## Related resources
### Header files
Mapidefs.h
> Provides data type definitions.
Mapitags.h
> Contains definitions of properties listed as associated properties.
## See also
[MAPI Properties](mapi-properties.md)
[MAPI Canonical Properties](mapi-canonical-properties.md)
[Mapping Canonical Property Names to MAPI Names](mapping-canonical-property-names-to-mapi-names.md)
[Mapping MAPI Names to Canonical Property Names](mapping-mapi-names-to-canonical-property-names.md)
| 39.727273 | 935 | 0.771548 | eng_Latn | 0.912798 |
aa3b7f8700f12dc56cdab3bb3b7101a419f39775 | 10,011 | md | Markdown | articles/security-center/tutorial-protect-resources.md | eduarandilla/azure-docs.es-es | 2d47e242f1f915183fb6a2852199649dbae474a5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/security-center/tutorial-protect-resources.md | eduarandilla/azure-docs.es-es | 2d47e242f1f915183fb6a2852199649dbae474a5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/security-center/tutorial-protect-resources.md | eduarandilla/azure-docs.es-es | 2d47e242f1f915183fb6a2852199649dbae474a5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: 'Tutorial sobre controles de aplicaciones y acceso: Azure Security Center'
description: En este tutorial se muestra cómo configurar una directiva de acceso a las máquinas virtuales Just-In-Time y una directiva de control de aplicaciones.
services: security-center
documentationcenter: na
author: memildin
manager: rkarlin
ms.assetid: 61e95a87-39c5-48f5-aee6-6f90ddcd336e
ms.service: security-center
ms.devlang: na
ms.topic: tutorial
ms.custom: mvc
ms.tgt_pltfrm: na
ms.workload: na
ms.date: 12/03/2018
ms.author: memildin
ms.openlocfilehash: 3e4404589e180be730579b8cbbfadd132502585a
ms.sourcegitcommit: 3543d3b4f6c6f496d22ea5f97d8cd2700ac9a481
ms.translationtype: HT
ms.contentlocale: es-ES
ms.lasthandoff: 07/20/2020
ms.locfileid: "86529325"
---
# <a name="tutorial-protect-your-resources-with-azure-security-center"></a>Tutorial: Protección de los recursos con Azure Security Center
Security Center limita la exposición a amenazas mediante controles de acceso y aplicación para bloquear actividades malintencionadas. El acceso a las máquinas virtuales Just-In-Time (JIT) reduce la exposición a ataques mediante la posibilidad de denegar el acceso persistente a las máquinas virtuales. En su lugar, se proporciona acceso controlado y auditado a VM solo cuando se necesita. Los controles de aplicación adaptables ayudan a proteger las VM frente a malware controlando qué aplicaciones se pueden ejecutar en dichas VM. Security Center usa el aprendizaje automático para analizar los procesos que se ejecutan en la máquina virtual y le ayuda a aplicar reglas de inclusión en listas de permitidos con esta inteligencia.
En este tutorial, aprenderá a:
> [!div class="checklist"]
> * Configuración de una directiva de acceso a las máquinas virtuales Just-In-Time
> * Configuración de una directiva de control de aplicación
## <a name="prerequisites"></a>Prerrequisitos
Para recorrer las características que se tratan en este tutorial, es preciso tener el plan de tarifa Estándar de Security Center. Dicho plan se puede probar de forma gratuita. Para más información, consulte la [página de precios](https://azure.microsoft.com/pricing/details/security-center/). En [Guía de inicio rápido de Azure Security Center](security-center-get-started.md) le explicamos cómo realizar la actualización al plan de tarifa Estándar.
## <a name="manage-vm-access"></a>Administración de acceso a VM
El acceso a VM JIT se puede usar para bloquear el tráfico entrante a las VM de Azure. Para ello, se reduce la exposición a ataques al mismo tiempo que se proporciona un acceso sencillo para conectarse a las VM cuando sea necesario.
No es necesario que los puertos de administración estén abiertos en todo momento. Solo deben estar abiertos mientras se está conectado a la máquina virtual, por ejemplo, para realizar tareas de administración o mantenimiento. Cuando se habilita Just-In-Time, Security Center usa las reglas del grupo de seguridad de red (NSG), que restringen el acceso a los puertos de administración para que no puedan ser objeto de ataques.
1. En el menú principal de Security Center, seleccione **Acceso de máquina virtual Just-In-Time** en **PROTECCIÓN EN LA NUBE AVANZADA**.
![Acceso de máquina virtual Just-In-Time][1]
**Just-in-time VM access** (Acceso a máquina virtual del tipo Just-In-Time) proporciona información acerca del estado de las máquinas virtuales:
- **Configurado**: máquinas virtuales que se han configurado para admitir el acceso a máquina virtual Just-In-Time.
- **Recomendado**: máquinas virtuales que pueden admitir el acceso a máquina virtual Just-In-Time, pero que no se han configurado para ello.
- **Ninguna recomendación**: una máquina virtual podría no recomendarse por diversas razones:
- Falta grupo de seguridad de red: la solución Just-In-Time requiere que exista un grupo de seguridad de red.
- Máquina virtual clásica: en la actualidad, el acceso a máquina virtual Just-In-Time de Security Center solo admite las máquinas virtuales implementadas mediante Azure Resource Manager.
- Otros: una máquina virtual de esta categoría si la solución Just-In-Time está desactivada en la directiva de seguridad de la suscripción o del grupo de recursos, o si la máquina virtual no tiene una IP pública y no existe ningún grupo de seguridad de red.
2. Seleccione una máquina virtual recomendada y haga clic en **Habilitar JIT en 1 VM** para configurar una directiva Just-In-Time para esa máquina virtual:
Puede guardar los puertos predeterminados que Security Center recomienda o agregar y configurar un puerto nuevo donde desee habilitar la solución Just-In-Time. En este tutorial, vamos a agregar un puerto seleccionando **Agregar**.
![Adición de configuración de puerto][2]
3. En **Add port configuration** (Agregar configuración de puerto), se identifica:
- El puerto
- El tipo de protocolo
- Las direcciones IP de origen permitidas (intervalos IP que pueden acceder una vez que se ha aprobado una solicitud)
- El tiempo de solicitud máximo (el período de tiempo máximo durante el que puede estar abierto un puerto específico)
4. Seleccione **Aceptar** para guardar.
## <a name="harden-vms-against-malware"></a>Proteger VM frente a malware
Los controles de aplicación adaptables ayudan a definir un conjunto de aplicaciones que se pueden ejecutar en grupos de recursos configurados que, entre otras ventajas, le ayuda a proteger las VM frente a malware. Security Center usa el aprendizaje automático para analizar los procesos que se ejecutan en la máquina virtual y le ayuda a aplicar reglas de inclusión en listas de permitidos con esta inteligencia.
1. Vuelva al menú principal de Security Center. En **PROTECCIÓN EN LA NUBE AVANZADA**, seleccione **Controles de aplicaciones adaptables**.
![Controles de aplicación adaptables][3]
La sección **Grupos de recursos** contiene tres pestañas:
- **Configurado**: lista de grupos de recursos con VM configuradas con control de aplicación.
- **Recomendado**: lista de grupos de recursos para los que se recomienda el control de aplicación.
- **Ninguna recomendación**: lista de grupos de recursos que contienen máquinas virtuales sin ninguna recomendación de control de aplicación. Por ejemplo, máquinas virtuales en las que las aplicaciones cambian constantemente y no han alcanzado un estado estable.
2. Seleccione la pestaña **Recomendado** para obtener una lista de grupos de recursos con las recomendaciones de control de aplicación.
![Recomendaciones de control de aplicación][4]
3. Seleccione un grupo de recursos para abrir la opción **Crear reglas de control de aplicaciones**. En **Seleccionar máquinas virtuales**, revise la lista de máquinas virtuales recomendadas y desactive cualquiera a la que no desee aplicar el control de aplicación. En **Seleccionar procesos para reglas de inclusión en lista blanca**, revise la lista de aplicaciones recomendadas y desactive aquellas a las que no desea que se apliquen. La lista incluye:
- **NOMBRE**: la ruta de acceso completa de la aplicación
- **PROCESOS**: el número de aplicaciones que residen dentro de cada ruta de acceso
- **COMÚN**: "Sí" indica que estos procesos se han ejecutado en la mayoría de las máquinas virtuales de este grupo de recursos
- **INFRINGIBLE**: un icono de advertencia indica si un atacante podría usar las aplicaciones para evitar las listas de aplicaciones permitidas. Se recomienda revisar estas aplicaciones antes de su aprobación.
4. Cuando haya terminado de realizar las selecciones, elija **Crear**.
## <a name="clean-up-resources"></a>Limpieza de recursos
Otras guías de inicio rápido y tutoriales de esta colección se basan en los valores de esta. Si planea continuar trabajando con las guías rápidas y tutoriales posteriores, siga ejecutando el plan de tarifa Estándar y mantenga el aprovisionamiento automático habilitado. Si no planea continuar o desea volver al nivel Gratis:
1. Vuelva al menú principal de Security Center y seleccione **Directiva de seguridad**.
2. Seleccione la suscripción o directiva que desea que vuelva al nivel Gratis. Se abre **Directiva de seguridad**.
3. En **COMPONENTES DE LA DIRECTIVAS**, seleccione **Plan de tarifa**.
4. Seleccione **Gratis** para cambiar la suscripción del nivel Estándar al Gratis.
5. Seleccione **Guardar**.
Si desea deshabilitar el aprovisionamiento automático:
1. Vuelva al menú principal de Security Center y seleccione **Directiva de seguridad**.
2. Seleccione la suscripción en la que quiere deshabilitar el aprovisionamiento automático.
3. En **Directiva de seguridad: Colección de datos**, en **Incorporación**, seleccione **Desactivado** para deshabilitar el aprovisionamiento automático.
4. Seleccione **Guardar**.
>[!NOTE]
> La deshabilitación del aprovisionamiento automático no quita el agente de Log Analytics de las máquinas virtuales de Azure en las que se ha aprovisionado. La deshabilitación del aprovisionamiento automático limita la supervisión de seguridad de los recursos.
>
## <a name="next-steps"></a>Pasos siguientes
En este tutorial, aprendió a limitar la exposición a amenazas mediante:
> [!div class="checklist"]
> * La configuración de un directiva de acceso a las máquinas virtuales Just-In-Time para proporcionar acceso controlado y auditado a las máquinas virtuales solo cuando sea necesario
> * La configuración de una directiva de controles de aplicación adaptables para controlar qué aplicaciones se pueden ejecutar en las VM
Pase al siguiente tutorial para aprender a responder a incidentes relacionados con la seguridad.
> [!div class="nextstepaction"]
> [Tutorial: Respuesta a incidentes de seguridad](tutorial-security-incident.md)
<!--Image references-->
[1]: ./media/tutorial-protect-resources/just-in-time-vm-access.png
[2]: ./media/tutorial-protect-resources/add-port.png
[3]: ./media/tutorial-protect-resources/adaptive-application-control-options.png
[4]: ./media/tutorial-protect-resources/recommended-resource-groups.png
| 75.270677 | 730 | 0.79123 | spa_Latn | 0.98925 |
aa3b822e34c278a64f269341b1899f3b0f8e9d47 | 399 | md | Markdown | _pages/cat_data_vis.md | burrussmp/burrussmp.github.io | a4bd01c55def4dcc58408fd2a8726a9b938aeb05 | [
"MIT"
] | null | null | null | _pages/cat_data_vis.md | burrussmp/burrussmp.github.io | a4bd01c55def4dcc58408fd2a8726a9b938aeb05 | [
"MIT"
] | null | null | null | _pages/cat_data_vis.md | burrussmp/burrussmp.github.io | a4bd01c55def4dcc58408fd2a8726a9b938aeb05 | [
"MIT"
] | null | null | null | ---
type: category
layout: archive
author_profile: true
permalink: /categories/data-visualization
taxonomy: Data Visualization
title: "Data Visualization"
header:
og_image: /assets/images/website_feature_image.png
overlay_image: /assets/images/header-image-2.png
caption: Copyright © Matthew Burruss
search: true
---
<p style="visibility:hidden">Blog posts in category "Data Visualization"</p> | 28.5 | 76 | 0.789474 | kor_Hang | 0.252971 |
aa3ba914eb095482d246a58789c20ba7d740e837 | 3,893 | md | Markdown | wdk-ddi-src/content/storport/nf-storport-storportallocatecontiguousmemoryspecifycachenode.md | aktsuda/windows-driver-docs-ddi | a7b832e82cc99f77dbde72349c0a61670d8765d3 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | wdk-ddi-src/content/storport/nf-storport-storportallocatecontiguousmemoryspecifycachenode.md | aktsuda/windows-driver-docs-ddi | a7b832e82cc99f77dbde72349c0a61670d8765d3 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | wdk-ddi-src/content/storport/nf-storport-storportallocatecontiguousmemoryspecifycachenode.md | aktsuda/windows-driver-docs-ddi | a7b832e82cc99f77dbde72349c0a61670d8765d3 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
UID: NF:storport.StorPortAllocateContiguousMemorySpecifyCacheNode
title: StorPortAllocateContiguousMemorySpecifyCacheNode function
author: windows-driver-content
description: The StorPortAllocateContiguousMemorySpecifyCacheNode routine allocates a range of physically contiguous noncached, nonpaged memory.
old-location: storage\storportallocatecontiguousmemoryspecifycachenode.htm
old-project: storage
ms.assetid: b2ed8c88-9ffd-4601-8fd0-c9390e9ba84d
ms.author: windowsdriverdev
ms.date: 3/29/2018
ms.keywords: StorPortAllocateContiguousMemorySpecifyCacheNode, StorPortAllocateContiguousMemorySpecifyCacheNode routine [Storage Devices], storage.storportallocatecontiguousmemoryspecifycachenode, storport/StorPortAllocateContiguousMemorySpecifyCacheNode, storprt_d91d6ab4-677e-4bc0-a0b5-1c252475ecbb.xml
ms.prod: windows-hardware
ms.technology: windows-devices
ms.topic: function
req.header: storport.h
req.include-header: Storport.h
req.target-type: Universal
req.target-min-winverclnt: Available starting with Windows 7.
req.target-min-winversvr:
req.kmdf-ver:
req.umdf-ver:
req.ddi-compliance: StorPortIrql
req.unicode-ansi:
req.idl:
req.max-support:
req.namespace:
req.assembly:
req.type-library:
req.lib:
req.dll:
req.irql: "<=DISPATCH_LEVEL"
topic_type:
- APIRef
- kbSyntax
api_type:
- HeaderDef
api_location:
- storport.h
api_name:
- StorPortAllocateContiguousMemorySpecifyCacheNode
product:
- Windows
targetos: Windows
req.typenames:
---
# StorPortAllocateContiguousMemorySpecifyCacheNode function
## -description
The <b>StorPortAllocateContiguousMemorySpecifyCacheNode</b> routine allocates a range of physically contiguous noncached, nonpaged memory.
## -parameters
### -param HwDeviceExtension [in]
A pointer to the hardware device extension for the host bus adapter (HBA).
### -param NumberOfBytes [in]
The number of bytes to allocate.
### -param LowestAcceptableAddress [in]
The lowest physical address that is valid for the allocation. For example, if the device can only reference physical memory in the 8 MB to 16 MB range, this value would be set to 0x800000 (8 MB).
### -param HighestAcceptableAddress [in]
The highest physical address that is valid for the allocation. For example, if the device can only reference physical memory below 16 MB, this value would be set to 0xFFFFFF (16 MB - 1).
### -param BoundaryAddressMultiple [in, optional]
The physical address multiple that this allocation must not cross.
### -param CacheType [in]
The desired cache type for the mapping.
### -param PreferredNode [in]
The preferred node from which the allocation should be made if pages are available on that node.
### -param BufferPointer [out]
The variable that receives the starting address of the allocated memory block. Upon return from this routine, if this variable is zero, a contiguous range could not be found to satisfy the request. If this variable is not <b>NULL</b>, it contains a pointer (for example, a virtual address in the nonpaged portion of the system) to the allocated physically contiguous memory.
## -returns
The <b>StorPortAllocateContiguousMemorySpecifyCacheNode</b> routine returns one of the following status codes:
<table>
<tr>
<th>Return code</th>
<th>Description</th>
</tr>
<tr>
<td width="40%">
<dl>
<dt><b>STOR_STATUS_NOT_IMPLEMENTED</b></dt>
</dl>
</td>
<td width="60%">
This function is not implemented on the active operating system.
</td>
</tr>
<tr>
<td width="40%">
<dl>
<dt><b>STOR_STATUS_SUCCESS</b></dt>
</dl>
</td>
<td width="60%">
The operation was successful.
</td>
</tr>
<tr>
<td width="40%">
<dl>
<dt><b>STOR_STATUS_INSUFFICIENT_RESOURCES</b></dt>
</dl>
</td>
<td width="60%">
The operation failed to allocate the requested memory because of insufficient resources.
</td>
</tr>
</table>
## -remarks
If the request fails, <i>BufferPointer</i> will be set to <b>NULL</b>.
| 24.484277 | 374 | 0.776522 | eng_Latn | 0.916514 |
aa3bd5ad2905e8b76923dbd760661e5bfe05c351 | 7,076 | md | Markdown | articles/app-service/overview-inbound-outbound-ips.md | matmahnke/azure-docs.pt-br | 6c96d25caf8663547775f333164198e3ed03972f | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/app-service/overview-inbound-outbound-ips.md | matmahnke/azure-docs.pt-br | 6c96d25caf8663547775f333164198e3ed03972f | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/app-service/overview-inbound-outbound-ips.md | matmahnke/azure-docs.pt-br | 6c96d25caf8663547775f333164198e3ed03972f | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Endereços IP de entrada/saída
description: Saiba como os endereços IP de entrada e saída são usados no serviço Azure App, quando eles mudam e como encontrar os endereços para seu aplicativo.
ms.topic: article
ms.date: 08/25/2020
ms.custom: seodec18, devx-track-azurecli
ms.openlocfilehash: e5b271cc5cd8cb52267b6ee44bc3965d0e4b0aab
ms.sourcegitcommit: 8c7f47cc301ca07e7901d95b5fb81f08e6577550
ms.translationtype: MT
ms.contentlocale: pt-BR
ms.lasthandoff: 10/27/2020
ms.locfileid: "92746151"
---
# <a name="inbound-and-outbound-ip-addresses-in-azure-app-service"></a>Endereços IP de entrada e saída no Serviço de Aplicativo do Azure
O [Serviço de Aplicativo do Azure](overview.md) é um serviço multilocatário, exceto para [Ambientes de Serviço de Aplicativo](environment/intro.md). Aplicativos que não estão em um ambiente de Serviço de Aplicativo (não na [Camada isolada](https://azure.microsoft.com/pricing/details/app-service/)) compartilham a infraestrutura de rede com outros aplicativos. Como resultado, os endereços IP de entrada e saída de um aplicativo podem ser diferentes e até alterar em determinadas situações.
[Ambientes de Serviço de Aplicativo](environment/intro.md) usam infraestruturas de rede dedicadas para que aplicativos executados em um ambiente de Serviço de Aplicativo obtenham endereços IP dedicados e estáticos para conexões de entrada e saída.
## <a name="how-ip-addresses-work-in-app-service"></a>Como os endereços IP funcionam no serviço de aplicativo
Um aplicativo do serviço de aplicativo é executado em um plano do serviço de aplicativo, e os planos do serviço de aplicativo são implantados em uma das unidades de implantação na infraestrutura do Azure (internamente chamada de espaço Web). Cada unidade de implantação é atribuída a até cinco endereços IP virtuais, o que inclui um endereço IP de entrada público e quatro endereços IP de saída. Todos os planos do serviço de aplicativo na mesma unidade de implantação e as instâncias de aplicativo que são executados neles compartilham o mesmo conjunto de endereços IP virtuais. Para um Ambiente do Serviço de Aplicativo (um plano do serviço de aplicativo na [camada isolada](https://azure.microsoft.com/pricing/details/app-service/)), o plano do serviço de aplicativo é a própria unidade de implantação e, portanto, os endereços IP virtuais são dedicados a ele como resultado.
Como você não tem permissão para mover um plano do serviço de aplicativo entre as unidades de implantação, os endereços IP virtuais atribuídos ao seu aplicativo geralmente permanecem os mesmos, mas há exceções.
## <a name="when-inbound-ip-changes"></a>Quando ocorrem alterações do IP de entrada
Independentemente do número de instâncias dimensionadas, cada aplicativo tem um único endereço IP de entrada. O endereço IP de entrada pode alterar ao executar uma das ações a seguir:
- Exclua um aplicativo e recrie-o em um grupo de recursos diferente (a unidade de implantação pode ser alterada).
- Excluir o último aplicativo em um grupo de recursos _e_ uma combinação de região e recriá-lo (a unidade de implantação pode ser alterada).
- Exclua uma associação TLS/SSL baseada em IP existente, como durante a renovação do certificado (consulte [renovar certificado](configure-ssl-certificate.md#renew-certificate)).
## <a name="find-the-inbound-ip"></a>Localizar o IP de entrada
Basta executar o seguinte comando em um terminal local:
```bash
nslookup <app-name>.azurewebsites.net
```
## <a name="get-a-static-inbound-ip"></a>Obter um IP de entrada estático
Às vezes, é possível querer um endereço IP dedicado e estático para o aplicativo. Para obter um endereço IP de entrada estático, você precisa [proteger um domínio personalizado](configure-ssl-bindings.md#secure-a-custom-domain). Se você não precisar realmente da funcionalidade de TLS para proteger seu aplicativo, você pode até mesmo carregar um certificado autoassinado para essa associação. Em uma associação TLS baseada em IP, o certificado é associado ao endereço IP em si, portanto, o serviço de aplicativo provisiona um endereço IP estático para que ele aconteça.
## <a name="when-outbound-ips-change"></a>Quando ocorrem alterações dos IPs de saída
Independentemente do número de instâncias dimensionadas, cada aplicativo tem um número definido de endereços IP de saída a qualquer momento. Qualquer conexão de saída do aplicativo do Serviço de Aplicativo, como um banco de dados back-end, usa um dos endereços IP de saída como o endereço IP de origem. O endereço IP a ser usado é selecionado aleatoriamente em tempo de execução, de modo que o serviço de back-end deve abrir seu firewall para todos os endereços IP de saída para seu aplicativo.
O conjunto de endereços IP de saída para seu aplicativo é alterado quando você executa uma das seguintes ações:
- Exclua um aplicativo e recrie-o em um grupo de recursos diferente (a unidade de implantação pode ser alterada).
- Excluir o último aplicativo em um grupo de recursos _e_ uma combinação de região e recriá-lo (a unidade de implantação pode ser alterada).
- Dimensione seu aplicativo entre as camadas inferiores ( **Basic** , **Standard** e **Premium** ) e a camada **Premium v2** (os endereços IP podem ser adicionados ou subtraídos do conjunto).
Você pode encontrar o conjunto de todos os endereços IP de saída possíveis que seu aplicativo pode usar, independentemente dos tipos de preço, procurando a `possibleOutboundIpAddresses` propriedade ou no campo **endereços IP de saída adicionais** na folha **Propriedades** no portal do Azure. Consulte [Localizar IPs de saída](#find-outbound-ips).
## <a name="find-outbound-ips"></a>Localizar IPs de saída
Para localizar os endereços IP de saída atualmente usados pelo aplicativo no Portal do Azure, clique em **Propriedades** na navegação esquerda do aplicativo. Eles são listados no campo **endereços IP de saída** .
É possível localizar as mesmas informações, executando o comando a seguir no [Cloud Shell](../cloud-shell/quickstart.md).
```azurecli-interactive
az webapp show --resource-group <group_name> --name <app_name> --query outboundIpAddresses --output tsv
```
```azurepowershell
(Get-AzWebApp -ResourceGroup <group_name> -name <app_name>).OutboundIpAddresses
```
Para localizar _todos os_ endereços IP de saída possíveis para seu aplicativo, independentemente dos tipos de preço, clique em **Propriedades** na navegação esquerda do seu aplicativo. Eles são listados no campo **endereços IP de saída adicionais** .
É possível localizar as mesmas informações, executando o comando a seguir no [Cloud Shell](../cloud-shell/quickstart.md).
```azurecli-interactive
az webapp show --resource-group <group_name> --name <app_name> --query possibleOutboundIpAddresses --output tsv
```
```azurepowershell
(Get-AzWebApp -ResourceGroup <group_name> -name <app_name>).PossibleOutboundIpAddresses
```
## <a name="next-steps"></a>Próximas etapas
Saiba como restringir o tráfego de entrada por endereços IP de origem.
> [!div class="nextstepaction"]
> [Restrições de IP estático](app-service-ip-restrictions.md)
| 78.622222 | 878 | 0.794093 | por_Latn | 0.999653 |
aa3cc4d468291758f51318f53f0646fd7eb69d71 | 1,550 | md | Markdown | README.md | Neui/cc-things | 35fb5af0f3aa4620a9e2e3e4ff8a2e8c04be6533 | [
"MIT"
] | null | null | null | README.md | Neui/cc-things | 35fb5af0f3aa4620a9e2e3e4ff8a2e8c04be6533 | [
"MIT"
] | null | null | null | README.md | Neui/cc-things | 35fb5af0f3aa4620a9e2e3e4ff8a2e8c04be6533 | [
"MIT"
] | null | null | null | <!-- Written in Markdown, use it to view it! -->
Programs and Snippets <sub><sup>for [Minecraft][MC Web] modification [computercraft][CC Web]</sup></sub>
====================================================================================
###### For Snippets, see the README.md in the folder `snippets`
Some programs might be uploaded to pastebin to download it directly to computercraft
very easily.
Just write `pastebin get <id> <name>` where `<id>` is the ID on pastebin <sub><sup>(it says next to the title, if it is `<todo>` then it hasn't uploaded yet)</sup></sub> and `<name>` is a filename you wish to save in.
minccweeper [`aY3iP8SF`][pb mineccweeper] <sub>(WIP)</sub>
-------------
This is a game based on minesweeper.
ccbash [`<todo>`][pb ccbash]<sub>(WIP)</sub>
--------
This is a shell based on the bash shell.
labyrinth [`MJS1fywR`][pb labyrinth]<sub>(WIP)</sub>
-----------
This is based of [illacceptanything/illacceptanything/labyrinth](https://github.com/illacceptanything/illacceptanything/tree/master/labyrinth). This is a labyrinth made in a filesystem/git/github repo.
This program should let you "explore" it inside of ComputerCraft.
It includes the labyrinth from github in the program, but there will be a way to use the files so multiple can be used easily.
<!---- LINK LIST ---->
<!-- Programs -->
[pb mineccweeper]: http://pastebin.com/aY3iP8SF
[pb ccbash]: http://pastebin.com
[pb labyrinth]: http://pastebin.com/MJS1fywR
<!-- Other things -->
[MC Web]: http://minecraft.net
[CC Web]: http://computercraft.info | 46.969697 | 217 | 0.669032 | eng_Latn | 0.932354 |
aa3ea88d56080dde31f7e0cc6e970b620e7db18b | 2,856 | md | Markdown | crusoe_observe/sabu-connector/README.md | CSIRT-MU/CRUSOE | 73e4ac0ced6c3ac46d24ac5c3feb01a1e88bd36b | [
"MIT"
] | 3 | 2021-11-09T09:55:17.000Z | 2022-02-19T02:58:27.000Z | crusoe_observe/sabu-connector/README.md | CSIRT-MU/CRUSOE | 73e4ac0ced6c3ac46d24ac5c3feb01a1e88bd36b | [
"MIT"
] | null | null | null | crusoe_observe/sabu-connector/README.md | CSIRT-MU/CRUSOE | 73e4ac0ced6c3ac46d24ac5c3feb01a1e88bd36b | [
"MIT"
] | null | null | null | # SABU connector
SABU connector receives IDEA messages containing information about vulnerabilities found within Masaryk University network from system Warden (* https://warden.cesnet.cz//en/index).
Connector parses the message and saves information into Neo4j database. It is possible to change IP regex in celery config so you are not restricted to only receive vulnerabilities
within Masaryk University network.
## Design
Connector consists of a single file JsonParsing.py. It checks for a running instance of Warden system, then starts parsing messages
received from Warden. These messages are of type IDEA described <a href="https://idea.cesnet.cz/en/index
">here</a>). After all messages are parsed, data obtained are sent to neo4j database (e.g. IP of the attacker, description of the event).
## Required packages/versions
Python 3.7+
Required packages are specified in setup.py and will be installed when you use one of the installation methods below.
You need to have a running Warden system for sabu-connector to work properly.
To achieve this, visit https://warden.cesnet.cz/ and apply for permission to
receive Warden messages (how to do that is described <a href="https://warden.cesnet.cz/cs/participation
">here</a>).
You will also need a running neo4j database to store parsed data from warden messages.
Once you set Warden configs to satisfy your needs and have running Warden and neo4j, you can run sabu-connector.
## Usage
### Install
```bash
$ pip install .
```
### Running
``` python
>>> from sabu import JsonParsing
>>> JsonParsing.parse(directory="/directory/with/received/messages/",
passwd="neo4jpassword", regex="IPRangeMU",
path_to_warden_filer_receiver="/path/to/warden/receiver/",
path_to_neo4j="/directory/to/save/json/")
```
#### Parameters description
`directory` = in Warden config (`warden_filer.cfg`), you have to specify where
the messages are going to flow from Warden system (e.g. "/var/warden_receiver")
In this 'directory', three seperate directories will be created by Warden:
`errors`, `incoming` and `temp`. You will find received messages in the `incoming`.
`passwd` = Password required to connect to neo4j database.
`regex` = Regular expression used to filter messages with given IP prefix in it
(e.g. `147\.251\.[0-2]?[0-9]?[0-9]\.[0-2]?[0-9]?[0-9]?` for Masaryk University
network.)
`path_to_warden_filer_receiver` = This path is used to check whether Warden is
running or not. If not, it will try to restart it and upon unsuccessfull restart
raise an custom WardenException.
`path_to_neo4j` = Directory in which the final JSON with parsed data from received
messages is stored and processed by neo4j client. Neo4j client si a custom script
consisting of Cypher commands, where Cypher is a Neo4j's graph query language.
| 43.938462 | 182 | 0.752801 | eng_Latn | 0.996508 |
aa404ddc78504a2343d889d6c91de16bcadcbfee | 906 | md | Markdown | README.md | vrklgn/facelist | 914337069c04cbccf7ef1ce7e503631b0ba41ae4 | [
"Apache-2.0"
] | null | null | null | README.md | vrklgn/facelist | 914337069c04cbccf7ef1ce7e503631b0ba41ae4 | [
"Apache-2.0"
] | null | null | null | README.md | vrklgn/facelist | 914337069c04cbccf7ef1ce7e503631b0ba41ae4 | [
"Apache-2.0"
] | null | null | null | Facelist
========
An app that queries Slack API for user profiles and show them on a simple web page.
Configuration
=============
facelist is configured by a config file e.g facelist.yaml:
* emailFilters - Only users with a email ending with one of these strings will be showed
* slackTeam - The name of your slack team
* slackAPIToken - Access token to the Slack api
The API-token requires the scopes:
* users:read
* users:read.email
Development
===========
Download external dependencies
$ go mod download
Build and run locally:
$ go build
$ ./facelist
The facelist should be served at http://localhost:8080/
Deploy app
==========
The included dockerfile can be used to deploy the app.
Alernative Local deployment with docker-compose
===============================================
$ docker-compose -d up
The facelist should be served at http://localhost:8080/
| 21.069767 | 92 | 0.669978 | eng_Latn | 0.984345 |
aa408446a252b257645fa4224580e330a0749d5b | 1,117 | md | Markdown | docs/Bestiary/u/ugash-iram.md | petersgiles/savage-tales-of-adventure | 2196083c62f52cc782ad19d632c14c30e9b78f1b | [
"MIT"
] | null | null | null | docs/Bestiary/u/ugash-iram.md | petersgiles/savage-tales-of-adventure | 2196083c62f52cc782ad19d632c14c30e9b78f1b | [
"MIT"
] | 2 | 2021-05-11T13:23:13.000Z | 2021-06-28T19:56:48.000Z | docs/Bestiary/u/ugash-iram.md | petersgiles/savage-tales-of-adventure | 2196083c62f52cc782ad19d632c14c30e9b78f1b | [
"MIT"
] | null | null | null | # Ugash-iram
No description for this creature yet.
**Attributes:** Agility d12+1, Smarts d8, Spirit d12+1, Strength d12+4,
Vigor d12+3
**Skills:** Fighting d12+1, Notice d12+1, Knowledge (Planes) d10,
Stealth d12+2, Swimming d12+2, Spellcasting d8
**Charisma:** +1; **Pace:** 1; **Parry:** 8; **Toughness:** 28 (5)
**Edges:** Arcane Background (Magic), Combat Reflexes, Level Headed,
Sweep
**Powers:** Lower Trait (curse), Puppet
**Special Abilities**
- **Armour +5:** Natural armour.
- **Tentacles:** Str+d8; Reach 1"; Grab.
- **Low Light Vision:** No penalties for dim or dark lighting.
- **Darkvision:** No vision penalties for darkness (range 24").
- **Grab:** Pin your opponent if you hit with a raise, they require a
raise on an opposed Strength roll to escape.
- **Aquatic:** Swimming Pace of 14", and cannot drown.
- **Resistances:** -2 damage from acid and cold.
- **Poison:** Inflict lethal poison if foe is Shaken or wounded.
- **Size +14:** Increases Toughness by +14.
- **Gargantuan:** -4 to attack medium-sized foes, they receive +4 to
their attacks. Counts as having Heavy Armour and Heavy Weapons.
| 41.37037 | 71 | 0.696509 | eng_Latn | 0.903979 |
aa40d3f88ed4bdbeb0ba004ff182250dd74c8f76 | 206 | md | Markdown | _docs/guide.md | Adaickalavan/adaickalavan.github.io | 924e5f3e5008dc1316195e76cb6748249e957312 | [
"MIT"
] | 1 | 2021-12-10T07:41:35.000Z | 2021-12-10T07:41:35.000Z | _docs/guide.md | Adaickalavan/adaickalavan.github.io | 924e5f3e5008dc1316195e76cb6748249e957312 | [
"MIT"
] | null | null | null | _docs/guide.md | Adaickalavan/adaickalavan.github.io | 924e5f3e5008dc1316195e76cb6748249e957312 | [
"MIT"
] | 2 | 2017-08-01T16:59:36.000Z | 2021-04-28T01:28:32.000Z | ---
title: "Guide"
toc: false
---
Here we document the computer setup steps and software development standards adopted in our projects.
[](/assets/images/guide_01.jpg) | 25.75 | 101 | 0.752427 | eng_Latn | 0.859039 |
aa425652c73a60959097a6cc7ca01b8aa6e403f9 | 134 | md | Markdown | README.md | jonra1993/AR-Roulette | aa92d58aa87af5712776013a79dff67f5916d8fc | [
"Apache-2.0"
] | null | null | null | README.md | jonra1993/AR-Roulette | aa92d58aa87af5712776013a79dff67f5916d8fc | [
"Apache-2.0"
] | null | null | null | README.md | jonra1993/AR-Roulette | aa92d58aa87af5712776013a79dff67f5916d8fc | [
"Apache-2.0"
] | null | null | null | # AR-Roulette
This project is an Android augment Reality App for Android devices of a Roulette. It uses Unity3D and EasyAR Framework.
| 44.666667 | 119 | 0.80597 | eng_Latn | 0.971207 |
aa43fc7020ea2ba90b301074665d418e4211148e | 63 | md | Markdown | 300-logic/xpages/formal-methods.md | mandober/mcs-topics | 3afc7936579dfefd7f823d774c4ac17cc6c57666 | [
"Unlicense"
] | 1 | 2019-01-18T21:56:33.000Z | 2019-01-18T21:56:33.000Z | 300-logic/xpages/formal-methods.md | mandober/eiirp | 3afc7936579dfefd7f823d774c4ac17cc6c57666 | [
"Unlicense"
] | 1 | 2019-06-16T19:34:58.000Z | 2019-06-16T19:35:03.000Z | 300-logic/xpages/formal-methods.md | mandober/dust-dllci | 3afc7936579dfefd7f823d774c4ac17cc6c57666 | [
"Unlicense"
] | null | null | null | # Formal methods
https://en.wikipedia.org/wiki/Formal_methods
| 15.75 | 44 | 0.793651 | deu_Latn | 0.298344 |
aa4426a9d974ee23060110c5096ae0c286a3c4dd | 1,718 | md | Markdown | cv.md | afarciniegasm/afarciniegasm.github.io | 9be046ba93f12ebb9e7746b9e8451c5c6d9bdd4d | [
"MIT"
] | null | null | null | cv.md | afarciniegasm/afarciniegasm.github.io | 9be046ba93f12ebb9e7746b9e8451c5c6d9bdd4d | [
"MIT"
] | null | null | null | cv.md | afarciniegasm/afarciniegasm.github.io | 9be046ba93f12ebb9e7746b9e8451c5c6d9bdd4d | [
"MIT"
] | null | null | null | ---
layout: page
title: Curriculum Vitae
sidebar_link: true
sidebar_sort_order: 2
excerpt_separator: <!--more-->
font-size: 7px
---
# Expériences professionnelles :
<html>
<table>
<tbody>
<tr>
<td > <b>Depuis <br> Sept. 2018</b> </td>
<td> <b>Maître de Conférences</b> - CY Cergy Paris Université - Laboratoire SATIE UMR CNRS 8029. </td>
</tr>
<tr>
<td> <b>Sept. 2017 - <br> Août 2018</b></td>
<td> <b>ATER</b> à l'IUT de Blois et au Laboratoire GREMAN UMR CNRS 7347. </td>
</tr>
<tr>
<td> <b>Nov. 2016 - <br> Août 2017</b></td>
<td> <b>Postdoctorant</b> au Laboratoire SATIE UMR CNRS 8029. </td>
</tr>
<tr>
<td> <b> Oct. 2015 - <br> Oct. 2016 </b></td>
<td> <b>Postdoctorant</b> au Laboratoire GREMAN UMR CNRS 7347. </td>
</tr>
<tr>
<td> <b> Nov. 2011 - <br> Nov. 2014 </b></td>
<td> <b>Doctorant</b> au Laboratoire de Mécanique et d'Acoustique de Marseille UMR CNRS 7031. </td>
</tr>
</tbody>
</table>
</html>
# Formation universitaire :
<html>
<table>
<tbody>
<tr>
<td> <b>Nov. 2011 - <br> Nov. 2014</b></td>
<td> <b>Doctorat d’Acoustique</b> avec mention très honorable. <br> Laboratoire LMA UMR CNRS 7031, Université d’Aix-Marseille, Marseille.</td>
</tr>
<tr>
<td> <b>Sept. 2010 - <br> Juill. 2011</b></td>
<td> <b>Master 2 Recherche en Électronique, Signal et Microsystèmes.</b> <br> École Nationale d’Ingénieurs
du Val de Loire, Blois.</td>
</tr>
<tr>
<td> <b>Août 2006 - <br> Juill. 2011</b></td>
<td> <b>Ingénieur en Électronique.</b> <br> Université Nationale de Colombie, Bogota (COLOMBIE).</td>
</tr>
</tbody>
</table>
</html>
| 28.633333 | 148 | 0.582654 | kor_Hang | 0.257 |
aa444cc94666444655c79be2708047c083534806 | 6,546 | md | Markdown | sections/zapier-integration.md | 10kmctaggart/10kft-api | 3c8312997e625842d1bc4f753f369f72625575b1 | [
"MIT"
] | null | null | null | sections/zapier-integration.md | 10kmctaggart/10kft-api | 3c8312997e625842d1bc4f753f369f72625575b1 | [
"MIT"
] | null | null | null | sections/zapier-integration.md | 10kmctaggart/10kft-api | 3c8312997e625842d1bc4f753f369f72625575b1 | [
"MIT"
] | null | null | null | # 10,000ft Zapier Integration
Zapier is a web automation service that lets you integrate 10,000ft with thousands of other apps. You can read more details on the 10,000ft + Zapier [integrations page](https://zapier.com/apps/10000ft/integrations).
## Requirements
* A 10,000ft account
* A Zapier account
* Optionally, an account with each service that will be connected with 10,000ft via Zapier
Zapier provides free and paid plans. See the [Zapier pricing page](https://zapier.com/app/pricing) for more info.
## Connecting 10,000ft with Zapier
* This step is only required when connecting 10,000ft with your Zapier account for the first time
* Start by making a new Zap in your Zapier account
* Find the 10,000ft app and pick any trigger to initiate the setup
* When prompted, add the 10,000ft API Token into Zapier, test and save your connection
<img src="../assets/make-a-zap/3.png" alt="add API token" width="480">
Once the connection is setup and tested, you can use it to make new Zap. Lets go through the steps and setup an example Zap.
## Configuring a Zap
Configuring a 10,000ft Zap typically involves,
* Connecting your 10,000ft account with Zapier
* Selecting a 10,000ft trigger
* Optionally, configure one or more Search steps to look up additional details
* 10,000ft Triggers typically return user or assignable IDs
* We provide find actions so you can get additional details (e.g. a user's email address) given their ID
* This allows you to combine attributes you get from the trigger with additional attributes you get via searching to create Zaps that are rich in details and provide higher value.
* Choosing an app to connect with (e.g. Email)
* Configure, test and enable your Zap
## Example: Send an email when a new assignment is made in 10,000ft
Lets try a specific example. In the steps below we will make a Zap that will send an email to when one of your team members are assigned to a project. When you are done, this is what the outline of your Zap will look like,
<img src="../assets/make-a-zap/overview.png" alt="overview" width="480">
And here are the steps in detail,
* Sign in to your Zapier account
* Start a Zap
* Search for the 10,000ft app and select it
* Select a 10,000ft Trigger (e.g. New Assignment)
<img src="../assets/make-a-zap/1.png" alt="new assignment trigger" width="480">
* Connect your 10,000ft app if prompted by supplying your 10,000ft API token
* Add a step to search 10,000ft and lookup details for the user_id in the assignment
<img src="../assets/make-a-zap/6.png" alt="find user by id options" width="480">
* Add a step and select 10,000ft as the app
* Search and select the `Find User by ID` action
* Configure it to find the user for the `user_id` from the New Assignment trigger we setup above
* Add a step to search 10,000ft and lookup details for the assignable_id in the assignment
* Add a step and select 10,000ft as the app
* Search and select the `Find Assignable by ID` action
* Configure it to find the assignable for the `assignable_id` from the New Assignment trigger we setup above
* Add a step to send an email
<img src="../assets/make-a-zap/email-template-options.png" alt="email template options" width="480">
* Select the Email by Zapier app
* Configure it to send an email to user in the New Assignment
* When you are done, the email template will look like this,
* Test and enable your Zap.
Now, when a new assignment is made on the 10,000ft schedule, the person who was assigned will be sent an email with the name of the Project (or Leave) that they were assigned to and the start date of that assignment.
## Filters & additional considerations
Zapier Filters are useful when building integrations with 10,000ft. You can use any attribute from a trigger of search action when implementing a filter. The `Type` attribute available in 10,000ft users and assignabled are particularly useful. For example, in the example above your Zap would typically exclude Placeholder users. This would be implemented by adding a FIlter to you Zap as shown below.
<img src="../assets/make-a-zap/filter-options.png" alt="email filter options" width="480">
Familiarize yourself with the different types of users and assignables available in 10,000ft when designing your 10,000ft Zaps so you can get the result you are trying to achive with your integration. See [10,000ft API documentation](../README.md) for more details on specific attributes.
## Triggers
10,000ft provides the following Triggers
* **New Assignment** Triggers when a new assignment is created.
* **New User** Triggers when a new user is created.
* **New Project** Triggers when a new project gets created.
* **New Time Entry** Triggers when a new time entry is created.
* **Assignment Updated** Triggers when an assignment is updated.
* **User Updated** Triggers when a new user is updated.
* **Project Updated** Triggers when a project gets updated.
* **Time Entry Updated** Triggers when a new time entry is updated.
## Actions
10,000ft provides the following actions for creating or updating information in your 10,000ft account via Zapier
* **Create Project** Create a new project.
* **Create User** Create a new team member.
* **Create Time Entry** Create a new time entry.
* **Update Project** Updates a project.
* **Update User** Updates a team member.
* **Update Time Entry** Update a time entry.
## Searches
* **Find Assignable by ID** Finds an existing assignable by the assignable's ID. An assignable is anything that can be assigned to a user such as a Project or Leave type.
* **Find Project by ID** Finds an existing project using the project's ID.
* **Find User by ID** Finds an existing user by their ID.
* **Find User by Email** Finds an existing user by their email.
* **Find User by Name** Finds an existing user by their name.
* **Find Assignable by Name** Finds an existing assignable by name.
* **Find Project by Name** Finds an existing project by name.
## More details about the 10,000ft API
Zapier is a convenient and powerful way to consume the 10,000ft API. The triggers, actions and searches listed above allow you to access commonly used API functionality without having to develop custom API integrations or write software code.
The 10,000ft API provides access to a number of advancaed features that are not currently supported with our Zapier triggers and actions. See [10,000ft API documentation](../README.md) for more details and email us questions to support@10000ft.com.
| 49.218045 | 401 | 0.754965 | eng_Latn | 0.998258 |
aa4459f8296ec65d56e7b61129d28d4f76832e89 | 9,130 | md | Markdown | translations/de-DE/content/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-repository-management-policies-in-your-enterprise-account.md | roamroam3/docs | d3099ded2a411e1550b2432d68fe18d992bbea85 | [
"CC-BY-4.0",
"MIT"
] | 5 | 2021-06-04T01:10:20.000Z | 2021-11-16T12:08:14.000Z | translations/de-DE/content/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-repository-management-policies-in-your-enterprise-account.md | roamroam3/docs | d3099ded2a411e1550b2432d68fe18d992bbea85 | [
"CC-BY-4.0",
"MIT"
] | 7 | 2021-09-01T20:07:07.000Z | 2022-03-30T06:25:14.000Z | translations/de-DE/content/github/setting-up-and-managing-your-enterprise/setting-policies-for-organizations-in-your-enterprise-account/enforcing-repository-management-policies-in-your-enterprise-account.md | roamroam3/docs | d3099ded2a411e1550b2432d68fe18d992bbea85 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-07-29T11:56:22.000Z | 2021-07-29T11:56:22.000Z | ---
title: Richtlinien zur Repository-Verwaltung in Deinem Enterprise-Konto erzwingen
intro: 'Enterprise-Inhaber können bestimmte Richtlinien zur Repository-Verwaltung für alle Organisationen erzwingen, die einem Enterprise-Konto gehören, oder zulassen, dass Richtlinien in jeder Organisation festgelegt werden.'
product: '{% data reusables.gated-features.enterprise-accounts %}'
redirect_from:
- /articles/enforcing-repository-management-settings-for-organizations-in-your-business-account/
- /articles/enforcing-repository-management-policies-for-organizations-in-your-enterprise-account/
- /articles/enforcing-repository-management-policies-in-your-enterprise-account
- /github/setting-up-and-managing-your-enterprise-account/enforcing-repository-management-policies-in-your-enterprise-account
- /github/setting-up-and-managing-your-enterprise/enforcing-repository-management-policies-in-your-enterprise-account
versions:
free-pro-team: '*'
topics:
- Enterprise
---
Weitere Informationen finden Sie unter„[Berechtigungsebenen für die Repositorys einer Organisation](/articles/repository-permission-levels-for-an-organization)“.
### Eine Richtlinie zu standardmäßigen Repository-Berechtigungen erzwingen
Für alle Organisationen Deines Enterprise-Kontos kannst Du eine standardmäßige Repository-Berechtigungsebene (keine, Lese-, Schreib- oder Administratorberechtigungen) für Organisationsmitglieder festlegen oder es Inhabern gestatten, diese Einstellung auf Organisationsebene zu verwalten.
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
4. Lies auf der Registerkarte **Repository policies** (Repository-Richtlinien) unter „Default permissions“ (Standardberechtigungen) die Informationen zum Ändern der Einstellung. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
5. Wähle im Dropdownmenü unter „Default permissions“ (Standardberechtigungen) eine Richtlinie aus. 
### Eine Richtlinie zum Erstellen von Repositorys erzwingen
In allen Organisationen Deines Enterprise-Kontos kannst Du festlegen, dass Mitglieder Repositorys erstellen können, die Repository-Erstellung auf Organisationsinhaber einschränken oder es Inhabern ermöglichen, die Einstellung auf Organisationsebene zu verwalten. Wenn Du Mitgliedern erlaubst, Repositorys zu erstellen, kannst Du angeben, ob die Mitglieder eine beliebige Kombination aus öffentlichen, privaten und internen Repositorys erstellen können. {% data reusables.repositories.internal-repo-default %} Weitere Informationen über interne Repositorys findest Du unter „[Ein internes Repository erstellen](/articles/creating-an-internal-repository)."
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
3. Lies auf der Registerkarte **Repository policies** (Repository-Richtlinien) unter „Repository creation“ (Repository-Erstellung) die Informationen zum Ändern der Einstellung. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
{% data reusables.enterprise-accounts.repo-creation-policy %}
{% data reusables.enterprise-accounts.repo-creation-types %}
6. Klicke auf **Save** (Speichern).
### Eine Richtlinie zum Forken privater oder interner Repositorys erzwingen
Für alle Organisationen Deines Enterprise-Kontos kannst Du Benutzern mit Zugriff auf ein privates oder internes Repository das Forken dieses Repositorys erlauben, das Forken privater oder interner Repositorys immer untersagen oder es Inhabern gestatten, diese Einstellung auf Organisationsebene zu verwalten.
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
3. Lies auf der Registerkarte **Repository policies** (Repository-Richtlinien) unter „Repository forking“ (Repository-Forking) die Informationen zum Ändern der Einstellung. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
4. Wähle im Dropdownmenü unter „Repository forking“ (Repository-Forking) eine Richtlinie aus. 
### Eine Richtlinie zum Einladen externer Mitarbeiter zu Repositorys erzwingen
In allen Organisationen Deines Enterprise-Kontos kannst Du Mitgliedern das Einladen von externen Mitarbeitern zu Repositorys erlauben, Einladungen externer Mitarbeiter auf Organisationsinhaber beschränken oder es Inhabern ermöglichen, die Einstellung auf Organisationsebene zu verwalten.
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
3. Lies auf der Registerkarte **Repository policies** (Repository-Richtlinien) unter „Repository invitations“ (Repository-Einladungen) die Informationen zum Ändern der Einstellung. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
4. Under "Repository invitations", use the drop-down menu and choose a policy. 
### Eine Richtlinie zum Ändern der Repository-Sichtbarkeit erzwingen
In allen Organisationen Ihres Enterprise-Kontos können Sie Mitgliedern mit Administratorberechtigungen das Ändern der Sichtbarkeit eines Repositorys erlauben, Änderungen der Repository-Sichtbarkeit auf Organisationsinhaber beschränken oder es Inhabern ermöglichen, die Einstellung auf Organisationsebene zu verwalten.
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
3. Lies auf der Registerkarte **Repository policies** (Repository-Richtlinien) unter „Repository visibility change“ (Änderung der Repository-Sichtbarkeit) die Informationen zum Ändern der Einstellung. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
{% data reusables.enterprise-accounts.repository-visibility-policy %}
### Eine Richtlinie zum Löschen oder Übertragen von Repositorys erzwingen
In allen Organisationen Ihres Enterprise-Kontos können Sie Mitgliedern mit Administratorberechtigungen das Löschen oder Übertragen eines Repositorys erlauben, das Löschen und Übertragen von Repositorys auf Organisationsinhaber beschränken oder es Inhabern ermöglichen, die Einstellung auf Organisationsebene zu verwalten.
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
3. Lies auf der Registerkarte **Repository policies** (Repository-Richtlinien) unter „Repository deletion and transfer“ (Löschen und Übertragen von Repositorys) die Informationen zum Ändern der Einstellung. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
{% data reusables.enterprise-accounts.repository-deletion-policy %}
### Eine Richtlinie zum Löschen von Issues erzwingen
In allen Organisationen Ihres Enterprise-Kontos können Sie Mitgliedern mit Administratorberechtigungen das Löschen von Issues in einem Repository erlauben, das Löschen von Issues auf Organisationsinhaber beschränken oder es Inhabern ermöglichen, die Einstellung auf Organisationsebene zu verwalten.
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
3. Lies auf der Registerkarte **Repository policies** (Repository-Richtlinien) unter „Repository issue deletion“ (Löschen von Repository-Issues) die Informationen zum Ändern der Einstellung. {% data reusables.enterprise-accounts.view-current-policy-config-orgs %}
4. Wähle im Dropdownmenü unter „Repository issue deletion“ (Löschen von Repository-Issues) eine Richtlinie aus. 
### Enforcing a policy on the default branch name
Across all organizations owned by your enterprise account, you can set the default branch name for any new repositories that members create. You can choose to enforce that default branch name across all organizations or allow individual organizations to set a different one.
{% data reusables.enterprise-accounts.access-enterprise %}
{% data reusables.enterprise-accounts.policies-tab %}
3. On the **Repository policies** tab, under "Default branch name", enter the default branch name that new repositories should use. 
4. Optionally, to enforce the default branch name for all organizations in the enterprise, select **Enforce across this enterprise**. 
5. Klicke auf **Update** (Aktualisieren). 
| 99.23913 | 654 | 0.823877 | deu_Latn | 0.855901 |
aa45ebc82ed851be5a82d6125264676045fb0088 | 972 | md | Markdown | README.md | mariopineda/mariopineda-CSE1110-assignment-3 | fbc11f66093279876c030da98ea2ded4bbee277c | [
"MIT"
] | null | null | null | README.md | mariopineda/mariopineda-CSE1110-assignment-3 | fbc11f66093279876c030da98ea2ded4bbee277c | [
"MIT"
] | 2 | 2018-05-23T19:46:17.000Z | 2018-06-14T17:22:04.000Z | README.md | Lordimpaler56/pde-graphics-3-collector-cards | 16d8642e0b9ba8ba00581fb0e328621d8c429861 | [
"MIT"
] | 14 | 2018-05-02T19:50:03.000Z | 2018-05-15T19:43:08.000Z | # processing-graphics-3-collector-cards
**[Assignment Standard Operating Procedures](https://github.com/mariopineda/assignment-sops)**
In this assignment you will be creating a collector card, e.g. a sports card (e.g. a hockey card), game card (e.g. Pokemon card) or an ID Card. You choose the type of card you would like to make. Your card must include the following components:
* a background colour
* at least one embedded image
* image(s) must be displayed with the correct aspect ratio
* text using at least one non-default font
* at least three [2D primitives](https://processing.org/reference/)
## Bonus Challenge
* an image for the canvas background
* at least 3 images
* more than three 2D primitives
* at least one [curve](https://processing.org/reference/)
* three or more different fonts
## References
* Fonts: https://processing.org/reference/PFont.html
* Text: http://processing.org/tutorials/text/
* Images: http://processing.org/tutorials/pixels/
| 42.26087 | 246 | 0.757202 | eng_Latn | 0.937936 |
aa47c4158ada940c17c568aa7eae9502e39fd30e | 983 | md | Markdown | Language/Reference/User-Interface-Help/tag-property.md | ryanmajidi/VBA-Docs | 8b07050f4ff38fcabda606284ec5f6f6634e9569 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | Language/Reference/User-Interface-Help/tag-property.md | ryanmajidi/VBA-Docs | 8b07050f4ff38fcabda606284ec5f6f6634e9569 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | Language/Reference/User-Interface-Help/tag-property.md | ryanmajidi/VBA-Docs | 8b07050f4ff38fcabda606284ec5f6f6634e9569 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Tag property
keywords: fm20.chm2002060
f1_keywords:
- fm20.chm2002060
ms.prod: office
api_name:
- Office.Tag
ms.assetid: 9cc2496d-f3c9-fca0-1e48-eb4ed0905b51
ms.date: 11/16/2018
---
# Tag property
Stores additional information about an object.
## Syntax
_object_.**Tag** [= _String_ ]
The **Tag** property syntax has these parts:
|Part|Description|
|:-----|:-----|
| _object_|Required. A valid object.|
| _String_|Optional. A string expression identifying the object. The default is a zero-length string ("").|
## Remarks
Use the **Tag** property to assign an identification string to an object without affecting other property settings or attributes.
For example, you can use **Tag** to check the identity of a form or control that is passed as a variable to a procedure.
## See also
- [Microsoft Forms examples](examples-microsoft-forms.md)
- [Microsoft Forms reference](reference-microsoft-forms.md)
- [Microsoft Forms concepts](concepts-microsoft-forms.md) | 25.205128 | 129 | 0.744659 | eng_Latn | 0.959165 |
aa4808ae7fe804e325d2c25e469e9677b17e3f75 | 551 | md | Markdown | site/_importers/jrnl.md | bunto/bunto-import | f605537fd1a3733c278d461acafa39643fd31bf8 | [
"MIT"
] | 1 | 2016-05-07T14:03:59.000Z | 2016-05-07T14:03:59.000Z | site/_importers/jrnl.md | bunto/bunto-import | f605537fd1a3733c278d461acafa39643fd31bf8 | [
"MIT"
] | 1 | 2016-04-10T10:26:12.000Z | 2016-04-10T10:26:37.000Z | site/_importers/jrnl.md | bunto/bunto-import | f605537fd1a3733c278d461acafa39643fd31bf8 | [
"MIT"
] | null | null | null | ---
layout: docs
title: Jrnl
prev_section: joomla3
link_source: jrnl
next_section: marley
permalink: /docs/jrnl/
---
To import your posts from [Jrnl](http://maebert.github.io/jrnl/), run:
{% highlight bash %}
$ ruby -rubygems -e 'require "bunto-import";
BuntoImport::Importers::Jrnl.run({
"file" => "~/journal.txt",
"time_format" => "%Y-%m-%d %H:%M",
"extension" => "md",
"layout" => "post"
})'
{% endhighlight %}
None of the fields are mandatory. The default to the values in the example
block above.
| 22.958333 | 74 | 0.622505 | eng_Latn | 0.65235 |
aa482684c2695bd422a6d22d2bc738a8d8c32f2c | 179 | md | Markdown | src/notes/js/_index.md | dkharazi/site | 5e9ec99af30d13bf262bbeb14a75d71c0ebc088b | [
"RSA-MD"
] | null | null | null | src/notes/js/_index.md | dkharazi/site | 5e9ec99af30d13bf262bbeb14a75d71c0ebc088b | [
"RSA-MD"
] | null | null | null | src/notes/js/_index.md | dkharazi/site | 5e9ec99af30d13bf262bbeb14a75d71c0ebc088b | [
"RSA-MD"
] | 1 | 2021-07-07T11:51:03.000Z | 2021-07-07T11:51:03.000Z | ---
title: "JavaScript"
subcategories: ["array", "this", "promises", "operators", "misc", "react"]
names: ["Array", "this", "Promises", "Operators", "Miscellaneous", "React"]
---
| 29.833333 | 75 | 0.625698 | eng_Latn | 0.287927 |
aa48b2c0de96c49c21e85f0e384bc66cf1385bd3 | 2,633 | md | Markdown | README.md | WhiteRaven777/uuid | b3cec15eac962ac46e88e6bdaf8e129368c33acb | [
"MIT"
] | 3 | 2021-07-24T09:47:33.000Z | 2022-02-14T15:49:14.000Z | README.md | WhiteRaven777/uuid | b3cec15eac962ac46e88e6bdaf8e129368c33acb | [
"MIT"
] | null | null | null | README.md | WhiteRaven777/uuid | b3cec15eac962ac46e88e6bdaf8e129368c33acb | [
"MIT"
] | null | null | null | # uuid
[![GoDoc Widget]][GoDoc]
`uuid` provides asynchronous unique numbering on the server side, based on [a draft update of RFC4122](https://www.ietf.org/archive/id/draft-peabody-dispatch-new-uuid-format-01.html).
## Install
```bash
$ go get -u github.com/WhiteRaven777/uuid
```
## Features
* Generate
* [ ] UUID v1
* Method to generate UUIDs using time and MAC address
* [ ] UUID v2
* Method to generate UUIDs using POSIX user ID or group ID to replace part of UUID v1
* [ ] UUID v3
* Method to generate UUIDs using MD5 in combination with information that is unique in a namespace
* [ ] UUID v4
* Method to generate UUIDs using random numbers
* [ ] UUID v5
* Method to generate UUIDs using SHA1 based on UUID v3
* [ ] UUID v6 (draft)
* Method to generate UUIDs using time based on the Gregorian calendar as well as v1, the clock sequence and random numbers
* [x] UUID v7 (draft)
* Method to generate UUIDs using unix time with millisecond or microsecond or nanosecond precision and random numbers
* [ ] UUID v8 (draft)
* Method to generate UUIDs using any precision and format of time and node when no other method is available
* Encode
* [x] Short string
* [x] UUID format
* [x] URN format
* [x] base64 format
* Decode (parse)
* [x] Short string
* [x] UUID format
* [x] URN format
* [x] base64 format
## Example
See [_examples/](https://github.com/WhiteRaven777/uuid/blob/master/_examples/) for a variety of examples.
```go
package main
import (
"fmt"
"time"
"github.com/WhiteRaven777/uuid"
)
func main() {
var (
id uuid.ID
uid uuid.UUID
t time.Time
)
id = uuid.New(uuid.UUIDv7)
// automatically generate based on generation timing
uid = id.Generate()
// you can convert it to a string
fmt.Println("UUID(short)", uid.Short())
fmt.Println("UUID(default)", uid.String())
// you can decode (parse) the string into the UUID
if buf, err := uuid.Parse(uid.String()); err == nil {
t = id.Decode(buf)
}
// generate based on any time
uid = id.Convert(t)
// you can convert it to a string
fmt.Println("URN", uid.URN())
fmt.Println("base64", uid.Base64())
// Note.
// Regenerated UUIDs from the same time information will almost never have the same value.
// This is because the time information is combined with random number information.
}
```
## License
Copyright (c) 2021-present [WhiteRaven777](https://github.com/WhiteRaven777)
Licensed under [MIT License](./LICENSE)
[GoDoc]: https://pkg.go.dev/github.com/WhiteRaven777/uuid?tab=versions
[GoDoc Widget]: https://godoc.org/github.com/WhiteRaven777/uuid?status.svg | 27.427083 | 183 | 0.696924 | eng_Latn | 0.825221 |
aa4952604d616f8cfe4b44e5a09ebe45ab72a525 | 10,465 | md | Markdown | _posts/cas/2018-02-20-cas-service-rbac-attributeresolution.md | linosgian/apereo.github.io | 2d370e3e3110085faafbe5f78d4498dd1d73207f | [
"MIT"
] | null | null | null | _posts/cas/2018-02-20-cas-service-rbac-attributeresolution.md | linosgian/apereo.github.io | 2d370e3e3110085faafbe5f78d4498dd1d73207f | [
"MIT"
] | null | null | null | _posts/cas/2018-02-20-cas-service-rbac-attributeresolution.md | linosgian/apereo.github.io | 2d370e3e3110085faafbe5f78d4498dd1d73207f | [
"MIT"
] | null | null | null | ---
layout: post
title: Apereo CAS - Attribute-based Application Authorization
summary: A walkthrough to demonstrate how one might fetch attributes from a number of data sources, turning them into roles that could then be used to enforce application access and authorization.
tags: [CAS]
---
<div class="alert alert-success">
<strong>Collaborate</strong><br/>This blog is managed and hosted on GitHub. If you wish to update the contents of this post or if you have found an inaccuracy and wish to make corrections, we recommend that you please submit a pull request to <a href="https://github.com/apereo/apereo.github.io">this repository</a>.
</div>
A fairly common CAS deployment use case is to enforce access to a particular set of applications via user attributes and roles. Once the authentication/authorization server passed on the required attributes and entitlements to the application, each service might individually be tasked with controlling entry access, and once authorized, enforcement of a set of specific functions inside the application which the user may be allowed to carry out. The purpose of this tutorial is to present an alternative to the first scenario, by providing options to centrally control and manage that ruleset that allows the user to enter an application that is integrated with Apereo CAS.
Our task list is rather short:
1. Configure CAS to fetch attributes from LDAP, JDBC and other potential sources.
2. Register an application with CAS and define authorization rules for access based on retrieved attributes.
To keep this tutorial simple, we are going to stick with the default CAS method of authentication with the obvious assumption that our authentication sources shall be different from sources that may produce user attributes.
# Environment
- CAS `5.2.x`
- [CAS Maven WAR Overlay](https://github.com/apereo/cas-overlay-template)
Follow the instructions provided by the `README` file to produce a functional build.
# Attribute Retrieval
[Attribute resolution strategies](https://apereo.github.io/cas/development/integration/Attribute-Resolution.html) in CAS are controlled by the [Person Directory project](https://github.com/apereo/person-directory). The Person Directory dependency is automatically bundled with the CAS server and provides a number of options to fetch attributes and user data from sources such as LDAP, JDBC, etc. Since we do have multiple sources of attributes, the Person Directory component is also able to aggregate and merge the results and has options to decide how to deal with disagreements in case two sources produce conflicting data.
There is very little left for us to do other than to teach CAS about our specific data sources.
## LDAP Attribute Retrieval
In the given `cas.properties` file, the following settings allow us to fetch attributes from LDAP:
```properties
cas.authn.attributeRepository.ldap[0].baseDn=ou=people,dc=example,dc=org
cas.authn.attributeRepository.ldap[0].ldap-url=ldap://localhost:1385
cas.authn.attributeRepository.ldap[0].userFilter=uid={0}
cas.authn.attributeRepository.ldap[0].useSsl=false
cas.authn.attributeRepository.ldap[0].bindDn=...
cas.authn.attributeRepository.ldap[0].bindCredential=...
cas.authn.attributeRepository.ldap[0].attributes.displayName=displayName
cas.authn.attributeRepository.ldap[0].attributes.givenName=givenName
cas.authn.attributeRepository.ldap[0].attributes.mail=email
```
The above configuration defined the very basic essentials as far as LDAP connection information while also teaching CAS the set of attributes that should be first *retrieved* and optionally *remapped*. In practice, CAS would begin to fetch `displayName`, `givenName` and `mail` from the directory server and then process the final collection to include `displayName`, `givenName` and `email`. From this point on, CAS only knows of the user's email address under the `email` attribute and needless to say, this is the attribute name that should be used everywhere else in the CAS configuration.
<div class="alert alert-info">
<strong>Multiple Sources</strong><br/>CAS settings able to accept multiple values are typically documented with an index, such as <code>cas.some.setting[0]=value</code>. The index [0] is meant to be incremented by the adopter to allow for distinct multiple configuration blocks
</div>
## JDBC Attribute Retrieval
The table `table_users` in our HyperSQL database contains the user attributes we need:
| `uid` | `attribute` | `value`
|-------------|------------------------|------------------------------
| `casuser` | `role` | `Manager`
| `casuser` | `role` | `Supervisor`
| `user2` | `role` | `Engineer`
The above schema is what's referred to as a *Multi-Row* setup in the Person Directory configuration. In other words, this is the sort of setup that has more than one row dedicated to a user entry and quite possibly similar to above, multiple rows carry out multiple values for a single attribute definition (i.e. `role`). In order to teach CAS about this setup, we could start with the following settings:
```properties
cas.authn.attributeRepository.jdbc[0].attributes.role=personRole
cas.authn.attributeRepository.jdbc[0].singleRow=false
cas.authn.attributeRepository.jdbc[0].columnMappings.attribute=value
cas.authn.attributeRepository.jdbc[0].sql=SELECT * FROM table_users WHERE {0}
cas.authn.attributeRepository.jdbc[0].username=uid
cas.authn.attributeRepository.jdbc[0].driverClass=...
cas.authn.attributeRepository.jdbc[0].user=...
cas.authn.attributeRepository.jdbc[0].password=...
cas.authn.attributeRepository.jdbc[0].url=...
```
Pay attention to how the `columnMappings` setting defines a set of 1-1 mappings between columns that contain the attribute name vs the attribute value. Furthermore and similar to the LDAP setup, we are teaching CAS to fetch the attribute `role` (again, determined based on the mappings defined) and virtually *rename* the attribute to `personRole`. Just like the LDAP setup and from this point on, CAS only knows of the user's role under the `personRole` attribute and needles to say, this is the attribute name that should be used everywhere else in the CAS configuration.
# Smoke Test
At this point, you should be able to authenticate into CAS and observe in the logs that the constructed authenticated principal contains the following attributes:
```bash
... <Authenticated principal [casuser] with attributes [{personRole=[Manager, Supervisor],
displayName=Test User, givenName=CAS, email=casuser@example.org}] ...>
```
If you [need to troubleshoot](https://apereo.github.io/cas/development/installation/Troubleshooting-Guide.html), the best course of action would be to adjust logs to produce `DEBUG` information.
# Application Registration
The CAS service management facility allows CAS server administrators to declare and configure which services/applications may make use of CAS in different ways. The core component of the service management facility is the service registry that stores one or more registered services containing metadata that drives a number of CAS behaviors including authorization rules.
To keep this tutorial simple, we are going to use the [JSON Service Registry](https://apereo.github.io/cas/development/installation/JSON-Service-Management.html). This registry reads services definitions from JSON configuration files on startup. JSON files are expected to be found inside a configured directory location and this registry will recursively look through the directory structure to find relevant JSON files.
For this tutorial, we expect CAS to find our JSON registration record files using the following setting:
```properties
cas.service-registry.initFromJson=false
cas.service-registry.json.location=file:/etc/cas/config/services
```
...and inside the above directory, we are going to create an `ExampleApplication-100.json` file that contains the following:
```json
{
"@class" : "org.apereo.cas.services.RegexRegisteredService",
"serviceId" : "https://example\\.application\\.edu.*",
"name" : "ExampleApplication",
"id" : 100,
"evaluationOrder" : 1
}
```
All that remains for us is to decorate the registration record with the authorization rules.
# Application Authorization Rules
The [access strategy of a registered service](https://apereo.github.io/cas/development/installation/Configuring-Service-Access-Strategy.html) provides fine-grained control over the application authorization rules. It describes whether the service is allowed to use the CAS server, allowed to participate in single sign-on authentication, and (as it's relevant for our use case here) it may also be configured to require a certain set of attributes that must exist before access can be granted to the service.
<div class="alert alert-info">
<strong>Remember</strong><br/>CAS is only gatekeeping here, deciding whether entrance is allowed to the given application. Once the user is allowed to enter, the extent of capabilities and functions available to the user are and must be decided by the application itself where CAS at that point would completely step aside.
</div>
Our JSON registration record could be modified as such:
```json
{
"@class" : "org.apereo.cas.services.RegexRegisteredService",
"serviceId" : "https://example\\.application\\.edu.*",
"name" : "ExampleApplication",
"id" : 100,
"evaluationOrder" : 1,
"accessStrategy" : {
"@class" : "org.apereo.cas.services.DefaultRegisteredServiceAccessStrategy",
"requiredAttributes" : {
"@class" : "java.util.HashMap",
"personRole" : [ "java.util.HashSet", [ "Manager" ] ]
}
}
}
```
In simpler terms, the above configuration is saying: *Access to applications that interact with CAS whose URL matches the pattern defined by the `serviceId` is only granted if the authenticating user has an attribute `personRole` that contains the value `Manager`*.
# Summary
I hope this review was of some help to you and I am sure that both this post as well as the functionality it attempts to explain can be improved in any number of ways. Please feel free to [engage and contribute](https://apereo.github.io/cas/developer/Contributor-Guidelines.html) as best as you can.
[Misagh Moayyed](https://fawnoos.com)
| 66.656051 | 675 | 0.765504 | eng_Latn | 0.993223 |
aa497c92e91abf7adb950c803c0714baf52c947e | 5,703 | md | Markdown | packages/util/docs/classes/address.address-1.md | llwslc/ethereumjs-monorepo | 4f23469c2e04389962c46e66e6ac92f1b9f9e489 | [
"MIT"
] | 1 | 2021-09-04T10:22:47.000Z | 2021-09-04T10:22:47.000Z | packages/util/docs/classes/address.address-1.md | llwslc/ethereumjs-monorepo | 4f23469c2e04389962c46e66e6ac92f1b9f9e489 | [
"MIT"
] | null | null | null | packages/util/docs/classes/address.address-1.md | llwslc/ethereumjs-monorepo | 4f23469c2e04389962c46e66e6ac92f1b9f9e489 | [
"MIT"
] | 1 | 2022-02-21T06:58:42.000Z | 2022-02-21T06:58:42.000Z | [ethereumjs-util](../README.md) / [address](../modules/address.md) / Address
# Class: Address
[address](../modules/address.md).Address
## Table of contents
### Constructors
- [constructor](address.address-1.md#constructor)
### Properties
- [buf](address.address-1.md#buf)
### Methods
- [equals](address.address-1.md#equals)
- [isPrecompileOrSystemAddress](address.address-1.md#isprecompileorsystemaddress)
- [isZero](address.address-1.md#iszero)
- [toBuffer](address.address-1.md#tobuffer)
- [toString](address.address-1.md#tostring)
- [fromPrivateKey](address.address-1.md#fromprivatekey)
- [fromPublicKey](address.address-1.md#frompublickey)
- [fromString](address.address-1.md#fromstring)
- [generate](address.address-1.md#generate)
- [generate2](address.address-1.md#generate2)
- [zero](address.address-1.md#zero)
## Constructors
### constructor
• **new Address**(`buf`)
#### Parameters
| Name | Type |
| :------ | :------ |
| `buf` | `Buffer` |
#### Defined in
[packages/util/src/address.ts:13](https://github.com/ethereumjs/ethereumjs-monorepo/blob/master/packages/util/src/address.ts#L13)
## Properties
### buf
• `Readonly` **buf**: `Buffer`
#### Defined in
[packages/util/src/address.ts:13](https://github.com/ethereumjs/ethereumjs-monorepo/blob/master/packages/util/src/address.ts#L13)
## Methods
### equals
▸ **equals**(`address`): `boolean`
Is address equal to another.
#### Parameters
| Name | Type |
| :------ | :------ |
| `address` | [Address](address.address-1.md) |
#### Returns
`boolean`
#### Defined in
[packages/util/src/address.ts:81](https://github.com/ethereumjs/ethereumjs-monorepo/blob/master/packages/util/src/address.ts#L81)
___
### isPrecompileOrSystemAddress
▸ **isPrecompileOrSystemAddress**(): `boolean`
True if address is in the address range defined
by EIP-1352
#### Returns
`boolean`
#### Defined in
[packages/util/src/address.ts:96](https://github.com/ethereumjs/ethereumjs-monorepo/blob/master/packages/util/src/address.ts#L96)
___
### isZero
▸ **isZero**(): `boolean`
Is address zero.
#### Returns
`boolean`
#### Defined in
[packages/util/src/address.ts:88](https://github.com/ethereumjs/ethereumjs-monorepo/blob/master/packages/util/src/address.ts#L88)
___
### toBuffer
▸ **toBuffer**(): `Buffer`
Returns Buffer representation of address.
#### Returns
`Buffer`
#### Defined in
[packages/util/src/address.ts:114](https://github.com/ethereumjs/ethereumjs-monorepo/blob/master/packages/util/src/address.ts#L114)
___
### toString
▸ **toString**(): `string`
Returns hex encoding of address.
#### Returns
`string`
#### Defined in
[packages/util/src/address.ts:107](https://github.com/ethereumjs/ethereumjs-monorepo/blob/master/packages/util/src/address.ts#L107)
___
### fromPrivateKey
▸ `Static` **fromPrivateKey**(`privateKey`): [Address](address.address-1.md)
Returns an address for a given private key.
#### Parameters
| Name | Type | Description |
| :------ | :------ | :------ |
| `privateKey` | `Buffer` | A private key must be 256 bits wide |
#### Returns
[Address](address.address-1.md)
#### Defined in
[packages/util/src/address.ts:50](https://github.com/ethereumjs/ethereumjs-monorepo/blob/master/packages/util/src/address.ts#L50)
___
### fromPublicKey
▸ `Static` **fromPublicKey**(`pubKey`): [Address](address.address-1.md)
Returns an address for a given public key.
#### Parameters
| Name | Type | Description |
| :------ | :------ | :------ |
| `pubKey` | `Buffer` | The two points of an uncompressed key |
#### Returns
[Address](address.address-1.md)
#### Defined in
[packages/util/src/address.ts:40](https://github.com/ethereumjs/ethereumjs-monorepo/blob/master/packages/util/src/address.ts#L40)
___
### fromString
▸ `Static` **fromString**(`str`): [Address](address.address-1.md)
Returns an Address object from a hex-encoded string.
#### Parameters
| Name | Type | Description |
| :------ | :------ | :------ |
| `str` | `string` | Hex-encoded address |
#### Returns
[Address](address.address-1.md)
#### Defined in
[packages/util/src/address.ts:31](https://github.com/ethereumjs/ethereumjs-monorepo/blob/master/packages/util/src/address.ts#L31)
___
### generate
▸ `Static` **generate**(`from`, `nonce`): [Address](address.address-1.md)
Generates an address for a newly created contract.
#### Parameters
| Name | Type | Description |
| :------ | :------ | :------ |
| `from` | [Address](address.address-1.md) | The address which is creating this new address |
| `nonce` | [BN](externals.bn-1.md) | The nonce of the from account |
#### Returns
[Address](address.address-1.md)
#### Defined in
[packages/util/src/address.ts:61](https://github.com/ethereumjs/ethereumjs-monorepo/blob/master/packages/util/src/address.ts#L61)
___
### generate2
▸ `Static` **generate2**(`from`, `salt`, `initCode`): [Address](address.address-1.md)
Generates an address for a contract created using CREATE2.
#### Parameters
| Name | Type | Description |
| :------ | :------ | :------ |
| `from` | [Address](address.address-1.md) | The address which is creating this new address |
| `salt` | `Buffer` | A salt |
| `initCode` | `Buffer` | The init code of the contract being created |
#### Returns
[Address](address.address-1.md)
#### Defined in
[packages/util/src/address.ts:72](https://github.com/ethereumjs/ethereumjs-monorepo/blob/master/packages/util/src/address.ts#L72)
___
### zero
▸ `Static` **zero**(): [Address](address.address-1.md)
Returns the zero address.
#### Returns
[Address](address.address-1.md)
#### Defined in
[packages/util/src/address.ts:23](https://github.com/ethereumjs/ethereumjs-monorepo/blob/master/packages/util/src/address.ts#L23)
| 20.966912 | 131 | 0.682974 | eng_Latn | 0.395542 |
aa4a100651ab1b7c8a13e48488834264d54135f5 | 3,303 | md | Markdown | Documents/SVG.md | viniciusfbb/skia4delphi | 1e6f463cd8a62e29ae9d95f14563d070ef7d5caf | [
"MIT",
"BSD-3-Clause"
] | 139 | 2021-08-11T01:21:33.000Z | 2022-02-07T16:10:19.000Z | Documents/SVG.md | viniciusfbb/skia4delphi | 1e6f463cd8a62e29ae9d95f14563d070ef7d5caf | [
"MIT",
"BSD-3-Clause"
] | 32 | 2021-08-17T00:45:37.000Z | 2022-02-08T23:59:39.000Z | Documents/SVG.md | viniciusfbb/skia4delphi | 1e6f463cd8a62e29ae9d95f14563d070ef7d5caf | [
"MIT",
"BSD-3-Clause"
] | 30 | 2021-08-11T05:04:53.000Z | 2022-02-04T16:25:11.000Z | <img src="/Assets/Artwork/LogoGradient.svg" width=360 height=200>
# SVG
## SVG in pure skia
The skia developed a way to load and render svgs with the class TSkSVGDOM. The code below shows how to load and render a svg into an ISkCanvas:
```pascal
var
LBitmap: TBitmap;
begin
LBitmap := TBitmap.Create(100, 100);
try
LBitmap.SkiaDraw(
procedure (const ACanvas: ISKCanvas)
var
LStream: ISkStream;
LDOM: ISkSVGDOM;
LSvgRect, LFitDest: TRectF;
begin
LStream := TSkStreamAdapter.Create(TStringStream.Create(TFile.ReadAllText('Assets\Samples\gorilla.svg')), True);
LDOM := TSkSVGDOM.Make(LStream);
if Assigned(LDOM) then
begin
if LDOM.ContainerSize.IsZero then
LDOM.ContainerSize := TSizeF.Create(LBitmap.Width, LBitmap.Height);
LSvgRect := TRectF.Create(PointF(0, 0), LDOM.ContainerSize);
LFitDest := LSvgRect.FitInto(RectF(0, 0, LBitmap.Width, LBitmap.Height));
ACanvas.Translate(LFitDest.Left, LFitDest.Top);
ACanvas.Scale(LFitDest.Width / LSvgRect.Width, LFitDest.Height / LSvgRect.Height);
LDOM.Render(ACanvas);
end;
end);
```
Note that in the example above we use LDOM.ContainerSize to inform the final size of the svg we want to render when the LDOM.ContainerSize is zero. If this is not done, you have the risk of LDOM.Render giving access violation when the width and height are not explicit in the svg source (which is quite common). So always use LDOM.ContainerSize before rendering as the example above.
We showed above how to load and render a svg using pure skia, but as this functionality is very important, we developed a dedicated control to svg render, called TSkSvg, see below.
## TSkSvg
TSkSvg is the control to load and display svgs easily:
```pascal
var
LSvg: TSkSvg;
begin
LSvg := TSkSvg.Create(Self);
LSvg.Svg.Source := TFile.ReadAllText('Assets\Samples\gorilla.svg');
LSvg.Parent := Self;
end;
```
The **Assets/Samples/gorilla.svg** svg file results in the output below:
<img src="../Assets/Samples/gorilla.svg" width=200 height=200>
#### property Svg.Source
String property of svg file content.
#### property Svg.OverrideColor
When this property is Null (default value), the control will render the svg in default color. But when this property have another value, the control will replace the svg color to the Svg.OverrideColor. This is usefull in icons svgs, for example.
## Limitations
Unfortunately, the skia rendering of SVG has an important limitation:
- Does not support style element and style attribute (see the workaround in next topic, [Considerations](#considerations))
- Does not support animated SVG
## Considerations
As the skia doesn't support svg style yet, you should disable the generation of these styles whenever you generate your svg. For example, in Adobe Illustrator when you export your vector as svg, you need to set the follow cofigurations:
- In Styling: choose **Presentation Attributes** instead of Inline CSS because CSS is not fully supported.
<img src="../Assets/Documents/adobe_illustrator_exporting_svg.png">
## Known issues
- Problems in MacOS with language with decimal separator different than dot. We are investigating the solution.
| 35.516129 | 383 | 0.730851 | eng_Latn | 0.960615 |
aa4af245d53d7f49c3518c5370d2eca0e35e42af | 130 | md | Markdown | README.md | Zevaztian33/MiPortafolio | 09de2329a3460237ee2f294cbc93922279a4c514 | [
"Apache-2.0"
] | 1 | 2020-10-08T14:24:53.000Z | 2020-10-08T14:24:53.000Z | README.md | Zevaztian33/MiPortafolio | 09de2329a3460237ee2f294cbc93922279a4c514 | [
"Apache-2.0"
] | 1 | 2020-10-07T18:07:15.000Z | 2020-10-07T18:07:15.000Z | README.md | Zevaztian33/MiPortafolio | 09de2329a3460237ee2f294cbc93922279a4c514 | [
"Apache-2.0"
] | null | null | null | # MiPortafolio
Curriculum virtual, portafolio de mis trabajos de diseño e ilustracion
https://zevaztian33.github.io/MiPortafolio/
| 32.5 | 70 | 0.830769 | spa_Latn | 0.685777 |
aa4af6aed4ac5c9e5ab51b81bf6dcd23f598abf0 | 5,514 | md | Markdown | README.md | SemanticComputing/parliamentsampo-web-app | 4b6d2cd163b815c8e00cd6af3c794d9c87ba29c9 | [
"MIT"
] | null | null | null | README.md | SemanticComputing/parliamentsampo-web-app | 4b6d2cd163b815c8e00cd6af3c794d9c87ba29c9 | [
"MIT"
] | null | null | null | README.md | SemanticComputing/parliamentsampo-web-app | 4b6d2cd163b815c8e00cd6af3c794d9c87ba29c9 | [
"MIT"
] | null | null | null | [](https://standardjs.com)
# ParliamentSampo User Interface
Based on [Sampo-UI – A framework for building semantic portal user interfaces](https://github.com/SemanticComputing/sampo-ui)
The Sampo-UI framework is being developed by the [Semantic Computing Research Group (SeCo)](https://seco.cs.aalto.fi)
at the Aalto University, Finland. See the [research page](https://seco.cs.aalto.fi/tools/sampo-ui) for
more information.
## Requirements
* [Node.js® – a JavaScript runtime built on Chrome's V8 JavaScript engine.](https://nodejs.org/en/) (version 16.13.0)
* [Nodemon – monitor for any changes in your source and automatically restart your server](https://nodemon.io/)
Note for Linux users: if your home directory is mounted from a network drive, using the [Node Version Manager](https://github.com/nvm-sh/nvm) for installing Node.js highly recommended.
## Installation
### Local development
Install the dependencies specified in `package.json` (this command needs to be run only once,
as long as you don't modify the dependencies):
`npm install`
Run client and server concurrently:
`npm run dev`
## Deploy with Docker
These example commands can be used to deploy the server at http://localhost:3006/ in **production** mode. Production mode means in this case that the server listens for API requests at URLs beginning with http://localhost:3006/api/v1/... and additionally serves the client (React app) at http://localhost:3006/. The API docs can be found at http://localhost:3006/api-docs/.
Note that in **development** mode Webpack is used for serving the client, and the server is used only for handling API requests.
The build argument API_URL must be provided.
### Build
`docker build --build-arg API_URL=http://localhost:3006/api/v1 -t sampo-web-app-image .`
### Run
`docker run -d -p 3006:3001 --name sampo-web-app sampo-web-app-image`
### Run with password protected endpoint
`docker run -d -p 3006:3001 -e SPARQL_ENDPOINT_BASIC_AUTH=your_password --name sampo-web-app sampo-web-app-image`
### Upgrade
```
docker build --build-arg API_URL=http://localhost:3006/api/v1 -t sampo-web-app-image .
docker stop sampo-web-app
docker rm sampo-web-app
docker run -d -p 3006:3001 --name sampo-web-app sampo-web-app-image
```
## Developer guide
### Coding style
The [JavaScript style guide, linter, and formatter](https://standardjs.com) module (named "standard" in package.json) is installed by default as development dependency. Do not install or create any additional style definitions or configurations. Instead, install an appropriate [plugin](https://standardjs.com/index.html#are-there-text-editor-plugins) for your text editor. If there are no plugins available for your favorite editor, it is highly recommended to switch into a supported editor.
## Documentation
### Client
Sampo-UI's React components are documented [here](https://semanticcomputing.github.io/sampo-ui) using Storybook.
Here is a list of the main JavaScript libraries on which the Sampo-UI client is built on:
* [React – A JavaScript library for building user interfaces](https://reactjs.org/)
* [Material-UI – React components for faster and easier web development](https://material-ui.com/)
* [Redux – A Predictable State Container for JS Apps](https://redux.js.org/)
* [redux-observable – RxJS-based middleware for Redux](https://redux-observable.js.org/)
* [Reselect – Selector library for Redux](https://github.com/reduxjs/reselect)
* [React Router – Declarative routing for React](https://reacttraining.com/react-router/web/guides/quick-start)
* [react-intl-universal – React internationalization package developed by Alibaba Group](https://github.com/alibaba/react-intl-universal)
* [deck.gl – Large-scale WebGL-powered Data Visualization](https://deck.gl)
* [react-map-gl – React friendly API wrapper around MapboxGL JS](https://github.com/visgl/react-map-gl)
* [Leaflet – a JavaScript library for interactive maps](https://leafletjs.com/)
* [Cytoscape – an open source software platform for visualizing complex networks](https://cytoscape.org/)
* [ApexCharts.js – Open Source JavaScript Charts for your website](https://apexcharts.com/)
* [React Sortable Tree – A React component for representation of hierarchical data](https://github.com/frontend-collective/react-sortable-tree)
* [Moment.js – Parse, validate, manipulate, and display dates and times in JavaScript](https://momentjs.com/)
### Backend
The API provided by Sampo-UI's backend includes routes for the following search paradigms: faceted search,
full text search, and federated full text or spatial search. The API is described using the
[OpenAPI Specification](https://swagger.io/specification). The same specification is used for both
documenting the API, and validating the API requests and responses.
An API documentation with example configuration can been seen [here](https://sampo-ui.demo.seco.cs.aalto.fi/api-docs/).
Sampo-UI's backend is based on the following JavaScript libraries:
* [Express – Fast, unopinionated, minimalist web framework for Node.js](https://expressjs.com/)
* [axios – Promise based HTTP client for the browser and Node.js](https://github.com/axios/axios)
* [Lodash – A modern JavaScript utility library delivering modularity, performance & extras](https://lodash.com/)
| 55.69697 | 495 | 0.766594 | eng_Latn | 0.853684 |
aa4b7f6d69865e80e1a26b5e532d380842effd65 | 31 | md | Markdown | README.md | antoineMica/CoinGeckoPuller | 4df71c6d52c5192b59c23df812d2d8481c23ce3a | [
"MIT"
] | null | null | null | README.md | antoineMica/CoinGeckoPuller | 4df71c6d52c5192b59c23df812d2d8481c23ce3a | [
"MIT"
] | null | null | null | README.md | antoineMica/CoinGeckoPuller | 4df71c6d52c5192b59c23df812d2d8481c23ce3a | [
"MIT"
] | null | null | null | # CoinGeckoPuller
STONKS MOON
| 10.333333 | 17 | 0.806452 | kor_Hang | 0.939938 |
9860fcd47fa9c070bad71a13aca42166f469ccd6 | 2,820 | md | Markdown | desktop-src/extensible-storage-engine/windows8api.jetresizedatabase-method.md | KrupalJoshi/win32 | f5099e1e3e455bb162771d80b0ba762ee5c974ec | [
"CC-BY-4.0",
"MIT"
] | 3 | 2020-04-24T13:02:42.000Z | 2021-07-17T15:32:03.000Z | desktop-src/extensible-storage-engine/windows8api.jetresizedatabase-method.md | KrupalJoshi/win32 | f5099e1e3e455bb162771d80b0ba762ee5c974ec | [
"CC-BY-4.0",
"MIT"
] | null | null | null | desktop-src/extensible-storage-engine/windows8api.jetresizedatabase-method.md | KrupalJoshi/win32 | f5099e1e3e455bb162771d80b0ba762ee5c974ec | [
"CC-BY-4.0",
"MIT"
] | 1 | 2022-03-09T23:50:05.000Z | 2022-03-09T23:50:05.000Z | ---
title: Windows8Api.JetResizeDatabase method (Microsoft.Isam.Esent.Interop.Windows8)
TOCTitle: 'JetResizeDatabase method '
ms:assetid: M:Microsoft.Isam.Esent.Interop.Windows8.Windows8Api.JetResizeDatabase(Microsoft.Isam.Esent.Interop.JET_SESID,Microsoft.Isam.Esent.Interop.JET_DBID,System.Int32,System.Int32@,Microsoft.Isam.Esent.Interop.Windows8.ResizeDatabaseGrbit)
ms:mtpsurl: https://msdn.microsoft.com/en-us/library/microsoft.isam.esent.interop.windows8.windows8api.jetresizedatabase(v=EXCHG.10)
ms:contentKeyID: 55104462
ms.date: 07/30/2014
ms.topic: article
f1_keywords:
- Microsoft.Isam.Esent.Interop.Windows8.Windows8Api.JetResizeDatabase
dev_langs:
- CSharp
- JScript
- VB
- other
api_name:
- Microsoft.Isam.Esent.Interop.Windows8.Windows8Api.JetResizeDatabase
topic_type:
- apiref
- kbSyntax
api_type:
- Managed
api_location:
- Microsoft.Isam.Esent.Interop.dll
ROBOTS: INDEX,FOLLOW
---
# Windows8Api.JetResizeDatabase method
Resizes a currently open database.
**Namespace:** [Microsoft.Isam.Esent.Interop.Windows8](dn335439\(v=exchg.10\).md)
**Assembly:** Microsoft.Isam.Esent.Interop (in Microsoft.Isam.Esent.Interop.dll)
## Syntax
``` vb
'Declaration
Public Shared Sub JetResizeDatabase ( _
sesid As JET_SESID, _
dbid As JET_DBID, _
desiredPages As Integer, _
<OutAttribute> ByRef actualPages As Integer, _
grbit As ResizeDatabaseGrbit _
)
'Usage
Dim sesid As JET_SESID
Dim dbid As JET_DBID
Dim desiredPages As Integer
Dim actualPages As Integer
Dim grbit As ResizeDatabaseGrbitWindows8Api.JetResizeDatabase(sesid, dbid, _
desiredPages, actualPages, grbit)
```
``` csharp
public static void JetResizeDatabase(
JET_SESID sesid,
JET_DBID dbid,
int desiredPages,
out int actualPages,
ResizeDatabaseGrbit grbit
)
```
#### Parameters
- sesid
Type: [Microsoft.Isam.Esent.Interop.JET_SESID](hh596745\(v=exchg.10\).md)
The session to use.
<!-- end list -->
- dbid
Type: [Microsoft.Isam.Esent.Interop.JET_DBID](hh596176\(v=exchg.10\).md)
The database to grow.
<!-- end list -->
- desiredPages
Type: [System.Int32](https://docs.microsoft.com/dotnet/api/system.int32?redirectedfrom=MSDN)
The desired size of the database, in pages.
<!-- end list -->
- actualPages
Type: [System.Int32](https://docs.microsoft.com/dotnet/api/system.int32?redirectedfrom=MSDN)
The size of the database, in pages, after the call.
<!-- end list -->
- grbit
Type: [Microsoft.Isam.Esent.Interop.Windows8.ResizeDatabaseGrbit](dn335369\(v=exchg.10\).md)
Resize options.
## See also
#### Reference
[Windows8Api class](dn335490\(v=exchg.10\).md)
[Windows8Api members](dn335373\(v=exchg.10\).md)
[Microsoft.Isam.Esent.Interop.Windows8 namespace](dn335439\(v=exchg.10\).md)
| 25.405405 | 244 | 0.735461 | yue_Hant | 0.744161 |
98614744063e48fd58918105aa5785eca0b959e6 | 1,746 | md | Markdown | docs/visual-basic/misc/bc30795.md | felipealbuquerq/docs.pt-br | 6808f7d63212e650a0ecadd7f5cd058594fd0d38 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/visual-basic/misc/bc30795.md | felipealbuquerq/docs.pt-br | 6808f7d63212e650a0ecadd7f5cd058594fd0d38 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/visual-basic/misc/bc30795.md | felipealbuquerq/docs.pt-br | 6808f7d63212e650a0ecadd7f5cd058594fd0d38 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Membros não compartilhados em uma estrutura não podem ser declarados como 'New'
ms.date: 07/20/2015
f1_keywords:
- vbc30795
- BC30795
helpviewer_keywords:
- BC30795
ms.assetid: 8e4e1ad8-3bac-475f-82e8-e4f134692204
ms.openlocfilehash: 201ccfad3bd9d5997251de6697c7b971b8f250fc
ms.sourcegitcommit: 2701302a99cafbe0d86d53d540eb0fa7e9b46b36
ms.translationtype: MT
ms.contentlocale: pt-BR
ms.lasthandoff: 04/28/2019
ms.locfileid: "64588306"
---
# <a name="non-shared-members-in-a-structure-cannot-be-declared-new"></a>Membros não compartilhados em uma estrutura não podem ser declarados como 'New'
Uma variável não compartilhada em uma estrutura é declarada com um `New` cláusula.
Você pode inicializar uma variável de referência compartilhada em uma estrutura, e você pode ter uma variável de referência não compartilhada sem inicialização, como as linhas de código a seguir mostram.
`Shared structVar1 As New System.ApplicationException`
`Dim structVar2 As System.ApplicationException`
No entanto, você não pode inicializar uma variável de referência não compartilhada em uma estrutura. A linha de código a seguir é inválida.
`Dim structVar3 As New System.ApplicationException ' INVALID IN A STRUCTURE`
**ID do erro:** BC30795
## <a name="to-correct-this-error"></a>Para corrigir este erro
- Remover o `Shared` modificador ou o `New` palavra-chave da declaração da variável de referência.
## <a name="see-also"></a>Consulte também
- [Instrução Structure](../../visual-basic/language-reference/statements/structure-statement.md)
- [Compartilhado](../../visual-basic/language-reference/modifiers/shared.md)
- [Operador New](../../visual-basic/language-reference/operators/new-operator.md)
| 42.585366 | 206 | 0.772623 | por_Latn | 0.99716 |
9861de4f7aab25df39c5793be24d443d511e00d5 | 1,958 | md | Markdown | node_modules/react-router-component/docs/recipes/custom-router.md | ywu37/calendar | 0d5db546e2d2ab7b5357cac284358ee6fac6b2be | [
"CC0-1.0"
] | 1 | 2020-07-23T16:26:24.000Z | 2020-07-23T16:26:24.000Z | node_modules/react-router-component/docs/recipes/custom-router.md | ywu37/calendar | 0d5db546e2d2ab7b5357cac284358ee6fac6b2be | [
"CC0-1.0"
] | 1 | 2019-09-15T22:21:52.000Z | 2019-09-15T22:21:52.000Z | node_modules/react-router-component/docs/recipes/custom-router.md | ywu37/calendar | 0d5db546e2d2ab7b5357cac284358ee6fac6b2be | [
"CC0-1.0"
] | null | null | null | # A custom Router component
You can define your own Router component.
This might be useful if you like to have a more traditional routing approach in
where you define routes as component's class attribute:
routes: {
'/': MainPage,
...
}
Another case for this is to have more control how routers render its children,
you can define your own `render()` and do what you want.
We are going to implement custom router as a mixin:
var React = require('react')
var Router = require('react-router-component')
var MyRouterMixin = {
mixins: [Router.RouterMixin, Router.RouteRenderingMixin],
getRoutes: function(props) {
var routes = []
for (var path in this.routes)
routes.push({path: path, handler: this.routes[path]})
return routes
},
setRoutingState: function(state) {
// contains match, matchProps, handler, prefix, navigation;
// see RouterMixin
this.setState(state);
}
}
There are two things you need to notice.
First, `Router.RouterMixin` implements routing machinery and triggers router's
update when something changes (hash, pathname or something else, depending on
the environment router works in).
This mixin expects that you would implement `getRoutes` method which should
return a list of route descriptions in form of `{path: ..., handler: ...}`.
`RouterMixin` also supports intercepting its use of `setState` via `setRoutingState`.
Second, `Router.RouteRenderingMixin` is a strategy which specifies how
handler is rendered. It provides a method `renderRouteHandler()`.
We can now define our custom routers like this:
var Application = React.createClass({
mixins: [MyRouterMixin],
routes: {
'/': MainPage,
'/users/:username': UserPage,
null: NotFoundPage
},
render: function() {
return this.transferPropsTo(this.renderRouteHandler());
}
});
| 28.794118 | 85 | 0.682329 | eng_Latn | 0.979944 |
986258ce5565624f57b604b30169861545c26041 | 894 | md | Markdown | Classes/QuestLib.md | Hammster/wildstar-api-docs | dd9a803184b6910eb352c9bee59bc28632a7f4b9 | [
"MIT"
] | 5 | 2017-07-23T17:06:58.000Z | 2018-11-29T11:43:21.000Z | Classes/QuestLib.md | Hammster/wildstar-api-docs | dd9a803184b6910eb352c9bee59bc28632a7f4b9 | [
"MIT"
] | 19 | 2017-04-10T12:57:29.000Z | 2017-09-16T11:52:38.000Z | Classes/QuestLib.md | Hammster/wildstar-api-docs | dd9a803184b6910eb352c9bee59bc28632a7f4b9 | [
"MIT"
] | 6 | 2017-04-07T21:47:27.000Z | 2021-01-21T00:33:23.000Z | QuestLib
========
------------------------------------------------------------------------
`Function`
GetAllEpisodes()
----------------
------------------------------------------------------------------------
`Function`
GetCount()
----------
------------------------------------------------------------------------
`Function`
GetEpisode()
------------
------------------------------------------------------------------------
`Function`
GetKnownCategories()
--------------------
------------------------------------------------------------------------
`Function`
GetMaxCount()
-------------
------------------------------------------------------------------------
`Function`
GetQuest()
----------
------------------------------------------------------------------------
`Function`
GetTrackedEpisodes()
--------------------
| 17.192308 | 73 | 0.168904 | che_Cyrl | 0.687614 |
9863831c801f8e3d1ab46cd16f3385ebb67c2a14 | 507 | md | Markdown | README.md | jtrussell/swindle | 914f9ddc7b155cf895fc233b9f3f0c1804bf23e3 | [
"MIT"
] | 1 | 2021-04-07T20:14:43.000Z | 2021-04-07T20:14:43.000Z | README.md | jtrussell/swindle | 914f9ddc7b155cf895fc233b9f3f0c1804bf23e3 | [
"MIT"
] | null | null | null | README.md | jtrussell/swindle | 914f9ddc7b155cf895fc233b9f3f0c1804bf23e3 | [
"MIT"
] | null | null | null | # Swindle Leaderboards
## Setting up the project
Our python dependencies are listed in `requirements.txt`.
We use `django-environ` to manage secrets and configuration. Before getting
started, you'll want to bootstrap your environment:
```
cp src/.env.example src/.env
```
Feel free to edit the values in `src/.env` to your liking, this file is
versioned.
Now, you may either launch the app with Docker or python (3):
```
docker-compose up
# Or
cd src
python manage.py runserver
```
## License
MIT | 16.9 | 75 | 0.7357 | eng_Latn | 0.994974 |
9865d82b5ccfe0a94f08bfb10cb1f5822ed9792f | 5,925 | markdown | Markdown | _posts/2019-12-01-king_county_housing_sales_eda.markdown | hkkelderman/hkkelderman.github.io | 9b83ef03c4179d41f6bec35129b011cf62f6696a | [
"MIT"
] | null | null | null | _posts/2019-12-01-king_county_housing_sales_eda.markdown | hkkelderman/hkkelderman.github.io | 9b83ef03c4179d41f6bec35129b011cf62f6696a | [
"MIT"
] | null | null | null | _posts/2019-12-01-king_county_housing_sales_eda.markdown | hkkelderman/hkkelderman.github.io | 9b83ef03c4179d41f6bec35129b011cf62f6696a | [
"MIT"
] | null | null | null | ---
layout: post
title: "King County Housing Sales EDA"
date: 2019-12-02 01:51:55 +0000
permalink: king_county_housing_sales_eda
---
As a research analyst for an environmental non-profit, cleaning and analyzing data for reports and projects is not a new experience for me, though having to do it all using Python (as up until this point I did most of my work in Excel), was a little overwhelming. I was assigned a project that required me to clean, explore, and model housing data from King County, Washington. Instead of going through my whole process in how I worked through this project, I wanted to highlight an issue I ran into when it came to the Exploratory Data Analysis (EDA) portion. During this aspect of the project, I was required to generate and then answer three questions through EDA. I thought all of my questions would have been answerable with this dataset, but as it turns out, two of the three I asked were left mostly unanswered. I want to explain why I couldn’t answer them, and how I might be able to answer these questions in the future.
#### My first question
First, does renovating a house increase the sale value of a house? And if it does, what types of renovations cause the largest increase in sale value?
I thought these would be simple enough to answer, all I needed was a subset of the original data that contained houses that had been sold multiple times and had also been renovated. The following columns were used to create that subset:
* ‘id’ - a column of unique IDs for each house in the dataset
* ‘yr_renovated’ - a column with the year the house was renovated
The first step I took was creating a new column (‘renovated’) that would show whether or not a house had been renovated, regardless of the year. Next, I subsetted the original dataframe by filtering the ‘id’ column for just those IDs that appeared multiple times (these were not duplicates, but instead houses that were sold multiple times at different prices). Lastly, I took a subset of that dataframe by filtering the ‘renovated’ column for only those houses that had been renovated, and was left with a dataframe that only had eight rows and four unique house IDs.
<a href="https://imgur.com/HAfs5S8"><img src="https://i.imgur.com/HAfs5S8.png" title="source: imgur.com" width="300" height="300"/></a>
This was a bit upsetting, as I thought this would have been an interesting answer to find out, but clearly with only eight rows and four houses, I was not going to find anything useful from this small subset; my questions had narrowed the data too much. Upon further inspection, I also happened to notice that for all four of these houses, none of the renovations took place in between the two dates of sale, all of them had undergone renovations before the first date sold. Now, in addition to being too small, the subset of data was no longer capable of answering my question.
Since I no longer was able to answer my original questions, I ran a couple of statistical checks on the original dataset, to see if there were some differences in houses that had been renovated and houses that had not. What I found, was that on average, renovated houses were not only larger than non-renovated houses, but they also sold for at least $200 thousand more.
My hope was that when I subsetted the original dataframe for houses that had been sold multiple times and had been renovated, I would be able to see if the price of the house went up after the renovation. I was also hoping that I would be able to see which aspects of the house changed after the renovation (like number of bathrooms or square feet of living space), to determine if certain changes to the house would lead to larger resale prices. The only way I’d be able to answer this question in the future is with a much larger dataset over a longer period of time.
### My second question
More people seem to be downsizing their lives. Getting rid of cars, having less stuff, moving to cities, and buying smaller homes. Does the housing data in King County support this? Are more people buying smaller houses?
Now it’s no secret that people are buying smaller homes, just look at the front page of Google when you search “people buying smaller homes”:
<a href="https://imgur.com/MqwFgNi"><img src="https://i.imgur.com/MqwFgNi.png" title="source: imgur.com" width="400" height="700"/></a>
*Searched on 11/25/2019*
I wanted to see if the housing data from King County, WA would support this trend, but it does not. After a quick check in the square footage of living space over the years, it’s quite clear that houses have only increased in size.
<a href="https://imgur.com/F9E5miF"><img src="https://i.imgur.com/F9E5miF.png" title="source: imgur.com" width="500" height="300"/></a>
If you look more closely, from 2000 through 2015, you’ll see that there is in fact a decrease from 2000 until about 2009, but since 2009, the size increased again almost back to where it was in 2000.
<a href="https://imgur.com/z3b2s6R"><img src="https://i.imgur.com/z3b2s6R.png" title="source: imgur.com" width="500" height="300"/></a>
My assumption is that this might be more visible with newer data. If we added data for house sales from 2016 through 2018, we might be able to visualize the downsizing in houses. It is important when working with data to always have the most recent data available, otherwise you'll be working with stale information and the results won't be relevant.
### Conclusion
I thought I had come up with some interesting questions for this dataset, for which I thought I’d be able to answer. Unfortunately, I was unable to do so, as the subset of data either became to narrow or there was out of date, unable to explain more current trends. But, this was a good learning experience. I came up with original questions, something I’ve always struggled with, and I learned that there are limits to what data can tell us.
| 107.727273 | 929 | 0.775865 | eng_Latn | 0.999945 |
986626bf09cd291da8bbf01acd6f3b58b16cfecc | 3,817 | md | Markdown | _posts/2014-10-28-ruby-rendering-erb-template.md | revathskumar/blog.revathskumar.com | 066a066a603528beb55431a9d55d251df57b4fcb | [
"MIT"
] | 1 | 2020-07-27T00:52:35.000Z | 2020-07-27T00:52:35.000Z | _posts/2014-10-28-ruby-rendering-erb-template.md | revathskumar/blog.revathskumar.com | 066a066a603528beb55431a9d55d251df57b4fcb | [
"MIT"
] | null | null | null | _posts/2014-10-28-ruby-rendering-erb-template.md | revathskumar/blog.revathskumar.com | 066a066a603528beb55431a9d55d251df57b4fcb | [
"MIT"
] | 2 | 2017-06-09T22:37:08.000Z | 2019-06-20T01:34:51.000Z | ---
layout: post
title: "Ruby: Rendering erb template"
excerpt: "Ruby: Rendering erb template"
date: 2014-10-28 00:00:00 IST
updated: 2014-10-28 00:00:00 IST
categories: ruby
---
I never used [ERB](http://www.ruby-doc.org/stdlib-2.1.4/libdoc/erb/rdoc/ERB.html) outside Rails or without [tilt](http://github.com/rtomayko/tilt). So while I
was working with a bare rack app, I though I should try our ERB directly and checkout its api.
So I taken a look into ERB Class just enough to render a template, nothing much in detail. Here is the syntax for ERB constructor,
```ruby
ERB.new(template_string, safe_eval=nil, trim_mode=nil, outvar='_erbout')
```
let see how we can render some template with this.
# Using Sting template
Here is the simple example, for rendering a string template. Since we didn't specify the `outvar` the `result` method will return the rendered html.
```ruby
name = "Whatznear";
ERB.new("<h1>Hello ERB World!! </h1><h3><%= name %></h3>").result(binding)
```
Hope you noticed that we are passing `binding` to result method. binding gives the context in which the template to be evaluated, so they can replace the correct variables with its values.
If you like looking into details of `binding`, you can check the [ruby doc for Binding](http://www.ruby-doc.org/core-2.1.4/Binding.html). The above snippet will result in
```html
<h1>Hello ERB World!! </h1><h3>Whatznear</h3>
```
# Using template file
If you want to render a template from file, you just need to read the content of file and pass to ERB constructor.
```ruby
require "erb"
class Basicerb
def initialize name
@name = name
@template = File.read('./index.erb')
end
def render
ERB.new(@template).result( binding )
end
end
```
```erb
<%# index.erb %>
<h1>Hello ERB World!! </h1><h3><%= @name %></h3>
```
Here, we used `@name`, an instance variable because we are passing the context of `Basicerb` object to `result` method.
If you want to store the rendered html into another instance variable you can the variable as `outvar`.
```ruby
require "erb"
class Basicerb
attr_reader :html
def initialize name
@name = name
@template = File.read('./index.erb')
end
def render
ERB.new(@template, 0, "", "@html").result( binding )
end
end
```
# Using layout and view template
The most confusing things was rendering some erb inside an layout. Here is the `layout.rb`
```erb
<div class="jumbotron">
<%= yield %>
</div>
```
and we use the above `index.erb` as view.
```ruby
require "erb"
class Basicerb
def initialize name
@name = name
@layout = File.read('./layout.erb')
@template = File.read('./index.erb')
end
def render
templates = [@template, @layout]
templates.inject(nil) do | prev, temp |
_render(temp) { prev }
end
end
def _render temp
ERB.new(temp).result( binding )
end
end
```
Lets break it down how it works, The [Enumerable#inject](http://www.ruby-doc.org/core-2.1.4/Enumerable.html#method-i-inject) will accept a value and a block. The block will be executed for every element and the value we passed will be taken as first element. So in this case, in the first iteration, `prev` will be `nil` and `temp` will be the `@template` (view) string and pass it to `_render` method. Since this `@template` doesn't have a `yield` it just render the string as before.
In the second iteration, the `prev` will be rendered html of `@template` and `temp` will be `@layout`. Then these values will be passed to `_render`. Now while rendering layout it have a `yield` method which will be replaced by rendered html of `@template`. And finaly the `render` method will return html as below.
```html
<div class="jumbotron">
<h1>Hello ERB World!! </h1><h3>Whatznear</h3>
</div>
```
Hooray, the result seems what we expected. | 30.055118 | 486 | 0.70448 | eng_Latn | 0.972476 |
98667c496727e0c34ed9446d838c53256d753f11 | 64 | md | Markdown | README.md | AchimPieters/Arduino---nRF24L01-Interfacing | 1c95d1e2d40bf153da4c2f7f6bcfa803833a852f | [
"MIT"
] | 1 | 2019-12-06T17:23:42.000Z | 2019-12-06T17:23:42.000Z | README.md | AchimPieters/Arduino---nRF24L01-Interfacing | 1c95d1e2d40bf153da4c2f7f6bcfa803833a852f | [
"MIT"
] | null | null | null | README.md | AchimPieters/Arduino---nRF24L01-Interfacing | 1c95d1e2d40bf153da4c2f7f6bcfa803833a852f | [
"MIT"
] | null | null | null | # Arduino---nRF24L01-Interfacing
Arduino - nRF24L01 Interfacing
| 21.333333 | 32 | 0.8125 | eng_Latn | 0.27964 |
9866b95d3f04b44c85b8f6a7441168dbc5f371d6 | 2,682 | md | Markdown | docs/mfc/manipulating-the-progress-control.md | POMATOpl/cpp-docs.pl-pl | ae1925d41d94142f6a43c4e721d45cbbbfeda4c7 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/mfc/manipulating-the-progress-control.md | POMATOpl/cpp-docs.pl-pl | ae1925d41d94142f6a43c4e721d45cbbbfeda4c7 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/mfc/manipulating-the-progress-control.md | POMATOpl/cpp-docs.pl-pl | ae1925d41d94142f6a43c4e721d45cbbbfeda4c7 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
description: 'Dowiedz się więcej o programie: manipulowanie formantem postępu'
title: Operowanie formantem postępu
ms.date: 11/04/2016
helpviewer_keywords:
- CProgressCtrl class [MFC], working with
- progress controls [MFC], manipulating
- CProgressCtrl class [MFC], manipulating
- controlling progress controls [MFC]
- CProgressCtrl class [MFC], using
ms.assetid: 9af561d1-980b-4003-a6da-ff79be15bf23
ms.openlocfilehash: cfb89dee0047d910fb983546c71e4a1e4a618f56
ms.sourcegitcommit: d6af41e42699628c3e2e6063ec7b03931a49a098
ms.translationtype: MT
ms.contentlocale: pl-PL
ms.lasthandoff: 12/11/2020
ms.locfileid: "97281096"
---
# <a name="manipulating-the-progress-control"></a>Operowanie formantem postępu
Istnieją trzy sposoby zmiany bieżącej pozycji kontrolki postępu ([Korzystanie CProgressCtrl](reference/cprogressctrl-class.md)).
- Pozycję można zmienić przez wstępnie ustawioną wartość przyrostu.
- Pozycję można zmienić za pomocą dowolnej kwoty.
- Pozycję można zmienić na określoną wartość.
### <a name="to-change-the-position-by-a-preset-amount"></a>Aby zmienić pozycję przez wstępnie ustawioną kwotę
1. Użyj funkcji elementu członkowskiego [SetStep](reference/cprogressctrl-class.md#setstep) , aby ustawić wartość przyrostu. Wartość domyślna to 10. Ta wartość jest zazwyczaj ustawiana jako jedno z ustawień początkowych dla kontrolki. Wartość kroku może być ujemna.
1. Użyj funkcji składowej [StepIt](reference/cprogressctrl-class.md#stepit) , aby zwiększyć położenie. Powoduje to, że formant będzie ponownie rysowany.
> [!NOTE]
> `StepIt` spowoduje Zawijanie pozycji. Na przykład, mając zakres od 1 -100, krok 20 i pozycja 90, `StepIt` ustawi pozycję na 10.
### <a name="to-change-the-position-by-an-arbitrary-amount"></a>Aby zmienić pozycję przez dowolną kwotę
1. Aby zmienić pozycję, użyj funkcji składowej [OffsetPos](reference/cprogressctrl-class.md#offsetpos) . `OffsetPos` akceptuje wartości ujemne.
> [!NOTE]
> `OffsetPos`, w przeciwieństwie `StepIt` do, nie otacza położenia. Nowe położenie zostanie dostosowane do zakresu.
### <a name="to-change-the-position-to-a-specific-value"></a>Aby zmienić pozycję na określoną wartość
1. Użyj funkcji składowej [SetPos](reference/cprogressctrl-class.md#setpos) , aby ustawić pozycję na określoną wartość. W razie potrzeby nowe położenie zostanie dostosowane do zakresu.
Zazwyczaj kontrolka postępu jest używana wyłącznie dla danych wyjściowych. Aby uzyskać bieżącą pozycję bez określania nowej wartości, użyj [GetPos](reference/cprogressctrl-class.md#getpos).
## <a name="see-also"></a>Zobacz też
[Korzystanie z CProgressCtrl](using-cprogressctrl.md)<br/>
[Formanty](controls-mfc.md)
| 48.763636 | 265 | 0.789709 | pol_Latn | 0.999535 |
986894bff1fb3682e1b660aca9b4c9d405590915 | 1,034 | md | Markdown | WindowsServerDocs/administration/windows-commands/telnet-display.md | Alexisblues/windowsserverdocs.es-es | 957fb5bbea150c6927f3b2674979a1839b0a55c7 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-09-02T07:49:33.000Z | 2020-09-02T07:49:33.000Z | WindowsServerDocs/administration/windows-commands/telnet-display.md | Alexisblues/windowsserverdocs.es-es | 957fb5bbea150c6927f3b2674979a1839b0a55c7 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | WindowsServerDocs/administration/windows-commands/telnet-display.md | Alexisblues/windowsserverdocs.es-es | 957fb5bbea150c6927f3b2674979a1839b0a55c7 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: telnet display
description: Artículo de referencia para la visualización de Telnet, que muestra los parámetros operativos.
ms.topic: reference
ms.assetid: 9272086c-3aaa-405d-ac71-652f25e2eb34
author: coreyp-at-msft
ms.author: coreyp
manager: dongill
ms.date: 10/16/2017
ms.openlocfilehash: f1ae8cd4b16457297e5f29854e44bc984ff0209a
ms.sourcegitcommit: 96d46c702e7a9c3a321bbbb5284f73911c7baa3c
ms.translationtype: MT
ms.contentlocale: es-ES
ms.lasthandoff: 08/27/2020
ms.locfileid: "89027063"
---
# <a name="telnet-display"></a>Telnet: Mostrar
> Se aplica a: Windows Server (canal semianual), Windows Server 2019, Windows Server 2016, Windows Server 2012 R2 y Windows Server 2012
Muestra los parámetros operativos.
## <a name="syntax"></a>Sintaxis
```
d[isplay]
```
#### <a name="parameters"></a>Parámetros
None
## <a name="examples"></a>Ejemplos
Mostrar parámetros operativos.
```
d
```
## <a name="additional-references"></a>Referencias adicionales
- [Clave de sintaxis de línea de comandos](command-line-syntax-key.md)
| 28.722222 | 135 | 0.769826 | spa_Latn | 0.262218 |
986a852f5285b86ca23248e30bd3f5d4b471f7ec | 3,466 | md | Markdown | _posts/2017-4-30-Week14.md | nikita09/nikita09.github.io | 51dd2a21de594ea46d0257792952fb4c5fddb3c4 | [
"MIT"
] | null | null | null | _posts/2017-4-30-Week14.md | nikita09/nikita09.github.io | 51dd2a21de594ea46d0257792952fb4c5fddb3c4 | [
"MIT"
] | null | null | null | _posts/2017-4-30-Week14.md | nikita09/nikita09.github.io | 51dd2a21de594ea46d0257792952fb4c5fddb3c4 | [
"MIT"
] | null | null | null | ---
layout: post
title: Week 14
---
### What did you do this past week?
This past week as usual I went to the lectures for the presentations. On Tuesday groups presented the extra credit lectures. It was interesting hearing listening various other python topics we did not cover in class. On Thrusday half of the groups presented their idb projects including us. It was interesting to see other projects and what other groups struggled with or learned. I think overall our presentation went well for our project. We also presented our extra credit about subprocesses which went well as well. We also got our final grade back for the udb project.
### What's in your way?
The only thing in my way now is the exam next week. I did not do too well on the last exam so I want to do better on ths exam. Also, I was not that good about keeping up with the material sometimes when I got busy with the project so there will be a lot more to review this time around. Other than that the semester is coming to an end and all grades are already in. The only thing left for the semester is the exam next week.
### What will you do next week?
This next week I plan on going to lectures as per usual. There is one more day of presentations and then on Thursday we have the exam. For next week I plan on preparing for the exam on Thursday. I want to go through all the lectures and pracice coding the concepts gone over in class. Additionally, I plan on reviewing all the readings because last exam there were more questions than I was expecting from the readings. I also want to go through the quizzes so I can practice some questions. It would be really good practice to go through the quizzes since when I take it I don't do too well.
### Class experience
Overall, I enjoy this class. I think Professor Fraij is an amazing teacher and makes the learning a lot more easier. I really liked working with my group too for the idb project. Everyone in my group was extremely smart and very easy to work with. We have not had any disagreements yet and someone is always willing to help others when someone is stuck. This is a nice change from other group projects I have worked on in the past. I really liked working with this group and on this project Other than the group project, I also like the material of the class and it is going at a good pace I think. The projects were fun and not too difficult. I got to learn a lot from the projects. The exam was a lot harder than I expected. The quizzes were a little nerve wrecking especially cause they were timed and you could not go back to change your answers. I always ended up makng silly mistakes and missed points. I wish I could have done better on the quizzes. Overall, I am really glad I got to take this class during my last semester at UT. I have learned some valuable skills that I will be able to apply in my job.
### Tip-of-the-week
My tip of the week is for everyone who is not graduating yet. I suggest all those who are still here and registering for classes to take electives you have an interest in. I know there were semesters when I was picking electives just by how easy the class will be. I kind of regret that a little because then I just took the class for the grade and not to actually learn. Down the road it will really help you decide what you like working on. It will especially help you decide what you would want to work on or the type of work you would like to do once you graduate.
| 138.64 | 1,115 | 0.781304 | eng_Latn | 1 |
986a998c45bd291d190ca549705cdfe5dcf89823 | 1,103 | md | Markdown | addons/c_addons.md | yancqS/node-api-cn | 2fc9db3c2ec566873e45b6a526d41d4f8b5d5256 | [
"CC-BY-4.0"
] | 1 | 2021-07-20T08:25:02.000Z | 2021-07-20T08:25:02.000Z | addons/c_addons.md | yancqS/node-api-cn | 2fc9db3c2ec566873e45b6a526d41d4f8b5d5256 | [
"CC-BY-4.0"
] | null | null | null | addons/c_addons.md | yancqS/node-api-cn | 2fc9db3c2ec566873e45b6a526d41d4f8b5d5256 | [
"CC-BY-4.0"
] | null | null | null |
<!--introduced_in=v0.10.0-->
<!-- type=misc -->
插件是用 C++ 编写的动态链接共享对象。
[`require()`][require] 函数可以将插件加载为普通的 Node.js 模块。
插件提供了 JavaScript 和 C/C++ 库之间的接口。
实现插件有三种选择：N-API、nan、或直接使用内部的 V8、libuv 和 Node.js 库。
除非你需要直接访问 N-API 未公开的函数，否则请使用 N-API。
有关 N-API 的更多信息，参阅[具有 N-API 的 C/C++ 插件][_n-api]。
当不使用 N-API 时，实现插件很复杂，涉及多个组件和 API 的知识：
- V8：Node.js 目前用于提供 JavaScript 实现的 C++ 库。
V8 提供了用于创建对象、调用函数等的机制。
V8 的 API 文档主要在 `v8.h` 头文件中（Node.js 源代码树中的 `deps/v8/include/v8.h`），也可以在查看[在线文档][v8-docs]。
- [libuv]：实现了 Node.js 的事件循环、工作线程、以及平台所有的的异步行为的 C 库。
它也是一个跨平台的抽象库，使所有主流操作系统中可以像 POSIX 一样访问常用的系统任务，比如与文件系统、socket、定时器、以及系统事件的交互。
libuv 还提供了一个类似 POSIX 多线程的线程抽象，可被用于强化更复杂的需要超越标准事件循环的异步插件。
建议插件开发者多思考如何通过在 libuv 的非阻塞系统操作、工作线程、或自定义的 libuv 线程中降低工作负载来避免在 I/O 或其他时间密集型任务中阻塞事件循环。
- 内置的 Node.js 库。Node.js 自身公开了插件可以使用的 C++ API，其中最重要的是 `node::ObjectWrap` 类。
- Node.js 包含了其他的静态链接库，如 OpenSSL。
这些库位于 Node.js 源代码树中的 `deps/` 目录。
只有 libuv、OpenSSL、V8 和 zlib 符号是被 Node.js 有目的地重新公开，并且可以被插件在不同程度上使用。
更多信息可查看[链接到 Node.js 自带的库][Linking to libraries included with Node.js]。
以下所有示例均可供[下载][download]，并可用作学习插件的起点。
| 33.424242 | 91 | 0.731641 | yue_Hant | 0.819378 |
986bbc726a6fd939bf825092053e10ea1cb1f43d | 1,652 | md | Markdown | README.md | BlockSync/BlockSync | 0954134951b33d65e336ba9cb045282e667596e9 | [
"MIT"
] | null | null | null | README.md | BlockSync/BlockSync | 0954134951b33d65e336ba9cb045282e667596e9 | [
"MIT"
] | 4 | 2015-05-11T03:57:29.000Z | 2015-05-18T19:57:29.000Z | README.md | BlockSync/BlockSync | 0954134951b33d65e336ba9cb045282e667596e9 | [
"MIT"
] | 3 | 2015-05-06T21:32:59.000Z | 2019-04-16T23:07:31.000Z | #BlockSync
[](https://travis-ci.org/BlockSync/BlockSync)
[](http://codecov.io/github/BlockSync/BlockSync?branch=master)
###What is BlockSync?
BlockSync is a library that is intended to make working with blocks easier, quicker to develop, and safer. BlockSync has the following ideals and goals:
* To make working with blocks, especially asyncronous blocks, easier.
* To ensure thread safety, but to not interfere with threads in any way.
* Tasks with concurrency limits must be followed perfectly.
* To maintain 100% code coverage.
* Should not cause dead locks.
* Should not waste time or CPU cycles in order to make the function work.
* Should not have race conditions.
BlockSync is a well tested (100% coverage), but is not mature. With time, usage, and feedback, it can become mature and battle-tested. I would like to challenge the community to find corner cases where BlockSync does not follow the goals mentioned above.
###PR Guidelines
* You must maintain 100% code coverage.
* Tests must cover all corner cases.
* Callbacks must always be called on the original thread.
* Invalid states should throw an exception.
* Description of what you've changed, and why is mandatory.
I highly encourage people to open pull requests and to try to break it-- the community is what makes projects great! :)
BlockSync was heavily inspired by [caolan/async](https://github.com/caolan/async). Eventually, BlockSync should implement all functionality of caolan/async, and extend it further.
| 56.965517 | 254 | 0.781477 | eng_Latn | 0.995783 |
986bc641302828bcfe107fd6f179a9bc6f18bc33 | 11,174 | md | Markdown | articles/hdinsight/hbase/apache-hbase-phoenix-psql.md | maiemy/azure-docs.it-it | b3649d817c2ec64a3738b5f05f18f85557d0d9b6 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/hdinsight/hbase/apache-hbase-phoenix-psql.md | maiemy/azure-docs.it-it | b3649d817c2ec64a3738b5f05f18f85557d0d9b6 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/hdinsight/hbase/apache-hbase-phoenix-psql.md | maiemy/azure-docs.it-it | b3649d817c2ec64a3738b5f05f18f85557d0d9b6 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Caricamento bulk di dati in Apache Phoenix tramite psql - Azure HDInsight
description: Usare lo strumento PSQL per caricare i dati di caricamento bulk in tabelle Apache Phoenix in Azure HDInsight
author: hrasheed-msft
ms.author: hrasheed
ms.reviewer: jasonh
ms.service: hdinsight
ms.topic: how-to
ms.custom: hdinsightactive
ms.date: 12/17/2019
ms.openlocfilehash: 513d48114d73b2c91ebecf06f9492a6ebf0ba1cf
ms.sourcegitcommit: 829d951d5c90442a38012daaf77e86046018e5b9
ms.translationtype: MT
ms.contentlocale: it-IT
ms.lasthandoff: 10/09/2020
ms.locfileid: "89504707"
---
# <a name="bulk-load-data-into-apache-phoenix-using-psql"></a>Caricamento bulk di dati in Apache Phoenix tramite psql
[Apache Phoenix](https://phoenix.apache.org/) è un database relazionale open source altamente parallelo basato su [Apache HBase](../hbase/apache-hbase-overview.md). Phoenix fornisce query simili a SQL tramite HBase. Phoenix usa i driver JDBC per consentire agli utenti di creare, eliminare e modificare tabelle, indici, viste e sequenze, nonché righe upsert SQL singolarmente e in blocco. Phoenix usa la compilazione nativa noSQL anziché MapReduce per compilare query e crea applicazioni a bassa latenza basate su HBase. Phoenix aggiunge coprocessori per supportare l'esecuzione del codice fornito dal client nello spazio degli indirizzi del server, eseguendo il codice che si trova nello stesso percorso dei dati. In questo modo viene ridotto al minimo il trasferimento di dati client/server. Per usare i dati tramite Phoenix in HDInsight, creare innanzitutto le tabelle e quindi caricarci i dati.
## <a name="bulk-loading-with-apache-phoenix"></a>Caricamento bulk di dati con Apache Phoenix
Esistono diversi modi per caricare i dati in HBase, tra cui l'uso di API client, un processo MapReduce con TableOutputFormat o l'immissione manuale dei dati tramite la shell di HBase. Phoenix offre due metodi per caricare i dati CSV nelle tabelle di Phoenix: uno strumento di caricamento client denominato `psql` e uno strumento di caricamento bulk basato su MapReduce.
`psql` è uno strumento a thread singolo ed è ideale per il caricamento di megabyte o gigabyte di dati. Tutti i file CSV da caricare devono avere l'estensione csv. È anche possibile specificare i file di script SQL nella riga di comando `psql` con l'estensione sql.
Il caricamento bulk con MapReduce viene usato per volumi di dati maggiori, in genere negli scenari di produzione, in quanto MapReduce usa più thread.
Prima di avviare il caricamento dei dati, verificare che Phoenix sia abilitato e che le impostazioni di timeout delle query siano quelle previste. Accedere al dashboard [Apache Ambari](https://ambari.apache.org/) del cluster HDInsight, selezionare HBase e quindi la scheda configurazione. Scorrere verso il basso per verificare che Apache Phoenix sia impostato su `enabled` come illustrato:
### <a name="use-psql-to-bulk-load-tables"></a>Usare `psql` per il caricamento bulk delle tabelle
1. Creare un file denominato `createCustomersTable.sql` e copiare il codice seguente nel file. Salvare quindi il file e chiuderlo.
```sql
CREATE TABLE Customers (
ID varchar NOT NULL PRIMARY KEY,
Name varchar,
Income decimal,
Age INTEGER,
Country varchar);
```
1. Creare un file denominato `listCustomers.sql` e copiare il codice seguente nel file. Salvare quindi il file e chiuderlo.
```sql
SELECT * from Customers;
```
1. Creare un file denominato `customers.csv` e copiare il codice seguente nel file. Salvare quindi il file e chiuderlo.
```txt
1,Samantha,260000.0,18,US
2,Sam,10000.5,56,US
3,Anton,550150.0,42,Norway
```
1. Creare un file denominato `customers2.csv` e copiare il codice seguente nel file. Salvare quindi il file e chiuderlo.
```txt
4,Nicolle,180000.0,22,US
5,Kate,210000.5,24,Canada
6,Ben,45000.0,32,Poland
```
1. Aprire un prompt dei comandi e passare alla directory in cui si trova il percorso dei file appena creati. Sostituire CLUSTERname, sotto, con il nome effettivo del cluster HBase. Eseguire quindi il codice per caricare i file nel nodo head del cluster:
```cmd
scp customers.csv customers2.csv createCustomersTable.sql listCustomers.sql sshuser@CLUSTERNAME-ssh.azurehdinsight.net:/tmp
```
1. Usare il [comando ssh](../hdinsight-hadoop-linux-use-ssh-unix.md) per connettersi al cluster. Modificare il comando seguente sostituendo CLUSTERNAME con il nome del cluster in uso e quindi immettere il comando:
```cmd
ssh sshuser@CLUSTERNAME-ssh.azurehdinsight.net
```
1. Dalla sessione SSH passare alla directory del percorso dello strumento **PSQL** . Eseguire il comando seguente:
```bash
cd /usr/hdp/current/phoenix-client/bin
```
1. Caricamento bulk dei dati. Il codice riportato di seguito creerà la tabella **Customers** e quindi caricherà i dati.
```bash
python psql.py /tmp/createCustomersTable.sql /tmp/customers.csv
```
Al termine dell' `psql` operazione, verrà visualizzato un messaggio simile al seguente:
```output
csv columns from database.
CSV Upsert complete. 3 rows upserted
Time: 0.081 sec(s)
```
1. È possibile continuare a utilizzare `psql` per visualizzare il contenuto della tabella Customers. Eseguire il codice seguente:
```bash
python psql.py /tmp/listCustomers.sql
```
In alternativa, è possibile usare [HBase Shell](./query-hbase-with-hbase-shell.md)o [Apache Zeppelin](./apache-hbase-phoenix-zeppelin.md) per eseguire query sui dati.
1. Caricare dati aggiuntivi. Ora che la tabella esiste già, il comando specifica la tabella. Eseguire il comando seguente:
```bash
python psql.py -t CUSTOMERS /tmp/customers2.csv
```
## <a name="use-mapreduce-to-bulk-load-tables"></a>Usare MapReduce per il caricamento bulk delle tabelle
Per un caricamento con velocità effettiva più elevata distribuito nel cluster, usare lo strumento di caricamento di MapReduce. Questo caricatore innanzitutto converte tutti i dati in HFiles e quindi fornisce i HFiles creati a HBase.
1. Questa sezione continua con la sessione SSH e gli oggetti creati in precedenza. Creare la tabella **Customers** e **customers.csv** file in base alle esigenze seguendo la procedura descritta sopra. Se necessario, ristabilire la connessione SSH.
1. Troncare il contenuto della tabella **Customers** . Dalla sessione ssh aperta, eseguire i comandi seguenti:
```bash
hbase shell
truncate 'CUSTOMERS'
exit
```
1. Copiare il `customers.csv` file da nodo head in archiviazione di Azure.
```bash
hdfs dfs -put /tmp/customers.csv wasbs:///tmp/customers.csv
```
1. Passare alla directory di esecuzione per il comando di caricamento bulk di MapReduce:
```bash
cd /usr/hdp/current/phoenix-client
```
1. Avviare il caricatore CSV di MapReduce usando il comando `hadoop` con il file jar del client Phoenix:
```bash
HADOOP_CLASSPATH=/usr/hdp/current/hbase-client/lib/hbase-protocol.jar:/etc/hbase/conf hadoop jar phoenix-client.jar org.apache.phoenix.mapreduce.CsvBulkLoadTool --table Customers --input /tmp/customers.csv
```
Al termine del caricamento, verrà visualizzato un messaggio simile al seguente:
```output
19/12/18 18:30:57 INFO client.ConnectionManager$HConnectionImplementation: Closing master protocol: MasterService
19/12/18 18:30:57 INFO client.ConnectionManager$HConnectionImplementation: Closing zookeeper sessionid=0x26f15dcceff02c3
19/12/18 18:30:57 INFO zookeeper.ZooKeeper: Session: 0x26f15dcceff02c3 closed
19/12/18 18:30:57 INFO zookeeper.ClientCnxn: EventThread shut down
19/12/18 18:30:57 INFO mapreduce.AbstractBulkLoadTool: Incremental load complete for table=CUSTOMERS
19/12/18 18:30:57 INFO mapreduce.AbstractBulkLoadTool: Removing output directory /tmp/50254426-aba6-400e-88eb-8086d3dddb6
```
1. Per usare MapReduce con Azure Data Lake Storage, individuare la directory radice di Azure Data Lake Storage, ovvero il valore `hbase.rootdir` in `hbase-site.xml`. Nel comando seguente, la directory radice di Azure Data Lake Storage è `adl://hdinsightconf1.azuredatalakestore.net:443/hbase1`. In questo comando specificare le cartelle di input e di output di Azure Data Lake Storage come parametri:
```bash
cd /usr/hdp/current/phoenix-client
$HADOOP_CLASSPATH=$(hbase mapredcp):/etc/hbase/conf hadoop jar /usr/hdp/2.4.2.0-258/phoenix/phoenix-4.4.0.2.4.2.0-258-client.jar
org.apache.phoenix.mapreduce.CsvBulkLoadTool --table Customers --input adl://hdinsightconf1.azuredatalakestore.net:443/hbase1/data/hbase/temp/input/customers.csv –zookeeper ZookeeperQuorum:2181:/hbase-unsecure --output adl://hdinsightconf1.azuredatalakestore.net:443/hbase1/data/hbase/output1
```
1. Per eseguire una query e visualizzare i dati, è possibile usare **PSQL** come descritto in precedenza. È anche possibile usare [HBase Shell](./query-hbase-with-hbase-shell.md)o [Apache Zeppelin](./apache-hbase-phoenix-zeppelin.md).
## <a name="recommendations"></a>Consigli
* Usare lo stesso supporto di archiviazione per le cartelle di input e di output: Archiviazione di Azure (WASB) o Azure Data Lake Storage (ADL). Per trasferire i dati da Archiviazione di Azure ad Azure Data Lake Storage, è possibile usare il comando `distcp`:
```bash
hadoop distcp wasb://@.blob.core.windows.net/example/data/gutenberg adl://.azuredatalakestore.net:443/myfolder
```
* Usare nodi di lavoro di dimensioni maggiori. I processi di mapping della copia bulk di MapReduce producono grandi quantità di file di output temporanei che riempiono lo spazio disponibile non-DFS. Per un caricamento bulk di grandi dimensioni, usare più nodi di lavoro e nodi di lavoro più grandi. Il numero di nodi di lavoro allocati al cluster influisce direttamente sulla velocità di elaborazione.
* Suddividere i file di input in blocchi di circa 10 GB. Il caricamento bulk è un'operazione con uso intensivo delle risorse di archiviazione, pertanto la suddivisione dei file di input in più blocchi garantisce prestazioni migliori.
* Evitare le aree sensibili del server di area. Se la chiave di riga aumenta in maniera monotona, le scritture sequenziali di HBase possono causare la formazione di aree sensibili nel server di area. L'uso di *valori salt* nella chiave di riga consente di ridurre le scritture sequenziali. Phoenix offre un modo per usare valori salt in modo trasparente nella chiave di riga con un byte di salt per una determinata tabella, come illustrato negli articoli di seguito.
## <a name="next-steps"></a>Passaggi successivi
* [Bulk Data Loading with Apache Phoenix](https://phoenix.apache.org/bulk_dataload.html) (Caricamento bulk di dati con Apache Phoenix)
* [Usare Apache Phoenix con cluster Apache HBase basati su Linux in HDInsight](../hbase/apache-hbase-query-with-phoenix.md)
* [Tabelle con salting](https://phoenix.apache.org/salted.html)
* [Grammatica Apache Phoenix](https://phoenix.apache.org/language/index.html)
| 58.810526 | 899 | 0.768838 | ita_Latn | 0.984767 |
986be0e227ee2a08874338b70b2d195df731499e | 3,073 | md | Markdown | presentation/TypeTheory.md | emilien-jegou/Irie-lang | f5b3646753e8b6bfb3dcafdab7e37b94cd257d71 | [
"BSD-3-Clause"
] | 36 | 2020-07-26T22:22:53.000Z | 2021-02-10T15:05:24.000Z | presentation/TypeTheory.md | emilien-jegou/Irie-lang | f5b3646753e8b6bfb3dcafdab7e37b94cd257d71 | [
"BSD-3-Clause"
] | 2 | 2020-07-29T17:42:05.000Z | 2020-07-31T15:13:59.000Z | presentation/TypeTheory.md | emilien-jegou/Irie-lang | f5b3646753e8b6bfb3dcafdab7e37b94cd257d71 | [
"BSD-3-Clause"
] | 1 | 2020-09-08T15:46:16.000Z | 2020-09-08T15:46:16.000Z | # Monotype environments (typing schemes)
2 environments have a greatest lower bound: d1 n d2, where (d1 n d2) (x) = d1(x) n d2(x)
interpret d1(x) = T for x not present in d1
! subsumption (on typing schemes) allows instantiation of type variables
# Generalization
suppose `e = let x = e1 in e2`. e1 must be typeable and have principal ty [D1-]t1+ under Pi
the most general choice is to insert x into Pi with principal type of e1
ie. x depends on lambda-bound vars, so those are moved into Pi (as monotype environments)
Generalisation: we want polymorphic typing schemes to be instantiated with fresh variables on every use
* lift all dominated irreducible THVars and THArgs to debruijn Pi bindings
* generalize at Abs (mutual functions together)
* only modify dominated type variables "Dominion" data (messing with the environment is obviously unsound)
Simplification is incidentally conveniently handled now:
* remove polar variables (those that appear only positively or only negatively) `a & int -> int`
* unify inseparable positive variables (co-occurence `a&b -> a|b` and indistinguishable variables `a->b->a|b`)
* unify variables that contain the same upper and lower bound (a<:t and t<:a)`a&int->a|int`
* minimize recursive types that may have been unrolled during biunification
# Note. Rank-n polymorphism
A constraint a <= t- gives a an upper bound ;
which only affects a when used as an upper bound (negative position)
The only exception is when inferring higher-rank polymorphism,
since a- and a+ must have the same polymorphic rank
# BiSubstitution
find substitution solving constraints of the form t+ <= t-
Atomic: (join/meet a type to the var)
a <= t- solved by [m- b = a n [b/a-]t- /a-]
t+ <= a solved by [m+ b = a u [b/a+]t+ /a+]
a <= c solved by [m- b = a n [b/a-]c /a-] -- (or equivalently, [a u b /b+])
SubConstraints, eg: (t1- -> t1+ <= t2+ -> t2-) = {t2+ <= t1- , t+ <= t2-}
# Recursive Types
Recursive types are guarded and covariant
(ie. `Ma. (a->bool)->a` ok, but not `Ma. a->Bool`)
however,
FA t+ , EX t+a and tg+ where ta+ is Bottom or a,
ta+ is guarded in tg+ and t+ = ta+ U tg+
ie. guarded can be weakened to a least pre-fixed point operator mu+:
`mu+ a. t+ = mu a. tg+`
guardedness is only required to coincide mu+ and mu-
covariance excludes `mu a. a->a` ?
: look at 2 types: t1=t2->t1 and t2=t1->t2
can introduce mus by covariances , and
by substitution: `t1=mu a. (mu b. t1->b) -> a`
mu is monotone, so t1 and t2 are still covariant;
t1 = mu a'. mu a. (mu b. a' -> b) -> a
t1 = mu a. (mu b. a->b) -> a
guardedness is crucial here, to introduce mu in t2->t1
otherwise mu+ and mu- wouldn't be the same
non-regular recursion ?
eg. isorecursive non-regular: add opaque roll/unroll primitives
The lambda-bound types here are flexible ie. subsumption can occur before beta-reduction. This can be weakened by instantiation to a (monomorphically abstracted) typing scheme.
We have to unconditionally trust annotations so far as the rank of polymorphism, since that cannot be inferred (cannot insert type abstractions)
| 51.216667 | 176 | 0.718191 | eng_Latn | 0.997633 |
986c58b6172a14d459ae20c1b1024753bee9095e | 156 | md | Markdown | domain/suntimesmediaholdings.com/index.md | billfitzgerald/smmd | 9af567b54b39dc2872cf0ee6c3ada27627490c42 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2020-12-20T19:10:17.000Z | 2021-07-18T22:32:37.000Z | domain/suntimesmediaholdings.com/index.md | billfitzgerald/smmd | 9af567b54b39dc2872cf0ee6c3ada27627490c42 | [
"CC-BY-4.0",
"MIT"
] | 8 | 2020-06-19T16:02:03.000Z | 2021-08-24T16:49:39.000Z | domain/suntimesmediaholdings.com/index.md | billfitzgerald/smmd | 9af567b54b39dc2872cf0ee6c3ada27627490c42 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-06-29T20:36:31.000Z | 2020-06-29T20:36:31.000Z | ---
company-name: "Sun-Times Media"
domain: suntimesmediaholdings.com
home: http://www.suntimesmediaholdings.com/
email: copyrightagent@suntimes.com
---
| 15.6 | 43 | 0.762821 | yue_Hant | 0.116197 |
986d01136c126ffb59618513b5883ecb5e134fed | 181 | md | Markdown | release_notes/1.1.0.md | splunk-soar-connectors/redcanary | f31c87e6e1cf374dc533df05e861dbd562d0a83c | [
"Apache-2.0"
] | null | null | null | release_notes/1.1.0.md | splunk-soar-connectors/redcanary | f31c87e6e1cf374dc533df05e861dbd562d0a83c | [
"Apache-2.0"
] | null | null | null | release_notes/1.1.0.md | splunk-soar-connectors/redcanary | f31c87e6e1cf374dc533df05e861dbd562d0a83c | [
"Apache-2.0"
] | null | null | null | **Red Canary Release Notes - Published by Red Canary May 17, 2021**
**Version 1.1.0 - Released May 17, 2021**
* Added 2 new actions
+ acknowledge detection
+ remediate detection
| 20.111111 | 67 | 0.723757 | eng_Latn | 0.906506 |
986d2c079b2eb6e3c3f9c07e68ee6b0244012526 | 363 | md | Markdown | _authors/laura-scholes.md | etikaj-digital/contentfulpages | 119d7f43253b8022c3da7b0b76c984ccf8a6c420 | [
"MIT"
] | null | null | null | _authors/laura-scholes.md | etikaj-digital/contentfulpages | 119d7f43253b8022c3da7b0b76c984ccf8a6c420 | [
"MIT"
] | null | null | null | _authors/laura-scholes.md | etikaj-digital/contentfulpages | 119d7f43253b8022c3da7b0b76c984ccf8a6c420 | [
"MIT"
] | null | null | null | ---
authorid: 32P81vHWG4wuQq4KImqiuc
fullName: Laura Scholes
lastmodified: 1524652335.161246
photo: 6JcSQGHzKEMAKiIcqW00Ey
profileUrl: https://theconversation.com//profiles/laura-scholes-366827
role: Research Fellow, Australian Research Council (DECRA), School of Early Childhood
and Inclusive Education, Queensland University of Technology
---
No content found | 36.3 | 85 | 0.829201 | eng_Latn | 0.529948 |
986d64b047ff1bf1c040544ed86fef0343cb12bd | 23,062 | md | Markdown | Framework/framework-en.md | small-yellow-dog/CS-Interview-Knowledge-Map | ceddc87b160cfbfcab1943edd5e096fdfee712b4 | [
"MIT"
] | 9,909 | 2018-08-22T05:44:26.000Z | 2022-03-31T07:10:51.000Z | Framework/framework-en.md | small-yellow-dog/CS-Interview-Knowledge-Map | ceddc87b160cfbfcab1943edd5e096fdfee712b4 | [
"MIT"
] | 129 | 2019-07-16T08:54:04.000Z | 2020-03-01T12:53:53.000Z | Framework/framework-en.md | small-yellow-dog/CS-Interview-Knowledge-Map | ceddc87b160cfbfcab1943edd5e096fdfee712b4 | [
"MIT"
] | 1,823 | 2018-08-22T05:44:28.000Z | 2022-03-22T01:03:26.000Z | <!-- START doctoc generated TOC please keep comment here to allow auto update -->
<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
**Table of Contents** *generated with [DocToc](https://github.com/thlorenz/doctoc)*
- [MVVM](#mvvm)
- [Dirty Checking](#dirty-checking)
- [Data hijacking](#data-hijacking)
- [Proxy vs. Object.defineProperty](#proxy-vs-objectdefineproperty)
- [Routing principle](#routing-principle)
- [Virtual Dom](#virtual-dom)
- [Why Virtual Dom is needed](#why-virtual-dom-is-needed)
- [Virtual Dom algorithm introduction](#virtual-dom-algorithm-introduction)
- [Virtual Dom algorithm implementation](#virtual-dom-algorithm-implementation)
- [recursion of the tree](#recursion-of-the-tree)
- [checking property changes](#checking-property-changes)
- [Algorithm Implementation for Detecting List Changes](#algorithm-implementation-for-detecting-list-changes)
- [Iterating and Marking Child Elements](#iterating-and-marking-child-elements)
- [Rendering Difference](#rendering-difference)
- [The End](#the-end)
<!-- END doctoc generated TOC please keep comment here to allow auto update -->
# MVVM
MVVM consists of the following three contents
* View: interface
* Model：Data model
* ViewModel：As a bridge responsible for communicating View and Model
In the JQuery period, if you need to refresh the UI, you need to get the corresponding DOM and then update the UI, so the data and business logic are strongly-coupled with the page.
In MVVM, the UI is driven by data. Once the data is changed, the corresponding UI will be refreshed. If the UI changes, the corresponding data will also be changed. In this way, we can only care about the data flow in business processing without dealing with the page directly. ViewModel only cares about the processing of data and business and does not care how View handles data. In this case, we can separate the View from the Model. If either party changes, it does not necessarily need to change the other party, and some reusable logic can be placed in a ViewModel, allowing multiple Views to reuse this ViewModel.
In MVVM, the core is the two-way binding of data, such as dirty checking by Angular and data hijacking in Vue.
## Dirty Checking
When the specified event is triggered, it will enter the dirty checking and call the `$digest` loop to walk through all the data observers to determine whether the current value is different from the previous value. If a change is detected, it will call the `$watch` function, and then call the `$digest` loop again until no changes are found. The cycle is at least two times, up to ten times.
Although dirty checking has inefficiencies, it can complete the task without caring about how the data is changed, but the two-way binding in `Vue` is problematic. And dirty checking can achieve batch detection of updated values, and then unified update UI, greatly reducing the number of operating DOM. Therefore, inefficiency is also relative, and this is what the benevolent sees the wise and sees wisdom.
## Data hijacking
Vue internally uses `Object.defineProperty()` to implement two-way binding, which allows you to listen for events of `set` and `get`.
```js
var data = { name: 'yck' }
observe(data)
let name = data.name // -> get value
data.name = 'yyy' // -> change value
function observe(obj) {
// judge the type
if (!obj || typeof obj !== 'object') {
return
}
Object.keys(obj).forEach(key => {
defineReactive(obj, key, obj[key])
})
}
function defineReactive(obj, key, val) {
// recurse the properties of child
observe(val)
Object.defineProperty(obj, key, {
enumerable: true,
configurable: true,
get: function reactiveGetter() {
console.log('get value')
return val
},
set: function reactiveSetter(newVal) {
console.log('change value')
val = newVal
}
})
}
```
The above code simply implements how to listen for the `set` and `get` events of the data, but that's not enough. You also need to add a Publish/Subscribe to the property when appropriate.
```html
<div>
{{name}}
</div>
```
::: v-pre
In the process of parsing the template code like above, when encountering `{{name}}`, add a publish/subscribe to the property `name`
:::
```js
// decouple by Dep
class Dep {
constructor() {
this.subs = []
}
addSub(sub) {
// Sub is an instance of Watcher
this.subs.push(sub)
}
notify() {
this.subs.forEach(sub => {
sub.update()
})
}
}
// Global property, configure Watcher with this property
Dep.target = null
function update(value) {
document.querySelector('div').innerText = value
}
class Watcher {
constructor(obj, key, cb) {
// Point Dep.target to itself
// Then trigger the getter of the property to add the listener
// Finally, set Dep.target as null
Dep.target = this
this.cb = cb
this.obj = obj
this.key = key
this.value = obj[key]
Dep.target = null
}
update() {
// get the new value
this.value = this.obj[this.key]
// update Dom with the update method
this.cb(this.value)
}
}
var data = { name: 'yck' }
observe(data)
// Simulate the action triggered by parsing the `{{name}}`
new Watcher(data, 'name', update)
// update Dom innerText
data.name = 'yyy'
```
Next, improve on the `defineReactive` function.
```js
function defineReactive(obj, key, val) {
// recurse the properties of child
observe(val)
let dp = new Dep()
Object.defineProperty(obj, key, {
enumerable: true,
configurable: true,
get: function reactiveGetter() {
console.log('get value')
// Add Watcher to the subscription
if (Dep.target) {
dp.addSub(Dep.target)
}
return val
},
set: function reactiveSetter(newVal) {
console.log('change value')
val = newVal
// Execute the update method of Watcher
dp.notify()
}
})
}
```
The above implements a simple two-way binding. The core idea is to manually trigger the getter of the property to add the Publish/Subscribe.
## Proxy vs. Object.defineProperty
Although `Object.defineProperty` has been able to implement two-way binding, it is still flawed.
* It can only implement data hijacking on properties, so it needs deep traversal of the entire object
* it can't listen to changes in data for arrays
Although Vue can detect the changes in array data, it is actually a hack and is flawed.
```js
const arrayProto = Array.prototype
export const arrayMethods = Object.create(arrayProto)
// hack the following functions
const methodsToPatch = [
'push',
'pop',
'shift',
'unshift',
'splice',
'sort',
'reverse'
]
methodsToPatch.forEach(function (method) {
// get the native function
const original = arrayProto[method]
def(arrayMethods, method, function mutator (...args) {
// call the native function
const result = original.apply(this, args)
const ob = this.__ob__
let inserted
switch (method) {
case 'push':
case 'unshift':
inserted = args
break
case 'splice':
inserted = args.slice(2)
break
}
if (inserted) ob.observeArray(inserted)
// trigger the update
ob.dep.notify()
return result
})
})
```
On the other hand, `Proxy` doesn't have the above problem. It natively supports listening to array changes and can intercept the entire object directly, so Vue will also replace `Object.defineProperty` with `Proxy` in the next big version.
```js
let onWatch = (obj, setBind, getLogger) => {
let handler = {
get(target, property, receiver) {
getLogger(target, property)
return Reflect.get(target, property, receiver);
},
set(target, property, value, receiver) {
setBind(value);
return Reflect.set(target, property, value);
}
};
return new Proxy(obj, handler);
};
let obj = { a: 1 }
let value
let p = onWatch(obj, (v) => {
value = v
}, (target, property) => {
console.log(`Get '${property}' = ${target[property]}`);
})
p.a = 2 // bind `value` to `2`
p.a // -> Get 'a' = 2
```
# Routing principle
The front-end routing is actually very simple to implement. The essence is to listen to changes in the URL, then match the routing rules, display the corresponding page, and no need to refresh. Currently, there are only two implementations of the route used by a single page.
- hash mode
- history mode
`www.test.com/#/` is the hash URL. When the hash value after `#` changes, no request will be sent to server. You can listen to the URL change through the `hashchange` event, and then jump to the corresponding page.
History mode is a new feature of HTML5, which is more beautiful than Hash URL.
# Virtual Dom
[source code](https://github.com/KieSun/My-wheels/tree/master/Virtual%20Dom)
## Why Virtual Dom is needed
As we know, modifying DOM is a costly task. We could consider using JS objects to simulate DOM objects, since operating on JS objects is much more time saving than operating on DOM.
For example
```js
// Let's assume this array simulates a ul which contains five li's.
[1, 2, 3, 4, 5]
// using this to replace the ul above.
[1, 2, 5, 4]
```
From the above example, it's apparent that the first ul's 3rd li is removed, and the 4th and the 5th are exchanged positions.
If the previous operation is applied to DOM, we have the following code:
```js
// removing the 3rd li
ul.childNodes[2].remove()
// interexchanging positions between the 4th and the 5th
let fromNode = ul.childNodes[4]
let toNode = node.childNodes[3]
let cloneFromNode = fromNode.cloneNode(true)
let cloneToNode = toNode.cloneNode(true)
ul.replaceChild(cloneFromNode, toNode)
ul.replaceChild(cloneToNode, fromNode)
```
Of course, in actual operations, we need an identifier for each node, as an index for checking if two nodes are identical. This is why both Vue and React's official documentation suggests using a unique identifier `key` for nodes in a list to ensure efficiency.
DOM element can not only be simulated, but they can also be rendered by JS objects.
Below is a simple implementation of a JS object simulating a DOM element.
```js
export default class Element {
/**
* @param {String} tag 'div'
* @param {Object} props { class: 'item' }
* @param {Array} children [ Element1, 'text']
* @param {String} key option
*/
constructor(tag, props, children, key) {
this.tag = tag
this.props = props
if (Array.isArray(children)) {
this.children = children
} else if (isString(children)) {
this.key = children
this.children = null
}
if (key) this.key = key
}
// render
render() {
let root = this._createElement(
this.tag,
this.props,
this.children,
this.key
)
document.body.appendChild(root)
return root
}
create() {
return this._createElement(this.tag, this.props, this.children, this.key)
}
// create an element
_createElement(tag, props, child, key) {
// create an element with tag
let el = document.createElement(tag)
// set properties on the element
for (const key in props) {
if (props.hasOwnProperty(key)) {
const value = props[key]
el.setAttribute(key, value)
}
}
if (key) {
el.setAttribute('key', key)
}
// add children nodes recursively
if (child) {
child.forEach(element => {
let child
if (element instanceof Element) {
child = this._createElement(
element.tag,
element.props,
element.children,
element.key
)
} else {
child = document.createTextNode(element)
}
el.appendChild(child)
})
}
return el
}
}
```
## Virtual Dom algorithm introduction
The next step after using JS to implement DOM element is to detect object changes.
DOM is a multi-branching tree. If we were to compare the old and the new trees thoroughly, the time complexity would be O(n ^ 3), which is simply unacceptable. Therefore, the React team optimized their algorithm to achieve an O(n) complexity for detecting changes.
The key to achieving O(n) is to only compare the nodes on the same level rather than across levels. This works because in actual usage we rarely move DOM elements across levels.
We then have two steps of the algorithm.
- from top to bottom, from left to right to iterate the object, aka depth first search. This step adds an index to every node, for rendering the differences later.
- whenever a node has a child element, we check whether the child element changed.
## Virtual Dom algorithm implementation
### recursion of the tree
First let's implement the recursion algorithm of the tree. Before doing that, let's consider the different cases of comparing two nodes.
1. new node's `tagName` or `key` is different from that of the old one. This means the old node is replaced, and we don't have to recurse on the node any more because the whole subtree is removed.
2. new node's `tagName` and `key` (maybe nonexistent) are the same as the old's. We start recursing on the subtree.
3. no new node appears. No operation needed.
```js
import { StateEnums, isString, move } from './util'
import Element from './element'
export default function diff(oldDomTree, newDomTree) {
// for recording changes
let patches = {}
// the index starts at 0
dfs(oldDomTree, newDomTree, 0, patches)
return patches
}
function dfs(oldNode, newNode, index, patches) {
// for saving the subtree changes
let curPatches = []
// three cases
// 1. no new node, do nothing
// 2. new nodes' tagName and `key` are different from the old one's, replace
// 3. new nodes' tagName and key are the same as the old one's, start recursing
if (!newNode) {
} else if (newNode.tag === oldNode.tag && newNode.key === oldNode.key) {
// check whether properties changed
let props = diffProps(oldNode.props, newNode.props)
if (props.length) curPatches.push({ type: StateEnums.ChangeProps, props })
// recurse the subtree
diffChildren(oldNode.children, newNode.children, index, patches)
} else {
// different node, replace
curPatches.push({ type: StateEnums.Replace, node: newNode })
}
if (curPatches.length) {
if (patches[index]) {
patches[index] = patches[index].concat(curPatches)
} else {
patches[index] = curPatches
}
}
}
```
### checking property changes
We also have three steps for checking for property changes
1. iterate the old property list, check if the property still exists in the new property list.
2. iterate the new property list, check if there are changes for properties existing in both lists.
3. for the second step, also check if a property doesn't exist in the old property list.
```js
function diffProps(oldProps, newProps) {
// three steps for checking for props
// iterate oldProps for removed properties
// iterate newProps for changed property values
// lastly check if new properties are added
let change = []
for (const key in oldProps) {
if (oldProps.hasOwnProperty(key) && !newProps[key]) {
change.push({
prop: key
})
}
}
for (const key in newProps) {
if (newProps.hasOwnProperty(key)) {
const prop = newProps[key]
if (oldProps[key] && oldProps[key] !== newProps[key]) {
change.push({
prop: key,
value: newProps[key]
})
} else if (!oldProps[key]) {
change.push({
prop: key,
value: newProps[key]
})
}
}
}
return change
}
```
### Algorithm Implementation for Detecting List Changes
This algorithm is the core of the Virtual Dom. Let's go down the list.
The main steps are similar to checking property changes. There are also three steps.
1. iterate the old node list, check if the node still exists in the new list.
2. iterate the new node list, check if there is any new node.
3. for the second step, also check if a node moved.
PS: this algorithm only handles nodes with `key`s.
```js
function listDiff(oldList, newList, index, patches) {
// to make the iteration more convenient, first take all keys from both lists
let oldKeys = getKeys(oldList)
let newKeys = getKeys(newList)
let changes = []
// for saving the node data after changes
// there are several advantages of using this array to save
// 1. we can correctly obtain the index of the deleted node
// 2. we only need to operate on the DOM once for interexchanged nodes
// 3. we only need to iterate for the checking in the `diffChildren` function
// we don't need to check again for nodes existing in both lists
let list = []
oldList &&
oldList.forEach(item => {
let key = item.key
if (isString(item)) {
key = item
}
// checking if the new children has the current node
// if not then delete
let index = newKeys.indexOf(key)
if (index === -1) {
list.push(null)
} else list.push(key)
})
// array after iterative changes
let length = list.length
// since deleting array elements changes the indices
// we remove from the back to make sure indices stay the same
for (let i = length - 1; i >= 0; i--) {
// check if the current element is null, if so then it means we need to remove it
if (!list[i]) {
list.splice(i, 1)
changes.push({
type: StateEnums.Remove,
index: i
})
}
}
// iterate the new list, check if a node is added or moved
// also add and move nodes for `list`
newList &&
newList.forEach((item, i) => {
let key = item.key
if (isString(item)) {
key = item
}
// check if the old children has the current node
let index = list.indexOf(key)
// if not then we need to insert
if (index === -1 || key == null) {
changes.push({
type: StateEnums.Insert,
node: item,
index: i
})
list.splice(i, 0, key)
} else {
// found the node, need to check if it needs to be moved.
if (index !== i) {
changes.push({
type: StateEnums.Move,
from: index,
to: i
})
move(list, index, i)
}
}
})
return { changes, list }
}
function getKeys(list) {
let keys = []
let text
list &&
list.forEach(item => {
let key
if (isString(item)) {
key = [item]
} else if (item instanceof Element) {
key = item.key
}
keys.push(key)
})
return keys
}
```
### Iterating and Marking Child Elements
For this function, there are two main functionalities.
1. checking differences between two lists
2. marking nodes
In general, the functionalities implemented are simple.
```js
function diffChildren(oldChild, newChild, index, patches) {
let { changes, list } = listDiff(oldChild, newChild, index, patches)
if (changes.length) {
if (patches[index]) {
patches[index] = patches[index].concat(changes)
} else {
patches[index] = changes
}
}
// marking last iterated node
let last = null
oldChild &&
oldChild.forEach((item, i) => {
let child = item && item.children
if (child) {
index =
last && last.children ? index + last.children.length + 1 : index + 1
let keyIndex = list.indexOf(item.key)
let node = newChild[keyIndex]
// only iterate nodes existing in both lists
// no need to visit the added or removed ones
if (node) {
dfs(item, node, index, patches)
}
} else index += 1
last = item
})
}
```
### Rendering Difference
From the earlier algorithms, we can already get the differences between two trees. After knowing the differences, we need to locally update DOM. Let's take a look at the last step of Virtual Dom algorithms.
Two main functionalities for this function
1. Deep search the tree and extract the nodes needing modifications
2. Locally update DOM
This code snippet is pretty easy to understand as a whole.
```js
let index = 0
export default function patch(node, patches) {
let changes = patches[index]
let childNodes = node && node.childNodes
// this deep search is the same as the one in diff algorithm
if (!childNodes) index += 1
if (changes && changes.length && patches[index]) {
changeDom(node, changes)
}
let last = null
if (childNodes && childNodes.length) {
childNodes.forEach((item, i) => {
index =
last && last.children ? index + last.children.length + 1 : index + 1
patch(item, patches)
last = item
})
}
}
function changeDom(node, changes, noChild) {
changes &&
changes.forEach(change => {
let { type } = change
switch (type) {
case StateEnums.ChangeProps:
let { props } = change
props.forEach(item => {
if (item.value) {
node.setAttribute(item.prop, item.value)
} else {
node.removeAttribute(item.prop)
}
})
break
case StateEnums.Remove:
node.childNodes[change.index].remove()
break
case StateEnums.Insert:
let dom
if (isString(change.node)) {
dom = document.createTextNode(change.node)
} else if (change.node instanceof Element) {
dom = change.node.create()
}
node.insertBefore(dom, node.childNodes[change.index])
break
case StateEnums.Replace:
node.parentNode.replaceChild(change.node.create(), node)
break
case StateEnums.Move:
let fromNode = node.childNodes[change.from]
let toNode = node.childNodes[change.to]
let cloneFromNode = fromNode.cloneNode(true)
let cloneToNode = toNode.cloneNode(true)
node.replaceChild(cloneFromNode, toNode)
node.replaceChild(cloneToNode, fromNode)
break
default:
break
}
})
}
```
## The End
The implementation of the Virtual Dom algorithms contains the following three steps:
1. Simulate the creation of DOM objects through JS
2. Check differences between two objects
3. Render the differences
```js
let test4 = new Element('div', { class: 'my-div' }, ['test4'])
let test5 = new Element('ul', { class: 'my-div' }, ['test5'])
let test1 = new Element('div', { class: 'my-div' }, [test4])
let test2 = new Element('div', { id: '11' }, [test5, test4])
let root = test1.render()
let patches = diff(test1, test2)
console.log(patches)
setTimeout(() => {
console.log('start updating')
patch(root, patches)
console.log('end updating')
}, 1000)
```
Although the current implementation is simple, it's definitely enough for understanding Virtual Dom algorithms.
| 31.548564 | 620 | 0.667939 | eng_Latn | 0.981307 |
986df8cbb3c48172c335c714531de869e7d6a6cd | 231 | md | Markdown | README.md | alisonmonteiro/is-json-valid | 48cee4c458153b2b0e9417ec9c307266e19af219 | [
"MIT"
] | null | null | null | README.md | alisonmonteiro/is-json-valid | 48cee4c458153b2b0e9417ec9c307266e19af219 | [
"MIT"
] | 2 | 2021-01-01T23:29:35.000Z | 2022-02-14T20:58:04.000Z | README.md | alisonmonteiro/is-json-valid | 48cee4c458153b2b0e9417ec9c307266e19af219 | [
"MIT"
] | null | null | null | # is-json-valid
Determine if a value is a valid JSON
## Install
```
$ npm i --save is-json-valid
```
## Usage
```javascript
const isJsonValid = require('is-json-valid')
const json = '{...}'
isJsonValid(json) //=> boolean
```
| 12.157895 | 44 | 0.632035 | est_Latn | 0.150755 |
986e091d20d760faeb4c615db667c143f60e126a | 593 | md | Markdown | _pages/about.md | moguzozcan/moguzozcan.github.io | 5f0744b513121cd12ee10ae0c3a3b9713b392f22 | [
"BSD-3-Clause",
"MIT"
] | 1 | 2019-01-25T13:15:36.000Z | 2019-01-25T13:15:36.000Z | _pages/about.md | moguzozcan/moguzozcan.github.io | 5f0744b513121cd12ee10ae0c3a3b9713b392f22 | [
"BSD-3-Clause",
"MIT"
] | null | null | null | _pages/about.md | moguzozcan/moguzozcan.github.io | 5f0744b513121cd12ee10ae0c3a3b9713b392f22 | [
"BSD-3-Clause",
"MIT"
] | 2 | 2019-01-11T17:50:22.000Z | 2019-04-08T21:20:33.000Z | ---
permalink: /about/
title: "About Me"
last_modified_at: 2018-01-10T11:22:24-05:00
---
I was born in 12 June 1990 in Rize, Turkey. I studied Electrical and Electronics Engineering at [Bilkent University](http://www.ee.bilkent.edu.tr/tr/).
I completed my MSc. at Middle East Technical University in [EEE](https://eee2.metu.edu.tr/tr) with Computer Engineering track. I have dropped my PhD in Computer Science in Ozyegin University. See [Ozyegin CS](https://cs.ozyegin.edu.tr/tr)
I have been working as a Software Engineer since June 2012 and currently I am working at Facebook London office. | 65.888889 | 238 | 0.767285 | eng_Latn | 0.946738 |
986e4ef48cc7c3afc559fb8495de0cd7fa699b6f | 2,015 | md | Markdown | README.md | Nirav-Madhani/NaturalPartitioning | b69e0c9ac24f08c296e39d93da2eb39b2576b82f | [
"MIT"
] | null | null | null | README.md | Nirav-Madhani/NaturalPartitioning | b69e0c9ac24f08c296e39d93da2eb39b2576b82f | [
"MIT"
] | null | null | null | README.md | Nirav-Madhani/NaturalPartitioning | b69e0c9ac24f08c296e39d93da2eb39b2576b82f | [
"MIT"
] | null | null | null |
# NaturalPartitioning
Simple project to implement Natural Partitioning using on 3-4-5 Rule. You can also generate the final tree using this notebook.
## Features
1. Apply Natural Partitioning to discrete data.
2. Both methods support user defined depth.
3. 2 Variants - Simple Printing and Recursive Dictionary that stores all information about partitioning, and can be plotted as tree.
Sample Input:
```
32, 38, 48, 91, 46, 37, 22, 69, 78, 82, 33, 49, 55, 66, 84, 86, 67, 80, 79, 44
```
Sample Output:
```
8 Distinct MSD
4 Partition
22.0 to 39.25
[32, 38, 37, 22, 33]
2 Distinct MSD
4 Partition
22.0 to 26.0
[22]
26.0 to 30.0
[]
30.0 to 34.0
[32, 33]
34.0 to 38.0
[37]
39.25 to 56.5
[48, 46, 49, 55, 44]
2 Distinct MSD
4 Partition
44.0 to 46.75
[46, 44]
46.75 to 49.5
[48, 49]
49.5 to 52.25
[]
52.25 to 55.0
[]
56.5 to 73.75
[69, 66, 67]
1 Distinct MSD
5 Partition
66.0 to 66.6
[66]
66.6 to 67.2
[67]
67.2 to 67.8
[]
67.8 to 68.4
[]
68.4 to 69.0
[]
73.75 to 91.0
[78, 82, 84, 86, 80, 79]
2 Distinct MSD
4 Partition
78.0 to 80.0
[78, 79]
80.0 to 82.0
[80]
82.0 to 84.0
[82]
84.0 to 86.0
[84]
```
## Applying on Star.csv
This time, rather than just printing, I'm using dictionary to store partition range as well as points in each partition
```
1939.0 - 9551.2
1939.0 - 4420.333333333334
4420.333333333334 - 6901.666666666667
6901.666666666667 - 9383.0
9551.2 - 17163.4
9675.0 - 11541.25
11541.25 - 13407.5
13407.5 - 15273.75
15273.75 - 17140.0
17163.4 - 24775.6
17200.0 - 19057.5
19057.5 - 20915.0
20915.0 - 22772.5
22772.5 - 24630.0
24775.6 - 32387.8
25000.0 - 26459.75
26459.75 - 27919.5
27919.5 - 29379.25
29379.25 - 30839.0
32387.8 - 40000.0
32460.0 - 33768.0
33768.0 - 35076.0
35076.0 - 36384.0
37692.0 - 39000.0
```
Sample Tree:
| 18.486239 | 133 | 0.633251 | eng_Latn | 0.600109 |
986e66388d5ab7ba234b6816a2d3b880fb518853 | 4,754 | md | Markdown | articles/frontdoor/waf-front-door-create-portal.md | EINSTEINPRACIANO/azure-docs.pt-br | 93bbbf115ab76d31e6bc8919a338700294966913 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2019-05-02T14:26:54.000Z | 2019-05-02T14:26:54.000Z | articles/frontdoor/waf-front-door-create-portal.md | jhomarolo/azure-docs.pt-br | d11ab7fab56d90666ea619c6b12754b7761aca97 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/frontdoor/waf-front-door-create-portal.md | jhomarolo/azure-docs.pt-br | d11ab7fab56d90666ea619c6b12754b7761aca97 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Criar uma política de firewall do aplicativo web para frente do Azure usando o portal do Azure
titlesuffix: Azure web application firewall
description: Saiba como criar uma política de WAF (firewall) do aplicativo web usando o portal do Azure.
services: frontdoor
documentationcenter: na
author: KumudD
manager: twooley
ms.service: frontdoor
ms.devlang: na
ms.topic: article
ms.tgt_pltfrm: na
ms.workload: infrastructure-services
ms.date: 04/8/2019
ms.author: kumud;tyao
ms.openlocfilehash: 26db3a67c3efbd0ba2a5c58facd0c07175f7ed12
ms.sourcegitcommit: 3102f886aa962842303c8753fe8fa5324a52834a
ms.translationtype: MT
ms.contentlocale: pt-BR
ms.lasthandoff: 04/23/2019
ms.locfileid: "61460197"
---
# <a name="create-a-waf-policy-for-azure-front-door-by-using-the-azure-portal"></a>Criar uma política de WAF para frente do Azure usando o portal do Azure
Este artigo descreve como criar uma política de WAF (firewall) do aplicativo web básico do Azure e aplicá-la a um host de front-end na frente do Azure.
## <a name="prerequisites"></a>Pré-requisitos
Crie um perfil de Front Door seguindo as instruções descritas no [Guia de Início Rápido: Crie um perfil de Front Door](quickstart-create-front-door.md).
## <a name="create-a-waf-policy"></a>Criar uma política de WAF
Primeiro, crie uma diretiva básica de WAF com gerenciado padrão regra definida (DRS) por meio do portal.
1. No canto superior esquerdo da tela, selecione **criar um recurso**> pesquise **WAF**> selecione **firewall do aplicativo Web (visualização)** > selecione **Criar**.
2. No **Noções básicas** guia da **criar uma política de WAF** página, insira ou selecione as informações a seguir, aceite os padrões para as configurações restantes e, em seguida, selecione **revisar + criar**:
| Configuração | Valor |
| --- | --- |
| Assinatura |Selecione o nome da sua assinatura de porta da frente.|
| Grupo de recursos |Selecione o nome do grupo de recursos da frente.|
| Nome da política |Insira um nome exclusivo para sua política de WAF.|
3. No **associação** guia da **criar uma política de WAF** página, selecione **Adicionar host de front-end**, insira as seguintes configurações e, em seguida, selecione **Add**:
| Configuração | Value |
| --- | --- |
| Porta da frente | Selecione seu nome de perfil de porta da frente.|
| Host de front-end | Selecione o nome do seu host de porta da frente e selecione **adicionar**.|
> [!NOTE]
> Se o host de front-end estiver associado a uma política de WAF, ele é mostrado como esmaecido. Você deve primeiro remover o host de front-end da política associada e, em seguida, reassociar o host de front-end para uma nova política de WAF.
1. Selecione **revisar + criar**, em seguida, selecione **criar**.
## <a name="configure-waf-rules-optional"></a>Configurar regras de WAF (opcionais)
### <a name="change-mode"></a>Alterar modo
Quando você cria uma política de WAF, o padrão do waf política está em **detecção** modo. Na **detecção** modo, o WAF não bloqueia todas as solicitações, em vez disso, as solicitações de correspondência com as regras de WAF são registradas nos logs de WAF.
Para ver o WAF em ação, você pode alterar as configurações do modo de **detecção** à **prevenção**. Na **prevenção** modo, as solicitações que regras de correspondência que são definidas no padrão regra definida (DRS) são bloqueadas e registradas em logs de WAF.
### <a name="default-rule-set-drs"></a>Conjunto de regras padrão (DRS)
Conjunto de regras de padrão gerenciados do Azure é habilitado por padrão. Para desabilitar uma regra individual dentro de um grupo de regras, expandir as regras dentro desse grupo de regra, selecione a **caixa de seleção** na frente de número da regra e selecione **desabilitar** na guia acima. Para alterar os tipos de ações para regras individuais dentro a regra definida, marque a caixa de seleção na frente do número de regra e, em seguida, selecione a **alterar a ação** guia acima.
## <a name="next-steps"></a>Próximas etapas
- Saiba mais sobre [firewall do aplicativo web do Azure](waf-overview.md).
- Saiba mais sobre [do Azure da frente](front-door-overview.md).
| 59.425 | 488 | 0.699201 | por_Latn | 0.998143 |
986eb9ef744b36a595b1989cc3f36d9dbb7687da | 22,433 | md | Markdown | README.md | kipcole9/cldr_dates_times | c5d495ac8bd4cdd8a279a517ed24c243c9c2e4a3 | [
"Apache-2.0"
] | 9 | 2017-10-07T00:01:18.000Z | 2019-01-12T17:20:09.000Z | README.md | kipcole9/cldr_dates_times | c5d495ac8bd4cdd8a279a517ed24c243c9c2e4a3 | [
"Apache-2.0"
] | 8 | 2017-10-05T20:00:52.000Z | 2019-02-12T00:22:11.000Z | README.md | kipcole9/cldr_dates_times | c5d495ac8bd4cdd8a279a517ed24c243c9c2e4a3 | [
"Apache-2.0"
] | 3 | 2017-10-05T11:35:34.000Z | 2018-12-28T16:31:35.000Z | # Date and Time Localization and Formatting
[](https://hex.pm/packages/ex_cldr_dates_times)
[](https://hex.pm/packages/ex_cldr_dates_times)
[](https://hex.pm/packages/ex_cldr_dates_times)
## Installation
**Note that `ex_cldr_dates_times` requires Elixir 1.8 or later.**
Add `ex_cldr_dates_time` as a dependency to your `mix` project:
```
defp deps do
[
{:ex_cldr_dates_times, "~> 2.0"}
]
end
```
then retrieve `ex_cldr_dates_times` from [hex](https://hex.pm/packages/ex_cldr_dates_times):
```
mix deps.get
mix deps.compile
```
### Configuring a required backend module
`ex_cldr_dates_times` uses the configuration set for the dependency `ex_cldr`. See the documentation for [ex_cldr](https://hexdocs.pm/ex_cldr/2.0.0/readme.html#configuration).
A `backend` module is required that is used to host the functions that manage CLDR data. An example to get started is:
1. Create a backend module (see [ex_cldr](https://hexdocs.pm/ex_cldr/2.0.0/readme.html#configuration) for details of the available options). Note the requirement to configure the appropriate `Cldr` provider backends.
```elixir
defmodule MyApp.Cldr do
use Cldr,
locales: ["en", "fr", "ja"],
providers: [Cldr.Number, Cldr.Calendar, Cldr.DateTime]
end
```
2. [Optional] Update `config.exs` configuration to specify this backend as the system default. Not required, but often useful.
```elixir
config :ex_cldr,
default_locale: "en",
default_backend: MyApp.Cldr
```
### Migration from Cldr.DatesTimes Version 1
1. In modules where there are calls to `Cldr.DateTime.to_string/2` (or the `Date` and `Time` equivalents), add `alias MyApp.Cldr` to the top of the module. That will ensure that calls are directed to the backend with minimal code change. This is the preferred approach.
2. Alternatively, update any calls to `Cldr.Date.to_string/2` to call `Cldr.Date.to_string/3` with the second parameter being a backend module. The same applies for migrating to `Cldr.DateTime.to_string/3`, `Cldr.Time.to_string/3` and `Cldr.DateTime.Relative.to_string/3`. For example:
```elixir
# Change from to_string/2 to to_string/3
# Old version
iex> Cldr.DateTime.to_string ~U[2020-05-30 03:52:56Z], format: :short
# New version. Note the addition of a backend module as
# the second parameter.
iex> Cldr.DateTime.to_string ~U[2020-05-30 03:52:56Z], MyApp.Cldr, format: :short
```
## Usage Introduction
`ex_cldr_dates_times` is an addon library application for [ex_cldr](https://hex.pm/packages/ex_cldr) that provides localisation and formatting for dates, times and date_times.
The primary api is `MyApp.Cldr.Date.to_string/2`, `MyApp.Cldr.Time.to_string/2`, `MyApp.Cldr.DateTime.to_string/2` and `MyApp.Cldr.DateTime.Relative.to_string/2`. In the following examples `MyApp` refers to a CLDR backend module that must be defined by the developer:
```elixir
iex> MyApp.Cldr.Date.to_string ~D[2020-05-30]
{:ok, "May 30, 2020"}
iex> MyApp.Cldr.Time.to_string ~U[2020-05-30 03:52:56Z]
{:ok, "3:52:56 AM"}
iex> MyApp.Cldr.DateTime.to_string ~U[2020-05-30 03:52:56Z]
{:ok, "May 30, 2020, 3:52:56 AM"}
# Note that if options are provided, a backend
# module is also required
iex> MyApp.Cldr.DateTime.Relative.to_string 1, unit: :day, format: :narrow
{:ok, "tomorrow"}
```
For help in `iex`:
```elixir
iex> h MyApp.Cldr.Date.to_string
iex> h MyApp.Cldr.Time.to_string
iex> h MyApp.Cldr.DateTime.to_string
iex> h MyApp.Cldr.DateTime.Relative.to_string
```
## Date, Time and DateTime Localization Formatting
Dates, Times and DateTimes can be formatted using:
* The format types defined for each locale. These format types provide cross-locale standardisation and therefore should be preferred where possible. The format types, implemented for `MyApp.Cldr.Date.to_string/2`, `MyApp.Cldr.Time.to_string/2`,`MyApp.Cldr.DateTime.to_string/2` are `:short`, `:medium`, `:long` and `:full`. The default is `:medium`. For example, assuming a configured backend called `MyApp.Cldr`:
```elixir
iex> MyApp.Cldr.DateTime.to_string ~U[2020-05-30 03:52:56Z], format: :short
{:ok, "5/30/20, 3:52 AM"}
iex> MyApp.Cldr.DateTime.to_string ~U[2020-05-30 03:52:56Z], format: :long
{:ok, "May 30, 2020 at 3:52:56 AM UTC"}
iex> MyApp.Cldr.DateTime.to_string ~U[2020-05-30 03:52:56Z], format: :medium
{:ok, "May 30, 2020, 3:52:56 AM"}
iex> MyApp.Cldr.DateTime.to_string ~U[2020-05-30 03:52:56Z], format: :long, locale: "fr"
{:ok, "30 mai 2020 à 03:52:56 UTC"}
```
* A user specified format string. A format string uses one or more formatting symbols to define what date and time elements should be places in the format. A simple example to format the time into hours and minutes:
```elixir
iex> MyApp.Cldr.DateTime.to_string ~U[2020-05-30 03:52:56Z], format: "hh:mm"
{:ok, "03:52"}
```
* For `DateTime`s there is also a set of predefined format name. These format names are returned by `MyApp.Cldr.DateTime.Format.date_time_available_formats/0` (assuming your backend is `MyApp.Cldr`). The set of common format names across all locales configured in `ex_cldr` can be returned by `Cldr.DateTime.Format.common_date_time_format_names`. These format names can be used with the `:format` parameter to `Cldr.DateTime.to_string/2` module only.
```elixir
iex> MyApp.Cldr.DateTime.Format.date_time_available_formats
%{mmmm_w_count_one: "'week' W 'of' MMMM", gy_mmm: "MMM y G", md: "M/d",
mmm_md: "MMMM d", e_hms: "E HH:mm:ss", ed: "d E", y_mmm: "MMM y",
e_hm: "E HH:mm", mmm_ed: "E, MMM d", y_mmm_ed: "E, MMM d, y",
gy_mm_md: "MMM d, y G", mmm: "LLL", y_md: "M/d/y", gy: "y G",
hms: "h:mm:ss a", hm: "h:mm a", y_mmmm: "MMMM y", m: "L",
gy_mmm_ed: "E, MMM d, y G", y_qqq: "QQQ y", e: "ccc", y_qqqq: "QQQQ y",
hmsv: "h:mm:ss a v", mmmm_w_count_other: "'week' W 'of' MMMM",
ehm: "E h:mm a", y_m_ed: "E, M/d/y", h: "h a", hmv: "h:mm a v",
yw_count_other: "'week' w 'of' y", mm_md: "MMM d", y_m: "M/y", m_ed: "E, M/d",
ms: "mm:ss", d: "d", y_mm_md: "MMM d, y", yw_count_one: "'week' w 'of' y",
y: "y", ehms: "E h:mm:ss a"}
# These format types can be invoked for any locale - meaning
# these format names are defined for all configured locales.
iex> Cldr.DateTime.Format.common_date_time_format_names(MyApp.Cldr)
[:gy_mmm, :md, :mmm_md, :e_hms, :ed, :y_mmm, :e_hm, :mmm_ed, :y_mmm_ed,
:gy_mm_md, :mmm, :y_md, :gy, :hms, :hm, :y_mmmm, :m, :gy_mmm_ed, :y_qqq, :e,
:y_qqqq, :hmsv, :mmmm_w_count_other, :ehm, :y_m_ed, :h, :hmv, :yw_count_other,
:mm_md, :y_m, :m_ed, :ms, :d, :y_mm_md, :y, :ehms]
iex> Cldr.DateTime.to_string ~U[2020-05-30 03:52:56Z], MyApp.Cldr, format: :gy_mmm_ed
{:ok, "Sat, May 30, 2020 AD"}
```
## Format strings
The [CLDR standard](http://unicode.org/reports/tr35/tr35-dates.html#Date_Field_Symbol_Table)
defines a wide range of format symbols. Most - but not all - of these symbols are supported in
`Cldr`. The supported symbols are described below. Note the [known restrictions and limitations](#known-restrictions-and-limitations).
| Element | Symbol | Example | Cldr Format |
| :-------------------- | :-------- | :-------------- | :--------------------------------- |
| Era | G, GG, GGG | "AD" | Abbreviated |
| | GGGG | "Anno Domini" | Wide |
| | GGGGG | "A" | Narrow |
| Year | y | 7 | Minimum necessary digits |
| | yy | "17" | Least significant 2 digits |
| | yyy | "017", "2017" | Padded to at least 3 digits |
| | yyyy | "2017" | Padded to at least 4 digits |
| | yyyyy | "02017" | Padded to at least 5 digits |
| ISOWeek Year | Y | 7 | Minimum necessary digits |
| | YY | "17" | Least significant 2 digits |
| | YYY | "017", "2017" | Padded to at least 3 digits |
| | YYYY | "2017" | Padded to at least 4 digits |
| | YYYYY | "02017" | Padded to at least 5 digits |
| Related Gregorian Year | r, rr, rr+ | 2017 | Minimum necessary digits |
| Cyclic Year | U, UU, UUU | "甲子" | Abbreviated |
| | UUUU | "甲子" (for now) | Wide |
| | UUUUU | "甲子" (for now) | Narrow |
| Extended Year | u+ | 4601 | Minimim necessary digits |
| Quarter | Q | 2 | Single digit |
| | QQ | "02" | Two digits |
| | QQQ | "Q2" | Abbreviated |
| | QQQQ | "2nd quarter" | Wide |
| | QQQQQ | "2" | Narrow |
| Standalone Quarter | q | 2 | Single digit |
| | qq | "02" | Two digits |
| | qqq | "Q2" | Abbreviated |
| | qqqq | "2nd quarter" | Wide |
| | qqqqq | "2" | Narrow |
| Month | M | 9 | Single digit |
| | MM | "09" | Two digits |
| | MMM | "Sep" | Abbreviated |
| | MMMM | "September" | Wide |
| | MMMMM | "S" | Narrow |
| Standalone Month | L | 9 | Single digit |
| | LL | "09" | Two digits |
| | LLL | "Sep" | Abbreviated |
| | LLLL | "September" | Wide |
| | LLLLL | "S" | Narrow |
| Week of Year | w | 2, 22 | Single digit |
| | ww | 02, 22 | Two digits, zero padded |
| Week of Month | W | 2 | Single digit. NOT IMPLEMENTED YET |
| Day of Year | D | 3, 33, 333 | Minimum necessary digits |
| | DD | 03, 33, 333 | Minimum of 2 digits, zero padded |
| | DDD | 003, 033, 333 | Minimum of 3 digits, zero padded |
| Day of Month | d | 2, 22 | Minimum necessary digits |
| | dd | 02, 22 | Two digits, zero padded |
| Day of Week | E, EE, EEE | "Tue" | Abbreviated |
| | EEEE | "Tuesday" | Wide |
| | EEEEE | "T" | Narrow |
| | EEEEEE | "Tu" | Short |
| | e | 2 | Single digit |
| | ee | "02" | Two digits |
| | eee | "Tue" | Abbreviated |
| | eeee | "Tuesday" | Wide |
| | eeeee | "T" | Narrow |
| | eeeeee | "Tu" | Short |
| Standalone Day of Week | c, cc | 2 | Single digit |
| | ccc | "Tue" | Abbreviated |
| | cccc | "Tuesday" | Wide |
| | ccccc | "T" | Narrow |
| | cccccc | "Tu" | Short |
| AM or PM | a, aa, aaa | "am." | Abbreviated |
| | aaaa | "am." | Wide |
| | aaaaa | "am" | Narrow |
| Noon, Mid, AM, PM | b, bb, bbb | "mid." | Abbreviated |
| | bbbb | "midnight" | Wide |
| | bbbbb | "md" | Narrow |
| Flexible time period | B, BB, BBB | "at night" | Abbreviated |
| | BBBB | "at night" | Wide |
| | BBBBB | "at night" | Narrow |
| Hour | h, K, H, k | | See the table below |
| Minute | m | 3, 10 | Minimim digits of minutes |
| | mm | "03", "12" | Two digits, zero padded |
| Second | s | 3, 48 | Minimim digits of seconds |
| | ss | "03", "48" | Two digits, zero padded |
| Fractional Seconds | S | 3, 48 | Minimim digits of fractional seconds |
| | SS | "03", "48" | Two digits, zero padded |
| Milliseconds | A+ | 4000, 63241 | Minimim digits of milliseconds since midnight |
| Generic non-location TZ | v | "Etc/UTC" | `:time_zone` key, unlocalised |
| | vvvv | "unk" | Generic timezone name. Currently returns only "unk" |
| Specific non-location TZ | z..zzz | "UTC" | `:zone_abbr` key, unlocalised |
| | zzzz | "GMT" | Delegates to `zone_gmt/4` |
| Timezone ID | V | "unk" | `:zone_abbr` key, unlocalised |
| | VV | "Etc/UTC | Delegates to `zone_gmt/4` |
| | VVV | "Unknown City" | Exemplar city. Not supported. |
| | VVVV | "GMT" | Delegates to `zone_gmt/4 |
| ISO8601 Format | Z..ZZZ | "+0100" | ISO8601 Basic Format with hours and minutes |
| | ZZZZ | "+01:00" | Delegates to `zone_gmt/4 |
| | ZZZZZ | "+01:00:10" | ISO8601 Extended format with optional seconds |
| ISO8601 plus Z | X | "+01" | ISO8601 Basic Format with hours and optional minutes or "Z" |
| | XX | "+0100" | ISO8601 Basic Format with hours and minutes or "Z" |
| | XXX | "+0100" | ISO8601 Basic Format with hours and minutes, optional seconds or "Z" |
| | XXXX | "+010059" | ISO8601 Basic Format with hours and minutes, optional seconds or "Z" |
| | XXXXX | "+01:00:10" | ISO8601 Extended Format with hours and minutes, optional seconds or "Z" |
| ISO8601 minus Z | x | "+0100" | ISO8601 Basic Format with hours and optional minutes |
| | xx | "-0800" | ISO8601 Basic Format with hours and minutes |
| | xxx | "+01:00" | ISO8601 Extended Format with hours and minutes |
| | xxxx | "+010059" | ISO8601 Basic Format with hours and minutes, optional seconds |
| | xxxxx | "+01:00:10" | ISO8601 Extended Format with hours and minutes, optional seconds |
| GMT Format | O | "+0100" | Short localised GMT format |
| | OOOO | "+010059" | Long localised GMT format |
## Formatting symbols for hour of day
The hour of day can be formatted differently depending whether
a 12- or 24-hour day is being represented and depending on the
way in which midnight and noon are represented. The following
table illustrates the differences:
| Symbol | Midn. | Morning | Noon | Afternoon | Midn. |
| :----: | :---: | :-----: | :--: | :--------: | :---: |
| h | 12 | 1...11 | 12 | 1...11 | 12 |
| K | 0 | 1...11 | 0 | 1...11 | 0 |
| H | 0 | 1...11 | 12 | 13...23 | 0 |
| k | 24 | 1...11 | 12 | 13...23 | 24 |
## Relative Date, Time and DateTime Localization Formatting
The primary API for formatting relative dates and datetimes is `MyApp.Cldr.DateTime.Relative.to_string/2`. Some examples:
```elixir
iex> MyApp.Cldr.DateTime.Relative.to_string(-1)
{:ok, "1 second ago"}
iex> MyApp.Cldr.DateTime.Relative.to_string(1)
{:ok, "in 1 second"}
iex> MyApp.Cldr.DateTime.Relative.to_string(1, unit: :day)
{:ok, "tomorrow"}
iex> MyApp.Cldr.DateTime.Relative.to_string(1, unit: :day, locale: "fr")
{:ok, "demain"}
iex> MyApp.Cldr.DateTime.Relative.to_string(1, unit: :day, format: :narrow)
{:ok, "tomorrow"}
iex> MyApp.Cldr.DateTime.Relative.to_string(1234, unit: :year)
{:ok, "in 1,234 years"}
iex> MyApp.Cldr.DateTime.Relative.to_string(1234, unit: :year, locale: "fr")
{:ok, "dans 1 234 ans"}
iex> MyApp.Cldr.DateTime.Relative.to_string(31)
{:ok, "in 31 seconds"}
iex> MyApp.Cldr.DateTime.Relative.to_string(~D[2017-04-29], relative_to: ~D[2017-04-26])
{:ok, "in 3 days"}
iex> MyApp.Cldr.DateTime.Relative.to_string(310, format: :short, locale: "fr")
{:ok, "dans 5 min"}
iex> MyApp.Cldr.DateTime.Relative.to_string(310, format: :narrow, locale: "fr")
{:ok, "+5 min"}
iex> MyApp.Cldr.DateTime.Relative.to_string 2, unit: :wed, format: :short
{:ok, "in 2 Wed."}
iex> MyApp.Cldr.DateTime.Relative.to_string 1, unit: :wed, format: :short
{:ok, "next Wed."}
iex> MyApp.Cldr.DateTime.Relative.to_string -1, unit: :wed, format: :short
{:ok, "last Wed."}
iex> MyApp.Cldr.DateTime.Relative.to_string -1, unit: :wed
{:ok, "last Wednesday"}
iex> MyApp.Cldr.DateTime.Relative.to_string -1, unit: :quarter
{:ok, "last quarter"}
iex> MyApp.Cldr.DateTime.Relative.to_string -1, unit: :mon, locale: "fr"
{:ok, "lundi dernier"}
iex> MyApp.Cldr.DateTime.Relative.to_string(~D[2017-04-29], unit: :ziggeraut)
{:error, {Cldr.UnknownTimeUnit,
"Unknown time unit :ziggeraut. Valid time units are [:day, :hour, :minute, :month, :second, :week, :year, :mon, :tue, :wed, :thu, :fri, :sat, :sun, :quarter]"}}
```
## Interval Formatting
Interval formats allow for software to format intervals like "Jan 10-12, 2008" as a shorter and more natural format than "Jan 10, 2008 - Jan 12, 2008". They are designed to take a start and end date, time or datetime plus a formatting pattern and use that information to produce a localized format.
An interval is expressed as either a `from` and `to` date, time or datetime. Or it can also be a `Date.Range` or `CalendarInterval` from the [calendar_interval](https://hex.pm/packages/calendar_interval) library.
`Cldr.Interval.to_string/3` function to format an interval based upon the type of the arguments: date, datetime or time. The modules `Cldr.Date.Interval`, `Cldr.Time.Interval` and `Cldr.DateTime.Interval` also provide a `to_string/3` function for when the desired output format is more specific.
Some examples:
```elixir
iex> Cldr.Interval.to_string ~D[2020-01-01], ~D[2020-12-31], MyApp.Cldr
{:ok, "Jan 1 – Dec 31, 2020"}
iex> Cldr.Interval.to_string ~D[2020-01-01], ~D[2020-01-12], MyApp.Cldr
{:ok, "Jan 1 – 12, 2020"}
iex> Cldr.Interval.to_string ~D[2020-01-01], ~D[2020-01-12], MyApp.Cldr,
...> format: :long
{:ok, "Wed, Jan 1 – Sun, Jan 12, 2020"}
iex> Cldr.Interval.to_string ~D[2020-01-01], ~D[2020-12-01], MyApp.Cldr,
...> format: :long, style: :year_and_month
{:ok, "January – December 2020"}
iex> use CalendarInterval
iex> Cldr.Interval.to_string ~I"2020-01-01/12", MyApp.Cldr,
...> format: :long
{:ok, "Wed, Jan 1 – Sun, Jan 12, 2020"}
iex> Cldr.Interval.to_string ~U[2020-01-01 00:00:00.0Z], ~U[2020-12-01 10:05:00.0Z], MyApp.Cldr,
...> format: :long
{:ok, "January 1, 2020 at 12:00:00 AM UTC – December 1, 2020 at 10:05:00 AM UTC"}
iex> Cldr.Interval.to_string ~U[2020-01-01 00:00:00.0Z], ~U[2020-01-01 10:05:00.0Z], MyApp.Cldr,
...> format: :long
{:ok, "January 1, 2020 at 12:00:00 AM UTC – 10:05:00 AM UTC"}
```
## Known restrictions and limitations
Although largely complete (with respect to the CLDR data), there are some known limitations as of release 2.0.
* *Timezones* Although the timezone format codes are supported (formatting symbols `v`, `V`, `x`, `X`, `z`, `Z`, `O`) not all localisations are performed. Only that data available within a `DateTime` struct is used to format timezone data.
| 58.267532 | 453 | 0.511256 | eng_Latn | 0.726161 |
986edd318ae202e2acbf599c3fc6916a57fb223e | 2,033 | md | Markdown | scripting-docs/winscript/reference/idebugapplicationnodeevents-onaddchild.md | tommorris/visualstudio-docs.fr-fr | dd3606399fd617d5584bbf08bbe616bbdbb36401 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | scripting-docs/winscript/reference/idebugapplicationnodeevents-onaddchild.md | tommorris/visualstudio-docs.fr-fr | dd3606399fd617d5584bbf08bbe616bbdbb36401 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | scripting-docs/winscript/reference/idebugapplicationnodeevents-onaddchild.md | tommorris/visualstudio-docs.fr-fr | dd3606399fd617d5584bbf08bbe616bbdbb36401 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: IDebugApplicationNodeEvents::onAddChild | Documents Microsoft
ms.custom: ''
ms.date: 01/18/2017
ms.prod: windows-script-interfaces
ms.reviewer: ''
ms.suite: ''
ms.tgt_pltfrm: ''
ms.topic: reference
apiname:
- IDebugApplicationNodeEvents.onAddChild
apilocation:
- scrobj.dll
helpviewer_keywords:
- IDebugApplicationNodeEvents::onAddChild
ms.assetid: 59ce33cf-1843-4b03-98a2-34859d3023f7
caps.latest.revision: 8
author: mikejo5000
ms.author: mikejo
manager: ghogen
ms.openlocfilehash: 3df872cd14b6d7fcd455371d1601b2a4082fb39a
ms.sourcegitcommit: aadb9588877418b8b55a5612c1d3842d4520ca4c
ms.translationtype: MT
ms.contentlocale: fr-FR
ms.lasthandoff: 10/27/2017
ms.locfileid: "24726149"
---
# <a name="idebugapplicationnodeeventsonaddchild"></a>IDebugApplicationNodeEvents::onAddChild
Gère l’événement lorsqu’un nœud enfant est ajouté à un objet de nœud d’application de débogage.
## <a name="syntax"></a>Syntaxe
```
HRESULT onAddChild(
IDebugApplicationNode* prddpChild
);
```
#### <a name="parameters"></a>Paramètres
`prddpChild`
[in] Le nœud application de débogage enfant qui a été ajouté.
## <a name="return-value"></a>Valeur de retour
La méthode retourne `HRESULT`. Les valeurs possibles sont notamment celles figurant dans le tableau suivant.
|Valeur|Description|
|-----------|-----------------|
|`S_OK`|La méthode a réussi.|
## <a name="remarks"></a>Remarques
Cette méthode gère l’événement lorsqu’un nœud enfant est ajouté à un objet de nœud d’application de débogage.
Les implémenteurs de le `IDebugApplicationNode` interface déclencher cet événement
## <a name="see-also"></a>Voir aussi
[IDebugApplicationNodeEvents (Interface)](../../winscript/reference/idebugapplicationnodeevents-interface.md)
[IDebugApplicationNodeEvents::onRemoveChild](../../winscript/reference/idebugapplicationnodeevents-onremovechild.md)
[Interface IDebugApplicationNode](../../winscript/reference/idebugapplicationnode-interface.md) | 35.051724 | 120 | 0.744712 | fra_Latn | 0.227768 |
986efae68dc478febc5ae45ef49065d6fddec769 | 64 | md | Markdown | README.md | Adrianducuara/lazyloading | 161e8098248701692b6c95656359a6f9f7c44edf | [
"MIT"
] | null | null | null | README.md | Adrianducuara/lazyloading | 161e8098248701692b6c95656359a6f9f7c44edf | [
"MIT"
] | null | null | null | README.md | Adrianducuara/lazyloading | 161e8098248701692b6c95656359a6f9f7c44edf | [
"MIT"
] | null | null | null | # lazyloading
Lazy loading plugin build with vanilla javascript
| 21.333333 | 49 | 0.84375 | eng_Latn | 0.726537 |
986f2d716136a5e2db7e384a9e786d0013fcd6c1 | 444 | md | Markdown | _posts/2019-06-04-maximum-difference-between-two-elements.md | chenshengxmu/chenshengxmu.github.io | 4198a875c21c932369e02fc58febb1fb4596dffe | [
"CC0-1.0"
] | null | null | null | _posts/2019-06-04-maximum-difference-between-two-elements.md | chenshengxmu/chenshengxmu.github.io | 4198a875c21c932369e02fc58febb1fb4596dffe | [
"CC0-1.0"
] | null | null | null | _posts/2019-06-04-maximum-difference-between-two-elements.md | chenshengxmu/chenshengxmu.github.io | 4198a875c21c932369e02fc58febb1fb4596dffe | [
"CC0-1.0"
] | null | null | null | ---
layout: post
title: Maximum difference between two elements such that larger element appears after the smaller number
---
```java
int maxDiff(int arr[], int arr_size)
{
int max_diff = arr[1] - arr[0];
int min_element = arr[0];
for (int i = 1; i < arr_size; i++)
{
if (arr[i] - min_element > max_diff)
{
max_diff = arr[i] - min_element;
}
if (arr[i] < min_element)
{
min_element = arr[i];
}
}
return max_diff;
}
```
| 17.76 | 104 | 0.628378 | eng_Latn | 0.882766 |
986f4da86c6667e402779f7e9d309d0416cd584a | 915 | md | Markdown | README.md | LuisLota/burger-builder | 4f2d47ad619afdb9805f216972df3bcf2c8af296 | [
"MIT"
] | null | null | null | README.md | LuisLota/burger-builder | 4f2d47ad619afdb9805f216972df3bcf2c8af296 | [
"MIT"
] | null | null | null | README.md | LuisLota/burger-builder | 4f2d47ad619afdb9805f216972df3bcf2c8af296 | [
"MIT"
] | null | null | null | # Burger-Builder
App created to learn React.js using Udemy course by Maximilian Schwarzmüller https://www.udemy.com/course/react-the-complete-guide-incl-redux/
In this Project is using
1. Routing
2. Create components
3. Redux
4. Authentication with firebase
5. Axios
# How to start
Then open in [http://localhost:3000/](http://localhost:3000/)
> deployed in https://react-my-burger-3281f.web.app/
```sh
npm install
npm start
```
# Core features of Burger-Builder
## Can create or signup for an user
## Create awesome burger
## Create actions with ingredients
## Summary of your burger
## You can order what you ask !
## See what orders you already have
 | 18.673469 | 143 | 0.72459 | eng_Latn | 0.787281 |
986f70ef410d01ef4f58edda7005b93ef7cd26d3 | 1,742 | md | Markdown | README.md | theMackabu/Pterodactyl-Theme-Library | 7dc54b3b77201def25832abc375d18819637e1a9 | [
"MIT"
] | null | null | null | README.md | theMackabu/Pterodactyl-Theme-Library | 7dc54b3b77201def25832abc375d18819637e1a9 | [
"MIT"
] | null | null | null | README.md | theMackabu/Pterodactyl-Theme-Library | 7dc54b3b77201def25832abc375d18819637e1a9 | [
"MIT"
] | null | null | null | [](https://github.com/Conjuringil/Pterodactyl-Theme-Library/blob/main/LICENSE)
## Will this break my panel? (IMPORTANT)
This will not break your panel unless you use a diffrent theme version for a diffrent panel version, if it for some reason does break your panel it is simple to remove the theme.
## Panel Versioning
Make sure that the theme you are installing corresponds with the version of the panel you are running; no help will be given if you have mismatched versions!
How do i use them?
You simple follow the instructions below, mainly consisting of two or three changes you need to make before you build your panel.
## Enola - 1.2.0, 1.2.1, and 1.2.2
Instructions to install the theme Enola are here
[Enola 1.2.2(Latest Panel Version)](https://github.com/Conjuringil/Pterodactyl-Theme-Library/wiki/latest-Enola)
## Twilight - 1.1.3, 1.2.0, 1.2.1, 1.2.2
Instructions to install the theme Twilight are here
[Enola 1.2.2(Latest Panel Version)](https://github.com/Conjuringil/Pterodactyl-Theme-Library/wiki/latest-Twilight)
## Recolor - 1.2.0, 1.2.1, 1.2.2
This theme is a recolor of the panel that you can edit, more information here
[Recolor](https://github.com/Conjuringil/Pterodactyl-Theme-Library/wiki/Recolor)
## Dracula - 1.2.0, 1.2.1, 1.2.2
This theme is a recolor of the panel that you can edit, more information here
[Dracula 1.2.2(Latest Panel Version)](https://github.com/Conjuringil/Pterodactyl-Theme-Library/wiki/latest-Dracula)
## If you have suggestions or issues dm me on discord, notil#9999.
| 51.235294 | 178 | 0.76062 | eng_Latn | 0.906577 |
986f729ad317d6ad4a5f8eb0821c106cfbdd0483 | 960 | md | Markdown | README.md | JMax45/instagram-planner | 0dbbb49ac450ac8bbddcb7b46cb72c6fcf6f4f06 | [
"MIT"
] | null | null | null | README.md | JMax45/instagram-planner | 0dbbb49ac450ac8bbddcb7b46cb72c6fcf6f4f06 | [
"MIT"
] | null | null | null | README.md | JMax45/instagram-planner | 0dbbb49ac450ac8bbddcb7b46cb72c6fcf6f4f06 | [
"MIT"
] | null | null | null | # Instagram Planner
A bot to schedule your posts on Instagram.
## Getting started
Use git to clone the bot.
```bash
git clone https://github.com/JMax45/instagram-planner
```
Install dependencies.
```bash
npm install
```
Set the environment variables (create an .env file or configure them depending on the server type).
```
TOKEN= # Your bot token
IG_USERNAME= # Your Instagram username
IG_PASSWORD= # Your Instagram password
DB_URL= # Your database url
DB_NAME= # Your database name
```
## Usage
Run the bot using ```npm start```.
## Making yourself an admin
The /schedule command has a private access so only the admins can execute it.
To register yourself as an admin write /admin to the bot, it will work only if
there are no other administrators to prevent other people from making themselves an admin.
## Schedule posts
Send ```/schedule``` to the bot.
The rest of the process is guided.
## License
[MIT](https://choosealicense.com/licenses/mit/) | 25.263158 | 99 | 0.748958 | eng_Latn | 0.989667 |
986ff89d6f2109e6fe151188a02140edfa2b243d | 4,261 | md | Markdown | articles/automation/automation-testing-runbook.md | Zwoch/azure-docs.de-de | c76b1dfefc2541ca6d661c9eaca428b42b34ebc8 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/automation/automation-testing-runbook.md | Zwoch/azure-docs.de-de | c76b1dfefc2541ca6d661c9eaca428b42b34ebc8 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/automation/automation-testing-runbook.md | Zwoch/azure-docs.de-de | c76b1dfefc2541ca6d661c9eaca428b42b34ebc8 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Testen eines Runbooks in Azure Automation
description: Bevor Sie ein Runbook in Azure Automation veröffentlichen, können Sie es testen, um sicherzustellen, dass es wie erwartet funktioniert. In diesem Artikel wird beschrieben, wie Sie ein Runbook testen und die Ausgabe anzeigen.
services: automation
ms.service: automation
author: georgewallace
ms.author: gwallace
ms.date: 03/16/2018
ms.topic: article
manager: carmonm
ms.openlocfilehash: 531fffe1ed24016d47708a729a3ee7642a1db64a
ms.sourcegitcommit: 48ab1b6526ce290316b9da4d18de00c77526a541
ms.translationtype: HT
ms.contentlocale: de-DE
ms.lasthandoff: 03/23/2018
---
# <a name="testing-a-runbook-in-azure-automation"></a>Testen eines Runbooks in Azure Automation
Wenn Sie ein Runbook testen, wird die [Entwurfsversion](automation-creating-importing-runbook.md#publishing-a-runbook) ausgeführt, und alle darin ausgeführten Aktionen werden abgeschlossen. Es wird kein Auftragsverlauf erstellt, aber die [Ausgabe](automation-runbook-output-and-messages.md#output-stream)- sowie die [Warnungs- und Fehlerdatenströme](automation-runbook-output-and-messages.md#message-streams) werden im Testausgabebereich angezeigt. Nachrichten an den [ausführlichen Datenstrom](automation-runbook-output-and-messages.md#message-streams) werden im Ausgabebereich nur angezeigt, wenn die Variable [$VerbosePreference](automation-runbook-output-and-messages.md#preference-variables) auf „Continue“ festgelegt ist.
Auch wenn die Entwurfsversion ausgeführt wird, führt das Runbook den Workflow trotzdem normal aus und wendet alle Aktionen auf die Ressourcen in der Umgebung an. Aus diesem Grund sollten Sie nur Runbooks für Ressourcen testen, die sich nicht in der Produktionsumgebung befinden.
Das Verfahren zum Testen der verschiedenen [Runbooktypen](automation-runbook-types.md) ist identisch, und es besteht kein Unterschied zwischen Tests mit dem Text-Editor und dem grafischen Editor im Azure-Portal.
## <a name="to-test-a-runbook-in-the-azure-portal"></a>So starten Sie ein Runbook im Azure-Portal
Sie können mit jedem [Runbooktyp](automation-runbook-types.md) im Azure-Portal arbeiten.
1. Öffnen Sie die Entwurfsversion des Runbooks entweder im [Text-Editor](automation-edit-textual-runbook.md) oder im [grafischen Editor](automation-graphical-authoring-intro.md).
2. Klicken Sie auf die Schaltfläche **Test** um das Blatt "Test" zu öffnen.
3. Wenn das Runbook über Parameter verfügt, werden diese im linken Bereich aufgeführt. Hier können Sie die für den Test zu verwendenden Werte angeben.
4. Wenn Sie den Test auf einem [Hybrid Runbook Worker](automation-hybrid-runbook-worker.md), ausführen möchten, ändern Sie die **Testlaufeinstellungen** auf **Hybrid Worker**, und wählen Sie den Namen der Zielgruppe aus. Andernfalls behalten Sie den Standardwert **Azure** bei, um den Test in der Cloud auszuführen.
5. Klicken Sie auf die Schaltfläche **Start** , um den Test zu starten.
6. Wenn das Runbook ein [PowerShell-Workflow](automation-runbook-types.md#powershell-workflow-runbooks) oder [grafisch](automation-runbook-types.md#graphical-runbooks) ist, können Sie es während des Tests mit den Schaltflächen unterhalb des Ausgabebereichs beenden oder anhalten. Wenn Sie das Runbook anhalten, wird die aktuelle Aktivität vor der Unterbrechung abgeschlossen. Nachdem das Runbook angehalten wurde, können Sie es beenden oder erneut starten.
7. Untersuchen Sie die Ausgabe des Runbooks im Ausgabebereich.
## <a name="next-steps"></a>Nächste Schritte
* Informationen zum Erstellen oder Importieren eines Runbooks finden Sie unter [Erstellen oder Importieren eines Runbooks in Azure Automation](automation-creating-importing-runbook.md)
* Weitere Informationen zur grafischen Inhaltserstellung finden Sie unter [Grafische Erstellung in Azure Automation](automation-graphical-authoring-intro.md)
* Die ersten Schritte mit PowerShell-Workflow-Runbooks sind unter [Mein erstes PowerShell-Workflow-Runbook](automation-first-runbook-textual.md)
* Weitere Informationen zum Konfigurieren von Runbooks für die Rückgabe von Statusmeldungen und Fehlern einschließlich der empfohlenen Methoden finden Sie unter [Runbookausgabe und -meldungen in Azure Automation](automation-runbook-output-and-messages.md)
| 103.926829 | 727 | 0.816475 | deu_Latn | 0.99257 |
9870062ad17e0bd632a2289a79e6296f2246bdf5 | 19,223 | md | Markdown | README.md | mrmubanga/rave-android | 08a8309f3b64b245876eeda38be55ab26925d5e5 | [
"Unlicense"
] | 1 | 2021-05-13T14:25:58.000Z | 2021-05-13T14:25:58.000Z | README.md | mrmubanga/rave-android | 08a8309f3b64b245876eeda38be55ab26925d5e5 | [
"Unlicense"
] | null | null | null | README.md | mrmubanga/rave-android | 08a8309f3b64b245876eeda38be55ab26925d5e5 | [
"Unlicense"
] | null | null | null | <p align="center">
<img title="Flutterwave" height="200" src="https://flutterwave.com/images/logo-colored.svg" width="50%"/>
</p>
# Flutterwave Android SDK
Flutterwave's Android SDK can be used to integrate the Flutterwave payment gateway into your android app. It comes with a ready-made Drop In UI and non-UI module, depending on your preference.
The payment methods currently supported are Cards, USSD, Mpesa, GH Mobile Money, UG Mobile Money, ZM Mobile Money, Rwanda Mobile Money, Franc Mobile Money, US ACH, UK Bank, SA Bank, Nigeria Bank Account, Nigeria Bank Transfer, Barter Mobile Wallet.
<img alt="Screenshot of Drop-In" src="https://i.imgur.com/UZZkC6e.png" width="900"/>
## Before you begin
- Ensure you have your test (and live) [API keys](https://developer.flutterwave.com/docs/api-keys).
- The use of this SDK means you have signed up on Flutterwave and have accepted Flutterwave's [terms and conditions](https://flutterwave.com/us/terms) and [privacy policy](https://flutterwave.com/us/privacy-policy).
## Requirements
- The minimum supported SDK version is 15
- Rave android sdk 1.0.50 and above only supports projects that have been migrated to [androidx](https://developer.android.com/jetpack/androidx/). For more information, read Google's [migration guide](https://developer.android.com/jetpack/androidx/migrate).
## Adding it to your project
**Step 1.** Add it in your root build.gradle at the end of repositories:
```groovy
allprojects {
repositories {
//...
maven { url 'https://jitpack.io' }
}
}
```
**Step 2.** Add the dependency
If you want to use the default Drop In UI, add the `rave-android` module dependency
```groovy
dependencies {
implementation 'com.github.flutterwave.rave-android:rave_android:2.1.34'
}
```
if you are not interested in our default UI and you want to use yours and only want to interact with our core sdk, use the `rave_presentation` module
```groovy
dependencies {
implementation 'com.github.Flutterwave.rave-android:rave_presentation:2.1.34'
}
```
**Step 3.** Add the `INTERNET` permission to your android manifest
<uses-permission android:name="android.permission.INTERNET" />
> The steps below show how to use the Flutterwave Android SDK as a Drop-in UI (all the views for the payment process are handled by the SDK). If you would like to use your own custom UI instead, please see the continuation [here](CustomUiImplementation.md).
## Usage
### For using the default UI
### 1. Create a `RaveUiManager` instance
Set the public key, encryption key and other required parameters. The `RaveUiManager` accepts a mandatory instance of the calling `Activity` (or a `Fragment` that has a parent activity).
new RaveUiManager(activity).setAmount(amount)
.setCurrency(currency)
.setEmail(email)
.setfName(fName)
.setlName(lName)
.setNarration(narration)
.setPublicKey(publicKey)
.setEncryptionKey(encryptionKey)
.setTxRef(txRef)
.setPhoneNumber(phoneNumber, boolean)
.acceptAccountPayments(boolean)
.acceptCardPayments(boolean)
.acceptMpesaPayments(boolean)
.acceptAchPayments(boolean)
.acceptGHMobileMoneyPayments(boolean)
.acceptUgMobileMoneyPayments(boolean)
.acceptZmMobileMoneyPayments(boolean)
.acceptRwfMobileMoneyPayments(boolean)
.acceptSaBankPayments(boolean)
.acceptUkPayments(boolean)
.acceptBankTransferPayments(boolean)
.acceptUssdPayments(boolean)
.acceptBarterPayments(boolean)
.acceptFrancMobileMoneyPayments(boolean)
.allowSaveCardFeature(boolean)
.onStagingEnv(boolean)
.setMeta(List<Meta>)
.withTheme(styleId)
.isPreAuth(boolean)
.setSubAccounts(List<SubAccount>)
.shouldDisplayFee(boolean)
.showStagingLabel(boolean)
.initialize();
<details>
<summary>Function Definitions</summary>
| Function | Parameter | Type | Required |
| ------------- |:-------------:| -----:| -----:|
| setAmount(amount) | This is the amount to be charged from card/account | `double` | Required
| setCurrency(currency) | This is the specified currency to charge the card in | `String` | Required
| setfName(fName) | This is the first name of the card holder or the customer | `String` | Required
| setlName(lName) | This is the last name of the card holder or the customer | `String` | Required
| setEmail(email) | This is the email address of the customer | `String` | Required
| setNarration(narration) | This is a custom description added by the merchant. For `Bank Transfer` payments, this becomes the account name of the account to be paid into. See more details [here](https://developer.flutterwave.com/v2.0/reference#pay-with-bank-transfer-nigeria). | `String` | Not Required
| setPublicKey(publicKey) | Merchant's public key. Get your merchant keys here for [ staging](https://flutterwavedevelopers.readme.io/blog/how-to-get-your-staging-keys-from-the-rave-sandbox-environment) and [live](https://flutterwavedevelopers.readme.io/blog/how-to-get-your-live-keys-from-the-rave-dashboard)| `String` | Required
| setEncryptionKey(encryptionKey) | Merchant's encryption key. Get your merchant keys here for [ staging](https://flutterwavedevelopers.readme.io/blog/how-to-get-your-staging-keys-from-the-rave-sandbox-environment) and [live](https://flutterwavedevelopers.readme.io/blog/how-to-get-your-live-keys-from-the-rave-dashboard) | `String` | Required
| setTxRef(txRef) | This is the unique reference, unique to the particular transaction being carried out. It is generated by the merchant for every transaction | `String` | Required
| setPhoneNumber(phoneNumber) | This sets the customer's phone number. This functions is also overloaded to allow you specify whether the customer can edit their phone number as such: `setPhoneNumber(phoneNumber,false)`. When set to false, the user will not be able to change the number you set here.| `String`<br/><br/>Optional overloads:<br/>`String`, `boolean` | Not Required
| acceptAccountPayments(boolean) | Set to `true` if you want to accept payments via bank accounts, else set to `false`. | `boolean` | Not Required
| acceptCardPayments(boolean) | Set to `true` if you want to accept payments via cards, else set to `false` | `boolean` | Not Required |
| acceptMpesaPayments(boolean) | Set to `true` if you want to accept Mpesa payments, else set to `false` . For this option to work, you should set your country to `KE` and your currency to `KES` | `boolean` | Not Required |
| acceptGHMobileMoneyPayments(boolean) | Set to `true` if you want to accept Ghana mobile money payments, else set to `false` . For this option to work, you should set your country to `GH` and your currency to `GHS`| `boolean` | Not Required |
| acceptUgMobileMoneyPayments(boolean) | Set to `true` if you want to accept Uganda mobile money payments, else set to `false` . For this option to work, you should set your country to `UG` and your currency to `UGX`| `boolean` | Not Required |
| acceptZmMobileMoneyPayments(boolean) | Set to `true` if you want to accept Zambia mobile money payments, else set to `false` . For this option to work, you should set your country to `NG` and your currency to `ZMW`. `MTN` is the only available network at the moment, see more details in the [API documentation](https://developer.flutterwave.com/reference#zambia-mobile-money).| `boolean` | Not Required |
| acceptRwfMobileMoneyPayments(boolean) | Set to `true` if you want to accept Rwanda mobile money payments, else set to `false` . For this option to work, you should set your country to `NG` and your currency to `RWF`. See more details in the [API documentation](https://developer.flutterwave.com/reference#rwanda-mobile-money).| `boolean` | Not Required |
| acceptSaBankPayments(boolean) | Set to `true` if you want to accept South African direct bank account payments, else set to `false` . For this option to work, you should set your country to `ZA` and your currency to `ZAR`.| `boolean` | Not Required |
| acceptUkPayments(boolean) | Set to `true` if you want to accept UK Bank Account payments, else set to `false` . For this option to work, you should set your country to `NG`, set currency to `GBP`, set accountbank `String`, set accountname `String`, set accountnumber `String`, set is_uk_bank_charge2 `true`, set payment_type `account`. `Please use your live credentials for this` | `boolean` | Not Required |
| acceptAchPayments(boolean) | Set to `true` if you want to accept US ACH charges from your customers, else set to `false` . For this option to work, you should set your country to `US` and your currency to `USD`. You also have to set `acceptAccountPayments(true)`| `boolean` | Not Required |
| acceptBankTransferPayments(boolean) | Set to `true` if you want to accept payments via bank transfer from your customers, else set to `false`. This option is currently only available for Nigerian Naira. <br/><br/><strong>Note:</strong> By default, the account numbers generated are dynamic. This method has been overloaded for more options as shown below:<br><ul><li>To generate static (permanent) accounts instead, pass in `true` as a second parameter. E.g. <br/>```acceptBankTransferPayments(true, true)```</li><li>To generate accounts that expire at a certain date, or after a certain number of payments, pass in integer values for `duration` and `frequency` as such: <br/>```acceptBankTransferPayments(true, duration, frequency)``` </li></ul>You can get more details in the [API documentation](https://developer.flutterwave.com/v2.0/reference#pay-with-bank-transfer-nigeria).| `boolean`<br/><br/>Optional overloads:<br/>`boolean`, `boolean`<br/><br/>`boolean`, `int`, `int` | Not Required |
| acceptUssdPayments(boolean) | Set to `true` if you want to accept payments via USSD transfer from your customers, else set to `false` . This option is currently only available for the Nigerian Naira.| `boolean` | Not Required |
| acceptBarterPayments(boolean) | Set to `true` if you want to accept payments via Barter from your customers, else set to `false`.| `boolean` | Not Required |
| acceptFrancMobileMoneyPayments(boolean) | Set to `true` if you want to accept Francophone mobile money payments, else set to `false` . For this option to work, you should set your country to `NG` and your currency to `XOF` for West African CFA franc like `Ivory Coast` OR `XAF` for Central African CFA franc like `Cameroon` . See more details in the [API documentation](https://developer.flutterwave.com/reference#mobile-money-francophone).| `boolean` | Not Required |
| allowSaveCardFeature(boolean) | Set to `true` if you want to give the user the option to save their cards for future transactions. This option helps them avoid retyping their card details for every transaction. Defaults to `true`.| `boolean` | Not Required |
| onStagingEnv(boolean) | Set to `true` if you want your transactions to run in the staging environment otherwise set to `false`. Defaults to false | `boolean` | Not Required
| setMeta(`List<Meta>`) | Pass in any other custom data you wish to pass. It takes in a `List` of `Meta` objects | List<Meta> | Not Required
| setSubAccounts(`List<SubAccount>`) | Pass in a `List` of `SubAccount`,if you want to split transaction fee with other people. Subaccounts are your vendors' accounts that you want to settle per transaction. To initialize a `SubAccount` class, do `SubAccount(String subAccountId,String transactionSplitRatio)` or `SubAccount(String subAccountId,String transactionSplitRatio,String transactionChargeType, String transactionCharge)` to also charge the subaccount a fee. [Learn more about split payments and subaccounts](https://developer.flutterwave.com/docs/split-payment).| `List<SubAccount>`| Not Required
| setIsPreAuth(boolean) | Set to `true` to preauthorise the transaction amount. [Learn more about preauthourization](https://developer.flutterwave.com/v2.0/reference#introduction-1). | `int` | Not Required
| withTheme(styleId) | Sets the theme of the UI. | `int` | Not Required
| setPaymentPlan(payment_plan) | If you want to do recurrent payment, this is the payment plan ID to use for the recurring payment, you can see how to create payment plans [here](https://flutterwavedevelopers.readme.io/v2.0/reference#create-payment-plan) and [here](https://flutterwavedevelopers.readme.io/docs/recurring-billing). This is only available for card payments | `String` | Not Required
| shouldDisplayFee(boolean) | Set to `false` to not display a dialog for confirming total amount(including charge fee) that Rave will charge. By default this is set to `true` | `boolean` | Not Required
| showStagingLabel(boolean) | Set to `false` to not display a staging label when in staging environment. By default this is set to `true` | `boolean` | Not Required
| initialize() | Launch the Rave Payment UI for when using the UI module, | N/A | Required
> <strong>Note:</strong> The order in which you call the methods for accepting different payment types is the order in which they will show in the UI.
> To see a more practical way of using the sdk, head to our sample app in the repository [here](https://github.com/Flutterwave/rave-android/tree/master/app)
</details>
### 2. Handle the response
In the calling activity, override the `onActivityResult` method to receive the payment response as shown below
```java
@Override
protected void onActivityResult(int requestCode, int resultCode, Intent data) {
/*
* We advise you to do a further verification of transaction's details on your server to be
* sure everything checks out before providing service or goods.
*/
if (requestCode == RaveConstants.RAVE_REQUEST_CODE && data != null) {
String message = data.getStringExtra("response");
if (resultCode == RavePayActivity.RESULT_SUCCESS) {
Toast.makeText(this, "SUCCESS " + message, Toast.LENGTH_SHORT).show();
}
else if (resultCode == RavePayActivity.RESULT_ERROR) {
Toast.makeText(this, "ERROR " + message, Toast.LENGTH_SHORT).show();
}
else if (resultCode == RavePayActivity.RESULT_CANCELLED) {
Toast.makeText(this, "CANCELLED " + message, Toast.LENGTH_SHORT).show();
}
}
else {
super.onActivityResult(requestCode, resultCode, data);
}
}
```
The intent's `message` object contains the raw JSON response from the Rave API. This can be parsed to retrieve any additional payment information needed. Typical success response can be found [here](https://gist.github.com/bolaware/305ef5a6df7744694d9c35787580a2d2) and failed response [here](https://gist.github.com/bolaware/afa972cbca782bbb942984ddec9f5262).
> **PLEASE NOTE**
> We advise you to do a further verification of transaction's details on your server to be
sure everything checks out before providing service or goods.
### 3. Customize the look
You can apply a new look by changing the color of certain parts of the UI to highlight your brand colors.
First specify the theme in your `styles.xml` file. In this theme, you can edit the style for each of the elements you'd like to style, like the pay button, OTP button, etc.
```XML
<style name="MyCustomTheme" parent="RaveAppTheme.NoActionBar">
<item name="colorPrimary">@color/colorPrimary</item>
<item name="colorPrimaryDark">@color/colorPrimaryDark</item>
<item name="colorAccent">@color/colorAccent</item>
<item name="OTPButtonStyle">@style/myOtpBtnStyle</item>
<item name="PayButtonStyle">@style/myBtnStyle</item>
<item name="PinButtonStyle">@style/myPinButtonStyle</item>
<item name="OTPHeaderStyle">@style/myOtpHeaderStyle</item>
<item name="TabLayoutStyle">@style/myTabLayoutStyle</item>
<item name="PinHeaderStyle">@style/myPinHeaderStyle</item>
<item name="PaymentTileStyle">@style/myPaymentTileStyle</item>
<item name="PaymentTileTextStyle">@style/myPaymentTileTextStyle</item>
<item name="PaymentTileDividerStyle">@style/myPaymentTileDividerStyle</item>
</style>
```
Then in your RavePayManager setup, add `.withTheme(<Reference to your style>)` anywhere before calling the `initialize()` function. e.g.
```java
new RavePayManager(activity).setAmount(amount)
//...
//...
.withTheme(R.Style.MyCustomTheme)
.initialize();
```
> There is a limit to which the drop-in UI can be customized. For further customization, see our Custom UI implemetation guide [here](CustomUiImplementation.md).
## Configuring Proguard
To configure Proguard, add the following lines to your proguard configuration file. These will keep files related to this sdk
```
keepclasseswithmembers public class com.flutterwave.raveandroid.** { *; }
dontwarn com.flutterwave.raveandroid.card.CardFragment
```
## Help
* Have issues integrating? Join our [Slack community](https://join.slack.com/t/flutterwavedevelopers/shared_invite/zt-7mdxu82t-~WwizwN3eWKjUXLY275AzQ) for support
* Find a bug? [Open an issue](https://github.com/Flutterwave/rave-android/issues)
* Want to contribute? [Check out contributing guidelines]() and [submit a pull request](https://help.github.com/articles/creating-a-pull-request).
## Want to contribute?
Feel free to create issues and pull requests. The more concise the pull requests the better :)
## License
```
Rave's Android SDK
MIT License
Copyright (c) 2020
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
```
| 75.980237 | 996 | 0.717682 | eng_Latn | 0.947041 |
98702d01b65f7746051f887c0eb9dad9f98788f2 | 723 | md | Markdown | vra7/vra7.md | chrisjaimon2012/tfwriter | 1ea629ed386bbe6a8f21617a430dae19ba536a98 | [
"MIT"
] | 78 | 2021-01-15T14:10:30.000Z | 2022-02-14T09:17:40.000Z | vra7/vra7.md | chrisjaimon2012/tfwriter | 1ea629ed386bbe6a8f21617a430dae19ba536a98 | [
"MIT"
] | 5 | 2021-04-09T15:21:28.000Z | 2022-01-28T19:02:05.000Z | vra7/vra7.md | chrisjaimon2012/tfwriter | 1ea629ed386bbe6a8f21617a430dae19ba536a98 | [
"MIT"
] | 30 | 2021-01-17T13:16:57.000Z | 2022-03-21T12:52:08.000Z | ---
layout: resource
title: vra7
type: provider
resource: vra7
---
### Index
- [Example Usage](#example-usage)
- [Resources](#resources)
- [Datasources](#datasources)
### Example Usage
```terraform
provider "vra7" {
version = "3.0.2"
# host - (required) is a type of string
host = null
# insecure - (optional) is a type of bool
insecure = null
# password - (required) is a type of string
password = null
# tenant - (required) is a type of string
tenant = null
# username - (required) is a type of string
username = null
}
```
[top](#index)
### Resources
- [vra7_deployment](./r/vra7_deployment.md)
[top](#index)
### Datasources
- [vra7_deployment](./d/vra7_deployment.md)
[top](#index) | 14.755102 | 45 | 0.650069 | eng_Latn | 0.821502 |
987038cee12496dc3dfa1c9de1a3b132e2e45458 | 5,109 | md | Markdown | articles/active-directory/application-config-sso-problem-configure-federated-sso-non-gallery.md | diablo444/azure-docs.de-de | 168079679b8171e6c2b6957d21d581f05752689d | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/active-directory/application-config-sso-problem-configure-federated-sso-non-gallery.md | diablo444/azure-docs.de-de | 168079679b8171e6c2b6957d21d581f05752689d | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/active-directory/application-config-sso-problem-configure-federated-sso-non-gallery.md | diablo444/azure-docs.de-de | 168079679b8171e6c2b6957d21d581f05752689d | [
"CC-BY-4.0",
"MIT"
] | 1 | 2022-01-21T14:22:47.000Z | 2022-01-21T14:22:47.000Z | ---
title: "Probleme beim Konfigurieren des einmaligen Anmeldens im Verbund für eine nicht im Katalog enthaltene Anwendung | Microsoft-Dokumentation"
description: "Hier finden Sie Informationen zu den häufigsten Problemen, die beim Konfigurieren des einmaligen Anmeldens im Verbund mit einer benutzerdefinierten SAML-Anwendung auftreten können, die nicht im Azure AD-Anwendungskatalog aufgeführt ist."
services: active-directory
documentationcenter:
author: ajamess
manager: femila
ms.assetid:
ms.service: active-directory
ms.workload: identity
ms.tgt_pltfrm: na
ms.devlang: na
ms.topic: article
ms.date: 07/11/2017
ms.author: asteen
ms.translationtype: Human Translation
ms.sourcegitcommit: a1ba750d2be1969bfcd4085a24b0469f72a357ad
ms.openlocfilehash: d6bc4a67a95f41db7f89fbafd35819d38a9844d1
ms.contentlocale: de-de
ms.lasthandoff: 06/20/2017
---
# <a name="problem-configuring-federated-single-sign-on-for-a-non-gallery-application"></a>Probleme beim Konfigurieren des einmaligen Anmeldens im Verbund für eine nicht im Katalog enthaltene Anwendung
Wenn beim Konfigurieren einer Anwendung ein Problem auftritt: Vergewissern Sie sich, dass Sie alle im Artikel [Konfigurieren des einmaligen Anmeldens für Anwendungen, die nicht im Azure Active Directory-Anwendungskatalog enthalten sind](https://docs.microsoft.com/azure/active-directory/active-directory-saas-custom-apps) beschriebenen Schritte ausgeführt haben.
## <a name="cant-add-another-instance-of-the-application"></a>Es kann keine weitere Instanz der Anwendung hinzugefügt werden.
Wenn Sie eine zweite Instanz einer Anwendung hinzufügen möchten, muss Folgendes möglich sein:
- Konfigurieren eines eindeutigen Bezeichners für die zweite Instanz. Sie können nicht den Bezeichner konfigurieren, den Sie bereits für die erste Instanz verwendet haben.
- Konfigurieren eines anderen Zertifikats als des Zertifikats, das für die erste Instanz verwendet wurde.
Wenn die Anwendung keinen der genannten Punkte unterstützt, können Sie keine zweite Instanz konfigurieren.
## <a name="where-do-i-set-the-entityid-user-identifier-format"></a>Wo wird das Format für EntityID (Benutzer-ID) festgelegt?
Sie können das Format für EntityID (Benutzer-ID), das von Azure AD nach der Benutzerauthentifizierung in der Antwort an die Anwendung gesendet wird, nicht auswählen.
In Azure AD wird das Format für das NameID-Attribut (Benutzer-ID) auf Grundlage des ausgewählten Werts oder des Formats festgelegt, das von der Anwendung in der SAML-Authentifizierungsanforderung angefordert wird. Weitere Informationen finden Sie im Artikel [SAML-Protokoll für einmaliges Anmelden](https://docs.microsoft.com/azure/active-directory/develop/active-directory-single-sign-on-protocol-reference#authnrequest) im Abschnitt zu NameIDPolicy.
## <a name="where-do-i-get-the-application-metadata-or-certificate-from-azure-ad"></a>Wo erhalte ich die Metadaten für die Anwendung oder das Zertifikat aus Azure AD?
Führen Sie zum Herunterladen der Metadaten für die Anwendung oder des Zertifikats aus Azure AD die folgenden Schritte aus:
1. Melden Sie sich beim [**Azure-Portal**](https://portal.azure.com/) als **Globaler Administrator** oder **Co-Administrator** an.
2. Öffnen Sie die **Azure Active Directory-Erweiterung**, indem Sie unten im Hauptnavigationsmenü auf der linken Seite auf **Weitere Dienste** klicken.
3. Geben Sie im Filtersuchfeld **Azure Active Directory** ein, und wählen Sie das Element **Azure Active Directory** aus.
4. Klicken Sie im linken Azure Active Directory-Navigationsmenü auf **Unternehmensanwendungen**.
5. Klicken Sie auf **Alle Anwendungen**, um eine Liste aller Anwendungen anzuzeigen.
* Wenn die gewünschte Anwendung nicht angezeigt wird, verwenden Sie das Steuerelement **Filter** oberhalb der Liste **Alle Anwendungen**, und legen Sie die Option **Anzeigen** auf **Alle Anwendungen** fest.
6. Wählen Sie die Anwendung aus, für die Sie das einmalige Anmelden konfiguriert haben.
7. Nachdem die Anwendung geladen wurde, klicken Sie im linken Navigationsmenü der Anwendung auf **Einmaliges Anmelden**.
8. Wechseln Sie zum Abschnitt **SAML-Signaturzertifikat**, und klicken Sie auf den Spaltenwert **Herunterladen**. Abhängig davon, welche Werte die Anwendung für die Konfiguration des einmaligen Anmeldens benötigt, wird die Option zum Herunterladen des Metadaten-XML oder des Zertifikats angezeigt.
Azure AD stellt keine URL zum Abrufen der Metadaten bereit. Die Metadaten können nur als XML-Datei abgerufen werden.
## <a name="dont-know-how-to-customize-saml-claims-sent-to-an-application"></a>Sie wissen nicht, wie man SAML-Ansprüche anpasst, die an eine Anwendung gesendet werden
Weitere Informationen zum Anpassen der SAML-Attributansprüche, die an Ihre Anwendung gesendet werden, finden Sie unter [Zuordnen von Benutzeransprüchen in Azure Active Directory](https://docs.microsoft.com/azure/active-directory/active-directory-claims-mapping).
## <a name="next-steps"></a>Nächste Schritte
[Verwalten von Anwendungen mit Azure Active Directory](active-directory-enable-sso-scenario.md)
| 68.12 | 451 | 0.80368 | deu_Latn | 0.995344 |
987059f14d5d5633f7b98b5a4f9e38db01b85d5c | 25,520 | md | Markdown | pyfunctest.md | Lunkov/pyfunctest | 2bc57a5307084d35fed12fd2f054c8dcafe4fb34 | [
"MIT"
] | 1 | 2021-05-03T12:51:50.000Z | 2021-05-03T12:51:50.000Z | pyfunctest.md | Lunkov/pyfunctest | 2bc57a5307084d35fed12fd2f054c8dcafe4fb34 | [
"MIT"
] | null | null | null | pyfunctest.md | Lunkov/pyfunctest | 2bc57a5307084d35fed12fd2f054c8dcafe4fb34 | [
"MIT"
] | null | null | null | # Table of Contents
* [fmods](#fmods)
* [FMods](#fmods.FMods)
* [\_\_init\_\_](#fmods.FMods.__init__)
* [scan](#fmods.FMods.scan)
* [printList](#fmods.FMods.printList)
* [count](#fmods.FMods.count)
* [getConfig](#fmods.FMods.getConfig)
* [getTmpFolder](#fmods.FMods.getTmpFolder)
* [startAll](#fmods.FMods.startAll)
* [stopAll](#fmods.FMods.stopAll)
* [fmod](#fmod)
* [FMod](#fmod.FMod)
* [\_\_init\_\_](#fmod.FMod.__init__)
* [isDocker](#fmod.FMod.isDocker)
* [minio](#minio)
* [MinIO](#minio.MinIO)
* [\_\_init\_\_](#minio.MinIO.__init__)
* [\_\_init\_\_](#__init__)
* [mysql](#mysql)
* [MySQL](#mysql.MySQL)
* [\_\_init\_\_](#mysql.MySQL.__init__)
* [git](#git)
* [GIT](#git.GIT)
* [\_\_init\_\_](#git.GIT.__init__)
* [clone](#git.GIT.clone)
* [httpserver](#httpserver)
* [HTTPSrv](#httpserver.HTTPSrv)
* [\_\_init\_\_](#httpserver.HTTPSrv.__init__)
* [migrate](#migrate)
* [Migrate](#migrate.Migrate)
* [\_\_init\_\_](#migrate.Migrate.__init__)
* [isMigrate](#migrate.Migrate.isMigrate)
* [run](#migrate.Migrate.run)
* [fmod\_db](#fmod_db)
* [FModDB](#fmod_db.FModDB)
* [\_\_init\_\_](#fmod_db.FModDB.__init__)
* [postgre](#postgre)
* [Postgre](#postgre.Postgre)
* [\_\_init\_\_](#postgre.Postgre.__init__)
* [http](#http)
* [HTTP](#http.HTTP)
* [\_\_init\_\_](#http.HTTP.__init__)
* [lfs](#lfs)
* [LFS](#lfs.LFS)
* [rm](#lfs.LFS.rm)
* [rabbitmq](#rabbitmq)
* [RabbitMQ](#rabbitmq.RabbitMQ)
* [\_\_init\_\_](#rabbitmq.RabbitMQ.__init__)
* [getConnect](#rabbitmq.RabbitMQ.getConnect)
* [kafka](#kafka)
* [Kafka](#kafka.Kafka)
* [\_\_init\_\_](#kafka.Kafka.__init__)
* [getConnect](#kafka.Kafka.getConnect)
* [ftp](#ftp)
* [FTP](#ftp.FTP)
* [getConnect](#ftp.FTP.getConnect)
* [docker](#docker)
* [Docker](#docker.Docker)
* [\_\_init\_\_](#docker.Docker.__init__)
* [build](#docker.Docker.build)
* [status](#docker.Docker.status)
* [start](#docker.Docker.start)
* [restart](#docker.Docker.restart)
* [stop](#docker.Docker.stop)
* [remove](#docker.Docker.remove)
* [logs](#docker.Docker.logs)
* [run](#docker.Docker.run)
* [statusWaiting](#docker.Docker.statusWaiting)
* [copy](#docker.Docker.copy)
* [src](#src)
* [src.fmods](#src.fmods)
* [FMods](#src.fmods.FMods)
* [\_\_init\_\_](#src.fmods.FMods.__init__)
* [scan](#src.fmods.FMods.scan)
* [printList](#src.fmods.FMods.printList)
* [count](#src.fmods.FMods.count)
* [getConfig](#src.fmods.FMods.getConfig)
* [getTmpFolder](#src.fmods.FMods.getTmpFolder)
* [startAll](#src.fmods.FMods.startAll)
* [stopAll](#src.fmods.FMods.stopAll)
* [src.fmod](#src.fmod)
* [FMod](#src.fmod.FMod)
* [\_\_init\_\_](#src.fmod.FMod.__init__)
* [isDocker](#src.fmod.FMod.isDocker)
* [src.test](#src.test)
* [src.test.mysql\_test](#src.test.mysql_test)
* [src.test.docker\_test](#src.test.docker_test)
* [src.test.kafka\_test](#src.test.kafka_test)
* [src.test.http\_test](#src.test.http_test)
* [src.test.minio\_test](#src.test.minio_test)
* [src.test.fmods\_test](#src.test.fmods_test)
* [src.test.rabbitmq\_test](#src.test.rabbitmq_test)
* [src.test.git\_test](#src.test.git_test)
* [src.test.postgre\_test](#src.test.postgre_test)
* [src.test.ftp\_test](#src.test.ftp_test)
* [src.minio](#src.minio)
* [MinIO](#src.minio.MinIO)
* [\_\_init\_\_](#src.minio.MinIO.__init__)
* [src.mysql](#src.mysql)
* [MySQL](#src.mysql.MySQL)
* [\_\_init\_\_](#src.mysql.MySQL.__init__)
* [src.git](#src.git)
* [GIT](#src.git.GIT)
* [\_\_init\_\_](#src.git.GIT.__init__)
* [clone](#src.git.GIT.clone)
* [src.httpserver](#src.httpserver)
* [HTTPSrv](#src.httpserver.HTTPSrv)
* [\_\_init\_\_](#src.httpserver.HTTPSrv.__init__)
* [src.migrate](#src.migrate)
* [Migrate](#src.migrate.Migrate)
* [\_\_init\_\_](#src.migrate.Migrate.__init__)
* [isMigrate](#src.migrate.Migrate.isMigrate)
* [run](#src.migrate.Migrate.run)
* [src.fmod\_db](#src.fmod_db)
* [FModDB](#src.fmod_db.FModDB)
* [\_\_init\_\_](#src.fmod_db.FModDB.__init__)
* [src.postgre](#src.postgre)
* [Postgre](#src.postgre.Postgre)
* [\_\_init\_\_](#src.postgre.Postgre.__init__)
* [src.http](#src.http)
* [HTTP](#src.http.HTTP)
* [\_\_init\_\_](#src.http.HTTP.__init__)
* [src.lfs](#src.lfs)
* [LFS](#src.lfs.LFS)
* [rm](#src.lfs.LFS.rm)
* [src.rabbitmq](#src.rabbitmq)
* [RabbitMQ](#src.rabbitmq.RabbitMQ)
* [\_\_init\_\_](#src.rabbitmq.RabbitMQ.__init__)
* [getConnect](#src.rabbitmq.RabbitMQ.getConnect)
* [src.kafka](#src.kafka)
* [Kafka](#src.kafka.Kafka)
* [\_\_init\_\_](#src.kafka.Kafka.__init__)
* [getConnect](#src.kafka.Kafka.getConnect)
* [src.ftp](#src.ftp)
* [FTP](#src.ftp.FTP)
* [getConnect](#src.ftp.FTP.getConnect)
* [src.docker](#src.docker)
* [Docker](#src.docker.Docker)
* [\_\_init\_\_](#src.docker.Docker.__init__)
* [build](#src.docker.Docker.build)
* [status](#src.docker.Docker.status)
* [start](#src.docker.Docker.start)
* [restart](#src.docker.Docker.restart)
* [stop](#src.docker.Docker.stop)
* [remove](#src.docker.Docker.remove)
* [logs](#src.docker.Docker.logs)
* [run](#src.docker.Docker.run)
* [statusWaiting](#src.docker.Docker.statusWaiting)
* [copy](#src.docker.Docker.copy)
<a name="fmods"></a>
# fmods
Class for work with testing Modules
<a name="fmods.FMods"></a>
## FMods Objects
```python
class FMods(object)
```
Class for load and build environment modules for functional tests
<a name="fmods.FMods.__init__"></a>
#### \_\_init\_\_
```python
| __init__(pathModules, pathTmp='', verbose=True)
```
Initialising object
Parameters
----------
pathModules : str
path to modules settings
pathTmp : str
path to temporary files
verbose : bool
verbose output
<a name="fmods.FMods.scan"></a>
#### scan
```python
| scan()
```
Scan subfolders for modules settings (path_modules)
<a name="fmods.FMods.printList"></a>
#### printList
```python
| printList()
```
Output the list of modules
<a name="fmods.FMods.count"></a>
#### count
```python
| count()
```
Count of modules
<a name="fmods.FMods.getConfig"></a>
#### getConfig
```python
| getConfig(moduleName)
```
Get configuration of module
Parameters
----------
moduleName : str
name of module
<a name="fmods.FMods.getTmpFolder"></a>
#### getTmpFolder
```python
| getTmpFolder(moduleName)
```
Get temporary path for module
Parameters
----------
moduleName : str
name of the module
Returns
-------
path:
temporary path for the module
<a name="fmods.FMods.startAll"></a>
#### startAll
```python
| startAll()
```
setUp for UTests
<a name="fmods.FMods.stopAll"></a>
#### stopAll
```python
| stopAll()
```
tearDown for UTests
<a name="fmod"></a>
# fmod
Class for work with testing Modules
<a name="fmod.FMod"></a>
## FMod Objects
```python
class FMod()
```
Class for environment module for functional tests
<a name="fmod.FMod.__init__"></a>
#### \_\_init\_\_
```python
| __init__(config, pathTmp, verbose)
```
Initialising object
Parameters
----------
config : dict
config of module
pathTmp : str
path to temporary files
verbose : bool
verbose output
<a name="fmod.FMod.isDocker"></a>
#### isDocker
```python
| isDocker()
```
Get parameters of module for docker
Returns
-------
ok
success
<a name="minio"></a>
# minio
Class for work with testing Modules
<a name="minio.MinIO"></a>
## MinIO Objects
```python
class MinIO(FMod)
```
Class for work with Minio
<a name="minio.MinIO.__init__"></a>
#### \_\_init\_\_
```python
| __init__(config, pathTmp, verbose)
```
Initialising object
Parameters
----------
config : dict
config of module
pathTmp : str
path to temporary files
verbose : bool
verbose output
<a name="__init__"></a>
# \_\_init\_\_
<a name="mysql"></a>
# mysql
Class for work with testing Modules
<a name="mysql.MySQL"></a>
## MySQL Objects
```python
class MySQL(FModDB)
```
Class for work with DB
<a name="mysql.MySQL.__init__"></a>
#### \_\_init\_\_
```python
| __init__(config, pathTmp, verbose)
```
Initialising object
Parameters
----------
config : dict
config of module
pathTmp : str
path to temporary files
verbose : bool
verbose output
<a name="git"></a>
# git
Class for work with testing Modules
<a name="git.GIT"></a>
## GIT Objects
```python
class GIT(FMod)
```
Class for load and build environment modules for functional tests
<a name="git.GIT.__init__"></a>
#### \_\_init\_\_
```python
| __init__(config, pathTmp, verbose)
```
Initialising object
Parameters
----------
config : dict
config of module
pathTmp : str
path to temporary files
verbose : bool
verbose output
<a name="git.GIT.clone"></a>
#### clone
```python
| clone()
```
Clone git repository
<a name="httpserver"></a>
# httpserver
Class for work with testing Modules
<a name="httpserver.HTTPSrv"></a>
## HTTPSrv Objects
```python
class HTTPSrv(FMod)
```
Class for work with HTTP (server)
<a name="httpserver.HTTPSrv.__init__"></a>
#### \_\_init\_\_
```python
| __init__(config, pathTmp, verbose)
```
Initialising object
Parameters
----------
config : dict
config of module
pathTmp : str
path to temporary files
verbose : bool
verbose output
<a name="migrate"></a>
# migrate
Class for work with testing Modules
<a name="migrate.Migrate"></a>
## Migrate Objects
```python
class Migrate(FMod)
```
Class for load and build environment modules for functional tests
<a name="migrate.Migrate.__init__"></a>
#### \_\_init\_\_
```python
| __init__(config, pathTmp, verbose)
```
Initialising object
Parameters
----------
config : dict
config of module
pathTmp : str
path to temporary files
verbose : bool
verbose output
<a name="migrate.Migrate.isMigrate"></a>
#### isMigrate
```python
| isMigrate()
```
Get parameters of module for Migrate
Returns
-------
ok
success
<a name="migrate.Migrate.run"></a>
#### run
```python
| run()
```
Migrate for Database container
<a name="fmod_db"></a>
# fmod\_db
Class for work with testing Modules
<a name="fmod_db.FModDB"></a>
## FModDB Objects
```python
class FModDB(FMod)
```
Class for environment module for functional tests
<a name="fmod_db.FModDB.__init__"></a>
#### \_\_init\_\_
```python
| __init__(config, pathTmp, verbose)
```
Initialising object
Parameters
----------
config : dict
config of module
pathTmp : str
path to temporary files
verbose : bool
verbose output
<a name="postgre"></a>
# postgre
Class for work with testing Modules
<a name="postgre.Postgre"></a>
## Postgre Objects
```python
class Postgre(FModDB)
```
Class for work with DB
<a name="postgre.Postgre.__init__"></a>
#### \_\_init\_\_
```python
| __init__(config, pathTmp, verbose)
```
Initialising object
Parameters
----------
config : dict
config of module
pathTmp : str
path to temporary files
verbose : bool
verbose output
<a name="http"></a>
# http
Class for work with testing Modules
<a name="http.HTTP"></a>
## HTTP Objects
```python
class HTTP(FMod)
```
Class for work with HTTP (client)
<a name="http.HTTP.__init__"></a>
#### \_\_init\_\_
```python
| __init__(config, pathTmp, verbose)
```
Initialising object
Parameters
----------
config : dict
config of module
pathTmp : str
path to temporary files
verbose : bool
verbose output
<a name="lfs"></a>
# lfs
Class for work with testing Modules
<a name="lfs.LFS"></a>
## LFS Objects
```python
class LFS(object)
```
Class for load and build environment modules for functional tests
<a name="lfs.LFS.rm"></a>
#### rm
```python
| @staticmethod
| rm(pathName)
```
remove folders
<a name="rabbitmq"></a>
# rabbitmq
Class for work with testing Modules
<a name="rabbitmq.RabbitMQ"></a>
## RabbitMQ Objects
```python
class RabbitMQ(FMod)
```
Class for work with RabbitMQ
<a name="rabbitmq.RabbitMQ.__init__"></a>
#### \_\_init\_\_
```python
| __init__(config, pathTmp, verbose)
```
Initialising object
Parameters
----------
config : dict
config of module
pathTmp : str
path to temporary files
verbose : bool
verbose output
<a name="rabbitmq.RabbitMQ.getConnect"></a>
#### getConnect
```python
| getConnect()
```
Connect to rabbitMQ
<a name="kafka"></a>
# kafka
Class for work with testing Modules
<a name="kafka.Kafka"></a>
## Kafka Objects
```python
class Kafka(FMod)
```
Class for work with Kafka
<a name="kafka.Kafka.__init__"></a>
#### \_\_init\_\_
```python
| __init__(config, pathTmp, verbose)
```
Initialising object
Parameters
----------
config : dict
config of module
pathTmp : str
path to temporary files
verbose : bool
verbose output
<a name="kafka.Kafka.getConnect"></a>
#### getConnect
```python
| getConnect()
```
Connect to rabbitMQ
<a name="ftp"></a>
# ftp
Class for work with testing Modules
<a name="ftp.FTP"></a>
## FTP Objects
```python
class FTP(FMod)
```
Class for work with FTP
<a name="ftp.FTP.getConnect"></a>
#### getConnect
```python
| getConnect()
```
Connect to FTP
<a name="docker"></a>
# docker
Class for work with testing Modules
<a name="docker.Docker"></a>
## Docker Objects
```python
class Docker(FMod)
```
Class for load and build environment modules for functional tests
<a name="docker.Docker.__init__"></a>
#### \_\_init\_\_
```python
| __init__(config, pathTmp, verbose)
```
Initialising object
Parameters
----------
config : dict
config of module
pathTmp : str
path to temporary files
verbose : bool
verbose output
<a name="docker.Docker.build"></a>
#### build
```python
| build(rm=True)
```
Build docker container of module
Parameters
----------
moduleName : str
name of module
config : dictionary
configuration of module
<a name="docker.Docker.status"></a>
#### status
```python
| status()
```
Status docker container of module
<a name="docker.Docker.start"></a>
#### start
```python
| start()
```
Start docker container of module
<a name="docker.Docker.restart"></a>
#### restart
```python
| restart()
```
Start docker container of module
<a name="docker.Docker.stop"></a>
#### stop
```python
| stop()
```
Stop docker container of module
Parameters
----------
moduleName : str
name of module
<a name="docker.Docker.remove"></a>
#### remove
```python
| remove()
```
Remove docker container of module
<a name="docker.Docker.logs"></a>
#### logs
```python
| logs()
```
Output logs of docker container of module
<a name="docker.Docker.run"></a>
#### run
```python
| run(rm=True)
```
Run docker container of module
<a name="docker.Docker.statusWaiting"></a>
#### statusWaiting
```python
| statusWaiting(status, timeout=120)
```
Waiting docker container status
Parameters
----------
status : str
status
timeout : int
timeout in seconds
<a name="docker.Docker.copy"></a>
#### copy
```python
| copy(src, dstDir)
```
src shall be an absolute path
<a name="src"></a>
# src
<a name="src.fmods"></a>
# src.fmods
Class for work with testing Modules
<a name="src.fmods.FMods"></a>
## FMods Objects
```python
class FMods(object)
```
Class for load and build environment modules for functional tests
<a name="src.fmods.FMods.__init__"></a>
#### \_\_init\_\_
```python
| __init__(pathModules, pathTmp='', verbose=True)
```
Initialising object
Parameters
----------
pathModules : str
path to modules settings
pathTmp : str
path to temporary files
verbose : bool
verbose output
<a name="src.fmods.FMods.scan"></a>
#### scan
```python
| scan()
```
Scan subfolders for modules settings (path_modules)
<a name="src.fmods.FMods.printList"></a>
#### printList
```python
| printList()
```
Output the list of modules
<a name="src.fmods.FMods.count"></a>
#### count
```python
| count()
```
Count of modules
<a name="src.fmods.FMods.getConfig"></a>
#### getConfig
```python
| getConfig(moduleName)
```
Get configuration of module
Parameters
----------
moduleName : str
name of module
<a name="src.fmods.FMods.getTmpFolder"></a>
#### getTmpFolder
```python
| getTmpFolder(moduleName)
```
Get temporary path for module
Parameters
----------
moduleName : str
name of the module
Returns
-------
path:
temporary path for the module
<a name="src.fmods.FMods.startAll"></a>
#### startAll
```python
| startAll()
```
setUp for UTests
<a name="src.fmods.FMods.stopAll"></a>
#### stopAll
```python
| stopAll()
```
tearDown for UTests
<a name="src.fmod"></a>
# src.fmod
Class for work with testing Modules
<a name="src.fmod.FMod"></a>
## FMod Objects
```python
class FMod()
```
Class for environment module for functional tests
<a name="src.fmod.FMod.__init__"></a>
#### \_\_init\_\_
```python
| __init__(config, pathTmp, verbose)
```
Initialising object
Parameters
----------
config : dict
config of module
pathTmp : str
path to temporary files
verbose : bool
verbose output
<a name="src.fmod.FMod.isDocker"></a>
#### isDocker
```python
| isDocker()
```
Get parameters of module for docker
Returns
-------
ok
success
<a name="src.test"></a>
# src.test
<a name="src.test.mysql_test"></a>
# src.test.mysql\_test
<a name="src.test.docker_test"></a>
# src.test.docker\_test
<a name="src.test.kafka_test"></a>
# src.test.kafka\_test
<a name="src.test.http_test"></a>
# src.test.http\_test
<a name="src.test.minio_test"></a>
# src.test.minio\_test
<a name="src.test.fmods_test"></a>
# src.test.fmods\_test
<a name="src.test.rabbitmq_test"></a>
# src.test.rabbitmq\_test
<a name="src.test.git_test"></a>
# src.test.git\_test
<a name="src.test.postgre_test"></a>
# src.test.postgre\_test
<a name="src.test.ftp_test"></a>
# src.test.ftp\_test
<a name="src.minio"></a>
# src.minio
Class for work with testing Modules
<a name="src.minio.MinIO"></a>
## MinIO Objects
```python
class MinIO(FMod)
```
Class for work with Minio
<a name="src.minio.MinIO.__init__"></a>
#### \_\_init\_\_
```python
| __init__(config, pathTmp, verbose)
```
Initialising object
Parameters
----------
config : dict
config of module
pathTmp : str
path to temporary files
verbose : bool
verbose output
<a name="src.mysql"></a>
# src.mysql
Class for work with testing Modules
<a name="src.mysql.MySQL"></a>
## MySQL Objects
```python
class MySQL(FModDB)
```
Class for work with DB
<a name="src.mysql.MySQL.__init__"></a>
#### \_\_init\_\_
```python
| __init__(config, pathTmp, verbose)
```
Initialising object
Parameters
----------
config : dict
config of module
pathTmp : str
path to temporary files
verbose : bool
verbose output
<a name="src.git"></a>
# src.git
Class for work with testing Modules
<a name="src.git.GIT"></a>
## GIT Objects
```python
class GIT(FMod)
```
Class for load and build environment modules for functional tests
<a name="src.git.GIT.__init__"></a>
#### \_\_init\_\_
```python
| __init__(config, pathTmp, verbose)
```
Initialising object
Parameters
----------
config : dict
config of module
pathTmp : str
path to temporary files
verbose : bool
verbose output
<a name="src.git.GIT.clone"></a>
#### clone
```python
| clone()
```
Clone git repository
<a name="src.httpserver"></a>
# src.httpserver
Class for work with testing Modules
<a name="src.httpserver.HTTPSrv"></a>
## HTTPSrv Objects
```python
class HTTPSrv(FMod)
```
Class for work with HTTP (server)
<a name="src.httpserver.HTTPSrv.__init__"></a>
#### \_\_init\_\_
```python
| __init__(config, pathTmp, verbose)
```
Initialising object
Parameters
----------
config : dict
config of module
pathTmp : str
path to temporary files
verbose : bool
verbose output
<a name="src.migrate"></a>
# src.migrate
Class for work with testing Modules
<a name="src.migrate.Migrate"></a>
## Migrate Objects
```python
class Migrate(FMod)
```
Class for load and build environment modules for functional tests
<a name="src.migrate.Migrate.__init__"></a>
#### \_\_init\_\_
```python
| __init__(config, pathTmp, verbose)
```
Initialising object
Parameters
----------
config : dict
config of module
pathTmp : str
path to temporary files
verbose : bool
verbose output
<a name="src.migrate.Migrate.isMigrate"></a>
#### isMigrate
```python
| isMigrate()
```
Get parameters of module for Migrate
Returns
-------
ok
success
<a name="src.migrate.Migrate.run"></a>
#### run
```python
| run()
```
Migrate for Database container
<a name="src.fmod_db"></a>
# src.fmod\_db
Class for work with testing Modules
<a name="src.fmod_db.FModDB"></a>
## FModDB Objects
```python
class FModDB(FMod)
```
Class for environment module for functional tests
<a name="src.fmod_db.FModDB.__init__"></a>
#### \_\_init\_\_
```python
| __init__(config, pathTmp, verbose)
```
Initialising object
Parameters
----------
config : dict
config of module
pathTmp : str
path to temporary files
verbose : bool
verbose output
<a name="src.postgre"></a>
# src.postgre
Class for work with testing Modules
<a name="src.postgre.Postgre"></a>
## Postgre Objects
```python
class Postgre(FModDB)
```
Class for work with DB
<a name="src.postgre.Postgre.__init__"></a>
#### \_\_init\_\_
```python
| __init__(config, pathTmp, verbose)
```
Initialising object
Parameters
----------
config : dict
config of module
pathTmp : str
path to temporary files
verbose : bool
verbose output
<a name="src.http"></a>
# src.http
Class for work with testing Modules
<a name="src.http.HTTP"></a>
## HTTP Objects
```python
class HTTP(FMod)
```
Class for work with HTTP (client)
<a name="src.http.HTTP.__init__"></a>
#### \_\_init\_\_
```python
| __init__(config, pathTmp, verbose)
```
Initialising object
Parameters
----------
config : dict
config of module
pathTmp : str
path to temporary files
verbose : bool
verbose output
<a name="src.lfs"></a>
# src.lfs
Class for work with testing Modules
<a name="src.lfs.LFS"></a>
## LFS Objects
```python
class LFS(object)
```
Class for load and build environment modules for functional tests
<a name="src.lfs.LFS.rm"></a>
#### rm
```python
| @staticmethod
| rm(pathName)
```
remove folders
<a name="src.rabbitmq"></a>
# src.rabbitmq
Class for work with testing Modules
<a name="src.rabbitmq.RabbitMQ"></a>
## RabbitMQ Objects
```python
class RabbitMQ(FMod)
```
Class for work with RabbitMQ
<a name="src.rabbitmq.RabbitMQ.__init__"></a>
#### \_\_init\_\_
```python
| __init__(config, pathTmp, verbose)
```
Initialising object
Parameters
----------
config : dict
config of module
pathTmp : str
path to temporary files
verbose : bool
verbose output
<a name="src.rabbitmq.RabbitMQ.getConnect"></a>
#### getConnect
```python
| getConnect()
```
Connect to rabbitMQ
<a name="src.kafka"></a>
# src.kafka
Class for work with testing Modules
<a name="src.kafka.Kafka"></a>
## Kafka Objects
```python
class Kafka(FMod)
```
Class for work with Kafka
<a name="src.kafka.Kafka.__init__"></a>
#### \_\_init\_\_
```python
| __init__(config, pathTmp, verbose)
```
Initialising object
Parameters
----------
config : dict
config of module
pathTmp : str
path to temporary files
verbose : bool
verbose output
<a name="src.kafka.Kafka.getConnect"></a>
#### getConnect
```python
| getConnect()
```
Connect to rabbitMQ
<a name="src.ftp"></a>
# src.ftp
Class for work with testing Modules
<a name="src.ftp.FTP"></a>
## FTP Objects
```python
class FTP(FMod)
```
Class for work with FTP
<a name="src.ftp.FTP.getConnect"></a>
#### getConnect
```python
| getConnect()
```
Connect to FTP
<a name="src.docker"></a>
# src.docker
Class for work with testing Modules
<a name="src.docker.Docker"></a>
## Docker Objects
```python
class Docker(FMod)
```
Class for load and build environment modules for functional tests
<a name="src.docker.Docker.__init__"></a>
#### \_\_init\_\_
```python
| __init__(config, pathTmp, verbose)
```
Initialising object
Parameters
----------
config : dict
config of module
pathTmp : str
path to temporary files
verbose : bool
verbose output
<a name="src.docker.Docker.build"></a>
#### build
```python
| build(rm=True)
```
Build docker container of module
Parameters
----------
moduleName : str
name of module
config : dictionary
configuration of module
<a name="src.docker.Docker.status"></a>
#### status
```python
| status()
```
Status docker container of module
<a name="src.docker.Docker.start"></a>
#### start
```python
| start()
```
Start docker container of module
<a name="src.docker.Docker.restart"></a>
#### restart
```python
| restart()
```
Start docker container of module
<a name="src.docker.Docker.stop"></a>
#### stop
```python
| stop()
```
Stop docker container of module
Parameters
----------
moduleName : str
name of module
<a name="src.docker.Docker.remove"></a>
#### remove
```python
| remove()
```
Remove docker container of module
<a name="src.docker.Docker.logs"></a>
#### logs
```python
| logs()
```
Output logs of docker container of module
<a name="src.docker.Docker.run"></a>
#### run
```python
| run(rm=True)
```
Run docker container of module
<a name="src.docker.Docker.statusWaiting"></a>
#### statusWaiting
```python
| statusWaiting(status, timeout=120)
```
Waiting docker container status
Parameters
----------
status : str
status
timeout : int
timeout in seconds
<a name="src.docker.Docker.copy"></a>
#### copy
```python
| copy(src, dstDir)
```
src shall be an absolute path
| 16.151899 | 65 | 0.654506 | eng_Latn | 0.311823 |
9870b5ff262fc9c85a897faa24e856ea09c46178 | 45 | md | Markdown | README.md | maphstay/Code-Wars | 0023eba08cbaf02b1ca86b22d7b877fdfb6d46da | [
"MIT"
] | null | null | null | README.md | maphstay/Code-Wars | 0023eba08cbaf02b1ca86b22d7b877fdfb6d46da | [
"MIT"
] | null | null | null | README.md | maphstay/Code-Wars | 0023eba08cbaf02b1ca86b22d7b877fdfb6d46da | [
"MIT"
] | null | null | null | # Code Wars
Soluções de tasks em JavaScript
| 15 | 32 | 0.777778 | por_Latn | 0.998337 |
98721a7f4c3b4953b3463cbecff16a8dd4d598a7 | 150 | md | Markdown | README.md | allGhostAnon/wifi-hacker-advanced | 332148c9e498a4b0769899f17676929b2fdc6254 | [
"MIT"
] | 2 | 2022-01-04T22:52:55.000Z | 2022-01-04T22:52:57.000Z | README.md | ElectronSz/wifi-hacker-advanced | 332148c9e498a4b0769899f17676929b2fdc6254 | [
"MIT"
] | null | null | null | README.md | ElectronSz/wifi-hacker-advanced | 332148c9e498a4b0769899f17676929b2fdc6254 | [
"MIT"
] | 2 | 2018-12-06T07:06:52.000Z | 2020-02-25T01:36:42.000Z | # wifi-hacker-advanced
Using your Linux OS, now you can run this script on your terminal, and hack wifi anywhere. Simple and very fast, 100% working.
| 50 | 126 | 0.773333 | eng_Latn | 0.998914 |
98721f0230d43e756b5ca447a6e3e8375a651afe | 12 | md | Markdown | README.md | bixbite2/08.06.2018 | d1302f4ca6934cc08d24b5b64b641e45750eb91f | [
"MIT"
] | null | null | null | README.md | bixbite2/08.06.2018 | d1302f4ca6934cc08d24b5b64b641e45750eb91f | [
"MIT"
] | null | null | null | README.md | bixbite2/08.06.2018 | d1302f4ca6934cc08d24b5b64b641e45750eb91f | [
"MIT"
] | null | null | null | # 08.06.2018 | 12 | 12 | 0.666667 | deu_Latn | 0.197821 |
987238b06910fd4b3fe25d226990a0e5b9797416 | 585 | md | Markdown | docs/pages/03-配置菜单/08-配置全屏功能.md | wangeditor-team/wangeditor-usage-doc | d4fae52349b41f9e122cc86b108c307b45333a9f | [
"MIT"
] | 2 | 2020-10-10T03:42:18.000Z | 2021-06-21T09:21:33.000Z | docs/pages/03-配置菜单/08-配置全屏功能.md | wangeditor-team/wangeditor-usage-doc | d4fae52349b41f9e122cc86b108c307b45333a9f | [
"MIT"
] | 7 | 2020-08-25T03:30:33.000Z | 2021-05-14T11:58:00.000Z | docs/pages/03-配置菜单/08-配置全屏功能.md | wangeditor-team/wangeditor-usage-doc | d4fae52349b41f9e122cc86b108c307b45333a9f | [
"MIT"
] | 3 | 2021-01-27T06:26:04.000Z | 2021-12-01T09:18:25.000Z | # 配置全屏功能
## 配置属性
编辑器创建之前, 可以使用 `editor.config.showFullScreen = true` 来展示全屏功能按钮, 默认是true, 就是不加这个属性默认展示全屏功能按钮
注意：[工具栏和编辑器区域分离](../01-开始使用/05-一个页面多个编辑器.html)的时候不支持全屏功能
```html
<div id="div1">
<p>欢迎使用 wangEditor 编辑器</p>
</div>
<!-- 引入 wangEditor.min.js -->
<script type="text/javascript">
const E = window.wangEditor
const editor = new E('#div1')
// 配置全屏功能按钮是否展示
editor.config.showFullScreen = true
editor.create()
</script>
```
## 使用API
我们也提供了API供用户使用（同样不支持工具栏和编辑区域分离的情况）：
```javascript
editor.fullScreen() // 全屏
editor.unFullScreen() // 取消全屏
``` | 17.727273 | 90 | 0.671795 | yue_Hant | 0.588384 |
987467e74cf414a4913a5c5838a7a50786f83c0c | 3,215 | md | Markdown | docs/dotnet/how-to-enumerate-data-types-in-assemblies-using-reflection-cpp-cli.md | kyser/cpp-docs.ru-ru | 085e0717cfcd00870d62803aed74a2d641034138 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/dotnet/how-to-enumerate-data-types-in-assemblies-using-reflection-cpp-cli.md | kyser/cpp-docs.ru-ru | 085e0717cfcd00870d62803aed74a2d641034138 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/dotnet/how-to-enumerate-data-types-in-assemblies-using-reflection-cpp-cli.md | kyser/cpp-docs.ru-ru | 085e0717cfcd00870d62803aed74a2d641034138 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: 'Как: перечисление типов данных с помощью отражения (C + +/ CLI) | Документы Microsoft'
ms.custom: ''
ms.date: 11/04/2016
ms.technology:
- cpp-cli
ms.topic: conceptual
dev_langs:
- C++
helpviewer_keywords:
- assemblies [C++], enumerating data types in
- public types [C++]
- reflection [C++], external assemblies
- assemblies [C++]
- data types [C++], enumerating
- public members [C++]
ms.assetid: c3578e6d-bb99-4599-80e1-ab795305f878
author: mikeblome
ms.author: mblome
ms.workload:
- cplusplus
- dotnet
ms.openlocfilehash: 5a4b85cb5af9d390d92bcca3e0462b0ae5b4d832
ms.sourcegitcommit: 76b7653ae443a2b8eb1186b789f8503609d6453e
ms.translationtype: MT
ms.contentlocale: ru-RU
ms.lasthandoff: 05/04/2018
---
# <a name="how-to-enumerate-data-types-in-assemblies-using-reflection-ccli"></a>Практическое руководство. Перечисление типов данных в сборках с помощью отражения (C++/CLI)
В следующем коде показано перечисление открытых типов и членов с помощью <xref:System.Reflection>.
Заданному имени сборки, в локальном каталоге или в глобальном кэше СБОРОК, в приведенном ниже коде пытается открыть ее и извлечь описания. В случае успешного выполнения каждого типа отображается с открытым членам.
Обратите внимание, что <xref:System.Reflection.Assembly.Load%2A?displayProperty=fullName> требует использования без расширения файла. Таким образом используя «mscorlib.dll» в качестве аргумента командной строки завершится ошибкой, пока с помощью просто «mscorlib» будет выведен из типов .NET Framework. Если имя сборки не указано, код обнаружит и о типах, имеющихся в текущей сборке (EXE-файл из данного кода).
## <a name="example"></a>Пример
```
// self_reflection.cpp
// compile with: /clr
using namespace System;
using namespace System::Reflection;
using namespace System::Collections;
public ref class ExampleType {
public:
ExampleType() {}
void Func() {}
};
int main() {
String^ delimStr = " ";
array<Char>^ delimiter = delimStr->ToCharArray( );
array<String^>^ args = Environment::CommandLine->Split( delimiter );
// replace "self_reflection.exe" with an assembly from either the local
// directory or the GAC
Assembly^ a = Assembly::LoadFrom("self_reflection.exe");
Console::WriteLine(a);
int count = 0;
array<Type^>^ types = a->GetTypes();
IEnumerator^ typeIter = types->GetEnumerator();
while ( typeIter->MoveNext() ) {
Type^ t = dynamic_cast<Type^>(typeIter->Current);
Console::WriteLine(" {0}", t->ToString());
array<MemberInfo^>^ members = t->GetMembers();
IEnumerator^ memberIter = members->GetEnumerator();
while ( memberIter->MoveNext() ) {
MemberInfo^ mi = dynamic_cast<MemberInfo^>(memberIter->Current);
Console::Write(" {0}", mi->ToString( ) );
if (mi->MemberType == MemberTypes::Constructor)
Console::Write(" (constructor)");
Console::WriteLine();
}
count++;
}
Console::WriteLine("{0} types found", count);
}
```
## <a name="see-also"></a>См. также
[Отражение (C++/CLI)](../dotnet/reflection-cpp-cli.md) | 37.383721 | 413 | 0.682426 | kor_Hang | 0.175901 |