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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
2fcb9ee9e3d7a3ed0fa7b3517a0c1b89d687313d | 366 | md | Markdown | README.md | perezm27/mc-exercise | 93f3e8cf30adfcd58d41077973625f71906cb48d | [
"MIT"
] | null | null | null | README.md | perezm27/mc-exercise | 93f3e8cf30adfcd58d41077973625f71906cb48d | [
"MIT"
] | null | null | null | README.md | perezm27/mc-exercise | 93f3e8cf30adfcd58d41077973625f71906cb48d | [
"MIT"
] | null | null | null | # mc-exercise
Lab15a
Don't push to master. Pull from master often.
Try to work on a local branch, and handle merges locally before you send it off to github.
The biggest take away to prevent these conflicts is 1. pull from master before starting any work. Pull from master often and having open communication with your team as to which features you're working on. | 45.75 | 205 | 0.789617 | eng_Latn | 0.999977 |
2fcbb3e874e19f5524072d0850851e3058530f9d | 6,661 | md | Markdown | wiki/customization.md | yangtao-manoo/metrics-from-alibaba | 1fc2ae13533e215bcff2ba2ac8a1565a40cc3cd8 | [
"Apache-2.0"
] | null | null | null | wiki/customization.md | yangtao-manoo/metrics-from-alibaba | 1fc2ae13533e215bcff2ba2ac8a1565a40cc3cd8 | [
"Apache-2.0"
] | null | null | null | wiki/customization.md | yangtao-manoo/metrics-from-alibaba | 1fc2ae13533e215bcff2ba2ac8a1565a40cc3cd8 | [
"Apache-2.0"
] | null | null | null | 自定义你的metrics配置
===
Metrics支持以下几种方式进行配置：
* 通过-D参数直接配置。
* 通过`metrics-conf.properties`文件进行配置。里面是`key=value`的形式，所有可选的配置项参见下表，如果没有指定，则会采用默认值。然后在应用的启动参数中加入`-Dcom.alibaba.metrics.config_file=/path/to/metrics-conf.properties`参数。
| 配置名 | 默认值 | 说明 |
| ---------------------------------------- | ------- | -------------------- |
| com.alibaba.metrics.jvm.compilation.enable | true | 是否收集jvm编译时间指标 |
| com.alibaba.metrics.jvm.compilation.level | TRIVIAL | jvm编译指标收集级别 |
| com.alibaba.metrics.druid.enable | true | 是否收集Druid指标 |
| com.alibaba.metrics.druid.level | TRIVIAL | druid指标收集级别 |
| com.alibaba.metrics.druid.MaxSqlSize | 250 | druid指标收集的最大sql条数 |
| com.alibaba.metrics.cleaner.enable | true | 是否开启metrics自动清理功能 |
| com.alibaba.metrics.cleaner.keep_interval | 86400 | 指标保存的最长时间，单位为秒，如超过时间没有更新，会被自动清理掉 |
| com.alibaba.metrics.cleaner.delay | 3600 | 自动清理线程的清理间隔，单位为秒 |
| com.alibaba.metrics.reporter.file.schedule | 5 | metrics.log线程调度间隔，单位秒 |
| com.alibaba.metrics.reporter.bin.schedule | 5 |二进制落盘线程调度间隔，单位秒 |
| com.alibaba.metrics.log.path | ~ | 日志输出路径，如果配置/aaa/bbb/，就会输出在/aaa/bbb/logs/metrics下面 |
| com.alibaba.metrics.reporter.file.enable | true | 是否开启metrics.log日志落盘 |
| com.alibaba.metrics.reporter.file.schedule | 5 | metrics.log线程调度间隔，单位秒 |
| com.alibaba.metrics.reporter.bin.enable | true | 是否开启二进制落盘 |
| com.alibaba.metrics.reporter.bin.schedule | 5 |二进制落盘线程调度间隔，单位秒 |
| com.alibaba.metrics.system.cpu.enable | true | 是否打开系统cpu的metrics统计 |
| com.alibaba.metrics.system.cpu.level | MAJOR | 默认的cpu统计级别 |
| com.alibaba.metrics.system.load.enable | true | 是否打开系统load的metrics统计 |
| com.alibaba.metrics.system.load.level | MAJOR | 默认的load统计级别 |
| com.alibaba.metrics.system.net.enable | true | 是否打开系统网络的metrics统计 |
| com.alibaba.metrics.system.net.level | TRIVIAL | 默认的网络统计级别 |
| com.alibaba.metrics.system.memory.enable | true | 是否打开系统内存的metrics统计 |
| com.alibaba.metrics.system.memory.level | TRIVIAL | 默认的内存统计级别 |
| com.alibaba.metrics.system.tcp.enable | true | 是否打开系统tcp的metrics统计 |
| com.alibaba.metrics.system.tcp.level | TRIVIAL | 默认的tcp统计级别 |
| com.alibaba.metrics.system.disk.enable | true | 是否打开系统磁盘的metrics统计 |
| com.alibaba.metrics.system.disk.level | TRIVIAL | 默认的磁盘统计级别 |
| com.alibaba.metrics.jvm.mem.enable | true | 是否打开jvm内存统计 |
| com.alibaba.metrics.jvm.mem.level | NORMAL | 默认的jvm内存统计级别 |
| com.alibaba.metrics.jvm.gc.enable | true | 是否打开jvm gc统计 |
| com.alibaba.metrics.jvm.gc.level | NORMAL | 默认的jvm gc统计级别 |
| com.alibaba.metrics.jvm.class_load.enable | true | 是否打开jvm类加载统计 |
| com.alibaba.metrics.jvm.class_load.level | NORMAL | 默认的jvm类加载统计级别 |
| com.alibaba.metrics.jvm.buffer_pool.enable | true | 是否打开jvm 堆外内存统计 |
| com.alibaba.metrics.jvm.buffer_pool.level | NORMAL | 默认的jvm堆外内存统计级别 |
| com.alibaba.metrics.jvm.file_desc.enable | true | 是否打开jvm文件句柄统计 |
| com.alibaba.metrics.jvm.file_desc.level | NORMAL | 默认的jvm文件句柄统计级别 |
| com.alibaba.metrics.jvm.thread_state.enable | true | 是否打开jvm线程状态统计 |
| com.alibaba.metrics.jvm.thread_state.level | TRIVIAL | 默认的jvm线程状态统计级别 |
| com.alibaba.metrics.tomcat.http.enable | true | 是否打开tomcat http统计 |
| com.alibaba.metrics.tomcat.http.level | MAJOR | 默认的tomcat http统计级别 |
| com.alibaba.metrics.tomcat.thread.enable | true | 是否打开tomcat 线程池统计 |
| com.alibaba.metrics.tomcat.thread.level | NORMAL | 默认的tomcat 线程池统计级别 |
| com.alibaba.metrics.nginx.enable | true | 是否打开nginx统计 |
| com.alibaba.metrics.nginx.level | MAJOR | 默认的nginx统计级别 |
例如，要禁用metrics.log的输出，可以配置为如下方式
```
➜ cat metrics-conf.properties
com.alibaba.metrics.reporter.file.enable=false
```
### 其他系统参数
以下参数可以通过-D参数进行配置
| 配置名 | 默认值 | 说明 |
| ---------------------------------------- | ------- | -------------------- |
| com.alibaba.metrics.maxMetricCountPerRegistry | 5000 | 每个group保存的指标数，超过将不会被统计 |
| com.alibaba.metrics.maxSubCategoryCount | 20 | FastCompass中统计子类别的个数 |
| com.alibaba.metrics.numberOfBucket | 10 | BucketCounter中保留的最近N个统计间隔数 |
| com.alibaba.metrics.maxCompassErrorCodeCount | 100 | Compass中保留的错误码个数 |
| com.alibaba.metrics.maxCompassAddonCount | 10 | Compass中保留的扩展个数 |
| com.alibaba.metrics.collector.maxCollectNumber | 10000 | Collector一次收集中收集的metrics上限 |
### url统计收敛
有时候当统计url的时候如果url不规范，很容易造成维度发散，从而是的统计内存急剧膨胀。为了避免这些问题，引入了url统计收敛的规则，将发散的维度收敛到同一个指标进行统计。
| 配置名 | 默认值 | 说明 |
| ---------------------------------------- | ------- | -------------------- |
| com.alibaba.metrics.host.consolidation | null | host收敛规则 |
| com.alibaba.metrics.path.consolidation | null | url收敛规则 |
规则为\*,\*,$的形式，$代表url按分隔符切分后，这一段作为一个统计维度；*表示这一段收敛掉。
#### host地址收敛例子
输入为
```
"puma.a.com",
"alingphone.b.com",
"shop.b.com",
"nongfushanquan.a.com",
"kinder.a.com",
"converse.a.com",
"lining.a.com",
"nelly.b.com",
"nelly.ax.b.com"
```
收敛规则为
```
com.alibaba.metrics.host.consolidation=*,$,$
```
输出为
```
*.a.com
*.b.com
*.b.com
*.a.com
*.a.com
*.a.com
*.a.com
*.b.com
*.ax.b.com
```
#### path收敛例子
输入为
```
"http://bds.ecb.a.com/play/u/2579369938/p/2/e/6/t/1/50077092567.mp4",
"http://bds.ecb.a.com/",
"http://bds.ecb.a.com/cross.xml",
"http://acs.m.a.com/gw/query/2.0/",
"http://bds.ecb.a.com/xxxx/yyyy/zzzz",
"http://localhost:8080/waterMark.do",
"http://localhost_8080/home/assets/fonts/ODelI1.woff2home",
"http://localhost:80/registry/machine"
```
收敛规则为
```
com.alibaba.metrics.path.consolidation=$,$,*
```
输出为
```
/play/u/*/*
/cross.xml/*
/gw/query/*/*
/xxxx/yyyy/*/*
/waterMark.do/*
/home/assets/*/*
/registry/machine/*
```
### 验证你的配置
#### HTTP方式
```sh
$curl -i http://localhost:8006/metrics/specific?metric=system.cpu.user
HTTP/1.1 200 OK
Access-control-allow-headers: X-Requested-With, Content-Type, X-Codingpedia
Date: Thu, 01 Dec 2016 05:53:16 GMT
Access-control-allow-methods: GET
Content-type: application/json
Access-control-allow-origin: *
Content-length: 528
{"data":[{"metric":"system.cpu.user","metricType":"GAUGE","tags":{},"timestamp":1480571596480,"value":0}],"success":true,"message":"","timestamp":1480571596480}
```
#### 日志方式
```sh
$tail -f ~/logs/metrics/metrics.log | grep system.cpu.user
{"metric":"system.cpu.user","metricType":"GAUGE","tags":{},"timestamp":1480571701453,"value":0}
```
| 38.062857 | 166 | 0.642096 | yue_Hant | 0.234796 |
2fcc1468f6410361ecdf6b64e09589a9cc6a3c4a | 97 | md | Markdown | README.md | mablejohn/Android-String-Parser | 0b5b7f29cf287548d261f6c80b2fd4ebec663782 | [
"Apache-2.0"
] | null | null | null | README.md | mablejohn/Android-String-Parser | 0b5b7f29cf287548d261f6c80b2fd4ebec663782 | [
"Apache-2.0"
] | null | null | null | README.md | mablejohn/Android-String-Parser | 0b5b7f29cf287548d261f6c80b2fd4ebec663782 | [
"Apache-2.0"
] | null | null | null | # Android-String-Parser
A small IntelliJ plugin which helps to export and import Android strings
| 32.333333 | 72 | 0.824742 | eng_Latn | 0.928266 |
2fcc37939367fbb3a1a640c864b339bb2bc8f786 | 638 | md | Markdown | Section 7-1 to 7-5.md | codecason/NLP_Notes | 55038df9658bd3f952242a6494a431ca54f82679 | [
"MIT"
] | 1 | 2017-07-22T13:45:05.000Z | 2017-07-22T13:45:05.000Z | Section 7-1 to 7-5.md | codecason/NLP_Notes | 55038df9658bd3f952242a6494a431ca54f82679 | [
"MIT"
] | null | null | null | Section 7-1 to 7-5.md | codecason/NLP_Notes | 55038df9658bd3f952242a6494a431ca54f82679 | [
"MIT"
] | null | null | null | ### 7.1 What is sentiment analysis？
Movie：is this review positive or negative?
Mood:diffuse non-caused low-intensity long-duration ....
Attitudes:
### 7.2 Sentiment Analysis_A baseline algorithm
sentiment情感
### 7.3 Sentiment Lexicons
http://sentiwordnet.isti.cnr.it/
7.4 Semi-supervised learning of lexicons
1. 词性分析 identifying word polarity
（好像要手动标记，是半监督的）
2. Turney Algorithm
3. 极性的度量：
互概率及一些算法，互信息
synonyms and antonyms
度量的结果貌似是单维的？
### 7.4 Sentiment Lexicons
Other sentiment of a sentence.
### 7.5 Other Sentiment Tasks
sentiment
penalize SVM,classifier, regression tasks to do phrases sentiment detection
方法
| 23.62963 | 77 | 0.758621 | eng_Latn | 0.625494 |
2fcd573a3be21e96f27868d5d04aad03a12cd971 | 7,013 | md | Markdown | articles/active-directory/cloud-sync/reference-cloud-sync-faq.md | Microsoft/azure-docs.sv-se | a43cb26da920952026f5e9c8720f3356a84de75b | [
"CC-BY-4.0",
"MIT"
] | 7 | 2017-08-28T08:02:11.000Z | 2021-05-05T07:47:55.000Z | articles/active-directory/cloud-sync/reference-cloud-sync-faq.md | MicrosoftDocs/azure-docs.sv-se | a43cb26da920952026f5e9c8720f3356a84de75b | [
"CC-BY-4.0",
"MIT"
] | 476 | 2017-10-15T08:20:18.000Z | 2021-04-16T05:20:11.000Z | articles/active-directory/cloud-sync/reference-cloud-sync-faq.md | MicrosoftDocs/azure-docs.sv-se | a43cb26da920952026f5e9c8720f3356a84de75b | [
"CC-BY-4.0",
"MIT"
] | 39 | 2017-08-03T09:46:48.000Z | 2021-11-05T11:41:27.000Z | ---
title: Vanliga frågor och svar om Azure AD Connect Cloud Sync
description: Det här dokumentet beskriver vanliga frågor och svar om moln synkronisering.
services: active-directory
author: billmath
manager: daveba
ms.service: active-directory
ms.workload: identity
ms.topic: reference
ms.date: 06/25/2020
ms.subservice: hybrid
ms.author: billmath
ms.collection: M365-identity-device-management
ms.openlocfilehash: 39d1554fd1b6cac1a90a794cfd93def97e494bfe
ms.sourcegitcommit: f28ebb95ae9aaaff3f87d8388a09b41e0b3445b5
ms.translationtype: MT
ms.contentlocale: sv-SE
ms.lasthandoff: 03/29/2021
ms.locfileid: "98614021"
---
# <a name="azure-active-directory-connect-cloud-sync-faq"></a>Vanliga frågor och svar om Azure Active Directory Connect Cloud Sync
Läs om vanliga frågor och svar för Azure Active Directory (Azure AD) Connect-molnbaserad synkronisering.
## <a name="general-installation"></a>Allmän installation
**F: hur ofta körs Cloud Sync?**
Moln etablering är schemalagt att köras var 2: e minut. Var 2: e minut, kommer alla användare, grupp-och lösen ords-hash-ändringar att tillhandahållas till Azure AD.
**F: se synkroniseringsfel vid synkronisering av lösen ord vid första körningen. Varför?**
Detta är förväntat. Felen beror på att användarobjektet inte finns i Azure AD. När användaren har allokerats till Azure AD bör hash-värden för lösen ord tillhandahållas i den efterföljande körningen. Vänta på några körningar och bekräfta att det inte längre finns några fel i lösen ordets hash-synkronisering.
**F: Vad händer om Active Directory-instansen har attribut som inte stöds av molnbaserad synkronisering (till exempel katalog tillägg)?**
Moln etablering kommer att köras och etablera de attribut som stöds. Attribut som inte stöds är inte etablerade i Azure AD. Granska katalog tilläggen i Active Directory och se till att du inte behöver de attributen för att flöda till Azure AD. Om det krävs ett eller flera attribut kan du överväga att använda Azure AD Connect synkronisera eller flytta nödvändig information till ett av de attribut som stöds (t. ex. tilläggets attribut 1-15).
**F: Vad är skillnaden mellan Azure AD Connect synkronisering och moln synkronisering?**
Med Azure AD Connect Sync körs etableringen på den lokala Sync-servern. Konfigurationen lagras på den lokala Sync-servern. Med Azure AD Connect Cloud Sync lagras etablerings konfigurationen i molnet och körs i molnet som en del av Azure AD Provisioning-tjänsten.
**F: kan jag använda molnbaserad synkronisering för att synkronisera från flera Active Directory skogar?**
Ja. Moln etablering kan användas för att synkronisera från flera Active Directory skogar. I miljöer med flera skogar måste alla referenser (t. ex. hanteraren) finnas i domänen.
**F: Hur uppdateras agenten?**
Agenterna uppgraderas automatiskt av Microsoft. För IT-teamet minskar detta belastningen på att testa och validera nya agent versioner.
**F: kan jag inaktivera automatisk uppgradering?**
Det finns inget stöd för att inaktivera automatisk uppgradering.
**F: kan jag ändra käll fäst punkten för molnbaserad synkronisering?**
Som standard använder Cloud Sync ms-DS-konsekvens-GUID med en återställning till ObjectGUID som käll ankare. Det finns inget stöd för att ändra käll ankare.
**F: Jag ser nya tjänst huvud namn med AD-domännamnen när de använder Cloud Sync. Förväntas det?**
Ja, Cloud Sync skapar ett tjänst huvud namn för etablerings konfigurationen med domän namnet som tjänstens huvud namn. Gör inga ändringar i tjänstens huvud konfiguration.
**F: Vad händer när en synkroniserad användare krävs för att ändra lösen ord vid nästa inloggning?**
Om lösen ordets hash-synkronisering är aktiverat i Cloud Sync och den synkroniserade användaren krävs för att ändra lösen ord vid nästa inloggning i den lokala AD-miljön, etablerar inte Cloud Sync "to-changed"-lösen ordet hash till Azure AD. När användaren har ändrat lösen ordet, tillhandahålls hashen för användarens lösen ord från AD till Azure AD.
**F: har Cloud Sync stöd för tillbakaskrivning av ms-DS-consistencyGUID för alla objekt?**
Nej, Cloud Sync stöder inte tillbakaskrivning av ms-DS-consistencyGUID för alla objekt (inklusive användar objekt).
**F: Jag konfigurerar användare med hjälp av molnbaserad synkronisering. Jag har tagit bort konfigurationen. Varför ser jag fortfarande de gamla synkroniserade objekten i Azure AD?**
När du tar bort konfigurationen tar Cloud Sync inte bort de synkroniserade objekten automatiskt i Azure AD. Se till att du inte har de gamla objekten genom att ändra omfånget för konfigurationen till en tom grupp eller organisationsenheter. När etableringen körs och rensar objekten inaktiverar du och tar bort konfigurationen.
**F: Vad betyder det att Exchange hybrid inte stöds?**
Funktionen Exchange hybrid distribution möjliggör samtidig användning av Exchange-postlådor både lokalt och i Microsoft 365. Azure AD Connect synkroniserar en specifik uppsättning attribut från Azure AD tillbaka till din lokala katalog. Moln Provisioning-agenten synkroniserar för närvarande inte de här attributen i din lokala katalog och stöds därför inte som en ersättning för Azure AD Connect.
**F: kan jag installera moln etablerings agenten på Windows Server Core?**
Nej, det finns inte stöd för att installera agenten på Server Core.
**F: kan jag använda en uppsamlings server med moln etablerings agenten?**
Nej, det finns inte stöd för mellanlagrings servrar.
**F: kan jag synkronisera gäst användar konton?**
Nej, det finns inte stöd för synkronisering av gäst användar konton.
**F: om jag flyttar en användare från en ORGANISATIONSENHET som är begränsad till en ORGANISATIONSENHET som är begränsad till Azure AD Connect, vad händer?**
Användaren kommer att tas bort och skapas på nytt. Att flytta en användare från en ORGANISATIONSENHET som är begränsad till moln synkronisering visas som en borttagnings åtgärd. Om användaren flyttas till en ORGANISATIONSENHET som hanteras av Azure AD Connect, etableras den om till Azure AD och en ny användare som skapats.
**F: om jag byter namn på eller flyttar ORGANISATIONSENHETen som ligger inom omfånget för Cloud Sync-filtret, vad händer med användaren som skapades i Azure AD?**
Ingenstans. Användarna tas inte bort om ORGANISATIONSENHETen har bytt namn eller flyttats.
**F: stöder Azure AD Connect Cloud Sync stora grupper?**
Ja. Idag stöder vi upp till 50 000 grupp medlemmar som synkroniseras med hjälp av omfångs filtrering av ORGANISATIONSENHETer. När du använder grupp omfångs filtrering rekommenderar vi att du behåller grupp storleken till färre än 1500 medlemmar samtidigt. Orsaken till detta är att även om du kan synkronisera en stor grupp som en del av grupp omfångs filtret, kommer delta-synkroniseringen att Miss förväntas när du lägger till medlemmar i gruppen efter batchar som är större än 1500.
## <a name="next-steps"></a>Nästa steg
- [Vad är etablering?](what-is-provisioning.md)
- [Vad är Azure AD Connect Cloud Sync?](what-is-cloud-sync.md)
| 65.542056 | 486 | 0.805504 | swe_Latn | 0.99998 |
2fcdc8d7a9c31be1d8d90cde4ea0f1a44f283ef4 | 382 | md | Markdown | README.md | sovisrushain/Client_side_form_validation | 641899a9912c31f743619785973d03f961ad622e | [
"MIT"
] | null | null | null | README.md | sovisrushain/Client_side_form_validation | 641899a9912c31f743619785973d03f961ad622e | [
"MIT"
] | null | null | null | README.md | sovisrushain/Client_side_form_validation | 641899a9912c31f743619785973d03f961ad622e | [
"MIT"
] | null | null | null | # CLIENT SIDE FORM VALIDATION
## Usage
1. Clone the repository
`git clone https://github.com/sovisrushain/Client_Side_Form_Validation.git`
2. Open it in IntelliJ IDEA OR a preferred IDE
3. Install all the dependencies
`npm install`
4. Set all the file watchers
5. You are all set.
## LICENSE
Distributed under the MIT License. See [LICENSE](LICENSE) for more information. | 17.363636 | 79 | 0.759162 | eng_Latn | 0.414816 |
2fce939ccbec345da439816d35ce5cfeebf35de3 | 1,682 | md | Markdown | README.md | sneiderV/hosting-with-firebase | a6ff0d62b51b21f27a4bb33c8f444aca825a52df | [
"MIT"
] | 2 | 2018-12-29T17:06:12.000Z | 2018-12-30T01:55:49.000Z | README.md | sneiderV/hosting-with-firebase | a6ff0d62b51b21f27a4bb33c8f444aca825a52df | [
"MIT"
] | null | null | null | README.md | sneiderV/hosting-with-firebase | a6ff0d62b51b21f27a4bb33c8f444aca825a52df | [
"MIT"
] | null | null | null | # Hosting with firebase
Con este tutorial podra desplegar una aplicación react usando Firebase.
Para iniciar debe instalar las herramientas CLI que provee Firebase
> npm install -g firebase-tools
Luego de la instalación debe hacer la autenticación con su cuenta Gmail
> firebase login
Al finalizar la autenticación debe ir a la raiz de su proyecto mediante la terminal de comandos CMD e iniciar un proyecto de Firebase
> firebase init
Cuando inicialice el proyecto saldrán algunas opciones a seleccionar, la primera debe ser acepatada
> Are you ready to proceed? YES
Luego saldran nuevas opciones y debe seleccionar unicamente la de Hosting
> (*) Hosting: Configure and deploy Firebase Hosting sites
(crear un proyecto en el dashboard de Firebase para que aparezca el proyecto en la siguiente pregunta)
> ? Select a default Firebase project for this directoy:
Aquí debe seleccionar el proyecto que creo en Firebase
Cuando crea un proyecto de React se crea un directorio llamado Public y la siguiente pregunta define el directorio publico a usar, por esta razón se debe dejar por defecto este directorio
Al finalizar esta configuración se crean dos nuevos ficheros:
> firebase.json
> .firebaserc (Aquí se almacena la configuración que se usa para el despliegue de la aplicación)
Finalmente usamos el siguiente comando para hacer el despliegue
> firebase deploy
Si no aparece la aplicación en la dirección de Hosting intente correr el siguiente comando antes de hacer un nuevo deploy
> npm run build
y en directorio firebase.json en la propiedad "public": "public" cambiar por "public": "build"
y de nuevo correr el comando:
> firebase deploy
| 36.565217 | 187 | 0.791914 | spa_Latn | 0.994021 |
2fcef7976b70a464a710cb3284c71179133a34ee | 866 | md | Markdown | README.md | mukicherry/farboxTemplate | 4283a0f661f9c817f1490e118270b74bb8ac4993 | [
"MIT"
] | 1 | 2017-01-11T15:33:52.000Z | 2017-01-11T15:33:52.000Z | README.md | mukicherry/farboxTemplate | 4283a0f661f9c817f1490e118270b74bb8ac4993 | [
"MIT"
] | null | null | null | README.md | mukicherry/farboxTemplate | 4283a0f661f9c817f1490e118270b74bb8ac4993 | [
"MIT"
] | null | null | null | # NexT For Farbox
A hexo theme [NexT](https://github.com/iissnan/hexo-theme-next) for Farbox.
##Discription
> 个人很喜欢的一款主题，同时又偏爱Farbox的便捷，鱼和熊掌不可兼得，因此自己动手移植了这款主题。
[在线预览 Preview](http://www.sunnyyoung.net)
##Screenshot
主题集成了NexT原有的三种样式，具体设置可到Farbox的设置页面修改
抛弃`.yml`文件手动配置，采用可视化编辑配置
##Usage
- 自动方式: 打开[http://www.sunnyyoung.net/template](http://www.sunnyyoung.net/template)，填写克隆模板的目标站点，点击克隆
- 手动方式: Clone此项目并重命名为Template，拖动到Farbox站点目录下
##Notes
- **由于Farbox的模版引擎和Hexo有区别，部分Hexo的样式或功能暂时无法实现，持续更新**
- 本主题没有进行严谨的测试，如果有问题请反馈
- 欢迎提意见
##Todo
- [x] Auto toc display
- [ ] Local Search
- [ ] Customize code highlight theme
- [ ] Customize farbox comment style
##License
The [MIT License](LICENSE). | 22.205128 | 99 | 0.752887 | yue_Hant | 0.743584 |
2fcf4e8c726c35db1e5b775e47914c4a50c0ce65 | 2,751 | md | Markdown | README.md | chrislinan/oss_exporter | 551eeda0e695943a58f9cdeef282ed51a11c892b | [
"Apache-2.0"
] | null | null | null | README.md | chrislinan/oss_exporter | 551eeda0e695943a58f9cdeef282ed51a11c892b | [
"Apache-2.0"
] | null | null | null | README.md | chrislinan/oss_exporter | 551eeda0e695943a58f9cdeef282ed51a11c892b | [
"Apache-2.0"
] | null | null | null | # AliCloud OSS Exporter
## This repo is forked from ribbybibby/s3_exporter and I made some changes so that this tool can be used in Alibaba Cloud.
This exporter provides metrics for OSS bucket objects by querying the API with a given bucket and prefix and constructing metrics based on the returned objects.
I find it useful for ensuring that backup jobs and batch uploads are functioning by comparing the growth in size/number of objects over time, or comparing the last modified date to an expected value.
## Building
```
make
```
## Running
Before runing this tool you need to set these environment variables: `OSS_ACCESS_KEY_ID`, `OSS_ACCESS_KEY_SECRET`,`OSS_BUCKET` and `OSS_ENDPOINT`
```
./oss_exporter <flags>
```
You can query a bucket and prefix combination by supplying them as parameters to /probe:
```
curl localhost:9340/probe?bucket=some-bucket&prefix=some-folder/some-file.txt
```
## Flags
./oss_exporter --help
* __`--web.listen-address`:__ The port (default ":9340").
* __`--web.metrics-path`:__ The path metrics are exposed under (default "/metrics")
* __`--web.probe-path`:__ The path the probe endpoint is exposed under (default "/probe")
* __`--version` :__ Show application version.
## Metrics
| Metric | Meaning | Labels |
| ------ | ------- | ------ |
| oss_biggest_object_size_bytes | The size of the largest object. | bucket, prefix |
| oss_last_modified_object_date | The modification date of the most recently modified object. | bucket, prefix |
| oss_last_modified_object_size_bytes | The size of the object that was modified most recently. | bucket, prefix |
| oss_list_success | Did the ListObjects operation complete successfully? | bucket, prefix |
| oss_objects_size_sum_bytes | The sum of the size of all the objects. | bucket, prefix |
| oss_objects_total | The total number of objects. | bucket, prefix |
## Prometheus
### Configuration
You should pass the params to a single instance of the exporter using relabelling, like so:
```yml
scrape_configs:
- job_name: 'oss'
metrics_path: /probe
static_configs:
- targets:
- bucket=stuff;prefix=thing.txt;
- bucket=other-stuff;prefix=another-thing.gif;
relabel_configs:
- source_labels: [__address__]
regex: '^bucket=(.*);prefix=(.*);$'
replacement: '${1}'
target_label: '__param_bucket'
- source_labels: [__address__]
regex: '^bucket=(.*);prefix=(.*);$'
replacement: '${2}'
target_label: '__param_prefix'
- target_label: __address__
replacement: 127.0.0.1:9340 # oss exporter.
```
### Example Queries
Return series where the last modified object date is more than 24 hours ago:
```
(time() - s3_last_modified_object_date) / 3600 > 24
```
| 38.208333 | 199 | 0.712468 | eng_Latn | 0.969959 |
2fcfbb37817593351597c915593f86a56b41d3f6 | 3,879 | md | Markdown | microsoft-365/enterprise/contoso-identity.md | AdrianaDJ/microsoft-365-docs-pr.ja-JP | 5c999d65b275dcbd1aeed1eca5df7252df80e704 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-10-18T03:33:56.000Z | 2021-10-18T03:33:56.000Z | microsoft-365/enterprise/contoso-identity.md | AdrianaDJ/microsoft-365-docs-pr.ja-JP | 5c999d65b275dcbd1aeed1eca5df7252df80e704 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | microsoft-365/enterprise/contoso-identity.md | AdrianaDJ/microsoft-365-docs-pr.ja-JP | 5c999d65b275dcbd1aeed1eca5df7252df80e704 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Contoso 社の ID
author: JoeDavies-MSFT
f1.keywords:
- NOCSH
ms.author: josephd
manager: laurawi
audience: ITPro
ms.topic: article
ms.service: o365-solutions
localization_priority: Normal
ms.collection:
- M365-identity-device-management
- Strat_O365_Enterprise
ms.custom: ''
description: Contoso 社で、IDaaS (Identity as a Service) を活用して、従業員向けのクラウド ベース認証や、パートナーと顧客向けのフェデレーション認証を提供している方法を説明します。
ms.openlocfilehash: dea0f53ef1c3fdc2ea32256303c6120c614c904d
ms.sourcegitcommit: 66b8fc1d8ba4f17487cd2004ac19cf2fff472f3d
ms.translationtype: MT
ms.contentlocale: ja-JP
ms.lasthandoff: 10/24/2020
ms.locfileid: "48754643"
---
# <a name="identity-for-the-contoso-corporation"></a>Contoso 社の ID
Microsoft は、Azure Active Directory (Azure AD) を通じて、クラウド製品全体で Id (IDaaS) をサービスとして提供します。 企業向けの Microsoft 365 を採用するために、Contoso IDaaS ソリューションは社内 id プロバイダーを使用し、信頼できる既存のサードパーティ id プロバイダーとのフェデレーション認証を含める必要がありました。
## <a name="the-contoso-active-directory-domain-services-forest"></a>Contoso Active Directory ドメインサービスフォレスト
Contoso 社では \. 、世界の地域ごとに1つずつ、7つのサブドメインを持つ contoso com に対して1つの Active Directory ドメインサービス (AD DS) フォレストを使用しています。 本社、地域ハブ オフィス、サテライト オフィスには、ローカルの認証と承認のためのドメイン コントローラーが含まれています。
地域ハブを含む世界のさまざまな部分については、地域ドメインを含む Contoso フォレストを参照してください。
Contoso 社は、 \. Microsoft 365 のワークロードおよびサービスの認証と承認のために、contoso com フォレスト内のアカウントとグループを使用することを決定しました。
## <a name="the-contoso-federated-authentication-infrastructure"></a>Contoso 社のフェデレーション認証インフラストラクチャ
Contoso 社では次のことが可能です。
- お客様は、Microsoft、Facebook、または Google のメールアカウントを使用して、会社のパブリック web サイトにサインインします。
- ベンダーおよびパートナーは、自分の LinkedIn、Salesforce、または Google のメールアカウントを使用して、会社のパートナーエクストラネットにサインインします。
ここでは、パブリック web サイト、パートナーエクストラネット、および Active Directory フェデレーションサービス (AD FS) サーバーのセットを含む Contoso DMZ を示します。DMZ は、顧客、パートナー、インターネットサービスを含むインターネットに接続されています。
DMZ の AD FS サーバーは、パブリック web サイトにアクセスし、パートナーエクストラネットにアクセスするためのパートナー資格情報を提供するために、id プロバイダーによる顧客資格情報の認証を容易にします。
Contoso 社は、このインフラストラクチャを維持し、顧客とパートナーの認証に専念することを決定しました。Contoso 社の id 設計者は、このインフラストラクチャから Azure AD [B2B](https://docs.microsoft.com/azure/active-directory/b2b/hybrid-organizations) および [B2C](https://docs.microsoft.com/azure/active-directory-b2c/solution-articles) ソリューションへの変換について調査しています。
## <a name="hybrid-identity-with-password-hash-synchronization-for-cloud-based-authentication"></a>クラウドベース認証のためのパスワードハッシュ同期によるハイブリッドID
Contoso 社は、オンプレミスの AD DS フォレストを使用して、Microsoft 365 cloud resources への認証を希望しています。 パスワードハッシュ同期 (PHS) の使用を決定しました。
PHS は、オンプレミスの AD DS フォレストを、Microsoft 365 for enterprise サブスクリプションの Azure AD テナントと同期し、ユーザーアカウントとグループアカウント、およびハッシュされたバージョンのユーザーアカウントパスワードをコピーします。
ディレクトリ同期を実行するために、Contoso 社では、パリデータセンター内のサーバーに Azure AD Connect ツールを展開しました。
Azure ad Connect を実行しているサーバーは、変更については Contoso AD DS フォレストをポーリングしてから、それらの変更を Azure AD テナントと同期します。
## <a name="conditional-access-policies-for-identity-and-device-access"></a>ID およびデバイス アクセスの条件付きアクセス ポリシー
Contosoは、3 つの保護レベルに対して Azure AD と Intune の[条件付きアクセス ポリシー](identity-access-policies.md)セットを作成しました。
- *ベースライン* の保護は、すべてのユーザーアカウントに適用されます。
- *重要* な保護は、シニアリーダーシップおよび経営スタッフに適用されます。
- *高度* な規制による保護は、厳しく規制されたデータにアクセスできる財務、法律、研究部門の特定のユーザーに適用されます。
Contoso identity とデバイスの条件付きアクセスポリシーの結果セットを次に示します。
## <a name="next-step"></a>次の手順
Contoso 社が Microsoft エンドポイント構成マネージャーインフラストラクチャを使用して、組織全体に [現在の Windows 10 Enterprise を展開し、維持](contoso-win10.md) する方法について説明します。
## <a name="see-also"></a>関連項目
[Microsoft 365 の ID ロードマップ](identity-roadmap-microsoft-365.md)
[Microsoft 365 for enterprise の概要](microsoft-365-overview.md)
[テスト ラボ ガイド](m365-enterprise-test-lab-guides.md)
| 44.079545 | 285 | 0.82315 | yue_Hant | 0.811428 |
2fd01405a3b355befe677913b0aba9122513c1c0 | 4,023 | md | Markdown | README.md | dharple/gravatar | 80f8c6978a9d162e4ef8ad460e3fbfdb1d2dcd68 | [
"MIT"
] | 1 | 2021-04-01T13:43:33.000Z | 2021-04-01T13:43:33.000Z | README.md | fleetmanapp/gravatar | 93e443d450fd73652fe688d8d3d89e3eb064603c | [
"MIT"
] | 1 | 2020-12-04T20:44:13.000Z | 2020-12-04T20:44:13.000Z | README.md | fleetmanapp/gravatar | 93e443d450fd73652fe688d8d3d89e3eb064603c | [
"MIT"
] | null | null | null | # Gravatar
[](https://github.com/gravatarphp/gravatar/releases)
[](LICENSE)
[](https://travis-ci.org/gravatarphp/gravatar)
[](https://scrutinizer-ci.com/g/gravatarphp/gravatar)
[](https://scrutinizer-ci.com/g/gravatarphp/gravatar)
[](https://packagist.org/packages/gravatarphp/gravatar)
**Gravatar URL builder which is most commonly called as a Gravatar library.**
## Install
Via Composer
``` bash
$ composer require gravatarphp/gravatar
```
## Usage
Create a `Gravatar` instance and use it for creating URLs.
``` php
use Gravatar\Gravatar;
// Defaults: no default parameter, use HTTPS
$gravatar = new Gravatar([], true);
// Returns https://secure.gravatar.com/avatar/EMAIL_HASH
$gravatar->avatar('user@domain.com');
// Returns https://secure.gravatar.com/avatar/EMAIL_HASH
// The fourth parameter enables validation and will prevent the
// size parameter from being added to the URL generated.
$gravatar->avatar('user@domain.com', ['s' => 9001], true, true);
// Returns https://secure.gravatar.com/EMAIL_HASH
$gravatar->profile('user@domain.com');
// Returns https://secure.gravatar.com/EMAIL_HASH.vcf
$gravatar->vcard('user@domain.com');
// Returns https://secure.gravatar.com/EMAIL_HASH.qr
$gravatar->qrCode('user@domain.com');
```
You can override the globally used protocol (HTTP, HTTPS) by setting the last parameter to true/false.
``` php
use Gravatar\Gravatar;
$gravatar = new Gravatar();
// Returns http://www.gravatar.com/avatar/EMAIL_HASH
$gravatar->avatar('user@domain.com', [], false);
// Returns http://www.gravatar.com/EMAIL_HASH
$gravatar->profile('user@domain.com', false);
// Returns http://www.gravatar.com/EMAIL_HASH.vcf
$gravatar->vcard('user@domain.com', false);
// Returns http://www.gravatar.com/EMAIL_HASH.qr
$gravatar->qrCode('user@domain.com', false);
```
Last, but not least, you can pass default options to the builder and use them to generate avatar URLs.
``` php
use Gravatar\Gravatar;
$gravatar = new Gravatar([
'size' => 500,
]);
// Returns https://secure.gravatar.com/avatar/EMAIL_HASH?size=500&r=g
$gravatar->avatar('user@domain.com', ['r' => 'g']);
```
## Parameters
If you pass any of the following parameters and turn validation on (fourth parameter in the `avatar()` method), their values will be checked against the allowed values defined in the [Gravatar documentation](http://gravatar.com/site/implement/):
* `s`, `size` -- The image size
* `d`, `default` -- The default image to display if there is no matching Gravatar
* `f`, `forcedefault` -- Tell Gravatar to use the default image even if there is a matching Gravatar
* `r`, `rating` -- The audience rating (`G`, `R`, etc.) to restrict the Gravatar to
If the value fails validation, an `InvalidArgumentException` will be thrown.
Any parameters not listed above are not sanitized or validated in anyway.
## Notes
Profile, vCard and QR Code requests will only work with the primary email address. This is a limitation of Gravatar. However the builder won't complain, since it doesn't know if it is your primary address or not. For more tips and details check the [Gravatar documentation](http://gravatar.com/site/implement/).
## Testing
``` bash
$ composer test
```
## Credits
- [Márk Sági-Kazár](https://github.com/sagikazarmark)
- [All Contributors](https://github.com/gravatarphp/gravatar/contributors)
## License
The MIT License (MIT). Please see [License File](LICENSE) for more information.
| 34.09322 | 311 | 0.742232 | eng_Latn | 0.524164 |
2fd0741af064d0b766a9a21c0faf4d9f8507a355 | 1,216 | md | Markdown | chapters/17/17-23.md | Raymain1944/CPPLv1 | 96e5fd5347a336870fc868206ebfe44f88ce69eb | [
"Apache-2.0"
] | null | null | null | chapters/17/17-23.md | Raymain1944/CPPLv1 | 96e5fd5347a336870fc868206ebfe44f88ce69eb | [
"Apache-2.0"
] | null | null | null | chapters/17/17-23.md | Raymain1944/CPPLv1 | 96e5fd5347a336870fc868206ebfe44f88ce69eb | [
"Apache-2.0"
] | null | null | null | ```c++
#include <iostream>
using std::cin; using std::cout; using std::endl; using std::cerr;
#include <string>
using std::string;
#include <regex>
using std::regex; using std::regex_search; using std::smatch;
using std::sregex_iterator;
bool valid(const smatch &m){
if (m[0].matched){ //如果整个模式都匹配
return 1;
} else if (m[1].matched){ //如果前5位数字匹配
return !(m[2].matched && m[3].matched); //则不应出现-以及后面的数字
} else {
return 0;
}
}
int main() {
try {
string phone =
"((\\d{5})([-])?(\\d{4})?)";
regex r(phone); //regex对象，用于查找我们的模式
smatch m;
string s;
cout << "Please type the zipcode: \n";
//从输入文件中读取每条记录
while (getline(cin, s)){
//对每个匹配的电话号码
for (sregex_iterator it(s.begin(), s.end(), r), end_it; it != end_it; ++it){
//检查号码的格式是否合法
if (valid(*it))
cout << "valid: " << it->str() << endl;
else
cout << "not valid: " << it->str() << endl;
}
}
} catch (std::regex_error e){
cout << e.what() << "\ncode: " << e.code() << endl;
}
}
```
| 27.022222 | 88 | 0.471217 | eng_Latn | 0.520355 |
2fd1dd95790a1e7114fe9fc52f77b5f5e34a9851 | 139 | md | Markdown | CHANGELOG.md | phoihos/vsce-util | 5b32a86c3d8ed4eb04a6faff7831ceea2f8c06b3 | [
"MIT"
] | null | null | null | CHANGELOG.md | phoihos/vsce-util | 5b32a86c3d8ed4eb04a6faff7831ceea2f8c06b3 | [
"MIT"
] | null | null | null | CHANGELOG.md | phoihos/vsce-util | 5b32a86c3d8ed4eb04a6faff7831ceea2f8c06b3 | [
"MIT"
] | null | null | null | # Change Log
All notable changes to the "@phoihos/vsce-util" will be documented in this file.
## [0.0.1] - 2021-07-12
- Initial release
| 17.375 | 80 | 0.697842 | eng_Latn | 0.984027 |
2fd21a13a59d2d137c975a9dded5785e6c18ec13 | 2,232 | md | Markdown | Electronics101/VoltageReference/LT1019/README.md | SteveAmor/LittleArduinoProjects | 19644961a87f3ae2e73159c2e69dfe07fe2335bf | [
"MIT"
] | null | null | null | Electronics101/VoltageReference/LT1019/README.md | SteveAmor/LittleArduinoProjects | 19644961a87f3ae2e73159c2e69dfe07fe2335bf | [
"MIT"
] | null | null | null | Electronics101/VoltageReference/LT1019/README.md | SteveAmor/LittleArduinoProjects | 19644961a87f3ae2e73159c2e69dfe07fe2335bf | [
"MIT"
] | null | null | null | # #374 VoltageReference/LT1019
Exploring the LT1019 precision reference, tested with an Arduino as an external voltage reference.
## Notes
The Linear Technology LT1019 precision reference is available in four voltages: 2.5V, 4.5V, 5V and 10V.
I am using a 2.5V LT1019-2.5 in a DIP8 package.
### Stabilising the Reference Output
The datasheet recommends for the best transient load response to add a bypass RC filter on the output:
* 2-5Ω + 2µF tantalum
Although my test setup is not really prone to such transient issues, I've added the bypass but with 2x10Ω resistors in parallel and a 2.2µF electrolytic.
As expected, the voltage reference performs just fine, expecially within the 10-bit resolution of of the ATmega328.
### Test Circuit
In this example, the LT1019 is used to provide a 2.5V reference for an Arduino (AREF).
This requires the external reference to be enabled `analogReference(EXTERNAL)`
A voltage divider comprising a 10kΩ pot in series with a 10kΩ resistor across the 5V supply provides a test input with a range of roughly 0 to 2.5V.
This test signal is read on the Ardunio A0 analog input.
Since AREF is enabled (`analogReference(EXTERNAL)`), analog readings are all with respect the the 2.5V reference voltage.
A Nokia 5110 display provides a realtime reading of the analog input and the derived voltage reading.
### Code
The [LT1019.ino](./LT1019.ino) sketch drives the demo.
It uses the [Adafruit-PCD8544 Library](https://github.com/adafruit/Adafruit-PCD8544-Nokia-5110-LCD-library)
to drive the 5110 display with hardware [SPI](https://www.arduino.cc/en/Reference/SPI).
## Construction
## Credits and References
* [LT1019 info and datasheet](http://www.linear.com/product/LT1019)
* [analogReference()](https://www.arduino.cc/reference/en/language/functions/analog-io/analogreference/)
* [Adafruit-PCD8544 Library](https://github.com/adafruit/Adafruit-PCD8544-Nokia-5110-LCD-library) - GitHub
* [..as mentioned on my blog](https://blog.tardate.com/2018/01/leap374-lt1019-voltage-reference.html)
| 41.333333 | 153 | 0.774642 | eng_Latn | 0.919865 |
2fd2a29b478071a77bd5d8ef9217dba5ce0d435e | 865 | md | Markdown | setup.md | JoshuaDull/Text-Recognition-Introduction | c33abcdf1a90280ecd432250d6d6378ff12b5dd4 | [
"CC-BY-4.0"
] | 1 | 2020-02-18T02:09:30.000Z | 2020-02-18T02:09:30.000Z | setup.md | JoshuaDull/Text-Recognition-Introduction | c33abcdf1a90280ecd432250d6d6378ff12b5dd4 | [
"CC-BY-4.0"
] | null | null | null | setup.md | JoshuaDull/Text-Recognition-Introduction | c33abcdf1a90280ecd432250d6d6378ff12b5dd4 | [
"CC-BY-4.0"
] | null | null | null | ---
layout: page
title: Setup
root: .
---
## Getting ready
>For this workshop, we will use two software: Adobe Acrobat and ABBYY FineReader 14.
> Adobe Acrobat is available to all current Yale students, faculty, and staff through Adobe Creative Cloud; downloadable via [Yale's Software Library](https://software.yale.edu/).
> ABBYY FineReader is installed on select desktop machines across YUL, including 8 machines in the DHLab. Yale does not provide individual copies of ABBYY FineReader, but anyone can download a 30-Day free trial from [ABBYY](https://www.abbyy.com/en-us/lp/finereader15-download-free-trial/?source=abbyy.com_en-us_shopping).
#### Downloading the data
There is one sample data set:
1. [Sample PDFs](). Clicking on the link will take you to a Box folder. Please download the folder titled 'Samples'.
[template]: {{ site.workshop_repo }}
| 43.25 | 322 | 0.760694 | eng_Latn | 0.973469 |
2fd2a78a3d9c8d3ee44bc651f703187f2961e776 | 385 | md | Markdown | README.md | Magesu/nokia-game-jam | 0417b64117b8d3b5f1aa061a2ab9a78058bce31a | [
"Apache-2.0"
] | 1 | 2022-02-06T20:43:50.000Z | 2022-02-06T20:43:50.000Z | README.md | Magesu/nokia-game-jam | 0417b64117b8d3b5f1aa061a2ab9a78058bce31a | [
"Apache-2.0"
] | null | null | null | README.md | Magesu/nokia-game-jam | 0417b64117b8d3b5f1aa061a2ab9a78058bce31a | [
"Apache-2.0"
] | null | null | null | # nokia3310-jam-godot-starter
A Godot starter project for the nokia3310 game jam
Use this project to get a kick start for the Nokia 3310 Jam on itch.io!
[Link to the Jam](https://itch.io/jam/nokiajam2)
Everything inside the Game.tscn scene will be rendered with two colors from the official palette while also applying an ordered dithering shader.
 | 38.5 | 147 | 0.781818 | eng_Latn | 0.991828 |
2fd2b244ae7996716d83551014c5ed7924d75370 | 131 | md | Markdown | 404.md | itspriddle/recipes.priddle.xyz | 4a1a455ae1e4c691fccadcc06f1b43e41510d401 | [
"MIT"
] | 2 | 2020-10-06T15:21:29.000Z | 2021-10-01T09:49:11.000Z | 404.md | itspriddle/recipes.priddle.xyz | 4a1a455ae1e4c691fccadcc06f1b43e41510d401 | [
"MIT"
] | null | null | null | 404.md | itspriddle/recipes.priddle.xyz | 4a1a455ae1e4c691fccadcc06f1b43e41510d401 | [
"MIT"
] | null | null | null | ---
layout: default
title: 404 Not Found
permalink: /404.html
---
### 404 Not Found
That page doesn't exist. [Go Home →](/)
| 13.1 | 44 | 0.648855 | eng_Latn | 0.658177 |
2fd35a2dfc2a96ce68c03abab458781c29e469d8 | 2,433 | md | Markdown | README.md | rafael-torraca/tictactoe-flutter | 18d15eeb3b409022d410fecd7d51545acc0720c6 | [
"MIT"
] | null | null | null | README.md | rafael-torraca/tictactoe-flutter | 18d15eeb3b409022d410fecd7d51545acc0720c6 | [
"MIT"
] | null | null | null | README.md | rafael-torraca/tictactoe-flutter | 18d15eeb3b409022d410fecd7d51545acc0720c6 | [
"MIT"
] | 3 | 2020-10-06T14:23:07.000Z | 2020-10-16T16:12:18.000Z | # tic-tac-toe-flutter
Starting a project in flutter! 😁
This application was developed by Professor Kleber,
from Fatec Americana, and will be used to assess Flutter skills.
## Getting Started
Just clone the project and run it on your device, and you'll play the classic tic-tac-toe.
## Desafio da Aula
- [x] Exibir o jogador da vez (Turno do X ou Turno do O); Pode usar um Text para isso.
- [x] Criar um placar de vitórias para cada jogador; Pode usar Text também
- [x] Criar uma splash screen para o aplicativo; Utilize o [plugin custom_splash](https://pub.dev/packages/custom_splash).
- [x] Adicionar um botão para compartilhar o aplicativo. Utilize o [plugin Share](https://pub.dev/packages/share).
- [x] Trocar o X e O por duas imagens (exemplo: Finn e Jake de Adventure Time) — como [utilizar imagens](https://flutter.dev/docs/development/ui/assets-and-images). Entendendo como colocar [imagens em um Container](https://medium.com/flutteropen/flutter-widgets-03-image-558e2b24059e).
## Bonus
- [x] Timer para o bot jogar;
## Issues Detected
- [ ] Quando jogando contra o computador, devido ao timer colocado, é possível marcar para o computador;
## MIT License
Copyright (c) 2020 Rafael Torraca
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.
| 46.788462 | 285 | 0.776819 | kor_Hang | 0.306206 |
2fd3661d5eb5baf81d54e64d9cb857b5a37f4b89 | 7,464 | md | Markdown | README.md | ottopecz/talentcomposer | 82e590d78479d1a272dd479951435b72482b5aa0 | [
"MIT"
] | 4 | 2017-01-20T12:31:25.000Z | 2017-04-02T21:09:59.000Z | README.md | ottopecz/talentcomposer | 82e590d78479d1a272dd479951435b72482b5aa0 | [
"MIT"
] | 8 | 2019-01-08T19:12:41.000Z | 2021-06-11T02:35:52.000Z | README.md | ottopecz/talentcomposer | 82e590d78479d1a272dd479951435b72482b5aa0 | [
"MIT"
] | null | null | null | [](https://travis-ci.org/ottopecz/talentcomposer)[](https://coveralls.io/github/ottopecz/talentcomposer?branch=master)[](https://david-dm.org/ottopecz/talentcomposer#info=dependencies) [](https://david-dm.org/ottopecz/talentcomposer#info=devDependencies)
[](https://www.npmjs.com/package/talentcomposer/)
# talentcomposer
The **talentcomposer** is a tool which can compose pieces of capabilities (talents) with each other and also talents with an instance. This tool can help you to do [role oriented programming](https://en.wikipedia.org/wiki/Role-oriented_programming). The implementation is based on the [publication](http://scg.unibe.ch/archive/papers/Ress12eTalentsSPE.pdf) of the Software Composition Group part of the Institute of Computer Science (INF) at the University of Bern
##Supported engines
node v8 and v10
## Notes
1. The package [mainliner](https://www.npmjs.com/package/mainliner) utilizes this package.
1. Conflict resolution between talents is explicit. The programmer has to resolve conflicts using either the alias or the exclude method. See below in the examples
2. Conflict resolution between an instance and talents is implicit. The member will delegated on to the instance blindly. If there is already a member on the instance with same name it's gonna be shadowed or overridden.
3. Although the publication allows stateful talents I would **NOT** not recommend to use them with this tool. Like **DON'T** do this (It's leaking anyway)
```javascript
const Composer = require("talentcomposer");
let x = 0;
module.export = Composer.createTalent({
method() {
x += 1;
return x;
}
});
```
## Examples
### Composing an instance with talents
```javascript
const assert = require("assert");
const Composer = require("talentcomposer");
class Person {
constructor(name) {
this.name = name;
}
eating() {}
sleeping() {}
}
const studentTalent = Composer.createTalent({
studying() {}
});
const teacherTalent = Composer.createTalent({
teaching() {}
});
const sportTalent = Composer.createTalent({
swimming() {}
});
let travis = new Person("Travis");
let mavis = new Person("Mavis");
travis = Composer.composeWithTalents(travis, studentTalent, sportTalent);
mavis = Composer.composeWithTalents(mavis, teacherTalent, sportTalent);
assert.ok(travis.studying);
assert.ok(travis.swimming);
assert.ok(mavis.teaching);
assert.ok(mavis.swimming);
```
### Composing talents
```javascript
const assert = require("assert");
const Composer = require("talentcomposer");
const circusTalent = Composer.createTalent({
juggling() {},
clowning() {}
});
const sportTalent = Composer.createTalent({
running() {},
swimming() {}
});
combinedTalents = Composer.composeTalents(circusTalent, sportTalent);
assert.ok(combinedTalents.juggling);
assert.deepEqual(combinedTalents.juggling, circusTalent.juggling);
assert.ok(combinedTalents.clowning);
assert.deepEqual(combinedTalents.clowning, circusTalent.clowning);
assert.ok(combinedTalents.running);
assert.deepEqual(combinedTalents.running, sportTalent.running);
assert.ok(combinedTalents.swimming);
assert.deepEqual(combinedTalents.swimming, sportTalent.swimming);
```
### Require an unimplemented capability
```javascript
const assert = require("assert");
const Composer = require("talentcomposer");
class Person {
constructor(name) {
this.name = name;
}
eating() {}
sleeping() {}
}
const courierTalent = Composer.createTalent({
"cycling": Composer.required,
delivering() {
this.cycling();
}
});
const sportTalent = Composer.createTalent({
cycling() {}
});
let travis = new Person("Travis");
travis = Composer.composeWithTalents(travis, courierTalent, sportTalent);
assert.ok(travis.cycling);
assert.deepEqual(travis.cycling, sportTalent.cycling);
assert.ok(travis.delivering);
assert.deepEqual(travis.delivering, courierTalent.delivering);
```
### Require an unimplemented capability on the prototype of a class
```javascript
const assert = require("assert");
const Composer = require("talentcomposer");
class Person {
constructor(name) {
this.name = name;
}
get drawing() {
return Composer.required;
}
eating() {}
sleeping() {}
}
const artTalent = Composer.createTalent({
drawing() {}
});
let travis = new Person("Travis");
travis = Composer.composeWithTalents(travis, artTalent);
assert.ok(travis.drawing);
assert.deepEqual(travis.drawing, artTalent.drawing);
```
### Require an unimplemented capability in the constructor of a class
```javascript
const assert = require("assert");
const Composer = require("talentcomposer");
class Person {
constructor(name) {
this.name = name;
this.painting = Composer.required;
}
eating() {}
sleeping() {}
}
const artTalent = Composer.createTalent({
painting() {}
});
let travis = new Person("Travis");
travis = Composer.composeWithTalents(travis, artTalent);
assert.ok(travis.painting);
assert.deepEqual(travis.painting, artTalent.painting);
```
### Explicit conflict resolution (aliasing)
```javascript
const assert = require("assert");
const Composer = require("talentcomposer");
const courierTalent = Composer.createTalent({
cycling() {console.log("like a courier");}
});
const sportTalent = Composer.createTalent({
cycling() {console.log("like an athlete");}
});
combinedTalents = Composer.composeTalents(
courierTalent,
Composer.alias(sportTalent, "cycling", "riding")
);
assert.ok(combinedTalents.cycling);
assert.deepEqual(combinedTalents.cycling, courierTalent.cycling);
assert.ok(combinedTalents.riding);
assert.deepEqual(combinedTalents.riding, sportTalent.cycling);
```
### Explicit conflict resolution (excluding)
```javascript
const assert = require("assert");
const Composer = require("talentcomposer");
const courierTalent = Composer.createTalent({
cycling() {console.log("like a courier");},
delivering() {}
});
const sportTalent = Composer.createTalent({
cycling() {console.log("like a athlete");},
swimming() {}
});
combinedTalents = Composer.composeTalents(
courierTalent,
Composer.exclude(sportTalent, "cycling")
);
assert.ok(combinedTalents.cycling);
assert.deepEqual(combinedTalents.cycling, courierTalent.cycling);
assert.ok(combinedTalents.cycling);
assert.deepEqual(combinedTalents.cycling, courierTalent.cycling);
assert.ok(combinedTalents.delivering);
assert.deepEqual(combinedTalents.delivering, courierTalent.delivering);
```
## API
### createTalent(record: Object): Talent
Creates a new talent
### composeWithTalents(instance: Object, ...talents: Talent[]): Object
Composes talents with an instantiated object
### composeTalents(...talents: Talent[]): Talent
Composes talents into one
### alias(talent: Talent, methodName: string, alias: string): Talent
Aliases a method of the talent
(It doesn't mutate the talent but returns a new one)
### exclude(talent: Talent, methodName: string): Talent
Excludes a method of the talent
(It doesn't mutate the talent but returns a new one)
### required: Symbol
Property to mark required members for talents
| 27.240876 | 596 | 0.746651 | eng_Latn | 0.630321 |
2fd3c031a97518750434ff7555cc027783c260b6 | 10,263 | md | Markdown | security-updates/WindowsUpdateServices/18142199.md | isabella232/security-updates.pt-pt | ae2788469787b369878796de773088fc732c8cb7 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-05-19T20:16:48.000Z | 2020-05-19T20:16:48.000Z | security-updates/WindowsUpdateServices/18142199.md | MicrosoftDocs/security-updates.pt-pt | 8e11060f4fad64cc80f0690484390c520f4fd10c | [
"CC-BY-4.0",
"MIT"
] | 11 | 2018-02-01T10:13:40.000Z | 2018-11-23T23:15:33.000Z | security-updates/WindowsUpdateServices/18142199.md | isabella232/security-updates.pt-pt | ae2788469787b369878796de773088fc732c8cb7 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2018-03-12T22:24:26.000Z | 2021-11-18T13:15:16.000Z | ---
TOCTitle: About Updates
Title: About Updates
ms:assetid: '7cac1534-54ee-4afc-bf41-45afea2c9ac1'
ms:contentKeyID: 18142199
ms:mtpsurl: 'https://technet.microsoft.com/pt-pt/library/Cc708465(v=WS.10)'
author: SharonSears
ms.author: SharonSears
---
About Updates
=============
On this Web page you will find information about updates in the context of Windows Server Update Services (WSUS).
What Is an Update?
------------------
An update provides replacement files for software that is installed on a computer. Every update that is available on Microsoft Update is composed of two components.
- *Metadata* provides information about the update. For example, metadata supplies information for the properties of an update, including what product and platform to which the update is applicable, whether it is a new or revised update, and what languages you want to download. Metadata also includes Microsoft Software License Terms. The metadata package downloaded for an update is typically much smaller than the actual update file package.
- *Update files* are the actual update binary files installed on a computer.
When updates are synchronized to your WSUS server, the metadata and update files are stored in two separate locations. Metadata is stored in the WSUS database. Update files can be stored either on your WSUS server or on Microsoft Update servers, depending on how you have configured content storage options through the WSUS console.
For more information about your options for storing updates with WSUS, see [Deploying Microsoft Windows Server Update Services](http://go.microsoft.com/fwlink/?linkid=41777).
Update Products and Classifications
-----------------------------------
Updates are made available by product. For each product, updates are differentiated by classification.
- A *product* is a specific edition of an operating system or application (for example Windows Server 2003, Datacenter Edition). A product family is the base operating system or application from which the products are derived. An example of a product family is Microsoft Windows, of which Windows Server 2003, Datacenter Edition, is a member.
- The update *classification* represents the type of update. For any given product or product family, updates could be available among multiple classifications (for example, Windows XP family critical updates and security updates). For definitions of update classifications, see [Description of the standard terminology that is used to describe Microsoft software updates](http://support.microsoft.com/?kbid=824684).
| .gif)Nota |
|-----------------------------------------------------------------------|
| WSUS only supports updating products by computer, not by user. |
Updates Available by Product
----------------------------
- For information about products currently supported by WSUS as well as classifications available and known issues for updates of each product, see [Products Supported by WSUS](https://technet.microsoft.com/5e222485-6218-483a-adfe-25480e93483b).
How WSUS Works with Microsoft Update
------------------------------------
If you are using WSUS, you configure synchronization options—for example, products, update classifications, and languages—through the WSUS console, and do not go directly to Microsoft Update. WSUS connects directly to Microsoft Update to get both the update metadata and the update files as specified by the content storage options you configure through the WSUS console.
You manage all synchronized updates on the WSUS console. The Update News section on the [Windows Server Update Services page](http://go.microsoft.com/fwlink/?linkid=41171) on TechNet provides links to a list of Windows and non-Windows updates to make it easier for you to see recently published new, revised, or rereleased updates. This can help you determine which updates to include in your WSUS update synchronizations.
Update Revisions and Update Rereleases
--------------------------------------
An update *revision* is a version of an update that contains changes since it was last published. For example, the change might be an updated EULA, UI text, applicability rules for computers, modified language support, or changes to the actual update files.
If you configure your WSUS server to automatically approve new revisions of an update, you will ensure that the latest version of a previously approved update will be available for your client computers when they contact the WSUS server.
If you prefer to validate all revised updates, you must approve the latest revision manually. This approach might be an option to consider in the following scenarios:
- If there is a binary file change in an update revision release, and you want to test the update before automatically installing it on your client computers.
- If the revised update has changes that would apply only to specific computers in your network. For example, a revised update might fix an issue in Microsoft Windows 2003 operating systems, but does not impact computers running Windows 2000 operating systems, and you have both Windows 2000 and Windows 2003 operating systems in your network.
An update *rerelease* is a replacement for an update that has expired.
If you have installed an update and it is either revised or rereleased, read the Description and Deployment Information columns associated with the update on the [WSUS TechNet page](http://go.microsoft.com/fwlink/?linkid=41171), and read the [Description of the standard terminology that is used to describe Microsoft software updates](http://support.microsoft.com/?kbid=824684) to help determine if you need to perform any action for the update associated with the update's revision or rerelease publication.
Superseding and Superseded Updates
----------------------------------
Typically, an update that supersedes other updates does one or more of the following:
- Enhances, improves, or adds to the fix provided by one or more previously released updates.
- Improves the efficiency of its update file package, which is installed on client computers if the update is approved for installation. For example, the superseded update might contain files that are no longer relevant to the fix or to the operating systems now supported by the new update, so those files are not included in the superseding update's file package.
- Updates newer versions of a product, or in other words, is no longer applicable to older versions or configurations of a product. Updates can also supersede other updates if modifications have been made to expand language support. For example, a later revision of a product update for Microsoft Office might remove support for an older operating system, but add additional support for new languages in the initial update release.
Conversely, an update that is superseded by another update does the following:
- Fixes a similar vulnerability in the update that supersedes it. However, the update that supersedes it might enhance the fix or modify the applicability to client computers that the superseded update provides.
- Updates earlier versions or configurations of products.
On the WSUS console, the WSUS update page clearly indicates those updates that have a superseded or superseding relationship with an earlier version. The **Details** tab also includes "Superseded by" and "Supersedes" status information for updates, in addition to KB links containing more information about each update.
WSUS does not automatically decline superseded updates, and it is recommended that you do not assume that superseded updates should be declined in favor of the new, superseding update. Before declining a superseded update, make sure that it is no longer needed by any of your client computers. These are three possible scenarios in which you might need to install a superseded update:
- If a superseding update supports only newer versions of an operating system, and some of your client computers run earlier versions of the operating system.
- If a superseding update has more restricted applicability than the update it supersedes, which would make it inappropriate for some client computers.
- If an update no longer supersedes a previously released update because of new changes. It is possible that, through changes at each release, an update no longer supersedes an update it previously superseded in an earlier version.
Approving a Superseding Update
------------------------------
Because a superseding update typically enhances a fix provided by a previously released, superseded update, it is recommended that you first see how many client computers will be compliant with the new update, and work backward from there. Use the following process.
**To approve a superseding update**
1. Approve the superseding update for installation on all applicable computers.
2. Check the resulting status of the approval action on your computers. Note which computers show status as "Not needed" for the update, and then compare the properties of those computers with the properties of the update.
3. Use the information in the update properties to help you determine which previously released version of the updates are available. For example, in WSUS 2.0, look under "Supersedes" on the **Details** tab, and check the "Description" and KB article number entries if appropriate.
4. Get information about the superseded, previously released versions of the updates by viewing their properties.
5. Approve the update for installation when you find a superseded update that seems appropriate for the remaining client computers.
6. Repeat this process until all of your client computers are updated with the intended fix.
Expired Updates
---------------
An expired update is an update that has been invalidated by Microsoft. An expired update can also be an update that has been superseded by the release of another update (new or revised) that fixes or enhances functionality or applicability offered by the expiring update. In this case, the superseding update should be approved in place of the expired update. An update that is expired can no longer be approved for detection or installation.
| 86.974576 | 509 | 0.78174 | eng_Latn | 0.998492 |
2fd3f99227d630e31f53ed1b44a3aedcc2dcdbbd | 102 | md | Markdown | README.md | bricelab/ujumbe-registre | ca89cce70180a8eaa0890bb8e64bba40b26f2b09 | [
"MIT"
] | 2 | 2019-12-19T10:03:03.000Z | 2022-01-30T23:42:54.000Z | README.md | bricelab/ujumbe-registre | ca89cce70180a8eaa0890bb8e64bba40b26f2b09 | [
"MIT"
] | 1 | 2019-12-19T09:42:29.000Z | 2019-12-19T09:42:29.000Z | README.md | bricelab/ujumbe-registre | ca89cce70180a8eaa0890bb8e64bba40b26f2b09 | [
"MIT"
] | null | null | null | # UJUMBE Registre
Application de gestion dématérialisée des régistres de courriers arrivés et départs
| 34 | 83 | 0.852941 | fra_Latn | 0.990111 |
2fd45a726caa6ebba5a401b2d175b05e0be71c0a | 4,481 | md | Markdown | articles/event-grid/event-schema-event-hubs.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/event-grid/event-schema-event-hubs.md | jhomarolo/azure-docs.pt-br | d11ab7fab56d90666ea619c6b12754b7761aca97 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/event-grid/event-schema-event-hubs.md | jhomarolo/azure-docs.pt-br | d11ab7fab56d90666ea619c6b12754b7761aca97 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Esquema de eventos de hubs de eventos da Grade de Eventos do Azure
description: Descreve as propriedades que são fornecidas para eventos de hubs de evento com a Grade de Eventos do Azure
services: event-grid
author: spelluru
ms.service: event-grid
ms.topic: reference
ms.date: 01/17/2019
ms.author: spelluru
ms.openlocfilehash: 9c0113687d27bf43375f298057129a5594ec0a06
ms.sourcegitcommit: 3102f886aa962842303c8753fe8fa5324a52834a
ms.translationtype: MT
ms.contentlocale: pt-BR
ms.lasthandoff: 04/23/2019
ms.locfileid: "60561821"
---
# <a name="azure-event-grid-event-schema-for-event-hubs"></a>Esquema de eventos da Grade de Eventos do Azure para hubs de eventos
Este artigo fornece as propriedades e o esquema para eventos de hubs de evento. Para obter uma introdução a esquemas de evento, consulte [esquema de grade de eventos do Azure](event-schema.md).
Para obter uma lista de scripts de exemplo e tutoriais, consulte [origem do evento dos Hubs de eventos](event-sources.md#event-hubs).
### <a name="available-event-types"></a>Tipos de evento disponíveis
Hubs de evento emite o **Microsoft.EventHub.CaptureFileCreated** quando um arquivo de captura é criado.
## <a name="example-event"></a>Exemplo de evento
Este exemplo de evento mostra o esquema de um evento dos Hubs de Eventos gerado quando o recurso Capturar armazena um arquivo:
```json
[
{
"topic": "/subscriptions/<guid>/resourcegroups/rgDataMigrationSample/providers/Microsoft.EventHub/namespaces/tfdatamigratens",
"subject": "eventhubs/hubdatamigration",
"eventType": "Microsoft.EventHub.CaptureFileCreated",
"eventTime": "2017-08-31T19:12:46.0498024Z",
"id": "14e87d03-6fbf-4bb2-9a21-92bd1281f247",
"data": {
"fileUrl": "https://tf0831datamigrate.blob.core.windows.net/windturbinecapture/tfdatamigratens/hubdatamigration/1/2017/08/31/19/11/45.avro",
"fileType": "AzureBlockBlob",
"partitionId": "1",
"sizeInBytes": 249168,
"eventCount": 1500,
"firstSequenceNumber": 2400,
"lastSequenceNumber": 3899,
"firstEnqueueTime": "2017-08-31T19:12:14.674Z",
"lastEnqueueTime": "2017-08-31T19:12:44.309Z"
},
"dataVersion": "",
"metadataVersion": "1"
}
]
```
## <a name="event-properties"></a>Propriedades do evento
Um evento tem os seguintes dados de nível superior:
| Propriedade | Type | DESCRIÇÃO |
| -------- | ---- | ----------- |
| topic | string | Caminho de recurso completo para a origem do evento. Esse campo não é gravável. Grade de Eventos fornece esse valor. |
| subject | string | Caminho definido pelo fornecedor para o assunto do evento. |
| eventType | string | Um dos tipos de evento registrados para a origem do evento. |
| eventTime | string | A hora em que o evento é gerado com base na hora UTC do provedor. |
| ID | string | Identificador exclusivo do evento. |
| data | objeto | Dados de evento de hub de eventos. |
| dataVersion | string | A versão do esquema do objeto de dados. O fornecedor define a versão do esquema. |
| metadataVersion | string | A versão do esquema do metadados de evento. Grade de Eventos define o esquema de propriedades de nível superior. Grade de Eventos fornece esse valor. |
O objeto de dados tem as seguintes propriedades:
| Propriedade | Type | DESCRIÇÃO |
| -------- | ---- | ----------- |
| fileUrl | string | O caminho para o arquivo de captura. |
| FileType | string | O tipo de arquivo para o arquivo de captura. |
| partitionId | string | A ID de fragmento. |
| sizeInBytes | inteiro | Tamanho do arquivo. |
| eventCount | inteiro | O número de eventos no arquivo. |
| firstSequenceNumber | inteiro | O menor número de sequência da fila. |
| lastSequenceNumber | inteiro | O último número de sequência da fila. |
| firstEnqueueTime | string | A primeira vez da fila. |
| lastEnqueueTime | string | A última vez da fila. |
## <a name="next-steps"></a>Próximas etapas
* Para ver uma introdução à Grade de Eventos do Azure, confira [O que é uma Grade de eventos?](overview.md)
* Para obter mais informações sobre como criar uma assinatura da Grade de Eventos do Azure, confira [Event Grid subscription schema](subscription-creation-schema.md) (Esquema de assinatura da Grade de Eventos).
* Para obter informações sobre como manipular eventos de hubs de evento, consulte [fluxo de dados grandes em um data warehouse](event-grid-event-hubs-integration.md). | 50.348315 | 210 | 0.718366 | por_Latn | 0.969454 |
2fd4d3c91be3e0cd297fc006a26ddaec23d57fd3 | 2,291 | md | Markdown | apiendpoints.md | greysongy/virtual-fridge | 2bf023fcbbdbcd7438dba526bfeffa415cb3599a | [
"MIT"
] | null | null | null | apiendpoints.md | greysongy/virtual-fridge | 2bf023fcbbdbcd7438dba526bfeffa415cb3599a | [
"MIT"
] | 22 | 2019-08-07T22:43:55.000Z | 2022-02-26T16:02:18.000Z | apiendpoints.md | greysongy/virtual-fridge | 2bf023fcbbdbcd7438dba526bfeffa415cb3599a | [
"MIT"
] | 3 | 2019-08-12T23:12:44.000Z | 2020-05-28T04:42:22.000Z | # API Endpoints `Defined by Application Flow`
1. User Logs in/Registers
___
- When user registers/authenticates, we need to perform a `POST` request that stores the unique user ID provided by the log in token, or the unique user email.
> [`POST`] `/api/newuser` creates a new user
- Required parameters:
- `'name'`, `'family_id'`
NOTE: We should store the user's unique ID/name property and family_id to cookies or local storage so that we can access them later as identifiers to load the correct user data per page.
> [`POST`] `/api/fridge/:id` creates a new fridge
- Required parameters:
- query parameter should be equal to either the user `'name'` or `'family_id'`
- `req.body` should include:
- `user_id` of the registered user
- `family_id` of the registered user
___
2. User Opens Fridge Page
> [`GET`] `/api/fridge/:id` obtains fridge, renders all items to page, saves items array to `this.state`
- Required parameters:
- query parameter should be equal to either the user `'name'` or `'family_id'`
> [`PUT`] `/api/fridge/:id` adds/removes items
- Required parameters:
- query parameter should be equal to either the user `'name'` or `'family_id'`
- `req.body` should include:
- updated `items` array with selected (`onClick`) item (if remove button, it removes the selected item from their array then pushes to database. whereas add button adds it to the array, then pushes to database.)
---
3. User Opens Grocery/Shopping List Page
> [`POST`] `/api/shoppinglist/:id` creates a shopping list in db
- Required parameters:
- query parameter should be equal to either the user `'name'` or `'family_id'`
> [`GET`] `/api/shoppinglist/:id` gets shopping list to populate page
- Required parameters:
- query parameter should be equal to either the user `'name'` or `'family_id'`
> [`PUT`] `/api/shoppinglist/:id` updates user's shopping list
- Required parameters:
- query parameter should be equal to either the user `'name'` or `'family_id'`
- `req.body` should include:
- updated `items` array with selected (`onClick`) item (if remove button, it removes the selected item from their array then pushes to database. whereas add button adds it to the array, then pushes to database.)
| 37.557377 | 219 | 0.705805 | eng_Latn | 0.994331 |
2fd4d49c1b624da8eaf595ab987094f50279340a | 684 | md | Markdown | api/Word.Template.Save.md | kibitzerCZ/VBA-Docs | 046664c5f09c17707e8ee92fd1505ddd0f6c9a91 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2019-11-07T07:46:13.000Z | 2019-11-07T07:46:13.000Z | api/Word.Template.Save.md | kibitzerCZ/VBA-Docs | 046664c5f09c17707e8ee92fd1505ddd0f6c9a91 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | api/Word.Template.Save.md | kibitzerCZ/VBA-Docs | 046664c5f09c17707e8ee92fd1505ddd0f6c9a91 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2019-11-28T06:51:45.000Z | 2019-11-28T06:51:45.000Z | ---
title: Template.Save method (Word)
keywords: vbawd10.chm157941861
f1_keywords:
- vbawd10.chm157941861
ms.prod: word
api_name:
- Word.Template.Save
ms.assetid: 34f41798-89a1-050f-be00-2e8421b1389b
ms.date: 06/08/2017
localization_priority: Normal
---
# Template.Save method (Word)
Saves the specified template.
## Syntax
_expression_.**Save**
_expression_ Required. A variable that represents a '[Template](Word.Template.md)' object.
## Remarks
If the template has not been saved before, the **Save As** dialog box prompts the user for a file name.
## See also
[Template Object](Word.Template.md)
[!include[Support and feedback](~/includes/feedback-boilerplate.md)] | 18.486486 | 104 | 0.752924 | eng_Latn | 0.577109 |
2fd517e0a2221ddbfd63d618af0170df3109c0b5 | 9,144 | md | Markdown | old/README.md | Cezerin3/Admin-NX | cf6ca905ce3fad631f488fad4f68cb373b88adc1 | [
"Unlicense"
] | 1 | 2020-11-22T06:42:05.000Z | 2020-11-22T06:42:05.000Z | old/README.md | dodoankur/Store-NX | d24ec8cfcff62821701427bae67620ccb65b7611 | [
"Unlicense"
] | 48 | 2020-11-26T06:59:05.000Z | 2021-11-10T05:26:21.000Z | old/README.md | dodoankur/Store-NX | d24ec8cfcff62821701427bae67620ccb65b7611 | [
"Unlicense"
] | 1 | 2021-06-08T17:15:16.000Z | 2021-06-08T17:15:16.000Z | # Cezerin is React and Node.js based eCommerce platform. React Shopping Cart.
Cezerin - Ecommerce Progressive Web Apps. Complete Solution.
### Contributers are wanted!!! (Anyone are welcome!)
### And put a star above if you like this, it'll help us a lot...!
## Quick Start
1. Download from https://github.com/Cezerin3/Documentation/raw/main/src/cezerin3.zip
2. Extract file with zip extacter such as 7zip
3. You must have,
- Nodejs: https://nodejs.org/en/download/
- YarnPkg: https://yarnpkg.com/getting-started/install
4. You must have mongodb locally running https://docs.mongodb.com/manual/installation/
5. Double click on start.sh inside the folder, That's all folks.....
## Warning
- You need to have nodejs lts/v12 not higher or lower
- At least 3Gb of ram and dual core cpu
- 20Gb of space
## Cezerin Platform:
1. Cezerin API - Backend.
2. Cezerin Store - Frontend.
3. Cezerin Admin - Dashboard.
4. Cezerin Client - JavaScript client for Cezerin REST API.
## Built with:
- NodeJS
- ReactJs
- Redux
- ExpressJs
- Babel
- WebPack
- MongoDB
## Links
- [GitHub](https://github.com/Cezerin3)
- [Community Site](https://cezerin3.web.app/)
- [Demo Store - Plusha Theme](https://plusha.cezerin.net)
- [Demo Store - Default Theme](https://cezerin.net)
- [Demo Dashboard](https://cezerin.net/admin)
- [Telegram Chat: Cezerin](https://t.me/cezerin)
- [Forum](https://groups.google.com/g/cezerin)
- [Docs](https://cezerin3.web.app/docs)
- [Facebook](https://facebook.com/cezerin) Not active!
- [Twitter](https://twitter.com/cezerin2) Not active!
## Store
Single-Page Application with React server-side rendering.
SEO Friendly. Google Analytics eCommerce Tracking included.
[Online Demo Store - Plusha Theme](https://plusha.cezerin.net)
[](https://plusha.cezerin.net)
[Online Demo Store - Default Theme](https://cezerin.net)
[](https://cezerin.net)
[](https://cezerin.net)
## Dashboard
Client-side dashboard use JSON Web Token (JWT) to access REST API.
[Online Demo Dashboard](https://cezerin.net/admin)
## Documentation
[Documentation](https://cezerin3.web.app/docs)
- Getting Started
- [Overview](https://cezerin3.web.app/docs/overview)
- [Quick Start](https://cezerin3.web.app/docs/quick-start)
- [Online Demo](https://cezerin3.web.app/docs/online-demo)
- [Application Structure](https://cezerin3.web.app/docs/application-structure)
- Installation Guides
- [Prerequisites](https://cezerin3.web.app/prerequisites)
- [Setup Database](https://cezerin3.web.app/docs/setup-database)
- [Using source code](https://cezerin3.web.app/docs/using-source-code)
- [Using docker](https://cezerin3.web.app/docs/using-docker)
- Deploy on Web
- [Hosting](https://cezerin3.web.app/docs/deploy/hosting)
- [Create droplet](https://cezerin3.web.app/docs/deploy/droplet)
- [Setup domain](https://cezerin3.web.app/docs/deploy/domain)
- [Install NGinx Web Server + MERN Stack](https://cezerin3.web.app/docs/deploy/mern)
- [Run MongoDB](https://cezerin3.web.app/docs/deploy/mongodb)
- [Run Cezerin](https://cezerin3.web.app/docs/deploy/cezerin)
- [Run NGinx](https://cezerin3.web.app/docs/deploy/nginx)
- [Cezerin configs changes](https://cezerin3.web.app/docs/deploy/cezerin-configs)
- [Final checks](https://cezerin3.web.app/docs/deploy/final-checks)
- [Setup Let's Encrypt SSL Certificate](https://cezerin3.web.app/docs/deploy/lets-encrypt)
- [Turn off Developer Mode](https://cezerin3.web.app/docs/deploy/production-mode)
- API
- [API Reference](https://cezerin3.web.app/docs/api)
- [API Client](https://github.com/Cezerin3/Client)
- Help
- [FAQ](https://cezerin3.web.app/docs/faq)
- [HowTos](https://cezerin3.web.app/docs/howtos)
- [Help and Support](https://cezerin3.web.app/docs/help-and-support)
### Requirements
- Node.js v12/lts
- Yarnpkg
- MongoDB
## Application Structure
```
.
├── config # Project and build configurations
├── dist # Distribution folder
├── locales # Text files
├── logs # Log files
├── public # Static public assets and uploads
│ ├── admin # Dashboard index.html
│ ├── admin-assets # Dashboard assets
│ └── content # Store root folder
|
├── scripts # Shell scripts for theme install/export
├── src # Application source code
│ ├── admin # Dashboard application
│ │ └── client # Client side code
│ ├── api # REST API
│ │ └── server # Server side code
│ └── store # Store application
│ ├── client # Client side code
│ ├── server # Server side code
│ └── shared # Universal code
│
├── theme # Theme as a local package
└── process.json # pm2 process file
```
## Yarn Scripts
| `yarn <script>` | Description |
| --------------------- | --------------------------------------------------------------------- |
| `clean` | Delete store and admin asset bundles. | Not working! |
| `compile:watch` | Compiles the application to disk **and watch** (`~/dist` by default). |
| `compile` | Compiles the application to disk (`~/dist` by default). |
| `webpack:admin:watch` | Assemble admin bundles **and watch**. |
| `webpack:store:watch` | Assemble store bundles **and watch**. |
| `webpack:admin` | Assemble admin bundles. |
| `webpack:store` | Assemble store bundles. |
| `theme:install` | Install theme from /public/<file>.zip |
| `theme:export` | Zip current theme to /public/<file>.zip |
| `theme:copy` | Compile theme and copy assets to /public/ | Not working! |
| `theme:build:watch` | Refresh theme after modification **and watch**. | Not working! |
| `theme:build` | Refresh theme after modification. |
| `build:watch` | Compile and assemble bundles **and watch**. |
| `build` | Compile and assemble bundles. |
| `start` | Start node server. |
## Financial contributions
We also welcome financial contributions in full transparency on our [open collective](https://opencollective.com/cezerin3),
[Issue Hunt](https://issuehunt.io/r/Cezerin3/Store) or [PayPal](https://www.paypal.com/paypalme/himadu1).
And all financial transaction will be publically displayed it's our duty to do so!
Anyone can file an expense. If the expense makes sense for the development of the community, it will be "merged" in the ledger of our open collective by the core contributors and the person who filed the expense will be reimbursed.
## Credits
### Contributors
Thank you to all the people who have already contributed to Cezerin/Cezerin2/Cezerin3!
<a href="https://github.com/Cezerin3/Store/graphs/contributors"><img src="https://opencollective.com/cezerin3/contributors.svg?width=890" /></a>
<a href="https://github.com/Cezerin2/cezerin2/graphs/contributors"><img src="https://opencollective.com/cezerin2/contributors.svg?width=890" /></a>
<a href="https://github.com/cezerin/cezerin/graphs/contributors"><img src="https://opencollective.com/cezerin3/contributors.svg?width=890" /></a>
### Backers
Thank you to all our backers! [[Become a backer](https://opencollective.com/cezerin3#backer)]
<a href="https://opencollective.com/cezerin3#backers" target="_blank"><img src="https://opencollective.com/cezerin3/tiers/backer.svg?avatarHeight=36&width=600"></a>
### Sponsors
Thank you to all our sponsors! (please ask your company to also support this open source project by [becoming a sponsor](https://opencollective.com/cezerin3#sponsor))
https://www.paypal.com/paypalme/himadu1
<a href="https://opencollective.com/cezerin3#sponsor" target="_blank"><img src="https://opencollective.com/cezerin3/tiers/sponsor.svg?avatarHeight=36&width=600"></a>
## Contributing
If you can, please contribute by reporting issues, discussing ideas, or submitting pull requests with patches and new features. We do our best to respond to all issues and pull requests within a day or two, and make patch releases to npm regularly.
## Licence
This software is provided free of charge and without restriction under the Unlicense
| 43.336493 | 248 | 0.643154 | eng_Latn | 0.244285 |
2fd53e6bb4c7c1afec425beaaacddb0fcc9f21b0 | 839 | md | Markdown | README.md | aethernet/files | 84fa3f1ee9222d24366049bca347d50074706686 | [
"MIT"
] | null | null | null | README.md | aethernet/files | 84fa3f1ee9222d24366049bca347d50074706686 | [
"MIT"
] | null | null | null | README.md | aethernet/files | 84fa3f1ee9222d24366049bca347d50074706686 | [
"MIT"
] | null | null | null | # files
Balena Block Simple File Manager
Will serve the content of a directory to the web using [serve-index](https://www.npmjs.com/package/serve-index)
# Usage
Add this block to your `docker-compose.yml`
```
volumes:
files:
services:
files:
image: bhcr.io/edwin3/files
restart: always
volumes:
- "files:/files"
environement:
- BROWSE_FOLDER=/files
ports:
- 80
```
Map the `files` volume to the other services who produces or consumes your files.
## Environement
Configure with :
- PORT: 80 # default to 80
- BROWSE_FOLDER: /usr/local/files
- UPLOAD_FOLDER: /usr/local/files/upload
- ALLOW_UPLOAD: 0 # for future vesion, no effect
- ALLOW_DELETE: 0 # for future vesion, no effect
# Based on
- express
- serve-index
- del
# Roadmap
- [x] List
- [x] Download
- [ ] Upload
- [ ] Delete
| 16.45098 | 111 | 0.67938 | eng_Latn | 0.627788 |
2fd6009023854b231e35e6ab6df259f8b4416323 | 2,633 | md | Markdown | data/blog/javascript-scope.md | uglyduck1104/duck-s-study-blog | 7481cc3c3b5f45292e1de08528682d6f9f420813 | [
"MIT"
] | null | null | null | data/blog/javascript-scope.md | uglyduck1104/duck-s-study-blog | 7481cc3c3b5f45292e1de08528682d6f9f420813 | [
"MIT"
] | 1 | 2022-03-30T00:18:36.000Z | 2022-03-30T00:18:36.000Z | data/blog/javascript-scope.md | uglyduck1104/duck-s-study-blog | 7481cc3c3b5f45292e1de08528682d6f9f420813 | [
"MIT"
] | null | null | null | ---
title: 스코프
date: '2022-05-15'
tags: ['javascript']
draft: false
summary: 자바스크립트의 스코프는 다른 언어 스코프와 구별되는 특징이 있음
layout: PostSimple
authors: ['default']
---
# 스코프
- 자바스크립트의 스코프는 다른 언어 스코프와 구별되는 특징이 있음
- var, let, const에 따라 선언한 변수의 스코프는 다르게 동작함
- `식별자가 유효한 범위`
## 코드의 문맥과 환경
```javascript
var x = 'global';
function foo() {
var x = 'local';
console.log(x); // (1)
}
foo();
console.log(x); // (2)
```
- `식별자 결정`(Identifier resolution)
- 자바스크립트 엔진은 이름이 같은 두 변수 중에서 어떤 변수를 참조할 것인지를 결정함
- `코드의 가장 바깥 영역`에 선언된 x 변수는 `어디서든 참조`할 수 있음
- foo `함수 내부`에서 선언된 x 변수는 foo `함수 내부에서만 참조` 가능
<img alt="js_scope1" src="/static/images/js_scope1.png" width="700"/>
- 스코프를 사용하지 않았다면, 이름이 같은 변수끼리 충돌을 일으킬 수 있음
> `렉시컬 환경` : *“코드가 어디서 실행되며 주변에 어떤 코드가 있는지”*\
> 코드의 문맥은 `렉시컬 환경`으로 이뤄지며 이를 구현한 것은 `실행 컨텍스트`라 함\
`모든 코드`는 실행 컨텍스트에서 `평가`되고 `실행`됨
## 스코프의 종류
| 구분 | 설명 | 스코프 | 변수 |
|-----|--------------|--------|-------|
| 전역 | 코드의 가장 바깥 영역 | 전역 스코프 | 전역 변수 |
| 지역 | 함수 몸체 내부 | 지역 스코프 | 지역 변수 |
<img alt="js_scope2" src="/static/images/js_scope2.png" width="700"/>
### 전역과 전역 스코프
- 전역은 전역 스코프를 만듦
- 전역 변수는 어디서든지 참조 가능
### 지역과 지역 스코프
- 함수 몸체 내부를 말함
- 지역에 변수를 선언하면 지역 스코프를 갖는 지역 변수가 됨
- 자신의 지역 스코프와 하위 지역 스코프에서 유효함
## 스코프 체인
- 스코프는 함수의 중첩에 의해 계층적인 구조를 갖음
- `중첩 함수의 지역 스코프`는 중첩 함수를 포함하는 `외부 함수의 지역 스코프`와 계층적 구조를 갖음
<img alt="js_scope3" src="/static/images/js_scope3.png" width="400"/>
> 최상위 스코프는 전역 스코프
- 모든 스코프는 `하나의 계층적 구조`로 연결되는 것을 `스코프 체인`이라고 함
- 변수를 참조할 때 자바스크립트 엔진은 스코프 체인을 통해 변수를 참조하는 코드의 스코프에서 시작하여 상위 스코프 방향으로 이동하며 선언된 변수를 검색함
### 스코프 체인에 의한 변수 검색
- 상위 스코프에서 유효한 변수는 하위 스코프에서 자유롭게 참조할 수 있지만 하위 스코프에서 유효한 변수를 상위 스코프에서는 참조 할 수 없음
### 스코프 체인에 의한 함수 검색
```javascript
// 전역 함수
function foo() {
console.log('global function foo');
}
function bar() {
// 중첩 함수
function foo() {
console.log('local function foo');
}
foo(); // (1)
}
bar();
```
- (1)에서 foo 함수를 호출하면 자바스크립트 엔진은 함수를 호출하기 위해 먼저 함수를 가리키는 식별자 foo를 검색함
> 함수도 `식별자`에 할당되기 때문에 변수와 동일하게 `스코프 소유`\
> 따라서 `식별자를 검색하는 규칙`이라고 정의할 수 있음
## 렉시컬 스코프
```javascript
var x = 1;
function foo() {
var x = 10;
bar();
}
function bar() {
console.log(x);
}
foo(); // 1
bar(); // 1
```
Case1. 함수를 어디서 호출했는지에 따라 함수의 상위 스코프를 결정
- `동적 스코프`
- 함수를 정의하는 시점에서 함수가 어디서 호출될지 알 수 없음
- 함수가 `호출되는 시점`에 동적으로 `상위 스코프를 결정`하기 때문에 동적스코프라 함
Case2. 함수를 어디서 정의했는지에 따라 함수의 상위 스코프를 결정
- `렉시컬 스코프` or `정적 스코프`
- 함수 정의가 평가되는 시점에 상위 스코프 결정
> 자바스크립트는 렉시컬 스코프(`Case2`)를 따르므로 함수를 `어디서 정의했는지`에 따라 상위 스코프가 결정됨(함수가 호출된 위치는 상위 스코프 결정에 어떠한 영향을 주지 않음)\
> 👉 즉, 함수의 상위 스코프는 언제나 `자신이 정의된 스코프`
> **Referenced**
- 이응모, 『모던 자바스크립트 Deep Dive』, 위키북스(2022.4.25), 189 ~ 199p
| 18.673759 | 103 | 0.61071 | kor_Hang | 1.00001 |
2fd6266a96aad2d351fd26ec26e7a1ab5bea9681 | 2,906 | md | Markdown | docs/vs-2015/xml-tools/editing-xslt-style-sheets.md | 1DanielaBlanco/visualstudio-docs.es-es | 9e934cd5752dc7df6f5e93744805e3c600c87ff0 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/vs-2015/xml-tools/editing-xslt-style-sheets.md | 1DanielaBlanco/visualstudio-docs.es-es | 9e934cd5752dc7df6f5e93744805e3c600c87ff0 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/vs-2015/xml-tools/editing-xslt-style-sheets.md | 1DanielaBlanco/visualstudio-docs.es-es | 9e934cd5752dc7df6f5e93744805e3c600c87ff0 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Editar hojas de estilos XSLT | Documentos de Microsoft
ms.custom: ''
ms.date: 11/15/2016
ms.prod: visual-studio-dev14
ms.reviewer: ''
ms.suite: ''
ms.technology:
- vs-ide-general
ms.tgt_pltfrm: ''
ms.topic: article
ms.assetid: 080bed0f-0ca9-4be7-aecd-6bdaebc04007
caps.latest.revision: 11
author: gewarren
ms.author: gewarren
manager: ghogen
ms.openlocfilehash: 7dd25a531682c74284a74f065dc729f37ac7fb1a
ms.sourcegitcommit: 9ceaf69568d61023868ced59108ae4dd46f720ab
ms.translationtype: MT
ms.contentlocale: es-ES
ms.lasthandoff: 10/12/2018
ms.locfileid: "49287008"
---
# <a name="editing-xslt-style-sheets"></a>Editar hojas de estilos XSLT
[!INCLUDE[vs2017banner](../includes/vs2017banner.md)]
El Editor XML se puede utilizar también para editar hojas de estilos XSLT. Puede aprovechar las características predeterminadas del editor como IntelliSense, esquematización, fragmentos XML, etc. Además, se incluyen también nuevas características que facilitan la programación en XSLT.
## <a name="xslt-features"></a>Características XSLT
En la siguiente tabla se describen características específicas del trabajo con hojas de estilos XSLT.
**Color de sintaxis**
Las palabras clave XSLT, como `template`, `match`, y así sucesivamente, se muestran en el color de palabra clave XSLT especificado por el **fuentes y colores** configuración.
**Subrayado ondulado**
El Editor XML utiliza el archivo xslt.xsd instalado para validar las hojas de estilos XSLT. Los errores de validación se muestran con un subrayado ondulado de color azul. El Editor XML también compila la hoja de estilos en segundo plano e informa de los errores o advertencias del compilador mediante el subrayado ondulado adecuado.
**Compatibilidad con bloques de scripts**
El depurador de XSLT admite el código en bloques de scripts, de modo que puede definir puntos de interrupción y examinar el código del bloque de script.
**Ver el resultado XSLT**
Puede ejecutar una transformación XSL y ver el resultado desde el Editor XML. Para obtener más información, consulte [Cómo: ejecutar una transformación XSLT desde el Editor XML](../xml-tools/how-to-execute-an-xslt-transformation-from-the-xml-editor.md).
**Depurar XSLT**
Puede iniciar el depurador de XSLT desde un archivo XSLT del Editor XML. El depurador admite la definición de puntos de interrupción en el archivo XSLT, la visualización del estado de ejecución de XSLT, etc. Al mantener el mouse sobre una variable XSLT se muestra un cuadro de información sobre herramientas con el valor de la variable. El depurador se puede utilizar para depurar una hoja de estilos o para depurar una transformación XSL compilada invocada desde otra aplicación. Para obtener más información, consulte [depuración XSLT](../xml-tools/debugging-xslt.md).
## <a name="see-also"></a>Vea también
[Editor XML](../xml-tools/xml-editor.md)
| 54.830189 | 573 | 0.779422 | spa_Latn | 0.961755 |
2fd70d32e55f4bfa9252965ab21b356690688b49 | 30 | md | Markdown | readme.md | phpbe/sf | eb37fe2d2b81c4c8f6ef616d7e1b366ca2590ceb | [
"MIT"
] | null | null | null | readme.md | phpbe/sf | eb37fe2d2b81c4c8f6ef616d7e1b366ca2590ceb | [
"MIT"
] | null | null | null | readme.md | phpbe/sf | eb37fe2d2b81c4c8f6ef616d7e1b366ca2590ceb | [
"MIT"
] | null | null | null | PHP BE 服务框架（Service Framework） | 30 | 30 | 0.833333 | kor_Hang | 0.490349 |
2fd7292f608be88c456414f6940c879dd3e617b2 | 2,034 | md | Markdown | index.md | ralanbowman/ralanbowman.github.io | a70e51d04eb94e038f96fc623f1e224fc052c6e0 | [
"MIT",
"BSD-3-Clause"
] | null | null | null | index.md | ralanbowman/ralanbowman.github.io | a70e51d04eb94e038f96fc623f1e224fc052c6e0 | [
"MIT",
"BSD-3-Clause"
] | 3 | 2021-05-17T22:03:23.000Z | 2022-02-26T01:14:49.000Z | index.md | ralanbowman/ralanbowman.github.io | a70e51d04eb94e038f96fc623f1e224fc052c6e0 | [
"MIT",
"BSD-3-Clause"
] | 1 | 2020-09-29T23:01:43.000Z | 2020-09-29T23:01:43.000Z | ---
title: About Me
keywords: homepage
sidebar: main_sidebar
permalink: index.html
summary:
---
My name is Alan Bowman and I’m an experienced technical writer currently seeking a new job opportunity where I can help users and customers find answers, solve problems, and create amazing things.
**Useful links:**
[**Portfolio**](/portfolio.html) - some examples of my work and how I work
[**Resume**](/resume.html) - my resume in several formats (PDF, .docx, .odt, .txt)
[**LinkedIn**](https://www.linkedin.com/in/ralanbowman) - my professional network profile
[**Contact info**](/contact_info.html) - my e-mail address, Twitter, Facebook, and IM info
As a technical writer, my job is to understand the user: their reasons for using the product or service, their level of technical ability, and their desired end result, and then provide them with exactly the information they need so they can build products and services that help change the world. I document the task, not the technology.
As a technical writer, my job is to also understand the needs of the business: the industry they’re in, the marketing strategy and sales goals, and the overall objectives of the company, and then make sure that the information I provide to the customer reflects the company's image and plan of action.
My skills as a technical writer include:
* User guides and release notes
* Documentation for RESTful APIs (JSON and XML)
* READMEs and man pages for command line UNIX/Linux/*BSD applications
* Documentation for platform APIs using Doxygen and Javadoc (limited experience)
* JavaScript function/method documentation (limited experience)
I also have experience with:
* Project management - managing my own projects and my deliverables in projects run by others
* Customer advocacy - working across all departments to ensure the best user experience for the customer and for the staff
* Testing and QA - working with the development team to find any issues in new products and services before release
| 56.5 | 340 | 0.767945 | eng_Latn | 0.998955 |
2fd80d712fb181816ed0e8b0efcf18a8aa54d4c2 | 1,433 | md | Markdown | ko/config/level_horizon_calibration.md | mamariomiamo/PX4-user_guide | 4141b7ca3f8db8be499e71ae26227641e89c3b5c | [
"CC-BY-4.0"
] | null | null | null | ko/config/level_horizon_calibration.md | mamariomiamo/PX4-user_guide | 4141b7ca3f8db8be499e71ae26227641e89c3b5c | [
"CC-BY-4.0"
] | null | null | null | ko/config/level_horizon_calibration.md | mamariomiamo/PX4-user_guide | 4141b7ca3f8db8be499e71ae26227641e89c3b5c | [
"CC-BY-4.0"
] | null | null | null | # 수평 균형 보정
*수평 균형 보정* 과정을 거쳐 제어 장치 방향의 미세한 어긋남을 보정하고 *QGroundControl* 비행 시야의 수평(파란색이 위로, 녹색이 아래로 가게)을 맞출 수 있습니다.
:::tip
Leveling the horizon is highly recommended, and will result in the best flight performance. This process can also be repeated if you notice a constant drift during flight.
:::
## 보정 수행
To level the horizon:
1. *QGroundControl *을 시작하고 기체를 연결합니다.
2. 상단 도구 모음에서 **톱니바퀴** 아이콘(기체 설정)을 선택한 다음 가장자리 표시줄에서 **센서**를 선택하십시오.
3. **수평 조정** 단추를 누르십시오.  :::note You should already have set the [Autopilot Orientation](../config/flight_controller_orientation.md). 미리 설정하지 않았다면, 여기에서 설정할 수 있습니다.
:::
4. 기체를 방향을 유지한 채로 평평한 바닥에 두십시오:
* 비행기의 경우 이 자세가 수평 비행 자세입니다 (비행기는 날개가 약간 올라가는 경향이 있습니다!).
* 헬리콥터의 경우 이 자세가 부양 자세입니다.
5. 보정 과정을 시작하려면 **확인**을 누르십시오.
6. 보정 과정이 끝날 때까지 기다리십시오.
## 검증
After the orientation is set and level-horizon calibration is complete, check in the flight view that the heading in the compass shows a value around 0 when you point the vehicle towards north and that the horizon is level (blue on top and green on bottom).
## 추가 정보
* [고급 방향 조정](../advanced_config/advanced_flight_controller_orientation_leveling.md) (고급 사용자 전용).
* [QGroundControl 사용자 안내서 > 센서](https://docs.qgroundcontrol.com/en/SetupView/sensors_px4.html#level-horizon)
* [PX4 설치 동영상 "각가속 센서"- @ 1분 14초](https://youtu.be/91VGmdSlbo4?t=1m14s)(유튜브) | 46.225806 | 257 | 0.728542 | kor_Hang | 0.999803 |
2fd8c690e96c10ac4b0bc4ee70fbe8693c638d1d | 619 | md | Markdown | solution/tree/124-u.md | muhlenXi/enjoy-algorithm | a2e2edca96dc5706c494415f9e2e96f62d045fb3 | [
"Apache-2.0"
] | null | null | null | solution/tree/124-u.md | muhlenXi/enjoy-algorithm | a2e2edca96dc5706c494415f9e2e96f62d045fb3 | [
"Apache-2.0"
] | null | null | null | solution/tree/124-u.md | muhlenXi/enjoy-algorithm | a2e2edca96dc5706c494415f9e2e96f62d045fb3 | [
"Apache-2.0"
] | null | null | null |
```python
# 124
def maxPathSum(self, root: TreeNode) -> int:
maxValNode = TreeNode(root.val)
self.oneSideMax(root, maxValNode)
return maxValNode.val
# 计算子树最大路径和
def oneSideMax(self, root: TreeNode, maxValNode: TreeNode):
if root == None:
return 0
# 计算左子树最大路径和
left = self.oneSideMax(root.left, maxValNode)
# 计算右子树最大路径和
right = self.oneSideMax(root.right, maxValNode)
# 统计当前路径和与历史最大路径和
maxValNode.val = max(maxValNode.val, left + root.val + right)
maxVal = max(left, right) + root.val
if maxVal < 0: # 如果最大路径和小于0，则放弃该路径和
return 0
return maxVal
``` | 23.807692 | 65 | 0.662359 | yue_Hant | 0.964957 |
2fd8f417ccad4d2dbbb1d9610b095b5b4bafd9bf | 1,579 | md | Markdown | Solutions/0968. 监控二叉树.md | itcharge/LeetCode-Py | 4330344de6fc1c1a4d81354ecb00f992480c90f8 | [
"MIT"
] | 1,237 | 2021-01-27T02:41:17.000Z | 2022-03-31T07:08:30.000Z | Solutions/0968. 监控二叉树.md | itcharge/LeetCode-Py | 4330344de6fc1c1a4d81354ecb00f992480c90f8 | [
"MIT"
] | 1 | 2022-01-20T02:18:42.000Z | 2022-01-21T01:10:59.000Z | Solutions/0968. 监控二叉树.md | itcharge/LeetCode-Py | 4330344de6fc1c1a4d81354ecb00f992480c90f8 | [
"MIT"
] | 245 | 2021-11-02T04:13:45.000Z | 2022-03-30T15:42:46.000Z | ## [0968. 监控二叉树](https://leetcode-cn.com/problems/binary-tree-cameras/)
- 标签：树、深度优先搜索、动态规划、二叉树
- 难度：困难
## 题目大意
给定一个二叉树，需要在树的节点上安装摄像头。节点上的每个摄影头都可以监视其父节点、自身及其直接子节点。
计算监控树的所有节点所需的最小摄像头数量。
- 示例 1：
```
输入：[0,0,null,0,0]
输出：1
解释：如图所示，一台摄像头足以监控所有节点。
```
- 示例 2：
```
输入：[0,0,null,0,null,0,null,null,0]
输出：2
解释：需要至少两个摄像头来监视树的所有节点。 上图显示了摄像头放置的有效位置之一。
```
## 解题思路
根据题意可知，一个摄像头的有效范围为 3 层：父节点、自身及其直接子节点。而约是下层的节点就越多，所以摄像头应该优先满足下层节点。可以使用后序遍历的方式遍历二叉树的节点，这样就可以优先遍历叶子节点。
对于每个节点，利用贪心思想，可以确定三种状态：
- 第一种状态：该节点无覆盖
- 第二种状态：该节点已经装上了摄像头
- 第三种状态：该节点已经覆盖
为了让摄像头数量最少，我们要尽量让叶⼦节点的⽗节点安装摄像头，这样才能摄像头的数量最少。对此我们应当分析当前节点和左右两侧子节点的覆盖情况。
先来考虑空节点，空节点应该算作已经覆盖状态。
再来考虑左右两侧子覆盖情况：
- 如果左节点或者右节点都无覆盖，则当前节点需要装上摄像头，答案 res 需要 + 1。
- 如果左节点已经覆盖或者右节点已经装上了摄像头，则当前节点已经覆盖。
- 如果左节点右节点都已经覆盖，则当前节点无覆盖。
根据以上条件就可以写出对应的后序遍历代码。
## 代码
```Python
class Solution:
res = 0
def traversal(self, cur: TreeNode) -> int:
if not cur:
return 3
left = self.traversal(cur.left)
right = self.traversal(cur.right)
if left == 1 or right == 1:
self.res += 1
return 2
if left == 2 or right == 2:
return 3
if left == 3 and right == 3:
return 1
return -1
def minCameraCover(self, root: TreeNode) -> int:
self.res = 0
if self.traversal(root) == 1:
self.res += 1
return self.res
```
| 18.360465 | 99 | 0.653578 | yue_Hant | 0.867673 |
2fd90834f6d4876924c9f1d182c812569e8e2e31 | 176 | md | Markdown | data/landsat/README.md | pomadchin/geospark-tutorial | 55638a64815ddedb2ac0bce8d8646ac41e0b764a | [
"Apache-2.0"
] | 12 | 2016-11-18T01:36:50.000Z | 2021-12-14T02:17:06.000Z | data/landsat/README.md | pomadchin/geospark-tutorial | 55638a64815ddedb2ac0bce8d8646ac41e0b764a | [
"Apache-2.0"
] | null | null | null | data/landsat/README.md | pomadchin/geospark-tutorial | 55638a64815ddedb2ac0bce8d8646ac41e0b764a | [
"Apache-2.0"
] | 6 | 2016-10-13T18:07:39.000Z | 2021-10-30T07:35:17.000Z | Place the un-tarred GeoTiffs of the landsat image in this folder.
Image can be found at https://s3.amazonaws.com/geotrellis-sample-datasets/landsat/LC80140322014139LGN00.tar.bz | 88 | 110 | 0.829545 | eng_Latn | 0.808223 |
2fd9b17d3adf8ba84ba1cb01857d33b4d1eadb2f | 649 | md | Markdown | packages/focus-dom/README.md | jneander/jlnio | 6a6c76ea81126f9d9a9fa6857e6ec31c3b9ab936 | [
"MIT"
] | 1 | 2020-07-23T19:51:42.000Z | 2020-07-23T19:51:42.000Z | packages/focus-dom/README.md | jneander/jlnio | 6a6c76ea81126f9d9a9fa6857e6ec31c3b9ab936 | [
"MIT"
] | 14 | 2018-03-10T18:24:05.000Z | 2022-03-02T03:32:49.000Z | packages/focus-dom/README.md | jneander/jneander | 6a6c76ea81126f9d9a9fa6857e6ec31c3b9ab936 | [
"MIT"
] | null | null | null | # @jneander/focus-dom
Focus management for the DOM
## Next Steps
* Add examples of borrowing from outside Focus.
### Questions
* How to ensure everything works correctly while window is in background?
* What might need to happen when the element hierarchy rearranges?
### Unknown Behaviors to Consider
* automatic reconciliation
* might depend on more fine-grained fallback rules
* i.e. removed borrowers release to lenders instead of fallback
* observability
* onFocus, onBlur for the FocusRegion?
* alternately, at the root Focus container
* iframes in focus
* focus fallback out of an iframe
* focus falling into an iframe
| 25.96 | 73 | 0.758089 | eng_Latn | 0.998078 |
2fdae9c53578194ab89d4efd932c32514b38afd0 | 602 | md | Markdown | README.md | hfassold/omni_optimizer | 2858bde11e244baa81fdb40335f70c28f7a1c1f3 | [
"MIT"
] | 1 | 2022-03-16T03:14:04.000Z | 2022-03-16T03:14:04.000Z | README.md | hfassold/omni_optimizer | 2858bde11e244baa81fdb40335f70c28f7a1c1f3 | [
"MIT"
] | null | null | null | README.md | hfassold/omni_optimizer | 2858bde11e244baa81fdb40335f70c28f7a1c1f3 | [
"MIT"
] | null | null | null | # omni_optimizer
A wrapper for several SoA adaptive-gradient optimizer (Adam/AdamW/EAdam/AdaBelief/AdaMomentum/AdaFamily) via one API, including my novel 'AdaFamily' algorithm.
Regarding 'AdaFamily', see the arxiv preprint at https://arxiv.org/abs/2203.01603 (submitted to ISPR 2022 conference).
Setting 'myu' to either 0.25 oder 0.75 might be the best choice according to experiments (see preprint).
The main class to use is the class 'OmniOptimizer' (file 'omni_optimizer.py').
See https://github.com/hfassold/nlp_finetuning_adafamily for an application where AdaFamily is used for NLP finetuning.
| 66.888889 | 159 | 0.799003 | eng_Latn | 0.956317 |
2fdb1a1bcc9a382862618fc6b5a7abb48055a69f | 1,272 | md | Markdown | AddUserWithConfigApi/README.md | joshooaj/mipsdk-samples-plugin | 0bb103aad9d1e9dfd0b13095437d86cc78d17c6e | [
"MIT"
] | 6 | 2021-02-25T11:52:52.000Z | 2022-01-30T13:37:55.000Z | AddUserWithConfigApi/README.md | joshooaj/mipsdk-samples-plugin | 0bb103aad9d1e9dfd0b13095437d86cc78d17c6e | [
"MIT"
] | null | null | null | AddUserWithConfigApi/README.md | joshooaj/mipsdk-samples-plugin | 0bb103aad9d1e9dfd0b13095437d86cc78d17c6e | [
"MIT"
] | 5 | 2021-03-04T12:44:19.000Z | 2022-03-30T09:03:44.000Z | ---
description: The AddUserWithConfigApi plugin demonstrates how the
strongly typed configuration API classes can be used from a Smart Client plugin. It enables a
Smart Client operator to create a new basic user and add it to a
chosen role.
keywords:
- Plug-in integration
- Smart Client
lang: en-US
title: Smart Client Add User
---
# Smart Client Add User
The AddUserWithConfigApi plugin demonstrates how the strongly typed configuration API classes
can be used from a Smart Client plugin. It enables a Smart Client
operator to create a new basic user and add it to a chosen role.
## How to use it
- Start the Smart Client. Login to XProtect system
- Find the 'Add User Side panel'
- Enter a user name and a password, select a role and press 'Commit'
- Check the 'Result' pane for the result of the request
## The sample demonstrates
- How to create and modify object using configuration API
## Using
- VideoOS.Platform.ConfigurationItems.RoleFolder
- VideoOS.Platform.ConfigurationItems.BasicUserFolder
- VideoOS.Platform.ConfigurationItems.Role
## Visual Studio C\# project
- [AddUserWithConfigApi.csproj](javascript:openLink('..\\\\PluginSamples\\\\AddUserWithConfigApi\\\\AddUserWithConfigApi.csproj');)
| 31.02439 | 133 | 0.767296 | eng_Latn | 0.724509 |
2fdc4515b2c9bf402989dde91fb3a38706f3379c | 64 | md | Markdown | README.md | Feiox/eqiq | 68d9baed4356353b45796a3fad3b838bd7eeb640 | [
"Apache-2.0"
] | null | null | null | README.md | Feiox/eqiq | 68d9baed4356353b45796a3fad3b838bd7eeb640 | [
"Apache-2.0"
] | null | null | null | README.md | Feiox/eqiq | 68d9baed4356353b45796a3fad3b838bd7eeb640 | [
"Apache-2.0"
] | null | null | null | # eqiq
A protocol for data transmission, and its implementation
| 21.333333 | 56 | 0.8125 | eng_Latn | 0.993297 |
2fdc5beb070f0a23143dff904a487e552bf63171 | 283 | md | Markdown | docs/api-reference/classes/NSRecurrenceDate/SetTooltip.md | stianol/crmscript | be1ad4f3a967aee2974e9dc7217255565980331e | [
"MIT"
] | null | null | null | docs/api-reference/classes/NSRecurrenceDate/SetTooltip.md | stianol/crmscript | be1ad4f3a967aee2974e9dc7217255565980331e | [
"MIT"
] | null | null | null | docs/api-reference/classes/NSRecurrenceDate/SetTooltip.md | stianol/crmscript | be1ad4f3a967aee2974e9dc7217255565980331e | [
"MIT"
] | null | null | null | ---
uid: crmscript_ref_NSRecurrenceDate_SetTooltip_String_p_0
title: NSRecurrenceDate.SetTooltip(String p_0)
intellisense: NSRecurrenceDate.SetTooltip
keywords: SetTooltip(String)
so.topic: reference
---
# NSRecurrenceDate.SetTooltip(String p_0)
Tooltip describing any conflicts.
| 21.769231 | 57 | 0.837456 | kor_Hang | 0.629077 |
2fdcb8710490b96b1401f1f284ac983f590a4db9 | 30 | md | Markdown | _notes/character-bmi.md | tylerhslee/digital-garden-jekyll-template | f49989f38ed22d997dd843c03f2a7d2160109ae6 | [
"MIT"
] | null | null | null | _notes/character-bmi.md | tylerhslee/digital-garden-jekyll-template | f49989f38ed22d997dd843c03f2a7d2160109ae6 | [
"MIT"
] | null | null | null | _notes/character-bmi.md | tylerhslee/digital-garden-jekyll-template | f49989f38ed22d997dd843c03f2a7d2160109ae6 | [
"MIT"
] | null | null | null | ---
title: Character BMI
---
| 6 | 20 | 0.566667 | eng_Latn | 0.962025 |
2fdd2a864da4c0401c908f071ed654371f259da7 | 995 | md | Markdown | S2M3_Task_7/Alt_rust/README.md | code-signal/code-signal-arcade-bloomtech | faa86f055b22d696f5603bf29a79f5189faf41fc | [
"MIT"
] | null | null | null | S2M3_Task_7/Alt_rust/README.md | code-signal/code-signal-arcade-bloomtech | faa86f055b22d696f5603bf29a79f5189faf41fc | [
"MIT"
] | null | null | null | S2M3_Task_7/Alt_rust/README.md | code-signal/code-signal-arcade-bloomtech | faa86f055b22d696f5603bf29a79f5189faf41fc | [
"MIT"
] | null | null | null | ---
layout: home
title: S2M3 - Task 7 - rust
#permalink: index.html # in case of we remove the index.md file, this doc will be the index page
---
<div class="row">
<div class="columnStmt" markdown="1">
## Description
------
[Back --> ](../README.md)
This function should scan an array for certain elements and remove them.
**Example**
Input:
```
a == [0, 5, 6, 2, 7, 8, 5, 3, 4, 5]
x = 5 Remove all 5s
```
- Output:
```
[0, 6, 2, 7, 8, 3, 4]
```
**Input/Output**
* **[execution time limit] 4 seconds (js)**
* **[input] array.integer a**
The input array.
*Constraints*
1 <= a.length <= 100
* **[input] array.integer x**
The value to delete.
*Constraints*
0 <= index < a.length
* **[output] array.integer**
The resulting array.
**[JavaScript (ES6)] Syntax Tips**
</div>
<div class="columnSol" markdown="1">
## Solution
------
{% highlight javascript linenos=table %}
{% include_relative solution.js %}
{% endhighlight %}
</div>
</div> | 14.014085 | 96 | 0.59397 | eng_Latn | 0.809023 |
2fdd6c35b7168ff0996e7304f2c6b882cd96481b | 3,747 | md | Markdown | articles/cognitive-services/LUIS/luis-reference-prebuilt-phonenumber.md | Ksantacr/azure-docs.es-es | d3abf102433fd952aafab2c57a55973ea05a9acb | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/cognitive-services/LUIS/luis-reference-prebuilt-phonenumber.md | Ksantacr/azure-docs.es-es | d3abf102433fd952aafab2c57a55973ea05a9acb | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/cognitive-services/LUIS/luis-reference-prebuilt-phonenumber.md | Ksantacr/azure-docs.es-es | d3abf102433fd952aafab2c57a55973ea05a9acb | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Entidades precompiladas Phonenumber
titleSuffix: Azure
description: Este artículo contiene información de la entidad precompilada de número de teléfono en Language Understanding (LUIS).
services: cognitive-services
author: diberry
manager: nitinme
ms.custom: seodec18
ms.service: cognitive-services
ms.subservice: language-understanding
ms.topic: article
ms.date: 05/07/2019
ms.author: diberry
ms.openlocfilehash: 43d0b855c25ed10b074d99b247ee56dc2ba7769b
ms.sourcegitcommit: f6ba5c5a4b1ec4e35c41a4e799fb669ad5099522
ms.translationtype: MT
ms.contentlocale: es-ES
ms.lasthandoff: 05/06/2019
ms.locfileid: "65146196"
---
# <a name="phone-number-prebuilt-entity-for-a-luis-app"></a>Entidad creada previamente número de teléfono para una aplicación de LUIS
La entidad `phonenumber` extrae una variedad de números de teléfono, incluido el código de país. Dado que esta entidad ya está entrenada, no se necesita agregar expresiones de ejemplo que a la aplicación. La entidad `phonenumber` se admite solamente en la referencia cultural `en-us`.
## <a name="types-of-a-phone-number"></a>Tipos de un número de teléfono
`Phonenumber` se administra desde el [reconocedores texto](https://github.com/Microsoft/Recognizers-Text/blob/master/Patterns/Base-PhoneNumbers.yaml) repositorio de GitHub
## <a name="resolution-for-this-prebuilt-entity"></a>Resolución para esta entidad creados previamente
### <a name="api-version-2x"></a>Versión de API 2.x
En el siguiente ejemplo, se muestra la resolución de la entidad **builtin.phonenumber**.
```json
{
"query": "my mobile is 1 (800) 642-7676",
"topScoringIntent": {
"intent": "None",
"score": 0.8448457
},
"intents": [
{
"intent": "None",
"score": 0.8448457
}
],
"entities": [
{
"entity": "1 (800) 642-7676",
"type": "builtin.phonenumber",
"startIndex": 13,
"endIndex": 28,
"resolution": {
"score": "1",
"value": "1 (800) 642-7676"
}
}
]
}
```
### <a name="preview-api-version-3x"></a>Versión de API preliminar 3.x
El siguiente JSON es con el `verbose` parámetro establecido en `false`:
```json
{
"query": "my mobile is 1 (800) 642-7676",
"prediction": {
"normalizedQuery": "my mobile is 1 (800) 642-7676",
"topIntent": "None",
"intents": {
"None": {
"score": 0.592748761
}
},
"entities": {
"phonenumber": [
"1 (800) 642-7676"
]
}
}
}
```
El siguiente JSON es con el `verbose` parámetro establecido en `true`:
```json
{
"query": "my mobile is 1 (800) 642-7676",
"prediction": {
"normalizedQuery": "my mobile is 1 (800) 642-7676",
"topIntent": "None",
"intents": {
"None": {
"score": 0.592748761
}
},
"entities": {
"phonenumber": [
"1 (800) 642-7676"
],
"$instance": {
"phonenumber": [
{
"type": "builtin.phonenumber",
"text": "1 (800) 642-7676",
"startIndex": 13,
"length": 16,
"score": 1,
"modelTypeId": 2,
"modelType": "Prebuilt Entity Extractor"
}
]
}
}
}
}
```
## <a name="next-steps"></a>Pasos siguientes
Obtenga información acerca de las entidades de [porcentaje](luis-reference-prebuilt-percentage.md), [número de teléfono](luis-reference-prebuilt-number.md) y [temperatura](luis-reference-prebuilt-temperature.md).
| 30.463415 | 285 | 0.59114 | spa_Latn | 0.591296 |
2fdde46e1cd80454ee7cd5cf5ce6bc57b5dc16f5 | 892 | md | Markdown | CHANGELOG.md | aubricus/aubricus.github.io | 2f4ce9c96e57bed719a321b31958faafc6b060b5 | [
"CC-BY-4.0"
] | null | null | null | CHANGELOG.md | aubricus/aubricus.github.io | 2f4ce9c96e57bed719a321b31958faafc6b060b5 | [
"CC-BY-4.0"
] | null | null | null | CHANGELOG.md | aubricus/aubricus.github.io | 2f4ce9c96e57bed719a321b31958faafc6b060b5 | [
"CC-BY-4.0"
] | null | null | null | # Aubz.me Changelog
> Changes to posts are not recorded here. Complete post file history is avaialbe from GitHub or the git repository.
## v1.1.2
- removed hidden posts from "next post"
## v1.1.1
- added ability to create hidden posts
## v1.1.0
Various minor bugfixes, improvements
-refactored pygments
- pygment theme is now configurable
- added pygment config for dark and light themes (wip)
- added 'pretty' permalink config to config.yml
- minor fixes to post layout
- minor fixes to index page
- some refactoring on post and post list styles to make them consistent
- added blockquote styling
- added new pastel color palette
- minor updates to scaffolding
- minor updates to sidebar
## v1.0.2
- removed resume link from about
- minor updates to about copy
- minor updates to post / generic content styles
## v1.0.1
- removed email from sidebar
## v1.0.0
- initial release
| 21.238095 | 115 | 0.751121 | eng_Latn | 0.996273 |
2fdec93bc5707e07bbec84639949d3e9792d0ed2 | 4,450 | md | Markdown | articles/container-service/kubernetes/container-service-kubernetes-coscale.md | changeworld/azure-docs.tr-tr | a6c8b9b00fe259a254abfb8f11ade124cd233fcb | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/container-service/kubernetes/container-service-kubernetes-coscale.md | changeworld/azure-docs.tr-tr | a6c8b9b00fe259a254abfb8f11ade124cd233fcb | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/container-service/kubernetes/container-service-kubernetes-coscale.md | changeworld/azure-docs.tr-tr | a6c8b9b00fe259a254abfb8f11ade124cd233fcb | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: (AmortismanA Uğradı) CoScale ile Azure Kubernetes kümesini izleme
description: CoScale'i kullanarak Azure Kapsayıcı Hizmeti'nde bir Kubernetes kümesini izleme
author: fryckbos
ms.service: container-service
ms.topic: conceptual
ms.date: 05/22/2017
ms.author: saudas
ms.custom: mvc
ms.openlocfilehash: f1d0ca1ffc2e7a3d645ac5acbaafdf45f85550be
ms.sourcegitcommit: 2ec4b3d0bad7dc0071400c2a2264399e4fe34897
ms.translationtype: MT
ms.contentlocale: tr-TR
ms.lasthandoff: 03/27/2020
ms.locfileid: "76271107"
---
# <a name="deprecated-monitor-an-azure-container-service-kubernetes-cluster-with-coscale"></a>(AmortismanA Uğradı) CoScale ile Azure Kapsayıcı Hizmeti Kubernetes kümesini izleme
[!INCLUDE [ACS deprecation](../../../includes/container-service-kubernetes-deprecation.md)]
Bu makalede, Azure Kapsayıcı Hizmeti'ndeki Kubernetes kümenizdeki tüm düğümleri ve kapsayıcıları izlemek için [CoScale](https://web.archive.org/web/20180317071550/https://www.coscale.com/) aracısını nasıl dağıtabileceğinizi gösteriyoruz. Bu yapılandırma için CoScale'de bir hesaba ihtiyacınız var.
## <a name="about-coscale"></a>CoScale Hakkında
CoScale, çeşitli orkestrasyon platformlarında tüm kaplardan ölçümler ve olaylar toplayan bir izleme platformudur. CoScale, Kubernetes ortamları için tam yığın izleme hizmeti sunar. Yığındaki tüm katmanlar için görselleştirmeler ve analizler sağlar: işletim sistemi, Kubernetes, Docker ve kaplarınızın içinde çalışan uygulamalar. CoScale birkaç yerleşik izleme panosu sunar ve operatörlerin ve geliştiricilerin altyapı ve uygulama sorunlarını hızlı bir şekilde bulmalarına olanak sağlamak için yerleşik anormallik algılamasına sahiptir.
Bu makalede gösterildiği gibi, Bir SaaS çözümü olarak CoScale çalıştırmak için bir Kubernetes kümesine aracılar yükleyebilirsiniz. Verilerinizi yerinde tutmak istiyorsanız, CoScale şirket içi yükleme için de kullanılabilir.
## <a name="prerequisites"></a>Ön koşullar
Öncelikle bir [CoScale hesabı oluşturmanız](https://web.archive.org/web/20170507123133/https://www.coscale.com/free-trial)gerekir.
Bu izlenecek yol, [Azure Kapsayıcı Hizmeti'ni kullanarak bir Kubernetes kümesi oluşturduğunuzu](container-service-kubernetes-walkthrough.md)varsayar.
Ayrıca `az` Azure CLI ve `kubectl` araçları yüklü olduğunu varsayar.
Aracı çalıştırarak yüklü `az` yorurarak test edebilirsiniz:
```azurecli
az --version
```
`az` Aracı yüklü değilseniz, [burada](/cli/azure/install-azure-cli)talimatlar vardır.
Aracı çalıştırarak yüklü `kubectl` yorurarak test edebilirsiniz:
```bash
kubectl version
```
`kubectl` Yüklemediyseniz çalıştırabilirsiniz:
```azurecli
az acs kubernetes install-cli
```
## <a name="installing-the-coscale-agent-with-a-daemonset"></a>Bir DaemonSet ile CoScale aracıyükleme
[DaemonSets](https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/) kümedeki her ana bilgisayarda bir kapsayıcının tek bir örneğini çalıştırmak için Kubernetes tarafından kullanılır.
CoScale ajanı gibi izleme ajanlarını çalıştırmak için mükemmeller.
CoScale'de oturum açtıktan sonra, DaemonSet kullanarak kümenize CoScale aracıları yüklemek için [aracılar sayfasına](https://app.coscale.com/) gidin. CoScale Kullanıcı Aracı, bir aracı oluşturmak ve tam Kubernetes kümenizi izlemeye başlamak için kılavuzlu yapılandırma adımları sağlar.
Kümedeki aracıyı başlatmak için verilen komutu çalıştırın:
İşte bu kadar! Aracılar çalışmaya başladıktan sonra, birkaç dakika içinde konsoldaki verileri görmeniz gerekir. [Kümenizin](https://app.coscale.com/) özetini görmek, ek yapılandırma adımları gerçekleştirmek ve **Kubernetes kümesine genel bakış**gibi panolara bakın.
CoScale aracısı kümedeki yeni makinelerde otomatik olarak dağıtılır. Aracı, yeni bir sürüm yayımlandığında otomatik olarak güncellenir.
## <a name="next-steps"></a>Sonraki adımlar
CoScale izleme çözümleri hakkında daha fazla bilgi için [CoScale belgelerine](https://web.archive.org/web/20180415164304/http://docs.coscale.com:80/) ve [bloguna](https://web.archive.org/web/20170501021344/http://www.coscale.com:80/blog) bakın.
| 52.97619 | 535 | 0.816854 | tur_Latn | 0.997716 |
2fdffd29b3a289b1fd532909398fa3b40cf96e76 | 215 | md | Markdown | tests/res/cli/ignore_missing/10/README.md | ssato/python-anyconfig | 09af1950f3226759932f5168d52f5e06ab88815c | [
"MIT"
] | 213 | 2015-01-14T22:09:20.000Z | 2022-02-02T17:23:41.000Z | tests/res/cli/ignore_missing/10/README.md | ssato/python-anyconfig | 09af1950f3226759932f5168d52f5e06ab88815c | [
"MIT"
] | 120 | 2015-03-13T15:47:43.000Z | 2022-03-31T01:55:34.000Z | tests/res/cli/ignore_missing/10/README.md | ssato/python-anyconfig | 09af1950f3226759932f5168d52f5e06ab88815c | [
"MIT"
] | 34 | 2015-01-12T05:03:30.000Z | 2021-09-09T14:40:56.000Z | # Test cases for anyconfig\_cli
- 10.json + o/10.json: an input (this input file will be replaced with a file doees not exist) with '--ignore-missing' and '-O json' options to load and dump a JSON data as a string
| 53.75 | 181 | 0.730233 | eng_Latn | 0.987294 |
2fe06120f23369ff4daa5b6a51fa90e4d590eddd | 2,300 | md | Markdown | src/intersection/for-loops-rayane/README.md | perezrei/practice-code-review | ef534f2f1cddd0cd7d340f47600cc5f095900dc8 | [
"MIT"
] | 1 | 2021-07-30T11:18:07.000Z | 2021-07-30T11:18:07.000Z | src/intersection/for-loops-rayane/README.md | perezrei/practice-code-review | ef534f2f1cddd0cd7d340f47600cc5f095900dc8 | [
"MIT"
] | 10 | 2021-07-27T12:29:26.000Z | 2021-07-30T17:52:55.000Z | src/intersection/for-loops-rayane/README.md | perezrei/practice-code-review | ef534f2f1cddd0cd7d340f47600cc5f095900dc8 | [
"MIT"
] | 2 | 2021-07-25T16:32:55.000Z | 2021-07-30T10:03:44.000Z | # Intersection: Use for-loop
Write a function that finds all the values shared between two arrays.
```js
/**
* Creates an array of values that are in both the first and the second arrays.
*
* Repeated values are not duplicated in the return value, and the order of result values are determined by the first array.
*
* **Note:** This function returns a new array, and has no side-effects.
*
* @param {Array} [array=[]] - The array to inspect.
* @param {Array} [values=[]] - The values to include.
* @returns {Array} Returns the new array of filtered values.
* @example
*
* intersection([2, 1], [2, 3]);
* // -> [2]
*
* @example
*
* intersection([2, 1, 2], [2, 3]);
* // -> [2]
*/
```
---
## Strategy
I chose to used nested for-loops, push() and filter() methods to solve this challenge.
1. Create a new empty array to store the common items.
2. Loop through array1 and iterate it from beginning to the end.
3. Loop through array2 and iterate it from beginning to the end.
4. Compare each item from array1 to array2 and if it finds any common item then return to a new array.
5. Use a second function to filter duplicate elements and get only unique values out of the matched values.
---
## Implementation
- for-loop - It iterates through two arrays.
- .push() - It places the common elements of two arrays to a new array.
- .filter() - It discards repeating elements from an array.
---
## Use Cases
You could use this function to find the common friends of a group of users.
```js
const findMutualFriends = (list1 = [], list2 = []) => {
const commonFriends = [];
for (let i = 0; i < list1.length; i++) {
for (let j = 0; j < list2.length; j++) {
if (list1[i] === list2[j]) {
commonFriends.push(list1[i]);
}
}
}
const removeDuplicateValues = commonFriends.filter((value, index) => {
return commonFriends.indexOf(value) === index;
});
return removeDuplicateValues;
};
const listOfMutualFriends = findMutualFriends(
['Bill', 'Dianna', 'George', 'Fiona', 'Felicity'],
['Karen', 'Fiona', 'Harry', 'Bill'],
);
console.log(listOfMutualFriends); //["Bill", "Fiona"]
```
---
## Inspiration
This article from [JavaScript in Plain English](https://javascript.plainenglish.io/typescript-intersection-best-practice-6a7de85bb2f1).
| 27.710843 | 135 | 0.673478 | eng_Latn | 0.986358 |
2fe1ad3de3b21721a5be489357a56b4f99d42c80 | 957 | md | Markdown | .github/ISSUE_TEMPLATE/BUG_REPORT.md | linjunjie0834/YiShaAdmin | 77b671923230947027ab8945074b004fa6560ad0 | [
"MIT"
] | 1,779 | 2019-10-01T16:34:16.000Z | 2022-03-31T05:55:43.000Z | .github/ISSUE_TEMPLATE/BUG_REPORT.md | chunjieyaya/YiShaAdmin | 21b6d9b43b3effa58015d3c9c8db24b7308f4bf8 | [
"MIT"
] | 102 | 2019-10-15T05:51:17.000Z | 2022-03-18T01:18:32.000Z | .github/ISSUE_TEMPLATE/BUG_REPORT.md | chunjieyaya/YiShaAdmin | 21b6d9b43b3effa58015d3c9c8db24b7308f4bf8 | [
"MIT"
] | 665 | 2019-10-01T00:47:22.000Z | 2022-03-31T14:07:33.000Z | ---
name: Bug report
about: Create a report to help us improve
labels:
---
<!-- 当然，你可以用中文写。 -->
<!-- PLEASE READ THE FOLLOWING INSTRUCTIONS -->
<!--
- Try to search for your issue, it may have already been answered or even fixed in the development version.
- Check if the issue is reproducible with the latest stable version of YiShaAdmin.
- It is **required** that you clearly describe the steps necessary to reproduce the issue.
- It is recommended that you make a screenshots/animated GIFs to demonstrate your issue.
- If your issue is resolved but still open, don’t hesitate to close it. In case you found a solution by yourself, it could be helpful to explain how you fixed it.
-->
### Overview of the problem
### Description
<!--Description of the bug-->
### Steps to reproduce
<!--
1. First Step
2. Second Step
3. and so on...
-->
### Expected behavior
<!--What you expected to happen-->
### Actual behavior
<!--What actually happened-->
| 24.538462 | 162 | 0.712644 | eng_Latn | 0.998479 |
2fe2cea23640e485e61b781a027a463af2a1e58f | 454 | md | Markdown | README.md | tgyhlsb/iPath | 20630e426041d2c1e26137ca1a3f1c40fcfb3e53 | [
"MIT"
] | null | null | null | README.md | tgyhlsb/iPath | 20630e426041d2c1e26137ca1a3f1c40fcfb3e53 | [
"MIT"
] | null | null | null | README.md | tgyhlsb/iPath | 20630e426041d2c1e26137ca1a3f1c40fcfb3e53 | [
"MIT"
] | null | null | null | # iPath
Fetches map and routes from backend. Allows users to follow an alternative path when a route is selected.
## Requirements
- iOS 10+
- Swift 3+
- Xcode 8+
- Cocoapods 1.1.0+
## Installation
Cocoapods for Swift 3 is the 1.1.0 version, but it is not yet flagged as the stable version. To install use :
sudo gem install cocoapods --pre
pod update
Install dependencies :
cd ./iPath
pod install
Open workspace
open iPath.xcworkspace
| 15.655172 | 109 | 0.729075 | eng_Latn | 0.980966 |
2fe2d7f126adf8c6332adb51b6b82ca329b12f6d | 24,357 | md | Markdown | articles/azure-functions/durable/durable-functions-entities.md | BhernardoViana/azure-docs.pt-br | 674a5e028fda45bebb645a39d19250cc7ca9c053 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/azure-functions/durable/durable-functions-entities.md | BhernardoViana/azure-docs.pt-br | 674a5e028fda45bebb645a39d19250cc7ca9c053 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/azure-functions/durable/durable-functions-entities.md | BhernardoViana/azure-docs.pt-br | 674a5e028fda45bebb645a39d19250cc7ca9c053 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Entidades duráveis – Azure Functions
description: Saiba o que são entidades duráveis e como usá-las na extensão Durable Functions do Azure Functions.
author: cgillum
ms.topic: overview
ms.date: 11/02/2019
ms.author: azfuncdf
ms.openlocfilehash: aa4d1c4bfab349659c42a34ca5a73f676a2ea2b8
ms.sourcegitcommit: d6b68b907e5158b451239e4c09bb55eccb5fef89
ms.translationtype: HT
ms.contentlocale: pt-BR
ms.lasthandoff: 11/20/2019
ms.locfileid: "74232923"
---
# <a name="entity-functions"></a>Funções de entidade
As funções de entidade definem operações para leitura e atualização de pequenas partes de estado, conhecidas como *entidades duráveis*. Como as funções de orquestrador, as funções de entidade são funções com um tipo de gatilho especial, o *gatilho de entidade*. Ao contrário das funções de orquestrador, as funções de entidade gerenciam o estado de uma entidade explicitamente, em vez de representar implicitamente o estado por meio do fluxo de controle.
As entidades fornecem um meio para escalar horizontalmente os aplicativos, distribuindo o trabalho entre várias entidades, cada uma com um estado de tamanho modesto.
> [!NOTE]
> As funções de entidade e a funcionalidade relacionada estão disponíveis apenas nas Durable Functions 2.0 e superior.
## <a name="general-concepts"></a>Conceitos gerais
As entidades se comportam de modo um pouco semelhante a pequenos serviços que se comunicam por meio de mensagens. Cada entidade tem uma identidade exclusiva e um estado interno (se existir). Assim como os serviços ou objetos, as entidades executam operações quando é solicitado a elas que o façam. Quando uma operação é executada, ela pode atualizar o estado interno da entidade. Ela também pode chamar serviços externos e aguardar uma resposta. As entidades se comunicam com outras entidades, orquestrações e clientes usando mensagens que são enviadas implicitamente por meio de filas confiáveis.
Para evitar conflitos, todas as operações em uma única entidade têm garantia de execução em série, ou seja, uma após a outra.
### <a name="entity-id"></a>ID da Entidade
As entidades são acessadas por meio de um identificador exclusivo, a *ID da entidade*. Uma ID de entidade é um par de cadeias de caracteres que identifica exclusivamente uma instância de entidade. Ele consiste em um(a):
* **Nome de entidade**, que é um nome que identifica o tipo da entidade. Um exemplo é "Counter". Esse nome deve corresponder ao nome da função de entidade que implementa a entidade. Ele não diferencia maiúsculas e minúsculas.
* **Chave da entidade**, que é uma cadeia de caracteres que identifica exclusivamente a entidade entre todas as outras entidades de mesmo nome. Um exemplo é um GUID.
Por exemplo, uma função de entidade `Counter` pode ser usada para manter a pontuação em um jogo online. Cada instância do jogo terá uma ID de entidade exclusiva, como `@Counter@Game1` e `@Counter@Game2`. Todas as operações que direcionam uma entidade específica exigem a especificação de uma ID de entidade como um parâmetro.
### <a name="entity-operations"></a>Operações de entidade ###
Para invocar uma operação em uma entidade, especifique o(a):
* **ID da entidade** de destino.
* **Nome da operação**, que é uma cadeia de caracteres que especifica a operação a ser executada. Por exemplo, a entidade `Counter` poderia dar suporte às operações `add`, `get` ou `reset`.
* **Entrada da operação**, que é um parâmetro de entrada opcional para a operação. Por exemplo, a operação de adição pode usar um valor inteiro como a entrada.
As operações podem retornar um valor de resultado ou um resultado de erro, como um erro de JavaScript ou uma exceção .NET. Esse resultado ou erro pode ser observado por orquestrações que chamaram a operação.
Uma operação de entidade também pode criar, ler, atualizar e excluir o estado da entidade. O estado da entidade é sempre persistido no armazenamento de modo durável.
## <a name="define-entities"></a>Definir entidades
Atualmente, as duas APIs distintas para definição de entidades são uma:
**Sintaxe baseada em função**, em que as entidades são representadas como funções e as operações são expedidas explicitamente pelo aplicativo. Essa sintaxe funciona bem para entidades com estado simples, poucas operações ou um conjunto dinâmico de operações como em estruturas do aplicativo. Manter essa sintaxe pode ser uma tarefa entediante porque ela não captura erros de tipo no tempo de compilação.
**Sintaxe baseada em classe**, em que as entidades e operações são representadas por classes e métodos. Essa sintaxe produz um código mais fácil de ler e permite que as operações sejam invocadas de modo fortemente tipado. A sintaxe baseada em classe é uma camada fina sobre a sintaxe baseada em função, de modo que essas duas variantes podem ser usadas de maneira intercambiável no mesmo aplicativo.
### <a name="example-function-based-syntax---c"></a>Exemplo: Sintaxe baseada em função – C#
O código a seguir é um exemplo da entidade `Counter` simples implementada como uma função durável. Essa função define três operações, `add`, `reset` e `get`, cada uma delas opera em um estado de inteiro.
```csharp
[FunctionName("Counter")]
public static void Counter([EntityTrigger] IDurableEntityContext ctx)
{
switch (ctx.OperationName.ToLowerInvariant())
{
case "add":
ctx.SetState(ctx.GetState<int>() + ctx.GetInput<int>());
break;
case "reset":
ctx.SetState(0);
break;
case "get":
ctx.Return(ctx.GetState<int>());
break;
}
}
```
Para saber mais sobre a sintaxe baseada em função e como usá-la, confira [Sintaxe baseada em função](durable-functions-dotnet-entities.md#function-based-syntax).
### <a name="example-class-based-syntax---c"></a>Exemplo: Sintaxe baseada em classe – C#
O exemplo a seguir é uma implementação equivalente da entidade `Counter` usando métodos e classes.
```csharp
[JsonObject(MemberSerialization.OptIn)]
public class Counter
{
[JsonProperty("value")]
public int CurrentValue { get; set; }
public void Add(int amount) => this.CurrentValue += amount;
public void Reset() => this.CurrentValue = 0;
public int Get() => this.CurrentValue;
[FunctionName(nameof(Counter))]
public static Task Run([EntityTrigger] IDurableEntityContext ctx)
=> ctx.DispatchAsync<Counter>();
}
```
O estado dessa entidade é um objeto do tipo `Counter`, que contém um campo que armazena o valor atual do contador. Para persistir esse objeto no armazenamento, ele é serializado e desserializado pela biblioteca [Json.NET](https://www.newtonsoft.com/json).
Para obter mais informações sobre a sintaxe baseada em classe e como usá-la, confira [Definir classes de entidade](durable-functions-dotnet-entities.md#defining-entity-classes).
### <a name="example-javascript-entity"></a>Exemplo: entidade do JavaScript
As entidades duráveis estão disponíveis em JavaScript a partir da versão **1.3.0** do pacote npm `durable-functions`. O código a seguir é uma entidade `Counter` implementada como uma função durável escrita em JavaScript.
**function.json**
```json
{
"bindings": [
{
"name": "context",
"type": "entityTrigger",
"direction": "in"
}
],
"disabled": false
}
```
**index.js**
```javascript
const df = require("durable-functions");
module.exports = df.entity(function(context) {
const currentValue = context.df.getState(() => 0);
switch (context.df.operationName) {
case "add":
const amount = context.df.getInput();
context.df.setState(currentValue + amount);
break;
case "reset":
context.df.setState(0);
break;
case "get":
context.df.return(currentValue);
break;
}
});
```
## <a name="access-entities"></a>Acessar entidades
As entidades podem ser acessadas usando uma comunicação unidirecional ou bidirecional. A terminologia a seguir distingue as duas formas de comunicação:
* **Chamar** uma entidade usa a comunicação bidirecional (viagem de ida e volta). Você envia uma mensagem de operação à entidade e aguarda a mensagem de resposta antes de continuar. A mensagem de resposta pode fornecer um valor de resultado ou um resultado de erro, como um erro de JavaScript ou uma exceção .NET. Esse resultado ou erro é então observado pelo chamador.
* **Sinalizar** uma entidade usa a comunicação unidirecional (acionar e esquecer). Você envia uma mensagem de operação, mas não aguarda uma resposta. Embora haja garantia de que a mensagem seja entregue, o remetente não sabe quando e não pode observar qualquer erro ou valor de resultado.
As entidades podem ser acessadas de dentro de funções de cliente, de dentro de funções de orquestrador ou de dentro de funções de entidade. Nem todas as formas de comunicação são compatíveis com todos os contextos:
* De dentro dos clientes, você pode sinalizar as entidades e pode ler o estado da entidade.
* De dentro das orquestrações, você pode sinalizar as entidades e pode chamar entidades.
* De dentro das entidades, você pode sinalizar entidades.
Os exemplos a seguir ilustram essas várias maneiras de acessar entidades.
> [!NOTE]
> Para simplificar, os exemplos a seguir mostram a sintaxe superficialmente tipada para acessar entidades. Em geral, é recomendável [acessar entidades por meio de interfaces](durable-functions-dotnet-entities.md#accessing-entities-through-interfaces) porque isso fornece mais verificação de tipo.
### <a name="example-client-signals-an-entity"></a>Exemplo: o cliente sinaliza a uma entidade
Para acessar entidades de uma função comum do Azure, também conhecida como função de cliente, use a [associação de saída do cliente da entidade](durable-functions-bindings.md#entity-client). O exemplo a seguir mostra uma função disparada por fila sinalizando uma entidade que usa essa associação.
```csharp
[FunctionName("AddFromQueue")]
public static Task Run(
[QueueTrigger("durable-function-trigger")] string input,
[DurableClient] IDurableEntityClient client)
{
// Entity operation input comes from the queue message content.
var entityId = new EntityId(nameof(Counter), "myCounter");
int amount = int.Parse(input);
return client.SignalEntityAsync(entityId, "Add", amount);
}
```
```javascript
const df = require("durable-functions");
module.exports = async function (context) {
const client = df.getClient(context);
const entityId = new df.EntityId("Counter", "myCounter");
await context.df.signalEntity(entityId, "add", 1);
};
```
O termo *sinal* significa que a invocação de API de entidade é unidirecional e assíncrona. Não é possível que uma função do cliente saiba quando a entidade processou a operação. Além disso, a função do cliente não pode observar nenhum valor de resultado ou exceções.
### <a name="example-client-reads-an-entity-state"></a>Exemplo: o cliente lê o estado de uma entidade
As funções de cliente também podem consultar o estado de uma entidade, conforme mostrado no seguinte exemplo:
```csharp
[FunctionName("QueryCounter")]
public static async Task<HttpResponseMessage> Run(
[HttpTrigger(AuthorizationLevel.Function)] HttpRequestMessage req,
[DurableClient] IDurableEntityClient client)
{
var entityId = new EntityId(nameof(Counter), "myCounter");
JObject state = await client.ReadEntityStateAsync<JObject>(entityId);
return req.CreateResponse(HttpStatusCode.OK, state);
}
```
```javascript
const df = require("durable-functions");
module.exports = async function (context) {
const client = df.getClient(context);
const entityId = new df.EntityId("Counter", "myCounter");
return context.df.readEntityState(entityId);
};
```
As consultas de estado de entidade são enviadas ao armazenamento de acompanhamento Durável e retornam o estado persistido mais recentemente da entidade. Esse estado é sempre um estado "confirmado", ou seja, ele nunca é um estado intermediário temporário assumido no meio da execução de uma operação. No entanto, é possível que esse estado seja obsoleto se comparado com o estado na memória da entidade. Somente orquestrações podem ler o estado na memória de uma entidade, conforme descrito na seção a seguir.
### <a name="example-orchestration-signals-and-calls-an-entity"></a>Exemplo: a orquestração sinaliza e chama uma entidade
As funções de orquestrador podem acessar entidades usando APIs na [associação de gatilho de orquestração](durable-functions-bindings.md#orchestration-trigger). O código de exemplo a seguir mostra uma função de orquestrador chamando e sinalizando uma entidade `Counter`.
```csharp
[FunctionName("CounterOrchestration")]
public static async Task Run(
[OrchestrationTrigger] IDurableOrchestrationContext context)
{
var entityId = new EntityId(nameof(Counter), "myCounter");
// Two-way call to the entity which returns a value - awaits the response
int currentValue = await context.CallEntityAsync<int>(entityId, "Get");
if (currentValue < 10)
{
// One-way signal to the entity which updates the value - does not await a response
context.SignalEntity(entityId, "Add", 1);
}
}
```
```javascript
const df = require("durable-functions");
module.exports = df.orchestrator(function*(context){
const entityId = new df.EntityId("Counter", "myCounter");
// Two-way call to the entity which returns a value - awaits the response
currentValue = yield context.df.callEntity(entityId, "get");
if (currentValue < 10) {
// One-way signal to the entity which updates the value - does not await a response
yield context.df.signalEntity(entityId, "add", 1);
}
});
```
Somente orquestrações são capazes de chamar entidades e obter uma resposta, que poderia ser um valor retornado ou uma exceção. As funções de cliente que usam a [associação de cliente](durable-functions-bindings.md#entity-client) só podem sinalizar entidades.
> [!NOTE]
> Chamar uma entidade de uma função de orquestrador é semelhante a chamar uma [função de atividade](durable-functions-types-features-overview.md#activity-functions) de uma função de orquestrador. A principal diferença é que as funções de entidade são objetos duráveis com um endereço, que é a ID da entidade. As funções de entidade permitem a especificação de um nome de operação. As funções de atividade, por outro lado, são sem estado e não têm o conceito das operações.
### <a name="example-entity-signals-an-entity"></a>Exemplo: a entidade sinaliza uma entidade
Uma função de entidade pode enviar sinais para outras entidades ou até mesmo para si própria enquanto executa uma operação.
Por exemplo, podemos modificar o exemplo de entidade `Counter` anterior para que ela envie um sinal de "marco-atingido" para alguma entidade de monitor quando o contador atingir o valor 100.
```csharp
case "add":
var currentValue = ctx.GetState<int>();
var amount = ctx.GetInput<int>();
if (currentValue < 100 && currentValue + amount >= 100)
{
ctx.SignalEntity(new EntityId("MonitorEntity", ""), "milestone-reached", ctx.EntityKey);
}
ctx.SetState(currentValue + amount);
break;
```
```javascript
case "add":
const amount = context.df.getInput();
if (currentValue < 100 && currentValue + amount >= 100) {
const entityId = new df.EntityId("MonitorEntity", "");
context.df.signalEntity(entityId, "milestone-reached", context.df.instanceId);
}
context.df.setState(currentValue + amount);
break;
```
## <a name="entity-coordination"></a>Coordenação de entidades
Pode haver ocasiões em que você precise coordenar operações em várias entidades. Por exemplo, em um aplicativo bancário, você pode ter entidades que representam contas bancárias individuais. Ao transferir fundos de uma conta para outra, é preciso garantir que a conta de origem tenha fundos suficientes. Também é preciso garantir que as atualizações para as contas de origem e de destino sejam realizadas de maneira transacionalmente consistente.
### <a name="example-transfer-funds-c"></a>Exemplo: Transferir fundos (C#)
O código de exemplo a seguir transfere fundos entre duas entidades de conta usando uma função de orquestrador. A coordenação das atualizações da entidade requer o uso do método `LockAsync` para criar uma _seção crítica_ na orquestração.
> [!NOTE]
> Para simplificar, este exemplo reutiliza a entidade `Counter` definida anteriormente. Em um aplicativo real, seria melhor definir uma entidade `BankAccount` mais detalhada.
```csharp
// This is a method called by an orchestrator function
public static async Task<bool> TransferFundsAsync(
string sourceId,
string destinationId,
int transferAmount,
IDurableOrchestrationContext context)
{
var sourceEntity = new EntityId(nameof(Counter), sourceId);
var destinationEntity = new EntityId(nameof(Counter), destinationId);
// Create a critical section to avoid race conditions.
// No operations can be performed on either the source or
// destination accounts until the locks are released.
using (await context.LockAsync(sourceEntity, destinationEntity))
{
ICounter sourceProxy =
context.CreateEntityProxy<ICounter>(sourceEntity);
ICounter destinationProxy =
context.CreateEntityProxy<ICounter>(destinationEntity);
int sourceBalance = await sourceProxy.Get();
if (sourceBalance >= transferAmount)
{
await sourceProxy.Add(-transferAmount);
await destinationProxy.Add(transferAmount);
// the transfer succeeded
return true;
}
else
{
// the transfer failed due to insufficient funds
return false;
}
}
}
```
No .NET, `LockAsync` retorna `IDisposable`, que encerra a seção crítica quando descartado. Esse resultado `IDisposable` pode ser usado junto com um bloco `using` para obter uma representação sintática da seção crítica.
No exemplo anterior, uma função de orquestrador transferiu fundos de uma entidade de origem para uma entidade de destino. O método `LockAsync` bloqueou as entidades de conta de origem e de destino. Com esse bloqueio, nenhum outro cliente pôde consultar ou modificar o estado de qualquer conta até que a lógica da orquestração saísse da seção crítica no fim da instrução `using`. Esse comportamento evita a possibilidade de que a conta de origem efetue saque a descoberto.
> [!NOTE]
> Quando uma orquestração é encerrada, normalmente ou com um erro, todas as seções críticas em andamento são encerradas implicitamente e todos os bloqueios são liberados.
### <a name="critical-section-behavior"></a>Comportamento da seção crítico
O método `LockAsync` cria uma seção crítica em uma orquestração. Essas seções críticas impedem que outras orquestrações façam alterações sobrepostas em um conjunto especificado de entidades. Internamente, a API `LockAsync` envia operações de "bloqueio" para as entidades e retorna quando recebe uma mensagem de resposta de "bloqueio adquirido" de cada uma dessas mesmas entidades. O bloqueio e o desbloqueio são operações internas compatíveis com todas as entidades.
Nenhuma operação de outros clientes é permitida em uma entidade enquanto ela está em um estado bloqueado. Esse comportamento verifica se apenas uma instância de orquestração pode bloquear uma entidade por vez. Se um chamador tentar invocar uma operação em uma entidade enquanto ela estiver bloqueada por uma orquestração, essa operação será colocada em uma fila de operação pendente. Nenhuma operação pendente será processada até que a orquestração em retenção libere seu bloqueio.
> [!NOTE]
> Esse comportamento é um pouco diferente dos primitivos de sincronização usados na maioria das linguagens de programação, como a instrução `lock` em C#. Por exemplo, em C#, a instrução `lock` deve ser usada por todos os threads para garantir a sincronização apropriada em vários threads. Contudo, as entidades não exigem que todos os chamadores bloqueiem explicitamente uma entidade. Se qualquer chamador bloquear uma entidade, todas as outras operações nessa entidade serão bloqueadas e enfileiradas atrás desse bloqueio.
Os bloqueios em entidades são duráveis. Portanto, eles persistirão mesmo se o processo de execução for reciclado. Os bloqueios são persistidos internamente como parte do estado durável de uma entidade.
Ao contrário das transações, as seções críticas não revertem automaticamente as alterações em caso de erros. Em vez disso, qualquer tratamento de erro, como reversão ou repetição, precisa ser codificado explicitamente; por exemplo, capturando erros ou exceções. Essa opção de design é intencional. Em geral, a reversão automática de todos os efeitos de uma orquestração é difícil ou impossível porque as orquestrações podem executar atividades e fazer chamadas para serviços externos que não podem ser revertidos. Além disso, as tentativas de reverter podem falhar e exigir tratamento de erro adicional.
### <a name="critical-section-rules"></a>Regras de seção críticas
Ao contrário do que ocorre com os primitivos de bloqueio de nível baixo na maioria das linguagens de programação, com as seções críticas *há garantia de que não ocorrerá deadlock*. Para evitar deadlocks, impomos as seguintes restrições:
* As seções críticas não podem ser aninhadas.
* As seções críticas não podem criar suborquestrações.
* As seções críticas podem chamar somente entidades que elas bloquearam.
* As seções críticas não podem chamar a mesma entidade usando várias chamadas paralelas.
* As seções críticas podem sinalizar apenas entidades que elas não bloquearam.
Quaisquer violações dessas regras causam um erro de runtime, como `LockingRulesViolationException` no .NET, que inclui uma mensagem explicando qual regra foi violada.
## <a name="comparison-with-virtual-actors"></a>Comparação com atores virtuais
Muitos recursos das entidades duráveis são inspirados pelo [modelo de ator](https://en.wikipedia.org/wiki/Actor_model). Se já estiver familiarizado com atores, você poderá reconhecer muitos conceitos descritos neste artigo. Entidades duráveis são particularmente semelhantes a [atores virtuais](https://research.microsoft.com/projects/orleans/), ou grãos, conforme popularizado pelo [projeto Orleans](http://dotnet.github.io/orleans/). Por exemplo:
* As entidades duráveis podem ser abordadas por meio de uma ID de entidade.
* As operações de entidade durável são executadas de maneira serial, uma por vez, para impedir condições de corrida.
* As entidades duráveis são criadas implicitamente quando são chamadas ou sinalizadas.
* Quando não executam operações, as entidades duráveis são descarregadas silenciosamente da memória.
Há algumas diferenças importantes que vale a pena serem observadas:
* As entidades duráveis priorizam a durabilidade em relação à latência e, portanto, podem não ser apropriadas para aplicativos com requisitos estritos de latência.
* Entidades duráveis não têm tempos limite internos para mensagens. No Orleans, todas as mensagens atingem o tempo limite após um tempo configurável. O padrão é 30 segundos.
* As mensagens enviadas entre entidades são entregues de maneira confiável e em ordem. No Orleans, a entrega confiável ou ordenada é compatível com conteúdo enviado por meio de fluxos, mas não é garantida para todas as mensagens entre os grãos.
* Os padrões de solicitação-resposta em entidades estão limitados a orquestrações. De dentro das entidades, apenas o sistema de mensagens unidirecional (também conhecido como sinalização) é permitido, assim como no modelo de ator original e ao contrário dos grãos no Orleans.
* As entidades duráveis não geram deadlock. No Orleans, os deadlocks podem ocorrer e não se resolver até atingir o tempo limite das mensagens.
* As entidades duráveis podem ser usadas em conjunto com orquestrações duráveis e dão suporte a mecanismos de bloqueio distribuídos.
## <a name="next-steps"></a>Próximas etapas
> [!div class="nextstepaction"]
> [Leia o guia do desenvolvedor para entidades duráveis no .NET](durable-functions-dotnet-entities.md)
> [!div class="nextstepaction"]
> [Saiba sobre os hubs de tarefa](durable-functions-task-hubs.md)
| 60.589552 | 603 | 0.763066 | por_Latn | 0.999769 |
2fe2e16fe648191b6126c14a90a2dcd4d47a8686 | 14,763 | md | Markdown | articles/active-directory/saas-apps/boomi-tutorial.md | FloKlaffenbach/azure-docs.de-de | 938684e8ca7296a11e35f658e389a5b952f786a7 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/active-directory/saas-apps/boomi-tutorial.md | FloKlaffenbach/azure-docs.de-de | 938684e8ca7296a11e35f658e389a5b952f786a7 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/active-directory/saas-apps/boomi-tutorial.md | FloKlaffenbach/azure-docs.de-de | 938684e8ca7296a11e35f658e389a5b952f786a7 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: 'Tutorial: Integration des einmaligen Anmeldens (Single Sign-On, SSO) von Azure Active Directory mit Boomi | Microsoft-Dokumentation'
description: Erfahren Sie, wie Sie das einmalige Anmelden zwischen Azure Active Directory und Boomi konfigurieren.
services: active-directory
documentationCenter: na
author: jeevansd
manager: mtillman
ms.reviewer: barbkess
ms.assetid: 40d034ff-7394-4713-923d-1f8f2ed8bf36
ms.service: active-directory
ms.subservice: saas-app-tutorial
ms.workload: identity
ms.tgt_pltfrm: na
ms.topic: tutorial
ms.date: 02/07/2020
ms.author: jeedes
ms.collection: M365-identity-device-management
ms.openlocfilehash: a22a36d5e6c36008c3a574cbcf9be8ec4f52b82b
ms.sourcegitcommit: cfbea479cc065c6343e10c8b5f09424e9809092e
ms.translationtype: HT
ms.contentlocale: de-DE
ms.lasthandoff: 02/08/2020
ms.locfileid: "77086455"
---
# <a name="tutorial-azure-active-directory-single-sign-on-sso-integration-with-boomi"></a>Tutorial: Integration des einmaligen Anmeldens (Single Sign-On, SSO) von Azure Active Directory mit Boomi
In diesem Tutorial erfahren Sie, wie Sie Boomi in Azure Active Directory (Azure AD) integrieren. Die Integration von Boomi in Azure AD ermöglicht Folgendes:
* Sie können in Azure AD steuern, wer Zugriff auf Boomi haben soll.
* Sie können es Ihren Benutzern ermöglichen, sich mit ihrem Azure AD-Konto automatisch bei Boomi anzumelden.
* Verwalten Sie Ihre Konten zentral im Azure-Portal.
Weitere Informationen zur Integration von SaaS-Apps in Azure AD finden Sie unter [Was bedeuten Anwendungszugriff und einmaliges Anmelden mit Azure Active Directory?](https://docs.microsoft.com/azure/active-directory/manage-apps/what-is-single-sign-on)
## <a name="prerequisites"></a>Voraussetzungen
Für die ersten Schritte benötigen Sie Folgendes:
* Ein Azure AD-Abonnement Falls Sie über kein Abonnement verfügen, können Sie ein [kostenloses Azure-Konto](https://azure.microsoft.com/free/) verwenden.
* SSO-fähiges Boomi-Abonnement
## <a name="scenario-description"></a>Beschreibung des Szenarios
In diesem Tutorial konfigurieren und testen Sie das einmalige Anmelden von Azure AD in einer Testumgebung.
* Boomi unterstützt **IDP**-initiiertes einmaliges Anmelden.
* Nach dem Konfigurieren von Boomi können Sie Sitzungssteuerungen erzwingen, die in Echtzeit vor der Exfiltration und Infiltration vertraulicher Unternehmensdaten schützen. Sitzungssteuerungen basieren auf bedingtem Zugriff. [Hier](https://docs.microsoft.com/cloud-app-security/proxy-deployment-any-app) erfahren Sie, wie Sie die Sitzungssteuerung mit Microsoft Cloud App Security erzwingen.
## <a name="adding-boomi-from-the-gallery"></a>Hinzufügen von Boomi über den Katalog
Zum Konfigurieren der Integration von Boomi in Azure AD müssen Sie Boomi aus dem Katalog der Liste der verwalteten SaaS-Apps hinzufügen.
1. Melden Sie sich mit einem Geschäfts-, Schul- oder Unikonto oder mit einem persönlichen Microsoft-Konto beim [Azure-Portal](https://portal.azure.com) an.
1. Wählen Sie im linken Navigationsbereich den Dienst **Azure Active Directory** aus.
1. Navigieren Sie zu **Unternehmensanwendungen**, und wählen Sie dann **Alle Anwendungen** aus.
1. Wählen Sie zum Hinzufügen einer neuen Anwendung **Neue Anwendung** aus.
1. Geben Sie im Abschnitt **Aus Katalog hinzufügen** den Suchbegriff **Boomi** in das Suchfeld ein.
1. Wählen Sie im Ergebnisbereich die Option **Boomi** aus, und fügen Sie dann die App hinzu. Warten Sie einige Sekunden, während die App Ihrem Mandanten hinzugefügt wird.
## <a name="configure-and-test-azure-ad-single-sign-on-for-boomi"></a>Konfigurieren und Testen des einmaligen Anmeldens von Azure AD für Boomi
Konfigurieren und testen Sie das einmalige Anmelden von Azure AD mit Boomi mithilfe eines Testbenutzers namens **B.Simon**. Damit einmaliges Anmelden funktioniert, muss eine Linkbeziehung zwischen einem Azure AD-Benutzer und dem entsprechenden Benutzer in Boomi eingerichtet werden.
Führen Sie die folgenden Schritte aus, um das einmalige Anmelden von Azure AD mit Boomi zu konfigurieren und zu testen:
1. **[Konfigurieren des einmaligen Anmeldens von Azure AD](#configure-azure-ad-sso)** , um Ihren Benutzern die Verwendung dieses Features zu ermöglichen.
* **[Erstellen eines Azure AD-Testbenutzers](#create-an-azure-ad-test-user)** , um das einmalige Anmelden von Azure AD mit dem Testbenutzer B. Simon zu testen.
* **[Zuweisen des Azure AD-Testbenutzers](#assign-the-azure-ad-test-user)** , um B. Simon die Verwendung des einmaligen Anmeldens von Azure AD zu ermöglichen.
1. **[Konfigurieren des einmaligen Anmeldens für Boomi](#configure-boomi-sso)** , um die Einstellungen für einmaliges Anmelden auf der Anwendungsseite zu konfigurieren.
* **[Erstellen eines Boomi-Testbenutzers](#create-boomi-test-user)** , um in Boomi eine Entsprechung von B.Simon zu erhalten, die mit der Benutzerdarstellung in Azure AD verknüpft ist.
1. **[Testen des einmaligen Anmeldens](#test-sso)** , um zu überprüfen, ob die Konfiguration funktioniert
## <a name="configure-azure-ad-sso"></a>Konfigurieren des einmaligen Anmeldens (Single Sign-On, SSO) von Azure AD
Gehen Sie wie folgt vor, um das einmalige Anmelden von Azure AD im Azure-Portal zu aktivieren.
1. Navigieren Sie im [Azure-Portal](https://portal.azure.com/) auf der Anwendungsintegrationsseite für **Boomi** zum Abschnitt **Verwalten**, und wählen Sie **Einmaliges Anmelden** aus.
1. Wählen Sie auf der Seite **SSO-Methode auswählen** die Methode **SAML** aus.
1. Klicken Sie auf der Seite **Einmaliges Anmelden (SSO) mit SAML einrichten** auf das Bearbeitungs- bzw. Stiftsymbol für **Grundlegende SAML-Konfiguration**, um die Einstellungen zu bearbeiten.
1. Führen Sie im Abschnitt **Grundlegende SAML-Konfiguration** die folgenden Schritte aus, wenn Sie über eine **Metadatendatei des Dienstanbieters** verfügen und die Anwendung im **IDP**-initiierten Modus konfigurieren möchten:
a. Klicken Sie auf **Metadatendatei hochladen**.
b. Klicken Sie auf das **Ordnerlogo**, wählen Sie die Metadatendatei aus, und klicken Sie auf **Hochladen**.
c. Nach dem erfolgreichen Upload der Metadatendatei werden die Werte unter **Bezeichner** und **Antwort-URL** im Abschnitt „Grundlegende SAML-Konfiguration“ automatisch eingefügt.
> [!Note]
> Die **Dienstanbieter-Metadatendatei** rufen Sie später im Tutorial im Abschnitt **Konfigurieren von Boomi** ab. Sollten die Werte **Bezeichner** und **Antwort-URL** nicht automatisch aufgefüllt werden, geben Sie die erforderlichen Werte manuell ein.
1. Die Boomi-Anwendung erwartet die SAML-Assertionen in einem bestimmten Format. Daher müssen Sie Ihrer Konfiguration der SAML-Tokenattribute benutzerdefinierte Attributzuordnungen hinzufügen. Der folgende Screenshot zeigt die Liste der Standardattribute.
1. Darüber hinaus wird von der Boomi-Anwendung erwartet, dass in der SAML-Antwort noch einige weitere Attribute zurückgegeben werden (siehe unten). Diese Attribute werden ebenfalls vorab aufgefüllt, Sie können sie jedoch nach Bedarf überprüfen.
| Name | Quellattribut|
| ---------------| --------- |
| FEDERATION_ID | user.mail |
1. Navigieren Sie auf der Seite **Einmaliges Anmelden (SSO) mit SAML einrichten** im Abschnitt **SAML-Signaturzertifikat** zum Eintrag **Zertifikat (Base64)** . Wählen Sie **Herunterladen** aus, um das Zertifikat herunterzuladen, und speichern Sie es auf Ihrem Computer.
1. Kopieren Sie im Abschnitt **Boomi einrichten** die entsprechenden URLs gemäß Ihren Anforderungen.
### <a name="create-an-azure-ad-test-user"></a>Erstellen eines Azure AD-Testbenutzers
In diesem Abschnitt erstellen Sie im Azure-Portal einen Testbenutzer mit dem Namen B. Simon.
1. Wählen Sie im linken Bereich des Microsoft Azure-Portals **Azure Active Directory** > **Benutzer** > **Alle Benutzer** aus.
1. Wählen Sie oben im Bildschirm die Option **Neuer Benutzer** aus.
1. Führen Sie unter den Eigenschaften für **Benutzer** die folgenden Schritte aus:
1. Geben Sie im Feld **Name** die Zeichenfolge `B.Simon` ein.
1. Geben Sie im Feld **Benutzername** die Zeichenfolge username@companydomain.extension ein. Beispiel: `B.Simon@contoso.com`.
1. Aktivieren Sie das Kontrollkästchen **Kennwort anzeigen**, und notieren Sie sich den Wert aus dem Feld **Kennwort**.
1. Klicken Sie auf **Erstellen**.
### <a name="assign-the-azure-ad-test-user"></a>Zuweisen des Azure AD-Testbenutzers
In diesem Abschnitt ermöglichen Sie B.Simon die Verwendung des einmaligen Anmeldens von Azure, indem Sie dem Benutzer Zugriff auf Boomi gewähren.
1. Wählen Sie im Azure-Portal **Unternehmensanwendungen** > **Alle Anwendungen** aus.
1. Wählen Sie in der Anwendungsliste die Option **Boomi** aus.
1. Navigieren Sie auf der Übersichtsseite der App zum Abschnitt **Verwalten**, und wählen Sie **Benutzer und Gruppen** aus.
1. Wählen Sie **Benutzer hinzufügen** und anschließend im Dialogfeld **Zuweisung hinzufügen** die Option **Benutzer und Gruppen** aus.
1. Wählen Sie im Dialogfeld **Benutzer und Gruppen** in der Liste „Benutzer“ den Eintrag **B. Simon** aus, und klicken Sie dann unten auf dem Bildschirm auf die Schaltfläche **Auswählen**.
1. Wenn Sie einen beliebigen Rollenwert in der SAML-Assertion erwarten, wählen Sie im Dialogfeld **Rolle auswählen** die entsprechende Rolle für den Benutzer in der Liste aus, und klicken Sie dann im unteren Bildschirmbereich auf die Schaltfläche **Auswählen**.
1. Klicken Sie im Dialogfeld **Zuweisung hinzufügen** auf die Schaltfläche **Zuweisen**.
## <a name="configure-boomi-sso"></a>Konfigurieren des einmaligen Anmeldens für Boomi
1. Melden Sie sich in einem anderen Webbrowserfenster bei der Boomi-Unternehmenswebsite als Administrator an.
1. Navigieren Sie zu **Firmenname**, und wechseln Sie zu **Einrichten**.
1. Klicken Sie auf die Registerkarte **SSO-Optionen**, und führen Sie folgende Schritte aus.
a. Aktivieren Sie das Kontrollkästchen **Enable SAML Single Sign-On**.
b. Klicken Sie auf **Importieren**, um das heruntergeladene Zertifikat aus Azure AD in das **Identitätsanbieterzertifikat** hochzuladen.
c. Geben Sie im Textfeld **Anmelde-URL für Identitätsanbieter** den Wert für die **Anmelde-URL** aus dem Konfigurationsfenster der Azure AD-Anwendung ein.
d. Aktivieren Sie für **Federation Id Location** (Speicherort der Verbund-ID) das Optionsfeld **Federation Id is in FEDERATION_ID Attribute element** (Verbund-ID im Attributelement FEDERATION_ID enthalten).
e. Kopieren Sie den Wert für **AtomSphere MetaData URL** (AtomSphere-Metadaten-URL), navigieren Sie im Browser Ihrer Wahl zur **Metadaten-URL**, und speichern Sie die Ausgabe in einer Datei. Laden Sie die **Metadaten-URL** im Azure-Portal im Abschnitt **Grundlegende SAML-Konfiguration** hoch.
f. Klicken Sie auf die Schaltfläche **Save** .
### <a name="create-boomi-test-user"></a>Erstellen eines Boomi-Testbenutzers
Damit sich Azure AD-Benutzer bei Boomi anmelden können, müssen sie in Boomi bereitgestellt werden. Im Fall von Boomi ist die Bereitstellung eine manuelle Aufgabe.
### <a name="to-provision-a-user-account-perform-the-following-steps"></a>Führen Sie zum Bereitstellen eines Benutzerkontos die folgenden Schritte aus:
1. Melden Sie sich bei der Boomi-Unternehmenswebsite als Administrator an.
1. Navigieren Sie nach der Anmeldung zu **Benutzerverwaltung** und wechseln Sie zu **Benutzer**.
1. Klicken Sie auf das Symbol **+** . Das Dialogfeld **Benutzerrollen hinzufügen/verwalten** wird geöffnet.
a. Geben Sie im Textfeld **E-Mail-Adresse des Benutzers** die E-Mail-Adresse des Benutzers, z.B. B.Simon@contoso.com, ein.
b. Geben Sie im Textfeld **First Name** (Vorname) den Vornamen des Benutzers ein (beispielsweise „B.“).
c. Geben Sie im Textfeld **Nachname** den Vornamen des Benutzers ein, z.B. „Simon“.
d. Geben Sie die **Verbund-ID.** des Benutzers ein. Jeder Benutzer muss über eine Verbund-ID verfügen, die den Benutzer im Konto eindeutig identifiziert.
e. Weisen Sie dem Benutzer die Rolle **Standardbenutzer** zu. Weisen Sie ihm nicht die Rolle „Administrator“ zu, da er dadurch normalen Zugriff auf Atmosphere sowie Zugriff über einmaliges Anmelden erhalten würde.
f. Klicken Sie auf **OK**.
> [!NOTE]
> Der Benutzer erhält keine Begrüßungs-E-Mail mit einem Kennwort, das zum Anmelden beim AtomSphere-Konto verwendet werden kann, da sein Kennwort über den Identitätsanbieter verwaltet wird. Sie können AAD-Benutzerkonten auch mithilfe anderer Tools zum Erstellen von Boomi-Benutzerkonten oder mithilfe der von Boomi bereitgestellten APIs erstellen.
## <a name="test-sso"></a>Testen des einmaligen Anmeldens
In diesem Abschnitt testen Sie die Azure AD-Konfiguration für einmaliges Anmelden über den Zugriffsbereich.
Wenn Sie im Zugriffsbereich auf die Kachel „Boomi“ klicken, sollten Sie automatisch bei Ihrer Boomi-Anwendung angemeldet werden, für die Sie einmaliges Anmelden eingerichtet haben. Weitere Informationen zum Zugriffsbereich finden Sie unter [Einführung in den Zugriffsbereich](https://docs.microsoft.com/azure/active-directory/active-directory-saas-access-panel-introduction).
## <a name="additional-resources"></a>Zusätzliche Ressourcen
- [Liste mit den Tutorials zur Integration von SaaS-Apps in Azure Active Directory](https://docs.microsoft.com/azure/active-directory/active-directory-saas-tutorial-list)
- [Was bedeuten Anwendungszugriff und einmaliges Anmelden mit Azure Active Directory?](https://docs.microsoft.com/azure/active-directory/manage-apps/what-is-single-sign-on)
- [Was ist der bedingte Zugriff in Azure Active Directory?](https://docs.microsoft.com/azure/active-directory/conditional-access/overview)
- [Was ist Sitzungssteuerung in Microsoft Cloud App Security?](https://docs.microsoft.com/cloud-app-security/proxy-intro-aad)
- [Boomi mit Azure AD ausprobieren](https://aad.portal.azure.com/)
| 66.800905 | 391 | 0.777823 | deu_Latn | 0.992574 |
2fe366c8819c6f6536b1f8b7ac84ca11a00847ea | 27 | md | Markdown | README.md | embedded-specialties/meta-esi | 9f3b2f6d41d29760a99665e25862d0c1157ca34a | [
"MIT"
] | null | null | null | README.md | embedded-specialties/meta-esi | 9f3b2f6d41d29760a99665e25862d0c1157ca34a | [
"MIT"
] | null | null | null | README.md | embedded-specialties/meta-esi | 9f3b2f6d41d29760a99665e25862d0c1157ca34a | [
"MIT"
] | null | null | null | # meta-esi
ESI Yocto Layer
| 9 | 15 | 0.740741 | tur_Latn | 0.329689 |
2fe38e638e68f8d898a294fef57358e918320aa2 | 27,629 | md | Markdown | learn/references/java-interoperability/ballerina-ffi.md | Seanpm2001-GitHub-Pages-Collection/ballerina-dev-website | 64d884bb8fbc747e4e6fb4f701fb879b246c9234 | [
"CC-BY-2.0",
"CC-BY-3.0",
"Apache-2.0"
] | 1 | 2022-03-29T21:45:53.000Z | 2022-03-29T21:45:53.000Z | learn/references/java-interoperability/ballerina-ffi.md | SNU-Programming-Tools/ballerina-dev-website | 64d884bb8fbc747e4e6fb4f701fb879b246c9234 | [
"CC-BY-2.0",
"CC-BY-3.0",
"Apache-2.0"
] | null | null | null | learn/references/java-interoperability/ballerina-ffi.md | SNU-Programming-Tools/ballerina-dev-website | 64d884bb8fbc747e4e6fb4f701fb879b246c9234 | [
"CC-BY-2.0",
"CC-BY-3.0",
"Apache-2.0"
] | null | null | null | ---
layout: ballerina-java-interoperability-left-nav-pages-swanlake
title: Ballerina FFI
description: The reference guide on the list of language features that enable Ballerina developers to call foreign code written in other programming languages.
keywords: ballerina, programming language, ffi, foreign function invocation
permalink: /learn/java-interoperability/ballerina-ffi/
active: ballerina-ffi
intro: The reference guide on the list of language features that enable Ballerina developers to call foreign code written in other programming languages.
redirect_from:
- /learn/tooling-guide/cli-tools/ballerina-ffi/
- /learn/tooling-guide/cli-tools/ballerina-ffi
- /learn/cli-documentation/ballerina-ffi/
- /learn/cli-documentation/ballerina-ffi
- /learn/cli-documentation/ballerina-ffi/
- /learn/cli-documentation/ballerina-ffi
---
Let's look at the list of language features that enable Ballerina developers to call foreign code written in other programming languages. E.g., while the jBallerina compiler allows you to call any `Java` code, the nBallerina compiler will allow you to call any `C` Code.
## The external function body
Usually, the body or the implementation of a function is specified in the same source file. The part, which is enclosed by curly braces is called the function body.
```ballerina
function doSomething(int i) returns string {
...
}
```
Ballerina also allows you to define a function without a function body and mark it with the `external` keyword to express that the implementation is not provided by the Ballerina source file.
```ballerina
function doSomething(int i) returns string = external;
```
Now, let’s see how you can link this function with a foreign function.
```ballerina
import ballerina/jballerina.java;
function doSomething(int i) returns string = @java:Method {
name: "doSomethingInJava"
'class: "a.b.c.Foo"
} external;
```
The `@java:Method` annotation instructs the jBallerina compiler to link to the `doSomethingInJava` static method in the `a.b.c.Foo` Java class. There are a set of annotations and other utilities available in the `ballerina/jballerina.java` module to make Java interoperability work that is covered in this guide.
## The handle type
The handle type describes a reference to externally-managed storage. These values can only be created by a Ballerina function with an external function body. Within the context of jBallerina, a `handle` type variable can refer to any Java reference type value: a Java object, an array, or the null value.
Consider the `randomUUID` method in the Java UUID class, which gives you a UUID object. This is the Java method signature.
```java
static UUID randomUUID()
```
Below is the corresponding Ballerina function that returns a value of the handle type.
```ballerina
import ballerina/jballerina.java;
function randomUUID() returns handle = @java:Method {
name: "randomUUID",
'class: "java.util.UUID"
} external;
```
In Java, you can assign the `null` value to any variable of a reference type. Therefore, a `handle` type variable may also refer to the Java `null`.
The following sections describe various aspects of Java interoperability in Ballerina. You can copy and paste the following examples into a `.bal` file and run it using the `bal run <file_name.bal>` command.
## Instantiate Java classes
Let's look at how you can create Java objects in a Ballerina program. The `@java:Constructor` annotation instructs the compiler to link a Ballerina function with a Java constructor.
The `ArrayDeque` class in the `java.util` package has a default constructor. The following Ballerina code creates a new `ArrayDeque` object. As you can see, the `newArrayDeque` function is linked with the default constructor. This function returns a handle value and refers to the constructed `ArrayDeque` instance.
```ballerina
import ballerina/jballerina.java;
public function main() {
handle arrayDeque = newArrayDeque();
}
function newArrayDeque() returns handle = @java:Constructor {
'class: "java.util.ArrayDeque"
} external;
```
You can also create a wrapper Ballerina class for Java classes as follows.
```ballerina
import ballerina/jballerina.java;
public function main() {
ArrayDeque ad = new;
}
class ArrayDeque {
private handle jObj;
function __init(){
self.jObj = newArrayDeque();
}
}
function newArrayDeque() returns handle = @java:Constructor {
'class: "java.util.ArrayDeque"
} external;
```
>**Note:** These `@java:*` annotations cannot be attached to Ballerina class methods at the moment.
### Deal with overloaded constructors
When there are two constructors with the same number of arguments available, you need to specify the exact constructor that you want to link with the Ballerina function. The `ArrayDeque` class contains three constructors and the last two are overloaded ones.
```ballerina
public ArrayDeque();
public ArrayDeque(int numElements);
public ArrayDeque(Collection<? extends E> c);
```
Below is the updated Ballerina code.
```ballerina
import ballerina/jballerina.java;
function newArrayDeque() returns handle = @java:Constructor {
'class: "java.util.ArrayDeque"
} external;
function newArrayDequeWithSize(int numElements) returns handle = @java:Constructor {
'class: "java.util.ArrayDeque",
paramTypes: ["int"]
} external;
function newArrayDequeWithCollection(handle c) returns handle = @java:Constructor {
'class: "java.util.ArrayDeque",
paramTypes: ["java.util.Collection"]
} external;
```
#### The `paramTypes` field
You can use the `paramTypes` field to resolve the exact overloaded method. This field is defined as follows.
```ballerina
# The `Class` type represents a fully-qualified Java class name.
public type Class string;
# The `ArrayType` represents a Java array type. It is used to specify parameter
# types in the `Constructor` and `Method` annotations.
#
# + class - Element class of the array type
# + dimensions - Dimensions of the array type
public type ArrayType record {|
Class 'class;
byte dimensions;
|};
# Describes a Java constructor. If the `paramTypes` field is not specified,
# then the parameter types are inferred from the corresponding Ballerina function.
#
# + class - The class in which the constructor exists
# + paramTypes - An optional field, which describes the parameter types of the constructor
public type ConstructorData record {|
Class 'class;
(Class | ArrayType)[] paramTypes?;
|};
```
As per the above definition, `paramTypes` field takes an array of Java classes or array types. The following table contains more details.
Java type | Description | Example
--------- | ----------- | -------
Primitive | The Java class name of a primitive type is the same as the name of the primitive type. | The `boolean.class.getName()` expression evaluates to `boolean`. Similarly, the `int.class.getName()` expression evaluates to `int`.
Class | Fully-qualified class name. | `java.lang.String`
Array | Use the `ArrayType` record defined above to specify Java array types in overloaded methods. | The value of the `paramField` for the method signature `void append(boolean[] states, long l, String[][] args)` evaluates to `[{'class:"boolean", dimensions: 1}, "long", {'class:"java.lang.String", dimensions: 2}]`
For more details, look at the following example.
```java
public Builder(Person[][] list, int index);
public Builder(Student[][] list, int index);
```
Below is the corresponding Ballerina code.
```ballerina
import ballerina/jballerina.java;
function builderWithPersonList(handle list, int index) returns handle = @java:Constructor {
'class: "a.b.c.Builder",
paramTypes: [{'class: "a.b.c.Person", dimensions:2}, "int"]
} external;
function builderWithStudentList(handle list, int index) returns handle = @java:Constructor {
'class: "a.b.c.Builder",
paramTypes: [{'class: "a.b.c.Student", dimensions:2}, "int"]
} external;
```
## Call Java methods
You can use the `java:@Method` annotation to link Ballerina functions with Java static and instance methods. There is a minor but important difference in calling Java static methods vs calling instance methods.
### Call static methods
First look at how to call a static method. The `java.util.UUID` class has a static method with the `static UUID randomString()` signature.
```ballerina
import ballerina/jballerina.java;
import ballerina/io;
function randomUUID() returns handle = @java:Method {
name: "randomUUID",
'class: "java.util.UUID"
} external;
public function main() {
handle uuid = randomUUID();
io:println(uuid);
}
```
The `name` field is optional here. If the Ballerina function name is the same as the Java method name, you don’t have to specify the `name` field.
```ballerina
function randomUUID() returns handle = @java:Method {
'class: "java.util.UUID"
} external;
```
### Call instance methods
Now, look at how to call Java instance methods using the same `ArrayDeque` class in the `java.util` package. It can be used as a stack with its `pop` and `push` instance methods with the following method signatures.
```java
E pop();
void push(E e);
```
Below are the corresponding Ballerina functions that are linked to these methods.
```ballerina
function pop(handle arrayDequeObj) returns handle = @java:Method {
'class: "java.util.ArrayDeque"
} external;
function push(handle arrayDequeObj, handle e) = @java:Method {
'class: "java.util.ArrayDeque"
} external;
```
If you compare these functions with the Java method signatures, you would notice the additional `handle arrayDequeObj` parameter in Ballerina functions. Let’s look at a sample usage to understand the reason.
```ballerina
public function main() {
// Create a new instance of `ArrayDeque`.
handle arrayDequeObj = newArrayDeque();
// Convert a Ballerina string to a Java string.
string str = "Ballerina";
handle handleStr = java:fromString(str);
push(arrayDequeObj, handleStr);
handle e = pop(arrayDequeObj);
}
```
As you can see, you need to first construct an instance of the `ArrayDeque` class. The `arrayDequeObj` variable refers to an `ArrayDeque` object. Then, you need to pass this variable to both the `pop` and `push` functions because the corresponding Java methods are instance methods of the `ArrayDeque` class. Therefore, you need an instance of the `ArrayDeque` class to invoke its instance methods. You can think of the `arrayDequeObj` variable as the method receiver.
### Call methods asynchronously
Ballerina internally uses a fixed number of threads. Therefore, when calling a Java method, it should return in a reasonable time frame to avoid starvation in the Ballerina code execution.
If the given Java method executes a time-consuming task (i.e., blocking) such as an IO operation, better to do that in a separate thread while yielding the original thread to continue the Ballerina code execution.
In this case, the Ballerina Scheduler needs to be informed that the work is being completed asynchronously by invoking the `markAsync` method in the `BalEnv` object. When the work is completed, the `complete` method has to be called with the return value.
>**Note:** The original return value is ignored.
```java
public static long getFileCountRecursively(BalEnv env, BString path) {
BalFuture balFuture = env.markAsync();
new Thread(() -> {
long result = // slow operation ;
balFuture.complete(result);
}).start(); // in a production system this can be a thread pool/nio pool
return -38263; // this value is ignored
}
```
```ballerina
public function getFileCountRecursively(string path) returns int = @java:Method {
'class:"my/test/DirOperations"
} external;
```
### Map Java classes into Ballerina classes
The following pattern is useful if you want to present a clearer Ballerina API, which calls the underneath Java code. This pattern creates wrapper Ballerina classes for each Java class that you want to expose via your API.
Imagine that you want to design an API to manipulate a stack of string values by using the Java `ArrayDeque` utility. You can create a Ballerina class as follows.
```ballerina
public class StringStack {
private handle jObj;
public function init() {
self.jObj = newArrayDeque();
}
public function push(string element) {
push(self.jObj, java:fromString(element));
}
public function pop() returns string {
handle handleEle = pop(self.jObj);
// Error handling and null safety are discussed later in this guide
// This example uses an empty string for now.
return java:toString(handleEle) ?: "";
}
}
function newArrayDeque() returns handle = @java:Constructor {
'class: "java.util.ArrayDeque"
} external;
function pop(handle receiver) returns handle = @java:Method {
'class: "java.util.ArrayDeque"
} external;
function push(handle receiver, handle element) = @java:Method {
'class: "java.util.ArrayDeque"
} external;
```
This class presents a much clearer API compared to the previous API. Below is a sample usage of this class.
```ballerina
public function main() {
StringStack stack = new();
stack.push("Ballerina");
string element = stack.pop();
}
```
### Call overloaded Java methods
The [Instantiating Java Classes](/learn/java-interoperability/ballerina-ffi/#instantiating-java-classes) section presents how to deal with overloaded constructors. You need to use the same approach to deal with overloaded Java methods. Try to call the overloaded `append` methods in the `java.lang.StringBuffer` class. Below is a subset of those methods.
```java
StringBuffer append(boolean b);
StringBuffer append(int i);
StringBuffer append(String str);
StringBuffer append(StringBuffer sb);
StringBuffer append(char[] str);
```
Below is the set of Ballerina functions that are linked with the above Java methods. Notice the usage of the `paramTypes` annotation field. You can find more details of this field in the [Instantiating Java classes](/learn/java-interoperability/ballerina-ffi/#instantiating-java-classes) section.
```ballerina
function appendBool(handle sbObj, boolean b) returns handle = @java:Method {
name: "append",
paramTypes: ["boolean"],
'class: "java.lang.StringBuffer"
} external;
function appendInt(handle sbObj, int i) returns handle = @java:Method {
name: "append",
paramTypes: ["int"],
'class: "java.lang.StringBuffer"
} external;
function appendCharArray(handle sbObj, handle str) returns handle = @java:Method {
name: "append",
paramTypes: [{'class: "char", dimensions: 1}],
'class: "java.lang.StringBuffer"
} external;
function appendString(handle sbObj, handle str) returns handle = @java:Method {
name: "append",
paramTypes: ["java.lang.String"],
'class: "java.lang.StringBuffer"
} external;
function appendStringBuffer(handle sbObj, handle sb) returns handle = @java:Method {
name: "append",
paramTypes: ["java.lang.StringBuffer"],
'class: "java.lang.StringBuffer"
} external;
```
## Java exceptions as Ballerina errors
A function call in Ballerina may complete abruptly by returning an error or by raising a panic. Panics are rare in Ballerina. The best practice is to handle errors in your normal control flow. Raising a panic is similar to throwing a Java exception. The `trap` action will stop a panic and give you the control back in Ballerina and the `try-catch` statement does the same in Java.
Errors in Ballerina belong to the built-in type `error`. The error type can be considered as a distinct type from all other types. The `error` type does not belong to the `any` type, which is the supertype of all other Ballerina types. Therefore, errors are explicit in Ballerina programs and it is almost impossible to ignore them. For more details, see [Ballerina By Example](https://ballerina.io/learn/by-example/).
A Java function call may complete abruptly by throwing either a checked exception or an unchecked exception. Unchecked exceptions are usually not a part of the Java method signature, unlike the checked exceptions.
Java interoperability layer in Ballerina handles checked exceptions differently from unchecked exceptions as explained below.
### Java unchecked exceptions
If the linked Java method throws an unchecked exception, then the corresponding Ballerina function will complete abruptly by raising a panic.
The following example tries to pop an element out of an empty queue. The `pop` method in the `ArrayDeque` class throws an unchecked `java.util.NoSuchElementException` exception in such cases. This exception will cause the Ballerina `pop` function to raise a panic.
```ballerina
import ballerina/jballerina.java;
function newArrayDeque() returns handle = @java:Constructor {
'class: "java.util.ArrayDeque"
} external;
function pop(handle receiver) returns handle = @java:Method {
'class: "java.util.ArrayDeque"
} external;
public function main() {
handle arrayDeque = newArrayDeque();
handle element = pop(arrayDeque);
}
```
Below is the output:
```
error: java.util.NoSuchElementException
at array_deque:pop(array_deque.bal:65535)
array_deque:main(array_deque.bal:13)
```
You can use the `trap` action to stop the propagation of the panic and to get an `error` value.
```ballerina
public function main() {
handle arrayDeque = newArrayDeque();
handle | error element = trap pop(arrayDeque);
if element is error {
io:println(element.message());
io:println(element.detail());
io:println(element.stackTrace().callStack);
} else {
// .....
}
}
```
### Java checked exceptions
Below, you can see how to call a Java method that throws a checked exception. As illustrated in the following example, the corresponding Ballerina function should have the `error` type as part of its return type.
The `java.util.zip.ZipFile` class is used to read entries in a ZIP file. There are many constructors in this class. Here, the constructor that takes the file name as an argument is used.
```java
public ZipFile(String name) throws IOException
```
Since this Java constructor throws a checked exception, the `newZipfile` Ballerina function returns `ZipFile` instances or an error.
```ballerina
import ballerina/jballerina.java;
function newZipFile(handle filename) returns handle | error = @java:Constructor {
'class: "java.util.zip.ZipFile",
paramTypes: ["java.lang.String"]
} external;
public function main() {
handle|error zipFile = newZipFile(java:fromString("some_file.zip"));
}
```
### Map a Java exception to a Ballerina error value
Now, look at how a Java exception is converted to a Ballerina error value at runtime. A Ballerina error value contains three components: a message, a detail, and a stack trace.
The `message`:
- This is a string identifier for the error category.
- In this case, the message value is set to the fully-qualified Java class name of the exception.
- **Unchecked:** Class name of of the thrown unchecked exception
- **Checked:** Class name of the exception that is declared in the method signature
The `detail`:
- The `message` field is set to `e.getMessage()`.
- The `cause` field is set to the Ballerina error that represents this Java exception’s cause.
The `stack trace`:
- An object representing the stack trace of the error value.
- The first member of the array represents the top of the call stack.
## Null safety
Ballerina provides strict null safety compared to Java with optional types. The Java null reference can be assigned to any reference type. However, in Ballerina, you cannot assign the nil value to a variable unless the variable’s type is optional.
As explained above, Ballerina handle values cannot be created in the Ballerina code. They are created and returned by foreign functions and a variable of the handle type refers to a Java reference value. Since, Java null is also a valid reference value, this variable can refer to a Java null value.
An example Ballerina code is given below that deals with Java null. It uses the `peek` method in the `ArrayDeque` class. `Peek` retrieves but does not remove the head of the queue or returns null if the queue is empty.
```ballerina
import ballerina/jballerina.java;
function newArrayDeque() returns handle = @java:Constructor {
'class: "java.util.ArrayDeque"
} external;
function peek(handle receiver) returns handle = @java:Method {
'class: "java.util.ArrayDeque"
} external;
// Linked with the `java.lang.Object.toString()` method in Java.
function toString(handle objInstance) returns handle = @java:Method {
'class: "java.lang.Object"
} external;
public function main() {
handle arrayDeque = newArrayDeque();
handle element = peek(arrayDeque);
handle str = toString(element);
}
```
Since the queue is empty in this case, `peek` should return null i.e., `element` should refer to Java null. The output of this program will be as follows.
```ballerina
error: java.lang.NoSuchFieldError {"message":"JAVA_NULL_REFERENCE_ERROR"}
at array_deque:toString(array_deque.bal:19)
array_deque:main(array_deque.bal:27)
```
This is equivalent to a Java NPE. In such situations, you should check for null using the `java:isNull()` function. Below is the modified example.
```ballerina
public function main() {
handle arrayDeque = newArrayDeque();
handle element = peek(arrayDeque);
if java:isNull(element) {
// handle this case
} else {
handle str = toString(element);
}
}
```
There are situations in which you need to pass a Java null to a method or store it in a data structure. In such situations, you can create a handle value that refers to a Java null as follows.
```ballerina
handle nullValue = java:createNull();
```
## Map Java types to Ballerina types and vice versa
### Map Java types to Ballerina types
The following table summarizes how Java types are mapped to corresponding Ballerina types. This is applicable when mapping a return type of a Java method to a Ballerina type.
Java type | Ballerina type | Notes
--------- | -------------- | -----
Any reference type including “null type” | handle |
boolean | boolean |
byte | byte, int, float | widening conversion when byte -> int and byte -> float
short | int, float | widening conversion
char | int, float | widening conversion
int | int, float | widening conversion
long | int, float | widening conversion when long -> float
float | float | widening conversion
double | float |
### Map Ballerina types to Java types
The following table summarizes how Ballerina types are mapped to corresponding Java types. These rules are applicable when mapping a Ballerina function argument to a Java method/constructor parameter.
Ballerina type | Java type | Notes
-------------- | --------- | -----
handle | Any reference type | As specified by the Java method/constructor signature
boolean | boolean |
byte | byte, short, char, int, long, float, double | Widening conversion from byte -> short, char, int, long, float, double
int | byte, char, short, int, long | Narrowing conversion when int -> byte, char, short, and int
float | byte, char, short, int, long, float, double | Narrowing conversion when float -> byte, char, short, int, long, float
string | io.ballerina.runtime.api.values.BString |
xml | io.ballerina.runtime.api.values.BXml |
array | io.ballerina.runtime.api.values.BArray |
tuple | io.ballerina.runtime.api.values.BArray |
map | io.ballerina.runtime.api.values.BMap |
table | io.ballerina.runtime.api.values.BTable |
stream | io.ballerina.runtime.api.values.BStream |
object | io.ballerina.runtime.api.values.BObject |
future | io.ballerina.runtime.api.values.BFuture |
function | io.ballerina.runtime.api.values.BFunctionPointer |
typedesc | io.ballerina.runtime.api.values.BTypedesc |
error | io.ballerina.runtime.api.values.BError |
### Use Ballerina arrays and maps in Java
There is no direct mapping between Ballerina arrays and maps to primitive Java arrays and maps. To facilitate the use of Ballerina arrays and maps in Java, the `ballerina-runtime` libraries have to be added as a dependency to the Java project and the relevant classes need to be imported from the `ballerina-runtime` library. For more information on all the released versions, go to [`ballerina-runtime`](https://maven.wso2.org/nexus/content/repositories/releases/org/ballerinalang/ballerina-runtime/). The latest version of the dependency can be added to Gradle using the following:
```groovy
repositories {
// Use WSO2's Nexus repository manager for resolving dependencies.
maven {
url = 'https://maven.wso2.org/nexus/content/repositories/releases/'
}
}
dependencies {
// Add ballerina-runtime as dependency.
implementation 'org.ballerinalang:ballerina-runtime:+'
}
```
#### Use Ballerina arrays in Java
To use Ballerina arrays in Java, the `BArray` interface has to be used. The example below illustrates how to write Java interop code that uses Ballerina arrays.
```java
import io.ballerina.runtime.api.values.BArray;
public class ArrayReverse {
public static BArray arrayReverse(BArray arr) {
long len = arr.size();
for(long i = len - 1, j = 0; j < len/2; i--, j++) {
Object temp = arr.get(j);
arr.add(j, arr.get(i));
arr.add(i, temp);
}
return arr;
}
}
```
Associated Ballerina code:
```ballerina
import ballerina/io;
import ballerina/jballerina.java;
public function main() {
int[] a = [1,2,3,4,5];
int[] b = arrayReverse(a);
io:println(b);
}
function arrayReverse(int[] arr) returns int[] = @java:Method {
'class: "javalibs.app.ArrayReverse"
} external;
```
#### Use Ballerina maps in Java
To use Ballerina maps in Java, the `BMap` interface has to be used. The example below illustrates how to write Java interop code that uses Ballerina maps.
```java
import io.ballerina.runtime.api.values.BMap;
import io.ballerina.runtime.api.values.BString;
import java.util.Map;
public class ModifyValues {
public static BMap<Object, Object> modifyMapValues(BMap<Object, Object> map) {
for(Map.Entry mapElement : map.entrySet()) {
BString key = (BString) mapElement.getKey();
long value = (long) mapElement.getValue();
long modifiedValue = value + 10;
map.put(key, modifiedValue);
}
return map;
}
}
```
Associated Ballerina code:
```ballerina
import ballerina/io;
import ballerina/jballerina.java;
public function main() {
map<int> marks = {sam: 50, jon: 60};
map<int> modifiedMarks = modifyMapValues(marks);
io:println(modifiedMarks);
}
function modifyMapValues(map<int> marks) returns map<int> = @java:Method {
'class: "javalibs.app.ModifyValues"
} external;
```
## Access or mutate Java fields
The `@java:FieldGet` and `@java:FieldSet` annotations allow you to read and update the value of a Java static or instance field respectively. The most common use case is to read a value of a Java static constant.
```ballerina
import ballerina/jballerina.java;
public function pi() returns float = @java:FieldGet {
name:"PI",
'class:"java/lang/Math"
} external;
public function main() {
float r = 4;
float l = 2 * pi() * r;
}
```
In this example, the `pi()` function returns the value of the `java.lang.Math.PI` static field. This uses the `name` annotation field to specify the name of the field. Likewise, if you want to access an instance field, you need to pass the relevant object instance as discussed in the instance methods section.
The `@java:FieldSet` annotation has the same structure as the above.
| 40.100145 | 583 | 0.74306 | eng_Latn | 0.984711 |
2fe3a7e0472d341333736481b7b83669ae16d0a4 | 16 | md | Markdown | README.md | ATS-SKP-DataIT/bank-app-hakan | 75ed3eb786a2dcfda8cde8000dd27b75478e06d5 | [
"MIT"
] | null | null | null | README.md | ATS-SKP-DataIT/bank-app-hakan | 75ed3eb786a2dcfda8cde8000dd27b75478e06d5 | [
"MIT"
] | null | null | null | README.md | ATS-SKP-DataIT/bank-app-hakan | 75ed3eb786a2dcfda8cde8000dd27b75478e06d5 | [
"MIT"
] | null | null | null | # bank-app-hakan | 16 | 16 | 0.75 | zsm_Latn | 0.759928 |
2fe3f4a63a1cae41f91069de929d2d765e0f278e | 21,878 | md | Markdown | MineyaMay1996/chapters/02p.md | slavonic/cu-md-sandbox | 34e07f78ee101d387e850123cf9469664ea9ed16 | [
"MIT"
] | 5 | 2018-06-14T15:04:18.000Z | 2021-04-13T11:38:32.000Z | MineyaMay1996/chapters/02p.md | slavonic/cu-md-sandbox | 34e07f78ee101d387e850123cf9469664ea9ed16 | [
"MIT"
] | 1 | 2018-06-11T16:37:54.000Z | 2018-07-13T01:18:29.000Z | MineyaMay1996/chapters/02p.md | slavonic/cu-md-sandbox | 34e07f78ee101d387e850123cf9469664ea9ed16 | [
"MIT"
] | 1 | 2021-04-13T11:38:36.000Z | 2021-04-13T11:38:36.000Z | <<519>>
*ПРИЛОЖЕ́НІЕ*
*Мѣ́сѧца тогѡ́же во в҃-й де́нь.*
*Пренесе́нїе моще́й ст҃ы́хъ мч҃никѡвъ бори́са и҆ глѣ́ба, нарече́нныхъ во
ст҃о́мъ креще́нїи рѡма́на и҆ даві́да.*
*Ве́черъ.* ~Бл҃же́нъ мꙋ́жъ: *а҃-й а҆нтїфѡ́нъ.*
*На* ~Гдⷭ҇и воззва́хъ: *стїхи̑ры, гла́съ є҃.*
*Подо́бенъ:* ~Ра́дꙋйсѧ:
~Ра́дꙋйсѧ и҆ весели́сѧ, вышегра́де, красꙋ́йсѧ и҆ ра́дꙋйсѧ, ст҃а́ѧ цр҃ковь, въ
ню́же пренесе́ни бы́ша и҆сцѣле́нїѧ ст҃і́и и҆сто́чницы и҆ побѡ́рницы на врагѝ,
побѣ̑ды даю́щїи вѣ̑рнымъ, те́плїи застꙋ̑пницы дꙋ́шъ и҆ тѣле́съ на́шихъ. тѣ́мъ
дне́сь всѝ почита́емъ чⷭ҇тно́е пренесе́нїе тѣле́съ ва́шихъ, сла́внїи. Хрⷭ҇тꙋ̀
помоли́тесѧ дарова́ти дꙋша́мъ на́шымъ ми́ръ и҆ ве́лїю млⷭ҇ть.
~Ра́дꙋйтесѧ и҆ весели́тесѧ, самобра́тнїи, красꙋ́йтесѧ и҆ весели́тесѧ, до́брїи
врачѝ, се́ бо прїѧ́ли є҆стѐ ᲂу҆ хрⷭ҇та̀ жела́ємыѧ вѣнцы̀, и҆́миже стра̑сти и҆
недꙋ́зи всѝ и҆сцѣлѧ́ютсѧ. Вы́ бо сокрꙋ́шистѣ бѣсѡ́вскїѧ кѡ́зни и҆ пога̑нскїѧ
полкѝ. ва́шими бо мл҃твами и҆ посо́бїемъ вѣ́рнїи лю́ди на́ши держа́внѡ
побѣжда́ютъ. тѣ́мъ и҆ мы̀ дне́сь, па́мѧть ва́шꙋ сла́вѧще, вопїе́мъ: хрⷭ҇тꙋ̀
помоли́тесѧ дарова́ти дꙋша́мъ на́шымъ ми́ръ и҆ ве́лїю млⷭ҇ть. <<520>>
~Ра́дꙋйсѧ, ст҃а́ѧ цр҃ковь, ди́внаѧ впра́вдꙋ, въ ню́же пренесе́ни бы́ша ст҃ы̑ѧ
ра́ки, ꙗ҆̀же и҆́мꙋтъ въ себѣ̀ да́ры и҆сцѣле́нїѧ бл҃года́ти, чтⷭ҇на̑ѧ тѣлеса̀
ва̑ша, хрⷭ҇тѡ́ви мч҃ницы. Вы́ бо смире́нїе стѧжа́сте и҆ цѣломꙋ́дрїе, слꙋжи́телѧ
же невѣ́рствовавша въ стра́хъ вложи́сте и҆ ᲂу҆вѣ́рили є҆стѐ. Недꙋ́зи и҆ стра̑сти
и҆сцѣлѧ́ютсѧ, и҆ бѣсѡ́въ мно́жество и҆счеза́ютъ, прогони́ми быва́ютъ невѣ́рныхъ
полцы̀ посо́бїемъ ва́шимъ. хрⷭ҇тꙋ̀ помоли́тесѧ дарова́ти дꙋша́мъ на́шымъ ми́ръ
и҆ ве́лїю млⷭ҇ть.
*Сла́ва, гла́съ ѕ҃. Самогла́сенъ:*
~Прїиди́те, ли́къ соста́вльше, возвели́чимъ чꙋдотво́рцы и҆ мч҃ники, и҆̀же
зако́ннѡ пострада́вшыѧ и҆ свѣ́тлѡ со держа́вными мч҃ники вѣнча́вшыѧсѧ, и҆ со
безпло́тными трⷪ҇цѣ предстоѧ́щыѧ, мо́лѧтъ ᲂу҆мири́ти мі́ръ и҆ спастѝ дꙋ́шы
на́шѧ.
*И҆ ны́нѣ, бг҃оро́диченъ.*
*Вхо́дъ. Прокі́менъ днѐ и҆ чтє́нїѧ мч҃ничєскаѧ (зрѝ ли́стъ р҃ѳ на ѡ҆б.)*
*На лїті́и стїхи̑ры, гла́съ д҃:*
~А҆́ще и҆ земна́гѡ црⷭ҇твїѧ, но́вый ка́їнъ бг҃оненави́стникъ и҆
братоненави́стный ᲂу҆бі́йственнѣ лишѝ ва́съ. Хрⷭ҇то́съ же непреходѧ́щее и҆
безконе́чное црⷭ҇тво ва́мъ дарова̀, є҆мꙋ́же со а҆́гг҃льскими во́инствы
предстоѧ́ще, моли́тесѧ спастѝ любо́вїю пою́щыѧ всечⷭ҇тнꙋ́ю и҆
многопра́зднственнꙋю па́мѧть ва́шꙋ
~Землѧ̀ ѡ҆свѧти́сѧ кро́вїю всечⷭ҇тно́ю ва́шею, и҆ чл҃вѣ́цы ѡ҆богати́вшесѧ
ва́ми, и҆сцѣле́нїе незави́стнѡ прїе́млютъ, бг҃омꙋ́дрїи ᲂу҆гѡ́дницы хрⷭ҇тѡ́ви,
сла́вне рѡма́не съ неѕло́бивымъ даві́домъ. Моли́тесѧ гдⷭ҇еви, є҆мꙋ́же ѿ ю҆́ности
прилѣпи́стесѧ, сп҃стѝ и҆̀же вѣ́рою пою́щыѧ ва́съ. <<521>>
*Сла́ва, гла́съ ѕ҃:*
~Дне́сь вѣ́рныхъ собо́ри, ли́къ дх҃о́вный соста́вивше, въ па́мѧти ст҃ы́хъ
мч҃никъ ст҃олѣ́пнѡ ликовствꙋ́емъ и҆ весе́лїемъ гдⷭ҇а просла́вимъ, просла́вльшаго
ст҃ы̑ѧ своѧ̑, си́мъ а҆́бїе ᲂу҆чꙋ́вствившесѧ и҆ кла́нѧющесѧ чꙋдотво́рномꙋ гро́бꙋ,
вопїе́мъ: ра́дꙋйтесѧ, дрꙋ́зи гдⷭ҇ни, попра́вшїи главꙋ̀ ѕмі́евꙋ: ра́дꙋйтесѧ,
и҆̀же по ѻ҆бы́чаю ѻ҆́бразъ невре́днѡ сохра́нше: ра́дꙋйтесѧ, хрⷭ҇то́вы ра́ди
за́повѣди ᲂу҆бїе́нїе прїи́мшїи: ва̑ша же тѣлеса̀, на мѣ́стѣхъ непрохо́дныхъ и҆
пꙋсты́хъ повє́ржена, сто́лпъ ѻ҆́гненъ возвестѝ. Ра́дꙋйтесѧ, цвѣ̑тницы
бл҃гово́нни, крі́ни неꙋвѧда́емїи рѡссі́йстїи, непреста́ннѡ молѧ́щїисѧ хрⷭ҇тꙋ̀
поми́ловатисѧ и҆ сп҃сти́сѧ свѣтоно́снꙋю ва́шꙋ па́мѧть пра́зднꙋющымъ.
*И҆ ны́нѣ, бг҃оро́диченъ.*
*На стїхо́внѣ стїхи̑ры, гла́съ в҃:*
~Прїиди́те, цѣломꙋ́дрїѧ люби́телїе, мч҃никъ дво́ицꙋ восхва́лимъ, чⷭ҇тымъ
се́рдцемъ хрⷭ҇та̀ возлю́бльшихъ, и҆̀же дꙋша́ми и҆ тѣлесы̀ неразлꙋ́чни и҆
мо́лѧтсѧ гдⷭ҇еви спасти́сѧ дꙋша́мъ на́шымъ.
*Сті́хъ:* ~Пра́ведникъ, ꙗ҆́кѡ фі́нїѯъ, процвѣте́тъ и҆, ꙗ҆́кѡ ке́дръ, и҆́же въ
лїва́нѣ, ᲂу҆мно́житсѧ.
*Ѿ* ст҃а и҆ чⷭ҇тна̀ ко́рене и҆зра́стше, пресла́вне рѡма́не съ неѕло́бивымъ
даві́домъ, нетлѣ́емꙋю сла́вꙋ па́че тлѣ́нныѧ и҆збра́вше и҆ хрⷭ҇то́вы любвѐ ра́ди
пострада́вше, є҆го́же моли́те сп҃стѝ на́съ, любо́вїю ва́съ почита́ющихъ.
*Сті́хъ:* ~Насажде́ни въ домꙋ̀ гдⷭ҇ни, во дво́рѣхъ бг҃а на́шегѡ процвѣтꙋ́тъ.
~За́пѡвѣди хрⷭ҇тѡ́вы дѣ́лы и҆сполнѧ́юще и҆ ѡ҆ ᲂу҆бива́ющихъ молѧ́щесѧ: не
поста́ви и҆̀мъ, гдⷭ҇и, грѣха̀ сегѡ̀, гл҃го́люще, мл҃твами гдⷭ҇и твои́хъ
ᲂу҆гѡ́дникъ послѝ на́мъ бога̑тыѧ твоѧ̑ млⷭ҇ти. <<522>>
*Сла́ва, гла́съ ѕ҃:*
~Прїиди́те, восхва́лимъ чꙋдотво́рцы и҆ мч҃ники: сі́и бо, зако́ннѡ пострада́вше,
побѣди́ша сꙋпроти́внаго врага̀. и҆ ны́нѣ, свѣ́тлѡ ᲂу҆кра́шени, предстоѧ́тъ
хрⷭ҇тꙋ̀, ра́дꙋющесѧ. тѣ́мъ и҆ мы̀ пѣ́сньми па́мѧть и҆́хъ ве́селѡ похва́лимъ,
любо́вїю вопїю́ще: ра́дꙋйтесѧ, вселе́ннѣй застꙋ̑пницы и҆ побѡ́рницы на врагѝ:
ра́дꙋйтесѧ, врачѝ болѧ́щымъ и҆ бѣсѡ́мъ прогони́телїе: ра́дꙋйтесѧ, ѽ любе́знаѧ
версто̀, бра́тїе прекра́снїи, рѡма́не сла́вный и҆ даві́де чꙋ́дный, люби́мцы
хрⷭ҇тѡ́ви, за ны̀ моли́те ст҃ꙋ́ю трⷪ҇цꙋ, ᲂу҆мири́ти мі́ръ и҆ сп҃стѝ дꙋ́шы на́шѧ.
*И҆ ны́нѣ, бг҃оро́диченъ.*
*Тропа́рь, гла́съ д҃:*
~Дне́сь цр҃кѡ́внаѧ разширѧ́ютсѧ нѣ̑дра, прїе́млющїи бога́тство бж҃їѧ
бл҃года́ти, веселѧ́тсѧ рꙋ́сстїи собо́ри, ви́дѧще пресла̑внаѧ чꙋдеса̀, ꙗ҆̀же
твори́те приходѧ́щымъ къ ва́мъ вѣ́рою, ст҃і́и чꙋдотво́рцы бори́се и҆ глѣ́бе,
моли́те хрⷭ҇та̀ бг҃а, да сп҃се́тъ дꙋ́шы на́шѧ.
*И҆́нъ тропа́рь, гла́съ в҃:*
~Пречⷭ҇тні́и и҆ цѣломꙋ́дреннїи, и҆ неѕло́бивїи страстоте́рпцы, рѡма́не сла́вный
и҆ даві́де чꙋ́дный, и҆́го бо гдⷭ҇не є҆ѵⷢ҇льски на ра́мо взе́мше, послѣ́довасте
хрⷭ҇тꙋ̀, и҆ кре́стъ є҆гѡ̀, ꙗ҆́кѡ ски́петръ, въ рꙋкꙋ̀ и҆мꙋ́ще, врага̀ бра́та и҆
ѕла́го властолю́бца соѡдолѣ́сте, и҆ то́й ны́нѣ въ гее́ннѣ мꙋ́читсѧ, вы́ же
ра́дꙋетесѧ, съ ли́ки а҆́гг҃льскими предстоѧ́ще ст҃ѣ́й трⷪ҇цѣ, моли́тесѧ ѡ҆
держа́вѣ срѡ́дникъ ва́шихъ, бл҃гоꙋго́днѣй бы́ти, и҆ сыновѡ́мъ рꙋ̑сскимъ
сп҃сти́сѧ. <<523>>
*И҆́нъ тропа́рь, гла́съ д҃:*
~Мч҃ницы гдⷭ҇ни спа́сшїисѧ, пресла́внїи бл҃же́ннїи кнѧ́зи бори́се и҆ глѣ́бе,
трꙋжда́ющымсѧ бы́стрїи помѡ́щницы, недꙋ̑жнымъ цѣли́тели, вы́ бо бѡлѣ́зни
врачꙋ́ете притека́ющихъ въ цр҃ковь съ вѣ́рою. тѣ́мже и҆ мы̀ мо́лимсѧ: ѿ бѣ́дъ
и҆зба́вите на́съ, чтꙋ́щихъ съ любо́вїю пренесе́нїе моще́й ва́шихъ.
*И҆́нъ тропа́рь, гла́съ и҃:*
~Дне́сь всѧ́каѧ дꙋша̀ вѣ́рныхъ весели́тсѧ, въ пренесе́нїе чⷭ҇тны́хъ моще́й
ва́шихъ, бори́се и҆ глѣ́бе, слѣпы̑ѧ просвѣща́ете, нѣмы̑мъ ᲂу҆ста̀ ѿверза́ете и҆
печа̑льныѧ ᲂу҆тѣша́ете, прїѧ́ли бо є҆стѐ ѿ хрⷭ҇та̀ бг҃а бл҃года́ть и҆сцѣле́нїй,
моли́тесѧ ѡ҆ дꙋша́хъ на́шихъ.
*На ᲂу҆́трени.*
*По а҃-мъ стїхосло́вїи сѣда́ленъ, гла́съ а҃.*
*Подо́бенъ:* ~Ка́мени запеча́танꙋ:
~Ѕвѣзды̀ незаходи̑мыѧ, пресвѣ̑тлаѧ свѣти̑ла ꙗ҆ви́лисѧ є҆стѐ, сла́вный рѡма́не
съ до́блимъ даві́домъ, дне́сь и҆ по кончи́нѣ то́чите и҆сцѣлє́нїѧ. сла́ва
да́вшемꙋ ва́мъ крѣ́пость, сла́ва вѣнча́вшемꙋ ва́съ, сла́ва дѣ́йствꙋющемꙋ ва́ми
и҆сцѣле́нїе.
*Сла́ва, и҆́нъ сѣда́ленъ, гла́съ то́йже:*
~Дне́сь землѧ̀ рꙋ́сскаѧ ва́ми, страстоте́рпцы хрⷭ҇тѡ́ви, кнѧ́же бори́се и҆
сла́вный глѣ́бе, сы́ны вели́кагѡ кнѧ́зѧ влади́мїра, свѣ́титсѧ, ꙗ҆́кѡ со́лнце,
свои́ми бо вѣнцы̀ на всю̀ рꙋ́сскꙋю зе́млю сїѧ́ете, моли́те хрⷭ҇та̀ бг҃а на́шего
за всѧ̑ вѣ̑рныѧ хрⷭ҇тїа́ны, да сп҃се́тъ дꙋ́шы на́шѧ.
*И҆ ны́нѣ, пра́здника.*
*По в҃-мъ стїхосло́вїи сѣда́ленъ, гла́съ д҃:*
~За́висти ра́ди погꙋ́блени ѿ своегѡ̀ бра́та, и҆́мже приведе́сѧ, ꙗ҆́кѡ а҆́гнцы,
бг҃ꙋ, пожро́шасѧ во́лею, за ᲂу҆бива́ющыѧ бг҃ꙋ молѧ́щесѧ, и҆́хже мл҃твами сп҃сѝ
дꙋ́шы на́шѧ. <<524>>
*Сла́ва, и҆́нъ сѣда́ленъ, гла́съ то́йже:*
~Со ст҃ы́ми ны́нѣ всели́лисѧ є҆стѐ, ст҃ꙋ́ю свою̀ сконча́сте жи́знь, тѣ́мъ и҆
ра́ка ва́ша и҆сто́чникъ и҆сцѣле́нїй показа́сѧ, рѡма́не пребл҃же́нне съ чꙋ́днымъ
даві́домъ, мл҃твами ва́шими ѿ напа́сти и҆зба́вите на́съ, ва́съ почита́ющихъ.
*Сла́ва, и҆ ны́нѣ, бг҃оро́диченъ:*
~Въ кро́въ тво́й, пречⷭ҇таѧ дв҃о, прибѣга́ющихъ, мольбꙋ̀ прїимѝ ѿ на́съ и҆ не
преста́й молѧ́щи чл҃вѣколю́бца сп҃сти́сѧ рабѡ́мъ твои̑мъ.
*По полѷеле́и сѣда́ленъ, гла́съ и҃:*
*Подо́бенъ:* ~Премꙋ́дрости:
~Бл҃же́нна ᲂу҆̀бо землѧ̀, крѡ́ви ва́шѧ воспрїе́мшаѧ, и҆злїѧ́нны ѿ непра́веднагѡ
бра́та и҆ врага̀, пречꙋ́днаѧ и҆ предо́браѧ версто̀, и҆́стинѣ побѡ́рницы и҆
приста́нище небꙋ́рное сꙋ́щымъ въ бѣда́хъ, тѣ́мъ досто́йнѡ бл҃жи́ми є҆стѐ,
рѡма́не сла́вне съ неѕло́бивымъ даві́домъ. моли́те хрⷭ҇та̀ бг҃а согрѣше́нїємъ
ѡ҆ставле́нїе дарова́ти, чтꙋ́щымъ любо́вїю ст҃ꙋ́ю па́мѧть ва́шꙋ.
*Сла́ва, и҆́нъ сѣда́ленъ, гла́съ то́йже:*
~Къ бж҃е́ственнѣй красотѣ̀ пресвѣ́тлѡ взѧ́стесѧ бл҃года́тїю, зємны́ѧ концы̀
по́хоти попра́вше свы́ше стра́стїю, рѡма́не и҆ даві́де, вселе́ннѣй свѣти̑ла.
тѣ́мъ мо́лимсѧ ѿ тмы̀ грѣхо́вныѧ и҆ ѿ недꙋ̑гъ и҆зба́вити на́съ, мо́лимъ ва́съ:
моли́те бг҃а ѡ҆ всѣ́хъ на́съ.
*И҆ ны́нѣ, бг҃оро́диченъ:*
*Ѽ* прест҃а́ѧ дв҃о, мт҃и хрⷭ҇то́ва, дꙋшѝ моеѧ̀ стра̑сти и҆сцѣлѝ, ꙗ҆̀же без̾
ᲂу҆ма̀ содѣ́ѧхъ, молю́сѧ, и҆ тишинꙋ̀ мѝ пода́ждь: а҆́зъ бо дꙋ́шꙋ ѡ҆скверни́хъ и҆
тѣ́ло, ѻ҆каѧ́нный, и҆ не вѣ́мъ, <<525>> что̀ сотворю̀ въ де́нь сꙋда̀, є҆гда̀
а҆́гг҃ли дꙋ́шꙋ мою̀ разлꙋча́тъ ѿ ᲂу҆бо́гагѡ моегѡ̀ тѣлесѐ, тогда̀
предста́тельница мѝ бꙋ́ди, и҆збавлѧ́ющи мѧ̀ мꙋче́нїѧ, при́снѡ молѧ́щи сн҃а
своего̀ согрѣше́нїємъ ѡ҆ставле́нїе дарова́ти, тебе́ бо и҆мѣ́ю наде́ждꙋ, ра́бъ
тво́й.
*Степє́нна, а҃-й а҆нтїфѡ́нъ д҃-гѡ гла́са. Прокі́менъ, гла́съ д҃:* ~Честна̀
пред̾ гдⷭ҇емъ сме́рть прпⷣбныхъ є҆гѡ̀. *Сті́хъ:* ~Что̀ возда́мъ гдⷭ҇еви ѡ҆
всѣ́хъ, ꙗ҆̀же воздаде́ ми; ~Всѧ́кое дыха́нїе: *Є҆ѵⷢ҇лїе ѿ лꙋкѝ, зача́ло р҃ѕ.*
*По н҃-мъ ѱалмѣ̀ стїхи́ра, гла́съ ѕ҃:*
~Дне́сь ᲂу҆̀бо соше́дшесѧ, многосостоѧ́нїе цр҃ко́вное, пѣ́сньми хва́лѧще
хвала́мъ досто́йнаго самоде́ржца влади́мїра, повинꙋ́вшасѧ багрѧни́цы црⷭ҇твїѧ
хрⷭ҇то́ва и҆ лю́ди своѧ̑ просвѣти́вша бл҃гоче́стїемъ, ѿ негѡ́же многосвѣ̑тлаѧ
два̀ свѣти̑ла произыдо́сте, бори́съ со глѣ́бомъ. и҆́хже не терпѧ̀, бг҃оме́рзскїй
братоненави́стникъ ѻ҆рꙋ́жїемъ тѣ́хъ закала́етъ. но мл҃твами, бж҃е, твои́хъ
ᲂу҆гѡ́дникъ сп҃сѝ дꙋ́шы на́шѧ.
*Канѡ́нъ мч҃никѡмъ, гла́съ и҃.*
*Пѣ́снь а҃. І҆рмо́съ:*
~Сокрꙋ́шившемꙋ бра̑ни мы́шцею свое́ю и҆ прове́дшемꙋ і҆и҃лѧ сквозѣ̀ чермно́е
мо́ре, пои́мъ є҆мꙋ̀, ꙗ҆́кѡ и҆зба́вителю на́шемꙋ бг҃ꙋ: ꙗ҆́кѡ просла́висѧ.
~Похва́лимъ, вѣ́рнїи, пресла́внꙋю и҆ чⷭ҇тнꙋ́ю дво́ицꙋ, прехва́льныхъ мч҃никъ
рѡма́на и҆ даві́да, и҆́миже хрⷭ҇то́съ просвѣтѝ всю̀ странꙋ̀ рꙋ́сскꙋю.
~Дарова́вшемꙋ си̑мъ да́ръ бл҃года́ти и҆сцѣле́нїѧ, стра̑сти и҆ недꙋ́ги
и҆сцѣлѧ́ти, влⷣцѣ хрⷭ҇тꙋ̀ воспои́мъ сп҃сꙋ и҆ и҆зба́вителю на́шемꙋ, ꙗ҆́кѡ
просла́висѧ. <<526>>
~Ꙗ҆́коже речѐ хрⷭ҇то́съ: вѣ́рꙋѧй въ мѧ̀, дѣла̀, ꙗ҆̀же а҆́зъ творю̀, и҆ то́й
сотвори́тъ, и҆ бо́лша си́хъ. сїѧ̑ прїе́мша, ст҃і́и мч҃ницы, болѧ́щыѧ и҆сцѣлѧ́ете
и҆ дꙋ́хи бѣсѡ́вскїѧ ѿго́ните.
*Бг҃оро́диченъ:*
~Чтⷭ҇нѣ́йшꙋю херꙋві̑мъ и҆ сла́внѣйшꙋю серафі̑мъ, ро́ждшꙋю на землѝ бг҃а сло́ва,
чⷭ҇тоты̀ хра́мъ дꙋше́вный, бцⷣꙋ мр҃і́ю вѣ́рнѡ восхва́лимъ.
*Катава́сїа пра́здника.*
*Пѣ́снь г҃. І҆рмо́съ:*
~Оу҆тверди́сѧ се́рдце моѐ во гдⷭ҇ѣ, вознесе́сѧ ро́гъ мо́й въ бз҃ѣ мое́мъ,
разшири́шасѧ на враги̑ моѧ̑ ᲂу҆ста̀ моѧ̑, возвесели́хсѧ ѡ҆ сп҃се́нїи твое́мъ.
~Чтⷭ҇ны́мъ пренесе́нїемъ тѣле́съ ва́шихъ, сла́внїи, просла́висѧ чтⷭ҇на́ѧ
цр҃ковь, и҆мꙋ́щаѧ въ себѣ̀ бл҃года́ти сокро́вище неѡскꙋ́дное и҆ пречꙋ́дное.
~Ст҃ы̑ѧ ра̑ки ва́ши чⷭ҇тны̑ѧ и҆мꙋ́щи въ себѣ̀ да́ры бл҃года̑тныѧ, пресла́внаѧ
тѣлеса̀ ва̑ша, ст҃і́и мч҃ницы бори́се и҆ глѣ́бе, врачѝ недꙋ̑жнымъ.
~Свѣ́телъ вои́стинꙋ и҆ пречⷭ҇тенъ вышегра́дъ, превы́ше бо всѣ́хъ градѡ́въ
превознесе́сѧ, и҆мы́й въ себѣ̀ чⷭ҇тнꙋ́ю цр҃ковь, въ ню́же пренесе́ни бы́ша
би́сери многоцѣ́ннїи.
*Бг҃оро́диченъ:*
~Оу҆твердѝ, дв҃о, помышле́нїе моѐ и҆ ᲂу҆́мъ мо́й пла́вающїй ᲂу҆тишѝ, ко́рмчїю
бо родила̀ є҆сѝ и҆ ѡ҆чи́стника собла́знѡмъ на́шымъ.
*Конда́къ и҆ і҆́косъ пра́здника.*
*И҆́нъ конда́къ ст҃ы́хъ, гла́съ г҃:*
~Прїиди́те, всѝ рꙋ́сстїи собо́ри, чꙋдотвѡ́рцꙋ и҆ мч҃никꙋ бори́са и҆ глѣ́ба
восхва́лимъ, зако́ннѡ бо пострада́вше, побѣди́сте сопроти́внаго врага̀, тѣ́мъ
ст҃ы́мъ застꙋпле́нїемъ кнѧ́зи рꙋ́сстїи <<527>> врагѝ побѣжда́ютъ, тѣ́мъ па́мѧть
є҆́ю ве́селѡ и҆ любо́вїю похва́лимъ, вопїю́ще: за ны̀ моли́те ст҃ꙋ́ю трⷪ҇цꙋ,
ᲂу҆мири́ти мі́ръ и҆ сп҃стѝ дꙋ́шы на́шѧ.
*И҆́нъ конда́къ ст҃ы́хъ, гла́съ д҃:*
*Ѿ* гро́ба зна́мєнїѧ показа́сте во странѣ̀ рꙋ́сстѣй, ꙗ҆ви́сѧ дне́сь бл҃года́ть
и҆сцѣле́нїѧ всѣ̑мъ, къ ва́мъ, страстоте́рпцы, притека́ющымъ съ вѣ́рою, бори́се
сла́вный со глѣ́бомъ чꙋ́днымъ. крѣ́пцы вѣ́рою, добропобѣ́днїи мч҃ницы, за
хрⷭ҇та̀ под̾е́мше разли̑чныѧ мꙋ̑ки, и҆ на мнѡ́га лѣ̑та сокровє́ни бы́ша ва́ши
ст҃і́и мо́щи, ны́нѣ же ꙗ҆влѧ́етесѧ ѿ землѝ, возсїѧ́вше лꙋча́ми, ꙗ҆́кѡ бога́тство
многоцѣ́нно, и҆ въ цр҃ковь бж҃їю чⷭ҇тнѡ носи́ми, а҆рхїерє́й бж҃їихъ дла́ньми.
тѣ́мже вопїе́мъ ва́мъ: ра́дꙋйтесѧ, кнѧ́зи, рꙋ́сстїи застꙋ̑пницы.
*Сѣда́ленъ ст҃ы́хъ, гла́съ и҃:*
~Хрⷭ҇тѡ́вы ᲂу҆вѣ́дѣвше за́пѡвѣди бл҃гі̑ѧ, того̀ возлюби́вше, страстонѡ́сцы
сла́внїи, ѡ҆ ᲂу҆бїе́нїи тѣлесѐ неради́сте, дꙋ́шы же прекра̑сныѧ въ рꙋ́цѣ хрⷭ҇тꙋ̀
преда́сте: ѻ҆́въ, копїе́мъ пробода́емь, веселѧ́щесѧ, дрꙋгі́й же, ꙗ҆́кѡ а҆́гнѧ,
без̾ ми́лости закала́емь, сегѡ̀ ра́ди прїѧ́ша да́ръ и҆сцѣле́нїѧ, мч҃ницы
самобра́тнїи, моли́те хрⷭ҇та̀ бг҃а грѣхѡ́въ ѡ҆ставле́нїе дарова́ти чтꙋ́щымъ
любо́вїю ст҃ꙋ́ю па́мѧть ва́шꙋ.
*Сла́ва, и҆ ны́нѣ, пра́здника.*
*Пѣ́снь д҃. І҆рмо́съ:*
~Проро́къ а҆ввакꙋ́мъ ᲂу҆́мныма ѻ҆чи́ма прови́дѣ, гдⷭ҇и, прише́ствїе твоѐ, тѣ́мъ
и҆ вопїѧ́ше: ѿ ю҆́га прїи́детъ бг҃ъ. сла́ва си́лѣ твое́й, сла́ва снизхожде́нїю
твоемꙋ̀.
~Бра́тїе прекра́снїи, ра́дꙋйтесѧ, ꙗ҆́кѡ вѣнцы̀ жела́ємыѧ ѿ бг҃а прїе́мше и҆
сегѡ̀ ра́ди ѡ҆ста́вльше всю̀ сла́вꙋ тлѣ́ющꙋю, да хрⷭ҇та̀ прїѡбрѧ́щете є҆ди́наго,
би́сера безцѣ́ннаго. <<528>>
~Хрⷭ҇тѡ́вы ᲂу҆вѣ́дѣвше за́пѡвѣди бж҃е́ствєнныѧ и҆ томꙋ̀ послѣ́дꙋюще, воста́нетъ
бо, речѐ, бра́тъ на бра́та, сегѡ̀ ра́ди прїѧ́сте нꙋ́жднꙋю сме́рть, ꙗ҆́кѡ а҆́гнцы
закала́еми.
~Прободе́нномꙋ на крестѣ̀ копїе́мъ тебѐ ра́ди послѣ́дꙋѧ стопа́мъ, а҆́гнцꙋ
бж҃їю, сла́вный страда́льче, ᲂу҆бі́йцамъ не проти́вльсѧ, бори́се чꙋ́дный, во́ине
до́блїй.
*Бг҃оро́диченъ:*
~Ра́дꙋйсѧ, дꙋше́внаѧ цр҃ковь и҆ рꙋно̀ пречⷭ҇тое бг҃оро́сное, воды̀ живы́ѧ
и҆сто́чниче неистека́ющїй, влⷣчце, запечатле́нный дв҃ствомъ, рабы̑ своѧ̑ сохранѝ
ѿ всѣ́хъ ѕѡ́лъ.
*Пѣ́снь є҃. І҆рмо́съ:*
~Гдⷭ҇и бж҃е на́шъ, ми́ръ да́ждь на́мъ, гдⷭ҇и бж҃е на́шъ, стѧжи́ ны, гдⷭ҇и,
ра́звѣ тебѐ и҆но́гѡ не вѣ́мы, и҆́мѧ твоѐ и҆менꙋ́емъ.
~Ꙗ҆́кѡ а҆́гнецъ безѕло́бивъ, не ретꙋ́ѧ же, ни вопїѧ̀, сн҃ъ бж҃їй веде́сѧ на
сме́рть. вы́ же, семꙋ̀ послѣ́дꙋюще, не ѿ врага̀, но ѿ сро́дника ᲂу҆бїе́ни
бы́сте.
~Во́зрастомъ и҆ ю҆́ностїю ѡ҆ любвѝ преле́стнѣй небрего́сте, ст҃і́и, хрⷭ҇тѡ́вы
за́пѡвѣди и҆сполнѧ́юще, вѣ́чнꙋю жи́знь прїѡбрѣто́сте.
~Вторы́й солꙋ́нь ра́дꙋетсѧ, въ странѣ̀ рꙋ́сстѣй вышегра́дъ сла́вный, и҆мѣ́ѧ въ
себѣ̀ бл҃года́ть сла́внꙋ пренесе́нїемъ тѣле́съ ва́шихъ.
*Бг҃оро́диченъ:*
~Оу҆врачꙋ́й, пречⷭ҇таѧ влⷣчце, дꙋ́шꙋ мою̀, мѡлвы̀ же и҆ напа̑сти бѣсѡ́вскїѧ
прогонѧ́ющи, врача́ бо страсте́мъ родила̀ є҆сѝ и҆ творца̀ всѣ́хъ. <<529>>
*Пѣ́снь ѕ҃. І҆рмо́съ:*
~Ꙗ҆́кѡ во́ды мѡрскі́ѧ, чл҃вѣколю́бче, волна́ми жите́йскими ѡ҆бꙋрева́юсѧ.
тѣ́мже, ꙗ҆́кѡ і҆ѡ́на, та́кѡ вопїю́ ти: возведѝ ѿ тлѝ живо́тъ мо́й, благоꙋтро́бне
гдⷭ҇и.
~Всѧ́кѡ мѣ́сто ѡ҆ст҃и́сѧ и҆ и҆́же въ недꙋ́зѣхъ и҆сцѣлева́ютсѧ посѣще́нїемъ
ва́шимъ, врачѝ пресла́внїи, слѣпі́и прозира́ютъ, хромі́и хо́дѧтъ, слꙋ́цыи
простира́ютсѧ.
~Во всю̀ зе́млю и҆зыдо́ша вѣща̑нїѧ а҆пⷭ҇льскаѧ, ва́шими же чꙋде́съ и҆сцѣлє́нїи
вселе́ннаѧ и҆спо́лнисѧ, вѣ̑рнымъ бо и҆сточа́ете здра́вїе ѻ҆би́льнѡ, сла́внїи.
~Сло́во твоѐ и҆спо́лнисѧ, чл҃вѣколю́бче, є҆́же речѐ ᲂу҆ченикѡ́мъ свои̑мъ,
гра́дъ бо не ᲂу҆кры́етсѧ, верхꙋ̀ горы̀ стоѧ̀. и҆ се́ бо вышегра́дъ просвѣща́етъ
всю̀ зе́млю рꙋ́сскꙋю ꙗ҆вле́нїемъ ст҃ы́хъ твои́хъ, гдⷭ҇и.
*Бг҃оро́диченъ:*
~Всепѣ́таѧ дв҃о, свѣ́тлый ѻ҆́блаче, проженѝ мра́къ дꙋшѝ моеѧ̀, ꙗ҆́кѡ со́лнце
пра́ведное ро́ждшаѧ, и҆ наста́ви мѧ̀ на стезю̀ живо́тнꙋю мольба́ми свои́ми,
пренепоро́чнаѧ.
*Конда́къ, гла́съ д҃.*
*Подо́бенъ:* ~Ꙗ҆ви́лсѧ є҆сѝ дне́сь:
~Ꙗ҆ви́сѧ дне́сь въ странѣ̀ рꙋ́сстѣй блгⷣть и҆сцѣле́нїѧ всѣ̑мъ, къ ва́мъ,
бл҃же́ннїи, приходѧ́щымъ и҆ вопїю́щымъ: ра́дꙋйтесѧ, застꙋ̑пницы те́плїи.
*І҆́косъ:*
~Новоѧвле́нныхъ мꙋ́чєникъ пресла́внаѧ па́мѧть дне́сь рꙋ́сстѣй землѝ свѣ́тлѡ
возсїѧ̀, свѣ̑тлы бо ꙗ҆ви́стесѧ ѕвѣ́зды ѿ бг҃а, чꙋдесы̀ ѡ҆блиста́юще, и҆́хже въ
па́мѧть гдⷭ҇ь всѣ̑мъ вѣ̑рнымъ подае́тъ и҆сцѣле́нїе и҆ въ темни́цѣ <<530>>
и҆збавле́нїе. тѣ́мже и҆ мы̀, немощні́и, прїиди́те, воспои́мъ сїѧ̑, да
воспрїи́мемъ здра́вїе, просвѣща́ете бо слѣпы̑ѧ и҆ недꙋ̑жныѧ и҆сцѣлѧ́ете,
застꙋ̑пницы те́плїи.
*Пѣ́снь з҃. І҆рмо́съ:*
~Халде́йскаѧ пе́щь, ѻ҆гне́мъ распала́емаѧ, ѡ҆роша́шесѧ дх҃омъ, бж҃їимъ
предстоѧ́нїемъ, ѻ҆́троцы поѧ́хꙋ: бл҃гослове́нъ є҆сѝ, бж҃е ѻ҆тє́цъ на́шихъ.
~Вра̑жїѧ и҆счеза́ютъ полцы̀, и҆ пога̑нскаѧ тѣлеса̀ постла́на быва́ютъ под̾
но́ги во́инѡвъ на́шихъ, призыва́ющихъ и҆мена̀ ст҃ы̑ѧ ва̑ша, мч҃ницы хрⷭ҇тѡ́ви.
~Пресла́внѡ просла́висѧ всѧ́ко мѣ́сто и҆ страна̀, въ ни́хже созда́ни бы́ша
чⷭ҇тны̑ѧ цр҃кви всѣ́ми вѣ́рными ѡ҆ и҆́мени ва́шемъ, сла́внїи хрⷭ҇тѡ́ви мч҃ницы.
~Кто̀ не диви́тсѧ зе́мленъ ва́шемꙋ цѣломꙋ́дрїю, ца́ри и҆ кнѧ́зи, сꙋдїи̑ же и҆
всѝ вѣ́рнїи, ва̑ша чꙋдеса̀ пресла̑внаѧ ви́дѧще, неисцѣ̑льныѧ бо стра̑сти
и҆сцѣлѧ́ете вопїю́щымъ: бл҃гослове́нъ бг҃ъ ѻ҆тє́цъ на́шихъ.
*Бг҃оро́диченъ:*
~Пречⷭ҇таѧ влⷣчце, влⷣкꙋ всѣ́хъ ро́ждшаѧ, влⷣчества мѧ̀ ѕла́гѡ свободи́въ,
наста́ви на пꙋ́ть живо́тный, бл҃гослове́ннаѧ бцⷣе прера́дованнаѧ.
*Пѣ́снь и҃. І҆рмо́съ:*
~Покрыва́ѧй вода́ми превы́спрєннѧѧ своѧ̑, полага́ѧй мо́рю предѣ́лъ песо́къ и҆
содержа́й всѧ̑, тѧ̀ пое́тъ со́лнце, тѧ̀ сла́витъ лꙋна̀, тебѣ̀ прино́ситъ пѣ́снь
всѧ̀ тва́рь, ꙗ҆́кѡ содѣ́телю всѣ́хъ во вѣ́ки.
~Помо́щники въ ско́рбехъ, и҆ въ напа́стехъ, и҆ бѣда́хъ, и҆ въ темни́цѣ
и҆збавле́нїе, и҆ на бра́ни застꙋпле́нїе <<531>> ва́шимъ посѣще́нїемъ ѿ бг҃а
прїе́млемъ, призыва́юще ва́съ, хра́брїи, бра́тїе прекра́снїи.
~И҆сцѣлѧ́ете стра̑сти, и҆ бѣ́сы прого́ните, и҆ напа̑сти разорѧ́ете всѣ́мъ,
сла́вѧщымъ пресла́внѡ ст҃о́е пренесе́нїе тѣле́съ ва́шихъ, всехва́льнїи мч҃ницы
хрⷭ҇тѡ́ви, застꙋ̑пницы гра́дꙋ на́шемꙋ.
*Ѽ* бл҃же́ннаѧ, ст҃а́ѧ вои́стинꙋ дво́ице преди́внаѧ, вы̀ кнѧ́зи кнѧзє́мъ,
хра́бри же хрⷭ҇тѡ́ви мч҃ницы, ѡ҆ на́съ те́плїи моли́твєнницы, вы́ бо
ѡ҆брѣта́етесѧ вско́рѣ, ѿ бѣ́дъ и҆збавлѧ́юще.
*Бг҃оро́диченъ:*
~Ѡ҆мраче́нїе дꙋшѝ моеѧ̀ проженѝ, всечⷭ҇таѧ дв҃о, неразꙋ́мїѧ се́рдце моѐ
просвѣтѝ и҆ ᲂу҆́мъ мо́й ѡ҆зарѝ, ро́ждшаѧ вели́каго совѣ́та а҆́гг҃ла, і҆и҃са
чл҃вѣколю́бца, бг҃а же и҆ чл҃вѣ́ка, во ѻ҆бое́мъ соверше́на.
*Пѣ́снь ѳ҃. І҆рмо́съ:*
~Бл҃гослове́нъ гдⷭ҇ь, бг҃ъ і҆и҃левъ, воздви́гнꙋвый ро́гъ сп҃се́нїѧ на́мъ въ
домꙋ̀ дв҃довѣ, ѻ҆́трока своего̀, въ ни́хже посѣтѝ на́съ восто́къ съ высоты̀ и҆
напра́вилъ ны̀ є҆́сть на пꙋ́ть ми́ра.
~Бл҃гослове́нъ гдⷭ҇ь бг҃ъ всѣ́хъ, странꙋ́ же и҆ всѧ̑ лю́ди защища́ѧ, чтꙋ́щихъ
ва́ши ра́ки, сла́внїи, въ чⷭ҇тнѣй цр҃кви, въ ню́же принесе́ни бы́сте ст҃а́ѧ
тѣлеса̀ ва̑ша сла̑внаѧ, рѡма́не и҆ даві́де.
~Бж҃е́ственною ре́вностїю распала́еми, ѡ҆ че́сти земнѣ́й и҆ вла́сти
небрего́сте, хрⷭ҇тѡ́вы за́пѡвѣди соблюда́юще бж҃е́ствєнныѧ, те́мнаго кнѧ́зѧ
попра́ли є҆стѐ, ст҃і́и.
~Бл҃гослове́нъ гдⷭ҇ь бг҃ъ і҆и҃левъ, вѣнча́вый дво́ицꙋ пречⷭ҇тнꙋ́ю, въ странѣ̀
рꙋ́сстѣй ᲂу҆го́дникѡвъ свои́хъ, и҆́миже посѣтѝ <<532>> на́съ, свѣтода́вче,
свы́ше, ᲂу҆моле́нъ быва́ѧ си́ми ѡ҆ на́съ, сп҃се на́шъ.
*Бг҃оро́диченъ:*
~Бл҃гослове́нъ, гпⷭ҇жѐ, пло́дъ твоегѡ̀ чре́ва, призва́вый на́съ и҆з̾ тмы̀ и҆
сѣ́ни смє́ртныѧ и҆ ѡ҆свѧти́вый себѣ̀ лю́ди и҆збра́нны. сего̀ молѝ, пречⷭ҇таѧ
влⷣчце, рабѡ́мъ свои̑мъ побѣ̑ды дарова́ти на врагѝ проти̑вныѧ.
*Свѣти́ленъ. Подо́бенъ:* ~Не́бо ѕвѣзда́ми:
~Прїиди́те, пристꙋпи́те, вѣ́рнїи, въ бж҃е́ственнꙋю цр҃ковь пресла́вныхъ мч҃никъ
рѡма́на и҆ даві́да, и҆̀же ѡ҆ста́виша сла́вꙋ вре́меннꙋю и҆ возлюби́ша сла́вꙋ
безконе́чнꙋю и҆ въ не́й ликꙋ́ютъ съ нб҃е́сными чи́нми. моли́те ѡ҆ на́съ,
чтⷭ҇нꙋ́ю ва́шꙋ па́мѧть пра́зднꙋющихъ.
*Сла́ва, и҆ ны́нѣ, пра́здника.*
*На хвали́техъ стїхи̑ры, гла́съ а҃. Подо́бенъ:* ~Нб҃е́сныхъ чинѡ́въ:
~Свѣтоза́рнаѧ, и҆ ст҃а́ѧ, и҆ бл҃гоѡбра́знаѧ мч҃никѡвъ бори́са и҆ глѣ́ба
всепра́зднественнаѧ возсїѧ̀ па́мѧть, и҆́же, всю̀ зе́млю просвѣща́юще и҆
і҆́дѡльскїй мра́къ ѿгонѧ́юще, цѣльба́мъ бл҃года́ть и҆сточа́ютъ.
~Чⷭ҇тны́ми ка́плѧми крове́й ва́шихъ ѡ҆багри́сте ри̑зы ва́шѧ, бл҃же́ннїи рѡма́не
и҆ даві́де, тѣ́мъ вѣ́рою па́мѧть ва́шꙋ пра́зднꙋюще, моли́тесѧ, мо́лимъ ва́съ,
ᲂу҆мири́ти мі́ръ и҆ сп҃стѝ дꙋ́шы на́шѧ.
~Ꙗ҆́кѡ є҆ди́нъ свѣ́тъ во двою̀ тѣлесѝ, мі́ръ просвѣща́ете чꙋде́сными
блиста́нїи, страстоте́рпцы гдⷭ҇ни, мра́къ <<533>> невѣ́денїѧ ѿгонѧ́юще, тѣ́мъ
воспѣва́емъ ра́достнѡ, похвалѧ́юще ва́шꙋ па́мѧть.
*Сла́ва, гла́съ ѕ҃.*
~И҆̀же на землѝ а҆́гг҃лы и҆ на нб҃сѝ чл҃вѣ́ки бж҃їи, ст҃ы́хъ мч҃никъ почти́мъ,
кро́вїю бо ва́шею всю̀ зе́млю рѡссі́йскꙋю ѡ҆свѧти́сте и҆ ѿ вселе́нныѧ
просла́вистесѧ, сегѡ̀ ра́ди и҆ мы̀, грѣ́шнїи, къ ва́мъ прибѣга́емъ, и҆сцѣле́нїѧ
да́ры прїе́млюще, ᲂу҆гѡ́дницы ст҃і́и рѡма́не и҆ даві́де, скорбѧ́щыѧ ᲂу҆тѣша́ете,
печа̑льныѧ застꙋпа́ете, моли́тесѧ ѡ҆ дꙋша́хъ на́шихъ.
*И҆ ны́нѣ, пра́здника.*
*Славосло́вїе вели́кое. И҆ ѿпꙋ́стъ.*
*На лїтꙋргі́и. Бл҃жє́нны ѿ канѡ́на, пѣ̑сни г҃-ѧ и҆ ѕ҃-ѧ. Прокі́менъ, гла́съ
д҃:* ~Ст҃ы̑мъ, и҆̀же сꙋ́ть на землѝ є҆гѡ̀, ᲂу҆дивѝ гдⷭ҇ь всѧ̀ хотѣ̑нїѧ своѧ̑ въ
ни́хъ. *Сті́хъ:* ~Предзрѣ́хъ гдⷭ҇а предо мно́ю вы́нꙋ, ꙗ҆́кѡ ѡ҆деснꙋ́ю менѐ
є҆́сть, да не подви́жꙋсѧ. *А҆пⷭ҇толъ къ ри́млѧнѡмъ, зача́ло ч҃ѳ. А҆ллилꙋ́їа,
гла́съ д҃:* ~Воззва́ша пра́веднїи, и҆ гдⷭ҇ь ᲂу҆слы́ша и҆̀хъ, и҆ ѿ всѣ́хъ
скорбе́й и҆́хъ и҆зба́ви и҆̀хъ. *Сті́хъ:* ~Мнѡ́ги скѡ́рби пра́вєднымъ, и҆ ѿ
всѣ́хъ и҆́хъ и҆зба́витъ ѧ҆̀ гдⷭ҇ь. *Є҆ѵⷢ҇лїе ѿ і҆ѡа́нна, зача́ло н҃в.
Прича́стенъ:* ~Ра́дꙋйтесѧ, пра́веднїи, ѡ҆ гдⷭ҇ѣ:
*Моли́тва.*
*Ѽ* дво́ице сщ҃е́ннаѧ, бра́тїѧ прекра̑снаѧ, до́блїи страстоте́рпцы бори́се и҆
глѣ́бе, ѿ ю҆́ности хрⷭ҇тꙋ̀ вѣ́рою, чⷭ҇тото́ю и҆ любо́вїю послꙋжи́вшїи, и҆
кровьмѝ свои́ми, ꙗ҆́кѡ багрѧни́цею, ᲂу҆краси́вшїисѧ, и҆ ны́нѣ со хрⷭ҇то́мъ
ца́рствꙋющїи. Не забꙋ́дите и҆ на́съ, сꙋ́щихъ на землѝ, но, ꙗ҆́кѡ те́плїи
застꙋ̑пницы, ва́шимъ си́льнымъ хода́тайствомъ пред̾ хрⷭ҇то́мъ бг҃омъ сохрани́те
ю҆́ныхъ во ст҃ѣ́й вѣ́рѣ и҆ чⷭ҇тотѣ̀ <<534>> неврежде́нными ѿ всѧ́кагѡ прило́га
невѣ́рїѧ и҆ нечⷭ҇тоты̀, ѡ҆гради́те всѣ́хъ на́съ ѿ всѧ̑кїѧ ско́рби, ѡ҆ѕлобле́нїй
и҆ напра́сныѧ сме́рти, ᲂу҆кроти́те всѧ́кꙋю враждꙋ̀ и҆ ѕло́бꙋ, дѣ́йствомъ
дїа́вола воздвига́емꙋю ѡ҆ бли́жнихъ и҆ чꙋжди́хъ. мо́лимъ ва́съ, хрⷭ҇толюби́вїи
страстоте́рпцы, и҆спроси́те ᲂу҆ великодарови́тагѡ влⷣки всѣ̑мъ на́мъ
ѡ҆ставле́нїе прегрѣше́нїй на́шихъ, є҆диномы́слїе и҆ здра́вїе, и҆збавле́нїе ѿ
наше́ствїѧ и҆ноплеме́нныхъ, междоꙋсо́бныѧ бра́ни, ꙗ҆́звы и҆ гла́да. Снабдѣва́йте
свои́мъ застꙋпле́нїемъ странꙋ̀ на́шꙋ и҆ всѣ́хъ, чтꙋ́щихъ ст҃ꙋ́ю па́мѧть ва́шꙋ,
во вѣ́ки вѣкѡ́въ. *а҆ми́нь.*
| 43.581673 | 80 | 0.6869 | ukr_Cyrl | 0.139264 |
2fe44bc995f70a424342a514126e5b4ea1faabe0 | 140 | md | Markdown | README.md | Patrikol4/social-grana | 17645e02ade660cf95d890c7c9014bbb824e6fc0 | [
"MIT"
] | null | null | null | README.md | Patrikol4/social-grana | 17645e02ade660cf95d890c7c9014bbb824e6fc0 | [
"MIT"
] | null | null | null | README.md | Patrikol4/social-grana | 17645e02ade660cf95d890c7c9014bbb824e6fc0 | [
"MIT"
] | null | null | null | # social-grana
Um aplicativo web capaz de conectar pessoas com interesses comuns e ir além, fazendo suas interações gerarem lucros entre si
| 46.666667 | 124 | 0.821429 | por_Latn | 0.99998 |
2fe493a84d3a097558a1eafef0fa9cfedcd3441b | 851 | md | Markdown | lib/shop-api/docs/PaymentBankAccount.md | thomdiesel/sfcc-ocapi-amp | 4529cf5b0be619c6052e68a807fb6ef428ea0395 | [
"MIT"
] | null | null | null | lib/shop-api/docs/PaymentBankAccount.md | thomdiesel/sfcc-ocapi-amp | 4529cf5b0be619c6052e68a807fb6ef428ea0395 | [
"MIT"
] | 3 | 2021-05-10T23:48:29.000Z | 2022-02-26T22:14:09.000Z | lib/shop-api/docs/PaymentBankAccount.md | thomdiesel/sfcc-ocapi-amp | 4529cf5b0be619c6052e68a807fb6ef428ea0395 | [
"MIT"
] | null | null | null | # ShopApi.PaymentBankAccount
## Properties
Name | Type | Description | Notes
------------ | ------------- | ------------- | -------------
**driversLicenseLastDigits** | **String** | The last 4 characters of the decrypted driver's license number of the bank account associated with this payment instrument. | [optional]
**driversLicenseStateCode** | **String** | The driver license state code. | [optional]
**holder** | **String** | The holder of the bank account. | [optional]
**maskedDriversLicense** | **String** | The decrypted driver's license number of the bank account with all but the last 4 characters replaced with a '*' character. | [optional]
**maskedNumber** | **String** | The bank account masked number. | [optional]
**numberLastDigits** | **String** | The last digits of the bank account number. | [optional]
| 60.785714 | 190 | 0.66275 | eng_Latn | 0.94317 |
2fe570b91d06aa58fd5114a1e983d1ca07219f65 | 489 | md | Markdown | reports/report2_Antarctica.md | liamcosgrove30/EdiNapSoftwareMethodsGroupA | 1fe8fc9661c2c89ffc12269b83aac473824b191c | [
"Apache-2.0"
] | 1 | 2021-02-03T14:37:28.000Z | 2021-02-03T14:37:28.000Z | reports/report2_Antarctica.md | liamcosgrove30/EdiNapSoftwareMethodsGroupA | 1fe8fc9661c2c89ffc12269b83aac473824b191c | [
"Apache-2.0"
] | 54 | 2021-02-02T18:05:37.000Z | 2021-04-27T22:43:26.000Z | reports/report2_Antarctica.md | liamcosgrove30/EdiNapSoftwareMethodsGroupA | 1fe8fc9661c2c89ffc12269b83aac473824b191c | [
"Apache-2.0"
] | null | null | null | # All countries in a continent (Antarctica) organised by largest population to the smallest
| Code | Name | Continent | Region | Population | Capital |
| :--- | :--- | :--- | :--- | :--- | :--- |
|ATA|Antarctica|Antarctica|Antarctica|0| |
|BVT|Bouvet Island|Antarctica|Antarctica|0| |
|HMD|Heard Island and McDonald Islands|Antarctica|Antarctica|0| |
|SGS|South Georgia and the South Sandwich Islands|Antarctica|Antarctica|0| |
|ATF|French Southern territories|Antarctica|Antarctica|0| |
| 48.9 | 91 | 0.713701 | eng_Latn | 0.71988 |
2fe605e17b5e1a091ab23feb24ed407f1c3191d9 | 2,967 | md | Markdown | sdk/eventgrid/azure-eventgrid/swagger/README.PYTHON_T2.md | vbarbaresi/azure-sdk-for-python | 397ba46c51d001ff89c66b170f5576cf8f49c05f | [
"MIT"
] | 8 | 2021-01-13T23:44:08.000Z | 2021-03-17T10:13:36.000Z | sdk/eventgrid/azure-eventgrid/swagger/README.PYTHON_T2.md | vbarbaresi/azure-sdk-for-python | 397ba46c51d001ff89c66b170f5576cf8f49c05f | [
"MIT"
] | 2 | 2021-11-03T06:10:36.000Z | 2021-12-01T06:29:39.000Z | sdk/eventgrid/azure-eventgrid/swagger/README.PYTHON_T2.md | vbarbaresi/azure-sdk-for-python | 397ba46c51d001ff89c66b170f5576cf8f49c05f | [
"MIT"
] | 1 | 2021-05-19T02:55:10.000Z | 2021-05-19T02:55:10.000Z | # Azure EventGrid Client for Python
> see https://aka.ms/autorest
### Configuration
```yaml
title: EventGridPublisherClient
description: EventGrid Python Publisher Client
generated-metadata: false
license-header: MICROSOFT_MIT_NO_VERSION
no-namespace-folders: true
output-folder: ../azure/eventgrid/_generated
source-code-folder-path: ./azure/eventgrid/_generated
input-file:
- https://github.com/ellismg/azure-rest-api-specs/blob/4bb5b76cb8401896b15f1be3fdaac6bd5d299b17/specification/eventgrid/data-plane/Microsoft.EventGrid/stable/2018-01-01/EventGrid.json
- https://github.com/Azure/azure-rest-api-specs/blob/master/specification/eventgrid/data-plane/Microsoft.Storage/stable/2018-01-01/Storage.json
- https://github.com/Azure/azure-rest-api-specs/blob/master/specification/eventgrid/data-plane/Microsoft.AppConfiguration/stable/2018-01-01/AppConfiguration.json
- https://github.com/Azure/azure-rest-api-specs/blob/master/specification/eventgrid/data-plane/Microsoft.Cache/stable/2018-01-01/RedisCache.json
- https://github.com/Azure/azure-rest-api-specs/blob/master/specification/eventgrid/data-plane/Microsoft.ContainerRegistry/stable/2018-01-01/ContainerRegistry.json
- https://github.com/Azure/azure-rest-api-specs/blob/master/specification/eventgrid/data-plane/Microsoft.Devices/stable/2018-01-01/IotHub.json
- https://github.com/Azure/azure-rest-api-specs/blob/master/specification/eventgrid/data-plane/Microsoft.EventHub/stable/2018-01-01/EventHub.json
- https://github.com/Azure/azure-rest-api-specs/blob/master/specification/eventgrid/data-plane/Microsoft.KeyVault/stable/2018-01-01/KeyVault.json
- https://github.com/Azure/azure-rest-api-specs/blob/master/specification/eventgrid/data-plane/Microsoft.MachineLearningServices/stable/2018-01-01/MachineLearningServices.json
- https://github.com/Azure/azure-rest-api-specs/blob/master/specification/eventgrid/data-plane/Microsoft.Maps/stable/2018-01-01/Maps.json
- https://github.com/Azure/azure-rest-api-specs/blob/master/specification/eventgrid/data-plane/Microsoft.Media/stable/2018-01-01/MediaServices.json
- https://github.com/Azure/azure-rest-api-specs/blob/master/specification/eventgrid/data-plane/Microsoft.Resources/stable/2018-01-01/Resources.json
- https://github.com/Azure/azure-rest-api-specs/blob/master/specification/eventgrid/data-plane/Microsoft.ServiceBus/stable/2018-01-01/ServiceBus.json
- https://github.com/Azure/azure-rest-api-specs/blob/master/specification/eventgrid/data-plane/Microsoft.SignalRService/stable/2018-01-01/SignalRService.json
- https://github.com/Azure/azure-rest-api-specs/blob/master/specification/eventgrid/data-plane/Microsoft.Web/stable/2018-01-01/Web.json
- https://github.com/Azure/azure-rest-api-specs/blob/master/specification/eventgrid/data-plane/Microsoft.Communication/stable/2018-01-01/AzureCommunicationServices.json
python: true
v3: true
use: "@autorest/python@5.1.0-preview.7"
``` | 82.416667 | 187 | 0.806202 | yue_Hant | 0.757726 |
2fe63ed02af04230c23b9312969784adc2097a9d | 2,197 | md | Markdown | windows.ui.notifications/badgenotification_badgenotification_93177318.md | scott-moore-ms/winrt-api | bcee574ec4fd60add25a9d1132f2571a351bd42e | [
"CC-BY-4.0",
"MIT"
] | 1 | 2019-04-16T08:13:06.000Z | 2019-04-16T08:13:06.000Z | windows.ui.notifications/badgenotification_badgenotification_93177318.md | scott-moore-ms/winrt-api | bcee574ec4fd60add25a9d1132f2571a351bd42e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | windows.ui.notifications/badgenotification_badgenotification_93177318.md | scott-moore-ms/winrt-api | bcee574ec4fd60add25a9d1132f2571a351bd42e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
-api-id: M:Windows.UI.Notifications.BadgeNotification.#ctor(Windows.Data.Xml.Dom.XmlDocument)
-api-type: winrt method
-api-device-family-note: xbox
---
<!-- Method syntax
public BadgeNotification(Windows.Data.Xml.Dom.XmlDocument content)
-->
# Windows.UI.Notifications.BadgeNotification.BadgeNotification
## -description
Creates and initializes a new instance of the [BadgeNotification](badgenotification.md).
## -parameters
### -param content
The XML content that defines the badge update.
## -remarks
The value attribute can be a number from 1-99 or a status glyph. See the [Badge overview](http://msdn.microsoft.com/library/a64c58bb-d9c9-4c09-a685-4df94fa7dfdd) for a complete list of available images.
## -examples
The following example code uses the [BadgeNotification](badgenotification_badgenotification_93177318.md) method to create a numeric badge notification.
```javascript
var Notifications = Windows.UI.Notifications;
var badgeXml = Notifications.BadgeUpdateManager.getTemplateContent(Notifications.BadgeTemplateType.badgeNumber);
var badgeAttributes = badgeXml.getElementsByTagName("badge");
badgeAttributes[0].setAttribute("value", "26");
// Create a badge notification from XML
var badgeNotification = new Notifications.badgeNotification(badgeXml);
```
## -see-also
[App tiles and badges sample](http://go.microsoft.com/fwlink/p/?linkid=231469), [Badge overview](http://msdn.microsoft.com/library/a64c58bb-d9c9-4c09-a685-4df94fa7dfdd), [Guidelines and checklist for tiles and badges](http://msdn.microsoft.com/library/e825f754-97dd-41c2-aff4-4dfb60eda677), [How to clear a badge](http://msdn.microsoft.com/library/6b2d57e0-51aa-4bce-894e-fa3fd32d77bb), [How to send a glyph or numeric badge in a local notification](http://msdn.microsoft.com/library/6b2d57e0-51aa-4bce-894e-fa3fd32d77bb), [How to set up periodic notifications for badges](http://msdn.microsoft.com/library/96c67773-2e5b-4278-b16d-2f813b16580c), [How to update a badge through push notifications](http://msdn.microsoft.com/library/bb962e30-6c95-4186-8a0e-6683140e17c7), [Badge XML schema](https://docs.microsoft.com/uwp/schemas/tiles/badgeschema/schema-root) | 53.585366 | 858 | 0.780155 | yue_Hant | 0.669583 |
2fe66e43b99f08e05b9f6d1461d3914d76babcc2 | 1,043 | md | Markdown | src/contents/empathy.md | yassermzh/alacolang | c7c4705e5b804ff4f3714b463b65bd3c8fb9dbe0 | [
"MIT"
] | null | null | null | src/contents/empathy.md | yassermzh/alacolang | c7c4705e5b804ff4f3714b463b65bd3c8fb9dbe0 | [
"MIT"
] | null | null | null | src/contents/empathy.md | yassermzh/alacolang | c7c4705e5b804ff4f3714b463b65bd3c8fb9dbe0 | [
"MIT"
] | null | null | null | ---
title: با عزیزمون که بیماری دوقطبی داره چطور همدلی کنیم؟
shortTitle: همدلی با بیمار
date: "2019-07-17"
tags: ['family']
order: 2
---
بهش نگیم: همه اینایی که میگی ذهنی است و کنترلش دست خودته!\
بگیم: من میفهمم که بیماری تو واقعی است و باعث میشه این فکرها و احساسها رو داشته باشی!
نگیم: همه ما یه وقتهایی اینطوری میشیم!\
بگیم: ممکنه من نتونم دقیقا احساست رو درک کنم، ولی تو برای من مهمی و میخوام کمکت کنم!
نگیم: به قسمتهای خوبش فکر کن!\
بگیم: وقتی کم میاری، به خودت بگو فقط یه روز، یه ساعت و یا یه دقیقه دیگه طاقت بیار. هر چقدر که توانش رو داری!
نگیم: تو چیزهای زیادی داری که براش زنده بمونی، چرا میخوای بمیری!\
بگیم: تو برای من مهمی، زندگی تو برای من مهمه!
نگیم: میخوای من چکار کنم؟ من نمی تونم شرایط تو رو تغییر بدم!\
بگیم: به من بگو چطور میتونم بهت کمک کنم؟
نگیم: خودت رو ازین شرایط بیار بیرون!\
بگیم: ممکنه باورش برات سخت باشه، ولی احساسی که الان داری همینطور نمیمونه و تغییر میکنه!
نگیم: خوب میشی، نگران نباش!\
بگیم: تو تنها نیستی، من کنارتم!
<!-- https://www.instagram.com/p/Bz_uHqjIeWQ/ --> | 31.606061 | 108 | 0.709492 | pes_Arab | 0.99894 |
2fe79aaf841533a90c6a5a7a83551fab27b8ad75 | 659 | md | Markdown | docs/examples/luke-study-notes.md | cbcgb-com/sgbs-training | 2fd62d2a6fa9a8b2e554c1b5ad13eac42675cf6f | [
"MIT"
] | 2 | 2020-10-18T20:14:28.000Z | 2020-11-06T19:44:58.000Z | docs/examples/luke-study-notes.md | ericmjl/sgbs-training | c6b21da0450e4824d9d1d84878c23206ae0347b1 | [
"MIT"
] | 1 | 2020-06-07T18:03:01.000Z | 2020-06-07T18:03:01.000Z | docs/examples/luke-study-notes.md | cbcgb-com/sgbs-training | 2fd62d2a6fa9a8b2e554c1b5ad13eac42675cf6f | [
"MIT"
] | null | null | null | # 路加福音查經預備範例
## 觀察
### 背景知識
- 路加福音 -- 作者？架構？目的？
- 文化背景 -- 猶太人對招待客人的習俗？對赦罪的態度？
- 本次經文上下文？
### 本次經文
- 總體架構？
- 主要事件？
- 重點焦點都被放在誰身上？
### 作者措辭
- 哪些字或詞可能會影響我們如何看待這段經文？
- 哪些詞、句是我們現代人不一定懂的？是翻譯問題還是原文問題？
### 翻譯
- 有沒有可能會令人誤解或不解的字、詞、句？
- 英文翻譯？
- 原文翻譯？（可以參考Mounce's Greek Dictionary；要注意，有時候光靠辭典是不足夠的）
### 內容
- 有令人感覺反差或者奇怪的地方嗎？這些是路加使用得巧妙的工具喔！
- 莫名其妙有個女人跑進來？
- 耶穌在沒有聽見西門的話就回復？
- 當時場景下的"punch-line" (Google Translate翻譯為「妙處」）是耶穌的哪句話？
### 解釋+歸納
- 耶穌的比喻：【本體】和【喻體】有那些？
- 耶穌的比喻究竟是對誰說的？
- 耶穌究竟想傳達什麼信息？
### 應用
- 得知了這一切，有什麼自我反省的方向？
- 作為路加福音的作者，路加本人有可能邀請我們思考那些事情呢？
### 其他注意事項
「夫子」（亦「老師」）是西門稱呼耶穌的方式，我個人認為不需要過度解釋，耶穌當時的名聲主要來自行神蹟以及在各地的會堂傳道，西門作為法利賽人，看重耶穌的「老師」身分是一件很自然的事情。
| 13.44898 | 90 | 0.699545 | yue_Hant | 0.961137 |
2fe7acb570d3bba7cb20854687f7cea64aa51113 | 671 | md | Markdown | windows.ui.xaml.automation.peers/automationpeer_isdialog_1486667341.md | angelazhangmsft/winrt-api | 1f92027f2462911960d6be9333b7a86f7b9bf457 | [
"CC-BY-4.0",
"MIT"
] | 199 | 2017-02-09T23:13:51.000Z | 2022-03-28T15:56:12.000Z | windows.ui.xaml.automation.peers/automationpeer_isdialog_1486667341.md | angelazhangmsft/winrt-api | 1f92027f2462911960d6be9333b7a86f7b9bf457 | [
"CC-BY-4.0",
"MIT"
] | 2,093 | 2017-02-09T21:52:45.000Z | 2022-03-25T22:23:18.000Z | windows.ui.xaml.automation.peers/automationpeer_isdialog_1486667341.md | angelazhangmsft/winrt-api | 1f92027f2462911960d6be9333b7a86f7b9bf457 | [
"CC-BY-4.0",
"MIT"
] | 620 | 2017-02-08T19:19:44.000Z | 2022-03-29T11:38:25.000Z | ---
-api-id: M:Windows.UI.Xaml.Automation.Peers.AutomationPeer.IsDialog
-api-type: winrt method
ms.custom: RS5
---
<!-- Method syntax.
public bool AutomationPeer.IsDialog()
-->
# Windows.UI.Xaml.Automation.Peers.AutomationPeer.IsDialog
## -description
Gets a value that indicates whether the element associated with this automation peer is a dialog window.
Equivalent WinUI method: [Microsoft.UI.Xaml.Automation.Peers.AutomationPeer.IsDialog](/windows/winui/api/microsoft.ui.xaml.automation.peers.automationpeer.isdialog).
## -returns
**true** if the element is a dialog; otherwise, **false**.
## -remarks
## -see-also
## -examples
| 23.137931 | 166 | 0.722802 | yue_Hant | 0.386527 |
2fe7bd305f86ef62868558a98c9ea2031fd6e849 | 2,818 | md | Markdown | README.md | pantras/rspec-repeat | 14d51c837982d21c98ffedfabb365d9d0aea6fc3 | [
"MIT"
] | 25 | 2015-09-24T15:51:08.000Z | 2021-05-21T13:20:47.000Z | README.md | rstacruz/rspec-repeat | 14d51c837982d21c98ffedfabb365d9d0aea6fc3 | [
"MIT"
] | 4 | 2015-10-22T03:22:26.000Z | 2018-10-02T06:47:30.000Z | README.md | pantras/rspec-repeat | 14d51c837982d21c98ffedfabb365d9d0aea6fc3 | [
"MIT"
] | 8 | 2015-10-02T20:25:20.000Z | 2021-02-24T15:35:56.000Z | # RSpec::Repeat
> Repeats an RSpec example until it succeeds
```rb
# spec_helper.rb
# Example: Repeat all tests in CI
if ENV['CI']
require 'rspec/repeat'
RSpec.configure do |config|
config.include RSpec::Repeat
config.around :each do |example|
repeat example, 3.times, verbose: true
end
end
end
```
[](https://travis-ci.org/rstacruz/rspec-repeat "See test builds")
<br>
## Advanced usage
### Options
```
repeat example, 3.times, { options }
```
You can pass an `options` hash:
- __clear_let__ *(Boolean)* — if *false*, `let` declarations will not be cleared.
- __exceptions__ *(Array)* — if given, it will only retry exception classes from this list.
- __wait__ *(Numeric)* — seconds to wait between each retry.
- __verbose__ *(Boolean)* — if *true*, it will print messages upon failure.
### Attaching to tags
This will allow you to repeat any example multiple times by tagging it.
```rb
# rails_helper.rb or spec_helper.rb
require 'rspec/repeat'
RSpec.configure do |config|
config.include RSpec::Repeat
config.around :each, :stubborn do |example|
repeat example, 3.times
end
end
```
```rb
describe 'stubborn tests', :stubborn do
# ...
end
```
### Attaching to features
This will make all `spec/features/` retry thrice. Perfect for Poltergeist/Selenium tests that intermittently fail for no reason.
```rb
# rails_helper.rb or spec_helper.rb
require 'rspec/repeat'
RSpec.configure do |config|
config.include RSpec::Repeat
config.around :each, type: :feature do |example|
repeat example, 3.times
end
end
```
In these cases, it'd be smart to restrict which exceptions to be retried.
```rb
repeat example, 3.times, verbose: true, exceptions: [
Net::ReadTimeout,
Selenium::WebDriver::Error::WebDriverError
]
```
### Repeating a specific test
You can also include RSpec::Repeat in just a single test block.
```rb
require 'rspec/repeat'
describe 'a stubborn test' do
include RSpec::Repeat
around do |example|
repeat example, 10.times
end
it 'works, eventually' do
expect(rand(2)).to eq 0
end
end
```
<br>
## Acknowledgement
Much of this code has been refactored out of [rspec-retry](https://github.com/NoRedInk/rspec-retry) by [@NoRedInk](https://github.com/NoRedInk).
<br>
## Thanks
**rspec-repeat** © 2015-2017, Rico Sta. Cruz. Released under the [MIT] License.<br>
Authored and maintained by Rico Sta. Cruz with help from contributors ([list][contributors]).
> [ricostacruz.com](http://ricostacruz.com) ·
> GitHub [@rstacruz](https://github.com/rstacruz) ·
> Twitter [@rstacruz](https://twitter.com/rstacruz)
[MIT]: http://mit-license.org/
[contributors]: http://github.com/rstacruz/rspec-repeat/contributors
| 22.544 | 144 | 0.710788 | eng_Latn | 0.916287 |
2fe8abd38ff22503ff94ca8df6c2f82d9af2e90f | 638 | md | Markdown | src/regions/weimar.md | prototypefund/datenguide | 195f65f0a1d64782ee31d681d5adc836571af92e | [
"MIT"
] | 68 | 2018-10-19T09:01:04.000Z | 2021-06-18T13:32:37.000Z | src/regions/weimar.md | prototypefund/datenguide | 195f65f0a1d64782ee31d681d5adc836571af92e | [
"MIT"
] | 176 | 2018-10-10T14:34:04.000Z | 2022-03-02T14:46:45.000Z | src/regions/weimar.md | prototypefund/datenguide | 195f65f0a1d64782ee31d681d5adc836571af92e | [
"MIT"
] | 8 | 2019-09-30T08:15:58.000Z | 2021-07-12T07:29:56.000Z | ---
id: '16055'
slug: weimar
source_url: 'https://de.wikipedia.org/wiki/Weimar'
comparison: 09162
name: Weimar
name_ext: krsfr. Stadt
state:
slug: thueringen
name: Thüringen
id: '16'
geo:
bbox:
- 11.235
- 50.917
- 11.402
- 51.037
---
Weimar ist eine kreisfreie Stadt in Thüringen in Deutschland, die vor allem für ihr kulturelles Erbe bekannt ist. Weimar liegt an einem Bogen der Ilm südöstlich des Ettersberges, des mit 478 Metern höchsten Berges im Thüringer Becken. Die Stadt ist nach Erfurt, Jena und Gera die viertgrößte Thüringens und liegt etwa auf halbem Wege zwischen Erfurt im Westen und Jena im Osten.
| 30.380952 | 378 | 0.741379 | deu_Latn | 0.995395 |
2fe9404b43693c07645c67baedaa751335d9b71e | 1,099 | md | Markdown | docs/components/Datepicker.md | ryanLees/beeshell | 7810df3ae22f7f6a1344e71ff5bc1b57a1b8460c | [
"MIT"
] | 876 | 2019-05-06T15:34:36.000Z | 2022-03-20T07:35:59.000Z | docs/components/Datepicker.md | ryanLees/beeshell | 7810df3ae22f7f6a1344e71ff5bc1b57a1b8460c | [
"MIT"
] | 96 | 2019-05-08T19:15:12.000Z | 2022-03-11T17:05:17.000Z | docs/components/Datepicker.md | ryanLees/beeshell | 7810df3ae22f7f6a1344e71ff5bc1b57a1b8460c | [
"MIT"
] | 156 | 2019-05-06T08:43:39.000Z | 2022-01-19T15:57:04.000Z | ---
name: Datepicker
title: 日期选择
route: /components/Datepicker
---
# Datepicker
日期选择组件。滚动选择交互，基于 Scrollpicker 实现。
## Usage
### 全部引入
```js
import { Datepicker } from 'beeshell';
```
### 按需引入
```js
import Datepicker from 'beeshell/dist/components/Datepicker';
```
## Examples
**Datepicker 与 BottomModal 组合应用**
## Code
[详细 Code](https://github.com/Meituan-Dianping/beeshell/tree/master/examples/Datepicker/index.tsx)
```jsx
import { Datepicker } from 'beeshell';
<Datepicker
proportion={[2, 1, 1]}
startYear={2010}
numberOfYears={10}
date='2016-03-30'
onChange={(date) => {
console.log(date)
}}
/>
```
## API
### Props
| Name | Type | Required | Default | Description |
| ---- | ---- | ---- | ---- | ---- |
| startYear | number | true | null | 开始年份 |
| proportion | number[] | false | [2, 1, 1] | 数据列 UI 样式占比 |
| numberOfYears | number | true | null | 向后显示几年 |
| date | string | false | null | 选定的日期字符串，'YYYY-MM-DD' 格式 |
| onChange | Function | false | null | 数据变化回调|
组合使用 [Scrollpicker](./Scrollpicker.md) 组件，透传 Scrollpicker 所有 Props
| 18.948276 | 97 | 0.637853 | yue_Hant | 0.477609 |
2fea9d4ae42ea00fd4ce918600cafcb4d9245202 | 1,182 | md | Markdown | docs/faq.md | mikkel1156/drago | 02dd05d609783d0e8e135a27db6899b4b6c5abdb | [
"Apache-2.0"
] | 882 | 2020-03-25T19:27:17.000Z | 2022-03-31T04:18:14.000Z | docs/faq.md | mikkel1156/drago | 02dd05d609783d0e8e135a27db6899b4b6c5abdb | [
"Apache-2.0"
] | 35 | 2020-06-24T12:15:51.000Z | 2021-12-10T10:39:21.000Z | docs/faq.md | mikkel1156/drago | 02dd05d609783d0e8e135a27db6899b4b6c5abdb | [
"Apache-2.0"
] | 41 | 2020-06-26T13:23:18.000Z | 2022-02-28T11:21:56.000Z | # FAQ
> [!WARNING]
> This section is still a work-in-progress. If you think you can contribute, please see our [contribution guidelines](docs/../../../contributing.md).
## Why Drago?
WireGuard® is an extremely simple yet fast and modern VPN that utilizes state-of-the-art cryptography. It aims to be faster, simpler, leaner, and more useful than IPsec, while avoiding the massive headache. It intends to be considerably more performant than OpenVPN. WireGuard is designed as a general purpose VPN for running on embedded interfaces and super computers alike, fit for many different circumstances. Initially released for the Linux kernel, it is now cross-platform and widely deployable, being regarded as the most secure, easiest to use, and simplest VPN solution in the industry.
WireGuard presents several advantages over other VPN solutions, but it does not allow for the dynamic configuration of network parameters such as IP addresses and firewall rules. Drago builds on top of WireGuard, allowing users to dynamically manage the configuration of their VPN networks, providing a unified control plane for overlays spanning from containers to virtual machines to IoT devices. | 118.2 | 596 | 0.803723 | eng_Latn | 0.999371 |
2feb2a337845ecd7cfa8b35612ae7558cd0d3ed7 | 23,436 | md | Markdown | docs/OpenAF-Channels.md | LeandroFernandes5/openaf | ac72b176d257b378322c917692955ce847e5da6d | [
"Apache-2.0"
] | 6 | 2017-11-27T16:47:42.000Z | 2021-08-22T12:05:37.000Z | docs/OpenAF-Channels.md | LeandroFernandes5/openaf | ac72b176d257b378322c917692955ce847e5da6d | [
"Apache-2.0"
] | 143 | 2017-08-17T01:51:54.000Z | 2022-03-20T04:23:09.000Z | docs/OpenAF-Channels.md | LeandroFernandes5/openaf | ac72b176d257b378322c917692955ce847e5da6d | [
"Apache-2.0"
] | 6 | 2017-08-18T15:37:49.000Z | 2021-12-06T20:47:09.000Z | # OpenAF Channels <a href="/"><img align="right" src="images/openaf_small.png"></a>
## What are channels?
By definition channels should allow for the flow of data between functionalities or processes. In a similar fashion, OpenAF channels allow the flow of data between two points or functionalities. These two points can be in on the same OpenAF script or in two different scripts (on the same machine or differents).
Let's consider a simple example: _Imagine that you have a script, called copyFiles.js, that copies files between a SFTP server and a local server. Additionally you have a preProcess.js script that will pre-process the copied files whenever they are copied. How do you make the name of the copied files “flow” to the preProcess.js script? You can build a channel between copyFiles.js and preProcess.js._
## How is data represented on a channel?
Data in OpenAF channels is represented by a set of key/value pairs. This set can be handle as a Map (where you can invoke get/set methods) or as a Queue (where you can invoke push/pop/shift methods) by the order a key/value was added/modified.
The keys and values used can be simple Strings or JSON Maps.
Using the example: _For every copied file the copyFiles.js script can set a key/value pair like the following_:
````javascript
Key = { "filename": "someData1234.dat" }
Value = {
"filename": "someData1234.dat",
"filepath": "/some/input/folder/someData1234.dat",
"dateReceived": "2016-12-02 12:34:56",
"dateCopied": "2016-12-02 12:35:05"
}
````
Then preProcess.js can simply invoke the shift method on the same channel to obtain the first key/value pair added to the channel.
## How to be notified of a change on a channel?
If a channel allows for the flow of data between two points how would the target point know that the source point as added or changed data in a channel? The answer is channel subscription. For any given OpenAF channel you can subscribe it so a function provided by you can be callback whenever any addition or change is made on a channel.
These subscriptions are non-blocking meaning that changing data on a channel won't be delayed by the subscriptions it holds at any given point. Each subscription will actually be executed on a separate thread in parallel.
At any time you can unsubscribe a previous channel subscript
Using the example: T_he copyFiles.js will add a key/value pair per each file it successfully copies in a “CopiedFiles” channel. The preProcess.js just needs to subscribe the “CopiedFiles” channel. Each time copyFiles.js adds a file, a provided preProcess.js function will be executed without delaying copyFiles.js functionality._
## Channels implementations
OpenAF channels can have different implementations on how the key/value set is stored and shared while maintaining the same interface methods. This means that, as a general rule, whatever implementation a channel uses the get/set/push/pop/etc… methods should be available.
Currently there are several different implementations built-in (on the included OpenWrap Channel library):
* Big (default until 20181210)
* DB
* Ignite
* Ops
* Remote
* Cache
* ElasticSearch
* MVS
* Simple (default from 20181210)
* Buffer
* Proxy
* Etcd
* Dummy (for testing)
And some available through oPacks:
* Mongo (mongo opack)
* Etcd3 (etcd3 opack, via GRPC)
* DynamoDB (aws opack)
The default implementation, until version 20181210, Big uses the OpenWrap Big Objects functionality (from the OpenWrap Object library). You don't need to know how this functionality works internally. For the sake of simplicity let's assume it's like an internal JavaScript Array of a Map with a Key and Value.
The remote implementation allows for the creation of a channel whose implementation is held on a different OpenAF script that can be accessed for a REST API. We will get into the details of how this is done and setup later but this implementation is important to access channels with local script storage (like the default implementation is).
### Channel basics
To access the channel functionality you can use functions in the ow.ch (OpenWrap Channel) library or the common shortcuts: $channel or $ch. We will use the $ch to show the channels basics.
The $ch is actually a javascript function that takes the unique name of a channel as it's parameter. This name only needs to be unique in a single OpenAF script.
#### Channel maintenance
Before using a channel you always need to create it.
````javascript
> $ch("mychannel").create() // default
> $ch("mychannel").create(true, "myimpl", {"option1": "value1"}) // to create a channel with a myimpl implementation
````
You can list the current created channels by:
````javascript
> $ch().list()
````
When you no longer need a channel and corresponding data you can destroy it by:
````javascript
> $ch("mychannel").destroy()
````
#### Channel value get/set/unset
You can add/set a key/value on a channel by:
````javascript
> $ch("mychannel1").set(1, "hello")
> $ch("mychannel1").set(2, "hello")
````
The keys and values can be string, numbers or maps:
````javascript
> $ch("mychannel").set({date: "20100601", person: "me"}, {data: ... })
````
You can add an array of map entries just indicating which map entries should be considered for keys
````javascript
> $ch("mychannel").setAll(["date", "person"], anArrayOfData)
````
To retrieve data you simply use the full key:
````javascript
> $ch("mychannel1").get(1)
> $ch("mychannel").get({date: "20100601", person: "me"})
````
To delete any entry just use the full key again:
````javascript
> $ch("mychannel").unset(1)
> $ch("mychannel").unset({date: "20100601", person: "me"})
````
To get a list of all the keys of a channel:
````javascript
> $ch("mychannel").getKeys()
> $ch("mychannel").getSortedKeys() // by the last changes
````
To get all elements of a channel:
````javascript
> $ch("mychannel").getAll()
````
To get the number of elements in a channel:
````javascript
> $ch("mychannel").size()
````
If you need to check and set an entry in one single “transaction” you just need to provide the value map element that needs to be checked and if true set the entry with the new value (usually to ensure that just one thread will actually change an entry):
````javascript
> $ch("mychannel").getSet({status: "toExecute"}, {jobId: 123}, { jobId: 123, runCommand: "processStuff.sh", status: "executing"})
````
Note: Usually it's a good practice to have the key elements as part of the value also thus setAll keeps the key elements also on the value map for each array element.
#### Using a channel as a queue
Ordering in channels is, by default, over the last modify time stamps. To retrieve the first element removing it from the channel:
````javascript
> var myvalue = $ch("mychannel").shift()
````
To remove the last:
````javascript
> var myvalue = $ch("mychannel").pop()
````
You can even add new elements using push:
````javascript
> $ch("mychannel").push(myvalue)
````
#### Channel forEach
To execute a function over all elements:
````javascript
> $ch("mychannel").forEach(function(key, value) {
// do stuff with key and value
})
````
#### Channel subscription
One of the most important functions of a channel is the ability to subscribe it for any change:
````javascript
> $ch("mychannel").subscribe(function(aChannelName, aOperation, aKeyOrKeys , aValueOrValues) { ... }, onlyFromNowOn)
````
The subscribe function will receive:
* aChannelName identifying the channel (only useful when you want to use a generic subscribing function);
* aOperation which will have a value of “set”, “setall” or “unset”;
* aKeyOrKeys representing the key or keys for the setall operation;
* aValueOrValues representing the value or values for the setall operation.
Once a function is provided subscribing a channel, it will be executed with a “set” operation for all existing elements (thus syncing all existing channel elements). You can override this behavior by setting onlyFromNowOn to true.
The subscribing function will always run in a separate thread so that the channel basic set, setall and unset operations performance is not directly affected by the number or performance of the subscribing functions. This is currently by design option.
For each subscribe instruction a corresponding UUID will be returned. You can use this UUID to unsubscribe the function from the channel if needed:
````javascript
> $ch("mychannel").unsubscribe(anUUID)
````
In advanced implementations you can also stop all subscribing functions running (called jobs) by executing:
````javascript
> $ch("mychannel").stopJobs()
````
This is usually only helpful when you want to stop a channel and all subscribing functions quickly. Otherwise if you just want to know when all current jobs finish you can use:
````javascript
> $ch("mychannel").waitForJobs(aLimitTimeout)
````
#### Persisting Channel values
A simple subscribe function is to keep an update filesystem copy of the channel values. There is a simple basic implementation built in. To add the built in subscribe function to a channel just execute:
````javascript
> $ch("mychannel").storeAdd("mychannel.channel", ["date", "person"])
````
This will also check if the file already exists and restore values from it so you need to provide the list of values to use as key. The contents are compressed by default and it's just a simple JSON file meaning you could use this function to read and maintain JSON file based data, for example. You can even create channels with different keys over the same data.
To just restore the values just use:
````javascript
> $ch("mychannel").storeRestore("mychannel.channel", ["date", "person"])
````
Do be aware that there is no locking mechanism preventing access to the file and that current implementation (e.g. memory, database, remote, etc…) contents will always override the filesystem values except, of course, on the initial data restore. So changing the file while a channel is “live” won't change it and on the next set/unset/setall all data on the file will be overwritten. For these reasons it's suitable to be used for small/medium size channels depending on the values size and keeping channel data always preserved. If you are looking for a solution to store large sized channels you can either use getAll or forEach to save them when needed or build a more sophisticated subscribe function (for example: keeping each value as a separate file on a folder structured indexed by keys).
#### Details specific to each implementation
### DB
*tbc*
### Ignite
The Ignite implementation encapsulates access to an Ignite data grid using functionality from the Ignite plugin. Upon creation the shouldCompress is ignored and the options available are not mandatory:
* *gridName* - The Ignite grid name to access
* *ignite* - A Ignite object from the Ignite plugin that you previously instatiated.
The name of the channel is actually the name of Ignite data grid cache that will be used. All functionality is available.
### Ops
The ops or operations implementation is a special channel that won't store values but will actually execute a specific function for each key and return the corresponding value (e.g. usefull for exposing functionality). That function will receive as argument the value map. On the creation the shouldCompress is obviously ignored and the options is actually the map of functions as demonstrated on the next example:
````javascript
$ch("myops").create(1, "ops", {
"help": () => { return { "add": "Add an argument a with b" } },
"add" : (v) => { return { result: v.a + v.b }; }
});
````
The to use it:
````javascript
> $ch("myops").get("help");
{
"add": "Add an argument a with b"
}
> $ch("myops").set("add", { a: 2, b: 3 });
{
"result": 5
}
````
Due to the nature of this implementation setAll, pop, shift and unset are not implemented and will just execute returning undefined.
### Cache
The cache implementation lets you define a channel that will use a provided function to retrieve and return the corresponding value given a key. The value will be kept in another OpenAF channel acting as a cache from which the value will be retrieved for a specific TTL (time-to-live) in ms. After the TTL the function will be executed again and the result kept in the other OpenAF channel. This is useful when you know that you will have a lot of gets but it's slow to retrieve each value and a key/value cache mechanism is usefull.
To create, the shouldCompress option is ignored and the following options can be used:
| Option | Mandatory | Type | Description |
|--------|-----------|------|-------------|
| func | Yes | Function | The function that receives a key and returns the corresponding value to be returned and cached for a TTL. |
| ttl | No | Number | The cache time-to-live in ms (defaults to 5 seconds) |
| ch | No | String | The name of the secundary OpenAF channel to store the cached values. This channel can already exist (for example if you don't want to cache values in memory). Defaults to the current name suffixed with "::__cache". Note: Upon "destroy" of the cache channel this channel will be also destroyed. |
The set/setAll functions will actually ignore the value provided and call the function with the key provided updating the cache value and ignoring/reseting the current TTL.
### ElasticSearch
The ElasticSearch implementation encapsulates the access to an ElasticSearch server/cluster. Pretty much all OpenAF channel functionality is available and there are some extensions to enable the use of ElasticSearch functionality. On creation, the shouldCompress is ignored but the options map should contain:
| Option | Mandatory | Type | Description |
|--------|-----------|------|-------------|
| index | Yes | String/Function | The ES index string or a function that returns the name (see also ow.ch.utils.getElasticIndex) |
| idKey | No | String | If the ES index uses an id field you can specify it (defaults to '_id') |
| url | Yes | String | The URL string to access the ES cluster/server using HTTP/HTTPs |
| user | No | String | If the ES cluster/server requires authentication credentials, you can specify the username. |
| pass | No | String | If the ES cluster/server requires authentication credentials, you can specify the password (encrypted or not). |
Examples:
````javascript
> $ch("myvalues").create(1, "elasticsearch", { url: "http://es.local", index: "myvalues" });
> $ch("values").create(1, "elasticsearch", { url: "http://es.local", index: ow.ch.utils.getElasticIndex("value", ow.ch.utils.getElasticIndex("values", "yyyy.w"))});
````
The getAll/getKeys functions accept an extra argument to provide an ES query map to restrict the results.
Nevertheless please use the ElasticSearch oPack that encapsulates more functionality not available through the OpenAF channel implementation and enables the easy creation of ElasticSearch channels.
### MVS
MVS or MVStore is the a "persistent, log structured key-value store" which is the actual storage subsystem of H2. It's fast, small and a good alternative to keeping channel data in memory at all althought it can also keep it in-memory. The shouldCompress option specifies if the entire data structure should be compress by MVS or not. Pretty much all channels functionality is available. Additionally you can specify on the options map:
| Option | Mandatory | Type | Description |
|--------|-----------|------|-------------|
| file | No | String | Specifies the file where MVS will store data to. If not defined it stores data in-memory. |
| compact | No | Boolean | If yes upon channel creation/destruction it will run the MVS compact operation over the file trying to save storage space. |
| map | No | String/Function | If not defined defaults to the string "default". Each file can contain several "collections" or maps of values. If defined as a function, the function will receive the key in use as an argument and it should return the map name to use (e.g. usefull for sharding) and a default map name when a key is not provided. |
Examples:
````javascript
> $ch("test").create(1, "mvs"); // Creates an in-memory mvs channel for map 'default'
> $ch("mymap").create(1, "mvs", { map: "mymap" }); // Creates an in-memory mvs channel for map 'mymap'
````
````javascript
// Creates a mvs file 'myfile.db' with a map 'mymap'
$ch("myfile").create(1, "mvs", { file: "myfile.db", map: "mymap" });
// Creates a mvs file 'myfile.db' with distributing values using the field date from the key to map names like "logs-yyyy.MM.dd"
var func = (key) => {
key = _$(key).isMap().default({});
var d = _$(key.date).isDate().default(new Date);
return "logs-" + ow.format.fromDate(d, "yyyy.MM.dd");
};
$ch("myfile").create(1, "mvs", { file: "myfile.db", map: func });
````
**Note:** function based map channels should only be used for adding/modifying values. For accessing you should create specific channels for the specific map name. Keep in mind that MVS supports concurrent read and write.
There are utilitary functions for mvs files in ow.ch.utils.mvs.* namely:
* *list(aFile)* - returning an array with all maps contained on a MVS file.
* *remove(aFile, aMapToRemove)* - deleting any map contained on a MVS file.
* *rename(aFile, oldMapName, newMapName)* - to rename an existing map contained on a MVS file.
### Simple
The simple implementation, default since version 20181210, instead of using the OpenWrap Big Objects uses plain javascript objects (e.g. arrays and maps). It benefits on add/modify performance but uses more memory in the overall for large or varying size values. All functionality is available and similar behaviour to the default implementation should be expected althought the shouldCompress option is ignored.
To create one just:
````javascript
> $ch("test").create(1, "simple")
````
### Buffer
The buffer implementation acts as a "proxy" to another channel. It can buffer values for a specific time and/or number of values before sending it to a target channel.
To create one just:
````javascript
> $ch("buffer").create(1, "buffer", {
bufferCh : "targetCh",
bufferIdxs : [ "key1", "key2" ],
bufferByTime : 2500,
bufferByNumber: 100,
bufferTmpCh : "buffer::__buffer"
});
````
### Proxy
This implementation allows to intersect channel request to another target channel. It can be useful to collect channel usage statistics using *ow.ch.utils.getStatsProxyFunction*.
To create a proxy just:
````javascript
> $ch("proxy").create(1, "proxy", {
chTarget : "targetCh".
proxyFunc : function(aMap) {
// Function that receives a map (by reference that can be changed)
// with: op (operation), name (target channel), function (where
// applicable), full (where applicable), match (the match of getSet),
// k (the key(s)), v (the value(s)) and timestamp. If this function
// returns something no operation will be executed on the chTarget
// and the value returned by the function will be the value returned
// by this channel.
}
});
````
### Etcd
This OpenAF channel implementation interacts with a [Etcd](https://etcd.io) cluster through HTTP/HTTPs. You can use the Etcd3 oPack to interact via GRPC.
To create an etcd channel just:
````javascript
> $ch("etcd").create(1, "etcd", {
url: "http://my.etcd.cluster:2379",
folder: "myFolder",
throwExceptions: false,
default: { result: 0 }
});
````
The options used are:
| Option | Mandatory | Type | Description |
|--------|-----------|------|-------------|
| url | Yes | String | The URL to connect to the Etcd cluster |
| folder | No | String | The key prefix to use. |
| throwExceptions | No | Boolean | If true, whenever there is an error (e.g. communication error, etc...) an exception will be thrown. |
| default | No | Map | If throwExceptions is false what should be returned on a get function in case of error. |
### Dummy
In this implementation all functionality will simple return without executing anything. It's mainly use for testing proposes.
### Mongo (through the Mongo oPack)
Please check the Mongo oPack documentation (tbc).
### Etcd3 (through the Etcd3 oPack)
This implementation differs from the "etcd" implementation since it will communicate via GRPC instead of HTTP.
Please check the Etcd3 oPack documentation (tbc).
### Dynamo (through the AWS oPack)
This implementation uses the AWS API directly to interact with AWS's Dynamo DB.
### Exposing channels externally
#### Remote channels
For whatever channel you have created you can expose it externally through a REST protocol. You can achieve this easily by executing for an existing channel:
````javascript
> $ch("mychannel").expose(1234, "/mychannel")
````
This creates a HTTP server on the port 1234 that will respond to REST queries on the URI “/mychannel”. You can create a remote channel on another openaf script or session to communicate with it by executing:
````javascript
> $ch("remoteChannel").createRemote("http://the.other.guy:1234/mychannel")
````
The channel “remoteChannel” can now be used normally. All operations will be relayed back to the original channel. But if you subscribe the “remoteChannel” you won't receive any set/setall/unset operations from “mychannel”.
### Peering channels
Peering is an advance mode of using remote channels where instead of unidirectional communication between from a source channel to a target channel there is actually bidirectional communication trying to keep both channels up to date.
On side A you simply execute (similar to *expose*):
````javascript
> $ch("mychannelOnA").peer(8010, "/mychannel", [ "http://the.other.guy:8011/mychannel" ]);
````
and on the other side B:
````javascript
> $ch("mychannelOnB").peer(8011, "/mychannel", [ "http://the.original.guy:8010/mychannel" ]);
````
If you look carefully on will notice the peer is actually contained on an array because you can actually have a list of peers (that should include all for each side). Let's add a side C:
On side A:
````javascript
> $ch("mychannelOnA").peer(8010, "/mychannel", [ "http://the.other.guy:8011/mychannel", "http://the.extra.guy:8012/mychannel" ]);
````
on side B:
````javascript
> $ch("mychannelOnB").peer(8011, "/mychannel", [ "http://the.original.guy:8010/mychannel", "http://the.extra.guy:8012/mychannel" ]);
````
and on side C:
````javascript
> $ch("mychannelOnC").peer(8012, "/mychannel", [ "http://the.original.guy:8010/mychannel", "http://the.other.guy:8011/mychannel" ]);
````
The peering functionality is a little similar to the Ignite type with the following differences:
* Subscribers will get triggered in each side upon data change
* Each side should mirrors all data
* Static list of peers
### Channels REST API
The next table describe in more detail the REST API to communicate with a exposed/peered channel:
| Channel operation | HTTP Method | URI |
|:------------------|:------------|:----|
| getAll | GET | [base uri]/o/a |
| getKeys | GET | [base uri]/o/k |
| getSortedKeys | GET | [base uri]/o/s |
| getSet | PUT | [base uri]/o/es/m/[match]/k/[key]/t/[timestamp] |
| set | PUT | [base uri]/o/e/k/[key]/t/[timestamp] |
| setAll | PUT | [base uri]/o/a/k/[key]/t/[timestamp] |
| get | GET | [base uri]/o/e/k/[key] |
| unset | DELETE | [base uri]/o/e/k/[key]/t/[timestamp] | | 45.069231 | 798 | 0.729988 | eng_Latn | 0.99585 |
2feb4874aceabb2b243f0c20061655e930897762 | 1,841 | md | Markdown | README.md | worldofprasanna/obuspa | c83f89af02edb1969e5beecbf12dfc40fe817c54 | [
"BSD-3-Clause"
] | null | null | null | README.md | worldofprasanna/obuspa | c83f89af02edb1969e5beecbf12dfc40fe817c54 | [
"BSD-3-Clause"
] | null | null | null | README.md | worldofprasanna/obuspa | c83f89af02edb1969e5beecbf12dfc40fe817c54 | [
"BSD-3-Clause"
] | null | null | null | # OB-USP-AGENT
Open Broadband-User Services Platform-Agent (OB-USP-Agent) is an open source project that is focused on creating a reference implementation of the User Services Platform (USP) [specification](https://usp.technology) from an "Agent" perspective. USP is a remote management and control protocol where management entities are separated between the Agent and the Controller. A USP Agent is responsible for exposing a set of "Service Elements" (essentially, a data model composed of objects and parameters that represent a specific set of functionality) for consumption by a Controller. While USP is capable of being used in many different environments, the home network is expected to be the most common environment, and in this environment a USP Agent would reside in a piece of Customer Premise Equipment (CPE), e.g. broadband home router, Wi-Fi access point, IoT gateway.
## Quick Start
For running the agent using Docker and Docker compose, use the following steps,
#### Step 1
```
$ git clone git@github.com:worldofprasanna/obuspa.git
```
#### Step 2
```
$ git clone git@github.com:DreamsOfImran/obuspc.git
```
#### Step 3
```
$ cd obuspc
```
#### Step 4
```
$ docker build -t obuspc .
```
#### Step 5
```
$ cd ../obuspa
```
#### Step 6
```
$ docker build -t obuspa .
$ docker-compose up
```
This will bring up USP Agent and ActiveMQ which can communicate with each other.
For build instructions, please refer to [QUICK_START_GUIDE](https://github.com/BroadbandForum/obuspa/blob/master/QUICK_START_GUIDE.md).
## Contributing
Thank you for your interest in contributing! Please refer to [CONTRIBUTING.md](https://github.com/BroadbandForum/obuspa/blob/master/CONTRIBUTING.md) for guidance.
## Wiki Access
Please also see our [WIKI](https://github.com/BroadbandForum/obuspa/wiki) for more details about the project.
| 40.021739 | 872 | 0.757197 | eng_Latn | 0.972424 |
2fec79721f3a07557bfc159856bebd57886cf777 | 1,038 | md | Markdown | README.md | chetansadhu/Behavioral-Cloning | bcedf03572cc7ddaa89928085c551333afbca935 | [
"MIT"
] | null | null | null | README.md | chetansadhu/Behavioral-Cloning | bcedf03572cc7ddaa89928085c551333afbca935 | [
"MIT"
] | null | null | null | README.md | chetansadhu/Behavioral-Cloning | bcedf03572cc7ddaa89928085c551333afbca935 | [
"MIT"
] | null | null | null | # **Behavioral Cloning**
[](http://www.udacity.com/drive)
Overview
---
In this project convolutional neural network is built to clone the driving behavior for autonomous cars. Using a simulator car is driven around the track and camera images are taken with steering angle. A neural network is built to predict the steering angles for a given image frame in the autonomous mode.
Folder Structure
---
* `model.py` - Python code for the neural network training and validation
* `drive.py` - Python code for connecting and communicating with the simulator
* `video.py` - Python code to record video from images
* `model.h5` - Keras model file
* `track1.mp4` - Video of car running on 1st track
* `track2.mp4` - Video of car running on 2nd track
* `training data` can be found [here](https://drive.google.com/file/d/1VCiQd__1LA5zdQ4TkxofbDKCO9OILa7x/view?usp=sharing)
* `analysis` - Folder containing some sample images and stats images | 61.058824 | 307 | 0.768786 | eng_Latn | 0.970817 |
2fed4be8fa463b821a0dfa48da0e8e84fa66b11d | 5,594 | md | Markdown | _posts/2018-12-26-Download-perkins-p3-diesel-engine-workshop-manual.md | Luanna-Lynde/28 | 1649d0fcde5c5a34b3079f46e73d5983a1bfce8c | [
"MIT"
] | null | null | null | _posts/2018-12-26-Download-perkins-p3-diesel-engine-workshop-manual.md | Luanna-Lynde/28 | 1649d0fcde5c5a34b3079f46e73d5983a1bfce8c | [
"MIT"
] | null | null | null | _posts/2018-12-26-Download-perkins-p3-diesel-engine-workshop-manual.md | Luanna-Lynde/28 | 1649d0fcde5c5a34b3079f46e73d5983a1bfce8c | [
"MIT"
] | null | null | null | ---
layout: post
comments: true
categories: Other
---
## Download Perkins p3 diesel engine workshop manual book
" "No. though he's admittedly hard-pressed to see anything either poetic or warriorlike about clutching a a million questions in life but only one answer-" from the reindeer-Chukches for train-oil, it will not neighbourhood a man was overtaken by such a storm of drifting snow The firelight dimmed as thickening haze screened it, grabbed Amos by the hand, the wineglass had shattered, a brown, isn't it. In cloning, that the whalers the dark night brings forth the moon!" he actually heard them spoken, will have an influence on the development of the organism, with bright white hair, I shouldn't tell you this myself, B. As she'd explained to Tom, with the twin fuses on the blacktop Siberian Polar Sea, and this impotence suggested that she might never in the middle. Large, locking them away to keep them harmless or giving them to a wizard in his hire to do with "Of course not" an alarm hundreds of dead young are found on the shore, for the love of God the Most High, covered with ice and awnings create shaded areas for socializing. The year-old Kaitlin, often taking his arm. ' Abou Sabir, rounded, But with, c. Like an oven timer: The goose is cooked. 6 4. The sandy plain is of with the work of the sailors, as though Victoria were using it as a plate warmer, but Junior was shaken by the mere thought of such a "Yeah, ii, glittering q. Curiosity and the measured payout of a full bladder lead Old Yeller through a maze of recreational The young woman's face pales further and her eyes become icier, less when it's dry, one-third, Agnes crazily considered wanted to see him. ); the last-named is the most common. Let me see, afraid of causing pain even with a gentle touch, K, Joey was [Illustration: JAPANESE BRIDGE. "Closer," he said. "He seems to be a good man. pump up any rage at the accusation that philosophical motives drove her to the name-Bartholomew?" Chapter 57 Looming, for Panglo. " Quoth I, puts it on the floor I told him I hoped he was right, and something in her face made him nervous, he quickly searched the small house, if at all, are you there?"--she turned to Tom. "I'll always know your face," he promised. life, it does. little gravy. Teelroy, on into the long valley where Otter had taken Licky the first day he was there, FSF seems to be largely immune from trends, O king of the age," added the vizier, she was at her sister's side, and oppression," Preston continued. Formerly the hunters almost every year, he had suspected that It's true, a few stray passed away in the coma. _ glimpsed in the mirror on the sun visor. "Selene isn't the evil genius you think, and this led to the laying of a coopful of Why-did-the chicken-cross-the-road jokes. But "What's this all about, the can be effected in a few moments, and now he knew he hadn't the nerve to do so, and probably also carbonic acid, the only sculpture I've acquired is Poriferan's, Barry: officially, but they aren't hardly ever smart, occupied by devil's bow and arrows, and the jasmine and incense, Seraphim was a virgin. The contrived welcome with the perkins p3 diesel engine workshop manual of cookies either had not fooled him or had "I won't say which studio," Teelroy added. hard and repeatedly, into the alley, nearly knocking it over, like a metal hooked up to utilities. "Now, moving her eyes only. "Kalens may have to hide himself away in a shell," she said. " When the king heard these tidings of Aamir, and she would Celestina told herself that she was coping well, the saltless land doesn't have an accommodating natural glow. manufacture of perkins p3 diesel engine workshop manual. departed from thence, must make certain, "and not my own clothes, and then agreed? " Colman groaned to himself. He was nobody, my ember of fire, which appeared to only three writers who have contributed as much fiction as Mr, but a would-be stage magician eventually needed perkins p3 diesel engine workshop manual mentor to reveal the most closely guarded secrets of illusion and to help him master the skills of deception needed for the highest-level prestidigitation. his little hands, "He's in Oregon, four maps. " plasting regularly and. you figure out the rhythm of it. " Yet he was following Otter. He reached out towards Yaved, the fifth as a third, perkins p3 diesel engine workshop manual not because the suit's from Bibliography 9 caused by the objects of the journey--scientific brow. Yet in the aftermath, ignored, he won't argue about being left afoot on these salt flats, motion is commotion, sir," Curtis replies, immediately to renew their proofs of friendship. I am a prisoner Now the Persian had a mameluke, if scanty change from the tiresome preserved back against one wall of the maze, though not for the same reasons that the Toad or Vol I page 43 "Middendorf" changed perkins p3 diesel engine workshop manual "Middendorff" world created by a superior intelligence, telling Barry that he thought his handshake was perkins p3 diesel engine workshop manual sincere, the reason is easily explained why the He would have done it. It was just a spectacular hour's ride away; the shopping was immeasurably better, and that they might see more forwards across the immeasurable deserts of Siberia, forty thousand had been searched. In the center of the and art collections of that time, then walked into the passenger compartment without turning perkins p3 diesel engine workshop manual the cabin lights to join Colman. 26, Ogion thought. Slow deep breaths. | 621.555556 | 5,480 | 0.784054 | eng_Latn | 0.999936 |
2fedb579680aa47e993628222069c92369160902 | 131 | md | Markdown | README.md | HuTheDesigner/Challenge_3 | a17bc05de39817fc421c109739e41717f9debae3 | [
"Apache-2.0"
] | null | null | null | README.md | HuTheDesigner/Challenge_3 | a17bc05de39817fc421c109739e41717f9debae3 | [
"Apache-2.0"
] | null | null | null | README.md | HuTheDesigner/Challenge_3 | a17bc05de39817fc421c109739e41717f9debae3 | [
"Apache-2.0"
] | null | null | null | # Challenge_3
Just some financial diagrams and displays graphically plotted seeking out data patterns.
Full Application Submitted.
| 32.75 | 88 | 0.847328 | eng_Latn | 0.994735 |
2fee24763e3d9f5c00b00a7fa3f073b8a708db70 | 1,307 | md | Markdown | biztalk/core/xml-information-set-elements-in-the-xml-disassembler-pipeline-component.md | OPS-E2E-PPE/biztalk-docs.zh-CN | 4783f895d987cb13d919c7bd12ae52975b972123 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | biztalk/core/xml-information-set-elements-in-the-xml-disassembler-pipeline-component.md | OPS-E2E-PPE/biztalk-docs.zh-CN | 4783f895d987cb13d919c7bd12ae52975b972123 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | biztalk/core/xml-information-set-elements-in-the-xml-disassembler-pipeline-component.md | OPS-E2E-PPE/biztalk-docs.zh-CN | 4783f895d987cb13d919c7bd12ae52975b972123 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: XML 拆装器管道组件中的 XML 信息集合元素 |Microsoft Docs
ms.custom: ''
ms.date: 06/08/2017
ms.prod: biztalk-server
ms.reviewer: ''
ms.suite: ''
ms.tgt_pltfrm: ''
ms.topic: article
helpviewer_keywords:
- XML Disassembler [pipeline component], information set
- XML Disassembler [pipeline component], processing instructions
- pipeline components, XML Disassembler
ms.assetid: cc82344c-6c4b-4154-a662-0b7ae5caad30
caps.latest.revision: 6
author: MandiOhlinger
ms.author: mandia
manager: anneta
ms.openlocfilehash: 2b9d2b581a327f8d7009794338d431a2358db748
ms.sourcegitcommit: 381e83d43796a345488d54b3f7413e11d56ad7be
ms.translationtype: MT
ms.contentlocale: zh-CN
ms.lasthandoff: 05/07/2019
ms.locfileid: "65298480"
---
# <a name="xml-information-set-elements-in-the-xml-disassembler-pipeline-component"></a>XML 拆装器管道组件中的 XML 信息集合元素
XML 拆装器处理 XML 信息集合元素，如下所示。
|元素|Description|
|-------------|-----------------|
|comment|注释保留在文档;但是，不会保留 XML 信封中的任何注释。|
|CDATA|CDATA 保留在文档中。 不保留显示在文档 （例如，在一个信封） 外部的 CDATA 元素。|
|处理指令|XML 拆装器保留显示中或之前的 XML 文档的处理指令。 不保留处理指令，使其不显示在 XML 文档或之前或之后信封。|
|XML 声明|删除所有传入 XML 消息的 XML 声明元素。|
## <a name="see-also"></a>请参阅
[XML 拆装器管道组件](../core/xml-disassembler-pipeline-component.md)
[如何配置 XML 拆装器管道组件](../core/how-to-configure-the-xml-disassembler-pipeline-component.md) | 34.394737 | 112 | 0.749809 | yue_Hant | 0.405551 |
2feef0ce011e1d83a89dbc1a6bee50e188d753a7 | 3,722 | md | Markdown | content/publication/impact-of-climate-change-on-precipitation-patterns-in-houston-texas-usa/index.md | zhiyingli-geo/zhiyingli-geo | c8499ef0f4daa069cc973b788d754d0cc3ca9035 | [
"MIT"
] | null | null | null | content/publication/impact-of-climate-change-on-precipitation-patterns-in-houston-texas-usa/index.md | zhiyingli-geo/zhiyingli-geo | c8499ef0f4daa069cc973b788d754d0cc3ca9035 | [
"MIT"
] | null | null | null | content/publication/impact-of-climate-change-on-precipitation-patterns-in-houston-texas-usa/index.md | zhiyingli-geo/zhiyingli-geo | c8499ef0f4daa069cc973b788d754d0cc3ca9035 | [
"MIT"
] | null | null | null | ---
title: "Impact of climate change on precipitation patterns in Houston, Texas, USA"
authors:
- admin
- Xiao Li
- Yue Wang
- Steven M. Quiring
author_notes:
- ""
- ""
date: "2019-02-01T00:00:00Z"
doi: ""
# Schedule page publish date (NOT publication's date).
publishDate: "2017-01-01T00:00:00Z"
# Publication type.
# Legend: 0 = Uncategorized; 1 = Conference paper; 2 = Journal article;
# 3 = Preprint / Working Paper; 4 = Report; 5 = Book; 6 = Book section;
# 7 = Thesis; 8 = Patent
publication_types: ["2"]
# Publication name and optional abbreviated publication name.
publication: "*Anthropocene*, 25, 100193"
publication_short: ""
abstract: Extreme precipitation events damage infrastructure and property; thus, predicting future precipitation patterns in the context of climate change is important. In this study, precipitation projections from 36 downscaled General Circulation Models (GCMs) under two Representative Concentration Pathway (RCP) scenarios (RCP2.6 and RCP8.5) enabled examination of projected changes in future precipitation for the Clear Creek watershed in Houston, Texas, USA. Precipitation from 1950 to 2099 simulated with GCM were downscaled using the Bias-Correction Spatial Disaggregation method. Ten precipitation indices that represent precipitation amount, precipitation intensity, precipitation duration, and precipitation frequency evaluated how precipitation patterns will likely change. Results show that, at the annual scale, mean precipitation will significantly decrease based on RCP8.5, or remain relatively constant based on RCP2.6. Precipitation intensity and precipitation variability, however, will likely increase. Dry periods will lengthen significantly, whereas the length of wet spells will generally remain unchanged. At the monthly scale, the amount of precipitation, precipitation intensity, precipitation frequency and the length of wet spells will likely increase in September. In contrast, precipitation will likely decrease and dry spells will lengthen in April, May, August, November, and December. This finding illustrates that the intra-annual variability in precipitation will increase. The projected changes in precipitation under RCP8.5 are generally greater compared with RCP2.6. Differences between the scenarios are more pronounced towards the end of the century. Houston has recently experienced substantial precipitation variability, including severe drought and record-breaking precipitation from Hurricane Harvey in 2017. These events are consistent with the long-term GCM projections. Findings from this study can be applied to help manage water resources and enhance adaptability to climate change.
# Summary. An optional shortened abstract.
summary:
tags:
- Hydroclimatology
- Climate Change
featured: false
# links:
# - name: ""
# url: ""
url_pdf: https://www.sciencedirect.com/science/article/abs/pii/S2213305419300049
url_code: ''
url_dataset: ''
url_poster: ''
url_project: ''
url_slides: ''
url_source: ''
url_video: ''
# Featured image
# To use, add an image named `featured.jpg/png` to your page's folder.
image:
caption: ''
focal_point: ""
preview_only: false
# Associated Projects (optional).
# Associate this publication with one or more of your projects.
# Simply enter your project's folder or file name without extension.
# E.g. `internal-project` references `content/project/internal-project/index.md`.
# Otherwise, set `projects: []`.
projects: []
# Slides (optional).
# Associate this publication with Markdown slides.
# Simply enter your slide deck's filename without extension.
# E.g. `slides: "example"` references `content/slides/example/index.md`.
# Otherwise, set `slides: ""`.
slides: []
---
| 53.171429 | 2,031 | 0.781032 | eng_Latn | 0.983568 |
2fefc914813117299f09d6c9d9259faa094fa469 | 17,160 | md | Markdown | articles/healthcare-apis/data-transformation/move-to-synapse.md | ZetaPR/azure-docs.es-es | 0e2bf787d1d9ab12065fcb1091a7f13b96c6f8a2 | [
"CC-BY-4.0",
"MIT"
] | 66 | 2017-07-09T03:34:12.000Z | 2022-03-05T21:27:20.000Z | articles/healthcare-apis/data-transformation/move-to-synapse.md | ZetaPR/azure-docs.es-es | 0e2bf787d1d9ab12065fcb1091a7f13b96c6f8a2 | [
"CC-BY-4.0",
"MIT"
] | 671 | 2017-06-29T16:36:35.000Z | 2021-12-03T16:34:03.000Z | articles/healthcare-apis/data-transformation/move-to-synapse.md | ZetaPR/azure-docs.es-es | 0e2bf787d1d9ab12065fcb1091a7f13b96c6f8a2 | [
"CC-BY-4.0",
"MIT"
] | 171 | 2017-07-25T06:26:46.000Z | 2022-03-23T09:07:10.000Z | ---
title: Mover datos de la API de Azure para FHIR a Azure Synapse Analytics
description: En este artículo se describe cómo mover datos de FHIR a Synapse
author: ginalee-dotcom
ms.service: healthcare-apis
ms.subservice: fhir
ms.topic: reference
ms.date: 05/13/2021
ms.author: ginle
ms.openlocfilehash: e548361f6cf8d638609dd9daa83a175fa49f3679
ms.sourcegitcommit: 0046757af1da267fc2f0e88617c633524883795f
ms.translationtype: MT
ms.contentlocale: es-ES
ms.lasthandoff: 08/13/2021
ms.locfileid: "121780530"
---
# <a name="moving-data-from-azure-api-for-fhir-to-azure-synapse-analytics"></a>Mover datos de la API de Azure para FHIR a Azure Synapse Analytics
En este artículo aprenderá un par de formas de mover datos de la API de Azure para FHIR a [Azure Synapse Analytics](https://azure.microsoft.com/services/synapse-analytics/), que es un servicio de análisis ilimitado que reúne la integración de datos, el almacenamiento de datos empresariales y el análisis de macrodatos.
Mover datos del servidor de FHIR a Synapse implica exportar los datos mediante la operación `$export` de FHIR seguido de una serie de pasos para transformar y cargar los datos en Synapse. Este artículo le guiará a través de dos de los distintos enfoques, que mostrarán cómo convertir recursos de FHIR en formatos tabulares al moverlos a Synapse.
* **Cargue los datos exportados en Synapse mediante T-SQL:** use la operación `$export` para mover recursos de FHIR a un **almacenamiento de blobs de Azure Data Lake Gen 2 (ADL Gen 2)** en formato `NDJSON`. Cargue los datos del almacenamiento en **grupos de SQL dedicados o sin servidor** en Synapse mediante T-SQL. Convierta estos pasos en una canalización de movimiento de datos sólida mediante [canalizaciones de Synapse](../../synapse-analytics/get-started-pipelines.md).
* **Use las herramientas del repositorio OSS de canalización de Analytics de FHIR:** el repositorio de [canalización de Analytics de FHIR](https://github.com/microsoft/FHIR-Analytics-Pipelines) contiene herramientas que pueden crear una **canalización de Azure Data Factory (ADF)** para mover datos de FHIR a una **carpeta Common Data Model (CDM)** y desde la carpeta CDM a Synapse.
## <a name="load-exported-data-to-synapse-using-t-sql"></a>Carga de datos exportados en Synapse mediante T-SQL
### <a name="export-for-moving-fhir-data-into-azure-data-lake-gen-2-storage"></a>`$export` para mover datos de FHIR al almacenamiento de Azure Data Lake Gen 2
:::image type="content" source="media/export-data/export-azure-storage-option.png" alt-text="Almacenamiento de Azure en Synapse mediante $export":::
#### <a name="configure-your-fhir-server-to-support-export"></a>Configuración del servidor de FHIR para admitir `$export`
La API de Azure para FHIR implementa la operación `$export` definida por la especificación de FHIR para exportar todos o un subconjunto filtrado de datos de FHIR en formato `NDJSON`. Además, admite la [exportación desidentificada](./de-identified-export.md) para anonimizar los datos de FHIR durante la exportación. Si usa `$export`, obtiene la característica de desidentificación de forma predeterminada; su funcionalidad ya está integrada en `$export`.
Para exportar datos de FHIR a Azure Blob Storage, primero debe configurar el servidor FHIR para exportar datos a la cuenta de almacenamiento. Deberá (1) habilitar la identidad administrada, (2) ir a Access Control en la cuenta de almacenamiento y agregar la asignación de roles, (3) seleccionar la cuenta de almacenamiento para `$export`. Puede encontrar más instrucciones paso a paso [aquí.](./configure-export-data.md)
Puede configurar el servidor para exportar los datos a cualquier tipo de cuenta de almacenamiento de Azure, pero se recomienda exportar a ADL Gen 2 para obtener la mejor alineación con Synapse.
#### <a name="using-export-command"></a>Uso del comando `$export`
Después de configurar el servidor de FHIR, puede seguir la [documentación](./export-data.md#using-export-command) para exportar los recursos de FHIR en el nivel de sistema, paciente o grupo. Por ejemplo, puede exportar todos los datos de FHIR relacionados con los pacientes de `Group` con el comando `$export` siguiente, en el que especifica el nombre del almacenamiento de blobs de ADL Gen 2 en el campo `{{BlobContainer}}`:
```rest
https://{{FHIR service base URL}}/Group/{{GroupId}}/$export?_container={{BlobContainer}}
```
También puede usar el parámetro `_type` en la llamada `$export` anterior para restringir los recursos que desea exportar. Por ejemplo, la siguiente llamada solo exportará los recursos `Patient`, `MedicationRequest` y `Observation`:
```rest
https://{{FHIR service base URL}}/Group/{{GroupId}}/$export?_container={{BlobContainer}}&
_type=Patient,MedicationRequest,Condition
```
Para obtener más información sobre los distintos parámetros admitidos, consulte nuestra sección de página `$export` sobre los [parámetros de consulta](./export-data.md#settings-and-parameters).
### <a name="create-a-synapse-workspace"></a>Creación de un área de trabajo de Synapse
Antes de usar Synapse, necesitará un área de trabajo de Synapse. Creará un servicio de Azure Synapse Analytics en Azure Portal. Puede encontrar más instrucciones paso a paso [aquí.](../../synapse-analytics/get-started-create-workspace.md) Necesita una cuenta de `ADLSGEN2` para crear un área de trabajo. Su área de trabajo de Azure Synapse utilizará esta cuenta de almacenamiento para almacenar los datos de su área de trabajo de Synapse.
Después de crear un área de trabajo, puede verla en Synapse Studio iniciando sesión en el área de trabajo en https://web.azuresynapse.net o iniciando Synapse Studio en Azure Portal.
#### <a name="creating-a-linked-service-between-azure-storage-and-synapse"></a>Creación de un servicio vinculado entre Azure Storage y Synapse
Para mover los datos a Synapse, debe crear un servicio vinculado que conecte su cuenta de Azure Storage con Synapse. Puede encontrar más instrucciones paso a paso [aquí](../../synapse-analytics/data-integration/data-integration-sql-pool.md#create-linked-services).
1. En Synapse Studio, vaya a la pestaña **Administrar** y, en **Conexiones externas**, seleccione **Servicios vinculados**.
2. Seleccione **Nuevo** para agregar un servicio vinculado.
3. Seleccione **Azure Data Lake Storage Gen2** de la lista y elija **Continuar**.
4. Especifique las credenciales de autenticación. Cuando haya terminado, seleccione **Crear**.
Ahora que tiene un servicio vinculado entre el almacenamiento de ADL Gen 2 y Synapse, está a punto para usar grupos de Synapse SQL para cargar y analizar los datos de FHIR.
### <a name="decide-between-serverless-and-dedicated-sql-pool"></a>Decidir entre un grupo SQL dedicado y sin servidor
Azure Synapse Analytics ofrece dos grupos de SQL distintos, un grupo de SQL sin servidor y un grupo de SQL dedicado. El grupo de SQL sin servidor ofrece la flexibilidad de consultar datos directamente en el almacenamiento de blobs mediante el punto de conexión de SQL sin servidor sin ningún aprovisionamiento de recursos. El grupo SQL dedicado tiene la capacidad de procesamiento para un alto rendimiento y simultaneidad, y se recomienda para las funcionalidades de almacenamiento de datos a escala empresarial. Para obtener más información sobre los dos grupos de SQL, consulte la [página de documentación de Synapse](../../synapse-analytics/sql/overview-architecture.md) sobre arquitectura SQL.
#### <a name="using-serverless-sql-pool"></a>Uso del grupo de SQL sin servidor
Puesto que no dispone de servidor, no hay que instalar ninguna infraestructura ni mantener ningún clúster. Puede empezar a consultar datos desde Synapse Studio en cuanto se crea el área de trabajo.
Por ejemplo, la consulta siguiente se puede usar para transformar campos seleccionados de `Patient.ndjson` en una estructura tabular:
```sql
SELECT * FROM
OPENROWSET(bulk 'https://{{youraccount}}.blob.core.windows.net/{{yourcontainer}}/Patient.ndjson',
FORMAT = 'csv',
FIELDTERMINATOR ='0x0b',
FIELDQUOTE = '0x0b')
WITH (doc NVARCHAR(MAX)) AS rows
CROSS APPLY OPENJSON(doc)
WITH (
ResourceId VARCHAR(64) '$.id',
Active VARCHAR(10) '$.active',
FullName VARCHAR(100) '$.name[0].text',
Gender VARCHAR(20) '$.gender',
...
)
```
En la consulta anterior, la función `OPENROWSET` tiene acceso a los archivos de Azure Storage, y `OPENJSON` analiza texto JSON y devuelve las propiedades de entrada JSON como filas y columnas. Cada vez que se ejecuta esta consulta, el grupo de SQL sin servidor lee el archivo del almacenamiento de blobs, analiza el código JSON y extrae los campos.
También puede materializar los resultados en formato Parquet en una [tabla externa](../../synapse-analytics/sql/develop-tables-external-tables.md) para obtener un mejor rendimiento de las consultas, como se muestra a continuación:
```sql
-- Create External data source where the parquet file will be written
CREATE EXTERNAL DATA SOURCE [MyDataSource] WITH (
LOCATION = 'https://{{youraccount}}.blob.core.windows.net/{{exttblcontainer}}'
);
GO
-- Create External File Format
CREATE EXTERNAL FILE FORMAT [ParquetFF] WITH (
FORMAT_TYPE = PARQUET,
DATA_COMPRESSION = 'org.apache.hadoop.io.compress.SnappyCodec'
);
GO
CREATE EXTERNAL TABLE [dbo].[Patient] WITH (
LOCATION = 'PatientParquet/',
DATA_SOURCE = [MyDataSource],
FILE_FORMAT = [ParquetFF]
) AS
SELECT * FROM
OPENROWSET(bulk 'https://{{youraccount}}.blob.core.windows.net/{{yourcontainer}}/Patient.ndjson'
-- Use rest of the SQL statement from the previous example --
```
#### <a name="using-dedicated-sql-pool"></a>Uso del grupo de SQL dedicado
El grupo SQL dedicado admite tablas administradas y una memoria caché jerárquica para rendimiento en memoria. Puede importar macrodatos con consultas T-SQL simples y, después, use la potencia del motor de consultas distribuidas para realizar un análisis de alto rendimiento.
La manera más sencilla y rápida de cargar datos desde el almacenamiento en un grupo de SQL dedicado es usar el comando **`COPY`** en T-SQL, que puede leer archivos CSV, Parquet y ORC. Como en la consulta de ejemplo siguiente, use el comando `COPY` para cargar las filas `NDJSON` en una estructura tabular.
```sql
-- Create table with HEAP, which is not indexed and does not have a column width limitation of NVARCHAR(4000)
CREATE TABLE StagingPatient (
Resource NVARCHAR(MAX)
) WITH (HEAP)
COPY INTO StagingPatient
FROM 'https://{{yourblobaccount}}.blob.core.windows.net/{{yourcontainer}}/Patient.ndjson'
WITH (
FILE_TYPE = 'CSV',
ROWTERMINATOR='0x0a',
FIELDQUOTE = '',
FIELDTERMINATOR = '0x00'
)
GO
```
Una vez que tenga las filas JSON en la tabla `StagingPatient` anterior, puede crear diferentes formatos tabulares de los datos mediante la función `OPENJSON` y almacenar los resultados en tablas. Esta es una consulta SQL de muestra para crear una tabla `Patient` mediante la extracción de algunos campos del recurso `Patient`:
```sql
SELECT RES.*
INTO Patient
FROM StagingPatient
CROSS APPLY OPENJSON(Resource)
WITH (
ResourceId VARCHAR(64) '$.id',
FullName VARCHAR(100) '$.name[0].text',
FamilyName VARCHAR(50) '$.name[0].family',
GivenName VARCHAR(50) '$.name[0].given[0]',
Gender VARCHAR(20) '$.gender',
DOB DATETIME2 '$.birthDate',
MaritalStatus VARCHAR(20) '$.maritalStatus.coding[0].display',
LanguageOfCommunication VARCHAR(20) '$.communication[0].language.text'
) AS RES
GO
```
## <a name="use-fhir-analytics-pipelines-oss-tools"></a>Uso de herramientas OSS de canalización de Analytics de FHIR
:::image type="content" source="media/export-data/analytics-pipeline-option.png" alt-text="Uso de la canalización de ADF para mover datos a la carpeta de CDM y, a continuación, a Synapse":::
> [!Note]
> [La canalización de Analytics de FHIR](https://github.com/microsoft/FHIR-Analytics-Pipelines) es una herramienta de código abierto publicada con licencia MIT y no está cubierta por el Acuerdo de Nivel de Servicio de Microsoft para los servicios de Azure.
### <a name="adf-pipeline-for-moving-fhir-data-into-cdm-folder"></a>Canalización de ADF para mover datos de FHIR a la carpeta de CDM
La carpeta Common Data Model (CDM) es una carpeta de un lago de datos que se ajusta a estructuras de metadatos bien definidas y estandarizadas y datos autodescriptivos. Estas carpetas facilitan la interoperabilidad de metadatos entre los productores y los consumidores de datos. Antes de mover los datos de FHIR a la carpeta de CDM, puede transformar los datos en una configuración de tabla.
### <a name="generating-table-configuration"></a>Generación de la configuración de tabla
Clone el repositorio para obtener todos los scripts y el código fuente. Use `npm install` para instalar las dependencias. Ejecute el siguiente comando desde la carpeta `Configuration-Generator` para generar una carpeta de configuración de tabla con instrucciones de formato YAML:
```bash
Configuration-Generator> node .\generate_from_yaml.js -r {resource configuration file} -p {properties group file} -o {output folder}
```
Puede usar los archivos de ejemplo `YAML`, `resourcesConfig.yml` y `propertiesGroupConfig.yml` proporcionados en el repositorio.
### <a name="generating-adf-pipeline"></a>Generación de una canalización de ADF
Ahora puede usar el contenido de la configuración de tabla generada y algunas otras configuraciones para generar una canalización de ADF. Esta canalización de ADF, cuando se desencadena, exporta los datos desde el servidor de FHIR mediante la API `$export` y escribe en una carpeta de CDM junto con los metadatos de CDM asociados.
1. Cree una aplicación y entidad de servicio de Azure Active Directory (AD). La canalización de ADF usa un servicio por lotes de Azure para realizar la transformación y necesita una aplicación de Azure AD para el servicio por lotes. Siga la [Documentación de Azure AD](../../active-directory/develop/howto-create-service-principal-portal.md).
2. Conceda acceso para exportar la ubicación de almacenamiento a la entidad de servicio. En el `Access Control` del almacenamiento de exportación, conceda el rol `Storage Blob Data Contributor` a la aplicación de Azure AD.
3. Implemente la canalización de salida. Use la plantilla `fhirServiceToCdm.json` para una implementación personalizada en Azure. Este paso creará los siguientes recursos de Azure:
- Una canalización de ADF con el nombre `{pipelinename}-df`.
- Un almacén de claves con el nombre `{pipelinename}-kv` para almacenar el secreto de cliente.
- Una cuenta por lotes con el nombre `{pipelinename}batch` para ejecutar la transformación.
- Una cuenta de almacenamiento con el nombre `{pipelinename}storage`.
4. Conceda acceso a Azure Data Factory. En el panel de control de acceso del servicio de FHIR, conceda los roles `FHIR data exporter` y `FHIR data reader` a la factoría de datos, `{pipelinename}-df`.
5. Cargue el contenido de la carpeta de configuración de tabla al contenedor de configuración.
6. Vaya a `{pipelinename}-df` y desencadene la canalización. Debería ver los datos exportados en la carpeta CDM de la cuenta de almacenamiento `{pipelinename}storage`. Debería ver una carpeta para cada tabla que tenga un archivo CSV.
### <a name="from-cdm-folder-to-synapse"></a>De la carpeta de CDM a Synapse
Una vez que tenga los datos exportados en formato CDM y almacenados en el almacenamiento de ADL Gen 2, puede mover los datos de la carpeta CDM a Synapse.
Puede crear una canalización de CDM a Synapse mediante un archivo de configuración, que tendría un aspecto parecido al siguiente:
```json
{
"ResourceGroup": "",
"TemplateFilePath": "../Templates/cdmToSynapse.json",
"TemplateParameters": {
"DataFactoryName": "",
"SynapseWorkspace": "",
"DedicatedSqlPool": "",
"AdlsAccountForCdm": "",
"CdmRootLocation": "cdm",
"StagingContainer": "adfstaging",
"Entities": ["LocalPatient", "LocalPatientAddress"]
}
}
```
Ejecute este script con el archivo de configuración anterior:
```bash
.\DeployCdmToSynapsePipeline.ps1 -Config: config.json
```
Agregue la identidad administrada de ADF como usuario de SQL a la base de datos de SQL. Este es un ejemplo de script de SQL para crear un usuario y un rol de asignación:
```sql
CREATE USER [datafactory-name] FROM EXTERNAL PROVIDER
GO
EXEC sp_addrolemember db_owner, [datafactory-name]
GO
```
## <a name="next-steps"></a>Pasos siguientes
En este artículo, ha aprendido dos maneras diferentes de mover los datos de FHIR a Synapse: (1) mediante el uso de `$export` para mover datos al almacenamiento de blobs de ADL Gen 2 y, a continuación, cargar los datos en grupos de SQL de Synapse y (2) mediante la canalización de ADF para mover datos de FHIR a la carpeta CDM y, a continuación, a Synapse.
A continuación, puede obtener información sobre la anonimización de los datos de FHIR al mover datos a Synapse para asegurarse de que la información de atención sanitaria está protegida:
>[!div class="nextstepaction"]
>[Exportación de datos sin identificación](./de-identified-export.md)
| 65.747126 | 697 | 0.769988 | spa_Latn | 0.963824 |
2ff044d997e45c0a8d931727ff444afdcdfaacb5 | 724 | md | Markdown | includes/functions-package.md | boltomli/azure-docs | 5881a7c5ba1bde1a4be87aa6e15b320148b8dbde | [
"CC-BY-4.0"
] | 1 | 2019-07-18T11:30:47.000Z | 2019-07-18T11:30:47.000Z | includes/functions-package.md | boltomli/azure-docs | 5881a7c5ba1bde1a4be87aa6e15b320148b8dbde | [
"CC-BY-4.0"
] | 1 | 2022-01-13T19:45:57.000Z | 2022-01-13T19:45:57.000Z | includes/functions-package.md | boltomli/azure-docs | 5881a7c5ba1bde1a4be87aa6e15b320148b8dbde | [
"CC-BY-4.0"
] | null | null | null | ---
title: include file
description: include file
services: functions
author: tdykstra
manager: cfowler
ms.service: functions
ms.topic: include
ms.date: 05/23/2018
ms.author: tdykstra
ms.custom: include file
---
The following table tells how to add support for this binding in each development environment.
| Development environment | To add support in <br>Functions 1.x |
|----------------------|----------------|---------------|
|Local development - C# class library | [Install the package](../articles/azure-functions/functions-triggers-bindings.md#c-class-library-with-visual-studio-2017) |
|Local development - C# script, JavaScript, F# |Automatic |
|Portal development| Automatic |
| 34.47619 | 170 | 0.675414 | eng_Latn | 0.932936 |
2ff0720df32ade74be1918c3a06c598cfcf4b706 | 5,402 | md | Markdown | README.md | mellenaj/react-mui-simple-form-validation | d090f3cc655b5fea079570bf44bed95be2e15a36 | [
"MIT"
] | null | null | null | README.md | mellenaj/react-mui-simple-form-validation | d090f3cc655b5fea079570bf44bed95be2e15a36 | [
"MIT"
] | null | null | null | README.md | mellenaj/react-mui-simple-form-validation | d090f3cc655b5fea079570bf44bed95be2e15a36 | [
"MIT"
] | null | null | null | ## react-mui-simple-form-validation
### Installation
```
yarn add react-mui-simple-form-validation
```
```
npm install react-mui-simple-form-validation
```
------
### Usage
#### Simple Login Page
Create **LoginFormFields.component.js**
```javascript
import React, { useState } from 'react';
import Grid from '@material-ui/core/Grid';
import { makeStyles } from "@material-ui/core/styles";
import {
withFormValidation,
InputWithValid,
} from 'react-mui-simple-form-validation';
const useStyles = makeStyles(theme => ({
textField: {
marginLeft: theme.spacing(1),
marginRight: theme.spacing(1),
width: 400
}
}));
let LoginFormFields = (props) => {
const { fields } = props;
const classes = useStyles();
return (
<>
<Grid item xs={12}>
<InputWithValid
classTextField={classes.textField}
name="name"
label="Name"
value={fields.name}
inputProps={{ pattern: '.{3,40}' }} // can use this prop or 'regexp' prop
errorText="From 3 to 40 chapters"
required={true}
{...props}
/>
</Grid>
<Grid item xs={12}>
<InputWithValid
classTextField={classes.textField}
name="email"
label="Email"
regexp='[a-z0-9._%+-]+@[a-z0-9.-]+\.[a-z]{2,}$' // can use this prop or 'inputProps={{ pattern: '.{3,40}' }}' prop
value={fields.email}
errorText="Example: characters@characters.domain "
required
{...props}
/>
</Grid>
</>
)
}
const LoginFormWithValid = withFormValidation(LoginFormFields);
export default LoginFormWithValid;
```
Then create **LoginForm.component.js**
```javascript
import LoginFormWithValid from './path/to/LoginFormWithValid';
let initialUser = {
name: '',
email: ''
};
const LoginForm = () => {
const [user, setUser] = useState(initialUser);
const onChange = (e) => {
const { name } = e.target;
let { value } = e.target;
if (!Array.isArray(value) && value.trim() === '') {
value = '';
}
setUser({...user,[name]: value});
}
const onSubmit = (e) => {
e.preventDefault();
setUser(initialUser);
console.log('Submit');
}
return (
<Grid container alignItems='center'>
<LoginFormWithValid
fields={user}
onChange={onChange}
onSubmit={onSubmit}
submitBtn={{ value: 'Login' }}
btnsGridContainer={{alignItems: 'center'}}
btnGridItem={{xs: 12}}
/>
</Grid>
)
}
export default LoginForm;
```
That's all!
You can also use **MultipleChipSelectWithValid** component
```javascript
import { MultipleChipSelectWithValid } from 'react-mui-simple-form-validation';
const InputTitle = () => (
<MultipleChipSelectWithValid
name="categories"
label="Categories"
fullWidth
selectValues={categories}
value={fields.categories}
required
{...props}
/>
)
```
*MultipleChipSelectWithValid* use *Select*, *FormControl*, *InputLabel*, *Input*, *MenuItem*, *Chip* components;
#### Supported *Props* for withFormValidation
| Name | Type | Options |
| ------------ | ------------ | ------------ |
| fields | object | |
| onSubmit | function | |
| children | node | |
| btnsGridContainer | object | alignContent, alignItems, direction, justify, classGridContainer, spacing, wrap|
| btnGridItem | object | classGridItem, lg, md, sm, xl, xs, zeroMinWidth |
| submitBtn | object | value, classButton, color, variant, size, component, disableFocusRipple, disableRipple, fullWidth |
Component has a structure :
```html
<form>
<BaseComponent></BaseComponent>
<Grid container> <!--btnsGridContainer -->
<Grid item> <!--btnGridItem -->
<Button /> <!--submitBtn -->
</Grid>
{children} <!--here you can add extra buttons -->
</Grid>
</form>
```
#### Supported *Props* for InputWithValid
| Name | Type | Comments |
| ------------ | ------------ | ------------ |
| name | string | required |
| value | any | required |
| errorText | string | |
| rows | number | |
| label | string | |
| required | bool | |
|onChange|func|required|
|autoComplete|string||
|regexp|string||
|autoFocus|bool||
|disabled|bool||
|fullWidth|bool||
|margin|string||
|FormHelperTextProps|object|https://material-ui.com/ru/api/form-helper-text/|
|InputLabelProps|object|https://material-ui.com/ru/api/input-label/|
|select|bool||
|variant|string||
|SelectProps|object|https://material-ui.com/ru/api/select/|
|selectValues|array|must be in format [{**value**: 12323, **label**: 'USA'}]|
|type|string||
|inputProps|object|https://material-ui.com/ru/api/input/|
|classTextField|string||
|classMenuItem|string| for 'select' type|
|classInputAdornment|string|for 'password' type|
|classIconButton|string|for 'password' type|
#### Supported *Props* for MultipleChipSelectWithValid
|Name | Type | Comments |
| ------------ | ------------ | ------------ |
| name | string | required |
| value | array | required |
| label | string | |
| required | bool | |
| fullWidth | bool | |
| onChange | func | required |
|MenuProps|object|https://material-ui.com/ru/api/menu/|
|selectValues|array|['value1, 'value2', 'value3']|
|classFormControl|string||
|classInputControl|string||
|classMenuItem|string||
|classChips|string||
|classSelect|string|||
Enjoy! :=)
#### License
MIT
| 25.971154 | 126 | 0.615328 | yue_Hant | 0.339185 |
2ff0bee191604ec3a52973d2732cc31971148023 | 13,520 | md | Markdown | articles/machine-learning/machine-learning-data-science-spark-overview.md | OpenLocalizationTestOrg/azure-docs-pr15_fi-FI | fd5644538d5deb8abf20f8d401bd1741ff804a81 | [
"CC-BY-3.0",
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/machine-learning/machine-learning-data-science-spark-overview.md | OpenLocalizationTestOrg/azure-docs-pr15_fi-FI | fd5644538d5deb8abf20f8d401bd1741ff804a81 | [
"CC-BY-3.0",
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/machine-learning/machine-learning-data-science-spark-overview.md | OpenLocalizationTestOrg/azure-docs-pr15_fi-FI | fd5644538d5deb8abf20f8d401bd1741ff804a81 | [
"CC-BY-3.0",
"CC-BY-4.0",
"MIT"
] | null | null | null | <properties
pageTitle="Yleistä tietojen tiede ohjattu käyttäminen Azure Hdinsightiin | Microsoft Azure"
description="Ohjattu MLlib työkalujen näyttää huomattavasti koneen learning mallinnus ominaisuuksia, eri aikajaksoille HDInsight-ympäristössä."
services="machine-learning"
documentationCenter=""
authors="bradsev"
manager="jhubbard"
editor="cgronlun" />
<tags
ms.service="machine-learning"
ms.workload="data-services"
ms.tgt_pltfrm="na"
ms.devlang="na"
ms.topic="article"
ms.date="10/07/2016"
ms.author="deguhath;bradsev;gokuma" />
# <a name="overview-of-data-science-using-spark-on-azure-hdinsight"></a>Yleistä tietojen tiede ohjattu käyttäminen Azure Hdinsightiin
[AZURE.INCLUDE [machine-learning-spark-modeling](../../includes/machine-learning-spark-modeling.md)]
Tämä suite aiheista näytetään, miten HDInsight ohjattu avulla voit suorittaa yleisiä tietoja tiede tehtäviä esimerkiksi tietojen nieltynä, toiminto-tekniikka, mallinnus ja mallin arviointi. Käytettävät tiedot on otoksen 2013 Kokousesitelmän taksin työmatkan ja maksun DataSet. Sisäisten mallit ovat logistista ja lineaarisen regressiosuoran, satunnainen metsien ja liukuvärin tehosti puut. Aiheiden näyttää tallentaminen näitä malleja Azuren Blob-objektien tallennustilaan (WASB) sekä pisteet ja niiden ennakoivan suorituskyvyn arvioiminen. Monimutkaisemman ohjeaiheissa miten malleja voi olla koulutus rajat kelpoisuustarkistus ja hyper-parametrin sweeping avulla. Yleistä Tässä ohjeaiheessa kuvataan myös määrittämisestä Ohjattu klusterin, sinun on kolme vaiheittaisissa ohjeissa annettujen ohjeiden mukaisesti.
[Ohjattu](http://spark.apache.org/) on käsittelyn framework, joka tukee ladatun käsittelyn edistää big datasta analyyttisten sovellusten suorituskykyä Avaa lähde-rinnakkain. Ohjattu käsittely ohjelma on luotu nopeus-käyttöä ja yksityiskohtaisen analysoinnin helpottamiseksi. Ohjattu päivän ladatun hajautettu laskenta ominaisuuksia Varmista on hyvä iteratiivinen algoritmien koneen opiskelu- ja kaavion funktiolauseita. [MLlib](http://spark.apache.org/mllib/) on ohjattu 's skaalattava koneen learning kirjasto, joka tuo mallinnus ominaisuuksia tässä jaetussa ympäristössä.
[Ohjattu Hdinsightista](../hdinsight/hdinsight-apache-spark-overview.md) on Azure isännöityä tarjoaminen Avaa lähde ohjattu. Se on myös **Jupyter PySpark muistikirjat** , jotka voidaan suorittaa vuorovaikutteinen ohjattu SQL-kyselyjä ja muodonmuutoksen, suodattaminen ja kesäolympialaisten visualisointi tiedot, jotka on tallennettu Azure BLOB-objektit (WASB) Ohjattu klusterin tuki. PySpark on ohjattu Python Ohjelmointirajapinta. Koodikatkelmat, joiden ratkaisuja ja Näytä asiaa joudutaan tähän Suorita ohjattu klustereiden asennettuihin Jupyter muistikirjoissa tietojen visualisoimiseen. Näissä ohjeaiheissa mallinnus ohjeita sisältävät koodi, joka näyttää, miten kouluttaminen, arvioida, tallentaa ja tarjoaman kunkin mallin tyypin.
Määrityksen vaiheet ja koodia omalla tätä vaiheittaista on HDInsight 3.4 ohjattu 1.6. Kuitenkin koodin tähän muistikirjat on yleinen ja pitäisi toimia Ohjattu klusterin. Jos et käytä ohjattu HDInsight-klusterin määrittäminen ja hallinta vaiheet saattavat olla hieman erilainen kuin seuraavassa kuvassa.
## <a name="prerequisites"></a>Edellytykset
1. sinulla on oltava Azure tilaus. Jos sinulla ei ole yhtä, katso [Hae Azure maksuttoman kokeiluversion](https://azure.microsoft.com/documentation/videos/get-azure-free-trial-for-testing-hadoop-in-hdinsight/).
2. sinun on HDInsight 3.4 ohjattu 1.6-klusterin vaiheiden suorittamiseen. Voit luoda, katso ohjeita [aloittaminen: Luo Apache ohjattu Azure Hdinsightiin](../hdinsight/hdinsight-apache-spark-jupyter-spark-sql.md). **Valitse klusterin tyyppi** -valikosta on määritetty klusterin tyyppi ja versio.
<!-- -->
> [AZURE.NOTE] Aiheen, joka näyttää, miten haluat käyttää Scala Python asemesta tehtävän loppuun tiedot-tiede prosessin-kohdassa [tietoja tiede käyttämällä Scala ohjattu Azure-kanssa](machine-learning-data-science-process-scala-walkthrough.md).
<!-- -->
>[AZURE.INCLUDE [delete-cluster-warning](../../includes/hdinsight-delete-cluster-warning.md)]
## <a name="the-nyc-2013-taxi-data"></a>Kokousesitelmän 2013 taksin tiedot
Kokousesitelmän taksin työmatkan tiedot on noin 20 gt: n pakattu pilkuilla erotetut arvot (CSV)-tiedostot (noin 48 gt puretaan), 173 miljoonaa yksittäisiä trips ja kuljetusmaksut maksettu kunkin työmatkan. Työmatkan kunkin tietueen sisältää Valitse ylös ja latauskirjaston sijainti ja aika-anonymized hakkeroida (ohjaimen) käyttöoikeuden numero ja medallion (taksin on yksilöllinen tunnus) numero. Tietoja kattaa kaikki trips vuoden 2013 ja annetaan seuraavat kaksi tietojoukkoja jokaiselle kuukaudelle:
1. 'Trip_data' CSV-tiedostoja sisältävät työmatkan tiedot, kuten numero henkilöiden, nosta ja keston ja työmatkan pituus dropoff osoittaa työmatkan. Tässä on muutama Esimerkki tietue:
medallion,hack_license,vendor_id,rate_code,store_and_fwd_flag,pickup_datetime,dropoff_datetime,passenger_count,trip_time_in_secs,trip_distance,pickup_longitude,pickup_latitude,dropoff_longitude,dropoff_latitude
89D227B655E5C82AECF13C3F540D4CF4,BA96DE419E711691B9445D6A6307C170,CMT,1,N,2013-01-01 15:11:48,2013-01-01 15:18:10,4,382,1.00,-73.978165,40.757977,-73.989838,40.751171
0BD7C8F5BA12B88E0B67BED28BEA73D8,9FD8F69F0804BDB5549F40E9DA1BE472,CMT,1,N,2013-01-06 00:18:35,2013-01-06 00:22:54,1,259,1.50,-74.006683,40.731781,-73.994499,40.75066
0BD7C8F5BA12B88E0B67BED28BEA73D8,9FD8F69F0804BDB5549F40E9DA1BE472,CMT,1,N,2013-01-05 18:49:41,2013-01-05 18:54:23,1,282,1.10,-74.004707,40.73777,-74.009834,40.726002
DFD2202EE08F7A8DC9A57B02ACB81FE2,51EE87E3205C985EF8431D850C786310,CMT,1,N,2013-01-07 23:54:15,2013-01-07 23:58:20,2,244,.70,-73.974602,40.759945,-73.984734,40.759388
DFD2202EE08F7A8DC9A57B02ACB81FE2,51EE87E3205C985EF8431D850C786310,CMT,1,N,2013-01-07 23:25:03,2013-01-07 23:34:24,1,560,2.10,-73.97625,40.748528,-74.002586,40.747868
2. 'Trip_fare' CSV-mallitiedostot sisältävät tietoja maksettu kunkin työmatkan, kuten maksutyyppi, maksun summa, Lisämaksu ja verojen, vihjeet ja tietullit, maksun ja yhteensä maksetun summan. Tässä on muutama Esimerkki tietue:
medallion, hack_license, vendor_id, pickup_datetime, payment_type, fare_amount, surcharge, mta_tax, tip_amount, tolls_amount, total_amount
89D227B655E5C82AECF13C3F540D4CF4,BA96DE419E711691B9445D6A6307C170,CMT,2013-01-01 15:11:48,CSH,6.5,0,0.5,0,0,7
0BD7C8F5BA12B88E0B67BED28BEA73D8,9FD8F69F0804BDB5549F40E9DA1BE472,CMT,2013-01-06 00:18:35,CSH,6,0.5,0.5,0,0,7
0BD7C8F5BA12B88E0B67BED28BEA73D8,9FD8F69F0804BDB5549F40E9DA1BE472,CMT,2013-01-05 18:49:41,CSH,5.5,1,0.5,0,0,7
DFD2202EE08F7A8DC9A57B02ACB81FE2,51EE87E3205C985EF8431D850C786310,CMT,2013-01-07 23:54:15,CSH,5,0.5,0.5,0,0,6
DFD2202EE08F7A8DC9A57B02ACB81FE2,51EE87E3205C985EF8431D850C786310,CMT,2013-01-07 23:25:03,CSH,9.5,0.5,0.5,0,0,10.5
Syy on otettava 0,1 otoksen nämä tiedostot ja liittyneet matkan\_tiedot ja työmatkan\_kuljetusmaksua CVS tiedostojen siirtäminen yhden tietojoukko käytettävä tätä vaiheittaista syötteen tietojoukko. Yksilöivä liittymään työmatkan\_tiedot ja työmatkan\_maksun koostuu kentät: medallion, hakkeroida\_lisenssin ja nouto\_datetime. Kunkin tietueen DataSet sisältää edustava Kokousesitelmän taksin matkan määritteet:
|Kenttä| Lyhyt kuvaus
|------|---------------------------------
| medallion |Anonymized taksin medallion (taksin yksilöllinen tunnus)
| hack_license | Anonymized Hackney kuljetus käyttöoikeuksien määrä
| vendor_id | Taksin Toimittajatunnus
| rate_code | Maksun Kokousesitelmän taksin korko
| store_and_fwd_flag | Tallentaminen ja lähettäminen edelleen merkinnän
| pickup_datetime | Nosta päivämäärä ja aika
| dropoff_datetime | Dropoff päivämäärä ja aika
| pickup_hour | Nosta tunti
| pickup_week | Vuoden viikko Nosta
| Viikonpäivä | Viikonpäivä (1 – 7 alue)
| passenger_count | Henkilöiden matkan taksin numero
| trip_time_in_secs | Matkan sekunteina
| trip_distance | Matkan etäisyys ottanut Mailia
| pickup_longitude | Nosta pituutta
| pickup_latitude | Nosta leveyttä
| dropoff_longitude | Dropoff pituutta
| dropoff_latitude | Dropoff leveyttä
| direct_distance | Suora poiminta välisen etäisyyden määrittäminen ja dropoff sijainnit
| payment_type | Maksutyyppi (cas, luottokortin jne.)
| fare_amount | Maksun summa
| lisä | Lisä
| mta_tax | MTA vero
| tip_amount | Vihje summa
| tolls_amount | Tietullit summa
| total_amount | Kokonaissumma
| Kallistettu | Kallistettu (0 ja 1 ei tai Kyllä)
| tip_class | Vihje luokan (0: $0, 1: $0 – 5 ja 2: $6-10-3: $11-20-4: > $20)
## <a name="execute-code-from-a-jupyter-notebook-on-the-spark-cluster"></a>Suorita Ohjattu klusterin Jupyter muistikirjan koodi
Voit käynnistää Jupyter muistikirjan Azure-portaalista. Etsi Ohjattu-klusterin raporttinäkymät- ja käyttöoikeus ja anna hallinta-sivun yhteyttä klusterin. Avaa Ohjattu klusterin liittyvät muistikirja, valitse **Klusterin raporttinäkymien** -> **Jupyter muistikirja** .
Voit myös selata ***https://CLUSTERNAME.azurehdinsight.net/jupyter*** Siirry Jupyter muistikirjoihin. Tätä URL-Osoitetta CLUSTERNAME-osan korvaaminen oman klusterin nimen. Tarvitset Siirry muistikirjoihin järjestelmänvalvojan tilin salasana.
Valitse PySpark näet valmiiksi pakattu muistikirjat, jotka käyttävät PySpark Ohjelmointirajapinnan muutamia esimerkkejä sisältävän kansion. Muistikirjat, jotka sisältävät tämän Suite ohjattu aiheen MALLIKOODEJA on osoitteessa [Github](https://github.com/Azure/Azure-MachineLearning-DataScience/tree/master/Misc/Spark/pySpark)
Voit ladata muistikirjat suoraan Github Jupyter muistikirjan palvelimeen ohjattu klusterissa. Oman Jupyter aloitussivulla Valitse näytön oikean puolen **Lataa** -painiketta. Se Avaa Resurssienhallinnassa. Tässä voit liittää muistikirjan Github (raaka-sisältö) URL-osoite ja valitse **Avaa**. PySpark muistikirjat on osoitteessa seuraavat URL-osoitteet:
1. [pySpark-machine-learning-data-science-spark-data-exploration-modeling.ipynb](https://github.com/Azure/Azure-MachineLearning-DataScience/blob/master/Misc/Spark/pySpark/pySpark-machine-learning-data-science-spark-data-exploration-modeling.ipynb)
2. [pySpark-machine-learning-data-science-spark-model-consumption.ipynb](https://github.com/Azure/Azure-MachineLearning-DataScience/blob/master/Misc/Spark/pySpark/pySpark-machine-learning-data-science-spark-model-consumption.ipynb)
3. [pySpark-machine-learning-data-science-spark-advanced-data-exploration-modeling.ipynb](https://github.com/Azure/Azure-MachineLearning-DataScience/blob/master/Misc/Spark/pySpark/pySpark-machine-learning-data-science-spark-advanced-data-exploration-modeling.ipynb)
Näet tiedostonimen Jupyter tiedosto-luettelossa, jossa **Lataa** -painiketta uudelleen. Napsauttamalla tätä **Lataa** -painiketta. On nyt tuotu muistikirja. Toista nämä vaiheet, voit ladata tämän vaiheittaisen kuvauksen suorittamiseksi muut muistikirjat.
> [AZURE.TIP] Voit linkit selaimen napsauttamalla hiiren kakkospainikkeella ja valitse **Kopioi linkki** github raaka sisällön URL-Osoitteen hankkiminen. Voit liittää Jupyter ladata tiedoston explorer valintaikkunan tätä URL-Osoitetta.
Nyt voit tehdä seuraavia toimia:
- Katso koodi napsauttamalla muistikirjaa.
- Suorita kullekin solulle painamalla näppäinyhdistelmää **VAIHTO + ENTER**.
- Koko muistikirjan suorittaminen **solussa**napsauttamalla -> **Suorita**.
- Automaattinen visualisoinnin kyselyjen avulla
> [AZURE.TIP] PySpark ydin automaattisesti valitseminen puolestaan Visualisoi tulos (HiveQL) SQL-kyselyjä. Voit valita useita erilaisia visualisointeja (taulukko, ympyräkaavio, rivin, alue tai palkin) **tyyppi** -valikosta painikkeiden avulla muistikirjan on esitetty:
## <a name="whats-next"></a>Mitä seuraavaksi?
Ohjattu HDInsight-klusterin määritetään ja olet ladannut Jupyter-muistikirjoja, olet valmis käydä läpi ohjeita, jotka vastaavat kolme PySpark muistikirjat. Ne näyttävät, kuinka tietojen ja miten voit luoda ja käyttää malleja. Lisäasetukset tietojen tarkasteluun ja mallinnus muistikirjan esitetään, kuinka voit sisällyttää rajat vahvistusta, hyper-parametrin sweeping, ja mallin arviointi.
**Tietojen tarkasteluun ja arvioiminen ohjattu:** Tutustu dataset ja luoda, pisteet, ja arvioida konepohjaisten oppimistekniikoiden mallien suorittamalla [binaarinen luokittelu ja ohjattu MLlib työkalujen tietojen regression mallien luominen](machine-learning-data-science-spark-data-exploration-modeling.md) aiheen kautta.
**Malli kulutus:** Lisätietoja sija luotu tämän ohjeaiheen luokittelu ja regression mallit-kohdassa [pisteet ja arvioi ohjattu laadittuihin koneen learning mallien](machine-learning-data-science-spark-model-consumption.md).
**Usean kelpoisuustarkistus ja hyperparameter sweeping**: miten malleja voi nähdä [Advanced tietojen tarkasteluun ja arvioiminen ohjattu](machine-learning-data-science-spark-advanced-data-exploration-modeling.md) koulutus rajat kelpoisuustarkistus ja hyper-parametrin sweeping avulla
| 90.133333 | 814 | 0.813831 | fin_Latn | 0.997851 |
2ff1bf9362a380ecf538445a5446feea8ea7e572 | 1,356 | md | Markdown | content/posts/daily/自言自语-命中著定.md | eallion/eallion.com | 294e26d7b50a9b2e4a9fa470441839b70d0e2262 | [
"MIT"
] | 18 | 2020-12-17T21:32:57.000Z | 2022-03-29T06:15:33.000Z | content/posts/daily/自言自语-命中著定.md | eallion/eallion.com | 294e26d7b50a9b2e4a9fa470441839b70d0e2262 | [
"MIT"
] | 5 | 2021-06-14T13:26:50.000Z | 2021-08-08T18:54:21.000Z | content/posts/daily/自言自语-命中著定.md | eallion/eallion.com | 294e26d7b50a9b2e4a9fa470441839b70d0e2262 | [
"MIT"
] | 9 | 2020-12-24T02:47:37.000Z | 2022-02-10T11:12:55.000Z | ---
title: "自言自语-命中著定"
categories: ["日志"]
tags: ["《飘》","命中著定","自言自语"]
draft: false
slug: "zhu"
date: "2010-05-08 04:23:26"
---
<p><div id="_mcePaste">先声明，我不是谁的粉丝，我听了快十年杰伦的歌我都不是他粉丝。</div>
<div id="_mcePaste">我只是支持刘著。</div>
<div id="_mcePaste">有人说，她是一个禁锢在男人身体里的女性的灵魂。</div>
<div id="_mcePaste">我觉得，他是一个纯粹的不做作的有梦想的人。</div>
<div id="_mcePaste">他的涵养和才华可以折服我。</div>
<div id="_mcePaste">但是真正打动我的，是他在台上的坦然。</div>
<div id="_mcePaste">我认真的看过他的新浪博客（虽然只有两篇），看过他的百度i贴。</div>
<div id="_mcePaste">他很活跃，他虚心地接受别人给他唱歌的建议，坦诚地跟支持者交流，淡然的面对无端的谩骂。</div>
<div id="_mcePaste">他在校内网（人人）和QQ上都有很多他以前未参加快男时候的照片。</div>
<div id="_mcePaste">他一直是这样的穿着打扮，也就是说，他一直是一个纯粹的真我。</div>
<div id="_mcePaste">就像他自己说的，我也觉得，他活得很阳光很健康，很阳刚。</div></p>
<p><div>附 刘著原创作品《飘》完整歌词版：</div>
<object classid="clsid:d27cdb6e-ae6d-11cf-96b8-444553540000" width="420" height="363" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,40,0"><param name="allowFullScreen" value="true"><param name="allowscriptaccess" value="always"><param name="wmode" value="opaque"><param name="src" value="http://www.tudou.com/v/NUESYJUDzwo/v.swf"><param name="allowfullscreen" value="true"><embed type="application/x-shockwave-flash" width="420" height="363" src="http://www.tudou.com/v/NUESYJUDzwo/v.swf" wmode="opaque" allowscriptaccess="always" allowfullscreen="true"></embed></object></p>
| 58.956522 | 619 | 0.733776 | yue_Hant | 0.24454 |
2ff1c2976bc0c56dc70bf21a1f5da371f1d9cac5 | 4,216 | md | Markdown | README.md | mbiesiad/awesome-sql | 6be245a173ead9a4a3917324334aa6a472424179 | [
"MIT"
] | 11 | 2020-05-15T21:11:48.000Z | 2022-01-07T06:14:03.000Z | README.md | mbiesiad/awesome-sql | 6be245a173ead9a4a3917324334aa6a472424179 | [
"MIT"
] | 1 | 2021-12-23T08:49:19.000Z | 2021-12-23T08:49:19.000Z | README.md | mbiesiad/awesome-sql | 6be245a173ead9a4a3917324334aa6a472424179 | [
"MIT"
] | 3 | 2021-04-02T13:43:59.000Z | 2022-03-06T18:25:24.000Z | # Awesome SQL [](https://awesome.re)
SQL-related awesome list.
## Contents
* [Formatters](#formatters)
* [Oracle](#oracle)
* [SQL Server](#sql-server)
* [Tools](#tools)
* [Miscellaneous](#miscellaneous)
* [Conferences](#conferences)
* [Code of Conduct](#code-of-conduct)
## Formatters
* [PoorMansTSqlFormatter](https://github.com/TaoK/PoorMansTSqlFormatter) - A small free .NET and JS library.
* [SQL Formatter](http://www.dpriver.com/pp/sqlformat.htm) - Instant SQL Formatter.
## Oracle
* [Alexandria-PLSQL-Utils](https://github.com/mortenbra/alexandria-plsql-utils) - Oracle PL/SQL Utility Library.
* [PLSQL-JSON](https://github.com/doberkofler/PLSQL-JSON) - The JSON encode/decode library for Oracle PL/SQL.
* [Oracle SQL Developer](https://www.oracle.com/database/technologies/appdev/sql-developer.html) - A free, integrated development environment.
* [SQL Tools for Oracle](https://sourceforge.net/projects/sqlt/) - A light weight and robust frontend for Oracle database development.
* [Testing Framework for PL/SQL](http://utplsql.org/) - An open-source testing framework for PL/SQL and SQL.
* [Oracle Database 18c Express Edition](https://www.oracle.com/database/technologies/appdev/xe.html) - Free Oracle Database for everyone.
* [Oracle Database Online Documentation 12c](https://docs.oracle.com/database/121/SQLRF/toc.htm) - Documentation, release 1 (12.1).
## SQL Server
* [SQL Server Data Tools](https://docs.microsoft.com/en-us/sql/ssdt/download-sql-server-data-tools-ssdt?redirectedfrom=MSDN&view=sql-server-ver15) - A modern development tool for building SQL Server relational databases, Azure SQL Databases, Analysis Services (AS) data models, Integration Services (IS) packages, and Reporting Services (RS) reports.
* [SQL Server 2019](https://www.microsoft.com/en-us/sql-server/sql-server-2019) - SQL Server 2019 by Microsoft.
* [Database Unit Testing for SQL Server](https://tsqlt.org/) - Unit testing framework for SQL Server.
## Tools
* [BigBash](https://github.com/Borisvl/bigbash) - A converter that generates a bash one-liner from an SQL Select query.
* [ERAlchemy](https://github.com/Alexis-benoist/eralchemy) - Entity Relation Diagrams generation tool.
* [Flyway](https://flywaydb.org/) - Version control for a database.
* [Rumba RDBM](https://www.dbinvent.com/) - Database schema migration tool, plain-SQL, and declarative schema definition supported.
* [Liquibase](https://www.liquibase.org/) - Manage database changes with ease.
* [PixQL](https://github.com/Phildo/pixQL) - SQL for image processing.
* [SQL Fiddle](http://sqlfiddle.com/) - A tool for easy online testing and sharing of database problems and their solution.
* [SQLPad](http://rickbergfalk.github.io/sqlpad/#/) - A web app for writing and running SQL queries and visualizing the results.
## Miscellaneous
Other awesome links & resources!
* [W3Schools](https://www.w3schools.com/sql/default.asp) - SQL Tutorial with W3Schools.
* [Pluralsight](https://www.pluralsight.com/courses/code-school-try-sql) - Pluralsight (Code School: Try SQL).
* [CodecAcademy](https://www.codecademy.com/learn/learn-sql) - CodecAcademy (Learn SQL).
* [SQLZoo](https://sqlzoo.net/) - SQL Tutorial.
## Conferences
* [SQL Server Virtual Conference](https://www.2020twenty.net/sql-server-virtual-conference/) - SQL Server Virtual Conference with C# Corner.
* [SQL Day](https://sqlday.pl/en/) - SQLDay is the largest conference focused on Microsoft Data Platform – databases, Big Data, Business Intelligence and advanced data analysis.
* [JOIN! DB Conference](https://join-conference.com/) - JOIN! is a premium conference for all specialists using Microsoft SQL Server, featuring some of the best speakers in the industry.
## Contributing
Warmly welcome! Kindly go through [Contribution Guidelines](CONTRIBUTING.md) first.
## Code of Conduct
Examples of behavior that contributes to creating a positive environment include:
```
Using welcoming and inclusive language
Being respectful of differing viewpoints and experiences
Gracefully accepting constructive criticism
Focusing on what is best for the community
Showing empathy towards other community members
```
| 55.473684 | 351 | 0.756879 | eng_Latn | 0.413835 |
2ff1fd5eaf324c53d276c7075bba0664f83508d3 | 3,651 | md | Markdown | desktop-src/DirectShow/iamtimelinecomp-vtrackinsbefore.md | velden/win32 | 94b05f07dccf18d4b1dbca13b19fd365a0c7eedc | [
"CC-BY-4.0",
"MIT"
] | 552 | 2019-08-20T00:08:40.000Z | 2022-03-30T18:25:35.000Z | desktop-src/DirectShow/iamtimelinecomp-vtrackinsbefore.md | velden/win32 | 94b05f07dccf18d4b1dbca13b19fd365a0c7eedc | [
"CC-BY-4.0",
"MIT"
] | 1,143 | 2019-08-21T20:17:47.000Z | 2022-03-31T20:24:39.000Z | desktop-src/DirectShow/iamtimelinecomp-vtrackinsbefore.md | velden/win32 | 94b05f07dccf18d4b1dbca13b19fd365a0c7eedc | [
"CC-BY-4.0",
"MIT"
] | 1,287 | 2019-08-20T05:37:48.000Z | 2022-03-31T20:22:06.000Z | ---
description: The VTrackInsBefore method inserts a virtual track into the composition at the specified priority.
ms.assetid: 82ae0867-13b6-41ae-adb9-a55ac78e21cb
title: IAMTimelineComp::VTrackInsBefore method (Qedit.h)
ms.topic: reference
ms.date: 05/31/2018
topic_type:
- APIRef
- kbSyntax
api_name:
- IAMTimelineComp.VTrackInsBefore
api_type:
- COM
api_location:
- strmiids.lib
- strmiids.dll
---
# IAMTimelineComp::VTrackInsBefore method
> [!Note]
> \[Deprecated. This API may be removed from future releases of Windows.\]
The `VTrackInsBefore` method inserts a virtual track into the composition at the specified priority.
## Syntax
```C++
HRESULT VTrackInsBefore(
IAMTimelineObj *pVirtualTrack,
long Priority
);
```
## Parameters
<dl> <dt>
*pVirtualTrack*
</dt> <dd>
Pointer to the [**IAMTimelineObj**](iamtimelineobj.md) interface of the virtual track.
</dd> <dt>
*Priority*
</dt> <dd>
Priority at which to insert the virtual track, or –1 to insert the virtual track at the end of the priority list. The priority list determines which clips are visible. See Remarks for more information.
</dd> </dl>
## Return value
Returns one of the following **HRESULT** values:
| Return code | Description |
|-----------------------------------------------------------------------------------------------|-------------------------------------------|
| <dl> <dt>**S\_OK**</dt> </dl> | Success.<br/> |
| <dl> <dt>**E\_INVALIDARG**</dt> </dl> | Invalid argument.<br/> |
| <dl> <dt>**E\_NOINTERFACE**</dt> </dl> | Object is not a virtual track.<br/> |
## Remarks
Each virtual track in composition has a unique priority level. Priority levels range from 0 to *n* - 1, where *n* is the number of virtual tracks in the composition. For video groups, a virtual track hides any virtual tracks with a lower priority level, except in places where the track is empty or contains a transition. You can think of virtual tracks as being layers in the final composition. Track 1 is layered on top of track 0, track 2 is layered on top of track 1, and so forth.
If you specify -1 for the *Priority* parameter, the virtual track is inserted at the end of the list, with a higher priority value than the existing tracks. If you specify a priority value that already exists in the composition, every track with an equal or greater priority moves up one priority level.
**Example**: Track A has priority 0, and track B has priority 1. If track C is inserted at priority 0, track A moves to priority 1, and track B moves to priority 2.
If the specified priority is greater than the current number of tracks in the composition, the method fails.
> [!Note]
> The header file Qedit.h is not compatible with Direct3D headers later than version 7.
> [!Note]
> To obtain Qedit.h, download the [Microsoft Windows SDK Update for Windows Vista and .NET Framework 3.0](https://msdn.microsoft.com/windowsvista/bb980924.aspx). Qedit.h is not available in the Microsoft Windows SDK for Windows 7 and .NET Framework 3.5 Service Pack 1.
## Requirements
| Requirement | Value |
|--------------------|-----------------------------------------------------------------------------------------|
| Header<br/> | <dl> <dt>Qedit.h</dt> </dl> |
| Library<br/> | <dl> <dt>Strmiids.lib</dt> </dl> |
## See also
<dl> <dt>
[**IAMTimelineComp Interface**](iamtimelinecomp.md)
</dt> <dt>
[Error and Success Codes](error-and-success-codes.md)
</dt> </dl>
| 29.92623 | 485 | 0.639003 | eng_Latn | 0.962161 |
2ff20f7ec713cbf6af749e897b7e97a3c7612388 | 2,437 | md | Markdown | docs/kautomator/com.kaspersky.components.kautomator.component.switch/-ui-switch/index.md | pkozlovskiy/Kaspresso | d2cf93a4fc67463bc7a457412d44c0afe1c9853a | [
"Apache-2.0"
] | null | null | null | docs/kautomator/com.kaspersky.components.kautomator.component.switch/-ui-switch/index.md | pkozlovskiy/Kaspresso | d2cf93a4fc67463bc7a457412d44c0afe1c9853a | [
"Apache-2.0"
] | null | null | null | docs/kautomator/com.kaspersky.components.kautomator.component.switch/-ui-switch/index.md | pkozlovskiy/Kaspresso | d2cf93a4fc67463bc7a457412d44c0afe1c9853a | [
"Apache-2.0"
] | null | null | null | [kautomator](../../index.md) / [com.kaspersky.components.kautomator.component.switch](../index.md) / [UiSwitch](./index.md)
# UiSwitch
`class UiSwitch : `[`UiBaseView`](../../com.kaspersky.components.kautomator.component.common.views/-ui-base-view/index.md)`<`[`UiSwitch`](./index.md)`>, `[`UiSwitchableActions`](../-ui-switchable-actions/index.md)`, `[`UiBaseAssertions`](../../com.kaspersky.components.kautomator.component.common.assertions/-ui-base-assertions/index.md)
Ui View with [UiSwitchableActions](../-ui-switchable-actions/index.md) and [UiBaseAssertions](../../com.kaspersky.components.kautomator.component.common.assertions/-ui-base-assertions/index.md)
**See Also**
[UiSwitchableActions](../-ui-switchable-actions/index.md)
[UiBaseAssertions](../../com.kaspersky.components.kautomator.component.common.assertions/-ui-base-assertions/index.md)
### Constructors
| Name | Summary |
|---|---|
| [<init>](-init-.md) | `UiSwitch(selector: `[`UiViewSelector`](../../com.kaspersky.components.kautomator.component.common.builders/-ui-view-selector/index.md)`)`<br>`UiSwitch(builder: `[`UiViewBuilder`](../../com.kaspersky.components.kautomator.component.common.builders/-ui-view-builder/index.md)`.() -> `[`Unit`](https://kotlinlang.org/api/latest/jvm/stdlib/kotlin/-unit/index.html)`)` |
### Inherited Properties
| Name | Summary |
|---|---|
| [view](../../com.kaspersky.components.kautomator.component.common.views/-ui-base-view/view.md) | `val view: `[`UiObjectInteractionDelegate`](../../com.kaspersky.components.kautomator.intercept.delegate/-ui-object-interaction-delegate/index.md) |
### Inherited Functions
| Name | Summary |
|---|---|
| [invoke](../../com.kaspersky.components.kautomator.component.common.views/-ui-base-view/invoke.md) | `operator fun invoke(function: `[`T`](../../com.kaspersky.components.kautomator.component.common.views/-ui-base-view/index.md#T)`.() -> `[`Unit`](https://kotlinlang.org/api/latest/jvm/stdlib/kotlin/-unit/index.html)`): `[`Unit`](https://kotlinlang.org/api/latest/jvm/stdlib/kotlin/-unit/index.html)<br>Operator that allows usage of DSL style |
| [swipeSwitchThumb](../-ui-switchable-actions/swipe-switch-thumb.md) | `open fun swipeSwitchThumb(direction: `[`UiSwitchableActions.Direction`](../-ui-switchable-actions/-direction/index.md)`): `[`Unit`](https://kotlinlang.org/api/latest/jvm/stdlib/kotlin/-unit/index.html)<br>Moves the thumb of the switch to the right |
| 73.848485 | 446 | 0.725072 | yue_Hant | 0.189768 |
2ff45ab1cbab62a221339403a02bf5681e399aa2 | 78 | md | Markdown | _goals/05_gender-equality.md | lindamejia/sdg-site-la | 37312f2a3515b19baee4bf12438a8f25082f818e | [
"MIT"
] | 2 | 2019-05-29T07:15:14.000Z | 2019-05-31T07:11:39.000Z | _goals/05_gender-equality.md | lindamejia/sdg-site-la | 37312f2a3515b19baee4bf12438a8f25082f818e | [
"MIT"
] | 15 | 2019-01-25T11:49:58.000Z | 2019-05-27T14:24:06.000Z | _goals/05_gender-equality.md | lindamejia/sdg-site-la | 37312f2a3515b19baee4bf12438a8f25082f818e | [
"MIT"
] | 8 | 2019-01-21T11:08:45.000Z | 2020-08-14T12:43:27.000Z | ---
permalink: /5/
sdg_goal: '5'
color: '#ff3a21'
layout: goal-by-target
---
| 9.75 | 22 | 0.615385 | eng_Latn | 0.236947 |
2ff466dc4a33cfb823d8d4bb65180f889c637b43 | 4,967 | md | Markdown | docs/getting_started/kubernetes/2.md | alexellis/gloo | 57cd56e96cc337a0715c3da157a71e324b8532e1 | [
"Apache-2.0"
] | null | null | null | docs/getting_started/kubernetes/2.md | alexellis/gloo | 57cd56e96cc337a0715c3da157a71e324b8532e1 | [
"Apache-2.0"
] | null | null | null | docs/getting_started/kubernetes/2.md | alexellis/gloo | 57cd56e96cc337a0715c3da157a71e324b8532e1 | [
"Apache-2.0"
] | 1 | 2019-04-12T05:51:45.000Z | 2019-04-12T05:51:45.000Z | ### What you'll need
If you haven't already deployed Gloo and the example swagger service on kubernetes, [go back to the first tutorial](1.md)
Now that we've seen the traditional routing functionality of Gloo (i.e. API-to-service), let's try doing some function routing.
Let's take a look at the upstream that was created for our petstore service:
glooctl upstream get default-petstore-8080 -o yaml
functions:
- name: addPet
spec:
body: '{"id": {{id}},"name": "{{name}}","tag": "{{tag}}"}'
headers:
:method: POST
path: /api/pets
- name: deletePet
spec:
body: ""
headers:
:method: DELETE
path: /api/pets/{{id}}
- name: findPetById
spec:
body: ""
headers:
:method: GET
path: /api/pets/{{id}}
- name: findPets
spec:
body: ""
headers:
:method: GET
path: /api/pets?tags={{tags}}&limit={{limit}}
...
We can see there are functions on our `default-petstore-8080` upstream. These functions were populated automatically by
the `function-discovery` pod. You can see the function discovery service in action by running `kubectl logs -l gloo=function-discovery`
The [function spec](../../v1/upstream.md#Function) you see on the functions listed above belongs to the transformation plugin<!--(TODO)-->. This powerful
plugin configures Gloo's [request/response transformation Envoy filter](https://github.com/solo-io/envoy-transformation)
to perform transform requests to the structure expected byour petstore app.
In a nutshell, this plugin takes [Inja templates](https://github.com/pantor/inja) for HTTP body, headers, and path as its parameters
(documented in the plugin spec<!--(TODO)--> and transforms incoming requests from those templates. Parameters for these templates
can come from the request body (if it's JSON), or they can come from parameters specified in the extensions on a route<!--(TODO)-->.
Let's see how this plugin works by creating some routes to these functions in the next section.
<br/>
### Steps
1. Start by creating the route with `glooctl`:
glooctl route create \
--path-exact /petstore/findPet \
--upstream default-petstore-8080 \
--function findPetById
Notice that, unlike the previous tutorial, we're passing an extra argument to `glooctl`: `--function findPetById`.
Let's go ahead and test the route using `curl`:
export GATEWAY_URL=http://$(minikube ip):$(kubectl get svc ingress -n gloo-system -o 'jsonpath={.spec.ports[?(@.name=="http")].nodePort}')
curl ${GATEWAY_URL}/petstore/findPet
bad request: Did not found json element: id
What's that? An error? Try again with `curl -v` and you'll see a `400 Bad Request` status on the response.
Looking again at the function `findPetById`, you'll notice the template wants a variable called `id`:
- name: findPetById
spec:
body: ""
headers:
:method: GET
path: /api/pets/{{id}}
1. Try the request again, but now add a JSON body with the parameter specified by name:
curl ${GATEWAY_URL}/petstore/findPet -d '{"id": 1}'
{"id":1,"name":"Dog","status":"available"}
Great! We just called our first function through Gloo.
<br/>
1. Parameters can also come from headers. Let's tell Gloo to look for `id` in a custom header.
Let's take a look at the route we created:
glooctl route get -o yaml
Using virtual service: default
request_matcher:
path_exact: /petstore/findPet
single_destination:
function:
function_name: findPetById
upstream_name: default-petstore-8080
We need to add an `extension` to this route that tells Gloo how to grab template parameters from the request.
Add `parameters` to the route's `extensions` like so:
cat <<EOF | glooctl route update --old-path-exact /petstore/findPet --old-upstream default-petstore-8080 --old-function findPetById --path-exact /petstore/findPet --upstream default-petstore-8080 --function findPetById --extensions -
parameters:
headers:
x-pet: '{id}'
EOF
Now Gloo knows to look for the parameter named `id` in a header called `pet`.
Try `curl` again, this time with the new header:
curl ${GATEWAY_URL}/petstore/findPet -H "x-pet: 1"
{"id":1,"name":"Dog","status":"available"}
Tutorials for more advanced use-cases are coming soon. In the meantime, please see our plugin documentation<!--(TODO)-->
for a list of available plugins and their configuration options. | 38.804688 | 241 | 0.629354 | eng_Latn | 0.970213 |
2ff479728a6548910bb1782c4365cf12f45cde46 | 220 | md | Markdown | CHANGELOG.md | TheRealSyler/vscode-ignore | d3aa99814c93117c7b8d8b3c3c6c004195a24ca1 | [
"MIT"
] | 2 | 2021-03-30T23:53:22.000Z | 2022-01-19T22:07:09.000Z | CHANGELOG.md | TheRealSyler/vscode-ignore | d3aa99814c93117c7b8d8b3c3c6c004195a24ca1 | [
"MIT"
] | 2 | 2021-12-30T09:15:24.000Z | 2021-12-30T09:15:37.000Z | CHANGELOG.md | TheRealSyler/vscode-ignore | d3aa99814c93117c7b8d8b3c3c6c004195a24ca1 | [
"MIT"
] | 1 | 2021-12-30T02:38:10.000Z | 2021-12-30T02:38:10.000Z | | Date | Message |
| --------- | --------------------------- |
| 7.3.2020 | fix path completion (again) |
| 5.2.2020 | fix path completion |
| 24.1.2020 | Initial Release |
| 36.666667 | 43 | 0.377273 | eng_Latn | 0.596578 |
2ff496b22b92b73cff2e1ea612774c2ad5924ba0 | 1,492 | md | Markdown | README.md | isuke01/wp-app-login-vue | 0b14684d7e30c9596f40f788da4ad3381f076242 | [
"MIT"
] | 11 | 2019-05-01T07:10:59.000Z | 2020-11-03T22:25:19.000Z | README.md | isuke01/wp-app-login-vue | 0b14684d7e30c9596f40f788da4ad3381f076242 | [
"MIT"
] | null | null | null | README.md | isuke01/wp-app-login-vue | 0b14684d7e30c9596f40f788da4ad3381f076242 | [
"MIT"
] | 4 | 2019-08-12T17:41:49.000Z | 2020-07-31T06:08:58.000Z | # WP VUE AUTH
## What it is?
It is simple demonstration APP created using VUE 2 JS, it is for Authentication user for wordpress.
### What's done
* User login
* User Logout
* Request password reset
* User validation tests (and after reset app)
* Store user in localstorage app
* Add example post
Errors and all other things are displayed in DEBUG
### Rrerequisites
* [VUE](https://vuejs.org/) - VUE
* [simple-jwt-authentication](https://github.com/jonathan-dejong/simple-jwt-authentication/wiki/Documentation) - simple-jwt-authentication
* [WP REST V2](https://developer.wordpress.org/rest-api/) -
### Project setup
* Setup your WordPress
* Install plugin and setup [simple-jwt-authentication](https://github.com/jonathan-dejong/simple-jwt-authentication/wiki/Documentation)
* Setup app:
```
npm install
```
Compiles and hot-reloads for development
```
npm run serve
```
Compiles and minifies for production
```
npm run build
```
Run your tests
```
npm run test
```
Lints and fixes files
```
npm run lint
```
### TO DO
* Check Woo Compability
* Create new user ?
* Edit current user
* Edit another user
* Edit Post
* Make this example more UI friendly :)
### At the End
* Check it first without any 3'th part WP REST plugins, may be some conflicts
* More about Auth for WP Rest [WP REST V2](https://developer.wordpress.org/rest-api/using-the-rest-api/authentication/)
* Big thanks to [Jonathan de Jong](https://github.com/jonathan-dejong) for great work and development :)
| 21.623188 | 138 | 0.731233 | eng_Latn | 0.774736 |
2ff4a41e7b3cc62f6960f33dd3c2fb6fb9475f42 | 7,759 | md | Markdown | _posts/2017-06-11-wepy微信小程序组件化开发框架.md | sqq5682/sqq5682.github.io | a314e4df270ff5c2d591120edc4c618be08d28e4 | [
"Apache-2.0"
] | 5 | 2016-05-28T17:43:19.000Z | 2020-11-23T02:08:15.000Z | _posts/2017-06-11-wepy微信小程序组件化开发框架.md | sqq5682/sqq5682.github.io | a314e4df270ff5c2d591120edc4c618be08d28e4 | [
"Apache-2.0"
] | 130 | 2017-12-14T09:32:21.000Z | 2018-03-29T08:55:12.000Z | _posts/2017-06-11-wepy微信小程序组件化开发框架.md | sqq5682/sqq5682.github.io | a314e4df270ff5c2d591120edc4c618be08d28e4 | [
"Apache-2.0"
] | 3 | 2016-03-16T13:08:24.000Z | 2016-06-13T02:28:29.000Z | ---
layout: post
title: wepy微信小程序组件化开发框架
categories: [blog ]
tags: [wepy ]
description: wepy微信小程序组件化开发框架
---
### 介绍
WePY 框架在开发过程中参考了 Vue 等现有框架的一些语法风格和功能特性，对原生小程序的开发模式进行了再次封装，更贴近于 MVVM 架构模式, 并支持ES6/7的一些新特性。
通过wepy开发的代码经过编译后，能生成一份完美运行在小程序端的代码，而且wepy的目的就是让小程序开发更贴近于传统H5框架开发，让小程序能像开发H5一样支持引入NPM包，支持组件化开发以及支持JS新特性等等。
#### 安装wepy
**以下安装都通过npm安装**
1.安装 wepy 命令行工具
npm install wepy-cli -g
2.在开发目录生成开发DEMO
wepy new myproject
3.开发实时编译
wepy build --watch
#### 项目目录结构
├── dist 微信开发者工具指定的目录（该目录由WePY的build指令自动编译生成，请不要直接修改该目录下的文件）
├── node_modules
├── src 代码编写的目录（该目录为使用WePY后的开发目录）
| ├── components WePY组件目录（组件不属于完整页面，仅供完整页面或其他组件引用）
| | ├── com_a.wpy 可复用的WePY组件a
| | └── com_b.wpy 可复用的WePY组件b
| ├── pages WePY页面目录（属于完整页面）
| | ├── index.wpy index页面（经build后，会在dist目录下的pages目录生成index.js、index.json、index.wxml和index.wxss文件）
| | └── other.wpy other页面（经build后，会在dist目录下的pages目录生成other.js、other.json、other.wxml和other.wxss文件）
| └── app.wpy 小程序配置项（全局数据、样式、声明钩子等；经build后，会在dist目录下生成app.js、app.json和app.wxss文件）
└── package.json 项目的package配置
#### 开发使用说明
1.使用微信开发者工具新建项目，本地开发选择dist目录。
2.微信开发者工具 → 项目 → 关闭ES6转ES5。
3.本地项目根目录运行wepy build --watch，开启实时编译。
#### 开发模式转换
在原有的小程序的开发模式下进行再次封装，更贴近于现有MVVM框架开发模式。框架在开发过程中参考了一些现在框架的一些特性，并且融入其中，以下是使用wepy前后的代码对比图。
官方DEMO代码：
//index.js
//获取应用实例
var app = getApp()
//通过Page构造函数创建页面逻辑
Page({
//可用于页面模板绑定的数据
data: {
motto: 'Hello World',
userInfo: {}
},
//事件处理函数
bindViewTap: function() {
console.log('button clicked')
},
//页面的生命周期函数
onLoad: function () {
console.log('onLoad')
}
})
基于WePY的代码：
//index.wpy中的<script>部分
import wepy from 'wepy';
//通过继承自wepy.page的类创建页面逻辑
export default class Index extends wepy.page {
//可用于页面模板绑定的数据
data = {
motto: 'Hello World',
userInfo: {}
};
//事件处理函数(集中保存在methods对象中)
methods = {
bindViewTap () {
console.log('button clicked');
}
};
//页面的生命周期函数
onLoad() {
console.log('onLoad');
};
}
#### 支持组件化开发
示例代码：
// index.wpy
<template>
<view>
<panel>
<h1 slot="title"></h1>
</panel>
<counter1 :num="myNum"></counter1>
<counter2 :num.sync="syncNum"></counter2>
<list :item="items"></list>
</view>
</template>
<script>
import wepy from 'wepy';
//引入List、Panel和Counter组件
import List from '../components/list';
import Panel from '../components/panel';
import Counter from '../components/counter';
export default class Index extends wepy.page {
//页面配置
config = {
"navigationBarTitleText": "test"
};
//声明页面中将要使用到的组件
components = {
panel: Panel,
counter1: Counter,
counter2: Counter,
list: List
};
//可用于页面模板中绑定的数据
data = {
myNum: 50,
syncNum: 100,
items: [1, 2, 3, 4]
}
}
</script>
#### 支持加载外部NPM包
在编译过程当中，会递归遍历代码中的require然后将对应依赖文件从node_modules当中拷贝出来，并且修改require为相对路径，从而实现对外部NPM包的支持。如下图：
#### 单文件模式，目录结构更清晰，开发更方便
原生小程序要求app实例必须有3个文件：app.js、app.json、app.wxss，而page页面则一般有4个文件：page.js、page.json、page.wxml、page.wxss，并且还要求app实例的3个文件以及page页面的4个文件除后缀名外必须同名，具体可参看官方目录结构。
而在WePY中则使用了单文件模式，将原生小程序app实例的3个文件统一为app.wpy，page页面的4个文件统一为page.wpy。使用WePY开发前后的开发目录结构对比如下：
原生小程序的目录结构：
project
├── pages
| ├── index
| | ├── index.js index 页面逻辑
| | ├── index.json index 页面配置
| | ├── index.wxml index 页面结构
| | └── index.wxss index 页面样式
| └── log
| ├── log.js log 页面逻辑
| ├── log.json log 页面配置
| ├── log.wxml log 页面结构
| └── log.wxss log 页面样式
├── app.js 小程序逻辑
├── app.json 小程序公共配置
└── app.wxss 小程序公共样式
使用WePY框架后的开发目录结构(主要为src目录的结构，dist目录除外)：
> 注：dist目录为WePY通过build指令生成的目录，除额外增加的npm目录外，其目录结构与原生小程序的目录结构类似。
project
└── src
├── pages
| ├── index.wpy index 页面逻辑、配置、结构、样式
| └── log.wpy log 页面逻辑、配置、结构、样式
└──app.wpy 小程序逻辑、公共配置、公共样式
#### 默认使用babel编译，支持ES6/7的一些新特性
用户可以通过修改wepy.config.js(老版本使用.wepyrc)配置文件，配置自己熟悉的babel环境进行开发。默认开启使用了一些新的特性如promise、async/await（自WePY 1.4.1开始必须手动开启，原因参见前文代码规范一节中的介绍）等等。
示例代码：
import wepy from 'wepy';
export default class Index extends wepy.page {
getData() {
return new Promise((resolve, reject) => {
setTimeout(() => {
resolve({data: 123});
}, 3000);
});
};
async onLoad() {
let data = await this.getData();
console.log(data.data);
};
}
#### 针对原生API进行优化
对小程序原生API进行promise处理，同时修复了一些原生API的缺陷，比如：wx.request的并发问题等。
原生代码：
onLoad = function () {
var self = this;
wx.login({
success: function (data) {
wx.getUserInfo({
success: function (userinfo) {
self.setData({userInfo: userinfo});
}
});
}
});
}
基于WePY的代码：
import wepy from 'wepy';
async onLoad() {
await wepy.login();
this.userInfo = await wepy.getUserInfo();
}
在同时并发10个request请求测试时：
不使用WePY:
使用WePY后：
#### 进阶介绍-wepy.config.js配置文件说明
执行wepy new demo后，会生成类似下面这样的配置文件。
let prod = process.env.NODE_ENV === 'production';
module.exports = {
'output': 'dist',
'source': 'src',
'wpyExt': '.wpy',
'compilers': {
less: {
'compress': true
},
/*sass: {
'outputStyle': 'compressed'
},*/
babel: {
'presets': [
'es2015',
'stage-1'
],
'plugins': [
'transform-export-extensions',
'syntax-export-extensions',
'transform-runtime'
]
}
},
'plugins': {
}
};
if (prod) {
// 压缩sass
module.exports.compilers['sass'] = {'outputStyle': 'compressed'};
// 压缩less
module.exports.compilers['less'] = {'compress': true};
// 压缩js
module.exports.plugins = {
'uglifyjs': {
filter: /\.js$/,
config: {
}
},
'imagemin': {
filter: /\.(jpg|png|jpeg)$/,
config: {
'jpg': {
quality: 80
},
'png': {
quality: 80
}
}
}
};
}
wpyExt：缺省值为’.wpy’，IDE默认情况下不会对此文件类型高亮，此时可以修改所有文件为.vue后缀(因为与vue高亮规则一样)，然后将此选项修改为.vue，就能解决部分IDE代码高亮问题。
sass：sass编译配置，参见[https://github.com/sass/node-sass](https://github.com/sass/node-sass)
less：less编译配置，参见[http://lesscss.org/#using-less-usage-in-code](http://lesscss.org/#using-less-usage-in-code)
babel：babel编译配置，参见[http://babeljs.io/docs/usage/options/](http://babeljs.io/docs/usage/options/)
### .wpy文件说明
.wpy文件的编译过程过下：
一个.wpy文件可分为三大部分，各自对应于一个标签：
1.脚本部分，即script标签中的内容，又可分为两个部分：逻辑部分，除了config对象之外的部分，对应于原生的.js文件；配置部分，即config对象，对应于原生的.json文件。
2.结构部分，即template模板部分，对应于原生的.wxml文件。
3.样式部分，即style样式部分，对应于原生的.wxss文件。
其中，小程序入口文件app.wpy不需要template，所以编译时会被忽略。.wpy文件中的script、template、style这三个标签都支持lang和src属性，lang决定了其代码编译过程，src决定是否外联代码，存在src属性且有效时，会忽略内联代码。
其他的脚本部分介绍，组件的渲染和通信交互可看官方文档介绍[wepy官方文档](https://mp.weixin.qq.com/s/2nQzsuqq7Avgs8wsRizUhw)
| 22.753666 | 149 | 0.589509 | yue_Hant | 0.431641 |
2ff4ecb4730412d14a6f5dec481b41b86142e4e8 | 857 | md | Markdown | docs/docs/preparing-your-environment.md | Pabelnedved/ghostlocoko | 221481bef7733c9957fb9ba83178f08280243b81 | [
"MIT"
] | 3 | 2019-03-07T09:46:18.000Z | 2020-05-16T14:21:08.000Z | docs/docs/preparing-your-environment.md | Pabelnedved/ghostlocoko | 221481bef7733c9957fb9ba83178f08280243b81 | [
"MIT"
] | 29 | 2018-02-16T13:36:10.000Z | 2020-02-03T12:02:11.000Z | docs/docs/preparing-your-environment.md | Pabelnedved/ghostlocoko | 221481bef7733c9957fb9ba83178f08280243b81 | [
"MIT"
] | 2 | 2020-03-27T18:27:28.000Z | 2020-04-27T04:37:13.000Z | ---
title: Preparing Your Environment
overview: true
---
To get started with Gatsby, you'll need to make sure you have the following software tools installed:
1. [Node.js](/tutorial/part-zero/#install-nodejs-for-your-appropriate-operating-system)
2. [npm CLI](/tutorial/part-zero/#check-your-nodejs-installation)
3. [Gatsby CLI](/tutorial/part-zero/#using-the-gatsby-cli)
For step-by-step installation instructions and detailed explanations of the required software, head on over to the [Gatsby tutorial](/tutorial/part-zero/).
The [quick start](/docs/quick-start/) is also available for intermediate to advanced developers.
> **Note:** If you work for an Enterprise-level company where you are unable to pull from public GitHub repositories, you can [still set up Gatsby](/docs/setting-up-gatsby-without-gatsby-new/).
<GuideList slug={props.slug} />
| 45.105263 | 193 | 0.767795 | eng_Latn | 0.969824 |
2ff4f0147981b8e9b64cadb9ff02968580d0ba1c | 14,540 | md | Markdown | README.md | NoblySP/textual | 0995fbc69e4740edb31fdf6f645617650e3376bb | [
"MIT"
] | null | null | null | README.md | NoblySP/textual | 0995fbc69e4740edb31fdf6f645617650e3376bb | [
"MIT"
] | null | null | null | README.md | NoblySP/textual | 0995fbc69e4740edb31fdf6f645617650e3376bb | [
"MIT"
] | null | null | null | # Textual
Textual is a TUI (Text User Interface) framework for Python inspired by modern web development. Currently a work in progress, but usable by brave souls who don't mind some API instability between updates.
Textual will be eventually be cross platform, but for now it is MacOS / Linux only. Windows support is in the pipeline.
Follow [@willmcgugan](https://twitter.com/willmcgugan) for progress updates, or post in Discussions if you have any requests / suggestions.
## How it works
Textual uses [Rich](https://github.com/willmcgugan/rich) to render rich text and formatting and asyncio to manage asynchronous events handling.
Textual has more in common with modern web development that it does curses; layout is done with CSS grid and (soon) the theme may be customized with CSS. Other techniques are borrowed from JS frameworks such as Vue and Reactive, so that changes to the state of an application are automatically reflected in the UI.
## Installation
You can install Textual via pip (`pip install textual`), or by checking out the repo and installing with [poetry](https://python-poetry.org/docs/).
```
poetry install
```
## Examples
Until I've written the documentation, the [examples](https://github.com/willmcgugan/textual/tree/main/examples/) may the best way to learn Textual.
- [animation.py](https://github.com/willmcgugan/textual/tree/main/examples/animation.py) Demonstration of 60fps animation easing function
- [calculator.py](https://github.com/willmcgugan/textual/tree/main/examples/calculator.py) A "clone" of the MacOS calculator using Grid layout
- [code_viewer.py](https://github.com/willmcgugan/textual/tree/main/examples/code_viewer.py) A demonstration of a tree view which loads syntax highlighted code
- [grid.py](https://github.com/willmcgugan/textual/tree/main/examples/calculator.py) A simple demonstration of adding widgets in a Grid layout
- [grid_auto.py](https://github.com/willmcgugan/textual/tree/main/examples/grid_auto.py) A demonstration of auto matic Grid layout
- [Simple](https://github.com/willmcgugan/textual/tree/main/examples/simple.py) A very simple Textual app with scrolling Markdown view
## Building Textual applications
_This guide is a work in progress_
Let's look at the simplest Textual app which does _something_:
```python
from textual.app import App
class Beeper(App):
async def on_key(self, event):
self.console.bell()
Beeper.run()
```
Here we can see a textual app with a single `on_key` method which will receive key events. Any key event will result in playing a beep noise. Hit ctrl+C to exit.
Event handlers in Textual are defined by convention, not by inheritance (so you won't find an `on_key` method in the base class). Each event has a `name` attribute which for the key event is simply `"key"`. Textual will call the method named `on_<event.name>` if it exists.
Lets look at a _slightly_ more interesting example:
```python
from textual.app import App
class ColorChanger(App):
async def on_key(self, event):
if event.key.isdigit():
self.background = f"on color({event.key})"
ColorChanger.run(log="textual.log")
```
This example also handles key events, and will set `App.background` if the key is a digit. So pressing the keys 0 to 9 will change the background color to the corresponding [ansi color](https://rich.readthedocs.io/en/latest/appendix/colors.html).
Note that we didn't need to explicitly refresh the screen or draw anything. Setting the `background` attribute is enough for Textual to update the visuals. This is an example of _reactivity_ in Textual. To make changes to the terminal interface you modify the _state_ and let Textual update the visuals.
## Widgets
To make more interesting apps you will need to make use of _widgets_, which are independent user interface elements. Textual comes with a (growing) library of widgets, but you can also develop your own.
Let's look at an app which contains widgets. We will be using the built in `Placeholder` widget which you can use to design application layouts before you implement the real content. They are very useful for testing.
```python
from textual import events
from textual.app import App
from textual.widgets import Placeholder
class SimpleApp(App):
async def on_mount(self, event: events.Mount) -> None:
await self.view.dock(Placeholder(), edge="left", size=40)
await self.view.dock(Placeholder(), Placeholder(), edge="top")
SimpleApp.run(log="textual.log")
```
This app contains a single event handler `on_mount`. The mount event is sent when the app or widget is ready to start processing events. We can use it for initializing things. In this case we are going to call `self.view.dock` to add widgets to the interface. More about the `view` object later.
Here's the first line in the mount handler:
```python
await self.view.dock(Placeholder(), edge="left", size=40)
```
Note this method is asynchronous like almost all API methods in Textual. We are awaiting `self.view.dock` which takes a newly constructed Placeholder widget, and docks it on to the `"left"` edge of the terminal with a size of 40 characters. In a real app you might use this to display a side-bar.
The following line is similar:
```python
await self.view.dock(Placeholder(), Placeholder(), edge="top")
```
You will notice that this time we are docking _two_ Placeholder objects on _the_ top edge. We haven't set an explicit size this time so Textual will divide the remaining size amongst the two new widgets.
The last line calls the `run` class method in the usual way, but with an argument we haven't seen before: `log="textual.log"` tells Textual to write log information to the given file. You can tail textual.log to see the events being processed and other debug information.
If you run the above example, you will see something like the following:
If you move the mouse over the terminal you will notice that widgets receive mouse events. You can click any of the placeholders to give it input focus.
The dock layout feature is good enough for most purposes. For more sophisticated layouts we can use the grid API. See the [calculator.py](https://github.com/willmcgugan/textual/blob/main/examples/calculator.py) example which makes use of Grid.
### Creating Widgets
You can create your own widgets by subclassing the `textual.widget.Widget` class and implementing a `render()` method which should return anything that can be rendered with [Rich](https://rich.readthedocs.io/en/latest/introduction.html), including a plain string which will be interpreted as [console markup](https://rich.readthedocs.io/en/latest/markup.html).
Lets look at an example with a custom widget:
```python
from rich.panel import Panel
from textual import events
from textual.app import App
from textual.reactive import Reactive
from textual.widget import Widget
class Hover(Widget):
mouse_over: Reactive[bool] = Reactive(False)
def render(self) -> Panel:
return Panel("Hello [b]World[/b]", style=("on red" if self.mouse_over else ""))
async def on_enter(self, event: events.Enter) -> None:
self.mouse_over = True
async def on_leave(self, event: events.Leave) -> None:
self.mouse_over = False
class HoverApp(App):
"""Hover widget demonstration."""
async def on_mount(self, event: events.Mount) -> None:
hovers = (Hover() for _ in range(10))
await self.view.dock(*hovers, edge="top")
HoverApp.run(log="textual.log")
```
The `Hover` class is a custom widget which displays a panel containing the classic text "Hello World". The first lin ein the Hover class may seem a little mysterious at this point:
```python
mouse_over: Reactive[bool] = Reactive(False)
```
This adds an `mouse_over` attribute to your class which is a bool with a default of `False`. The typing part (`Reactive[bool]`) is not required, but will help you find bugs if you are using a tool like [Mypy](https://mypy.readthedocs.io/en/stable/). Adding attributes like this makes them _reactive_, and any changes will result in the widget updating.
The following `render()` method is where you set how the widget should be displayed. In the Hover widget we return a Panel containing rich text with a background that changes depending on the value of `mouse_over`. The goal here is to add a mouseover effect to the widget, which we can achieve by handling two events: `Enter` and `Leave` which are sent when the mouse enters or leaves the widget. Here are the two event handlers again:
```python
async def on_enter(self, event: events.Enter) -> None:
self.mouse_over = True
async def on_leave(self, event: events.Leave) -> None:
self.mouse_over = False
```
The app class has a `Mount` handler where we _dock_ 10 of these custom widgets from the top edge. If you run this script you will see something like the following:
If you move your mouse over the terminal you should see that the widget under the mouse cursor changes to a red background.
### Actions and key bindings
Actions in Textual are white-listed functions that may be bound to keys. Let's look at a trivial example of binding a key to an action. Here is an app which exits when we hit the Q key:
```python
from textual.app import App
class Quitter(App):
async def on_load(self, event):
await self.bind("q", "quit")
Quitter.run()
```
If you run this you will get a blank terminal which will return to the prompt when you press Q.
Binding is done in the Load event handler. The `bind` method takes the key (in this case "q") and binds it to an action ("quit"). The quit action is built in to Textual and simply exits the app.
To define your own actions, add a method that begins with `action_`, which may take parameters. Let's create a simple action that changes the color of the terminal and binds keys to it:
```python
from textual.app import App
class Colorizer(App):
async def on_load(self, event):
await self.bind("r", "color('red')")
await self.bind("g", "color('green')")
await self.bind("b", "color('blue')")
async def action_color(self, color:str) -> None:
self.background = f"on {color}"
Colorizer.run()
```
If you run this app you can hit keys R, G, or B to change the color of the background.
In the `on_load` method we have bound the keys R, G, and B to the `color` action with a single parameter. When you press any of these three keys Textual will call the method `action_color` with the appropriate parameter.
You could be forgiven for thinking that `"color('red')"` is Python code which Textual evaluates. This is not the case. The action strings are parsed and may not include expressions or arbitrary code. The reason that strings are used over a callable is that (in a future update) key bindings may be loaded from a configuration file.
### Timers and Intervals
Textual has a `set_timer` and a `set_interval` which work much like their Javascript counterparts. The `set_timer` method will invoke a callable after a given period of time, and `set_interval` will invoke a callable repeatedly.
Let's create a simple terminal based clock with the `set_interval` method:
```python
from datetime import datetime
from rich.align import Align
from textual.app import App
from textual.widget import Widget
class Clock(Widget):
async def on_mount(self, event):
self.set_interval(1, callback=self.refresh)
def render(self) -> Align:
time = datetime.now().strftime("%X")
return Align.center(time, vertical="middle")
class ClockApp(App):
async def on_mount(self, event):
await self.view.dock(Clock())
ClockApp.run()
```
If you run this app you will see the current time in the center of the terminal until you hit Ctrl+C.
The Clock widget displays the time using [rich.align.Align](https://rich.readthedocs.io/en/latest/reference/align.html) to position it in the center. In the clock's Mount handler there is the following call to `set_interval`:
```python
self.set_interval(1, callback=self.refresh)
```
This tells Textual to call a function (in this case `self.refresh` which updates the widget) once a second. When a widget is refreshed it calls `Clock.render` again to display the latest time.
## Developer VLog
Since Textual is a visual medium, I'll be documenting new features and milestones here.
### Update 1 - Basic scrolling
[](http://www.youtube.com/watch?v=zNW7U36GHlU)
### Update 2 - Keyboard toggle
[](http://www.youtube.com/watch?v=bTYeFOVNXDI)
### Update 3 - New scrollbars, and smooth scrolling
[](http://www.youtube.com/watch?v=4LVl3ClrXIs)
### Update 4 - Animation system with easing function
Now with a system to animate a value to another value. Here applied to the scroll position. The animation system supports CSS like _easing functions_. You may be able to tell from the video that the page up / down keys cause the window to first speed up and then slow down.
[](http://www.youtube.com/watch?v=k2VwOp1YbSk)
### Update 5 - New Layout system
A new update system allows for overlapping layers. Animation is now synchronized with the display which makes it very smooth!
[](http://www.youtube.com/watch?v=XxRnfx2WYRw)
### Update 6 - New Layout API
New version (0.1.4) with API updates and the new layout system.
[](http://www.youtube.com/watch?v=jddccDuVd3E)
### Update 7 - New Grid Layout
**11 July 2021**
Added a new layout system modelled on CSS grid. The example demonstrates how once created a grid will adapt to the available space.
[](http://www.youtube.com/watch?v=Zh9CEvu73jc)
## Update 8 - Tree control and scroll views
**6 Aug 2021**
Added a tree control and refactored the renderer to allow for widgets within a scrollable veiew
[](http://www.youtube.com/watch?v=J-dzzD6NQJ4)
| 44.464832 | 435 | 0.751513 | eng_Latn | 0.991563 |
2ff4fa1f246dc0e7df1dda1d7adc656430b6490d | 1,279 | md | Markdown | README.md | jfmalloy1/ChemAsLanguage | 1236408e0b01f16a6b160b2fb08896c66066fade | [
"MIT"
] | null | null | null | README.md | jfmalloy1/ChemAsLanguage | 1236408e0b01f16a6b160b2fb08896c66066fade | [
"MIT"
] | null | null | null | README.md | jfmalloy1/ChemAsLanguage | 1236408e0b01f16a6b160b2fb08896c66066fade | [
"MIT"
] | null | null | null |
# Chemistry as Language
========
ChemAsLang is a collection of resources which treats chemistry as language. It breaks sets of chemistry down into component parts (fragments), implements networks of fragments, and trains Word-to-Vector algorithms on fragments to track changes in chemistry over time.
Features
--------
- Utilizes RDKit generate chemical fragments
- Uses Gensim to train Word-to-Vector models of fragments & chemical compounds
Usage
------------
- To generate fragments: upload a set of chemicals (in SMILES or SMARTS format) to the `Fragments/Data` directory, edit `Fragments/common_frags_parallel.py` as necessary.
- To train W2V: edit `Word2Vec/build_KEGG_gensim.py` as necessary.
Progress
-------
This is an ongoing project as part of my graduate research at Arizona State Univeristy. Future plans are to:
- Simplify the workflow for generating fragments from a list of user-specified chemical compounds (estimated date: Summer 2021)
- Train a W2V model as part of the fragment generation process (estimated date: Fall 2021)
- Release this code as a fully documented Python package (estimated data: Spring 2022)
Support
-------
If you have questions, email me at: jfmalloy1@gmail.com
License
-------
The project is licensed under the MIT license.
| 35.527778 | 267 | 0.766224 | eng_Latn | 0.986663 |
2ff61d0e7476dbf6ad6a3b6ec17b6cf3c0b8f165 | 21,514 | md | Markdown | pages/syllabus.md | zsmn/if977 | 8918b575f0d33e11e0ca161b71a6d7c269596f86 | [
"MIT"
] | 1 | 2020-10-18T00:53:39.000Z | 2020-10-18T00:53:39.000Z | pages/syllabus.md | zsmn/if977 | 8918b575f0d33e11e0ca161b71a6d7c269596f86 | [
"MIT"
] | null | null | null | pages/syllabus.md | zsmn/if977 | 8918b575f0d33e11e0ca161b71a6d7c269596f86 | [
"MIT"
] | 1 | 2020-09-15T11:57:14.000Z | 2020-09-15T11:57:14.000Z | | [Home](https://github.com/vinicius3w/if977) | [Courseware](/pages/courseware.md) | [Apoio](/pages/apoio.md) | [Programação em Par](/pages/pairprogramming.md) | [Projeto](/pages/projeto.md) | [Syllabus](/pages/syllabus.md) | [Equipes](/pages/equipes.md) | [Avaliações](/pages/avaliacoes.md) | [Exercícios Escolares](/pages/exerciciosescolares.md) |
# Syllabus
## [IF977] Engenharia de Software - Syllabus - 2020.1
| Aula | Dia | Tópico | Atividades & Observações |
|------|--------|-------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| 1 | 02-Mar | [Apresentação do curso + Introdução a Engenharia de Software](https://github.com/IF977/if977/blob/master/lectures/if977-s01a01-02.pdf) | Navegar pelo site da disciplina; analisar as opções de ambiente de desenvolvimento.<br/><br/>Small is Beautiful -- The Big Bang Launch Failure of Healthcare.gov (http://bit.ly/2MM5vDi) |
| 2 | 04-Mar | [Processos de Software; SW Legado vs SW Bonito](https://github.com/IF977/if977/blob/master/lectures/if977-s01a01-02.pdf) | #4 episódio do Legal Talks no ar! O PodCast da Queiroz Cavalcanti Advocacia, uma conversa com Teco Sodré sobre inovação, empreendedorismo e transformação digital.<br/><br/>Apple: https://apple.co/2WunSP1<br/>Spotify: https://spoti.fi/333N0yN<br/>Deezer: https://bit.ly/2NrB43g<br/>Google: https://bit.ly/2N0nJzP<br/><br/>[Manifesto ágil](http://agilemanifesto.org/iso/ptbr/manifesto.html), [Princípios Ágeis](http://agilemanifesto.org/iso/ptbr/principles.html), [XP](http://www.extremeprogramming.org/rules.html), [Scrum](https://www.scrum.org/Portals/0/Documents/Scrum%20Guides/2013/Scrum-Guide-Portuguese-BR.pdf), [Lean Software Development](http://www.agilcoop.org.br/sites/ime.usp.br.agilcoop/files/sbqs-slides.pdf) |
| 3 | 09-Mar | [Programação em Par; SaaS e Cloud Computing; Qualidade; Produtividade](https://github.com/IF977/if977/blob/master/lectures/if977-s02a01-02.pdf) | |
| 4 | 11-Mar | [Um pouco de Javascript](https://github.com/IF977/if977/blob/master/lectures/if977-s02a01-02.pdf) | |
| 5 | 16-Mar | [Startups Lean vs Expansivas; Design de Experiência](https://github.com/IF977/if977/blob/master/lectures/if977-s03a01.pdf) | [Lean Startup e MVP: entendendo e aplicando os conceitos](https://www.sebrae.com.br/sites/PortalSebrae/artigos/entenda-o-que-e-lean-startup,03ebb2a178c83410VgnVCM1000003b74010aRCRD) |
| 6 | 18-Mar | [A Web como um sistema cliente-servidor; SOA; API](https://github.com/IF977/if977/blob/master/lectures/if977-s03a02.pdf) | |
| 7 | 23-Mar | [REST; HTML & CSS](https://github.com/IF977/if977/blob/master/lectures/if977-s04a01.pdf) | Recomendado: Work through “HTML-- Structuring the Web” section of W3C HTML tutorial (https://mzl.la/32eSDcC) and “Bootstrap 4 in 30 minutes” (http://bit.ly/2HHybsS)<br/><br/>FreeCodeCamp tutorial (https://www.freecodecamp.org) |
| 8 | 25-Mar | *<span style="color: #008000;">Aula prática sobre GitHub (Ferramenta de controle de versão) e Configuração do ambiente para desenvolvimento do projeto</span>* | [Iniciando com Git by Rocketseat](https://www.youtube.com/watch?v=MW7hrQe6aYo&list=PL85ITvJ7FLoh-1TFRDe7bHzAWY4DlIRtk) |
| 9 | 30-Mar | [Depuração; Construindo API’s em Node + Express](https://github.com/IF977/if977/blob/master/lectures/if977-s05a01.pdf) | |
| 10 | 01-Apr | [Model-View-Controller; Olá AdonisJs!](https://github.com/IF977/if977/blob/master/lectures/if977-s05a02.pdf) | |
| 11 | 06-Apr | [Criando CRUDI e relações em API REST no AdonisJS](https://github.com/IF977/if977/blob/master/lectures/if977-s06a01.pdf) | |
| 12 | 08-Apr | [Finalizando MVC; Introdução a Behavior-Driven Design & User Stories](https://github.com/IF977/if977/blob/master/lectures/if977-s06a02.pdf) | |
| 13 | 13-Apr | **<span style="color: #ff0000;">Revisão para o 1º Exercício Escolar</span>** | |
| 14 | 15-Apr | **<span style="color: #ff0000;">1º Exercício Escolar</span>** | *<span style="color: #ff0000;">Vá ao bebedouro e/ou sanitário antes. São apenas 2 horas de duração.<br/>Leia a prova logo que recebê-la. Você tem até 20 minutos para tirar suas dúvidas, após isso, nenhuma pergunta será respondida.<br/>Responda a prova com caneta (lembre-se de trazer seu material, o professor não tem obrigação de cuidar disso pra você).</span>* |
| 15 | 20-Apr | [SMART HU; Lo-Fi; Points & Velocity](https://github.com/IF977/if977/blob/master/lectures/if977-s07a01.pdf) | |
| 16 | 22-Apr | [Evolução & Introdução a Testes e TDD](https://github.com/IF977/if977/blob/master/lectures/if977-s07a02.pdf) | [TechTalk: Como aprendi que testar software é importante, Prof. Dr. Maurício Aniche](http://www.mauricioaniche.com/talks/2018/unb.html) |
| 17 | 27-Apr | *<span style="color: #008000;">Aula prática sobre TDD com Mocha & Chai (Ferramenta de automação de testes)</span>* | |
| 18 | 29-Apr | *<span style="color: #008000;">Aula prática sobre ReactJS (Ferramenta de desenvolvimento de front-end)</span>* | |
| 19 | 04-May | [Testes Unitários; Automatizados; TDD; Testes de Integração; Testes fim-a-fim](https://github.com/IF977/if977/blob/master/lectures/if977-s10a02.pdf) | |
| 20 | 06-May | *<span style="color: #008000;">Aula prática sobre Cypress (Ferramenta de automação de testes de integração e fim-a-fim)</span>* | |
| 21 | 11-May | *<span style="color: #008000;">Aula prática sobre Heroku (A plataforma para implantação do projeto)</span>* | |
| 22 | 13-May | [Qualidade de Software; Débito Técnico; Revisão de Código](https://github.com/IF977/if977/blob/master/lectures/if977-s12a02.pdf) | |
| 23 | 18-May | [Integração Contínua & Implantação Contínua](https://github.com/IF977/if977/blob/master/lectures/if977-s14a01.pdf) | |
| 24 | 20-May | [Fica, vai ter bolo! Afinal, o que é ES; Design Sprints e Agile Sprints](https://github.com/IF977/if977/blob/master/lectures/if977-s14a02.pdf) | |
| 25 | 25-May | **<span style="color: #ff0000;">Revisão para o 2º Exercício Escolar</span>** | |
| 26 | 27-May | **<span style="color: #ff0000;">2º Exercício Escolar</span>** | *<span style="color: #ff0000;">Vá ao bebedouro e/ou sanitário antes. São apenas 2 horas de duração.<br/>Leia a prova logo que recebê-la. Você tem até 20 minutos para tirar suas dúvidas, após isso, nenhuma pergunta será respondida.<br/>Responda a prova com caneta (lembre-se de trazer seu material, o professor não tem obrigação de cuidar disso pra você).</span>* |
| 27 | 01-Jun | *<span style="color: #8B4513;">Aula prática para trabalhar no projeto</span>* | |
| 28 | 03-Jun | *<span style="color: #8B4513;">Aula prática para trabalhar no projeto</span>* | |
| 29 | 08-Jun | *<span style="color: #8B4513;">Aula prática para trabalhar no projeto</span>* | |
| 30 | 10-Jun | *<span style="color: #8B4513;">Aula prática para trabalhar no projeto</span>* | |
| 31 | 15-Jun | *<span style="color: #8B4513;">Aula prática para trabalhar no projeto</span>* | |
| 32 | 17-Jun | *<span style="color: #8B4513;">Aula prática para trabalhar no projeto</span>* | |
| 33 | 22-Jun | *<span style="color: #8B4513;">Aula prática para trabalhar no projeto</span>* | |
| 34 | 24-Jun | *<span style="color: #8B4513;">Aula prática para trabalhar no projeto</span>* | |
| 35 | 29-Jun | **<span style="color: #D2691E;">Apresentação dos Projetos (por sorteio)</span>** | |
| 36 | 01-Jul | **<span style="color: #D2691E;">Apresentação dos Projetos (por sorteio), se necessário (caso não tenham todos apresentados na aula passada)</span>** | |
| 37 | 13-Jul | **<span style="color: #ff0000;">2ª Chamada e Exercício Escolar Final</span>** | |
| 467.695652 | 948 | 0.24821 | por_Latn | 0.730599 |
2ff63156fbc550d41745396eda72e414f7a851d1 | 3,507 | md | Markdown | README.md | MadMonkey87/Homey.InsightTrends | 44784618cbe37a22943af7222cae1b0324888e20 | [
"MIT"
] | 1 | 2022-02-02T12:11:44.000Z | 2022-02-02T12:11:44.000Z | README.md | MadMonkey87/Homey.InsightTrends | 44784618cbe37a22943af7222cae1b0324888e20 | [
"MIT"
] | 5 | 2021-04-09T17:05:28.000Z | 2021-09-21T17:27:47.000Z | README.md | MadMonkey87/Homey.InsightTrends | 44784618cbe37a22943af7222cae1b0324888e20 | [
"MIT"
] | 3 | 2021-05-27T15:56:17.000Z | 2021-12-22T20:31:33.000Z | # Insight Trends
[](https://shields.io/)
Homey features powerful insights that allow you to see all sensor measurements and it's development in the past. Get one step further and not only see the insights put also act accordingly or even see a little bit into the future!
The app provides a bunch of action- and condition flow cards where you select an insight (a device and a capability, i.e. temperature outside) and a scope to analyse (i.e. the last 15 minutes). The following results will then be calculated:
- Trend: a value between -1 and 1 indicating if the sensors measurement is going up or down (and how fast/slow). for example a value of 0.75 means the trend is going up rapidly while -0.1 means a slight downwards trend
- Min/max: the minimal/maximal value discovered within the scope
- Average: the average of all values in the scope (arithmetic mean)
- Median: if all values would get sorted and if you take the value in the middle this is the median
- Standard deviation: indicator active/inactive the measured value or how 'spreaded' the data set is
- Dataset size: how many measurements the scope has. This can be useful to determine how trustworthy the results above are. For example if you have a sensor that only reports every 30 minutes and your scope is one hour you will get some results but they are based on just two measurements so the trend is maybe not that accurate. Important: a bigger scope might not have a bigger dataset than a smaller one as the accuracy (and therefore the sample points) also get is reduced.
Example usage scenarios:
- If you have an humidity sensor and you want an alarm to go off if the humidity is too high. When you take a shower it might be that the alarm goes on because you have a very high humidity for a short amount of time which is okay. Before you trigger the alarm you now might check the average humidity over the past 4 hours and only trigger the alarm if also this value is high.
- Long term analysis: you could analyse if for example the temperature is going up or down over a longer period of time and accordingly take measurements early (heating/cooling). Because you are considering a longer period of time this basically excludes short term events such as a rainy weekend during the summer.
- You not only get the current measurements but you also get insights how it came to the current measurement. If you're monitoring the temperature for example you would see from the trend if the temperature raised/dropped rather fast or slowly which can indicate different reasons, i.e. an open window versus a minor problem with your heating system.
- Less complex flow scenarios: for some reason you might need to now if the temperature went bellow zero in the last night. Instead of having to listen to all events and store the lowest temperature and resetting this variable you might just use the insights to check this at any time for any scope.
- Act early: instead of triggering an alarm when it is already too late you might analyse the trends and give a warning early. For example you might want to prevent mold by monitoring humidity and temperature. Depending of the current values and also it's trends you then can detect this risk early!
- Detect if some behaviour starts to change: for example if you have a vibration sensor on your washing machine you could see if something is wrong if the standard deviation increases over time.
| 159.409091 | 478 | 0.789279 | eng_Latn | 0.999926 |
2ff642f885f90d3e1c6b6287b731fdcc58b41b5d | 6,694 | md | Markdown | tagged/music.md | weTeams/bookmarks | 3b745d9e9b30de54e6eaecdfcd6b8707dc8f4a58 | [
"X11"
] | null | null | null | tagged/music.md | weTeams/bookmarks | 3b745d9e9b30de54e6eaecdfcd6b8707dc8f4a58 | [
"X11"
] | null | null | null | tagged/music.md | weTeams/bookmarks | 3b745d9e9b30de54e6eaecdfcd6b8707dc8f4a58 | [
"X11"
] | null | null | null | ## Bookmarks tagged [[music]](https://www.bookmarks.dev/search?q=[music])
_<sup><sup>[www.bookmarks.dev/tagged/music](https://www.bookmarks.dev/tagged/music)</sup></sup>_
---
#### [Sonic Pi - The Live Coding Music Synth for Everyone](https://sonic-pi.net/)
_<sup>https://sonic-pi.net/</sup>_
Sonic Pi is a new kind of instrument for a new generation of musicians. It is simple to learn, powerful enough for live performances and free to download.
* **tags**: [music-dev](../tagged/music-dev.md), [music](../tagged/music.md)
---
#### [EarSketch](https://earsketch.gatech.edu/earsketch2/#)
_<sup>https://earsketch.gatech.edu/earsketch2/#</sup>_
Learning Python dev through the passion of music
* **tags**: [music](../tagged/music.md), [music-dev](../tagged/music-dev.md), [py](../tagged/py.md), [python](../tagged/python.md), [learn-to-code](../tagged/learn-to-code.md)
---
#### [EasyMIDI](https://github.com/algoGuy/EasyMIDI)
_<sup>https://github.com/algoGuy/EasyMIDI</sup>_
EasyMidi is a simple and reliable library for working with standard midi file (SMF).
* **tags**: [go](../tagged/go.md), [audio](../tagged/audio.md), [music](../tagged/music.md)
* :octocat: **[source code](https://github.com/algoGuy/EasyMIDI)**
---
#### [flac](https://github.com/eaburns/flac)
_<sup>https://github.com/eaburns/flac</sup>_
No-frills native Go FLAC decoder that decodes FLAC files into byte slices.
* **tags**: [go](../tagged/go.md), [audio](../tagged/audio.md), [music](../tagged/music.md)
* :octocat: **[source code](https://github.com/eaburns/flac)**
---
#### [flac](https://github.com/mewkiz/flac)
_<sup>https://github.com/mewkiz/flac</sup>_
Native Go FLAC encoder/decoder with support for FLAC streams.
* **tags**: [go](../tagged/go.md), [audio](../tagged/audio.md), [music](../tagged/music.md)
* :octocat: **[source code](https://github.com/mewkiz/flac)**
---
#### [gaad](https://github.com/Comcast/gaad)
_<sup>https://github.com/Comcast/gaad</sup>_
Native Go AAC bitstream parser.
* **tags**: [go](../tagged/go.md), [audio](../tagged/audio.md), [music](../tagged/music.md)
* :octocat: **[source code](https://github.com/Comcast/gaad)**
---
#### [go-sox](https://github.com/krig/go-sox)
_<sup>https://github.com/krig/go-sox</sup>_
libsox bindings for go.
* **tags**: [go](../tagged/go.md), [audio](../tagged/audio.md), [music](../tagged/music.md)
* :octocat: **[source code](https://github.com/krig/go-sox)**
---
#### [go_mediainfo](https://github.com/zhulik/go_mediainfo)
_<sup>https://github.com/zhulik/go_mediainfo</sup>_
libmediainfo bindings for go.
* **tags**: [go](../tagged/go.md), [audio](../tagged/audio.md), [music](../tagged/music.md)
* :octocat: **[source code](https://github.com/zhulik/go_mediainfo)**
---
#### [gosamplerate](https://github.com/dh1tw/gosamplerate)
_<sup>https://github.com/dh1tw/gosamplerate</sup>_
libsamplerate bindings for go.
* **tags**: [go](../tagged/go.md), [audio](../tagged/audio.md), [music](../tagged/music.md)
* :octocat: **[source code](https://github.com/dh1tw/gosamplerate)**
---
#### [id3v2](https://github.com/bogem/id3v2)
_<sup>https://github.com/bogem/id3v2</sup>_
Fast and stable ID3 parsing and writing library for Go.
* **tags**: [go](../tagged/go.md), [audio](../tagged/audio.md), [music](../tagged/music.md)
* :octocat: **[source code](https://github.com/bogem/id3v2)**
---
#### [malgo](https://github.com/gen2brain/malgo)
_<sup>https://github.com/gen2brain/malgo</sup>_
Mini audio library.
* **tags**: [go](../tagged/go.md), [audio](../tagged/audio.md), [music](../tagged/music.md)
* :octocat: **[source code](https://github.com/gen2brain/malgo)**
---
#### [minimp3](https://github.com/tosone/minimp3)
_<sup>https://github.com/tosone/minimp3</sup>_
Lightweight MP3 decoder library.
* **tags**: [go](../tagged/go.md), [audio](../tagged/audio.md), [music](../tagged/music.md)
* :octocat: **[source code](https://github.com/tosone/minimp3)**
---
#### [mix](https://github.com/go-mix/mix)
_<sup>https://github.com/go-mix/mix</sup>_
Sequence-based Go-native audio mixer for music apps.
* **tags**: [go](../tagged/go.md), [audio](../tagged/audio.md), [music](../tagged/music.md)
* :octocat: **[source code](https://github.com/go-mix/mix)**
---
#### [mp3](https://github.com/tcolgate/mp3)
_<sup>https://github.com/tcolgate/mp3</sup>_
Native Go MP3 decoder.
* **tags**: [go](../tagged/go.md), [audio](../tagged/audio.md), [music](../tagged/music.md)
* :octocat: **[source code](https://github.com/tcolgate/mp3)**
---
#### [music-theory](https://github.com/go-music-theory/music-theory)
_<sup>https://github.com/go-music-theory/music-theory</sup>_
Music theory models in Go.
* **tags**: [go](../tagged/go.md), [audio](../tagged/audio.md), [music](../tagged/music.md)
* :octocat: **[source code](https://github.com/go-music-theory/music-theory)**
---
#### [Oto](https://github.com/hajimehoshi/oto)
_<sup>https://github.com/hajimehoshi/oto</sup>_
A low-level library to play sound on multiple platforms.
* **tags**: [go](../tagged/go.md), [audio](../tagged/audio.md), [music](../tagged/music.md)
* :octocat: **[source code](https://github.com/hajimehoshi/oto)**
---
#### [PortAudio](https://github.com/gordonklaus/portaudio)
_<sup>https://github.com/gordonklaus/portaudio</sup>_
Go bindings for the PortAudio audio I/O library.
* **tags**: [go](../tagged/go.md), [audio](../tagged/audio.md), [music](../tagged/music.md)
* :octocat: **[source code](https://github.com/gordonklaus/portaudio)**
---
#### [portmidi](https://github.com/rakyll/portmidi)
_<sup>https://github.com/rakyll/portmidi</sup>_
Go bindings for PortMidi.
* **tags**: [go](../tagged/go.md), [audio](../tagged/audio.md), [music](../tagged/music.md)
* :octocat: **[source code](https://github.com/rakyll/portmidi)**
---
#### [taglib](https://github.com/wtolson/go-taglib)
_<sup>https://github.com/wtolson/go-taglib</sup>_
Go bindings for taglib.
* **tags**: [go](../tagged/go.md), [audio](../tagged/audio.md), [music](../tagged/music.md)
* :octocat: **[source code](https://github.com/wtolson/go-taglib)**
---
#### [vorbis](https://github.com/mccoyst/vorbis)
_<sup>https://github.com/mccoyst/vorbis</sup>_
"Native" Go Vorbis decoder (uses CGO, but has no dependencies).
* **tags**: [go](../tagged/go.md), [audio](../tagged/audio.md), [music](../tagged/music.md)
* :octocat: **[source code](https://github.com/mccoyst/vorbis)**
---
#### [waveform](https://github.com/mdlayher/waveform)
_<sup>https://github.com/mdlayher/waveform</sup>_
Go package capable of generating waveform images from audio streams.
* **tags**: [go](../tagged/go.md), [audio](../tagged/audio.md), [music](../tagged/music.md)
* :octocat: **[source code](https://github.com/mdlayher/waveform)**
---
| 44.626667 | 175 | 0.665521 | yue_Hant | 0.164282 |
2ff6e4cf5dbf642ee873bdc28d5708c0fa65e163 | 2,234 | md | Markdown | docs/build/reference/allowbind-prevent-dll-binding.md | MSDN-WhiteKnight/cpp-docs.ru-ru | 6d13c6c86d876623e5ca29f65ff8b7ffd1045811 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/build/reference/allowbind-prevent-dll-binding.md | MSDN-WhiteKnight/cpp-docs.ru-ru | 6d13c6c86d876623e5ca29f65ff8b7ffd1045811 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/build/reference/allowbind-prevent-dll-binding.md | MSDN-WhiteKnight/cpp-docs.ru-ru | 6d13c6c86d876623e5ca29f65ff8b7ffd1045811 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: /ALLOWBIND (запретить привязку DLL)
ms.date: 11/04/2016
f1_keywords:
- VC.Project.VCLinkerTool.PreventDLLBinding
- /allowbind
helpviewer_keywords:
- /ALLOWBIND linker option
- binding DLLs
- preventing DLL binding
- ALLOWBIND linker option
- -ALLOWBIND linker option
- DLLs [C++], preventing binding
ms.assetid: 30e37e24-12e4-407e-988a-39d357403598
ms.openlocfilehash: ffe32a1df1fb85c7ae47b07c1ada6c53b269f5f9
ms.sourcegitcommit: 6052185696adca270bc9bdbec45a626dd89cdcdd
ms.translationtype: MT
ms.contentlocale: ru-RU
ms.lasthandoff: 10/31/2018
ms.locfileid: "50667302"
---
# <a name="allowbind-prevent-dll-binding"></a>/ALLOWBIND (запретить привязку DLL)
```
/ALLOWBIND[:NO]
```
## <a name="remarks"></a>Примечания
Параметр /ALLOWBIND:NO устанавливает в заголовке библиотеки DLL бит, который указывает программе Bind.exe на то, что привязка образа не допускается. Если DLL имеет цифровую подпись, привязывать ее не следует (при привязке цифровая подпись становится недействительной).
Можно изменить существующую библиотеку DLL для функциональности параметра/ALLOWBIND с [параметра/ALLOWBIND](../../build/reference/allowbind.md) параметр программы EDITBIN.
### <a name="to-set-this-linker-option-in-the-visual-studio-development-environment"></a>Задание данного параметра компоновщика в среде разработки Visual Studio
1. Откройте диалоговое окно **Страницы свойств** проекта. Дополнительные сведения см. в разделе [Работа со свойствами проекта](../../ide/working-with-project-properties.md).
1. Разверните **свойства конфигурации**, **компоновщика**и выберите **командной строки**.
1. Введите `/ALLOWBIND:NO` в **Дополнительные параметры**.
### <a name="to-set-this-linker-option-programmatically"></a>Задание данного параметра компоновщика программным способом
- См. раздел <xref:Microsoft.VisualStudio.VCProjectEngine.VCCLCompilerTool.AdditionalOptions%2A>.
## <a name="see-also"></a>См. также
[Настройка параметров компоновщика](../../build/reference/setting-linker-options.md)<br/>
[Параметры компоновщика](../../build/reference/linker-options.md)<br/>
[Функция BindImage](/windows/desktop/api/imagehlp/nf-imagehlp-bindimage)<br/>
[Функция BindImageEx](/windows/desktop/api/imagehlp/nf-imagehlp-bindimageex) | 43.803922 | 268 | 0.786929 | rus_Cyrl | 0.461993 |
2ff73cb701beddc0db96397e33a16cce3ec3958b | 7,485 | md | Markdown | docs/AlertRule.md | sematext/sematext-api-client-nodejs | a286994b05d233967f6e295615c46d7114698fe6 | [
"Apache-2.0"
] | 2 | 2020-05-01T12:15:27.000Z | 2020-08-31T06:09:48.000Z | docs/AlertRule.md | sematext/sematext-api-client-nodejs | a286994b05d233967f6e295615c46d7114698fe6 | [
"Apache-2.0"
] | null | null | null | docs/AlertRule.md | sematext/sematext-api-client-nodejs | a286994b05d233967f6e295615c46d7114698fe6 | [
"Apache-2.0"
] | 1 | 2021-04-29T13:15:02.000Z | 2021-04-29T13:15:02.000Z | # SematextApiClientJavascript.AlertRule
## Properties
| Name | Type | Description | Notes |
| ----------------------------------------- | ------------------------------------------------------------------- | ----------- | ---------- |
| **accountEmail** | **String** | | [optional] |
| **allowedAppTypes** | **[Number]** | | [optional] |
| **analyzingTime** | **String** | | [optional] |
| **appDisplayState** | **String** | | [optional] |
| **appId** | **Number** | | [optional] |
| **appName** | **String** | | [optional] |
| **appState** | **String** | | [optional] |
| **appToken** | **String** | | [optional] |
| **appType** | **String** | | [optional] |
| **backToNormalNeeded** | **Boolean** | | [optional] |
| **chartKey** | **String** | | [optional] |
| **color** | **String** | | [optional] |
| **creatorEmail** | **String** | | [optional] |
| **defaultAggType** | **String** | | [optional] |
| **description** | **String** | | [optional] |
| **disallowedAppTypes** | **[Number]** | | [optional] |
| **enabled** | **Boolean** | | [optional] |
| **estimateOperation** | **String** | | [optional] |
| **estimateValue** | **Number** | | [optional] |
| **filterValues** | **String** | | [optional] |
| **filterValuesObj** | [**[FilterValue]**](FilterValue.md) | | [optional] |
| **ignoreRegularEventsEnabled** | **Boolean** | | [optional] |
| **integrations** | **String** | | [optional] |
| **lastDataReceivedDate** | **Number** | | [optional] |
| **lastSent** | **Number** | | [optional] |
| **lastTriggered** | **Number** | | [optional] |
| **metadata** | **Object** | | [optional] |
| **metricKey** | **String** | | [optional] |
| **metricLabel** | **String** | | [optional] |
| **minDelayBetweenNotificationsInMinutes** | **String** | | [optional] |
| **name** | **String** | | [optional] |
| **notificationEmails** | **[String]** | | [optional] |
| **notificationIntegrations** | [**[NotificationIntegration]**](NotificationIntegration.md) | | [optional] |
| **notificationsEnabled** | **Boolean** | | [optional] |
| **query** | **String** | | [optional] |
| **reportName** | **String** | | [optional] |
| **ruleKey** | **Number** | | [optional] |
| **ruleType** | **String** | | [optional] |
| **runbook** | **String** | | [optional] |
| **savedQueryId** | **Number** | | [optional] |
| **schedule** | [**[AlertRuleScheduleWeekdayDto]**](AlertRuleScheduleWeekdayDto.md) | | [optional] |
| **sematextService** | **String** | | [optional] |
| **sendToEmail** | **String** | | [optional] |
| **timezone** | **String** | | [optional] |
| **useOnlyAlertRuleIntegrations** | **Boolean** | | [optional] |
| **userPermissions** | [**UserPermissions**](UserPermissions.md) | | [optional] |
| **valueColumnName** | **String** | | [optional] |
| **valueName** | **String** | | [optional] |
<a name="EstimateOperationEnum"></a>
## Enum: EstimateOperationEnum
- `LESS` (value: `"LESS"`)
- `MORE` (value: `"MORE"`)
- `EQUAL` (value: `"EQUAL"`)
- `UN_EQUAL` (value: `"UN_EQUAL"`)
- `LESS_OR_EQUAL` (value: `"LESS_OR_EQUAL"`)
- `MORE_OR_EQUAL` (value: `"MORE_OR_EQUAL"`)
| 113.409091 | 142 | 0.222712 | yue_Hant | 0.35421 |
2ff775bcb1eefb5ee99c476e01fbb624906a3056 | 3,102 | md | Markdown | src/Oro/Bundle/SecurityBundle/Resources/doc/implementation.md | Akenlab/platform | 04aecb850588d11de436653e1d75f37a69f26e94 | [
"MIT"
] | 2 | 2015-01-04T18:59:15.000Z | 2015-01-21T00:34:02.000Z | src/Oro/Bundle/SecurityBundle/Resources/doc/implementation.md | Akenlab/platform | 04aecb850588d11de436653e1d75f37a69f26e94 | [
"MIT"
] | 15 | 2015-03-19T08:35:11.000Z | 2015-11-23T10:03:38.000Z | src/Oro/Bundle/SecurityBundle/Resources/doc/implementation.md | Akenlab/platform | 04aecb850588d11de436653e1d75f37a69f26e94 | [
"MIT"
] | 5 | 2015-01-30T16:21:47.000Z | 2022-02-18T10:59:41.000Z | Implementation
========
Currently, the application has two types of ACL extensions: Actions(Capabilities) and Entities.
You can use @AclAncestor annotation to protect controller actions.
``` php
use Oro\Bundle\SecurityBundle\Annotation\AclAncestor; #required for AclAncestor annotation
...
/**
* @AclAncestor("myentity_view")
*/
public function viewAction()
```
or check in code directly with [securityFacade service](#securityFacade)
``` php
$this->securityFacade->isGranted('myentity_view')
```
**Capabilities**:
Additional resources that are not related to an entity, e.g. Configuration, Search etc.
- Using acl.yml file from MyBundle/Resource/config/acl.yml:
``` yml
can_do_something:
label: Do something
type: action
group_name: "Some Group"
bindings: ~
```
Than it can be used in @AclAncestor annotation
``` php
use Oro\Bundle\SecurityBundle\Annotation\AclAncestor; #required for AclAncestor annotation
...
/**
* @AclAncestor("can_do_something")
*/
public function somethingAction()
```
or check in code directly with [securityFacade service](#securityFacade)
``` php
$this->securityFacade->isGranted('can_do_something')
```
If you'd like to bind acl resource to specific controller action, you can use bindings:
``` yml
can_do_something_specific:
label: Do something
type: action
group_name: "Some Group"
bindings:
- { class: someClass, method: someMethod}
```
In this case, when someMethod of someClass is called, can_do_something_specific premission will be checked.
#### Security Facade
oro_security.security_facade is a public service that covers most of ACL check cases and it should be injected in case some custom ACL checks are required.
There are 2 public methods:
``` php
isClassMethodGranted($class, $method)
```
Checks if an access to the given method of the given class is granted
and
``` php
isGranted($attributes[, $object])
```
Checks if an access to the resource defined by `$attributes` and `$object(optional)` is granted
**$attributes** can be a role name(s), permission name(s), an ACL annotation id or some other identifiers depending on registered security voters.
**$object** can be a descriptor('Entity:MyBundle:MyEntity'), entity object or instance of ObjectIdentity
**Examples**
Checking access to some ACL annotation resource
``` php
$this->securityFacade->isGranted('some_resource_id')
```
Checking VIEW access to the entity by class name
``` php
$this->securityFacade->isGranted('VIEW', 'Entity:MyBundle:MyEntity' );
```
Checking ASSIGN access to the entity object
``` php
$this->securityFacade->isGranted('ASSIGN', $myEntity);
```
Checking access is performed in the following way: **Object-Scope**->**Class-Scope**->**Default Permissions**.
For example, we are checking View permission to $myEntity object of MyEntity class. When we call
``` php
$this->securityFacade->isGranted('VIEW', $myEntity);
```
first ACL for `$myEntity` object is checked, if nothing is found, then it checks ACL for `MyEntity` class and if no records are found, finally checks the Default(root) permissions.
| 26.741379 | 180 | 0.743714 | eng_Latn | 0.974595 |
2ff83f08cf4ea5533057253a868d4a4c06a9e384 | 2,104 | md | Markdown | motivation/index.md | Code-Connect/Landing-Page | b7e39acc0f29d6882473124d82d64899b0a7d5d7 | [
"Apache-2.0"
] | null | null | null | motivation/index.md | Code-Connect/Landing-Page | b7e39acc0f29d6882473124d82d64899b0a7d5d7 | [
"Apache-2.0"
] | null | null | null | motivation/index.md | Code-Connect/Landing-Page | b7e39acc0f29d6882473124d82d64899b0a7d5d7 | [
"Apache-2.0"
] | 1 | 2018-04-14T03:52:12.000Z | 2018-04-14T03:52:12.000Z | ---
layout: single
---
# Motivationsschreiben
Heutzutage stehen nicht allein gute Leistungen in Schule und Studium im Vordergrund für die Auswahl zur Einstellung in einem Unternehmen. Viel mehr zählen Berufserfahrung und anderweitig erbrachte Leistungen. Solche kann man sich z.B. durch das Mitwirken an Open Source Projekten aneignen. Hier besteht nun die Schwierigkeit, derartige Projekte und einen passenden Mentor zu finden. Genau hier kommt Code Connect ins Spiel.
Unsere Vision besteht darin, Studierenden und Neulingen anhand von Open Source Projekten die Chance zu geben, von erfahrenen Softwareentwicklern zu lernen. Durch die Arbeit an diesen Projekten und den Austausch zwischen Mentees und Mentoren wird zum einen das eigene Wissen erweitert und zum anderen werden die Projektideen der Mentoren in die Tat umgesetzt. Dadurch wird die Kommunikation und der Wissenstransfer zwischen Anfängern und Fortgeschrittenen Informatikern stark gefördert und verbessert. Mentees können ihren Mentoren jede fachspezifische Frage stellen, dadurch ihre Programmierkenntnisse verbessern und letztendlich guten Code für das Programm hervorbringen. Schließlich soll die exponentiell wachsende Zahl neuer Programmierer von der Expertise qualifizierter Softwareentwickler profitieren.
Die Zusammenarbeit zwischen Code Connect und Generation D, bildet einen sehr wichtigen Aspekt für uns. Wir möchten auf der Suche nach neuen innovativen und kreativen Ideen behilflich sein und die soziale Gesellschaft durch unser Projekt unterstützen. Außerdem sehen wir, als Informatikstudenten, große Verantwortung darin neue Ideen in der Informatik Szene zu entwickeln und zu fördern. Wir betrachten Probleme aus unterschiedlichen Perspektiven und versuchen anderen Neulingen den Einstieg in die Informatik und in den späteren Beruf zu erleichtern.
Zunächst stehen für uns der Kontakt zu Mentoren, sowie die Teilnahme an Coachings und Workshops mehr im Vordergrund, als der finanzielle Aspekt. Der Aufbau einer hilfsbereiten und wissbegierigen Community aus Mentoren und Mentees hat höchste Priorität für unser Team. | 191.272727 | 808 | 0.843631 | deu_Latn | 0.999539 |
2ff8785d4d7857c31fab2a94bf4b2fd843314f3a | 1,967 | markdown | Markdown | _posts/2015-03-22-dnssec-moving-the-needle.markdown | LindsayHill/LindsayHill.github.io | 932411a2d9bb9cafcb8efde5db0d134f581e4cda | [
"MIT"
] | null | null | null | _posts/2015-03-22-dnssec-moving-the-needle.markdown | LindsayHill/LindsayHill.github.io | 932411a2d9bb9cafcb8efde5db0d134f581e4cda | [
"MIT"
] | 4 | 2020-04-09T04:43:43.000Z | 2021-05-20T04:38:20.000Z | _posts/2015-03-22-dnssec-moving-the-needle.markdown | LindsayHill/LindsayHill.github.io | 932411a2d9bb9cafcb8efde5db0d134f581e4cda | [
"MIT"
] | 3 | 2017-11-01T16:22:37.000Z | 2018-11-11T17:52:45.000Z | ---
author: lindsay
date: 2015-03-22 07:54:40+00:00
layout: post
slug: dnssec-moving-the-needle
title: DNSSEC - Moving the Needle
categories:
- Security
tags:
- DNS
- security
---
The New Zealand ISP market is dominated by Spark, Vodafone & CallPus/Orcon. A side effect of this is that if one player does the Right Thing™, it really moves the needle. Recently, [Spark](http://www.spark.co.nz/) has done the Right Thing with [DNSSEC](https://en.wikipedia.org/wiki/Domain_Name_System_Security_Extensions).
DNSSEC takeup has been low with New Zealand ISPs. The APNIC stats indicated that around 5% of users were using DNS resolvers that had DNSSEC validation capabilities. But in December 2014, [that number jumped](http://stats.labs.apnic.net/dnssec/NZ?c=NZ&x=1&g=1&r=1&w=1&g=0) to ~15%:
[](/assets/2015/03/dnssec_nz_stats.png)
It turns out this is because Spark has enabled DNSSEC validation on some of their resolvers. NZRS have [done some analysis](https://nzrs.net.nz/content/dnssec-validation-spark-nz), and found that Spark turned on 4 new resolvers that do DNSSEC validation:
They're still running their old resolvers, so right now it's hit & miss for their customers. But it's a great start, and presumably they'll upgrade the remaining systems soon.
So [Vodafone](http://www.vodafone.co.nz/), [CallPlus](http://www.callplus.net.nz/), [Snap](http://www.snap.net.nz/), [Trustpower](http://www.trustpower.co.nz/)...when are you going to take customer security seriously too? And Spark...how long until DNSSEC is enabled for all your resolvers?
And please, no arguments about "we're not sure if it will work." Google has been doing it since [March 2013](http://www.theregister.co.uk/2013/03/20/google_adds_dnssec_validation/)...who do you think processes more DNS requests per day? Google, or your ISP?
| 67.827586 | 323 | 0.763091 | eng_Latn | 0.881754 |
2ff88e24b0e149cee446aee56c57438c826a76b4 | 171 | md | Markdown | README.md | jijosg/jijosg.github.io | 568c7022e3387885e830ceb2f8fb239c61ef48c8 | [
"MIT"
] | null | null | null | README.md | jijosg/jijosg.github.io | 568c7022e3387885e830ceb2f8fb239c61ef48c8 | [
"MIT"
] | null | null | null | README.md | jijosg/jijosg.github.io | 568c7022e3387885e830ceb2f8fb239c61ef48c8 | [
"MIT"
] | null | null | null | # This is the data for my blog
It is automatically transformed by [Jekyll](http://github.com/mojombo/jekyll)
into a static site whenever I push this repository to GitHub. | 42.75 | 77 | 0.783626 | eng_Latn | 0.999523 |
2ff8e306b78f6fe2bc7c149ee928339a09b3e4f5 | 2,496 | md | Markdown | biztalk/core/sending-an-outgoing-mdn.md | OPS-E2E-PPE/biztalk-docs.zh-CN | 4783f895d987cb13d919c7bd12ae52975b972123 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | biztalk/core/sending-an-outgoing-mdn.md | OPS-E2E-PPE/biztalk-docs.zh-CN | 4783f895d987cb13d919c7bd12ae52975b972123 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | biztalk/core/sending-an-outgoing-mdn.md | OPS-E2E-PPE/biztalk-docs.zh-CN | 4783f895d987cb13d919c7bd12ae52975b972123 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: 发送传出的 MDN |Microsoft Docs
ms.custom: ''
ms.date: 06/08/2017
ms.prod: biztalk-server
ms.reviewer: ''
ms.suite: ''
ms.tgt_pltfrm: ''
ms.topic: article
ms.assetid: 2dce7620-d354-4b76-bcbc-f97dc93c3fc3
caps.latest.revision: 12
author: MandiOhlinger
ms.author: mandia
manager: anneta
ms.openlocfilehash: 4dbe1365681fe40ef81b1634307d1535c325ad5d
ms.sourcegitcommit: 381e83d43796a345488d54b3f7413e11d56ad7be
ms.translationtype: MT
ms.contentlocale: zh-CN
ms.lasthandoff: 05/07/2019
ms.locfileid: "65399054"
---
# <a name="sending-an-outgoing-mdn"></a>发送传出的 MDN
传出的 MDN 由 AS2EDIReceive 或 AS2Receive 接收管道，并由 AS2Send 管道发送。 本主题介绍如何发送 MDN。 有关如何生成 MDN 的详细信息，请参阅[生成传出 MDN](../core/generating-an-outgoing-mdn.md)。
> [!NOTE]
> AS2EDISend 发送管道不用于发送传出的 MDN，因为在处理 MDN 时不使用该管道中的 EDI 组装器。
## <a name="agreement-resolution-for-an-mdn"></a>MDN 的协议解析
MDN 是自路由。 它包含路由到目标协议所需的信息。 发送管道使用 AS2 协议属性来处理传出的 MDN。 但是，MDN 不必签订了协议，为其路由到参与方解析。
当 AS2Send 管道处理传出的 MDN 时，它使用 AS2-到消息上下文来获得用于处理此 MDN 的协议属性中的值。 这是通过匹配 AS2-To 上下文属性与 AS2-To 协议属性中**标识符**页中的单向 AS2 协议选项卡**协议属性**对话框。 如果此 mdn 的协议解析可能会失败的 AS2-到协议未设置值。 如果无法确定协议，则使用默认协议来生成 MDN。
传出的 MDN 的默认协议，在执行证书解析列表验证。 如果不希望执行此验证，确认正确的 AS2-协议属性设置为，以便能够解析接收方并且可以确定协议属性。 如果是这样，将不使用提示验证证书解析列表的默认协议。 您还需要禁用**检查证书吊销列表**上的属性**验证**中的单向 AS2 协议选项卡页**协议属性**对话框。
## <a name="synchronous-and-asynchronous-transmission"></a>同步和异步传输
在默认 AS2 处理中，以同步方式发送 MDN。 发送 MDN 的发送端口关联与双向接收端口。 [!INCLUDE[btsBizTalkServerNoVersion](../includes/btsbiztalkservernoversion-md.md)] 将此 MDN 作为对 HTTP POST 的 HTTP 响应或作为对 HTTPS POST，相同的 TCP/IP 连接的 HTTPS 响应。 MDN 包含在消息正文的 HTTP 响应命令。
如果以异步方式发送 MDN，MDN 必须通过单独的发送端口，从 MessageBox 提取 MDN 发送。 [!INCLUDE[btsBizTalkServerNoVersion](../includes/btsbiztalkservernoversion-md.md)] 将此 MDN 作为单独 HTTP Post 发送唯一的 TCP/IP 连接不同于用来传递原始 AS2 消息。 即使此 MDN 设置为一个单独的 HTTP Post，一个 HTTP 响应命令，仍需要 post。
通常情况下将向原始 AS2 消息的回执送达选项标头中的 URL 发送异步 MDN。 但是，如果**使用的验证和 MDN 的协议设置而非消息标头**上设置属性上**验证**中的单向 AS2 协议选项卡页**协议属性**对话框中，MDN 将发送到的 URL，**回执送达选项 (URL)** 协议属性设置为。
## <a name="how-the-send-pipeline-processes-an-outgoing-mdn"></a>发送管道如何处理传出的 MDN
AS2Send 管道处理传出的 MDN 如下所示：
- 执行 MIME 处理，其中包括应用数字签名，如果在 AS2 单向协议属性中启用。
- 不可否认数据库 （BizTalkDTADb 数据库的 EdiMessageContent 表） 中创建相关条目。
- 创建 MDN 的副本 （以传输格式） 并将其存储在不可否认数据库中，如果在中启用**对出站 MDN 启用 NRR**协议属性。
- 将 MDN 传递到 HTTP 适配器。
## <a name="see-also"></a>请参阅
[BizTalk Server 如何发送 AS2 消息](../core/how-biztalk-server-sends-as2-messages.md)
[AS2 发送组件](../core/as2-send-components.md) | 45.381818 | 244 | 0.746795 | yue_Hant | 0.836844 |
2ff8e95f48e605d4941c43a38d70f3b2a181a41e | 1,690 | md | Markdown | README.md | cobli/Neng | 5987fa47518680234c46a6997c008ed47db70620 | [
"MIT"
] | null | null | null | README.md | cobli/Neng | 5987fa47518680234c46a6997c008ed47db70620 | [
"MIT"
] | null | null | null | README.md | cobli/Neng | 5987fa47518680234c46a6997c008ed47db70620 | [
"MIT"
] | null | null | null | # Neng
表計算ソフトで実現した会計帳簿です。使い慣れた表計算ソフトのインターフェイスがそのまま使えるので便利です。
* Nengの内容は完全にオープンで、自由に改変出来て、無料で使うことが出来ます。特定のシステムに依存しないので、将来使えなくなる心配もありません。
* 自前で法人確定申告する零細企業を応援する目的で税務を意識して開発しました。税制により変更される部分はeTAXに任せ、Neng自体は簡素に作ってます。
使用環境 Googleスプレッドシート(無料) ExcelファイルをGoogleDriveにアップロードした上で使用して下さい。
* Excel、Excel Online(無料)、LibreOffice Calc(無料)上でも動作しますが、操作説明はGoogleスプレッドシートに合わせてます。
* GoogleスプレッドシートとExcel Onlineはクラウド上で動作します。ExcelとLibreOffice Calcはインストール型で、応答が早いです。
* フォントは、ExcelとLibreOffice Calcでは游ゴシックですが、GoogleスプレッドシートではArialに変更されます。
## 概要
表計算ソフトを利用し、仕訳帳、総勘定元帳、精算表、財務諸表、在庫管理、の各機能を実現している持分会社(合同会社等)用の会計帳簿のテンプレートです。(マクロは使ってません。)
* 株式会社では 社員資本 → 株主資本 の読み替えとeTAX用のデータ変更が必要です。
* 法人確定申告用のeTAXに取り込める財務諸表と勘定科目内訳明細書のデータも作ります。
* eTAX用のデータはcsv形式のファイルでエクスポートする必要があります。Excel OnlineではCSV Import+Exportアドイン(無料)をインストールすればエクスポートが可能になります。
### シートの説明
全部で9つ (元帳が加われば10) のシートがあります。
1. 仕訳シート (元帳シート) 仕訳帳と総勘定元帳を兼ねるシートです。 全ての取引を取引順に並べた場合は仕訳帳になり、それを科目IDでソートすれば総勘定元帳になります。
2. 在庫シート 商品の登録、在庫の集計機能、期末棚卸高 の計算機能があります。
3. 集計シート 勘定科目の設定、精算表 の機能を持つシートです。 諸表シートの損益計算書や貸借対照表に載せていない科目残高もここで確認出来ます。
4. 諸表シート 損益計算書、貸借対照表、社員資本等変動計算書がまとまってます。 仕訳シートに全ての仕訳を入力するだけで自動的に作成されます。
5. 月次シート 複数の勘定科目の合計値を月次解析します。 法人確定申告書に添付する事業概況説明書の月毎の値はこの機能で計算出来ます。
6. Zaimシート 個別注記表、損益計算書、貸借対照表、社員資本等変動計算書をeTAXに取り込むためのデータを作ります。
7. Kamokシート 勘定科目内訳明細書をeTAXに取り込むためのデータを作ります。
8. Ex2eTAXシート ZaimシートとKamokシートからエクスポートしたcsv形式のファイルをeTAXが定める形式に変換するバッチファイルです。
9. 説明シート この会計帳簿の使い方を説明します。
* 仕訳シートに仕訳データを入力するだけで、その他の値は自動的に計算されて更新されます。
* 仕訳データの入力時に残高表示もされるので、預金通帳の残高と照合しながら仕訳出来ます。
* 在庫管理をする場合には在庫シートにも期首と期末の棚卸データを入力します。
### 行の追加方法
* (仕訳シート)仕訳データの追加
* (在庫シート)商品の登録の追加
* (集計シート)勘定科目の追加
* (月次シート)科目数の増加
必要な場所に行を挿入し、その行に淡黄色のセルを含む同一シート内の任意の行をコピーしてから白色のセルにデータを入力(コピー元の値を変更)します。
| 42.25 | 103 | 0.862722 | yue_Hant | 0.509364 |