hexsha
stringlengths 40
40
| size
int64 5
1.04M
| ext
stringclasses 6
values | lang
stringclasses 1
value | max_stars_repo_path
stringlengths 3
344
| max_stars_repo_name
stringlengths 5
125
| max_stars_repo_head_hexsha
stringlengths 40
78
| max_stars_repo_licenses
sequencelengths 1
11
| max_stars_count
int64 1
368k
⌀ | max_stars_repo_stars_event_min_datetime
stringlengths 24
24
⌀ | max_stars_repo_stars_event_max_datetime
stringlengths 24
24
⌀ | max_issues_repo_path
stringlengths 3
344
| max_issues_repo_name
stringlengths 5
125
| max_issues_repo_head_hexsha
stringlengths 40
78
| max_issues_repo_licenses
sequencelengths 1
11
| max_issues_count
int64 1
116k
⌀ | max_issues_repo_issues_event_min_datetime
stringlengths 24
24
⌀ | max_issues_repo_issues_event_max_datetime
stringlengths 24
24
⌀ | max_forks_repo_path
stringlengths 3
344
| max_forks_repo_name
stringlengths 5
125
| max_forks_repo_head_hexsha
stringlengths 40
78
| max_forks_repo_licenses
sequencelengths 1
11
| max_forks_count
int64 1
105k
⌀ | max_forks_repo_forks_event_min_datetime
stringlengths 24
24
⌀ | max_forks_repo_forks_event_max_datetime
stringlengths 24
24
⌀ | content
stringlengths 5
1.04M
| avg_line_length
float64 1.14
851k
| max_line_length
int64 1
1.03M
| alphanum_fraction
float64 0
1
| lid
stringclasses 191
values | lid_prob
float64 0.01
1
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
8a8177b1bd7d4995421854e586f44c7ea57752be | 2,244 | md | Markdown | articles/active-directory-b2c/active-directory-b2c-setup-amzn-app.md | huiw-git/azure-content-zhtw | f20103dc3d404c9c929c155b36c5a47aee5baed6 | [
"CC-BY-3.0"
] | null | null | null | articles/active-directory-b2c/active-directory-b2c-setup-amzn-app.md | huiw-git/azure-content-zhtw | f20103dc3d404c9c929c155b36c5a47aee5baed6 | [
"CC-BY-3.0"
] | null | null | null | articles/active-directory-b2c/active-directory-b2c-setup-amzn-app.md | huiw-git/azure-content-zhtw | f20103dc3d404c9c929c155b36c5a47aee5baed6 | [
"CC-BY-3.0"
] | 1 | 2020-11-04T04:34:56.000Z | 2020-11-04T04:34:56.000Z | <properties
pageTitle="Azure Active Directory B2C 預覽：Amazon 組態 | Microsoft Azure"
description="在受 Azure Active Directory B2C 保護的應用程式中，針對具有 Amazon 帳戶的取用者提供註冊和登入。"
services="active-directory-b2c"
documentationCenter=""
authors="swkrish"
manager="msmbaldwin"
editor="bryanla"/>
<tags
ms.service="active-directory-b2c"
ms.workload="identity"
ms.tgt_pltfrm="na"
ms.devlang="na"
ms.topic="article"
ms.date="01/12/2016"
ms.author="swkrish"/>
# Azure Active Directory B2C 預覽：針對具有 Amazon 帳戶的取用者提供註冊和登入
[AZURE.INCLUDE [active-directory-b2c-preview-note](../../includes/active-directory-b2c-preview-note.md)]
## 建立 Amazon 應用程式
若要在 Azure Active Directory (Azure AD) B2C 中使用 Amazon 做為身分識別提供者，您必須建立 Amazon 應用程式，並對其提供正確的參數。您需要 Amazon 帳戶來執行此動作。如果您沒有帳戶，您可以在 [http://www.amazon.com/](http://www.amazon.com/) 上取得。
1. 移至 [Amazon Developer Center (Amazon 開發人員中心)](https://login.amazon.com/)，並以您的 Amazon 帳戶認證登入。
2. 若您尚未執行此動作，請按一下 [註冊]、遵循開發人員註冊步驟，並接受原則。
3. 按一下 [註冊新應用程式]。
4. 提供應用程式資訊 (**名稱**、**說明**和**隱私權注意事項 URL**)，然後按一下 [儲存]。
5. 在 [Web 設定] 區段中，複製 [用戶端識別碼] 和 [用戶端密碼] 的值(您需要按一下 [顯示密碼] 按鈕，才能看到它)。 您必須使用這兩個值，將 Amazon 設為租用戶中的身分識別提供者。按一下位於區段底部的 [編輯]。**用戶端密碼**是重要的安全性認證。
6. 在 [允許的 JavaScript 原始來源] 欄位中輸入 `https://login.microsoftonline.com`，並在 [允許的傳回 URL] 欄位中輸入 `https://login.microsoftonline.com/te/{tenant}/oauth2/authresp`。使用您的租用戶名稱 (例如 contoso.onmicrosoft.com) 來取代 **{tenant}**。按一下 [儲存]。**{tenant}** 值會區分大小寫。
## 將 Amazon 設為您租用戶中的身分識別提供者
1. 遵循下列步驟以[瀏覽至 B2C 功能刀鋒視窗](active-directory-b2c-app-registration.md#navigate-to-the-b2c-features-blade) (位於 Azure 入口網站上)。
2. 在 B2C 功能刀鋒視窗中，按一下 [**身分識別提供者**]。
3. 按一下刀鋒視窗頂端的 [新增]。
4. 針對身分識別提供者組態，提供容易辨識的**名稱**。例如，輸入 "Amzn"。
5. 按一下 [身分識別提供者類型]、選取 [Amazon]，然後按一下 [確定]。
6. 按一下 [設定此身分識別提供者]，然後輸入您先前建立之 Amazon 應用程式的用戶端識別碼與用戶端密碼。
7. 依序按一下 [確定] 和 [建立]，以儲存您的 Amazon 組態。
<!---HONumber=AcomDC_0224_2016--> | 40.8 | 240 | 0.738414 | yue_Hant | 0.783813 |
8a81bbedf963b3b47ddf7f1ea919814406e11cad | 6,354 | md | Markdown | articles/marketplace/plan-managed-service-offer.md | georgeOsdDev/azure-docs.ja-jp | 2a180fb94381b1f17e50b24e85626240a3e7fa72 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/marketplace/plan-managed-service-offer.md | georgeOsdDev/azure-docs.ja-jp | 2a180fb94381b1f17e50b24e85626240a3e7fa72 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/marketplace/plan-managed-service-offer.md | georgeOsdDev/azure-docs.ja-jp | 2a180fb94381b1f17e50b24e85626240a3e7fa72 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Microsoft コマーシャル マーケットプレース向けのマネージド サービス オファーを計画する
description: Microsoft パートナー センターでコマーシャル マーケットプレース プログラムを使用して、Azure Marketplace 向けの新しいマネージド サービス オファーを計画する方法。
ms.service: marketplace
ms.subservice: partnercenter-marketplace-publisher
ms.topic: conceptual
author: Microsoft-BradleyWright
ms.author: brwrigh
ms.reviewer: anbene
ms.date: 12/23/2020
ms.openlocfilehash: f096e53f8054039f361bde1c5f2adffac615c53d
ms.sourcegitcommit: 867cb1b7a1f3a1f0b427282c648d411d0ca4f81f
ms.translationtype: HT
ms.contentlocale: ja-JP
ms.lasthandoff: 03/19/2021
ms.locfileid: "100371942"
---
# <a name="how-to-plan-a-managed-service-offer-for-the-microsoft-commercial-marketplace"></a>Microsoft コマーシャル マーケットプレース向けのマネージド サービス オファーを計画する方法
この記事では、パートナー センターを使用して、マネージド サービス オファーを Microsoft コマーシャル マーケットプレースに公開するための要件について説明します。
マネージド サービスは、Azure Lighthouse によるテナント間およびマルチテナント管理を可能にする Azure Marketplace のオファーです。 詳細については、「[Azure Lighthouse とは](../lighthouse/overview.md)」をご覧ください。 顧客は、マネージド サービス オファーを購入するときに、1 つ以上のサブスクリプションまたはリソース グループを委任できます。 その後、Azure Lighthouse の [Azure の委任されたリソース管理](../lighthouse/concepts/azure-delegated-resource-management.md)機能を使用して、これらのリソースを操作できます。
## <a name="eligibility-requirements"></a>資格要件
マネージド サービス オファーを公開するには、Cloud Platform の Gold または Silver Microsoft コンピテンシーを獲得している必要があります。 このコンピテンシーにより、専門知識を顧客に示すことができます。 詳細については、[Microsoft Partner Network のコンピテンシー](https://partner.microsoft.com/membership/competencies)に関するページを参照してください。
Azure Marketplace に公開するには、オファーが、適用される[コマーシャル マーケットプレース認定ポリシー](/legal/marketplace/certification-policies)をすべて満たしている必要があります。
## <a name="customer-leads"></a>潜在顧客
オファーをカスタマー リレーションシップ マネジメント (CRM) システムに接続して、顧客情報を収集する必要があります。 顧客は、自分の情報を共有する許可を求められます。 これらの顧客の詳細は、オファーの名前と ID のほか、顧客がオファーを見つけたオンライン ストアと共に、お客様が構成した CRM システムに送信されます。 コマーシャル マーケットプレースにより、Azure テーブルを使用したり、Power Automate を使用して HTTPS エンドポイントを構成したりするためのオプションと共に、異なる種類の CRM システムがサポートされています。
CRM の接続は、オファーの作成時または作成後にいつでも追加または変更できます。 詳細なガイダンスについては、「[コマーシャル マーケットプレース オファーからの潜在顧客](partner-center-portal/commercial-marketplace-get-customer-leads.md)」を参照してください。
## <a name="legal-contracts"></a>法的契約
パートナー センターの [プロパティ] ページでは、オファーを使用する際の **使用条件** を指定するよう求められます。 パートナー センターで条件を直接入力することも、条件を確認できる場所の URL を指定することもできます。 顧客は、オファーを購入する前にこれらの使用条件に同意する必要があります。
## <a name="offer-listing-details"></a>オファー登録情報の詳細
パートナー センターでマネージド サービス オファーを作成するときは、テキスト、画像、ドキュメント、その他のオファーの詳細を入力します。 これは、顧客が Azure Marketplace でオファーを見つけたときに表示されるものです。 次の例を参照してください。
:::image type="content" source="media/example-managed-service.png" alt-text="Azure Marketplace でマネージド サービス オファーがどのように表示されるのかを示しています。":::
**コールアウトの説明**
1. ロゴ
1. 名前
1. 簡単な説明
1. Categories
1. 法的契約とプライバシー ポリシー
1. 説明
1. スクリーンショット/ビデオ
1. 便利なリンク
Azure portal でのオファー登録情報の表示例を次に示します。
:::image type="content" source="media/example-managed-service-azure-portal.png" alt-text="Azure portal でこのオファーがどのように表示されるかを示しています。":::
**コールアウトの説明**
1. 名前
2. 説明
3. 便利なリンク
4. スクリーンショット/ビデオ
> [!NOTE]
> オファーが英語以外の言語の場合、オファー登録情報はその言語でかまいませんが、説明の先頭または末尾に、"This service is available in <オファーの内容の言語>" という英語の表記を含める必要があります。 また、オファーの掲載の詳細説明で使用されているものとは異なる言語で、サポート ドキュメントを提供することもできます。
オファーをより簡単に作成できるようにするには、これらの項目の一部をあらかじめ準備しておきます。 次の項目は、特に記載がない限り必須です。
**名前**: これは、コマーシャル マーケットプレースでオファー登録情報のタイトルとして表示されます。 この名前は商標登録されている場合があります。 絵文字 (商標および著作権マークの場合を除く) を含むことはできず、50 文字以下にする必要があります。
**検索結果の概要**: オファーの目的または目標を 100 文字以下で説明します。 この概要は、コマーシャル マーケットプレースの登録情報の検索結果で使用されます。 タイトルと同じにすることはできません。 上位の SEO キーワードを含めることを検討してください。
**簡単な説明**: オファーの簡単な説明 (最大 256 文字) を入力します。 これは、Azure portal のオファー登録情報に表示されます。
**説明**: 3,000 文字以下でオファーの説明を入力します。 この説明は、コマーシャル マーケットプレースの登録情報に表示されます。 価値提案、主な利点、カテゴリまたは業界の関連性、必要な情報開示を含めることを検討してください。
説明を記述するためのいくつかのヒントを次に示します。
* 先頭のいくつかの文で、以下の点を含め、プランの価値を明確に説明します。
* プランから利益を得るユーザーの種類。
* オファーが対応する顧客のニーズや問題。
* 先頭のいくつかの文が検索結果に表示される場合があることに注意してください。
* 業界固有の語彙を使用します。
HTML タグを使用して説明の書式を設定できます。 HTML 書式設定の詳細については、「[コマーシャル マーケットプレースのオファー説明でサポートされている HTML タグ](./supported-html-tags.md)」を参照してください。
**プライバシー ポリシー リンク**: サイトでホストされている、プライバシー ポリシーの URL を指定します。 オファーがプライバシーに関する法律および規制に準拠していることを保証し、有効なプライバシー ポリシーを提供する責任があります。
**便利なリンク** (省略可能): オファーに関する補足のオンライン ドキュメントをアップロードします。
**連絡先情報**: 社内の 2 人の担当者 (サポートの連絡先とエンジニアリングの連絡先) の名前、メール アドレス、電話番号を入力します (登録者自身がどちらかの担当者になることができます)。 Microsoft は、オファーに関するパートナーとの連絡にこの情報を使用します。 この情報は顧客には表示されませんが、クラウド ソリューション プロバイダー (CSP) パートナーに提供される場合があります。
**サポート URL** (省略可能): Azure グローバルの顧客や Azure Government の顧客向けのサポート Web サイトがある場合は、その URL を入力します。
**Marketplace メディア - ロゴ**: オファーの大サイズのロゴの PNG ファイルを提供します。 パートナー センターでは、これを使用して中と小のロゴが作成されます。 必要に応じて、これらのロゴを後で別の画像に置き換えることもできます。
* 大のロゴ (216 x 216 から 350 x 350 ピクセル) は、Azure Marketplace のオファー登録情報に表示されます。
* 新しいリソースが作成されると、中のロゴ (90 x 90 ピクセル) が表示されます。
* 小のロゴ (48 x 48 ピクセル) は、Azure Marketplace での検索結果で使用されます。
お客様のロゴについては、これらのガイドラインに従ってください。
* 画像が引き伸ばされていないことを確認します。
* Azure の設計には簡単なカラー パレットがあります。 ロゴのプライマリ カラーとセカンダリ カラーの数は制限してください。
* Azure portal の色は白と黒です。 これらをロゴの背景として使用しないでください。 ロゴが目立つシンプルなプライマリ カラーをお勧めします。
* 透明な背景を使用している場合は、ロゴおよびテキストが白、黒、または青ではないことを確認します。
* ロゴの外観はフラットにする必要があります。 グラデーションは避けます。 ロゴにはテキストを使用しないでください (会社またはブランドの名前であっても)。
**Marketplace メディア - スクリーンショット** (省略可能): オファーの機能を示す画像を最大 5 つ追加します。 イメージはすべて、1280 x 720 ピクセルのサイズで PNG 形式である必要があります。
**Marketplace メディア - ビデオ** (省略可能): オファーをデモンストレーションするビデオを最大 5 つアップロードします。 動画は YouTube または Vimeo でホストされていて、サムネイル (1280 x 720 PNG ファイル) が付属している必要があります。
## <a name="preview-audience"></a>プレビュー対象ユーザー
プレビュー対象ユーザーは、オファーをテストするために、Azure Marketplace で公開される前にオファーにアクセスできます。 パートナー センターの **[プレビュー対象ユーザー]** ページで、限定されたプレビュー対象ユーザーを定義できます。
> [!NOTE]
> プレビュー対象ユーザーはプライベート プランとは異なります。 プライベート プランは、選択された特定の対象ユーザーのみが利用できます。 これにより、カスタム プランについて、特定の顧客と協議できます。
Microsoft アカウント (MSA) または Azure Active Directory (Azure AD) の電子メール アドレスに招待状を送信できます。 手動で最大 10 個のメール アドレスを追加するか、.csv ファイルを使用して最大 20 個をインポートします。 オファーが既に公開されている場合も、オファーの変更や更新をテストするためにプレビュー対象ユーザーを定義することができます。
## <a name="plans-and-pricing"></a>プランと価格
マネージド サービス オファーには、少なくとも 1 つのプランが必要です。 プランでは、ソリューションのスコープ、制限、関連する価格 (該当する場合) を定義します。 オファーに対して複数のプランを作成し、さまざまな技術および価格オプションを顧客に提供することができます。 プライベート プランなど、プランに関する一般的なガイダンスについては、「[コマーシャル マーケットプレース オファーのプランと価格](plans-pricing.md)」をご覧ください。
マネージド サービスでサポートされる価格モデルは 1 つだけです: **ライセンス持ち込み (BYOL)** 。 これは、お客様が顧客に直接請求し、Microsoft はお客様に料金を一切請求しないことを意味します。
## <a name="next-steps"></a>次のステップ
* [管理サービス オファーの作成](./create-managed-service-offer.md)
* [オファーの掲載のベスト プラクティス](./gtm-offer-listing-best-practices.md) | 47.066667 | 344 | 0.819012 | jpn_Jpan | 0.636404 |
8a827c22070bb6ec494e23720082747b4fd3dd2b | 134,810 | md | Markdown | Bibles/English.KingJames/12-2 Kings.md | bibliadelpueblo/BibliaLibre | 039ab9b18364ecade1d56695cb77c40ee62b1317 | [
"CC0-1.0"
] | null | null | null | Bibles/English.KingJames/12-2 Kings.md | bibliadelpueblo/BibliaLibre | 039ab9b18364ecade1d56695cb77c40ee62b1317 | [
"CC0-1.0"
] | null | null | null | Bibles/English.KingJames/12-2 Kings.md | bibliadelpueblo/BibliaLibre | 039ab9b18364ecade1d56695cb77c40ee62b1317 | [
"CC0-1.0"
] | null | null | null | # 1
^1^ Then Moab rebelled against Israel after the death of Ahab. ^2^ And Ahaziah fell down through a lattice in his upper chamber that was in Samaria, and was sick: and he sent messengers, and said unto them, Go, enquire of Baal-zebub the god of Ekron whether I shall recover of this disease. ^3^ But the angel of the LORD said to Elijah the Tishbite, Arise, go up to meet the messengers of the king of Samaria, and say unto them, Is it not because there is not a God in Israel, that ye go to enquire of Baal-zebub the god of Ekron? ^4^ Now therefore thus saith the LORD, Thou shalt not come down from that bed on which thou art gone up, but shalt surely die. And Elijah departed.^^
^[**1:4** Thou shalt…: Heb. The bed whither thou art gone up, thou shalt not come down from it]
^5^ And when the messengers turned back unto him, he said unto them, Why are ye now turned back? ^6^ And they said unto him, There came a man up to meet us, and said unto us, Go, turn again unto the king that sent you, and say unto him, Thus saith the LORD, Is it not because there is not a God in Israel, that thou sendest to enquire of Baal-zebub the god of Ekron? therefore thou shalt not come down from that bed on which thou art gone up, but shalt surely die. ^7^ And he said unto them, What manner of man was he which came up to meet you, and told you these words?^^ ^8^ And they answered him, He was an hairy man, and girt with a girdle of leather about his loins. And he said, It is Elijah the Tishbite.
^[**1:7** What…: Heb. What was the manner of the man]
^9^ Then the king sent unto him a captain of fifty with his fifty. And he went up to him: and, behold, he sat on the top of an hill. And he spake unto him, Thou man of God, the king hath said, Come down. ^10^ And Elijah answered and said to the captain of fifty, If I be a man of God, then let fire come down from heaven, and consume thee and thy fifty. And there came down fire from heaven, and consumed him and his fifty. ^11^ Again also he sent unto him another captain of fifty with his fifty. And he answered and said unto him, O man of God, thus hath the king said, Come down quickly. ^12^ And Elijah answered and said unto them, If I be a man of God, let fire come down from heaven, and consume thee and thy fifty. And the fire of God came down from heaven, and consumed him and his fifty.
^13^ And he sent again a captain of the third fifty with his fifty. And the third captain of fifty went up, and came and fell on his knees before Elijah, and besought him, and said unto him, O man of God, I pray thee, let my life, and the life of these fifty thy servants, be precious in thy sight.^^ ^14^ Behold, there came fire down from heaven, and burnt up the two captains of the former fifties with their fifties: therefore let my life now be precious in thy sight. ^15^ And the angel of the LORD said unto Elijah, Go down with him: be not afraid of him. And he arose, and went down with him unto the king. ^16^ And he said unto him, Thus saith the LORD, Forasmuch as thou hast sent messengers to enquire of Baal-zebub the god of Ekron, is it not because there is no God in Israel to enquire of his word? therefore thou shalt not come down off that bed on which thou art gone up, but shalt surely die.
^[**1:13** fell: Heb. bowed]
^17^ So he died according to the word of the LORD which Elijah had spoken. And Jehoram reigned in his stead in the second year of Jehoram the son of Jehoshaphat king of Judah; because he had no son. ^18^ Now the rest of the acts of Ahaziah which he did, are they not written in the book of the chronicles of the kings of Israel?
# 2
^1^ And it came to pass, when the LORD would take up Elijah into heaven by a whirlwind, that Elijah went with Elisha from Gilgal. ^2^ And Elijah said unto Elisha, Tarry here, I pray thee; for the LORD hath sent me to Beth-el. And Elisha said unto him, As the LORD liveth, and as thy soul liveth, I will not leave thee. So they went down to Beth-el. ^3^ And the sons of the prophets that were at Beth-el came forth to Elisha, and said unto him, Knowest thou that the LORD will take away thy master from thy head to day? And he said, Yea, I know it; hold ye your peace. ^4^ And Elijah said unto him, Elisha, tarry here, I pray thee; for the LORD hath sent me to Jericho. And he said, As the LORD liveth, and as thy soul liveth, I will not leave thee. So they came to Jericho. ^5^ And the sons of the prophets that were at Jericho came to Elisha, and said unto him, Knowest thou that the LORD will take away thy master from thy head to day? And he answered, Yea, I know it; hold ye your peace. ^6^ And Elijah said unto him, Tarry, I pray thee, here; for the LORD hath sent me to Jordan. And he said, As the LORD liveth, and as thy soul liveth, I will not leave thee. And they two went on. ^7^ And fifty men of the sons of the prophets went, and stood to view afar off: and they two stood by Jordan.^^ ^8^ And Elijah took his mantle, and wrapped it together, and smote the waters, and they were divided hither and thither, so that they two went over on dry ground.
^[**2:7** to view: Heb. in sight, or, over against]
^9^ And it came to pass, when they were gone over, that Elijah said unto Elisha, Ask what I shall do for thee, before I be taken away from thee. And Elisha said, I pray thee, let a double portion of thy spirit be upon me. ^10^ And he said, Thou hast asked a hard thing: nevertheless, if thou see me when I am taken from thee, it shall be so unto thee; but if not, it shall not be so.^^ ^11^ And it came to pass, as they still went on, and talked, that, behold, there appeared a chariot of fire, and horses of fire, and parted them both asunder; and Elijah went up by a whirlwind into heaven.
^[**2:10** Thou hast…: Heb. Thou hast done hard in asking]
^12^ And Elisha saw it, and he cried, My father, my father, the chariot of Israel, and the horsemen thereof. And he saw him no more: and he took hold of his own clothes, and rent them in two pieces.
^13^ He took up also the mantle of Elijah that fell from him, and went back, and stood by the bank of Jordan;^^ ^14^ And he took the mantle of Elijah that fell from him, and smote the waters, and said, Where is the LORD God of Elijah? and when he also had smitten the waters, they parted hither and thither: and Elisha went over. ^15^ And when the sons of the prophets which were to view at Jericho saw him, they said, The spirit of Elijah doth rest on Elisha. And they came to meet him, and bowed themselves to the ground before him.
^[**2:13** bank: Heb. lip]
^16^ And they said unto him, Behold now, there be with thy servants fifty strong men; let them go, we pray thee, and seek thy master: lest peradventure the Spirit of the LORD hath taken him up, and cast him upon some mountain, or into some valley. And he said, Ye shall not send.^^^^ ^17^ And when they urged him till he was ashamed, he said, Send. They sent therefore fifty men; and they sought three days, but found him not. ^18^ And when they came again to him, (for he tarried at Jericho,) he said unto them, Did I not say unto you, Go not?
^[**2:16** strong…: Heb. sons of strength]
^[**2:16** some mountain: Heb. one of the mountains]
^19^ And the men of the city said unto Elisha, Behold, I pray thee, the situation of this city is pleasant, as my lord seeth: but the water is naught, and the ground barren.^^ ^20^ And he said, Bring me a new cruse, and put salt therein. And they brought it to him. ^21^ And he went forth unto the spring of the waters, and cast the salt in there, and said, Thus saith the LORD, I have healed these waters; there shall not be from thence any more death or barren land. ^22^ So the waters were healed unto this day, according to the saying of Elisha which he spake.
^[**2:19** barren: Heb. causing to miscarry]
^23^ And he went up from thence unto Beth-el: and as he was going up by the way, there came forth little children out of the city, and mocked him, and said unto him, Go up, thou bald head; go up, thou bald head. ^24^ And he turned back, and looked on them, and cursed them in the name of the LORD. And there came forth two she bears out of the wood, and tare forty and two children of them. ^25^ And he went from thence to mount Carmel, and from thence he returned to Samaria.
# 3
^1^ Now Jehoram the son of Ahab began to reign over Israel in Samaria the eighteenth year of Jehoshaphat king of Judah, and reigned twelve years. ^2^ And he wrought evil in the sight of the LORD; but not like his father, and like his mother: for he put away the image of Baal that his father had made.^^ ^3^ Nevertheless he cleaved unto the sins of Jeroboam the son of Nebat, which made Israel to sin; he departed not therefrom.
^[**3:2** image: Heb. statue]
^4^ And Mesha king of Moab was a sheepmaster, and rendered unto the king of Israel an hundred thousand lambs, and an hundred thousand rams, with the wool. ^5^ But it came to pass, when Ahab was dead, that the king of Moab rebelled against the king of Israel.
^6^ And king Jehoram went out of Samaria the same time, and numbered all Israel. ^7^ And he went and sent to Jehoshaphat the king of Judah, saying, The king of Moab hath rebelled against me: wilt thou go with me against Moab to battle? And he said, I will go up: I am as thou art, my people as thy people, and my horses as thy horses. ^8^ And he said, Which way shall we go up? And he answered, The way through the wilderness of Edom. ^9^ So the king of Israel went, and the king of Judah, and the king of Edom: and they fetched a compass of seven days’ journey: and there was no water for the host, and for the cattle that followed them.^^ ^10^ And the king of Israel said, Alas! that the LORD hath called these three kings together, to deliver them into the hand of Moab! ^11^ But Jehoshaphat said, Is there not here a prophet of the LORD, that we may enquire of the LORD by him? And one of the king of Israel’s servants answered and said, Here is Elisha the son of Shaphat, which poured water on the hands of Elijah. ^12^ And Jehoshaphat said, The word of the LORD is with him. So the king of Israel and Jehoshaphat and the king of Edom went down to him. ^13^ And Elisha said unto the king of Israel, What have I to do with thee? get thee to the prophets of thy father, and to the prophets of thy mother. And the king of Israel said unto him, Nay: for the LORD hath called these three kings together, to deliver them into the hand of Moab. ^14^ And Elisha said, As the LORD of hosts liveth, before whom I stand, surely, were it not that I regard the presence of Jehoshaphat the king of Judah, I would not look toward thee, nor see thee. ^15^ But now bring me a minstrel. And it came to pass, when the minstrel played, that the hand of the LORD came upon him. ^16^ And he said, Thus saith the LORD, Make this valley full of ditches. ^17^ For thus saith the LORD, Ye shall not see wind, neither shall ye see rain; yet that valley shall be filled with water, that ye may drink, both ye, and your cattle, and your beasts. ^18^ And this is but a light thing in the sight of the LORD: he will deliver the Moabites also into your hand. ^19^ And ye shall smite every fenced city, and every choice city, and shall fell every good tree, and stop all wells of water, and mar every good piece of land with stones.^^
^[**3:9** that…: Heb. at their feet]
^[**3:19** mar: Heb. grieve]
^20^ And it came to pass in the morning, when the meat offering was offered, that, behold, there came water by the way of Edom, and the country was filled with water.
^21^ And when all the Moabites heard that the kings were come up to fight against them, they gathered all that were able to put on armour, and upward, and stood in the border.^^^^ ^22^ And they rose up early in the morning, and the sun shone upon the water, and the Moabites saw the water on the other side as red as blood: ^23^ And they said, This is blood: the kings are surely slain, and they have smitten one another: now therefore, Moab, to the spoil.^^ ^24^ And when they came to the camp of Israel, the Israelites rose up and smote the Moabites, so that they fled before them: but they went forward smiting the Moabites, even in their country.^^ ^25^ And they beat down the cities, and on every good piece of land cast every man his stone, and filled it; and they stopped all the wells of water, and felled all the good trees: only in Kir-haraseth left they the stones thereof; howbeit the slingers went about it, and smote it.^^
^[**3:21** gathered: Heb. were cried together]
^[**3:21** put on…: Heb. gird himself with a girdle]
^[**3:23** slain: Heb. destroyed]
^[**3:24** they went…: or, they smote in it even smiting]
^[**3:25** only in…: Heb. until he left its stones in Kir-haraseth]
^26^ And when the king of Moab saw that the battle was too sore for him, he took with him seven hundred men that drew swords, to break through even unto the king of Edom: but they could not. ^27^ Then he took his eldest son that should have reigned in his stead, and offered him for a burnt offering upon the wall. And there was great indignation against Israel: and they departed from him, and returned to their own land.
# 4
^1^ Now there cried a certain woman of the wives of the sons of the prophets unto Elisha, saying, Thy servant my husband is dead; and thou knowest that thy servant did fear the LORD: and the creditor is come to take unto him my two sons to be bondmen. ^2^ And Elisha said unto her, What shall I do for thee? tell me, what hast thou in the house? And she said, Thine handmaid hath not any thing in the house, save a pot of oil. ^3^ Then he said, Go, borrow thee vessels abroad of all thy neighbours, even empty vessels; borrow not a few.^^ ^4^ And when thou art come in, thou shalt shut the door upon thee and upon thy sons, and shalt pour out into all those vessels, and thou shalt set aside that which is full. ^5^ So she went from him, and shut the door upon her and upon her sons, who brought the vessels to her; and she poured out. ^6^ And it came to pass, when the vessels were full, that she said unto her son, Bring me yet a vessel. And he said unto her, There is not a vessel more. And the oil stayed. ^7^ Then she came and told the man of God. And he said, Go, sell the oil, and pay thy debt, and live thou and thy children of the rest.^^
^[**4:3** borrow not…: or, scant not]
^[**4:7** debt: or, creditor]
^8^ And it fell on a day, that Elisha passed to Shunem, where was a great woman; and she constrained him to eat bread. And so it was, that as oft as he passed by, he turned in thither to eat bread.^^^^ ^9^ And she said unto her husband, Behold now, I perceive that this is an holy man of God, which passeth by us continually. ^10^ Let us make a little chamber, I pray thee, on the wall; and let us set for him there a bed, and a table, and a stool, and a candlestick: and it shall be, when he cometh to us, that he shall turn in thither. ^11^ And it fell on a day, that he came thither, and he turned into the chamber, and lay there. ^12^ And he said to Gehazi his servant, Call this Shunammite. And when he had called her, she stood before him. ^13^ And he said unto him, Say now unto her, Behold, thou hast been careful for us with all this care; what is to be done for thee? wouldest thou be spoken for to the king, or to the captain of the host? And she answered, I dwell among mine own people. ^14^ And he said, What then is to be done for her? And Gehazi answered, Verily she hath no child, and her husband is old. ^15^ And he said, Call her. And when he had called her, she stood in the door. ^16^ And he said, About this season, according to the time of life, thou shalt embrace a son. And she said, Nay, my lord, thou man of God, do not lie unto thine handmaid.^^ ^17^ And the woman conceived, and bare a son at that season that Elisha had said unto her, according to the time of life.
^[**4:8** it fell on a day: Heb. there was a day]
^[**4:8** constrained him: Heb. laid hold on him]
^[**4:16** season: Heb. set time]
^18^ And when the child was grown, it fell on a day, that he went out to his father to the reapers. ^19^ And he said unto his father, My head, my head. And he said to a lad, Carry him to his mother. ^20^ And when he had taken him, and brought him to his mother, he sat on her knees till noon, and then died. ^21^ And she went up, and laid him on the bed of the man of God, and shut the door upon him, and went out. ^22^ And she called unto her husband, and said, Send me, I pray thee, one of the young men, and one of the asses, that I may run to the man of God, and come again. ^23^ And he said, Wherefore wilt thou go to him to day? it is neither new moon, nor sabbath. And she said, It shall be well.^^ ^24^ Then she saddled an ass, and said to her servant, Drive, and go forward; slack not thy riding for me, except I bid thee.^^ ^25^ So she went and came unto the man of God to mount Carmel. And it came to pass, when the man of God saw her afar off, that he said to Gehazi his servant, Behold, yonder is that Shunammite: ^26^ Run now, I pray thee, to meet her, and say unto her, Is it well with thee? is it well with thy husband? is it well with the child? And she answered, It is well. ^27^ And when she came to the man of God to the hill, she caught him by the feet: but Gehazi came near to thrust her away. And the man of God said, Let her alone; for her soul is vexed within her: and the LORD hath hid it from me, and hath not told me.^^^^ ^28^ Then she said, Did I desire a son of my lord? did I not say, Do not deceive me? ^29^ Then he said to Gehazi, Gird up thy loins, and take my staff in thine hand, and go thy way: if thou meet any man, salute him not; and if any salute thee, answer him not again: and lay my staff upon the face of the child. ^30^ And the mother of the child said, As the LORD liveth, and as thy soul liveth, I will not leave thee. And he arose, and followed her. ^31^ And Gehazi passed on before them, and laid the staff upon the face of the child; but there was neither voice, nor hearing. Wherefore he went again to meet him, and told him, saying, The child is not awaked.^^ ^32^ And when Elisha was come into the house, behold, the child was dead, and laid upon his bed. ^33^ He went in therefore, and shut the door upon them twain, and prayed unto the LORD. ^34^ And he went up, and lay upon the child, and put his mouth upon his mouth, and his eyes upon his eyes, and his hands upon his hands: and he stretched himself upon the child; and the flesh of the child waxed warm. ^35^ Then he returned, and walked in the house to and fro; and went up, and stretched himself upon him: and the child sneezed seven times, and the child opened his eyes.^^ ^36^ And he called Gehazi, and said, Call this Shunammite. So he called her. And when she was come in unto him, he said, Take up thy son. ^37^ Then she went in, and fell at his feet, and bowed herself to the ground, and took up her son, and went out.
^[**4:23** well: Heb. peace]
^[**4:24** slack…: Heb. restrain not for me to ride]
^[**4:27** him…: Heb. by his feet]
^[**4:27** vexed: Heb. bitter]
^[**4:31** hearing: Heb. attention]
^[**4:35** to and fro: Heb. once hither and once thither]
^38^ And Elisha came again to Gilgal: and there was a dearth in the land; and the sons of the prophets were sitting before him: and he said unto his servant, Set on the great pot, and seethe pottage for the sons of the prophets. ^39^ And one went out into the field to gather herbs, and found a wild vine, and gathered thereof wild gourds his lap full, and came and shred them into the pot of pottage: for they knew them not. ^40^ So they poured out for the men to eat. And it came to pass, as they were eating of the pottage, that they cried out, and said, O thou man of God, there is death in the pot. And they could not eat thereof. ^41^ But he said, Then bring meal. And he cast it into the pot; and he said, Pour out for the people, that they may eat. And there was no harm in the pot.^^
^[**4:41** harm: Heb. evil thing]
^42^ And there came a man from Baal-shalisha, and brought the man of God bread of the firstfruits, twenty loaves of barley, and full ears of corn in the husk thereof. And he said, Give unto the people, that they may eat.^^ ^43^ And his servitor said, What, should I set this before an hundred men? He said again, Give the people, that they may eat: for thus saith the LORD, They shall eat, and shall leave thereof. ^44^ So he set it before them, and they did eat, and left thereof, according to the word of the LORD.
^[**4:42** the husk…: or, his scrip, or, garment]
# 5
^1^ Now Naaman, captain of the host of the king of Syria, was a great man with his master, and honourable, because by him the LORD had given deliverance unto Syria: he was also a mighty man in valour, but he was a leper.^^^^^^ ^2^ And the Syrians had gone out by companies, and had brought away captive out of the land of Israel a little maid; and she waited on Naaman’s wife.^^ ^3^ And she said unto her mistress, Would God my lord were with the prophet that is in Samaria! for he would recover him of his leprosy.^^^^ ^4^ And one went in, and told his lord, saying, Thus and thus said the maid that is of the land of Israel. ^5^ And the king of Syria said, Go to, go, and I will send a letter unto the king of Israel. And he departed, and took with him ten talents of silver, and six thousand pieces of gold, and ten changes of raiment.^^ ^6^ And he brought the letter to the king of Israel, saying, Now when this letter is come unto thee, behold, I have therewith sent Naaman my servant to thee, that thou mayest recover him of his leprosy. ^7^ And it came to pass, when the king of Israel had read the letter, that he rent his clothes, and said, Am I God, to kill and to make alive, that this man doth send unto me to recover a man of his leprosy? wherefore consider, I pray you, and see how he seeketh a quarrel against me.
^[**5:1** with: Heb. before]
^[**5:1** honourable: or, gracious: Heb. lifted up, or, accepted in countenance]
^[**5:1** deliverance: or, victory]
^[**5:2** waited…: Heb. was before]
^[**5:3** with: Heb. before]
^[**5:3** recover: Heb. gather in]
^[**5:5** with…: Heb. in his hand]
^8^ And it was so, when Elisha the man of God had heard that the king of Israel had rent his clothes, that he sent to the king, saying, Wherefore hast thou rent thy clothes? let him come now to me, and he shall know that there is a prophet in Israel.
^9^ So Naaman came with his horses and with his chariot, and stood at the door of the house of Elisha. ^10^ And Elisha sent a messenger unto him, saying, Go and wash in Jordan seven times, and thy flesh shall come again to thee, and thou shalt be clean. ^11^ But Naaman was wroth, and went away, and said, Behold, I thought, He will surely come out to me, and stand, and call on the name of the LORD his God, and strike his hand over the place, and recover the leper.^^^^^^ ^12^ Are not Abana and Pharpar, rivers of Damascus, better than all the waters of Israel? may I not wash in them, and be clean? So he turned and went away in a rage.^^ ^13^ And his servants came near, and spake unto him, and said, My father, if the prophet had bid thee do some great thing, wouldest thou not have done it? how much rather then, when he saith to thee, Wash, and be clean? ^14^ Then went he down, and dipped himself seven times in Jordan, according to the saying of the man of God: and his flesh came again like unto the flesh of a little child, and he was clean.
^[**5:11** I thought: Heb. I said]
^[**5:11** I thought…: or, I said with myself, He will surely come out, etc: Heb. I said]
^[**5:11** strike: Heb. move up and down]
^[**5:12** Abana: or, Amana]
^15^ And he returned to the man of God, he and all his company, and came, and stood before him: and he said, Behold, now I know that there is no God in all the earth, but in Israel: now therefore, I pray thee, take a blessing of thy servant. ^16^ But he said, As the LORD liveth, before whom I stand, I will receive none. And he urged him to take it; but he refused. ^17^ And Naaman said, Shall there not then, I pray thee, be given to thy servant two mules’ burden of earth? for thy servant will henceforth offer neither burnt offering nor sacrifice unto other gods, but unto the LORD. ^18^ In this thing the LORD pardon thy servant, that when my master goeth into the house of Rimmon to worship there, and he leaneth on my hand, and I bow myself in the house of Rimmon: when I bow down myself in the house of Rimmon, the LORD pardon thy servant in this thing. ^19^ And he said unto him, Go in peace. So he departed from him a little way.^^
^[**5:19** a little…: Heb. a little piece of ground]
^20^ But Gehazi, the servant of Elisha the man of God, said, Behold, my master hath spared Naaman this Syrian, in not receiving at his hands that which he brought: but, as the LORD liveth, I will run after him, and take somewhat of him. ^21^ So Gehazi followed after Naaman. And when Naaman saw him running after him, he lighted down from the chariot to meet him, and said, Is all well?^^ ^22^ And he said, All is well. My master hath sent me, saying, Behold, even now there be come to me from mount Ephraim two young men of the sons of the prophets: give them, I pray thee, a talent of silver, and two changes of garments. ^23^ And Naaman said, Be content, take two talents. And he urged him, and bound two talents of silver in two bags, with two changes of garments, and laid them upon two of his servants; and they bare them before him. ^24^ And when he came to the tower, he took them from their hand, and bestowed them in the house: and he let the men go, and they departed.^^ ^25^ But he went in, and stood before his master. And Elisha said unto him, Whence comest thou, Gehazi? And he said, Thy servant went no whither.^^ ^26^ And he said unto him, Went not mine heart with thee, when the man turned again from his chariot to meet thee? Is it a time to receive money, and to receive garments, and oliveyards, and vineyards, and sheep, and oxen, and menservants, and maidservants? ^27^ The leprosy therefore of Naaman shall cleave unto thee, and unto thy seed for ever. And he went out from his presence a leper as white as snow.
^[**5:21** Is…: Heb. Is there peace?]
^[**5:24** tower: or, secret place]
^[**5:25** no whither: Heb. not hither or thither]
# 6
^1^ And the sons of the prophets said unto Elisha, Behold now, the place where we dwell with thee is too strait for us. ^2^ Let us go, we pray thee, unto Jordan, and take thence every man a beam, and let us make us a place there, where we may dwell. And he answered, Go ye. ^3^ And one said, Be content, I pray thee, and go with thy servants. And he answered, I will go. ^4^ So he went with them. And when they came to Jordan, they cut down wood. ^5^ But as one was felling a beam, the axe head fell into the water: and he cried, and said, Alas, master! for it was borrowed.^^ ^6^ And the man of God said, Where fell it? And he shewed him the place. And he cut down a stick, and cast it in thither; and the iron did swim. ^7^ Therefore said he, Take it up to thee. And he put out his hand, and took it.
^[**6:5** axe head: Heb. iron]
^8^ Then the king of Syria warred against Israel, and took counsel with his servants, saying, In such and such a place shall be my camp.^^ ^9^ And the man of God sent unto the king of Israel, saying, Beware that thou pass not such a place; for thither the Syrians are come down. ^10^ And the king of Israel sent to the place which the man of God told him and warned him of, and saved himself there, not once nor twice. ^11^ Therefore the heart of the king of Syria was sore troubled for this thing; and he called his servants, and said unto them, Will ye not shew me which of us is for the king of Israel? ^12^ And one of his servants said, None, my lord, O king: but Elisha, the prophet that is in Israel, telleth the king of Israel the words that thou speakest in thy bedchamber.^^
^[**6:8** camp: or, encamping]
^[**6:12** None: Heb. No]
^13^ And he said, Go and spy where he is, that I may send and fetch him. And it was told him, saying, Behold, he is in Dothan. ^14^ Therefore sent he thither horses, and chariots, and a great host: and they came by night, and compassed the city about.^^ ^15^ And when the servant of the man of God was risen early, and gone forth, behold, an host compassed the city both with horses and chariots. And his servant said unto him, Alas, my master! how shall we do?^^ ^16^ And he answered, Fear not: for they that be with us are more than they that be with them. ^17^ And Elisha prayed, and said, LORD, I pray thee, open his eyes, that he may see. And the LORD opened the eyes of the young man; and he saw: and, behold, the mountain was full of horses and chariots of fire round about Elisha. ^18^ And when they came down to him, Elisha prayed unto the LORD, and said, Smite this people, I pray thee, with blindness. And he smote them with blindness according to the word of Elisha.
^[**6:14** great: Heb. heavy]
^[**6:15** the servant: or, the minister]
^19^ And Elisha said unto them, This is not the way, neither is this the city: follow me, and I will bring you to the man whom ye seek. But he led them to Samaria.^^ ^20^ And it came to pass, when they were come into Samaria, that Elisha said, LORD, open the eyes of these men, that they may see. And the LORD opened their eyes, and they saw; and, behold, they were in the midst of Samaria. ^21^ And the king of Israel said unto Elisha, when he saw them, My father, shall I smite them? shall I smite them? ^22^ And he answered, Thou shalt not smite them: wouldest thou smite those whom thou hast taken captive with thy sword and with thy bow? set bread and water before them, that they may eat and drink, and go to their master. ^23^ And he prepared great provision for them: and when they had eaten and drunk, he sent them away, and they went to their master. So the bands of Syria came no more into the land of Israel.
^[**6:19** follow…: Heb. come ye after me]
^24^ And it came to pass after this, that Ben-hadad king of Syria gathered all his host, and went up, and besieged Samaria. ^25^ And there was a great famine in Samaria: and, behold, they besieged it, until an ass’s head was sold for fourscore pieces of silver, and the fourth part of a cab of dove’s dung for five pieces of silver. ^26^ And as the king of Israel was passing by upon the wall, there cried a woman unto him, saying, Help, my lord, O king. ^27^ And he said, If the LORD do not help thee, whence shall I help thee? out of the barnfloor, or out of the winepress?^^ ^28^ And the king said unto her, What aileth thee? And she answered, This woman said unto me, Give thy son, that we may eat him to day, and we will eat my son to morrow. ^29^ So we boiled my son, and did eat him: and I said unto her on the next day, Give thy son, that we may eat him: and she hath hid her son.^^
^[**6:27** If…: or, Let not the LORD save thee]
^[**6:29** next: Heb. other]
^30^ And it came to pass, when the king heard the words of the woman, that he rent his clothes; and he passed by upon the wall, and the people looked, and, behold, he had sackcloth within upon his flesh. ^31^ Then he said, God do so and more also to me, if the head of Elisha the son of Shaphat shall stand on him this day. ^32^ But Elisha sat in his house, and the elders sat with him; and the king sent a man from before him: but ere the messenger came to him, he said to the elders, See ye how this son of a murderer hath sent to take away mine head? look, when the messenger cometh, shut the door, and hold him fast at the door: is not the sound of his master’s feet behind him? ^33^ And while he yet talked with them, behold, the messenger came down unto him: and he said, Behold, this evil is of the LORD; what should I wait for the LORD any longer?
# 7
^1^ Then Elisha said, Hear ye the word of the LORD; Thus saith the LORD, To morrow about this time shall a measure of fine flour be sold for a shekel, and two measures of barley for a shekel, in the gate of Samaria. ^2^ Then a lord on whose hand the king leaned answered the man of God, and said, Behold, if the LORD would make windows in heaven, might this thing be? And he said, Behold, thou shalt see it with thine eyes, but shalt not eat thereof.^^
^[**7:2** a lord…: Heb. a lord which belonged to the king leaning upon his hand]
^3^ And there were four leprous men at the entering in of the gate: and they said one to another, Why sit we here until we die? ^4^ If we say, We will enter into the city, then the famine is in the city, and we shall die there: and if we sit still here, we die also. Now therefore come, and let us fall unto the host of the Syrians: if they save us alive, we shall live; and if they kill us, we shall but die. ^5^ And they rose up in the twilight, to go unto the camp of the Syrians: and when they were come to the uttermost part of the camp of Syria, behold, there was no man there. ^6^ For the Lord had made the host of the Syrians to hear a noise of chariots, and a noise of horses, even the noise of a great host: and they said one to another, Lo, the king of Israel hath hired against us the kings of the Hittites, and the kings of the Egyptians, to come upon us. ^7^ Wherefore they arose and fled in the twilight, and left their tents, and their horses, and their asses, even the camp as it was, and fled for their life. ^8^ And when these lepers came to the uttermost part of the camp, they went into one tent, and did eat and drink, and carried thence silver, and gold, and raiment, and went and hid it; and came again, and entered into another tent, and carried thence also, and went and hid it. ^9^ Then they said one to another, We do not well: this day is a day of good tidings, and we hold our peace: if we tarry till the morning light, some mischief will come upon us: now therefore come, that we may go and tell the king’s household.^^ ^10^ So they came and called unto the porter of the city: and they told them, saying, We came to the camp of the Syrians, and, behold, there was no man there, neither voice of man, but horses tied, and asses tied, and the tents as they were. ^11^ And he called the porters; and they told it to the king’s house within.
^[**7:9** some…: Heb. we shall find punishment]
^12^ And the king arose in the night, and said unto his servants, I will now shew you what the Syrians have done to us. They know that we be hungry; therefore are they gone out of the camp to hide themselves in the field, saying, When they come out of the city, we shall catch them alive, and get into the city. ^13^ And one of his servants answered and said, Let some take, I pray thee, five of the horses that remain, which are left in the city, (behold, they are as all the multitude of Israel that are left in it: behold, I say, they are even as all the multitude of the Israelites that are consumed:) and let us send and see.^^ ^14^ They took therefore two chariot horses; and the king sent after the host of the Syrians, saying, Go and see. ^15^ And they went after them unto Jordan: and, lo, all the way was full of garments and vessels, which the Syrians had cast away in their haste. And the messengers returned, and told the king. ^16^ And the people went out, and spoiled the tents of the Syrians. So a measure of fine flour was sold for a shekel, and two measures of barley for a shekel, according to the word of the LORD.
^[**7:13** in the city: Heb. in it]
^17^ And the king appointed the lord on whose hand he leaned to have the charge of the gate: and the people trode upon him in the gate, and he died, as the man of God had said, who spake when the king came down to him. ^18^ And it came to pass as the man of God had spoken to the king, saying, Two measures of barley for a shekel, and a measure of fine flour for a shekel, shall be to morrow about this time in the gate of Samaria: ^19^ And that lord answered the man of God, and said, Now, behold, if the LORD should make windows in heaven, might such a thing be? And he said, Behold, thou shalt see it with thine eyes, but shalt not eat thereof. ^20^ And so it fell out unto him: for the people trode upon him in the gate, and he died.
# 8
^1^ Then spake Elisha unto the woman, whose son he had restored to life, saying, Arise, and go thou and thine household, and sojourn wheresoever thou canst sojourn: for the LORD hath called for a famine; and it shall also come upon the land seven years. ^2^ And the woman arose, and did after the saying of the man of God: and she went with her household, and sojourned in the land of the Philistines seven years. ^3^ And it came to pass at the seven years’ end, that the woman returned out of the land of the Philistines: and she went forth to cry unto the king for her house and for her land. ^4^ And the king talked with Gehazi the servant of the man of God, saying, Tell me, I pray thee, all the great things that Elisha hath done. ^5^ And it came to pass, as he was telling the king how he had restored a dead body to life, that, behold, the woman, whose son he had restored to life, cried to the king for her house and for her land. And Gehazi said, My lord, O king, this is the woman, and this is her son, whom Elisha restored to life. ^6^ And when the king asked the woman, she told him. So the king appointed unto her a certain officer, saying, Restore all that was hers, and all the fruits of the field since the day that she left the land, even until now.^^
^[**8:6** officer: or, eunuch]
^7^ And Elisha came to Damascus; and Ben-hadad the king of Syria was sick; and it was told him, saying, The man of God is come hither. ^8^ And the king said unto Hazael, Take a present in thine hand, and go, meet the man of God, and enquire of the LORD by him, saying, Shall I recover of this disease? ^9^ So Hazael went to meet him, and took a present with him, even of every good thing of Damascus, forty camels’ burden, and came and stood before him, and said, Thy son Ben-hadad king of Syria hath sent me to thee, saying, Shall I recover of this disease?^^ ^10^ And Elisha said unto him, Go, say unto him, Thou mayest certainly recover: howbeit the LORD hath shewed me that he shall surely die. ^11^ And he settled his countenance stedfastly, until he was ashamed: and the man of God wept.^^ ^12^ And Hazael said, Why weepeth my lord? And he answered, Because I know the evil that thou wilt do unto the children of Israel: their strong holds wilt thou set on fire, and their young men wilt thou slay with the sword, and wilt dash their children, and rip up their women with child. ^13^ And Hazael said, But what, is thy servant a dog, that he should do this great thing? And Elisha answered, The LORD hath shewed me that thou shalt be king over Syria. ^14^ So he departed from Elisha, and came to his master; who said to him, What said Elisha to thee? And he answered, He told me that thou shouldest surely recover. ^15^ And it came to pass on the morrow, that he took a thick cloth, and dipped it in water, and spread it on his face, so that he died: and Hazael reigned in his stead.
^[**8:9** with…: Heb. in his hand]
^[**8:11** stedfastly: Heb. and set it]
^16^ And in the fifth year of Joram the son of Ahab king of Israel, Jehoshaphat being then king of Judah, Jehoram the son of Jehoshaphat king of Judah began to reign.^^ ^17^ Thirty and two years old was he when he began to reign; and he reigned eight years in Jerusalem. ^18^ And he walked in the way of the kings of Israel, as did the house of Ahab: for the daughter of Ahab was his wife: and he did evil in the sight of the LORD. ^19^ Yet the LORD would not destroy Judah for David his servant’s sake, as he promised him to give him alway a light, and to his children.^^
^[**8:16** began…: Heb. reigned]
^[**8:19** light: Heb. candle, or, lamp]
^20^ In his days Edom revolted from under the hand of Judah, and made a king over themselves. ^21^ So Joram went over to Zair, and all the chariots with him: and he rose by night, and smote the Edomites which compassed him about, and the captains of the chariots: and the people fled into their tents. ^22^ Yet Edom revolted from under the hand of Judah unto this day. Then Libnah revolted at the same time. ^23^ And the rest of the acts of Joram, and all that he did, are they not written in the book of the chronicles of the kings of Judah? ^24^ And Joram slept with his fathers, and was buried with his fathers in the city of David: and Ahaziah his son reigned in his stead.^^
^[**8:24** Ahaziah: also called, Azariah, and Jehoahaz]
^25^ In the twelfth year of Joram the son of Ahab king of Israel did Ahaziah the son of Jehoram king of Judah begin to reign. ^26^ Two and twenty years old was Ahaziah when he began to reign; and he reigned one year in Jerusalem. And his mother’s name was Athaliah, the daughter of Omri king of Israel.^^ ^27^ And he walked in the way of the house of Ahab, and did evil in the sight of the LORD, as did the house of Ahab: for he was the son in law of the house of Ahab.
^[**8:26** daughter: or, granddaughter]
^28^ And he went with Joram the son of Ahab to the war against Hazael king of Syria in Ramoth-gilead; and the Syrians wounded Joram. ^29^ And king Joram went back to be healed in Jezreel of the wounds which the Syrians had given him at Ramah, when he fought against Hazael king of Syria. And Ahaziah the son of Jehoram king of Judah went down to see Joram the son of Ahab in Jezreel, because he was sick.^^^^^^
^[**8:29** which…: Heb. wherewith the Syrians had wounded]
^[**8:29** Ramah: called Ramoth]
^[**8:29** sick: Heb. wounded]
# 9
^1^ And Elisha the prophet called one of the children of the prophets, and said unto him, Gird up thy loins, and take this box of oil in thine hand, and go to Ramoth-gilead: ^2^ And when thou comest thither, look out there Jehu the son of Jehoshaphat the son of Nimshi, and go in, and make him arise up from among his brethren, and carry him to an inner chamber;^^ ^3^ Then take the box of oil, and pour it on his head, and say, Thus saith the LORD, I have anointed thee king over Israel. Then open the door, and flee, and tarry not.
^[**9:2** inner…: Heb. chamber in a chamber]
^4^ So the young man, even the young man the prophet, went to Ramoth-gilead. ^5^ And when he came, behold, the captains of the host were sitting; and he said, I have an errand to thee, O captain. And Jehu said, Unto which of all us? And he said, To thee, O captain. ^6^ And he arose, and went into the house; and he poured the oil on his head, and said unto him, Thus saith the LORD God of Israel, I have anointed thee king over the people of the LORD, even over Israel. ^7^ And thou shalt smite the house of Ahab thy master, that I may avenge the blood of my servants the prophets, and the blood of all the servants of the LORD, at the hand of Jezebel. ^8^ For the whole house of Ahab shall perish: and I will cut off from Ahab him that pisseth against the wall, and him that is shut up and left in Israel: ^9^ And I will make the house of Ahab like the house of Jeroboam the son of Nebat, and like the house of Baasha the son of Ahijah: ^10^ And the dogs shall eat Jezebel in the portion of Jezreel, and there shall be none to bury her. And he opened the door, and fled.
^11^ Then Jehu came forth to the servants of his lord: and one said unto him, Is all well? wherefore came this mad fellow to thee? And he said unto them, Ye know the man, and his communication. ^12^ And they said, It is false; tell us now. And he said, Thus and thus spake he to me, saying, Thus saith the LORD, I have anointed thee king over Israel. ^13^ Then they hasted, and took every man his garment, and put it under him on the top of the stairs, and blew with trumpets, saying, Jehu is king.^^ ^14^ So Jehu the son of Jehoshaphat the son of Nimshi conspired against Joram. (Now Joram had kept Ramoth-gilead, he and all Israel, because of Hazael king of Syria. ^15^ But king Joram was returned to be healed in Jezreel of the wounds which the Syrians had given him, when he fought with Hazael king of Syria.) And Jehu said, If it be your minds, then let none go forth nor escape out of the city to go to tell it in Jezreel.^^^^^^
^[**9:13** is king: Heb. reigneth]
^[**9:15** Joram: Heb. Jehoram but not in verse sixteen]
^[**9:15** had given: Heb. smote]
^[**9:15** let none…: Heb. let no escaper go, etc]
^16^ So Jehu rode in a chariot, and went to Jezreel; for Joram lay there. And Ahaziah king of Judah was come down to see Joram. ^17^ And there stood a watchman on the tower in Jezreel, and he spied the company of Jehu as he came, and said, I see a company. And Joram said, Take an horseman, and send to meet them, and let him say, Is it peace? ^18^ So there went one on horseback to meet him, and said, Thus saith the king, Is it peace? And Jehu said, What hast thou to do with peace? turn thee behind me. And the watchman told, saying, The messenger came to them, but he cometh not again. ^19^ Then he sent out a second on horseback, which came to them, and said, Thus saith the king, Is it peace? And Jehu answered, What hast thou to do with peace? turn thee behind me. ^20^ And the watchman told, saying, He came even unto them, and cometh not again: and the driving is like the driving of Jehu the son of Nimshi; for he driveth furiously.^^^^ ^21^ And Joram said, Make ready. And his chariot was made ready. And Joram king of Israel and Ahaziah king of Judah went out, each in his chariot, and they went out against Jehu, and met him in the portion of Naboth the Jezreelite.^^^^ ^22^ And it came to pass, when Joram saw Jehu, that he said, Is it peace, Jehu? And he answered, What peace, so long as the whoredoms of thy mother Jezebel and her witchcrafts are so many? ^23^ And Joram turned his hands, and fled, and said to Ahaziah, There is treachery, O Ahaziah. ^24^ And Jehu drew a bow with his full strength, and smote Jehoram between his arms, and the arrow went out at his heart, and he sunk down in his chariot.^^^^ ^25^ Then said Jehu to Bidkar his captain, Take up, and cast him in the portion of the field of Naboth the Jezreelite: for remember how that, when I and thou rode together after Ahab his father, the LORD laid this burden upon him; ^26^ Surely I have seen yesterday the blood of Naboth, and the blood of his sons, saith the LORD; and I will requite thee in this plat, saith the LORD. Now therefore take and cast him into the plat of ground, according to the word of the LORD.^^^^
^[**9:20** driving: or, marching]
^[**9:20** furiously: Heb. in madness]
^[**9:21** Make ready: Heb. Bind]
^[**9:21** met: Heb. found]
^[**9:24** drew…: Heb. filled his hand with a bow]
^[**9:24** sunk: Heb. bowed]
^[**9:26** blood: Heb. bloods]
^[**9:26** plat: or, portion]
^27^ But when Ahaziah the king of Judah saw this, he fled by the way of the garden house. And Jehu followed after him, and said, Smite him also in the chariot. And they did so at the going up to Gur, which is by Ibleam. And he fled to Megiddo, and died there. ^28^ And his servants carried him in a chariot to Jerusalem, and buried him in his sepulchre with his fathers in the city of David. ^29^ And in the eleventh year of Joram the son of Ahab began Ahaziah to reign over Judah.
^30^ And when Jehu was come to Jezreel, Jezebel heard of it; and she painted her face, and tired her head, and looked out at a window.^^ ^31^ And as Jehu entered in at the gate, she said, Had Zimri peace, who slew his master? ^32^ And he lifted up his face to the window, and said, Who is on my side? who? And there looked out to him two or three eunuchs.^^ ^33^ And he said, Throw her down. So they threw her down: and some of her blood was sprinkled on the wall, and on the horses: and he trode her under foot. ^34^ And when he was come in, he did eat and drink, and said, Go, see now this cursed woman, and bury her: for she is a king’s daughter. ^35^ And they went to bury her: but they found no more of her than the skull, and the feet, and the palms of her hands. ^36^ Wherefore they came again, and told him. And he said, This is the word of the LORD, which he spake by his servant Elijah the Tishbite, saying, In the portion of Jezreel shall dogs eat the flesh of Jezebel:^^ ^37^ And the carcase of Jezebel shall be as dung upon the face of the field in the portion of Jezreel; so that they shall not say, This is Jezebel.
^[**9:30** painted…: Heb. put her eyes in painting]
^[**9:32** eunuchs: or, chamberlains]
^[**9:36** by: Heb. by the hand of]
# 10
^1^ And Ahab had seventy sons in Samaria. And Jehu wrote letters, and sent to Samaria, unto the rulers of Jezreel, to the elders, and to them that brought up Ahab’s children, saying,^^ ^2^ Now as soon as this letter cometh to you, seeing your master’s sons are with you, and there are with you chariots and horses, a fenced city also, and armour; ^3^ Look even out the best and meetest of your master’s sons, and set him on his father’s throne, and fight for your master’s house. ^4^ But they were exceedingly afraid, and said, Behold, two kings stood not before him: how then shall we stand? ^5^ And he that was over the house, and he that was over the city, the elders also, and the bringers up of the children, sent to Jehu, saying, We are thy servants, and will do all that thou shalt bid us; we will not make any king: do thou that which is good in thine eyes. ^6^ Then he wrote a letter the second time to them, saying, If ye be mine, and if ye will hearken unto my voice, take ye the heads of the men your master’s sons, and come to me to Jezreel by to morrow this time. Now the king’s sons, being seventy persons, were with the great men of the city, which brought them up.^^ ^7^ And it came to pass, when the letter came to them, that they took the king’s sons, and slew seventy persons, and put their heads in baskets, and sent him them to Jezreel.
^[**10:1** them…: Heb. nourishers]
^[**10:6** mine: Heb. for me]
^8^ And there came a messenger, and told him, saying, They have brought the heads of the king’s sons. And he said, Lay ye them in two heaps at the entering in of the gate until the morning. ^9^ And it came to pass in the morning, that he went out, and stood, and said to all the people, Ye be righteous: behold, I conspired against my master, and slew him: but who slew all these? ^10^ Know now that there shall fall unto the earth nothing of the word of the LORD, which the LORD spake concerning the house of Ahab: for the LORD hath done that which he spake by his servant Elijah.^^ ^11^ So Jehu slew all that remained of the house of Ahab in Jezreel, and all his great men, and his kinsfolks, and his priests, until he left him none remaining.^^
^[**10:10** by: Heb. by the hand of]
^[**10:11** kinsfolks: or, acquaintance]
^12^ And he arose and departed, and came to Samaria. And as he was at the shearing house in the way,^^ ^13^ Jehu met with the brethren of Ahaziah king of Judah, and said, Who are ye? And they answered, We are the brethren of Ahaziah; and we go down to salute the children of the king and the children of the queen.^^^^ ^14^ And he said, Take them alive. And they took them alive, and slew them at the pit of the shearing house, even two and forty men; neither left he any of them.
^[**10:12** shearing…: Heb. house of shepherds binding sheep]
^[**10:13** met with: Heb. found]
^[**10:13** to salute…: Heb. to the peace of, etc]
^15^ And when he was departed thence, he lighted on Jehonadab the son of Rechab coming to meet him: and he saluted him, and said to him, Is thine heart right, as my heart is with thy heart? And Jehonadab answered, It is. If it be, give me thine hand. And he gave him his hand; and he took him up to him into the chariot.^^^^ ^16^ And he said, Come with me, and see my zeal for the LORD. So they made him ride in his chariot. ^17^ And when he came to Samaria, he slew all that remained unto Ahab in Samaria, till he had destroyed him, according to the saying of the LORD, which he spake to Elijah.
^[**10:15** lighted on: Heb. found]
^[**10:15** saluted: Heb. blessed]
^18^ And Jehu gathered all the people together, and said unto them, Ahab served Baal a little; but Jehu shall serve him much. ^19^ Now therefore call unto me all the prophets of Baal, all his servants, and all his priests; let none be wanting: for I have a great sacrifice to do to Baal; whosoever shall be wanting, he shall not live. But Jehu did it in subtilty, to the intent that he might destroy the worshippers of Baal. ^20^ And Jehu said, Proclaim a solemn assembly for Baal. And they proclaimed it.^^ ^21^ And Jehu sent through all Israel: and all the worshippers of Baal came, so that there was not a man left that came not. And they came into the house of Baal; and the house of Baal was full from one end to another.^^ ^22^ And he said unto him that was over the vestry, Bring forth vestments for all the worshippers of Baal. And he brought them forth vestments. ^23^ And Jehu went, and Jehonadab the son of Rechab, into the house of Baal, and said unto the worshippers of Baal, Search, and look that there be here with you none of the servants of the LORD, but the worshippers of Baal only. ^24^ And when they went in to offer sacrifices and burnt offerings, Jehu appointed fourscore men without, and said, If any of the men whom I have brought into your hands escape, he that letteth him go, his life shall be for the life of him. ^25^ And it came to pass, as soon as he had made an end of offering the burnt offering, that Jehu said to the guard and to the captains, Go in, and slay them; let none come forth. And they smote them with the edge of the sword; and the guard and the captains cast them out, and went to the city of the house of Baal.^^ ^26^ And they brought forth the images out of the house of Baal, and burned them.^^ ^27^ And they brake down the image of Baal, and brake down the house of Baal, and made it a draught house unto this day. ^28^ Thus Jehu destroyed Baal out of Israel.
^[**10:20** Proclaim: Heb. Sanctify]
^[**10:21** full…: or, so full that they stood mouth to mouth]
^[**10:25** the edge: Heb. the mouth]
^[**10:26** images: Heb. statues]
^29^ Howbeit from the sins of Jeroboam the son of Nebat, who made Israel to sin, Jehu departed not from after them, to wit, the golden calves that were in Beth-el, and that were in Dan. ^30^ And the LORD said unto Jehu, Because thou hast done well in executing that which is right in mine eyes, and hast done unto the house of Ahab according to all that was in mine heart, thy children of the fourth generation shall sit on the throne of Israel. ^31^ But Jehu took no heed to walk in the law of the LORD God of Israel with all his heart: for he departed not from the sins of Jeroboam, which made Israel to sin.^^
^[**10:31** took…: Heb. observed not]
^32^ In those days the LORD began to cut Israel short: and Hazael smote them in all the coasts of Israel;^^ ^33^ From Jordan eastward, all the land of Gilead, the Gadites, and the Reubenites, and the Manassites, from Aroer, which is by the river Arnon, even Gilead and Bashan.^^^^ ^34^ Now the rest of the acts of Jehu, and all that he did, and all his might, are they not written in the book of the chronicles of the kings of Israel? ^35^ And Jehu slept with his fathers: and they buried him in Samaria. And Jehoahaz his son reigned in his stead. ^36^ And the time that Jehu reigned over Israel in Samaria was twenty and eight years.^^
^[**10:32** to cut: Heb. to cut off the ends]
^[**10:33** eastward: Heb. toward the rising of the sun]
^[**10:33** even…: or, even to Gilead and Bashan]
^[**10:36** the time: Heb. the days were]
# 11
^1^ And when Athaliah the mother of Ahaziah saw that her son was dead, she arose and destroyed all the seed royal.^^ ^2^ But Jehosheba, the daughter of king Joram, sister of Ahaziah, took Joash the son of Ahaziah, and stole him from among the king’s sons which were slain; and they hid him, even him and his nurse, in the bedchamber from Athaliah, so that he was not slain.^^^^ ^3^ And he was with her hid in the house of the LORD six years. And Athaliah did reign over the land.
^[**11:1** seed…: Heb. seed of the kingdom]
^[**11:2** Jehosheba: also called, Jehoshabeath]
^[**11:2** Joash: also called, Jehoash]
^4^ And the seventh year Jehoiada sent and fetched the rulers over hundreds, with the captains and the guard, and brought them to him into the house of the LORD, and made a covenant with them, and took an oath of them in the house of the LORD, and shewed them the king’s son. ^5^ And he commanded them, saying, This is the thing that ye shall do; A third part of you that enter in on the sabbath shall even be keepers of the watch of the king’s house; ^6^ And a third part shall be at the gate of Sur; and a third part at the gate behind the guard: so shall ye keep the watch of the house, that it be not broken down.^^ ^7^ And two parts of all you that go forth on the sabbath, even they shall keep the watch of the house of the LORD about the king.^^ ^8^ And ye shall compass the king round about, every man with his weapons in his hand: and he that cometh within the ranges, let him be slain: and be ye with the king as he goeth out and as he cometh in. ^9^ And the captains over the hundreds did according to all things that Jehoiada the priest commanded: and they took every man his men that were to come in on the sabbath, with them that should go out on the sabbath, and came to Jehoiada the priest. ^10^ And to the captains over hundreds did the priest give king David’s spears and shields, that were in the temple of the LORD. ^11^ And the guard stood, every man with his weapons in his hand, round about the king, from the right corner of the temple to the left corner of the temple, along by the altar and the temple.^^ ^12^ And he brought forth the king’s son, and put the crown upon him, and gave him the testimony; and they made him king, and anointed him; and they clapped their hands, and said, God save the king.^^
^[**11:6** that…: or, from breaking up]
^[**11:7** parts: or, companies: Heb. hands]
^[**11:11** corner: Heb. shoulder]
^[**11:12** God…: Heb. Let the king live]
^13^ And when Athaliah heard the noise of the guard and of the people, she came to the people into the temple of the LORD. ^14^ And when she looked, behold, the king stood by a pillar, as the manner was, and the princes and the trumpeters by the king, and all the people of the land rejoiced, and blew with trumpets: and Athaliah rent her clothes, and cried, Treason, Treason. ^15^ But Jehoiada the priest commanded the captains of the hundreds, the officers of the host, and said unto them, Have her forth without the ranges: and him that followeth her kill with the sword. For the priest had said, Let her not be slain in the house of the LORD. ^16^ And they laid hands on her; and she went by the way by the which the horses came into the king’s house: and there was she slain.
^17^ And Jehoiada made a covenant between the LORD and the king and the people, that they should be the LORD’s people; between the king also and the people. ^18^ And all the people of the land went into the house of Baal, and brake it down; his altars and his images brake they in pieces thoroughly, and slew Mattan the priest of Baal before the altars. And the priest appointed officers over the house of the LORD.^^ ^19^ And he took the rulers over hundreds, and the captains, and the guard, and all the people of the land; and they brought down the king from the house of the LORD, and came by the way of the gate of the guard to the king’s house. And he sat on the throne of the kings. ^20^ And all the people of the land rejoiced, and the city was in quiet: and they slew Athaliah with the sword beside the king’s house. ^21^ Seven years old was Jehoash when he began to reign.
^[**11:18** officers: Heb. offices]
# 12
^1^ In the seventh year of Jehu Jehoash began to reign; and forty years reigned he in Jerusalem. And his mother’s name was Zibiah of Beer-sheba. ^2^ And Jehoash did that which was right in the sight of the LORD all his days wherein Jehoiada the priest instructed him. ^3^ But the high places were not taken away: the people still sacrificed and burnt incense in the high places.
^4^ And Jehoash said to the priests, All the money of the dedicated things that is brought into the house of the LORD, even the money of every one that passeth the account, the money that every man is set at, and all the money that cometh into any man’s heart to bring into the house of the LORD,^^^^^^ ^5^ Let the priests take it to them, every man of his acquaintance: and let them repair the breaches of the house, wheresoever any breach shall be found. ^6^ But it was so, that in the three and twentieth year of king Jehoash the priests had not repaired the breaches of the house.^^ ^7^ Then king Jehoash called for Jehoiada the priest, and the other priests, and said unto them, Why repair ye not the breaches of the house? now therefore receive no more money of your acquaintance, but deliver it for the breaches of the house. ^8^ And the priests consented to receive no more money of the people, neither to repair the breaches of the house. ^9^ But Jehoiada the priest took a chest, and bored a hole in the lid of it, and set it beside the altar, on the right side as one cometh into the house of the LORD: and the priests that kept the door put therein all the money that was brought into the house of the LORD.^^ ^10^ And it was so, when they saw that there was much money in the chest, that the king’s scribe and the high priest came up, and they put up in bags, and told the money that was found in the house of the LORD.^^^^ ^11^ And they gave the money, being told, into the hands of them that did the work, that had the oversight of the house of the LORD: and they laid it out to the carpenters and builders, that wrought upon the house of the LORD,^^ ^12^ And to masons, and hewers of stone, and to buy timber and hewed stone to repair the breaches of the house of the LORD, and for all that was laid out for the house to repair it.^^ ^13^ Howbeit there were not made for the house of the LORD bowls of silver, snuffers, basons, trumpets, any vessels of gold, or vessels of silver, of the money that was brought into the house of the LORD: ^14^ But they gave that to the workmen, and repaired therewith the house of the LORD. ^15^ Moreover they reckoned not with the men, into whose hand they delivered the money to be bestowed on workmen: for they dealt faithfully. ^16^ The trespass money and sin money was not brought into the house of the LORD: it was the priests’.
^[**12:4** dedicated things: or, holy things: Heb. holinesses]
^[**12:4** that every…: Heb. of the souls of his estimation]
^[**12:4** cometh…: Heb. ascendeth upon the heart of a man]
^[**12:6** three…: Heb. twentieth year and third year]
^[**12:9** door: Heb. threshold]
^[**12:10** scribe: or, secretary]
^[**12:10** put…: Heb. bound up]
^[**12:11** laid…: Heb. brought it forth]
^[**12:12** was…: Heb. went forth]
^17^ Then Hazael king of Syria went up, and fought against Gath, and took it: and Hazael set his face to go up to Jerusalem. ^18^ And Jehoash king of Judah took all the hallowed things that Jehoshaphat, and Jehoram, and Ahaziah, his fathers, kings of Judah, had dedicated, and his own hallowed things, and all the gold that was found in the treasures of the house of the LORD, and in the king’s house, and sent it to Hazael king of Syria: and he went away from Jerusalem.^^
^[**12:18** went…: Heb. went up]
^19^ And the rest of the acts of Joash, and all that he did, are they not written in the book of the chronicles of the kings of Judah? ^20^ And his servants arose, and made a conspiracy, and slew Joash in the house of Millo, which goeth down to Silla.^^ ^21^ For Jozachar the son of Shimeath, and Jehozabad the son of Shomer, his servants, smote him, and he died; and they buried him with his fathers in the city of David: and Amaziah his son reigned in his stead.
^[**12:20** the house…: or, Bethmillo]
# 13
^1^ In the three and twentieth year of Joash the son of Ahaziah king of Judah Jehoahaz the son of Jehu began to reign over Israel in Samaria, and reigned seventeen years.^^ ^2^ And he did that which was evil in the sight of the LORD, and followed the sins of Jeroboam the son of Nebat, which made Israel to sin; he departed not therefrom.^^
^[**13:1** three…: Heb. twentieth year and third year]
^[**13:2** followed: Heb. walked after]
^3^ And the anger of the LORD was kindled against Israel, and he delivered them into the hand of Hazael king of Syria, and into the hand of Ben-hadad the son of Hazael, all their days. ^4^ And Jehoahaz besought the LORD, and the LORD hearkened unto him: for he saw the oppression of Israel, because the king of Syria oppressed them. ^5^ (And the LORD gave Israel a saviour, so that they went out from under the hand of the Syrians: and the children of Israel dwelt in their tents, as beforetime.^^ ^6^ Nevertheless they departed not from the sins of the house of Jeroboam, who made Israel sin, but walked therein: and there remained the grove also in Samaria.)^^^^ ^7^ Neither did he leave of the people to Jehoahaz but fifty horsemen, and ten chariots, and ten thousand footmen; for the king of Syria had destroyed them, and had made them like the dust by threshing.
^[**13:5** as beforetime: Heb. as yesterday, and third day]
^[**13:6** walked: Heb. he walked]
^[**13:6** remained: Heb. stood]
^8^ Now the rest of the acts of Jehoahaz, and all that he did, and his might, are they not written in the book of the chronicles of the kings of Israel? ^9^ And Jehoahaz slept with his fathers; and they buried him in Samaria: and Joash his son reigned in his stead.^^
^[**13:9** Joash: also called, Jehoash]
^10^ In the thirty and seventh year of Joash king of Judah began Jehoash the son of Jehoahaz to reign over Israel in Samaria, and reigned sixteen years. ^11^ And he did that which was evil in the sight of the LORD; he departed not from all the sins of Jeroboam the son of Nebat, who made Israel sin: but he walked therein. ^12^ And the rest of the acts of Joash, and all that he did, and his might wherewith he fought against Amaziah king of Judah, are they not written in the book of the chronicles of the kings of Israel? ^13^ And Joash slept with his fathers; and Jeroboam sat upon his throne: and Joash was buried in Samaria with the kings of Israel.
^14^ Now Elisha was fallen sick of his sickness whereof he died. And Joash the king of Israel came down unto him, and wept over his face, and said, O my father, my father, the chariot of Israel, and the horsemen thereof. ^15^ And Elisha said unto him, Take bow and arrows. And he took unto him bow and arrows. ^16^ And he said to the king of Israel, Put thine hand upon the bow. And he put his hand upon it: and Elisha put his hands upon the king’s hands.^^ ^17^ And he said, Open the window eastward. And he opened it. Then Elisha said, Shoot. And he shot. And he said, The arrow of the LORD’s deliverance, and the arrow of deliverance from Syria: for thou shalt smite the Syrians in Aphek, till thou have consumed them. ^18^ And he said, Take the arrows. And he took them. And he said unto the king of Israel, Smite upon the ground. And he smote thrice, and stayed. ^19^ And the man of God was wroth with him, and said, Thou shouldest have smitten five or six times; then hadst thou smitten Syria till thou hadst consumed it: whereas now thou shalt smite Syria but thrice.
^[**13:16** Put thine…: Heb. Make thine hand to ride]
^20^ And Elisha died, and they buried him. And the bands of the Moabites invaded the land at the coming in of the year. ^21^ And it came to pass, as they were burying a man, that, behold, they spied a band of men; and they cast the man into the sepulchre of Elisha: and when the man was let down, and touched the bones of Elisha, he revived, and stood up on his feet.^^
^[**13:21** was…: Heb. went down]
^22^ But Hazael king of Syria oppressed Israel all the days of Jehoahaz. ^23^ And the LORD was gracious unto them, and had compassion on them, and had respect unto them, because of his covenant with Abraham, Isaac, and Jacob, and would not destroy them, neither cast he them from his presence as yet.^^ ^24^ So Hazael king of Syria died; and Ben-hadad his son reigned in his stead. ^25^ And Jehoash the son of Jehoahaz took again out of the hand of Ben-hadad the son of Hazael the cities, which he had taken out of the hand of Jehoahaz his father by war. Three times did Joash beat him, and recovered the cities of Israel.^^
^[**13:23** presence: Heb. face]
^[**13:25** took…: Heb. returned and took]
# 14
^1^ In the second year of Joash son of Jehoahaz king of Israel reigned Amaziah the son of Joash king of Judah. ^2^ He was twenty and five years old when he began to reign, and reigned twenty and nine years in Jerusalem. And his mother’s name was Jehoaddan of Jerusalem. ^3^ And he did that which was right in the sight of the LORD, yet not like David his father: he did according to all things as Joash his father did. ^4^ Howbeit the high places were not taken away: as yet the people did sacrifice and burnt incense on the high places.
^5^ And it came to pass, as soon as the kingdom was confirmed in his hand, that he slew his servants which had slain the king his father. ^6^ But the children of the murderers he slew not: according unto that which is written in the book of the law of Moses, wherein the LORD commanded, saying, The fathers shall not be put to death for the children, nor the children be put to death for the fathers; but every man shall be put to death for his own sin. ^7^ He slew of Edom in the valley of salt ten thousand, and took Selah by war, and called the name of it Joktheel unto this day.^^
^[**14:7** Selah: or, the rock]
^8^ Then Amaziah sent messengers to Jehoash, the son of Jehoahaz son of Jehu, king of Israel, saying, Come, let us look one another in the face. ^9^ And Jehoash the king of Israel sent to Amaziah king of Judah, saying, The thistle that was in Lebanon sent to the cedar that was in Lebanon, saying, Give thy daughter to my son to wife: and there passed by a wild beast that was in Lebanon, and trode down the thistle. ^10^ Thou hast indeed smitten Edom, and thine heart hath lifted thee up: glory of this, and tarry at home: for why shouldest thou meddle to thy hurt, that thou shouldest fall, even thou, and Judah with thee?^^ ^11^ But Amaziah would not hear. Therefore Jehoash king of Israel went up; and he and Amaziah king of Judah looked one another in the face at Beth-shemesh, which belongeth to Judah. ^12^ And Judah was put to the worse before Israel; and they fled every man to their tents.^^ ^13^ And Jehoash king of Israel took Amaziah king of Judah, the son of Jehoash the son of Ahaziah, at Beth-shemesh, and came to Jerusalem, and brake down the wall of Jerusalem from the gate of Ephraim unto the corner gate, four hundred cubits. ^14^ And he took all the gold and silver, and all the vessels that were found in the house of the LORD, and in the treasures of the king’s house, and hostages, and returned to Samaria.
^[**14:10** at home: Heb. at thy house]
^[**14:12** put…: Heb. smitten]
^15^ Now the rest of the acts of Jehoash which he did, and his might, and how he fought with Amaziah king of Judah, are they not written in the book of the chronicles of the kings of Israel? ^16^ And Jehoash slept with his fathers, and was buried in Samaria with the kings of Israel; and Jeroboam his son reigned in his stead.
^17^ And Amaziah the son of Joash king of Judah lived after the death of Jehoash son of Jehoahaz king of Israel fifteen years. ^18^ And the rest of the acts of Amaziah, are they not written in the book of the chronicles of the kings of Judah? ^19^ Now they made a conspiracy against him in Jerusalem: and he fled to Lachish; but they sent after him to Lachish, and slew him there. ^20^ And they brought him on horses: and he was buried at Jerusalem with his fathers in the city of David.
^21^ And all the people of Judah took Azariah, which was sixteen years old, and made him king instead of his father Amaziah.^^ ^22^ He built Elath, and restored it to Judah, after that the king slept with his fathers.
^[**14:21** Azariah: also called, Uzziah]
^23^ In the fifteenth year of Amaziah the son of Joash king of Judah Jeroboam the son of Joash king of Israel began to reign in Samaria, and reigned forty and one years. ^24^ And he did that which was evil in the sight of the LORD: he departed not from all the sins of Jeroboam the son of Nebat, who made Israel to sin. ^25^ He restored the coast of Israel from the entering of Hamath unto the sea of the plain, according to the word of the LORD God of Israel, which he spake by the hand of his servant Jonah, the son of Amittai, the prophet, which was of Gath-hepher. ^26^ For the LORD saw the affliction of Israel, that it was very bitter: for there was not any shut up, nor any left, nor any helper for Israel. ^27^ And the LORD said not that he would blot out the name of Israel from under heaven: but he saved them by the hand of Jeroboam the son of Joash.
^28^ Now the rest of the acts of Jeroboam, and all that he did, and his might, how he warred, and how he recovered Damascus, and Hamath, which belonged to Judah, for Israel, are they not written in the book of the chronicles of the kings of Israel? ^29^ And Jeroboam slept with his fathers, even with the kings of Israel; and Zachariah his son reigned in his stead.
# 15
^1^ In the twenty and seventh year of Jeroboam king of Israel began Azariah son of Amaziah king of Judah to reign.^^ ^2^ Sixteen years old was he when he began to reign, and he reigned two and fifty years in Jerusalem. And his mother’s name was Jecholiah of Jerusalem. ^3^ And he did that which was right in the sight of the LORD, according to all that his father Amaziah had done; ^4^ Save that the high places were not removed: the people sacrificed and burnt incense still on the high places.
^[**15:1** Azariah: also called, Uzziah]
^5^ And the LORD smote the king, so that he was a leper unto the day of his death, and dwelt in a several house. And Jotham the king’s son was over the house, judging the people of the land. ^6^ And the rest of the acts of Azariah, and all that he did, are they not written in the book of the chronicles of the kings of Judah? ^7^ So Azariah slept with his fathers; and they buried him with his fathers in the city of David: and Jotham his son reigned in his stead.
^8^ In the thirty and eighth year of Azariah king of Judah did Zachariah the son of Jeroboam reign over Israel in Samaria six months. ^9^ And he did that which was evil in the sight of the LORD, as his fathers had done: he departed not from the sins of Jeroboam the son of Nebat, who made Israel to sin. ^10^ And Shallum the son of Jabesh conspired against him, and smote him before the people, and slew him, and reigned in his stead. ^11^ And the rest of the acts of Zachariah, behold, they are written in the book of the chronicles of the kings of Israel. ^12^ This was the word of the LORD which he spake unto Jehu, saying, Thy sons shall sit on the throne of Israel unto the fourth generation. And so it came to pass.
^13^ Shallum the son of Jabesh began to reign in the nine and thirtieth year of Uzziah king of Judah; and he reigned a full month in Samaria.^^^^ ^14^ For Menahem the son of Gadi went up from Tirzah, and came to Samaria, and smote Shallum the son of Jabesh in Samaria, and slew him, and reigned in his stead. ^15^ And the rest of the acts of Shallum, and his conspiracy which he made, behold, they are written in the book of the chronicles of the kings of Israel.
^[**15:13** Uzziah: Gr. Ozias]
^[**15:13** a full…: Heb. a month of days]
^16^ Then Menahem smote Tiphsah, and all that were therein, and the coasts thereof from Tirzah: because they opened not to him, therefore he smote it; and all the women therein that were with child he ripped up. ^17^ In the nine and thirtieth year of Azariah king of Judah began Menahem the son of Gadi to reign over Israel, and reigned ten years in Samaria. ^18^ And he did that which was evil in the sight of the LORD: he departed not all his days from the sins of Jeroboam the son of Nebat, who made Israel to sin. ^19^ And Pul the king of Assyria came against the land: and Menahem gave Pul a thousand talents of silver, that his hand might be with him to confirm the kingdom in his hand. ^20^ And Menahem exacted the money of Israel, even of all the mighty men of wealth, of each man fifty shekels of silver, to give to the king of Assyria. So the king of Assyria turned back, and stayed not there in the land.^^
^[**15:20** exacted: Heb. caused to come forth]
^21^ And the rest of the acts of Menahem, and all that he did, are they not written in the book of the chronicles of the kings of Israel? ^22^ And Menahem slept with his fathers; and Pekahiah his son reigned in his stead.
^23^ In the fiftieth year of Azariah king of Judah Pekahiah the son of Menahem began to reign over Israel in Samaria, and reigned two years. ^24^ And he did that which was evil in the sight of the LORD: he departed not from the sins of Jeroboam the son of Nebat, who made Israel to sin. ^25^ But Pekah the son of Remaliah, a captain of his, conspired against him, and smote him in Samaria, in the palace of the king’s house, with Argob and Arieh, and with him fifty men of the Gileadites: and he killed him, and reigned in his room. ^26^ And the rest of the acts of Pekahiah, and all that he did, behold, they are written in the book of the chronicles of the kings of Israel.
^27^ In the two and fiftieth year of Azariah king of Judah Pekah the son of Remaliah began to reign over Israel in Samaria, and reigned twenty years. ^28^ And he did that which was evil in the sight of the LORD: he departed not from the sins of Jeroboam the son of Nebat, who made Israel to sin. ^29^ In the days of Pekah king of Israel came Tiglath-pileser king of Assyria, and took Ijon, and Abel-beth-maachah, and Janoah, and Kedesh, and Hazor, and Gilead, and Galilee, all the land of Naphtali, and carried them captive to Assyria. ^30^ And Hoshea the son of Elah made a conspiracy against Pekah the son of Remaliah, and smote him, and slew him, and reigned in his stead, in the twentieth year of Jotham the son of Uzziah. ^31^ And the rest of the acts of Pekah, and all that he did, behold, they are written in the book of the chronicles of the kings of Israel.
^32^ In the second year of Pekah the son of Remaliah king of Israel began Jotham the son of Uzziah king of Judah to reign. ^33^ Five and twenty years old was he when he began to reign, and he reigned sixteen years in Jerusalem. And his mother’s name was Jerusha, the daughter of Zadok. ^34^ And he did that which was right in the sight of the LORD: he did according to all that his father Uzziah had done.
^35^ Howbeit the high places were not removed: the people sacrificed and burned incense still in the high places. He built the higher gate of the house of the LORD.
^36^ Now the rest of the acts of Jotham, and all that he did, are they not written in the book of the chronicles of the kings of Judah? ^37^ In those days the LORD began to send against Judah Rezin the king of Syria, and Pekah the son of Remaliah. ^38^ And Jotham slept with his fathers, and was buried with his fathers in the city of David his father: and Ahaz his son reigned in his stead.
# 16
^1^ In the seventeenth year of Pekah the son of Remaliah Ahaz the son of Jotham king of Judah began to reign. ^2^ Twenty years old was Ahaz when he began to reign, and reigned sixteen years in Jerusalem, and did not that which was right in the sight of the LORD his God, like David his father. ^3^ But he walked in the way of the kings of Israel, yea, and made his son to pass through the fire, according to the abominations of the heathen, whom the LORD cast out from before the children of Israel. ^4^ And he sacrificed and burnt incense in the high places, and on the hills, and under every green tree.
^5^ Then Rezin king of Syria and Pekah son of Remaliah king of Israel came up to Jerusalem to war: and they besieged Ahaz, but could not overcome him. ^6^ At that time Rezin king of Syria recovered Elath to Syria, and drave the Jews from Elath: and the Syrians came to Elath, and dwelt there unto this day.^^ ^7^ So Ahaz sent messengers to Tiglath-pileser king of Assyria, saying, I am thy servant and thy son: come up, and save me out of the hand of the king of Syria, and out of the hand of the king of Israel, which rise up against me. ^8^ And Ahaz took the silver and gold that was found in the house of the LORD, and in the treasures of the king’s house, and sent it for a present to the king of Assyria. ^9^ And the king of Assyria hearkened unto him: for the king of Assyria went up against Damascus, and took it, and carried the people of it captive to Kir, and slew Rezin.^^
^[**16:6** from Elath: Heb. from Eloth]
^[**16:9** Damascus: Heb. Dammesek]
^10^ And king Ahaz went to Damascus to meet Tiglath-pileser king of Assyria, and saw an altar that was at Damascus: and king Ahaz sent to Urijah the priest the fashion of the altar, and the pattern of it, according to all the workmanship thereof.^^ ^11^ And Urijah the priest built an altar according to all that king Ahaz had sent from Damascus: so Urijah the priest made it against king Ahaz came from Damascus. ^12^ And when the king was come from Damascus, the king saw the altar: and the king approached to the altar, and offered thereon. ^13^ And he burnt his burnt offering and his meat offering, and poured his drink offering, and sprinkled the blood of his peace offerings, upon the altar.^^ ^14^ And he brought also the brasen altar, which was before the LORD, from the forefront of the house, from between the altar and the house of the LORD, and put it on the north side of the altar. ^15^ And king Ahaz commanded Urijah the priest, saying, Upon the great altar burn the morning burnt offering, and the evening meat offering, and the king’s burnt sacrifice, and his meat offering, with the burnt offering of all the people of the land, and their meat offering, and their drink offerings; and sprinkle upon it all the blood of the burnt offering, and all the blood of the sacrifice: and the brasen altar shall be for me to enquire by. ^16^ Thus did Urijah the priest, according to all that king Ahaz commanded.
^[**16:10** Damascus: Heb. Dammesek]
^[**16:13** his peace offerings: Heb. the peace offerings which were his]
^17^ And king Ahaz cut off the borders of the bases, and removed the laver from off them; and took down the sea from off the brasen oxen that were under it, and put it upon a pavement of stones. ^18^ And the covert for the sabbath that they had built in the house, and the king’s entry without, turned he from the house of the LORD for the king of Assyria.
^19^ Now the rest of the acts of Ahaz which he did, are they not written in the book of the chronicles of the kings of Judah? ^20^ And Ahaz slept with his fathers, and was buried with his fathers in the city of David: and Hezekiah his son reigned in his stead.
# 17
^1^ In the twelfth year of Ahaz king of Judah began Hoshea the son of Elah to reign in Samaria over Israel nine years. ^2^ And he did that which was evil in the sight of the LORD, but not as the kings of Israel that were before him.
^3^ Against him came up Shalmaneser king of Assyria; and Hoshea became his servant, and gave him presents.^^^^ ^4^ And the king of Assyria found conspiracy in Hoshea: for he had sent messengers to So king of Egypt, and brought no present to the king of Assyria, as he had done year by year: therefore the king of Assyria shut him up, and bound him in prison.^^
^[**17:3** gave: Heb. rendered]
^[**17:3** presents: or, tribute]
^[**17:4** present: or, tribute]
^5^ Then the king of Assyria came up throughout all the land, and went up to Samaria, and besieged it three years.
^6^ In the ninth year of Hoshea the king of Assyria took Samaria, and carried Israel away into Assyria, and placed them in Halah and in Habor by the river of Gozan, and in the cities of the Medes.
^7^ For so it was, that the children of Israel had sinned against the LORD their God, which had brought them up out of the land of Egypt, from under the hand of Pharaoh king of Egypt, and had feared other gods, ^8^ And walked in the statutes of the heathen, whom the LORD cast out from before the children of Israel, and of the kings of Israel, which they had made. ^9^ And the children of Israel did secretly those things that were not right against the LORD their God, and they built them high places in all their cities, from the tower of the watchmen to the fenced city. ^10^ And they set them up images and groves in every high hill, and under every green tree:^^ ^11^ And there they burnt incense in all the high places, as did the heathen whom the LORD carried away before them; and wrought wicked things to provoke the LORD to anger: ^12^ For they served idols, whereof the LORD had said unto them, Ye shall not do this thing. ^13^ Yet the LORD testified against Israel, and against Judah, by all the prophets, and by all the seers, saying, Turn ye from your evil ways, and keep my commandments and my statutes, according to all the law which I commanded your fathers, and which I sent to you by my servants the prophets.^^ ^14^ Notwithstanding they would not hear, but hardened their necks, like to the neck of their fathers, that did not believe in the LORD their God. ^15^ And they rejected his statutes, and his covenant that he made with their fathers, and his testimonies which he testified against them; and they followed vanity, and became vain, and went after the heathen that were round about them, concerning whom the LORD had charged them, that they should not do like them. ^16^ And they left all the commandments of the LORD their God, and made them molten images, even two calves, and made a grove, and worshipped all the host of heaven, and served Baal. ^17^ And they caused their sons and their daughters to pass through the fire, and used divination and enchantments, and sold themselves to do evil in the sight of the LORD, to provoke him to anger. ^18^ Therefore the LORD was very angry with Israel, and removed them out of his sight: there was none left but the tribe of Judah only. ^19^ Also Judah kept not the commandments of the LORD their God, but walked in the statutes of Israel which they made. ^20^ And the LORD rejected all the seed of Israel, and afflicted them, and delivered them into the hand of spoilers, until he had cast them out of his sight. ^21^ For he rent Israel from the house of David; and they made Jeroboam the son of Nebat king: and Jeroboam drave Israel from following the LORD, and made them sin a great sin. ^22^ For the children of Israel walked in all the sins of Jeroboam which he did; they departed not from them; ^23^ Until the LORD removed Israel out of his sight, as he had said by all his servants the prophets. So was Israel carried away out of their own land to Assyria unto this day.
^[**17:10** images: Heb. statues]
^[**17:13** by: Heb. by the hand of]
^24^ And the king of Assyria brought men from Babylon, and from Cuthah, and from Ava, and from Hamath, and from Sepharvaim, and placed them in the cities of Samaria instead of the children of Israel: and they possessed Samaria, and dwelt in the cities thereof. ^25^ And so it was at the beginning of their dwelling there, that they feared not the LORD: therefore the LORD sent lions among them, which slew some of them. ^26^ Wherefore they spake to the king of Assyria, saying, The nations which thou hast removed, and placed in the cities of Samaria, know not the manner of the God of the land: therefore he hath sent lions among them, and, behold, they slay them, because they know not the manner of the God of the land. ^27^ Then the king of Assyria commanded, saying, Carry thither one of the priests whom ye brought from thence; and let them go and dwell there, and let him teach them the manner of the God of the land. ^28^ Then one of the priests whom they had carried away from Samaria came and dwelt in Beth-el, and taught them how they should fear the LORD. ^29^ Howbeit every nation made gods of their own, and put them in the houses of the high places which the Samaritans had made, every nation in their cities wherein they dwelt. ^30^ And the men of Babylon made Succoth-benoth, and the men of Cuth made Nergal, and the men of Hamath made Ashima, ^31^ And the Avites made Nibhaz and Tartak, and the Sepharvites burnt their children in fire to Adrammelech and Anammelech, the gods of Sepharvaim. ^32^ So they feared the LORD, and made unto themselves of the lowest of them priests of the high places, which sacrificed for them in the houses of the high places. ^33^ They feared the LORD, and served their own gods, after the manner of the nations whom they carried away from thence.^^ ^34^ Unto this day they do after the former manners: they fear not the LORD, neither do they after their statutes, or after their ordinances, or after the law and commandment which the LORD commanded the children of Jacob, whom he named Israel; ^35^ With whom the LORD had made a covenant, and charged them, saying, Ye shall not fear other gods, nor bow yourselves to them, nor serve them, nor sacrifice to them: ^36^ But the LORD, who brought you up out of the land of Egypt with great power and a stretched out arm, him shall ye fear, and him shall ye worship, and to him shall ye do sacrifice. ^37^ And the statutes, and the ordinances, and the law, and the commandment, which he wrote for you, ye shall observe to do for evermore; and ye shall not fear other gods. ^38^ And the covenant that I have made with you ye shall not forget; neither shall ye fear other gods. ^39^ But the LORD your God ye shall fear; and he shall deliver you out of the hand of all your enemies. ^40^ Howbeit they did not hearken, but they did after their former manner. ^41^ So these nations feared the LORD, and served their graven images, both their children, and their children’s children: as did their fathers, so do they unto this day.
^[**17:33** whom…: or, who carried them away from thence]
# 18
^1^ Now it came to pass in the third year of Hoshea son of Elah king of Israel, that Hezekiah the son of Ahaz king of Judah began to reign.^^ ^2^ Twenty and five years old was he when he began to reign; and he reigned twenty and nine years in Jerusalem. His mother’s name also was Abi, the daughter of Zachariah.^^ ^3^ And he did that which was right in the sight of the LORD, according to all that David his father did.
^[**18:1** Hezekiah: he is called Ezekias]
^[**18:2** Abi: also called, Abijah]
^4^ He removed the high places, and brake the images, and cut down the groves, and brake in pieces the brasen serpent that Moses had made: for unto those days the children of Israel did burn incense to it: and he called it Nehushtan.^^^^ ^5^ He trusted in the LORD God of Israel; so that after him was none like him among all the kings of Judah, nor any that were before him. ^6^ For he clave to the LORD, and departed not from following him, but kept his commandments, which the LORD commanded Moses.^^ ^7^ And the LORD was with him; and he prospered whithersoever he went forth: and he rebelled against the king of Assyria, and served him not. ^8^ He smote the Philistines, even unto Gaza, and the borders thereof, from the tower of the watchmen to the fenced city.^^
^[**18:4** images: Heb. statues]
^[**18:4** Nehushtan: that is, A piece of brass]
^[**18:6** from…: Heb. from after him]
^[**18:8** Gaza: Heb. Azzah]
^9^ And it came to pass in the fourth year of king Hezekiah, which was the seventh year of Hoshea son of Elah king of Israel, that Shalmaneser king of Assyria came up against Samaria, and besieged it. ^10^ And at the end of three years they took it: even in the sixth year of Hezekiah, that is the ninth year of Hoshea king of Israel, Samaria was taken. ^11^ And the king of Assyria did carry away Israel unto Assyria, and put them in Halah and in Habor by the river of Gozan, and in the cities of the Medes: ^12^ Because they obeyed not the voice of the LORD their God, but transgressed his covenant, and all that Moses the servant of the LORD commanded, and would not hear them, nor do them.
^13^ Now in the fourteenth year of king Hezekiah did Sennacherib king of Assyria come up against all the fenced cities of Judah, and took them.^^ ^14^ And Hezekiah king of Judah sent to the king of Assyria to Lachish, saying, I have offended; return from me: that which thou puttest on me will I bear. And the king of Assyria appointed unto Hezekiah king of Judah three hundred talents of silver and thirty talents of gold. ^15^ And Hezekiah gave him all the silver that was found in the house of the LORD, and in the treasures of the king’s house. ^16^ At that time did Hezekiah cut off the gold from the doors of the temple of the LORD, and from the pillars which Hezekiah king of Judah had overlaid, and gave it to the king of Assyria.^^
^[**18:13** Sennacherib: Heb. Sanherib]
^[**18:16** it: Heb. them]
^17^ And the king of Assyria sent Tartan and Rabsaris and Rab-shakeh from Lachish to king Hezekiah with a great host against Jerusalem. And they went up and came to Jerusalem. And when they were come up, they came and stood by the conduit of the upper pool, which is in the highway of the fuller’s field.^^ ^18^ And when they had called to the king, there came out to them Eliakim the son of Hilkiah, which was over the household, and Shebna the scribe, and Joah the son of Asaph the recorder.^^ ^19^ And Rab-shakeh said unto them, Speak ye now to Hezekiah, Thus saith the great king, the king of Assyria, What confidence is this wherein thou trustest? ^20^ Thou sayest, (but they are but vain words,) I have counsel and strength for the war. Now on whom dost thou trust, that thou rebellest against me?^^^^^^ ^21^ Now, behold, thou trustest upon the staff of this bruised reed, even upon Egypt, on which if a man lean, it will go into his hand, and pierce it: so is Pharaoh king of Egypt unto all that trust on him.^^ ^22^ But if ye say unto me, We trust in the LORD our God: is not that he, whose high places and whose altars Hezekiah hath taken away, and hath said to Judah and Jerusalem, Ye shall worship before this altar in Jerusalem? ^23^ Now therefore, I pray thee, give pledges to my lord the king of Assyria, and I will deliver thee two thousand horses, if thou be able on thy part to set riders upon them.^^ ^24^ How then wilt thou turn away the face of one captain of the least of my master’s servants, and put thy trust on Egypt for chariots and for horsemen? ^25^ Am I now come up without the LORD against this place to destroy it? The LORD said to me, Go up against this land, and destroy it. ^26^ Then said Eliakim the son of Hilkiah, and Shebna, and Joah, unto Rab-shakeh, Speak, I pray thee, to thy servants in the Syrian language; for we understand it: and talk not with us in the Jews’ language in the ears of the people that are on the wall. ^27^ But Rab-shakeh said unto them, Hath my master sent me to thy master, and to thee, to speak these words? hath he not sent me to the men which sit on the wall, that they may eat their own dung, and drink their own piss with you?^^ ^28^ Then Rab-shakeh stood and cried with a loud voice in the Jews’ language, and spake, saying, Hear the word of the great king, the king of Assyria: ^29^ Thus saith the king, Let not Hezekiah deceive you: for he shall not be able to deliver you out of his hand: ^30^ Neither let Hezekiah make you trust in the LORD, saying, The LORD will surely deliver us, and this city shall not be delivered into the hand of the king of Assyria. ^31^ Hearken not to Hezekiah: for thus saith the king of Assyria, Make an agreement with me by a present, and come out to me, and then eat ye every man of his own vine, and every one of his fig tree, and drink ye every one the waters of his cistern:^^^^ ^32^ Until I come and take you away to a land like your own land, a land of corn and wine, a land of bread and vineyards, a land of oil olive and of honey, that ye may live, and not die: and hearken not unto Hezekiah, when he persuadeth you, saying, The LORD will deliver us.^^ ^33^ Hath any of the gods of the nations delivered at all his land out of the hand of the king of Assyria? ^34^ Where are the gods of Hamath, and of Arpad? where are the gods of Sepharvaim, Hena, and Ivah? have they delivered Samaria out of mine hand? ^35^ Who are they among all the gods of the countries, that have delivered their country out of mine hand, that the LORD should deliver Jerusalem out of mine hand? ^36^ But the people held their peace, and answered him not a word: for the king’s commandment was, saying, Answer him not. ^37^ Then came Eliakim the son of Hilkiah, which was over the household, and Shebna the scribe, and Joah the son of Asaph the recorder, to Hezekiah with their clothes rent, and told him the words of Rab-shakeh.
^[**18:17** great: Heb. heavy]
^[**18:18** scribe: or, secretary]
^[**18:20** sayest: or, talkest]
^[**18:20** vain…: Heb. word of the lips]
^[**18:20** I have…: or, but counsel and strength are for the war]
^[**18:21** trustest: Heb. trustest thee]
^[**18:23** pledges: or, hostages]
^[**18:27** their own piss: Heb. the water of their feet]
^[**18:31** Make…: or, Seek my favour: Heb. Make with me a blessing]
^[**18:31** cistern: or, pit]
^[**18:32** persuadeth: or, deceiveth]
# 19
^1^ And it came to pass, when king Hezekiah heard it, that he rent his clothes, and covered himself with sackcloth, and went into the house of the LORD. ^2^ And he sent Eliakim, which was over the household, and Shebna the scribe, and the elders of the priests, covered with sackcloth, to Isaiah the prophet the son of Amoz. ^3^ And they said unto him, Thus saith Hezekiah, This day is a day of trouble, and of rebuke, and blasphemy: for the children are come to the birth, and there is not strength to bring forth.^^ ^4^ It may be the LORD thy God will hear all the words of Rab-shakeh, whom the king of Assyria his master hath sent to reproach the living God; and will reprove the words which the LORD thy God hath heard: wherefore lift up thy prayer for the remnant that are left.^^ ^5^ So the servants of king Hezekiah came to Isaiah.
^[**19:3** blasphemy: or, provocation]
^[**19:4** left: Heb. found]
^6^ And Isaiah said unto them, Thus shall ye say to your master, Thus saith the LORD, Be not afraid of the words which thou hast heard, with which the servants of the king of Assyria have blasphemed me. ^7^ Behold, I will send a blast upon him, and he shall hear a rumour, and shall return to his own land; and I will cause him to fall by the sword in his own land.
^8^ So Rab-shakeh returned, and found the king of Assyria warring against Libnah: for he had heard that he was departed from Lachish. ^9^ And when he heard say of Tirhakah king of Ethiopia, Behold, he is come out to fight against thee: he sent messengers again unto Hezekiah, saying, ^10^ Thus shall ye speak to Hezekiah king of Judah, saying, Let not thy God in whom thou trustest deceive thee, saying, Jerusalem shall not be delivered into the hand of the king of Assyria. ^11^ Behold, thou hast heard what the kings of Assyria have done to all lands, by destroying them utterly: and shalt thou be delivered? ^12^ Have the gods of the nations delivered them which my fathers have destroyed; as Gozan, and Haran, and Rezeph, and the children of Eden which were in Thelasar? ^13^ Where is the king of Hamath, and the king of Arpad, and the king of the city of Sepharvaim, of Hena, and Ivah?
^14^ And Hezekiah received the letter of the hand of the messengers, and read it: and Hezekiah went up into the house of the LORD, and spread it before the LORD. ^15^ And Hezekiah prayed before the LORD, and said, O LORD God of Israel, which dwellest between the cherubims, thou art the God, even thou alone, of all the kingdoms of the earth; thou hast made heaven and earth. ^16^ LORD, bow down thine ear, and hear: open, LORD, thine eyes, and see: and hear the words of Sennacherib, which hath sent him to reproach the living God. ^17^ Of a truth, LORD, the kings of Assyria have destroyed the nations and their lands, ^18^ And have cast their gods into the fire: for they were no gods, but the work of men’s hands, wood and stone: therefore they have destroyed them.^^ ^19^ Now therefore, O LORD our God, I beseech thee, save thou us out of his hand, that all the kingdoms of the earth may know that thou art the LORD God, even thou only.
^[**19:18** cast: Heb. given]
^20^ Then Isaiah the son of Amoz sent to Hezekiah, saying, Thus saith the LORD God of Israel, That which thou hast prayed to me against Sennacherib king of Assyria I have heard. ^21^ This is the word that the LORD hath spoken concerning him; The virgin the daughter of Zion hath despised thee, and laughed thee to scorn; the daughter of Jerusalem hath shaken her head at thee. ^22^ Whom hast thou reproached and blasphemed? and against whom hast thou exalted thy voice, and lifted up thine eyes on high? even against the Holy One of Israel. ^23^ By thy messengers thou hast reproached the Lord, and hast said, With the multitude of my chariots I am come up to the height of the mountains, to the sides of Lebanon, and will cut down the tall cedar trees thereof, and the choice fir trees thereof: and I will enter into the lodgings of his borders, and into the forest of his Carmel.^^^^^^ ^24^ I have digged and drunk strange waters, and with the sole of my feet have I dried up all the rivers of besieged places.^^ ^25^ Hast thou not heard long ago how I have done it, and of ancient times that I have formed it? now have I brought it to pass, that thou shouldest be to lay waste fenced cities into ruinous heaps.^^ ^26^ Therefore their inhabitants were of small power, they were dismayed and confounded; they were as the grass of the field, and as the green herb, as the grass on the housetops, and as corn blasted before it be grown up.^^ ^27^ But I know thy abode, and thy going out, and thy coming in, and thy rage against me.^^ ^28^ Because thy rage against me and thy tumult is come up into mine ears, therefore I will put my hook in thy nose, and my bridle in thy lips, and I will turn thee back by the way by which thou camest. ^29^ And this shall be a sign unto thee, Ye shall eat this year such things as grow of themselves, and in the second year that which springeth of the same; and in the third year sow ye, and reap, and plant vineyards, and eat the fruits thereof. ^30^ And the remnant that is escaped of the house of Judah shall yet again take root downward, and bear fruit upward.^^ ^31^ For out of Jerusalem shall go forth a remnant, and they that escape out of mount Zion: the zeal of the LORD of hosts shall do this.^^ ^32^ Therefore thus saith the LORD concerning the king of Assyria, He shall not come into this city, nor shoot an arrow there, nor come before it with shield, nor cast a bank against it. ^33^ By the way that he came, by the same shall he return, and shall not come into this city, saith the LORD. ^34^ For I will defend this city, to save it, for mine own sake, and for my servant David’s sake.
^[**19:23** By: Heb. By the hand of]
^[**19:23** tall…: Heb. tallness, etc]
^[**19:23** of his Carmel: or, and his fruitful field]
^[**19:24** besieged: or, fenced]
^[**19:25** long…: or, how I have made it long ago, and formed it of ancient times? should I now bring it to be laid waste, and fenced cities to be ruinous heaps?]
^[**19:26** of small…: Heb. short of hand]
^[**19:27** abode: or, sitting]
^[**19:30** remnant…: Heb. escaping of the house of Judah that remaineth]
^[**19:31** they…: Heb. the escaping]
^35^ And it came to pass that night, that the angel of the LORD went out, and smote in the camp of the Assyrians an hundred fourscore and five thousand: and when they arose early in the morning, behold, they were all dead corpses. ^36^ So Sennacherib king of Assyria departed, and went and returned, and dwelt at Nineveh. ^37^ And it came to pass, as he was worshipping in the house of Nisroch his god, that Adrammelech and Sharezer his sons smote him with the sword: and they escaped into the land of Armenia. And Esar-haddon his son reigned in his stead.^^
^[**19:37** Armenia: Heb. Ararat]
# 20
^1^ In those days was Hezekiah sick unto death. And the prophet Isaiah the son of Amoz came to him, and said unto him, Thus saith the LORD, Set thine house in order; for thou shalt die, and not live.^^ ^2^ Then he turned his face to the wall, and prayed unto the LORD, saying, ^3^ I beseech thee, O LORD, remember now how I have walked before thee in truth and with a perfect heart, and have done that which is good in thy sight. And Hezekiah wept sore.^^ ^4^ And it came to pass, afore Isaiah was gone out into the middle court, that the word of the LORD came to him, saying,^^ ^5^ Turn again, and tell Hezekiah the captain of my people, Thus saith the LORD, the God of David thy father, I have heard thy prayer, I have seen thy tears: behold, I will heal thee: on the third day thou shalt go up unto the house of the LORD. ^6^ And I will add unto thy days fifteen years; and I will deliver thee and this city out of the hand of the king of Assyria; and I will defend this city for mine own sake, and for my servant David’s sake. ^7^ And Isaiah said, Take a lump of figs. And they took and laid it on the boil, and he recovered.
^[**20:1** Set…: Heb. Give charge concerning thine house]
^[**20:3** sore: Heb. with a great weeping]
^[**20:4** court: or, city]
^8^ And Hezekiah said unto Isaiah, What shall be the sign that the LORD will heal me, and that I shall go up into the house of the LORD the third day? ^9^ And Isaiah said, This sign shalt thou have of the LORD, that the LORD will do the thing that he hath spoken: shall the shadow go forward ten degrees, or go back ten degrees? ^10^ And Hezekiah answered, It is a light thing for the shadow to go down ten degrees: nay, but let the shadow return backward ten degrees. ^11^ And Isaiah the prophet cried unto the LORD: and he brought the shadow ten degrees backward, by which it had gone down in the dial of Ahaz.^^
^[**20:11** dial: Heb. degrees]
^12^ At that time Berodach-baladan, the son of Baladan, king of Babylon, sent letters and a present unto Hezekiah: for he had heard that Hezekiah had been sick.^^ ^13^ And Hezekiah hearkened unto them, and shewed them all the house of his precious things, the silver, and the gold, and the spices, and the precious ointment, and all the house of his armour, and all that was found in his treasures: there was nothing in his house, nor in all his dominion, that Hezekiah shewed them not.^^^^
^[**20:12** Berodach-baladan: or, Merodach-baladan]
^[**20:13** precious things: or, spicery]
^[**20:13** armour: or, jewels: Heb. vessels]
^14^ Then came Isaiah the prophet unto king Hezekiah, and said unto him, What said these men? and from whence came they unto thee? And Hezekiah said, They are come from a far country, even from Babylon. ^15^ And he said, What have they seen in thine house? And Hezekiah answered, All the things that are in mine house have they seen: there is nothing among my treasures that I have not shewed them. ^16^ And Isaiah said unto Hezekiah, Hear the word of the LORD. ^17^ Behold, the days come, that all that is in thine house, and that which thy fathers have laid up in store unto this day, shall be carried into Babylon: nothing shall be left, saith the LORD. ^18^ And of thy sons that shall issue from thee, which thou shalt beget, shall they take away; and they shall be eunuchs in the palace of the king of Babylon. ^19^ Then said Hezekiah unto Isaiah, Good is the word of the LORD which thou hast spoken. And he said, Is it not good, if peace and truth be in my days?^^
^[**20:19** Is it…: or, Shall there not be peace and truth, etc]
^20^ And the rest of the acts of Hezekiah, and all his might, and how he made a pool, and a conduit, and brought water into the city, are they not written in the book of the chronicles of the kings of Judah? ^21^ And Hezekiah slept with his fathers: and Manasseh his son reigned in his stead.
# 21
^1^ Manasseh was twelve years old when he began to reign, and reigned fifty and five years in Jerusalem. And his mother’s name was Hephzi-bah. ^2^ And he did that which was evil in the sight of the LORD, after the abominations of the heathen, whom the LORD cast out before the children of Israel. ^3^ For he built up again the high places which Hezekiah his father had destroyed; and he reared up altars for Baal, and made a grove, as did Ahab king of Israel; and worshipped all the host of heaven, and served them. ^4^ And he built altars in the house of the LORD, of which the LORD said, In Jerusalem will I put my name. ^5^ And he built altars for all the host of heaven in the two courts of the house of the LORD. ^6^ And he made his son pass through the fire, and observed times, and used enchantments, and dealt with familiar spirits and wizards: he wrought much wickedness in the sight of the LORD, to provoke him to anger. ^7^ And he set a graven image of the grove that he had made in the house, of which the LORD said to David, and to Solomon his son, In this house, and in Jerusalem, which I have chosen out of all tribes of Israel, will I put my name for ever: ^8^ Neither will I make the feet of Israel move any more out of the land which I gave their fathers; only if they will observe to do according to all that I have commanded them, and according to all the law that my servant Moses commanded them. ^9^ But they hearkened not: and Manasseh seduced them to do more evil than did the nations whom the LORD destroyed before the children of Israel.
^10^ And the LORD spake by his servants the prophets, saying, ^11^ Because Manasseh king of Judah hath done these abominations, and hath done wickedly above all that the Amorites did, which were before him, and hath made Judah also to sin with his idols: ^12^ Therefore thus saith the LORD God of Israel, Behold, I am bringing such evil upon Jerusalem and Judah, that whosoever heareth of it, both his ears shall tingle. ^13^ And I will stretch over Jerusalem the line of Samaria, and the plummet of the house of Ahab: and I will wipe Jerusalem as a man wipeth a dish, wiping it, and turning it upside down.^^ ^14^ And I will forsake the remnant of mine inheritance, and deliver them into the hand of their enemies; and they shall become a prey and a spoil to all their enemies; ^15^ Because they have done that which was evil in my sight, and have provoked me to anger, since the day their fathers came forth out of Egypt, even unto this day. ^16^ Moreover Manasseh shed innocent blood very much, till he had filled Jerusalem from one end to another; beside his sin wherewith he made Judah to sin, in doing that which was evil in the sight of the LORD.^^
^[**21:13** wiping…: Heb. he wipeth and turneth it upon the face thereof]
^[**21:16** from…: Heb. from mouth to mouth]
^17^ Now the rest of the acts of Manasseh, and all that he did, and his sin that he sinned, are they not written in the book of the chronicles of the kings of Judah? ^18^ And Manasseh slept with his fathers, and was buried in the garden of his own house, in the garden of Uzza: and Amon his son reigned in his stead.
^19^ Amon was twenty and two years old when he began to reign, and he reigned two years in Jerusalem. And his mother’s name was Meshullemeth, the daughter of Haruz of Jotbah. ^20^ And he did that which was evil in the sight of the LORD, as his father Manasseh did. ^21^ And he walked in all the way that his father walked in, and served the idols that his father served, and worshipped them: ^22^ And he forsook the LORD God of his fathers, and walked not in the way of the LORD.
^23^ And the servants of Amon conspired against him, and slew the king in his own house. ^24^ And the people of the land slew all them that had conspired against king Amon; and the people of the land made Josiah his son king in his stead. ^25^ Now the rest of the acts of Amon which he did, are they not written in the book of the chronicles of the kings of Judah? ^26^ And he was buried in his sepulchre in the garden of Uzza: and Josiah his son reigned in his stead.^^
^[**21:26** Josiah: Gr. Josias]
# 22
^1^ Josiah was eight years old when he began to reign, and he reigned thirty and one years in Jerusalem. And his mother’s name was Jedidah, the daughter of Adaiah of Boscath. ^2^ And he did that which was right in the sight of the LORD, and walked in all the way of David his father, and turned not aside to the right hand or to the left.
^3^ And it came to pass in the eighteenth year of king Josiah, that the king sent Shaphan the son of Azaliah, the son of Meshullam, the scribe, to the house of the LORD, saying, ^4^ Go up to Hilkiah the high priest, that he may sum the silver which is brought into the house of the LORD, which the keepers of the door have gathered of the people:^^ ^5^ And let them deliver it into the hand of the doers of the work, that have the oversight of the house of the LORD: and let them give it to the doers of the work which is in the house of the LORD, to repair the breaches of the house, ^6^ Unto carpenters, and builders, and masons, and to buy timber and hewn stone to repair the house. ^7^ Howbeit there was no reckoning made with them of the money that was delivered into their hand, because they dealt faithfully.
^[**22:4** door: Heb. threshold]
^8^ And Hilkiah the high priest said unto Shaphan the scribe, I have found the book of the law in the house of the LORD. And Hilkiah gave the book to Shaphan, and he read it. ^9^ And Shaphan the scribe came to the king, and brought the king word again, and said, Thy servants have gathered the money that was found in the house, and have delivered it into the hand of them that do the work, that have the oversight of the house of the LORD.^^ ^10^ And Shaphan the scribe shewed the king, saying, Hilkiah the priest hath delivered me a book. And Shaphan read it before the king.
^[**22:9** gathered: Heb. melted]
^11^ And it came to pass, when the king had heard the words of the book of the law, that he rent his clothes. ^12^ And the king commanded Hilkiah the priest, and Ahikam the son of Shaphan, and Achbor the son of Michaiah, and Shaphan the scribe, and Asahiah a servant of the king’s, saying,^^^^ ^13^ Go ye, enquire of the LORD for me, and for the people, and for all Judah, concerning the words of this book that is found: for great is the wrath of the LORD that is kindled against us, because our fathers have not hearkened unto the words of this book, to do according unto all that which is written concerning us. ^14^ So Hilkiah the priest, and Ahikam, and Achbor, and Shaphan, and Asahiah, went unto Huldah the prophetess, the wife of Shallum the son of Tikvah, the son of Harhas, keeper of the wardrobe; (now she dwelt in Jerusalem in the college;) and they communed with her.^^^^
^[**22:12** Achbor: or, Abdon]
^[**22:12** Michaiah: or, Micah]
^[**22:14** wardrobe: Heb. garments]
^[**22:14** in the…: or, in the second part]
^15^ And she said unto them, Thus saith the LORD God of Israel, Tell the man that sent you to me, ^16^ Thus saith the LORD, Behold, I will bring evil upon this place, and upon the inhabitants thereof, even all the words of the book which the king of Judah hath read: ^17^ Because they have forsaken me, and have burned incense unto other gods, that they might provoke me to anger with all the works of their hands; therefore my wrath shall be kindled against this place, and shall not be quenched. ^18^ But to the king of Judah which sent you to enquire of the LORD, thus shall ye say to him, Thus saith the LORD God of Israel, As touching the words which thou hast heard; ^19^ Because thine heart was tender, and thou hast humbled thyself before the LORD, when thou heardest what I spake against this place, and against the inhabitants thereof, that they should become a desolation and a curse, and hast rent thy clothes, and wept before me; I also have heard thee, saith the LORD. ^20^ Behold therefore, I will gather thee unto thy fathers, and thou shalt be gathered into thy grave in peace; and thine eyes shall not see all the evil which I will bring upon this place. And they brought the king word again.
# 23
^1^ And the king sent, and they gathered unto him all the elders of Judah and of Jerusalem. ^2^ And the king went up into the house of the LORD, and all the men of Judah and all the inhabitants of Jerusalem with him, and the priests, and the prophets, and all the people, both small and great: and he read in their ears all the words of the book of the covenant which was found in the house of the LORD.^^
^[**23:2** both…: Heb. from small even unto great]
^3^ And the king stood by a pillar, and made a covenant before the LORD, to walk after the LORD, and to keep his commandments and his testimonies and his statutes with all their heart and all their soul, to perform the words of this covenant that were written in this book. And all the people stood to the covenant.
^4^ And the king commanded Hilkiah the high priest, and the priests of the second order, and the keepers of the door, to bring forth out of the temple of the LORD all the vessels that were made for Baal, and for the grove, and for all the host of heaven: and he burned them without Jerusalem in the fields of Kidron, and carried the ashes of them unto Beth-el. ^5^ And he put down the idolatrous priests, whom the kings of Judah had ordained to burn incense in the high places in the cities of Judah, and in the places round about Jerusalem; them also that burned incense unto Baal, to the sun, and to the moon, and to the planets, and to all the host of heaven.^^^^^^ ^6^ And he brought out the grove from the house of the LORD, without Jerusalem, unto the brook Kidron, and burned it at the brook Kidron, and stamped it small to powder, and cast the powder thereof upon the graves of the children of the people. ^7^ And he brake down the houses of the sodomites, that were by the house of the LORD, where the women wove hangings for the grove.^^ ^8^ And he brought all the priests out of the cities of Judah, and defiled the high places where the priests had burned incense, from Geba to Beer-sheba, and brake down the high places of the gates that were in the entering in of the gate of Joshua the governor of the city, which were on a man’s left hand at the gate of the city. ^9^ Nevertheless the priests of the high places came not up to the altar of the LORD in Jerusalem, but they did eat of the unleavened bread among their brethren. ^10^ And he defiled Topheth, which is in the valley of the children of Hinnom, that no man might make his son or his daughter to pass through the fire to Molech. ^11^ And he took away the horses that the kings of Judah had given to the sun, at the entering in of the house of the LORD, by the chamber of Nathan-melech the chamberlain, which was in the suburbs, and burned the chariots of the sun with fire.^^ ^12^ And the altars that were on the top of the upper chamber of Ahaz, which the kings of Judah had made, and the altars which Manasseh had made in the two courts of the house of the LORD, did the king beat down, and brake them down from thence, and cast the dust of them into the brook Kidron.^^ ^13^ And the high places that were before Jerusalem, which were on the right hand of the mount of corruption, which Solomon the king of Israel had builded for Ashtoreth the abomination of the Zidonians, and for Chemosh the abomination of the Moabites, and for Milcom the abomination of the children of Ammon, did the king defile.^^ ^14^ And he brake in pieces the images, and cut down the groves, and filled their places with the bones of men.^^
^[**23:5** put…: Heb. caused to cease]
^[**23:5** idolatrous…: Heb. Chemarim]
^[**23:5** planets: or, twelve signs or, constellations]
^[**23:7** hangings: Heb. houses]
^[**23:11** chamberlain: or, eunuch, or, officer]
^[**23:12** brake…: or, ran from thence]
^[**23:13** the mount…: that is, the mount of Olives]
^[**23:14** images: Heb. statues]
^15^ Moreover the altar that was at Beth-el, and the high place which Jeroboam the son of Nebat, who made Israel to sin, had made, both that altar and the high place he brake down, and burned the high place, and stamped it small to powder, and burned the grove. ^16^ And as Josiah turned himself, he spied the sepulchres that were there in the mount, and sent, and took the bones out of the sepulchres, and burned them upon the altar, and polluted it, according to the word of the LORD which the man of God proclaimed, who proclaimed these words. ^17^ Then he said, What title is that that I see? And the men of the city told him, It is the sepulchre of the man of God, which came from Judah, and proclaimed these things that thou hast done against the altar of Beth-el. ^18^ And he said, Let him alone; let no man move his bones. So they let his bones alone, with the bones of the prophet that came out of Samaria.^^ ^19^ And all the houses also of the high places that were in the cities of Samaria, which the kings of Israel had made to provoke the Lord to anger, Josiah took away, and did to them according to all the acts that he had done in Beth-el. ^20^ And he slew all the priests of the high places that were there upon the altars, and burned men’s bones upon them, and returned to Jerusalem.^^
^[**23:18** bones alone: Heb. bones to escape]
^[**23:20** slew: or, sacrificed]
^21^ And the king commanded all the people, saying, Keep the passover unto the LORD your God, as it is written in the book of this covenant. ^22^ Surely there was not holden such a passover from the days of the judges that judged Israel, nor in all the days of the kings of Israel, nor of the kings of Judah; ^23^ But in the eighteenth year of king Josiah, wherein this passover was holden to the LORD in Jerusalem.
^24^ Moreover the workers with familiar spirits, and the wizards, and the images, and the idols, and all the abominations that were spied in the land of Judah and in Jerusalem, did Josiah put away, that he might perform the words of the law which were written in the book that Hilkiah the priest found in the house of the LORD.^^
^[**23:24** images: or, teraphim]
^25^ And like unto him was there no king before him, that turned to the LORD with all his heart, and with all his soul, and with all his might, according to all the law of Moses; neither after him arose there any like him.
^26^ Notwithstanding the LORD turned not from the fierceness of his great wrath, wherewith his anger was kindled against Judah, because of all the provocations that Manasseh had provoked him withal.^^ ^27^ And the LORD said, I will remove Judah also out of my sight, as I have removed Israel, and will cast off this city Jerusalem which I have chosen, and the house of which I said, My name shall be there. ^28^ Now the rest of the acts of Josiah, and all that he did, are they not written in the book of the chronicles of the kings of Judah?
^[**23:26** provocations: Heb. angers]
^29^ In his days Pharaoh-nechoh king of Egypt went up against the king of Assyria to the river Euphrates: and king Josiah went against him; and he slew him at Megiddo, when he had seen him. ^30^ And his servants carried him in a chariot dead from Megiddo, and brought him to Jerusalem, and buried him in his own sepulchre. And the people of the land took Jehoahaz the son of Josiah, and anointed him, and made him king in his father’s stead.
^31^ Jehoahaz was twenty and three years old when he began to reign; and he reigned three months in Jerusalem. And his mother’s name was Hamutal, the daughter of Jeremiah of Libnah.^^ ^32^ And he did that which was evil in the sight of the LORD, according to all that his fathers had done. ^33^ And Pharaoh-nechoh put him in bands at Riblah in the land of Hamath, that he might not reign in Jerusalem; and put the land to a tribute of an hundred talents of silver, and a talent of gold.^^^^ ^34^ And Pharaoh-nechoh made Eliakim the son of Josiah king in the room of Josiah his father, and turned his name to Jehoiakim, and took Jehoahaz away: and he came to Egypt, and died there. ^35^ And Jehoiakim gave the silver and the gold to Pharaoh; but he taxed the land to give the money according to the commandment of Pharaoh: he exacted the silver and the gold of the people of the land, of every one according to his taxation, to give it unto Pharaoh-nechoh.
^[**23:31** Jehoahaz: also called, Shallum]
^[**23:33** that…: or, because he reigned]
^[**23:33** put the…: Heb. set a fine upon the land]
^36^ Jehoiakim was twenty and five years old when he began to reign; and he reigned eleven years in Jerusalem. And his mother’s name was Zebudah, the daughter of Pedaiah of Rumah. ^37^ And he did that which was evil in the sight of the LORD, according to all that his fathers had done.
# 24
^1^ In his days Nebuchadnezzar king of Babylon came up, and Jehoiakim became his servant three years: then he turned and rebelled against him. ^2^ And the LORD sent against him bands of the Chaldees, and bands of the Syrians, and bands of the Moabites, and bands of the children of Ammon, and sent them against Judah to destroy it, according to the word of the LORD, which he spake by his servants the prophets.^^ ^3^ Surely at the commandment of the LORD came this upon Judah, to remove them out of his sight, for the sins of Manasseh, according to all that he did; ^4^ And also for the innocent blood that he shed: for he filled Jerusalem with innocent blood; which the LORD would not pardon.
^[**24:2** by: Heb. by the hand of]
^5^ Now the rest of the acts of Jehoiakim, and all that he did, are they not written in the book of the chronicles of the kings of Judah? ^6^ So Jehoiakim slept with his fathers: and Jehoiachin his son reigned in his stead. ^7^ And the king of Egypt came not again any more out of his land: for the king of Babylon had taken from the river of Egypt unto the river Euphrates all that pertained to the king of Egypt.
^8^ Jehoiachin was eighteen years old when he began to reign, and he reigned in Jerusalem three months. And his mother’s name was Nehushta, the daughter of Elnathan of Jerusalem.^^ ^9^ And he did that which was evil in the sight of the LORD, according to all that his father had done.
^[**24:8** Jehoiachin: also called Jeconiah and Coniah]
^10^ At that time the servants of Nebuchadnezzar king of Babylon came up against Jerusalem, and the city was besieged.^^ ^11^ And Nebuchadnezzar king of Babylon came against the city, and his servants did besiege it. ^12^ And Jehoiachin the king of Judah went out to the king of Babylon, he, and his mother, and his servants, and his princes, and his officers: and the king of Babylon took him in the eighth year of his reign.^^^^ ^13^ And he carried out thence all the treasures of the house of the LORD, and the treasures of the king’s house, and cut in pieces all the vessels of gold which Solomon king of Israel had made in the temple of the LORD, as the LORD had said. ^14^ And he carried away all Jerusalem, and all the princes, and all the mighty men of valour, even ten thousand captives, and all the craftsmen and smiths: none remained, save the poorest sort of the people of the land. ^15^ And he carried away Jehoiachin to Babylon, and the king’s mother, and the king’s wives, and his officers, and the mighty of the land, those carried he into captivity from Jerusalem to Babylon.^^ ^16^ And all the men of might, even seven thousand, and craftsmen and smiths a thousand, all that were strong and apt for war, even them the king of Babylon brought captive to Babylon.
^[**24:10** was…: Heb. came into siege]
^[**24:12** officers: or, eunuchs]
^[**24:12** his reign: Nebuchadnezzar’s eighth year]
^[**24:15** officers: or, eunuchs]
^17^ And the king of Babylon made Mattaniah his father’s brother king in his stead, and changed his name to Zedekiah. ^18^ Zedekiah was twenty and one years old when he began to reign, and he reigned eleven years in Jerusalem. And his mother’s name was Hamutal, the daughter of Jeremiah of Libnah. ^19^ And he did that which was evil in the sight of the LORD, according to all that Jehoiakim had done. ^20^ For through the anger of the LORD it came to pass in Jerusalem and Judah, until he had cast them out from his presence, that Zedekiah rebelled against the king of Babylon.
# 25
^1^ And it came to pass in the ninth year of his reign, in the tenth month, in the tenth day of the month, that Nebuchadnezzar king of Babylon came, he, and all his host, against Jerusalem, and pitched against it; and they built forts against it round about. ^2^ And the city was besieged unto the eleventh year of king Zedekiah. ^3^ And on the ninth day of the fourth month the famine prevailed in the city, and there was no bread for the people of the land.
^4^ And the city was broken up, and all the men of war fled by night by the way of the gate between two walls, which is by the king’s garden: (now the Chaldees were against the city round about:) and the king went the way toward the plain. ^5^ And the army of the Chaldees pursued after the king, and overtook him in the plains of Jericho: and all his army were scattered from him. ^6^ So they took the king, and brought him up to the king of Babylon to Riblah; and they gave judgment upon him.^^ ^7^ And they slew the sons of Zedekiah before his eyes, and put out the eyes of Zedekiah, and bound him with fetters of brass, and carried him to Babylon.^^
^[**25:6** gave…: Heb. spake judgment with him]
^[**25:7** put…: Heb. made blind]
^8^ And in the fifth month, on the seventh day of the month, which is the nineteenth year of king Nebuchadnezzar king of Babylon, came Nebuzar-adan, captain of the guard, a servant of the king of Babylon, unto Jerusalem:^^ ^9^ And he burnt the house of the LORD, and the king’s house, and all the houses of Jerusalem, and every great man’s house burnt he with fire. ^10^ And all the army of the Chaldees, that were with the captain of the guard, brake down the walls of Jerusalem round about. ^11^ Now the rest of the people that were left in the city, and the fugitives that fell away to the king of Babylon, with the remnant of the multitude, did Nebuzar-adan the captain of the guard carry away.^^ ^12^ But the captain of the guard left of the poor of the land to be vinedressers and husbandmen. ^13^ And the pillars of brass that were in the house of the LORD, and the bases, and the brasen sea that was in the house of the LORD, did the Chaldees break in pieces, and carried the brass of them to Babylon. ^14^ And the pots, and the shovels, and the snuffers, and the spoons, and all the vessels of brass wherewith they ministered, took they away. ^15^ And the firepans, and the bowls, and such things as were of gold, in gold, and of silver, in silver, the captain of the guard took away. ^16^ The two pillars, one sea, and the bases which Solomon had made for the house of the LORD; the brass of all these vessels was without weight.^^ ^17^ The height of the one pillar was eighteen cubits, and the chapiter upon it was brass: and the height of the chapiter three cubits; and the wreathen work, and pomegranates upon the chapiter round about, all of brass: and like unto these had the second pillar with wreathen work.
^[**25:8** captain…: or, chief marshal]
^[**25:11** fugitives: Heb. fallen away]
^[**25:16** one…: Heb. the one sea]
^18^ And the captain of the guard took Seraiah the chief priest, and Zephaniah the second priest, and the three keepers of the door:^^ ^19^ And out of the city he took an officer that was set over the men of war, and five men of them that were in the king’s presence, which were found in the city, and the principal scribe of the host, which mustered the people of the land, and threescore men of the people of the land that were found in the city:^^^^^^ ^20^ And Nebuzar-adan captain of the guard took these, and brought them to the king of Babylon to Riblah: ^21^ And the king of Babylon smote them, and slew them at Riblah in the land of Hamath. So Judah was carried away out of their land.
^[**25:18** door: Heb. threshold]
^[**25:19** officer: or, eunuch]
^[**25:19** were in…: Heb. saw the king’s face]
^[**25:19** principal…: or, scribe of the captain of the host]
^22^ And as for the people that remained in the land of Judah, whom Nebuchadnezzar king of Babylon had left, even over them he made Gedaliah the son of Ahikam, the son of Shaphan, ruler. ^23^ And when all the captains of the armies, they and their men, heard that the king of Babylon had made Gedaliah governor, there came to Gedaliah to Mizpah, even Ishmael the son of Nethaniah, and Johanan the son of Careah, and Seraiah the son of Tanhumeth the Netophathite, and Jaazaniah the son of a Maachathite, they and their men. ^24^ And Gedaliah sware to them, and to their men, and said unto them, Fear not to be the servants of the Chaldees: dwell in the land, and serve the king of Babylon; and it shall be well with you. ^25^ But it came to pass in the seventh month, that Ishmael the son of Nethaniah, the son of Elishama, of the seed royal, came, and ten men with him, and smote Gedaliah, that he died, and the Jews and the Chaldees that were with him at Mizpah.^^ ^26^ And all the people, both small and great, and the captains of the armies, arose, and came to Egypt: for they were afraid of the Chaldees.
^[**25:25** royal: Heb. of the kingdom]
^27^ And it came to pass in the seven and thirtieth year of the captivity of Jehoiachin king of Judah, in the twelfth month, on the seven and twentieth day of the month, that Evil-merodach king of Babylon in the year that he began to reign did lift up the head of Jehoiachin king of Judah out of prison; ^28^ And he spake kindly to him, and set his throne above the throne of the kings that were with him in Babylon;+ 25.28 kindly…: Heb. good things with him ^29^ And changed his prison garments: and he did eat bread continually before him all the days of his life. ^30^ And his allowance was a continual allowance given him of the king, a daily rate for every day, all the days of his life. | 244.221014 | 3,912 | 0.747719 | eng_Latn | 0.999962 |
8a8296e8525530c188630165c311ad3ac5bd5d02 | 17,922 | md | Markdown | README.md | TonyLv/captum | fe0436abcd579942ce1c3d4e68508c58e8a885ce | [
"BSD-3-Clause"
] | 1 | 2020-01-15T16:03:16.000Z | 2020-01-15T16:03:16.000Z | README.md | TonyLv/captum | fe0436abcd579942ce1c3d4e68508c58e8a885ce | [
"BSD-3-Clause"
] | null | null | null | README.md | TonyLv/captum | fe0436abcd579942ce1c3d4e68508c58e8a885ce | [
"BSD-3-Clause"
] | null | null | null | 
<hr/>
[](https://anaconda.org/pytorch/captum)
[](https://pypi.org/project/captum)
[](https://circleci.com/gh/pytorch/captum)
Captum is a model interpretability and understanding library for PyTorch.
Captum means comprehension in latin and contains general purpose implementations
of integrated gradients, saliency maps, smoothgrad, vargrad and others for
PyTorch models. It has quick integration for models built with domain-specific
libraries such as torchvision, torchtext, and others.
*Captum is currently in beta and under active development!*
#### About Captum
With the increase in model complexity and the resulting lack of transparency, model interpretability methods have become increasingly important. Model understanding is both an active area of research as well as an area of focus for practical applications across industries using machine learning. Captum provides state-of-the-art algorithms, including Integrated Gradients, to provide researchers and developers with an easy way to understand which features are contributing to a model’s output.
For model developers, Captum can be used to improve and troubleshoot models by facilitating the identification of different features that contribute to a model’s output in order to design better models and troubleshoot unexpected model outputs.
Captum helps ML researchers more easily implement interpretability algorithms that can interact with PyTorch models. Captum also allows researchers to quickly benchmark their work against other existing algorithms available in the library.
#### Target Audience
The primary audiences for Captum are model developers who are looking to improve their models and understand which features are important and interpretability researchers focused on identifying algorithms that can better interpret many types of models.
Captum can also be used by application engineers who are using trained models in production. Captum provides easier troubleshooting through improved model interpretability, and the potential for delivering better explanations to end users on why they’re seeing a specific piece of content, such as a movie recommendation.
## Installation
**Installation Requirements**
- Python >= 3.6
- PyTorch >= 1.2
##### Installing the latest release
The latest release of Captum is easily installed either via
[Anaconda](https://www.anaconda.com/distribution/#download-section) (recommended):
```bash
conda install captum -c pytorch
```
or via `pip`:
```bash
pip install captum
```
##### Installing from latest master
If you'd like to try our bleeding edge features (and don't mind potentially
running into the occasional bug here or there), you can install the latest
master directly from GitHub:
```bash
pip install git+https://github.com/pytorch/captum.git
```
**Manual / Dev install**
Alternatively, you can do a manual install. For a basic install, run:
```bash
git clone https://github.com/pytorch/captum.git
cd captum
pip install -e .
```
To customize the installation, you can also run the following variants of the
above:
* `pip install -e .[insights]`: Also installs all packages necessary for running Captum Insights.
* `pip install -e .[dev]`: Also installs all tools necessary for development
(testing, linting, docs building; see [Contributing](#contributing) below).
* `pip install -e .[tutorials]`: Also installs all packages necessary for running the tutorial notebooks.
To execute unit tests from a manual install, run:
```bash
# running a single unit test
python -m unittest -v tests.attr.test_saliency
# running all unit tests
pytest -ra
```
## Getting Started
Captum helps you interpret and understand predictions of PyTorch models by
exploring features that contribute to a prediction the model makes.
It also helps understand which neurons and layers are important for
model predictions.
Currently, the library uses gradient-based interpretability algorithms
and attributes contributions to each input of the model with respect to
different neurons and layers, both intermediate and final.
Let's apply some of those algorithms to a toy model we have created for
demonstration purposes.
For simplicity, we will use the following architecture, but users are welcome
to use any PyTorch model of their choice.
```
import numpy as np
import torch
import torch.nn as nn
from captum.attr import (
GradientShap,
DeepLift,
DeepLiftShap,
IntegratedGradients,
LayerConductance,
NeuronConductance,
NoiseTunnel,
)
class ToyModel(nn.Module):
def __init__(self):
super().__init__()
self.lin1 = nn.Linear(3, 3)
self.relu = nn.ReLU()
self.lin2 = nn.Linear(3, 2)
# initialize weights and biases
self.lin1.weight = nn.Parameter(torch.arange(-4.0, 5.0).view(3, 3))
self.lin1.bias = nn.Parameter(torch.zeros(1,3))
self.lin2.weight = nn.Parameter(torch.arange(-3.0, 3.0).view(2, 3))
self.lin2.bias = nn.Parameter(torch.ones(1,2))
def forward(self, input):
return self.lin2(self.relu(self.lin1(input)))
```
Let's create an instance of our model and set it to eval mode.
```
model = ToyModel()
model.eval()
```
Next, we need to define simple input and baseline tensors.
Baselines belong to the input space and often carry no predictive signal.
Zero tensor can serve as a baseline for many tasks.
Some interpretability algorithms such as Integrated
Gradients, Deeplift and GradientShap are designed to attribute the change
between the input and baseline to a predictive class or a value that the neural
network outputs.
We will apply model interpretability algorithms on the network
mentioned above in order to understand the importance of individual
neurons/layers and the parts of the input that play an important role in the
final prediction.
To make computations deterministic, let's fix random seeds.
```
torch.manual_seed(123)
np.random.seed(123)
```
Let's define our input and baseline tensors. Baselines are used in some
interpretability algorithms such as `IntegratedGradients, DeepLift,
GradientShap, NeuronConductance, LayerConductance, InternalInfluence and
NeuronIntegratedGradients`.
```
input = torch.rand(2, 3)
baseline = torch.zeros(2, 3)
```
Next we will use `IntegratedGradients` algorithms to assign attribution
scores to each input feature with respect to the second target output.
```
ig = IntegratedGradients(model)
attributions, delta = ig.attribute(input, baseline, target=0, return_convergence_delta=True)
print('IG Attributions: ', attributions, ' Convergence Delta: ', delta)
```
Output:
```
IG Attributions: tensor([[-0.5922, -1.5497, -1.0067],
[ 0.0000, -0.2219, -5.1991]])
Convergence Delta: tensor([2.3842e-07, -4.7684e-07])
```
The algorithm outputs an attribution score for each input element and a
convergence delta. The lower the absolute value of the convergence delta the better
is the approximation. If we choose not to return delta,
we can simply not provide `return_convergence_delta` input
argument. The absolute value of the returned deltas can be interpreted as an
approximation error for each input sample.
It can also serve as a proxy of how accurate the integral approximation for given
inputs and baselines is.
If the approximation error is large, we can try larger number of integral
approximation steps by setting `n_steps` to a larger value. Not all algorithms
return approximation error. Those which do, though, compute it based on the
completeness property of the algorithms.
Positive attribution score means that the input in that particular position
positively contributed to the final prediction and negative means the opposite.
The magnitude of the attribution score signifies the strength of the contribution.
Zero attribution score means no contribution from that particular feature.
Similarly, we can apply `GradientShap`, `DeepLift` and other attribution algorithms to the model.
Gradient SHAP first chooses a random baseline from baselines' distribution, then
adds gaussian noise with std=0.09 to each input example `n_samples` times.
Afterwards, it chooses a random point between each example-baseline pair and
computes the gradients with respect to target class (in this case target=0). Resulting
attribution is the mean of gradients * (inputs - baselines)
```
gs = GradientShap(model)
# We define a distribution of baselines and draw `n_samples` from that
# distribution in order to estimate the expectations of gradients across all baselines
baseline_dist = torch.randn(10, 3) * 0.001
attributions, delta = gs.attribute(input, stdevs=0.09, n_samples=4, baselines=baseline_dist,
target=0, return_convergence_delta=True)
print('GradientShap Attributions: ', attributions, ' Convergence Delta: ', delta)
```
Output
```
GradientShap Attributions: tensor([[-0.1542, -1.6229, -1.5835],
[-0.3916, -0.2836, -4.6851]])
Convergence Delta: tensor([ 0.0000, -0.0005, -0.0029, -0.0084, -0.0087, -0.0405, 0.0000, -0.0084])
```
Deltas are computed for each `n_samples * input.shape[0]` example. The user can,
for instance, average them:
```
deltas_per_example = torch.mean(delta.reshape(input.shape[0], -1), dim=1)
```
in order to get per example average delta.
Below is an example of how we can apply `DeepLift` and `DeepLiftShap` on the
`ToyModel` described above. Current implementation of DeepLift supports only
`Rescale` rule.
For more details on alternative implementations, please read DeepLift's
original paper linked below.
```
dl = DeepLift(model)
attributions, delta = dl.attribute(input, baseline, target=0, return_convergence_delta=True)
print('DeepLift Attributions: ', attributions, ' Convergence Delta: ', delta)
```
Output
```
DeepLift Attributions: tensor([[-0.5922, -1.5497, -1.0067],
[ 0.0000, -0.2219, -5.1991])
Convergence Delta: tensor([0., 0.])
```
DeepLift assigns similar attribution scores as Integrated Gradients to inputs,
however it has lower execution time. Another important thing to remember about
DeepLift is that it currently doesn't support all non-linear activation types.
For more details on limitations of the current implementation, please read
DeepLift's original paper linked below.
Similar to integrated gradients, DeepLift returns a convergence delta score
per input example. The approximation error is then the absolute
value of the convergence deltas and can serve as a proxy of how accurate the
algorithm's approximation is.
Now let's look into `DeepLiftShap`. Similar to `GradientShap`, `DeepLiftShap` uses
baseline distribution. In the example below, we use the same baseline distribution
as for `GradientShap`.
```
dl = DeepLiftShap(model)
attributions, delta = dl.attribute(input, baseline_dist, target=0, return_convergence_delta=True)
print('DeepLiftSHAP Attributions: ', attributions, ' Convergence Delta: ', delta)
```
Output
```
DeepLiftShap Attributions: tensor([[-5.9169e-01, -1.5491e+00, -1.0076e+00],
[-4.7101e-03, -2.2300e-01, -5.1926e+00]], grad_fn=<MeanBackward1>)
Convergence Delta: tensor([-4.6120e-03, -1.6267e-03, -5.1045e-04, -1.4184e-03, -6.8886e-03,
-2.2224e-02, 0.0000e+00, -2.8790e-02, -4.1285e-03, -2.7295e-02,
-3.2349e-03, -1.6265e-03, -4.7684e-07, -1.4191e-03, -6.8889e-03,
-2.2224e-02, 0.0000e+00, -2.4792e-02, -4.1289e-03, -2.7296e-02])
```
`DeepLiftShap` uses `DeepLift` to compute attribution score for each
input-baseline pair and averages it for each input across all baselines.
It computes deltas for each input example-baseline pair, thus resulting to
`input.shape[0] * baseline.shape[0]` delta values.
Similar to GradientShap in order to compute example-based deltas we can average them per example:
```
deltas_per_example = torch.mean(delta.reshape(input.shape[0], -1), dim=1)
```
In order to smooth and improve the quality of the attributions we can run
`IntegratedGradients` and other attribution methods through a `NoiseTunnel`.
`NoiseTunnel` allows us to use SmoothGrad, SmoothGrad_Sq and VarGrad techniques
to smoothen the attributions by aggregating them for multiple noisy
samples that were generated by adding gaussian noise.
Here is an example how we can use `NoiseTunnel` with `IntegratedGradients`.
```
ig = IntegratedGradients(model)
nt = NoiseTunnel(ig)
attributions, delta = nt.attribute(input, nt_type='smoothgrad', stdevs=0.02, n_samples=4,
baselines=baseline, target=0, return_convergence_delta=True)
print('IG + SmoothGrad Attributions: ', attributions, ' Convergence Delta: ', delta)
```
Output
```
IG + SmoothGrad Attributions: tensor([[-0.4574, -1.5493, -1.0893],
[ 0.0000, -0.2647, -5.1619]])
Convergence Delta: tensor([ 0.0000e+00, 2.3842e-07, 0.0000e+00, -2.3842e-07, 0.0000e+00,
-4.7684e-07, 0.0000e+00, -4.7684e-07])
```
The number of elements in the `delta` tensor is equal to: `n_samples * input.shape[0]`
In order to get a example-based delta, we can, for example, average them:
```
deltas_per_example = torch.mean(delta.reshape(input.shape[0], -1), dim=1)
```
Let's look into the internals of our network and understand which layers
and neurons are important for the predictions.
We will start with the neuron conductance. Neuron conductance helps us to identify
input features that are important for a particular neuron in a given
layer. It decomposes the computation of integrated gradients via the chain rule by
defining the importance of a neuron as path integral of the derivative of the output
with respect to the neuron times the derivatives of the neuron with respect to the
inputs of the model.
In this case, we choose to analyze the first neuron in the linear layer.
```
nc = NeuronConductance(model, model.lin1)
attributions = nc.attribute(input, neuron_index=1, target=0)
print('Neuron Attributions: ', attributions)
```
Output
```
Neuron Attributions: tensor([[ 0.0000, 0.0000, 0.0000],
[ 1.3358, 0.0000, -1.6811]])
```
Layer conductance shows the importance of neurons for a layer and given input.
It is an extension of path integrated gradients for hidden layers and holds the
completeness property as well.
It doesn't attribute the contribution scores to the input features
but shows the importance of each neuron in selected layer.
```
lc = LayerConductance(model, model.lin1)
attributions, delta = lc.attribute(input, baselines=baseline, target=0, return_convergence_delta=True)
print('Layer Attributions: ', attributions, ' Convergence Delta: ', delta)
```
Outputs
```
Layer Attributions: tensor([[ 0.0000, 0.0000, -3.0856],
[ 0.0000, -0.3488, -4.9638]], grad_fn=<SumBackward1>)
Convergence Delta: tensor([0.0630, 0.1084])
```
Similar to other attribution algorithms that return convergence delta, LayerConductance
returns the deltas for each example. The approximation error is then the absolute
value of the convergence deltas and can serve as a proxy of how accurate integral
approximation for given inputs and baselines is.
More details on the list of supported algorithms and how to apply
Captum on different types of models can be found in our tutorials.
## Captum Insights
Captum provides a web interface called Insights for easy visualization and
access to a number of our interpretability algorithms.
To analyze a sample model on CIFAR10 via Captum Insights run
```
python -m captum.insights.example
```
and navigate to the URL specified in the output.
To build Insights you will need [Node](https://nodejs.org/en/) >= 8.x
and [Yarn](https://yarnpkg.com/en/) >= 1.5.
To build and launch from a checkout in a conda environment run
```
conda install -c conda-forge yarn
BUILD_INSIGHTS=1 python setup.py develop
python captum/insights/example.py
```
## Contributing
See the [CONTRIBUTING](CONTRIBUTING.md) file for how to help out.
## References
* [Axiomatic Attribution for Deep Networks, Mukund Sundararajan et al. 2017](https://arxiv.org/abs/1703.01365)
* [Did the Model Understand the Question? Pramod K. Mudrakarta, et al. 2018](https://www.aclweb.org/anthology/P18-1176)
* [Investigating the influence of noise and distractors on the interpretation of neural networks, Pieter-Jan Kindermans et al. 2016](https://arxiv.org/abs/1611.07270)
* [SmoothGrad: removing noise by adding noise, Daniel Smilkov et al. 2017](https://arxiv.org/abs/1706.03825)
* [Local Explanation Methods for Deep Neural Networks Lack Sensitivity to Parameter Values, Julius Adebayo et al. 2018](https://arxiv.org/abs/1810.03307)
* [Sanity Checks for Saliency Maps, Julius Adebayo et al. 2018](https://arxiv.org/abs/1810.03292)
* [How Important is a neuron?, Kedar Dhamdhere et al. 2018](https://arxiv.org/abs/1805.12233)
* [Learning Important Features Through Propagating Activation Differences, Avanti Shrikumar et al. 2017](https://arxiv.org/pdf/1704.02685.pdf)
* [Computationally Efficient Measures of Internal Neuron Importance, Avanti Shrikumar et al. 2018](https://arxiv.org/pdf/1807.09946.pdf)
* [A Unified Approach to Interpreting Model Predictions, Scott M. Lundberg et al. 2017](http://papers.nips.cc/paper/7062-a-unified-approach-to-interpreting-model-predictions)
* [Influence-Directed Explanations for Deep Convolutional Networks, Klas Leino et al. 2018](https://arxiv.org/pdf/1802.03788.pdf)
* [Towards better understanding of gradient-based attribution methods for deep neural networks, Marco Ancona et al. 2018](https://openreview.net/pdf?id=Sy21R9JAW)
## License
Captum is BSD licensed, as found in the [LICENSE](LICENSE) file.
| 43.289855 | 495 | 0.758565 | eng_Latn | 0.977296 |
8a830777b5a0d4d7013ebd43586edafa88dd7ee8 | 1,620 | md | Markdown | README.md | TierraAJ/GifTastic | 9070bbc59f8716b5d39db8d6027d738e69a4ce0a | [
"MIT"
] | null | null | null | README.md | TierraAJ/GifTastic | 9070bbc59f8716b5d39db8d6027d738e69a4ce0a | [
"MIT"
] | null | null | null | README.md | TierraAJ/GifTastic | 9070bbc59f8716b5d39db8d6027d738e69a4ce0a | [
"MIT"
] | null | null | null | (Found a Template - Still under construction)
GifTastic
This project demonstrates using Giphy API.
Getting Started
These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See deployment for notes on how to deploy the project on a live system.
Prerequisites
What things you need to install the software and how to install them
Give examples
Installing
A step by step series of examples that tell you how to get a development env running
Say what the step will be
Give the example
And repeat
until finished
End with an example of getting some data out of the system or using it for a little demo
Running the tests
Explain how to run the automated tests for this system
Break down into end to end tests
Explain what these tests test and why
Give an example
And coding style tests
Explain what these tests test and why
Give an example
Deployment
Add additional notes about how to deploy this on a live system
Built With
Dropwizard - The web framework used
Maven - Dependency Management
ROME - Used to generate RSS Feeds
Contributing
Please read CONTRIBUTING.md for details on our code of conduct, and the process for submitting pull requests to us.
Versioning
We use SemVer for versioning. For the versions available, see the tags on this repository.
Authors
Billie Thompson - Initial work - PurpleBooth
See also the list of contributors who participated in this project.
License
This project is licensed under the MIT License - see the LICENSE.md file for details
Acknowledgments
Hat tip to anyone whose code was used
Inspiration
etc
| 27.457627 | 200 | 0.807407 | eng_Latn | 0.999774 |
8a83eada965ba5fc6342b3db2cf1e04189be3530 | 39,100 | md | Markdown | f/flulaermkoelnv/index.md | nnworkspace/gesetze | 1d9a25fdfdd9468952f739736066c1ef76069051 | [
"Unlicense"
] | null | null | null | f/flulaermkoelnv/index.md | nnworkspace/gesetze | 1d9a25fdfdd9468952f739736066c1ef76069051 | [
"Unlicense"
] | null | null | null | f/flulaermkoelnv/index.md | nnworkspace/gesetze | 1d9a25fdfdd9468952f739736066c1ef76069051 | [
"Unlicense"
] | null | null | null | ---
Title: Verordnung über die Festsetzung des Lärmschutzbereichs für den Verkehrsflughafen
Köln/Bonn
jurabk: FluLärmKölnV
layout: default
origslug: flul_rmk_lnv
slug: flulaermkoelnv
---
# Verordnung über die Festsetzung des Lärmschutzbereichs für den Verkehrsflughafen Köln/Bonn (FluLärmKölnV)
Ausfertigungsdatum
: 1975-12-01
Fundstelle
: BGBl I: 1975, 2953
## Eingangsformel
Auf Grund des § 4 Abs. 1 des Gesetzes zum Schutz gegen Fluglärm vom
30\. März 1971 (Bundesgesetzbl. I S. 282), geändert durch Artikel 70
des Einführungsgesetzes zum Strafgesetzbuch vom 2. März 1974
(Bundesgesetzbl. I S. 469), wird im Einvernehmen mit dem
Bundesminister für Verkehr und mit Zustimmung des Bundesrates
verordnet:
## § 1
Zum Schutz der Allgemeinheit vor Gefahren, erheblichen Nachteilen und
erheblichen Belästigungen durch Fluglärm in der Umgebung des
Verkehrsflughafens Köln/Bonn wird der in § 2 bestimmte
Lärmschutzbereich festgesetzt.
## § 2
Der Lärmschutzbereich mit seinen zwei Schutzzonen wird nach Anlage 1
bestimmt durch die interpolierten Verbindungslinien zwischen den
Kurvenpunkten, soweit diese Linien außerhalb des Flugplatzgeländes
verlaufen.
## § 3
(1) Liegt eine bauliche Anlage zu einem Teil im Lärmschutzbereich, so
gilt sie als ganz im Lärmschutzbereich gelegen. Liegt eine bauliche
Anlage zu einem Teil in der Schutzzone 1, so gilt sie als ganz in
dieser Schutzzone gelegen.
(2) Auf die Errichtung einer baulichen Anlage ist Absatz 1
entsprechend anzuwenden.
## § 4
Der nach § 2 bestimmte Lärmschutzbereich ist in einer topographischen
Karte im Maßstab 1:50.000 und in Blättern der Deutschen Grundkarte im
Maßstab 1:5.000 dargestellt. Die topographische Karte ist als Anlage 2
dieser Verordnung beigefügt. Die Blätter der Deutschen Grundkarte sind
beim Regierungspräsidenten Köln, 5 Köln, Zeughausstr. 4 - 8, zu
jedermanns Einsicht archivmäßig gesichert niedergelegt.
## § 5
Diese Verordnung tritt am Tag nach der Verkündung in Kraft.
## Schlußformel
Der Bundesminister des Innern
## Anlage 1 (zu § 2 der Verordnung über die Festsetzung des Lärmschutzbereichs für den Verkehrsflughafen Köln/Bonn)
(Fundstelle des Originaltextes: BGBl. I 1975, 2954 - 2959)
* * **Lärmschutzbereich**
* *
* * Koordinatensystem:
* Gauß-Krüger
* * Interpolation:
* Polynom 3. Grades mit stetigem Tangentenübergang
* *
* * **Kurvenpunkte der Schutzzone 1**
* *
* *
* *
* * Nr.
* Y (Rechts)
* X (Hoch)
* Nr.
* Y (Rechts)
* X (Hoch)
* Nr.
* Y (Rechts)
* X (Hoch)
* *
* * 1
* 2581193.0
* 5638055.9
* 51
* 2582770.9
* 5636206.9
* 101
* 2581624.5
* 5635763.9
* * 2
* 2581202.2
* 5638052.0
* 52
* 2582783.3
* 5636127.9
* 102
* 2581577.5
* 5635828.7
* * 3
* 2581211.5
* 5638048.3
* 53
* 2582791.9
* 5636048.4
* 103
* 2581529.2
* 5635892.5
* * 4
* 2581230.5
* 5638042.0
* 54
* 2582799.6
* 5635968.7
* 104
* 2581485.1
* 5635959.2
* * 5
* 2581268.9
* 5638030.8
* 55
* 2582810.1
* 5635889.4
* 105
* 2581440.1
* 5636025.4
* * 6
* 2581346.8
* 5638012.7
* 56
* 2582827.0
* 5635811.2
* 106
* 2581394.2
* 5636090.9
* * 7
* 2581424.2
* 5637992.3
* 57
* 2582853.4
* 5635735.7
* 107
* 2581347.4
* 5636155.8
* * 8
* 2581500.2
* 5637967.5
* 58
* 2582886.3
* 5635662.8
* 108
* 2581299.7
* 5636220.0
* * 9
* 2581538.9
* 5637957.0
* 59
* 2582920.7
* 5635590.6
* 109
* 2581251.2
* 5636283.6
* * 10
* 2581578.3
* 5637949.8
* 60
* 2582959.1
* 5635520.4
* 110
* 2581201.9
* 5636346.7
* *
* * 11
* 2581618.3
* 5637949.2
* 61
* 2583000.3
* 5635451.7
* 111
* 2581151.9
* 5636409.1
* * 12
* 2581638.2
* 5637950.8
* 62
* 2583043.8
* 5635384.5
* 112
* 2581101.2
* 5636470.9
* * 13
* 2581658.1
* 5637952.7
* 63
* 2583088.5
* 5635318.2
* 113
* 2581049.8
* 5636532.3
* * 14
* 2581676.7
* 5637945.3
* 64
* 2583133.9
* 5635252.3
* 114
* 2580998.1
* 5636593.3
* * 15
* 2581682.7
* 5637937.3
* 65
* 2583179.5
* 5635186.6
* 115
* 2580946.4
* 5636654.3
* * 16
* 2581688.5
* 5637929.2
* 66
* 2583224.9
* 5635120.7
* 116
* 2580894.4
* 5636715.1
* * 17
* 2581683.2
* 5637920.7
* 67
* 2583269.4
* 5635054.2
* 117
* 2580868.1
* 5636745.3
* * 18
* 2581677.0
* 5637912.8
* 68
* 2583311.7
* 5634986.3
* 118
* 2580839.8
* 5636773.5
* * 19
* 2581664.4
* 5637897.3
* 69
* 2583330.7
* 5634951.1
* 119
* 2580807.0
* 5636796.4
* * 20
* 2581642.4
* 5637863.9
* 70
* 2583338.9
* 5634932.9
* 120
* 2580773.9
* 5636819.0
* *
* * 21
* 2581628.9
* 5637826.3
* 71
* 2583344.7
* 5634913.7
* 121
* 2580707.0
* 5636862.8
* * 22
* 2581622.1
* 5637786.8
* 72
* 2583345.2
* 5634903.8
* 122
* 2580639.8
* 5636906.4
* * 23
* 2581620.4
* 5637746.9
* 73
* 2583339.9
* 5634895.3
* 123
* 2580582.0
* 5636961.7
* * 24
* 2581622.6
* 5637706.9
* 74
* 2583329.9
* 5634894.8
* 124
* 2580520.4
* 5637012.6
* * 25
* 2581625.9
* 5637627.0
* 75
* 2583320.2
* 5634897.2
* 125
* 2580486.9
* 5637034.5
* * 26
* 2581627.6
* 5637587.0
* 76
* 2583301.7
* 5634904.9
* 126
* 2580451.6
* 5637053.3
* * 27
* 2581632.8
* 5637547.4
* 77
* 2583267.0
* 5634924.8
* 127
* 2580414.3
* 5637067.9
* * 28
* 2581642.6
* 5637508.6
* 78
* 2583233.7
* 5634946.9
* 128
* 2580375.5
* 5637077.3
* * 29
* 2581661.5
* 5637473.3
* 79
* 2583168.9
* 5634993.8
* 129
* 2580335.7
* 5637081.3
* * 30
* 2581683.2
* 5637439.7
* 80
* 2583105.2
* 5635042.3
* 130
* 2580295.7
* 5637080.1
* *
* * 31
* 2581732.0
* 5637376.3
* 81
* 2583042.0
* 5635091.4
* 131
* 2580256.3
* 5637073.0
* * 32
* 2581785.1
* 5637316.5
* 82
* 2582978.7
* 5635140.4
* 132
* 2580218.9
* 5637058.8
* * 33
* 2581840.4
* 5637258.8
* 83
* 2582915.3
* 5635189.1
* 133
* 2580183.2
* 5637040.8
* * 34
* 2581897.2
* 5637202.4
* 84
* 2582851.1
* 5635236.9
* 134
* 2580150.1
* 5637018.3
* * 35
* 2581955.2
* 5637147.3
* 85
* 2582785.9
* 5635283.2
* 135
* 2580122.1
* 5636989.8
* * 36
* 2582014.1
* 5637093.2
* 86
* 2582719.0
* 5635327.0
* 136
* 2580111.9
* 5636972.6
* * 37
* 2582073.6
* 5637039.6
* 87
* 2582650.0
* 5635367.7
* 137
* 2580105.8
* 5636953.5
* * 38
* 2582134.1
* 5636987.3
* 88
* 2582578.8
* 5635404.0
* 138
* 2580104.8
* 5636933.6
* * 39
* 2582195.4
* 5636935.9
* 89
* 2582507.6
* 5635440.6
* 139
* 2580108.4
* 5636913.9
* * 40
* 2582257.3
* 5636885.2
* 90
* 2582431.9
* 5635466.3
* 140
* 2580115.3
* 5636895.1
* *
* * 41
* 2582319.9
* 5636835.3
* 91
* 2582353.9
* 5635484.1
* 141
* 2580134.8
* 5636860.1
* * 42
* 2582383.2
* 5636786.4
* 92
* 2582274.8
* 5635496.4
* 142
* 2580157.7
* 5636827.3
* * 43
* 2582446.4
* 5636737.4
* 93
* 2582195.5
* 5635507.2
* 143
* 2580209.0
* 5636765.9
* * 44
* 2582507.6
* 5636685.8
* 94
* 2582116.5
* 5635519.7
* 144
* 2580265.0
* 5636708.8
* * 45
* 2582569.9
* 5636635.6
* 95
* 2582038.3
* 5635536.4
* 145
* 2580323.9
* 5636654.6
* * 46
* 2582622.3
* 5636575.2
* 96
* 2581961.3
* 5635558.3
* 146
* 2580352.5
* 5636626.7
* * 47
* 2582664.9
* 5636507.5
* 97
* 2581886.2
* 5635585.8
* 147
* 2580373.1
* 5636592.4
* * 48
* 2582700.7
* 5636436.0
* 98
* 2581813.3
* 5635618.7
* 148
* 2580385.9
* 5636554.5
* * 49
* 2582730.2
* 5636361.6
* 99
* 2581744.0
* 5635658.6
* 149
* 2580391.0
* 5636514.8
* * 50
* 2582753.3
* 5636285.0
* 100
* 2581679.0
* 5635705.3
* 150
* 2580389.4
* 5636474.9
* *
* * noch Schutzzone 1
* *
* * 151
* 2580381.8
* 5636435.6
* 201
* 2579097.8
* 5637534.2
* 251
* 2580086.4
* 5637403.0
* * 152
* 2580376.7
* 5636416.3
* 202
* 2579041.3
* 5637590.9
* 252
* 2580080.1
* 5637422.0
* * 153
* 2580371.5
* 5636396.9
* 203
* 2578984.1
* 5637646.8
* 253
* 2580069.3
* 5637460.5
* * 154
* 2580356.9
* 5636383.3
* 204
* 2578925.8
* 5637701.6
* 254
* 2580048.1
* 5637537.7
* * 155
* 2580339.7
* 5636373.0
* 205
* 2578866.9
* 5637755.7
* 255
* 2580032.0
* 5637574.3
* * 156
* 2580319.8
* 5636371.4
* 206
* 2578837.4
* 5637782.7
* 256
* 2580013.7
* 5637609.9
* * 157
* 2580299.8
* 5636370.6
* 207
* 2578813.7
* 5637814.9
* 257
* 2579990.3
* 5637642.3
* * 158
* 2580259.8
* 5636370.1
* 208
* 2578797.0
* 5637851.3
* 258
* 2579963.8
* 5637672.3
* * 159
* 2580220.2
* 5636375.3
* 209
* 2578787.1
* 5637890.0
* 259
* 2579908.9
* 5637730.5
* * 160
* 2580182.0
* 5636387.2
* 210
* 2578783.6
* 5637929.9
* 260
* 2579852.4
* 5637787.2
* *
* * 161
* 2580147.0
* 5636406.7
* 211
* 2578785.4
* 5637969.8
* 261
* 2579794.9
* 5637842.8
* * 162
* 2580117.6
* 5636433.7
* 212
* 2578788.0
* 5637989.7
* 262
* 2579736.3
* 5637897.2
* * 163
* 2580092.3
* 5636464.7
* 213
* 2578791.7
* 5638009.3
* 263
* 2579676.4
* 5637950.3
* * 164
* 2580066.7
* 5636495.5
* 214
* 2578801.0
* 5638027.0
* 264
* 2579615.6
* 5638002.3
* * 165
* 2580014.3
* 5636555.9
* 215
* 2578812.9
* 5638043.1
* 265
* 2579554.3
* 5638053.6
* * 166
* 2579960.0
* 5636614.7
* 216
* 2578830.5
* 5638052.5
* 266
* 2579491.9
* 5638103.7
* * 167
* 2579903.2
* 5636671.1
* 217
* 2578848.7
* 5638060.8
* 267
* 2579428.6
* 5638152.7
* * 168
* 2579846.1
* 5636727.1
* 218
* 2578886.9
* 5638072.8
* 268
* 2579363.6
* 5638199.2
* * 169
* 2579785.8
* 5636779.7
* 219
* 2578926.7
* 5638076.7
* 269
* 2579297.6
* 5638244.5
* * 170
* 2579752.8
* 5636802.4
* 220
* 2578966.6
* 5638074.0
* 270
* 2579232.8
* 5638291.3
* *
* * 171
* 2579717.2
* 5636820.6
* 221
* 2579005.4
* 5638064.1
* 271
* 2579168.5
* 5638339.0
* * 172
* 2579678.8
* 5636831.7
* 222
* 2579041.5
* 5638046.9
* 272
* 2579114.0
* 5638397.6
* * 173
* 2579639.1
* 5636836.4
* 223
* 2579073.3
* 5638022.6
* 273
* 2579059.2
* 5638455.9
* * 174
* 2579599.1
* 5636835.9
* 224
* 2579097.9
* 5637991.1
* 274
* 2579010.1
* 5638519.1
* * 175
* 2579559.4
* 5636830.8
* 225
* 2579120.8
* 5637958.3
* 275
* 2578973.2
* 5638590.1
* * 176
* 2579520.4
* 5636821.9
* 226
* 2579168.3
* 5637893.9
* 276
* 2578942.5
* 5638664.0
* * 177
* 2579501.2
* 5636816.5
* 227
* 2579217.4
* 5637830.8
* 277
* 2578917.0
* 5638739.8
* * 178
* 2579491.6
* 5636813.6
* 228
* 2579267.2
* 5637768.1
* 278
* 2578896.3
* 5638817.1
* * 179
* 2579481.6
* 5636814.1
* 229
* 2579315.4
* 5637704.3
* 279
* 2578880.7
* 5638895.5
* * 180
* 2579474.3
* 5636821.0
* 230
* 2579361.3
* 5637638.8
* 280
* 2578870.4
* 5638974.9
* *
* * 181
* 2579467.3
* 5636828.1
* 231
* 2579405.6
* 5637572.2
* 281
* 2578865.0
* 5639054.7
* * 182
* 2579455.0
* 5636843.9
* 232
* 2579455.2
* 5637509.4
* 282
* 2578862.9
* 5639134.7
* * 183
* 2579449.9
* 5636852.6
* 233
* 2579509.2
* 5637450.4
* 283
* 2578861.5
* 5639214.6
* * 184
* 2579445.4
* 5636861.6
* 234
* 2579564.9
* 5637392.9
* 284
* 2578857.6
* 5639294.5
* * 185
* 2579453.4
* 5636867.6
* 235
* 2579622.9
* 5637337.9
* 285
* 2578849.7
* 5639374.2
* * 186
* 2579460.9
* 5636874.2
* 236
* 2579684.6
* 5637287.0
* 286
* 2578836.3
* 5639453.0
* * 187
* 2579476.5
* 5636886.7
* 237
* 2579717.4
* 5637264.1
* 287
* 2578814.6
* 5639530.0
* * 188
* 2579505.2
* 5636914.6
* 238
* 2579751.9
* 5637243.7
* 288
* 2578790.1
* 5639606.2
* * 189
* 2579528.0
* 5636947.5
* 239
* 2579788.4
* 5637227.5
* 289
* 2578777.4
* 5639644.1
* * 190
* 2579540.3
* 5636985.5
* 240
* 2579827.2
* 5637217.8
* 290
* 2578766.3
* 5639682.6
* *
* * 191
* 2579538.8
* 5637025.5
* 241
* 2579867.2
* 5637216.6
* 291
* 2578762.6
* 5639702.2
* * 192
* 2579526.2
* 5637063.4
* 242
* 2579906.6
* 5637223.6
* 292
* 2578762.8
* 5639722.2
* * 193
* 2579507.7
* 5637098.9
* 243
* 2579944.4
* 5637236.5
* 293
* 2578766.6
* 5639731.5
* * 194
* 2579486.1
* 5637132.6
* 244
* 2579981.1
* 5637252.5
* 294
* 2578774.6
* 5639737.5
* * 195
* 2579437.3
* 5637196.0
* 245
* 2580016.2
* 5637271.9
* 295
* 2578784.5
* 5639739.0
* * 196
* 2579385.4
* 5637256.8
* 246
* 2580048.1
* 5637290.0
* 296
* 2578794.5
* 5639738.1
* * 197
* 2579331.9
* 5637316.3
* 247
* 2580074.3
* 5637326.3
* 297
* 2578814.0
* 5639733.8
* * 198
* 2579276.7
* 5637374.3
* 248
* 2580083.4
* 5637344.1
* 298
* 2578851.6
* 5639720.1
* * 199
* 2579217.4
* 5637428.0
* 249
* 2580088.7
* 5637363.3
* 299
* 2578888.4
* 5639704.6
* * 200
* 2579156.9
* 5637480.3
* 250
* 2580089.7
* 5637383.3
* 300
* 2578962.1
* 5639673.4
* *
* * noch Schutzzone 1
* *
* * 301
* 2579036.7
* 5639644.6
* 321
* 2580240.8
* 5638996.5
*
*
*
* * 302
* 2579113.9
* 5639623.5
* 322
* 2580289.8
* 5638933.2
*
*
*
* * 303
* 2579192.6
* 5639608.8
* 323
* 2580339.4
* 5638870.4
*
*
*
* * 304
* 2579271.6
* 5639596.8
* 324
* 2580389.8
* 5638808.3
*
*
*
* * 305
* 2579351.1
* 5639587.8
* 325
* 2580440.7
* 5638746.6
*
*
*
* * 306
* 2579430.6
* 5639578.5
* 326
* 2580492.2
* 5638685.4
*
*
*
* * 307
* 2579509.6
* 5639566.0
* 327
* 2580544.2
* 5638624.6
*
*
*
* * 308
* 2579587.7
* 5639548.6
* 328
* 2580596.8
* 5638564.3
*
*
*
* * 309
* 2579664.3
* 5639525.5
* 329
* 2580649.4
* 5638504.1
*
*
*
* * 310
* 2579738.9
* 5639496.7
* 330
* 2580702.6
* 5638444.3
*
*
*
* *
* * 311
* 2579810.9
* 5639461.8
* 331
* 2580756.5
* 5638385.1
*
*
*
* * 312
* 2579879.9
* 5639421.4
* 332
* 2580815.9
* 5638331.5
*
*
*
* * 313
* 2579912.4
* 5639398.1
* 333
* 2580880.3
* 5638284.0
*
*
*
* * 314
* 2579943.9
* 5639373.3
* 334
* 2580946.0
* 5638238.4
*
*
*
* * 315
* 2579971.0
* 5639344.0
* 335
* 2581012.1
* 5638193.4
*
*
*
* * 316
* 2579996.1
* 5639312.8
* 336
* 2581070.1
* 5638138.3
*
*
*
* * 317
* 2580047.3
* 5639251.2
* 337
* 2581133.2
* 5638089.1
*
*
*
* * 318
* 2580098.0
* 5639189.4
* 338
* 2581193.0
* 5638055.9
*
*
*
* * 319
* 2580144.9
* 5639124.5
*
*
*
*
*
*
* * 320
* 2580192.6
* 5639060.3
*
*
*
*
*
*
* *
* * **Kurvenpunkte der Schutzzone 2**
* *
* * 1
* 2581693.6
* 5638529.2
* 51
* 2582550.1
* 5637786.3
* 101
* 2586395.4
* 5632279.5
* * 2
* 2581702.3
* 5638524.3
* 52
* 2582608.2
* 5637731.3
* 102
* 2586499.8
* 5632158.2
* * 3
* 2581711.0
* 5638519.2
* 53
* 2582670.5
* 5637681.1
* 103
* 2586601.6
* 5632034.8
* * 4
* 2581728.5
* 5638509.6
* 54
* 2582735.2
* 5637634.0
* 104
* 2586690.8
* 5631902.0
* * 5
* 2581764.1
* 5638491.4
* 55
* 2582868.9
* 5637546.2
* 105
* 2586784.0
* 5631771.8
* * 6
* 2581837.8
* 5638460.2
* 56
* 2583006.6
* 5637464.5
* 106
* 2586873.3
* 5631639.1
* * 7
* 2581914.4
* 5638437.2
* 57
* 2583144.5
* 5637383.3
* 107
* 2586960.2
* 5631504.7
* * 8
* 2581993.7
* 5638426.7
* 58
* 2583209.0
* 5637336.0
* 108
* 2587044.3
* 5631368.6
* * 9
* 2582073.7
* 5638427.7
* 59
* 2583241.5
* 5637312.8
* 109
* 2587123.0
* 5631229.3
* * 10
* 2582153.0
* 5638438.0
* 60
* 2583274.1
* 5637289.5
* 110
* 2587196.6
* 5631087.2
* *
* * 11
* 2582231.3
* 5638454.7
* 61
* 2583302.0
* 5637260.8
* 111
* 2587228.8
* 5631014.0
* * 12
* 2582309.9
* 5638469.2
* 62
* 2583326.0
* 5637228.8
* 112
* 2587255.8
* 5630938.7
* * 13
* 2582465.2
* 5638507.8
* 63
* 2583348.4
* 5637195.7
* 113
* 2587266.1
* 5630900.0
* * 14
* 2582618.4
* 5638553.9
* 64
* 2583386.5
* 5637125.4
* 114
* 2587269.8
* 5630880.4
* * 15
* 2582769.2
* 5638607.5
* 65
* 2583419.5
* 5637052.5
* 115
* 2587269.8
* 5630860.4
* * 16
* 2582918.5
* 5638665.0
* 66
* 2583451.8
* 5636979.3
* 116
* 2587262.5
* 5630841.8
* * 17
* 2583067.5
* 5638723.5
* 67
* 2583513.0
* 5636831.4
* 117
* 2587252.4
* 5630824.5
* * 18
* 2583216.6
* 5638781.5
* 68
* 2583568.3
* 5636681.2
* 118
* 2587223.7
* 5630796.6
* * 19
* 2583366.3
* 5638838.0
* 69
* 2583611.4
* 5636527.1
* 119
* 2587206.1
* 5630787.2
* * 20
* 2583441.8
* 5638864.5
* 70
* 2583664.7
* 5636376.3
* 120
* 2587187.1
* 5630780.9
* *
* * 21
* 2583479.9
* 5638876.8
* 71
* 2583715.6
* 5636224.6
* 121
* 2587167.1
* 5630781.7
* * 22
* 2583518.3
* 5638888.0
* 72
* 2583766.8
* 5636073.0
* 122
* 2587147.8
* 5630787.0
* * 23
* 2583557.3
* 5638896.7
* 73
* 2583820.8
* 5635922.4
* 123
* 2587128.8
* 5630793.2
* * 24
* 2583577.2
* 5638898.9
* 74
* 2583879.0
* 5635773.3
* 124
* 2587091.6
* 5630807.9
* * 25
* 2583587.2
* 5638898.5
* 75
* 2583942.1
* 5635626.3
* 125
* 2587019.4
* 5630842.4
* * 26
* 2583596.1
* 5638894.0
* 76
* 2584009.6
* 5635481.2
* 126
* 2586949.4
* 5630881.1
* * 27
* 2583595.2
* 5638884.0
* 77
* 2584081.1
* 5635338.0
* 127
* 2586880.9
* 5630922.4
* * 28
* 2583589.5
* 5638875.8
* 78
* 2584159.9
* 5635198.8
* 128
* 2586746.7
* 5631009.6
* * 29
* 2583582.9
* 5638868.3
* 79
* 2584243.3
* 5635062.2
* 129
* 2586614.6
* 5631099.8
* * 30
* 2583568.5
* 5638854.5
* 80
* 2584331.3
* 5634928.6
* 130
* 2586485.0
* 5631193.7
* *
* * 31
* 2583537.5
* 5638829.1
* 81
* 2584422.6
* 5634797.2
* 131
* 2586356.8
* 5631289.3
* * 32
* 2583472.6
* 5638782.3
* 82
* 2584516.7
* 5634667.8
* 132
* 2586229.6
* 5631386.4
* * 33
* 2583406.1
* 5638737.9
* 83
* 2584612.0
* 5634539.2
* 133
* 2586097.3
* 5631476.5
* * 34
* 2583271.4
* 5638651.6
* 84
* 2584710.0
* 5634412.8
* 134
* 2585971.9
* 5631575.9
* * 35
* 2583136.1
* 5638566.1
* 85
* 2584809.7
* 5634287.6
* 135
* 2585847.7
* 5631676.8
* * 36
* 2583001.1
* 5638480.3
* 86
* 2584907.4
* 5634160.8
* 136
* 2585723.3
* 5631777.4
* * 37
* 2582867.5
* 5638392.1
* 87
* 2585000.8
* 5634030.9
* 137
* 2585601.2
* 5631880.9
* * 38
* 2582801.8
* 5638346.3
* 88
* 2585094.6
* 5633901.3
* 138
* 2585480.2
* 5631985.6
* * 39
* 2582737.2
* 5638299.2
* 89
* 2585188.4
* 5633771.7
* 139
* 2585360.1
* 5632091.4
* * 40
* 2582676.9
* 5638246.6
* 90
* 2585281.4
* 5633641.5
* 140
* 2585240.9
* 5632198.1
* *
* * 41
* 2582617.8
* 5638192.6
* 91
* 2585378.5
* 5633514.2
* 141
* 2585122.2
* 5632305.3
* * 42
* 2582564.6
* 5638132.9
* 92
* 2585474.4
* 5633386.2
* 142
* 2585002.8
* 5632411.8
* * 43
* 2582514.3
* 5638070.7
* 93
* 2585572.5
* 5633259.8
* 143
* 2584881.8
* 5632516.6
* * 44
* 2582492.0
* 5638037.5
* 94
* 2585671.9
* 5633134.4
* 144
* 2584760.7
* 5632621.1
* * 45
* 2582475.2
* 5638001.2
* 95
* 2585772.5
* 5633009.9
* 145
* 2584637.6
* 5632723.4
* * 46
* 2582466.9
* 5637962.1
* 96
* 2585874.7
* 5632886.8
* 146
* 2584513.8
* 5632824.7
* * 47
* 2582469.3
* 5637922.2
* 97
* 2585975.9
* 5632762.9
* 147
* 2584388.0
* 5632923.8
* * 48
* 2582481.4
* 5637884.0
* 98
* 2586080.4
* 5632641.6
* 148
* 2584260.9
* 5633020.9
* * 49
* 2582500.4
* 5637848.8
* 99
* 2586186.1
* 5632521.5
* 149
* 2584134.7
* 5633119.3
* * 50
* 2582523.7
* 5637816.4
* 100
* 2586292.4
* 5632401.9
* 150
* 2584009.4
* 5633218.8
* *
* * noch Schutzzone 2
* *
* * 151
* 2583888.5
* 5633323.6
* 201
* 2578955.5
* 5636292.1
* 251
* 2577305.7
* 5639883.9
* * 152
* 2583766.6
* 5633427.2
* 202
* 2578876.0
* 5636301.0
* 252
* 2577309.9
* 5639963.8
* * 153
* 2583642.2
* 5633527.9
* 203
* 2578797.2
* 5636314.9
* 253
* 2577309.9
* 5640043.8
* * 154
* 2583515.8
* 5633626.0
* 204
* 2578719.7
* 5636334.7
* 254
* 2577306.6
* 5640123.8
* * 155
* 2583386.4
* 5633720.1
* 205
* 2578681.6
* 5636346.9
* 255
* 2577286.6
* 5640282.6
* * 156
* 2583253.5
* 5633809.2
* 206
* 2578643.6
* 5636359.4
* 256
* 2577254.8
* 5640439.4
* * 157
* 2583115.8
* 5633890.7
* 207
* 2578606.5
* 5636374.3
* 257
* 2577218.2
* 5640595.2
* * 158
* 2582972.3
* 5633961.5
* 208
* 2578588.6
* 5636383.2
* 258
* 2577180.9
* 5640750.8
* * 159
* 2582822.9
* 5634018.7
* 209
* 2578574.8
* 5636397.7
* 259
* 2577136.6
* 5640904.5
* * 160
* 2582668.5
* 5634060.9
* 210
* 2578570.7
* 5636417.2
* 260
* 2577085.7
* 5641056.2
* *
* * 161
* 2582591.0
* 5634080.7
* 211
* 2578572.2
* 5636437.2
* 261
* 2577029.2
* 5641205.9
* * 162
* 2582514.3
* 5634103.6
* 212
* 2578575.4
* 5636456.9
* 262
* 2576970.5
* 5641354.7
* * 163
* 2582439.4
* 5634131.5
* 213
* 2578582.9
* 5636496.2
* 263
* 2576911.3
* 5641503.4
* * 164
* 2582366.0
* 5634163.4
* 214
* 2578601.7
* 5636574.0
* 264
* 2576884.6
* 5641578.8
* * 165
* 2582293.6
* 5634197.4
* 215
* 2578649.1
* 5636726.8
* 265
* 2576872.9
* 5641617.1
* * 166
* 2582151.0
* 5634270.0
* 216
* 2578668.2
* 5636804.5
* 266
* 2576863.3
* 5641655.9
* * 167
* 2582009.6
* 5634344.8
* 217
* 2578681.3
* 5636883.5
* 267
* 2576857.8
* 5641695.5
* * 168
* 2581866.9
* 5634417.2
* 218
* 2578681.9
* 5636963.5
* 268
* 2576857.5
* 5641715.5
* * 169
* 2581723.9
* 5634489.0
* 219
* 2578670.0
* 5637042.6
* 269
* 2576859.7
* 5641735.4
* * 170
* 2581584.7
* 5634568.2
* 220
* 2578658.6
* 5637081.0
* 270
* 2576865.9
* 5641754.4
* *
* * 171
* 2581440.1
* 5634636.5
* 221
* 2578645.0
* 5637118.6
* 271
* 2576877.1
* 5641771.0
* * 172
* 2581297.0
* 5634708.1
* 222
* 2578626.2
* 5637153.9
* 272
* 2576892.8
* 5641783.3
* * 173
* 2581156.6
* 5634784.8
* 223
* 2578602.9
* 5637186.4
* 273
* 2576911.4
* 5641790.6
* * 174
* 2581086.3
* 5634823.0
* 224
* 2578579.1
* 5637218.5
* 274
* 2576931.1
* 5641794.5
* * 175
* 2581019.8
* 5634867.4
* 225
* 2578525.8
* 5637278.2
* 275
* 2576971.0
* 5641796.9
* * 176
* 2580957.7
* 5634917.9
* 226
* 2578467.7
* 5637333.2
* 276
* 2577011.1
* 5641795.6
* * 177
* 2580898.2
* 5634971.4
* 227
* 2578407.7
* 5637386.1
* 277
* 2577090.9
* 5641790.8
* * 178
* 2580844.5
* 5635030.7
* 228
* 2578291.5
* 5637496.2
* 278
* 2577170.9
* 5641791.1
* * 179
* 2580795.7
* 5635094.1
* 229
* 2578182.3
* 5637613.2
* 279
* 2577210.7
* 5641795.4
* * 180
* 2580745.7
* 5635156.5
* 230
* 2578128.8
* 5637672.6
* 280
* 2577249.9
* 5641803.3
* *
* * 181
* 2580656.4
* 5635289.3
* 231
* 2578079.8
* 5637735.9
* 281
* 2577288.1
* 5641815.1
* * 182
* 2580560.3
* 5635417.3
* 232
* 2578033.8
* 5637801.3
* 282
* 2577324.8
* 5641831.0
* * 183
* 2580458.0
* 5635540.3
* 233
* 2577951.8
* 5637938.7
* 283
* 2577359.7
* 5641850.6
* * 184
* 2580347.1
* 5635655.6
* 234
* 2577881.2
* 5638082.3
* 284
* 2577423.7
* 5641898.7
* * 185
* 2580226.4
* 5635760.7
* 235
* 2577821.0
* 5638230.5
* 285
* 2577482.2
* 5641953.3
* * 186
* 2580098.2
* 5635856.5
* 236
* 2577791.3
* 5638304.8
* 286
* 2577537.5
* 5642011.1
* * 187
* 2579973.3
* 5635956.6
* 237
* 2577761.5
* 5638379.1
* 287
* 2577592.0
* 5642069.7
* * 188
* 2579845.7
* 5636053.1
* 238
* 2577724.6
* 5638450.1
* 288
* 2577651.7
* 5642122.9
* * 189
* 2579782.5
* 5636102.1
* 239
* 2577687.5
* 5638521.0
* 289
* 2577712.3
* 5642175.2
* * 190
* 2579723.3
* 5636155.9
* 240
* 2577615.0
* 5638663.6
* 290
* 2577774.6
* 5642225.3
* *
* * 191
* 2579656.6
* 5636200.1
* 241
* 2577543.9
* 5638806.9
* 291
* 2577840.9
* 5642270.0
* * 192
* 2579584.7
* 5636235.3
* 242
* 2577479.5
* 5638953.4
* 292
* 2577911.1
* 5642308.4
* * 193
* 2579511.1
* 5636266.5
* 243
* 2577427.2
* 5639104.7
* 293
* 2577984.8
* 5642339.6
* * 194
* 2579472.8
* 5636278.3
* 244
* 2577378.2
* 5639257.0
* 294
* 2578061.9
* 5642360.7
* * 195
* 2579435.0
* 5636291.1
* 245
* 2577332.7
* 5639410.4
* 295
* 2578140.8
* 5642374.4
* * 196
* 2579395.3
* 5636296.0
* 246
* 2577311.7
* 5639487.5
* 296
* 2578220.7
* 5642376.9
* * 197
* 2579355.3
* 5636297.6
* 247
* 2577294.2
* 5639565.6
* 297
* 2578300.4
* 5642369.6
* * 198
* 2579275.3
* 5636295.8
* 248
* 2577284.7
* 5639645.0
* 298
* 2578378.5
* 5642352.3
* * 199
* 2579195.4
* 5636291.6
* 249
* 2577287.3
* 5639725.0
* 299
* 2578453.7
* 5642324.9
* * 200
* 2579035.4
* 5636288.8
* 250
* 2577297.2
* 5639804.4
* 300
* 2578523.8
* 5642286.3
* *
* * noch Schutzzone 2
* *
* * 301
* 2578585.5
* 5642235.5
* 321
* 2579476.7
* 5640586.0
* 341
* 2580792.1
* 5639827.3
* * 302
* 2578639.2
* 5642176.1
* 322
* 2579543.0
* 5640541.2
* 342
* 2580824.7
* 5639754.3
* * 303
* 2578681.0
* 5642107.9
* 323
* 2579614.3
* 5640505.0
* 343
* 2580859.4
* 5639682.2
* * 304
* 2578715.2
* 5642035.6
* 324
* 2579688.5
* 5640474.9
* 344
* 2580927.1
* 5639537.2
* * 305
* 2578743.4
* 5641960.7
* 325
* 2579763.2
* 5640446.3
* 345
* 2580997.0
* 5639393.3
* * 306
* 2578766.7
* 5641884.2
* 326
* 2579836.9
* 5640415.3
* 346
* 2581070.1
* 5639251.0
* * 307
* 2578787.0
* 5641806.8
* 327
* 2579912.0
* 5640387.6
* 347
* 2581146.3
* 5639110.3
* * 308
* 2578825.3
* 5641651.3
* 328
* 2579989.3
* 5640366.9
* 348
* 2581227.1
* 5638972.2
* * 309
* 2578865.7
* 5641496.5
* 329
* 2580066.0
* 5640344.4
* 349
* 2581270.0
* 5638904.7
* * 310
* 2578913.5
* 5641343.8
* 330
* 2580215.2
* 5640286.4
* 350
* 2581316.5
* 5638839.6
* *
* * 311
* 2578971.7
* 5641194.8
* 331
* 2580358.7
* 5640215.5
* 351
* 2581372.4
* 5638782.3
* * 312
* 2579005.7
* 5641122.4
* 332
* 2580431.9
* 5640183.4
* 352
* 2581430.3
* 5638727.1
* * 313
* 2579043.7
* 5641052.0
* 333
* 2580503.2
* 5640147.1
* 353
* 2581553.0
* 5638624.3
* * 314
* 2579085.9
* 5640984.0
* 334
* 2580573.0
* 5640108.0
* 354
* 2581617.7
* 5638577.3
* * 315
* 2579136.6
* 5640922.1
* 335
* 2580605.0
* 5640084.0
* 355
* 2581693.6
* 5638529.2
* * 316
* 2579186.3
* 5640859.4
* 336
* 2580635.6
* 5640058.2
*
*
*
* * 317
* 2579238.4
* 5640798.8
* 337
* 2580664.4
* 5640030.5
*
*
*
* * 318
* 2579293.6
* 5640740.9
* 338
* 2580686.8
* 5639997.3
*
*
*
* * 319
* 2579352.1
* 5640686.3
* 339
* 2580708.9
* 5639964.0
*
*
*
* * 320
* 2579413.1
* 5640634.5
* 340
* 2580753.2
* 5639897.2
*
*
*
| 8.352916 | 115 | 0.382711 | yue_Hant | 0.137039 |
8a847bb32313a783c55a1e6290664f93a0d60e83 | 4,253 | md | Markdown | README.md | thealetheia/motor | 4aa7629ed4a6564492e9fa7054e01aa56754ef28 | [
"MIT"
] | 8 | 2021-04-22T16:46:56.000Z | 2022-01-16T13:03:50.000Z | README.md | thealetheia/motor | 4aa7629ed4a6564492e9fa7054e01aa56754ef28 | [
"MIT"
] | 1 | 2020-12-07T10:09:55.000Z | 2020-12-07T10:09:55.000Z | README.md | thealetheia/cutest | 654baf4bdb32c223c8aed8f24659494845c01ac1 | [
"MIT"
] | null | null | null | # Motor
> ⚙️ A set of tools for logging, debugging, and measuring of your code.
```go
package main
import "aletheia.icu/motor"
func main() {
// Motor functions via three three basic output modes.
//
// 1. log() is used for ordinary logs.
// 2. debug() is used when "probing" and debugging.
// 3. trace() is invoked only tracing / benchmarking purposes.
log, debug, trace := motor.New()
// V(2) forces debug mode.
motor.V(2)
log("Hello, world!")
if debug() {
debug("In debug mode.")
n, m := 10, 0
for i := 1; i <= n; i++ {
trace("m (%d) += %d", m, i)
m += i
}
debug("verifying")
debug("m =", m)
debug("m expected =", n*(n+1)/2)
}
}
```
```go
package main
//go:generate go install aletheia.icu/motor/cmd/probe
import (
"strconv"
"testing"
"aletheia.icu/motor"
)
var log, debug, _ = motor.New()
// $ probe tinything [n]
//
func TestTinything(t *testing.T) {
// if not in probe, quit early
if !debug() {
// in general order, by now
// this test would have performed nothing.
return
}
log("Proceed")
// in probe, simply use args to augment the test.
n, _ := strconv.Atoi(motor.Args[0])
log("n = %d", n)
}
```
This repository contains a small Go library, an interface, and two simple command–line tools, [**probe**](#program-probe) and [**speed**](#program-speed).
## Install
```
go get -u aletheia.icu/motor
" optional
go install aletheia.icu/motor/cmd/probe
go install aletheia.icu/motor/cmd/speed
```
## Background
Here's the deal.
I grew accustomed to a certain minimalistic programming style,
Suddenly, everything made sense. No more worries about logging and metrics. I've finally managed to incoroporate unit testing into my development workflow, to the point motor programming should probably look reminiscent of so–called test–driven development, which I learned to hate over the years.
There's nothing worse than `assert(2+2, 4)` and you know it.
I've come to realise that at some point my code becomes aware of its surroundings, be it planned or not. Motor programming model exploits this: there are three output modes, progressively more and more verbose. In normal conditions, my code is expected to run in log(1), debug(2), and sometimes, trace(3) modes.
Now, quantitative analysis of code, benchmarks.
Go can be very progressive in some major respects. For instance, it supports first–class benchmarks via `Benchmark*` functions and go test. Unfortunately, this is simply not enough. Benchmarking becomes overly counter–intuitive to apply in your development workflow the moment you walk out of the _some abstract algorithm in some abstract context_ realm. And it's a good thing. There's no point desperately trying to fit your all–round code into a very square hole that is a benchmark. Quite a lot of it has to do with data locality. In real–life, code components are far from decoupled. It's not so much of a trouble, but inconvenience—to test them as such, without constantly having to fall back and refer to them as the whole. Maybe we're better off performing at least some of the measturements while the code is still running normally? In any case, that's exactly what `speed` does. There are two things you can measure, _∆t_ and _∆d/∆t_. This may not seem like much, but in fact it's all you need. You get time and differential, latency and throughput. Go take some measurements! Good code is traceable, so you should report them over trace(). If the program runs in _speed_, it will trace automatically. The tool will then collect the printed measurements and produce a CSV (comma–separated values) output.
## Usage
Motor is a [no bullshit](https://www.gandi.net/en/no-bullshit) piece of software.
### Program [probe](#probe)
Use program to run an individual probe of a test.
In vim, list all availablte tests with
```
:!probe
TestAlbus
TestBrewer
TestMethod01
TestMethod02
TestZoo
```
Then,
```
:!probe method01
=== RUN TestMethod01
probe complete
--- PASS: TestMethod01 (0.00s)
PASS
ok test 0.083s
```
To run a tracing probe,
```
:!probe method02...
=== RUN TestMethod01
tracing on
% n=1 m=7.083
% n=2 m=9.112
probe complete
--- PASS: TestMethod02 (0.00s)
PASS
ok test 0.180s
```
### Program [speed](#speed)
TBA
## License
MIT
| 29.331034 | 1,313 | 0.716671 | eng_Latn | 0.993262 |
8a8530159cdd496ff2eef88e05291df832da2532 | 1,702 | md | Markdown | api/qsharp/microsoft.quantum.chemistry.jordanwigner._applyjordanwignerpqandpqqrterm_.md | MicrosoftDocs/quantum-docs-pr.tr-TR | 507bdf01149f248e4218691060b82064fb5931bc | [
"CC-BY-4.0",
"MIT"
] | 2 | 2020-05-19T20:14:09.000Z | 2021-02-04T09:19:21.000Z | api/qsharp/microsoft.quantum.chemistry.jordanwigner._applyjordanwignerpqandpqqrterm_.md | MicrosoftDocs/quantum-docs-pr.tr-TR | 507bdf01149f248e4218691060b82064fb5931bc | [
"CC-BY-4.0",
"MIT"
] | null | null | null | api/qsharp/microsoft.quantum.chemistry.jordanwigner._applyjordanwignerpqandpqqrterm_.md | MicrosoftDocs/quantum-docs-pr.tr-TR | 507bdf01149f248e4218691060b82064fb5931bc | [
"CC-BY-4.0",
"MIT"
] | 2 | 2019-11-26T10:16:44.000Z | 2021-11-15T09:09:34.000Z | ---
uid: Microsoft.Quantum.Chemistry.JordanWigner._ApplyJordanWignerPQandPQQRTerm_
title: _ApplyJordanWignerPQandPQQRTerm_ işlemi
ms.date: 1/23/2021 12:00:00 AM
ms.topic: article
qsharp.kind: operation
qsharp.namespace: Microsoft.Quantum.Chemistry.JordanWigner
qsharp.name: _ApplyJordanWignerPQandPQQRTerm_
qsharp.summary: Applies time-evolution by a PQ or PQQR term described by a `GeneratorIndex`.
ms.openlocfilehash: cd4a63378f4e491217a7bb478a8ea3dcce67bc5a
ms.sourcegitcommit: 71605ea9cc630e84e7ef29027e1f0ea06299747e
ms.translationtype: MT
ms.contentlocale: tr-TR
ms.lasthandoff: 01/26/2021
ms.locfileid: "98839562"
---
# <a name="_applyjordanwignerpqandpqqrterm_-operation"></a>_ApplyJordanWignerPQandPQQRTerm_ işlemi
Ad alanı: [Microsoft. hisse. Chemistry. JordanWigner](xref:Microsoft.Quantum.Chemistry.JordanWigner)
Paket: [Microsoft. hisse. Chemistry](https://nuget.org/packages/Microsoft.Quantum.Chemistry)
Bir PQ veya PQQR teriminin bir tarafından tanımlanan zaman gelişimini uygular `GeneratorIndex` .
```qsharp
operation _ApplyJordanWignerPQandPQQRTerm_ (term : Microsoft.Quantum.Simulation.GeneratorIndex, stepSize : Double, qubits : Qubit[]) : Unit is Adj + Ctl
```
## <a name="input"></a>Giriş
### <a name="term--generatorindex"></a>terim: [Generatorındex](xref:Microsoft.Quantum.Simulation.GeneratorIndex)
`GeneratorIndex` PQ veya PQQR terimini temsil etme.
### <a name="stepsize--double"></a>stepSize: [Double](xref:microsoft.quantum.lang-ref.double)
Zaman evrimi süresi.
### <a name="qubits--qubit"></a>qubits: [qubit](xref:microsoft.quantum.lang-ref.qubit)[]
Hamiltonian, qubit.
## <a name="output--unit"></a>Çıkış: [birim](xref:microsoft.quantum.lang-ref.unit)
| 33.372549 | 152 | 0.788484 | yue_Hant | 0.488998 |
8a8568601103e37822388c3ff4ee2ec5666bddbe | 1,482 | md | Markdown | pages/travel_and_lodging.md | ICESAT-2HackWeek/wiki | 73cbfe52c57bfc8c0afcb6d978119a555d5ddfd2 | [
"MIT",
"BSD-3-Clause"
] | null | null | null | pages/travel_and_lodging.md | ICESAT-2HackWeek/wiki | 73cbfe52c57bfc8c0afcb6d978119a555d5ddfd2 | [
"MIT",
"BSD-3-Clause"
] | 1 | 2022-02-26T06:54:05.000Z | 2022-02-26T06:54:05.000Z | pages/travel_and_lodging.md | ICESAT-2HackWeek/wiki | 73cbfe52c57bfc8c0afcb6d978119a555d5ddfd2 | [
"MIT",
"BSD-3-Clause"
] | 2 | 2018-10-30T15:49:28.000Z | 2019-06-12T01:04:04.000Z | ---
title: Travel and Lodging
sidebar: mydoc_sidebar
permalink: travel_and_lodging.html
---
# Travel
Seattle-Tacoma International Airport offers a range of connections to the University of Washington Campus.
The [Link light rail](https://www.soundtransit.org/Schedules/Link-light-rail) is an easy, great way to get to the UW from the airport. It picks you up at the airport, comes about every 5-15 minutes, and drops you off right on the UW campus; just a 15 minute walk from the dorms you will be staying in.
From the arrivals hall at Sea-Tac Airport, follow the signs for Link Light Rail; the station is a short walk from the terminal on the far side of the parking garage. Tickets must be purchased at the station before boarding. The cost is $2.50 and can be paid in cash or with a credit/debit card. Take the train to the last stop (UW). [Here are directions](https://www.google.com/maps/dir/UW+%2F+Husky+Stadium+Link+Station,+Montlake+Boulevard+Northeast,+Seattle,+WA/Lander+Hall,+Northeast+Campus+Parkway,+Seattle,+WA/@47.6528701,-122.3174734,15z/data=!3m1!4b1!4m14!4m13!1m5!1m1!1s0x549014eca005d559:0x2a5b4b6f98dddc9c!2m2!1d-122.3037817!2d47.6498128!1m5!1m1!1s0x549014f3ba755af3:0x942b03c21f9cc45e!2m2!1d-122.3148976!2d47.655826!3e2) walking from the UW link stop to the Lander Hall where you will check in.
Taxis and uber/lyft are also available from the airport. Note that for uber/lyft you will meet the car in the 3rd floor parking lot for pick up.
# Lodging
TBD | 74.1 | 805 | 0.786775 | eng_Latn | 0.988787 |
8a85814b7957d059da6e29f5e491a6b56a9f02e0 | 6,489 | md | Markdown | 2017/2017-12-04-SageTechnologies.md | CrosseyeJack/dmca | 8e99e61d8a5aee2d21b6e9a5e0299a3524a1ef07 | [
"CC-BY-3.0"
] | 4,432 | 2015-01-05T19:30:36.000Z | 2022-03-30T18:15:29.000Z | 2017/2017-12-04-SageTechnologies.md | evido3s/dmca | 1ba09591aaa995f19e84088074924d7120536d41 | [
"CC-BY-3.0"
] | 189 | 2015-03-04T20:55:32.000Z | 2022-03-20T13:11:53.000Z | 2017/2017-12-04-SageTechnologies.md | evido3s/dmca | 1ba09591aaa995f19e84088074924d7120536d41 | [
"CC-BY-3.0"
] | 2,135 | 2015-01-01T12:23:57.000Z | 2022-03-31T18:12:08.000Z | **Are you the copyright owner or authorized to act on the copyright owner's behalf?**
Yes. I am [private] of Sage Technologies.
**Please provide a detailed description of the original copyrighted work that has allegedly been infringed. If possible, include a URL to where it is posted online.**
A few months ago, an employee stole sensitive files from a project we're planning to release on the Christmas day of 2017. The original files are stored [private].
Amber is a security module that was written by me. However, he obtained 1/3 of the original module. As such, this contains enough code to jepordize the security of our systems(read/write access to
our databases). The stolen code found [here](https://github.com/Jeamz/Novo) which contains no public license and shows the copyright notice on the README.md file. Our company-group can be found [here](https://github.com/Sage-io).
All members within that company-group are employees that work for us. As you can see, [private] (Jeamz) is not apart of our company-group.
In conjunction, my IP was posted in the Novo directory. The following files with line
numbers contain my public IP:
- [private]
- [private]
That IP goes straight to my home router and someone could do some serious damage with it. Both "master" and "dev" branches are hereby requested by Sage Technologies LLC to be
taken down immediately. Failure in this solution will result in harsh legal action against [private]. Preferably, I formerly request that both the [repository](https://github.com/Jeamz/Novo)
and [user] (https://github.com/Jeamz) to be terminated immediately. As such, this user was working on many of our porjects all of which are private on his account. In an effort to prevent him from
leaking any or all stolen work, we request that this user is to be terminated immediately. Much of our work is built up or on to by many of our employees. As such, this user could make these
projects public, leak much more sensitive data and shamefully claim credit for all work. This breaks our [NDA][private]
which all employees are required to acknowledge and sign before officially working with us. This document is active from which the time they sign to the time they die.
In an effort to stop cases like this, we've cracked down on our company repo and placed all projects under my own account for close monitoring. It's unclear how many other
projects this user may have. Said user is a risk our systems and data and thus, must be dealt with immediately.
*We have asked [private] (Jeamz) numerous times either by phone(text) or by email. No response.*
**What files should be taken down? Please provide URLs for each file, or if the entire repository, the repository's URL:**
Repository(master & dev branches): https://github.com/Jeamz/Novo
Master Branch - https://github.com/Jeamz/Novo/tree/master
Security Module: https://github.com/Jeamz/Novo/tree/master/amber
SignupController.swift: https://github.com/Jeamz/Novo/blob/master/Novo/SignupController.swift
LoginController.swift: https://github.com/Jeamz/Novo/blob/master/Novo/LoginController.swift
Dev Branch - https://github.com/Jeamz/Novo/tree/dev
All of Sapphire: https://github.com/Jeamz/Novo/tree/dev/Sapphire
All of Novo: https://github.com/Jeamz/Novo/tree/dev/Novo
All of Azure: https://github.com/Jeamz/Novo/tree/dev/Azure
**Have you searched for any forks of the allegedly infringing files or repositories? Each fork is a distinct repository and must be identified separately if you believe it is infringing and wish to have it taken down.**
No forks were found in our search. However, this user may have stolen project files that he made private to prevent us from knowing.
**Is the work licensed under an open source license? If so, which open source license? Are the allegedly infringing files being used under the open source license, or are they in violation of the license?**
Sage Technologies LLC uses github as a way to store our files securely. No one has access to these files but our employees including myself. There is no public open-source license. On the stolen repo our
own [license](https://github.com/Jeamz/Novo/blob/master/LICENSE) can be found. It clear states that you can't steal, copy or publish our code/software.
**What would be the best solution for the alleged infringement? Are there specific changes the other person can make other than removal?**
In both Sage Technologies and [private] (Jeamz) intrest, we formly request that both user [Jeamz] and repository[https://github.com/Jeamz/Novo] are
to be terminated immediately. As stated before, if this doesn't work, we will persue legal action against [private] (Jeamz).
**Do you have the alleged infringer's contact information? If so, please provide it:**
Username: Jeamz
Profile: https://github.com/Jeamz
Full Name: [private]
Address: [private]
Email: [private]
Phone Number: [private]
**Type (or copy and paste) the following statement: "I have a good faith belief that use of the copyrighted materials described above on the infringing web pages is not authorized by the copyright owner, or its agent, or the law. I have taken fair use into consideration."**
I have a good faith belief that use of the copyrighted materials described above on the infringing web pages is not authorized by the copyright owner, or its agent, or the law. I have taken fair use into consideration.
**Type (or copy and paste) the following statement: "I swear, under penalty of perjury, that the information in this notification is accurate and that I am the copyright owner, or am authorized to act on behalf of the owner, of an exclusive right that is allegedly infringed."**
I swear, under penalty of perjury, that the information in this notification is accurate and that I am the copyright owner, or am authorized to act on behalf of the owner, of an exclusive right that is allegedly infringed.
**Please confirm that you have you have read our Guide to Submitting a DMCA Takedown Notice: https://help.github.com/articles/guide-to-submitting-a-dmca-takedown-notice/**
I formerly confirm that I have read Github's guide to Submitting a DMCA Takedown Notice. https://help.github.com/articles/guide-to-submitting-a-dmca-takedown-notice
**So that we can get back to you, please provide either your telephone number or physical address:**
Number: [private]
Address: [private]
**Please type your full legal name below to sign this request:**
[private]
| 87.689189 | 280 | 0.776699 | eng_Latn | 0.999013 |
8a8591838768d700e8b3c8a3556500abef93200c | 3,337 | md | Markdown | packages-next/admin-ui/CHANGELOG.md | yatping/keystone | 9a8e68d60f140c6dbad2bfc3e6987aa474cba75d | [
"MIT"
] | null | null | null | packages-next/admin-ui/CHANGELOG.md | yatping/keystone | 9a8e68d60f140c6dbad2bfc3e6987aa474cba75d | [
"MIT"
] | null | null | null | packages-next/admin-ui/CHANGELOG.md | yatping/keystone | 9a8e68d60f140c6dbad2bfc3e6987aa474cba75d | [
"MIT"
] | null | null | null | # @keystone-next/admin-ui
## 2.0.1
### Patch Changes
- [`39a5890de`](https://github.com/keystonejs/keystone/commit/39a5890de2021b9e32569ce4011c3e2948d4ede6) [#4160](https://github.com/keystonejs/keystone/pull/4160) Thanks [@JedWatson](https://github.com/JedWatson)! - Show a neutral button on the Item form when there are no changes to save
- Updated dependencies [[`344157577`](https://github.com/keystonejs/keystone/commit/344157577aa285b22cd621809a72a540830f47ab), [`ce6b8ebee`](https://github.com/keystonejs/keystone/commit/ce6b8ebeef39f2d22bfc62500a408739a7f1f419), [`6c3b566a1`](https://github.com/keystonejs/keystone/commit/6c3b566a130fa4eb5ae57e638b4cff7a16299998), [`c3e4c1e3f`](https://github.com/keystonejs/keystone/commit/c3e4c1e3fdf8ffdbfd785860c26d15e665c5e25e)]:
- @keystone-ui/[email protected]
- @keystone-ui/[email protected]
- @keystone-ui/[email protected]
- @keystone-ui/[email protected]
- @keystone-ui/[email protected]
- @keystone-ui/[email protected]
## 2.0.0
### Major Changes
- [`ae0fc4d78`](https://github.com/keystonejs/keystone/commit/ae0fc4d787ba47eb9e5258a20a57f76124aee797) [#4132](https://github.com/keystonejs/keystone/pull/4132) Thanks [@mitchellhamilton](https://github.com/mitchellhamilton)! - Remove entrypoint at `@keystone-next/admin-ui` and replace with `@keystone-next/admin-ui/context` and `@keystone-next/pages/*`
### Minor Changes
- [`166acb9bf`](https://github.com/keystonejs/keystone/commit/166acb9bf211e0ee8a90d4740f6ebc54ffe72dec) [#4138](https://github.com/keystonejs/keystone/pull/4138) Thanks [@mitchellhamilton](https://github.com/mitchellhamilton)! - Support uploading files with apollo-upload-client
### Patch Changes
- [`71b74161d`](https://github.com/keystonejs/keystone/commit/71b74161dfc9d7f0b918a3451cf545935afce94d) [#4146](https://github.com/keystonejs/keystone/pull/4146) Thanks [@mitchellhamilton](https://github.com/mitchellhamilton)! - Disable create buttons while create item modal is open
- Updated dependencies [[`ae0fc4d78`](https://github.com/keystonejs/keystone/commit/ae0fc4d787ba47eb9e5258a20a57f76124aee797), [`166acb9bf`](https://github.com/keystonejs/keystone/commit/166acb9bf211e0ee8a90d4740f6ebc54ffe72dec), [`ae0fc4d78`](https://github.com/keystonejs/keystone/commit/ae0fc4d787ba47eb9e5258a20a57f76124aee797), [`166acb9bf`](https://github.com/keystonejs/keystone/commit/166acb9bf211e0ee8a90d4740f6ebc54ffe72dec)]:
- @keystone-next/[email protected]
- @keystone-next/[email protected]
- @keystone-next/[email protected]
## 1.0.0
### Major Changes
- [`9d360a67b`](https://github.com/keystonejs/keystone/commit/9d360a67b69ec38e3018fe132b1e34f24956f86c) [#4106](https://github.com/keystonejs/keystone/pull/4106) Thanks [@mitchellhamilton](https://github.com/mitchellhamilton)! - Initial release
### Patch Changes
- Updated dependencies [[`9d360a67b`](https://github.com/keystonejs/keystone/commit/9d360a67b69ec38e3018fe132b1e34f24956f86c)]:
- @keystone-ui/[email protected]
- @keystone-ui/[email protected]
- @keystone-ui/[email protected]
- @keystone-ui/[email protected]
- @keystone-ui/[email protected]
- @keystone-ui/[email protected]
- @keystone-ui/[email protected]
- @keystone-ui/[email protected]
- @keystone-ui/[email protected]
- @keystone-ui/[email protected]
- @keystone-ui/[email protected]
- @keystone-ui/[email protected]
- @keystone-next/[email protected]
- @keystone-next/[email protected]
| 56.559322 | 436 | 0.76386 | yue_Hant | 0.132108 |
8a85b5689de2b0f941a8f909618b69f4bf313f95 | 4,416 | md | Markdown | doc/getting-started/index.md | bobheadlabs/sourcegraph | 9699b27c150ea30b64abe06e4dfbf6eddc8b71b0 | [
"Apache-2.0"
] | 9,389 | 2016-06-02T08:25:07.000Z | 2022-03-31T05:42:12.000Z | doc/getting-started/index.md | bobheadlabs/sourcegraph | 9699b27c150ea30b64abe06e4dfbf6eddc8b71b0 | [
"Apache-2.0"
] | 26,417 | 2016-06-02T10:01:04.000Z | 2022-03-31T21:51:26.000Z | doc/getting-started/index.md | bobheadlabs/sourcegraph | 9699b27c150ea30b64abe06e4dfbf6eddc8b71b0 | [
"Apache-2.0"
] | 970 | 2016-06-02T14:19:57.000Z | 2022-03-30T09:41:22.000Z | # Using Sourcegraph
Welcome to Sourcegraph!
## What is Sourcegraph?
Sourcegraph is a code search and intelligence tool for developers. It lets you search and explore all of your organization's code on the web, with integrations into your existing tools.
## What does Sourcegraph do?
Sourcegraph's main features are:
- [Code search](#code-search): fast, up-to-date, and scalable, with regexp support on any branch or commit without an indexing delay (and diff search)
- [Code intelligence](#code-intelligence): jump-to-definition, find references, and other smart, IDE-like code browsing features on any branch, commit, or PR/code review
- Easy and secure self-hosted installation (your code never touches our servers)
- [Integrations](#integrations) with code hosts, code review tools, editors, web browsers, etc.
## What do I use Sourcegraph for?
Sourcegraph helps you:
- Find example code
- Explore/read code (including during a code review)
- Debug issues
- Locate a specific piece of code
- Determine the impact of changes
Sourcegraph makes it faster and easier to perform these tasks, for you and everyone else at your organization.
## Who should use Sourcegraph?
All developers, except:
- Sourcegraph is more useful to developers working with larger codebases or teams (15+ developers).
- If you rarely search, read, or review code, you probably won't find Sourcegraph useful. (But you should start reading and reviewing more code!)
## Who else uses Sourcegraph?
In addition to the [companies listed on about.sourcegraph.com](https://about.sourcegraph.com), many large technology companies with 500-15,000+ engineers use Sourcegraph internally.
Also, both Facebook and Google provide an in-house Sourcegraph-like code search and intelligence tool to their employees. A [published research paper from Google](https://static.googleusercontent.com/media/research.google.com/en//pubs/archive/43835.pdf) and a [Google developer survey](https://docs.google.com/document/d/1LQxLk4E3lrb3fIsVKlANu_pUjnILteoWMMNiJQmqNVU/edit#heading=h.xxziwxixfqq3) showed that 98% of developers surveyed consider their Sourcegraph-like internal tool to be critical. Developers use it on average for 5.3 sessions each day. (Facebook's and Google's in-house tools are not available to other companies; use Sourcegraph instead.)
## How do I start using Sourcegraph?
1. [Install Sourcegraph](../admin/install/index.md) inside your organization on your internal code, if nobody else has yet
1. Install and configure the [web browser code host integrations](../integration/browser_extension.md) (recommended)
1. Start searching and browsing code on Sourcegraph by visiting the URL of your organization's internal Sourcegraph instance
1. [Personalize Sourcegraph](personalization/index.md) with themes, quick links, and badges!
You can also try [Sourcegraph.com](https://sourcegraph.com/search), which is a public instance of Sourcegraph for use on open-source code only.
---
## Code intelligence
Sourcegraph gives your development team cross-repository IDE-like features on your code:
- Hover tooltips
- Go-to-definition
- Find references
- Symbol search
Sourcegraph gives you code intelligence in:
- **code files in Sourcegraph's web UI**
- **diffs in your code review tool**, via [integrations](../integration/index.md)
- **code files on your code host**, via [integrations](../integration/index.md)
Read the [code intelligence documentation](../code_intelligence/index.md) to learn more and to set it up.
---
## Code search
Sourcegraph code search is fast, works across all your repositories at any commit, and has no indexing delay. Code search also includes advanced features, including:
- Powerful, flexible query syntax
- Commit diff search
- Commit message search
- Custom search scopes
- Saved search monitoring
Read the [code search documentation](../code_search/index.md) to learn more and discover the full feature set.
---
## Integrations
Sourcegraph allows you to get code intelligence and code search on code files and code review diffs in your code host and review tool. See our [integrations documentation](../integration/index.md) to set up Sourcegraph with your tools and roll it out to your entire team.
| 45.061224 | 655 | 0.782156 | eng_Latn | 0.972366 |
8a865c4a6e2de2017cb80b3742206e5ddbfbc18b | 4,709 | md | Markdown | _posts/2019-07-04-Download-the-pool-party.md | Ozie-Ottman/11 | 1005fa6184c08c4e1a3030e5423d26beae92c3c6 | [
"MIT"
] | null | null | null | _posts/2019-07-04-Download-the-pool-party.md | Ozie-Ottman/11 | 1005fa6184c08c4e1a3030e5423d26beae92c3c6 | [
"MIT"
] | null | null | null | _posts/2019-07-04-Download-the-pool-party.md | Ozie-Ottman/11 | 1005fa6184c08c4e1a3030e5423d26beae92c3c6 | [
"MIT"
] | null | null | null | ---
layout: post
comments: true
categories: Other
---
## Download The pool party book
remove the dust from the space in their path, and the hope of a speedy release the pool party the fetters of the ice. "You're the pool party. Though currently in no condition for boys down there to camp-site sixty-two and ask if I should put the pool party through. Without sigh or complaint, by a quarter of a milliparsec. It happens yearly that Atlantic. PACHTUSSOV'S voyages in 1832-35. So he arose and going in to Shah The pool party, "The Zorphs "An astronaut?" Shaking her head, too, 21--30 930 No hesitation preceded Grace's response? The drapes of decomposition. " bliss was killing, then laughed and ran her hands along the back of a chair. The prisoning spell was still there, the "Tomorrow, but he wasn't a talented enough Sherlock to leap immediately to the meaning of their absence, took a cigarette from an alabaster box and lit it with an alabaster lighter. It was the first time he'd used an obscenity conversationally, he knew that she was chaste of the pool party and body; wherefore he repented with the utmost of repentance and feared for himself from the king and said, she entered anyway. short-winged birds, faded, and shadows spun with shadows? " No some in comparatively recent times? Spetsbergen i Aarene 1827 og 1828_, her energy and skill, as well. But I do have some knowledge that might prove useful. withered his soul if he had possessed a soul. [148] The command of the every day; she smiled rarely and with composure, only thirty-nine, I fear lest the Khalif come to know of this and be wroth with me; so tell me thou what is to be done in this wherewith I am afflicted of the affair of this damsel, dwelled for a long time on the things that had been learned and the transformation of minds that had been brought about since then, he purchased five thousand dollars' worth of cocaine and LSD to establish his credibility, that she us are in entire agreement with your analysis, Harry, boatswain. But this may not be so, under Iria Hill, they will punish you, photographs him. And what I seek, there. moisture. " from the coast to Kandy and other places. To leave Bartholomew. the pool party, still clear of snow, and Leilani goes yikes, she listened to the leaves when the wind rustled them or stormed in the I killed time earlier tonight reading the promo pamphlet on this place, quick and tender as the first flame of a catching fire, and to them he was to drank at once large quantities of it, it shall be prolonged and not curtailed, pie, whereupon the folk dispersed to their dwelling-places and the news was bruited abroad that the king purposed to marry the vizier's daughter Shehrzad, Agnes stiffened, "One idiot who should never have been allowed out of a cage got what he asked for, you wouldn't be able to the pool party it. could she stay with Clarissa?" Aunt Gen suggested! Boetian. " He held audiences, counseling that every child was an individual, haunting out of sheer mean entirely wanting. Was it tomorrow or today. she offered her hand; the pool party younger and more foolish, purifying wells. Neary's statement gives rise to expressions of a the pool party distrust of the government from many in the explained the choices to Amanda as I handed her into the runabout and unplugged the car the pool party its 200 are said to have fallen. Ruggieri, and now gazing up at his mother once more. If you do find him, tools. Singh was uncomfortably the pool party that the idea of a rescue mission had died out only a few years after the initial tragedy. " Micky's hands were cold and moist from the condensation the pool party the Could have used a bottle of that myself last November. I saw here, depends on choosing exactly the roughly-timbered the pool party habitation, I "Ah," said the Patterner. For good reason. Houses made settling noises all the time. At night we lay to at a floe. We now have a fertilized egg cell which open to the north, but kept his wild powers bound with spells until they could make him Sturgeon Lives Comfortably, Nolan knew, it was true: Here he sat in a peculiar what your niece is intending to do up there in Idaho. Some might call it slumming. FOR AMERICANS OF Chinese the pool party San Francisco has a large Chinese population-1965 was the Year of the Snake. "I did chores for her and eventually became a sort of assistant, in order to ascertain the chronometer's rate of going; baby. Quiet. ] the bed, and being the pool party What had it irked them. (_Betula odorata_, the thing that scared her was not the monstrous father of this child. " is mainly characteristic the pool party this stem, however. tufts of white clouds? | 523.222222 | 4,621 | 0.786367 | eng_Latn | 0.999961 |
8a867d38bba5b3963d87ab4c96bbc8f1beda928f | 1,178 | md | Markdown | README.md | simp06/cuponatic_test | 148c2dbdea5deca96b112fbb4b5932f535cc5f8d | [
"MIT"
] | null | null | null | README.md | simp06/cuponatic_test | 148c2dbdea5deca96b112fbb4b5932f535cc5f8d | [
"MIT"
] | null | null | null | README.md | simp06/cuponatic_test | 148c2dbdea5deca96b112fbb4b5932f535cc5f8d | [
"MIT"
] | null | null | null | # Web Service search & stadistic of Product
### Prerequisites
```
PHP 7.0>
MySQL 5.4>
Composer
```
### Installing
Clone Repo in folder project
```
git clone https://github.com/simp06/cuponatic_test /folderProject
```
Install Dependence
```
composer install
```
Create Database
```
mysql>CREATE DATABASE test_cuponatic;
```
Execute to Migration;
```
php artisan migrate --path=/database/migrations/productospalabras/
```
Execute dump csv or execute script dump sql to database (bd_test_cuponatic.sql)
```
mysql>use test_cuponatic;
mysql>LOAD DATA LOCAL INFILE '/PathProject/data_producto.csv'
INTO TABLE producto_test
FIELDS TERMINATED BY ','
ENCLOSED BY '"'
LINES TERMINATED BY '\n'
IGNORE 1 LINES;
```
### Requisites Functions Webservice
*Content-Type Allowed :
```
application/json
```
*Format json
```
{"field":"value"..}
```
## Method Allowed Webservice
```
GET,POST
```
### Metod GET /stadistic
Show 20 product most searched & top 5 word like test
```
//host:PORT/api/stadistic
```
### Metod POST /search
Search product by keyword
```
//host:PORT/api/search
```
### NOTE:File csv to modified and add PK (id_producto) view rootfolderproject/data_producto.csv
| 17.58209 | 95 | 0.720713 | kor_Hang | 0.376191 |
8a86b51e50c4dda2a634299322244a5a94d91750 | 3,626 | md | Markdown | _data/blog/2020-10-07-our-fertility-journey.md | lgschoem/blog-gatsby-delog | 7741a0a289e7414a58507f822fad1fd08792a72d | [
"MIT"
] | null | null | null | _data/blog/2020-10-07-our-fertility-journey.md | lgschoem/blog-gatsby-delog | 7741a0a289e7414a58507f822fad1fd08792a72d | [
"MIT"
] | null | null | null | _data/blog/2020-10-07-our-fertility-journey.md | lgschoem/blog-gatsby-delog | 7741a0a289e7414a58507f822fad1fd08792a72d | [
"MIT"
] | null | null | null | ---
template: BlogPost
path: /our-fertility-journey
date: 2020-10-07T04:46:52.921Z
title: Our Fertility Journey
---
I could not wait to start trying for a baby, so as soon as we were married I came off the pill (in which I had been on for 10+ years). Who knew falling pregnant would be so hard. It took about a year for my hormones to somewhat "balance" themselves out with the help of Jeanette (a functional hormone specialist).
2017 - Still no luck of conceiving, we decided to go down the Calgary Regional Fertility Clinic. I remember being excited, that they must of been the best of the best. Their recommendation seemed to be a cookie cutter approach. Start with Clomid (a drug which helps/stimulates ovulation) along with IUI. We decided to just start with the Clomid on its own at first. We tried 3 cycles of this with again ZERO luck. So next was to try it with an IUI (where sperm is placed directly into the uterus). First try was again unsuccessful, so onto our second IUI. A rollercoaster of emotions, with less hope seen as the first one did not "work". It was Lyntons birthday weekend. We decided to also add pre and post acupuncture, trying to stay "as relax" as possible. Thats what everyone tells you.......don't think about, stress is preventing it from happening. But trust me, that is the last thing you want to hear when you have been trying and waiting soooooo damn long. The weekend after this IUI I was flying out to LA for a bachelotte weekend, I decided not to drink just in case I was pregnant. I had slight cramping/spotting/sore boobs which are all signs of by period coming, but on Day 32 I decided to do a pregnancy test and it was POSITIVE!!! I was over the moon happy, but I think mainly just shocked as we had waited for so long that I couldn't believe it actually happened.
We were so excited but obviously wouldn't proper sink in until be were able to have an ultra sound and see baby. When we finally did baby was so strong and everything seemed healthy and normal. I remember when we got given the scan photo I felt so proud that it was finally my turn to be pregnant and have a baby. It was July 1 (Canada Day) and we had just finished celebrating a day at the lake. Feeling great and actually surprised that I didn't have any spotting all day. On the way home, my funny felt off, like I needed to go to the bathroom. When we arrived home and I on the toilet, I felt like I was bleeding and when I looked down sure enough I saw a giant clot. I was absolutely beside myself, I told Lynton I think we have lost the baby. The midwife said these things can happen and be totally normal and to try and relax and get some rest. At around 4am I started to get bad cramps and I passed another huge clot.....this was not normal, I knew something was wrong. I remember telling Lynton I instantly don't feel pregnant anymore.
After visiting the doctor, we were sent for an urgent Ultra Sound. I was so nervous and scared, I remember when the technician was doing it I was watching Lyntons face to see his reaction, which wasn't what I was expecting. I truly didn't know how I was going to take the news. When the doctor came in to give us the results, my heart drop and never felt so much emotional pain....No heart beat, no baby, nothing was left.
How do you ever get over something like that? Totally out of your control mixed with guilt and something I had done wrong. It was a very dark and sad few days, I have never cried so hard and so much. While reflecting over the next week, I knew that I couldn't let this hold us down, for what ever reason
| 226.625 | 1,397 | 0.76834 | eng_Latn | 0.999978 |
8a892a03ea766e4d3ced82073df688c356ad47a8 | 3,820 | md | Markdown | drafts/polyamory.md | riceissa/issarice.com | 38c8ac68d254db3d53bd93cd71d4df2888530bb4 | [
"CC0-1.0"
] | 12 | 2015-12-18T05:40:50.000Z | 2022-02-01T00:18:04.000Z | drafts/polyamory.md | riceissa/issarice.com | 38c8ac68d254db3d53bd93cd71d4df2888530bb4 | [
"CC0-1.0"
] | 2 | 2020-11-28T10:36:26.000Z | 2021-01-20T19:06:39.000Z | drafts/polyamory.md | riceissa/issarice.com | 38c8ac68d254db3d53bd93cd71d4df2888530bb4 | [
"CC0-1.0"
] | 9 | 2016-08-13T15:02:43.000Z | 2021-02-11T18:14:44.000Z | ---
title: Polyamory
author: Issa Rice
created: 2015-07-25
date: 2015-08-22
status: notes
belief: possible
---
Just some notes for now.
- [gwern comments on Open Thread, February 1\-14, 2012](http://lesswrong.com/lw/9p9/open_thread_february_114_2012/5v6g)
- [File on dropboxusercontent\.com](https://dl.dropboxusercontent.com/u/5317066/2012-gwern-polyamory.txt) (this one talks about Aspergers at the end)
- [What does "experienced polyamorous folk tend to have a lot more practice with explicit communication than the mainstream" mean?](https://www.quora.com/Polyamory/What-does-experienced-polyamorous-folk-tend-to-have-a-lot-more-practice-with-explicit-communication-than-the-mainstream-mean)
- [How common is polyamory among Aspies?](https://www.quora.com/How-common-is-polyamory-among-Aspies)
- [A Nice Thing About Polyamory](http://www.theferrett.com/ferrettworks/2015/01/a-nice-thing-about-polyamory/)
- [Relationship anarchy](!w), or, as [Kaj Sotala says](http://lesswrong.com/lw/2ee/unknown_knowns_why_did_you_choose_to_be_monogamous/27gd), the idea of not needing to "draw a sharp line between romantic partners and close friends" by "[finding] such a division slightly artificial in the first place."
- [Polyhacking](http://lesswrong.com/lw/79x/polyhacking/)
- [Rational Romantic Relationships, Part 1: Relationship Styles and Attraction Basics](http://lesswrong.com/lw/63i/rational_romantic_relationships_part_1/)
- [Unknown knowns: Why did you choose to be monogamous?](http://lesswrong.com/lw/2ee/unknown_knowns_why_did_you_choose_to_be_monogamous/)
- From [a comment](http://lesswrong.com/lw/2ee/unknown_knowns_why_did_you_choose_to_be_monogamous/27hz):
- [Polyamory FAQ \- More Than Two](https://www.morethantwo.com/polyamory.html)
- [alt\.polyamory Frequently Asked Questions \(FAQ\)](http://www.faqs.org/faqs/polyamory/faq/)
- See also gwern in [The Melancholy of Subculture Society](http://www.gwern.net/The%20Melancholy%20of%20Subculture%20Society#fn18):
> It’s something of a mystery why
> [monogamy](http://en.wikipedia.org/wiki/monogamy "Wikipedia: monogamy")
> has thrived over the last millennium - why *not* allow
> [polygyny](http://en.wikipedia.org/wiki/polygyny "Wikipedia: polygyny"),
> [polyandry](http://en.wikipedia.org/wiki/polyandry "Wikipedia: polyandry"),
> both
> ([polygamy](http://en.wikipedia.org/wiki/polygamy "Wikipedia: polygamy"))
> or even full blown
> [polyamory](http://en.wikipedia.org/wiki/polyamory "Wikipedia: polyamory")?
> Why restrict freedom in this regard, restrict it so viciously that
> society is willing to kill over it? One explanation I find appealing
> suggests that marriage - sex - may be an example of societies
> encouraging the formation of more-optimal *multiple* hierarchies of
> status as opposed to a single one. To very broadly generalize, those
> alternatives seem to boil down to polygyny (polyandry being very rare)
> and polygyny seems to correlate with societies where there are few ways
> to status but violence & hunting, while monogamy encourages males to
> engage in economic competition for mates
Related is [a comment by Wei Dai](http://lesswrong.com/lw/2ee/unknown_knowns_why_did_you_choose_to_be_monogamous/27d4) and Tertilt's [PDF on berkeley\.edu](http://eml.berkeley.edu/~webfac/bardhan/e271_f05/tertilt.pdf) that is linked.
- Hmm I also want to talk about this in the context of e.g. [decline in traditional romantic relationships](http://www.webcitation.org/query?url=http%3A%2F%2Fwww.theguardian.com%2Fworld%2F2013%2Foct%2F20%2Fyoung-people-japan-stopped-having-sex&date=2014-11-16)
- [Polyamory vs monoamory and following up](https://www.facebook.com/vipulnaik.r/posts/10208711835929206), a discussion on Vipul Naik's Facebook wall
| 76.4 | 302 | 0.764398 | eng_Latn | 0.873604 |
8a899999e15c845a3113a7d1b1af1c6ecc6f0217 | 5,365 | md | Markdown | README.md | rosscm/multiGIviewer | 351f5a1291f161c315679ceebc9c4ce110812ab2 | [
"MIT"
] | null | null | null | README.md | rosscm/multiGIviewer | 351f5a1291f161c315679ceebc9c4ce110812ab2 | [
"MIT"
] | null | null | null | README.md | rosscm/multiGIviewer | 351f5a1291f161c315679ceebc9c4ce110812ab2 | [
"MIT"
] | null | null | null |
<div align="center">
# multiGIviewer
An interactive R {shiny} web application built with the {golem}
framework to view multi-screen genetic interaction data
<div align="left">
# Contents
- [Usage](#usage)
- [Inputs](#inputs)
- [Outputs](#outputs)
# Usage
Watch this short demo on how to use `multiGIviewer` to view replicated
genetic interactions (qGI scores) across two or more CRISPR screens of
interest.
# Inputs
| Parameters | Values | Properties |
|-------------------------|--------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| **Dataset** | GIN\_20210406, GIN\_20210107, GIN\_20201129, CHEM\_20210218, CHEM\_20210218\_GIN\_20210406 | qGI scores for 280 (GIN\_20210406), 257 (GIN\_20210107), 247 (GIN\_20201129), 68 (CHEM\_20210218), 348 (CHEM\_20210218) & (GIN\_20210406) screens \[*required*; default GIN\_20210406\] |
| **Screens** | screens IDs | list of all screens in selected dataset; two or more screens need to be selected to view replicated interactions \[*required*\] |
| **Media conditions(s)** | min, rich, pyro and/or DMSO | media type used to define wildtype single mutant fitness; more than one can be selected if screens were done in different media types \[*required*\] |
| **FDR threshold** | value from 0 to 1 | threshold to define significant genetic interactions; interactions must pass threshold in at least two screens to be shown \[*required*; default 0.2\] |
| **Positive colour** | HEX colour codes | colour to fill darkest positive points \[*optional*; default `#FAE057`\] |
| **Negative colour** | HEX colour codes | colour to fill darkest negative points \[*optional*; default `#61C2FA`\] |
| **Plot labels** | gene symbols | comma separated (character sensitive) list of genes to label on plot \[*optional*; default top ten positive and negative interactions\] |
| **Label type** | Text or Padded box | method to draw plot labels; padded box wraps text in a white box to better visualize labels \[*optional*; default Text\] |
| **Reference line(s)** | y=x, x=0 and/or y=0 | selection of reference lines to draw on plot \[*optional*\] |
# Outputs
#### Plot
| Elements | Properties |
|---------------------------------------------|------------------------------------|
| **Fitness HAP1 wildtype \[LFC\] (x-axis)** | corresponds to `mean_wtLFC` column |
| **Fitness HAP1 knockout \[LFC\] (y-axis)** | corresponds to `mean_koLFC` column |
| **Genetic interaction in n screens (fill)** | corresponds to `n_sig` column |
| **Mean qGI score (size)** | corresponds to `mean_qGI` column |
#### Table
| Columns | Properties |
|-----------------|-----------------------------------------------------------------------------------------|
| **gene** | gene interaction |
| **mean\_qGI** | mean qGI score of interaction across selected screens |
| **min\_FDR** | minimum qGI FDR value of interaction across selected screens |
| **mean\_wtLFC** | mean wildtype dropout effect (log2-foldchange) across selected media condition(s) |
| **mean\_koLFC** | mean knockout dropout effect (log2-foldchange) across selected screens |
| **n\_sig** | number of times positive or negative interaction is significant across selected screens |
| **screen\_sig** | list of screens where interaction is significant |
| 87.95082 | 306 | 0.399068 | eng_Latn | 0.908285 |
8a8a295a8f3aad459c993340809c1fbf25e91d7c | 186 | md | Markdown | docs/compose/compose/danbroid.util.compose/-material-colors/yellow500.md | danbrough/util | 2a3ae340114d1cf8b96aceeddcc62a0057d4ef3e | [
"Apache-2.0"
] | null | null | null | docs/compose/compose/danbroid.util.compose/-material-colors/yellow500.md | danbrough/util | 2a3ae340114d1cf8b96aceeddcc62a0057d4ef3e | [
"Apache-2.0"
] | null | null | null | docs/compose/compose/danbroid.util.compose/-material-colors/yellow500.md | danbrough/util | 2a3ae340114d1cf8b96aceeddcc62a0057d4ef3e | [
"Apache-2.0"
] | null | null | null | //[compose](../../../index.md)/[danbroid.util.compose](../index.md)/[MaterialColors](index.md)/[yellow500](yellow500.md)
# yellow500
[androidJvm]\
val [yellow500](yellow500.md): Color
| 26.571429 | 120 | 0.688172 | eng_Latn | 0.120209 |
8a8a720d0b13c017fbb3c20c3b46c5e5f61e9b0e | 2,235 | md | Markdown | docs/2014/integration-services/lesson-4-2-creating-a-corrupted-file.md | keunyop/sql-docs.ko-kr | ebbdcd44eebf4861c9ea9a8c13de6c2098b9f539 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2019-12-04T01:36:20.000Z | 2019-12-04T01:36:20.000Z | docs/2014/integration-services/lesson-4-2-creating-a-corrupted-file.md | keunyop/sql-docs.ko-kr | ebbdcd44eebf4861c9ea9a8c13de6c2098b9f539 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/2014/integration-services/lesson-4-2-creating-a-corrupted-file.md | keunyop/sql-docs.ko-kr | ebbdcd44eebf4861c9ea9a8c13de6c2098b9f539 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: '2단계: 손상된 된 파일 만들기 | Microsoft Docs'
ms.custom: ''
ms.date: 06/13/2017
ms.prod: sql-server-2014
ms.reviewer: ''
ms.technology: integration-services
ms.topic: conceptual
ms.assetid: cd0b18dc-66c3-4d88-86ef-8e40cb660fae
author: janinezhang
ms.author: janinez
manager: craigg
ms.openlocfilehash: fa1bb23843447cc77276a34d5466d417f2a87a05
ms.sourcegitcommit: 5a8678bf85f65be590676745a7fe4fcbcc47e83d
ms.translationtype: MT
ms.contentlocale: ko-KR
ms.lasthandoff: 03/22/2019
ms.locfileid: "58393351"
---
# <a name="step-2-creating-a-corrupted-file"></a>2단계: 손상된 파일 만들기
변환 오류의 구성 및 처리를 보여 주기 위해 처리 시 구성 요소의 실패를 야기하는 예제 플랫 파일을 만들어야 합니다.
이 태스크에서는 기존 예제 플랫 파일의 복사본을 만듭니다. 그런 다음 메모장에서 해당 파일을 열고 변환 조회를 수행하는 동안 일치 항목을 생성하지 못하도록 **CurrencyID** 열을 편집합니다. 이 새 파일을 처리하면 조회 실패로 Currency Key Lookup 변환이 실패하며 따라서 패키지의 나머지 부분도 실패합니다. 손상된 예제 파일을 만든 다음에는 패키지를 실행하여 패키지 오류를 봅니다.
### <a name="to-create-a-corrupted-sample-flat-file"></a>손상된 예제 플랫 파일을 만들려면
1. 메모장이나 기타 텍스트 편집기에서 Currency_VEB.txt 파일을 엽니다.
예제 데이터는 SSIS 단원 패키지에 포함되어 있습니다. 예제 데이터 및 단원 패키지를 다운로드하려면 다음을 수행합니다.
1. [Integration Services 제품 예제](https://go.microsoft.com/fwlink/?LinkID=267527)로 이동합니다.
2. **DOWNLOADS** 탭을 클릭합니다.
3. SQL2012.Integration_Services.Create_Simple_ETL_Tutorial.Sample.zip 파일을 클릭합니다.
2. 텍스트 편집기의 찾기 및 바꾸기의 모든 인스턴스를 찾으려면 기능 사용 `VEB` 로 바꿉니다 `BAD`합니다.
3. 다른 샘플 데이터 파일과 동일한 폴더에서 수정 된 파일을 저장 `Currency_BAD.txt`합니다.
> [!IMPORTANT]
> 했는지 `Currency_BAD.txt` 다른 샘플 데이터 파일과 동일한 폴더에 저장 됩니다.
4. 텍스트 편집기를 닫습니다.
### <a name="to-verify-that-an-error-will-occur-during-run-time"></a>런타임 도중 오류가 발생하는지 확인하려면
1. **디버그** 메뉴에서 **디버깅 시작**을 클릭합니다.
세 번째 데이터 흐름 반복에서 Lookup Currency Key 변환은 Currency_BAD.txt 파일을 처리하려고 하며 여기서 변환이 실패합니다. 변환 실패로 인해 전체 패키지가 실패하게 됩니다.
2. **디버그** 메뉴에서 **디버깅 중지**를 클릭합니다.
3. 디자인 화면에서 **실행 결과** 탭을 클릭합니다.
4. 로그를 찾아보고 다음의 처리되지 않은 오류가 발생했는지 확인합니다.
`[Lookup Currency Key[27]] Error: Row yielded no match during lookup.`
> [!NOTE]
> 27은 구성 요소의 ID입니다. 이 값은 데이터 흐름을 작성할 때 할당되며 패키지 값과 다를 수 있습니다.
## <a name="next-steps"></a>다음 단계
[3단계: 오류 흐름 리디렉션 추가](lesson-4-3-adding-error-flow-redirection.md)
| 33.358209 | 229 | 0.677852 | kor_Hang | 1.000004 |
8a8a8b827c6705cd2ca317afad7845a635838167 | 2,194 | md | Markdown | curriculum/challenges/chinese/03-front-end-libraries/react-and-redux/extract-state-logic-to-redux.md | lucassorenson/freeCodeCamp | d58d37ff98b73434d0747a3215dfedfbaf12db8e | [
"BSD-3-Clause"
] | 4 | 2021-01-13T19:56:42.000Z | 2021-01-13T19:57:45.000Z | curriculum/challenges/chinese/03-front-end-libraries/react-and-redux/extract-state-logic-to-redux.md | lucassorenson/freeCodeCamp | d58d37ff98b73434d0747a3215dfedfbaf12db8e | [
"BSD-3-Clause"
] | 789 | 2020-10-09T18:48:14.000Z | 2022-03-28T13:33:21.000Z | curriculum/challenges/chinese/03-front-end-libraries/react-and-redux/extract-state-logic-to-redux.md | majacQ/freeCodeCamp | b1533c217f1e688f47093f28dbc7cd8af010eb8e | [
"BSD-3-Clause"
] | 1 | 2021-08-16T18:23:32.000Z | 2021-08-16T18:23:32.000Z | ---
id: 5a24c314108439a4d4036143
title: 提取状态逻辑给 Redux
challengeType: 6
forumTopicId: 301429
dashedName: extract-state-logic-to-redux
---
# --description--
完成 React 组件后，我们需要把在本地`状态`执行的逻辑移到 Redux 中，这是为小规模 React 应用添加 Redux 的第一步。该应用的唯一功能是把用户的新消息添加到无序列表中。下面我们用简单的示例来演示 React 和 Redux 之间的配合。
# --instructions--
首先，定义 action 的类型 'ADD'，将其设置为常量`ADD`。接着，定义创建 action 的函数`addMessage()`，用该函数创建添加消息的 action，把`message`传给创建 action 的函数并返回包含该消息的`action`
接着，创建名为`messageReducer()`的 reducer 方法，为这些消息处理状态。初始状态应为空数组。reducer 向状态中的消息数组添加消息，或返回当前状态。最后，创建 Redux store 并传给 reducer。
# --hints--
应存在一个值为字符串`ADD`的常量`ADD`。
```js
assert(ADD === 'ADD');
```
创建 action 的函数`addMessage`应返回`type`等于`ADD`的对象，其返回的消息即被传入的消息。
```js
assert(
(function () {
const addAction = addMessage('__TEST__MESSAGE__');
return addAction.type === ADD && addAction.message === '__TEST__MESSAGE__';
})()
);
```
`messageReducer`应是一个函数。
```js
assert(typeof messageReducer === 'function');
```
存在一个 store 且其初始状态为空数组。
```js
assert(
(function () {
const initialState = store.getState();
return typeof store === 'object' && initialState.length === 0;
})()
);
```
分发`addMessage`到 store 应添加新消息到状态中消息数组。
```js
assert(
(function () {
const initialState = store.getState();
const isFrozen = DeepFreeze(initialState);
store.dispatch(addMessage('__A__TEST__MESSAGE'));
const addState = store.getState();
return isFrozen && addState[0] === '__A__TEST__MESSAGE';
})()
);
```
`messageReducer`被其它任何 actions 调用时应返回当前状态。
```js
assert(
(function () {
const addState = store.getState();
store.dispatch({ type: 'FAKE_ACTION' });
const testState = store.getState();
return addState === testState;
})()
);
```
# --seed--
## --seed-contents--
```jsx
// Define ADD, addMessage(), messageReducer(), and store here:
```
# --solutions--
```jsx
const ADD = 'ADD';
const addMessage = (message) => {
return {
type: ADD,
message
}
};
const messageReducer = (state = [], action) => {
switch (action.type) {
case ADD:
return [
...state,
action.message
];
default:
return state;
}
};
const store = Redux.createStore(messageReducer);
```
| 18.913793 | 130 | 0.659982 | kor_Hang | 0.288367 |
8a8aad2214ea78b371a679940a55e6f7edafbaba | 1,975 | md | Markdown | _containers/jlboat-BioinfoContainers-finestructure.md | singularityhub/singularityhub-archive | dd1d471db0c4ac01998cb84bd1ab82e97c8dab65 | [
"ECL-2.0",
"Apache-2.0"
] | null | null | null | _containers/jlboat-BioinfoContainers-finestructure.md | singularityhub/singularityhub-archive | dd1d471db0c4ac01998cb84bd1ab82e97c8dab65 | [
"ECL-2.0",
"Apache-2.0"
] | null | null | null | _containers/jlboat-BioinfoContainers-finestructure.md | singularityhub/singularityhub-archive | dd1d471db0c4ac01998cb84bd1ab82e97c8dab65 | [
"ECL-2.0",
"Apache-2.0"
] | null | null | null | ---
id: 8821
name: "jlboat/BioinfoContainers"
branch: "master"
tag: "finestructure"
commit: "5f15386e1057282311ce1b4a7cae3f747425ed6b"
version: "2440a75a4d72c1613ffa08b4a2ccfeb9"
build_date: "2019-05-08T15:11:14.149Z"
size_mb: 660
size: 226115615
sif: "https://datasets.datalad.org/shub/jlboat/BioinfoContainers/finestructure/2019-05-08-5f15386e-2440a75a/2440a75a4d72c1613ffa08b4a2ccfeb9.simg"
datalad_url: https://datasets.datalad.org?dir=/shub/jlboat/BioinfoContainers/finestructure/2019-05-08-5f15386e-2440a75a/
recipe: https://datasets.datalad.org/shub/jlboat/BioinfoContainers/finestructure/2019-05-08-5f15386e-2440a75a/Singularity
collection: jlboat/BioinfoContainers
---
# jlboat/BioinfoContainers:finestructure
```bash
$ singularity pull shub://jlboat/BioinfoContainers:finestructure
```
## Singularity Recipe
```singularity
Bootstrap: docker
From: ubuntu:latest
%help
Commands on PATH:
beagle2chromopainter.pl
chromopainter2chromopainterv2.pl
convertrecfile.pl
finestructuregreedy.sh
impute2chromopainter.pl
makeuniformrecfile.pl
msms2cp.pl
phasescreen.pl
phasesubsample.pl
plink2chromopainter.pl
qsub_run.sh
%environment
export PATH=$PATH:/opt/fs_4.0.1/
%post
apt-get update --fix-missing && apt-get install -y wget make libgsl-dev unzip automake libwxgtk3.0-dev wx-common build-essential
cpan -f Switch
cd /opt
wget https://people.maths.bris.ac.uk/~madjl/finestructure/fs_4.0.1.zip
unzip fs_4.0.1.zip
#wget https://people.maths.bris.ac.uk/~madjl/finestructure/finestructure-0.1.0GUI.tar.gz
#tar -xzvf finestructure-0.1.0GUI.tar.gz
#cd finestructure-0.1.0/gui
#./configure
#make
#make install
chmod -R 777 /opt/fs_4.0.1/
%runscript
exec "$@"
```
## Collection
- Name: [jlboat/BioinfoContainers](https://github.com/jlboat/BioinfoContainers)
- License: [MIT License](https://api.github.com/licenses/mit)
| 28.214286 | 146 | 0.736709 | yue_Hant | 0.219628 |
8a8c18bef7979181536e71c5f549bdf3eda58a22 | 2,176 | md | Markdown | content/enterprise_influxdb/v1.8/administration/security.md | clwluvw/docs-v2 | dc0c00fb59edd1580198242cb15109a01dfe40cc | [
"MIT"
] | 42 | 2019-10-14T18:38:17.000Z | 2022-03-29T15:34:49.000Z | content/enterprise_influxdb/v1.8/administration/security.md | clwluvw/docs-v2 | dc0c00fb59edd1580198242cb15109a01dfe40cc | [
"MIT"
] | 1,870 | 2019-10-14T17:03:50.000Z | 2022-03-30T22:23:24.000Z | content/enterprise_influxdb/v1.8/administration/security.md | clwluvw/docs-v2 | dc0c00fb59edd1580198242cb15109a01dfe40cc | [
"MIT"
] | 181 | 2019-11-08T19:40:05.000Z | 2022-03-25T10:01:02.000Z | ---
title: Manage security in InfluxDB Enterprise
description: Protect the data in your InfluxDB Enterprise instance.
menu:
enterprise_influxdb_1_8:
name: Manage security
weight: 110
parent: Administration
---
Some customers may choose to install InfluxDB Enterprise with public internet access, however doing so can inadvertently expose your data and invite unwelcome attacks on your database.
Check out the sections below for how protect the data in your InfluxDB Enterprise instance.
## Enable authentication
Password protect your InfluxDB Enterprise instance to keep any unauthorized individuals
from accessing your data.
Resources:
[Set up Authentication](/influxdb/v1.8/administration/authentication_and_authorization/#set-up-authentication)
## Manage users and permissions
Restrict access by creating individual users and assigning them relevant
read and/or write permissions.
Resources:
[User types and privileges](/influxdb/v1.8/administration/authentication_and_authorization/#user-types-and-privileges),
[User management commands](/influxdb/v1.8/administration/authentication_and_authorization/#user-management-commands),
[Fine-grained authorization](/enterprise_influxdb/v1.8/guides/fine-grained-authorization/)
## Enable HTTPS
Using HTTPS secures the communication between clients and the InfluxDB server, and, in
some cases, HTTPS verifies the authenticity of the InfluxDB server to clients (bi-directional authentication).
The communicatio between the meta nodes and the data nodes are also secured via HTTPS.
Resources:
[Enabling HTTPS](/enterprise_influxdb/v1.8/guides/https_setup/)
## Secure your host
### Ports
For InfluxDB Enterprise data nodes, close all ports on each host except for port `8086`.
You can also use a proxy to port `8086`. By default, data nodes and meta nodes communicate with each other over '8088','8089',and'8091'
For InfluxDB Enterprise, [backing up and restoring](/enterprise_influxdb/v1.8/administration/backup-and-restore/) is performed from the meta nodes.
### AWS Recommendations
InfluxData recommends implementing on-disk encryption; InfluxDB does not offer built-in support to encrypt the data.
| 40.296296 | 184 | 0.808364 | eng_Latn | 0.972722 |
8a8c505acaefba93f2ed23c11d6671c70417c548 | 140 | md | Markdown | Readme.md | wirster/zderweapp | d37dab12de0924647360ed32f950e3814d729903 | [
"MIT"
] | null | null | null | Readme.md | wirster/zderweapp | d37dab12de0924647360ed32f950e3814d729903 | [
"MIT"
] | null | null | null | Readme.md | wirster/zderweapp | d37dab12de0924647360ed32f950e3814d729903 | [
"MIT"
] | null | null | null | 微信小程序编译预览模式
# npm script
$ npm run dev:weapp
# 仅限全局安装
$ taro build --type weapp --watch
# npx 用户也可以使用
$ npx taro build --type weapp --watch
| 17.5 | 37 | 0.707143 | eng_Latn | 0.37959 |
8a8d038e8e60d2d098f2b8693962bf1af1140381 | 906 | md | Markdown | STL_1/code/README.md | code-abil/CP-ClassNotes | 3168a7b324eb0fc6f51dfe3d93a67ed812be8e0d | [
"MIT"
] | null | null | null | STL_1/code/README.md | code-abil/CP-ClassNotes | 3168a7b324eb0fc6f51dfe3d93a67ed812be8e0d | [
"MIT"
] | null | null | null | STL_1/code/README.md | code-abil/CP-ClassNotes | 3168a7b324eb0fc6f51dfe3d93a67ed812be8e0d | [
"MIT"
] | null | null | null | ### Contents
1. [test1.cpp](https://github.com/code-abil/CP-ClassNotes/blob/master/STL_1/code/test1.cpp) ==> Iterators, auto keyword, set, multiset, traversals, map, string.
2. [test2.cpp](https://github.com/code-abil/CP-ClassNotes/blob/master/STL_1/code/test2.cpp) ==> set, Skewed BST
3. [test3.cpp](https://github.com/code-abil/CP-ClassNotes/blob/master/STL_1/code/test3.cpp) ==> 2D Vectors
4. [pairs.cpp](https://github.com/code-abil/CP-ClassNotes/blob/master/STL_1/code/pairs.cpp) ==> pairs, 1ex form
5. [deque.cpp](https://github.com/code-abil/CP-ClassNotes/blob/master/STL_1/code/deque.cpp)
6. [queue.cpp](https://github.com/code-abil/CP-ClassNotes/blob/master/STL_1/code/queue.cpp)
7. [stack.cpp](https://github.com/code-abil/CP-ClassNotes/blob/master/STL_1/code/stack.cpp)
8. [vectors.cpp](https://github.com/code-abil/CP-ClassNotes/blob/master/STL_1/code/vectors.cpp) ==> Vector initialisations.
| 90.6 | 160 | 0.746137 | yue_Hant | 0.392209 |
8a8d66cc1b8c5bdd197b141295615858346987de | 279 | md | Markdown | _posts/2012-03-13-t179564928955457539.md | craigwmcclellan/craigmcclellan.github.io | bd9432ea299f1141442b9ba90eb3aa001984c20d | [
"MIT"
] | 1 | 2018-08-04T15:31:00.000Z | 2018-08-04T15:31:00.000Z | _posts/2012-03-13-t179564928955457539.md | craigwmcclellan/craigmcclellan.github.io | bd9432ea299f1141442b9ba90eb3aa001984c20d | [
"MIT"
] | null | null | null | _posts/2012-03-13-t179564928955457539.md | craigwmcclellan/craigmcclellan.github.io | bd9432ea299f1141442b9ba90eb3aa001984c20d | [
"MIT"
] | 1 | 2018-08-04T15:31:03.000Z | 2018-08-04T15:31:03.000Z | ---
layout: post
microblog: true
audio:
photo:
date: 2012-03-13 07:49:49 -0600
guid: http://craigmcclellan.micro.blog/2012/03/13/t179564928955457539.html
---
Second married birthday. Second breakfast in bed. @laura_mcclellan is the best. [t.co/ODRFlOU4](http://t.co/ODRFlOU4)
| 27.9 | 118 | 0.74552 | eng_Latn | 0.30111 |
8a8e40cf53950e091eafe8e6de1a463b80d203cb | 824 | md | Markdown | _mentors/mentor_3.md | govhackaustralia/project-jabberwocky-poc | 5ff4193c84018aac93740b6296ae81be2bd629ab | [
"CC-BY-4.0"
] | null | null | null | _mentors/mentor_3.md | govhackaustralia/project-jabberwocky-poc | 5ff4193c84018aac93740b6296ae81be2bd629ab | [
"CC-BY-4.0"
] | 2 | 2020-09-15T00:55:33.000Z | 2021-09-27T20:49:54.000Z | _mentors/mentor_3.md | govhackaustralia/project-jabberwocky-poc | 5ff4193c84018aac93740b6296ae81be2bd629ab | [
"CC-BY-4.0"
] | 1 | 2016-05-27T06:09:49.000Z | 2016-05-27T06:09:49.000Z | ---
name: Mentor 3
id: mentor_3
photo_url: https://static.pexels.com/photos/9635/suit-portrait-preparation-wedding-large.jpg
title: Science Ninja
ask_me_about: Stuff and things.
organisation: organisation_1
jurisdiction: australia
location: online
contact:
twitter: jesserobertson
email: [email protected]
fields:
- field_1
- field_2
# themes:
# - theme_1
# - theme_3
datasets:
- dataset_1
---
I’m a geologist/physicist/data scientist at the CSIRO. I work on a range of science projects across the organisation, generally using geoscience and geospatial data with machine learning and data analysis to improve exploration and production strategies for the minerals and mets sector. As well as science-y things, you can ask me about webservices, maps and geospatial data. Python is my poison of choice. | 35.826087 | 407 | 0.785194 | eng_Latn | 0.9517 |
8a8e753dd027dd7b342c3a8999f59077028dfd84 | 2,622 | md | Markdown | aspnet/mvc/overview/older-versions-1/controllers-and-routing/index.md | cmk1988/Docs.de-de | fc224e6cd389ed48f4b89b920e1be1d89af12cc7 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | aspnet/mvc/overview/older-versions-1/controllers-and-routing/index.md | cmk1988/Docs.de-de | fc224e6cd389ed48f4b89b920e1be1d89af12cc7 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | aspnet/mvc/overview/older-versions-1/controllers-and-routing/index.md | cmk1988/Docs.de-de | fc224e6cd389ed48f4b89b920e1be1d89af12cc7 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
uid: mvc/overview/older-versions-1/controllers-and-routing/index
title: Controller und Routing | Microsoft-Dokumentation
author: rick-anderson
description: In dieser Tutorials erfahren Sie ASP.NET-Routing, die ASP.NET MVC-Controlleraktionen Browseranforderungen zugeordnet.
ms.author: riande
ms.date: 09/28/2011
ms.assetid: 124df537-428c-4861-b6c2-4830c094fe0c
msc.legacyurl: /mvc/overview/older-versions-1/controllers-and-routing
msc.type: chapter
ms.openlocfilehash: 5da0db768aaf39dc67bb2344e645c491c78a03a1
ms.sourcegitcommit: 45ac74e400f9f2b7dbded66297730f6f14a4eb25
ms.translationtype: MT
ms.contentlocale: de-DE
ms.lasthandoff: 08/16/2018
ms.locfileid: "48255989"
---
<a name="controllers-and-routing"></a>Controller und Routing
====================
> In dieser Tutorials erfahren Sie ASP.NET-Routing, die ASP.NET MVC-Controlleraktionen Browseranforderungen zugeordnet.
- [ASP.NET MVC-Routing – Übersicht (C#)](asp-net-mvc-routing-overview-cs.md)
- [Grundlegendes zu Aktionsfiltern (C#)](understanding-action-filters-cs.md)
- [Verbessern der Leistung mit Ausgabezwischenspeicherung (C#)](improving-performance-with-output-caching-cs.md)
- [Hinzufügen von dynamischen Inhalten zu einer zwischengespeicherten Seite (C#)](adding-dynamic-content-to-a-cached-page-cs.md)
- [Erstellen eines Controllers (C#)](creating-a-controller-cs.md)
- [Erstellen einer Aktion (C#)](creating-an-action-cs.md)
- [ASP.NET MVC-Routing – Übersicht (VB)](asp-net-mvc-routing-overview-vb.md)
- [Grundlegendes zu Aktionsfiltern (VB)](understanding-action-filters-vb.md)
- [Verbessern der Leistung mit Ausgabezwischenspeicherung (VB)](improving-performance-with-output-caching-vb.md)
- [Hinzufügen von dynamischen Inhalten zu einer zwischengespeicherten Seite (VB)](adding-dynamic-content-to-a-cached-page-vb.md)
- [Erstellen eines Controllers (VB)](creating-a-controller-vb.md)
- [Erstellen einer Aktion (VB)](creating-an-action-vb.md)
- [ASP.NET MVC-Controller – Übersicht (C#)](aspnet-mvc-controllers-overview-cs.md)
- [Erstellen von benutzerdefinierten Routen (C#)](creating-custom-routes-cs.md)
- [Erstellen einer Routeneinschränkung (C#)](creating-a-route-constraint-cs.md)
- [Erstellen einer benutzerdefinierten Routeneinschränkung (C#)](creating-a-custom-route-constraint-cs.md)
- [ASP.NET MVC-Controller – Übersicht (VB)](asp-net-mvc-controller-overview-vb.md)
- [Erstellen von benutzerdefinierten Routen (VB)](creating-custom-routes-vb.md)
- [Erstellen einer Routeneinschränkung (VB)](creating-a-route-constraint-vb.md)
- [Erstellen einer benutzerdefinierten Routeneinschränkung (VB)](creating-a-custom-route-constraint-vb.md)
| 60.976744 | 130 | 0.786804 | deu_Latn | 0.655482 |
8a8ed382e16c374b7ddbed05471f1cdb095beb86 | 442 | md | Markdown | public/README.md | vanessa2808/Thegioicongnghe24.com | 7f00b47d3a0dd7e65ce426afc203cea3f9842e3c | [
"MIT"
] | null | null | null | public/README.md | vanessa2808/Thegioicongnghe24.com | 7f00b47d3a0dd7e65ce426afc203cea3f9842e3c | [
"MIT"
] | 2 | 2021-01-16T20:10:26.000Z | 2021-09-29T17:47:14.000Z | public/README.md | vanessa2808/Webfood-laravel | 7f00b47d3a0dd7e65ce426afc203cea3f9842e3c | [
"MIT"
] | null | null | null | # firebase-storage-image-upload
upload image to firebase storage from app and view it, https://photo-upload-prithvi.firebaseapp.com/
Change API KEY with your FIrebase API Key below
var config = {
apiKey: "",//change api key
authDomain: "fir-f138c.firebaseapp.com",
databaseURL: "https://fir-f138c.firebaseio.com",
storageBucket: "fir-f138c.appspot.com",
messagingSenderId: "918310331531"
};
| 31.571429 | 100 | 0.683258 | eng_Latn | 0.332225 |
8a8ee48852839db46c77bc3049a903bf556326cc | 38 | md | Markdown | README.md | codesteller/idd-analysis | 2e5691cff1abc97563594fca0be9612da8fc98eb | [
"Apache-2.0"
] | null | null | null | README.md | codesteller/idd-analysis | 2e5691cff1abc97563594fca0be9612da8fc98eb | [
"Apache-2.0"
] | null | null | null | README.md | codesteller/idd-analysis | 2e5691cff1abc97563594fca0be9612da8fc98eb | [
"Apache-2.0"
] | null | null | null | # idd-analysis
### [Work In Progress] | 12.666667 | 22 | 0.657895 | deu_Latn | 0.508328 |
8a8ee4c4ca7c668ee582f4e5bc057b0aaa0c85ec | 4,680 | md | Markdown | _articles/jp/bitrise-cli/index.md | ofalvai/devcenter | 57a21d525eea46c1dae650a5a77603472e91a98f | [
"MIT"
] | 182 | 2015-01-09T10:04:39.000Z | 2021-12-19T02:04:54.000Z | _articles/jp/bitrise-cli/index.md | ofalvai/devcenter | 57a21d525eea46c1dae650a5a77603472e91a98f | [
"MIT"
] | 228 | 2015-07-14T18:10:30.000Z | 2021-11-24T14:41:39.000Z | _articles/jp/bitrise-cli/index.md | ofalvai/devcenter | 57a21d525eea46c1dae650a5a77603472e91a98f | [
"MIT"
] | 299 | 2015-01-08T16:03:49.000Z | 2021-12-02T16:17:18.000Z | ---
changelog:
last_modified_at:
title: YAML mode & Bitrise CLI
redirect_from:
- "/bitrise-cli"
- "/bitrise-cli/"
menu:
main:
identifier: bitrise-cli-main
weight: 23
---
{% include not_translated_yet.html %}
Bitrise is a collection of tools and services to help you with the development
and automation of your software projects, with a main focus on mobile apps.
Most of this DevCenter describes things related to [bitrise.io](https://www.bitrise.io),
the hosted automation service, but the heart of Bitrise is the
[open source Bitrise CLI / runner](https://github.com/bitrise-io/bitrise),
which is responsible for interpreting the build configuration and executing it.
This open source runner is referred to as `Bitrise CLI` or `Bitrise`,
and **it's a tool which you can install and run on your own Mac/PC!**
This section of the DevCenter is dedicated to this runner (`Bitrise CLI`) and the
`bitrise.yml` configuration format, **the things described here don't even require a**
[**bitrise.io**](https://www.bitrise.io) **account**, the only requirement is that
you install the `Bitrise CLI` on your Mac/PC.
{% include message_box.html type="note" title="Bitrise CLI on bitrise.io" content="
The CLI you can install is exactly the same as what's used on [bitrise.io](https://www.bitrise.io). When a build starts on [bitrise.io](https://www.bitrise.io), a virtual machine is created for the build with the Bitrise CLI preinstalled, and once the virtual machine is ready, the build is performed through the Bitrise CLI. "%}
## Bitrise CLI - the open source, offline, automation runner
To run a Bitrise build on your machine, you can install our [open source runner](https://www.bitrise.io/cli)
and use the `bitrise` command to execute your _workflows_ locally.
It's a great help when you're developing steps, debugging builds,
or just want to use Bitrise for _any kind of automation_ on your machine.
## bitrise.yml - the configuration format
The configuration format of the `Bitrise CLI` is referred to as `bitrise.yml`,
as that's the expected file name the configuration should be saved with.
_Technically the CLI can also accept the configuration in JSON format, and the file name can be changed too, but if you save the configuration into a file named_ `_bitrise.yml_`_, you can simply_ `_bitrise run_` _in that directory, without specifying any configuration path, and the CLI will read the configuration from_ `_bitrise.yml_` _automatically._
## Step Library (StepLib)
The StepLib is the collection of the build steps you can use in your
`bitrise.yml`. The steps in the official [Bitrise StepLib](https://github.com/bitrise-io/bitrise-steplib)
are all open source, **you can write your own** too and then share it with others!
See the [step-template](https://github.com/bitrise-steplib/step-template) for more information.
You can also create your own Step Library if you want to, but it's usually easier to just reference your steps with their `git clone` URL directly if you don't want to share it with others.
{% include message_box.html type="note" title="Custom StepLib support in tools" content="
The Bitrise CLI tools can work with custom step libraries, but other tools like the Visual Workflow Editor on [bitrise.io](https://www.bitrise.io) might be limited in functionality for steps not available in the main [Bitrise StepLib](https://github.com/bitrise-io/bitrise-steplib). "%}
If possible, you should share your steps in the main [Bitrise StepLib](https://github.com/bitrise-io/bitrise-steplib),
to help others as well as for the extra reliability the StepLib offers.
_Custom StepLibs can also provide fallbacks (alternative download URLs, caches),
automatic and preiodic checks etc. to provide the best reliability, but you get all these for free
if you use the main Bitrise StepLib._
### Why to use the StepLib and Steps instead of ad-hoc build scripts?
Same reason why code libraries / dependencies are awesome:
You have a code which can be updated independently from other parts,
and **you can re-use/share** this between your configurations.
**Shared maintenance**: when you use Steps created by others you don't have to maintain
the codes, but you can contribute to it if you want to, or create and use your own.
**Versioned**: If a new version doesn't work for you, **you can always go back to a previous one**.
_We frequently push features as Steps instead of building it into the core tools.
This allows faster and versioned iterations, and updating the parts independently.
We try to maintain compatibility as much as possible, so older versions can work too,
providing a way to upgrade when it's appropriate for you._ | 56.385542 | 353 | 0.771795 | eng_Latn | 0.998304 |
8a8efb3e3a255ec6d76ec01077f6de01c6571c4f | 828 | md | Markdown | SharePoint/SharePointServer/PSConfigHelp/read-the-microsoft-software-license-terms.md | adrianwells/OfficeDocs-SharePoint | d60d49cf4bca382969fba214bf33b3530e046a4a | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-04-19T21:33:32.000Z | 2020-04-19T21:33:32.000Z | SharePoint/SharePointServer/PSConfigHelp/read-the-microsoft-software-license-terms.md | adrianwells/OfficeDocs-SharePoint | d60d49cf4bca382969fba214bf33b3530e046a4a | [
"CC-BY-4.0",
"MIT"
] | null | null | null | SharePoint/SharePointServer/PSConfigHelp/read-the-microsoft-software-license-terms.md | adrianwells/OfficeDocs-SharePoint | d60d49cf4bca382969fba214bf33b3530e046a4a | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: "Read the Microsoft Software License Terms"
ms.reviewer:
ms.author: mikeplum
author: MikePlumleyMSFT
manager: pamgreen
ms.date: 3/1/2018
audience: ITPro
ms.topic: article
ms.prod: sharepoint-server-itpro
localization_priority: Normal
ROBOTS: NOINDEX
ms.collection:
- IT_Sharepoint_Server
- IT_Sharepoint_Server_Top
ms.assetid: cef3d17a-5e66-4750-be94-ff9aa011cd80
description: "Summary: Learn about the Microsoft Software License Terms in SharePoint Server."
---
# Read the Microsoft Software License Terms
**Summary:** Learn about the Microsoft Software License Terms in SharePoint Server.
The Microsoft Software License Terms define the legal conditions under which you can use your software. In Setup, select the ** I accept the terms of this agreement ** check box to enable the **Continue** button.
| 30.666667 | 213 | 0.788647 | eng_Latn | 0.858634 |
8a8f420233eaeee62fc895f4fb8809b89451a958 | 473 | md | Markdown | CHANGELOG.md | jrock2004/vscode-ember-snippets | 664eb573f8b1cebe2e745186c4a51ed01260492a | [
"MIT"
] | 1 | 2020-07-21T10:06:47.000Z | 2020-07-21T10:06:47.000Z | CHANGELOG.md | jrock2004/vscode-ember-snippets | 664eb573f8b1cebe2e745186c4a51ed01260492a | [
"MIT"
] | null | null | null | CHANGELOG.md | jrock2004/vscode-ember-snippets | 664eb573f8b1cebe2e745186c4a51ed01260492a | [
"MIT"
] | 1 | 2020-06-01T14:51:37.000Z | 2020-06-01T14:51:37.000Z | # Change Log
## [Unreleased]
- Initial release
## [1.0.0]
- Copied over the snippets that the original plugin uses, with some fixes
## [1.1.0]
- Lower VS code version requirements
## [1.1.1]
- Adding to readme the missing ember-data
## [1.2.0]
- Adding a few new snippets. handlebars let, service inject
## [2.0.0]
- Ember runloop snippets
- Add snippets for most of ember-test-helpers
- More ember computed snippets
- Remove logger snippets
- Update service snippet | 19.708333 | 73 | 0.714588 | eng_Latn | 0.936076 |
8a8fe605ff94e6f61012d7db119ccea951650c84 | 170 | md | Markdown | README.md | whimsial/binder-r-test | 61f530538d3497dec99857d2762dc3c30fddae41 | [
"MIT"
] | null | null | null | README.md | whimsial/binder-r-test | 61f530538d3497dec99857d2762dc3c30fddae41 | [
"MIT"
] | null | null | null | README.md | whimsial/binder-r-test | 61f530538d3497dec99857d2762dc3c30fddae41 | [
"MIT"
] | null | null | null | [](https://mybinder.org/v2/gh/whimsial/binder-r-test/HEAD?urlpath=rstudio)
# binder-r-test
A repository to test binder + r
| 34 | 120 | 0.747059 | yue_Hant | 0.206646 |
8a9020147ae58c2aafbe4c3e0cdb9ec55d89f338 | 681 | md | Markdown | dns-subdomain/README.md | fkhademi/aviatrix | a35b6025561849e31c52ae6a12acd955131caeb8 | [
"Apache-2.0"
] | null | null | null | dns-subdomain/README.md | fkhademi/aviatrix | a35b6025561849e31c52ae6a12acd955131caeb8 | [
"Apache-2.0"
] | 1 | 2021-06-11T16:43:27.000Z | 2021-06-11T16:43:27.000Z | dns-subdomain/README.md | fkhademi/aviatrix | a35b6025561849e31c52ae6a12acd955131caeb8 | [
"Apache-2.0"
] | 2 | 2021-03-17T11:29:14.000Z | 2021-06-29T14:30:41.000Z | # dns-subdomain
### Description
This will create the following:
* A DNS subdomain in Route53
* The necessary glue and authority records in the parent domain
* A wildcard cert signed by LetsEncrypt for this subdomain
* The cert and key will be stored in an S3 bucket
### Variables
The following variables are required:
key | value
--- | ---
dns_aws_access_key | Access Key with permissions to R53 and S3
dns_aws_secret_key | Secret Key with permissions to R53 and S3
pod_id | A number between 0 and 255
The following variables are optional:
key | default value
--- | ---
aws_region | eu-central-1
dns_zone | avxlab.de
email_address | [email protected]
bucket_name | avx-build | 24.321429 | 63 | 0.760646 | eng_Latn | 0.994854 |
8a914b66402415ec6cc61dbcdcd267f29f05558d | 790 | md | Markdown | README.md | Aaron1011/cita-common | 5acb4259e4398403ede0faf2b464b15c66b87e8c | [
"ECL-2.0",
"Apache-2.0"
] | 32 | 2018-01-09T02:20:38.000Z | 2019-11-09T10:01:35.000Z | README.md | Aaron1011/cita-common | 5acb4259e4398403ede0faf2b464b15c66b87e8c | [
"ECL-2.0",
"Apache-2.0"
] | 143 | 2017-12-21T11:59:07.000Z | 2019-10-16T07:22:28.000Z | README.md | Aaron1011/cita-common | 5acb4259e4398403ede0faf2b464b15c66b87e8c | [
"ECL-2.0",
"Apache-2.0"
] | 37 | 2017-12-21T05:38:43.000Z | 2019-10-17T07:09:52.000Z | # Libraries for [CITA](https://github.com/citahub/cita)
[](https://circleci.com/gh/citahub/cita-common/tree/develop)
[](https://codecov.io/gh/citahub/cita-common)
This repository is a collection of crates used by microservices in [CITA](https://github.com/citahub/cita).
Crates below are extracted from [Parity](https://github.com/paritytech/parity):
- rlp
## License [](https://app.fossa.com/projects/git%2Bgithub.com%2Fcitahub%2Fcita-common?ref=badge_shield)
Same as [CITA](https://github.com/citahub/cita)
| 52.666667 | 211 | 0.764557 | yue_Hant | 0.50495 |
8a91aed3b9a68fd446a33cf6e6cbdb838ff10058 | 14,577 | md | Markdown | doc/developer/design/20210401_volatile_sources.md | guylapid/materialize | 8629a120a5a628b6ef06f379b48ba723797db944 | [
"MIT"
] | 3,840 | 2020-02-13T18:28:21.000Z | 2022-03-31T17:25:04.000Z | doc/developer/design/20210401_volatile_sources.md | guylapid/materialize | 8629a120a5a628b6ef06f379b48ba723797db944 | [
"MIT"
] | 5,802 | 2020-02-13T18:59:27.000Z | 2022-03-31T21:50:24.000Z | doc/developer/design/20210401_volatile_sources.md | guylapid/materialize | 8629a120a5a628b6ef06f379b48ba723797db944 | [
"MIT"
] | 295 | 2020-02-13T18:49:32.000Z | 2022-03-30T10:55:12.000Z | # Volatile sources
## Summary
Our users want to connect Materialize to upstream sources that do not provide
guarantees about what data they will present. These sources are in tension with
the goal of providing a deterministic, replayable system.
This design doc proposes to:
* Introduce "volatile source" as a term of art that describes a source that
does not meet a specific standard of reliability.
* Use the terminology consistently in the docs site and error messages to
educate our users about volatile sources.
* Restrict the use of volatile sources in contexts where they could impede
future improvements to the system's determinism and correctness.
## Goals
The only goal is to **stabilize the [PubNub] and [SSE] sources**.
Both of these are volatile sources with some worrying correctness properties,
but their existence will massively improve the "wow factor" for demos of
Materialize Cloud.
[PubNub]: https://github.com/MaterializeInc/materialize/pull/6189
[SSE]: https://github.com/MaterializeInc/materialize/pull/6208
## Description
### Terminology
A "volatile source" is any source that cannot reliabily present the same data
with the same timestamps across different instantiations.
A "instantiation" of a source occurs whenever:
* A new index is created on the source or on an unmaterialized view that
references the source.
* An ad-hoc query or `TAIL` references the source directly.
Restarting Materialize will cause all sources to be reinstantiated. Referencing
a materialized view that in turn depends on a source does not create a new
instantiation of a source.
Examples of volatile sources:
* Any Kinesis source. Since Kinesis streams have mandatory retention periods
(by default 24 hours), a new instantiation of the source will not see
any data that has expired.
* A PubNub demo source, since new instantiations always start from the tail
of the stream.
* An append-only Kafka source with a non-infinite retention policy.
* A file source, where the file is periodically overwritten.
Examples of nonvolatile sources:
* A PubNub source with [retention](https://www.pubnub.com/docs/messages/storage),
though we don't presently support this.
* An append-only Kafka source, when the topic has infinite retention and no
compaction policy.
* An upsert Kafka source, when the topic has infinite retention but *may*
have a key compaction policy.
* A file source, when the file is treated as append only.
It's important to note that volatility is a property of how a source is
*configured*, rather than fundamental to a source type. Kinesis is the rare
exception. All other sources can be either volatile and non-volatile modes,
depending on how the source is configured.
### Discussion
Volatile sources impede Materialize's goal of providing users with correct,
deterministic results. If you restart Materialize, we want to guarantee that you
will see exactly the same data at exactly the same timestamps, and there is
ongoing work to facilitate that. If you've created a volatile source, there is
simply no possibility that we'll be able to provide that guarantee, because the
upstream source may have garbage collected the data that you saw last time you
ran Materialize.
Several forthcoming initiatives depend on this determinism guarantee, however:
* Exactly-once sinks
* Active-active replication
* Dataflow transformations that consider source instances to be logically
equivalent
My contention is that it is wholly unrealistic to expect our users to only use
nonvolatile sources with Materialize. The streaming world runs on inconsistency
and nondurability. To play in this space, we need to interoperate seamlessly
with volatile sources, and then offer a large, inviting off ramp into the
Materialize world of determinism and consistency.
The proposal here, then, is to bake the notion of volatility into the system. We
start by marking volatile sources as such. Any view that depends on such a
source becomes volatile. Any sink created from a volatile source or view becomes
volatile. The optimizer will need to be careful not to treat different
instantiations of a volatile source or view as logically equivalent. Exactly
once sinks and other features that only work on nonvolatile sources can look
for and reject volatile sources.
### Design
To start, I propose that we observe a simple rule:
* All PubNub, SSE, and Kinesis sources are marked as volatile.
* All other sources are marked as having unknown volatility (`NULL`).
In the future, we'll want to allow users to mark Kafka, S3, and file sources as
volatile at their option, to capture when their *configuration* of the source is
volatile. See [Future work](#future-work) below.
The only user-visible change at the moment will be an additional column in
`SHOW SOURCES` that indicates whether a source is volatile
```
> SHOW SOURCES;
name | type | volatile | materialized
-------------+------+----------+-------------
pubnub_src | user | true | false
kafka_src | user | NULL | false
```
and similarly for `SHOW VIEWS`:
```
> SHOW VIEWS;
name | type | volatile | materialized
--------------+------+----------+-------------
pubnub_view | user | true | true
kafka_view | user | NULL | true
```
In the docs, we'll want to add a page about "Volatile sources" that explains
what they are, why they are good for demos, and why they are bad for production
applications that care about correctness. We can add a warning callout on
PubNub, SSE, and Kinesis source pages that links to the volatile source page.
The big "gotcha" with volatile sources is that different instantiations can have
different data within the same `materialized` process. Consider a sequence like
the following:
```sql
CREATE SOURCE market_orders_raw FROM PUBNUB
SUBSCRIBE KEY 'sub-c-4377ab04-f100-11e3-bffd-02ee2ddab7fe'
CHANNEL 'pubnub-market-orders';
CREATE MATERIALIZED VIEW market_orders_1 AS
SELECT text::jsonb AS val FROM market_orders_raw;
-- Imagine the user makes a cup of coffee now.
CREATE MATERIALIZED VIEW market_orders_2 AS
SELECT text::jsonb AS val FROM market_orders_raw;
```
The data in `market_orders_1` and `market_orders_2` will not be equivalent,
because they'll each have instantiated separate copies of the source at
separate times. `market_orders_1` will contain some historical data that
`market_orders_2` does not.
The more I think about it, the more this seems like reasonable, even desirable
behavior from a volatile source, provided we can educate users sufficiently.
### Implications
#### Exactly-once sinks
Exactly-once sinks will need to error if they are created on a volatile source
or view. This will be easy to check in the coordinator. The error message might
read:
```
ERROR: exactly-once sinks cannot be created from a volatile {source|view}
DETAIL: Data in volatile {sources|views} is not consistent across restarts,
which is at odds with exactly-once semantics. To learn more, visit
https://materialize.com/s/volatility.
```
#### Active-active replication
Active-active replication will rely on the determinism of the dataflow
computation to compute identical results across two separate instances of
Materialize. That is at odds with volatile sources, which will provide the
two copies of Materialize with two different sets of data.
One easy solution is to simply ban volatile sources when using Materialize
in this hypothetical distributed mode.
Alternatively, we could say "you got what you asked for", and message the
deficiencies accordingly.
#### Optimizer
The optimizer will need to be careful to treat different instances of volatile
sources and views as logically different views. This is a burden for the
optimizer team, but hopefully a small one. The check to see whether two
sources or views is roughly:
```rust
fn are_objects_equivalent(metadata: &Metadata, id1: GlobalId, id2: GlobalId) -> bool {
id1 == id2 && !metadata.is_volatile(id1)
}
```
#### Other to-be-developed features
There is no obligation for new features to play well with volatile sources. In
other words, it is acceptable for engineers to treat volatile sources as
second-class citizens in Materialize.
For example, if you add a new sink type, there is no obligation to make it work
with volatile sources if doing so would be difficult. If you add a new
optimization that would be substantially complicated by volatile sources, there
is no obligation to do that hard work; you can just disable the optimization for
volatile sources instead.
That said, our backwards compatibility still applies to volatile sources. It is
not okay to break existing, working features involving volatile sources (modulo
extenuating circumstances).
## Future work
### Toggleable volatility
In the future, I believe we'll want to allow users to explicitly mark a source
as nonvolatile or volatile at their option, e.g. via a flag to `CREATE SOURCE`:
```sql
CREATE SOURCE [NONVOLATILE | VOLATILE] src
FROM KAFKA BROKER ...
```
Correctly choosing the defaults here will require a good deal of thought,
though, so I'd like to hold off on this discussion for now. The proposal above
of treating all Kafka, S3, and file sources as nonvolatile is equivalent to the
system's current behavior.
Another benefit of deferring this toggleability is that computing the
`volatility` bit as proposed in this doc does not require storing any additional
state, as it is a pure function of the source type. If we decide we don't like
the concept of volatility, we can excise it without breaking backwards
compatibility.
### Volatility removal
Source persistence may one day permit the conversion of a volatile source
into a nonvolatile one. If we can write down the data we see as it flows into
Materialize, then it doesn't matter if the upstream source garbage collects it.
### Expanded volatility bits
We might discover that a single volatility bit is too coarse. For example,
exactly-once sinks could learn to support volatile sources that provide the
guarantee that you will never see a message more than once.
This proposal leaves the door open for slicing "volatility" into multiple
dimensions. This is another good reason to punt on
[toggleable volatility](#toggleable-volatility). Once volatility specifications
are part of `CREATE SOURCE`, we'll have to worry about backwards compatibility;
until then, we have a lot of latitude to refine our notion of volatility.
### Automated volatility violation detection
Relying on users to properly declare their sources as volatile or nonvolatile is
error prone. Unfortunately this problem is inherent to interfacing with external
systems; our users are responsibile for configuring and operating those systems
according to some specification, and then telling us what that specification is.
Given a nonvolatile Kafka source, for example, there is simply no way for
Materialize to prevent a user from adding a short retention policy to the
underlying Kafka topic that will make the source volatile.
Still, in many cases, Materialize could assist in detecting volatility
violations. We could spot-check the data across instances of the same source
occasionally, for example, and report any errors that we notice. We could
periodically query the Kafka broker for its retention settings and surface any
misconfigurations. We could remember a file's inode and size, and complain if
either has changed after Materialize restarts.
## Alternatives
### Forced materialization
One considered alternative was forcing all PubNub and SSE sources to be
materialized. This neatly sidesteps the volatility within a single
`materialized` binary, because it guarantees there is only one instantiation
of each volatile source.
This _severely_ limits Materialize's expressivity, though. One use case we
expect to be very common in demos is to only materialize the last _n_ seconds
of data, which requires both an unmaterialized source and a materialized view:
```sql
CREATE SOURCE market_orders_raw FROM PUBNUB SUBSCRIBE KEY 'sub-c-4377ab04-f100-11e3-bffd-02ee2ddab7fe' CHANNEL 'pubnub-market-orders';
CREATE MATERIALIZED VIEW market_orders AS
SELECT *
FROM (
SELECT
(text::jsonb)->>'bid_price' AS bid_price,
(text::jsonb)->>'order_quantity' AS order_quantity,
(text::jsonb)->>'symbol' AS symbol,
(text::jsonb)->>'trade_type' AS trade_type,
((text::jsonb)->'timestamp')::bigint * 1000 AS timestamp_ms
FROM market_orders_raw
)
WHERE mz_logical_timestamp() BETWEEN timestamp_ms AND timestamp_ms + 30000
```
### One-shot sources
One other discussed alternative was to introduce a "one-shot" source, which
could be used in exactly one materialized view:
```
CREATE MATERIALIZED VIEW market_orders AS
WITH market_orders_raw AS SOURCE (
PUBNUB SUBSCRIBE KEY 'sub-c-4377ab04-f100-11e3-bffd-02ee2ddab7fe' CHANNEL 'pubnub-market-orders';
)
SELECT *
FROM (
SELECT
(text::jsonb)->>'bid_price' AS bid_price,
(text::jsonb)->>'order_quantity' AS order_quantity,
(text::jsonb)->>'symbol' AS symbol,
(text::jsonb)->>'trade_type' AS trade_type,
((text::jsonb)->'timestamp')::bigint * 1000 AS timestamp_ms
FROM market_orders_raw
)
WHERE mz_logical_timestamp() BETWEEN timestamp_ms AND timestamp_ms + 30000
```
The idea here is to force you to type out the `SOURCE` definition every time you
want to use it, to make it more clear that you will get different data in
different views that use that source. But this design does not fit well into the
existing catalog infrastructure, which maintains a very clear separation between
sources and views. And even with this design, I _still_ think we'd want to
introduce the notion of volatility, because we'll want to exactly-once sinks and
active-active replication to know that `market_orders` does not uphold the
usual consistency properties.
### Wait for volatility removal
We could, in principle, reject the idea of volatile sources, and wait for source
persistence to unlock [volatility removal](#volatility-removal). Then the story
for using volatile sources with Materialize would be to _require_ using them
with source persistence, so that they become nonvolatile.
Source persistence is likely 1-2 years away, though, especially an
implementation that works seamlessly with compaction. It's also not clear to
me whether every user who wants a volatile source would be ok with requiring
persistence for those sources.
| 41.061972 | 134 | 0.774096 | eng_Latn | 0.996899 |
8a925888f9f3f3a449cdbaaf99a631e14e0b9e57 | 3,459 | md | Markdown | docs/framework/windows-workflow-foundation/samples/suspended-instance-management.md | windsting/docs.zh-cn | 58ee94e9e5af4d174dfc08371e20421178dd28ca | [
"CC-BY-4.0",
"MIT"
] | 1 | 2019-02-20T13:35:38.000Z | 2019-02-20T13:35:38.000Z | docs/framework/windows-workflow-foundation/samples/suspended-instance-management.md | windsting/docs.zh-cn | 58ee94e9e5af4d174dfc08371e20421178dd28ca | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/windows-workflow-foundation/samples/suspended-instance-management.md | windsting/docs.zh-cn | 58ee94e9e5af4d174dfc08371e20421178dd28ca | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: 挂起的实例管理
ms.date: 03/30/2017
ms.assetid: f5ca3faa-ba1f-4857-b92c-d927e4b29598
ms.openlocfilehash: c23d2dfd48ecb57a3fb418734c916586178986e9
ms.sourcegitcommit: 2701302a99cafbe0d86d53d540eb0fa7e9b46b36
ms.translationtype: MT
ms.contentlocale: zh-CN
ms.lasthandoff: 04/28/2019
ms.locfileid: "64622423"
---
# <a name="suspended-instance-management"></a>挂起的实例管理
此示例演示如何管理已挂起的工作流实例。 <xref:System.ServiceModel.Activities.Description.WorkflowUnhandledExceptionBehavior> 的默认操作为 `AbandonAndSuspend`。 这意味着，在默认情况下，从 <xref:System.ServiceModel.WorkflowServiceHost> 中承载的某个工作流实例抛出的未处理异常会导致从内存中释放（放弃）该实例，而该实例的持久版本将被标记为已挂起。 已挂起的工作流实例在取消挂起之前无法运行。
此示例演示如何实现用于查询已挂起实例的命令行实用工具，以及如何为用户提供恢复或终止实例的选项。 在此示例中，一个工作流服务有意引发异常，从而使该服务挂起。 然后可以使用命令行实用工具查询该实例，并随后恢复或终止该实例。
## <a name="demonstrates"></a>演示
<xref:System.ServiceModel.WorkflowServiceHost> 与<xref:System.ServiceModel.Activities.Description.WorkflowUnhandledExceptionBehavior>和<xref:System.ServiceModel.Activities.WorkflowControlEndpoint>Windows Workflow Foundation (WF) 中。
## <a name="discussion"></a>讨论
本示例中实现的命令行实用工具特定于 [!INCLUDE[netfx_current_long](../../../../includes/netfx-current-long-md.md)] 中附带的 SQL 实例存储区实现。 如果您具有该实例存储区的自定义实现，则可以使用特定于您实例存储区的实现替换示例中的 `WorkflowInstanceCommand` 实现，来改编此实用工具。
所提供的实现直接针对 SQL 实例存储区来运行 SQL 命令以列出挂起的实例，并依赖于添加到 <xref:System.ServiceModel.Activities.WorkflowControlEndpoint> 的 <xref:System.ServiceModel.WorkflowServiceHost>，以便恢复或终止实例。
#### <a name="to-set-up-build-and-run-the-sample"></a>设置、生成和运行示例
1. 此示例要求启用以下 Windows 组件：
1. Microsoft Message Queues (MSMQ) Server
2. SQL Server Express
2. 设置 SQL Server 数据库。
1. 从 Visual Studio 2010 命令提示符下，从将执行以下 SuspendedInstanceManagement 示例目录运行"setup.cmd":
1. 使用 SQL Server Express 创建持久性数据库。 如果持久性数据库已存在，则删除该数据库并重新创建一个
2. 设置持久性数据库。
3. 将 IIS APPPOOL\DefaultAppPool 和 NT AUTHORITY\Network Service 添加到设置持久性数据库时定义的 InstanceStoreUsers 角色。
3. 设置服务队列。
1. 在 Visual Studio 2010 中，右键单击**SampleWorkflowApp**项目，然后单击**设为启动项目**。
2. 编译并运行 SampleWorkflowApp 通过按**F5**。 这将创建所需队列。
3. 按**Enter**停止 SampleWorkflowApp。
4. 通过在命令提示符下运行 Compmgmt.msc 来打开计算机管理控制台。
5. 展开**服务和应用程序**，**消息队列**，**专用队列**。
6. 右键单击**ReceiveTx**队列，然后选择**属性**。
7. 选择**安全**选项卡上，并允许**Everyone**有权**接收消息**，**扫视消息**，和**将消息发送**。
4. 现在运行示例。
1. 在 Visual Studio 2010 中，再次运行该 SampleWorkflowApp 项目而不进行调试通过按**Ctrl + F5**。 将在控制台窗口中输出两个终结点地址：一个用于应用程序终结点，另一个来自 <xref:System.ServiceModel.Activities.WorkflowControlEndpoint>。 随后会创建一个工作流实例，该实例的跟踪记录会出现在控制台窗口中。 该工作流实例会引发异常，从而导致该实例挂起或中止。
2. 随后可以使用命令行实用工具对这些实例中的任何一个进行进一步操作。 命令行参数的语法如下：
`SuspendedInstanceManagement -Command:[CommandName] -Server:[ServerName] -Database:[DatabaseName] -InstanceId:[InstanceId]`
支持的命令为：`Query`、`Resume` 和 `Terminate`。 只有 `Resume` 和 `Terminate` 才需要 InstanceId 开关。
#### <a name="to-cleanup-optional"></a>清理（可选）
1. 通过在 `vs2010` 命令提示符下运行 Compmgmt.msc 来打开计算机管理控制台。
2. 展开**服务和应用程序**，**消息队列**，**专用队列**。
3. 删除**ReceiveTx**队列。
4. 若要删除持久性数据库，请运行 cleanup.cmd。
> [!IMPORTANT]
> 您的计算机上可能已安装这些示例。 在继续操作之前，请先检查以下（默认）目录：
>
> `<InstallDrive>:\WF_WCF_Samples`
>
> 如果此目录不存在，请转到[Windows Communication Foundation (WCF) 和.NET Framework 4 的 Windows Workflow Foundation (WF) 示例](https://go.microsoft.com/fwlink/?LinkId=150780)若要下载所有 Windows Communication Foundation (WCF) 和[!INCLUDE[wf1](../../../../includes/wf1-md.md)]示例。 此示例位于以下目录：
>
> `<InstallDrive>:\WF_WCF_Samples\WF\Application\SuspendedInstanceManagement`
| 39.758621 | 271 | 0.759179 | yue_Hant | 0.864365 |
8a931d4a5277ec2d225fb66c27b7ee57ddb58257 | 205 | md | Markdown | demos/depend-on/README.md | privatenumber/webpack-librarytarget-demo | eab7eb5bda9ef0f29d53d6677ea2ceae12f12e26 | [
"MIT"
] | 5 | 2020-06-17T06:13:29.000Z | 2022-03-02T11:24:42.000Z | demos/depend-on/README.md | privatenumber/webpack-librarytarget-demo | eab7eb5bda9ef0f29d53d6677ea2ceae12f12e26 | [
"MIT"
] | 3 | 2020-09-21T03:26:38.000Z | 2021-01-07T23:45:57.000Z | demos/depend-on/README.md | privatenumber/webpack-playground | eab7eb5bda9ef0f29d53d6677ea2ceae12f12e26 | [
"MIT"
] | null | null | null | # Depend on
This demonstrates how custom chunk "entry-points" can be created. Since they are entry-points and not real chunks, they can externalize dependencies. Note, the chunks must be loaded manually.
| 51.25 | 191 | 0.795122 | eng_Latn | 0.999499 |
8a93e79c11a08385bcfe39230484cf40320d7744 | 3,857 | md | Markdown | _posts/2018-09-15-Download-tennis-skills-and-rules.md | Camille-Conlin/26 | 00f0ca24639a34f881d6df937277b5431ae2dd5d | [
"MIT"
] | null | null | null | _posts/2018-09-15-Download-tennis-skills-and-rules.md | Camille-Conlin/26 | 00f0ca24639a34f881d6df937277b5431ae2dd5d | [
"MIT"
] | null | null | null | _posts/2018-09-15-Download-tennis-skills-and-rules.md | Camille-Conlin/26 | 00f0ca24639a34f881d6df937277b5431ae2dd5d | [
"MIT"
] | null | null | null | ---
layout: post
comments: true
categories: Other
---
## Download Tennis skills and rules book
Your father is with you in many places, she tempered it with wariness. to form the earthly paradise of the Samoyed of the present day. "Micky Asking the mentally disabled what they think is, just went bing-bong, who gives the following description and agreeable, not slaves like the workers in the roaster tower, only I had time, that's what you're to nod for, a violation of the rights of man. In the same way the child offers its father and courage have a strong claim on our admiration. By the Archmage Thorion. But if a "No offense taken," Noah said. But it's more than just things that're different. Harry saw too many old private-eye movies tennis skills and rules the late show. He had nothing but his bright red hair, as far as Celestina knew, as before, and maybe the gov'ment never done killed your MOOG INDIGO scar tissue. We're still basically in love. He crumpled them and threw them in By the time Agnes opened the driver's door and slumped behind the steering wheel, perhaps to rest or "You've been drinking now," she softly accused! possibly Gwyneth Paltrow?" digging for the Red Mother, in which case the election will automatically be suspended. No Cain. The laptop had been stored on a shelf in the entertainment center, and lay face down on the couch with his feet toward me. " He did not turn. At the He whistles the dog to his side. If tennis skills and rules Roke was now what it once was- if we had more people of the true art gathered here, the couldn't seem to stop contemplating it, which had an unpleasant taste and was tough as Shaking two apricots from the bag into his band: "I'm not alone with this view, go saying, into square compartments one or two feet deep, it won't work. house. Station attendants, Ms, realizing he must have slept for hours. " After tennis skills and rules pause he asked, entered into discourse with him, then. Tennis skills and rules uneasy in an ordinary-looking town tennis skills and rules a sweet spring morning, and we're not, as if the shining angel who would guide him elsewhere had already entered his body and was with him to begin the journey. He filled the first cup and saying, her face in shadow, posts and out of the mud on those infrequent occasions when the street floods during a hard-pouring toad-drowner, leaving the damp imprint of her sodden clothes. "I'd like to. There's tennis skills and rules old pallet in the woodhouse. It is because human beings first sledges surpassed our expectation. It didn't play anything, ii. For I believe that the place where ice-obstacles will of very wide theoretical conclusions, excessive for a woman. Then suddenly he stopped. One day, unconditional love that she had words than I am, noisy stream he had heard singing through his Leilani knew that Preston had moved the chair close to the bed when she heard him sit on it, hoping this was one of the times Detweiler stuck around for more than three days, it occurred to him that the Pyramids could be taken as symbolizing the hierarchical form of an ideal. FROM ST. A preacher from the Mayflower I1, then buried her tennis skills and rules against my shoulder, p. But the words had no weight or meaning? We did not see any beggars in our journey into the interior (the present Spitzbergen), though," Micky noted. If you've been up to something, but instead he official certificate given by Commandant Baschleff or any with such momentum that he tennis skills and rules into the side of a Lexus stopped in the lane adjacent to the motor wonder so overcomes them that he can see what they had been like and what they Along with bones of the mammoth there are found on the New Siberian cartons of eggs. 463. just a little way. Instead he took off his fur hat and laid it upon his heart, 'Do this. | 428.555556 | 3,760 | 0.787918 | eng_Latn | 0.999978 |
8a943c80e34855ccdc39db09d58473413e4179aa | 21,793 | md | Markdown | aspnet/mvc/overview/security/create-an-aspnet-mvc-5-app-with-facebook-and-google-oauth2-and-openid-sign-on.md | trobinson41/Docs | 1a90e4611003a53cb1892268372c2511817ca917 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2018-04-15T15:25:36.000Z | 2018-04-15T15:25:36.000Z | aspnet/mvc/overview/security/create-an-aspnet-mvc-5-app-with-facebook-and-google-oauth2-and-openid-sign-on.md | MEvans-HSTV/aspnet | a60a99104fe7a29e271667cead6a06b6d8258d03 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | aspnet/mvc/overview/security/create-an-aspnet-mvc-5-app-with-facebook-and-google-oauth2-and-openid-sign-on.md | MEvans-HSTV/aspnet | a60a99104fe7a29e271667cead6a06b6d8258d03 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
uid: mvc/overview/security/create-an-aspnet-mvc-5-app-with-facebook-and-google-oauth2-and-openid-sign-on
title: "Create MVC 5 App with Facebook, Twitter, LinkedIn and Google OAuth2 Sign-on (C#) | Microsoft Docs"
author: Rick-Anderson
description: "This tutorial shows you how to build an ASP.NET MVC 5 web application that enables users to log in using OAuth 2.0 with credentials from an external authenti..."
ms.author: aspnetcontent
manager: wpickett
ms.date: 04/03/2015
ms.topic: article
ms.assetid: 81ee500f-fc37-40d6-8722-f1b64720fbb6
ms.technology: dotnet-mvc
ms.prod: .net-framework
msc.legacyurl: /mvc/overview/security/create-an-aspnet-mvc-5-app-with-facebook-and-google-oauth2-and-openid-sign-on
msc.type: authoredcontent
---
Create an ASP.NET MVC 5 App with Facebook, Twitter, LinkedIn and Google OAuth2 Sign-on (C#)
====================
by [Rick Anderson](https://github.com/Rick-Anderson)
> This tutorial shows you how to build an ASP.NET MVC 5 web application that enables users to log in using [OAuth 2.0](http://oauth.net/2/) with credentials from an external authentication provider, such as Facebook, Twitter, LinkedIn, Microsoft, or Google. For simplicity, this tutorial focuses on working with credentials from Facebook and Google.
>
> Enabling these credentials in your web sites provides a significant advantage because millions of users already have accounts with these external providers. These users may be more inclined to sign up for your site if they do not have to create and remember a new set of credentials.
>
> See also [ASP.NET MVC 5 app with SMS and email Two-Factor Authentication](aspnet-mvc-5-app-with-sms-and-email-two-factor-authentication.md).
>
> The tutorial also shows how to add profile data for the user, and how to use the Membership API to add roles. This tutorial was written by [Rick Anderson](https://blogs.msdn.com/rickAndy) ( Please follow me on Twitter: [@RickAndMSFT](https://twitter.com/RickAndMSFT) ).
<a id="start"></a>
## Getting Started
Start by installing and running [Visual Studio Express 2013 for Web](https://go.microsoft.com/fwlink/?LinkId=299058) or [Visual Studio 2013](https://go.microsoft.com/fwlink/?LinkId=306566). Install Visual Studio [2013 Update 3](https://go.microsoft.com/fwlink/?LinkId=390521) or higher. For help with Dropbox, GitHub, Linkedin, Instagram, buffer, salesforce, STEAM, Stack Exchange, Tripit, twitch, Twitter, Yahoo and more, see this [one stop guide](http://www.oauthforaspnet.com/).
> [!NOTE]
> You must install Visual Studio [2013 Update 3](https://go.microsoft.com/fwlink/?LinkId=390521) or higher to use Google OAuth 2 and to debug locally without SSL warnings.
Click **New Project** from the **Start** page, or you can use the menu and select **File**, and then **New Project**.
<a id="1st"></a>
## Creating Your First Application
Click **New Project**, then select **Visual C#** on the left, then **Web** and then select **ASP.NET Web Application**. Name your project "MvcAuth" and then click **OK**.
In the **New ASP.NET Project** dialog, click **MVC**. If the Authentication is not **Individual User Accounts**, click the **Change Authentication** button and select **Individual User Accounts**. By checking **Host in the cloud**, the app will be very easy to host in Azure.
If you selected **Host in the cloud**, complete the configure dialog.
### Use NuGet to update to the latest OWIN middleware
Use the NuGet package manager to update the [OWIN middleware](../../../aspnet/overview/owin-and-katana/getting-started-with-owin-and-katana.md). Select **Updates** in the left menu. You can click on the **Update All** button or you can search for only OWIN packages (shown in the next image):
In the image below, only OWIN packages are shown:
From the Package Manager Console (PMC), you can enter the `Update-Package` command, which will update all packages.
Press **F5** or **Ctrl+F5** to run the application. In the image below, the port number is 1234. When you run the application, you'll see a different port number.
Depending on the size of your browser window, you might need to click the navigation icon to see the **Home**, **About**, **Contact**, **Register** and **Log in** links.
<a id="ssl"></a>
## Setting up SSL in the Project
To connect to authentication providers like Google and Facebook, you will need to set up IIS-Express to use SSL. It's important to keep using SSL after login and not drop back to HTTP, your login cookie is just as secret as your username and password, and without using SSL you're sending it in clear-text across the wire. Besides, you've already taken the time to perform the handshake and secure the channel (which is the bulk of what makes HTTPS slower than HTTP) before the MVC pipeline is run, so redirecting back to HTTP after you're logged in won't make the current request or future requests much faster.
1. In **Solution Explorer**, click the **MvcAuth** project.
2. Hit the F4 key to show the project properties. Alternatively, from the **View** menu you can select **Properties Window**.
3. Change **SSL Enabled** to True.
4. Copy the SSL URL (which will be `https://localhost:44300/` unless you've created other SSL projects).
5. In **Solution Explorer**, right click the **MvcAuth** project and select **Properties**.
6. Select the **Web** tab, and then paste the SSL URL into the **Project Url** box. Save the file (Ctl+S). You will need this URL to configure Facebook and Google authentication apps.
7. Add the [RequireHttps](https://msdn.microsoft.com/en-us/library/system.web.mvc.requirehttpsattribute.aspx) attribute to the `Home` controller to require all requests must use HTTPS. A more secure approach is to add the [RequireHttps](https://msdn.microsoft.com/en-us/library/system.web.mvc.requirehttpsattribute.aspx) filter to the application. See the section "Protect the Application with SSL and the Authorize Attribute" in my tutoral [Create an ASP.NET MVC app with auth and SQL DB and deploy to Azure App Service](https://docs.microsoft.com/aspnet/core/security/authorization/secure-data). A portion of the Home controller is shown below.
[!code-csharp[Main](create-an-aspnet-mvc-5-app-with-facebook-and-google-oauth2-and-openid-sign-on/samples/sample1.cs?highlight=1)]
8. Press CTRL+F5 to run the application. If you've installed the certificate in the past, you can skip the rest of this section and jump to [Creating a Google app for OAuth 2 and connecting the app to the project](#goog), otherwise, follow the instructions to trust the self-signed certificate that IIS Express has generated.
9. Read the **Security Warning** dialog and then click **Yes** if you want to install the certificate representing localhost.
10. IE shows the *Home* page and there are no SSL warnings.
11. Google Chrome also accepts the certificate and will show HTTPS content without a warning. Firefox uses its own certificate store, so it will display a warning. For our application you can safely click **I Understand the Risks**.
<a id="goog"></a>
## Creating a Google app for OAuth 2 and connecting the app to the project
1. Navigate to the [Google Developers Console](https://console.developers.google.com/).
1. If you haven't created a project before, select **Credentials** in the left tab, and then select **Create**.
1. In the left tab, click **Credentials**.
1. Click **Create credentials** then **OAuth client ID**.
1. In the **Create Client ID** dialog, keep the default **Web application** for the application type.
2. Set the **Authorized JavaScript** origins to the SSL URL you used above (`https://localhost:44300/` unless you've created other SSL projects)
3. Set the **Authorized redirect URI** to:
`https://localhost:44300/signin-google/`
5. Click the OAuth Consent screen menu item, then set your email address and product name. When you have completed the form click **Save**.
6. Click the Library menu item, search **Google+ API**, click on it then press Enable.
The image below shows the enabled APIs.
7. From the Google APIs API Manager, visit the **Credentials** tab to obtain the **Client ID**. Download to save a JSON file with application secrets. Copy and paste the **ClientId** and **ClientSecret** into the `UseGoogleAuthentication` method found in the *Startup.Auth.cs* file in the *App_Start* folder. The **ClientId** and **ClientSecret** values shown below are samples and don't work.
[!code-csharp[Main](create-an-aspnet-mvc-5-app-with-facebook-and-google-oauth2-and-openid-sign-on/samples/sample2.cs?highlight=37-39)]
> [!WARNING]
> Security - Never store sensitive data in your source code. The account and credentials are added to the code above to keep the sample simple. See [Best practices for deploying passwords and other sensitive data to ASP.NET and Azure App Service](../../../identity/overview/features-api/best-practices-for-deploying-passwords-and-other-sensitive-data-to-aspnet-and-azure.md).
8. Press **CTRL+F5** to build and run the application. Click the **Log in** link.
9. Under **Use another service to log in**, click **Google**.
> [!NOTE]
> If you miss any of the steps above you will get a HTTP 401 error. Recheck your steps above. If you miss a required setting (for example **product name**), add the missing item and save, it can take a few minutes for authentication to work.
10. You will be redirected to the google site where you will enter your credentials.
11. After you enter your credentials, you will be prompted to give permissions to the web application you just created:
12. Click **Accept**. You will now be redirected back to the **Register** page of the MvcAuth application where you can register your Google account. You have the option of changing the local email registration name used for your Gmail account, but you generally want to keep the default email alias (that is, the one you used for authentication). Click **Register**.
<a id="fb"></a>
## Creating the app in Facebook and connecting the app to the project
For Facebook OAuth2 authentication, you need to copy to your project some settings from an application that you create in Facebook.
1. In your browser, navigate to [https://developers.facebook.com/apps](https://developers.facebook.com/apps) and log in by entering your Facebook credentials.
2. If you aren't already registered as a Facebook developer, click **Register as a Developer** and follow the directions to register.
3. On the **Apps** tab, click **Create New App**.
4. Enter an **App Name** and **Category**, then click **Create App**.
This must be unique across Facebook. The **App Namespace** is the part of the URL that your App will use to access the Facebook application for authentication (for example, https://apps.facebook.com/{App Namespace}). If you don't specify an **App Namespace**, the **App ID** will be used for the URL. The **App ID** is a long system-generated number that you will see in the next step.
5. Submit the standard security check.
6. Select **Settings** for the left menu bar.
7. On the **Basic** settings section of the page select **Add Platform** to specify that you are adding a website application. 
8. Select **Website** from the platform choices.
9. Make a note of your **App ID** and your **App Secret** so that you can add both into your MVC application later in this tutorial. Also, Add your Site URL (`https://localhost:44300/`) to test your MVC application. Also, add a **Contact Email**. Then, select **Save Changes**.
> [!NOTE]
> Note that you will only be able to authenticate using the email alias you have registered. Other users and test accounts will not be able to register. You can grant other Facebook accounts access to the application on the Facebook **Developer Roles** tab.
10. In Visual Studio, open *App\_Start\Startup.Auth.cs*.
11. Copy and paste the **AppId** and **App Secret** into the `UseFacebookAuthentication` method. The **AppId** and **App Secret** values shown below are samples and will not work.
[!code-csharp[Main](create-an-aspnet-mvc-5-app-with-facebook-and-google-oauth2-and-openid-sign-on/samples/sample3.cs?highlight=33-35,38-39)]
12. Click **Save Changes**.
13. Press **CTRL+F5** to run the application.
Select **Log in** to display the Login page. Click **Facebook** under **Use another service to log in.**
Enter your Facebook credentials.
You will be prompted to grant permission for the application to access your public profile and friend list.
You are now logged in. You can now register this account with the application.
When you register, an entry is added to the *Users* table of the membership database.
<a id="mdb"></a>
## Examine the Membership Data
In the **View** menu, click **Server Explorer**.
Expand **DefaultConnection (MvcAuth)**, expand **Tables**, right click **AspNetUsers** and click **Show Table Data**.
<a id="ap"></a>
## Adding Profile Data to the User Class
In this section you'll add birth date and home town to the user data during registration, as shown in the following image.
Open the *Models\IdentityModels.cs* file and add birth date and home town properties:
[!code-csharp[Main](create-an-aspnet-mvc-5-app-with-facebook-and-google-oauth2-and-openid-sign-on/samples/sample4.cs?highlight=3-4)]
Open the *Models\AccountViewModels.cs* file and the set birth date and home town properties in `ExternalLoginConfirmationViewModel`.
[!code-csharp[Main](create-an-aspnet-mvc-5-app-with-facebook-and-google-oauth2-and-openid-sign-on/samples/sample5.cs?highlight=8-9)]
Open the *Controllers\AccountController.cs* file and add code for birth date and home town in the `ExternalLoginConfirmation` action method as shown:
[!code-csharp[Main](create-an-aspnet-mvc-5-app-with-facebook-and-google-oauth2-and-openid-sign-on/samples/sample6.cs?highlight=21-23)]
Add birth date and home town to the *Views\Account\ExternalLoginConfirmation.cshtml* file:
[!code-cshtml[Main](create-an-aspnet-mvc-5-app-with-facebook-and-google-oauth2-and-openid-sign-on/samples/sample7.cshtml?highlight=27-40)]
Delete the membership database so you can again register your Facebook account with your application and verify you can add the new birth date and home town profile information.
From **Solution Explorer**, click the **Show All Files** icon, then right click *Add\_Data\aspnet-MvcAuth-<dateStamp>.mdf* and click **Delete**.
From the **Tools** menu, click **NuGet Package Manger**, then click **Package Manager Console** (PMC). Enter the following commands in the PMC.
1. Enable-Migrations
2. Add-Migration Init
3. Update-Database
Run the application and use FaceBook and Google to log in and register some users.
## Examine the Membership Data
In the **View** menu, click **Server Explorer**.
Right click **AspNetUsers** and click **Show Table Data**.
The `HomeTown` and `BirthDate` fields are shown below.
<a id="off"></a>
## Logging off your App and Logging in With Another Account
If you log on to your app with Facebook,, and then log out and try to log in again with a different Facebook account (using the same browser), you will be immediately logged in to the previous Facebook account you used. In order to use another account, you need to navigate to Facebook and log out at Facebook. The same rule applies to any other 3rd party authentication provider. Alternatively, you can log in with another account by using a different browser.
## Next Steps
See [Introducing the Yahoo and LinkedIn OAuth security providers for OWIN](http://www.jerriepelser.com/blog/introducing-the-yahoo-linkedin-oauth-security-providers-for-owin/) by Jerrie Pelser for Yahoo and LinkedIn instructions. See Jerrie's Pretty social login buttons for ASP.NET MVC 5 to get enable social login buttons.
Follow my tutorial [Create an ASP.NET MVC app with auth and SQL DB and deploy to Azure App Service](https://docs.microsoft.com/aspnet/core/security/authorization/secure-data), which continues this tutorial and shows the following:
1. How to deploy your app to Azure.
2. How to secure you app with roles.
3. How to secure your app with the [RequireHttps](https://msdn.microsoft.com/en-us/library/system.web.mvc.requirehttpsattribute(v=vs.108).aspx) and [Authorize](https://msdn.microsoft.com/en-us/library/system.web.mvc.authorizeattribute(v=vs.100).aspx) filters.
4. How to use the membership API to add users and roles.
Please leave feedback on how you liked this tutorial and what we could improve. You can also request new topics at [Show Me How With Code](http://aspnet.uservoice.com/forums/228522-show-me-how-with-code). You can even ask for and vote on new features to be added to ASP.NET. For example, you can vote for a tool to [create and manage users and roles.](http://aspnet.uservoice.com/forums/41199-general-asp-net/suggestions/5646857-asp-net-identity-membership-db-tool-to-mangage-use)
For an good explanation of how ASP.NET External Authentication Services work, see Robert McMurray's [External Authentication Services](https://asp.net/web-api/overview/security/external-authentication-services). Robert's article also goes into detail in enabling Microsoft and Twitter authentication. Tom Dykstra's excellent [EF/MVC tutorial](../getting-started/getting-started-with-ef-using-mvc/creating-an-entity-framework-data-model-for-an-asp-net-mvc-application.md) shows how to work with the Entity Framework.
| 75.148276 | 656 | 0.758179 | eng_Latn | 0.891481 |
8a9472dfe2b31de0ea357a608d7e59cae726b713 | 5,335 | md | Markdown | treebanks/yo_ytb/yo_ytb-dep-goeswith.md | emmettstr/docs | 2d0376d6e07f3ffa828f6152d12cf260a530c64d | [
"Apache-2.0"
] | null | null | null | treebanks/yo_ytb/yo_ytb-dep-goeswith.md | emmettstr/docs | 2d0376d6e07f3ffa828f6152d12cf260a530c64d | [
"Apache-2.0"
] | null | null | null | treebanks/yo_ytb/yo_ytb-dep-goeswith.md | emmettstr/docs | 2d0376d6e07f3ffa828f6152d12cf260a530c64d | [
"Apache-2.0"
] | null | null | null | ---
layout: base
title: 'Statistics of goeswith in UD_Yoruba-YTB'
udver: '2'
---
## Treebank Statistics: UD_Yoruba-YTB: Relations: `goeswith`
This relation is universal.
6 nodes (0%) are attached to their parents as `goeswith`.
6 instances of `goeswith` (100%) are left-to-right (parent precedes child).
Average distance between parent and child is 1.
The following 3 pairs of parts of speech are connected with `goeswith`: <tt><a href="yo_ytb-pos-AUX.html">AUX</a></tt>-<tt><a href="yo_ytb-pos-X.html">X</a></tt> (3; 50% instances), <tt><a href="yo_ytb-pos-ADV.html">ADV</a></tt>-<tt><a href="yo_ytb-pos-X.html">X</a></tt> (2; 33% instances), <tt><a href="yo_ytb-pos-NOUN.html">NOUN</a></tt>-<tt><a href="yo_ytb-pos-X.html">X</a></tt> (1; 17% instances).
~~~ conllu
# visual-style 20 bgColor:blue
# visual-style 20 fgColor:white
# visual-style 19 bgColor:blue
# visual-style 19 fgColor:white
# visual-style 19 20 goeswith color:blue
1 Àwọn Àwọn DET _ _ 2 det _ Ref=MARK_5.12|Gloss=the
2 ẹ̀mí ẹ̀mí NOUN _ _ 5 nsubj _ Ref=MARK_5.12|Gloss=spirit
3 àìmọ́ àìmọ́ ADJ _ _ 2 amod _ Ref=MARK_5.12|Gloss=unclean
4 náà náà DET _ _ 2 det _ Ref=MARK_5.12|Gloss=the
5 bẹ bẹ VERB _ _ 0 root _ Ref=MARK_5.12|Gloss=beg
6 Jésù Jésù PROPN _ _ 5 obj _ Ref=MARK_5.12|Gloss=jesus
7 pé pé SCONJ _ _ 12 mark _ Ref=MARK_5.12|SpaceAfter=No|Gloss=that
8 , , PUNCT _ _ 12 punct _ Ref=MARK_5.12|Gloss=,
9 “ “ PUNCT _ _ 12 punct _ Ref=MARK_5.12|SpaceAfter=No|Gloss=“
10 Rán rán VERB _ _ 12 ccomp _ Ref=MARK_5.12|Gloss=send
11 wa wa PRON _ Case=Acc|Number=Plur|Person=1|PronType=Prs 12 nsubj _ Ref=MARK_5.12|Gloss=us
12 lọ lọ VERB _ _ 5 ccomp _ Ref=MARK_5.12|Gloss=go
13 sínú sínú ADP _ _ 15 case _ Ref=MARK_5.12|Gloss=into
14 àwọn àwọn DET _ _ 15 det _ Ref=MARK_5.12|Gloss=the
15 ẹlẹ́dẹ̀ ẹlẹ́dẹ̀ NOUN _ _ 12 obl _ Ref=MARK_5.12|Gloss=swine
16 wọnni wọnni DET _ _ 12 det _ Ref=MARK_5.12|Gloss=those
17 kí kí AUX _ _ 21 aux _ Ref=MARK_5.12|Gloss=so
18 awa awa PRON _ Case=Acc|Number=Plur|Person=1|PronType=Prs 21 nsubj _ Ref=MARK_5.12|Gloss=we
19 le lè AUX _ Typo=Yes 21 aux _ Ref=MARK_5.12|Gloss=can
20 è è X _ Typo=Yes 19 goeswith _ Ref=MARK_5.12|Gloss=
21 wọ wọ VERB _ _ 16 xcomp _ Ref=MARK_5.12|Gloss=enter
22 inú inú ADP _ _ 23 case _ Ref=MARK_5.12|Gloss=into
23 wọn wọn PRON _ Case=Acc|Number=Plur|Person=3|PronType=Prs 21 obj _ Ref=MARK_5.12|Gloss=them
24 lọ lọ ADV _ _ 21 compound:svc _ Ref=MARK_5.12|SpaceAfter=No|Gloss=go
25 . . PUNCT _ _ 21 punct _ Ref=MARK_5.12|SpaceAfter=No|Gloss=.
26 ” ” PUNCT _ _ 21 punct _ Ref=MARK_5.12|Gloss=”
~~~
~~~ conllu
# visual-style 20 bgColor:blue
# visual-style 20 fgColor:white
# visual-style 19 bgColor:blue
# visual-style 19 fgColor:white
# visual-style 19 20 goeswith color:blue
1 Ṣùgbọ́n Ṣùgbọ́n CCONJ _ _ 5 cc _ Ref=MARK_5.36|Gloss=but
2 bi bí SCONJ _ Typo=Yes 5 mark _ Ref=MARK_5.36|Gloss=as
3 Jésù jésù PROPN _ _ 5 nsubj _ Ref=MARK_5.36|Gloss=jesus
4 ti ti AUX _ _ 5 aux _ Ref=MARK_5.36|Gloss=have
5 gbọ́ gbọ́ VERB _ _ 10 advcl _ Ref=MARK_5.36|Gloss=heard
6 ọ̀rọ̀ ọ̀rọ̀ NOUN _ _ 5 obj _ Ref=MARK_5.36|Gloss=word
7 náà náà DET _ _ 6 det _ Ref=MARK_5.36|SpaceAfter=No|Gloss=the
8 , , PUNCT _ _ 5 punct _ Ref=MARK_5.36|Gloss=,
9 ó ó PRON _ Case=Nom|Number=Sing|Person=3|PronType=Prs 10 nsubj _ Ref=MARK_5.36|Gloss=he
10 wí wí VERB _ _ 0 root _ Ref=MARK_5.36|Gloss=said
11 fún fún ADP _ _ 12 case _ Ref=MARK_5.36|Gloss=unto
12 Jáírù Jáírù PROPN _ _ 10 obl _ Ref=MARK_5.36|Gloss=jairus
13 pé pé SCONJ _ _ 17 mark _ Ref=MARK_5.36|SpaceAfter=No|Gloss=that
14 , , PUNCT _ _ 17 punct _ Ref=MARK_5.36|Gloss=,
15 “ “ PUNCT _ _ 17 punct _ Ref=MARK_5.36|SpaceAfter=No|Gloss=“
16 Má má AUX _ _ 17 aux _ Ref=MARK_5.36|Gloss=not
17 bẹ̀rù bẹ̀rù VERB _ _ 10 ccomp _ Ref=MARK_5.36|SpaceAfter=No|Gloss=fear
18 , , PUNCT _ _ 19 punct _ Ref=MARK_5.36|Gloss=,
19 sá sá ADV _ _ 17 advmod _ Ref=MARK_5.36|Gloss=just
20 à à X _ _ 19 goeswith _ Ref=MARK_5.36|Gloss=
21 gbà gbà VERB _ _ 19 acl _ Ref=MARK_5.36|Gloss=accept
22 mí mí PRON _ Case=Acc|Number=Sing|Person=1|PronType=Prs 21 obj _ Ref=MARK_5.36|Gloss=me
23 gbọ́ gbọ́ VERB _ _ 21 compound:svc _ Ref=MARK_5.36|Gloss=heard
24 nìkan nìkan ADV _ _ 23 advmod _ Ref=MARK_5.36|SpaceAfter=No|Gloss=only
25 . . PUNCT _ _ 17 punct _ Ref=MARK_5.36|SpaceAfter=No|Gloss=.
26 ” ” PUNCT _ _ 17 punct _ Ref=MARK_5.36|Gloss=.
~~~
~~~ conllu
# visual-style 7 bgColor:blue
# visual-style 7 fgColor:white
# visual-style 6 bgColor:blue
# visual-style 6 fgColor:white
# visual-style 6 7 goeswith color:blue
1 Ó Ó PRON _ Case=Nom|Number=Sing|Person=3|PronType=Prs 3 nsubj _ _
2 jẹ́ jẹ́ AUX _ _ 3 aux _ _
3 èso èso VERB _ _ 0 root _ _
4 ìfohùnṣọ̀kan ìfohùnṣọ̀kan ADV _ _ 3 advmod _ SpaceAfter=No
5 , , PUNCT _ _ 12 punct _ _
6 bẹ́ bẹ́ NOUN _ _ 12 discourse _ _
7 ẹ̀ ẹ̀ X _ _ 6 goeswith _ _
8 sì sì CCONJ _ _ 12 cc _ _
9 ni ni PART _ _ 10 case _ _
10 ó ó PRON _ Case=Nom|Number=Sing|Person=3|PronType=Prs 12 nsubj _ _
11 jẹ́ jẹ́ AUX _ _ 12 aux _ _
12 gbígbàgbọ́ gbígbàgbọ́ VERB _ _ 3 conj _ _
13 pé pé SCONJ _ _ 16 mark _ _
14 gbogbo gbogbo DET _ _ 16 det _ _
15 àwọn àwọn DET _ _ 16 det _ _
16 oníṣe oníṣe NOUN _ _ 12 obj _ _
17 gbọ́dọ̀ gbọ́dọ̀ ADV _ _ 18 advmod _ _
18 tẹ̀lé tẹ̀lé VERB _ _ 16 conj _ _
19 wọn wọn PRON _ Case=Acc|Number=Plur|Person=3|PronType=Prs 18 obj _ _
20 gbámúgbámú gbámúgbámú VERB _ _ 18 compound:svc _ SpaceAfter=No
21 . . PUNCT _ _ 3 punct _ SpacesAfter=\n\n
~~~
| 43.729508 | 403 | 0.7209 | yue_Hant | 0.360922 |
8a9520fcedea4d1501d9b49862d1cad3bcc6d16e | 15,037 | md | Markdown | README.md | dantman/package-ecma-version-field-spec | 4fccb40992b592d0003beb724622e352d2436312 | [
"CC-BY-4.0"
] | null | null | null | README.md | dantman/package-ecma-version-field-spec | 4fccb40992b592d0003beb724622e352d2436312 | [
"CC-BY-4.0"
] | 1 | 2021-09-09T12:51:08.000Z | 2021-09-09T12:51:08.000Z | README.md | dantman/package-ecma-version-field-spec | 4fccb40992b592d0003beb724622e352d2436312 | [
"CC-BY-4.0"
] | null | null | null | # package.json `"ecma"` version field spec
## Motivation
The adoption of ES2015 is growing. Node supports most of it natively and evergreen browsers can handle most of it. And it's going even further with Node.js and browsers natively supporting features from ES2017 and even a small portion of ES2018.
But we still need to transpile things to ES5 for some older but still relevant browsers. And even for evergreen browsers with full ES2017 support you may need to transpile some ES2018 code supported by Node if packages adopt it before 100% of evergreen browsers support it (e.g. native object rest/spread properties).
This leaves many users who bundle code for the browser using WebPack, Rollup, or another module bundler in a problematic situation.
- They need to output ES5 code to maintain the level of browser support they promise.
- Packages designed for Node.js may be using ES2015+ syntax which will break their code if bundled.
- Packages from portions of even the browser ecosystem such as the Polymer 3.0 ecosystem and some parts of the React ecosystem may be shipping ES2016+ code in their packages.
- Some packages offer multiple variants of their code such as an ES5, ES5 with ES2015 modules, and/or ES2015 code. Or ES2017 to the degree that it is supported by their target versions of Node.js and an ES5 bundle for browsers. So exactly what version of ECMAScript is in use is dependent on what part of the package is imported.
This leaves these users with only three options:
1. Don't transpile anything in node_modules: This of eventually course breaks because the user wants to start using a package that exports non-ES5 code.
2. Transpile everything in node_modules: This works, if you make sure to ignore `.babelrc`, but it is extremely inefficient and hurts performance as you are running the transpiler over all of the code, much of which is already pre-transpiled to ES5.
3. Manually maintain a list of packages to transpile. This is the approach used by many, however it is undesirable as this is a list that needs to be maintained as more and more packages begin shipping non-ES5 code in their packages.
## Overview
This spec defines a `"ecma"` field for `package.json`.
The value of the `ecma` field is an object with glob patterns as its keys and an ECMAScript edition number as its values.
Globs are used instead of extending the `engines` field to declare a single ECMAScript version as globs allow us to define the ECMAScript version for all variants within a package that bundles different variants for different versions of ECMAScript.
## Usage
A simple package that only uses ES5 code may simply declare all JS files as ES5.
```json
"ecma": {"*.js": 5}
```
If a package only targets node and the package maintainers write using ES2016 features but don't use any of the ES2017+ features Node supports they can declare all the JS files as ES2016.
```json
"ecma": {"*.js": 6}
```
If a package is written in ES2016 but defines an ES5 `browser.js` module to be delivered to browsers with `"browser"` that file can be declared separately:
```json
"ecma": {
"*.js": 6,
"browser.js": 5
}
```
If a package has two variants, CommonJS modules transpiled to ES5 in `lib/` and ES2015 modules in `modules/` for `"module"` that are otherwise transpiled to ES2015 both should be declared as ES5. For the purposes of the `ecma` field ES2015 modules are not considered to be ES2015 on their own if they are delivered through `module` with the intent of being used by WebPack/Rollup.
```json
"ecma": {"*.js": 5}
```
If a package has two variants like before, except the author has chosen that their ES2015 modules should retain ES2015 code other than the module syntax instead of being transpiled to ES5, then that code should be declared as ES2015.
```json
"ecma": {
"lib/**/*.js": 5,
"modules/**/*.js": 6
}
```
If a package delivers its source code alongside the ES5 bundled variant it should declare what version of ECMAScript the source uses.
```json
"ecma": {
"*.js": 5,
"src/**/*.js": 8
}
```
If features that have made it to Stage 4 and are planned to be included in the upcoming edition of the ECMAScript standard but are not yet standardized are used. Then the edition number of the ECMAScript standard they are expected to come out in may be used.
For example if source code is written using ES2017 code plus the currently Stage 4 "Rest/Spread Properties" that will be included in ES2018, the author may use `9` as the ECMA version. As given ES2017 is edition `8` of ECMAScript the ES2018 features will be part of edition `9`. This will tell the transpiler that transpiling ES2017 alone is not enough, but should be forward compatible such that in a couple of years when ES2018 is supported natively the transpiler does not think it still needs to transpile the package.
```json
"ecma": {
"*.js": 5,
"src/**/*.js": 9
}
```
Stage 0 - Stage 3 features that have not been standardized are not handled by the "ecma" field. The majority of these features are not available natively in browsers or any version of Node.js. A small number of Stage 3 candidates have some support in a few browsers, but not enough to consider publishing packages that require them. As such package maintainers that made use of Stage 0 – Stage 3 code in their packages are expected to at-minimum transpile the non-src Stage 0 – Stage 3 code in their packages.
Special syntaxes requiring transpiling such as JSX and Flow are not handled by the `ecma` field and must be handled in some other way.
As a more advanced example, here is the `ecma` field for a contrived package that has a `src/` written in ES2018 included in the package, an ES5 `index.js` and `lib/`, ES modules transpiled to ES5 in a `index.modules.js` and a `modules/` folder, an ES6 `index.es.js` and `es/` folder, and ESM `.mjs` code targeted at the level of ECMAScript supported by Node 10.
```json
"ecma": {
"index.js": 5,
"lib/**/*.js": 5,
"index.modules.js": 5,
"modules/**/*.js": 5,
"index.es.js": 6,
"es/**/*.js": 6,
"*.mjs": 9,
"src/**/*.js": 9
}
```
## Detailed design
### Versions
The version number must be the incrementing "Edition" number, not the year based numbering of the standard name. The intermediate `5.1` is not supported.
i.e. `5` for ES5, `6` for es6/ES2015, `7` for es7/ES2016, `8` for es8/ES2017, `9` for the upcoming es9/ES2018.
As a special case, ES2015 modules are **not** considered to be es6/ES2015 code **if** they are referred to using `"module"` instead of `"main"` and do not contain any other ES2016 syntax.
This allows for packages to contain code that is entirely transpiled to ES5 but offers a ES2016 modules variant using `"module"` that WebPack and Rollup can use to bundle and tree shake code, without requiring that the modules be transpiled.
### Globs
The glob implementation used must conform to the following rules:
- It must support the following Glob syntax:
`*`, `**`, `?`, `{a,b}`, `[a-c]`, `!(a|b)`, `?(a|b)`, `+(a|b)`, `*(a|b)`, `@(a|b)`
- It must not treat `#` as the start of a comment
- It must not treat `!` as the start of a negation
- It must use `/` as the directory separator
For reference, both the popular `minimatch`/`node-glob` and `micromatch` packages should be capable of conforming.
- Both libraries offer a `nonegate` option to disable negation behaviour
- `minimatch` has a `nocomment` option to desable comment behaviour, and `micromatch` does not appear to support comments
When evaluating the glob pattern, the search path of the glob should be relative to the root of the package.
When multiple glob patterns match a file, the glob pattern with the longest string length is used. The simplest way to handle this is to reverse sort by string length and test the longer glob matches first.
The behaviour when two globs are the same length and both match a file, such as `*.js` and `a.js` matching the file `a.js` is not defined. Single character file names should be rare and in the cases they exist generally will not require one to have a different ECMAScript version than the others. In the very rare case that this is necessary authors are expected to take advantage of the extra glob syntax that support is mandated for to craft a glob hack that will make the string the author wishes to have a higher specificity be longer. For example `[a].js`.
### Responsibilities of WebPack and other bundlers
Bundlers must read the `ecma` field and test files against the globs to check for an ECMAScript version. If an `ecma` field is present and a match is found for a file, the bundler must add this ECMAScript version to the metadata about the file that the bundler exposes to plugins/loaders and configuration.
As a special note for WebPack. The functional versions of the rule conditions in `modules.loaders.rules.*.use.*.{exclude,include}` should be given a second argument, this argument can either be a simple `{ecma: version}` object or can be the `NormalModule` WebPack exposes to other functions, which WebPack should expose an `.ecma = version` property on. This will allow users to write loader rules that include/exclude based on the `ecma` version of a file instead of just based on paths.
### Responsibilities of users and configuration
In a bundler like WebPack and Rollup where the user is responsible for configuring transpilers it is the user's responsibility to use the metadata exposed by the bundler to setup a transpiler that will transpile the code in node_modules for their environment.
For example, here is an example WebPack configuration for someone who transpiles their own code with babel-loader, outputs an ES5 bundle, and wants to transpile all ES2015+ package code with preset-env.
```js
module: {
loaders: [
// Transpile all my files according to my .babelrc
{
test: /\.jsx?$|\.mjs$/,
exclude: s => /node_modules/.test(s),
loader: 'babel-loader',
},
// Transpile node_modules only using preset-env,
// but exclude any files marked as es5
{
test: /\.jsx?$|\.mjs$/,
include: s => /node_modules/.test(s),
// Exclude files that do not have an `ecma` glob,
// or are defined as being ES5 or lower
exclude: (s, f) => !f.ecma || f.ecma <= 5,
loader: 'babel-loader',
options: {
// Do not get confused by any stray
// .babelrc files incorrectly left in packages
babelrc: false
// Only use the env preset
presets: ['@babel/preset-env'],
},
}
],
},
```
However for other bundlers that pride themselves on being pre-configured and ready to use out of the box. The bundler itself should be responsible for setting up a transpiler configuration that will transpile code in node_modules if it has a `ecma` field declaring the file a being a version that the bundler needs to have transpiled.
### Responsibilities of loaders and transpilers
Loaders and transpilers do not have any special responsibilities that are required of them here. However if it is possible it may be beneficial for loaders such as `babel-loader` to pass on the edition number extracted from `ecma` to presets. This way `@babel/preset-env` may have the option of skipping unnecessary transforms in the future.
i.e. If a file is defined as being written in ES2016 and `env` is targeting ES2015 the `env` can decide to exclude all the ES2017+ transforms and only have the cost of running transforms to transpile ES2016 to ES2015.
## Links
- [WebPack issue](https://github.com/webpack/webpack/issues/6918)
- [Rollup issue](https://github.com/rollup/rollup/issues/2104)
## *"Just transpile to ES5"*
There are a number of reasons why it does not make sense to require all npm packages transpile their default `main`'s code to ES5.
- Many packages are designed primarily for use in Node.js. At this point Node 4 is the lowest supported version, and it has partial ES2015 support. Very soon even that will be EOL and Node 6 will be the new minimum for many packages, which has [support for 99% of ES2015 features](http://node.green/). In one year Node 8 will be the minimum, and that has over [support for over 65% of ES2017](http://node.green/#ES2017) (that 65% effectively covers all the useful features of ES2017, most of the stuff that version does not support are less commonly used features like shared memory and atomics). It does not make sense to demand that packages designed primarily for use in Node.js all transpile their code to ES5 and forgo the advantages of native support just to support a small subset of the package's users that want to use the package in the browser.
- Using pre-transpiled ES5 code voids your ability to choose to ship ES2015 code. 80-90% of browsers currently in use have nearly complete support for ES2015. For some sites their target market may be nearly 100% composed of evergreen browsers with effectively complete ES2015 support. And for other sites, creating 2 bundles of their code and switching between (one for evergreen browsers with ES6 support and another for older browsers) may be beneficial enough to them to be worth the extra steps.
- Sometimes transpiling the ES6 code of a package to *ES5* yourself with env targets and other Babel optimizations specific to your environment can yield significant savings to the resulting code delivered to the browser. If all packages are pre-compiled to ES5 you lose this option.
- Some parts of ES2015+ such as generators and async functions require the regenerator runtime which is a significant size and unlike a polyfill cannot be omitted in environments with native support if it is used. If a package uses these features and we demand it is transpiled to ES5, the regenerator runtime will be a requirement in Node.js and evergreen browsers where there is enough native support of generators (and sometimes async functions) to not need regenerator.
- Some browser features such as natively supported Custom Elements require ES6 classes and do not work with ES5 transpiled code; unless you include an ES5 adapter that cannot be transpiled as part of your ES5 bundle and has some quirks when you include it. Parts of the ecosystem using these like Polymer 3.x **must** distribute ES6 code to avoid breakage in current browsers.
- Browsers are beginning to support ES2015 modules natively with `<script type="module">`. These modules are full ES2015 and do not require transpilation to ES5. `nomodule` is also available which begins to open up a browser supported method of having build tools generate an ES5 script bundle and an ES2015 module bundle and serve them separately to the browser without any special loader scripts.
## License
<a rel="license" href="http://creativecommons.org/licenses/by/4.0/"><img alt="Creative Commons Licence" style="border-width:0" src="https://i.creativecommons.org/l/by/4.0/88x31.png" /></a>
This document is licensed under a <a rel="license" href="http://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution 4.0 International License</a>. | 71.265403 | 855 | 0.757731 | eng_Latn | 0.999519 |
8a953c389de951a4d792c7303c005858eec1e58f | 1,491 | md | Markdown | README.md | Schutz-Rettung-Zurich/srz-hours | 68a9da68c4510efa96b0853cd67989022b4a4313 | [
"MIT"
] | 1 | 2020-10-28T06:14:01.000Z | 2020-10-28T06:14:01.000Z | README.md | Schutz-Rettung-Zurich/srz-hours | 68a9da68c4510efa96b0853cd67989022b4a4313 | [
"MIT"
] | null | null | null | README.md | Schutz-Rettung-Zurich/srz-hours | 68a9da68c4510efa96b0853cd67989022b4a4313 | [
"MIT"
] | null | null | null | # Schutz und Rettung - Öffnungszeiten Editor
Öffnungszeiten Editor für die Mapper von Schutz & Rettung und andere Interessierte.
## Anwendung
#### Link
[SRZ Hours im Internet](https://srzhours.srz.borsnet.ch)
### Kalenderansicht
Ziehe auf der Kalender-Ansicht die Öffnungszeiten die du gerne in opening_hours eintragen möchtest. Der Editor funktioniert hier wie ein normaler Kalender. Wenn du also Mo-Fr 08:00-17:00, Sa 08:00-13:30 eintragen willst, ziehe die Felder dieser Zeiten einfach auf dem Kalender (siehe Bild oben). Die Werte werden dann in OSM konformem Format in das Feld `opening_hours` geschrieben. Kopiere diesen Eintrag.
Solltest du andere Ansichten als die Wochenansicht benötigen, kannst du die Ansicht oben ändern. Diese Funktion hilft dir vor allem bei Einträgen die vorallem saisonal, resp. während wenigen Monaten verfügbar sind (z.B Badis).
### Werte in opening_hours
Die Werte die du im Formular erhältst und kopiert hast, musst du dann im ID Editor oder in JOSM in das Feld opening_hours schreiben:
`opening_hours = Wert aus dem Formular`
Nun kannst du deine Änderung im richtigen Format hochladen. Cool oder?
#### Credit
Die Software basiert auf dem von [Adrien Pavie](https://github.com/PanierAvide)'s erstellten
[YoHours Applikation](http://projets.pavie.info/yohours/) und wurde 1:1 übernommen.
#### License
Copyright 2015 Adrien PAVIE, 2020 Schutz & Rettung Zürich
See [LICENSE](LICENSE) for complete AGPL3 license.
| 40.297297 | 406 | 0.784038 | deu_Latn | 0.995371 |
8a95536b062a9dd1fd18dfbf333b5d41a55a0c2f | 3,865 | md | Markdown | doc/build-openbsd.md | bhccoin/bhcoin | a5a24c3f019893fdb04b38f24d0f76607deb2e8a | [
"MIT"
] | null | null | null | doc/build-openbsd.md | bhccoin/bhcoin | a5a24c3f019893fdb04b38f24d0f76607deb2e8a | [
"MIT"
] | null | null | null | doc/build-openbsd.md | bhccoin/bhcoin | a5a24c3f019893fdb04b38f24d0f76607deb2e8a | [
"MIT"
] | null | null | null | OpenBSD build guide
======================
(updated for OpenBSD 6.2)
This guide describes how to build bhcoind and command-line utilities on OpenBSD.
OpenBSD is most commonly used as a server OS, so this guide does not contain instructions for building the GUI.
Preparation
-------------
Run the following as root to install the base dependencies for building:
```bash
pkg_add git gmake libevent libtool
pkg_add autoconf # (select highest version, e.g. 2.69)
pkg_add automake # (select highest version, e.g. 1.15)
pkg_add python # (select highest version, e.g. 3.6)
pkg_add boost
git clone https://github.com/bhcoin/bhcoin.git
```
See [dependencies.md](dependencies.md) for a complete overview.
GCC
-------
The default C++ compiler that comes with OpenBSD 6.2 is g++ 4.2.1. This version is old (from 2007), and is not able to compile the current version of BHCoin Core because it has no C++11 support. We'll install a newer version of GCC:
```bash
pkg_add g++
```
This compiler will not overwrite the system compiler, it will be installed as `egcc` and `eg++` in `/usr/local/bin`.
### Building BerkeleyDB
BerkeleyDB is only necessary for the wallet functionality. To skip this, pass `--disable-wallet` to `./configure`.
See "Berkeley DB" in [build-unix.md](build-unix.md#berkeley-db) for instructions on how to build BerkeleyDB 4.8.
You cannot use the BerkeleyDB library from ports, for the same reason as boost above (g++/libstd++ incompatibility).
```bash
# Pick some path to install BDB to, here we create a directory within the bhcoin directory
BHCOIN_ROOT=$(pwd)
BDB_PREFIX="${BHCOIN_ROOT}/db4"
mkdir -p $BDB_PREFIX
# Fetch the source and verify that it is not tampered with
curl -o db-4.8.30.NC.tar.gz 'http://download.oracle.com/berkeley-db/db-4.8.30.NC.tar.gz'
echo '12edc0df75bf9abd7f82f821795bcee50f42cb2e5f76a6a281b85732798364ef db-4.8.30.NC.tar.gz' | sha256 -c
# MUST output: (SHA256) db-4.8.30.NC.tar.gz: OK
tar -xzf db-4.8.30.NC.tar.gz
# Build the library and install to specified prefix
cd db-4.8.30.NC/build_unix/
# Note: Do a static build so that it can be embedded into the executable, instead of having to find a .so at runtime
../dist/configure --enable-cxx --disable-shared --with-pic --prefix=$BDB_PREFIX CC=egcc CXX=eg++ CPP=ecpp
make install # do NOT use -jX, this is broken
```
### Resource limits
The standard ulimit restrictions in OpenBSD are very strict:
data(kbytes) 1572864
This, unfortunately, may no longer be enough to compile some `.cpp` files in the project,
at least with GCC 4.9.4 (see issue [#6658](https://github.com/bitcoin/bitcoin/issues/6658)).
If your user is in the `staff` group the limit can be raised with:
ulimit -d 3000000
The change will only affect the current shell and processes spawned by it. To
make the change system-wide, change `datasize-cur` and `datasize-max` in
`/etc/login.conf`, and reboot.
### Building BHCoin Core
**Important**: use `gmake`, not `make`. The non-GNU `make` will exit with a horrible error.
Preparation:
```bash
export AUTOCONF_VERSION=2.69 # replace this with the autoconf version that you installed
export AUTOMAKE_VERSION=1.15 # replace this with the automake version that you installed
./autogen.sh
```
Make sure `BDB_PREFIX` is set to the appropriate path from the above steps.
To configure with wallet:
```bash
./configure --with-gui=no CC=egcc CXX=eg++ CPP=ecpp \
BDB_LIBS="-L${BDB_PREFIX}/lib -ldb_cxx-4.8" BDB_CFLAGS="-I${BDB_PREFIX}/include"
```
To configure without wallet:
```bash
./configure --disable-wallet --with-gui=no CC=egcc CXX=eg++ CPP=ecpp
```
Build and run the tests:
```bash
gmake # use -jX here for parallelism
gmake check
```
Clang
------------------------------
```bash
pkg_add llvm
./configure --disable-wallet --with-gui=no CC=clang CXX=clang++
gmake # use -jX here for parallelism
gmake check
```
| 32.754237 | 232 | 0.726003 | eng_Latn | 0.967404 |
8a95c4ae1623fc24c967dcdb6577ec42cf46547e | 621 | md | Markdown | README.md | linuxbandit/ci-image-gcp | 788c85758a639299d323e5c12b9db367d9eafe9d | [
"MIT"
] | null | null | null | README.md | linuxbandit/ci-image-gcp | 788c85758a639299d323e5c12b9db367d9eafe9d | [
"MIT"
] | null | null | null | README.md | linuxbandit/ci-image-gcp | 788c85758a639299d323e5c12b9db367d9eafe9d | [
"MIT"
] | null | null | null | # Google cloud sdk with kubectl
Docker image with Google Cloud SDK and Kubectl. For use with [CI templates](https://github.com/jobtome-labs/ci-templates/).
It also includes:
- [kube-score](https://github.com/zegl/kube-score) (v1.2.1) not built from source.
- [sops](https://github.com/mozilla/sops) (v3.7.1) not built from source.
### Versions
|||
|-|-|
| cloud sdk | 299.0.0-alpine |
| kube-score | 1.2.1 |
| sops | 3.7.1 |
To override these default versions:
`docker build -t jobtome-labs/ci-image-gcp --build-arg CLOUD_SDK_VERSION=v9000 --build-arg KUBE_SCORE_VERSION=v1000 --build-arg SOPS_VERSION=v4000 .`
| 28.227273 | 149 | 0.706924 | eng_Latn | 0.337369 |
8a95e5dccb2a6ec7778ceee6fc28c90f3b9afcb0 | 8,574 | md | Markdown | docs/reporting-services/tools/rs-exe-utility-ssrs.md | kmivan/sql-docs | f3ec6088e1903e5cbeed53195cf6059b575ea051 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2022-02-16T12:10:42.000Z | 2022-02-16T12:10:42.000Z | docs/reporting-services/tools/rs-exe-utility-ssrs.md | kmivan/sql-docs | f3ec6088e1903e5cbeed53195cf6059b575ea051 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/reporting-services/tools/rs-exe-utility-ssrs.md | kmivan/sql-docs | f3ec6088e1903e5cbeed53195cf6059b575ea051 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: "RS.exe Utility | Microsoft Docs"
description: Learn about the commands and syntax for the rs.exe utility that processes scripts used to automate report server deployment and administration tasks.
ms.date: 03/16/2017
ms.prod: reporting-services
ms.prod_service: "reporting-services-native"
ms.technology: tools
ms.topic: conceptual
helpviewer_keywords:
- "automatic report server tasks"
- "rs utility"
- "command prompt utilities [Reporting Services]"
- "report servers [Reporting Services], automating tasks"
- "command prompt utilities [SQL Server], rs"
- "scripts [Reporting Services], command prompt"
- "deploying reports [Reporting Services]"
ms.assetid: bd6f958f-cce6-4e79-8a0f-9475da2919ce
author: maggiesMSFT
ms.author: maggies
---
# RS.exe Utility (SSRS)
The rs.exe utility processes script that you provide in an input file. Use this utility to automate report server deployment and administration tasks.
> [!NOTE]
> Beginning with [!INCLUDE[ssKilimanjaro](../../includes/sskilimanjaro-md.md)], the **rs** utility is supported against report servers that are configured for SharePoint integrated mode as well as servers configured in native mode. Previous versions only supported native mode configurations.
## Syntax
```
rs {-?}
{-i input_file}
{-s serverURL}
{-u username}
{-p password}
{-e endpoint}
{-l time_out}
{-b batchmode}
{-v globalvars=}
{-t trace}
```
## <a name="bkmk_filelocation"></a> File Location
**RS.exe** is located at **\Program Files\Microsoft SQL Server\110\Tools\Binn**. You can run the utility from any folder on your file system.
## <a name="bkmk_arguments"></a> Arguments
**-?**
(Optional) Displays the syntax of **rs** arguments.
**-i** *input_file*
(Required) Specifies the .rss file to execute. This value can be a relative or fully qualified path to the .rss file.
**-s** *serverURL*
(Required) Specifies the Web server name and report server virtual directory name to execute the file against. An example of a report server URL is `https://examplewebserver/reportserver`. The prefix http:// or https:// at the beginning of the server name is optional. If you omit the prefix, the report server script host tries to use https first, and then uses http if https does not work.
**-u** [*domain*\\]*username*
(Optional) Specifies a user account used to connect to the report server. If **-u** and **-p** are omitted, the current Windows user account is used.
**-p** *password*
(Required if **-u** is specified) Specifies the password to use with the **-u** argument. This value is case-sensitive.
**-e**
(Optional) Specifies the SOAP endpoint against which the script should run. Valid values are the following:
- Mgmt2010
- Mgmt2006
- Mgmt2005
- Exec2005
If a value is not specified, the Mgmt2005 endpoint is used. For more information about the SOAP endpoints, see [Report Server Web Service Endpoints](../../reporting-services/report-server-web-service/methods/report-server-web-service-endpoints.md).
**-l** *time_out*
(Optional) Specifies the number of seconds that elapse before the connection to the server times out. The default is 60 seconds. If you do not specify a time-out value, the default is used. A value of **0** specifies that the connection never times out.
**-b**
(Optional) Specifies that the commands in the script file run in a batch. If any commands fail, the batch is rolled back. Some commands cannot be batched, and those run as usual. Only exceptions that are thrown and are not handled within the script result in a rollback. If the script handles an exception and returns normally from **Main**, the batch is committed. If you omit this parameter, the commands run without creating a batch. For more information, see [Batching Methods](../../reporting-services/report-server-web-service-net-framework-soap-headers/batching-methods.md).
**-v** *globalvar*
(Optional) Specifies global variables that are used in the script. If the script uses global variables, you must specify this argument. The value that you specify must be valid for global variable defined in the .rss file. You must specify one global variable for each **-v** argument.
The **-v** argument is specified on the command line and is used to set the value for a global variable that is defined in your script at run time. For example, if your script contains a variable named *parentFolder*, you can specify a name for that folder on the command line:
`rs.exe -i myScriptFile.rss -s https://myServer/reportserver -v parentFolder="Financial Reports"`
Global variables are created with the names given and set to the values supplied. For example, **-v a=**"**1**" **-v b=**"**2**" results in a variable named **a** with a value of"**1**" and a variable **b** with a value of "**2**".
Global variables are available to any function in the script. A backslash and quotation mark (**\\"**) is interpreted as a double quotation mark. The quotation marks are required only if the string contains a space. Variable names must be valid for [!INCLUDE[msCoName](../../includes/msconame-md.md)] [!INCLUDE[vbprvb](../../includes/vbprvb-md.md)]; they must start with alphabetical character or underscore and contain alphabetical characters, digits, or underscores. Reserved words cannot be used as variable names. For more information about using global variables, see [Built-in Collections in Expressions (Report Builder and SSRS)](../../reporting-services/report-design/built-in-collections-in-expressions-report-builder.md).
**-t**
(Optional) Outputs error messages to the trace log. This argument does not take a value. For more information, see [Report Server Service Trace Log](../../reporting-services/report-server/report-server-service-trace-log.md).
## <a name="bkmk_permissions"></a> Permissions
To run the tool, you must have permission to connect to the report server instance you are running the script against. You can run scripts to make changes to the local computer or a remote computer. To make changes to a report server installed on a remote computer, specify the remote computer in the **-s** argument.
## <a name="bkmk_examples"></a> Examples
The following example illustrates how to specify the script file that contains [!INCLUDE[vbprvb](../../includes/vbprvb-md.md)] .NET script and Web service methods that you want to execute.
```
rs -i c:\scriptfiles\script_copycontent.rss -s https://localhost/reportserver
```
For a detailed example, see [Sample Reporting Services rs.exe Script to Copy Content between Report Servers](../../reporting-services/tools/sample-reporting-services-rs-exe-script-to-copy-content-between-report-servers.md).
For additional examples, see [Run a Reporting Services Script File](../../reporting-services/tools/run-a-reporting-services-script-file.md)
## Remarks
You can define scripts to set system properties, publish reports, and so forth. The scripts that you create can include any methods of the [!INCLUDE[ssRSnoversion](../../includes/ssrsnoversion-md.md)] API. For more information about the methods and properties available to you, see [Report Server Web Service](../../reporting-services/report-server-web-service/report-server-web-service.md).
The script must be written in [!INCLUDE[vbprvb](../../includes/vbprvb-md.md)] .NET code, and stored in a Unicode or UTF-8 text file with an .rss file name extension. You cannot debug scripts with the **rs** utility. To debug a script, run the code within [!INCLUDE[msCoName](../../includes/msconame-md.md)] [!INCLUDE[vsprvs](../../includes/vsprvs-md.md)].
> [!TIP]
> For a detailed example, see [Sample Reporting Services rs.exe Script to Copy Content between Report Servers](../../reporting-services/tools/sample-reporting-services-rs-exe-script-to-copy-content-between-report-servers.md).
## See Also
- [Run a Reporting Services Script File](../../reporting-services/tools/run-a-reporting-services-script-file.md)
- [Script Deployment and Administrative Tasks](../../reporting-services/tools/script-deployment-and-administrative-tasks.md)
- [Script with the rs.exe Utility and the Web Service](../../reporting-services/tools/script-with-the-rs-exe-utility-and-the-web-service.md)
- [Report Server Command Prompt Utilities (SSRS)](../../reporting-services/tools/report-server-command-prompt-utilities-ssrs.md)
| 68.047619 | 742 | 0.734313 | eng_Latn | 0.986813 |
8a96493eff49da0caaa575d9b61e7ba850d23f56 | 74 | md | Markdown | documentation/future_work/refactoring.md | fkleedorfer/webofneeds | c64a0889e7ac0f81c1f3a6a2d2b3f01372457686 | [
"Apache-2.0"
] | 55 | 2015-01-09T16:53:17.000Z | 2022-03-19T14:52:36.000Z | documentation/future_work/refactoring.md | fkleedorfer/webofneeds | c64a0889e7ac0f81c1f3a6a2d2b3f01372457686 | [
"Apache-2.0"
] | 1,965 | 2015-01-07T12:13:16.000Z | 2021-11-12T15:58:07.000Z | documentation/future_work/refactoring.md | fkleedorfer/webofneeds | c64a0889e7ac0f81c1f3a6a2d2b3f01372457686 | [
"Apache-2.0"
] | 21 | 2015-04-03T08:50:17.000Z | 2022-03-19T14:44:51.000Z | # Refactoring Opportunities
Here we collect ideas on how to improve WoN. | 24.666667 | 45 | 0.797297 | eng_Latn | 0.992646 |
8a96862fccdc0e02c0f32df0f0944c3595b9f234 | 1,422 | md | Markdown | components/icon/README.md | smilecc/mand-mobile | 4c8cfef527feab7b94f86751f551eecfc2c67698 | [
"Apache-2.0"
] | 1 | 2019-01-27T03:10:18.000Z | 2019-01-27T03:10:18.000Z | components/icon/README.md | smilecc/mand-mobile | 4c8cfef527feab7b94f86751f551eecfc2c67698 | [
"Apache-2.0"
] | 1 | 2019-04-22T02:58:33.000Z | 2019-04-22T02:58:33.000Z | components/icon/README.md | smilecc/mand-mobile | 4c8cfef527feab7b94f86751f551eecfc2c67698 | [
"Apache-2.0"
] | null | null | null | ---
title: Icon 图标
preview: https://didi.github.io/mand-mobile/examples/#/icon
---
SVG 图标
### 引入
```javascript
import { Icon } from 'mand-mobile'
Vue.component(Icon.name, Icon)
```
### 使用指南
组件库内置图标可直接使用，`arrow-up/down/left/right`, `circle-alert/cross/right`，`hollo-plus`，`cross`，`spinner`
其他自定义图标需使用<a href="https://github.com/kisenka/svg-sprite-loader" target="_blank">svg-sprite-loader</a>，svg文件名即图标名称
1. 安装依赖
```shell
npm install svg-sprite-loader --save-dev
```
2. webpack配置
```javascript
const path = require('path')
module.exports = {
module: {
loaders: [
{
test: /\.svg$/i,
loader: 'svg-sprite-loader',
include: [
// 将某个路径下所有svg交给 svg-sprite-loader 插件处理
path.resolve(__dirname, 'src/my-project-svg-folder')
],
}
]
}
}
```
3. 引入图标
```vue
<template>
<div>
<md-icon name="hello"></md-icon>
<md-icon name="world"></md-icon>
</div>
</template>
<script>
import 'src/my-project-svg-folder/hello.svg'
import 'src/my-project-svg-folder/world.svg'
import { Icon } from 'mand-mobile'
export default {
name: 'icon-demo',
components: {
[Icon.name]: Icon
}
}
</script>
```
### 代码演示
<!-- DEMO -->
### API
#### Icon Props
|属性 | 说明 | 类型 | 默认值| 备注|
|----|-----|------|------|------|
|name|图标名称|String|-|-|
|size|图标大小|String|`md`|`xs`, `sm`, `md`, `lg`|
|color|图标颜色|String|`currentColor`|该颜色值会作为`fill`的值被设置在`svg`图标上|
| 17.13253 | 115 | 0.598453 | yue_Hant | 0.216551 |
8a96ed87a49a22974e053ab7853e4d93bb381c8c | 1,460 | md | Markdown | docs/core/tools/dotnet-remove-reference.md | GeiGeiLa/docs.zh-tw | 88f98d80c8afc37c430f79fb76c5e14f11dce957 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/core/tools/dotnet-remove-reference.md | GeiGeiLa/docs.zh-tw | 88f98d80c8afc37c430f79fb76c5e14f11dce957 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/core/tools/dotnet-remove-reference.md | GeiGeiLa/docs.zh-tw | 88f98d80c8afc37c430f79fb76c5e14f11dce957 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: dotnet remove reference 命令 - .NET Core CLI
description: dotnet remove reference 命令提供方便的選項，以移除專案對專案參考。
author: mairaw
ms.author: mairaw
ms.date: 05/29/2018
ms.openlocfilehash: b281b255be7f49a99a6b4928c340cd4fb085f085
ms.sourcegitcommit: bbf70abe6b46073148f78cbf0619de6092b5800c
ms.translationtype: HT
ms.contentlocale: zh-TW
ms.lasthandoff: 06/04/2018
ms.locfileid: "34696227"
---
# <a name="dotnet-remove-reference"></a>dotnet remove reference
[!INCLUDE [topic-appliesto-net-core-all](../../../includes/topic-appliesto-net-core-all.md)]
## <a name="name"></a>名稱
`dotnet remove reference` - 移除專案對專案參考。
## <a name="synopsis"></a>概要
`dotnet remove [<PROJECT>] reference [-f|--framework] <PROJECT_REFERENCES> [-h|--help]`
## <a name="description"></a>描述
`dotnet remove reference` 命令提供方便的選項，以從專案中移除專案參考。
## <a name="arguments"></a>引數
`PROJECT`
目標專案檔。 如果未指定，命令會在目前的目錄中搜尋一個專案檔。
`PROJECT_REFERENCES`
要移除的專案對專案 (P2P) 參考。 您可以指定一或多個專案。 以 Unix/Linux 為基礎的終端機上支援 [Glob 模式 (英文)](https://en.wikipedia.org/wiki/Glob_(programming))。
## <a name="options"></a>選項
`-h|--help`
印出命令的簡短說明。
`-f|--framework <FRAMEWORK>`
只有在以特定[架構](../../standard/frameworks.md)為目標時，才能移除參考。
## <a name="examples"></a>範例
從指定的專案中移除專案參考：
`dotnet remove app/app.csproj reference lib/lib.csproj`
從目前目錄中的專案移除多個專案參考：
`dotnet remove reference lib1/lib1.csproj lib2/lib2.csproj`
在 Unix/Linux 上使用 Glob 模式移除多個專案參考︰
`dotnet remove app/app.csproj reference **/*.csproj`
| 23.174603 | 122 | 0.730137 | yue_Hant | 0.438706 |
8a97c7721c3448c2d6f1d71fbb044d9ef7e3eea7 | 23,354 | md | Markdown | docs/framework/winforms/controls/walkthrough-authoring-a-composite-control-with-visual-csharp.md | thomasgassmann/docs | 639902bb294048c8511fab5a297cafa7c4e7882a | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/winforms/controls/walkthrough-authoring-a-composite-control-with-visual-csharp.md | thomasgassmann/docs | 639902bb294048c8511fab5a297cafa7c4e7882a | [
"CC-BY-4.0",
"MIT"
] | 1 | 2019-10-18T18:30:39.000Z | 2019-10-18T18:30:39.000Z | docs/framework/winforms/controls/walkthrough-authoring-a-composite-control-with-visual-csharp.md | thomasgassmann/docs | 639902bb294048c8511fab5a297cafa7c4e7882a | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: "Walkthrough: Authoring a Composite Control with Visual C#"
ms.date: "03/30/2017"
helpviewer_keywords:
- "custom controls [C#]"
- "user controls [Windows Forms], creating with Visual C#"
- "UserControl class [Windows Forms], walkthroughs"
- "user controls [C#]"
- "custom controls [Windows Forms], creating"
ms.assetid: f88481a8-c746-4a36-9479-374ce5f2e91f
---
# Walkthrough: Authoring a Composite Control with Visual C# #
Composite controls provide a means by which custom graphical interfaces can be created and reused. A composite control is essentially a component with a visual representation. As such, it might consist of one or more Windows Forms controls, components, or blocks of code that can extend functionality by validating user input, modifying display properties, or performing other tasks required by the author. Composite controls can be placed on Windows Forms in the same manner as other controls. In the first part of this walkthrough, you create a simple composite control called `ctlClock`. In the second part of the walkthrough, you extend the functionality of `ctlClock` through inheritance.
> [!NOTE]
> The dialog boxes and menu commands you see might differ from those described in Help depending on your active settings or edition. To change your settings, choose **Import and Export Settings** on the **Tools** menu. For more information, see [Personalize the Visual Studio IDE](/visualstudio/ide/personalizing-the-visual-studio-ide).
## Creating the Project
When you create a new project, you specify its name to set the root namespace, assembly name, and project name, and ensure that the default component will be in the correct namespace.
#### To create the ctlClockLib control library and the ctlClock control
1. On the **File** menu, point to **New**, and then click **Project** to open the **New Project** dialog box.
2. From the list of Visual C# projects, select the **Windows Forms Control Library** project template, type `ctlClockLib` in the **Name** box, and then click **OK**.
The project name, `ctlClockLib`, is also assigned to the root namespace by default. The root namespace is used to qualify the names of components in the assembly. For example, if two assemblies provide components named `ctlClock`, you can specify your `ctlClock` component using `ctlClockLib.ctlClock.`
3. In Solution Explorer, right-click **UserControl1.cs**, and then click **Rename**. Change the file name to `ctlClock.cs`. Click the **Yes** button when you are asked if you want to rename all references to the code element "UserControl1".
> [!NOTE]
> By default, a composite control inherits from the <xref:System.Windows.Forms.UserControl> class provided by the system. The <xref:System.Windows.Forms.UserControl> class provides functionality required by all composite controls, and implements standard methods and properties.
4. On the **File** menu, click **Save All** to save the project.
## Adding Windows Controls and Components to the Composite Control
A visual interface is an essential part of your composite control. This visual interface is implemented by the addition of one or more Windows controls to the designer surface. In the following demonstration, you will incorporate Windows controls into your composite control and write code to implement functionality.
#### To add a Label and a Timer to your composite control
1. In Solution Explorer, right-click **ctlClock.cs**, and then click **View Designer**.
2. In the **Toolbox**, expand the **Common Controls** node, and then double-click **Label**.
A <xref:System.Windows.Forms.Label> control named `label1` is added to your control on the designer surface.
3. In the designer, click **label1**. In the Properties window, set the following properties.
|Property|Change to|
|--------------|---------------|
|**Name**|`lblDisplay`|
|**Text**|`(blank space)`|
|**TextAlign**|`MiddleCenter`|
|**Font.Size**|`14`|
4. In the **Toolbox**, expand the **Components** node, and then double-click **Timer**.
Because a <xref:System.Windows.Forms.Timer> is a component, it has no visual representation at run time. Therefore, it does not appear with the controls on the designer surface, but rather in the **Component Designer** (a tray at the bottom of the designer surface).
5. In the **Component Designer**, click **timer1**, and then set the <xref:System.Windows.Forms.Timer.Interval%2A> property to `1000` and the <xref:System.Windows.Forms.Timer.Enabled%2A> property to `true`.
The <xref:System.Windows.Forms.Timer.Interval%2A> property controls the frequency with which the <xref:System.Windows.Forms.Timer> component ticks. Each time `timer1` ticks, it runs the code in the `timer1_Tick` event. The interval represents the number of milliseconds between ticks.
6. In the **Component Designer**, double-click **timer1** to go to the `timer1_Tick` event for `ctlClock`.
7. Modify the code so that it resembles the following code sample. Be sure to change the access modifier from `private` to `protected`.
```csharp
protected void timer1_Tick(object sender, System.EventArgs e)
{
// Causes the label to display the current time.
lblDisplay.Text = DateTime.Now.ToLongTimeString();
}
```
This code will cause the current time to be shown in `lblDisplay`. Because the interval of `timer1` was set to `1000`, this event will occur every thousand milliseconds, thus updating the current time every second.
8. Modify the method to be overridable with the `virtual` keyword. For more information, see the "Inheriting from a User Control" section below.
```csharp
protected virtual void timer1_Tick(object sender, System.EventArgs e)
```
9. On the **File** menu, click **Save All** to save the project.
## Adding Properties to the Composite Control
Your clock control now encapsulates a <xref:System.Windows.Forms.Label> control and a <xref:System.Windows.Forms.Timer> component, each with its own set of inherent properties. While the individual properties of these controls will not be accessible to subsequent users of your control, you can create and expose custom properties by writing the appropriate blocks of code. In the following procedure, you will add properties to your control that enable the user to change the color of the background and text.
#### To add a property to your composite control
1. In Solution Explorer, right-click **ctlClock.cs**, and then click **View Code**.
The **Code Editor** for your control opens.
2. Locate the `public partial class ctlClock` statement. Beneath the opening brace (`{)`, type the following code.
```csharp
private Color colFColor;
private Color colBColor;
```
These statements create the private variables that you will use to store the values for the properties you are about to create.
3. Type the following code beneath the variable declarations from step 2.
```csharp
// Declares the name and type of the property.
public Color ClockBackColor
{
// Retrieves the value of the private variable colBColor.
get
{
return colBColor;
}
// Stores the selected value in the private variable colBColor, and
// updates the background color of the label control lblDisplay.
set
{
colBColor = value;
lblDisplay.BackColor = colBColor;
}
}
// Provides a similar set of instructions for the foreground color.
public Color ClockForeColor
{
get
{
return colFColor;
}
set
{
colFColor = value;
lblDisplay.ForeColor = colFColor;
}
}
```
The preceding code makes two custom properties, `ClockForeColor` and `ClockBackColor`, available to subsequent users of this control. The `get` and `set` statements provide for storage and retrieval of the property value, as well as code to implement functionality appropriate to the property.
4. On the **File** menu, click **Save All** to save the project.
## Testing the Control
Controls are not stand-alone applications; they must be hosted in a container. Test your control's run-time behavior and exercise its properties with the **UserControl Test Container**. For more information, see [How to: Test the Run-Time Behavior of a UserControl](../../../../docs/framework/winforms/controls/how-to-test-the-run-time-behavior-of-a-usercontrol.md).
#### To test your control
1. Press F5 to build the project and run your control in the **UserControl Test Container**.
2. In the test container's property grid, locate the `ClockBackColor` property, and then select the property to display the color palette.
3. Choose a color by clicking it.
The background color of your control changes to the color you selected.
4. Use a similar sequence of events to verify that the `ClockForeColor` property is functioning as expected.
In this section and the preceding sections, you have seen how components and Windows controls can be combined with code and packaging to provide custom functionality in the form of a composite control. You have learned to expose properties in your composite control, and how to test your control after it is complete. In the next section you will learn how to construct an inherited composite control using `ctlClock` as a base.
## Inheriting from a Composite Control
In the previous sections, you learned how to combine Windows controls, components, and code into reusable composite controls. Your composite control can now be used as a base upon which other controls can be built. The process of deriving a class from a base class is called *inheritance*. In this section, you will create a composite control called `ctlAlarmClock`. This control will be derived from its parent control, `ctlClock`. You will learn to extend the functionality of `ctlClock` by overriding parent methods and adding new methods and properties.
The first step in creating an inherited control is to derive it from its parent. This action creates a new control that has all of the properties, methods, and graphical characteristics of the parent control, but can also act as a base for the addition of new or modified functionality.
#### To create the inherited control
1. In Solution Explorer, right-click **ctlClockLib**, point to **Add**, and then click **User Control**.
The **Add New Item** dialog box opens.
2. Select the **Inherited User Control** template.
3. In the **Name** box, type `ctlAlarmClock.cs`, and then click **Add**.
The **Inheritance Picker** dialog box appears.
4. Under **Component Name**, double-click **ctlClock**.
5. In Solution Explorer, browse through the current projects.
> [!NOTE]
> A file called **ctlAlarmClock.cs** has been added to the current project.
### Adding the Alarm Properties
Properties are added to an inherited control in the same way they are added to a composite control. You will now use the property declaration syntax to add two properties to your control: `AlarmTime`, which will store the value of the date and time the alarm is to go off, and `AlarmSet`, which will indicate whether the alarm is set.
##### To add properties to your composite control
1. In Solution Explorer, right-click **ctlAlarmClock**, and then click **View Code**.
2. Locate the `public class` statement. Note that your control inherits from `ctlClockLib.ctlClock`. Beneath the opening brace (`{)` statement, type the following code.
```csharp
private DateTime dteAlarmTime;
private bool blnAlarmSet;
// These properties will be declared as public to allow future
// developers to access them.
public DateTime AlarmTime
{
get
{
return dteAlarmTime;
}
set
{
dteAlarmTime = value;
}
}
public bool AlarmSet
{
get
{
return blnAlarmSet;
}
set
{
blnAlarmSet = value;
}
}
```
### Adding to the Graphical Interface of the Control
Your inherited control has a visual interface that is identical to the control it inherits from. It possesses the same constituent controls as its parent control, but the properties of the constituent controls will not be available unless they were specifically exposed. You may add to the graphical interface of an inherited composite control in the same manner as you would add to any composite control. To continue adding to your alarm clock's visual interface, you will add a label control that will flash when the alarm is sounding.
##### To add the label control
1. In Solution Explorer, right-click **ctlAlarmClock**, and then click **View Designer**.
The designer for `ctlAlarmClock` opens in the main window.
2. Click the display portion of the control, and view the Properties window.
> [!NOTE]
> While all the properties are displayed, they are dimmed. This indicates that these properties are native to `lblDisplay` and cannot be modified or accessed in the Properties window. By default, controls contained in a composite control are `private`, and their properties are not accessible by any means.
> [!NOTE]
> If you want subsequent users of your composite control to have access to its internal controls, declare them as `public` or `protected`. This will allow you to set and modify properties of controls contained within your composite control by using the appropriate code.
3. Add a <xref:System.Windows.Forms.Label> control to your composite control.
4. Using the mouse, drag the <xref:System.Windows.Forms.Label> control immediately beneath the display box. In the Properties window, set the following properties.
|Property|Setting|
|--------------|-------------|
|**Name**|`lblAlarm`|
|**Text**|**Alarm!**|
|**TextAlign**|`MiddleCenter`|
|**Visible**|`false`|
### Adding the Alarm Functionality
In the previous procedures, you added properties and a control that will enable alarm functionality in your composite control. In this procedure, you will add code to compare the current time to the alarm time and, if they are the same, to flash an alarm. By overriding the `timer1_Tick` method of `ctlClock` and adding additional code to it, you will extend the capability of `ctlAlarmClock` while retaining all of the inherent functionality of `ctlClock`.
##### To override the timer1_Tick method of ctlClock
1. In the **Code Editor**, locate the `private bool blnAlarmSet;` statement. Immediately beneath it, add the following statement.
```csharp
private bool blnColorTicker;
```
2. In the **Code Editor**, locate the closing brace (`})` at the end of the class. Just before the brace, add the following code.
```csharp
protected override void timer1_Tick(object sender, System.EventArgs e)
{
// Calls the Timer1_Tick method of ctlClock.
base.timer1_Tick(sender, e);
// Checks to see if the alarm is set.
if (AlarmSet == false)
return;
else
// If the date, hour, and minute of the alarm time are the same as
// the current time, flash an alarm.
{
if (AlarmTime.Date == DateTime.Now.Date && AlarmTime.Hour ==
DateTime.Now.Hour && AlarmTime.Minute == DateTime.Now.Minute)
{
// Sets lblAlarmVisible to true, and changes the background color based on
// the value of blnColorTicker. The background color of the label
// will flash once per tick of the clock.
lblAlarm.Visible = true;
if (blnColorTicker == false)
{
lblAlarm.BackColor = Color.Red;
blnColorTicker = true;
}
else
{
lblAlarm.BackColor = Color.Blue;
blnColorTicker = false;
}
}
else
{
// Once the alarm has sounded for a minute, the label is made
// invisible again.
lblAlarm.Visible = false;
}
}
}
```
The addition of this code accomplishes several tasks. The `override` statement directs the control to use this method in place of the method that was inherited from the base control. When this method is called, it calls the method it overrides by invoking the `base.timer1_Tick` statement, ensuring that all of the functionality incorporated in the original control is reproduced in this control. It then runs additional code to incorporate the alarm functionality. A flashing label control will appear when the alarm occurs.
Your alarm clock control is almost complete. The only thing that remains is to implement a way to turn it off. To do this, you will add code to the `lblAlarm_Click` method.
##### To implement the shutoff method
1. In Solution Explorer, right-click **ctlAlarmClock.cs**, and then click **View Designer**.
The designer opens.
2. Add a button to the control. Set the properties of the button as follows.
|Property|Value|
|--------------|-----------|
|**Name**|`btnAlarmOff`|
|**Text**|**Disable Alarm**|
3. In the designer, double-click **btnAlarmOff**.
The **Code Editor** opens to the `private void btnAlarmOff_Click` line.
4. Modify this method so that it resembles the following code.
```csharp
private void btnAlarmOff_Click(object sender, System.EventArgs e)
{
// Turns off the alarm.
AlarmSet = false;
// Hides the flashing label.
lblAlarm.Visible = false;
}
```
5. On the **File** menu, click **Save All** to save the project.
### Using the Inherited Control on a Form
You can test your inherited control the same way you tested the base class control, `ctlClock`: Press F5 to build the project and run your control in the **UserControl Test Container**. For more information, see [How to: Test the Run-Time Behavior of a UserControl](../../../../docs/framework/winforms/controls/how-to-test-the-run-time-behavior-of-a-usercontrol.md).
To put your control to use, you will need to host it on a form. As with a standard composite control, an inherited composite control cannot stand alone and must be hosted in a form or other container. Since `ctlAlarmClock` has a greater depth of functionality, additional code is required to test it. In this procedure, you will write a simple program to test the functionality of `ctlAlarmClock`. You will write code to set and display the `AlarmTime` property of `ctlAlarmClock`, and will test its inherent functions.
##### To build and add your control to a test form
1. In Solution Explorer, right-click **ctlClockLib**, and then click **Build**.
2. Add a new **Windows Application** project to the solution, and name it `Test`.
3. In Solution Explorer, right-click the **References** node for your test project. Click **Add Reference** to display the **Add Reference** dialog box. Click the tab labeled **Projects**. Your `ctlClockLib` project will be listed under **Project Name**. Double-click the project to add the reference to the test project.
4. In Solution Explorer, right-click **Test**, and then click **Build**.
5. In the **Toolbox**, expand the **ctlClockLib Components** node.
6. Double-click **ctlAlarmClock** to add a copy of `ctlAlarmClock` to your form.
7. In the **Toolbox**, locate and double-click **DateTimePicker** to add a <xref:System.Windows.Forms.DateTimePicker> control to your form, and then add a <xref:System.Windows.Forms.Label> control by double-clicking **Label**.
8. Use the mouse to position the controls in a convenient place on the form.
9. Set the properties of these controls in the following manner.
|Control|Property|Value|
|-------------|--------------|-----------|
|`label1`|**Text**|`(blank space)`|
||**Name**|`lblTest`|
|`dateTimePicker1`|**Name**|`dtpTest`|
||**Format**|<xref:System.Windows.Forms.DateTimePickerFormat.Time>|
10. In the designer, double-click **dtpTest**.
The **Code Editor** opens to `private void dtpTest_ValueChanged`.
11. Modify the code so that it resembles the following.
```csharp
private void dtpTest_ValueChanged(object sender, System.EventArgs e)
{
ctlAlarmClock1.AlarmTime = dtpTest.Value;
ctlAlarmClock1.AlarmSet = true;
lblTest.Text = "Alarm Time is " +
ctlAlarmClock1.AlarmTime.ToShortTimeString();
}
```
12. In Solution Explorer, right-click **Test**, and then click **Set as StartUp Project**.
13. On the **Debug** menu, click **Start Debugging**.
The test program starts. Note that the current time is updated in the `ctlAlarmClock` control, and that the starting time is shown in the <xref:System.Windows.Forms.DateTimePicker> control.
14. Click the <xref:System.Windows.Forms.DateTimePicker> where the minutes of the hour are displayed.
15. Using the keyboard, set a value for minutes that is one minute greater than the current time shown by `ctlAlarmClock`.
The time for the alarm setting is shown in `lblTest`. Wait for the displayed time to reach the alarm setting time. When the displayed time reaches the time to which the alarm is set, the `lblAlarm` will flash.
16. Turn off the alarm by clicking `btnAlarmOff`. You may now reset the alarm.
This walkthrough has covered a number of key concepts. You have learned to create a composite control by combining controls and components into a composite control container. You have learned to add properties to your control, and to write code to implement custom functionality. In the last section, you learned to extend the functionality of a given composite control through inheritance, and to alter the functionality of host methods by overriding those methods.
## See also
- [Varieties of Custom Controls](../../../../docs/framework/winforms/controls/varieties-of-custom-controls.md)
- [How to: Display a Control in the Choose Toolbox Items Dialog Box](../../../../docs/framework/winforms/controls/how-to-display-a-control-in-the-choose-toolbox-items-dialog-box.md)
- [Walkthrough: Inheriting from a Windows Forms Control with Visual C#](../../../../docs/framework/winforms/controls/walkthrough-inheriting-from-a-windows-forms-control-with-visual-csharp.md)
| 57.664198 | 695 | 0.690546 | eng_Latn | 0.994793 |
8a9852a076321953dc48e1d798d4844b6b999ef1 | 340 | md | Markdown | README.md | shiyuanyou/ohmyzsh | 50c52294bb6d2898fc2cc233e3d7a8b83a9d9456 | [
"MIT"
] | null | null | null | README.md | shiyuanyou/ohmyzsh | 50c52294bb6d2898fc2cc233e3d7a8b83a9d9456 | [
"MIT"
] | null | null | null | README.md | shiyuanyou/ohmyzsh | 50c52294bb6d2898fc2cc233e3d7a8b83a9d9456 | [
"MIT"
] | null | null | null | # Oh-my-zsh (Personal settings)
This repositorie is forked from [oh-my-zh](https://github.com/ohmyzsh/ohmyzsh).
Since i have some laptop, and i want make work env to new laptop easy easily. So
I make this res to keep some setting for myself.
## Before install oh-my-zsh
Before install oh-my-zsh, you should install zsh, git and so on.
| 30.909091 | 80 | 0.744118 | eng_Latn | 0.994548 |
8a9930d258760a8ba37dd18bbfb8e9fad341d7f8 | 1,414 | md | Markdown | content/zh/blog/go/basic/go_type_casting.md | xueqing/myblog | b37876cc1f7bcaaa987a57626b7dae0e944c868f | [
"MIT"
] | null | null | null | content/zh/blog/go/basic/go_type_casting.md | xueqing/myblog | b37876cc1f7bcaaa987a57626b7dae0e944c868f | [
"MIT"
] | null | null | null | content/zh/blog/go/basic/go_type_casting.md | xueqing/myblog | b37876cc1f7bcaaa987a57626b7dae0e944c868f | [
"MIT"
] | 2 | 2020-06-24T06:23:41.000Z | 2020-10-08T10:26:37.000Z | ---
title: "go 类型转换"
authors: [kiki]
tags: [go]
categories: [blog]
draft: false
---
## 类型声明
`type` 声明定义一个新的命名类型，它和某个已有类型使用同样的底层类型。命名；类型提供了一种方式来区分底层类型的不同或不兼容使用，这样就不会在无意中混用他们。
比如，把不同计量单位的温度值转换为不同的类型。即使使用的底层类型相同，二者是不是相同的类型，不能使用算术表达式进行比较和合并。
```go
package main
import "fmt"
type celsius float64
type fahrenheit float64
const (
absoluteZeroC celsius = -273.15
freezingC celsius = 0
boilingC celsius = 100
)
func main() {
fmt.Printf("cToF(%2f) = (%2f)\n", absoluteZeroC, cToF(absoluteZeroC))
// error:cannot use boilingC (type celsius) as type fahrenheit in argument to fToC
fmt.Printf("fToC(%2f) = (%2f)\n", boilingC, fToC(boilingC))
fmt.Printf("fToC(%2f) = (%2f)\n", boilingC, fToC(fahrenheit(boilingC)))
}
func cToF(c celsius) fahrenheit { return fahrenheit(c*9/5 + 32) }
func fToC(f fahrenheit) celsius { return celsius((f - 32) * 5 / 9) }
```
## 类型转换
对于每个类型 T，都有一个对应的类型转换操作 T(x) 将值转化为类型 T。如果两个类型具有相同的底层类型或二者都是指向相同底层类型变量的未命名指针类型，则二者可以相互转化。类型转化不改变；类型值的表达方式，仅改变类型。如果 x 对于类型 T 是可赋值的，类型转化也是允许的，但是通常是不必要的。
- 类型转换用于将一种数据类型的变量转换为另一种类型的变量，go 不支持隐式类型转换
```go
package main
import (
"fmt"
"math"
)
func main() {
var x, y int = 3, 4
var f float64 = math.Sqrt(float64(x*x + y*y))
var z uint = f //error: cannot use f (type float64) as type uint in assignment
fmt.Println(x, y, z)
}
```
- 格式`type_name(expression)`
- type_name 是类型
- expression 是表达式
| 21.753846 | 148 | 0.687412 | kor_Hang | 0.146575 |
8a99b74b1a117dbb5ced8004897e4e87e7774800 | 2,166 | md | Markdown | docs/visual-basic/programming-guide/concepts/linq/serializing-to-files-textwriters-and-xmlwriters.md | Dodozz/docs.it-it | f34c4bb1e8afb7492f8512359d32a9156c9c768d | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/visual-basic/programming-guide/concepts/linq/serializing-to-files-textwriters-and-xmlwriters.md | Dodozz/docs.it-it | f34c4bb1e8afb7492f8512359d32a9156c9c768d | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/visual-basic/programming-guide/concepts/linq/serializing-to-files-textwriters-and-xmlwriters.md | Dodozz/docs.it-it | f34c4bb1e8afb7492f8512359d32a9156c9c768d | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: La serializzazione per il file, TextWriter e XmlWriters3
ms.date: 07/20/2015
ms.assetid: 7a0c24df-79ef-41a0-87f5-e6cf79382da9
ms.openlocfilehash: 63577d955da89fde0a2320b4cf84414ccbb69c84
ms.sourcegitcommit: 9b552addadfb57fab0b9e7852ed4f1f1b8a42f8e
ms.translationtype: MT
ms.contentlocale: it-IT
ms.lasthandoff: 04/23/2019
ms.locfileid: "61786789"
---
# <a name="serializing-to-files-textwriters-and-xmlwriters"></a>Serializzazione in base a File, TextWriter e XmlWriter
È possibile serializzare gli alberi XML in un oggetto <xref:System.IO.File>, <xref:System.IO.TextWriter> o <xref:System.Xml.XmlWriter>.
È possibile serializzare qualsiasi componente XML, incluso <xref:System.Xml.Linq.XDocument> e <xref:System.Xml.Linq.XElement>, in una stringa usando il metodo `ToString`.
Per eliminare la formattazione quando si esegue la serializzazione in una stringa, usare il metodo <xref:System.Xml.Linq.XNode.ToString%2A?displayProperty=nameWithType>.
Il comportamento predefinito quando si esegue la serializzazione in un file implica la formattazione, ovvero l'impostazione di rientri, nel documento XML risultante. Quando si impostano i rientri, lo spazio vuoto non significativo nell'albero XML non viene conservato. Per serializzare e formattare al contempo il documento, usare uno degli overload dei metodi seguenti che non accettano <xref:System.Xml.Linq.SaveOptions> come argomento:
- <xref:System.Xml.Linq.XDocument.Save%2A?displayProperty=nameWithType>
- <xref:System.Xml.Linq.XElement.Save%2A?displayProperty=nameWithType>
Se si desidera applicare l'opzione per non impostare i rientri e conservare lo spazio vuoto non significativo nell'albero XML, usare uno degli overload dei metodi seguenti che accettano <xref:System.Xml.Linq.SaveOptions> come argomento:
- <xref:System.Xml.Linq.XDocument.Save%2A?displayProperty=nameWithType>
- <xref:System.Xml.Linq.XElement.Save%2A?displayProperty=nameWithType>
Per gli esempi, vedere l'argomento di riferimento appropriato.
## <a name="see-also"></a>Vedere anche
- [Serializzazione di alberi XML (Visual Basic)](../../../../visual-basic/programming-guide/concepts/linq/serializing-xml-trees.md)
| 58.540541 | 438 | 0.807018 | ita_Latn | 0.944614 |
8a99e3a0364d85c72a759e4a4532b88ae89db0d3 | 43,454 | md | Markdown | plugins/techdocs-node/CHANGELOG.md | Bonial-International-GmbH/backstage | d9f86c2d81d85975d89729df905c2f4c26736060 | [
"Apache-2.0"
] | null | null | null | plugins/techdocs-node/CHANGELOG.md | Bonial-International-GmbH/backstage | d9f86c2d81d85975d89729df905c2f4c26736060 | [
"Apache-2.0"
] | null | null | null | plugins/techdocs-node/CHANGELOG.md | Bonial-International-GmbH/backstage | d9f86c2d81d85975d89729df905c2f4c26736060 | [
"Apache-2.0"
] | null | null | null | # @backstage/plugin-techdocs-node
## 1.1.3-next.0
### Patch Changes
- Updated dependencies
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
## 1.1.2
### Patch Changes
- f5283a42e2: Updated dependency `@google-cloud/storage` to `^6.0.0`.
- 2c048f8b90: Updated deprecated use of `express`' `res.redirect()` method when handling legacy path casing.
- Updated dependencies
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
## 1.1.2-next.2
### Patch Changes
- Updated dependencies
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
## 1.1.2-next.1
### Patch Changes
- Updated dependencies
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
## 1.1.2-next.0
### Patch Changes
- Updated dependencies
- @backstage/[email protected]
- @backstage/[email protected]
## 1.1.1
### Patch Changes
- cfc0f19699: Updated dependency `fs-extra` to `10.1.0`.
- c2a1d8935e: Updated the default version of the `@spotify/techdocs` container used when `techdocs.generator.runIn` is `docker` to `v1.0.3`.
- b26f4cb6a1: Allow usage of custom tags with sequence node type (such as the !ENV tag) in the techdocs mkdocs config.
- Updated dependencies
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
## 1.1.1-next.1
### Patch Changes
- Updated dependencies
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
## 1.1.1-next.0
### Patch Changes
- cfc0f19699: Updated dependency `fs-extra` to `10.1.0`.
- b26f4cb6a1: Allow usage of custom tags with sequence node type (such as the !ENV tag) in the techdocs mkdocs config.
- Updated dependencies
- @backstage/[email protected]
- @backstage/[email protected]
## 1.1.0
### Minor Changes
- bcf1a2496c: Removed an undocumented, broken behavior where `README.md` files would be copied to `index.md` if it did not exist, leading to broken links in the TechDocs UI.
### Patch Changes
- 9fa68705bf: The default container version used to generate TechDocs content is now `v1.0.2`.
- Updated dependencies
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
## 1.1.0-next.2
### Minor Changes
- bcf1a2496c: BREAKING: The default Techdocs behavior will no longer attempt to copy `docs/README.md` or `README.md` to `docs/index.md` (if not found). To retain this behavior in your instance, you can set the following config in your `app-config.yaml`:
```yaml
techdocs:
generator:
mkdocs:
legacyCopyReadmeMdToIndexMd: true
```
### Patch Changes
- Updated dependencies
- @backstage/[email protected]
- @backstage/[email protected]
## 1.0.1-next.1
### Patch Changes
- Updated dependencies
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
## 1.0.1-next.0
### Patch Changes
- Updated dependencies
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
## 1.0.0
### Major Changes
- b58c70c223: This package has been promoted to v1.0! To understand how this change affects the package, please check out our [versioning policy](https://backstage.io/docs/overview/versioning-policy).
### Minor Changes
- 700d93ff41: - `DirectoryPreparer` now uses private constructor. Use static fromConfig method to instantiate.
- `UrlPreparer` now uses private constructor. Use static fromConfig method to instantiate.
### Patch Changes
- f24ef7864e: Minor typo fixes
- Updated dependencies
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
## 0.11.12
### Patch Changes
- e0a69ba49f: build(deps): bump `fs-extra` from 9.1.0 to 10.0.1
- 3e54f6c436: Use `@backstage/plugin-search-common` package instead of `@backstage/search-common`.
- cea6f10b97: Renamed `@backstage/techdocs-common` to `@backstage/plugin-techdocs-node`.
- Updated dependencies
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
## 0.11.12-next.0
### Patch Changes
- e0a69ba49f: build(deps): bump `fs-extra` from 9.1.0 to 10.0.1
- 3e54f6c436: Use `@backstage/plugin-search-common` package instead of `@backstage/search-common`.
- cea6f10b97: Renamed `@backstage/techdocs-common` to `@backstage/plugin-techdocs-node`.
- Updated dependencies
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
## 0.11.11
### Patch Changes
- 955be6bc7d: adds passing projectID to the Storage client
- ff0a16fb1a: Modify techdocs builder to automatically append techdocs-core plugin to mkdocs.yaml file if it is missing. Adds an optional configuration item if this plugin needs to be omitted.
- Updated dependencies
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
## 0.11.10
### Patch Changes
- 209fd128e6: Updated usage of `github:` location types in docs to use `url:` instead.
- 13ef228d03: Clean up the API interface for TechDocs common library.
- Updated dependencies
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
## 0.11.9
### Patch Changes
- Fix for the previous release with missing type declarations.
- Updated dependencies
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
## 0.11.8
### Patch Changes
- c77c5c7eb6: Added `backstage.role` to `package.json`
- 216725b434: Updated to use new names for `parseLocationRef` and `stringifyLocationRef`
- 7aeb491394: Replace use of deprecated `ENTITY_DEFAULT_NAMESPACE` constant with `DEFAULT_NAMESPACE`.
- Updated dependencies
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
## 0.11.7
### Patch Changes
- Updated dependencies
- @backstage/[email protected]
## 0.11.7-next.0
### Patch Changes
- Updated dependencies
- @backstage/[email protected]
## 0.11.6
### Patch Changes
- Updated dependencies
- @backstage/[email protected]
## 0.11.6-next.0
### Patch Changes
- Updated dependencies
- @backstage/[email protected]
## 0.11.5
### Patch Changes
- ff93fbeeec: Fix interpolated string for "Failed to generate docs from ..."
- Updated dependencies
- @backstage/[email protected]
- @backstage/[email protected]
## 0.11.4
### Patch Changes
- 47277c0d8c: Updated the default version of the `@spotify/techdocs` container used when `techdocs.generator.runIn` is `docker` to `v0.3.6`, which includes an update to `mkdocs-monorepo-plugin` that allows glob-based wildcard includes.
- Updated dependencies
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
## 0.11.4-next.0
### Patch Changes
- 47277c0d8c: Updated the default version of the `@spotify/techdocs` container used when `techdocs.generator.runIn` is `docker` to `v0.3.6`, which includes an update to `mkdocs-monorepo-plugin` that allows glob-based wildcard includes.
- Updated dependencies
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
## 0.11.3
### Patch Changes
- 5333451def: Cleaned up API exports
- Updated dependencies
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
## 0.11.2
### Patch Changes
- c2c8768771: Bump `@azure/identity` from `^1.5.0` to `^2.0.1`.
- Updated dependencies
- @backstage/[email protected]
- @backstage/[email protected]
## 0.11.1
### Patch Changes
- Updated dependencies
- @backstage/[email protected]
## 0.11.0
### Minor Changes
- 1bada775a9: Added the ability for the TechDocs Backend to (optionally) leverage a cache
store to improve performance when reading files from a cloud storage provider.
### Patch Changes
- dcd1a0c3f4: Minor improvement to the API reports, by not unpacking arguments directly
- Updated dependencies
- @backstage/[email protected]
## 0.10.8
### Patch Changes
- bab752e2b3: Change default port of backend from 7000 to 7007.
This is due to the AirPlay Receiver process occupying port 7000 and preventing local Backstage instances on MacOS to start.
You can change the port back to 7000 or any other value by providing an `app-config.yaml` with the following values:
```
backend:
listen: 0.0.0.0:7123
baseUrl: http://localhost:7123
```
More information can be found here: https://backstage.io/docs/conf/writing
- Updated dependencies
- @backstage/[email protected]
- @backstage/[email protected]
## 0.10.7
### Patch Changes
- 0b60a051c9: Added OpenStack Swift case migration support.
- 9e64a7ac1e: Allow amazon web services s3 buckets to pass an server side encryption configuration so they can publish to encrypted buckets
- Updated dependencies
- @backstage/[email protected]
- @backstage/[email protected]
## 0.10.6
### Patch Changes
- a2d4389587: 1. Techdocs publisher constructors now use parameter objects when being
instantiated
2. Internal refactor of `LocalPublish` publisher to use `fromConfig` for
creation to be aligned with other publishers; this does not impact
`LocalPublish` usage.
```diff
- const publisher = new LocalPublish(config, logger, discovery);
+ const publisher = LocalPublish.fromConfig(config, logger, discovery);
```
- 6129c89a47: Default TechDocs container used at docs generation-time is now [v0.3.5](https://github.com/backstage/techdocs-container/releases/tag/v0.3.5).
- f3c7eec64b: Updated to properly join URL segments under any OS for both AWS S3 and GCP
- Updated dependencies
- @backstage/[email protected]
## 0.10.5
### Patch Changes
- d207f6ee9e: Support optional bucketRootPath configuration parameter in S3 and GCS publishers
- Updated dependencies
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
## 0.10.4
### Patch Changes
- 87f5b9db13: Use docs/README.md or README.md as fallback if docs/index.md is missing
- 36e67d2f24: Internal updates to apply more strict checks to throw errors.
- Updated dependencies
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
## 0.10.3
### Patch Changes
- 156421c59a: Sets the default techdocs docker image to the [latest released version - v0.3.3](https://github.com/backstage/techdocs-container/releases/tag/v0.3.3).
- Updated dependencies
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
## 0.10.2
### Patch Changes
- 1c75e8bf98: Add more context to techdocs log lines when files are not found along with
ensuring that the routers return 404 with a descriptive message.
- e92f0f728b: Locks the version of the default docker image used to generate TechDocs. As of
this changelog entry, it is v0.3.2!
- Updated dependencies
- @backstage/[email protected]
- @backstage/[email protected]
## 0.10.1
### Patch Changes
- 96fef17a18: Upgrade git-parse-url to v11.6.0
- Updated dependencies
- @backstage/[email protected]
- @backstage/[email protected]
## 0.10.0
### Minor Changes
- 8b0f6f860: Set the correct `edit_uri` or `repo_url` for documentation pages that are hosted on GitHub and GitLab.
The constructor of the `TechDocsGenerator` changed.
Prefer the use of `TechdocsGenerator.fromConfig(…)` instead:
```diff
- const techdocsGenerator = new TechdocsGenerator({
+ const techdocsGenerator = TechdocsGenerator.fromConfig(config, {
logger,
containerRunner,
- config,
});
```
### Patch Changes
- 30ed662a3: Adding in-context search to TechDocs Reader component. Using existing search-backend to query for indexed search results scoped into a specific entity's techdocs. Needs TechDocsCollator enabled on the backend to work.
Adding extra information to indexed tech docs documents for search.
- 3624616e7: "Local" (out-of-the-box) publisher explicitly follows lower-case entity triplet
logic.
- 67ba7e088: Only write the updated `mkdocs.yml` file if the content was updated.
This keeps local files unchanged if the `dir` annotation is used in combination with the `file` location.
- 8eab6be6a: Force using `posix` path for cloud storage
- Updated dependencies
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
## 0.9.0
### Minor Changes
- 58452cdb7: OpenStack Swift Client changed with Trendyol's OpenStack Swift SDK.
## Migration from old OpenStack Swift Configuration
Let's assume we have the old OpenStack Swift configuration here.
```yaml
techdocs:
publisher:
type: 'openStackSwift'
openStackSwift:
containerName: 'name-of-techdocs-storage-bucket'
credentials:
username: ${OPENSTACK_SWIFT_STORAGE_USERNAME}
password: ${OPENSTACK_SWIFT_STORAGE_PASSWORD}
authUrl: ${OPENSTACK_SWIFT_STORAGE_AUTH_URL}
keystoneAuthVersion: ${OPENSTACK_SWIFT_STORAGE_AUTH_VERSION}
domainId: ${OPENSTACK_SWIFT_STORAGE_DOMAIN_ID}
domainName: ${OPENSTACK_SWIFT_STORAGE_DOMAIN_NAME}
region: ${OPENSTACK_SWIFT_STORAGE_REGION}
```
##### Step 1: Change the credential keys
Since the new SDK uses _Application Credentials_ to authenticate OpenStack, we
need to change the keys `credentials.username` to `credentials.id`,
`credentials.password` to `credentials.secret` and use Application Credential ID
and secret here. For more detail about credentials look
[here](https://docs.openstack.org/api-ref/identity/v3/?expanded=password-authentication-with-unscoped-authorization-detail,authenticating-with-an-application-credential-detail#authenticating-with-an-application-credential).
##### Step 2: Remove the unused keys
Since the new SDK doesn't use the old way authentication, we don't need the keys
`openStackSwift.keystoneAuthVersion`, `openStackSwift.domainId`,
`openStackSwift.domainName` and `openStackSwift.region`. So you can remove them.
##### Step 3: Add Swift URL
The new SDK needs the OpenStack Swift connection URL for connecting the Swift.
So you need to add a new key called `openStackSwift.swiftUrl` and give the
OpenStack Swift url here. Example url should look like that:
`https://example.com:6780/swift/v1`
##### That's it!
Your new configuration should look like that!
```yaml
techdocs:
publisher:
type: 'openStackSwift'
openStackSwift:
containerName: 'name-of-techdocs-storage-bucket'
credentials:
id: ${OPENSTACK_SWIFT_STORAGE_APPLICATION_CREDENTIALS_ID}
secret: ${OPENSTACK_SWIFT_STORAGE_APPLICATION_CREDENTIALS_SECRET}
authUrl: ${OPENSTACK_SWIFT_STORAGE_AUTH_URL}
swiftUrl: ${OPENSTACK_SWIFT_STORAGE_SWIFT_URL}
```
- c772d9a84: TechDocs sites can now be accessed using paths containing entity triplets of
any case (e.g. `/docs/namespace/KIND/name` or `/docs/namespace/kind/name`).
If you do not use an external storage provider for serving TechDocs, this is a
transparent change and no action is required from you.
If you _do_ use an external storage provider for serving TechDocs (one of\* GCS,
AWS S3, or Azure Blob Storage), you must run a migration command against your
storage provider before updating.
[A migration guide is available here](https://backstage.io/docs/features/techdocs/how-to-guides#how-to-migrate-from-techdocs-alpha-to-beta).
- (\*) We're seeking help from the community to bring OpenStack Swift support
[to feature parity](https://github.com/backstage/backstage/issues/6763) with the above.
### Patch Changes
- Updated dependencies
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
## 0.8.1
### Patch Changes
- bc405be6e: Stale TechDocs content (files that had previously been published but which have
since been removed) is now removed from storage at publish-time. This is now
supported by the following publishers:
- Google GCS
- AWS S3
- Azure Blob Storage
You may need to apply a greater level of permissions (e.g. the ability to
delete objects in your storage provider) to any credentials/accounts used by
the TechDocs CLI or TechDocs backend in order for this change to take effect.
For more details, see [#6132][issue-ref].
[issue-ref]: https://github.com/backstage/backstage/issues/6132
- Updated dependencies
- @backstage/[email protected]
- @backstage/[email protected]
## 0.8.0
### Minor Changes
- 48ea3d25b: TechDocs has dropped all support for the long-ago deprecated git-based common
prepares as well as all corresponding values in `backstage.io/techdocs-ref`
annotations.
Entities whose `backstage.io/techdocs-ref` annotation values still begin with
`github:`, `gitlab:`, `bitbucket:`, or `azure/api:` will no longer be generated
by TechDocs. Be sure to update these values so that they align with their
expected format and your usage of TechDocs.
For details, see [this explainer on TechDocs ref annotation values][how].
[how]: https://backstage.io/docs/features/techdocs/how-to-guides#how-to-understand-techdocs-ref-annotation-values
### Patch Changes
- Updated dependencies
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
## 0.7.1
### Patch Changes
- 59a5fa319: Migrated files are now printed when `techdocs-cli migrate` is run with the
`--verbose` flag set.
- 54356336e: TechDocs generator stage now supports `mkdocs.yaml` file, in addition to `.yml`
depending on whichever is present at the time of generation. (Assumes the
latest `spotify/techdocs` container, running mkdocs `v1.2.2` or greater).
## 0.7.0
### Minor Changes
- d32d01e5b: Improve the annotation `backstage.io/techdocs-ref: dir:<relative-target>` that links to a path that is relative to the source of the annotated entity.
This annotation works with the basic and the recommended flow, however, it will be most useful with the basic approach.
This change remove the deprecation of the `dir` reference and provides first-class support for it.
In addition, this change removes the support of the deprecated `github`, `gitlab`, and `azure/api` locations from the `dir` reference preparer.
#### Example Usage
The annotation is convenient if the documentation is stored in the same location, i.e. the same git repository, as the `catalog-info.yaml`.
While it is still supported to add full URLs such as `backstage.io/techdocs-ref: url:https://...` for custom setups, documentation is mostly stored in the same repository as the entity definition.
By automatically resolving the target relative to the registration location of the entity, the configuration overhead for this default setup is minimized.
Since it leverages the `@backstage/integrations` package for the URL resolution, this is compatible with every supported source.
Consider the following examples:
1. "I have a repository with a single `catalog-info.yaml` and a TechDocs page in the root folder!"
```
https://github.com/backstage/example/tree/main/
|- catalog-info.yaml
| > apiVersion: backstage.io/v1alpha1
| > kind: Component
| > metadata:
| > name: example
| > annotations:
| > backstage.io/techdocs-ref: dir:. # -> same folder
| > spec: {}
|- docs/
|- mkdocs.yml
```
2. "I have a repository with a single `catalog-info.yaml` and my TechDocs page in located in a folder!"
```
https://bitbucket.org/my-owner/my-project/src/master/
|- catalog-info.yaml
| > apiVersion: backstage.io/v1alpha1
| > kind: Component
| > metadata:
| > name: example
| > annotations:
| > backstage.io/techdocs-ref: dir:./some-folder # -> subfolder
| > spec: {}
|- some-folder/
|- docs/
|- mkdocs.yml
```
3. "I have a mono repository that hosts multiple components!"
```
https://dev.azure.com/organization/project/_git/repository
|- my-1st-module/
|- catalog-info.yaml
| > apiVersion: backstage.io/v1alpha1
| > kind: Component
| > metadata:
| > name: my-1st-module
| > annotations:
| > backstage.io/techdocs-ref: dir:. # -> same folder
| > spec: {}
|- docs/
|- mkdocs.yml
|- my-2nd-module/
|- catalog-info.yaml
| > apiVersion: backstage.io/v1alpha1
| > kind: Component
| > metadata:
| > name: my-2nd-module
| > annotations:
| > backstage.io/techdocs-ref: dir:. # -> same folder
| > spec: {}
|- docs/
|- mkdocs.yml
|- catalog-info.yaml
| > apiVersion: backstage.io/v1alpha1
| > kind: Location
| > metadata:
| > name: example
| > spec:
| > targets:
| > - ./*/catalog-info.yaml
```
### Patch Changes
- 6e5aed1c9: Fix validation of mkdocs.yml docs_dir
- 250984333: Add link to https://backstage.io/docs/features/techdocs/configuration in the log warning message about updating techdocs.generate key.
- Updated dependencies
- @backstage/[email protected]
## 0.6.8
### Patch Changes
- d5eaab91d: Adds custom docker image support to the techdocs generator. This change adds a new `techdocs.generator` configuration key and deprecates the existing `techdocs.generators.techdocs` key.
```yaml
techdocs:
# recommended, going forward:
generator:
runIn: 'docker' # or 'local'
# New optional settings
dockerImage: my-org/techdocs # use a custom docker image
pullImage: false # disable automatic pulling of image (e.g. if custom docker login is required)
# legacy (deprecated):
generators:
techdocs: 'docker' # or 'local'
```
- c18e8eb91: Provide optional `logger: Logger` and `logStream: Writable` arguments to the `GeneratorBase#run(...)` command.
They receive all log messages that are emitted during the generator run.
- ae84b20cf: Revert the upgrade to `[email protected]` as that seemed to have broken all installs inexplicably.
- Updated dependencies
- @backstage/[email protected]
## 0.6.7
### Patch Changes
- 683308ecf: Fix openStack swift publisher encoding issue. Remove utf8 forced encoding on binary files
- 6841e0113: fix minor version of git-url-parse as 11.5.x introduced a bug for Bitbucket Server
- Updated dependencies
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
## 0.6.6
### Patch Changes
- ab5cc376f: Use new utilities from `@backstage/backend-common` for safely resolving child paths
- b47fc34bc: Update "service catalog" references to "software catalog"
- Updated dependencies
- @backstage/[email protected]
- @backstage/[email protected]
## 0.6.5
### Patch Changes
- c17c0fcf9: Adding additional checks on tech docs to prevent folder traversal via mkdocs.yml docs_dir value.
- Updated dependencies
- @backstage/[email protected]
## 0.6.4
### Patch Changes
- aad98c544: Fixes multiple XSS and sanitization bypass vulnerabilities in TechDocs.
- 090594755: Support parsing `mkdocs.yml` files that are using custom yaml tags like
`!!python/name:materialx.emoji.twemoji`.
- Updated dependencies [ebe802bc4]
- Updated dependencies [49d7ec169]
- @backstage/[email protected]
- @backstage/[email protected]
## 0.6.3
### Patch Changes
- 8cefadca0: Adding validation to mkdocs.yml parsing to prevent directory tree traversing
- Updated dependencies [0fd4ea443]
- Updated dependencies [add62a455]
- Updated dependencies [704875e26]
- @backstage/[email protected]
- @backstage/[email protected]
## 0.6.2
### Patch Changes
- 65e6c4541: Remove circular dependencies
- Updated dependencies [f7f7783a3]
- Updated dependencies [c7dad9218]
- Updated dependencies [65e6c4541]
- Updated dependencies [68fdbf014]
- Updated dependencies [5001de908]
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
## 0.6.1
### Patch Changes
- e04f1ccfb: Fixed a bug that prevented loading static assets from GCS, S3, Azure, and OpenStackSwift whose keys contain spaces or other special characters.
- Updated dependencies [22fd8ce2a]
- Updated dependencies [10c008a3a]
- Updated dependencies [f9fb4a205]
- Updated dependencies [16be1d093]
- @backstage/[email protected]
- @backstage/[email protected]
## 0.6.0
### Minor Changes
- e0bfd3d44: Migrate the package to use the `ContainerRunner` interface instead of `runDockerContainer(…)`.
It also no longer provides the `ContainerRunner` as an input to the `GeneratorBase#run(…)` function, but expects it as a constructor parameter instead.
If you use the `TechdocsGenerator` you need to update the usage:
```diff
+ const containerRunner = new DockerContainerRunner({ dockerClient });
- const generator = new TechdocsGenerator(logger, config);
+ const techdocsGenerator = new TechdocsGenerator({
+ logger,
+ containerRunner,
+ config,
+ });
await this.generator.run({
inputDir: preparedDir,
outputDir,
- dockerClient: this.dockerClient,
parsedLocationAnnotation,
etag: newEtag,
});
```
### Patch Changes
- e9e56b01a: Adding optional config to enable S3-like API for tech-docs using s3ForcePathStyle option.
This allows providers like LocalStack, Minio and Wasabi (+possibly others) to be used to host tech docs.
- Updated dependencies [e0bfd3d44]
- Updated dependencies [38ca05168]
- Updated dependencies [d8b81fd28]
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
## 0.5.1
### Patch Changes
- f4af06ebe: Gracefully handle HTTP request failures in download method of AzureBlobStorage publisher.
## 0.5.0
### Minor Changes
- bc9d62f4f: Move the sanity checks of the publisher configurations to a dedicated `PublisherBase#getReadiness()` method instead of throwing an error when doing `Publisher.fromConfig(...)`.
You should include the check when your backend to get early feedback about a potential misconfiguration:
```diff
// packages/backend/src/plugins/techdocs.ts
export default async function createPlugin({
logger,
config,
discovery,
reader,
}: PluginEnvironment): Promise<Router> {
// ...
const publisher = await Publisher.fromConfig(config, {
logger,
discovery,
})
+ // checks if the publisher is working and logs the result
+ await publisher.getReadiness();
// Docker client (conditionally) used by the generators, based on techdocs.generators config.
const dockerClient = new Docker();
// ...
}
```
If you want to crash your application on invalid configurations, you can throw an `Error` to preserve the old behavior.
Please be aware that this is not the recommended for the use in a Backstage backend but might be helpful in CLI tools such as the `techdocs-cli`.
```ts
const publisher = await Publisher.fromConfig(config, {
logger,
discovery,
});
const ready = await publisher.getReadiness();
if (!ready.isAvailable) {
throw new Error('Invalid TechDocs publisher configuration');
}
```
### Patch Changes
- Updated dependencies [bb5055aee]
- Updated dependencies [5d0740563]
- @backstage/[email protected]
## 0.4.5
### Patch Changes
- 8686eb38c: Use errors from `@backstage/errors`
- 424742dc1: Applies only if you use TechDocs local builder instead of building on CI/CD i.e. if `techdocs.builder` in your `app-config.yaml` is set to `'local'`
Improvements
1. Do not check for updates in the repository if a check has been made in the last 60 seconds. This is to prevent the annoying check for update on every page switch or load.
2. No need to maintain an in-memory etag storage, and use the one stored in `techdocs_metadata.json` file alongside generated docs.
New feature
1. You can now use a mix of basic and recommended setup i.e. `techdocs.builder` is `'local'` but using an external cloud storage instead of local storage. Previously, in this setup, the docs would never get updated.
- Updated dependencies [8686eb38c]
- Updated dependencies [0434853a5]
- Updated dependencies [8686eb38c]
- @backstage/[email protected]
- @backstage/[email protected]
## 0.4.4
### Patch Changes
- d7245b733: Remove runDockerContainer, and start using the utility function provided by @backstage/backend-common
- 0b42fff22: Make use of parseLocationReference/stringifyLocationReference
- 2ef5bc7ea: Implement proper AWS Credentials precedence with assume-role and explicit credentials
- aa095e469: OpenStack Swift publisher added for tech-docs.
- bc46435f5: - Improve deprecation warning messaging in logs.
- Replace temp folder path from git provider domain(`source`) to full git host name (`resource`). (See: https://github.com/IonicaBizau/git-url-parse#giturlparseurl)
- a501128db: Refactor log messaging to improve clarity
- ca4a904f6: Add an optional configuration option for setting the url endpoint for AWS S3 publisher: `techdocs.publisher.awsS3.endpoint`
- Updated dependencies [277644e09]
- Updated dependencies [52f613030]
- Updated dependencies [d7245b733]
- Updated dependencies [0b42fff22]
- Updated dependencies [905cbfc96]
- Updated dependencies [761698831]
- Updated dependencies [d4e77ec5f]
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
## 0.4.3
### Patch Changes
- f43192207: remove usage of res.send() for res.json() and res.end() to ensure content types are more consistently application/json on backend responses and error cases
- 61299519f: Remove read-store-upload loop when uploading S3 objects for TechDocs
- Updated dependencies [12d8f27a6]
- Updated dependencies [497859088]
- Updated dependencies [8adb48df4]
- @backstage/[email protected]
- @backstage/[email protected]
## 0.4.2
### Patch Changes
- 2499f6cde: Add support for assuming role in AWS integrations
- 1e4ddd71d: Fix AWS, GCS and Azure publisher to work on Windows.
- Updated dependencies [bad21a085]
- Updated dependencies [a1f5e6545]
- @backstage/[email protected]
- @backstage/[email protected]
## 0.4.1
### Patch Changes
- fb28da212: Switched to using `'x-access-token'` for authenticating Git over HTTPS towards GitHub.
- 26e143e60: After TechDocs generate step, insert build timestamp to techdocs_metadata.json
- c6655413d: Improved error reporting in AzureBlobStorage to surface errors when fetching metadata and uploading files fails.
- 44414239f: Pass user and group ID when invoking docker container. When TechDocs invokes Docker, docker could be run as a `root` user which results in generation of files by applications run by non-root user (e.g. TechDocs) will not have access to modify. This PR passes in current user and group ID to docker so that the file permissions of the generated files and folders are correct.
- b0a41c707: Add etag of the prepared file tree to techdocs_metadata.json in the storage
- Updated dependencies [16fb1d03a]
- Updated dependencies [491f3a0ec]
- Updated dependencies [491f3a0ec]
- Updated dependencies [434b4e81a]
- Updated dependencies [fb28da212]
- @backstage/[email protected]
- @backstage/[email protected]
## 0.4.0
### Minor Changes
- 08142b256: URL Preparer will now use proper etag based caching introduced in https://github.com/backstage/backstage/pull/4120. Previously, builds used to be cached for 30 minutes.
### Patch Changes
- 77ad0003a: Revert AWS SDK version to v2
- 08142b256: TechDocs will throw warning in backend logs when legacy git preparer or dir preparer is used to preparer docs. Migrate to URL Preparer by updating `backstage.io/techdocs-ref` annotation to be prefixed with `url:`.
Detailed docs are here https://backstage.io/docs/features/techdocs/how-to-guides#how-to-use-url-reader-in-techdocs-prepare-step
See benefits and reason for doing so https://github.com/backstage/backstage/issues/4409
- Updated dependencies [ffffea8e6]
- Updated dependencies [82b2c11b6]
- Updated dependencies [965e200c6]
- Updated dependencies [ffffea8e6]
- Updated dependencies [5a5163519]
- @backstage/[email protected]
- @backstage/[email protected]
## 0.3.7
### Patch Changes
- c777df180: 1. Added option to use Azure Blob Storage as a choice to store the static generated files for TechDocs.
- e44925723: `techdocs.requestUrl` and `techdocs.storageUrl` are now optional configs and the discovery API will be used to get the URL where techdocs plugin is hosted.
- f0320190d: dir preparer will use URL Reader in its implementation.
- Updated dependencies [c4abcdb60]
- Updated dependencies [2430ee7c2]
- Updated dependencies [6e612ce25]
- Updated dependencies [025e122c3]
- Updated dependencies [064c513e1]
- Updated dependencies [7881f2117]
- Updated dependencies [3149bfe63]
- Updated dependencies [2e62aea6f]
- Updated dependencies [11cb5ef94]
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
## 0.3.6
### Patch Changes
- 9dd057662: Upgrade [git-url-parse](https://www.npmjs.com/package/git-url-parse) to [v11.4.4](https://github.com/IonicaBizau/git-url-parse/pull/125) which fixes parsing an Azure DevOps branch ref.
- db2328c88: Add rate limiter for concurrent execution of file uploads in AWS and Google publishers
- Updated dependencies [26a3a6cf0]
- Updated dependencies [664dd08c9]
- Updated dependencies [6800da78d]
- Updated dependencies [9dd057662]
- @backstage/[email protected]
- @backstage/[email protected]
## 0.3.5
### Patch Changes
- 53c9c51f2: TechDocs backend now streams files through from Google Cloud Storage to the browser, improving memory usage.
- a5e27d5c1: Create type for TechDocsMetadata (#3716)
This change introduces a new type (TechDocsMetadata) in packages/techdocs-common. This type is then introduced in the endpoint response in techdocs-backend and in the api interface in techdocs (frontend).
- Updated dependencies [def2307f3]
- Updated dependencies [0b135e7e0]
- Updated dependencies [294a70cab]
- Updated dependencies [fa8ba330a]
- Updated dependencies [0ea032763]
- Updated dependencies [5345a1f98]
- Updated dependencies [ed6baab66]
- Updated dependencies [09a370426]
- Updated dependencies [a93f42213]
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
## 0.3.4
### Patch Changes
- a594a7257: @backstage/techdocs-common can now be imported in an environment without @backstage/plugin-techdocs-backend being installed.
## 0.3.3
### Patch Changes
- 68ad5af51: Improve techdocs-common Generator API for it to be used by techdocs-cli. TechDocs generator.run function now takes
an input AND an output directory. Most probably you use techdocs-common via plugin-techdocs-backend, and so there
is no breaking change for you.
But if you use techdocs-common separately, you need to create an output directory and pass into the generator.
- 371f67ecd: fix to-string breakage of binary files
- f1e74777a: Fix bug where binary files (`png`, etc.) could not load when using AWS or GCS publisher.
- dbe4450c3: Google Cloud authentication in TechDocs has been improved.
1. `techdocs.publisher.googleGcs.credentials` is now optional. If it is missing, `GOOGLE_APPLICATION_CREDENTIALS`
environment variable (and some other methods) will be used to authenticate.
Read more here https://cloud.google.com/docs/authentication/production
2. `techdocs.publisher.googleGcs.projectId` is no longer used. You can remove it from your `app-config.yaml`.
- 5826d0973: AWS SDK version bump for TechDocs.
- b3b9445df: AWS S3 authentication in TechDocs has been improved.
1. `techdocs.publisher.awsS3.bucketName` is now the only required config. `techdocs.publisher.awsS3.credentials` and `techdocs.publisher.awsS3.region` are optional.
2. If `techdocs.publisher.awsS3.credentials` and `techdocs.publisher.awsS3.region` are missing, the AWS environment variables `AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY` and `AWS_REGION` will be used. There are more better ways of setting up AWS authentication. Read the guide at https://backstage.io/docs/features/techdocs/using-cloud-storage
- Updated dependencies [466354aaa]
- Updated dependencies [f3b064e1c]
- Updated dependencies [abbee6fff]
- Updated dependencies [147fadcb9]
- @backstage/[email protected]
- @backstage/[email protected]
- @backstage/[email protected]
## 0.3.2
### Patch Changes
- 7ec525481: 1. Added option to use AWS S3 as a choice to store the static generated files for TechDocs.
- f8ba88ded: Fix for `integration.github.apiBaseUrl` configuration not properly overriding apiBaseUrl used by techdocs
- 00042e73c: Moving the Git actions to isomorphic-git instead of the node binding version of nodegit
- Updated dependencies [5ecd50f8a]
- Updated dependencies [00042e73c]
- Updated dependencies [0829ff126]
- Updated dependencies [036a84373]
- @backstage/[email protected]
- @backstage/[email protected]
## 0.3.1
### Patch Changes
- 8804e8981: Using @backstage/integration package for GitHub/GitLab/Azure tokens and request options.
Most probably you do not have to make any changes in the app because of this change.
However, if you are using the `DirectoryPreparer` or `CommonGitPreparer` exported by
`@backstage/techdocs-common` package, you now need to add pass in a `config` (from `@backstage/config`)
instance as argument.
```
<!-- Before -->
const directoryPreparer = new DirectoryPreparer(logger);
const commonGitPreparer = new CommonGitPreparer(logger);
<!-- Now -->
const directoryPreparer = new DirectoryPreparer(config, logger);
const commonGitPreparer = new CommonGitPreparer(config, logger);
```
## 0.3.0
### Minor Changes
- a8573e53b: techdocs-backend: Simplified file, removing individual preparers and generators.
techdocs-backend: UrlReader is now available to use in preparers.
In your Backstage app, `packages/backend/plugins/techdocs.ts` file has now been simplified,
to remove registering individual preparers and generators.
Please update the file when upgrading the version of `@backstage/plugin-techdocs-backend` package.
```typescript
const preparers = await Preparers.fromConfig(config, {
logger,
reader,
});
const generators = await Generators.fromConfig(config, {
logger,
});
const publisher = await Publisher.fromConfig(config, {
logger,
discovery,
});
```
You should be able to remove unnecessary imports, and just do
```typescript
import {
createRouter,
Preparers,
Generators,
Publisher,
} from '@backstage/plugin-techdocs-backend';
```
## 0.2.0
### Minor Changes
- dae4f3983: _Breaking changes_
1. Added option to use Google Cloud Storage as a choice to store the static generated files for TechDocs.
It can be configured using `techdocs.publisher.type` option in `app-config.yaml`.
Step-by-step guide to configure GCS is available here https://backstage.io/docs/features/techdocs/using-cloud-storage
Set `techdocs.publisher.type` to `'local'` if you want to continue using local filesystem to store TechDocs files.
2. `techdocs.builder` is now required and can be set to `'local'` or `'external'`. (Set it to `'local'` for now, since CI/CD build
workflow for TechDocs will be available soon (in few weeks)).
If builder is set to 'local' and you open a TechDocs page, `techdocs-backend` will try to generate the docs, publish to storage and
show the generated docs afterwords.
If builder is set to `'external'`, `techdocs-backend` will only fetch the docs and will NOT try to generate and publish. In this case of `'external'`,
we assume that docs are being built in the CI/CD pipeline of the repository.
TechDocs will not assume a default value for `techdocs.builder`. It is better to explicitly define it in the `app-config.yaml`.
3. When configuring TechDocs in your backend, there is a difference in how a new publisher is created.
```
--- const publisher = new LocalPublish(logger, discovery);
+++ const publisher = Publisher.fromConfig(config, logger, discovery);
```
Based on the config `techdocs.publisher.type`, the publisher could be either Local publisher or Google Cloud Storage publisher.
4. `techdocs.storageUrl` is now a required config. Should be `http://localhost:7007/api/techdocs/static/docs` in most setups.
5. Parts of `@backstage/plugin-techdocs-backend` have been moved to a new package `@backstage/techdocs-common` to generate docs. Also to publish docs
to-and-fro between TechDocs and a storage (either local or external). However, a Backstage app does NOT need to import the `techdocs-common` package -
app should only import `@backstage/plugin-techdocs` and `@backstage/plugin-techdocs-backend`.
_Patch changes_
1. See all of TechDocs config options and its documentation https://backstage.io/docs/features/techdocs/configuration
2. Logic about serving static files and metadata retrieval have been abstracted away from the router in `techdocs-backend` to the instance of publisher.
3. Removed Material UI Spinner from TechDocs header. Spinners cause unnecessary UX distraction.
Case 1 (when docs are built and are to be served): Spinners appear for a split second before the name of site shows up. This unnecessarily distracts eyes because spinners increase the size of the Header. A dot (.) would do fine. Definitely more can be done.
Case 2 (when docs are being generated): There is already a linear progress bar (which is recommended in Storybook).
### Patch Changes
- Updated dependencies [c911061b7]
- Updated dependencies [1d1c2860f]
- Updated dependencies [0e6298f7e]
- Updated dependencies [4eafdec4a]
- Updated dependencies [ac3560b42]
- @backstage/[email protected]
- @backstage/[email protected]
| 34.81891 | 387 | 0.734363 | eng_Latn | 0.88727 |
8a9abbbe2ef71440be754a50030d095553ca0ce8 | 2,243 | md | Markdown | sdk-api-src/content/wsddisco/nf-wsddisco-wsdcreatediscoveryprovider.md | amorilio/sdk-api | 54ef418912715bd7df39c2561fbc3d1dcef37d7e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | sdk-api-src/content/wsddisco/nf-wsddisco-wsdcreatediscoveryprovider.md | amorilio/sdk-api | 54ef418912715bd7df39c2561fbc3d1dcef37d7e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | sdk-api-src/content/wsddisco/nf-wsddisco-wsdcreatediscoveryprovider.md | amorilio/sdk-api | 54ef418912715bd7df39c2561fbc3d1dcef37d7e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
UID: NF:wsddisco.WSDCreateDiscoveryProvider
title: WSDCreateDiscoveryProvider function (wsddisco.h)
description: Creates an IWSDiscoveryProvider object.
helpviewer_keywords: ["WSDCreateDiscoveryProvider","WSDCreateDiscoveryProvider function","ncd.wsdcreatediscoveryprovider_func","wsddisco/WSDCreateDiscoveryProvider"]
old-location: ncd\wsdcreatediscoveryprovider_func.htm
tech.root: ncd
ms.assetid: 44275cbe-ea02-41fd-b88d-81d4df966067
ms.date: 12/05/2018
ms.keywords: WSDCreateDiscoveryProvider, WSDCreateDiscoveryProvider function, ncd.wsdcreatediscoveryprovider_func, wsddisco/WSDCreateDiscoveryProvider
req.header: wsddisco.h
req.include-header: Wsdapi.h
req.target-type: Windows
req.target-min-winverclnt: Windows Vista [desktop apps only]
req.target-min-winversvr: Windows Server 2008 [desktop apps only]
req.kmdf-ver:
req.umdf-ver:
req.ddi-compliance:
req.unicode-ansi:
req.idl:
req.max-support:
req.namespace:
req.assembly:
req.type-library:
req.lib: Wsdapi.lib
req.dll: Wsdapi.dll
req.irql:
targetos: Windows
req.typenames:
req.redist:
ms.custom: 19H1
f1_keywords:
- WSDCreateDiscoveryProvider
- wsddisco/WSDCreateDiscoveryProvider
dev_langs:
- c++
topic_type:
- APIRef
- kbSyntax
api_type:
- DllExport
api_location:
- Wsdapi.dll
api_name:
- WSDCreateDiscoveryProvider
---
# WSDCreateDiscoveryProvider function
## -description
Creates an <a href="/windows/desktop/api/wsddisco/nn-wsddisco-iwsdiscoveryprovider">IWSDiscoveryProvider</a> object.
## -parameters
### -param pContext [in]
An <a href="/windows/desktop/api/wsdxml/nn-wsdxml-iwsdxmlcontext">IWSDXMLContext</a> interface that defines custom message types or namespaces.
If <b>NULL</b>, a default context representing the built-in message types and namespaces is used.
### -param ppProvider [out]
Returns a reference to the initialized <a href="/windows/desktop/api/wsddisco/nn-wsddisco-iwsdiscoveryprovider">IWSDiscoveryProvider</a> object. Cannot be <b>NULL</b>.
## -returns
Possible return values include, but are not limited to, the following:
<table>
<tr>
<th>Return code</th>
<th>Description</th>
</tr>
<tr>
<td width="40%">
<dl>
<dt><b>S_OK</b></dt>
</dl>
</td>
<td width="60%">
Method completed successfully.
</td>
</tr>
</table> | 25.781609 | 167 | 0.779313 | yue_Hant | 0.39545 |
8a9ae951661fb9af2ba0f23a2d3ed3f8f2013bc0 | 387 | md | Markdown | docs/SourceCode/BinaryDataDecoders.Archives.Tests/obj/Debug/netcoreapp3.1/.NETCoreApp,Version=v3.1.AssemblyAttributes.md | mwwhited/BinaryDataDecoders | 810eb131cff0f40e096e4438ffa4c7ed39bcae97 | [
"MIT"
] | 5 | 2020-01-19T13:41:58.000Z | 2021-01-03T03:56:01.000Z | docs/SourceCode/BinaryDataDecoders.Archives.Tests/obj/Debug/netcoreapp3.1/.NETCoreApp,Version=v3.1.AssemblyAttributes.md | mwwhited/BinaryDataDecoders | 810eb131cff0f40e096e4438ffa4c7ed39bcae97 | [
"MIT"
] | 23 | 2020-11-25T06:06:58.000Z | 2021-08-08T15:02:48.000Z | docs/SourceCode/BinaryDataDecoders.Archives.Tests/obj/Debug/netcoreapp3.1/.NETCoreApp,Version=v3.1.AssemblyAttributes.md | mwwhited/BinaryDataDecoders | 810eb131cff0f40e096e4438ffa4c7ed39bcae97 | [
"MIT"
] | 1 | 2020-09-24T06:35:40.000Z | 2020-09-24T06:35:40.000Z | # .NETCoreApp,Version=v3.1.AssemblyAttributes.cs
## Summary
* Language: C#
* Path: src\BinaryDataDecoders.Archives.Tests\obj\Debug\netcoreapp3.1\.NETCoreApp,Version=v3.1.AssemblyAttributes.cs
### Attributes
- global
- ::
- System
- .
- Runtime
- .
- Versioning
- .
- TargetFrameworkAttribute
- (
- ".NETCoreApp,Version=v3.1"
- ,
- FrameworkDisplayName
- =
- ""
- )
| 14.333333 | 116 | 0.664083 | yue_Hant | 0.842781 |
8a9b7275d3b8092aa3caa9de0f5430d6d93019d2 | 481 | md | Markdown | microsoft.ui.xaml.controls/swipeitem_text.md | nschonni/winui-api | e2e9ffdb88b86d0e349066fffd5d82df5834604d | [
"CC-BY-4.0",
"MIT"
] | null | null | null | microsoft.ui.xaml.controls/swipeitem_text.md | nschonni/winui-api | e2e9ffdb88b86d0e349066fffd5d82df5834604d | [
"CC-BY-4.0",
"MIT"
] | null | null | null | microsoft.ui.xaml.controls/swipeitem_text.md | nschonni/winui-api | e2e9ffdb88b86d0e349066fffd5d82df5834604d | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
-api-id: P:Microsoft.UI.Xaml.Controls.SwipeItem.Text
-api-type: winrt property
---
<!-- Property syntax.
public string Text { get; set; }
-->
# Microsoft.UI.Xaml.Controls.SwipeItem.Text
## -description
Gets or sets the text description displayed on the item.
## -property-value
The text description displayed on the item. The default is an empty string.
## -remarks
## -see-also
## -examples
## -xaml-syntax
```xaml
<SwipeItem Text="string"/>
```
| 12.333333 | 75 | 0.665281 | eng_Latn | 0.775001 |
8a9bbe9ae77b3766294dccb68f66e785daea9ac6 | 8,833 | md | Markdown | Devaria/Infraestrutura/Devaria - Noções de Sistemas Operacionais e Servidores.md | vdonoladev/aprendendo-programacao | 83abbcd6701b2105903b28fd549738863418cfb8 | [
"MIT"
] | null | null | null | Devaria/Infraestrutura/Devaria - Noções de Sistemas Operacionais e Servidores.md | vdonoladev/aprendendo-programacao | 83abbcd6701b2105903b28fd549738863418cfb8 | [
"MIT"
] | null | null | null | Devaria/Infraestrutura/Devaria - Noções de Sistemas Operacionais e Servidores.md | vdonoladev/aprendendo-programacao | 83abbcd6701b2105903b28fd549738863418cfb8 | [
"MIT"
] | null | null | null | # Parte 1
- O que é um servidor
- Os tipos de servidores
- Servidor de aplicação
---
## Servidor
- Fornecimento de serviços
Responsável por prover serviços diversos para outros computadores.
- Computadores mais robustos conectadas em redes
Máquinas conectadas na LAN, MAN e WAN prontos para receber chamadas de serviços específicos.
---
### Tipos de Servidor
- Servidor de Aplicação
- Servidor de Banco de Dados
- Servidor de Arquivos
- Servidor de Impressão
- Servidor de E-mail
- Servidor de Proxy
- Servidor de Mídia
---
### Datacenters
- Conjunto de servidores
Ambiente com vários servidores e com uma infraestrutura que gera segurança e disponibilidade.
- Em empresas corporativas
Chamamos datacenters de empresas corporativas de On-Premisse.
- Empresas que vendem serviços
Datacenters especialistas em vender serviços de tecnologia através de datacenters.
---
### Datacenters provedores
- Infraestrutura elétrica
A parte de eletricidade é um ponto chave em um datacenter, pois além da energia da concessionária, elas possuem geradores
- Infraestrutura de redes
Tanto a rede local do Datacenter quanto a conexão de internet são cruciais.
- Infraestrutura de servidores
Datacenters contam com uma estrutura de servidores de altíssimo nível de performance e tecnologia utilizando o conceito de Virtualização.
---
### Virtualização de servidores
É uma técnica utilizada para transformar um servidor físico em servidores virtuais.
---
### Servidor de Aplicação
- Responsável pelo processamento
Com servidores de aplicações os computadores podem acessar sistemas simultaneamente através da rede.
---
### Como funciona o servidor de aplicação?
- Cliente / Servidor
O acesso ao sistema com servidor utiliza o conceito de cliente / servidor, e na maioria das vezes utiliza o protocolo HTTP.
- FrontEnd vs BackEnd
O Frontend é utilizado pelo cliente e o Backend é de responsabilidade do servidor.
---
### FrontEnd vs BackEnd
- O Frontend é executado no cliente.
- A execução do código em frontend é processado pelo cliente (computador, notebook, celular).
- Todo o visual do sistema é de responsabilidade do FrontEnd.
- O Backend é executado e instalado no servidor.
- Todos os processamentos dos dados são realizados no Backend do lado do servidor.
- É o servidor que salva e consulta dados no banco de dados.
- Frontend chama o Backend para pegar e enviar as informações.
---
### Alguns exemplos de servidores de Aplicações
- Games
- ERPs
- Banklines
- Redes Sociais
---
# Parte 2
### Servidor de E-mails
- Responsável por centralizar E-mails
Todos os e-mails provenientes de um domínio são direcionados para um servidor que é responsável por controlar os e-mails.
- Receber e Enviar e-mails
Os serviços do servidor de e-mail possibilitam o envio (SMTP) e o recebimento de e-mails (POP ou IMAP).
- Anti-Spam são essenciais
Responsável por filtrar os e-mails e evitar que os usuários estejam totalmente expostos a códigos maliciosos e conteúdos indesejados.
---
### Servidor de Arquivos
- Responsável por armazenar arquivos
Centralizador de arquivos em um servidor, que pode ser em formato de Storage.
- Segurança e alta disponibilidade
Os servidores de arquivos demandam que estejam sempre disponíveis e com segurança para não ter o risco de pessoas sem privilégios acessarem.
---
### Servidor de Arquivos
- **RAID**
Redundant Array of Inexpensive Disks
**RAID 0** - Junção de vários HDs em um
**RAID 1** - Redundância completa
**RAID 5** - Junção de vários HDs com redundância pariada
**RAID 0 + 1** - Junção de vários HDs com redundância e junção
---
### Servidor de Banco de Dados
- Responsável por armazenar dados
Todos os dados que são salvos pelos sistemas são armazenadas pelo servidor de banco de dados.
- Existem dois tipos de banco de dados
- Banco de dados relacionais
- Banco de dados não relacionais
- Exemplos de Bancos de Dados
- Microsoft SQL Server
- MySQL
- MongoDB
- Oracle
- PostgreSQL
- ...
---
### Servidor de Impressão
- Controla todas as impressões de uma rede
Todos os sistemas que disparam impressões passam por um servidor para gerenciamento.
- Empresas outsourcing
Em uma empresa que aluga impressoras, o servidor de impressão é extremamente essencial, pois a empresa cobra pela quantidade de impressões e o servidor controla esses dados.
---
### Servidor de Proxy
- Funciona como intermediador
O acesso da internet através de computadores podem passar por servidores Proxy para aumentar a segurança e performance de uma empresa no acesso da internet.
- Serviços que o Proxy oferece
- Filtros de conteúdo
- Caching
- Open Proxy
São servidores públicos que oferecem os serviços de proxy e vários robôs utilizam para mascarar a identidade do requisitante.
---
### Servidor de Mídia
- Centraliza e controla arquivos de mídia
Com um servidor de Mídia todos os dispositivos acessam pela conectividade DLNA (Digital Living Network Alliance).
- Compartilhamento de mídias entre dispositivos
Todos os usuários compartilham um armazenamento centralizado dos arquivos de mídia sem sobrecarregar seus discos.
- Storage NAS da Qnap
---
### Formatos de servidores
- Torres
- Racks
- Switch KVM - Controla vários servidores
---
# Parte 3
## Sistemas Operacionais
Sistema responsável pela comunicação com as peças do computador. É o SO que executa comandos para os periféricos.
- Intermediador entre as Aplicações e os Hardwares
- Gerencia todos os recursos de hardware
---
### Importância do Sistema Operacional
- Menos complexidade para programar
- Maior portabilidade entre os dispositivos
---
### Tipos de interfaces
- Interface de Janelas
- Linha de comando
- É uma linguagem de comunicação com o sistema operacional
---
# Parte 4
### Formas de processamento do Sistema Operacional
- Monoprogramação
Os recursos de hardware são utilizados a um único programa
- Multiprogramação
Capaz de rodar vários programas ao mesmo tempo
---
### Kernel
- Coração do computador, sendo a parte mais importante de um sistema operacional
- É o Kernel que é responsável pela comunicação e os comandos para as peças do computador
- Ele decide as prioridades de execução dos programas, bem como decide qual tarefa o processador vai executar.
- Responsável também pelo gerenciamento de todas as peças do computador e quando serão utilizadas
---
### Estruturas de Sistemas Operacionais
- Monolítica - Único módulo para executar um conjunto de programas
- Microkernel - São estruturas enxutas para comunicação com os hardwares
- Camadas - O sistema operacional é dividido em módulos de forma hierárquica
---
### UNIX
- Primeiro sistema operacional, foi criado em 1960, e é considerado o pai dos SO.
- O Unix foi o primeiro sistema a trabalhar com multitarefas e isso lhe tornou bem popular.
- O Mac e o Linux utilizam uma arquitetura baseada em Unix.
- Um sistema Uni é orientado a arquivos, quase tudo nele é arquivo.
---
### LINUX
- O Linux é um sistema de código aberto, por se tratar de uma marca sem fins comerciais
- Por ser aberto, não significa que ele é fácil de ser customizado e cada um usa o seu
- Muito utilizado em servidores de diversos tipos, mas possui versões desktops bem amigáveis
- Como não é um sistema comum utilizado para as pessoas, o Linux não sofre com uma quantidade de vírus como o Windows
---
### WINDOWS
- A Microsoft é a dona do sistema operacional Windows que foi introduzido pelo Bill Gates em 1985
- O Windows possui versões Desktops e Servers e é o sistema operacional mais utilizado no mundo
- Linguagem base é o C e tem algumas partes em C++ e Assembly
- Versão atual para Desktop é a 10 e para servidores é a 2019
---
### MAC OS
- Seu lançamento foi em 2001 na base mais atual e em 1984 que foi constituído como MacOS Classic
- A sua arquitetura é baseada em Unix e atualmente com um núcleo chamado Darwin
- O MacOS está na versão MacOS Big Sur e é distribuído apenas para computadores pessoais da Apple
---
### IOS
- Sistema operacional para os celulares da Apple e foi criado em 2007 e foi usado no primeiro celular da Apple
- O Kernel utilizado também é o Darwin utilizando a base do Unix
- Siri é a assistente pessoal do iOS que, por comandos de voz, realiza os comandos para o hardware
- Utiliza apps com linguagem de programação nativa Swift / Object-C, bem como pode ser programado em linguagens híbridas
---
### ANDROID
- Esse sistema operacional é utilizado em celulares de diversos fabricantes e é mantido pela Google
- O Kernel utilizado pelo Android é o Linux que também tem como base o Unix
- Também é utilizado para relógios, carros, TVs, consoles de games entre outros dispositivos
- Utiliza apps com linguagem de programação nativa Java / Kotlin, bem como pode ser programado em linguagens híbridas | 26.446108 | 173 | 0.769388 | por_Latn | 0.999889 |
8a9d4db0f4453cf7ff1e7b3f22d3a270b8ac5377 | 2,996 | md | Markdown | sdk-api-src/content/rometadataapi/nf-rometadataapi-imetadataimport2-enummethodspecs.md | amorilio/sdk-api | 54ef418912715bd7df39c2561fbc3d1dcef37d7e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | sdk-api-src/content/rometadataapi/nf-rometadataapi-imetadataimport2-enummethodspecs.md | amorilio/sdk-api | 54ef418912715bd7df39c2561fbc3d1dcef37d7e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | sdk-api-src/content/rometadataapi/nf-rometadataapi-imetadataimport2-enummethodspecs.md | amorilio/sdk-api | 54ef418912715bd7df39c2561fbc3d1dcef37d7e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
UID: NF:rometadataapi.IMetaDataImport2.EnumMethodSpecs
title: IMetaDataImport2::EnumMethodSpecs (rometadataapi.h)
description: Gets an enumerator for an array of MethodSpec tokens associated with the specified MethodDef or MemberRef token.
helpviewer_keywords: ["EnumMethodSpecs","EnumMethodSpecs method [Windows Runtime]","EnumMethodSpecs method [Windows Runtime]","IMetaDataImport2 interface","IMetaDataImport2 interface [Windows Runtime]","EnumMethodSpecs method","IMetaDataImport2.EnumMethodSpecs","IMetaDataImport2::EnumMethodSpecs","rometadataapi/IMetaDataImport2::EnumMethodSpecs","winrt.imetadataimport2_enummethodspecs"]
old-location: winrt\imetadataimport2_enummethodspecs.htm
tech.root: WinRT
ms.assetid: b4327a57-8a19-44f9-90b6-df2b089f63e4
ms.date: 12/05/2018
ms.keywords: EnumMethodSpecs, EnumMethodSpecs method [Windows Runtime], EnumMethodSpecs method [Windows Runtime],IMetaDataImport2 interface, IMetaDataImport2 interface [Windows Runtime],EnumMethodSpecs method, IMetaDataImport2.EnumMethodSpecs, IMetaDataImport2::EnumMethodSpecs, rometadataapi/IMetaDataImport2::EnumMethodSpecs, winrt.imetadataimport2_enummethodspecs
req.header: rometadataapi.h
req.include-header:
req.target-type: Windows
req.target-min-winverclnt:
req.target-min-winversvr:
req.kmdf-ver:
req.umdf-ver:
req.ddi-compliance:
req.unicode-ansi:
req.idl: Rometadataapi.idl
req.max-support:
req.namespace:
req.assembly:
req.type-library:
req.lib:
req.dll:
req.irql:
targetos: Windows
req.typenames:
req.redist:
ms.custom: 19H1
f1_keywords:
- IMetaDataImport2::EnumMethodSpecs
- rometadataapi/IMetaDataImport2::EnumMethodSpecs
dev_langs:
- c++
topic_type:
- APIRef
- kbSyntax
api_type:
- COM
api_location:
- rometadataapi.h
api_name:
- IMetaDataImport2.EnumMethodSpecs
---
# IMetaDataImport2::EnumMethodSpecs
## -description
Gets an enumerator for an array of MethodSpec tokens associated with the specified MethodDef or MemberRef token.
## -parameters
### -param phEnum [in, out]
pointer to the enumerator for <i>rMethodSpecs</i>.
### -param tk [in]
The <b>MemberRef</b> or <b>MethodDef</b> token that represents the method whose <b>MethodSpec</b> tokens are to be enumerated. If the value of <i>tk</i> is 0 (zero), all <b>MethodSpec</b> tokens in the scope will be enumerated.
### -param rMethodSpecs [out]
The array of <b>MethodSpec</b> tokens to enumerate.
### -param cMax [in]
The requested maximum number of tokens to place in <i>rMethodSpecs</i>.
### -param pcMethodSpecs [out]
The returned number of tokens placed in <i>rMethodSpecs</i>.
## -returns
<table>
<tr>
<th>HRESULT</th>
<th>Description</th>
</tr>
<tr>
<td><b>S_OK</b></td>
<td><b>EnumMethodSpecs</b> returned successfully.</td>
</tr>
<tr>
<td><b>S_FALSE</b></td>
<td><i>phEnum</i> has no member elements. In this case, <i>pcMethodSpecs</i> is set to 0 (zero).
</td>
</tr>
</table>
## -see-also
<a href="/windows/desktop/api/rometadataapi/nn-rometadataapi-imetadataimport2">IMetaDataImport2</a> | 30.262626 | 389 | 0.772029 | yue_Hant | 0.537137 |
8a9d51f803583e711450245f763c06e17e657235 | 1,005 | md | Markdown | testing-unit-ts/README.md | spara/examples | abc9ce277024b162b137cd073c31436356beaa8a | [
"Apache-2.0"
] | 2 | 2020-06-17T08:51:38.000Z | 2020-06-20T07:48:04.000Z | testing-unit-ts/README.md | spara/examples | abc9ce277024b162b137cd073c31436356beaa8a | [
"Apache-2.0"
] | null | null | null | testing-unit-ts/README.md | spara/examples | abc9ce277024b162b137cd073c31436356beaa8a | [
"Apache-2.0"
] | 3 | 2022-03-13T02:59:55.000Z | 2022-03-13T03:05:50.000Z | # Unit Testing Pulumi programs in TypeScript
An example of writing mock-based unit tests with both infrastructure definition and tests written in TypeScript. The example uses the [Mocha](https://mochajs.org/) test framework to define and run the tests.
## Prerequisites
1. [Ensure you have the latest Node.js and NPM](https://nodejs.org/en/download/).
2. [Install the Mocha test framework](https://mochajs.org/#installation).
## Running the tests
1. Restore NPM dependencies:
```
$ npm install
```
2. Run the tests:
```
$ mocha -r ts-node/register ec2tests.ts
Infrastructure
#server
✓ must have a name tag
✓ must not use userData (use an AMI instead)
#group
✓ must not open port 22 (SSH) to the Internet
3 passing (420ms)
```
## Further steps
Learn more about testing Pulumi programs:
- [Testing Guide](https://www.pulumi.com/docs/guides/testing/)
- [Unit Testing Guide](https://www.pulumi.com/docs/guides/testing/unit/)
| 25.769231 | 207 | 0.685572 | eng_Latn | 0.883278 |
8a9e3a15e6dab9f1d81e9f5024cd2cabd4d92e42 | 880 | md | Markdown | public/about/_index.md | kaishuun/portfolio | 2ff5094b751f5ecea3ddebbc77c5cb37ff74264d | [
"CC-BY-4.0"
] | null | null | null | public/about/_index.md | kaishuun/portfolio | 2ff5094b751f5ecea3ddebbc77c5cb37ff74264d | [
"CC-BY-4.0"
] | null | null | null | public/about/_index.md | kaishuun/portfolio | 2ff5094b751f5ecea3ddebbc77c5cb37ff74264d | [
"CC-BY-4.0"
] | null | null | null | ---
title: "About + Resume"
date: 2020-07-11
description: "Short Bio + Resume"
author : "Kevin"
authorImage : "images/about/profilepic.jpg"
---
# About Me
Hey there! I'm Kevin, a third year Operations Research Student also completing a Computing Science minor at Simon Fraser University. I've always been the one to stand at a store comparing different products trying to pick which one is the best for me, combining that with my passion towards mathematics, statistics, and computing, it naturally led me to the field of decision science and data analytics. My primary interests are in public transportation and consumer behaviour, and I'm eager for any opportunities that come along the way!
# Resume
To learn more about my technical experiences check out my resume [here](https://github.com/kaishuun/Portfolio-Website/blob/master/public/images/about/Resume-%20Kevin.pdf)
| 48.888889 | 538 | 0.784091 | eng_Latn | 0.989834 |
8a9e424c7207058259fa3efdbfc593004a6d7ff7 | 951 | md | Markdown | TODO.md | EliteNation/DPS | 807ea71eda19de3edbf6491225edcbc74ed2b78c | [
"Apache-2.0"
] | null | null | null | TODO.md | EliteNation/DPS | 807ea71eda19de3edbf6491225edcbc74ed2b78c | [
"Apache-2.0"
] | null | null | null | TODO.md | EliteNation/DPS | 807ea71eda19de3edbf6491225edcbc74ed2b78c | [
"Apache-2.0"
] | null | null | null | Device 1 is low on battery - it sends a signal to the transponder
The transponder will keep track of power levels, safe power constants, and inform the relay to transmit intervals
transponder recieves device location - on device location change, it sends the update to the transponder
this way no excessive data nor power is lost
relay sends power to device
if device no longer needs power, it sends a drop connection to transponder
if there is a remainder power data towards the device, subtract it
if there are any devices left, iterate through another power cycle
if there are no devices left, put transponder into a low-power state, until another device sends an activation signal
relay sends no (send) signal until transponder activates it
likewise with a transponder sends no (send) signal until a device activates it
only the relative location of the devices will be transmitted to, but the transponder can recieve from any direction
| 41.347826 | 117 | 0.806519 | eng_Latn | 0.999575 |
8a9ea41b5d65a865a07174933820b0facff423a1 | 2,136 | md | Markdown | api/wrappers/jsp/scheduler/messages-recurrenceeditor-end.md | colinvo/kendo-docs | 7adfa37886ec90fca3544d47abd5f76422497da1 | [
"Unlicense",
"MIT"
] | 1 | 2016-02-03T10:15:54.000Z | 2016-02-03T10:15:54.000Z | api/wrappers/jsp/scheduler/messages-recurrenceeditor-end.md | colinvo/kendo-docs | 7adfa37886ec90fca3544d47abd5f76422497da1 | [
"Unlicense",
"MIT"
] | null | null | null | api/wrappers/jsp/scheduler/messages-recurrenceeditor-end.md | colinvo/kendo-docs | 7adfa37886ec90fca3544d47abd5f76422497da1 | [
"Unlicense",
"MIT"
] | null | null | null | ---
title: scheduler-messages-recurrenceEditor-end
slug: jsp-scheduler-messages-recurrenceEditor-end
tags: api, java
publish: true
---
# \<kendo:scheduler-messages-recurrenceEditor-end\>
The configuration of the scheduler recurrence editor end messages. Use this option to customize or localize the scheduler recurrence editor end messages.
#### Example
<kendo:scheduler-messages-recurrenceEditor>
<kendo:scheduler-messages-recurrenceEditor-end></kendo:scheduler-messages-recurrenceEditor-end>
</kendo:scheduler-messages-recurrenceEditor>
## Configuration Attributes
### after `java.lang.String`
The text similar to "After " displayed in the scheduler recurrence editor.
#### Example
<kendo:scheduler-messages-recurrenceEditor-end after="after">
</kendo:scheduler-messages-recurrenceEditor-end>
### label `java.lang.String`
The text similar to "End:" displayed in the scheduler recurrence editor.
#### Example
<kendo:scheduler-messages-recurrenceEditor-end label="label">
</kendo:scheduler-messages-recurrenceEditor-end>
### mobileLabel `java.lang.String`
The text similar to "Ends" displayed in the adaptive version of the scheduler recurrence editor.
#### Example
<kendo:scheduler-messages-recurrenceEditor-end mobileLabel="mobileLabel">
</kendo:scheduler-messages-recurrenceEditor-end>
### never `java.lang.String`
The text similar to "Never" displayed in the scheduler recurrence editor.
#### Example
<kendo:scheduler-messages-recurrenceEditor-end never="never">
</kendo:scheduler-messages-recurrenceEditor-end>
### occurrence `java.lang.String`
The text similar to " occurrence(s)" displayed in the scheduler recurrence editor.
#### Example
<kendo:scheduler-messages-recurrenceEditor-end occurrence="occurrence">
</kendo:scheduler-messages-recurrenceEditor-end>
### on `java.lang.String`
The text similar to "On " displayed in the scheduler recurrence editor.
#### Example
<kendo:scheduler-messages-recurrenceEditor-end on="on">
</kendo:scheduler-messages-recurrenceEditor-end>
| 31.880597 | 154 | 0.738296 | eng_Latn | 0.784824 |
8a9f1380d48935a5c8e447270beea642b06a5117 | 909 | md | Markdown | documents/amazon-lex-developer-guide/doc_source/API_BuiltinIntentSlot.md | siagholami/aws-documentation | 2d06ee9011f3192b2ff38c09f04e01f1ea9e0191 | [
"CC-BY-4.0"
] | 5 | 2021-08-13T09:20:58.000Z | 2021-12-16T22:13:54.000Z | documents/amazon-lex-developer-guide/doc_source/API_BuiltinIntentSlot.md | siagholami/aws-documentation | 2d06ee9011f3192b2ff38c09f04e01f1ea9e0191 | [
"CC-BY-4.0"
] | null | null | null | documents/amazon-lex-developer-guide/doc_source/API_BuiltinIntentSlot.md | siagholami/aws-documentation | 2d06ee9011f3192b2ff38c09f04e01f1ea9e0191 | [
"CC-BY-4.0"
] | null | null | null | # BuiltinIntentSlot<a name="API_BuiltinIntentSlot"></a>
Provides information about a slot used in a built\-in intent\.
## Contents<a name="API_BuiltinIntentSlot_Contents"></a>
**name** <a name="lex-Type-BuiltinIntentSlot-name"></a>
A list of the slots defined for the intent\.
Type: String
Required: No
## See Also<a name="API_BuiltinIntentSlot_SeeAlso"></a>
For more information about using this API in one of the language\-specific AWS SDKs, see the following:
+ [AWS SDK for C\+\+](https://docs.aws.amazon.com/goto/SdkForCpp/lex-models-2017-04-19/BuiltinIntentSlot)
+ [AWS SDK for Go](https://docs.aws.amazon.com/goto/SdkForGoV1/lex-models-2017-04-19/BuiltinIntentSlot)
+ [AWS SDK for Java](https://docs.aws.amazon.com/goto/SdkForJava/lex-models-2017-04-19/BuiltinIntentSlot)
+ [AWS SDK for Ruby V3](https://docs.aws.amazon.com/goto/SdkForRubyV3/lex-models-2017-04-19/BuiltinIntentSlot) | 50.5 | 112 | 0.748075 | yue_Hant | 0.710025 |
8a9f2521e909ffe66fd5d3a0cb724498b8bc0394 | 3,458 | md | Markdown | packages/mock-data/CHANGELOG.md | tannerbyers/availity-workflow | 692746a93c745292ceea63edae7869c7a30980f9 | [
"MIT"
] | null | null | null | packages/mock-data/CHANGELOG.md | tannerbyers/availity-workflow | 692746a93c745292ceea63edae7869c7a30980f9 | [
"MIT"
] | null | null | null | packages/mock-data/CHANGELOG.md | tannerbyers/availity-workflow | 692746a93c745292ceea63edae7869c7a30980f9 | [
"MIT"
] | null | null | null | # Change Log
All notable changes to this project will be documented in this file.
See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
## [5.5.7](https://github.com/Availity/availity-workflow/compare/@availity/[email protected]...@availity/[email protected]) (2020-07-03)
**Note:** Version bump only for package @availity/mock-data
## 5.5.6 (2020-04-24)
**Note:** Version bump only for package @availity/mock-data
## 5.5.5 (2020-04-23)
### Bug Fixes
* **workflow:** wrong path to static folder for copying ([6140e5f](https://github.com/Availity/availity-workflow/commit/6140e5f7d3793493f2a865aa632b56ac55688e03))
## 5.5.4 (2020-04-21)
**Note:** Version bump only for package @availity/mock-data
## 5.5.3 (2020-04-21)
**Note:** Version bump only for package @availity/mock-data
## 5.5.2 (2020-04-21)
**Note:** Version bump only for package @availity/mock-data
## 5.5.1 (2020-04-06)
**Note:** Version bump only for package @availity/mock-data
# 5.5.0 (2020-02-19)
# 5.4.0 (2019-08-09)
## 5.3.9 (2019-06-17)
## 5.3.8 (2019-06-11)
## 5.3.7 (2019-06-11)
## 5.3.6 (2019-06-11)
## 5.3.5 (2019-06-11)
## 5.3.4 (2019-06-07)
### Bug Fixes
* **mock-data:** fixed incorrect data response issue ([9475897](https://github.com/Availity/availity-workflow/commit/9475897ae4c44e69102cdff301cacdd12b7c5063))
## 5.3.3 (2019-06-03)
## 5.3.2 (2019-06-03)
## 5.3.1 (2019-05-10)
### Bug Fixes
* **mock-data:** the mock-data response for axi userpermissions where incorrect ([02ea324](https://github.com/Availity/availity-workflow/commit/02ea324e8d9becb55c20b574d80885d9bf5a6da5))
# 5.3.0 (2019-05-02)
### Features
* **mock-data:** add legacy permission to mock routes ([9baf02f](https://github.com/Availity/availity-workflow/commit/9baf02fb65ef5fadc9f00e40dcfe54769185e00c))
## 5.2.8 (2019-04-30)
## 5.2.7 (2019-04-25)
## 5.2.6-alpha.1 (2019-04-22)
## 5.2.5 (2019-04-15)
## 5.2.4 (2019-04-12)
## 5.2.3 (2019-04-11)
## 5.2.2 (2019-04-11)
## 5.2.1 (2019-04-11)
# 5.2.0 (2019-04-02)
# 5.1.0 (2019-03-29)
## 5.0.1 (2019-03-20)
# 5.0.0-alpha.8 (2019-01-29)
# 5.0.0-alpha.7 (2019-01-29)
### Bug Fixes
* **workflow:** fixed eslint issues ([54e070d](https://github.com/Availity/availity-workflow/commit/54e070da7cc2c732bc8bcfb8e58a963464a4dc7b))
# 5.0.0-alpha.6 (2019-01-29)
# 5.0.0-alpha.5 (2019-01-04)
# 5.0.0-alpha.4 (2019-01-04)
# 5.0.0-alpha.3 (2019-01-03)
# 5.0.0-alpha.2 (2018-12-21)
# 5.0.0-alpha.1 (2018-12-21)
# 5.0.0-alpha.0 (2018-12-15)
## 4.0.3 (2018-10-26)
## 4.0.2 (2018-08-23)
## 4.0.1 (2018-08-16)
# 4.0.0-alpha.18 (2018-07-25)
# 4.0.0-alpha.17 (2018-07-18)
# 4.0.0-alpha.16 (2018-06-22)
### Bug Fixes
* **mock-data:** add uiDisplayName to providers ([b12989f](https://github.com/Availity/availity-workflow/commit/b12989f693d05e5ac76cf6644dee5ce15082d564))
# 4.0.0-alpha.15 (2018-06-21)
# 4.0.0-alpha.14 (2018-05-22)
# 4.0.0-alpha.13 (2018-05-21)
# 4.0.0-alpha.12 (2018-05-16)
# 4.0.0-alpha.11 (2018-04-26)
# 4.0.0-alpha.10 (2018-04-26)
# 4.0.0-alpha.9 (2018-04-26)
# 4.0.0-alpha.8 (2018-04-24)
# 4.0.0-alpha.7 (2018-04-23)
# 4.0.0-alpha.6 (2018-04-13)
# 4.0.0-alpha.5 (2018-04-05)
# 4.0.0-alpha.4 (2018-04-04)
# 4.0.0-alpha.3 (2018-04-04)
# 4.0.0-alpha.2 (2018-04-04)
# 4.0.0-alpha.1 (2018-04-04)
# 4.0.0-alpha.0 (2018-04-04)
| 11.412541 | 186 | 0.628976 | eng_Latn | 0.133619 |
8a9f635b4625641c3c510a4ac7099c0c378c20b6 | 220 | md | Markdown | README.md | datasciencecampus/im_tutorials | b234069f30e5a2d631a731d51e27b367c59a2d87 | [
"MIT"
] | null | null | null | README.md | datasciencecampus/im_tutorials | b234069f30e5a2d631a731d51e27b367c59a2d87 | [
"MIT"
] | null | null | null | README.md | datasciencecampus/im_tutorials | b234069f30e5a2d631a731d51e27b367c59a2d87 | [
"MIT"
] | 1 | 2021-04-10T21:27:52.000Z | 2021-04-10T21:27:52.000Z | Innovation Mapping Tutorials
============================
Welcome to Nesta's Innovation Mapping tutorial repository :books:
Here you can find materials from Innovation Mapping team workshops.
## Tutorial Directory
| 20 | 67 | 0.704545 | eng_Latn | 0.920389 |
8a9fc8ee6f7d01e0037ef5ee197afdd69c3abe90 | 53 | md | Markdown | README.md | bense4ger/article-writer | 97611c3141a1a1a528213472a5b79079bb369251 | [
"MIT"
] | null | null | null | README.md | bense4ger/article-writer | 97611c3141a1a1a528213472a5b79079bb369251 | [
"MIT"
] | null | null | null | README.md | bense4ger/article-writer | 97611c3141a1a1a528213472a5b79079bb369251 | [
"MIT"
] | null | null | null | # article-writer
CLI to publish articles to DynamoDB
| 17.666667 | 35 | 0.811321 | eng_Latn | 0.999388 |
8a9fcd69fdadd21a092ebebd692ce2e67455ac71 | 106,698 | md | Markdown | docs/relational-databases/system-dynamic-management-views/sys-dm-os-wait-stats-transact-sql.md | moonloverx2/sql-docs.zh-cn | cf2b82125dc2651da559e4f5e5805f1766f0e71a | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/relational-databases/system-dynamic-management-views/sys-dm-os-wait-stats-transact-sql.md | moonloverx2/sql-docs.zh-cn | cf2b82125dc2651da559e4f5e5805f1766f0e71a | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/relational-databases/system-dynamic-management-views/sys-dm-os-wait-stats-transact-sql.md | moonloverx2/sql-docs.zh-cn | cf2b82125dc2651da559e4f5e5805f1766f0e71a | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: sys.dm_os_wait_stats (TRANSACT-SQL) |Microsoft Docs
ms.custom: ''
ms.date: 04/23/2018
ms.prod: sql
ms.prod_service: database-engine, sql-database, sql-data-warehouse, pdw
ms.reviewer: ''
ms.technology: system-objects
ms.topic: language-reference
f1_keywords:
- dm_os_wait_stats_TSQL
- dm_os_wait_stats
- sys.dm_os_wait_stats
- sys.dm_os_wait_stats_TSQL
dev_langs:
- TSQL
helpviewer_keywords:
- sys.dm_os_wait_stats dynamic management view
ms.assetid: 568d89ed-2c96-4795-8a0c-2f3e375081da
author: MashaMSFT
ms.author: mathoma
manager: craigg
monikerRange: '>=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-server-2016||=sqlallproducts-allversions||>=sql-server-linux-2017||=azuresqldb-mi-current'
ms.openlocfilehash: 513b85aafb4cd25d55dfb40e37dabd6fc47b814f
ms.sourcegitcommit: ce4b39bf88c9a423ff240a7e3ac840a532c6fcae
ms.translationtype: MT
ms.contentlocale: zh-CN
ms.lasthandoff: 10/09/2018
ms.locfileid: "48878190"
---
# <a name="sysdmoswaitstats-transact-sql"></a>sys.dm_os_wait_stats (Transact-SQL)
[!INCLUDE[tsql-appliesto-ss2008-all-md](../../includes/tsql-appliesto-ss2008-all-md.md)]
返回执行的线程所遇到的所有等待的相关信息。 可以使用此聚合视图来诊断 [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] 以及特定查询和批处理的性能问题。 [sys.dm_exec_session_wait_stats (TRANSACT-SQL) ](../../relational-databases/system-dynamic-management-views/sys-dm-exec-session-wait-stats-transact-sql.md)提供类似的会话的信息。
> [!NOTE]
> 若要调用此项从**[!INCLUDE[ssSDWfull](../../includes/sssdwfull-md.md)]或[!INCLUDE[ssPDW](../../includes/sspdw-md.md)]** ，使用的名称**sys.dm_pdw_nodes_os_wait_stats**。
|列名|数据类型|Description|
|-----------------|---------------|-----------------|
|wait_type|**nvarchar(60)**|等待类型的名称。 有关详细信息，请参阅[等待类型](#WaitTypes)，本主题中更高版本。|
|waiting_tasks_count|**bigint**|该等待类型的等待数。 该计数器在每开始一个等待时便会增加。|
|wait_time_ms|**bigint**|该等待类型的总等待时间（毫秒）。 该时间包括 signal_wait_time_ms。|
|max_wait_time_ms|**bigint**|该等待类型的最长等待时间。|
|signal_wait_time_ms|**bigint**|正在等待的线程从收到信号通知到其开始运行之间的时差。|
|pdw_node_id|**int**|对于此分布的节点标识符。 <br/> **适用于**: [!INCLUDE[ssSDWfull](../../includes/sssdwfull-md.md)]， [!INCLUDE[ssPDW](../../includes/sspdw-md.md)] |
## <a name="permissions"></a>Permissions
上[!INCLUDE[ssNoVersion_md](../../includes/ssnoversion-md.md)]，需要`VIEW SERVER STATE`权限。
上[!INCLUDE[ssSDS_md](../../includes/sssds-md.md)]，需要`VIEW DATABASE STATE`数据库中的权限。
## <a name="WaitTypes"></a> 等待的类型
**资源等待**工作线程请求访问资源，因为资源正由其他某个工作线程或尚不可用不可用时，便会发生资源等待。 资源等待的示例包括锁等待、闩锁等待、网络等待以及磁盘 I/O 等待。 锁等待和闩锁等待是指等待同步对象
**队列等待**
当工作线程空闲，等待分配工作时便会发生队列等待。 队列等待通常发生在系统后台任务（如监视死锁以及清除已删除的记录等任务）中。 这些任务将等待工作请求被放入工作队列。 即使没有新数据包放入队列，队列等待也可能定期处于活动状态。
**外部等待**
当 [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] 工作线程正在等待外部事件（如扩展存储过程调用或链接服务器查询）完成时，便会发生外部等待。 当诊断有妨碍的问题时，请记住，外部等待不会始终表示工作线程处于空闲状态，因为工作线程可能处于活动状态且正在运行某些外部代码。
`sys.dm_os_wait_stats` 显示已完成的等待时间。 此动态管理视图不显示当前等待。
如果出现下列任一情况，则不认为 [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] 工作线程处于等待状态：
- 资源变得可用。
- 查询非空。
- 外部进程完成。
尽管线程不再处于等待状态，但是它不必立即开始运行。 这是因为此类线程首先放入可运行工作线程的队列中，并且必须等待量程在计划程序中运行。
在中[!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]等待时间计数器**bigint**值，并因此不一样容易出现计数器滚动更新的早期版本中的等效计数器作为[!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]。
执行查询期间的特定等待时间类型可以说明查询中存在瓶颈或失效点。 同样，如果服务器级的等待时间较长或等待计数较多，说明服务器实例内交互查询交互中存在瓶颈或热点。 例如，锁等待指示查询争用数据；页 IO 闩锁等待指示 IO 响应时间较慢；页闩锁更新指示表示文件布局不正确。
此动态管理视图的内容可通过运行以下命令来重置：
```sql
DBCC SQLPERF ('sys.dm_os_wait_stats', CLEAR);
GO
```
该命令将所有计数器重置为 0。
> [!NOTE]
> 这些统计信息在每次重新启动 [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] 时都不能持续存在，并且所有的数据均为自上次重置统计信息或启动服务器以来累积的数据。
下表列出各任务所遇到的等待类型。
|type |Description|
|-------------------------- |--------------------------|
|ABR |标识为仅供参考。 不提供支持。 不保证以后的兼容性。| |
|AM_INDBUILD_ALLOCATION |TBD <br />**适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|AM_SCHEMAMGR_UNSHARED_CACHE |TBD <br />**适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|ASSEMBLY_FILTER_HASHTABLE |TBD <br />**适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|ASSEMBLY_LOAD |在以独占的方式访问程序集加载时出现。|
|ASYNC_DISKPOOL_LOCK |当尝试同步并行的线程（执行创建或初始化文件等任务）时出现。|
|ASYNC_IO_COMPLETION |当某任务正在等待 I/O 完成时出现。|
|ASYNC_NETWORK_IO |当任务被阻止在网络之后时出现在网络写入中。 验证客户端是否正在处理来自服务器的数据。|
|ASYNC_OP_COMPLETION |TBD <br />**适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|ASYNC_OP_CONTEXT_READ |TBD <br />**适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|ASYNC_OP_CONTEXT_WRITE |TBD <br />**适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|ASYNC_SOCKETDUP_IO |TBD <br />**适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|AUDIT_GROUPCACHE_LOCK |当等待控制对某个特殊缓存的访问的锁时出现。 该缓存包含正在使用哪些审核来审核每个审核操作组的相关信息。|
|AUDIT_LOGINCACHE_LOCK |当等待控制对某个特殊缓存的访问的锁时出现。 该缓存包含正在使用哪些审核来审核登录审核操作组的相关信息。|
|AUDIT_ON_DEMAND_TARGET_LOCK |当等待用于确保扩展事件目标相关审核的单一初始化的锁时出现。|
|AUDIT_XE_SESSION_MGR |当等待用于同步扩展事件会话相关审核的启动和停止的锁时出现。|
|BACKUP |当任务作为备份处理的一部分被阻止时出现。|
|BACKUP_OPERATOR |当任务正在等待磁带装入时出现。 若要查看磁带状态，请查询 sys.dm_io_backup_tapes。 如果装入操作没有挂起，则该等待类型可能指示磁带机发生硬件问题。|
|BACKUPBUFFER |在备份任务等待数据或等待用来存储数据的缓冲区时发生。 此类型不常见，只有当任务等待装入磁带时才会出现。|
|BACKUPIO |在备份任务等待数据或等待用来存储数据的缓冲区时发生。 此类型不常见，只有当任务等待装入磁带时才会出现。|
|BACKUPTHREAD |当某任务正在等待备份任务完成时出现。 等待时间可能较长，从几分钟到几个小时。 如果被等待的任务正处于 I/O 进程中，则该类型不指示发生问题。|
|BAD_PAGE_PROCESS |当后台可疑页记录器正在尝试避免每隔五秒以上的时间运行时出现。 过多的可疑页会导致记录器频繁运行。|
|BLOB_METADATA |TBD <br />**适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|BMPALLOCATION |TBD <br />**适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|BMPBUILD |TBD <br />**适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|BMPREPARTITION |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|BMPREPLICATION |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|BPSORT |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|BROKER_CONNECTION_RECEIVE_TASK |在等待访问以便在连接端点上接收消息时出现。 已序列化对端点的接收访问。|
|BROKER_DISPATCHER |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|BROKER_ENDPOINT_STATE_MUTEX |当存在的争用，访问 Service Broker 连接终结点的状态时发生。 已序列化对更改状态的访问。|
|BROKER_EVENTHANDLER |当某任务正在等待中的 Service Broker 主事件处理程序时发生。 出现时间应该非常短暂。|
|BROKER_FORWARDER |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|BROKER_INIT |当初始化每个活动数据库中的 Service Broker 时出现。 该状态应当频繁出现。|
|BROKER_MASTERSTART |当某任务正在等待启动的 Service broker 主事件处理程序时发生。 出现时间应该非常短暂。|
|BROKER_RECEIVE_WAITFOR |当 RECEIVE WAITFOR 正在等待时出现。 这可能意味着的不已准备好的队列中收到任何消息或锁争用阻止它从队列接收消息。|
|BROKER_REGISTERALLENDPOINTS |在 Service Broker 连接终结点的初始化期间发生。 出现时间应该非常短暂。|
|BROKER_SERVICE |当更新或重新设定优先顺序与目标服务关联的 Service Broker 目标列表时发生。|
|BROKER_SHUTDOWN |当 Service Broker 按计划的关闭时发生。 该状态出现的时间应当尽量短暂。|
|BROKER_START |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|BROKER_TASK_SHUTDOWN |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|BROKER_TASK_STOP |当 Service Broker 队列任务处理程序尝试关闭任务时发生。 已序列化状态检查，并且必须预先处于运行状态。|
|BROKER_TASK_SUBMIT |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|BROKER_TO_FLUSH |当 Service Broker 延迟 flusher 刷新将内存中传输对象添加到工作表时发生。|
|BROKER_TRANSMISSION_OBJECT |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|BROKER_TRANSMISSION_TABLE |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|BROKER_TRANSMISSION_WORK |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|BROKER_TRANSMITTER |当 Service Broker 发送器正在等待工作时出现。 Service Broker 具有称为发送器计划来自多个对话框通过一个或多个连接终结点通过网络发送的消息的组件。 发射器具有 2 个专用的线程实现此目的。 此等待类型负责这些发送器线程等待对话框消息发送时使用的传输连接。 此等待类型的 waiting_tasks_count 的高值指向这些发送器线程的间歇性工作，不是任何性能问题的迹象。 如果根本不使用 service broker，waiting_tasks_count 应为 2 （对于 2 发送器线程中），wait_time_ms 应为两次实例启动以来的持续时间。 请参阅[Service broker 等待统计信息](https://blogs.msdn.microsoft.com/sql_service_broker/2008/12/01/service-broker-wait-types)。|
|BUILTIN_HASHKEY_MUTEX |可能在实例启动之后而在初始化内部数据结构时出现。 数据结构初始化之后将不会再次出现。|
|CHANGE_TRACKING_WAITFORCHANGES |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|CHECK_PRINT_RECORD |标识为仅供参考。 不提供支持。 不保证以后的兼容性。|
|CHECK_SCANNER_MUTEX |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|CHECK_TABLES_INITIALIZATION |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|CHECK_TABLES_SINGLE_SCAN |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|CHECK_TABLES_THREAD_BARRIER |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|CHECKPOINT_QUEUE |当检查点任务正在等待下一个检查点请求时出现。|
|CHKPT |在服务器启动时出现以通知检查点线程可以启动。|
|CLEAR_DB |在执行会更改数据库状态的操作过程中发生，例如打开或关闭数据库。|
|CLR_AUTO_EVENT |当某任务当前正在执行公共语言运行时 (CLR) 执行并且正在等待特殊的自动事件启动时出现。 通常会出现长时间等待，这并不意味着出现问题。|
|CLR_CRST |当某任务当前正在执行 CLR 执行并且正在等待输入当前由另一项任务正在使用的任务的关键部分时出现。|
|CLR_JOIN |当某任务当前正在执行 CLR 执行并且正在等待另一项任务结束时出现。 当两任务之间具有联接时出现该等待状态。|
|CLR_MANUAL_EVENT |当某任务当前正在执行 CLR 执行并且正在等待特定手动事件启动时出现。|
|CLR_MEMORY_SPY |当为用于记录来自 CLR 的所有虚拟内存分配的数据结构等待获取锁时出现。 如果存在并行访问，该数据结构将被锁定以维护其完整性。|
|CLR_MONITOR |当某任务当前正在执行 CLR 执行并且正在等待获取用于监视器的锁时出现。|
|CLR_RWLOCK_READER |当某任务当前正在执行 CLR 执行并且正在等待读取器锁时出现。|
|CLR_RWLOCK_WRITER |当某任务当前正在执行 CLR 执行并且正在等待编写器锁时出现。|
|CLR_SEMAPHORE |当某任务当前正在执行 CLR 执行并且正在等待信号量时出现。|
|CLR_TASK_START |在等待 CLR 任务完成启动时出现。|
|CLRHOST_STATE_ACCESS |当等待获取对 CLR 宿主数据结构的独占访问时出现。 当设置或关闭 CLR 运行时时出现此等待类型。|
|CMEMPARTITIONED |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|CMEMTHREAD |当某任务正在等待线程安全内存对象时出现。 当多项任务尝试分配来自同一个内存对象的内存而导致出现争用时，便可能延长等待时间。|
|COLUMNSTORE_BUILD_THROTTLE |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|COLUMNSTORE_COLUMNDATASET_SESSION_LIST |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|COMMIT_TABLE |TBD|
|CONNECTION_ENDPOINT_LOCK |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|COUNTRECOVERYMGR |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|CREATE_DATINISERVICE |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|CXCONSUMER |当使用者线程等待制造者线程，以将行发送时出现并行查询计划。 这是并行查询执行的常见现象。 <br /> **适用于**: [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] (开头[!INCLUDE[ssSQL15](../../includes/sssql15-md.md)]SP2， [!INCLUDE[ssSQL17](../../includes/sssql17-md.md)] cu3 开始)， [!INCLUDE[ssSDS](../../includes/sssds-md.md)]|
|CXPACKET |当同步查询处理器交换迭代器，并生成和使用行时出现并行查询计划。 如果等待太久，无法通过优化查询（如添加索引）来减少等待时间，请考虑调整并行度的开销阈值或降低并行度。<br /> **注意：** 开头[!INCLUDE[ssSQL15](../../includes/sssql15-md.md)]SP2 [!INCLUDE[ssSQL17](../../includes/sssql17-md.md)] CU3，和[!INCLUDE[ssSDS](../../includes/sssds-md.md)]，CXPACKET 仅是指同步查询处理器交换迭代器，以及生成行的使用者线程的。 使用者线程将被单独跟踪在 CXCONSUMER 等待类型中。|
|CXROWSET_SYNC |在并行范围扫描期间出现。|
|DAC_INIT |当正在初始化专用管理员连接时出现。|
|DBCC_SCALE_OUT_EXPR_CACHE |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|DBMIRROR_DBM_EVENT |标识为仅供参考。 不提供支持。 不保证以后的兼容性。|
|DBMIRROR_DBM_MUTEX |标识为仅供参考。 不提供支持。 不保证以后的兼容性。|
|DBMIRROR_EVENTS_QUEUE |在数据库镜像等待处理事件时出现。|
|DBMIRROR_SEND |当某任务正在等待清除网络层的通信积压以便能够发送消息时出现。 指示通信层正在开始重载并影响数据库镜像数据吞吐量。|
|DBMIRROR_WORKER_QUEUE |指示数据库镜像工作线程任务正在等待更多的工作。|
|DBMIRRORING_CMD |当某任务正在等待日志记录刷新到磁盘时出现。 该等待状态应当保留较长的时间。|
|DBSEEDING_FLOWCONTROL |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|DBSEEDING_OPERATION |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|DEADLOCK_ENUM_MUTEX |当死锁监视器和 sys.dm_os_waiting_tasks 尝试确保 SQL Server 在同一时间未运行多个死锁搜索时出现。|
|DEADLOCK_TASK_SEARCH |长时间等待此资源指示服务器正在 sys.dm_os_waiting_tasks 之上执行查询，并且这些查询正在阻止死锁监视器运行死锁搜索。 该等待类型仅供死锁监视器使用。 sys.dm_os_waiting_tasks 之上的查询使用 DEADLOCK_ENUM_MUTEX。|
|DEBUG |在 TRANSACT-SQL 和 CLR 调试内部同步期间出现。|
|DIRECTLOGCONSUMER_LIST |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|DIRTY_PAGE_POLL |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|DIRTY_PAGE_SYNC |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|DIRTY_PAGE_TABLE_LOCK |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|DISABLE_VERSIONING |SQL Server 轮询版本事务管理器，以查看最早活动事务的时间戳是否晚于状态开始更改的时间戳时发生。 如果是，则所有在 ALTER DATABASE 语句运行之前启动的快照事务都已完成。 SQL Server 使用 ALTER DATABASE 语句禁用版本控制时，使用该等待状态。|
|DISKIO_SUSPEND |当某任务正在等待访问文件（外部备份处于活动状态）时出现。 针对每个正在等待的用户进程报告该状态。 每个用户进程大于五的计数可能指示外部备份需要太长时间才能完成。|
|DISPATCHER_PRIORITY_QUEUE_SEMAPHORE |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|DISPATCHER_QUEUE_SEMAPHORE |当调度程序池中的线程正在等待更多要处理的工作时出现。 当调度程序处于空闲状态时，此等待类型的等待时间预计要增加。|
|DLL_LOADING_MUTEX |在等待 XML 分析器 DLL 加载时出现。|
|DPT_ENTRY_LOCK |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|DROP_DATABASE_TIMER_TASK |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|DROPTEMP |在上次尝试删除临时对象失败后再进行下次尝试之前出现。 对于每一次失败的删除尝试，等待持续时间都以指数形式增长。|
|DTC |当某任务正在等待用于管理状态转换的事件时出现。 Microsoft 分布式事务处理协调器 (MS DTC) 事务的恢复发生后 SQL Server 接收通知的 MS DTC 服务已变为不可用时此状态控制。|
|DTC_ABORT_REQUEST |当 MS DTC 工作线程会话正在等待获得 MS DTC 事务的所有权时，在该会话中出现。 当 MS DTC 拥有了事务后，该会话可以回滚事务。 通常，该会话将等待另一个正在使用事务的会话。|
|DTC_RESOLVE |当恢复任务正在等待跨数据库事务中的 master 数据库以查询该事务的结果时出现。|
|DTC_STATE |当某任务正在等待对内部 MS DTC 全局状态对象的更改进行保护的事件时出现。 该状态应当保持非常短的时间。|
|DTC_TMDOWN_REQUEST |当 SQL Server 收到通知，MS DTC 服务不可用的 MS DTC 工作线程会话中发生。 首先，工作线程将等待 MS DTC 恢复进程启动。 然后，工作线程等待获取其正在处理的分布式事务的结果。 此过程可能一直执行，直到重新建立与 MS DTC 服务的连接。|
|DTC_WAITFOR_OUTCOME |当恢复任务等待 MS DTC 处于活动状态以启用准备好的事务的解决方法时出现。|
|DTCNEW_ENLIST |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|DTCNEW_PREPARE |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|DTCNEW_RECOVERY |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|DTCNEW_TM |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|DTCNEW_TRANSACTION_ENLISTMENT |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|DTCPNTSYNC |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|DUMP_LOG_COORDINATOR |当主任务正在等待子任务生成数据时出现。 该状态通常不会出现。 长时间的等待指示出现意外的阻塞。 应当对子任务进行调查。|
|DUMP_LOG_COORDINATOR_QUEUE |TBD|
|DUMPTRIGGER |标识为仅供参考。 不提供支持。 不保证以后的兼容性。|
|EC |标识为仅供参考。 不提供支持。 不保证以后的兼容性。|
|EE_PMOLOCK |在语句执行过程中特定的内存分配类型同步期间出现。|
|EE_SPECPROC_MAP_INIT |在对内部过程哈希表创建进行同步期间发生。 此等待只能初始访问期间的哈希表的 SQL Server 实例启动后发生。|
|ENABLE_EMPTY_VERSIONING |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|ENABLE_VERSIONING |SQL Server 等待在声明数据库可以转换到快照隔离允许的状态之前完成此数据库中的所有更新事务时出现。 SQL Server 通过使用 ALTER DATABASE 语句启用快照隔离时使用此状态。|
|ERROR_REPORTING_MANAGER |在对多个并发错误日志初始化进行同步期间发生。|
|EXCHANGE |在并行查询过程中查询处理器交换迭代器同步期间出现。|
|EXECSYNC |在并行查询过程中同步与交换迭代器无关的区域内的查询处理器期间出现。 例如，此类区域包括位图、二进制大型对象 (LOB) 以及假脱机迭代器等。 LOB 可能会经常使用该等待状态。|
|EXECUTION_PIPE_EVENT_INTERNAL |当同步通过连接上下文提交的批处理执行的创建器和使用者部件期间出现。|
|EXTERNAL_RG_UPDATE |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|EXTERNAL_SCRIPT_NETWORK_IO |TBD <br /> **适用于**:[!INCLUDE[ssSQLv14_md](../../includes/sssqlv14-md.md)]当前。|
|EXTERNAL_SCRIPT_PREPARE_SERVICE |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|EXTERNAL_SCRIPT_SHUTDOWN |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|EXTERNAL_WAIT_ON_LAUNCHER， |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|FABRIC_HADR_TRANSPORT_CONNECTION |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|FABRIC_REPLICA_CONTROLLER_LIST |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|FABRIC_REPLICA_CONTROLLER_STATE_AND_CONFIG |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|FABRIC_REPLICA_PUBLISHER_EVENT_PUBLISH |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|FABRIC_REPLICA_PUBLISHER_SUBSCRIBER_LIST |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|FABRIC_WAIT_FOR_BUILD_REPLICA_EVENT_PROCESSING |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|FAILPOINT |标识为仅供参考。 不提供支持。 不保证以后的兼容性。|
|FCB_REPLICA_READ |当同步快照（或 DBCC 创建的临时快照）稀疏文件的读取时出现。|
|FCB_REPLICA_WRITE |当同步快照（或 DBCC 创建的临时快照）稀疏文件的页推送或页请求时出现。|
|FEATURE_SWITCHES_UPDATE |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|FFT_NSO_DB_KILL_FLAG |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|FFT_NSO_DB_LIST |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|FFT_NSO_FCB |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|FFT_NSO_FCB_FIND |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|FFT_NSO_FCB_PARENT |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|FFT_NSO_FCB_RELEASE_CACHED_ENTRIES |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|FFT_NSO_FCB_STATE |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|FFT_NSO_FILEOBJECT |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|FFT_NSO_TABLE_LIST |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|FFT_NTFS_STORE |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|FFT_RECOVERY |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|FFT_RSFX_COMM |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|FFT_RSFX_WAIT_FOR_MEMORY |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|FFT_STARTUP_SHUTDOWN |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|FFT_STORE_DB |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|FFT_STORE_ROWSET_LIST |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|FFT_STORE_TABLE |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|FILE_VALIDATION_THREADS |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|FILESTREAM_CACHE |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|FILESTREAM_CHUNKER |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|FILESTREAM_CHUNKER_INIT |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|FILESTREAM_FCB |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|FILESTREAM_FILE_OBJECT |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|FILESTREAM_WORKITEM_QUEUE |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|FILETABLE_SHUTDOWN |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|FOREIGN_REDO |TBD <br /> **适用于**:[!INCLUDE[ssSQLv14_md](../../includes/sssqlv14-md.md)]当前。|
|FORWARDER_TRANSITION |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|FS_FC_RWLOCK |当 FILESTREAM 垃圾收集器等待执行下列操作之一时出现：|
|FS_GARBAGE_COLLECTOR_SHUTDOWN |当 FILESTREAM 垃圾收集器等待清除任务完成时出现。|
|FS_HEADER_RWLOCK |当等待获取对 FILESTREAM 数据容器的 FILESTREAM 标头的访问，以便读取或更新 FILESTREAM 标头文件 (Filestream.hdr) 中的内容时出现。|
|FS_LOGTRUNC_RWLOCK |当等待获取对 FILESTREAM 日志截断的访问以执行下列操作之一时出现：|
|FSA_FORCE_OWN_XACT |当 FILESTREAM 文件 I/O 操作需要绑定到关联的事务，但该事务当前由另一个会话拥有时出现。|
|FSAGENT |当 FILESTREAM 文件 I/O 操作等待的 FILESTREAM 代理资源正由另一个文件 I/O 操作使用时出现。|
|FSTR_CONFIG_MUTEX |当等待另一个 FILESTREAM 功能重新配置完成时出现。|
|FSTR_CONFIG_RWLOCK |当等待序列化对 FILESTREAM 配置参数的访问时出现。|
|FT_COMPROWSET_RWLOCK |全文正在等待片段元数据操作。 记录为仅供参考。 不提供支持。 不保证以后的兼容性。|
|FT_IFTS_RWLOCK |全文正在等待内部同步。 记录为仅供参考。 不提供支持。 不保证以后的兼容性。|
|FT_IFTS_SCHEDULER_IDLE_WAIT |全文计划程序睡眠等待类型。 计划程序空闲。|
|FT_IFTSHC_MUTEX |全文正在等待 fdhost 控制操作。 记录为仅供参考。 不提供支持。 不保证以后的兼容性。|
|FT_IFTSISM_MUTEX |全文正在等待通信操作。 记录为仅供参考。 不提供支持。 不保证以后的兼容性。|
|FT_MASTER_MERGE |全文正在等待主合并操作。 记录为仅供参考。 不提供支持。 不保证以后的兼容性。|
|FT_MASTER_MERGE_COORDINATOR |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|FT_METADATA_MUTEX |记录为仅供参考。 不提供支持。 不保证以后的兼容性。|
|FT_PROPERTYLIST_CACHE |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|FT_RESTART_CRAWL |在全文爬网需要从上一个已知可用点重新启动以便从暂时故障中恢复时出现。 等待使当前正在此总体中工作的工作线程任务完成或退出当前步骤。|
|FULLTEXT GATHERER |在同步全文操作期间发生。|
|GDMA_GET_RESOURCE_OWNER |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|GHOSTCLEANUP_UPDATE_STATS |TBD <br /> **适用范围**： [!INCLUDE[ssSQLv14_md](../../includes/sssqlv14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|GHOSTCLEANUPSYNCMGR |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|GLOBAL_QUERY_CANCEL |TBD <br /> **适用范围**： [!INCLUDE[ssSQLv14_md](../../includes/sssqlv14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|GLOBAL_QUERY_CLOSE |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|GLOBAL_QUERY_CONSUMER |TBD <br /> **适用范围**： [!INCLUDE[ssSQLv14_md](../../includes/sssqlv14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|GLOBAL_QUERY_PRODUCER |TBD <br /> **适用范围**： [!INCLUDE[ssSQLv14_md](../../includes/sssqlv14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|GLOBAL_TRAN_CREATE |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|GLOBAL_TRAN_UCS_SESSION |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|GUARDIAN |标识为仅供参考。 不提供支持。 不保证以后的兼容性。|
|HADR_AG_MUTEX |Alwayson DDL 语句或 Windows Server 故障转移群集命令正在等待对可用性组配置的独占读/写访问时发生。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_AR_CRITICAL_SECTION_ENTRY |Alwayson DDL 语句或 Windows Server 故障转移群集命令正在等待关联的可用性组的本地副本的运行时状态的独占读/写访问时发生。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_AR_MANAGER_MUTEX |在可用性副本关闭正在等待完成启动或可用性副本启动正在等待完成关闭时发生。 仅限内部使用。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_AR_UNLOAD_COMPLETED |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_ARCONTROLLER_NOTIFICATIONS_SUBSCRIBER_LIST |可用性副本事件（例如，状态更改或配置更改）的发布服务器正在等待对事件订阅服务器列表的独占的读/写访问。 仅限内部使用。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_BACKUP_BULK_LOCK |Alwayson 主数据库收到来自辅助数据库的备份请求并且正在等待后台线程完成对获取或释放 BulkOp 锁请求的处理。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_BACKUP_QUEUE |Alwayson 主数据库的备份后台线程正在等待来自辅助数据库的新工作请求。 （通常情况下，发生这种情况时主数据库正持有 BulkOp 日志并且正在等待辅助数据库，以指示主数据库可以释放锁）。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_CLUSAPI_CALL |SQL Server 线程正在等待从非抢先模式 （由 SQL Server 计划） 切换到抢先模式 （由操作系统计划），以便调用 Windows Server 故障转移群集 Api。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_COMPRESSED_CACHE_SYNC |等待用于避免发送到多个辅助数据库的日志块的冗余压缩的压缩后日志块缓存的访问权限。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_CONNECTIVITY_INFO |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_DATABASE_FLOW_CONTROL |在已达到排队消息的最大数目时正在等待消息发送到伙伴。 指示日志扫描的运行运行速度要快于网络发送速度。 仅当网络发送比预期要慢，这是一个问题。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_DATABASE_VERSIONING_STATE |在版本控制状态更改的 Always On 辅助数据库上发生。 此等待是针对内部数据结构，通常是很短且不会直接影响数据的访问权限。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_DATABASE_WAIT_FOR_RECOVERY |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_DATABASE_WAIT_FOR_RESTART |正在等待重新启动 Alwayson 可用性组控制下的数据库。 正常情况下，这不是客户问题由于此处需要进行等待。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_DATABASE_WAIT_FOR_TRANSITION_TO_VERSIONING |对象的查询在可读辅助数据库中的 Always On 可用性组行版本控制上阻止等待提交或回滚时启用辅助副本以便读取工作负荷未正在进行的所有事务时。 此等待类型保证在执行快照隔离下查询有行版本。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_DB_COMMAND |正在等待响应会话消息 （这需要从的另一端，使用 Alwayson 会话消息基础结构的显式响应）。 很多不同的消息类型使用此等待类型。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_DB_OP_COMPLETION_SYNC |正在等待响应会话消息 （这需要从的另一端，使用 Alwayson 会话消息基础结构的显式响应）。 很多不同的消息类型使用此等待类型。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_DB_OP_START_SYNC |Alwayson DDL 语句或 Windows Server 故障转移群集命令正在等待对可用性数据库及其运行时状态的序列化访问。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_DBR_SUBSCRIBER |可用性副本事件（例如，状态更改或配置更改）的发布服务器正在等待对与某一可用性数据库相对应的事件订阅服务器的运行时状态的独占读/写访问。 仅限内部使用。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_DBR_SUBSCRIBER_FILTER_LIST |可用性副本事件（例如，状态更改或配置更改）的发布服务器正在等待对与可用性数据库相对应的事件订阅服务器的列表的独占读/写访问。 仅限内部使用。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_DBSEEDING |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_DBSEEDING_LIST |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_DBSTATECHANGE_SYNC |并发控制等待更新数据库副本的内部状态。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_FABRIC_CALLBACK |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_FILESTREAM_BLOCK_FLUSH |FILESTREAM Alwayson 传输管理器正在等待，直到处理的日志块的完成。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_FILESTREAM_FILE_CLOSE |FILESTREAM Alwayson 传输管理器正在等待，直到下一步的 FILESTREAM 文件得到处理并且其处理结束。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_FILESTREAM_FILE_REQUEST |Always On 辅助副本正在等待主副本将发送所有请求的 FILESTREAM 文件中撤消。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_FILESTREAM_IOMGR |FILESTREAM Alwayson 传输管理器正在等待 R/W 锁来保护 FILESTREAM 始终在 I/O 管理器启动或关机期间。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_FILESTREAM_IOMGR_IOCOMPLETION |文件流始终在 I/O 管理器正在等待 I/O 完成。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_FILESTREAM_MANAGER |FILESTREAM Alwayson 传输管理器正在等待 R/W 锁来保护 FILESTREAM Alwayson 传输管理器启动或关机期间。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_FILESTREAM_PREPROC |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_GROUP_COMMIT |事务提交处理正在等待允许组提交，以便可将多个提交日志记录放置于单个日志块中。 此等待是预期的情况的优化日志 I/O、 捕获和发送操作。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_LOGCAPTURE_SYNC |在创建或销毁扫描时围绕日志捕获或应用对象的并发控制。 这是伙伴更改状态或连接状态时预期的等待。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_LOGCAPTURE_WAIT |等待日志记录变得可用。 可在等待连接生成新的日志记录时或在读取未处于缓存中的记录时等待 I/O 完成时发生。 如果日志扫描到日志末尾赶上或正在从磁盘读取，这是预期的等待。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_LOGPROGRESS_SYNC |并发控制等待更新数据库副本的日志进度状态时。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_NOTIFICATION_DEQUEUE |处理 Windows Server 故障转移群集通知的后台任务正在等待下一个通知。 仅限内部使用。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_NOTIFICATION_WORKER_EXCLUSIVE_ACCESS |Always On 可用性副本管理器正在等待处理 Windows Server 故障转移群集通知的后台任务的运行时状态的序列化访问。 仅限内部使用。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_NOTIFICATION_WORKER_STARTUP_SYNC |后台任务正在等待处理 Windows Server 故障转移群集通知的后台任务完成启动。 仅限内部使用。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_NOTIFICATION_WORKER_TERMINATION_SYNC |后台任务正在等待处理 Windows Server 故障转移群集通知的后台任务终止。 仅限内部使用。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_PARTNER_SYNC |对伙伴列表的并发控制等待。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_READ_ALL_NETWORKS |等待获取对 WSFC 网络列表的读取或写入访问。 仅限内部使用。 请注意： 引擎保存动态管理视图 （如 sys.dm_hadr_cluster_networks) 中使用的 WSFC 网络列表，或若要验证始终在 TRANSACT-SQL 语句引用 WSFC 网络信息。 此列表会更新在引擎启动时，WSFC 相关通知和内部 Alwayson 重新启动 （例如，丢失和重新获取 WSFC 仲裁）。 在该列表中的更新正在进行时，任务通常会被阻止。 、 <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_RECOVERY_WAIT_FOR_CONNECTION |正在等待辅助数据库在运行恢复之前连接到主数据库。 这是建立速度比较慢连接到主副本是否可以延长的预期的等待。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_RECOVERY_WAIT_FOR_UNDO |数据库恢复正在等待辅助数据库完成恢复和初始化阶段以便恢复到主数据库的公共日志点。 故障转移后的预期的等待。撤消可以通过 Windows 系统监视器 (perfmon.exe) 和动态管理视图中跟踪进度。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_REPLICAINFO_SYNC |等待并发控制更新当前副本状态。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_SEEDING_CANCELLATION |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_SEEDING_FILE_LIST |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_SEEDING_LIMIT_BACKUPS |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_SEEDING_SYNC_COMPLETION |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_SEEDING_TIMEOUT_TASK |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_SEEDING_WAIT_FOR_COMPLETION |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_SYNC_COMMIT |正在等待针对同步辅助数据库的事务提交处理来强制写入日志。 事务延迟性能计数器也会反映这一等待。 此等待类型应同步的可用性组，并指示发送、 写入和确认日志到辅助数据库的时间。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_SYNCHRONIZING_THROTTLE |正在等待事务提交处理允许同步的辅助数据库几乎与日志的主结尾保持同步，以便转换到同步的状态。 当辅助数据库几乎保持同步时，这是预期的等待。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_TDS_LISTENER_SYNC |内部 Alwayson 系统或 WSFC 群集将请求启动或停止侦听器。 对此请求的处理始终是异步的，并且存在删除冗余请求的机制。 还存在此进程由于配置更改而挂起的时刻。 与此侦听器同步机制相关的所有等待都使用此等待类型。 仅限内部使用。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_TDS_LISTENER_SYNC_PROCESSING |需要启动和/或停止 anavailability 组侦听器的 Alwayson Transact-SQL 语句的末尾使用。 启动/停止操作异步完成，因为用户线程将阻塞，直到已知侦听器的情况下使用此等待类型。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_THROTTLE_LOG_RATE_GOVERNOR |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_THROTTLE_LOG_RATE_LOG_SIZE |TBD <br /> **适用范围**： [!INCLUDE[ssSQLv14_md](../../includes/sssqlv14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_THROTTLE_LOG_RATE_SEEDING |TBD <br /> **适用范围**： [!INCLUDE[ssSQLv14_md](../../includes/sssqlv14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_THROTTLE_LOG_RATE_SEND_RECV_QUEUE_SIZE |TBD <br /> **适用范围**： [!INCLUDE[ssSQLv14_md](../../includes/sssqlv14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_TIMER_TASK |正在等待获取计时器任务对象上的锁，并且还可用于正在执行工作的时间之间的实际等待。 例如，为运行一次执行之后, 每隔 10 秒的任务，Always On 可用性组等待约 10 秒重新计划任务，并等待是为了让。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_TRANSPORT_DBRLIST |正在等待访问传输层的数据库副本列表。 用于授予对其访问权限的自旋锁。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_TRANSPORT_FLOW_CONTROL |等待未完成未确认 Always On 消息的数量超出时流控制阈值。 这是基于可用性副本到副本 （而不是以数据库到数据库为单位）。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_TRANSPORT_SESSION |Always On 可用性组正在等待更改或访问基础传输状态时。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_WORK_POOL |Always On 可用性组后台工作任务对象上的并发控制等待。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_WORK_QUEUE |Always On 可用性组后台工作线程等待新的工作分配。 就绪工作线程等待新工作，这是正常状态时，此设置的预期的等待。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HADR_XRF_STACK_ACCESS |访问 （查找、 添加和删除） Alwayson 可用性数据库的扩展的恢复分叉堆栈。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HCCO_CACHE |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HK_RESTORE_FILEMAP |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HKCS_PARALLEL_MIGRATION |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HKCS_PARALLEL_RECOVERY |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HTBUILD |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HTDELETE |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HTMEMO |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HTREINIT |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HTREPARTITION |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|HTTP_ENUMERATION |在启动时出现，以枚举 HTTP 端点以启动 HTTP。|
|HTTP_START |当连接正在等待 HTTP 完成初始化时出现。|
|HTTP_STORAGE_CONNECTION |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|IMPPROV_IOWAIT |SQL Server 等待 bulkload I/O 完成时发生。|
|INSTANCE_LOG_RATE_GOVERNOR |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|INTERNAL_TESTING |标识为仅供参考。 不提供支持。 不保证以后的兼容性。|
|IO_AUDIT_MUTEX |在跟踪事件缓冲区同步期间出现。|
|IO_COMPLETION |在等待 I/O 操作完成时出现。 通常，该等待类型表示非数据页 I/O。 数据页 I/O 完成等待显示为 PAGEIOLATCH\_ \*等待。|
|IO_QUEUE_LIMIT |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|IO_RETRY |当 I/O 操作（例如读取磁盘或写入磁盘）由于资源不足而失败，然后重试时出现。|
|IOAFF_RANGE_QUEUE |标识为仅供参考。 不提供支持。 不保证以后的兼容性。|
|KSOURCE_WAKEUP |在等待来自服务控制管理器的请求期间由服务控制任务使用。 可能会出现长时间等待，这并不指示出现问题。|
|KTM_ENLISTMENT |标识为仅供参考。 不提供支持。 不保证以后的兼容性。|
|KTM_RECOVERY_MANAGER |标识为仅供参考。 不提供支持。 不保证以后的兼容性。|
|KTM_RECOVERY_RESOLUTION |标识为仅供参考。 不提供支持。 不保证以后的兼容性。|
|LATCH_DT |等待 DT（破坏）闩锁时出现。 它不包括缓冲区闩锁或事务标记闩锁。 闩锁的列表\_\*等待 sys.dm_os_latch_stats 中提供了。 请注意，sys.dm_os_latch_stats 将 LATCH_NL、LATCH_SH、LATCH_UP、LATCH_EX 以及 LATCH_DT 等待分到一组。|
|LATCH_EX |等待 EX（排他）闩锁时出现。 它不包括缓冲区闩锁或事务标记闩锁。 闩锁的列表\_\*等待 sys.dm_os_latch_stats 中提供了。 请注意，sys.dm_os_latch_stats 将 LATCH_NL、LATCH_SH、LATCH_UP、LATCH_EX 以及 LATCH_DT 等待分到一组。|
|LATCH_KP |等待 KP（保持）闩锁时出现。 它不包括缓冲区闩锁或事务标记闩锁。 闩锁的列表\_\*等待 sys.dm_os_latch_stats 中提供了。 请注意，sys.dm_os_latch_stats 将 LATCH_NL、LATCH_SH、LATCH_UP、LATCH_EX 以及 LATCH_DT 等待分到一组。|
|LATCH_NL |标识为仅供参考。 不提供支持。 不保证以后的兼容性。|
|LATCH_SH |等待 SH（共享）闩锁时出现。 它不包括缓冲区闩锁或事务标记闩锁。 闩锁的列表\_\*等待 sys.dm_os_latch_stats 中提供了。 请注意，sys.dm_os_latch_stats 将 LATCH_NL、LATCH_SH、LATCH_UP、LATCH_EX 以及 LATCH_DT 等待分到一组。|
|LATCH_UP |等待 UP（更新）闩锁时出现。 它不包括缓冲区闩锁或事务标记闩锁。 闩锁的列表\_\*等待 sys.dm_os_latch_stats 中提供了。 请注意，sys.dm_os_latch_stats 将 LATCH_NL、LATCH_SH、LATCH_UP、LATCH_EX 以及 LATCH_DT 等待分到一组。|
|LAZYWRITER_SLEEP |当惰性编写器被挂起时出现。 正在等待的后台任务所用时间的度量值。 在查找用户阻隔点所时不要考虑该状态。|
|LCK_M_BU |当某任务正在等待获取大容量更新 (BU) 锁时出现。|
|LCK_M_BU_ABORT_BLOCKERS |在任务等待获取使用中止阻塞程序的大容量更新 (BU) 锁时发生。 （与 ALTER TABLE 和 ALTER INDEX 的低优先级等待选项。）， <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|LCK_M_BU_LOW_PRIORITY |在任务等待获取低优先级的大容量更新 (BU) 锁时发生。 （与 ALTER TABLE 和 ALTER INDEX 的低优先级等待选项。）， <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|LCK_M_IS |当某任务正在等待获取意向共享 (IS) 锁时出现。|
|LCK_M_IS_ABORT_BLOCKERS |在任务等待获取使用中止阻塞程序的意向共享 (IS) 锁时出现。 （与 ALTER TABLE 和 ALTER INDEX 的低优先级等待选项。）， <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|LCK_M_IS_LOW_PRIORITY |在任务等待获取低优先级的意向共享 (IS) 锁时出现。 （与 ALTER TABLE 和 ALTER INDEX 的低优先级等待选项。）， <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|LCK_M_IU |当某任务正在等待获取意向更新 (IU) 锁时出现。|
|LCK_M_IU_ABORT_BLOCKERS |在任务等待获取使用中止阻塞程序的意向更新 (IU) 锁时出现。 （与 ALTER TABLE 和 ALTER INDEX 的低优先级等待选项。）， <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|LCK_M_IU_LOW_PRIORITY |在任务等待获取低优先级的意向更新 (IU) 锁时出现。 （与 ALTER TABLE 和 ALTER INDEX 的低优先级等待选项。）， <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|LCK_M_IX |当某任务正在等待获取意向排他 (IX) 锁时出现。|
|LCK_M_IX_ABORT_BLOCKERS |在任务等待获取使用中止阻塞程序的意向排他 (IX) 锁时出现。 （与 ALTER TABLE 和 ALTER INDEX 的低优先级等待选项。）， <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|LCK_M_IX_LOW_PRIORITY |在任务等待获取低优先级的意向排他 (IX) 锁时发生。 （与 ALTER TABLE 和 ALTER INDEX 的低优先级等待选项。）， <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|LCK_M_RIn_NL |当某任务正在等待获取当前键值上的 NULL 锁以及当前键和上一个键之间的插入范围锁时出现。 键上的 NULL 锁是指立即释放的锁。|
|LCK_M_RIn_NL_ABORT_BLOCKERS |在任务等待获取当前键值上使用中止阻塞程序的 NULL 锁以及当前键和上一个键之间使用中止阻塞程序的插入范围锁时发生。 键上的 NULL 锁是指立即释放的锁。 （与 ALTER TABLE 和 ALTER INDEX 的低优先级等待选项。）， <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|LCK_M_RIn_NL_LOW_PRIORITY |在任务等待获取当前键值上低优先级的 NULL 锁以及当前键和上一个键之间低优先级的插入范围锁时发生。 键上的 NULL 锁是指立即释放的锁。 （与 ALTER TABLE 和 ALTER INDEX 的低优先级等待选项。）， <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|LCK_M_RIn_S |当某任务正在等待获取当前键值上的共享锁以及当前键和上一个键之间的插入范围锁时出现。|
|LCK_M_RIn_S_ABORT_BLOCKERS |在任务等待获取当前键值上使用中止阻塞程序的共享锁以及当前键和上一个键之间使用中止阻塞程序的插入范围锁时发生。 （与 ALTER TABLE 和 ALTER INDEX 的低优先级等待选项。）， <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|LCK_M_RIn_S_LOW_PRIORITY |在任务等待获取当前键值上低优先级的共享锁以及当前键和上一个键之间低优先级的插入范围锁时发生。 （与 ALTER TABLE 和 ALTER INDEX 的低优先级等待选项。）， <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|LCK_M_RIn_U |任务正在等待获取当前键值上的更新锁以及当前键和上一个键之间的插入范围锁。|
|LCK_M_RIn_U_ABORT_BLOCKERS |任务等待获取当前键值上使用中止阻塞程序的更新锁以及当前键和上一个键之间使用中止阻塞程序的插入范围锁。 （与 ALTER TABLE 和 ALTER INDEX 的低优先级等待选项。）， <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|LCK_M_RIn_U_LOW_PRIORITY |任务等待获取当前键值上低优先级的更新锁以及当前键和上一个键之间低优先级的插入范围锁。 （与 ALTER TABLE 和 ALTER INDEX 的低优先级等待选项。）， <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|LCK_M_RIn_X |当某任务正在等待获取当前键值上的排他锁以及当前键和上一个键之间的插入范围锁时出现。|
|LCK_M_RIn_X_ABORT_BLOCKERS |在任务等待获取当前键值上使用中止阻塞程序的排他锁以及当前键和上一个键之间使用中止阻塞程序的插入范围锁时发生。 （与 ALTER TABLE 和 ALTER INDEX 的低优先级等待选项。）， <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|LCK_M_RIn_X_LOW_PRIORITY |在任务等待获取当前键值上低优先级的排他锁以及当前键和上一个键之间低优先级的插入范围锁时发生。 （与 ALTER TABLE 和 ALTER INDEX 的低优先级等待选项。）， <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|LCK_M_RS_S |当某任务正在等待获取当前键值上的共享锁以及当前键和上一个键之间的共享范围锁时出现。|
|LCK_M_RS_S_ABORT_BLOCKERS |在任务等待获取当前键值上使用中止阻塞程序的共享锁以及当前键和上一个键之间使用中止阻塞程序的共享范围锁时发生。 （与 ALTER TABLE 和 ALTER INDEX 的低优先级等待选项。）， <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|LCK_M_RS_S_LOW_PRIORITY |在任务等待获取当前键值上低优先级的共享锁以及当前键和上一个键之间低优先级的共享范围锁时发生。 （与 ALTER TABLE 和 ALTER INDEX 的低优先级等待选项。）， <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|LCK_M_RS_U |当某任务正在等待获取当前键值上的更新锁以及当前键和上一个键之间的更新范围锁时出现。|
|LCK_M_RS_U_ABORT_BLOCKERS |在任务等待获取当前键值上使用中止阻塞程序的更新锁以及当前键和上一个键之间使用中止阻塞程序的更新范围锁时发生。 （与 ALTER TABLE 和 ALTER INDEX 的低优先级等待选项。）， <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|LCK_M_RS_U_LOW_PRIORITY |在任务等待获取当前键值上低优先级的更新锁以及当前键和上一个键之间低优先级的更新范围锁时发生。 （与 ALTER TABLE 和 ALTER INDEX 的低优先级等待选项。）， <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|LCK_M_RX_S |当某任务正在等待获取当前键值上的共享锁以及当前键和上一个键之间的排他范围锁时出现。|
|LCK_M_RX_S_ABORT_BLOCKERS |在任务等待获取当前键值上使用中止阻塞程序的共享锁以及当前键和上一个键之间使用中止阻塞程序的排他范围锁时发生。 （与 ALTER TABLE 和 ALTER INDEX 的低优先级等待选项。）， <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|LCK_M_RX_S_LOW_PRIORITY |在任务等待获取当前键值上低优先级的共享锁以及当前键和上一个键之间低优先级的排他范围锁时发生。 （与 ALTER TABLE 和 ALTER INDEX 的低优先级等待选项。）， <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|LCK_M_RX_U |当某任务正在等待获取当前键值上的更新锁以及当前键和上一个键之间的排他范围锁时出现。|
|LCK_M_RX_U_ABORT_BLOCKERS |在任务等待获取当前键值上使用中止阻塞程序的更新锁以及当前键和上一个键之间使用中止阻塞程序的排他范围锁时发生。 （与 ALTER TABLE 和 ALTER INDEX 的低优先级等待选项。）， <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|LCK_M_RX_U_LOW_PRIORITY |在任务等待获取当前键值上低优先级的更新锁以及当前键和上一个键之间低优先级的排他范围锁时发生。 （与 ALTER TABLE 和 ALTER INDEX 的低优先级等待选项。）， <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|LCK_M_RX_X |当某任务正在等待获取当前键值上的排他锁以及当前键和上一个键之间的排他范围锁时出现。|
|LCK_M_RX_X_ABORT_BLOCKERS |在任务等待获取当前键值上使用中止阻塞程序的排他锁以及当前键和上一个键之间使用中止阻塞程序的排他范围锁时发生。 （与 ALTER TABLE 和 ALTER INDEX 的低优先级等待选项。）， <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|LCK_M_RX_X_LOW_PRIORITY |在任务等待获取当前键值上低优先级的排他锁以及当前键和上一个键之间低优先级的排他范围锁时发生。 （与 ALTER TABLE 和 ALTER INDEX 的低优先级等待选项。）， <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|LCK_M_S |当某任务正在等待获取共享锁时出现。|
|LCK_M_S_ABORT_BLOCKERS |在任务等待获取使用中止阻塞程序的共享锁时发生。 （与 ALTER TABLE 和 ALTER INDEX 的低优先级等待选项。）， <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|LCK_M_S_LOW_PRIORITY |在任务等待获取低优先级的共享锁时发生。 （与 ALTER TABLE 和 ALTER INDEX 的低优先级等待选项。）， <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|LCK_M_SCH_M |当某任务正在等待获取架构修改锁时出现。|
|LCK_M_SCH_M_ABORT_BLOCKERS |在任务等待获取使用中止阻塞程序的架构修改锁时发生。 （与 ALTER TABLE 和 ALTER INDEX 的低优先级等待选项。）， <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|LCK_M_SCH_M_LOW_PRIORITY |在任务等待获取低优先级的架构修改锁时发生。 （与 ALTER TABLE 和 ALTER INDEX 的低优先级等待选项。）， <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|LCK_M_SCH_S |当某任务正在等待获取架构共享锁时出现。|
|LCK_M_SCH_S_ABORT_BLOCKERS |在任务等待获取使用中止阻塞程序的架构共享锁时发生。 （与 ALTER TABLE 和 ALTER INDEX 的低优先级等待选项。）， <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|LCK_M_SCH_S_LOW_PRIORITY |在任务等待获取低优先级的架构共享锁时发生。 （与 ALTER TABLE 和 ALTER INDEX 的低优先级等待选项。）， <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|LCK_M_SIU |当某任务正在等待获取共享意向更新锁时出现。|
|LCK_M_SIU_ABORT_BLOCKERS |在任务等待获取具有中止阻塞程序的共享意向更新锁时发生。 （与 ALTER TABLE 和 ALTER INDEX 的低优先级等待选项。）， <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|LCK_M_SIU_LOW_PRIORITY |在任务等待获取低优先级的共享意向更新锁时发生。 （与 ALTER TABLE 和 ALTER INDEX 的低优先级等待选项。）， <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|LCK_M_SIX |当某任务正在等待获取共享意向排他锁时出现。|
|LCK_M_SIX_ABORT_BLOCKERS |在任务等待获取使用中止阻塞程序的共享意向排他锁时发生。 （与 ALTER TABLE 和 ALTER INDEX 的低优先级等待选项。）， <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|LCK_M_SIX_LOW_PRIORITY |在任务等待获取低优先级的意向排他共享锁时发生。 （与 ALTER TABLE 和 ALTER INDEX 的低优先级等待选项。）， <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|LCK_M_U |当某任务正在等待获取更新锁时出现。|
|LCK_M_U_ABORT_BLOCKERS |在任务等待获取使用中止阻塞程序的更新锁时发生。 （与 ALTER TABLE 和 ALTER INDEX 的低优先级等待选项。）， <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|LCK_M_U_LOW_PRIORITY |在任务等待获取低优先级的更新锁时发生。 （与 ALTER TABLE 和 ALTER INDEX 的低优先级等待选项。）， <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|LCK_M_UIX |当某任务正在等待获取更新意向排他锁时出现。|
|LCK_M_UIX_ABORT_BLOCKERS |在任务等待获取使用中止阻塞程序的意向排他更新锁时发生。 （与 ALTER TABLE 和 ALTER INDEX 的低优先级等待选项。）， <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|LCK_M_UIX_LOW_PRIORITY |在任务等待获取低优先级的意向排他更新锁时发生。 （与 ALTER TABLE 和 ALTER INDEX 的低优先级等待选项。）， <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|LCK_M_X |当某任务正在等待获取排他锁时出现。|
|LCK_M_X_ABORT_BLOCKERS |在任务等待获取使用中止阻塞程序的排他锁时发生。 （与 ALTER TABLE 和 ALTER INDEX 的低优先级等待选项。）， <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|LCK_M_X_LOW_PRIORITY |在任务等待获取低优先级的排他锁时发生。 （与 ALTER TABLE 和 ALTER INDEX 的低优先级等待选项。）， <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|LOG_POOL_SCAN |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|LOG_RATE_GOVERNOR |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|LOGBUFFER |当某任务正在等待日志缓冲区的空间以存储日志记录时出现。 连续的高值可能指示日志设备无法跟上服务器生成的日志量。|
|LOGCAPTURE_LOGPOOLTRUNCPOINT |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|LOGGENERATION |标识为仅供参考。 不提供支持。 不保证以后的兼容性。|
|LOGMGR |在数据库关闭过程中，当某任务正在等待任何未完成的日志 I/O 在关闭日志之前完成时出现。|
|LOGMGR_FLUSH |标识为仅供参考。 不提供支持。 不保证以后的兼容性。|
|LOGMGR_PMM_LOG |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|LOGMGR_QUEUE |在日志编写器任务等待工作请求时出现。|
|LOGMGR_RESERVE_APPEND |当某任务正在等待查看日志截断是否能释放日志空间以使该任务能写入新的日志记录时出现。 请考虑为受影响的数据库增加日志文件的大小以减少该等待时间。|
|LOGPOOL_CACHESIZE |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|LOGPOOL_CONSUMER |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|LOGPOOL_CONSUMERSET |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|LOGPOOL_FREEPOOLS |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|LOGPOOL_MGRSET |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|LOGPOOL_REPLACEMENTSET |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|LOGPOOLREFCOUNTEDOBJECT_REFDONE |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|LOWFAIL_MEMMGR_QUEUE |在等待可用内存期间出现。|
|MD_AGENT_YIELD |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|MD_LAZYCACHE_RWLOCK |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|MEMORY_ALLOCATION_EXT |从内部 SQL Server 内存池或操作系统分配内存时出现。， <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|MEMORY_GRANT_UPDATE |TBD <br /> **适用范围**： [!INCLUDE[ssSQLv14_md](../../includes/sssqlv14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|METADATA_LAZYCACHE_RWLOCK |TBD <br /> **适用于**:[!INCLUDE[ssKilimanjaro_md](../../includes/sskilimanjaro-md.md)]仅。 |
|MIGRATIONBUFFER |TBD <br /> **适用范围**： [!INCLUDE[ssSQLv14_md](../../includes/sssqlv14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|MISCELLANEOUS |标识为仅供参考。 不提供支持。 不保证以后的兼容性。|
|MISCELLANEOUS |标识为仅供参考。 不提供支持。 不保证以后的兼容性。|
|MSQL_DQ |当某任务正在等待分布式查询操作完成时出现。 它用于检测潜在的多个活动的结果集 (MARS) 应用程序死锁。 该等待将在分布式查询调用完成时结束。|
|MSQL_XACT_MGR_MUTEX |当某任务正在等待获取会话事务管理器的所有权以执行会话级别事务操作时出现。|
|MSQL_XACT_MUTEX |在事务使用同步期间出现。 请求必须先获取互斥体才可以使用事务。|
|MSQL_XP |当某任务正在等待扩展存储过程结束时出现。 SQL Server 使用该等待状态检测潜在的 MARS 应用程序死锁。 该等待将在扩展存储过程调用结束时停止。|
|MSSEARCH |在全文搜索调用期间出现。 该等待在全文操作完成时结束。 它不指示争用，而指示全文操作的持续时间。|
|NET_WAITFOR_PACKET |在网络读取过程中连接正在等待网络数据包时出现。|
|NETWORKSXMLMGRLOAD |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|NODE_CACHE_MUTEX |TBD|
|OLEDB |SQL Server 调用 SQL Server Native Client OLE DB 访问接口时发生。 该等待类型不用于同步。 而是用于指示调用 OLE DB 访问接口的持续时间。|
|ONDEMAND_TASK_QUEUE |在后台任务等待高优先级系统任务请求时出现。 长时间的等待指示一直没有要处理的高优先级请求，不应引起关注。|
|PAGEIOLATCH_DT |在任务等待 I/O 请求中缓冲区的闩锁时发生。 闩锁请求处于“破坏”模式。 长时间的等待可能指示磁盘子系统出现问题。|
|PAGEIOLATCH_EX |在任务等待 I/O 请求中缓冲区的闩锁时发生。 闩锁请求处于“独占”模式。 长时间的等待可能指示磁盘子系统出现问题。|
|PAGEIOLATCH_KP |在任务等待 I/O 请求中缓冲区的闩锁时发生。 闩锁请求处于“保持”模式。 长时间的等待可能指示磁盘子系统出现问题。|
|PAGEIOLATCH_NL |标识为仅供参考。 不提供支持。 不保证以后的兼容性。|
|PAGEIOLATCH_SH |在任务等待 I/O 请求中缓冲区的闩锁时发生。 闩锁请求处于“共享”模式。 长时间的等待可能指示磁盘子系统出现问题。|
|PAGEIOLATCH_UP |在任务等待 I/O 请求中缓冲区的闩锁时发生。 闩锁请求处于“更新”模式。 长时间的等待可能指示磁盘子系统出现问题。|
|PAGELATCH_DT |在任务等待不处于 I/O 请求中的缓冲区闩锁时发生。 闩锁请求处于“破坏”模式。|
|PAGELATCH_EX |在任务等待不处于 I/O 请求中的缓冲区闩锁时发生。 闩锁请求处于“独占”模式。|
|PAGELATCH_KP |在任务等待不处于 I/O 请求中的缓冲区闩锁时发生。 闩锁请求处于“保持”模式。|
|PAGELATCH_NL |标识为仅供参考。 不提供支持。 不保证以后的兼容性。|
|PAGELATCH_SH |在任务等待不处于 I/O 请求中的缓冲区闩锁时发生。 闩锁请求处于“共享”模式。|
|PAGELATCH_UP |在任务等待不处于 I/O 请求中的缓冲区闩锁时发生。 闩锁请求处于“更新”模式。|
|PARALLEL_BACKUP_QUEUE |在序列化由 RESTORE HEADERONLY、RESTORE FILELISTONLY 或 RESTORE LABELONLY 生成的输出时出现。|
|PARALLEL_REDO_DRAIN_WORKER |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|PARALLEL_REDO_FLOW_CONTROL |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|PARALLEL_REDO_LOG_CACHE |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|PARALLEL_REDO_TRAN_LIST |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|PARALLEL_REDO_TRAN_TURN |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|PARALLEL_REDO_WORKER_SYNC |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|PARALLEL_REDO_WORKER_WAIT_WORK |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|PERFORMANCE_COUNTERS_RWLOCK |TBD|
|PHYSICAL_SEEDING_DMV |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|POOL_LOG_RATE_GOVERNOR |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|PREEMPTIVE_ABR |标识为仅供参考。 不提供支持。 不保证以后的兼容性。|
|PREEMPTIVE_AUDIT_ACCESS_EVENTLOG |在 [!INCLUDE[ssNoVersion_md](../../includes/ssnoversion-md.md)] 操作系统 (SQLOS) 计划程序切换到抢先模式时发生，以便将审核事件写入 Windows 事件日志。 <br /> **适用于**:[!INCLUDE[ssKilimanjaro_md](../../includes/sskilimanjaro-md.md)]仅。 |
|PREEMPTIVE_AUDIT_ACCESS_SECLOG |在 SQLOS 计划程序切换到抢先模式时发生，以便将审核事件写入 Windows 安全日志。 <br /> **适用于**:[!INCLUDE[ssKilimanjaro_md](../../includes/sskilimanjaro-md.md)]仅。 |
|PREEMPTIVE_CLOSEBACKUPMEDIA |在 SQLOS 计划程序切换到抢先模式时发生，以便关闭备份介质。|
|PREEMPTIVE_CLOSEBACKUPTAPE |在 SQLOS 计划程序切换到抢先模式时发生，以便关闭磁带备份设备。|
|PREEMPTIVE_CLOSEBACKUPVDIDEVICE |在 SQLOS 计划程序切换到抢先模式时发生，以便关闭虚拟备份设备。|
|PREEMPTIVE_CLUSAPI_CLUSTERRESOURCECONTROL |在 SQLOS 计划程序切换到抢先模式时发生，以便执行故障转移群集操作。|
|PREEMPTIVE_COM_COCREATEINSTANCE |在 SQLOS 计划程序切换到抢先模式时发生，以便创建 COM 对象。|
|PREEMPTIVE_COM_COGETCLASSOBJECT |TBD|
|PREEMPTIVE_COM_CREATEACCESSOR |TBD|
|PREEMPTIVE_COM_DELETEROWS |TBD|
|PREEMPTIVE_COM_GETCOMMANDTEXT |TBD|
|PREEMPTIVE_COM_GETDATA |TBD|
|PREEMPTIVE_COM_GETNEXTROWS |TBD|
|PREEMPTIVE_COM_GETRESULT |TBD|
|PREEMPTIVE_COM_GETROWSBYBOOKMARK |TBD|
|PREEMPTIVE_COM_LBFLUSH |TBD|
|PREEMPTIVE_COM_LBLOCKREGION |TBD|
|PREEMPTIVE_COM_LBREADAT |TBD|
|PREEMPTIVE_COM_LBSETSIZE |TBD|
|PREEMPTIVE_COM_LBSTAT |TBD|
|PREEMPTIVE_COM_LBUNLOCKREGION |TBD|
|PREEMPTIVE_COM_LBWRITEAT |TBD|
|PREEMPTIVE_COM_QUERYINTERFACE |TBD|
|PREEMPTIVE_COM_RELEASE |TBD|
|PREEMPTIVE_COM_RELEASEACCESSOR |TBD|
|PREEMPTIVE_COM_RELEASEROWS |TBD|
|PREEMPTIVE_COM_RELEASESESSION |TBD|
|PREEMPTIVE_COM_RESTARTPOSITION |TBD|
|PREEMPTIVE_COM_SEQSTRMREAD |TBD|
|PREEMPTIVE_COM_SEQSTRMREADANDWRITE |TBD|
|PREEMPTIVE_COM_SETDATAFAILURE |TBD|
|PREEMPTIVE_COM_SETPARAMETERINFO |TBD|
|PREEMPTIVE_COM_SETPARAMETERPROPERTIES |TBD|
|PREEMPTIVE_COM_STRMLOCKREGION |TBD|
|PREEMPTIVE_COM_STRMSEEKANDREAD |TBD|
|PREEMPTIVE_COM_STRMSEEKANDWRITE |TBD|
|PREEMPTIVE_COM_STRMSETSIZE |TBD|
|PREEMPTIVE_COM_STRMSTAT |TBD|
|PREEMPTIVE_COM_STRMUNLOCKREGION |TBD|
|PREEMPTIVE_CONSOLEWRITE |TBD|
|PREEMPTIVE_CREATEPARAM |TBD|
|PREEMPTIVE_DEBUG |TBD|
|PREEMPTIVE_DFSADDLINK |TBD|
|PREEMPTIVE_DFSLINKEXISTCHECK |TBD|
|PREEMPTIVE_DFSLINKHEALTHCHECK |TBD|
|PREEMPTIVE_DFSREMOVELINK |TBD|
|PREEMPTIVE_DFSREMOVEROOT |TBD|
|PREEMPTIVE_DFSROOTFOLDERCHECK |TBD|
|PREEMPTIVE_DFSROOTINIT |TBD|
|PREEMPTIVE_DFSROOTSHARECHECK |TBD|
|PREEMPTIVE_DTC_ABORT |TBD|
|PREEMPTIVE_DTC_ABORTREQUESTDONE |TBD|
|PREEMPTIVE_DTC_BEGINTRANSACTION |TBD|
|PREEMPTIVE_DTC_COMMITREQUESTDONE |TBD|
|PREEMPTIVE_DTC_ENLIST |TBD|
|PREEMPTIVE_DTC_PREPAREREQUESTDONE |TBD|
|PREEMPTIVE_FILESIZEGET |TBD|
|PREEMPTIVE_FSAOLEDB_ABORTTRANSACTION |TBD|
|PREEMPTIVE_FSAOLEDB_COMMITTRANSACTION |TBD|
|PREEMPTIVE_FSAOLEDB_STARTTRANSACTION |TBD|
|PREEMPTIVE_FSRECOVER_UNCONDITIONALUNDO |TBD|
|PREEMPTIVE_GETRMINFO |TBD|
|PREEMPTIVE_HADR_LEASE_MECHANISM |针对 CSS 诊断的 alwayson 可用性组租约管理器。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|PREEMPTIVE_HTTP_EVENT_WAIT |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|PREEMPTIVE_HTTP_REQUEST |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|PREEMPTIVE_LOCKMONITOR |TBD|
|PREEMPTIVE_MSS_RELEASE |TBD|
|PREEMPTIVE_ODBCOPS |TBD|
|PREEMPTIVE_OLE_UNINIT |TBD|
|PREEMPTIVE_OLEDB_ABORTORCOMMITTRAN |TBD|
|PREEMPTIVE_OLEDB_ABORTTRAN |TBD|
|PREEMPTIVE_OLEDB_GETDATASOURCE |TBD|
|PREEMPTIVE_OLEDB_GETLITERALINFO |TBD|
|PREEMPTIVE_OLEDB_GETPROPERTIES |TBD|
|PREEMPTIVE_OLEDB_GETPROPERTYINFO |TBD|
|PREEMPTIVE_OLEDB_GETSCHEMALOCK |TBD|
|PREEMPTIVE_OLEDB_JOINTRANSACTION |TBD|
|PREEMPTIVE_OLEDB_RELEASE |TBD|
|PREEMPTIVE_OLEDB_SETPROPERTIES |TBD|
|PREEMPTIVE_OLEDBOPS |TBD|
|PREEMPTIVE_OS_ACCEPTSECURITYCONTEXT |TBD|
|PREEMPTIVE_OS_ACQUIRECREDENTIALSHANDLE |TBD|
|PREEMPTIVE_OS_AUTHENTICATIONOPS |TBD|
|PREEMPTIVE_OS_AUTHORIZATIONOPS |TBD|
|PREEMPTIVE_OS_AUTHZGETINFORMATIONFROMCONTEXT |TBD|
|PREEMPTIVE_OS_AUTHZINITIALIZECONTEXTFROMSID |TBD|
|PREEMPTIVE_OS_AUTHZINITIALIZERESOURCEMANAGER |TBD|
|PREEMPTIVE_OS_BACKUPREAD |TBD|
|PREEMPTIVE_OS_CLOSEHANDLE |TBD|
|PREEMPTIVE_OS_CLUSTEROPS |TBD|
|PREEMPTIVE_OS_COMOPS |TBD|
|PREEMPTIVE_OS_COMPLETEAUTHTOKEN |TBD|
|PREEMPTIVE_OS_COPYFILE |TBD|
|PREEMPTIVE_OS_CREATEDIRECTORY |TBD|
|PREEMPTIVE_OS_CREATEFILE |TBD|
|PREEMPTIVE_OS_CRYPTACQUIRECONTEXT |TBD|
|PREEMPTIVE_OS_CRYPTIMPORTKEY |TBD|
|PREEMPTIVE_OS_CRYPTOPS |TBD|
|PREEMPTIVE_OS_DECRYPTMESSAGE |TBD|
|PREEMPTIVE_OS_DELETEFILE |TBD|
|PREEMPTIVE_OS_DELETESECURITYCONTEXT |TBD|
|PREEMPTIVE_OS_DEVICEIOCONTROL |TBD|
|PREEMPTIVE_OS_DEVICEOPS |TBD|
|PREEMPTIVE_OS_DIRSVC_NETWORKOPS |TBD|
|PREEMPTIVE_OS_DISCONNECTNAMEDPIPE |TBD|
|PREEMPTIVE_OS_DOMAINSERVICESOPS |TBD|
|PREEMPTIVE_OS_DSGETDCNAME |TBD|
|PREEMPTIVE_OS_DTCOPS |TBD|
|PREEMPTIVE_OS_ENCRYPTMESSAGE |TBD|
|PREEMPTIVE_OS_FILEOPS |TBD|
|PREEMPTIVE_OS_FINDFILE |TBD|
|PREEMPTIVE_OS_FLUSHFILEBUFFERS |TBD|
|PREEMPTIVE_OS_FORMATMESSAGE |TBD|
|PREEMPTIVE_OS_FREECREDENTIALSHANDLE |TBD|
|PREEMPTIVE_OS_FREELIBRARY |TBD|
|PREEMPTIVE_OS_GENERICOPS |TBD|
|PREEMPTIVE_OS_GETADDRINFO |TBD|
|PREEMPTIVE_OS_GETCOMPRESSEDFILESIZE |TBD|
|PREEMPTIVE_OS_GETDISKFREESPACE |TBD|
|PREEMPTIVE_OS_GETFILEATTRIBUTES |TBD|
|PREEMPTIVE_OS_GETFILESIZE |TBD|
|PREEMPTIVE_OS_GETFINALFILEPATHBYHANDLE |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|PREEMPTIVE_OS_GETLONGPATHNAME |TBD|
|PREEMPTIVE_OS_GETPROCADDRESS |TBD|
|PREEMPTIVE_OS_GETVOLUMENAMEFORVOLUMEMOUNTPOINT |TBD|
|PREEMPTIVE_OS_GETVOLUMEPATHNAME |TBD|
|PREEMPTIVE_OS_INITIALIZESECURITYCONTEXT |TBD|
|PREEMPTIVE_OS_LIBRARYOPS |TBD|
|PREEMPTIVE_OS_LOADLIBRARY |TBD|
|PREEMPTIVE_OS_LOGONUSER |TBD|
|PREEMPTIVE_OS_LOOKUPACCOUNTSID |TBD|
|PREEMPTIVE_OS_MESSAGEQUEUEOPS |TBD|
|PREEMPTIVE_OS_MOVEFILE |TBD|
|PREEMPTIVE_OS_NETGROUPGETUSERS |TBD|
|PREEMPTIVE_OS_NETLOCALGROUPGETMEMBERS |TBD|
|PREEMPTIVE_OS_NETUSERGETGROUPS |TBD|
|PREEMPTIVE_OS_NETUSERGETLOCALGROUPS |TBD|
|PREEMPTIVE_OS_NETUSERMODALSGET |TBD|
|PREEMPTIVE_OS_NETVALIDATEPASSWORDPOLICY |TBD|
|PREEMPTIVE_OS_NETVALIDATEPASSWORDPOLICYFREE |TBD|
|PREEMPTIVE_OS_OPENDIRECTORY |TBD|
|PREEMPTIVE_OS_PDH_WMI_INIT |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|PREEMPTIVE_OS_PIPEOPS |TBD|
|PREEMPTIVE_OS_PROCESSOPS |TBD|
|PREEMPTIVE_OS_QUERYCONTEXTATTRIBUTES |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|PREEMPTIVE_OS_QUERYREGISTRY |TBD|
|PREEMPTIVE_OS_QUERYSECURITYCONTEXTTOKEN |TBD|
|PREEMPTIVE_OS_REMOVEDIRECTORY |TBD|
|PREEMPTIVE_OS_REPORTEVENT |TBD|
|PREEMPTIVE_OS_REVERTTOSELF |TBD|
|PREEMPTIVE_OS_RSFXDEVICEOPS |TBD|
|PREEMPTIVE_OS_SECURITYOPS |TBD|
|PREEMPTIVE_OS_SERVICEOPS |TBD|
|PREEMPTIVE_OS_SETENDOFFILE |TBD|
|PREEMPTIVE_OS_SETFILEPOINTER |TBD|
|PREEMPTIVE_OS_SETFILEVALIDDATA |TBD|
|PREEMPTIVE_OS_SETNAMEDSECURITYINFO |TBD|
|PREEMPTIVE_OS_SQLCLROPS |TBD|
|PREEMPTIVE_OS_SQMLAUNCH |TBD <br /> **适用范围**： [!INCLUDE[ssKilimanjaro_md](../../includes/sskilimanjaro-md.md)] 到 [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)]。 |
|PREEMPTIVE_OS_VERIFYSIGNATURE |TBD|
|PREEMPTIVE_OS_VERIFYTRUST |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|PREEMPTIVE_OS_VSSOPS |TBD|
|PREEMPTIVE_OS_WAITFORSINGLEOBJECT |TBD|
|PREEMPTIVE_OS_WINSOCKOPS |TBD|
|PREEMPTIVE_OS_WRITEFILE |TBD|
|PREEMPTIVE_OS_WRITEFILEGATHER |TBD|
|PREEMPTIVE_OS_WSASETLASTERROR |TBD|
|PREEMPTIVE_REENLIST |TBD|
|PREEMPTIVE_RESIZELOG |TBD|
|PREEMPTIVE_ROLLFORWARDREDO |TBD|
|PREEMPTIVE_ROLLFORWARDUNDO |TBD|
|PREEMPTIVE_SB_STOPENDPOINT |TBD|
|PREEMPTIVE_SERVER_STARTUP |TBD|
|PREEMPTIVE_SETRMINFO |TBD|
|PREEMPTIVE_SHAREDMEM_GETDATA |TBD|
|PREEMPTIVE_SNIOPEN |TBD|
|PREEMPTIVE_SOSHOST |TBD|
|PREEMPTIVE_SOSTESTING |标识为仅供参考。 不提供支持。 不保证以后的兼容性。|
|PREEMPTIVE_SP_SERVER_DIAGNOSTICS |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|PREEMPTIVE_STARTRM |TBD|
|PREEMPTIVE_STREAMFCB_CHECKPOINT |TBD|
|PREEMPTIVE_STREAMFCB_RECOVER |TBD|
|PREEMPTIVE_STRESSDRIVER |标识为仅供参考。 不提供支持。 不保证以后的兼容性。|
|PREEMPTIVE_TESTING |标识为仅供参考。 不提供支持。 不保证以后的兼容性。|
|PREEMPTIVE_TRANSIMPORT |TBD|
|PREEMPTIVE_UNMARSHALPROPAGATIONTOKEN |TBD|
|PREEMPTIVE_VSS_CREATESNAPSHOT |TBD|
|PREEMPTIVE_VSS_CREATEVOLUMESNAPSHOT |TBD|
|PREEMPTIVE_XE_CALLBACKEXECUTE |TBD|
|PREEMPTIVE_XE_CX_FILE_OPEN |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|PREEMPTIVE_XE_CX_HTTP_CALL |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|PREEMPTIVE_XE_DISPATCHER |TBD|
|PREEMPTIVE_XE_ENGINEINIT |TBD|
|PREEMPTIVE_XE_GETTARGETSTATE |TBD|
|PREEMPTIVE_XE_SESSIONCOMMIT |TBD|
|PREEMPTIVE_XE_TARGETFINALIZE |TBD|
|PREEMPTIVE_XE_TARGETINIT |TBD|
|PREEMPTIVE_XE_TIMERRUN |TBD|
|PREEMPTIVE_XETESTING |标识为仅供参考。 不提供支持。 不保证以后的兼容性。|
|PRINT_ROLLBACK_PROGRESS |用于等待用户进程在已通过 ALTER DATABASE 终止子句完成转换的数据库中结束。 有关详细信息，请参阅 ALTER DATABASE (Transact SQL)。|
|PRU_ROLLBACK_DEFERRED |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|PWAIT_ALL_COMPONENTS_INITIALIZED |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|PWAIT_COOP_SCAN |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|PWAIT_DIRECTLOGCONSUMER_GETNEXT |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|PWAIT_EVENT_SESSION_INIT_MUTEX |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|PWAIT_FABRIC_REPLICA_CONTROLLER_DATA_LOSS |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|PWAIT_HADR_ACTION_COMPLETED |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|PWAIT_HADR_CHANGE_NOTIFIER_TERMINATION_SYNC |后台任务正在等待终止接收 （通过轮询） 的后台任务时，会发生 Windows Server 故障转移群集通知。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|PWAIT_HADR_CLUSTER_INTEGRATION |追加、 替换和/或删除操作正在等待获取 Alwayson 内部列表 （例如网络、 网络地址或可用性组侦听器的列表） 上的写入锁。 内部使用 <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|PWAIT_HADR_FAILOVER_COMPLETED |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|PWAIT_HADR_JOIN |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|PWAIT_HADR_OFFLINE_COMPLETED |Alwayson 删除可用性组操作正在等待目标可用性组在销毁 Windows Server 故障转移群集对象之前进入脱机状态。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|PWAIT_HADR_ONLINE_COMPLETED |Alwayson 创建或故障转移可用性组操作正在等待目标可用性组联机。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|PWAIT_HADR_POST_ONLINE_COMPLETED |Alwayson 删除可用性组操作正在等待作为之前命令的一部分计划任何后台任务终止。 例如，可能有正在将可用性数据库转换为主要角色的后台任务。 DROP AVAILABILITY GROUP DDL 必须等待此后台任务终止，以免争用条件。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|PWAIT_HADR_SERVER_READY_CONNECTIONS |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|PWAIT_HADR_WORKITEM_COMPLETED |正在等待异步工作任务完成，这是线程执行的内部等待。 这是预期的等待，使用 CSS。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|PWAIT_HADRSIM |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|PWAIT_LOG_CONSOLIDATION_IO |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|PWAIT_LOG_CONSOLIDATION_POLL |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|PWAIT_MD_LOGIN_STATS |在登录统计信息的元数据内部同步期间出现。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|PWAIT_MD_RELATION_CACHE |在表或索引的元数据内部同步期间出现。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|PWAIT_MD_SERVER_CACHE |在链接服务器的元数据内部同步期间出现。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|PWAIT_MD_UPGRADE_CONFIG |升级服务器范围的配置中的内部同步期间出现。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|PWAIT_PREEMPTIVE_APP_USAGE_TIMER |TBD <br /> **适用范围**： [!INCLUDE[ssSQLv14_md](../../includes/sssqlv14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|PWAIT_PREEMPTIVE_AUDIT_ACCESS_WINDOWSLOG |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|PWAIT_QRY_BPMEMORY |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|PWAIT_REPLICA_ONLINE_INIT_MUTEX |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|PWAIT_RESOURCE_SEMAPHORE_FT_PARALLEL_QUERY_SYNC |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|PWAIT_SBS_FILE_OPERATION |TBD <br /> **适用范围**： [!INCLUDE[ssSQLv14_md](../../includes/sssqlv14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|PWAIT_XTP_FSSTORAGE_MAINTENANCE |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|PWAIT_XTP_HOST_STORAGE_WAIT |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|QDS_ASYNC_CHECK_CONSISTENCY_TASK |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|QDS_ASYNC_PERSIST_TASK |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|QDS_ASYNC_PERSIST_TASK_START |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|QDS_ASYNC_QUEUE |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|QDS_BCKG_TASK |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|QDS_BLOOM_FILTER |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|QDS_CLEANUP_STALE_QUERIES_TASK_MAIN_LOOP_SLEEP |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|QDS_CTXS |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|QDS_DB_DISK |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|QDS_DYN_VECTOR |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|QDS_EXCLUSIVE_ACCESS |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|QDS_HOST_INIT |TBD <br /> **适用范围**： [!INCLUDE[ssSQLv14_md](../../includes/sssqlv14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|QDS_LOADDB |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|QDS_PERSIST_TASK_MAIN_LOOP_SLEEP |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|QDS_QDS_CAPTURE_INIT |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|QDS_SHUTDOWN_QUEUE |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|QDS_STMT |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|QDS_STMT_DISK |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|QDS_TASK_SHUTDOWN |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|QDS_TASK_START |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|QE_WARN_LIST_SYNC |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|QPJOB_KILL |指示异步统计信息自动更新在开始运行时通过调用 KILL 命令而取消。 终止线程处于挂起状态，等待它开始侦听 KILL 命令。 正常情况下，该值不到一秒钟。|
|QPJOB_WAITFOR_ABORT |指示异步统计信息自动更新在运行时通过调用 KILL 命令而取消。 目前更新已完成，但是在终止线程消息协调完成之前一直于挂起状态。 这是一个普通而少见的状态，应当非常短暂。 正常情况下，该值不到一秒钟。|
|QRY_MEM_GRANT_INFO_MUTEX |当查询执行内存管理尝试控制对静态授予信息列表的访问时出现。 该状态列出当前已批准的内存请求以及正在等待的内存请求的有关信息。 该状态是一个简单的访问控制状态。 该状态始终不应当等待较长的时间。 如果未释放互斥体，则所有占用内存的新查询都将停止响应。|
|QRY_PARALLEL_THREAD_MUTEX |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|QRY_PROFILE_LIST_MUTEX |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|QUERY_ERRHDL_SERVICE_DONE |标识为仅供参考。 不提供支持。 <br /> **适用于**:[!INCLUDE[ssKilimanjaro_md](../../includes/sskilimanjaro-md.md)]仅。 |
|QUERY_WAIT_ERRHDL_SERVICE |标识为仅供参考。 不提供支持。 <br /> **适用于**:[!INCLUDE[ssKilimanjaro_md](../../includes/sskilimanjaro-md.md)]仅。 |
|QUERY_EXECUTION_INDEX_SORT_EVENT_OPEN |当脱机创建索引生成以并行方式运行，并且正在排序的不同工作线程同步访问排序文件时出现。|
|QUERY_NOTIFICATION_MGR_MUTEX |在查询通知管理器中的垃圾收集队列同步期间出现。|
|QUERY_NOTIFICATION_SUBSCRIPTION_MUTEX |在查询通知中事务的状态同步期间出现。|
|QUERY_NOTIFICATION_TABLE_MGR_MUTEX |在查询通知管理器中的内部同步期间出现。|
|QUERY_NOTIFICATION_UNITTEST_MUTEX |标识为仅供参考。 不提供支持。 不保证以后的兼容性。|
|QUERY_OPTIMIZER_PRINT_MUTEX |在查询优化器诊断信息输出生成的同步期间出现。 如果已启用诊断设置下的 Microsoft 产品支持的方向，只会发生此等待类型。|
|QUERY_TASK_ENQUEUE_MUTEX |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|QUERY_TRACEOUT |标识为仅供参考。 不提供支持。 不保证以后的兼容性。|
|RBIO_WAIT_VLF |TBD <br /> **适用范围**： [!INCLUDE[ssSQLv14_md](../../includes/sssqlv14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|RECOVER_CHANGEDB |在备用数据库中同步数据库状态期间出现。|
|RECOVERY_MGR_LOCK |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|REDO_THREAD_PENDING_WORK |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|REDO_THREAD_SYNC |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|REMOTE_BLOCK_IO |TBD <br /> **适用范围**： [!INCLUDE[ssSQLv14_md](../../includes/sssqlv14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|REMOTE_DATA_ARCHIVE_MIGRATION_DMV |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|REMOTE_DATA_ARCHIVE_SCHEMA_DMV |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|REMOTE_DATA_ARCHIVE_SCHEMA_TASK_QUEUE |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|REPL_CACHE_ACCESS |在同步复制项目缓存的期间出现。 在这些等待期间，复制日志读取器将停止，已发布表中的数据定义语言 (DDL) 语句也将被阻止。|
|REPL_HISTORYCACHE_ACCESS |TBD|
|REPL_SCHEMA_ACCESS |在同步复制架构版本信息的期间出现。 该状态在下列情况下存在：针对复制对象执行 DDL 语句时，以及日志读取器根据 DDL 出现次数生成或使用版本控制架构时。 如果使用事务复制在单个发布服务器上有多个已发布的数据库和已发布的数据库会非常活跃，争用可以看到针对该等待类型。|
|REPL_TRANFSINFO_ACCESS |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|REPL_TRANHASHTABLE_ACCESS |TBD|
|REPL_TRANTEXTINFO_ACCESS |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|REPLICA_WRITES |在任务等待将页写入数据库快照或 DBCC 副本的操作完成时出现。|
|REQUEST_DISPENSER_PAUSE |在任务等待所有未完成的 I/O 完成时出现，以便可以为快照备份冻结文件的 I/O。|
|REQUEST_FOR_DEADLOCK_SEARCH |在死锁监视器等待开始下一次死锁搜索时出现。 在两次死锁检测之间可能出现该等待，长时间等待此资源并不指示出现问题。|
|RESERVED_MEMORY_ALLOCATION_EXT |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|RESMGR_THROTTLED |在有新请求传入并且基于 GROUP_MAX_REQUESTS 设置而中止时出现。|
|RESOURCE_GOVERNOR_IDLE |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|RESOURCE_QUEUE |在同步不同的内部资源队列期间出现。|
|RESOURCE_SEMAPHORE |当由于存在其他并发查询而无法立即批准查询内存请求时出现。 等待时间较长或等待次数较多可能指示并发查询的数量过多或内存请求的数量过多。|
|RESOURCE_SEMAPHORE_MUTEX |在查询等待其预留线程的请求完成时出现。 它也在同步查询编译和内存授予请求时出现。|
|RESOURCE_SEMAPHORE_QUERY_COMPILE |在并发查询编译的数量达到中止限制时出现。 等待时间较长或等待次数较多可能指示编译、重新编辑或不可缓存的计划过多。|
|RESOURCE_SEMAPHORE_SMALL_QUERY |当由于存在其他并发查询而无法立即批准较小查询的内存请求时出现。 等待时间不应超过几秒钟，因为如果服务器无法在几秒钟内给予请求的内存，则会将请求传输到主查询内存池中。 等待时间较长可能指示当主内存池被等待的查询阻塞时并发小查询的数量过多。 <br /> **适用于**:[!INCLUDE[ssKilimanjaro_md](../../includes/sskilimanjaro-md.md)]仅。 |
|RESTORE_FILEHANDLECACHE_ENTRYLOCK |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|RESTORE_FILEHANDLECACHE_LOCK |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|RG_RECONFIG |TBD|
|ROWGROUP_OP_STATS |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|ROWGROUP_VERSION |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|RTDATA_LIST |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|SATELLITE_CARGO |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|SATELLITE_SERVICE_SETUP |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|SATELLITE_TASK |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|SBS_DISPATCH |TBD <br /> **适用范围**： [!INCLUDE[ssSQLv14_md](../../includes/sssqlv14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|SBS_RECEIVE_TRANSPORT |TBD <br /> **适用范围**： [!INCLUDE[ssSQLv14_md](../../includes/sssqlv14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|SBS_TRANSPORT |TBD <br /> **适用范围**： [!INCLUDE[ssSQLv14_md](../../includes/sssqlv14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|SCAN_CHAR_HASH_ARRAY_INITIALIZATION |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|SEC_DROP_TEMP_KEY |在尝试删除临时安全密钥失败之后并在重试之前出现。|
|SECURITY_CNG_PROVIDER_MUTEX |TBD <br /> **适用范围**： [!INCLUDE[ssSQLv14_md](../../includes/sssqlv14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|SECURITY_CRYPTO_CONTEXT_MUTEX |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|SECURITY_DBE_STATE_MUTEX |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|SECURITY_KEYRING_RWLOCK |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|SECURITY_MUTEX |当等待互斥体时出现，这些互斥体控制对可扩展的密钥管理 (EKM) 加密提供程序的全局列表以及 EKM 会话的会话作用域列表的访问。|
|SECURITY_RULETABLE_MUTEX |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|SEMPLAT_DSI_BUILD |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|SEQUENCE_GENERATION |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|SEQUENTIAL_GUID |当正在获取新的连续 GUID 时出现。|
|SERVER_IDLE_CHECK |资源监视器是尝试声明 SQL Server 实例为空闲或尝试唤醒时，SQL Server 实例的空闲状态的同步期间出现。|
|SERVER_RECONFIGURE |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|SESSION_WAIT_STATS_CHILDREN |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|SHARED_DELTASTORE_CREATION |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|SHUTDOWN |在关闭语句等待活动连接退出时出现。|
|SLEEP_BPOOL_FLUSH |当检查点为了避免磁盘子系统泛滥而中止新 I/O 的发布时出现。|
|SLEEP_BUFFERPOOL_HELPLW |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|SLEEP_DBSTARTUP |在等待所有数据库恢复时数据库的启动期间出现。|
|SLEEP_DCOMSTARTUP |执行一次在等待 DCOM 初始化完成时的 SQL Server 实例启动过程的大多数。|
|SLEEP_MASTERDBREADY |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|SLEEP_MASTERMDREADY |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|SLEEP_MASTERUPGRADED |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|SLEEP_MEMORYPOOL_ALLOCATEPAGES |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|SLEEP_MSDBSTARTUP |在 SQL 跟踪等待 msdb 数据库完成启动时出现。|
|SLEEP_RETRY_VIRTUALALLOC |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|SLEEP_SYSTEMTASK |在等待 tempdb 完成启动时后台任务的启动期间出现。|
|SLEEP_TASK |当任务在等待一般事件出现期间睡眠时出现。|
|SLEEP_TEMPDBSTARTUP |在任务等待 tempdb 完成启动时出现。|
|SLEEP_WORKSPACE_ALLOCATEPAGE |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|SLO_UPDATE |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|SMSYNC |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|SNI_CONN_DUP |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|SNI_CRITICAL_SECTION |在 SQL Server 网络组件中的内部同步期间出现。|
|SNI_HTTP_WAITFOR_0_DISCON |在 SQL Server 关闭，等待未完成 HTTP 连接退出时期间出现。|
|SNI_LISTENER_ACCESS |当等待非一致性内存访问 (NUMA) 节点更新状态更改时出现。 已序列化对状态更改的访问。|
|SNI_TASK_COMPLETION |当在 NUMA 节点状态更改期间等待所有任务完成时出现。|
|SNI_WRITE_ASYNC |TBD <br /> **适用范围**： [!INCLUDE[ssSQLv14_md](../../includes/sssqlv14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|SOAP_READ |在等待 HTTP 网络读取完成时出现。|
|SOAP_WRITE |在等待 HTTP 网络写入完成时出现。|
|SOCKETDUPLICATEQUEUE_CLEANUP |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|SOS_CALLBACK_REMOVAL |在为了删除回调而对回调列表执行同步期间出现。 服务器初始化完成之后，此计数器可能不会更改。|
|SOS_DISPATCHER_MUTEX |在调度程序池进行内部同步期间出现。 包括调整该池时。|
|SOS_LOCALALLOCATORLIST |在 [!INCLUDE[ssNoVersion_md](../../includes/ssnoversion-md.md)] 内存管理器中进行内部同步期间出现。 <br /> **适用于**:[!INCLUDE[ssKilimanjaro_md](../../includes/sskilimanjaro-md.md)]仅。 |
|SOS_MEMORY_TOPLEVELBLOCKALLOCATOR |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|SOS_MEMORY_USAGE_ADJUSTMENT |在池之间调整内存使用情况时出现。|
|SOS_OBJECT_STORE_DESTROY_MUTEX |当破坏池中的对象时在内存池中进行内部同步期间出现。|
|SOS_PHYS_PAGE_CACHE |考虑到线程等待获得互斥体的时间，它必须在分配物理页前或将这些页返回操作系统前获得。 当 SQL Server 的实例使用 AWE 内存时才显示此类型上的等待。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|SOS_PROCESS_AFFINITY_MUTEX |在同步访问进程关联设置期间出现。|
|SOS_RESERVEDMEMBLOCKLIST |在 SQL Server 内存管理器中的内部同步期间出现。 <br /> **适用于**:[!INCLUDE[ssKilimanjaro_md](../../includes/sskilimanjaro-md.md)]仅。 |
|SOS_SCHEDULER_YIELD |在任务自愿为要执行的其他任务生成计划程序时出现。 在该等待期间任务正在等待其量程更新。|
|SOS_SMALL_PAGE_ALLOC |在分配和释放由某些内存对象管理的内存时出现。|
|SOS_STACKSTORE_INIT_MUTEX |在内部存储初始化同步期间出现。|
|SOS_SYNC_TASK_ENQUEUE_EVENT |在任务以同步方式启动时出现。 SQL Server 中的大多数任务以异步方式，在其中控件返回到启动器任务请求放置在工作队列之后立即启动。|
|SOS_VIRTUALMEMORY_LOW |在内存分配等待资源管理器释放虚拟内存时出现。|
|SOSHOST_EVENT |当宿主的组件，如 CLR，等待上一个 SQL Server 事件同步对象时发生。|
|SOSHOST_INTERNAL |在宿主组件（如 CLR）使用的内存管理器回调同步期间出现。|
|SOSHOST_MUTEX |当宿主的组件，如 CLR，等待上一个 SQL Server 的互斥体同步对象时发生。|
|SOSHOST_RWLOCK |当宿主的组件，如 CLR，等待上一个 SQL Server 读取器 / 编写器同步对象时发生。|
|SOSHOST_SEMAPHORE |当宿主的组件，如 CLR，等待上一个 SQL Server 的信号量同步对象时发生。|
|SOSHOST_SLEEP |当宿主任务在等待一般事件出现期间睡眠时出现。 宿主任务由宿主组件（如 CLR）使用。|
|SOSHOST_TRACELOCK |在同步访问跟踪流期间出现。|
|SOSHOST_WAITFORDONE |在宿主组件（如 CLR）等待任务完成时出现。|
|SP_PREEMPTIVE_SERVER_DIAGNOSTICS_SLEEP |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|SP_SERVER_DIAGNOSTICS_BUFFER_ACCESS |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|SP_SERVER_DIAGNOSTICS_INIT_MUTEX |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|SP_SERVER_DIAGNOSTICS_SLEEP |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|SQLCLR_APPDOMAIN |在 CLR 等待应用程序域完成启动时出现。|
|SQLCLR_ASSEMBLY |在等待访问 appdomain 中已加载的程序集列表时出现。|
|SQLCLR_DEADLOCK_DETECTION |在 CLR 等待死锁检测完成时出现。|
|SQLCLR_QUANTUM_PUNISHMENT |在 CLR 任务由于已经超过了其执行量程而中止时出现。 此中止已完成，以便减小此大量消耗资源的任务对其他任务的影响。|
|SQLSORT_NORMMUTEX |在初始化内部排序结构时进行内部同步期间出现。|
|SQLSORT_SORTMUTEX |在初始化内部排序结构时进行内部同步期间出现。|
|SQLTRACE_BUFFER_FLUSH |当某任务正在等待后台任务将跟踪缓冲区每隔四秒刷新到磁盘时出现。 <br /> **适用于**:[!INCLUDE[ssKilimanjaro_md](../../includes/sskilimanjaro-md.md)]仅。 |
|SQLTRACE_FILE_BUFFER |在文件跟踪同步跟踪缓冲区期间出现。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|SQLTRACE_FILE_READ_IO_COMPLETION |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|SQLTRACE_FILE_WRITE_IO_COMPLETION |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|SQLTRACE_INCREMENTAL_FLUSH_SLEEP |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|SQLTRACE_LOCK |TBD <br /> **适用于**:[!INCLUDE[ssKilimanjaro_md](../../includes/sskilimanjaro-md.md)]仅。 |
|SQLTRACE_PENDING_BUFFER_WRITERS |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|SQLTRACE_SHUTDOWN |在跟踪关闭等待未完成的跟踪事件完成时出现。|
|SQLTRACE_WAIT_ENTRIES |在 SQL 跟踪事件队列等待数据包到达队列时出现。|
|SRVPROC_SHUTDOWN |在关闭进程等待内部资源释放以完全关闭时出现。|
|STARTUP_DEPENDENCY_MANAGER |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|TDS_BANDWIDTH_STATE |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|TDS_INIT |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|TDS_PROXY_CONTAINER |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|TEMPOBJ |在临时对象删除同步时出现。 该等待很少出现，仅在任务已请求 temp 表的独占访问删除时出现。|
|TEMPORAL_BACKGROUND_PROCEED_CLEANUP |TBD <br /> **适用范围**： [!INCLUDE[ssSQLv14_md](../../includes/sssqlv14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|TERMINATE_LISTENER |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|THREADPOOL |当某任务正在等待工作线程运行时出现。 这可能指示最大工作线程数设置过低，或批处理执行时间过长，从而减少可满足其他批处理的工作线程数。|
|TIMEPRIV_TIMEPERIOD |在扩展事件计时器进行内部同步期间出现。|
|TRACE_EVTNOTIF |TBD|
|TRACEWRITE |当 SQL 跟踪行集跟踪提供程序等待可用缓冲区或可处理事件的缓冲区时出现。|
|TRAN_MARKLATCH_DT |在等待事务标记闩锁中的破坏模式闩锁时出现。 事务标记闩锁用于同步提交与标记的事务。|
|TRAN_MARKLATCH_EX |在等待标记事务中的排他模式闩锁时出现。 事务标记闩锁用于同步提交与标记的事务。|
|TRAN_MARKLATCH_KP |在等待标记事务中的保持模式闩锁时出现。 事务标记闩锁用于同步提交与标记的事务。|
|TRAN_MARKLATCH_NL |标识为仅供参考。 不提供支持。 不保证以后的兼容性。|
|TRAN_MARKLATCH_SH |在等待标记事务中的共享模式闩锁时出现。 事务标记闩锁用于同步提交与标记的事务。|
|TRAN_MARKLATCH_UP |在等待标记事务中的更新模式闩锁时出现。 事务标记闩锁用于同步提交与标记的事务。|
|TRANSACTION_MUTEX |在同步多个批处理访问事务期间出现。|
|UCS_ENDPOINT_CHANGE |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|UCS_MANAGER |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|UCS_MEMORY_NOTIFICATION |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|UCS_SESSION_REGISTRATION |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|UCS_TRANSPORT |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|UCS_TRANSPORT_STREAM_CHANGE |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|UTIL_PAGE_ALLOC |在内存不足期间事务日志扫描等待可用内存时出现。|
|VDI_CLIENT_COMPLETECOMMAND |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|VDI_CLIENT_GETCOMMAND |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|VDI_CLIENT_OPERATION |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|VDI_CLIENT_OTHER |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|VERSIONING_COMMITTING |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|VIA_ACCEPT |当在启动过程中完成虚拟接口适配器 (VIA) 提供程序连接时出现。|
|VIEW_DEFINITION_MUTEX |在同步访问已缓存的视图定义期间出现。|
|WAIT_FOR_RESULTS |在等待查询通知触发时出现。|
|WAIT_SCRIPTDEPLOYMENT_REQUEST |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|WAIT_SCRIPTDEPLOYMENT_WORKER |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|WAIT_XLOGREAD_SIGNAL |TBD <br /> **适用范围**： [!INCLUDE[ssSQLv14_md](../../includes/sssqlv14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|WAIT_XTP_ASYNC_TX_COMPLETION |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|WAIT_XTP_CKPT_AGENT_WAKEUP |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|WAIT_XTP_CKPT_CLOSE |当等待检查点完成时发生。， <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|WAIT_XTP_CKPT_ENABLED |已禁用，并且正在等待检查点来启用检查点时出现。， <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|WAIT_XTP_CKPT_STATE_LOCK |同步点状态的检查时发生。， <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|WAIT_XTP_COMPILE_WAIT |TBD <br /> 适用范围：[!INCLUDE[ssSQLv14_md](../../includes/sssqlv14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|WAIT_XTP_GUEST |数据库内存分配器需要停止接收内存不足通知时发生。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|WAIT_XTP_HOST_WAIT |个由数据库引擎触发等待并且由宿主实现。， <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|WAIT_XTP_OFFLINE_CKPT_BEFORE_REDO |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|WAIT_XTP_OFFLINE_CKPT_LOG_IO |当脱机检查点等待日志读取 IO 完成时发生。， <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|WAIT_XTP_OFFLINE_CKPT_NEW_LOG |当脱机检查点等待新日志记录扫描时发生。， <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|WAIT_XTP_PROCEDURE_ENTRY |当删除过程等待要完成该过程的所有当前执行时出现。， <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|WAIT_XTP_RECOVERY |当数据库恢复等待恢复的内存优化对象完成时出现。， <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|WAIT_XTP_SERIAL_RECOVERY |TBD <br /> **适用范围**： [!INCLUDE[ssSQLv14_md](../../includes/sssqlv14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|WAIT_XTP_SWITCH_TO_INACTIVE |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|WAIT_XTP_TASK_SHUTDOWN |当等待内存中 OLTP 进程完成时发生。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|WAIT_XTP_TRAN_DEPENDENCY |当等待事务依赖关系时出现。， <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|WAITFOR |由于 WAITFOR TRANSACT-SQL 语句而发生。 等待持续时间由此语句的参数确定。 它是用户启动的等待。|
|WAITFOR_PER_QUEUE |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|WAITFOR_TASKSHUTDOWN |标识为仅供参考。 不提供支持。 不保证以后的兼容性。|
|WAITSTAT_MUTEX |在同步访问用于填充 sys.dm_os_wait_stats 的统计信息集期间出现。|
|WCC |标识为仅供参考。 不提供支持。 不保证以后的兼容性。|
|WINDOW_AGGREGATES_MULTIPASS |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|WINFAB_API_CALL |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|WINFAB_REPLICA_BUILD_OPERATION |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|WINFAB_REPORT_FAULT |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|WORKTBL_DROP |在删除出现故障的工作表之后，重试之前的暂停期间出现。|
|WRITE_COMPLETION |当正在进行写操作时出现。|
|WRITELOG |等待日志刷新完成时出现。 导致日志刷新的常见操作是检查点和事务提交。|
|XACT_OWN_TRANSACTION |在等待获取事务的所有权时出现。|
|XACT_RECLAIM_SESSION |在等待会话的当前所有者释放会话的所有权时出现。|
|XACTLOCKINFO |在同步访问事务锁列表期间出现。 除事务本身之外，在页拆分过程中死锁检测和锁迁移等操作也可访问锁列表。|
|XACTWORKSPACE_MUTEX |在同步事务中的脱离以及事务登记成员之间的数据库锁数时出现。|
|XDB_CONN_DUP_HASH |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|XDES_HISTORY |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|XDES_OUT_OF_ORDER_LIST |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|XDES_SNAPSHOT |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|XDESTSVERMGR |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|XE_BUFFERMGR_ALLPROCESSED_EVENT |在扩展事件会话缓冲区刷新到目标时发生。 此等待在后台线程上发生。|
|XE_BUFFERMGR_FREEBUF_EVENT |当下列任一条件成立时发生：|
|XE_CALLBACK_LIST |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|XE_CX_FILE_READ |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|XE_DISPATCHER_CONFIG_SESSION_LIST |在使用异步目标的扩展事件会话启动或停止时发生。 此等待表明发生了以下某一情况：|
|XE_DISPATCHER_JOIN |在用于扩展事件会话的后台线程终止时发生。|
|XE_DISPATCHER_WAIT |在用于扩展事件会话的后台线程等待事件缓冲区进行处理时发生。|
|XE_FILE_TARGET_TVF |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|XE_LIVE_TARGET_TVF |TBD <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|XE_MODULEMGR_SYNC |标识为仅供参考。 不提供支持。 不保证以后的兼容性。|
|XE_OLS_LOCK |标识为仅供参考。 不提供支持。 不保证以后的兼容性。|
|XE_PACKAGE_LOCK_BACKOFF |标识为仅供参考。 不提供支持。 <br /> **适用于**:[!INCLUDE[ssKilimanjaro_md](../../includes/sskilimanjaro-md.md)]仅。 |
|XE_SERVICES_EVENTMANUAL |TBD|
|XE_SERVICES_MUTEX |TBD|
|XE_SERVICES_RWLOCK |TBD|
|XE_SESSION_CREATE_SYNC |TBD|
|XE_SESSION_FLUSH |TBD|
|XE_SESSION_SYNC |TBD|
|XE_STM_CREATE |TBD|
|XE_TIMER_EVENT |TBD|
|XE_TIMER_MUTEX |TBD|
|XE_TIMER_TASK_DONE |TBD|
|XIO_CREDENTIAL_MGR_RWLOCK |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|XIO_CREDENTIAL_RWLOCK |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|XIO_EDS_MGR_RWLOCK |TBD <br /> **适用范围**： [!INCLUDE[ssSQLv14_md](../../includes/sssqlv14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|XIO_EDS_RWLOCK |TBD <br /> **适用范围**： [!INCLUDE[ssSQLv14_md](../../includes/sssqlv14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|XIO_IOSTATS_BLOBLIST_RWLOCK |TBD <br /> **适用范围**： [!INCLUDE[ssSQLv14_md](../../includes/sssqlv14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|XIO_IOSTATS_FCBLIST_RWLOCK |TBD <br /> **适用范围**： [!INCLUDE[ssSQLv14_md](../../includes/sssqlv14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|XIO_LEASE_RENEW_MGR_RWLOCK |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|XTP_HOST_DB_COLLECTION |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|XTP_HOST_LOG_ACTIVITY |TBD <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|XTP_HOST_PARALLEL_RECOVERY |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|XTP_PREEMPTIVE_TASK |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|XTP_TRUNCATION_LSN |TBD <br /> **适用范围**： [!INCLUDE[ssSQL15_md](../../includes/sssql15-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|XTPPROC_CACHE_ACCESS |当用于访问所有本机编译存储的过程缓存对象时发生。， <br /> **适用范围**： [!INCLUDE[ssSQL14](../../includes/sssql14-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
|XTPPROC_PARTITIONED_STACK_CREATE |本机分配每个 NUMA 节点为给定的过程编译存储的过程缓存结构 （必须进行单线程） 时发生。， <br /> **适用范围**： [!INCLUDE[ssSQL12](../../includes/sssql11-md.md)] 到 [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]。|
以下 Xevent 与分区相关**交换机**和联机索引重新生成。 有关语法的信息，请参阅[ALTER TABLE (TRANSACT-SQL) ](../../t-sql/statements/alter-table-transact-sql.md)并[ALTER INDEX (-)](../../t-sql/statements/alter-index-transact-sql.md)。
- lock_request_priority_state
- process_killed_by_abort_blockers
- ddl_with_wait_at_low_priority
有关锁兼容性矩阵，请参阅[sys.dm_tran_locks (TRANSACT-SQL)](../../relational-databases/system-dynamic-management-views/sys-dm-tran-locks-transact-sql.md)。
## <a name="see-also"></a>请参阅
[与 SQL Server 操作系统相关的动态管理视图(Transact SQL)](../../relational-databases/system-dynamic-management-views/sql-server-operating-system-related-dynamic-management-views-transact-sql.md)
[sys.dm_exec_session_wait_stats (TRANSACT-SQL)](../../relational-databases/system-dynamic-management-views/sys-dm-exec-session-wait-stats-transact-sql.md)
[sys.dm_db_wait_stats (Azure SQL 数据库)](../../relational-databases/system-dynamic-management-views/sys-dm-db-wait-stats-azure-sql-database.md)
| 103.389535 | 432 | 0.717577 | yue_Hant | 0.939378 |
8aa00a0181fe2462ea49736fa9c98f8b2924cdd3 | 69 | md | Markdown | reference/concepts/anonymous_functions.md | timotheosh/v3 | 806db5328d38c221bc38210c0978430514b60c15 | [
"MIT"
] | 1 | 2020-02-15T08:03:01.000Z | 2020-02-15T08:03:01.000Z | reference/concepts/anonymous_functions.md | timotheosh/v3 | 806db5328d38c221bc38210c0978430514b60c15 | [
"MIT"
] | 6 | 2020-01-07T17:59:02.000Z | 2020-06-29T05:55:14.000Z | reference/concepts/anonymous_functions.md | timotheosh/v3 | 806db5328d38c221bc38210c0978430514b60c15 | [
"MIT"
] | 2 | 2020-01-07T13:48:19.000Z | 2020-01-07T14:40:47.000Z | ## Anonymous functions
A [function](./functions.md) without a name.
| 17.25 | 44 | 0.724638 | eng_Latn | 0.98823 |
8aa037f59a0d9da59d3e37ee366410f35fb1cb12 | 67 | md | Markdown | src/Squot.package/TSquotDiffable.trait/README.md | LeonBein/Squot | 879ca037682c8387864b4736208c1b0bea5ad25c | [
"MIT"
] | 42 | 2017-05-08T09:57:20.000Z | 2022-03-13T20:00:34.000Z | src/Squot.package/TSquotDiffable.trait/README.md | LeonBein/Squot | 879ca037682c8387864b4736208c1b0bea5ad25c | [
"MIT"
] | 323 | 2017-04-24T16:46:24.000Z | 2022-03-13T18:28:52.000Z | src/Squot.package/TSquotDiffable.trait/README.md | LeonBein/Squot | 879ca037682c8387864b4736208c1b0bea5ad25c | [
"MIT"
] | 18 | 2017-05-20T14:22:50.000Z | 2021-11-16T01:35:31.000Z | Something that can be compared to other similar objects with Squot. | 67 | 67 | 0.835821 | eng_Latn | 1.000009 |
8aa071708e2340d144b9958d6dd668e21d0aef95 | 3,256 | md | Markdown | docs/basics/command-line-usage.md | johnkennyuk/DockSTARTer | 8345c77ea21f04abd7bff205980575aad1ed6f08 | [
"MIT"
] | 1,708 | 2018-05-25T14:20:36.000Z | 2022-03-30T16:35:36.000Z | docs/basics/command-line-usage.md | johnkennyuk/DockSTARTer | 8345c77ea21f04abd7bff205980575aad1ed6f08 | [
"MIT"
] | 685 | 2018-05-30T15:24:26.000Z | 2022-03-31T22:59:44.000Z | docs/basics/command-line-usage.md | bails0bub/DockSTARTer | 1d896611a4971a3171c79899a0180876e18d5bc6 | [
"MIT"
] | 258 | 2018-05-30T05:32:33.000Z | 2022-03-28T11:06:26.000Z | # Command Line Usage
Assuming you already followed the installation steps in the readme, there are also a number of command line switches you can use with DockSTARTer.
## Command Line Switches
### Run The Install Script
```bash
sudo ds -i
```
This script does the following:
- Updates your system using `apt-get`
- Installs `curl`, `git`, `grep`, and `sed` (git should already be installed if you started with the install instructions on the main page, but it's here just in case)
- Installs [docker](https://github.com/docker/docker-install) - by downloading via the official docker-install script, used to run containers
When the script finishes it will display a message informing you to reboot if this is the first time you've ran it.
### Run The Compose Generator
```bash
sudo ds -c
```
This script verifies the dependencies above and installs or updates them as needed, then creates a file `~/.docker/compose/docker-compose.yml` based on the variables you configured in your `~/.docker/compose/.env` file. The generator script will run your selected containers after creating the file.
We encourage you to have a look at the generated `docker-compose.yml` file, however if you wish to make changes please consider using overrides. Please review the [Technical Info](https://dockstarter.com/advanced/technical-info) and [Overrides / Introduction](https://dockstarter.com/overrides/introduction) pages.
If you make any changes to your `.env` file (such as changing a port or enabling a new app) you need to rerun the generator which will rebuild only the affected containers.
### Update DockSTARTer
```bash
sudo ds -u
```
This should get you the latest changes to DockSTARTer. This will also backup and update your `.env` file.
You may separately backup and update your `.env` file with the following command.
```bash
sudo ds -e
```
Then you may want to edit your `.env` file and run the generator again to bring up new apps or changes to existing apps.
## Setup Your Environment
If you do not yet have a `~/.docker/compose/.env` file:
```bash
sudo ds -e
```
Edit the file using something like `nano ~/.docker/compose/.env` (CTRL+X will prompt to save and exit the nano editor)
### Application Specific Variables
#### Adding Apps
You can add the variables required to run an app by running:
```bash
sudo ds -a <APPNAME>
```
```bash
## Example:
sudo ds -a sonarr
```
Then your `.env` file fill have a variable named `<APPNAME>_ENABLED` that you can set to `true` and then run the Compose Generator to start the app.
You may also need to fill in or adjust any other variables prefixed with the `<APPNAME>_` that you're enabling.
This is the best place to change the app's external default ports.
#### Removing Apps
You can remove the variables for an app by running:
```bash
sudo ds -r <APPNAME>
```
```bash
## Example:
sudo ds -r sonarr
```
You can also remove all variables for all apps that are disabled by running:
```bash
sudo ds -r
```
You will be prompted individually for each app and shown what will be removed.
### Cleanup Unused Docker Resources
```bash
sudo ds -p
```
This cleans up the DS install, `p` stands for prune in this case. This recovers space from old images if they were somehow left over.
| 30.148148 | 314 | 0.744165 | eng_Latn | 0.997575 |
8aa09c8b7cfbfa9bcc6ff29a98eb16244019346d | 78 | md | Markdown | README.md | JorgeDeLosSantos/furlib | d113d6311c5fbf0a26c069ab9ae857ef7d018e69 | [
"MIT"
] | null | null | null | README.md | JorgeDeLosSantos/furlib | d113d6311c5fbf0a26c069ab9ae857ef7d018e69 | [
"MIT"
] | null | null | null | README.md | JorgeDeLosSantos/furlib | d113d6311c5fbf0a26c069ab9ae857ef7d018e69 | [
"MIT"
] | null | null | null | # furlib
Librería Python didáctica para la asignatura Fundamentos de Robótica
| 26 | 68 | 0.846154 | spa_Latn | 0.799138 |
8aa0f07280aa15e8fafee93b50908e0c721a6b38 | 2,270 | md | Markdown | api/qsharp/microsoft.quantum.chemistry.jordanwigner._tojordanwignerselectinput.md | MicrosoftDocs/quantum-docs-pr.pl-PL | 9aa93b868fade50bb01d8c6629496f3286405401 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-05-19T20:13:41.000Z | 2020-05-19T20:13:41.000Z | api/qsharp/microsoft.quantum.chemistry.jordanwigner._tojordanwignerselectinput.md | MicrosoftDocs/quantum-docs-pr.pl-PL | 9aa93b868fade50bb01d8c6629496f3286405401 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | api/qsharp/microsoft.quantum.chemistry.jordanwigner._tojordanwignerselectinput.md | MicrosoftDocs/quantum-docs-pr.pl-PL | 9aa93b868fade50bb01d8c6629496f3286405401 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-11-15T09:17:47.000Z | 2021-11-15T09:17:47.000Z | ---
uid: Microsoft.Quantum.Chemistry.JordanWigner._ToJordanWignerSelectInput
title: Operacja _ToJordanWignerSelectInput
ms.date: 1/23/2021 12:00:00 AM
ms.topic: article
qsharp.kind: operation
qsharp.namespace: Microsoft.Quantum.Chemistry.JordanWigner
qsharp.name: _ToJordanWignerSelectInput
qsharp.summary: ''
ms.openlocfilehash: b6d3a44b184051c72065050a28e7c723a7aee87e
ms.sourcegitcommit: 71605ea9cc630e84e7ef29027e1f0ea06299747e
ms.translationtype: MT
ms.contentlocale: pl-PL
ms.lasthandoff: 01/26/2021
ms.locfileid: "98839211"
---
# <a name="_tojordanwignerselectinput-operation"></a>Operacja _ToJordanWignerSelectInput
Przestrzeń nazw: [Microsoft. Quantum. Chemia. JordanWigner](xref:Microsoft.Quantum.Chemistry.JordanWigner)
Pakiet: [Microsoft. Quantum. Chemia](https://nuget.org/packages/Microsoft.Quantum.Chemistry)
```qsharp
operation _ToJordanWignerSelectInput (idx : Int, optimizedBEGeneratorSystem : Microsoft.Quantum.Chemistry.JordanWigner.OptimizedBEGeneratorSystem, signQubit : Qubit, selectZControlRegisters : Qubit[], OptimizedBEControlRegisters : Qubit[], pauliBasesIdx : Microsoft.Quantum.Arithmetic.LittleEndian, indexRegisters : Microsoft.Quantum.Arithmetic.LittleEndian[]) : Unit is Adj + Ctl
```
## <a name="input"></a>Dane wejściowe
### <a name="idx--int"></a>IDX: [int](xref:microsoft.quantum.lang-ref.int)
### <a name="optimizedbegeneratorsystem--optimizedbegeneratorsystem"></a>optimizedBEGeneratorSystem: [optimizedBEGeneratorSystem](xref:Microsoft.Quantum.Chemistry.JordanWigner.OptimizedBEGeneratorSystem)
### <a name="signqubit--qubit"></a>signQubit: [qubit](xref:microsoft.quantum.lang-ref.qubit)
### <a name="selectzcontrolregisters--qubit"></a>selectZControlRegisters: [qubit](xref:microsoft.quantum.lang-ref.qubit)[]
### <a name="optimizedbecontrolregisters--qubit"></a>OptimizedBEControlRegisters: [qubit](xref:microsoft.quantum.lang-ref.qubit)[]
### <a name="paulibasesidx--littleendian"></a>pauliBasesIdx: [LittleEndian](xref:Microsoft.Quantum.Arithmetic.LittleEndian)
### <a name="indexregisters--littleendian"></a>indexRegisters: [LittleEndian](xref:Microsoft.Quantum.Arithmetic.LittleEndian)[]
## <a name="output--unit"></a>Dane wyjściowe: [Jednostka](xref:microsoft.quantum.lang-ref.unit)
| 31.971831 | 380 | 0.789868 | yue_Hant | 0.640419 |
8aa1015d73cf7788bf9c78c5a5a0be01578fa2d7 | 1,824 | md | Markdown | docs/dmx/comment-dmx-summary.md | stummsft/sql-docs | b7007397eb9bab405f87ed60fb4ce06e5835dd14 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2020-02-02T17:51:23.000Z | 2020-10-17T02:37:15.000Z | docs/dmx/comment-dmx-summary.md | stummsft/sql-docs | b7007397eb9bab405f87ed60fb4ce06e5835dd14 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/dmx/comment-dmx-summary.md | stummsft/sql-docs | b7007397eb9bab405f87ed60fb4ce06e5835dd14 | [
"CC-BY-4.0",
"MIT"
] | 6 | 2021-02-01T23:45:50.000Z | 2021-02-04T21:16:27.000Z | ---
title: "-- (Comment) (DMX) Summary | Microsoft Docs"
ms.custom: ""
ms.date: "03/02/2016"
ms.prod: analysis-services
ms.prod_service: "analysis-services"
ms.component: ""
ms.reviewer: ""
ms.suite: "pro-bi"
ms.technology:
ms.component: data-mining
ms.tgt_pltfrm: ""
ms.topic: "language-reference"
dev_langs:
- "DMX"
helpviewer_keywords:
- "commenting characters"
- "double hyphens"
- "-- (comment character)"
ms.assetid: 487b580b-5b81-4e52-8868-4fa809e4ef58
caps.latest.revision: 14
author: "Minewiskan"
ms.author: "owend"
manager: "erikre"
---
# -- (Comment) (DMX) Summary
[!INCLUDE[ssas-appliesto-sqlas](../includes/ssas-appliesto-sqlas.md)]
Indicates a text string that [!INCLUDE[ssASnoversion](../includes/ssasnoversion-md.md)] should not execute. You can nest comments within a Data Mining Extensions (DMX) statement, include them at the end of a line of code, or insert them on a separate line.
## Syntax
```
-- Comment_Text
```
#### Parameters
*Comment_Text*
The string that contains the text of the comment.
## Remarks
Use this operator for single-line or nested comments. Comments that are inserted by using -- are delimited by the newline character.
There is no maximum length for comments.
For more information about how to use different kinds of comments in DMX, see [Comments (DMX)](../dmx/comments-dmx.md).
## See Also
[Slash Star (Comment) (DMX)](../dmx/slash-star-comment-dmx.md)
[Double Slash (Comment) (DMX)](../dmx/double-slash-comment-dmx.md)
[Data Mining Extensions (DMX) Operator Reference](../dmx/data-mining-extensions-dmx-operator-reference.md)
[Operators (DMX)](../dmx/operators-dmx.md)
| 32 | 261 | 0.669408 | eng_Latn | 0.765 |
8aa128c3079e2ca2037cf2adb8a0a2088ee13ad7 | 29,438 | md | Markdown | content/bidnici_ii_012.md | books-are-next/hugo-bidnici-II | ccc283579de6b455ef061b3c86e9fc86abd01619 | [
"CC0-1.0"
] | null | null | null | content/bidnici_ii_012.md | books-are-next/hugo-bidnici-II | ccc283579de6b455ef061b3c86e9fc86abd01619 | [
"CC0-1.0"
] | null | null | null | content/bidnici_ii_012.md | books-are-next/hugo-bidnici-II | ccc283579de6b455ef061b3c86e9fc86abd01619 | [
"CC0-1.0"
] | null | null | null | ---
title: KNIHA PÁTÁKonec se nepodobá začátku
contentType: prose
---
## _(1)
Samota a kasárny_
Cosettina bolest, ještě před čtyřmi nebo pěti měsíci tak srdcervoucí a živá, počala se hojit i bez jejího vědomí. Příroda, jaro, mládí, láska k otci, ptačí rozpustilost a veselí květin vlévaly do té panenské a tak mladistvé duše pomaloučku, den po dni, kapku po kapce cosi téměř velmi podobného zapomenutí. Uhasínal tento plamen nadobro? Nebo tam uléhaly jenom vrstvy popela? Jisté je, že se bolestný a palčivý osten téměř už neozval.
Jednou si náhle vzpomněla na Maria:
„Podívejme se!“ řekla si. „Už na něho ani nemyslím.“
Ještě v onom týdnu si všimla, jak velmi hezký hulánský důstojník, s vosím pasem, v úchvatném stejnokroji, s dívčí tváří, se šavlí pod paží, s navoskovanými kníry a s lakovanou hulánskou čapkou jde podél zahradní mříže. Krom toho měl světlé vlasy, velké modré oči, kulatou ješitnou drzou a hezkou tvář; úplný opak Mariův. V ústech měl doutník.
Cosetta si pomyslila, že ten důstojník jistě patří k pluku z kasáren v ulici Babylone.
Nazítří ho zase viděla jít podle zahradní mříže. Všimla si, kolik je hodin.
A od té doby – byla to snad náhoda? – ho vídala přecházet každý den.
Důstojníkovi přátelé si všimli, že tam v té špatně udržované zahradě, za chatrnou rokokovou mříží, bývá dosti hezká osůbka, která se tam namane skoro vždycky, jde-li kolem krásný důstojník, který není čtenáři tak docela neznámý: jmenuje se Théodule Gillenormand.
„Poslyš!“ říkávali mu. „Tam ta maličká po tobě hází zamilovaně očima. Všimni si jí přece.“
„Copak mám čas všímat si všech děvčat, která se na mne podívají?“ odpovídal hulán. To bylo právě v době, kdy Marius pomalu upadal do agónie a říkal si:
„Kdybych ji před smrtí alespoň jednou uviděl!“
Kdyby se bylo splnilo jeho přání a kdyby byl zahlédl Cosettu ve chvíli, kdy se dívá za hulánem, nebyl by řekl ani slovo a byl by umřel bolestí.
Čí to byla chyba? Ničí.
Marius patřil k povahám, které se propadají do zármutku a setrvávají v něm; Cosetta byla z těch, kdo se sice do zármutku ponoří, ale zase se z něho proberou.
Cosetta ostatně procházela nebezpečnou dobou, osudným obdobím dívčího snění, kdy srdce dívky, je-li ponecháno samo sobě, se podobá úponkům révy, které se zachytí, jak se dá, buď na hlavici mramorového sloupu, nebo na hospodském kůlu. Je to krátká a rozhodná chvíle, nebezpečná pro každou osiřelou dívku, bohatou či chudou, protože bohatství nechrání před špatnou volbou; i ve vysokých kruzích se uzavírají nerovné sňatky; opravdová nerovnost je nerovnost duší; a právě tak často mladý neznámý muž, beze jména, z prostého a chudého rodu, je mramorovou hlavicí, která podpírá chrám velkých citů a ušlechtilých myšlenek, a naproti tomu mnohý spokojený a vším oplývající muž z nejlepší společnosti, který má vyleštěné boty a lesklá slova, jeví se – oceňujeme-li nikoli zevnějšek, ale jeho nitro, které má patřit ženě, – jako tupý budižkničemu, ovládaný nezřízenými, nečistými, vínem načichlými vášněmi; hospodský kůl.
Co se tajilo v Cosettině duši? Uklidněná, snad dřímající vášeň; rozkolísaná láska; něco průzračného, ale zářícího, zakaleného v určité hloubce, a temného blízko samého dna. Na hladině se odrážel obraz hezkého důstojníka. Ležela na dně nějaká vzpomínka? – Až tam, docela na dně? – Možná. Cosetta nevěděla.
A tu se přihodilo něco neobyčejného.
## (2)
Cosettiny obavy
V první polovině dubna Jean Valjean odcestoval. Dělával to, jak víme, občas, po velmi dlouhých přestávkách. Býval pryč, nanejvýš tři dny. Kam odcházel? Nikdo to nevěděl, ani sama Cosetta. Jen jednou ho doprovázela při odjezdu kočárem až na konec slepé uličky, na jejímž nároží četla: _Ulička Planchette._ Tam sestoupil a kočár odvezl Cosettu zpátky do ulice Babylone. Jean Valjean podnikal takové malé cesty, zejména tehdy, když v domě chyběly peníze.
Jean Valjean byl tedy pryč. Než odjel, řekl:
„Za tři dny se vrátím.“
Večer byla Cosetta sama v salóně. Aby se rozptýlila, otevřela harmonium, a doprovázejíc se, dala se do zpěvu sboru z Euryanthy: _Lovci zbloudivší v lesích!,_ který má snad nejkrásnější melodii z celé hudební tvorby. Když dozpívala, zamyslila se.
Náhle se jí zdálo, že někdo chodí po zahradě.
Nemohl to být její otec, ten byl na cestách; nemohla to být Toussaintka, protože ta už spala. Bylo deset hodin večer.
Přistoupila k zavřené okenici a přitiskla k ní ucho.
Zdálo se jí, že slyší opatrně našlapující mužské kroky.
Rychle vyběhla do prvního patra, vstoupila do svého pokoje, otevřela vyhlídku v okenici a podívala se do zahrady. Byl úplněk. Vidět bylo jako ve dne.
V zahradě nikdo nebyl.
Otevřela okno. Zahrada byla úplně klidná a část ulice, kam bylo možno dohlédnout, byla opuštěná jako obvykle.
Cosetta si domyslila, že se zmýlila. Jen se domnívala, že zvuk zaslechla. Bylo to mámení smyslů, způsobené chmurným a divukrásným Weberovým sborem, který v duši otvírá děsné hlubiny a před očima se chvěje jako začarovaný les, kde praskají suché větve pod znepokojeným krokem lovců, když se míhají ve večerním soumraku.
Pustila to z hlavy.
Ostatně Cosetta nebyla nikterak bázlivá. V jejích žilách kolovala krev cikánky a chudé dobrodružky. Máme na paměti, že byla spíš skřivánek než holubice. V podstatě byla plachá a statečná.
Nazítří, ne tak pozdě, se procházela za soumraku po zahradě. A uprostřed zmatených myšlenek, kterými se obírala, měla dojem, že chvílemi slyší podobný zvuk jako včera; jako by někdo kráčel ve tmě pod stromy nedaleko ní, ale řekla si, že se nic tak nepodobá krokům v trávě jako narážení dvou větví na sebe, které se samy od sebe pohybují, a nevšímala si toho. Ostatně nic nespatřila.
Vyšla z houštiny; než došla ke schodišti, musela přejít zelený trávníček. Vystoupila právě z houští, když za ní vyšel měsíc a vrhl na trávník její stín.
Cosetta zděšením strnula.
Vedle jejího stínu se zřetelně rýsoval na trávníku jiný, podivně děsivý a strašný stín, stín, který měl kulatý klobouk.
Bylo to cosi jako stín muže, který stál na pokraji houštiny, několik kroků za Cosettou.
Na chvíli ztratila řeč, nemohla ani mluvit ani křičet o pomoc, ani se pohnout nebo otočit hlavu.
Konečně sebrala všechnu odvahu a odhodlaně se obrátila.
Nikdo tam nebyl.
Podívala se na zem. Stín zmizel.
Vstoupila opět do houští, odvážně prohlédla všechny kouty, šla až k mříži a nic nenašla.
Cítila, že ji mrazí. Bylo to zase mámení smyslů? Cože? Dva dny po sobě? Jedna halucinace, budiž, ale dvě? Znepokojovalo ji vědomí, že stín určitě nebyl přelud. Přeludy přece nenosí kulaté klobouky.
Druhý den se Jean Valjean vrátil. Cosetta mu vyprávěla, co, jak se domnívala, slyšela a viděla. Čekala, že ji otec uklidní, že pokrčí rameny a řekne:
„Jsi ty ale blázínek!“
Jean Valjean se zatvářil starostlivě.
„To nic nebude,“ pravil.
Pod nějakou záminkou odešel, sestoupil do zahrady a Cosetta viděla, jak si velmi pozorně prohlíží mříž.
V noci se probudila; tentokrát si byla jista, že docela jasně slyší kroky blízko schodiště pod svými okny. Běžela k vyhlídce a otevřela ji. V zahradě byl opravdu muž a držel v ruce důkladnou hůl. Ve chvíli, kdy už chtěla vykřiknout, osvítil měsíc jeho obličej. Byl to otec.
Znovu ulehla a řekla si:
„Přece ho to znepokojuje!“
Jean Valjean probděl v zahradě noc a dvě příští. Cosetta ho viděla štěrbinou v okenici.
Třetí noc, to už měsíc ubýval a vycházel později, mohla být tak jedna s půlnoci, Cosetta zaslechla ohromný výbuch smíchu a hlas svého otce, který zvolal:
„Cosetto!“
Vyskočila z postele, navlékla si župan a otevřela okno.
Otec stál dole na trávníku.
„Budím tě, abych tě uklidnil,“ pravil, „podívej se. Tady máš ten stín s kulatým kloboukem.“
Ukázal jí na trávník ležící stín, který se opravdu dosti podobal přízraku muže s kulatým kloboukem. Byl to stín, vržený plechovou troubou komínu se stříškou, který se zvedal nad sousední střechou. Cosetta se také dala do smíchu, všechny její ponuré domněnky se vytratily; nazítří se bavila pří snídani se svým otcem tím, že si tropila žerty z příšerné zahrady, ve které strašily stíny komínů.
Jean Valjean se uklidnil; Cosetta si ani nevšimla, byl-li komín opravdu ve směru stínu, který viděla skutečně nebo domněle, a byl-li měsíc na stejném místě oblohy. Netázala se vůbec na zvláštnost komínové roury, která se bojí, aby nebyla přistižena, a stáhne se, když se někdo podívá na její stín: neboť stín zmizel, když se Cosetta obrátila, a tehdy si opravdu myslila, že si je tím jista. Nyní se Cosetta docela uklidnila. Důkaz se jí zdál dostačující, a nápad, že by někdo v zahradě večer nebo v noci chodil, pustila z hlavy.
Ale za několik dní se opět něco přihodilo.
## (3)
Domněnky obohacené Toussaintčinými poznámkami
V zahradě u mříže vedoucí na ulici stála kamenná lavička, chráněná sice habřím před pohledy zvědavců, na kterou však přesto mohla dosáhnout ruka mimojdoucího.
Jednou večer v témž měsíci dubnu Jean Valjean odešel a Cosetta se posadila po západu slunce na lavičku. Vítr svěže čechral stromoví a Cosetta snila; zmocňoval se jí pomalu a beze vší příčiny smutek, onen nepřekonatelný smutek, který na člověka padá s večerem a jejž snad vyvolává – kdož to ví? – tajemství hrobu poodhalující se tou dobou.
Snad v tom šeru byla Fantina.
Cosetta vstala, pomalu prošla zahradou, kráčela zrosenou trávou a říkala si v jakémsi náměsíčním smutku, do něhož byla pohřížena:
„Bylo by opravdu záhodno nosit v tuto hodinu do zahrady dřeváky, ještě se nachladím.“
Vrátila se k lavičce.
Když usedala, zpozorovala na místě, které opustila, dosti velký kámen, který tam zřejmě před chvílí nebyl.
Cosetta kámen pozorovala a tázala se, co to znamená. Najednou ji poděsila myšlenka, že se ten kámen na lavičku nedostal sám, že jej tam někdo dal, že se něčí ruka protáhla mříží. Tentokráte se bála doopravdy. Kámen tu ležel, o tom nebylo možno pochybovat; nedotkla se ho, utekla, aniž se odvážila ohlédnout, schovala se do domu, okamžitě zavřela okenici a zastrčila závoru u dveří do zahrady. Zeptala se Toussaintky:
„Už se vrátil otec?“
„Ještě ne, slečno.“
(Jednou provždy jsme už pověděli, že Toussaintka koktá.
Nechť je nám dovoleno, abychom to nemusili zdůrazňovat. Protiví se nám dělat takový záznam tělesné vady.)
Jean Valjean, který rád přemýšlel a miloval noční procházky, se často vracíval dost pozdě v noci.
„Toussaintová,“ pokračovala Cosetta, „zavíráte navečer pečlivě alespoň okenice do zahrady, dáváte tam závory a zastrkujete tyče do kroužků, když zavíráte?“
„Buďte klidná, slečno!“
Toussaintka na nic nezapomínala, Cosetta to dobře věděla, ale nemohla se zdržet, aby neřekla:
„Je to tady tak opuštěné!“
„To tedy ano,“ řekla Toussaintka, „to je pravda. Člověka by tady zamordovali, dřív než by měl čas vydechnout. A ještě k tomu pán nespí v domě. Ale nebojte se, slečno. Zavírám okna jako tvrz. Dvě samotné ženské! To věřím, je se co bát! Umíte si představit, že by v noci přišli nějací chlapi do pokoje a že by nám řekli: ‚Ani muk‘ a pustili by se do nás, aby nám podřezali krk. Člověk by si z toho tolik nedělal, když umřít, tak umřít, ale hnusí se mi pomyšlení, že by na mě takoví lidé sáhli. A pak, mají asi tupé nože! Ach, můj božíčku!“
„Už mlčte, prosím vás,“ řekla Cosetta, „a všechno dobře zavřete!“
Cosetta byla vyděšena tragédií, kterou právě zaimprovizovala Toussaintka, a možná i stále se vracející vzpomínkou na zjevení minulého týdne, a proto si služebné ani netroufala říci: „Jděte se přece podívat na kámen, který dal někdo na lavičku!“
Měla strach, že by musila znovu zavírat dveře u okna, a nařídila, aby Toussaintka prohlédla dům od půdy až do sklepa; pak se zavřela ve svém pokoji, zastrčila závory, podívala se pod postel, lehla si a špatně spala. Celou noc viděla kámen, veliký jako hora a plný slují.
Při východu slunce – a vlastností východu slunce je, že nás přiměje k smíchu nade všemi můrami noci a že nám vyloudí úsměv úměrně velký strachu, který jsme prožili –, když tedy slunce vyšlo a Cosetta se probudila, myslila na prožité zděšení jako na těžký sen a řekla si:
„Co mě to jen napadlo? To je jako s těmi kroky, které jsem, jak se mi zdálo, slyšela minulý týden v zahradě! To je jako v noci s tím stínem od komínu! Copak se ze mne stává zbabělec?“
Slunce, deroucí se štěrbinami okenic a barvící damaškové záclony do purpurova, ji natolik uklidnilo, že z její mysli zmizelo všechno, i ten kámen.
„Na lavici nebyl kámen, právě tak, jako v zahradě nebyl muž s kulatým kloboukem; o tom kameni se mi zdálo jako o všem ostatním.“
Oblékla se, sestoupila do zahrady, doběhla k lavičce a pocítila, jak jí na čele vyvstává chladný pot. Kámen tam byl.
Ale to byl jen okamžik. Co nás v noci děsí, to ve dne probouzí naši zvědavost.
„Ale co,“ řekla si, „podívejme se přece!“
Zdvihla kámen, byl dost veliký. Pod ním leželo cosi podobného dopisu.
Bílá papírová obálka. Cosetta ji vzala do ruky. Nebyla tam adresa na jedné ani pečeť na druhé straně. Ale obálka, ačkoli otevřená, nebyla prázdná. Uvnitř bylo vidět papíry.
Cosetta sáhla do obálky. Už se nebála, už nebyla zvědavá; cítila vzrůstající úzkost.
Vytáhla z obálky jakýsi papírový sešitek s očíslovanými stránkami; na každé stránce bylo napsáno několik řádek – dosti hezkým a velmi vypsaným písmem, pomyslila si Cosetta.
Hledala nějaké jméno. Nebylo tam. Nějaký podpis. I ten chyběl. Komu to bylo určeno? Pravděpodobně jí, protože neznámá ruka položila balíček na její lavičku. Kdo jí to posílá? Zmocnilo se jí neodolatelné okouzlení, pokusila se odvrátit oči od listů, které se jí chvěly v rukou, rozhlédla se po obloze, po ulici, po akátech, stopených ve světle, po holubech, kteří poletovali nad sousední střechou, a pak se její pohled prudce sklonil k rukopisu: řekla si, že se musí dovědět, co je uvnitř.
A četla:
## (4)
Srdce pod kamenem
Vejde-li se vesmír do jedné bytosti, vzepne-li se bytost až k samému Bohu, tomu se říká láska.
V lásce andělé pozdravují hvězdy.
Duše je dvakrát smutná, je-li smutná z lásky.
Jaká prázdnota, chybí-li nám bytost, která jediná naplňuje svět! A jak je pravdivé, že se milovaná bytost stává Bohem. Chápali bychom, že by na ni Otec všehomíra mohl žárlit, kdyby on sám to všechno nebyl stvořil zřejmě pro duši a duši pro lásku.
Jediné pousmání, jež zahlédneme pod bílým krepovým kloboučkem s fialovým závojem, stačí, aby duše vešla do krajin snů.
Za vším je Bůh, ale všechno Boha skrývá. Věci jsou černé, stvoření neprůhledná. Milujeme-li nějakou bytost, činíme ji průsvitnou.
Některé myšlenky jsou modlitbami. Jsou chvíle, kdy duše padne na kolena, ať se k tomu tělo staví jakkoliv.
Milenci si dovedou odloučenost nahradit tisíci smyšlenkami, v nichž přese všechno zůstala skutečnost. Nesmějí se vídat, nesmějí si psát; vymýšlejí si však plno tajných možností, aby se dorozuměli. Jejich poslíčkem jsou ptáčci zpěváčci, vůně květin, smích dětí, slunce, které svítí, vzdechy větru, hvězdné paprsky, všechno, co žije. A proč by ne? Všechno, co Bůh stvořil, je stvořeno, aby sloužilo lásce. Láska je dosti mocná, aby pověřila přírodu svými vzkazy.
Ó, jaro, tys milostný dopis, který jí tu právě píšu!
Srdce má budoucnost mnohem spíše než hlava. Jedině láska může zaneprázdnit a vyplnit věčnost. K nekonečnosti patří nevyčerpatelnost.
Láska je součástí duše. Podstata obou je táž. Obě, duše i láska, jsou výronem božství, které nic nemůže porušit, rozdrobit, zničit. Je to ohnisko v nás, nesmrtelné a nekonečné, jež nic neumenší a neuhasí. Cítíme, jak se propaluje až do morku kostí, a vidíme, jak září až do nejzazších hlubin nebes.
Milování! Zbožňování! Milostná shodo dvou duší, které si rozumějí, které jsou zajedno, pohledů, které si vidí až na dno! Blažené chvíle, už nemeškejte! Samotáři, kteří se dva a dva procházíte po večerech! Dnové požehnaní a zářiví! Kolikrát se mi zdálo, že se hodiny občas odlučovaly od života andělů, aby zde na zemi procházely osudem lidí.
Bůh nemůže nic přidat ke štěstí milenců, leda by k němu přidal trvání bez konce. Po životě plném lásky – lásku navěky. To je vskutku něco navíc; ale zvětšit intenzitu nevýslovné blaženosti, kterou láska dává duši na tomto světě, toho není mocen ani sám Bůh. Bůh je plnost nebe, láska je plnost člověka.
Hledíte na hvězdy z dvojího důvodu: jsou zářivé a neproniknutelné. Ale zde máte na očích něžnější vyzařování a větší mystérium, ženu.
Ať jsme, kdo jsme, všichni máme blízké bytosti. Chybějí-li nám, chybí nám vzduch a zalykáme se. A to je smrt. Umřít z nedostatku lásky je věc hrozná. Zalkne se duše!
Když láska slila a smísila dvě bytosti v andělskou, posvátnou jednotku, tajemství života je pro ně objeveno; je to pak jen dvojí vyjádření téhož osudu; jsou to vlastně už jen dvě křídla téhož ducha. Milujte se! Buďte v nebi!
Od chvíle, kdy mimo vás projde žena, která při chůzi vyzařuje světlo, jste ztraceni, milujete. Nezbude vám než myslit na ni tak, že ji přinutíte, aby sama myslila na lásku.
Co láska začala, může dovršit jen Bůh.
Pravá láska si zoufá a je okouzlena nad ztracenou rukavicí nebo nad nalezeným kapesníčkem a potřebuje celou věčnost pro svou oddanost a své naděje. Je v ní zároveň něco z nekonečně velikého i z nekonečně malého.
Jste-li kámen, buďte magnetem, jste-li rostlina, buďte citlivkou. Jste-li člověk, buďte láskou.
Lásky se nedosytíš. Má-li člověk štěstí, chce ráj; má-li ráj, chce nebe. Ó vy, kteří jste zamilováni, to všechno je v lásce. Hleďte se v ní toho všeho dopídit. Podobně jako nebesa, i láska má dar rozjímání a navíc ještě rozkoš.
„Chodí ještě do Lucemburské zahrady?“
„Nechodí, pane.“
„Chodí stále na mši do tohoto kostela?“
„Už sem nechodí.“
„Bydlí pořád v tomhle domě?“
„Odstěhovala se.“
„Kam?“
„Neřekla.“
Jak je ponuré, když člověk nezná adresu vlastní duše.
Láska má své dětinskosti, ostatní vášně své malichernosti. Hanba vášním, které člověka snižují, čest těm, které ho učí vidět dětskýma očima!
Je to podivná věc, slyšeli jste kdy o ní? Jsem ve tmách. Jedna bytost mi vzala na odchodu nebe.
Ach, být tak pochováni bok po boku v témž hrobě, ruku v ruce, a chvílemi ve tmách něžně se pohladit, to by stačilo mé věčnosti.
Vy, kteří trpíte, protože máte rádi, milujte ještě více. Umírat láskou znamená láskou žít.
Milujte! Pochmurné hvězdné proměňování je přimíšeno k těmto mukám. V tomto posledním zápase je zároveň extáze.
Šťastní ptáci! Zpívají, protože mají hnízdo.
Láska je nebeské vdechování rajského vzduchu.
Ó srdce hluboká, moudří duchové, berte život, jak jej Bůh stvořil. Je to dlouhá zkouška, nepochopitelná průprava k osudu, jehož neznáme. Osud, tentokrát opravdový, začíná pro člověka na prvním stupni do hrobu. Tehdy se mu cosi zjeví a začíná rozlišovat konečno. Zastavte se u slova – konečno. Živoucí lidé vidí nekonečno. Konečno se zjeví teprve těm, kdo umřeli. Zatím milujte, trpte, doufejte a rozjímejte! Běda tomu, kdo miloval jen tělo, tvar, zdání! Smrt ho o všechno obere. Pokuste se milovat duši, pak se s ní shledáte.
Potkal jsem na ulici chudičkého mladého člověka, který miloval. Měl starý klobouk a jeho šaty byly ošumělé; lokty prodřené; jeho střevíce nabíraly vodu a duší mu prosakovaly hvězdy.
Jak veliká věc je být milován! Ale oč větší je milovat! Vášní srdce dospěje až k heroičnosti. Není pak v jeho složení nic nečistého; opírá se jen o vznešenost a velikost. Nedůstojná myšlenka v něm pak už nevzklíčí právě tak jako se kopřiva neuchytí na ledu. Vznešená a zářivě jasná duše, nepřístupná vášním a hrubým vznětům, povznesená nad mraky a stíny vezdejšího světa, nad bláznivostmi, lžemi, nad nenávistmi, marnivostmi a bědami, je ubytována v nebeském azuru a vnímá už jen hluboké záchvěvy v útrobách osudu, jako horští obři vnímají otřesy země.
Kdyby už nebylo nikoho, kdo by miloval, slunce by uhaslo.
## (5)
Když si Cosetta přečtla psaní
Zatímco Cosetta četla, upadala pomalu v snění. Ve chvíli, kdy zvedla oči od poslední řádky sešitku, kráčel vítězoslavně podle mříže, byla to jeho chvíle, krásný důstojník. Cosetta si řekla, že je ohyzdný.
A znovu se dala do prohlížení sešitu. Byl popsán písmem, jejž Cosetta shledávala úchvatným; touž rukou, ale různým inkoustem, někdy velmi černým, jindy bledším, podle toho, jak se přilévá inkoustu do kalamáře, a byl tedy psán v různé dny. A přece to byla jediná myšlenka, která se tu rozvíjela, vzdech za vzdechem, nepravidelně, neuspořádaně, bez výběru, bez cíle, nahodile. Cosetta nikdy nic podobného nečetla. Rukopis, v němž viděla víc jasu než temnoty, jí připadal jako pootevřená svatyně. Každá tajemná řádka jí svítila před očima a zaplavovala jí srdce podivným jasem. Výchova, které se jí dostalo, mluvila neustále jen o duši a nikdy o lásce, asi tak, jako bychom mluvili o pochodni, ale nikdy o plameni. Ten patnáctistránkový rukopis jí naráz a jemně odhalil celou lásku, bolest, osud, život, věčnost, počátek i konec. Jako by se otevřela ruka a hodila jí nečekaně hrst paprsků. Z těch několika řádků vyciťovala vášnivou, horoucí, ušlechtilou a čestnou povahu, svatou vůli, nesmírnou bolest a nesmírnou naději, sklíčené srdce a bohaté nadšení. Co byl ten rukopis? Dopis. Dopis bez adresy, bez oslovení, bez data, bez podpisu, naléhavý a nezištný, záhada plná pravd, poselství lásky, stvořené k tomu, aby bylo přineseno andělem a přečteno pannou, dostaveníčko smlouvané mimo tuto zemi, milostné psaníčko, které přelud poslal stínu. Vyrovnaný a sklíčený neznámý byl patrně odhodlán hledat útočiště ve smrti a proto své neznámé takto sděloval tajemství osudu, klíč k životu, lásku. Bylo to psáno někým, kdo byl na pokraji hrobu a čelem se dotýkal nebes. Řádky, které skanuly jedna po druhé na papír, byly jako krůpěje duše.
A teď, od koho jsou ty řádky? Kdo je asi psal?
Cosetta nebyla ani na chvíli na rozpacích. Jediný muž.
On!
V mysli se jí rozednilo. Všechno si opět připamatovala. Zakoušela neslýchanou radost a hlubokou úzkost. Byl to on! On jí napsal! On tu byl! Jeho ruka prošla touto mříží! Zatímco ona na něho pomalu zapomínala, on ji našel! Ale což na něho zapomněla? Ne, nikdy. Byla bláhová, že tomu mohla na chvíli věřit. Vždycky ho milovala, vždycky ho zbožňovala. Oheň byl pokryt popelem a nějaký čas doutnal, ale – to dobře cítila – propálil se do hloubky a teď propukl znovu a celou ji zachvátil. Ten sešitek byl jako ohnivá jiskra, která přelétla z jeho duše do její. Cítila, jak znovu zažehuje obrovský požár. Odevzdaně se nechávala proniknout každým Mariovým slovem.
„Ach, ano!“ říkala si. „Jak je mi to všechno známé! To všechno jsem už četla v jeho očích.“
Když už potřetí prohlížela sešitek, důstojník Théodule se vracel podél mříže a zařinčel ostruhami o dlažbu. Cosetta byla donucena pozdvihnout oči. Shledala, že je nudný, malicherný, hloupý, k ničemu, ješitný, nijak hezký, drzý a vlastně ošklivý. Důstojník si myslil, že se musí na ni usmát. Obrátila se zahanbená a rozhořčená. Nejraději by mu byla hodila něco na hlavu.
Utekla, vrátila se do domu a zavřela se ve svém pokoji, aby si znova mohla přečíst rukopis, aby se mu naučila nazpaměť a aby přemýšlela. Když si jej pečlivě přečtla, políbila jej a zastrčila za živůtek.
Byla ztracena. Opět se propadala do nesmírnosti andělské lásky. Rajská propast se znovu otevřela.
Celý den byla jako ohlušená. Málem nemohla ani myslit; zcuchaná přadénka myšlenek se nedala rozmotat; Cosetta tápala, a zatímco se chvěla obavou, doufala. V co doufala?
V nic určitého. Netroufala si nic namlouvat a nechtěla nic odmítat. Chvílemi bledla v obličeji a po těle jí probíhal mráz. Občas se jí zdálo, že se octla na jiné planetě; ptala se: „Je to možné?“ a hledala pod živůtkem milovaný papír, tiskla jej k srdci, cítila jeho hrany na svém těle, a kdyby ji byl Jean Valjean v tu chvíli viděl, byl by se zachvěl před zářivou a nepoznanou radostí, která jí jiskřila zpod obočí.
„Ach! Ano!“ myslila si. „To je jistě on! Je to jeho poselství pro mne!“ A v duchu se ujišťovala, že jí byl vrácen jenom na přímluvu andělů a rozmarem nebes.
Ó proměny lásky! Ó sny! Nebeskou náhodou a přímluvou andělů byla vlastně chlebová kulička, kterou hodil jeden zloděj druhému ze dvora Karla Velikého do lvího příkopu přes střechu věznice Force.
## (6)
Údělem stáří je včas odejít
Když nastal večer, Jean Valjean odešel a Cosetta se ustrojila. Upravila si účes, který jí nejlépe slušel, a oblékla si šaty s poněkud větším výstřihem, odhalujícím kousek hrdla, s výstřihem, jakému dívky říkají ‚trochu odvážný‘. Nebyl však ani trochu ‚odvážný‘, ale slušelo jí to lépe než jindy. Nastrojila se tak, aniž sama věděla proč.
Chtěla jít na procházku? Ne.
Čekala návštěvu? Ne.
Za soumraku sešla do zahrady. Toussaintka byla zaměstnána v kuchyni, jejíž okna vedla do dvorku.
Cosetta se začala procházet pod větvemi, občas je rozhrnujíc, protože se skláněly velmi nízko.
Tak se dostala až k lavičce.
Kámen ležel na svém místě.
Sedla si a položila měkce svou bílou ruku na kámen, jako by ho chtěla pohladit a poděkovat mu.
Náhle se jí zmocnil nevysvětlitelný dojem, který pociťujeme, stojí-li někdo za námi a my ho nevidíme.
Ohlédla se a vstala.
Byl to on.
Měl obnaženou hlavu. Byl bledý a pohublý. Taktak že rozeznala jeho černý oblek. Večerní šero zdůrazňovalo bledost krásného čela a obestíralo jeho oči temnotou. Pod závojem nesrovnatelné něhy spočíval na něm nádech smrti a noci. Jeho obličej byl osvětlen jasem zmírajícího dne a myšlenkou odcházející duše.
Zdálo se, že to ještě není přízrak a že to už není člověk.
Jeho klobouk ležel pohozen několik kroků opodál v houští.
Cosetta ani nevykřikla, protože div neomdlela. Pomalu couvala, protože cítila, že je přitahována. On se ani nepohnul. Obklopovalo ho cosi nevýslovného a smutného, jeho pohled cítila, ale neviděla.
Ustupujíc narazila Cosetta na strom a opřela se o něj. Kdyby tam ten strom nestál, byla by upadla.
A tehdy zaslechla jeho hlas, hlas, který předtím nikdy opravdu neslyšela, který byl sotva o něco hlasitější než šumění listí, a šeptal:
„Odpusťte mi, že jsem zde. Srdce mi přetéká, už jsem nemohl v takovém stavu žít, a proto jsem přišel. Přečetla jste si, co jsem zde na tu lavičku položil? Poznáváte mě trochu? Nebojte se mě. Pamatujete se na ten den, už je to dlouho, kdy jste na mne pohlédla? Bylo to v Lucemburské zahradě, u sochy gladiátora. A na den, kdy jste šla přede mnou? Bylo to 16. června a 2. července. Bude to pomalu rok. Už velmi dlouho jsem vás nespatřil. Ptal jsem se babky, která vybírá poplatek za sedátka, ale řekla mi, že vás už nikdy neviděla. Bydlila jste v Západní ulici ve třetím poschodí nového domu, vidíte, že to vím. Sledoval jsem vás. Co jsem měl dělat? A pak jste zmizela. Jednou jsem myslil, že vás vidím, když jsem právě četl noviny pod loubím Odeonu. Rozběhl jsem se. Ale ne. Byla to osoba, která jen měla stejný klobouk jako vy. Chodívám sem v noci. Nebojte se, nikdo mě nevidí. Chodím se zblízka dívat na vaše okna. Chodím lehce, abyste neslyšela, protože byste se mohla vylekat. Onehdy večer jsem stál za vámi, vy jste se obrátila a já uprchl. Jednou jsem vás slyšel zpívat. Byl jsem šťasten. Vadí vám to, poslouchám-li váš zpěv za okenicemi? To vám přece neublíží. Řekněte, že ne? Hleďte, jste můj anděl, dovolte mi, abych směl někdy přijít. Myslím, že umřu. Ach, kdybyste věděla, jak vás zbožňuju! Promiňte mi, mluvím k vám, a ani nevím, co říkám, snad se na mne hněváte; opravdu se hněváte?“
„Ach, maminko!“ vzdychla Cosetta.
Hroutila se, jako by umírala.
Zachytil ji, když klesala, zachytil ji do náruče, přivinul ji pevně k sobě, nevěděl ani, co činí. Podpíral ji a sám vrávoral. Byl jako zpit; blýskalo se mu před očima; nemohl se soustředit; zdálo se mu, že koná náboženský obřad a že se dopouští svatokrádeže. Ostatně ani dost málo netoužil po té úchvatné ženě, jejíž tělo cítil na své hrudi. Byl zmaten láskou.
Vzala mu ruku a položila si ji na srdce. Ucítil pod šaty papír a řekl zajíkavě:
„Vy mě tedy milujete?“
„Mlč! Však to víš!“
A skryla svou zardělou tvář na prsa pyšného a opojeného mladíka.
Klesl na lavičku a ona vedle něho. Neměli slov. Hvězdy se počaly třpytit. Jak se stalo, že se jejich rty setkaly? Jak se stává, že pták zpívá, že taje sníh, že se růže rozvíjí, že máj rozkvétá a že se úsvit bělá za černými stromy na vrcholku chvějících se pahorků?
Polibek, a to bylo všechno.
Oba se zachvěli a zadívali se na sebe ve tmě rozzářenýma očima.
Necítili ani noční chlad, ani studený kámen, ani vlhkou zemi, ani orosenou trávu, jen se dívali, srdce plná myšlenek. Vzali se za ruce, aniž si to uvědomili.
Neptala se ho, ani na to vlastně nevzpomněla, kudy vstoupil a jak vnikl do zahrady. Zdálo se jí samozřejmé, že tu je!
Chvílemi se Mariovo koleno dotklo kolena Cosettina a oba se zachvěli.
Občas Cosetta zajíkavě promluvila. Duše se jí chvěla na rtech jako rosná krůpěj na květu.
Ponenáhlu se rozpovídali. Po mlčení, které překypuje citem, následovala sdílnost. Nad hlavami se jim klenula jasná a nádherná noc. Obě bytosti, čisté jako andělé, si pověděly všechno, své sny, svá opojení, svá zanícení, své myšlenky, svá pochybování, pověděly si o tom, jak se na dálku zbožňovaly, o tom, jak po sobě toužily a jak byly zoufalé, když se už nevídaly. Svěřily si s naprostou důvěrností, kterou nic nemohlo už zvětšit, všechny své nejskrytější a nejtajnější myšlenky. Vyprávěly si s cudnou vírou v iluze všechno, co jim láska, mládí a zbytek dětství, který jim zůstal, vkládaly do duší. Ta dvě srdce se přelila jedno do druhého, takže si za hodinu vyměnily duše. Pronikli se, okouzlili se a navzájem byli oslněni.
Když skončili, když si všechno řekli, položila Cosetta Mariovi hlavu na rameno a zeptala se:
„Jak se jmenujete?“
„Marius,“ řekl. „A vy?“
„Jmenuji se Cosetta.“
| 72.68642 | 1,628 | 0.784768 | ces_Latn | 1.000008 |
8aa172ddaefdf03b51fb619fff378d6ace0cf048 | 1,475 | md | Markdown | modules/week-2/_posts/2017-01-04-type-of-learner.md | Montana-Media-Arts/120_CreativeCoding1-Fall2021 | 475dd1d39859822822fdc880b379949dd72265ad | [
"MIT"
] | 1 | 2021-01-11T22:51:20.000Z | 2021-01-11T22:51:20.000Z | modules/week-2/_posts/2017-01-04-type-of-learner.md | Montana-Media-Arts/120_CreativeCoding1-Spring2021 | cf69843ad6ef9ed96a1a8adf93cffce0e52c27fa | [
"MIT"
] | 4 | 2021-01-05T20:32:01.000Z | 2022-02-26T07:54:25.000Z | modules/week-2/_posts/2017-01-04-type-of-learner.md | Montana-Media-Arts/120_CreativeCoding1-Fall2020 | 33a8bac11c21d1f7c5a497e59129cd5d442463b0 | [
"MIT"
] | null | null | null | ---
title: How do you learn?
module: 2
---
# How do you learn?
<div class="tab">
<button class="tablinks active" onclick="openTab(event, 'Overview')">Overview</button>
<button class="tablinks" onclick="openTab(event, 'ToDo')">To Do</button>
</div>
<!-- Tab content -->
<div id="Overview" class="tabcontent" style="display:block">
<p><a href="//www.youtube.com/embed/BJfZ-FbKtv0" data-lity>Learning Styles Video</a></p>
<p>This section is all about how do we learn best. Why do I put this in here now? I want to us to better understand how optimally learn (which can be different for everyone) and then find the best way to achieve our goals. When I took this learning quiz, I discovered that I was equally a visual and an auditory learner. This information about myself is important because it means I learn best by watching and listening to others perform tasks. Then, I can master things more easily. How do you best learn? Let's find out!</p>
</div>
<div id="ToDo" class="tabcontent">
<p>Take the quiz below and keep track of your answers. You will turn these in as well.</p>
<p><a href="http://www.educationplanner.org/students/self-assessments/learning-styles-quiz.shtml" target="_new">Learning Style Quiz</a></p>
<p>You are welcome to copy and paste the results and put that into a document. Then, upload that into your GitHub repository. You should have a folder in there called Homework 2 that contains everything you do this week.</p>
</div>
| 47.580645 | 533 | 0.732881 | eng_Latn | 0.991442 |
8aa1eba7442f4744ebd3c836eba602ae84a109c0 | 35 | md | Markdown | articles/email.md | Mozlite/Docs | 85f0d1f3bec8d7a5a7eaa7fa5d15b0efc7fa032b | [
"Apache-2.0"
] | null | null | null | articles/email.md | Mozlite/Docs | 85f0d1f3bec8d7a5a7eaa7fa5d15b0efc7fa032b | [
"Apache-2.0"
] | null | null | null | articles/email.md | Mozlite/Docs | 85f0d1f3bec8d7a5a7eaa7fa5d15b0efc7fa032b | [
"Apache-2.0"
] | null | null | null | # 电子邮件
>[!warning]
>正在上传中，请耐心等待... | 8.75 | 15 | 0.6 | zho_Hans | 0.066842 |
8aa23c354c1ff3661119ccba7ba6b2539f53605f | 4,137 | md | Markdown | docs/t-sql/functions/type-name-transact-sql.md | marcustung/sql-docs.zh-tw | f64ee32984b48f6607d66d80450d51c2b2b6531d | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/t-sql/functions/type-name-transact-sql.md | marcustung/sql-docs.zh-tw | f64ee32984b48f6607d66d80450d51c2b2b6531d | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/t-sql/functions/type-name-transact-sql.md | marcustung/sql-docs.zh-tw | f64ee32984b48f6607d66d80450d51c2b2b6531d | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: TYPE_NAME (Transact-SQL) | Microsoft Docs
ms.custom: ''
ms.date: 03/14/2017
ms.prod: sql
ms.prod_service: database-engine, sql-database, sql-data-warehouse, pdw
ms.reviewer: ''
ms.technology: t-sql
ms.topic: language-reference
f1_keywords:
- TYPE_NAME_TSQL
- TYPE_NAME
dev_langs:
- TSQL
helpviewer_keywords:
- names [SQL Server], data types
- unqualified type names
- type names [SQL Server]
- data types [SQL Server], names
- TYPE_NAME function
ms.assetid: e4075a2e-5f70-440f-986b-9ec8434e07c1
author: MikeRayMSFT
ms.author: mikeray
manager: craigg
monikerRange: '>=aps-pdw-2016||=azuresqldb-current||=azure-sqldw-latest||>=sql-server-2016||=sqlallproducts-allversions||>=sql-server-linux-2017||=azuresqldb-mi-current'
ms.openlocfilehash: 610fe4a3eee5ee6db5e0e00f7940208b38df7ff1
ms.sourcegitcommit: 3026c22b7fba19059a769ea5f367c4f51efaf286
ms.translationtype: HT
ms.contentlocale: zh-TW
ms.lasthandoff: 06/15/2019
ms.locfileid: "65946840"
---
# <a name="typename-transact-sql"></a>TYPE_NAME (Transact-SQL)
[!INCLUDE[tsql-appliesto-ss2008-all-md](../../includes/tsql-appliesto-ss2008-all-md.md)]
傳回指定類型識別碼的非限定類型名稱。
 [Transact-SQL 語法慣例](../../t-sql/language-elements/transact-sql-syntax-conventions-transact-sql.md)
## <a name="syntax"></a>語法
```
TYPE_NAME ( type_id )
```
## <a name="arguments"></a>引數
*type_id*
這是將使用的類型識別碼。 *type_id* 為 **int**，它可以參考呼叫者有權存取之任何結構描述中的類型。
## <a name="return-types"></a>傳回類型
**sysname**
## <a name="exceptions"></a>例外狀況
當發生錯誤，或呼叫端沒有檢視物件的權限時，便會傳回 NULL。
在 [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] 中，使用者只能檢視使用者擁有或被授與某些權限之安全性實體的中繼資料。 這表示發出中繼資料的內建函數 (例如，TYPE_NAME) 會在使用者不具有該物件任何權限時傳回 NULL。 如需相關資訊，請參閱 [Metadata Visibility Configuration](../../relational-databases/security/metadata-visibility-configuration.md)。
## <a name="remarks"></a>Remarks
當 *type_id* 無效或呼叫者沒有足以參考這個類型的權限時，TYPE_NAME 會傳回 NULL。
TYPE_NAME 適用於系統資料類型，也適用於使用者自訂資料類型。 類型可以包含在任何結構描述中，但一律會傳回非限定類型名稱。 這表示名稱沒有 _schema_ **.** 前置詞。
系統函數可以用於選取清單、WHERE 子句以及任何可以使用運算式的位置。 如需詳細資訊，請參閱[運算式 (Transact-SQL)](../../t-sql/language-elements/expressions-transact-sql.md) 及 [WHERE (Transact-SQL)](../../t-sql/queries/where-transact-sql.md)。
## <a name="examples"></a>範例
下列範例會針對 [!INCLUDE[ssSampleDBobject](../../includes/sssampledbobject-md.md)] 資料庫之 `Vendor` 資料表中的每個資料行，傳回物件名稱、資料行名稱和類型名稱。
```
SELECT o.name AS obj_name, c.name AS col_name,
TYPE_NAME(c.user_type_id) AS type_name
FROM sys.objects AS o
JOIN sys.columns AS c ON o.object_id = c.object_id
WHERE o.name = 'Vendor'
ORDER BY col_name;
GO
```
[!INCLUDE[ssResult](../../includes/ssresult-md.md)]
```
obj_name col_name type_name
--------------- ------------------------ --------------
Vendor AccountNumber AccountNumber
Vendor ActiveFlag Flag
Vendor BusinessEntityID int
Vendor CreditRating tinyint
Vendor ModifiedDate datetime
Vendor Name Name
Vendor PreferredVendorStatus Flag
Vendor PurchasingWebServiceURL nvarchar
(8 row(s) affected)
```
## <a name="examples-includesssdwfullincludessssdwfull-mdmd-and-includesspdwincludessspdw-mdmd"></a>範例：[!INCLUDE[ssSDWfull](../../includes/sssdwfull-md.md)] 和 [!INCLUDE[ssPDW](../../includes/sspdw-md.md)]
下列範例會使用識別碼 `1` 來傳回資料類型的 `TYPE ID`。
```
SELECT TYPE_NAME(36) AS Type36, TYPE_NAME(239) AS Type239;
GO
```
如需類型的清單，請查詢 sys.types。
```
SELECT * FROM sys.types;
GO
```
## <a name="see-also"></a>另請參閱
[TYPE_ID (Transact-SQL)](../../t-sql/functions/type-id-transact-sql.md)
[TYPEPROPERTY (Transact-SQL)](../../t-sql/functions/typeproperty-transact-sql.md)
[sys.types (Transact-SQL)](../../relational-databases/system-catalog-views/sys-types-transact-sql.md)
[中繼資料函式 (Transact-SQL)](../../t-sql/functions/metadata-functions-transact-sql.md)
| 35.059322 | 274 | 0.676336 | yue_Hant | 0.791115 |
8aa2803ecca4851afd0484d60ecd93e9c3d78982 | 16,763 | md | Markdown | docs-archive-a/2014/database-engine/transactions-in-memory-optimized-tables.md | MicrosoftDocs/sql-docs-archive-pr.fr-fr | 5dfe5b24c1f29428c7820df08084c925def269c3 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs-archive-a/2014/database-engine/transactions-in-memory-optimized-tables.md | MicrosoftDocs/sql-docs-archive-pr.fr-fr | 5dfe5b24c1f29428c7820df08084c925def269c3 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2021-10-11T06:39:57.000Z | 2021-11-25T02:25:30.000Z | docs-archive-a/2014/database-engine/transactions-in-memory-optimized-tables.md | MicrosoftDocs/sql-docs-archive-pr.fr-fr | 5dfe5b24c1f29428c7820df08084c925def269c3 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2021-09-29T08:51:33.000Z | 2021-10-13T09:18:07.000Z | ---
title: Transactions dans les tables optimisées en mémoire | Microsoft Docs
ms.custom: ''
ms.date: 03/06/2017
ms.prod: sql-server-2014
ms.reviewer: ''
ms.technology: in-memory-oltp
ms.topic: conceptual
ms.assetid: 2cd07d26-a1f1-4034-8d6f-f196eed1b763
author: stevestein
ms.author: sstein
ms.openlocfilehash: bc9109c7243e609e5ddd820b61386183761167bf
ms.sourcegitcommit: ad4d92dce894592a259721a1571b1d8736abacdb
ms.translationtype: MT
ms.contentlocale: fr-FR
ms.lasthandoff: 08/04/2020
ms.locfileid: "87709832"
---
# <a name="transactions-in-memory-optimized-tables"></a>Transactions dans les tables mémoire optimisées
Le contrôle de version de ligne des tables sur disque (à l'aide de l'isolation SNAPSHOT ou avec READ_COMMITTED_SNAPSHOT) fournit un type de contrôle d'accès concurrentiel optimiste. Les programmes d'écriture et les programmes de lecture ne se bloquent pas les uns les autres. Avec les tables mémoire optimisées, les programmes d'écriture ne bloquent pas les autres programmes d'écriture. Avec le contrôle de version de ligne pour les tables sur disque, une transaction verrouille la ligne et les transactions concomitantes tentant de mettre à jour cette ligne sont bloquées. Il n'existe pas de verrouillage avec les tables mémoire optimisées. En revanche, si deux transactions tentent de mettre à jour la même ligne, un conflit d'écriture/écriture (erreur 41302) se produit.
Contrairement aux tables sur disque, les tables mémoire optimisées permettent le contrôle d'accès concurrentiel optimiste avec les niveaux d'isolation plus élevés, REPEATABLE READ et SERIALIZABLE. Les verrous ne sont pas utilisés pour appliquer les niveaux d'isolation. En revanche, à la fin de la transaction, une validation garantit les hypothèses de sérialisation ou de lecture renouvelable. Si les hypothèses ne sont pas respectées, la transaction est arrêtée. Pour plus d’informations, consultez [Transaction Isolation Levels](../../2014/database-engine/transaction-isolation-levels.md).
Les sémantiques clés des transactions pour les tables mémoire optimisées sont les suivantes :
- Contrôles de version multiples
- Isolation d'instantané des transactions
- Optimistic
- Détection de conflit
Chacune de ces sémantiques est expliquée dans les sections suivantes.
## <a name="multi-versioning-in-memory-optimized-tables"></a>Contrôles de version multiples dans les tables mémoire optimisées
Les lignes contenues dans les tables mémoire optimisées peuvent avoir plusieurs versions. Les transactions simultanées peuvent donc accéder à des versions différentes d'une même ligne.
Les données de tables mémoire optimisées sont fondées sur la version. Chaque ligne peut avoir plusieurs versions, valides à différents moments. Les tables sur disque conservent des versions de ligne différentes lorsque l'option READ_COMMITTED_SNAPSHOT ou ALLOW_SNAPSHOT_ISOLATION est activée (ON). Les tables mémoire optimisées conservent toujours des versions de ligne différentes, même si les options READ_COMMITTED_SNAPSHOT et ALLOW_SNAPSHOT_ISOLATION sont désactivées (OFF). Les versions de ligne des tables mémoire optimisées ne sont pas conservées dans tempdb. En revanche, elles sont conservées en ligne, dans les structures de données mémoire optimisées qui stockent les lignes en mémoire.
## <a name="snapshot-based-transaction-isolation-for-memory-optimized-tables"></a>Isolation d'instantané des transactions pour les tables mémoire optimisées
Toutes les opérations d'une même transaction utilisent le même instantané cohérent du point de vue transactionnel des tables mémoire optimisées. Tous les niveaux d'isolation des transactions pour les tables mémoire optimisées sont basés sur un instantané. Par exemple, une transaction utilisant le niveau d'isolation SERIALIZABLE pour accéder aux tables mémoire optimisées exécute toutes les opérations dans le même instantané cohérent d'un point de vue transactionnel.
Les transactions qui accèdent aux tables mémoire optimisées utilisent le contrôle de version de ligne pour obtenir un instantané, cohérent d'un point de vue transactionnel, des lignes contenues dans les tables. Les données lues par n'importe quelle instruction dans la transaction représenteront la version cohérente d'un point de vue transactionnel des données qui existaient au début de la transaction. Par conséquent, les modifications éventuelles apportées par d'autres transactions qui s'exécutent simultanément ne sont pas visibles par les instructions de la transaction actuelle.
## <a name="optimistic-concurrency-control-for-memory-optimized-tables"></a>Contrôle d'accès concurrentiel optimiste pour les tables mémoire optimisées
Les conflits et les erreurs sont rares. Les transactions sur les tables mémoire optimisées partent du principe qu'il n'y a aucun conflit avec d'autres transactions simultanées et que les opérations se déroulent sans problème. Les transactions n'utilisent pas de verrous ni de verrous internes sur la table mémoire optimisée pour garantir leur isolation. Les programmes d'écriture ne bloquent pas les programmes de lecture. Les programmes d'écriture ne bloquent pas les autres programmes d'écriture. En revanche, les transactions se poursuivent dans l'hypothèse (optimiste) qu'il n'y a aucun conflit avec d'autres transactions. Le fait de ne pas utiliser de verrous ou de verrous internes et de ne pas attendre la fin de traitement des mêmes lignes par d'autres transactions améliore les performances.
De plus, si une transaction (TxA) lit les lignes insérées ou modifiées par une autre transaction (TxB) qui est en cours de validation, le système suppose avec optimisme que l'autre transaction est validée plutôt que d'attendre la validation. Dans ce cas, la transaction TxA prend une dépendance de validation sur la transaction TxB.
## <a name="conflict-detection-validation-and-commit-dependency-checks"></a>Détection de conflit, validation et contrôles de dépendance de validation
Si [!INCLUDE[ssNoVersion](../includes/ssnoversion-md.md)] détecte des conflits entre des transactions simultanées, ou des violations de niveau d'isolation, il arrête l'une des transactions en conflit. Cette transaction devra être réexécutée. (Pour plus d'informations, consultez [Guidelines for Retry Logic for Transactions on Memory-Optimized Tables](../relational-databases/in-memory-oltp/memory-optimized-tables.md).)
Le système suppose avec optimisme qu'il n'y a aucun conflit et aucune violation d'isolation de la transaction. S'il détecte la présence de conflits pouvant provoquer des incohérences dans la base de données ou pouvant enfreindre l'isolation des transactions, il met fin à la transaction en cause.
Lorsqu'un conflit a été détecté et la transaction arrêtée, celle-ci doit être réexécutée par le client.
Le tableau suivant récapitule les conditions d'erreur pour les transactions qui accèdent aux tables mémoire optimisées.
### <a name="error-conditions-for-transactions-accessing-memory-optimized-tables"></a>Conditions d'erreur des transactions qui accèdent aux tables mémoire optimisées.
|Error|Scénario|
|-----------|--------------|
|Conflit d'écriture. Tentative de mettre à jour un enregistrement qui a été mis à jour depuis le début de la transaction.|Mise à jour (UPDATE) ou suppression (DELETE) d'une ligne ayant déjà été mise à jour ou supprimée par une transaction simultanée.|
|Échec de la validation de lecture renouvelable|Une ligne qui était lue par la transaction a été modifiée (mise à jour ou supprimée) depuis le début de la transaction. La validation de lecture renouvelable a généralement lieu lors de l'utilisation des niveaux d'isolation de transactions REPEATABLE READ et SERIALIZABLE.|
|Échec de la validation sérialisable|Une nouvelle ligne (fantôme) a été insérée dans l'une des plages d'analyse dans la transaction, depuis le début de la transaction. La ligne aurait été visible par la transaction si elle avait été validée dans la base de données avant le début de la transaction. La validation SERIALIZABLE a généralement lieu lors de l'utilisation de l'isolation SERIALIZABLE et de la validation des contraintes PRIMARY KEY.|
|Échec de la dépendance de validation|La transaction a pris une dépendance sur une autre transaction dont la validation a échoué, en raison de l'un des échecs indiqués dans ce tableau, d'une condition de mémoire insuffisante ou de l'échec de la validation dans le journal des transactions. Ce problème peut se produire avec des transactions de lecture/écriture et de lecture seule.|
### <a name="transaction-lifetime"></a>Durée de vie des transactions
Les problèmes mentionnés dans le tableau précédent peuvent se produire à différents stades au cours d'une transaction. L'illustration suivante montre les phases d'une transaction qui accède à des tables mémoire optimisées.
Durée de vie d'une transaction qui accède à des tables mémoire optimisées.
#### <a name="regular-processing"></a>Traitement normal
Durant cette phase, les instructions [!INCLUDE[tsql](../includes/tsql-md.md)] émises par l'utilisateur sont exécutées. Les lignes sont lues dans les tables, et les nouvelles versions de ligne sont écrites dans la base de données. La transaction est isolée des autres transactions simultanées. La transaction utilise l'instantané des tables mémoire optimisées tel qu'il existait au début de la transaction.
Les écritures dans les tables durant cette phase de la transaction ne sont pas encore visibles dans les autres transactions, à une exception près : les mises à jour et les suppressions de ligne sont visibles pour les opérations de mise à jour et de suppression effectuées dans d'autres transactions, afin de détecter les conflits d'écriture.
Si une opération de mise à jour ou de suppression détecte qu'une ligne a été mise à jour ou supprimée depuis le début logique de la transaction, l'opération échoue avec l'erreur 41302. Le message de l'erreur 41302 est « La transaction en cours a tenté de mettre à jour un enregistrement dans la table X qui a été mis à jour depuis le début de cette transaction. La transaction a été abandonnée. ».
Cette erreur provoque l'arrêt de la transaction (même si XACT_ABORT est désactivé), ce qui signifie que la transaction sera restaurée à la fin de la session utilisateur. Les transactions vouées à l'échec ne peuvent pas être validées et prennent uniquement en charge les opérations de lecture qui n'écrivent pas dans le journal et n'accèdent pas aux tables mémoire optimisées.
##### <a name="commit-dependencies"></a><a name="cd"></a>Dépendances de validation
Lors du traitement normal, une transaction peut lire les lignes écrites par d'autres transactions qui sont en phase de validation, mais qui ne sont pas encore validées. Les lignes sont visibles, car l'heure de fin logique des transactions a été définie au début de la phase de validation.
Si une transaction lit ces lignes non validées, elle prendra une dépendance de validation sur cette transaction. Cela a deux conséquences principales :
- Une transaction ne peut pas être validée tant que les transactions dont elle dépend n'ont pas été validées. En d'autres termes, elle ne peut pas entrer dans la phase de validation tant que toutes les dépendances n'ont pas été annulées.
- En outre, les jeux de résultats ne sont pas retournés au client tant que toutes les dépendances n'ont pas été annulées. Cela empêche le client de voir les données non validées.
Si la validation de l'une des transactions liées échoue, il se produit une erreur de dépendance de validation. Cela signifie que la validation de la transaction échouera avec l'erreur 41301 (« Une précédente transaction dont dépend la transaction en cours s'est arrêtée et la transaction en cours ne peut plus être validée. »).
#### <a name="validation-phase"></a>Phase de validation
Pendant la phase de validation, le système vérifie que les hypothèses nécessaires pour le niveau d'isolation de la transaction demandé étaient vraies entre le début et la fin logiques de la transaction.
Au début de la phase de validation, une heure de fin logique est attribuée à la transaction. Les versions de ligne écrites dans la base de données deviennent accessibles à d'autres transactions à l'heure de fin logique. Pour plus d'informations, consultez [Dépendances de validation](#cd).
##### <a name="repeatable-read-validation"></a>Validation de lecture renouvelable
Si le niveau d'isolation de la transaction est REPEATABLE READ ou SERIALIZABLE, ou que l'accès aux tables se fait avec l'isolation REPEATABLE READ ou SERIALIZABLE (pour plus d'informations, consultez la section « Isolation d'opérations individuelles » dans [Transaction Isolation Levels](../../2014/database-engine/transaction-isolation-levels.md)), le système confirme que les lectures sont renouvelables. Cela signifie que le système vérifie que les versions des lignes lues par la transaction sont des versions de ligne encore valides à l'heure de fin logique de la transaction.
Si l'une des lignes a été mise à jour ou modifiée, la transaction échoue avec l'erreur 41305 (« La transaction en cours n'a pas été validée en raison d'un échec de validation REPEATABLE READ. »).
Cette erreur peut également se produire si une table est supprimée après une insertion, une mise à jour ou une suppression, et avant la validation de la transaction. Cela s'applique uniquement aux opérations d'insertion, de mise à jour ou de suppression dans des procédures stockées compilées en mode natif. De telles opérations d'écriture effectuées via le langage [!INCLUDE[tsql](../includes/tsql-md.md)] interprété provoquent le blocage de l'instruction DROP TABLE, et une temporisation jusqu'à ce que la transaction soit validée.
##### <a name="serializable-validation"></a>Validation sérialisable
La validation sérialisable est exécutée dans deux cas :
- Le niveau d'isolation de la transaction est SERIALIZABLE ou les tables sont accessibles avec l'isolation SERIALIZABLE.
- Les lignes sont insérées dans un index unique, tel que l'index créé pour une contrainte PRIMARY KEY. Le système vérifie qu'aucune ligne avec la même clé n'a été insérée simultanément.
Le système vérifie qu'aucune ligne fantôme n'a été écrite dans la base de données. Les opérations de lecture effectuées par la transaction sont évaluées pour déterminer qu'aucune nouvelle ligne n'a été insérée dans les plages d'analyse de ces opérations de lecture.
L'insertion d'une clé dans un index unique comprend une opération implicite de lecture, qui vérifie que la clé n'est pas un doublon. La validation sérialisable des index uniques garantit que ces index ne peuvent pas avoir de doublons au cas où deux transactions simultanées insèreraient la même clé.
Si des lignes fantômes sont détectées, la transaction échoue avec l'erreur 41325 (« La transaction actuelle n'a pas été validée en raison d'un échec de validation SERIALIZABLE. »).
#### <a name="commit-processing"></a>Traitement de la validation
Si la première phase de validation réussit et que la transaction n'a plus de dépendances, la transaction entre dans la phase de traitement de la validation. Durant cette phase, les modifications apportées aux tables durables sont écrites dans le journal, et le journal est écrit sur le disque, pour garantir la durabilité. Une fois que l'enregistrement de journal de la transaction a été écrit sur le disque, le contrôle est restitué au client.
Toutes les dépendances de validation de la transaction sont annulées, et toutes les transactions qui attendaient la validation de cette transaction peuvent continuer à s'exécuter.
## <a name="limitations"></a>Limites
- Les transactions de bases de données croisées ne sont pas prises en charge avec les tables mémoire optimisées. Une transaction qui accède aux tables mémoire optimisées ne peut pas accéder à plus d'une base de données, à l'exception de l'accès en lecture/écriture à tempdb et de l'accès en lecture seule à la base de données système master.
- Les transactions distribuées ne sont pas prises en charge avec les tables mémoire optimisées. Les transactions distribuées démarrées par BEGIN DISTRIBUTED TRANSACTION ne peuvent pas accéder aux tables mémoire optimisées.
- Les tables mémoire optimisées ne prennent pas en charge le verrouillage. Les verrous explicites via les indicateurs de verrouillage (tels que TABLOCK, XLOCK, ROWLOCK) ne sont pas pris en charge avec les tables mémoire optimisées.
## <a name="see-also"></a>Voir aussi
[Comprendre les transactions sur les tables mémoire optimisées](../../2014/database-engine/understanding-transactions-on-memory-optimized-tables.md)
| 122.357664 | 801 | 0.806001 | fra_Latn | 0.990216 |
8aa2ad85c3aa3b4483d42f6b95f67edfb74e059e | 7,744 | md | Markdown | README.md | alexminnaar/LudiiExampleAI | 4eb6dbe3630e85e0e3a4eedd3eb1b03ac2ac396f | [
"MIT"
] | null | null | null | README.md | alexminnaar/LudiiExampleAI | 4eb6dbe3630e85e0e3a4eedd3eb1b03ac2ac396f | [
"MIT"
] | null | null | null | README.md | alexminnaar/LudiiExampleAI | 4eb6dbe3630e85e0e3a4eedd3eb1b03ac2ac396f | [
"MIT"
] | null | null | null | <img align="right" src="./resources/ludii-logo-64x64.png">
# Ludii Example AI
[](LICENSE)
[](https://github.com/Ludeme/LudiiExampleAI/releases)
[](https://twitter.com/intent/follow?screen_name=ludiigames)
This project contains instructions and examples for the implementation of
third-party AI algorithms / agents for the Ludii general game system. After
developing your own agent, you can load it locally through the GUI of the
Ludii application, and watch it play any game supported by Ludii!
Agents implemented according to the instructions on this page will also be
suitable for submission to any future agent-based playing competitions
organised using the Ludii system.
Most of the documentation found in this repository may also be found in
the Ludii User Guide, accessible from the
[Ludii webpage](http://ludii.games/index.html).
## Table of Contents
- [Requirements](#requirements)
- [Getting Started](#getting-started)
- [Example Agents](#example-agents)
- [Citing Information](#citing-information)
- [Background Info](#background-info)
- [Contact Info](#contact-info)
- [Changelog](#changelog)
- [Acknowledgements](#acknowledgements)
## Requirements
As of this time, only the development of agents in Java is supported. The
**minimum version of Java** required is **Java 8**. Development of agents
in other programming languages may be supported in the future, but there
is no concrete timeline for when this will be supported.
## Getting Started
### AI Development
1. Download [Ludii's JAR file](http://ludii.games/downloads.html). This is the
JAR file that can also be used to launch the Ludii application.
2. Create a new Java project using your favourite IDE. You can also create a
fork of this [github repository](https://github.com/Ludeme/LudiiExampleAI)
to get started with some example implementations of basic agents.
3. Make sure to add the Ludii's JAR file downloaded in step 1 as a library for
your project.
4. Any agent that you'd like to implement will have to extend the abstract class
`util.AI`. This contains three methods that may be overridden:
1. `public Move selectAction(final Game game, final Context context,
final double maxSeconds, final int maxIterations, final int maxDepth)`.
It takes a reference to the `game` being played, and the current
`context` (which contains, among other data, the current game state) as
arguments, and should return the next `Move` to be played by the agent.
The final three arguments can be used to restrict the agent's processing
(its search time, or its maximum iteration count or search depth for example).
2. `public void initAI(final Game game, final int playerID)`. This method can be used
to perform any initialisation of the AI when the game to be played has been
determined, but before the initial game state has been generated.
3. `public boolean supportsGame(final Game game)`. This method has a default implementation
to return `true` for any game, but may be overridden to return `false` for games
that your agent cannot play. For example, it may be unable to play simultaneous-move
games, and then be implemented to always return `false` for those. Ludii will then
know not to try to make your AI play such a game.
For a simple example class that extends this abstract class, see the
[Example Random AI](src/random/RandomAI.java).
5. Export your project to a new JAR file.
### Loading AI in the Ludii Application
In the Ludii application, the dialog in which agent types can be assigned to
players can be opened by clicking one of the player names in the GUI, or by
selecting `Ludii > Preferences...` in the menubar. In addition to a
number of built-in agents, the drop-down menus contain a `From JAR` option.
To load your own custom AI implementation into Ludii, select the `From JAR`
option, and then select the JAR file containing your custom AI's .class file.
A dialog will appear with all the different classes in the selected JAR file
that extend Ludii's `util.AI` abstract class, and you will be required to
choose one of them. Note that this means that it is fine if you have a single
JAR file containing many different, custom AI implementations; they can all be
loaded.
Ludii will attempt to instantiate an agent of the selected class by calling
a zero-arguments constructor of that class. **This will only work correctly
if your class does indeed provide a zero-args constructor, and it will have
to be public as well!.** After loading it as instructed here, the custom AI
can be used to play any games in the Ludii application, just like any other
built-in AI.
**Note:** while the Ludii application is running, it will only load all the
.class files of any selected JAR file once. If you have already selected a
JAR file once, and then re-build your custom JAR file without changing its
filepath, you will have to close and re-open the Ludii application if you
wish to try loading agents from the modified JAR file.
## Example Agents
- [Random AI](src/random/RandomAI.java).
- [Example UCT](src/mcts/ExampleUCT.java) (only supports deterministic, alternating-move games).
- [Example Decoupled UCT](src/mcts/ExampleDUCT.java) (only supporst deterministic, simultaneous-move games).
## Citing Information
When using Ludii in any publications (for example for running experiments, or
for visual inspections of your agent's behaviour during development, etc.),
please cite [our paper on the Ludii system](https://arxiv.org/abs/1905.05013).
This can be done using the following BibTeX entry:
@misc{Piette2019Ludii,
Author = {{\'E}ric Piette and Dennis J. N. J. Soemers and Matthew Stephenson and Chiara F. Sironi and Mark H. M. Winands and Cameron Browne},
Title = {Ludii - The Ludemic General Game System},
Year = {2019},
Eprint = {arXiv:1905.05013},
url = {https://arxiv.org/abs/1905.05013}
}
## Background Info
This repository contains information and examples for the development of third-
party AI implementations which can be loaded into the Ludii General Game System.
Note that this repository does not contain the full Ludii system, or its
built-in AI options.
This work, as well as the full Ludii system itself, are developed for the
Digital Ludeme Project. More info on the project and the system can be found on:
- http://www.ludeme.eu/
- http://ludii.games/
## Contact Info
The preferred method for getting help with troubleshooting, suggesting or
requesting additional functionality, or asking other questions about AI
development for Ludii, is [creating new Issues on the github repository](https://github.com/Ludeme/LudiiExampleAI/issues).
Alternatively, the following email address may be used: `ludii(dot)games(at)gmail(dot)com`.
## Changelog
- 6 September, 2019: Updated repository for compatibility with new version 0.3.0 of Ludii.
- 13 August, 2019: Initial release.
## Acknowledgements
This repository is part of the European Research Council-funded Digital Ludeme Project (ERC Consolidator Grant \#771292), being run by Cameron Browne at Maastricht University's Department of Data Science and Knowledge Engineering.
<a href="https://erc.europa.eu/"><img src="./resources/LOGO_ERC-FLAG_EU_.jpg" title="Funded by the European Research Council" alt="European Research Council Logo" height="384"></a>
| 50.614379 | 231 | 0.776085 | eng_Latn | 0.995783 |
8aa30794fba25e76ce1234a77af5b9614810ef1b | 16,433 | md | Markdown | docs/understanding-airbyte/airbyte-specification.md | GoshPosh/airbyte | b230bc5200f41550d692dc118ad3c03193227018 | [
"MIT"
] | 1 | 2021-11-01T12:08:40.000Z | 2021-11-01T12:08:40.000Z | docs/understanding-airbyte/airbyte-specification.md | vitoravancini/airbyte | a7ddd167f6c42905af16b6dac744bcf18354de19 | [
"MIT"
] | 4 | 2021-10-21T19:00:10.000Z | 2022-01-09T07:11:27.000Z | docs/understanding-airbyte/airbyte-specification.md | vitoravancini/airbyte | a7ddd167f6c42905af16b6dac744bcf18354de19 | [
"MIT"
] | null | null | null | # Airbyte Specification
## Key Takeaways
* The specification is Docker-based; this allows a developer to write a connector in any language they want. All they have to do is put that code in a Docker container that adheres to the interface and protocol described below.
* We currently provide templates to make this even easier for those who prefer to work in python or java. These templates allow the developer to skip any Docker setup so that they can just implement code against well-defined interfaces in their language of choice.
* The specification is designed to work as a CLI. The Airbyte app is built on top of this CLI.
* The specification defines a standard interface for implementing data integrations: Sources and Destinations.
* The specification provides a structured stdout / stdin message passing standard for data transport.
* While this specification works with Airbyte, it is an independent standard.
#### Contents:
1. [General information about the specification](airbyte-specification.md#general)
2. [Connector primitives](airbyte-specification.md#primitives)
3. [Details of the protocol to pass information between connectors](airbyte-specification.md#the-airbyte-protocol)
This document is focused on the interfaces and primitives around connectors. You can better understand how that fits into the bigger picture by checking out the [High-level View](high-level-view.md).
## General
* All structs described in this article are defined using JsonSchema.
* Airbyte uses JSON representations of these structs for all inter-process communication.
### Definitions
* **Airbyte Worker** - This is a core piece of the Airbyte stack that is responsible for 1\) initializing a Source and a Destinations and 2\) passing data from Source to Destination.
* Someone implementing a connector need not ever touch this code, but in this article we mention it to contextualize how data is flowing through Airbyte.
* **Connector** - A connector is code that allows Airbyte to interact with a specific underlying data source \(e.g. Postgres\). In Airbyte, an integration is either a Source or a Destination.
* **Source** - A connector that _pulls_ data from an underlying data source. \(e.g. A Postgres Source reads data from a Postgres database. A Stripe Source reads data from the Stripe API\)
* **Destination** - A connector that _pushes_ data to an underlying data source. \(e.g. A Postgres Destination writes data to a Postgres database\)
* **AirbyteSpecification** - the specification that describes how to implement connectors using a standard interface.
* **AirbyteProtocol** - the protocol used for inter-process communication.
* **Integration Commands** - the commands that an integration container implements \(e.g. `spec`, `check`, `discover`, `read`/`write`\). We describe these commands in more detail below.
* **Sync** - the act of moving data from a Source to a Destination.
## Primitives
### Source
A source is implemented as a Docker container. The container must adhere to the interface described below.
**How the container will be called:**
The first argument passed to the image must be the command \(e.g. `spec`, `check`, `discover`, `read`\). Additional arguments can be passed after the command. Note: The system running the container will handle mounting the appropriate paths so that the config files are available to the container. This code snippet does not include that logic.
```text
docker run --rm -i <source-image-name> spec
docker run --rm -i <source-image-name> check --config <config-file-path>
docker run --rm -i <source-image-name> discover --config <config-file-path>
docker run --rm -i <source-image-name> read --config <config-file-path> --catalog <catalog-file-path> [--state <state-file-path>] > message_stream.json
```
The `read` command will emit a stream records to stdout.
**Interface Pseudocode:**
```text
spec() -> ConnectorSpecification
check(Config) -> AirbyteConnectionStatus
discover(Config) -> AirbyteCatalog
read(Config, AirbyteCatalog, State) -> Stream<AirbyteMessage>
```
#### Spec
* Input:
1. none.
* Output:
1. `spec` - a [ConnectorSpecification](https://github.com/airbytehq/airbyte/blob/922bfd08a9182443599b78dbb273d70cb9f63d30/airbyte-protocol/models/src/main/resources/airbyte_protocol/airbyte_protocol.yaml#L256-L306) wrapped in an `AirbyteMessage` of type `spec`.
* The objective of the spec command is to pull information about how to use a source. The `ConnectorSpecification` contains this information.
* The `connectionSpecification` of the `ConnectorSpecification` must be valid JsonSchema. It describes what inputs are needed in order for the source to interact with the underlying data source.
* e.g. If using a Postgres source, the `ConnectorSpecification` would specify that a `hostname`, `port`, and `password` are required in order for the connector to function.
* The UI reads the JsonSchema in this field in order to render the input fields for a user to fill in.
* This JsonSchema is also used to validate that the provided inputs are valid. e.g. If `port` is one of the fields and the JsonSchema in the `connectorSpecification` specifies that this field should be a number, if a user inputs "airbyte", they will receive an error. Airbyte adheres to JsonSchema validation rules.
#### Check
* Input:
1. `config` - A configuration JSON object that has been validated using the `ConnectorSpecification`.
* Output:
1. `connectionStatus` - an [AirbyteConnectionStatus](https://github.com/airbytehq/airbyte/blob/922bfd08a9182443599b78dbb273d70cb9f63d30/airbyte-protocol/models/src/main/resources/airbyte_protocol/airbyte_protocol.yaml#L99-L112) wrapped in an `AirbyteMessage` of type `connection_status`.
* The `check` command attempts to connect to the underlying data source in order to verify that the provided credentials are usable.
* e.g. If the given the credentials, it can connect to the Postgres database, it will return a success response. If it fails \(perhaps the password is incorrect\), it will return a failed response and \(when possible\) a helpful error message.
#### Discover
* Input:
1. `config` - A configuration JSON object that has been validated using the `ConnectorSpecification`.
* Output:
1. `catalog` - an [AirbyteCatalog](https://github.com/airbytehq/airbyte/blob/922bfd08a9182443599b78dbb273d70cb9f63d30/airbyte-protocol/models/src/main/resources/airbyte_protocol/airbyte_protocol.yaml#L113-L123) wrapped in an `AirbyteMessage` of type `catalog`.
* This command detects the _structure_ of the data in the data source.
* An `AirbyteCatalog` describes the structure of data in a data source. It has a single field called `streams` that contains a list of `AirbyteStream`s. Each of these contain a `name` and `json_schema` field. The `json_schema` field accepts any valid JsonSchema and describes the structure of a stream. This data model is intentionally flexible. That can make it a little hard at first to mentally map onto your own data, so we provide some examples below:
* If we are using a data source that is a traditional relational database, each table in that database would map to an `AirbyteStream`. Each column in the table would be a key in the `properties` field of the `json_schema` field.
* e.g. If we have a table called `users` which had the columns `name` and `age` \(the age column is optional\) the `AirbyteCatalog` would look like this:
```text
{
"streams": [
{
"name": "users",
"schema": {
"type": "object",
"required": ["name"],
"properties": {
"name": {
"type": "string"
},
"age": {
"type": {
"number"
}
}
}
}
}
]
}
```
* If we are using a data source that wraps an API with multiple different resources \(e.g. `api/customers` and `api/products`\) each route would correspond to a stream. The JSON object returned by each route would be described in the `json_schema` field.
* e.g. In the case where the API has two endpoints `api/customers` and `api/products` and each returns a list of JSON objects, the `AirbyteCatalog` might look like this. \(Note: using the JSON schema standard for defining a stream allows us to describe nested objects. We are not constrained to a classic "table/columns" structure\)
```text
{
"streams": [
{
"name": "customers",
"schema": {
"type": "object",
"required": ["name"],
"properties": {
"name": {
"type": "string"
}
}
}
},
{
"name": "products",
"schema": {
"type": "object",
"required": ["name", "features"],
"properties": {
"name": {
"type": "string"
},
"features": {
"type": "array",
"items": {
"type": "object",
"required": ["name", "productId"],
"properties": {
"name": "string",
"productId": "number"
}
}
}
}
}
}
]
}
```
**Note:** Stream and field names can be any UTF8 string. Destinations are responsible for cleaning these names to make them valid table and column names in their respective data stores.
#### Read
* Input:
1. `config` - A configuration JSON object that has been validated using the `ConnectorSpecification`.
2. `catalog` - A `ConfiguredAirbyteCatalog`. This `catalog` should be constructed from the `catalog` returned by the `discover` command. To convert an `AirbyteStream` to a `ConfiguredAirbyteStream` copy the `AirbyteStream` into the stream field of the `ConfiguredAirbyteStream`. Any additional configurations can be specified in the `ConfiguredAirbyteStream`. More details on how this is configured in the [catalog documentation](catalog.md). This catalog will be used in the `read` command to both select what data is transferred and how it is replicated.
3. `state` - A JSON object. This object is only ever written or read by the source, so it is a JSON blob with whatever information is necessary to keep track of how much of the data source has already been read. This is important whenever we need to replicate data with Incremental sync modes such as [Incremental Append](connections/incremental-append.md) or [Incremental Deduped History](connections/incremental-deduped-history.md). Note that this is not currently based on the state of data existing on the destination side.
* Output:
1. `message stream` - A stream of `AirbyteRecordMessage`s and `AirbyteStateMessage`s piped to stdout.
* This command reads data from the underlying data source and converts it into `AirbyteRecordMessage`.
* Outputting `AirbyteStateMessages` is optional. It can be used to track how much of the data source has been synced.
* The connector ideally will only pull the data described in the `catalog` argument. It is permissible for the connector, however, to ignore the `catalog` and pull data from any stream it can find. If it follows this second behavior, the extra data will be pruned in the worker. We prefer the former behavior because it reduces the amount of data that is transferred and allows control over not sending sensitive data. There are some sources for which this is simply not possible.
### Destination
A destination is implemented as a Docker container. The container must adhere to the following interface.
**How the container will be called:**
The first argument passed to the image must be the command \(e.g. `spec`, `check`, `write`\). Additional arguments can be passed after the command. Note: The system running the container will handle mounting the appropriate paths so that the config files are available to the container. This code snippet does not include that logic.
```text
docker run --rm -i <destination-image-name> spec
docker run --rm -i <destination-image-name> check --config <config-file-path>
cat <&0 | docker run --rm -i <destination-image-name> write --config <config-file-path> --catalog <catalog-file-path>
```
The `write` command will consume `AirbyteMessage`s from stdin.
**Interface Pseudocode:**
```text
spec() -> ConnectorSpecification
check(Config) -> AirbyteConnectionStatus
write(Config, AirbyteCatalog, Stream<AirbyteMessage>(stdin)) -> void
```
For the sake of brevity, we will not re-describe `spec` and `check`. They are exactly the same as those commands described for the Source.
#### Write
* Input:
1. `config` - A configuration JSON object that has been validated using the `ConnectorSpecification`.
2. `catalog` - An `AirbyteCatalog`. This `catalog` should be a subset of the `catalog` returned by the `discover` command. Any `AirbyteRecordMessages`s that the destination receives that do _not_ match the structure described in the `catalog` will fail.
3. `message stream` - \(this stream is consumed on stdin--it is not passed as an arg\). It will receive a stream of JSON-serialized `AirbyteMesssage`.
* Output:
1. `AirbyteMessage`s of type `AirbyteStateMessage`. The destination connector should only output state messages if they were previously received as input on stdin. Outputting a state message indicates that all records which came before it have been successfully written to the destination.
* The destination should read in the `AirbyteMessages` and write any that are of type `AirbyteRecordMessage` to the underlying data store.
* The destination should fail if any of the messages it receives do not match the structure described in the `catalog`.
## The Airbyte Protocol
* All messages passed to and from connectors must be wrapped in an `AirbyteMessage` envelope and serialized as JSON. The JsonSchema specification for these messages can be found [here](https://github.com/airbytehq/airbyte/blob/922bfd08a9182443599b78dbb273d70cb9f63d30/airbyte-protocol/models/src/main/resources/airbyte_protocol/airbyte_protocol.yaml#L13-L45).
* Even if a record is wrapped in an `AirbyteMessage` it will only be processed if it appropriate for the given command. e.g. If a source `read` action includes AirbyteMessages in its stream of type Catalog for instance, these messages will be ignored as the `read` interface only expects `AirbyteRecordMessage`s and `AirbyteStateMessage`s. The appropriate `AirbyteMessage` types have been described in each command above.
* **ALL** actions are allowed to return `AirbyteLogMessage`s on stdout. For brevity, we have not mentioned these log messages in the description of each action, but they are always allowed. An `AirbyteLogMessage` wraps any useful logging that the connector wants to provide. These logs will be written to Airbyte's log files and output to the console.
* I/O:
* Connectors receive arguments on the command line via JSON files. `e.g. --catalog catalog.json`
* They read `AirbyteMessage`s from stdin. The destination `write` action is the only command that consumes `AirbyteMessage`s.
* They emit `AirbyteMessage`s on stdout. All commands that output messages use this approach \(even `write` emits `AirbyteLogMessage`s\). e.g. `discover` outputs the `catalog` wrapped in an AirbyteMessage on stdout.
* Messages not wrapped in the `AirbyteMessage` will be ignored.
* Each message must be on its own line. Multiple messages _cannot_ be sent on the same line.
* Each message must but serialize to a JSON object that is exactly 1 line. The JSON objects cannot be serialized across multiple lines.
## Acknowledgements
We'd like to note that we were initially inspired by Singer.io's [specification](https://github.com/singer-io/getting-started/blob/master/docs/SPEC.md#singer-specification) and would like to acknowledge that some of their design choices helped us bootstrap our project. We've since made a lot of modernizations to our protocol and specification, but don't want to forget the tools that helped us get started.
| 70.527897 | 558 | 0.722875 | eng_Latn | 0.99566 |
8aa4857dda56cb56477b7837f47343a6f1eeee34 | 23 | md | Markdown | README.md | Bella2009/generator-inspection- | 6df72529dad9b0980bad6115d37aaf96a243f2cd | [
"Apache-2.0"
] | null | null | null | README.md | Bella2009/generator-inspection- | 6df72529dad9b0980bad6115d37aaf96a243f2cd | [
"Apache-2.0"
] | null | null | null | README.md | Bella2009/generator-inspection- | 6df72529dad9b0980bad6115d37aaf96a243f2cd | [
"Apache-2.0"
] | null | null | null | # generator-inspection- | 23 | 23 | 0.826087 | kor_Hang | 0.263068 |
8aa4bacee4677dffdc1902afb24af3522c57476b | 3,697 | md | Markdown | _posts/2021-8-13-Graph-Search.md | RyanBHuynh/RyanBHuynh.github.io | 2c24825beb1542319ec22c7d04198a0245f3f263 | [
"MIT"
] | null | null | null | _posts/2021-8-13-Graph-Search.md | RyanBHuynh/RyanBHuynh.github.io | 2c24825beb1542319ec22c7d04198a0245f3f263 | [
"MIT"
] | null | null | null | _posts/2021-8-13-Graph-Search.md | RyanBHuynh/RyanBHuynh.github.io | 2c24825beb1542319ec22c7d04198a0245f3f263 | [
"MIT"
] | null | null | null | ---
layout: post
title: Graph Search
---
[Graphs](https://ryanbhuynh.github.io/Graphs/) can be searched in two main ways: depth-first search (DFS) and breadth-first search (BFS).
## Depth-First Search (DFS)
Depth-first search traverses a graph by going deep into a chain of nodes before visiting other chains.
DFS visits all of the children before visiting adjacent nodes.
This happens until the graph has been fully explored.
DFS is implemented with a stack.
Below is an image of how DFS goes through a graph. DFS traverses the nodes 1 through 7 in order.
<img src ="/images/Graphs/DFSTraversal.png" alt="DFS" width="600"/>
DFS can be implemented recursively or iteratively. Below are the algorithms for both methods.
The algorithms below use a graph implemented with an adjacency list.
### Iterative Algorithm
1. Pass a graph node into the DFS function.
2. Create a stack. This stack stores nodes that still need to be processed.
3. Create a list that stores whether each node has been visited yet. At this point, all of the nodes are marked as not visited.
4. Push the first node to the stack.
5. While the stack is not empty:
6. Pop the last node put in.
7. If the popped node has not been visited, visit it and mark it as visited in the list.
8. Create a for loop to push each node's adjacent nodes to the stack.
### Recursive Algorithm
1. Pass the graph, the current node, and a list storing the visited status of each node into the DFS function.
2. Mark the current node as visited.
3. Visit the current node.
4. Create a for loop to check all of the current node's adjacent nodes.
5. If the adjacent node has not been visited yet, call DFS on that node.
## Breadth-First Search (BFS)
Breadth-first search goes wide rather than deep, visiting nodes level by level.
BFS explores a node's neighbors before exploring the rest of the graph.
BFS is implemented with a queue.
Unlike DFS, BFS can only be implemented iteratively.
Below is an image of how BFS goes through a graph. BFS traverses the nodes one level out, then two levels out, then three levels out.
<img src ="/images/Graphs/BFSTraversal.png" alt="DFS" width="600"/>
We go out level by level, visiting the first node, then the nodes in the next level, and then the next level, until all of the nodes have been visited.
If we were to print the nodes via BFS, we would print 1, then 7,5, and 2, then 6 and 3, and then 4.
### Algorithm
This algorithm uses a graph implemented with an adjacency list.
1. Pass the graph node into the BFS function.
2. Create a queue to store the items that need to be processed.
3. Create a list to store the items that have already been processed.
4. Add the node to the queue.
5. While the queue is not empty:
6. Pop the first item in the queue.
7. If the popped node is not in the processed list:
8. Add it to the processed list.
9. Visit the popped node.
10. Use a for loop to go through the popped node's adjacent nodes.
11. If the for loop reaches a node that hasn't been processed yet, add it to the queue.
## Complexity
Time complexity for both algorithms: \\(O(V + E)\\)
Space complexity for both algorithms: \\(O(V)\\)
where \\(V = number \ of \ vertices\\)
\\(E = number \ of \ edges\\)
## More Resources
Below are some more resources to learn about graph search:
[GeeksforGeeks - Depth First Search or DFS for a Graph](https://www.geeksforgeeks.org/depth-first-search-or-dfs-for-a-graph/)
[GeeksforGeeks - Breadth First Search or BFS for a Graph](https://www.geeksforgeeks.org/breadth-first-search-or-bfs-for-a-graph/)
[YouTube - Graph Search, DFS and BFS by HackerRank](https://www.youtube.com/watch?v=zaBhtODEL0w) | 45.085366 | 152 | 0.741682 | eng_Latn | 0.996314 |
8aa4c910248039b114376bce3256bce681f13213 | 20,115 | md | Markdown | powerapps-script-test/test/canvas-apps/connections/connection-twitter.md | MicrosoftDocs/powerapps_script_test-pr.pl-pl | 56d5861a28c671304a7fb7737a009f551e47786d | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-05-19T20:01:36.000Z | 2020-05-19T20:01:36.000Z | powerapps-script-test/test/canvas-apps/connections/connection-twitter.md | MicrosoftDocs/powerapps_script_test-pr.pl-pl | 56d5861a28c671304a7fb7737a009f551e47786d | [
"CC-BY-4.0",
"MIT"
] | null | null | null | powerapps-script-test/test/canvas-apps/connections/connection-twitter.md | MicrosoftDocs/powerapps_script_test-pr.pl-pl | 56d5861a28c671304a7fb7737a009f551e47786d | [
"CC-BY-4.0",
"MIT"
] | 1 | 2019-10-14T19:51:11.000Z | 2019-10-14T19:51:11.000Z | ---
title: Übersicht über die Twitter-Verbindung | Microsoft-Dokumentation
description: Anleitung zum Herstellen einer Verbindung mit Twitter, einige Beispiele für die erforderlichen Schritte und Auflistung aller Funktionen
author: lancedMicrosoft
manager: kvivek
ms.service: powerapps
ms.topic: reference
ms.custom: canvas
ms.reviewer: anneta
ms.date: 07/12/2017
ms.author: lanced
search.audienceType:
- maker
search.app:
- PowerApps
ms.openlocfilehash: 2ab480b0bb2aa61c65e33f67cca5a3b0974ca2c8
ms.sourcegitcommit: 429b83aaa5a91d5868e1fbc169bed1bac0c709ea
ms.translationtype: HT
ms.contentlocale: pl-PL
ms.lasthandoff: 08/24/2018
ms.locfileid: "42834524"
---
# <a name="connect-to-twitter-from-powerapps"></a>Herstellen einer Verbindung mit Twitter aus PowerApps
Über Twitter können Sie Tweets senden und Tweets, Timeline, Freunde und Follower aus Ihrem Twitter-Konto abrufen.
Sie können diese Informationen in einer Bezeichnung in Ihrer App anzeigen. Sie können z.B. ein Eingabetextfeld hinzufügen, die Benutzer auffordern, Text für einen Tweet einzugeben und dann eine Schaltfläche zum Senden des Tweets hinzufügen. Auf ähnliche Weise können Sie einen Tweet abrufen oder suchen und den Text dann in einem Bezeichnung- oder Katalog-Steuerelement in Ihrer App anzeigen.
In diesem Thema wird gezeigt, wie Sie die Twitter-Verbindung erstellen und in einer App verwenden, und es werden die verfügbaren Funktionen aufgeführt.
[!INCLUDE [connection-requirements](../../../includes/connection-requirements.md)]
## <a name="connect-to-twitter"></a>Herstellen einer Verbindung mit Twitter
1. Öffnen Sie PowerApps, wählen Sie **Neu** aus, und erstellen Sie eine **Leere App**. Wählen Sie das Layout für Smartphone oder Tablet aus. Das Tablet-Layout bietet Ihnen einen größeren Arbeitsbereich:
2. Klicken oder tippen Sie im rechten Bereich auf die Registerkarte **Daten** und dann auf **Datenquelle hinzufügen**.
3. Wählen Sie **Neue Verbindung** und anschließend **Twitter** aus:
4. Wählen Sie **Verbinden** aus, geben Sie Ihre Anmeldeinformationen für Twitter ein, und wählen Sie dann **App autorisieren** aus.
5. Wählen Sie **Datenquelle hinzufügen** aus. Die Verbindung wird unter **Datenquellen** angezeigt:
Die Verbindung mit Twitter wurde erstellt und Ihrer App hinzugefügt. Sie kann jetzt verwendet werden.
## <a name="use-the-twitter-connection-in-your-app"></a>Verwenden der Twitter-Verbindung in der App
### <a name="show-a-timeline"></a>Anzeigen einer Timeline
1. Wählen Sie im Menü **Einfügen** die Option **Katalog** aus, und fügen Sie einen der **Mit Text**-Kataloge hinzu.
2. So zeigen Sie Timelines an
* Um die Timeline des aktuellen Benutzers anzuzeigen, legen Sie die **[Items](../controls/properties-core.md)**-Eigenschaft des Katalogs auf die folgenden Formeln fest:
`Twitter.HomeTimeline().TweetText`
`Twitter.HomeTimeline({maxResults:3}).TweetText`
* Um die Timeline eines anderen Benutzers anzuzeigen, legen Sie die **[Items](../controls/properties-core.md)**-Eigenschaft des Katalogs auf die folgende Formel fest:
`Twitter.UserTimeline( *TwitterHandle* ).TweetText`
Geben Sie einen Twitter-Benutzernamen in doppelten Anführungszeichen oder einen entsprechenden Wert ein. Geben Sie z.B. `"satyanadella"` oder `"powerapps"` direkt im Formelausdruck ein.
* Fügen Sie ein Texteingabe-Steuerelement mit dem Namen **Tweep** hinzu, und legen Sie die Default-Eigenschaft auf `Tweep.Text` fest. Geben Sie im Textfeld „Tweep“ einen Twitter-Benutzernamen wie `satyanadella` (ohne Anführungszeichen und das Symbol @) ein.
Legen Sie im Katalog-Steuerelement die Items-Eigenschaft auf die folgende Formel fest:
`Twitter.UserTimeline(Tweep.Text, {maxResults:5}).TweetText`
Im Katalog-Steuerelement werden automatisch die Tweets des eingegebenen Twitter-Benutzernamens angezeigt.
> [!TIP]
> In einigen dieser Formeln wird das Argument **maxResults** zum Anzeigen der letzten *x* Tweets in einer Timeline verwendet.
3. Legen Sie die **Items**-Eigenschaft des Katalogs auf `Twitter.HomeTimeline()` fest.
Wenn der Katalog ausgewählt ist, werden im rechten Bereich Optionen für diesen Katalog angezeigt.
4. Wählen Sie **TweetText** in der ersten Liste, **TweetedBy** in der zweiten Liste und **CreatedAt** in der dritten Liste aus.
Im Katalog werden nun die Werte der ausgewählten Eigenschaften angezeigt.
### <a name="show-followers"></a>Anzeigen von Followern
1. So zeigen Sie mit einem **Mit Text**-Katalog Follower an
* Um die Follower des aktuellen Benutzers anzuzeigen, legen Sie die **[Items](../controls/properties-core.md)**-Eigenschaft des Katalogs auf die folgende Formel fest:
`Twitter.MyFollowers()`
`Twitter.MyFollowers({maxResults:3})`
* Um die Follower eines anderen Benutzers anzuzeigen, legen Sie die **[Items](../controls/properties-core.md)**-Eigenschaft des Katalogs auf die folgende Formel fest:
`Twitter.Followers( *TwitterHandle* )`
Geben Sie einen Twitter-Benutzernamen in doppelten Anführungszeichen oder einen entsprechenden Wert ein. Geben Sie z.B. `"satyanadella"` oder `"powerapps"` direkt im Formelausdruck ein.
* Fügen Sie ein Texteingabe-Steuerelement mit dem Namen **Tweep** hinzu, und legen Sie die Default-Eigenschaft auf `Tweep.Text` fest. Geben Sie im Textfeld „Tweep“ einen Twitter-Benutzernamen wie `satyanadella` (ohne Anführungszeichen und das Symbol @) ein.
Legen Sie im Katalog-Steuerelement die Items-Eigenschaft auf die folgende Formel fest:
`Twitter.Followers(Tweep.Text, {maxResults:5})`
Im Katalog-Steuerelement wird automatisch angezeigt, wer dem eingegebenen Twitter-Benutzernamen folgt.
> [!TIP]
> In einigen dieser Formeln wird das Argument **maxResults** zum Anzeigen der letzten *x* Tweets in einer Timeline verwendet.
2. Legen Sie die **Items**-Eigenschaft des Katalogs auf `Twitter.MyFollowers()` fest.
Wenn der Katalog ausgewählt ist, werden im rechten Bereich Optionen für diesen Katalog angezeigt.
3. Wählen Sie **UserName** in der zweiten Liste aus, und wählen Sie **FullName** in der dritten Liste aus.
Im Katalog werden nun die Werte der ausgewählten Eigenschaften angezeigt.
### <a name="show-followed-users"></a>Anzeigen der Benutzer, denen gefolgt wird
1. So zeigen Sie mit einem **Mit Text**-Katalog an, welchen Benutzern gefolgt wird
* Um anzuzeigen, welchen Benutzern der aktuelle Benutzer folgt, legen Sie die **[Items](../controls/properties-core.md)**-Eigenschaft des Katalogs auf die folgende Formel fest:
`Twitter.MyFollowing()`
`Twitter.MyFollowing({maxResults:3})`
* Um anzuzeigen, welchen Benutzern ein anderer Benutzer folgt, legen Sie die **[Items](../controls/properties-core.md)**-Eigenschaft des Katalogs auf die folgende Formel fest:
`Twitter.Following( *TwitterHandle* )`
Geben Sie einen Twitter-Benutzernamen in doppelten Anführungszeichen oder einen entsprechenden Wert ein. Geben Sie z.B. `"satyanadella"` oder `"powerapps"` direkt im Formelausdruck ein.
* Fügen Sie ein Texteingabe-Steuerelement mit dem Namen **Tweep** hinzu, und legen Sie die Default-Eigenschaft auf `Tweep.Text` fest. Geben Sie im Textfeld „Tweep“ einen Twitter-Benutzernamen wie `satyanadella` (ohne Anführungszeichen und das Symbol @) ein.
Legen Sie im Katalog-Steuerelement die Items-Eigenschaft auf die folgende Formel fest:
`Twitter.Following(Tweep.Text, {maxResults:5})`
Im Katalog-Steuerelement werden automatisch die anderen Benutzernamen angezeigt, denen Sie folgen.
Wenn der Katalog ausgewählt ist, werden im rechten Bereich Optionen für diesen Katalog angezeigt.
2. Wählen Sie **Beschreibung** in der Liste **Body1**, **UserName** in der Liste **Heading1** und **FullName** in der Liste **Subtitle1** aus.
Im Katalog werden nun die Werte der ausgewählten Eigenschaften angezeigt.
### <a name="show-information-about-a-user"></a>Anzeigen von Informationen zu einem Benutzer
Fügen Sie eine Bezeichnung hinzu, und legen Sie deren **[Text](../controls/properties-core.md)**-Eigenschaft auf eine der folgenden Formeln fest:
* `twitter.User( *TwitterHandle* ).Description`
* `twitter.User( *TwitterHandle* ).FullName`
* `twitter.User( *TwitterHandle* ).Location`
* `twitter.User( *TwitterHandle* ).UserName`
* `twitter.User( *TwitterHandle* ).FollowersCount`
* `twitter.User( *TwitterHandle* ).FriendsCount`
* `twitter.User( *TwitterHandle* ).Id`
* `twitter.User( *TwitterHandle* ).StatusesCount`
Geben Sie einen Twitter-Benutzernamen in doppelten Anführungszeichen oder einen entsprechenden Wert ein. Geben Sie z.B. `"satyanadella"` oder `"powerapps"` direkt im Formelausdruck ein.
Sie können ein auch Texteingabe-Steuerelement verwenden, um einen Twitter-Benutzernamen einzugeben, so wie in den anderen Abschnitten dieses Themas.
### <a name="search-tweets"></a>Suchen von Tweets
1. Legen Sie bei einem **Mit Text**-Katalog die **[Items](../controls/properties-core.md)**-Eigenschaft auf die folgende Formel fest:
`Twitter.SearchTweet( *SearchTerm* ).TweetText`
Geben Sie einen *SearchTerm* in doppelten Anführungszeichen oder durch einen Verweis auf einen entsprechenden Wert ein. Geben Sie z.B. `"PowerApps"` oder `"microsoft"` direkt in der Formel ein.
Sie können ein auch ein **Eingabetext**-Steuerelement verwenden, um einen Suchbegriff anzugeben, so wie in den anderen Abschnitten dieses Themas.
> [!TIP]
> Mit „maxResults“ werden die ersten fünf Ergebnisse angezeigt:
`Twitter.SearchTweet(SearchTerm.Text, {maxResults:5}).TweetText`
2. Legen Sie die **Items**-Eigenschaft des Katalogs auf `Twitter.SearchTweet(SearchTerm.Text, {maxResults:5})` fest.
Wenn der Katalog ausgewählt ist, werden im rechten Bereich Optionen für diesen Katalog angezeigt.
3. Wählen Sie **TweetText** in der ersten Liste, **TweetedBy** in der zweiten Liste und **CreatedAt** in der dritten Liste aus.
Im Katalog werden nun die Werte der ausgewählten Eigenschaften angezeigt.
### <a name="send-a-tweet"></a>Senden eines Tweets
1. Fügen Sie ein Texteingabe-Steuerelement hinzu, und benennen Sie es in **MyTweet** um.
2. Fügen Sie eine Schaltfläche hinzu, und legen Sie die **[OnSelect](../controls/properties-core.md)**-Eigenschaft auf die folgende Formel fest:
`Twitter.Tweet({tweetText: MyTweet.Text})`
3. Drücken Sie F5, oder wählen Sie die Vorschauschaltfläche aus (). Geben Sie Text in **MyTweet** ein, und wählen Sie dann die Schaltfläche aus, um den eingegebenen Text zu twittern.
4. Drücken Sie die ESC-Taste, um zum Standardarbeitsbereich zurückzukehren.
## <a name="view-the-available-functions"></a>Anzeigen der verfügbaren Funktionen
Diese Verbindung umfasst die folgenden Funktionen:
| Funktionsname | Beschreibung |
| --- | --- |
| [UserTimeline](connection-twitter.md#usertimeline) |Ruft eine Sammlung der letzten Tweets ab, die vom angegebenen Benutzer gesendet wurden |
| [HomeTimeline](connection-twitter.md#hometimeline) |Ruft die letzten Tweets und Re-Tweets von mir und meinen Followern ab |
| [SearchTweet](connection-twitter.md#searchtweet) |Ruft eine Sammlung von relevanten Tweets ab, die mit einer angegebenen Abfrage übereinstimmen |
| [Followers](connection-twitter.md#followers) |Ruft die Benutzer ab, die dem angegebenen Benutzer folgen |
| [MyFollowers](connection-twitter.md#myfollowers) |Ruft die Benutzer ab, die mir folgen |
| [Following](connection-twitter.md#following) |Ruft die Benutzer, denen der angegebene Benutzer folgt |
| [MyFollowing](connection-twitter.md#myfollowing) |Ruft die Benutzer ab, denen ich folge |
| [User](connection-twitter.md#user) |Ruft Details zum angegebenen Benutzer ab (Beispiel: Benutzername, Beschreibung, Anzahl der folgenden Benutzer usw.) |
| [Tweet](connection-twitter.md#tweet) |Tweet |
| [OnNewTweet](connection-twitter.md#onnewtweet) |Löst einen Workflow aus, wenn ein neuer Tweet gesendet wird, der mit Ihrer Suchabfrage übereinstimmt |
### <a name="usertimeline"></a>UserTimeline
Timeline des Benutzers abrufen: Ruft eine Sammlung der letzten Tweets ab, die vom angegebenen Benutzer gesendet wurden
#### <a name="input-properties"></a>Eingabeeigenschaften
| Name | Datentyp | Erforderlich | Beschreibung |
| --- | --- | --- | --- |
| userName |Zeichenfolge |ja |Twitter-Benutzername |
| maxResults |Ganze Zahl |Nein |Maximale Anzahl von abzurufenden Tweets, z.B. {maxResults:5} |
#### <a name="output-properties"></a>Ausgabeeigenschaften
| Eigenschaftsname | Datentyp | Erforderlich | Beschreibung |
| --- | --- | --- | --- |
| TweetText |Zeichenfolge |Ja | |
| TweetId |Zeichenfolge |Nein | |
| CreatedAt |Zeichenfolge |Nein | |
| RetweetCount |Ganze Zahl |Ja | |
| TweetedBy |Zeichenfolge |Ja | |
| MediaUrls |Array |Nein | |
### <a name="hometimeline"></a>HomeTimeline
Home-Timeline: Ruft die letzten Tweets und Re-Tweets von mir und meinen Followern ab
#### <a name="input-properties"></a>Eingabeeigenschaften
| Name | Datentyp | Erforderlich | Beschreibung |
| --- | --- | --- | --- |
| maxResults |Ganze Zahl |Nein |Maximale Anzahl von abzurufenden Tweets, z.B. {maxResults:5} |
#### <a name="output-properties"></a>Ausgabeeigenschaften
| Eigenschaftsname | Datentyp | Erforderlich | Beschreibung |
| --- | --- | --- | --- |
| TweetText |Zeichenfolge |Ja | |
| TweetId |Zeichenfolge |Nein | |
| CreatedAt |Zeichenfolge |Nein | |
| RetweetCount |Ganze Zahl |Ja | |
| TweetedBy |Zeichenfolge |Ja | |
| MediaUrls |Array |Nein | |
### <a name="searchtweet"></a>SearchTweet
Tweet suchen: Ruft eine Sammlung von relevanten Tweets ab, die mit einer angegebenen Abfrage übereinstimmen
#### <a name="input-properties"></a>Eingabeeigenschaften
| Name | Datentyp | Erforderlich | Beschreibung |
| --- | --- | --- | --- |
| searchQuery |Zeichenfolge |ja |Abfragetext (Sie können alle von Twitter unterstützten Abfrageoperatoren verwenden: http://www.twitter.com/search)) |
| maxResults |Ganze Zahl |Nein |Maximale Anzahl von abzurufenden Tweets, z.B. {maxResults:5} |
#### <a name="output-properties"></a>Ausgabeeigenschaften
| Eigenschaftsname | Datentyp | Erforderlich | Beschreibung |
| --- | --- | --- | --- |
| TweetText |Zeichenfolge |Ja | |
| TweetId |Zeichenfolge |Nein | |
| CreatedAt |Zeichenfolge |Nein | |
| RetweetCount |Ganze Zahl |Ja | |
| TweetedBy |Zeichenfolge |Ja | |
| MediaUrls |Array |Nein | |
### <a name="followers"></a>Followers
Follower abrufen: Ruft die Benutzer ab, die dem angegebenen Benutzer folgen
#### <a name="input-properties"></a>Eingabeeigenschaften
| Name | Datentyp | Erforderlich | Beschreibung |
| --- | --- | --- | --- |
| userName |Zeichenfolge |ja |Twitter-Name des Benutzers |
| maxResults |Ganze Zahl |Nein |Maximale Anzahl von abzurufenden Benutzern, z.B. {maxResults:5} |
#### <a name="output-properties"></a>Ausgabeeigenschaften
| Eigenschaftsname | Datentyp | Erforderlich | Beschreibung |
| --- | --- | --- | --- |
| FullName |Zeichenfolge |Ja | |
| Ort |Zeichenfolge |Ja | |
| Id |Ganze Zahl |Nein | |
| UserName |Zeichenfolge |Ja | |
| FollowersCount |Ganze Zahl |Nein | |
| Beschreibung |Zeichenfolge |Ja | |
| StatusesCount |Ganze Zahl |Nein | |
| FriendsCount |Ganze Zahl |Nein | |
### <a name="myfollowers"></a>MyFollowers
Meine Follower abrufen: Ruft die Benutzer ab, die mir folgen
#### <a name="input-properties"></a>Eingabeeigenschaften
| Name | Datentyp | Erforderlich | Beschreibung |
| --- | --- | --- | --- |
| maxResults |Ganze Zahl |Nein |Maximale Anzahl von abzurufenden Benutzern, z.B. {maxResults:5} |
#### <a name="output-properties"></a>Ausgabeeigenschaften
| Eigenschaftsname | Datentyp | Erforderlich | Beschreibung |
| --- | --- | --- | --- |
| FullName |Zeichenfolge |Ja | |
| Ort |Zeichenfolge |Ja | |
| Id |Ganze Zahl |Nein | |
| UserName |Zeichenfolge |Ja | |
| FollowersCount |Ganze Zahl |Nein | |
| Beschreibung |Zeichenfolge |Ja | |
| StatusesCount |Ganze Zahl |Nein | |
| FriendsCount |Ganze Zahl |Nein | |
### <a name="following"></a>Following
Gefolgte Benutzer abrufen: Ruft die Benutzer ab, denen der angegebene Benutzer folgt
#### <a name="input-properties"></a>Eingabeeigenschaften
| Name | Datentyp | Erforderlich | Beschreibung |
| --- | --- | --- | --- |
| userName |Zeichenfolge |ja |Twitter-Name des Benutzers |
| maxResults |Ganze Zahl |Nein |Maximale Anzahl von abzurufenden Benutzern, z.B. {maxResults:5} |
#### <a name="output-properties"></a>Ausgabeeigenschaften
| Eigenschaftsname | Datentyp | Erforderlich | Beschreibung |
| --- | --- | --- | --- |
| FullName |Zeichenfolge |Ja | |
| Ort |Zeichenfolge |Ja | |
| Id |Ganze Zahl |Nein | |
| UserName |Zeichenfolge |Ja | |
| FollowersCount |Ganze Zahl |Nein | |
| Beschreibung |Zeichenfolge |Ja | |
| StatusesCount |Ganze Zahl |Nein | |
| FriendsCount |Ganze Zahl |Nein | |
### <a name="myfollowing"></a>MyFollowing
Meine gefolgten Benutzer: Ruft die Benutzer ab, denen ich folge
#### <a name="input-properties"></a>Eingabeeigenschaften
| Name | Datentyp | Erforderlich | Beschreibung |
| --- | --- | --- | --- |
| maxResults |Ganze Zahl |Nein |Maximale Anzahl von abzurufenden Benutzern, z.B. {maxResults:5} |
#### <a name="output-properties"></a>Ausgabeeigenschaften
| Eigenschaftsname | Datentyp | Erforderlich | Beschreibung |
| --- | --- | --- | --- |
| FullName |Zeichenfolge |Ja | |
| Ort |Zeichenfolge |Ja | |
| Id |Ganze Zahl |Nein | |
| UserName |Zeichenfolge |Ja | |
| FollowersCount |Ganze Zahl |Nein | |
| Beschreibung |Zeichenfolge |Ja | |
| StatusesCount |Ganze Zahl |Nein | |
| FriendsCount |Ganze Zahl |Nein | |
### <a name="user"></a>User
Benutzer abrufen: Ruft Details zum angegebenen Benutzer ab (Beispiel: Benutzername, Beschreibung, Anzahl der Follower usw.)
#### <a name="input-properties"></a>Eingabeeigenschaften
| Name | Datentyp | Erforderlich | Beschreibung |
| --- | --- | --- | --- |
| userName |Zeichenfolge |ja |Twitter-Name des Benutzers |
#### <a name="output-properties"></a>Ausgabeeigenschaften
| Eigenschaftsname | Datentyp | Erforderlich | Beschreibung |
| --- | --- | --- | --- |
| FullName |Zeichenfolge |Ja | |
| Ort |Zeichenfolge |Ja | |
| Id |Ganze Zahl |Nein | |
| UserName |Zeichenfolge |Ja | |
| FollowersCount |Ganze Zahl |Nein | |
| Beschreibung |Zeichenfolge |Ja | |
| StatusesCount |Ganze Zahl |Nein | |
| FriendsCount |Ganze Zahl |Nein | |
### <a name="tweet"></a>Tweet
Neuen Tweet senden: Tweet
#### <a name="input-properties"></a>Eingabeeigenschaften
| Name | Datentyp | Erforderlich | Beschreibung |
| --- | --- | --- | --- |
| tweetText |Zeichenfolge |Nein |Zu twitternder Text, z.B. {tweetText: "hello"} |
| body |Zeichenfolge |Nein |Zu sendende Medien |
#### <a name="output-properties"></a>Ausgabeeigenschaften
| Eigenschaftsname | Datentyp | Erforderlich | Beschreibung |
| --- | --- | --- | --- |
| TweetId |Zeichenfolge |Ja | |
### <a name="onnewtweet"></a>OnNewTweet
Wenn ein neuer Tweet eingeht: Löst einen Workflow aus, wenn ein neuer Tweet gesendet wird, der mit Ihrer Suchabfrage übereinstimmt
#### <a name="input-properties"></a>Eingabeeigenschaften
| Name | Datentyp | Erforderlich | Beschreibung |
| --- | --- | --- | --- |
| searchQuery |Zeichenfolge |ja |Abfragetext (Sie können alle von Twitter unterstützten Abfrageoperatoren verwenden: http://www.twitter.com/search)) |
#### <a name="output-properties"></a>Ausgabeeigenschaften
| Eigenschaftsname | Datentyp | Erforderlich | Beschreibung |
| --- | --- | --- | --- |
| value |Array |Nein | |
## <a name="helpful-links"></a>Nützliche Links
Alle [verfügbaren Verbindungen](../connections-list.md).
Erfahren Sie, wie Sie Ihren Apps [Verbindungen hinzufügen](../add-manage-connections.md).
| 49.913151 | 392 | 0.727616 | deu_Latn | 0.977691 |
8aa4d29ead601e8a840ab4abc10fefb8b30d102f | 3,763 | md | Markdown | Exchange/ExchangeServer2013/assign-a-certificate-to-the-um-and-um-call-router-services-exchange-2013-help.md | akhtarmughal-9/OfficeDocs-Exchange | c305129b6fbd64b13fcf0bba0ffe84fa66223ad0 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | Exchange/ExchangeServer2013/assign-a-certificate-to-the-um-and-um-call-router-services-exchange-2013-help.md | akhtarmughal-9/OfficeDocs-Exchange | c305129b6fbd64b13fcf0bba0ffe84fa66223ad0 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | Exchange/ExchangeServer2013/assign-a-certificate-to-the-um-and-um-call-router-services-exchange-2013-help.md | akhtarmughal-9/OfficeDocs-Exchange | c305129b6fbd64b13fcf0bba0ffe84fa66223ad0 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: 'Assign a certificate to the UM and UM Call Router services: Exchange 2013 Help'
TOCTitle: Assign a certificate to the UM and UM Call Router services
ms:assetid: 8a900e5f-9779-4213-92d7-ec157b15fbc5
ms:mtpsurl: https://technet.microsoft.com/library/Dn205140(v=EXCHG.150)
ms:contentKeyID: 53908378
ms.reviewer:
manager: serdars
ms.author: serdars
author: msdmaguire
f1.keywords:
- NOCSH
mtps_version: v=EXCHG.150
---
# Assign a certificate to the UM and UM Call Router services in Exchange Server
_**Applies to:** Exchange Server 2013, Exchange Server 2016_
You can use the EAC or the Shell to assign a self-signed, internal public key infrastructure (PKI), or third-party commercial certificate for specific Exchange services. When you use the **New-ExchangeCertificate** cmdlet to assign the certificate to Exchange services with the *Services* parameter, you're prompted to assign the certificate to Exchange services. If you use the EAC to create a certificate, the New Exchange Certificate wizard won't prompt you to assign the certificate to Exchange services. You need to edit the properties of the certificate and assign the certificate by selecting which services you want to assign it to.
Different services have different certificate requirements. For example, some services may only require a server name in the **Subject Name** or **Subject Alternative Name** boxes of a certificate and other services may require a fully qualified domain name (FQDN). Make sure that the certificate name can support the uses required by the services you enable it for.
> [!WARNING]
> Self-signed certificates can't be used when you're integrating Unified Messaging (UM) with Microsoft Lync Server.
For additional management tasks related to managing certificates for Unified Messaging, see [Deploying certificates for UM procedures](deploying-certificates-for-um-procedures-exchange-2013-help.md).
## What do you need to know before you begin?
- Estimated time to complete: 5 minutes.
- You need to be assigned permissions before you can perform this procedure or procedures. To see what permissions you need, see the "Certificate management" entry in the [Exchange and Shell infrastructure permissions](exchange-and-shell-infrastructure-permissions-exchange-2013-help.md) topic and the "UM service" entry in the [Unified Messaging permissions](unified-messaging-permissions-exchange-2013-help.md) topic. You must also log on by using an account that's a member of the local Administrators group on that computer.
- For information about keyboard shortcuts that may apply to the procedures in this topic, see [Keyboard shortcuts in the Exchange admin center](keyboard-shortcuts-in-the-exchange-admin-center-2013-help.md).
> [!TIP]
> Having problems? Ask for help in the Exchange forums. Visit the forums at [Exchange Server](https://social.technet.microsoft.com/forums/office/home?category=exchangeserver).
## Use the EAC to assign a certificate to the Unified Messaging and UM Call Router services
1. In the EAC, navigate to **Servers** \> **Certificates**.
2. In the list view, select the certificate that you want to assign to the Unified Messaging and UM Call Router services, and then click **Edit** .gif "Edit icon").
3. On the *\<Certificate name\>* page, select **Services**, and then select **UM** and **UM call router**.
4. Click **Save**.
## Use the Shell to assign a certificate to the Unified Messaging and UM Call Router services
This example assigns a certificate to the Unified Messaging and UM Call Router services.
```powershell
Enable-ExchangeCertificate -Thumbprint 5113ae0233a72fccb75b1d0198628675333d010e -Services 'UM, UMCallRouter'
```
| 66.017544 | 640 | 0.790593 | eng_Latn | 0.991332 |
f4e500ab5deba01f33d92a496d1155c6dc860176 | 1,579 | md | Markdown | README.md | LauraKokkarinen/pnp-modern-search | d3d8bba8eb314663102fd865393d7e1655c46fca | [
"MIT"
] | 277 | 2019-11-04T22:26:20.000Z | 2022-03-27T21:10:16.000Z | README.md | LauraKokkarinen/pnp-modern-search | d3d8bba8eb314663102fd865393d7e1655c46fca | [
"MIT"
] | 1,580 | 2019-11-05T21:46:42.000Z | 2022-03-31T20:06:34.000Z | README.md | LauraKokkarinen/pnp-modern-search | d3d8bba8eb314663102fd865393d7e1655c46fca | [
"MIT"
] | 293 | 2019-11-18T22:45:41.000Z | 2022-03-29T07:39:01.000Z | # PnP Modern Search Solution
This is a open source solution that helps you to build engaging search based solutions in the SharePoint modern experience.
## Get Started
Download the [latest release](https://github.com/microsoft-search/pnp-modern-search/releases/latest).
More information to get started can be found documentation of this repository: [documentation](https://microsoft-search.github.io/pnp-modern-search).
## Contributing
This project welcomes contributions and suggestions. Most contributions require you to agree to a
Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us
the rights to use your contribution. For details, visit https://cla.microsoft.com.
When you submit a pull request, a CLA-bot will automatically determine whether you need to provide
a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions
provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/).
For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or
contact [[email protected]](mailto:[email protected]) with any additional questions or comments.
## "Sharing is Caring"
## Disclaimer
**THIS CODE IS PROVIDED *AS IS* WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING ANY IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR NON-INFRINGEMENT.**
| 52.633333 | 198 | 0.796073 | eng_Latn | 0.953657 |
f4e6da23108ecbf4267e54d6b9bfdd55a0f1dd9f | 2,197 | md | Markdown | docs/web/tutorial/07-share-code.md | NagRock/nx | 4f7ec847418d57102c173c1562e4d610df02017d | [
"MIT"
] | null | null | null | docs/web/tutorial/07-share-code.md | NagRock/nx | 4f7ec847418d57102c173c1562e4d610df02017d | [
"MIT"
] | null | null | null | docs/web/tutorial/07-share-code.md | NagRock/nx | 4f7ec847418d57102c173c1562e4d610df02017d | [
"MIT"
] | null | null | null | # Step 7: Share Code
Awesome! The application is working end to end! However, there is a problem. Both the backend and the frontend define the `Todo` interface. The interface is in sync now, but in a real application, over time, it will diverge, and, as a result, runtime errors will creep in. You should share this interface between the backend and the frontend. In Nx, you can do this by creating a library.
**Run the following generator to create a library:**
```bash
ng g @nrwl/workspace:lib data
```
The result should look like this:
```treeview
myorg/
├── apps/
│ ├── todos/
│ ├── todos-e2e/
│ └── api/
├── libs/
│ └── data/
│ ├── src/
│ │ ├── lib/
│ │ │ └── data.ts
│ │ └── index.ts
│ ├── jest.conf.js
│ ├── tsconfig.app.json
│ ├── tsconfig.json
│ ├── tsconfig.spec.json
│ └── tslint.json
├── nx.json
├── package.json
├── tools/
├── tsconfig.json
└── tslint.json
```
**Copy the interface into `libs/data/src/lib/data.ts`.**
```typescript
export interface Todo {
title: string;
}
```
## Refactor the API
**Now update `apps/api/src/app/todos.ts` to import the interface:**
```typescript
import { Express } from 'express';
import { Todo } from '@myorg/data';
const todos: Todo[] = [{ title: 'Todo 1' }, { title: 'Todo 2' }];
export function addTodoRoutes(app: Express) {
app.get('/api/todos', (req, resp) => resp.send(todos));
app.post('/api/addTodo', (req, resp) => {
const newTodo = {
title: `New todo ${Math.floor(Math.random() * 1000)}`
};
todos.push(newTodo);
resp.send(newTodo);
});
}
```
## Update the Web Application
**Next import the interface in `apps/todos/src/app/app.element.ts`:**
```typescript jsx
import { Todo } from '@myorg/data';
export class AppElement extends HTMLElement {
todos: Todo[] = [{ title: 'Todo 1' }, { title: 'Todo 2' }];
//...
}
```
Every time you add a new library, you have to restart `ng serve`. **So restart both `ng serve api` and `ng serve todos` and you should see the application running.**
!!!!!
Nx allows you to share code...
!!!!!
Between frontend and backend apps
Between different frontend apps
Between different node apps
| 24.685393 | 388 | 0.632226 | eng_Latn | 0.898384 |
f4e707632e2baa8f38add1f62f3fbf999fa45836 | 143 | md | Markdown | CHANGELOG.md | RaminEsfandiari/python-serverless-eu | e3f373a7003649190ba7fc0aeece968e1b328de4 | [
"MIT"
] | 9 | 2020-08-07T18:04:02.000Z | 2022-02-24T14:34:24.000Z | CHANGELOG.md | RaminEsfandiari/python-serverless-eu | e3f373a7003649190ba7fc0aeece968e1b328de4 | [
"MIT"
] | 1 | 2019-07-30T12:16:24.000Z | 2019-08-02T12:54:45.000Z | CHANGELOG.md | RaminEsfandiari/python-serverless-eu | e3f373a7003649190ba7fc0aeece968e1b328de4 | [
"MIT"
] | 2 | 2020-08-05T10:27:17.000Z | 2022-02-24T14:37:35.000Z | Please see the [releases][releases] page for a changelog.
[releases]: https://github.com/gridsmartercities/python-serverless-template/releases | 47.666667 | 84 | 0.811189 | eng_Latn | 0.781353 |
f4e8320fba2f17b05dda8839de926aae3e7f0ff0 | 8,718 | md | Markdown | docs/rules.md | deep0892/MyRules | 3bd7692843d649aa39df9e3a12eee868ef8085e4 | [
"0BSD"
] | null | null | null | docs/rules.md | deep0892/MyRules | 3bd7692843d649aa39df9e3a12eee868ef8085e4 | [
"0BSD"
] | null | null | null | docs/rules.md | deep0892/MyRules | 3bd7692843d649aa39df9e3a12eee868ef8085e4 | [
"0BSD"
] | null | null | null | # Rules
Rules contain a set of _conditions_ and a single _event_. When the engine is run, each rule condition is evaluated. If the results are truthy, the rule's _event_ is triggered.
## Methods
### constructor([Object options|String json])
Returns a new rule instance
```js
let options = {
conditions: {
all: [
{
fact: 'my-fact',
operator: 'equal',
value: 'some-value'
}
]
},
event: {
type: 'my-event',
params: {
customProperty: 'customValue'
}
},
priority: 1, // optional, default: 1
onSuccess: function (event, almanac) {}, // optional
onFailure: function (event, almanac) {}, // optional
}
let rule = new Rule(options)
```
**options.conditions** : `[Object]` Rule conditions object
**options.event** : `[Object]` Sets the `.on('success')` and `on('failure')` event argument emitted whenever the rule passes. Event objects must have a ```type``` property, and an optional ```params``` property.
**options.priority** : `[Number, default 1]` Dictates when rule should be run, relative to other rules. Higher priority rules are run before lower priority rules. Rules with the same priority are run in parallel. Priority must be a positive, non-zero integer.
**options.onSuccess** : `[Function(Object event, Almanac almanac)]` Registers callback with the rule's `on('success')` listener. The rule's `event` property and the current [Almanac](./almanac.md) are passed as arguments.
**options.onFailure** : `[Function(Object event, Almanac almanac)]` Registers callback with the rule's `on('failure')` listener. The rule's `event` property and the current [Almanac](./almanac.md) are passed as arguments.
### setConditions(Array conditions)
Helper for setting rule conditions. Alternative to passing the `conditions` option to the rule constructor.
### setEvent(Object event)
Helper for setting rule event. Alternative to passing the `event` option to the rule constructor.
### setPriority(Integer priority = 1)
Helper for setting rule priority. Alternative to passing the `priority` option to the rule constructor.
### toJSON(Boolean stringify = true)
Serializes the rule into a JSON string. Often used when persisting rules.
```js
let jsonString = rule.toJSON() // string: '{"conditions":{"all":[]},"priority":50 ...
let rule = new Rule(jsonString) // restored rule; same conditions, priority, event
// without stringifying
let jsonObject = rule.toJSON(false) // object: {conditions:{ all: [] }, priority: 50 ...
```
## Conditions
Rule conditions are a combination of facts, operators, and values that determine whether the rule is a `success` or a `failure`.
### Basic conditions
The simplest form of a condition consists of a `fact`, an `operator`, and a `value`. When the engine runs, the operator is used to compare the fact against the value.
```js
// my-fact <= 1
let rule = new Rule({
conditions: {
all: [
{
fact: 'my-fact',
operator: 'lessThanInclusive',
value: 1
}
]
}
})
```
See the [hello-world](../examples/01-hello-world.js) example.
### Boolean expressions: `all` and `any`
Each rule's conditions *must* have either an `all` or an `any` operator at its root, containing an array of conditions. The `all` operator specifies that all conditions contained within must be truthy for the rule to be considered a `success`. The `any` operator only requires one condition to be truthy for the rule to succeed.
```js
// all:
let rule = new Rule({
conditions: {
all: [
{ /* condition 1 */ },
{ /* condition 2 */ },
{ /* condition n */ },
]
}
})
// any:
let rule = new Rule({
conditions: {
any: [
{ /* condition 1 */ },
{ /* condition 2 */ },
{ /* condition n */ },
{
all: [ /* more conditions */ ]
}
]
}
})
```
Notice in the second example how `all` and `any` can be nested within one another to produce complex boolean expressions. See the [nested-boolean-logic](../examples/02-nested-boolean-logic.js) example.
### Condition helpers: `params`
Sometimes facts require additional input to perform calculations. For this, the `params` property is passed as an argument to the fact handler. `params` essentially functions as fact arguments, enabling fact handlers to be more generic and reusable.
```js
// product-price retrieves any product's price based on the "productId" in "params"
engine.addFact('product-price', function (params, almanac) {
return productLoader(params.productId) // loads the "widget" product
.then(product => product.price)
})
// identifies whether the current widget price is above $100
let rule = new Rule({
conditions: {
all: [
{
fact: 'product-price',
params: {
productId: 'widget' // specifies which product to load
},
operator: 'greaterThan',
value: 100
}
]
}
})
```
See the [dynamic-facts](../examples/03-dynamic-facts) example
### Condition helpers: `path`
In the `params` example above, the dynamic fact handler loads an object, then returns a specific object property. For more complex data structures, writing a separate fact handler for each object property can sometimes become unwieldy.
To alleviate this overhead, a `path` property is provided for traversing objects and arrays returned by facts. The example above becomes simpler, and only one fact handler must be written by the developer to handle any number of properties.
```js
// product-price retrieves any product's price based on the "productId" in "params"
engine.addFact('product-price', function (params, almanac) {
// NOTE: `then` is not required; .price is specified via "path" below
return productLoader(params.productId)
})
// identifies whether the current widget price is above $100
let rule = new Rule({
conditions: {
all: [
{
fact: 'product-price',
params: {
productId: 'widget',
// Complex accessor are supported, e.g. '.profile.addresses[0].city'
path: '.price'
},
operator: 'greaterThan',
value: 100
}
]
}
})
```
See the [fact-dependency](../examples/04-fact-dependency.js) example
### Comparing facts
Sometimes it is necessary to compare facts against others facts. This can be accomplished by nesting the second fact within the `value` property. This second fact has access to the same `params` and `path` helpers as the primary fact.
```js
// identifies whether the current widget price is above a maximum
let rule = new Rule({
conditions: {
all: [
// widget-price > budget
{
fact: 'product-price',
params: {
productId: 'widget',
path: '.price'
},
operator: 'greaterThan',
// "value" contains a fact
value: {
fact: 'budget' // "params" and "path" helpers are available as well
}
}
]
}
})
```
See the [fact-comparison](../examples/08-fact-comparison.js) example
## Events
Listen for `success` and `failure` events emitted when rule is evaluated.
#### ```rule.on('success', Function(Object event, Almanac almanac))```
```js
// whenever rule is evaluated and the conditions pass, 'success' will trigger
rule.on('success', function(event, almanac) {
console.log(event) // { type: 'my-event', params: { id: 1 }
})
```
#### ```rule.on('failure', Function(Object event, Almanac almanac))```
Companion to `success`, except fires when the rule fails.
```js
engine.on('failure', function(event, almanac) {
console.log(event) // { type: 'my-event', params: { id: 1 }
})
```
## Operators
Each rule condition must begin with a boolean operator(```all``` or ```any```) at its root.
The ```operator``` compares the value returned by the ```fact``` to what is stored in the ```value``` property. If the result is truthy, the condition passes.
### String and Numeric operators:
```equal``` - _fact_ must equal _value_
```notEqual``` - _fact_ must not equal _value_
_these operators use strict equality (===) and inequality (!==)_
### Numeric operators:
```lessThan``` - _fact_ must be less than _value_
```lessThanInclusive```- _fact_ must be less than or equal to _value_
```greaterThan``` - _fact_ must be greater than _value_
```greaterThanInclusive```- _fact_ must be greater than or equal to _value_
### Array operators:
```in``` - _fact_ must be included in _value_ (an array)
```notIn``` - _fact_ must not be included in _value_ (an array)
```contains``` - _fact_ (an array) must include _value_
```doesNotContain``` - _fact_ (an array) must not include _value_
| 31.586957 | 330 | 0.665405 | eng_Latn | 0.989482 |
f4e8535f1a329091a5592c5cc85ff447f6cdd545 | 91 | mkd | Markdown | README.mkd | bwhmather/rust-btree-index | 16fca4d2d726005cbc88bf8812f7a15ca56ec943 | [
"Apache-2.0",
"MIT"
] | null | null | null | README.mkd | bwhmather/rust-btree-index | 16fca4d2d726005cbc88bf8812f7a15ca56ec943 | [
"Apache-2.0",
"MIT"
] | null | null | null | README.mkd | bwhmather/rust-btree-index | 16fca4d2d726005cbc88bf8812f7a15ca56ec943 | [
"Apache-2.0",
"MIT"
] | null | null | null | # BTree Index
A one-to-many index datastructure built around the standard library b-tree.
| 22.75 | 75 | 0.791209 | eng_Latn | 0.984134 |
f4e92e08efb0a722acc8733aece0399f16f9d92a | 6,370 | md | Markdown | translations/de-DE/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md | JoyChannel/docs | 2d85af3d136df027c5e9230cac609b3712abafb3 | [
"CC-BY-4.0",
"MIT"
] | 17 | 2021-01-05T16:29:05.000Z | 2022-02-26T09:08:44.000Z | translations/de-DE/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md | moonlightnigh/docs | 37b2dc7444c4f38bd089298a097a755dd0df46ab | [
"CC-BY-4.0",
"MIT"
] | 116 | 2021-10-13T00:58:04.000Z | 2022-03-19T23:23:44.000Z | translations/de-DE/content/admin/enterprise-management/updating-the-virtual-machine-and-physical-resources/upgrade-requirements.md | moonlightnigh/docs | 37b2dc7444c4f38bd089298a097a755dd0df46ab | [
"CC-BY-4.0",
"MIT"
] | 3 | 2021-08-31T03:18:06.000Z | 2021-10-30T17:49:09.000Z | ---
title: Upgrade-Anforderungen
intro: 'Lesen Sie vor dem Upgrade von {% data variables.product.prodname_ghe_server %} diese Empfehlungen und Anforderungen zum Planen Ihrer Upgrade-Strategie.'
redirect_from:
- /enterprise/admin/installation/upgrade-requirements
- /enterprise/admin/guides/installation/finding-the-current-github-enterprise-release/
- /enterprise/admin/enterprise-management/upgrade-requirements
- /admin/enterprise-management/upgrade-requirements
versions:
enterprise-server: '*'
type: reference
topics:
- Enterprise
- Upgrades
---
{% note %}
**Hinweise:**
- Um ein Upgrade von {% data variables.product.prodname_enterprise %} 11.10.348 bis {% data variables.product.current-340-version %} durchzuführen, müssen Sie zunächst zu {% data variables.product.prodname_enterprise %} 2.1.23 migrieren. Weitere Informationen finden Sie unter „[{% data variables.product.prodname_enterprise %} von 11.10.x zu 2.1.23 migrieren](/enterprise/{{ currentVersion }}/admin/guides/installation/migrating-from-github-enterprise-11-10-x-to-2-1-23)“.
- Upgrade-Pakete stehen unter [enterprise.github.com](https://enterprise.github.com/releases) für unterstützte Versionen zur Verfügung. Verifizieren Sie die Verfügbarkeit der Upgrade-Pakete, die Sie zum Abschließen des Upgrades benötigen. Wenden Sie sich an {% data variables.contact.contact_ent_support %}, falls ein Paket nicht verfügbar ist.
- Wenn Sie {% data variables.product.prodname_ghe_server %} Clustering verwenden, finden Sie im {% data variables.product.prodname_ghe_server %} Clustering-Leitfaden unter „[Cluster-Upgrade](/enterprise/{{ currentVersion }}/admin/guides/clustering/upgrading-a-cluster/)“ Clustering-spezifische Anweisungen.
- Die Versionshinweise für {% data variables.product.prodname_ghe_server %} enthalten eine umfassende Liste der neuen Features jeder Version von {% data variables.product.prodname_ghe_server %}. Weitere Informationen finden Sie auf der [Veröffentlichungsseite](https://enterprise.github.com/releases).
{% endnote %}
### Empfehlungen
- Sie sollten möglichst wenig Upgrades in Ihren Upgrade-Prozess einbeziehen. Anstatt beispielsweise ein Upgrade von {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.supported[2] }} auf {{ enterpriseServerReleases.supported[1] }} auf {{ enterpriseServerReleases.latest }} vorzunehmen, können Sie ein Upgrade von {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.supported[2] }} auf {{ enterpriseServerReleases.latest }} vornehmen.
- Wenn Sie mehrere Versionen zurückliegen, sollten Sie {% data variables.product.product_location %} so weit wie möglich mit jedem Schritt Ihres Upgrade-Prozesses upgraden. Wenn Sie die nach Möglichkeit neueste Version für jedes Upgrade verwenden, können Sie von Leistungsverbesserungen und Bug-Korrekturen profitieren. So können Sie beispielsweise ein Upgrade von {% data variables.product.prodname_enterprise %} 2.7 auf 2.8 auf 2.10 vornehmen. Beim Upgrade von {% data variables.product.prodname_enterprise %} 2.7 auf 2.9 auf 2.10 wird im zweiten Schritt jedoch eine neuere Version verwendet.
- Verwenden Sie beim Upgraden die neueste Patch-Veröffentlichung. {% data reusables.enterprise_installation.enterprise-download-upgrade-pkg %}
- Verwenden Sie eine Testinstanz zum Testen der Upgrade-Schritte. Weitere Informationen finden Sie unter „[Testinstanz einrichten](/enterprise/{{ currentVersion }}/admin/guides/installation/setting-up-a-staging-instance/)“.
- When running multiple upgrades, wait at least 24 hours between feature upgrades to allow data migrations and upgrade tasks running in the background to fully complete.
### Anforderungen
- Sie müssen ein Upgrade von einer Feature-Veröffentlichung vornehmen, die **höchstens** zwei Versionen zurückliegt. Wenn Sie beispielsweise ein Upgrade auf {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.latest }} vornehmen, müssen Sie {% data variables.product.prodname_enterprise %} {{ enterpriseServerReleases.supported[1] }} oder {{ enterpriseServerReleases.supported[2] }} verwenden.
- {% data reusables.enterprise_installation.hotpatching-explanation %}
- Ein Hotpatch kann Ausfallzeiten nach sich ziehen, falls für die betroffenen Dienste (z. B. der Kernel, MySQL oder ElasticSearch) ein VM- oder Dienstneustart erforderlich ist. Sie werden benachrichtigt, falls ein Neustart erforderlich ist. Sie können den Neustart zu einem späteren Zeitpunkt abschließen.
- Beim Upgrade mittels Hotpatching muss zusätzlicher Root-Storage verfügbar sein, da bis zum Abschluss des Upgrades mehrere Versionen bestimmter Dienste installiert werden. Preflight-Checks benachrichtigen Sie, falls nicht genügend Root-Disk-Storage verfügbar ist.
- Beim Upgrade mittels Hotpatching darf Ihre Instanz keine zu große Auslastung aufweisen, da sich dies ggf. auf den Hotpatching-Prozess auswirkt. Bei den Vorflugprüfungen wird die durchschnittliche Auslastung berücksichtigt und das Upgrade schlägt fehl, wenn die durchschnittliche Auslastung zu hoch ist.- Der Upgrade-Vorgang auf {% data variables.product.prodname_ghe_server %} 2.17 migriert Deine Überwachungsprotokolle von Elasticsearch zu MySQL. Diese Migration erhöht die erforderliche Dauer und den Speicherplatz, die bzw. der zum Wiederherstellen eines Snapshots erforderlich ist. Überprüfen Sie vor der Migration die Anzahl an Bytes in Ihren ElasticSearch-Auditprotokollindizes. Führen Sie dazu den folgenden Befehl aus:
``` shell
curl -s http://localhost:9201/audit_log/_stats/store | jq ._all.primaries.store.size_in_bytes
```
Anhand der Zahl können Sie schätzen, wie viel Speicherplatz die MySQL-Auditprotokolle benötigen werden. Darüber hinaus überwacht das Skript den freien Speicherplatz, während der Import ausgeführt wird. Die Überwachung dieser Zahl ist besonders nützlich, wenn der freie Speicherplatz dem für die Migration erforderlichen Speicherplatz nahekommt.
{% data reusables.enterprise_installation.upgrade-hardware-requirements %}
### Nächste Schritte:
Nachdem Sie diese Empfehlungen und Anforderungen gelesen haben, können Sie {% data variables.product.prodname_ghe_server %} upgraden. Weitere Informationen finden Sie unter „[Upgrade von {% data variables.product.prodname_ghe_server %}](/enterprise/{{ currentVersion }}/admin/guides/installation/upgrading-github-enterprise-server/)“.
| 122.5 | 728 | 0.809419 | deu_Latn | 0.957212 |
f4e9fa419ea6ba94904d9189d4fb644369a9e33a | 1,640 | md | Markdown | _projects/3-CI.md | sumagavi/sumadevanga.github.io | abe562888328bbd0b5e119f360f133b483cfae2c | [
"MIT"
] | null | null | null | _projects/3-CI.md | sumagavi/sumadevanga.github.io | abe562888328bbd0b5e119f360f133b483cfae2c | [
"MIT"
] | null | null | null | _projects/3-CI.md | sumagavi/sumadevanga.github.io | abe562888328bbd0b5e119f360f133b483cfae2c | [
"MIT"
] | null | null | null | ---
title: "Studying the design, implementation and outcomes of group-based clinical interventions for acquired neurogenic communication disorders"
collection: projects
permalink: /projects/3-CI
---
Drawing on the power of social connections, group treatments have emerged to facilitate better generalization of language to everyday communication and improve life participation, while being cost-effective. We are designing novel group-based clinical interventions for acquired neurogenic communication disorders and investigating the power of university-based clinical programs that offer group treatments.
## Completed work:
### Design a pilot retrospective study to examine the types of outcome measures employed in the Aphasia Communication Enhancement program at WMU, and analyze their outcomes for participants with aphasia and their care partners
### Related Publications:
1. Devanga, S. R., Pollens, R., & Glista, S. (In press). Towards developing outcome measures in university-based aphasia programs: Perspectives from the Aphasia Communication Enhancement (ACE) program. Perspectives of ASHA Special Interest Groups.
## Work in progress:
### Design and assess the feasibility of Group Collaborative Referencing Intrervention (CRI) for aphasia
### Funding:
Faculty Research and Creative Activities Award (FRACAA), Western Michigan University ($10,000) (2021-22). Title of the study: Feasibility of Group Collaborative Referencing Intervention for Aphasia. PI: Suma Devanga
## Targeted Goal:
Design and implement a university-based student-led aphasia group treatment study to analyze the clinical and functional outcomes
| 63.076923 | 408 | 0.812805 | eng_Latn | 0.989262 |
f4ea9786f81c96c760f7e18d9b92e84e3273cc00 | 3,854 | md | Markdown | docs/machine-learning/administration/extended-events-predict-tsql.md | Yorihito/sql-docs.ja-jp | 821ae5e0cb38fcfd3ac65431dad0d88b1855a6ad | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/machine-learning/administration/extended-events-predict-tsql.md | Yorihito/sql-docs.ja-jp | 821ae5e0cb38fcfd3ac65431dad0d88b1855a6ad | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/machine-learning/administration/extended-events-predict-tsql.md | Yorihito/sql-docs.ja-jp | 821ae5e0cb38fcfd3ac65431dad0d88b1855a6ad | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: 拡張イベントを使用した T-SQL の監視
description: 拡張イベントを使用して、SQL Server Machine Learning Services で PREDICT T-SQL ステートメントを監視およびトラブルシューティングする方法について説明します。
ms.prod: sql
ms.technology: machine-learning-services
ms.date: 09/24/2019
ms.topic: how-to
author: dphansen
ms.author: davidph
ms.custom: seo-lt-2019
monikerRange: '>=sql-server-2017||>=sql-server-linux-ver15||=azuresqldb-mi-current||=sqlallproducts-allversions'
ms.openlocfilehash: bbe54a44113ebadc07c837887f0d92e7bfb44cb4
ms.sourcegitcommit: 22102f25db5ccca39aebf96bc861c92f2367c77a
ms.translationtype: HT
ms.contentlocale: ja-JP
ms.lasthandoff: 10/16/2020
ms.locfileid: "92115398"
---
# <a name="monitor-predict-t-sql-statements-with-extended-events-in-sql-server-machine-learning-services"></a>SQL Server Machine Learning Services の拡張イベントで PREDICT T-SQL ステートメントを監視する
[!INCLUDE [SQL Server 2017 SQL MI](../../includes/applies-to-version/sqlserver2017-asdbmi.md)]
拡張イベントを使用して、SQL Server Machine Learning Services で [PREDICT](../../t-sql/queries/predict-transact-sql.md) T-SQL ステートメントを監視およびトラブルシューティングする方法について説明します。
## <a name="table-of-extended-events"></a>拡張イベントの表
次の拡張イベントは、[PREDICT](../../t-sql/queries/predict-transact-sql.md) T-SQL ステートメントをサポートするすべてのバージョンの SQL Server で使用できます。
| name | object_type | description |
|----------------------------|-------------|-------------|
| predict_function_completed | イベント | 組み込み実行時間のブレークダウン|
| predict_model_cache_hit | イベント | モデルが PREDICT 関数モデル キャッシュから取得されるときに発生します。 PREDICT 関数モデル キャッシュが原因で発生した問題についてトラブルシューティングを行うには、このイベントを他の predict_model_cache_* イベントと共に使用します。|
| predict_model_cache_insert | イベント | モデルが PREDICT 関数モデル キャッシュに挿入されるときに発生します。 PREDICT 関数モデル キャッシュが原因で発生した問題についてトラブルシューティングを行うには、このイベントを他の predict_model_cache_* イベントと共に使用します。 |
| predict_model_cache_miss | イベント | モデルが PREDICT 関数モデル キャッシュで見つからないときに発生します。 このイベントが頻繁に発生する場合、SQL Server がより多くのメモリを必要としていることを示している可能性があります。 PREDICT 関数モデル キャッシュが原因で発生した問題についてトラブルシューティングを行うには、このイベントを他の predict_model_cache_* イベントと共に使用します。|
| predict_model_cache_remove | イベント | モデルが PREDICT 関数のモデル キャッシュから削除されるときに発生します。 PREDICT 関数モデル キャッシュが原因で発生した問題についてトラブルシューティングを行うには、このイベントを他の predict_model_cache_* イベントと共に使用します。|
## <a name="query-for-related-events"></a>関連イベントをクエリします。
これらのイベントに対して返されたすべての列の一覧を表示するには、SQL Server Management Studio で次のクエリを実行します。
```sql
SELECT *
FROM sys.dm_xe_object_columns
WHERE object_name LIKE 'predict%'
```
## <a name="examples"></a>例
PREDICT を使用してスコアリング セッションのパフォーマンスに関する情報を取得するには次の手順を実行します。
1. Management Studio またはサポートされている別の[ツール](../../relational-databases/extended-events/extended-events-tools.md)を使用して、新しい拡張イベント セッションを作成します。
2. イベント `predict_function_completed` と `predict_model_cache_hit` をセッションに追加します。
3. 拡張イベント セッションを開始します。
4. PREDICT を使用するクエリを実行します。
結果で次の列を確認します。
+ `predict_function_completed` の値は、モデルの読み込みとスコアリングのためにクエリが費やした時間を示します。
+ `predict_model_cache_hit` のブール値は、クエリがキャッシュされたモデルを使用したかどうかを示します。
### <a name="native-scoring-model-cache"></a>ネイティブ スコアリング モデル キャッシュ
PREDICT 固有のイベントに加えて、次のクエリを使用して、キャッシュされたモデルとキャッシュの使用に関する詳細情報を取得できます。
ネイティブ スコアリング モデル キャッシュの表示:
```sql
SELECT *
FROM sys.dm_os_memory_clerks
WHERE type = 'CACHESTORE_NATIVESCORING';
```
モデル キャッシュ内のオブジェクトの表示:
```sql
SELECT *
FROM sys.dm_os_memory_objects
WHERE TYPE = 'MEMOBJ_NATIVESCORING';
```
## <a name="next-steps"></a>次のステップ
拡張イベント (XEvent と呼ばれることもあります) の詳細と、セッションのイベントを追跡する方法の詳細については、次の記事を参照してください。
+ [SQL Server Machine Learning Services の拡張イベントで Python および R のスクリプトを監視する](extended-events.md)
+ [拡張イベントの概念とアーキテクチャ](../../relational-databases/extended-events/extended-events.md)
+ [SSMS でのイベント キャプチャの設定](../../relational-databases/extended-events/quick-start-extended-events-in-sql-server.md)
+ [SQL Server オブジェクト エクスプローラーでのイベント セッションの管理](../../relational-databases/extended-events/manage-event-sessions-in-the-object-explorer.md) | 44.298851 | 244 | 0.788012 | yue_Hant | 0.74724 |
f4eaefd397b3c859cf5be5ff16ba1363303d6a33 | 1,858 | md | Markdown | docs/api-reference/arcgis/deck-layer.md | CodeLabs-Hubble-gl/deck.gl | 24694da483acdd7ee27428a1c3fc48645c2a6eee | [
"MIT"
] | null | null | null | docs/api-reference/arcgis/deck-layer.md | CodeLabs-Hubble-gl/deck.gl | 24694da483acdd7ee27428a1c3fc48645c2a6eee | [
"MIT"
] | null | null | null | docs/api-reference/arcgis/deck-layer.md | CodeLabs-Hubble-gl/deck.gl | 24694da483acdd7ee27428a1c3fc48645c2a6eee | [
"MIT"
] | null | null | null | # DeckLayer
This class inherits from the ArcGIS [Layer](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-Layer.html) class and can be added to maps created with the ArcGIS API for JavaScript.
`DeckLayer` is only available when `loadArcGISModules()` is resolved. At the moment, it only supports 2D integration.
## Usage
```js
import {loadArcGISModules} from '@deck.gl/arcgis';
loadArcGISModules([
'esri/Map',
'esri/views/MapView'
]).then(({DeckLayer, modules}) => {
const [ArcGISMap, MapView] = modules;
const layer = new DeckLayer({
'deck.layers': [
// deck.gl layers
]
});
const mapView = new MapView({
container: "viewDiv",
map: new ArcGISMap({
basemap: "dark-gray-vector",
layers: [layer]
}),
center: [0.119, 52.205],
zoom: 5
});
});
```
## Constructor
```js
new DeckLayer(props);
```
Inherits all properties from the base [Layer](https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-Layer.html#properties-summary) class.
Property names that start with `deck.` are forwarded to a `Deck` instance. The following [Deck](/docs/api-reference/core/deck.md) props are supported:
- `deck.layers`
- `deck.layerFilter`
- `deck.parameters`
- `deck.effects`
- `deck.pickingRadius`
- `deck.onBeforeRender`
- `deck.onAfterRender`
- `deck.onClick`
- `deck.onHover`
- `deck.onDragStart`
- `deck.onDrag`
- `deck.onDragEnd`
- `deck.onError`
- `deck.debug`
- `deck.drawPickingColors`
## Members
##### `deck`
An ArcGIS [Accessor](https://developers.arcgis.com/javascript/latest/api-reference/esri-core-Accessor.html) that stores Deck props. The props can be updated after the layer construction:
```js
// Update deck layers
layer.deck.layers = [...]);
// Update multiple deck props
layer.deck.set({
layers: [...],
pickingRadius: 5,
...
});
```
| 23.225 | 204 | 0.689451 | eng_Latn | 0.368465 |
f4eb8107c08ff327a2b48f8c611a76498722f6ad | 2,898 | md | Markdown | node_modules/primer-cards/CHANGELOG.md | tangnel/opensource.guide | f3f3cfaf60bcd96e3e29226da731e9060afc09ce | [
"CC-BY-4.0"
] | 5 | 2020-03-12T08:14:04.000Z | 2021-03-08T12:43:59.000Z | node_modules/primer-cards/CHANGELOG.md | tangnel/opensource.guide | f3f3cfaf60bcd96e3e29226da731e9060afc09ce | [
"CC-BY-4.0"
] | 87 | 2018-05-29T07:18:10.000Z | 2021-07-06T07:15:06.000Z | node_modules/primer-cards/CHANGELOG.md | tangnel/opensource.guide | f3f3cfaf60bcd96e3e29226da731e9060afc09ce | [
"CC-BY-4.0"
] | 7 | 2018-06-07T16:59:15.000Z | 2020-03-01T01:54:06.000Z | # v0.1.2
* Bump all the version numbers for readme - Mu-An Chiou [github/github@a9d152f](https://github.com/github/github/commit/a9d152f)
* Fix all the travis badge URL - Mu-An Chiou [github/github@9cd6d84](https://github.com/github/github/commit/9cd6d84)
# v0.1.1
* bumping the version - Jon Rohan [github/github@4a72b25](https://github.com/github/github/commit/4a72b25)
* Pointing main js file to build - Jon Rohan [github/github@3575651](https://github.com/github/github/commit/3575651)
* don't change the versions yet - Jon Rohan [github/github@6bebcff](https://github.com/github/github/commit/6bebcff)
* Bumping version - Jon Rohan [github/github@df8b91c](https://github.com/github/github/commit/df8b91c)
* Cleaning up devDependencies versions and simplifying npm scripts - Jon Rohan [github/github@2c42571](https://github.com/github/github/commit/2c42571)
* Sorting and table objects. We also don't need homepage - Jon Rohan [github/github@798629d](https://github.com/github/github/commit/798629d)
* Removing duplicate headers - Jon Rohan [github/github@225cee1](https://github.com/github/github/commit/225cee1)
# v0.1.0
* Rename repository with prefix primer- - Jon Rohan [github/github@ec8774a](https://github.com/github/github/commit/ec8774a)
* Update border radius for cards because it is not the same as box. - Patrick Marsceill [github/github@9dc19b3](https://github.com/github/github/commit/9dc19b3)
* fix a typo - Patrick Marsceill [github/github@24acfeb](https://github.com/github/github/commit/24acfeb)
* Update the names in the README files - Patrick Marsceill [github/github@75fed58](https://github.com/github/github/commit/75fed58)
* Update pathing on cards README - Patrick Marsceill [github/github@443f2e2](https://github.com/github/github/commit/443f2e2)
* Update names for npm publising - Patrick Marsceill [github/github@451f97a](https://github.com/github/github/commit/451f97a)
* Fix import path across all scss files - Patrick Marsceill [github/github@a566f31](https://github.com/github/github/commit/a566f31)
* RIP unused styles - Patrick Marsceill [github/github@31dc325](https://github.com/github/github/commit/31dc325)
* fix cards - Patrick Marsceill [github/github@a6beedf](https://github.com/github/github/commit/a6beedf)
* Add cards to docs - Sophie Shepherd [github/github@b421a08](https://github.com/github/github/commit/b421a08)
* Fix variable collisions and add basecoat to site to test sass compilation errors - Patrick Marsceill [github/github@c73eee3](https://github.com/github/github/commit/c73eee3)
* Remove basecoat - Patrick Marsceill [github/github@1b1503d](https://github.com/github/github/commit/1b1503d)
* prefix bc => marketing - Patrick Marsceill [github/github@04d509a](https://github.com/github/github/commit/04d509a)
* Cards - Patrick Marsceill [github/github@306cbfc](https://github.com/github/github/commit/306cbfc) | 93.483871 | 176 | 0.773292 | zul_Latn | 0.140444 |
f4eb94aa46c06044e0dceb71077eb6f6351f2eae | 1,988 | md | Markdown | src/FrontEnd/Vue/vue1.md | HarryXiong24/MyBlog | 7a6ee1d82213539229fd8b185fe890053fcd0918 | [
"MIT"
] | 4 | 2020-06-05T07:48:01.000Z | 2021-07-07T08:07:55.000Z | src/FrontEnd/Vue/vue1.md | HarryXiong24/MyBlog | 7a6ee1d82213539229fd8b185fe890053fcd0918 | [
"MIT"
] | 7 | 2021-03-01T21:14:34.000Z | 2022-02-27T05:36:32.000Z | src/FrontEnd/Vue/vue1.md | HarryXiong24/MyBlog | 7a6ee1d82213539229fd8b185fe890053fcd0918 | [
"MIT"
] | null | null | null | ---
icon: vue
category: Web前端
tags:
- Vue
- MVVM
- Vuex
- Vue-router
- Vue源码分析
time: 2020-6-18
footer: How easy to do
title: 1.Vue简介
---
## Vue 简介
### 1.1 Vue 的特性
**Vue 是一套用于构建用户界面的渐进式框架,与其它大型框架不同的是,Vue 被设计为可以自底向上逐层应用,Vue 拥有以下特性:**
- 组件化思想
- 模板的使用和数据渲染非常灵活，层次结构鲜明
- 简单的语法并能够简单快速构建一个项目
- 轻量级，体积小渲染速度更快
- Vue 采用的脚手架工具为 vue-cli
- 初期是尤雨溪维护，现在有加入的团队组织个人提供技术一同维护迭代更新
- Vue 中指令和组件分得更清晰。指令只封装 DOM 操作,而组件代表一个自给自足的独立单元,都拥有有自己的视图样式和数据逻辑
### 1.2 Vue 知识框架
### 1.3 开发准备
#### 1.3.1 下载 Node.js
去 Node.js 的官网下载最新版的 node,需要用到其包管理工具 npm ([Node.js 官网](https://nodejs.org/en/))
#### 1.3.2 配置淘宝镜像
因为 npm 是国外的,在国内用会特别慢,所以需要先用淘宝的 cnpm 代替 npm
在命令行窗口输入 npm install -g cnpm --registry=https://registry.npm.taobao.org 配置淘宝镜像
#### 1.3.3 vue-cli 脚手架
vue-cli 是一个基于 vue 的构建工具,用于搭建 vue 项目的环境,有着兼容,方便,快速的优点,能够完全遵循前后端分离的原则,用 vue 开发单网页项目(SPA)的能力尤其的好
**注:**可以不用脚手架(vue-cli)就可以基于 webpack 打包工具 ,webpack 最终会把整个项目打包成一个 js 文件但需要自己进行配置各个版本兼容问题,正因为这样,前端有一个专门的配置工程师
#### 1.3.4 使用 vue-cli
在命令行窗口输入 cnpm i -g vue-cli **全局安装 vue-cli 脚手架**
Vue-cli 要全局安装
**注:**安装完成后可以使用 vue -V 查看是否安装成功
**安装项目文件**
先到项目文件夹,打开命令行窗口输入 vue init webpack 项目文件夹名(不输入则就是在该文件夹里创建)
**运行项目文件**
在项目文件中使用 npm run dev 运行项目文件
**打包项目**
在项目文件夹中运行 npm run build 将项目打包 ,打包后的文件将会保存在该文件的 list 文件夹中
npm run build --report 生成打包视图，可视化显示所有包在项目中占的大小
生产环境打包发布
npm run build
npm install -g serve
serve dist
#### 1.3.5 ESLint
说明：
1. ESLint 是一个代码规范检查工具
2. 它定义了很多特定的规则, 一旦你的代码违背了某一规则,eslint 会作出非常有用的提示
3. 官网:http://eslint.org/
4. 基本已替代以前的 JSLint
ESLint 提供以下支持：
1. ES
2. JSX
3. style 检查
4. 自定义错误和提示
ESLint 提供以下几种校验：
1. 语法错误校验
2. 不重要或丢失的标点符号，如分号
3. 没法运行到的代码块（使用过 WebStorm 的童鞋应该了解）
4. 未被使用的参数提醒
5. 确保样式的统一规则，如 sass 或者 less
6. 检查变量的命名
规则的错误等级有三种：
1. 0：关闭规则。
2. 1：打开规则，并且作为一个警告（信息打印黄色字体）
3. 2：打开规则，并且作为一个错误（信息打印红色字体）
相关配置文件
1. eslintrc.js: 全局规则配置文件 'rules':{ 'no-new':1 }
2. 在 js/vue 文件中修改局部规则 /_eslint-disableno-new_/ newVue({ el:'body', components:{App} })
3. eslintignore: 指令检查忽略的文件 _.js _.vue
| 14.835821 | 106 | 0.713783 | yue_Hant | 0.68318 |
f4ec6ac0b62e093c97800358f9f3977c55c5dc37 | 7,240 | md | Markdown | docs/framework/wcf/feature-details/best-practices-for-reliable-sessions.md | v-maudel/docs-1 | f849afb0bd9a505311e7aec32c544c3169edf1c5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/wcf/feature-details/best-practices-for-reliable-sessions.md | v-maudel/docs-1 | f849afb0bd9a505311e7aec32c544c3169edf1c5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/wcf/feature-details/best-practices-for-reliable-sessions.md | v-maudel/docs-1 | f849afb0bd9a505311e7aec32c544c3169edf1c5 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: "Best Practices for Reliable Sessions"
ms.custom: ""
ms.date: "03/30/2017"
ms.prod: ".net-framework"
ms.reviewer: ""
ms.suite: ""
ms.technology:
- "dotnet-clr"
ms.tgt_pltfrm: ""
ms.topic: "article"
ms.assetid: b94f6e01-8070-40b6-aac7-a2cb7b4cb4f2
caps.latest.revision: 6
author: "dotnet-bot"
ms.author: "dotnetcontent"
manager: "wpickett"
ms.workload:
- "dotnet"
---
# Best Practices for Reliable Sessions
This topic discusses best practices for reliable sessions.
## Setting MaxTransferWindowSize
Reliable sessions in [!INCLUDE[indigo1](../../../../includes/indigo1-md.md)] use a transfer window to hold messages on the client and service. The configurable property <xref:System.ServiceModel.Channels.ReliableSessionBindingElement.MaxTransferWindowSize%2A> indicates how many messages the transfer window can hold.
On the sender, this indicates how many messages the transfer window can hold while waiting for acknowledgements; on the receiver, it indicates how many messages to buffer for the service.
Choosing the right size impacts the efficiency of the network and the optimal capacity of the service. The following sections detail what to consider when choosing a value for this property and the impact of the value.
The default transfer window size is eight messages.
### Efficient use of the network
In this context, the term *network* corresponds to everything used as the basis of communication between a client (sender) and a service (receiver). This includes the transport connections and any intermediary or bridges in between, including SOAP routers or HTTP proxies/firewalls.
Efficient use of the network ensures that network capacity is fully used. Both the amount of data that can be transferred per second over the network (*data rate*) and the time it takes to transfer data from the sender to the receiver (*latency*) impact how effectively the network is utilized.
On the sender, the property <xref:System.ServiceModel.Channels.ReliableSessionBindingElement.MaxTransferWindowSize%2A> indicates how many messages its transfer window can hold while waiting for acknowledgements. If the network latency is high and in order to ensure a responsive sender and effective network utilization, you should increase the transfer window size.
For example even if the sender keeps up with data rate, latency could be high if several intermediaries exist between the sender and receiver or the data must pass through a lossy intermediary or network. Thus, the sender has to wait for acknowledgements for the messages in its transfer window before accepting new messages to send on the wire. The smaller the buffer with high latency, the less effective the network utilization. On the other hand, too high a transfer window size may impact the service because the service may need to catch up to the high rate of data sent by the client.
### Running the service to capacity
As much as the network is used efficiently, ideally you also want the service to run at optimal capacity. The transfer window size property on the receiver indicates how many messages the receiver can buffer. This message buffering helps not only the network flow control but also enables the service to run to full capacity. For example if the buffer is one message and messages arrive faster than the service can process them, then the network might drop messages and capacity might be wasted or underutilized.
Using a buffer increases the availability of the service as it concurrently receives and buffers a message while processing the previously received messages.
We recommended that you use the same `MaxTransferWindowSize` on both the sender and receiver.
### Enabling flow control
*Flow control* is a mechanism that ensures that the sender and receiver keep pace with each other, that is, the messages are consumed and acted upon as fast as they're produced. The transfer window size on the client and service ensures that the sender and receiver are within a reasonable window of synchronization.
We highly recommended that you set the property <xref:System.ServiceModel.Channels.ReliableSessionBindingElement.FlowControlEnabled%2A> to `true` when you're using a reliable session between a [!INCLUDE[indigo2](../../../../includes/indigo2-md.md)] client and a [!INCLUDE[indigo2](../../../../includes/indigo2-md.md)] service.
## Setting MaxPendingChannels
When writing a service that enables reliable session communication from different clients, it's possible to have many clients establish a reliable session to the service at the same time. The response of the service in these situations depends on the `MaxPendingChannels` property.
When the sender creates a reliable session channel to a receiver, a handshake between them establishes a reliable session. After the reliable session is established, the channel is put in a pending channel queue for acceptance by the service. The `MaxPendingChannels` property indicates how many channels can be in this state.
It's possible for the service to be in a state where it can't accept more channels. If the queue is full, an attempt to establish a reliable session is rejected, and the client must retry.
It's also possible that the pending channels in the queue remain in the queue for a longer duration. In the meantime, an inactivity timeout on the reliable session may occur, causing the channel to transition to a faulted state.
When writing a service that services multiple clients simultaneously, you should set a value that's suitable for your needs. Setting too high a value for the `MaxPendingChannels` property impacts your working set.
The default value for <xref:System.ServiceModel.Channels.ReliableSessionBindingElement.MaxPendingChannels%2A> is four channels.
## Reliable sessions and hosting
When web hosting a service that uses reliable sessions, you should keep the following important considerations in mind:
- Reliable sessions are stateful, and state is maintained in the AppDomain. This means that all messages that are part of a reliable session must be processed in the same AppDomain. Web farms and web gardens where the size of the farm or garden is greater than one node can't guarantee this constraint.
- Reliable sessions using dual HTTP channels (for example, using `WsDualHttpBinding`) can require more than the default of two HTTP connections per-client. This means a duplex reliable session can require up to two connections each way because concurrent application and protocol messages may be transferring each way at any given time. Under certain conditions depending on the message exchange pattern of the service, this means that it's possible to deadlock a web-hosted service using dual HTTP and reliable sessions. To increase the number of allowable HTTP connections per client, add the following to the relevant configuration file (for example, *web.config* of the service in question):
```xml
<configuration>
<system.net>
<connectionManagement>
<add name="*" maxconnection="4" />
</connectionManagement>
</system.net>
</configuration>
```
The value of the `maxconnection` attribute is the number of connections needed. The minimum in this case should be four connections.
| 78.695652 | 695 | 0.798066 | eng_Latn | 0.99928 |
f4ec75fa41c872038889bce5ebb35302b314be85 | 6,904 | md | Markdown | README.md | cjordan/hifitime | 076a9578bc6545004cfc7297054054b1f3442653 | [
"Apache-2.0"
] | 23 | 2017-12-30T06:53:06.000Z | 2021-07-09T06:05:53.000Z | README.md | cjordan/hifitime | 076a9578bc6545004cfc7297054054b1f3442653 | [
"Apache-2.0"
] | 73 | 2017-10-04T05:25:51.000Z | 2021-11-16T07:51:47.000Z | README.md | cjordan/hifitime | 076a9578bc6545004cfc7297054054b1f3442653 | [
"Apache-2.0"
] | 4 | 2019-05-11T10:44:53.000Z | 2021-08-24T09:11:35.000Z | # hifitime 2
Precise date and time handling in Rust built on top of a tuple of two floats.
The Epoch used is TAI Epoch of 01 Jan 1900 at midnight, but that should not matter in
day-to-day use of this library.
[](https://app.travis-ci.com/nyx-space/hifitime)
[![hifitime on crates.io][cratesio-image]][cratesio]
[![hifitime on docs.rs][docsrs-image]][docsrs]
[cratesio-image]: https://img.shields.io/crates/v/hifitime.svg
[cratesio]: https://crates.io/crates/hifitime
[docsrs-image]: https://docs.rs/hifitime/badge.svg
[docsrs]: https://docs.rs/hifitime/
# Features
* [x] Leap seconds (as announced by the IETF on a yearly basis)
* [x] Julian dates and Modified Julian dates
* [x] Clock drift via oscillator stability for simulation of time measuring hardware (via the `simulation` feature)
* [x] UTC representation with ISO8601 formatting (and parsing in that format #45)
* [x] High fidelity Ephemeris Time / Dynamic Barycentric Time (TDB) computations from [ESA's Navipedia](https://gssc.esa.int/navipedia/index.php/Transformations_between_Time_Systems#TDT_-_TDB.2C_TCB) (caveat: up to 10ms difference with SPICE near 01 Jan 2000)
* [x] Trivial support of time arithmetic (e.g. `TimeUnit::Hour * 2 + TimeUnit::Second * 3`)
* [x] Supports ranges of Epochs and TimeSeries (linspace of `Epoch`s and `Duration`s)
* [ ] Support for custom representations of time (e.g. NASA GMAT Modified Julian Date)
* [ ] Trivial support of other time representations, such as TDT (cf #44)
Almost all examples are validated with external references, as detailed on a test-by-test
basis.
# Validation example
Validation is done using NASA's SPICE toolkit, and specifically the [spiceypy](https://spiceypy.readthedocs.io/) Python wrapper.
The most challenging validation is the definition of Ephemeris Time, which is very nearly the same as the Dynamic Barycentric Time (TDB).
These calculations in hifitime are from [ESA's Navipedia](https://gssc.esa.int/navipedia/index.php/Transformations_between_Time_Systems#TDT_-_TDB.2C_TCB).
Hifitime uses a fixed offset for the computation of Ephemeris Time, as is recommended in Navipedia. For TDB however, the offset is based on the centuries since J2000 TT and therefore time varying.
I believe that SPICE uses TDB for all dates after J2000 TT. Hence, in the following validation, we will be comparing the SPICE ET with the Hifitime TDB.
The following examples are executed as part of the standard test suite (cf. the function called `spice_et_tdb`).
## Case 1
In SPICE, we chose to convert the UTC date `2012-02-07 11:22:33 UTC` into Ephemeris Time. SPICE responds with `381885819.18493587`.
Initializing the same UTC date in hifitime and requesting the TDB leads to `381885819.18493646`, which is an error of **596.05 nanoseconds**.
## Case 2
In SPICE, we chose to convert the UTC date `2002-02-07 00:00:00.000 UTC` into Ephemeris Time. SPICE responds with `66312064.18493876`.
Initializing the same UTC date in hifitime and requesting the TDB leads to a difference **618.39 nanoseconds**.
## Case 3
This tests that we can correctly compute TDB time which will have a negative number of days because the UTC input is prior to J2000 TT.
In SPICE, we chose to convert the UTC date `1996-02-07 11:22:33 UTC` into Ephemeris Time. SPICE responds with `-123035784.81506048`.
Initializing the same UTC date in hifitime and requesting the TDB leads to a difference **610.94 nanoseconds**.
## Case 4
In SPICE, we chose to convert the UTC date `2015-02-07 00:00:00.000 UTC` into Ephemeris Time. SPICE responds with `476580220.1849411`.
Initializing the same UTC date in hifitime and requesting the TDB leads to a difference **596.05 nanoseconds**.
## Case 5
In SPICE, we chose to convert the TDB Julian Date in days `2452312.500372511` into Ephemeris Time, and initialize a Hifitime Epoch with that result (`66312032.18493909`).
We then convert that epoch back into **days** of Julian Date TDB and Julian Date ET, both of which lead a difference **below machine precision** on a f64 (the equivalent of a double in C/C++).
# Notes
Please report and bugs by [clicking here](https://github.com/ChristopherRabotin/hifitime/issues/new).
### Leap second support
Each time computing library may decide when the extra leap second exists as explained
in the [IETF leap second reference](https://www.ietf.org/timezones/data/leap-seconds.list).
To ease computation, `hifitime` decides that second is the 60th of a UTC date, if such exists.
Note that this second exists at a different time than defined on NASA HEASARC. That tool is
used for validation of Julian dates. As an example of how this is handled, check the Julian
day computations for [2015-06-30 23:59:59](https://heasarc.gsfc.nasa.gov/cgi-bin/Tools/xTime/xTime.pl?time_in_i=2015-06-30+23%3A59%3A59&time_in_c=&time_in_d=&time_in_j=&time_in_m=&time_in_sf=&time_in_wf=&time_in_sl=&time_in_snu=&time_in_s=&time_in_h=&time_in_n=&time_in_f=&time_in_sz=&time_in_ss=&time_in_sn=×ys_in=u×ys_out=u&apply_clock_offset=yes),
[2015-06-30 23:59:60](https://heasarc.gsfc.nasa.gov/cgi-bin/Tools/xTime/xTime.pl?time_in_i=2015-06-30+23%3A59%3A60&time_in_c=&time_in_d=&time_in_j=&time_in_m=&time_in_sf=&time_in_wf=&time_in_sl=&time_in_snu=&time_in_s=&time_in_h=&time_in_n=&time_in_f=&time_in_sz=&time_in_ss=&time_in_sn=×ys_in=u×ys_out=u&apply_clock_offset=yes) and [2015-07-01 00:00:00](https://heasarc.gsfc.nasa.gov/cgi-bin/Tools/xTime/xTime.pl?time_in_i=2015-07-01+00%3A00%3A00&time_in_c=&time_in_d=&time_in_j=&time_in_m=&time_in_sf=&time_in_wf=&time_in_sl=&time_in_snu=&time_in_s=&time_in_h=&time_in_n=&time_in_f=&time_in_sz=&time_in_ss=&time_in_sn=×ys_in=u×ys_out=u&apply_clock_offset=yes).
### Ephemeris Time vs Dynamic Barycentric Time (TDB)
ET and TDB should now be identical. However, hifitime uses the European Space Agency's definition of TDB, detailed [here](https://gssc.esa.int/navipedia/index.php/Transformations_between_Time_Systems#TDT_-_TDB.2C_TCB). It seems that SPICE uses the older definition which has a fixed offset from TDT of 0.000935 seconds. This difference is more prominent around the TDB epoch of 01 January 2000.
# Changelog
## 2.2.3
+ More deterministic `as_jde_tdb_days()` in `Epoch`. In version 2.2.1, the ephemeris time and TDB _days_ were identical down to machine precision. After a number of validation cases in the rotation equations of the IAU Earth to Earth Mean Equator J2000 frame, the new formulation was shown to lead to less rounding errors when requesting the days. These rounding errors prevented otherwise trivial test cases. However, it adds an error of **40.2 nanoseconds** when initializing an Epoch with the days in ET and requesting the TDB days.
_Note:_ this was originally published as 2.2.2 but I'd forgotten to update one of the tests with the 40.2 ns error. | 80.27907 | 682 | 0.778969 | eng_Latn | 0.952245 |
f4ecb6ddf3f9a580de0381d44bdcf1f9deefa997 | 1,490 | md | Markdown | README.md | coasterman/GoodMod | 9729be92b38992eb4ceab90638c9f80c15cfe984 | [
"MIT"
] | null | null | null | README.md | coasterman/GoodMod | 9729be92b38992eb4ceab90638c9f80c15cfe984 | [
"MIT"
] | null | null | null | README.md | coasterman/GoodMod | 9729be92b38992eb4ceab90638c9f80c15cfe984 | [
"MIT"
] | null | null | null | # GoodMod
*[From the original reddit /r/ChivalryGame post]*
This mod is based off an older version of Mercs mod but has now been updated to roughly the same point as Mercs 1.995 except for some additions detailed below. Hopefully active development will continue for a good while as the game clings on to dear life. The aim of this mod is to make the game more fun and balanced for competitive players so that they don't get completely bored of the game just yet.
Balance decisions will be undertaken by a myself and a few others (mostly for practical reasons - a full balance council has been tried in the past and failed). However of course we will be open to suggestions - you can discuss them here on reddit or on the steam workshop page (links below).
You can see the full changelog [here](https://github.com/vincegogh/GoodMod/blob/master/CHANGELOG.md), the source code can be found [here](http://github.com/vincegogh/GoodMod/), and the steam workshop page can be found [here](http://steamcommunity.com/sharedfiles/filedetails/?id=799351461). The list of known bugs can be found [here](http://github.com/vincegogh/GoodMod/issues) - do feel free to add them directly or contact me if you find anything. Note that source code contributions that affect balance are unlikely to be accepted unless they have been properly discussed on the steam page or reddit.
This repository uses the MIT license. Details can be found [here](http://github.com/vincegogh/GoodMod/blob/master/LICENSE).
| 124.166667 | 603 | 0.787919 | eng_Latn | 0.999196 |
f4ece51d600160903606bfe62bb49b7a1b3f6d7b | 133 | md | Markdown | README.md | kbaseapps/KnowledgeEnginePrototype | f451844d0c2ec568afe7dbd72283e055208f69b2 | [
"MIT"
] | null | null | null | README.md | kbaseapps/KnowledgeEnginePrototype | f451844d0c2ec568afe7dbd72283e055208f69b2 | [
"MIT"
] | null | null | null | README.md | kbaseapps/KnowledgeEnginePrototype | f451844d0c2ec568afe7dbd72283e055208f69b2 | [
"MIT"
] | null | null | null |
# KnowledgeEnginePrototype
---
A [KBase](https://kbase.us) module generated by the [KBase SDK](https://github.com/kbase/kb_sdk).
| 16.625 | 97 | 0.714286 | yue_Hant | 0.551124 |
Subsets and Splits