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
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
b962c890b65ae75f5cf81f780966d2eee20e493e | 1,606 | md | Markdown | docs/vs-2015/extensibility/debugger/reference/idebugfunctionposition2-getoffset.md | thoelkef/visualstudio-docs.de-de | bfc727b45dcd43a837d3f4f2b06b45d59da637bc | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/vs-2015/extensibility/debugger/reference/idebugfunctionposition2-getoffset.md | thoelkef/visualstudio-docs.de-de | bfc727b45dcd43a837d3f4f2b06b45d59da637bc | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/vs-2015/extensibility/debugger/reference/idebugfunctionposition2-getoffset.md | thoelkef/visualstudio-docs.de-de | bfc727b45dcd43a837d3f4f2b06b45d59da637bc | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: 'IDebugFunctionPosition2:: gezu ffset | Microsoft-Dokumentation'
ms.date: 11/15/2016
ms.prod: visual-studio-dev14
ms.technology: vs-ide-sdk
ms.topic: reference
f1_keywords:
- IDebugFunctionPosition2::GetOffset
helpviewer_keywords:
- IDebugFunctionPosition2::GetOffset
ms.assetid: 60943782-aec7-4be2-b222-1984ed53a543
caps.latest.revision: 14
ms.author: gregvanl
manager: jillfra
ms.openlocfilehash: ecff2d4bc287cb4ece9989dc3ed371c7786264e2
ms.sourcegitcommit: 6cfffa72af599a9d667249caaaa411bb28ea69fd
ms.translationtype: MT
ms.contentlocale: de-DE
ms.lasthandoff: 09/02/2020
ms.locfileid: "68180923"
---
# <a name="idebugfunctionposition2getoffset"></a>IDebugFunctionPosition2::GetOffset
[!INCLUDE[vs2017banner](../../../includes/vs2017banner.md)]
Ruft die Position der Funktion im Quelldokument ab.
## <a name="syntax"></a>Syntax
```cpp#
HRESULT GetOffset(
TEXT_POSITION* pPosition
);
```
```csharp
int GetOffset(
TEXT_POSITION[] pPosition
);
```
#### <a name="parameters"></a>Parameter
`pPosition`
[in, out] Eine [TEXT_POSITION](../../../extensibility/debugger/reference/text-position.md) -Struktur, die mit der Position der Funktion in einem Dokument ausgefüllt ist.
## <a name="return-value"></a>Rückgabewert
Wenn die Ausführung erfolgreich ist, wird `S_OK`, andernfalls ein Fehlercode zurückgegeben.
## <a name="see-also"></a>Weitere Informationen
[IDebugFunctionPosition2](../../../extensibility/debugger/reference/idebugfunctionposition2.md)
[TEXT_POSITION](../../../extensibility/debugger/reference/text-position.md)
| 31.490196 | 172 | 0.746575 | yue_Hant | 0.46955 |
b962c91006eabf4395ca2aed28d14a92f1651f9c | 7,411 | md | Markdown | reference/docs-conceptual/samples/Managing-Processes-with-Process-Cmdlets.md | ADVRVer/powerShell-Docs.zh-tw | 63ac91b89be9bec33417f7c38faf5f4ae76f15dc | [
"CC-BY-4.0",
"MIT"
] | null | null | null | reference/docs-conceptual/samples/Managing-Processes-with-Process-Cmdlets.md | ADVRVer/powerShell-Docs.zh-tw | 63ac91b89be9bec33417f7c38faf5f4ae76f15dc | [
"CC-BY-4.0",
"MIT"
] | null | null | null | reference/docs-conceptual/samples/Managing-Processes-with-Process-Cmdlets.md | ADVRVer/powerShell-Docs.zh-tw | 63ac91b89be9bec33417f7c38faf5f4ae76f15dc | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
ms.date: 06/05/2017
keywords: powershell,cmdlet
title: 使用處理程序 Cmdlet 管理處理程序
ms.openlocfilehash: 8de0cbae508958bf7970ce69e03257ea0a8dca6f
ms.sourcegitcommit: 6545c60578f7745be015111052fd7769f8289296
ms.translationtype: HT
ms.contentlocale: zh-TW
ms.lasthandoff: 04/22/2020
ms.locfileid: "75870739"
---
# <a name="managing-processes-with-process-cmdlets"></a>使用處理程序 Cmdlet 管理處理程序
您可以使用 Windows PowerShell 中的處理程序 Cmdlet，管理 Windows PowerShell 中的本機和遠端處理程序。
## <a name="getting-processes-get-process"></a>取得處理程序 (Get-Process)
若要取得在本機電腦上執行的處理程序，請在不使用參數的情況下執行 **Get-Process**。
您可以藉由指定處理程序的名稱或識別碼，來取得特定處理程序。 下列命令會取得閒置處理程序︰
```
PS> Get-Process -id 0
Handles NPM(K) PM(K) WS(K) VM(M) CPU(s) Id ProcessName
------- ------ ----- ----- ----- ------ -- -----------
0 0 0 16 0 0 Idle
```
雖然 Cmdlet 在某些情況下未傳回任何資料是正常的，但是當您依處理程序的 ProcessId 指定處理程序時，由於一般目的是擷取已知的執行中處理程序，因此如果 **Get-Process** 找不到任何相符項目，則會產生錯誤。 如果沒有該識別碼的處理程序，很可能是識別碼不正確，或感興趣的處理程序已經結束：
```
PS> Get-Process -Id 99
Get-Process : No process with process ID 99 was found.
At line:1 char:12
+ Get-Process <<<< -Id 99
```
您可以使用 Get-Process Cmdlet 的 Name 參數，根據處理序名稱指定處理程序的子集。 Name 參數可以接受以逗號分隔的多個名稱清單，而且支援使用萬用字元，因此您可以輸入名稱模式。
例如，下列命令會取得名稱開頭為 "ex" 的處理程序。
```
PS> Get-Process -Name ex*
Handles NPM(K) PM(K) WS(K) VM(M) CPU(s) Id ProcessName
------- ------ ----- ----- ----- ------ -- -----------
234 7 5572 12484 134 2.98 1684 EXCEL
555 15 34500 12384 134 105.25 728 explorer
```
因為 .NET System.Diagnostics.Process 類別是 Windows PowerShell 處理程序的基礎，所以它會遵循 System.Diagnostics.Process 所使用的一些慣例。 其中一個慣例是可執行檔的處理程序名稱，絕對不可以在可執行檔名稱結尾包含 ".exe"。
**Get-Process** 也接受 Name 參數有多個值。
```
PS> Get-Process -Name exp*,power*
Handles NPM(K) PM(K) WS(K) VM(M) CPU(s) Id ProcessName
------- ------ ----- ----- ----- ------ -- -----------
540 15 35172 48148 141 88.44 408 explorer
605 9 30668 29800 155 7.11 3052 powershell
```
您可以使用 Get-Process 的 ComputerName 參數取得遠端電腦上的處理程序。 例如，下列命令會取得本機電腦 (以 "localhost" 表示) 和兩部遠端電腦上的 PowerShell 處理程序。
```
PS> Get-Process -Name PowerShell -ComputerName localhost, Server01, Server02
Handles NPM(K) PM(K) WS(K) VM(M) CPU(s) Id ProcessName
------- ------ ----- ----- ----- ------ -- -----------
258 8 29772 38636 130 3700 powershell
398 24 75988 76800 572 5816 powershell
605 9 30668 29800 155 7.11 3052 powershell
```
電腦名稱雖然未出現在此顯示中，但儲存在 Get-Process 所傳回之處理程序物件的 MachineName 屬性中。 下列命令會使用 Format-Table Cmdlet 顯示處理程序物件的處理程序 ID、ProcessName 和 MachineName (ComputerName) 屬性。
```
PS> Get-Process -Name PowerShell -ComputerName localhost, Server01, Server01 |
Format-Table -Property ID, ProcessName, MachineName
Id ProcessName MachineName
-- ----------- -----------
3700 powershell Server01
3052 powershell Server02
5816 powershell localhost
```
這個更複雜的命令會將 MachineName 屬性新增至標準 Get-Process 顯示。
```
PS> Get-Process powershell -ComputerName localhost, Server01, Server02 |
Format-Table -Property Handles,
@{Label="NPM(K)";Expression={[int]($_.NPM/1024)}},
@{Label="PM(K)";Expression={[int]($_.PM/1024)}},
@{Label="WS(K)";Expression={[int]($_.WS/1024)}},
@{Label="VM(M)";Expression={[int]($_.VM/1MB)}},
@{Label="CPU(s)";Expression={if ($_.CPU -ne $()){$_.CPU.ToString("N")}}},
Id, ProcessName, MachineName -auto
Handles NPM(K) PM(K) WS(K) VM(M) CPU(s) Id ProcessName MachineName
------- ------ ----- ----- ----- ------ -- ----------- -----------
258 8 29772 38636 130 3700 powershell Server01
398 24 75988 76800 572 5816 powershell localhost
605 9 30668 29800 155 7.11 3052 powershell Server02
```
## <a name="stopping-processes-stop-process"></a>停止處理程序 (Stop-Process)
Windows PowerShell 可讓您彈性地列出處理程序，但停止處理程序又如何？
**Stop-Process** Cmdlet 接受使用 Name 或 Id 指定您要停止的處理程序。 您是否能夠停止處理程序取決於您的權限。 某些處理程序無法停止。 例如，如果您嘗試停止閒置處理程序，您會收到錯誤︰
```
PS> Stop-Process -Name Idle
Stop-Process : Process 'Idle (0)' cannot be stopped due to the following error:
Access is denied
At line:1 char:13
+ Stop-Process <<<< -Name Idle
```
您也可以 **Confirm** 參數來強制提示。 如果您在指定處理程序名稱時使用萬用字元，此參數特別有用，因為您可能會不小心比對一些不想停止的處理程序︰
```
PS> Stop-Process -Name t*,e* -Confirm
Confirm
Are you sure you want to perform this action?
Performing operation "Stop-Process" on Target "explorer (408)".
[Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help
(default is "Y"):n
Confirm
Are you sure you want to perform this action?
Performing operation "Stop-Process" on Target "taskmgr (4072)".
[Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help
(default is "Y"):n
```
您可以使用一些物件篩選 Cmdlet 來管理複雜的處理程序。 因為當處理程序物件不再回應時的 Responding 屬性為 true，所以您可以使用下列命令停止所有無回應的應用程式︰
```powershell
Get-Process | Where-Object -FilterScript {$_.Responding -eq $false} | Stop-Process
```
您可以在其他情況下使用相同的方法。 例如，假設當使用者啟動另一個應用程式時，次要通知區域應用程式會自動執行。 您可能會發現這在終端機服務工作階段中無法正常運作，但您仍然想要在實體電腦主控台上執行的工作階段中予以保留。 連線到實體電腦桌面之工作階段的工作階段識別碼一律為 0，因此您可以使用 **Where-Object** 和處理程序 **SessionId**，停止該處理程序在其他工作階段中的所有執行個體：
```powershell
Get-Process -Name BadApp | Where-Object -FilterScript {$_.SessionId -neq 0} | Stop-Process
```
Stop-Process Cmdlet 沒有 ComputerName 參數。 因此，若要在遠端電腦上執行停止處理程序命令，您需要使用 Invoke-Command Cmdlet。 例如，若要停止 Server01 遠端電腦上的 PowerShell 處理程序，請輸入：
```powershell
Invoke-Command -ComputerName Server01 {Stop-Process Powershell}
```
## <a name="stopping-all-other-windows-powershell-sessions"></a>停止所有其他 Windows PowerShell 工作階段
能夠停止目前工作階段以外的所有執行中 PowerShell 工作階段有時可能會很有用。 如果工作階段使用太多資源或無法存取 (可能在遠端執行或在其他桌面工作階段中)，您可能無法直接將它停止。 不過如果您嘗試停止所有執行中的工作階段，可能反而終止目前的工作階段。
每個 Windows PowerShell 工作階段都有包含 Windows PowerShell 處理程序識別碼的環境變數 PID。 您可以根據每個工作階段的識別碼檢查 $PID，並只終止具有不同識別碼的 Windows PowerShell 工作階段。下列管線命令會執行這項操作，並傳回終止的工作階段清單 (因為使用了 **PassThru** 參數)：
```
PS> Get-Process -Name powershell | Where-Object -FilterScript {$_.Id -ne $PID} | Stop-Process -PassThru
Handles NPM(K) PM(K) WS(K) VM(M) CPU(s) Id ProcessName
------- ------ ----- ----- ----- ------ -- -----------
334 9 23348 29136 143 1.03 388 powershell
304 9 23152 29040 143 1.03 632 powershell
302 9 20916 26804 143 1.03 1116 powershell
335 9 25656 31412 143 1.09 3452 powershell
303 9 23156 29044 143 1.05 3608 powershell
287 9 21044 26928 143 1.02 3672 powershell
```
## <a name="starting-debugging-and-waiting-for-processes"></a>啟動、偵錯及等候處理程序
Windows PowerShell 也提供啟動 (或重新啟動)、偵錯處理程序，以及等候處理程序完成再執行命令的 Cmdlet。 如需這些 Cmdlet 的資訊，請參閱每個 Cmdlet 的 Cmdlet 說明主題。
## <a name="see-also"></a>另請參閱
- [Get-Process](/powershell/module/Microsoft.PowerShell.Management/Get-Process)
- [Stop-Process](/powershell/module/Microsoft.PowerShell.Management/Stop-Process)
- [Start-Process](/powershell/module/Microsoft.PowerShell.Management/Start-Process)
- [Wait-Process](/powershell/module/Microsoft.PowerShell.Management/Wait-Process)
- [Debug-Process](/powershell/module/Microsoft.PowerShell.Management/Debug-Process)
- [Invoke-Command](/powershell/module/Microsoft.PowerShell.Core/Invoke-Command)
| 39.21164 | 205 | 0.657401 | yue_Hant | 0.964467 |
b962ce605ddabcc4b3de949afc12cfe6b8d2dde5 | 4,056 | md | Markdown | windows-apps-src/publish/app-marketing-guidelines.md | strongstrongyiwen/windows-uwp | 0528894d38bde657dad92e5dd91eb8282e239328 | [
"CC-BY-4.0",
"MIT"
] | 502 | 2017-02-10T13:25:49.000Z | 2022-03-28T12:24:50.000Z | windows-apps-src/publish/app-marketing-guidelines.md | strongstrongyiwen/windows-uwp | 0528894d38bde657dad92e5dd91eb8282e239328 | [
"CC-BY-4.0",
"MIT"
] | 3,579 | 2017-02-08T19:31:35.000Z | 2022-03-31T17:14:17.000Z | windows-apps-src/publish/app-marketing-guidelines.md | strongstrongyiwen/windows-uwp | 0528894d38bde657dad92e5dd91eb8282e239328 | [
"CC-BY-4.0",
"MIT"
] | 1,233 | 2017-02-08T18:04:11.000Z | 2022-03-31T18:47:26.000Z | ---
description: Learn how to promote your apps and content in the Microsoft Store. These guidelines cover how to use the assets that are available to you, along with recommendations for promoting your apps in print, TV, social media and digital advertising.
title: Microsoft Store marketing guidelines for apps
ms.assetid: CEB81E9D-5C64-458F-AAF1-C59BBBBB272E
ms.date: 10/31/2018
ms.topic: article
keywords: windows 10, uwp
ms.localizationpriority: medium
---
# Microsoft Store marketing guidelines for apps
Learn how to promote your apps and content in the Microsoft Store. These guidelines cover how to use the assets that are available to you, along with recommendations for promoting your apps in print, TV, social media and digital advertising.
## Store badges
We’ve created special promotional badges to help you drive more customers to your app's listing in the Microsoft Store. These badges are available in 44 languages. Keep in mind that there are certain requirements you need to follow when using these images; these requirements, along with usage examples and guidelines, are available in a PDF file.
[](https://download.microsoft.com/download/0/7/D/07DF43D4-B1A8-4D38-BC02-4903BB36CEE8/Microsoft_Store_Badge_Guidelines.pdf) **Microsoft Store Badge Guidelines (PDF, English)**
## Badge generator and images
You can use our [badge generator](https://developer.microsoft.com/store/badges) to generate HTML that displays the Store badge (in the language of your choice) and links directly to your app's Store listing.
You can also download the complete set of badge images (in PNG and PDF format) from the link below.
[](https://download.microsoft.com/download/6/6/6/66641831-E662-4898-BB21-75D6C193A8F9/All%20Badges.zip) **All badge images**
## Device images
To promote your app, you may want to show how it looks when running on a Windows device. We have a variety of device chassis images for you to select from, including phones, tablets, laptops and PCs. Best practices and technical specifications for how to use these images can be found in the [Microsoft Store Marketing Guidelines](https://download.microsoft.com/download/0/7/D/07DF43D4-B1A8-4D38-BC02-4903BB36CEE8/Microsoft_Store_Badge_Guidelines.pdf).
[](https://download.microsoft.com/download/1/A/5/1A58A23A-1388-4097-B441-A3E8DBC14849/Windows_Store_Device_Art.zip) **Windows device art**
## License to Microsoft Marks
*Microsoft Marks* means the *Microsoft badge* described on the [badge generator](https://developer.microsoft.com/store/badges) page. To use these badges, you must:
- Have your app or other content available in the Microsoft Store, or be part of the [Microsoft Affiliate Program](https://www.microsoftaffiliates.com/).
- If you are registered as an app developer in Partner Center, comply with the [“License to Microsoft Marks”](/legal/windows/agreements/app-developer-agreement#license_to_mark) section of the App Developer Agreement.
- If you are not registered as an app developer in Partner Center, Microsoft grants you a worldwide, nonexclusive, nontransferable, royalty-free license to use the badges solely as described in the Microsoft Store Badge Guidelines. Microsoft may change these guidelines, but if it does, Microsoft will use reasonable means to redirect you to any new URLs where these specifications are posted. Microsoft reserves all rights not expressly granted herein.
- Follow the logo usage specifications described in the [Microsoft Store Badge Guidelines](https://download.microsoft.com/download/0/7/D/07DF43D4-B1A8-4D38-BC02-4903BB36CEE8/Microsoft_Store_Badge_Guidelines.pdf).
Microsoft is the sole owner of the Microsoft Marks and associated goodwill, and the sole beneficiary of the goodwill associated with your use of the Microsoft Marks. Microsoft may revoke this license at any time and at its sole discretion.
| 76.528302 | 456 | 0.790434 | eng_Latn | 0.978031 |
b962f1ff2b3d39c9493fedb6b89070c5eadb498f | 2,054 | md | Markdown | docs/framework/unmanaged-api/debugging/createcordbobject-function.md | roel4ez/docs | 3924cfceca7eb9ee88706129f99cf9aa2aeeb668 | [
"CC-BY-4.0",
"MIT"
] | 2 | 2019-06-02T11:09:59.000Z | 2019-06-15T10:17:08.000Z | docs/framework/unmanaged-api/debugging/createcordbobject-function.md | roel4ez/docs | 3924cfceca7eb9ee88706129f99cf9aa2aeeb668 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2019-05-10T16:33:09.000Z | 2019-05-10T16:33:09.000Z | docs/framework/unmanaged-api/debugging/createcordbobject-function.md | roel4ez/docs | 3924cfceca7eb9ee88706129f99cf9aa2aeeb668 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2019-02-14T06:38:48.000Z | 2019-02-14T06:38:48.000Z | ---
title: "CreateCordbObject Function"
ms.date: "03/30/2017"
api_name:
- "CreateCoredbObject"
api_location:
- "mscordbi_macx86.dll"
api_type:
- "COM"
f1_keywords:
- "CreateCordbObject"
helpviewer_keywords:
- "remote debugging API [Silverlight]"
- "CreateCordbObject function"
- "Silverlight, remote debugging"
ms.assetid: b259821d-4fa7-464d-85cf-304dfffc8089
topic_type:
- "apiref"
author: "rpetrusha"
ms.author: "ronpet"
---
# CreateCordbObject Function
Creates a debugger interface ([ICorDebug](../../../../docs/framework/unmanaged-api/debugging/icordebug-interface.md)) that provides functionality for instantiating a managed debugging session on a remote process.
## Syntax
```
HRESULT CordbCreateObject (
[in] int iDebuggerVersion,
[out] IUnknown** ppCordb
);
```
## Parameters
`iDebuggerVersion`
[in] Debugger version of the target process. This parameter must be CorDebugVersion_2_0 for remote debugging.
`ppCordb`
[out] Pointer to a pointer to an object that will be cast to an [ICorDebug](../../../../docs/framework/unmanaged-api/debugging/icordebug-interface.md) interface and returned.
## Return Value
S_OK
The number of CLRs in the process was successfully determined, and the corresponding handle and path arrays were properly filled.
E_INVALIDARG
`ppCordb` is null, or `iDebuggerVersion` is not CorDebugVersion_2_0.
E_OUTOFMEMORY
Unable to allocate enough memory for `ppCordb`
E_FAIL (or other E_ return codes)
Other failures.
## Remarks
The [ICorDebug](../../../../docs/framework/unmanaged-api/debugging/icordebug-interface.md) interface that is returned in `ppCordb` is the top-level debugging interface for all managed debugging services.
## Requirements
**Platforms:** See [System Requirements](../../../../docs/framework/get-started/system-requirements.md).
**Header:** CoreClrRemoteDebuggingInterfaces.h
**Library:** mscordbi_macx86.dll
**.NET Framework Versions:** 3.5 SP1
| 31.6 | 214 | 0.711782 | eng_Latn | 0.588061 |
b9632eaa876c454d013d468aa6cf9ba472259003 | 892 | md | Markdown | docs/ado/guide/data/handling-errors-in-other-languages.md | huanwnn/sql-docs.zh-tw | 1c3423fa4a220bc3d44cc086bb42c21ebec79471 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/ado/guide/data/handling-errors-in-other-languages.md | huanwnn/sql-docs.zh-tw | 1c3423fa4a220bc3d44cc086bb42c21ebec79471 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/ado/guide/data/handling-errors-in-other-languages.md | huanwnn/sql-docs.zh-tw | 1c3423fa4a220bc3d44cc086bb42c21ebec79471 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2021-01-09T04:04:39.000Z | 2021-01-09T04:04:39.000Z | ---
title: 處理其他語言的錯誤 |Microsoft Docs
ms.prod: sql
ms.prod_service: connectivity
ms.technology: connectivity
ms.custom: ''
ms.date: 02/14/2017
ms.reviewer: ''
ms.topic: conceptual
ms.assetid: 8c57f35e-3c04-4f17-bf3e-3ad053951530
author: rothja
ms.author: jroth
ms.openlocfilehash: 498de75e624528a2d2bd9ab5aa4225c9d22f11db
ms.sourcegitcommit: 6037fb1f1a5ddd933017029eda5f5c281939100c
ms.translationtype: MT
ms.contentlocale: zh-TW
ms.lasthandoff: 05/04/2020
ms.locfileid: "82758834"
---
# <a name="handling-errors-in-other-languages"></a>處理其他語言的錯誤
到目前為止，本節討論了 Microsoft® Visual Basic®觀點的錯誤。 本節的其餘部分將概述 Visual Basic 以外的語言中的錯誤處理。
此章節包含下列主題。
- [處理 VBScript 的錯誤](../../../ado/guide/data/handling-errors-in-vbscript.md)
- [處理 Visual C++ 的錯誤](../../../ado/guide/data/handling-errors-in-visual-c.md)
- [處理 JScript 的錯誤](../../../ado/guide/data/handling-errors-in-jscript.md)
| 29.733333 | 81 | 0.743274 | yue_Hant | 0.408246 |
b963c9567b9aaeba953c8a5df58cdf6d1ea9f85a | 297 | md | Markdown | docs/ipfsd/ipfsd/danbroid.ipfsd.service/-i-p-f-s-service/on-rebind.md | danbrough/ipfsd | a136e8df465f055166717220bc8f18c9fd67a87d | [
"MIT"
] | null | null | null | docs/ipfsd/ipfsd/danbroid.ipfsd.service/-i-p-f-s-service/on-rebind.md | danbrough/ipfsd | a136e8df465f055166717220bc8f18c9fd67a87d | [
"MIT"
] | null | null | null | docs/ipfsd/ipfsd/danbroid.ipfsd.service/-i-p-f-s-service/on-rebind.md | danbrough/ipfsd | a136e8df465f055166717220bc8f18c9fd67a87d | [
"MIT"
] | null | null | null | //[ipfsd](../../index.md)/[danbroid.ipfsd.service](../index.md)/[IPFSService](index.md)/[onRebind](on-rebind.md)
# onRebind
[androidJvm]
Content
open override fun [onRebind](on-rebind.md)(intent: [Intent](https://developer.android.com/reference/kotlin/android/content/Intent.html)?)
| 24.75 | 139 | 0.700337 | yue_Hant | 0.561088 |
b9643bad7a9070980d7c82b13f246c142b437d12 | 476 | md | Markdown | src/markdown-pages/csumb-saluted-as-top-military-school-3-straight-years.md | csumb-archives/news-gatsby | ef59f9a219e94123b306ebba3a856f78612446a5 | [
"MIT"
] | 1 | 2020-09-09T22:40:34.000Z | 2020-09-09T22:40:34.000Z | src/markdown-pages/csumb-saluted-as-top-military-school-3-straight-years.md | csumb-archives/news-gatsby | ef59f9a219e94123b306ebba3a856f78612446a5 | [
"MIT"
] | 4 | 2020-08-12T21:16:50.000Z | 2020-10-02T19:21:15.000Z | src/markdown-pages/csumb-saluted-as-top-military-school-3-straight-years.md | csumb-archives/news-gatsby | ef59f9a219e94123b306ebba3a856f78612446a5 | [
"MIT"
] | null | null | null | ---
slug: csumb-saluted-as-top-military-school-3-straight-years
title: "CSUMB saluted as top military school 3 straight years"
date: January 01 2020
---
<p>
For the third consecutive year, CSU Monterey Bay has been named a
"military-friendly school" by G.I. Jobs magazine. The list honors the top 20
percent of colleges and universities that are doing the most to embrace
America's military members and veterans as students. – <em>KION,</em> Oct. 19,
2011
</p>
| 29.75 | 80 | 0.737395 | eng_Latn | 0.997312 |
b96441c8858e81300cfca62c3f45d78f12308fd5 | 207 | md | Markdown | lainlain/bc/bc-peb.md | kelaspajak/docs | 6aef89b6a433d131c21339048e35b2f8e915e708 | [
"MIT"
] | null | null | null | lainlain/bc/bc-peb.md | kelaspajak/docs | 6aef89b6a433d131c21339048e35b2f8e915e708 | [
"MIT"
] | null | null | null | lainlain/bc/bc-peb.md | kelaspajak/docs | 6aef89b6a433d131c21339048e35b2f8e915e708 | [
"MIT"
] | null | null | null | ---
id: 103
title: Pemberitahuan Ekspor Barang
linkurl: https://kutt.it/rdIw43
fitur: lainlain
category: lainlain
createdTime : 12/01/2020
modifiedTime : 12/01/2020
topik: DJBC
color: ffd33d
img: bc.jpeg
--- | 17.25 | 34 | 0.753623 | ind_Latn | 0.100036 |
b964ab1f739bd93dd2c918c40abe553985f51aa9 | 4,961 | md | Markdown | test/hlk/testref/d0c757e4-44aa-4de8-9c8b-1b05b96855a9.md | michaeltang4829/commercialization-public | 34b0f79c731f807561ddc605baf101d58ce528db | [
"CC-BY-4.0",
"MIT"
] | 4 | 2020-07-17T23:27:34.000Z | 2021-11-22T08:02:59.000Z | test/hlk/testref/d0c757e4-44aa-4de8-9c8b-1b05b96855a9.md | michaeltang4829/commercialization-public | 34b0f79c731f807561ddc605baf101d58ce528db | [
"CC-BY-4.0",
"MIT"
] | null | null | null | test/hlk/testref/d0c757e4-44aa-4de8-9c8b-1b05b96855a9.md | michaeltang4829/commercialization-public | 34b0f79c731f807561ddc605baf101d58ce528db | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Hybrid Information Command Test (LOGO)
description: Hybrid Information Command Test (LOGO)
MSHAttr:
- 'PreferredSiteName:MSDN'
- 'PreferredLib:/library/windows/hardware'
ms.assetid: 33797bda-4884-481f-aaa6-c23dbcc698cb
author: dawn.wood
ms.author: dawnwood
ms.date: 11/05/2018
ms.topic: article
---
# <span id="p_hlk_test.d0c757e4-44aa-4de8-9c8b-1b05b96855a9"></span>Hybrid Information Command Test (LOGO)
This test ensures that the following hybrid commands are working as defined in the requirements:
- Change by LBA
- Hybrid Control -Both threshold and disable/enable cache
- Evict
- Demote By Size
## Test details
|||
|---|---|
| **Specifications** | <ul><li>Device.Storage.Hd.Sata.HybridInformation.BasicFunction</li></ul> |
| **Platforms** | <ul><li>Windows 10, client editions (x86)</li><li>Windows 10, client editions (x64)</li></ul> |
| **Supported Releases** | <ul><li>Windows 10</li><li>Windows 10, version 1511</li><li>Windows 10, version 1607</li><li>Windows 10, version 1703</li><li>Windows 10, version 1709</li><li>Windows 10, version 1803</li><li>Next update to Windows 10</li></ul> |
|**Expected run time (in minutes)**| 240 |
|**Category**| Compatibility |
|**Timeout (in minutes)**| 14400 |
|**Requires reboot**| false |
|**Requires special configuration**| false |
|**Type**| automatic |
## <span id="Additional_documentation"></span><span id="additional_documentation"></span><span id="ADDITIONAL_DOCUMENTATION"></span>Additional documentation
Tests in this feature area might have additional documentation, including prerequisites, setup, and troubleshooting information, that can be found in the following topic(s):
- [Device.Storage additional documentation](device-storage-additional-documentation.md)
## <span id="Running_the_test"></span><span id="running_the_test"></span><span id="RUNNING_THE_TEST"></span>Running the test
Before you run the test, complete the test setup as described in the test requirements: [Hard Disk Drive Testing Prerequisites](hard-disk-drive-testing-prerequisites.md).
## <span id="Troubleshooting"></span><span id="troubleshooting"></span><span id="TROUBLESHOOTING"></span>Troubleshooting
For generic troubleshooting of HLK test failures, see [Troubleshooting Windows HLK Test Failures](../user/troubleshooting-windows-hlk-test-failures.md).
For troubleshooting information, see [Troubleshooting Device.Storage Testing](troubleshooting-devicestorage-testing.md).
Hybridflt.sys must be installed for this test to work properly.
## <span id="More_information"></span><span id="more_information"></span><span id="MORE_INFORMATION"></span>More information
The test should automatically turn the hybrid information on before checking the logs if it was not on already.
This test relies on some behavior of hybrids that are not tested in this particular test or in some test cases. Ensure that tagged I/Os go to the cache and that dirty data thresholds are respected.
You can use the Command Syntax section to execute a specific test case.
### <span id="Command_syntax"></span><span id="command_syntax"></span><span id="COMMAND_SYNTAX"></span>Command syntax
<table>
<colgroup>
<col width="50%" />
<col width="50%" />
</colgroup>
<thead>
<tr class="header">
<th>Command</th>
<th>Description</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td><p><strong>Hybriddrive.exe -drive <disk #> -scenario logcommand</strong></p></td>
<td><p>Runs the test.</p></td>
</tr>
<tr class="even">
<td><p><strong>-Drive <disk#></strong></p></td>
<td><p>The drive to be tested on. The behavior of boot drives or drives with a file system is not defined.</p></td>
</tr>
<tr class="odd">
<td><p><strong>-Verbosity</strong></p></td>
<td><p>The logging level for this test.</p></td>
</tr>
<tr class="even">
<td><p><strong>-?</strong></p></td>
<td><p>Displays help.</p></td>
</tr>
<tr class="odd">
<td><p><strong>-Scenario logcommand</strong></p></td>
<td><p>The scenario to run.</p></td>
</tr>
<tr class="even">
<td><p><strong>-case #</strong></p></td>
<td><p>The test case to run.</p></td>
</tr>
</tbody>
</table>
### <span id="Parameters"></span><span id="parameters"></span><span id="PARAMETERS"></span>Parameters
| Parameter name | Parameter description |
|------------------------|----------------------------------------------------------------|
| **Verbosity** | Verbosity of log output. 0 is least verbose, 4 is most verbose |
| **Scenario** | Scenario that test targets to. |
| **WDKDeviceID** | Instance path of device to test |
| **LLU\_NetAccessOnly** | User account for accessing test file share. |
| **LLU\_LclAdminUsr** | User account for running the test. |
| **StorageDriveNumber** | Drive number of device to test |
| 35.435714 | 256 | 0.670228 | eng_Latn | 0.660362 |
b9654ff1ca4d22ce050bf9c40c078b0e587c741e | 4,610 | md | Markdown | articles/mysql/howto-alert-on-metric.md | changeworld/azure-docs.tr-tr | a6c8b9b00fe259a254abfb8f11ade124cd233fcb | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/mysql/howto-alert-on-metric.md | changeworld/azure-docs.tr-tr | a6c8b9b00fe259a254abfb8f11ade124cd233fcb | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/mysql/howto-alert-on-metric.md | changeworld/azure-docs.tr-tr | a6c8b9b00fe259a254abfb8f11ade124cd233fcb | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Metrik uyarıları yapılandırma - Azure portalı - MySQL için Azure Veritabanı
description: Bu makalede, Azure portalından MySQL için Azure Veritabanı için metrik uyarıların nasıl yapılandırılabildiğini ve bunlara erişilen açıklanmaktadır.
author: rachel-msft
ms.author: raagyema
ms.service: mysql
ms.topic: conceptual
ms.date: 3/18/2020
ms.openlocfilehash: c917804b42bc987228bbb2542682fe9fb308a467
ms.sourcegitcommit: 2ec4b3d0bad7dc0071400c2a2264399e4fe34897
ms.translationtype: MT
ms.contentlocale: tr-TR
ms.lasthandoff: 03/28/2020
ms.locfileid: "80067886"
---
# <a name="use-the-azure-portal-to-set-up-alerts-on-metrics-for-azure-database-for-mysql"></a>MySQL için Azure Veritabanı ölçümlerinde uyarılar ayarlamak için Azure portalını kullanın
Bu makalede, Azure portalını kullanarak MySQL uyarıları için Azure Veritabanı'nı nasıl ayarlayabileceğiniz gösterilmektedir. Azure hizmetleriniz için izleme ölçümlerine dayalı bir uyarı alabilirsiniz.
Belirli bir metnin değeri atadığınız bir eşiği geçtiğinde uyarı tetikler. Uyarı, hem koşul ilk karşılaştığında hem de daha sonra bu koşul artık karşılanmadığında tetikler.
Bir uyarıyı tetiklediğinde aşağıdaki eylemleri yapmak üzere yapılandırabilirsiniz:
* Hizmet yöneticisine ve yardımcı yöneticilere e-posta bildirimleri gönderme
* Belirttiğiniz ek e-postalara e-posta gönderin.
* Web kancası çağırma
Şu bilgileri kullanarak uyarı kurallarını yapılandırabilir ve bilgi alabilirsiniz:
* [Azure portalında](../azure-monitor/platform/alerts-metric.md#create-with-azure-portal)
* [Azure CLI](../azure-monitor/platform/alerts-metric.md#with-azure-cli)
* [Azure İzleyici REST API'si](https://docs.microsoft.com/rest/api/monitor/metricalerts)
## <a name="create-an-alert-rule-on-a-metric-from-the-azure-portal"></a>Azure portalından bir metrik te uyarı kuralı oluşturma
1. Azure [portalında,](https://portal.azure.com/)izlemek istediğiniz MySQL sunucusu için Azure Veritabanı'nı seçin.
2. Kenar çubuğunun **İzleme** bölümü altında, gösterildiği gibi **Uyarılar'ı** seçin:
3. **Metrik uyarı ekle** (+ simgesi) seçeneğini belirleyin.
4. **Oluştur kuralı** sayfası aşağıda gösterildiği gibi açılır. Gerekli bilgileri doldurun:
5. **Koşul** bölümünde, **Koşul Ekle'yi**seçin.
6. Uyarılacak sinyaller listesinden bir metrik seçin. Bu örnekte, "Depolama yüzdesi"ni seçin.
7. **Koşul** (ör. "Büyük"), **Eşik** (ör. Yüzde 85), **Zaman Toplama**, **Zaman zaman** metrik kural uyarı tetikler önce memnun edilmelidir (ör. "Son 30 dakika içinde") ve **Frekans**.
Tamamlandığında **Bitti'yi** seçin.
8. Eylem **Grupları** bölümünde, uyarıda bildirim almak için yeni bir grup oluşturmak için **Yeni** Oluştur'u'nu seçin.
9. "Eylem grubu ekle" formunu bir ad, kısa ad, abonelik ve kaynak grubuyla doldurun.
10. **E-posta/SMS/Push/Voice** eylem türünü yapılandırın.
Bildirim almak için abonelik Sahiplerini, Katkıda Bulunanları ve Okuyucuları seçmek için "Azure Kaynak Yöneticisi Rolü'nü e-posta yla gönder"i seçin.
İsteğe bağlı olarak, uyarı çıktığında çağrılsın istiyorsanız **Webhook** alanında geçerli bir URI sağlayın.
Tamamlandığında **Tamam'ı** seçin.
11. Uyarı kural adı, Açıklama ve Önem belirtin.
12. Uyarıyı oluşturmak için **uyarı oluştur kuralını** seçin.
Birkaç dakika içinde, uyarı etkin dir ve daha önce açıklandığı gibi tetikler.
## <a name="manage-your-alerts"></a>Uyarılarınızı yönetme
Bir uyarı oluşturduktan sonra, uyarıyı seçebilir ve aşağıdaki eylemleri yapabilirsiniz:
* Bu uyarıyla ilgili önceki güne ait metrik eşiği ve gerçek değerleri gösteren bir grafiği görüntüleyin.
* Uyarı kuralını **düzenle** veya **sil.**
* Bildirimleri geçici olarak durdurmak veya bildirim almaya devam etmek istiyorsanız, uyarıyı **devre dışı bırakın** veya **etkinleştirin.**
## <a name="next-steps"></a>Sonraki adımlar
* [Uyarılardaki web hook'ları yapılandırma](../azure-monitor/platform/alerts-webhooks.md)hakkında daha fazla bilgi edinin.
* Hizmetinizin kullanılabilir ve yanıt veren olduğundan emin olmak için [metrik koleksiyonuna genel bir bakış](../monitoring-and-diagnostics/insights-how-to-customize-monitoring.md) alın.
| 51.222222 | 200 | 0.778525 | tur_Latn | 0.999618 |
b965ba0e508865e45c7fe50f0d34b34ba084f863 | 1,447 | md | Markdown | service-level-testing/rest-api/test-file/uripath.md | ematean/Doc | 44e61e8a35d0cd1f8786b99ffd5661cd6493680c | [
"MIT"
] | 1 | 2019-07-07T01:23:54.000Z | 2019-07-07T01:23:54.000Z | service-level-testing/rest-api/test-file/uripath.md | autonomx/AutonomxDoc | 44e61e8a35d0cd1f8786b99ffd5661cd6493680c | [
"MIT"
] | null | null | null | service-level-testing/rest-api/test-file/uripath.md | autonomx/AutonomxDoc | 44e61e8a35d0cd1f8786b99ffd5661cd6493680c | [
"MIT"
] | null | null | null | # UriPath
## UriPath
* UriPath column in CSV appends the Uri path to the base Url defined in the apiConfig.properties file
* ```text
apiConfig.properties:
# global configuration
api.uriPath = http://demo.autonomx.io
```
* Uri path value is then appened to the api.uriPath value
* eg. We append /auth/local to base url: http://demo.autonomx.io
## Override Uri Path
* We can override the base url value through setting the full url in the UriPath column
* eg. http://www.google.com
* The url must start with http or https
## Dynamic URI Values
* We can use stored values from config or set in the test file to set the uri path
* eg. <@site1> where site1 is set in apiConfig.properties
* ```text
apiConfig.properties:
# global configuration
api.uriPath = http://demo.autonomx.io
site1 = http://www.google.ca
```
* or <@site1><@uri1>. This then becomes http://www.google.ca/auth/local
* ```text
apiConfig.properties:
# global configuration
api.uriPath = http://demo.autonomx.io
site1 = http://www.google.ca
uri1 = /auth/local
```
## Query Parameters
* Query Parameters can be set by appending to the UriPath
* eg. /content-manager/explorer/user/?source=users-permissions
* Multiple query path can be added by &
* /content-manager/explorer/user/?source=users-permissions&key=value
| 27.301887 | 101 | 0.706289 | eng_Latn | 0.598775 |
b965e128de4e603ec05c66fc4e95d7f270fac8e8 | 2,471 | md | Markdown | README.md | rahulsrma26/paradise | 20058283068715ea90585be5d85822f4470452dd | [
"MIT"
] | 3 | 2020-09-11T01:56:11.000Z | 2020-10-20T12:45:05.000Z | README.md | rahulsrma26/paradise | 20058283068715ea90585be5d85822f4470452dd | [
"MIT"
] | null | null | null | README.md | rahulsrma26/paradise | 20058283068715ea90585be5d85822f4470452dd | [
"MIT"
] | null | null | null | # Paradise
A file sharing and media streaming solution for local networks. Using this utility you can start a local server on your machine that is visible to other devices like mobile, laptop etc. Which can be used to download/upload files from other machines.
## Why it's needed?
### Can't I just transfer files from/to External drive or internet.
This utility is useful for people that are using office/work laptop/device that usually disables USB ports and/or external disks. And you want to transfer locally, so that it will be faster as well as don't your internet data.
## Getting Started
These instructions will get you a server up and running on your local machine.
### Prerequisites
Requires: python 3.6+
### Installing
Paradise is available on [PyPi](https://pypi.org/project/paradise/) and can be easily installed using pip.
```
pip install paradise
```
If you already have paradise and want to update to a newer version
```
pip install -U paradise
```
You can get the cutting edge version directly from dev branch (this can be unstable)
```
pip install git+https://github.com/rahulsrma26/paradise
```
## Running
```
paradise
```
This will show the output and ip of your machine on local network
```
INFO: Uvicorn running on http://127.0.0.1:8000 (Press CTRL+C to quit)
INFO: Started reloader process [14192] using statreload
INFO: Started server process [1580]
INFO: Waiting for application startup.
[Visit url] http://192.168.0.123:8000
INFO: Application startup complete.
```
Web server can be reached using http://127.0.0.1:8000 on your browser on the same machine. But if you want to access the web server from other devices then you need to open `Visit url` in the browser. In this example it is `http://192.168.0.123:8000`.
## Built With
* [FastAPI](http://https://fastapi.tiangolo.com/) - Backend
* [Vue.js](https://vuejs.org/) - Client framework
## Authors
* **Rahul Sharma** - *Initial work* - [Rahul Sharma](https://github.com/rahulsrma26)
## License
This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details
## Acknowledgments
* Hat tip to anyone whose code was used
* Inspiration - [Testing & Packaging by Hynek Schlawack](https://hynek.me/articles/testing-packaging/)
| 31.278481 | 251 | 0.743424 | eng_Latn | 0.979002 |
b965e886915beb17825f91150be3c16a24b69638 | 118 | md | Markdown | naivecoin/naivecoin-ui/README.md | tqbdev/CNM-TH2015-CK | 47bc99a850ecf1a4608ece53a9479a5abc4f7f26 | [
"Apache-2.0"
] | null | null | null | naivecoin/naivecoin-ui/README.md | tqbdev/CNM-TH2015-CK | 47bc99a850ecf1a4608ece53a9479a5abc4f7f26 | [
"Apache-2.0"
] | null | null | null | naivecoin/naivecoin-ui/README.md | tqbdev/CNM-TH2015-CK | 47bc99a850ecf1a4608ece53a9479a5abc4f7f26 | [
"Apache-2.0"
] | 1 | 2019-10-07T00:42:47.000Z | 2019-10-07T00:42:47.000Z | # Naivecoin UI
The repository for chapter6 UI code of naivecoin
The naivecoin tutorial: https://lhartikk.github.io/
| 19.666667 | 51 | 0.788136 | kor_Hang | 0.414771 |
b9661cb81c29a912805a0d031a4bc09d470561b3 | 2,515 | md | Markdown | fortios/r/fortios_switchcontrollerqos_qospolicy.md | chrisjaimon2012/tfwriter | 1ea629ed386bbe6a8f21617a430dae19ba536a98 | [
"MIT"
] | 78 | 2021-01-15T14:10:30.000Z | 2022-02-14T09:17:40.000Z | fortios/r/fortios_switchcontrollerqos_qospolicy.md | chrisjaimon2012/tfwriter | 1ea629ed386bbe6a8f21617a430dae19ba536a98 | [
"MIT"
] | 5 | 2021-04-09T15:21:28.000Z | 2022-01-28T19:02:05.000Z | fortios/r/fortios_switchcontrollerqos_qospolicy.md | chrisjaimon2012/tfwriter | 1ea629ed386bbe6a8f21617a430dae19ba536a98 | [
"MIT"
] | 30 | 2021-01-17T13:16:57.000Z | 2022-03-21T12:52:08.000Z | # fortios_switchcontrollerqos_qospolicy
[back](../fortios.md)
### Index
- [Example Usage](#example-usage)
- [Variables](#variables)
- [Resource](#resource)
- [Outputs](#outputs)
### Terraform
```terraform
terraform {
required_providers {
fortios = ">= 1.11.0"
}
}
```
[top](#index)
### Example Usage
```terraform
module "fortios_switchcontrollerqos_qospolicy" {
source = "./modules/fortios/r/fortios_switchcontrollerqos_qospolicy"
# default_cos - (required) is a type of number
default_cos = null
# name - (required) is a type of string
name = null
# queue_policy - (optional) is a type of string
queue_policy = null
# trust_dot1p_map - (optional) is a type of string
trust_dot1p_map = null
# trust_ip_dscp_map - (optional) is a type of string
trust_ip_dscp_map = null
}
```
[top](#index)
### Variables
```terraform
variable "default_cos" {
description = "(required)"
type = number
}
variable "name" {
description = "(required)"
type = string
}
variable "queue_policy" {
description = "(optional)"
type = string
default = null
}
variable "trust_dot1p_map" {
description = "(optional)"
type = string
default = null
}
variable "trust_ip_dscp_map" {
description = "(optional)"
type = string
default = null
}
```
[top](#index)
### Resource
```terraform
resource "fortios_switchcontrollerqos_qospolicy" "this" {
# default_cos - (required) is a type of number
default_cos = var.default_cos
# name - (required) is a type of string
name = var.name
# queue_policy - (optional) is a type of string
queue_policy = var.queue_policy
# trust_dot1p_map - (optional) is a type of string
trust_dot1p_map = var.trust_dot1p_map
# trust_ip_dscp_map - (optional) is a type of string
trust_ip_dscp_map = var.trust_ip_dscp_map
}
```
[top](#index)
### Outputs
```terraform
output "id" {
description = "returns a string"
value = fortios_switchcontrollerqos_qospolicy.this.id
}
output "queue_policy" {
description = "returns a string"
value = fortios_switchcontrollerqos_qospolicy.this.queue_policy
}
output "trust_dot1p_map" {
description = "returns a string"
value = fortios_switchcontrollerqos_qospolicy.this.trust_dot1p_map
}
output "trust_ip_dscp_map" {
description = "returns a string"
value = fortios_switchcontrollerqos_qospolicy.this.trust_ip_dscp_map
}
output "this" {
value = fortios_switchcontrollerqos_qospolicy.this
}
```
[top](#index) | 19.960317 | 76 | 0.691054 | eng_Latn | 0.729807 |
b966402f5e3a7da4645972df971af2ec307262a2 | 31,798 | md | Markdown | CHANGELOG.md | KDPInnovations/cordova-plugin-firebase | ec32320584aaf6d9aa048b21c61f5cd03b74998f | [
"MIT"
] | null | null | null | CHANGELOG.md | KDPInnovations/cordova-plugin-firebase | ec32320584aaf6d9aa048b21c61f5cd03b74998f | [
"MIT"
] | null | null | null | CHANGELOG.md | KDPInnovations/cordova-plugin-firebase | ec32320584aaf6d9aa048b21c61f5cd03b74998f | [
"MIT"
] | null | null | null | # Version 10.1.2-cli
* (iOS): Bump Firebase SDK versions to v6.28.1 to resolve build freeze issue.
* Resolves [#460](https://github.com/dpa99c/cordova-plugin-firebasex/issues/460).
# Version 10.1.1-cli
* (iOS) Fix regression bug in `getToken()` introduced by [35a2a68e8db3808723c9f2fcb6aa176021f6c77a](https://github.com/dpa99c/cordova-plugin-firebasex/commit/35a2a68e8db3808723c9f2fcb6aa176021f6c77a).
* Resolves [#456](https://github.com/dpa99c/cordova-plugin-firebasex/issues/456).
* (iOS) Update to use Firebase SDK v6.28.0
* Resolves [#453](https://github.com/dpa99c/cordova-plugin-firebasex/issues/453).
# Version 10.1.0-cli
* (iOS) Use precompiled pod for Firestore to reduce build times.
* *BREAKING CHANGE:* Requires `cocoapods>=1.9` (previously `cocoapods>=1.8`).
* Adds hook script to check local cocoapods version during plugin install.
* Based on PR [#440](https://github.com/dpa99c/cordova-plugin-firebasex/pull/440).
* Resolves [#407](https://github.com/dpa99c/cordova-plugin-firebasex/issues/407).
* (Android) Fixed regression bug related to default Crashlytics permission.
* See [this comment](https://github.com/dpa99c/cordova-plugin-firebasex/issues/335#issuecomment-651218052).
* (iOS) Bump pinned Firebase SDK versions to latest 6.27.0
* See [release notes](https://firebase.google.com/support/release-notes/ios#version_6270_-_june_16_2020)
* (Android): Bump Firebase SDK versions to latest for Analytics & Inapp Messaging.
# Version 10.0.0-cli
* *BREAKING CHANGE:* (Android, iOS) Migrate from Fabric Crashlytics SDK to Firebase Crashlytics SDK.
** Based on [this commit](https://github.com/vickydlion/cordova-plugin-firebasex/commit/0dfb5753edcd9fc19a0e7a52fdd4fc79d6d976ea) in [PR #432](https://github.com/dpa99c/cordova-plugin-firebasex/pull/432).
** Resolves [#335](https://github.com/dpa99c/cordova-plugin-firebasex/issues/335).
** Removes `isCrashlyticsCollectionCurrentlyEnabled()` as it's no longer necessary to manually init Crashlytics and a runtime method exists to enable/disable it.
** For more info see the [Firebase Crashlytics SDK upgrade documentation](https://firebase.google.com/docs/crashlytics/upgrade-sdk).
* (iOS) Fix exception raised if another plugin as already configured Firebase
* Merged from PR [#419](https://github.com/dpa99c/cordova-plugin-firebasex/pull/419).
* (iOS) Handle case where LD_RUNPATH_SEARCH_PATHS is an array. Resolves [#344](https://github.com/dpa99c/cordova-plugin-firebasex/issues/344).
* (Android, iOS): Avoid collection state getting out of sync & remove restriction to override config defaults.
* Merged from PR [#423](https://github.com/dpa99c/cordova-plugin-firebasex/pull/423).
* (iOS) Fix escaping already escaped json.
* Merged from PR [#430](https://github.com/dpa99c/cordova-plugin-firebasex/pull/430).
* Further resolves [#401](https://github.com/dpa99c/cordova-plugin-firebasex/issues/401).
* (Android): Fix parsing of existing `colors.xml` when it contains multiple existing `<color>` to prevent overwriting the existing values.
* Resolves [#436](https://github.com/dpa99c/cordova-plugin-firebasex/issues/436).
* (Android, iOS): Return success/failure result when subscribing/unsubscribing from topics.
* Resolves [#422](https://github.com/dpa99c/cordova-plugin-firebasex/issues/422).
# Version 9.1.2-cli
* (Android) Fix retrieval of auth provider ID - [see here for more info](https://github.com/firebase/FirebaseUI-Android/issues/329#issuecomment-564409912)
* (iOS) Align retrieval of auth provider ID with Android.
* (Typing): correct return type of a method
* Merged from PR [#390](https://github.com/dpa99c/cordova-plugin-firebasex/pull/390).
* (Documentation) Update guidance and requirements when opening issues
* (iOS): Fix escaping of line endings in multi-line log messages being sent from native iOS implementation to JS console.
* Resolves [#401](https://github.com/dpa99c/cordova-plugin-firebasex/issues/401).
* (iOS): Set shouldEstablishDirectChannel via a plugin variable which defaults to false.
Resolves [#406](https://github.com/dpa99c/cordova-plugin-firebasex/issues/406).
* Bump androidx plugin version dependencies.
Resolves [#418](https://github.com/dpa99c/cordova-plugin-firebasex/issues/418).
# Version 9.1.1-cli
* (iOS): Bump Firebase SDK components to v6.23.0.
* Relates to [#373](https://github.com/dpa99c/cordova-plugin-firebasex/issues/373).
* See https://firebase.google.com/support/release-notes/ios#version_6230_-_april_21_2020.
* (Android) Bump Firebase SDK (and other Gradle dependencies) to latest versions.
* See https://firebase.google.com/support/release-notes/android#2020-04-23
# Version 9.1.0-cli
* (Android & iOS) *BREAKING CHANGE*: Add support for filters to `fetchDocumentInFirestoreCollection()`
* *BREAKING CHANGE* to function signature.
* Merged from PR [#367](https://github.com/dpa99c/cordova-plugin-firebasex/pull/367).
* (Android) Fix regression bug which causes CLI builds to fail on Android.
Resolves [#369](https://github.com/dpa99c/cordova-plugin-firebasex/issues/369).
# Version 9.0.3-cli
* (Android & iOS) Add `reloadCurrentUser()`
* (Doc) `createChannel()` suggestion for multiple sounds
* Merged from PR [#225](https://github.com/dpa99c/cordova-plugin-firebasex/pull/225).
* (iOS) Implement `getInfo()` for iOS.
* Merged from PR [#363](https://github.com/dpa99c/cordova-plugin-firebasex/pull/363).
* (Android & iOS) Add `signInUserWithCustomToken()` AND `signInUserAnonymously()` auth methods
* Merged from PR [#359](https://github.com/dpa99c/cordova-plugin-firebasex/pull/359).
# Version 9.0.2-cli
* (Android): Don't display app icon for large notification icon on Android. Resolves [#343](https://github.com/dpa99c/cordova-plugin-firebasex/issues/343).
* (Android & iOS) Sign out of Google signing out of Firebase. Resolves [#353](https://github.com/dpa99c/cordova-plugin-firebasex/issues/353).
* (Android & iOS) Add `documentExistsInFirestoreCollection()` and fix resolution of `fetchDocumentInFirestoreCollection()`.
# Version 9.0.1-cli
* Document `cli_build` branch.
* *BREAKING CHANGE*: Remove Firebase Inapp Messaging and Google Tag Manager SDK components due to causing Cordova CLI build issues.
* Resolves [#326](https://github.com/dpa99c/cordova-plugin-firebasex/issues/326).
# Version 9.0.0
* *BREAKING CHANGE*: Change method signature of `setCrashlyticsCollectionEnabled()` to `(enabled, success, error)` (from `()`) to allow enabling/disabling of Crashlytics at runtime and align it with `setPerformanceCollectionEnabled()` and `setAnalyticsCollectionEnabled()`
* Add `isCrashlyticsCollectionEnabled()` and `isCrashlyticsCollectionCurrentlyEnabled()` to respectively check if persistent Crashlytics setting is enabled and if Crashlytics is enabling during the current app session.
* Add `isAnalyticsCollectionEnabled()` and `isPerformanceCollectionEnabled()` to check if persistent settings are enabled.
* *BREAKING CHANGE*: Remove Firebase Inapp Messaging SDK component due to causing Cordova CLI build issues.
* Resolves [#326](https://github.com/dpa99c/cordova-plugin-firebasex/issues/326).
* (iOS) Override CDVPlugin class abstract method `handleOpenURL` instead of implementing app delegate method `application:openURL:options` to prevent conflicts with other plugins.
* Resolves [#328](https://github.com/dpa99c/cordova-plugin-firebasex/issues/328).
* (Android) Fix parsing of existing `colors.xml` when it only contains a single `<color>` to prevent overwriting the existing value.
* Fixes [#284](https://github.com/dpa99c/cordova-plugin-firebasex/issues/284).
# Version 8.1.1
* (Doc) Document custom FCM message handling.
* (Doc) Rationalise heading levels.
* (iOS) Implement message receiver mechanism (equivalent to existing Android mechanism) to enable custom handling of specific message types.
* (Android) Extend custom receiver to handle payload obtained from system notification message bundle received while in background/not running.
* (Android) Ignore invocation of auth state change listener at app start (same as on iOS) to prevent error due to race condition with plugin initialisation.
# Version 8.1.0
* Add support for Firebase inapp messaging
* Merged from PR [#312](https://github.com/dpa99c/cordova-plugin-firebasex/pull/312).
* Add support for Firestore realtime database. Resolves [#190](https://github.com/dpa99c/cordova-plugin-firebasex/issues/190).
* (Doc) Add note regarding persistence of data collection settings. Resolves [#315](https://github.com/dpa99c/cordova-plugin-firebasex/issues/315).
* (iOS) Added missing Google Tag Manager Pod for iOS.
* Merged from PR [#318](https://github.com/dpa99c/cordova-plugin-firebasex/pull/318).
* (iOS) Don't set `FirebaseScreenReportEnabled=false` in app list when `FIREBASE_ANALYTICS_COLLECTION_ENABLE=false`. Resolves [#317](https://github.com/dpa99c/cordova-plugin-firebasex/issues/317).
* (Android) Disable strict version check in Google Services plugin for Gradle as it causes erroneous build failures.
# Version 8.0.1
* Add `registerAuthStateChangeListener()` to support invocation of a callback function on the Firebase Authentication state changing.
Resolves [#311](https://github.com/dpa99c/cordova-plugin-firebasex/issues/311).
* (Android) Bump Firebase SDK dependency versions to latest releases. Resolves [#279](https://github.com/dpa99c/cordova-plugin-firebasex/issues/279).
* (iOS) Bump podspec versions for Firebase SDK components to [latest release (v6.17.0)](https://firebase.google.com/support/release-notes/ios#version_6170_-_february_11_2020)
# Version 8.0.0
* *BREAKING CHANGE*: Rework `verifyPhoneNumber()` to preserve and reference the native credentials object (rather than attempting to extract and parse its properties to JS). Fixes [#176](https://github.com/dpa99c/cordova-plugin-firebasex/issues/176).
* Add other Firebase Authentication methods: Google Sign In, Sign In with Apple, email/password sign in, and authentication utility methods. Partially resolves [#208](https://github.com/dpa99c/cordova-plugin-firebasex/issues/208).
* (Android) Add check `google-services` plugin does not already exist. Fixes [#282](https://github.com/dpa99c/cordova-plugin-firebasex/issues/282).
* (iOS) Update pinned Firebase SDK versions to latest v6.13.0. Resolves [#232](https://github.com/dpa99c/cordova-plugin-firebasex/issues/232).
# Version 7.0.2
* (Android) Fix error caused by local variable
* Merged from PR [#229](https://github.com/dpa99c/cordova-plugin-firebasex/pull/229).
* (iOS Hook) Fix retrieving Xcode project path
* Merged from PR [#234](https://github.com/dpa99c/cordova-plugin-firebasex/pull/234).
* (Android) Check google-services plugin doesn't already exist in Gradle script
* Merged from PR [#281](https://github.com/dpa99c/cordova-plugin-firebasex/pull/281).
# Version 7.0.1
* (Android) Replace references to cordovaActivity with applicationContext when app is not running and therefore cordovaActivity doesn't exist.
Resolves [#165](https://github.com/dpa99c/cordova-plugin-firebasex/issues/165).
* Fix .forEach is not a function.
Merged from PR [#219](https://github.com/dpa99c/cordova-plugin-firebasex/pull/219).
Resolves [#213](https://github.com/dpa99c/cordova-plugin-firebasex/issues/213).
* (Android) Parse this plugin's `plugin.xml` to extract default values for plugin variables not explicitly set at plugin install time.
Fixes [#218](https://github.com/dpa99c/cordova-plugin-firebasex/issues/218).
* (iOS) Fix after_prepare hook to run on multiple platforms so if they are added in one operation using `cordova prepare`, both platforms are processed.
Fixes [#221](https://github.com/dpa99c/cordova-plugin-firebasex/issues/221).
* (Typedef) Update the typedef for recent plugin API changes.
# Version 7.0.0
* (iOS) Update Firebase SDK to [v6.11.0 released 22 Oct 2019](https://firebase.google.com/support/release-notes/ios#version_6110_-_october_22_2019)
* (Android) Update pinned Firebase SDK versions to latest as of [25 Oct 2019](https://firebase.google.com/support/release-notes/android#2019-10-25)
Resolves [#207](https://github.com/dpa99c/cordova-plugin-firebasex/issues/207)
* (Doc) Document parameter types in API functions.
Resolves [#140](https://github.com/dpa99c/cordova-plugin-firebasex/issues/140)
* (Doc) fix `onMessageReceived()` code sample.
Merged from PR [#142](https://github.com/dpa99c/cordova-plugin-firebasex/pull/142).
* (Doc) Example sound name for custom Android notification sound.
Resolves [#160](https://github.com/dpa99c/cordova-plugin-firebasex/issues/160)
* (Feat): add Typescript declaration
Merged from PR [#166](https://github.com/dpa99c/cordova-plugin-firebasex/pull/166).
* (Doc) Fix `createChannel()` examples.
Merged from PR [#167](https://github.com/dpa99c/cordova-plugin-firebasex/pull/167).
* (Android) Expose `description` notification channel field.
Merged from PR [#168](https://github.com/dpa99c/cordova-plugin-firebasex/pull/168).
* (iOS) Update CocoaPods spec url to new CDN.
Merged from PR [#173](https://github.com/dpa99c/cordova-plugin-firebasex/pull/173).
* (Doc) Fix code example for default android icon.
Merged from PR [#174](https://github.com/dpa99c/cordova-plugin-firebasex/pull/174).
* (iOS) Support iOS 13 APNS format token change.
Merged from PR [#177](https://github.com/dpa99c/cordova-plugin-firebasex/pull/177).
* (Hook) Remove check for presence of platform in `config.xml`
Merged from PR [#185](https://github.com/dpa99c/cordova-plugin-firebasex/pull/185).
* (Feat) Expose Firebase Messaging autoinit API functions to allow enabling/disabling/checking of autoinit.
* If disabled and `unregister()` is called, a new token will not be automatically allocated.
* Resolves [#147](https://github.com/dpa99c/cordova-plugin-firebasex/issues/147).
* (iOS) Fix `logEvent()` so it doesn't generated warning message in console. Fixes [#154](https://github.com/dpa99c/cordova-plugin-firebasex/issues/154).
* (iOS) Handle notification messages that contain `"content-available":1` which wakes up the app while in the background to deliver the message payload immediately when the message arrives (without requiring user interaction by tapping the system notification).
Fixes [#158](https://github.com/dpa99c/cordova-plugin-firebasex/issues/158).
* (Android)(Do) Clarify Android custom notification icons example. Resolves [#183](https://github.com/dpa99c/cordova-plugin-firebasex/issues/183).
* (Doc) Add example of using stacktrace.js with `logError()`.
Clarifies [#118](https://github.com/dpa99c/cordova-plugin-firebasex/issues/118).
* (Doc) Add link to [cordova-plugin-firebasex-ionic3-test](https://github.com/dpa99c/cordova-plugin-firebasex-ionic3-test) Ionic 3 example project
* Add `signInWithCredential()` to sign user into Firebase account and `linkUserWithCredential()` to link user account with credentials obtained via `verifyPhoneNumber()`.
* (Android) *BREAKING CHANGE* Rework `verifyPhoneNumber()`
* Remove redundant `verified` in returned credentials object.
* Support mocking of instant verification for `verifyPhoneNumber()` on Android for integration testing.
* (iOS) *BREAKING CHANGE* Rework `verifyPhoneNumber()`
* Return the same credential object structure as Android.
* (iOS) Add `SETUP_RECAPTCHA_VERIFICATION` plugin variable to automatically set up reCAPTURE verification for phone auth.
* (Doc) Add section to explicitly document all supported plugin variables.
* (iOS) Add `onApnsTokenReceived()` to register a callback function to be invoked when the APNS token is allocated.
Resolves [#201](https://github.com/dpa99c/cordova-plugin-firebasex/issues/201).
* (Android) Tweak default empty values when sending stacktrace using `logError()`
* (Doc) Better example of using `logError()` to track unhandled JS exceptions vs logging a non-fatal logical error.
* (iOS) Modify `logError()` to send stacktrace.js output as an actual stacktrace instead of custom keys.
Resolves [#118](https://github.com/dpa99c/cordova-plugin-firebasex/issues/118).
* (Hook) Fix parsing of `config.xml` to extract app name.
Fixes [#139](https://github.com/dpa99c/cordova-plugin-firebasex/issues/139).
* (Android) Ensure functions which return a boolean result return an actual boolean type rather than a binary integer.
Fixes [#153](https://github.com/dpa99c/cordova-plugin-firebasex/issues/153).
* (Hook) Rework hook scripts to:
* be fully synchronous to eliminate race conditions (remove q dependency)
* use [xml-js](https://github.com/nashwaan/xml-js) (instead of [xml2js](https://github.com/Leonidas-from-XIV/node-xml2js)) to convert XML>JSON and JSON>XML
* (Android) handle existing `colors.xml`.
Resolves [#132](https://github.com/dpa99c/cordova-plugin-firebasex/issues/132).
# Version 6.1.0
* (iOS) Add `getAPNSToken()` plugin API method to get the APNS token on iOS. Derived from merging PR [#100](https://github.com/dpa99c/cordova-plugin-firebasex/pull/100).
* Merge PR [#103](https://github.com/dpa99c/cordova-plugin-firebasex/pull/103) - fix for app name containing an ampersand.
* Merge PR [#115](https://github.com/dpa99c/cordova-plugin-firebasex/pull/115) - fix for short attribute in app name.
* Merge PR [#121](https://github.com/dpa99c/cordova-plugin-firebasex/pull/121) - fixes missing resolution of promise in after_prepare hook which caused other plugins to not run their after_prepare script (a bug introduced in v6.0.7)
* (Android) Merge PR [#64](https://github.com/dpa99c/cordova-plugin-firebasex/pull/64) - replace Android hooks scripts to configure Gradle with actual Gradle configuration.
* (iOS) Add missing `tap` property for notification messages received while app is running in background.
* Based on https://github.com/arnesson/cordova-plugin-firebase/pull/1104
* Resolves [#96](https://github.com/dpa99c/cordova-plugin-firebasex/issues/96)
* (iOS) Fix issues causing foreground notifications not to display on first run. Fixes [#109](https://github.com/dpa99c/cordova-plugin-firebasex/issues/109).
* (iOS) Update string format when subscribing/unsubscribing topics. Resolves [#110](https://github.com/dpa99c/cordova-plugin-firebasex/issues/110]).
* Support disabling of data collection (analytics/performance/crashlytics) at app startup and manual enabling of these at runtime.
* Resolves [#116](https://github.com/dpa99c/cordova-plugin-firebasex/issues/116]) and [#79](https://github.com/dpa99c/cordova-plugin-firebasex/issues/79]).
* Remove Android implementation of `getBadgeNumber()`/`setBadgeNumber()` as it doesn't work on Android 8+.
* Resolves [#124](https://github.com/dpa99c/cordova-plugin-firebasex/issues/124]).
# Version 6.0.7
* Merge PR [#93](https://github.com/dpa99c/cordova-plugin-firebasex/pull/93): Update Fabric dependencies
* Port code to apply IOS_STRIP_DEBUG plugin variable to Podfile into this plugin's hook scripts (from cordova-plugin-cocoapod-supportx).
* Fixes [#89](https://github.com/dpa99c/cordova-plugin-firebasex/issues/89).
# Version 6.0.6
* Fix parameter type passed to hasPermission success callback for Android. Fixes [#83](https://github.com/dpa99c/cordova-plugin-firebasex/issues/83).
# Version 6.0.5
* Fix `hasPermission()` to return boolean result on Android (same as iOS).
* Update docs to flag this as a breaking change from `cordova-plugin-firebase`.
* Resolves [#81](https://github.com/dpa99c/cordova-plugin-firebasex/issues/81).
# Version 6.0.4
* Replace dependency on `cordova-lib` with `xml2js`.
* (iOS) Restore placeholder GoogleService-Info.plist.
* Partially reverts a9c66746ca3592f0eec217f7701d5835f33b43c5
* See [#74](https://github.com/dpa99c/cordova-plugin-firebasex/issues/74)
* (iOS) Handle and report native logical errors.
# Version 6.0.3
* (iOS) If grantPermission() is called when permission is already granted, return an error (rather than attempting to grant permission again which causes issues).
* See [#61](https://github.com/dpa99c/cordova-plugin-firebasex/issues/61)
* (iOS) Run badge number operations on UI thread (instead of background thread).
* Resolves [#72](https://github.com/dpa99c/cordova-plugin-firebasex/issues/72)
* (iOS) Handle situation where value of sound is not an NSString.
* See [#61](https://github.com/dpa99c/cordova-plugin-firebasex/issues/61)
* (iOS) Add try/catch handlers at all code entry points to handle unexpected exceptions in order to prevent app crashes. Log native exceptions to native and JS consoles.
* See [#61](https://github.com/dpa99c/cordova-plugin-firebasex/issues/61)
* Remove `google-services.json` and `GoogleService-Info.plist` placeholders.
* See [#63](https://github.com/dpa99c/cordova-plugin-firebasex/issues/63)
# Version 6.0.2
* (Android) Improved exception handling to prevent app crashes due to plugin exceptions.
Document caveats of received message payload when notification message is received while app is not running on Android.
Further resolves [#52](https://github.com/dpa99c/cordova-plugin-firebasex/issues/52).
# Version 6.0.1
* (Android) Expose notification message properties in message object sent to onMessageReceived().
Ensure message is always sent to onMessageReceived(), regardless if it was tapped.
Resolves [#52](https://github.com/dpa99c/cordova-plugin-firebasex/issues/52).
# Version 6.0.0
* *BREAKING CHANGES*
* `onMessageReceived()` is now called when a message is received (data or notification) AND when a system notification is tapped (whether app is running or not)
* Resolves [#48](https://github.com/dpa99c/cordova-plugin-firebasex/issues/48).
* The `tap` parameter passed to `onMessageReceived()` is only set if a system notification is tapped
* If the system notification was tapped while the app is running in the foreground, the value will be `tap: "foreground"`
* If the system notification was tapped while the app is not running / in the background, the value will be `tap: "background"`
# Version 5.0.0
* *BREAKING CHANGES*
* `onNotificationOpen()` renamed to `onMessageReceived()`
* Changed key names for custom notification properties in FCM data messages to display system notifications in foreground.
* Message payload is always delivered to `onMessageReceived()` for both data and notification messages.
* `messageType` key indicates type of FCM message: `notification` or `data`
* `tap` is only set when `messageType` is `notification`
* Explicit dependency on `cordova-plugin-androidx-adapter` since Android implementation uses AndroidX so is incompatible with Android Support Library.
* Set `remote-notification` background mode in native Xcode project for iOS.
* Reworked plugin documentation.
* Support customisable display of system notifications while app is in foreground for both notification and data messages (both Android & iOS).
* Set default color accent and notification channel for FCM notifications.
* Add support for default and custom notification channels for Android 8+
* Customise importance, visibility, LED light, badge number, notification sound and vibration pattern
* Calling `logError()` on Android now also logs to native logcat (as well as a non-fatal error to remote Crashlytics service).
* Fix `logError()` on iOS to log non-fatal error to remote Crashyltics service.
* Implement stubs for `hasPermission()` and `grantPermission()` on Android so they both return true in to the success callback.
* Rationalise permission check/request on iOS.
* Remove legacy support for iOS 9 and below.
* Support overridable default color accent for Android notification icons via `ANDROID_ICON_ACCENT` plugin variable.
# Version 4.0.0
* *BREAKING CHANGE:* set min supported versions to `cordova@9` and `cordova-ios@5`.
* Drop dependency on cordova-plugin-cocoapodsx to install pod dependencies.
* Instead update plugin.xml to use podspec formatting as required by cordova-ios@5.
* Remove iOS plugin variables as these are not (currently) supported by cordova-ios@5
* Resolves [#22](https://github.com/dpa99c/cordova-plugin-firebasex/issues/22).
# Version 3.0.8
* \[iOS\] Add support for stripping debug symbols for libraries included via Cocoapods. Resolves [#28](https://github.com/dpa99c/cordova-plugin-firebasex/issues/28).
# Version 3.0.7
* \[iOS\] Ensure runpath search path contains `$(inherited)` to avoid build warnings/issues. Resolves [#25](https://github.com/dpa99c/cordova-plugin-firebasex/issues/25).
# Version 3.0.6
* Update iOS to Firebase SDK v6.3.0 (from v5.20.2) - major version increment so update source code for breaking changes to API. Resolves [#9](https://github.com/dpa99c/cordova-plugin-firebasex/issues/9).
* Add support for NDK crashlytics on Android. Resolves [#17](https://github.com/dpa99c/cordova-plugin-firebasex/issues/17).
# Version 3.0.5
* Bump min version of cordova-plugin-cocoapod-supportx to 1.7.2 which fixes bug when using a plugin variable to specify the `ios-min-version` in `<pods-config>`
# Version 3.0.4
* Bump min version of cordova-plugin-cocoapod-supportx to 1.7.1 which supports using a plugin variable to specify the `ios-min-version` in `<pods-config>`
# Version 3.0.3
* Implement didReceiveRegistrationToken delegate for iOS. Resolves [#16](https://github.com/dpa99c/cordova-plugin-firebasex/issues/16).
* Document dependency on Cocoapods. Resolves [#15](https://github.com/dpa99c/cordova-plugin-firebasex/issues/15).
* Make min iOS version configurable. Resolves [#14](https://github.com/dpa99c/cordova-plugin-firebasex/issues/14).
# Version 3.0.2
* Update legacy Xpath reference to `<application>` element in `AndroidManifest.xml`
# Version 3.0.1
* Bump default iOS Firebase SDK version to 5.20.2 (https://firebase.google.com/support/release-notes/ios#version_5202_-_april_10_2019). Resolves [#8](https://github.com/dpa99c/cordova-plugin-firebasex/issues/8).
# Version 3.0.0
* Reapply: Support user-overriding of default Android Gradle & iOS Cocoapods versions using plugin variables.
# Version 2.1.2
* Revert: Support user-overriding of default Android Gradle & iOS Cocoapods versions using plugin variables.
* Since it's not working on iOS due to Cocoapods plugin dependency.
* Need to fix that plugin to handle plugin variables then reinstate this change in a major version release.
# Version 2.1.1
* Support user-overriding of default Android Gradle & iOS Cocoapods versions using plugin variables.
# Version 2.1.0
* Update Android source to use AndroidX class names and adds dependency on [cordova-plugin-androidx](https://github.com/dpa99c/cordova-plugin-androidx) for forward compatibility with future versions of Firebase libraries on Android.
* Note: if you include other plugins in your project which reference the legacy Android Support Library, you'll still need to include [cordova-plugin-androidx-adapter](https://github.com/dpa99c/cordova-plugin-androidx-adapter) in your project to dynamically patch them.
* Pins Firebase and Crashlytics Gradle dependencies to latest major version (to prevent build failures due to unexpected changes in subsequent major versions).
* Set minimum supported versions to `cordova@8+`, `cordova-android@8+`, `cordova-ios@4+`.
# Version 2.0.7
* Merge [PR #7](https://github.com/dpa99c/cordova-plugin-firebasex/pull/7): use `<pod>` instead of deprecated `<<framework type="podspec">`. Resolves [#5](https://github.com/dpa99c/cordova-plugin-firebasex/issues/5).
# Version 2.0.6
* Use Cocoapods to satisfy iOS Firebase SDK (rather than bundling with plugin). See https://github.com/arnesson/cordova-plugin-firebase/pull/972.
* Add support for logMessage() and sendCrash() functions (ported from cordova-fabric-plugin)
* Bump version of Crashlytics library on Android to current latest (v2.9.8 - Dec 2018)
* Bump Firebase SDK versions in iOS PodSpecs to latest version (v5.15.0)
* Remove redundant build-extras.gradle
* Set minimum iOS version to 9.0 in podspec
* Remove unnecessary extra <config-file> block which can lead to race condition
* Fixes issues cause by Firebase SDK updates on 5 April 2019 (https://firebase.google.com/support/release-notes/android#update_-_april_05_2019) which removed deprecated API features causing Android build failures.
See https://github.com/arnesson/cordov
* Fix compatibility with cordova@9 CLI
* Add explicit dependency on cordova-lib to prevent build error on iOS. Fixes #2.
---> **FORKED FROM `cordova-plugin-firebase` AS `cordova-plugin-firebasex`** <---
# Version 2.0.5
### Bug Fixes
- <a href="https://github.com/arnesson/cordova-plugin-firebase/issues/897">#897</a>: Fixed issue with after_prepare hook not copying required files
# Version 2.0.4
### Bug Fixes
- <a href="https://github.com/arnesson/cordova-plugin-firebase/issues/866">#866</a>: Fixed issue with loading .plist file on some iOS devices
# Version 2.0.3
### Features
- <a href="https://github.com/arnesson/cordova-plugin-firebase/pull/874">#874</a>: Added new api `setCrashlyticsUserId` which allows setting Crashlytics user identifier
- <a href="https://github.com/arnesson/cordova-plugin-firebase/pull/861">#861</a>: Updated `verifyPhoneNumber` api on android to add the following properties to the returned object:
- `code` - sms code
- `verified` - whether or not the verification was successful
### Bug Fixes
- <a href="https://github.com/arnesson/cordova-plugin-firebase/issues/869">#869</a>: Replace add/remove hooks with install/uninstall hooks to ensure proper configuration of the plugin
- <a href="https://github.com/arnesson/cordova-plugin-firebase/pull/870">#870</a>: Add error handling to `fetch` api on iOS
# Version 2.0.2
### Bug Fixes
- <a href="https://github.com/arnesson/cordova-plugin-firebase/issues/837">#837</a>: Fixed android build
# Version 2.0.1
### Bug Fixes
- <a href="https://github.com/arnesson/cordova-plugin-firebase/pull/836">#836</a>: Fixed Crashlytics on iOS
- <a href="https://github.com/arnesson/cordova-plugin-firebase/pull/830">#830</a>: Fixed initialization of firebase services
# Version 2.0.0
### Features
- <a href="https://github.com/arnesson/cordova-plugin-firebase/issues/796">#796</a>: Update Firebase SDK Version to 5.x
### Bug Fixes
- <a href="https://github.com/arnesson/cordova-plugin-firebase/issues/822">#822</a>: Can't use initFirebase() on 1.1.3 [Firebase isn't initialized]
- <a href="https://github.com/arnesson/cordova-plugin-firebase/issues/827">#827</a>: doc missing: initFirebase call needed before anything
- <a href="https://github.com/arnesson/cordova-plugin-firebase/pull/824">#824</a>: Removed initRemoteConfig method
# Version 1.1.4 (deprecated)
This version has been deprecated due to complications with PR <a href="https://github.com/arnesson/cordova-plugin-firebase/pull/784">#784</a>
# Version 1.1.3 (deprecated)
This version has been deprecated due to complications with PR <a href="https://github.com/arnesson/cordova-plugin-firebase/pull/784">#784</a>
# Version 1.1.2 (deprecated)
This version has been deprecated due to complications with PR <a href="https://github.com/arnesson/cordova-plugin-firebase/pull/784">#784</a>
# Version 1.1.1 (deprecated)
This version has been deprecated due to complications with PR <a href="https://github.com/arnesson/cordova-plugin-firebase/pull/784">#784</a>
# Version 1.1.0 (deprecated)
This version has been deprecated due to complications with PR <a href="https://github.com/arnesson/cordova-plugin-firebase/pull/784">#784</a>
# Version 1.0.5
To force cordova to use this version, add the following to your project's config.xml:
```
<plugin name="cordova-plugin-firebase" spec="1.0.5" />
```
or by running:
```
cordova plugin add [email protected] --save
```
| 72.268182 | 273 | 0.762752 | eng_Latn | 0.618564 |
b966af224c9de6084bed04f9b849d1a9ed326a35 | 1,802 | md | Markdown | texturepack/README.md | AbysssDevelopment/mcpi-repo | 502e31f94f3fe4b7d5046995b249a541bc9ef10d | [
"MIT"
] | null | null | null | texturepack/README.md | AbysssDevelopment/mcpi-repo | 502e31f94f3fe4b7d5046995b249a541bc9ef10d | [
"MIT"
] | null | null | null | texturepack/README.md | AbysssDevelopment/mcpi-repo | 502e31f94f3fe4b7d5046995b249a541bc9ef10d | [
"MIT"
] | null | null | null | # mcpi-texturepack
Code for adding texture packs into MCPI-Reborn.
> This repo is a upload of the code which was originally made by `NikZapp#6774` on Discord with minor tweaks to work with MCPI-Reborn. Here is a formatted version of the original README from NikZapp:
## MCPI Texturepack utility v1.1
Coded by NikZapp. This code is sadly not protected.
### Files not to touch:
+ `addpack.py`
+ `recoveryPack.zip`
`badgeFix.zip` changes the Minecon logo to an MCPI Approved logo, requested by @TheBrokenRail. `new_textures.mcpit` is a pack using `Bracket The Fox#6969`'s textures made from the newer version of Minecraft. `ZombiePigmanFix.zip` is a fix to the zombie pigman texture not showing the outside of heads.
### Features:
1. Install custom textures witout navigating in all the folders.
2. Every texture is fully customisable.
3. All textures are stored in one file.
4. Easy to use.
### Will be added soon:
+ [ ] HD Texture support!
+ [x] Autocompleting `gui_blocks.png` (how blocks look in your inventory)
+ [ ] More!
### How to use:
1. Execute the `addpack.py` file in the command line as root (using `sudo`, for example).
2. If you want to install a texturepack, input the path to it.
3. If you however want to remove all texturepacks, just press enter.
To create a texturepack, follow these steps:
1. Put all of your textures in one folder. There should be no subfolders, like this:
+ Not to do:
```
/path/to/your/pack/gui/gui2.png
/path/to/your/pack/terrain.png
/path/to/your/pack/mob/creeper.png
```
+ To do:
```
/path/to/your/pack/gui2.png
/path/to/your/pack/terrain.png
/path/to/your/pack/creeper.png
```
2. Compress the textures using the `.zip` format:
```
/path/to/your/pack.zip/gui2.png
/path/to/your/pack.zip/terrain.png
/path/to/your/pack.zip/creeper.png
```
Done!
| 33.37037 | 301 | 0.738069 | eng_Latn | 0.986085 |
b966c6bc3c2da7c33f1fecdda5cb8e6dc89abdce | 535 | md | Markdown | api/Excel.slicercache.cleardatefilter.md | ryanmajidi/VBA-Docs | 8b07050f4ff38fcabda606284ec5f6f6634e9569 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | api/Excel.slicercache.cleardatefilter.md | ryanmajidi/VBA-Docs | 8b07050f4ff38fcabda606284ec5f6f6634e9569 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | api/Excel.slicercache.cleardatefilter.md | ryanmajidi/VBA-Docs | 8b07050f4ff38fcabda606284ec5f6f6634e9569 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: SlicerCache.ClearDateFilter method (Excel)
keywords: vbaxl10.chm897098
f1_keywords:
- vbaxl10.chm897098
ms.prod: excel
ms.assetid: d999d249-c0c7-747c-b402-acc650df5367
ms.date: 06/08/2017
---
# SlicerCache.ClearDateFilter method (Excel)
Clears the filter for a timeline (date filter).
## Syntax
_expression_. `ClearDateFilter`
_expression_ A variable that represents a [SlicerCache object (Excel)](Excel.SlicerCache.md) object.
## Return value
**VOID**
## See also
[SlicerCache Object](Excel.SlicerCache.md)
| 15.735294 | 100 | 0.757009 | kor_Hang | 0.246873 |
b96710940d10696f0ddc1d41f5ed17b1524c5862 | 211 | md | Markdown | _posts/2014-3-3-Hello-World.md | jcc1110/jcc1110.github.io | 01ba9609e6b65783c3fdb8925ec11ce617d23066 | [
"MIT"
] | null | null | null | _posts/2014-3-3-Hello-World.md | jcc1110/jcc1110.github.io | 01ba9609e6b65783c3fdb8925ec11ce617d23066 | [
"MIT"
] | null | null | null | _posts/2014-3-3-Hello-World.md | jcc1110/jcc1110.github.io | 01ba9609e6b65783c3fdb8925ec11ce617d23066 | [
"MIT"
] | null | null | null | ---
layout: post
title: Bienvenidos!
---
Bienvenidos a mi primer Blog de prueba.
Buscando mejoras...
Proximamente...
CARGANDO en 3, 2, 1...
| 16.230769 | 67 | 0.71564 | spa_Latn | 0.868107 |
b9675e9a2661e9e249413999edb2b8d639b1c085 | 1,224 | md | Markdown | _news/2019-01-11-tutorial-5.md | bo-li-research/bo-li-research.github.io | d37517875e717bcec844f548f777a396fedfae41 | [
"MIT"
] | null | null | null | _news/2019-01-11-tutorial-5.md | bo-li-research/bo-li-research.github.io | d37517875e717bcec844f548f777a396fedfae41 | [
"MIT"
] | null | null | null | _news/2019-01-11-tutorial-5.md | bo-li-research/bo-li-research.github.io | d37517875e717bcec844f548f777a396fedfae41 | [
"MIT"
] | null | null | null | ---
title: "Three papers are top downloaded in 2018"
collection: news
type: "News"
permalink: /news/2019-01-11-tutorial-5
venue: "Bio. Opt. Express"
date: 2019-01-11
---
Congrats!
3 BOE papers are top downloaded in 2018
<br/>
<br/>
Paper 1: <br/>
M. Wang, C. Wu, D. Sinefeld, **B. Li**, F. Xia and C. Xu, ["Comparing the effective attenuation lengths for long wavelength in vivo imaging of the mouse brain,"](http://bo-li-research.github.io/files/paper-2018-BOE-2.pdf) Bio. Opt. Express, vol. 9, pp. 3534-3543 2018.
<br/>
Paper 2:<br/>
K. Charan, **B. Li**, M. Wang, C. P. Lin and C. Xu, ["Fiber-based tunable repetition rate source for deep tissue two-photon fluorescence microscopy,"](http://bo-li-research.github.io/files/paper-2018-BOE-1.pdf) Bio. Opt. Express, vol. 9, pp. 2304-2311 2018.
<br/>
Paper 3:<br/>
F. Xia, C. Wu, D. Sinefeld, **B. Li**, Y. Qin and C. Xu, ["In vivo label-free confocal imaging of the deep mouse brain with long-wavelength illumination,"](http://bo-li-research.github.io/files/paper-2018-BOE-3.pdf) Bio. Opt. Express, vol. 9, pp. 6545-6555 2018.
<br/>
<br/>
Two papers in Opt. Lett. and Apt. Opt. are top downloaded!
<br/>
<br/>
<br/>
<img src='/images/News-2019-01-11.jpg'>
| 38.25 | 269 | 0.677288 | eng_Latn | 0.472458 |
b967d30205faa14a18f213ab45ed0faae5b9e13c | 1,176 | md | Markdown | docs/core/transaction/verificationUnconfirmed.md | taimoor1234567/DDKCORE | 73ea1c21e3eb6f9abbe06ecf200e8f6ec4611ccc | [
"MIT"
] | 49 | 2018-12-20T05:00:37.000Z | 2021-09-11T10:47:26.000Z | docs/core/transaction/verificationUnconfirmed.md | taimoor1234567/DDKCORE | 73ea1c21e3eb6f9abbe06ecf200e8f6ec4611ccc | [
"MIT"
] | 45 | 2018-11-27T16:39:45.000Z | 2020-03-19T12:06:57.000Z | docs/core/transaction/verificationUnconfirmed.md | taimoor1234567/DDKCORE | 73ea1c21e3eb6f9abbe06ecf200e8f6ec4611ccc | [
"MIT"
] | 37 | 2018-11-13T18:18:35.000Z | 2021-12-02T12:35:29.000Z | # Verification unconfirmed transaction
Transaction verify takes place in several steps.
* Check the absence of sender `address` in black list.
* Check the absence of transaction `id` in [transaction storage](transaction/memoryStorage.md).
* Verifying the `signature` of transaction.
To verify `signature`, you need to get a data buffer from type of transaction, creation time, salt, sender public key and asset.
Create hash sha256 from data buffer, using [NodeJS Crypto](https://nodejs.org/api/crypto.html)
get buffer from signature, buffer from sender public key and verify signature using [sodium-native](https://www.npmjs.com/package/sodium-native) and method crypto_sign_verify_detached
* If the sender have second public key, we must to verify second signature of the transaction, using the same algoritm of verifying signature.
* Time of creation transaction must be the same or less then current slot time.
* Transaction must be not five days older then current slot
* Check transaction amount.
Sender account `balance` must be the same or more then sum of transaction `amount` and transaction `fee`
* Verify transaction [asset](transaction/asset/index.md)
| 78.4 | 184 | 0.789116 | eng_Latn | 0.974422 |
b9681c74a0ccfbff9b7d505ac45351dadf81d2fb | 2,534 | md | Markdown | desktop-src/WinAuto/aria-container--no-active-descendants--keyboard-events.md | citelao/win32 | bf61803ccb0071d99eee158c7416b9270a83b3e4 | [
"CC-BY-4.0",
"MIT"
] | 552 | 2019-08-20T00:08:40.000Z | 2022-03-30T18:25:35.000Z | desktop-src/WinAuto/aria-container--no-active-descendants--keyboard-events.md | citelao/win32 | bf61803ccb0071d99eee158c7416b9270a83b3e4 | [
"CC-BY-4.0",
"MIT"
] | 1,143 | 2019-08-21T20:17:47.000Z | 2022-03-31T20:24:39.000Z | desktop-src/WinAuto/aria-container--no-active-descendants--keyboard-events.md | citelao/win32 | bf61803ccb0071d99eee158c7416b9270a83b3e4 | [
"CC-BY-4.0",
"MIT"
] | 1,287 | 2019-08-20T05:37:48.000Z | 2022-03-31T20:22:06.000Z | ---
title: ARIA Container Role (without active descendant) Keyboard Accessibility Error
description: ARIA Container Role (without active descendant) Keyboard Accessibility Error
ms.assetid: 15EDD3CC-FC2A-42FC-95DD-B04D9AF3515E
keywords:
- AriaContainerWithoutActiveDescendantKeyboardAccessiblityId
ms.topic: article
ms.date: 05/31/2018
---
# ARIA Container Role (without active descendant) Keyboard Accessibility Error
## Text
Element is a focusable container without active descendant defined and without **OnKeyDown**/**OnKeyPress**/**OnKeyUp** event handlers (neither on container nor on one of child elements).
## Type
Error
## Description
This error applies to elements that have a container role, do not have an **aria-activedescendant** attribute, and are not disabled. These elements implement keyboard navigation among child elements by using the concept known as *roving index*. In this concept, the **tabindex** attributes of child elements are maintained dynamically, ensuring that at all times only one child element is in tab order.
This error indicates that a container element that does not have the **aria-activedescendant** attribute, and that is not disabled, is not accessible to keyboard users. The problem exists because the container does not have the needed keyboard event handlers (**keydown**, **keyup**, or **keypress**), and neither do any of the container's child elements.
To fix this error, define a **keydown**, **keyup**, or **keypress** event handler for the container or one of its child elements.
## Example
```HTML
<div role="listbox" id="listbox1" >
<div role="option" id="listbox1-1" tabindex="0" class="selected">Item 1</div>
<div role="option" id="listbox1-2">Item 2</div>
<div role="option" id="listbox1-3">Item 3</div>
...
<div>
<script>
...
listbox1.addEventListener('keyup', function(e) {
var itm = e.srcElement;
var prev = itm.previousElementSibling;
var next = itm.nextElementSibling;
if (e.keyCode == 38 && prev) {
// On arrow up move focus to the previous item.
itm.setAttribute('tabindex', '-1');
prev.setAttribute('tabindex','0');
prev.focus();
}
else if (e.keyCode == 40 && next) {
// On arrow down move focus to the next item.
itm.setAttribute('tabindex', '-1');
next.setAttribute('tabindex','0');
next.focus();
}
});
</script>
```
## Related topics
<dl> <dt>
[ARIA Container Role Keyboard Accessibility Error](aria-container-keyboard-events.md)
</dt> </dl>
| 30.53012 | 402 | 0.71468 | eng_Latn | 0.940352 |
b968b8d25e7b326933d9540845b4303e75461f0f | 303 | md | Markdown | README.md | KonstantinKlepikov/covid-kaliningrad | bd7402c07661cf93ad0e4bda69d22c7449660d60 | [
"MIT"
] | 5 | 2021-01-28T02:28:31.000Z | 2022-03-09T15:25:19.000Z | README.md | KonstantinKlepikov/covid-kaliningrad | bd7402c07661cf93ad0e4bda69d22c7449660d60 | [
"MIT"
] | 1 | 2021-01-01T23:14:19.000Z | 2021-01-01T23:14:19.000Z | README.md | KonstantinKlepikov/covid-kaliningrad | bd7402c07661cf93ad0e4bda69d22c7449660d60 | [
"MIT"
] | null | null | null | # covid-kaliningrad
Visualizing covid-19 data in Kaliningrad region (Russia).
This is a buld-in databaseless app.
For more information see the [article(rus)](https://konstantinklepikov.github.io/2021/01/10/zapuskaem-machine-learning-mvp.html)
[Application](https://covid-kaliningrad.herokuapp.com/)
| 30.3 | 128 | 0.788779 | eng_Latn | 0.356908 |
b96a5aeafea178f7a1008504fa25c5a53b2d7497 | 5,517 | md | Markdown | docs/xml-tools/how-to-use-xml-snippets.md | ryanshripat/visualstudio-docs | b400528a83bea06d208d95c77282631ae4a93091 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/xml-tools/how-to-use-xml-snippets.md | ryanshripat/visualstudio-docs | b400528a83bea06d208d95c77282631ae4a93091 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/xml-tools/how-to-use-xml-snippets.md | ryanshripat/visualstudio-docs | b400528a83bea06d208d95c77282631ae4a93091 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-07-31T20:49:34.000Z | 2020-07-31T20:49:34.000Z | ---
title: "How to use XML snippets"
ms.date: 11/04/2016
ms.prod: visual-studio-dev15
ms.technology: vs-xml-tools
ms.topic: conceptual
ms.assetid: 3a27375b-81cc-48f6-a884-e1cb8c4f78f5
author: gewarren
ms.author: gewarren
manager: douge
ms.workload:
- "multiple"
---
# How to: Use XML snippets
You can invoke XML snippets by using the following two commands on the XML Editor shortcut menu. The **Insert Snippet** command inserts the XML snippet at the cursor position. The **Surround With** command wraps the XML snippet around the selected text. Each XML snippet has designated snippet types. The snippet types determine whether the snippet is available with the **Insert Snippet** command, the **Surround With** command, or both.
After the XML snippet has been added to the editor, any editable fields in the snippet are highlighted in yellow, and the cursor is positioned on the first editable field.
## Insert snippet
The following procedures describe how to access the **Insert Snippet** command.
> [!NOTE]
> The **Insert Snippet** command is also available through the keyboard shortcut (**Ctrl**+**K**, then **Ctrl**+**X**).
### To insert snippets from the shortcut menu
1. Position the cursor where you want to insert the XML snippet.
2. Right-click and select **Insert Snippet**.
A list of available XML snippets is displayed.
3. Select a snippet from the list using the mouse, or by typing the name of the snippet and pressing **Tab** or **Enter**.
### To insert snippets using the IntelliSense menu
1. Position the cursor where you want to insert the XML snippet.
2. From the **Edit** menu, point to **IntelliSense**, and then select **Insert Snippet**.
A list of available XML snippets is displayed.
3. Select a snippet from the list using the mouse or by typing the name of the snippet and pressing **Tab** or **Enter**.
### To insert snippets through the IntelliSense Complete Word list
1. Position the cursor where you want to insert the XML snippet.
2. Begin typing the XML snippet that you want to add to your file. If automatic completion is turned on, the IntelliSense complete word list is displayed. If it does not appear, press **Ctrl**+**Space** to activate it.
3. Select the XML snippet from the complete word list.
4. Press **Tab**, **Tab** to invoke the XML snippet.
> [!NOTE]
> There may be cases when the XML snippet does not get invoked. For example, if you try to insert an `xs:complexType` element inside an `xs:element` node, the editor does not generate an XML snippet. When an `xs:complexType` element is used inside an `xs:element` node, there are no required attributes or subelements, so the editor does not have any data to insert.
### To insert snippets using the shortcut name
1. Position the cursor where you want to insert the XML snippet.
2. Type `<` in the editor pane.
3. Press **Esc** to close the IntelliSense complete word list.
4. Type the shortcut name of the snippet, and press **Tab** to invoke the XML snippet.
## Surround With
The following procedures describe how to access the **Surround With** command.
> [!NOTE]
> The **Surround With** command is also available through the keyboard shortcut (**Ctrl**+**K**, then **Ctrl**+**S**).
### To use surround with from the context menu
1. Select the text to surround in the XML Editor.
2. Right-click and select **Surround With**.
A list of available surrounds with XML snippets is displayed.
3. Select a snippet from the list using the mouse, or by typing the name of the snippet and pressing **Tab** or **Enter**.
### To use surround with from the IntelliSense menu
1. Select the text to surround in the XML Editor.
2. From the **Edit** menu, point to **IntelliSense**, and then select **Surround With**.
A list of available surrounds with XML snippets is displayed.
3. Select a snippet from the list using the mouse, or by typing the name of the snippet and pressing **Tab** or **Enter**.
## Using XML snippets
Once you choose an XML snippet, the text of the code snippet is inserted automatically at the cursor position. Any editable fields in the snippet are highlighted, and the first editable field is selected automatically. The currently selected field is boxed.
When a field is selected, you can type a new value for the field. Pressing **Tab** cycles through the editable fields of the snippet; pressing **Shift**+**Tab** cycles through them in reverse order. Clicking a field places the cursor in the field, and double-clicking a field selects it. When a field is highlighted, a ToolTip might be displayed, offering a description of the field.
Only the first instance of a given field is editable. When that field is highlighted, the other instances of that field are outlined. When you change the value of an editable field, that field is changed everywhere it is used in the snippet.
Pressing **Enter** or **Esc** cancels field editing and returns the editor to normal.
The default colors for editable code snippet fields can be changed by modifying the Code Snippet Field setting in the **Fonts and Colors** pane of the **Options** dialog box. For more information, see [How to: Change Fonts and Colors in the Editor](../ide/reference/how-to-change-fonts-and-colors-in-the-editor.md).
## See also
- [XML Snippets](../xml-tools/xml-snippets.md)
- [How to: Generate an XML Snippet From an XML Schema](../xml-tools/how-to-generate-an-xml-snippet-from-an-xml-schema.md)
- [How to: Create XML Snippets](../xml-tools/how-to-create-xml-snippets.md) | 48.823009 | 438 | 0.749683 | eng_Latn | 0.997444 |
b96bf4c720e1f305c99e1514386e73b2d0ccb645 | 2,509 | md | Markdown | sdk-api-src/content/dvbsiparser/nf-dvbsiparser-ipbdasiparser-geteit.md | amorilio/sdk-api | 54ef418912715bd7df39c2561fbc3d1dcef37d7e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | sdk-api-src/content/dvbsiparser/nf-dvbsiparser-ipbdasiparser-geteit.md | amorilio/sdk-api | 54ef418912715bd7df39c2561fbc3d1dcef37d7e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | sdk-api-src/content/dvbsiparser/nf-dvbsiparser-ipbdasiparser-geteit.md | amorilio/sdk-api | 54ef418912715bd7df39c2561fbc3d1dcef37d7e | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
UID: NF:dvbsiparser.IPBDASiParser.GetEIT
title: IPBDASiParser::GetEIT (dvbsiparser.h)
description: Gets the event information table (EIT) from the program and system information protocol (PSIP) tables in a Protected Broadcast Device Architecture (PBDA) transport stream.
helpviewer_keywords: ["GetEIT","GetEIT method [Microsoft TV Technologies]","GetEIT method [Microsoft TV Technologies]","IPBDASiParser interface","IPBDASiParser interface [Microsoft TV Technologies]","GetEIT method","IPBDASiParser.GetEIT","IPBDASiParser::GetEIT","dshow.ipbdasiparser_geteit","dvbsiparser/IPBDASiParser::GetEIT","mstv.ipbdasiparser_geteit"]
old-location: mstv\ipbdasiparser_geteit.htm
tech.root: mstv
ms.assetid: ab7df40a-6a1c-4017-bece-618fb75797cf
ms.date: 12/05/2018
ms.keywords: GetEIT, GetEIT method [Microsoft TV Technologies], GetEIT method [Microsoft TV Technologies],IPBDASiParser interface, IPBDASiParser interface [Microsoft TV Technologies],GetEIT method, IPBDASiParser.GetEIT, IPBDASiParser::GetEIT, dshow.ipbdasiparser_geteit, dvbsiparser/IPBDASiParser::GetEIT, mstv.ipbdasiparser_geteit
req.header: dvbsiparser.h
req.include-header:
req.target-type: Windows
req.target-min-winverclnt: Windows 7 [desktop apps only]
req.target-min-winversvr: None supported
req.kmdf-ver:
req.umdf-ver:
req.ddi-compliance:
req.unicode-ansi:
req.idl: Dvbsiparser.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:
- IPBDASiParser::GetEIT
- dvbsiparser/IPBDASiParser::GetEIT
dev_langs:
- c++
topic_type:
- APIRef
- kbSyntax
api_type:
- COM
api_location:
- dvbsiparser.h
api_name:
- IPBDASiParser.GetEIT
---
# IPBDASiParser::GetEIT
## -description
Gets the event information table (EIT) from the program and system information protocol (PSIP) tables in a Protected Broadcast Device Architecture (PBDA) transport stream.
## -parameters
### -param dwSize [in]
Reserved. Set to zero.
### -param pBuffer [in]
Reserved. Set to <b>NULL</b>.
### -param ppEIT [out]
Receives a pointer to the <a href="/previous-versions/windows/desktop/api/dvbsiparser/nn-dvbsiparser-ipbda_eit">IPBDA_EIT</a> interface. The caller must release the interface.
## -returns
If this method succeeds, it returns <b>S_OK</b>. Otherwise, it returns an <b>HRESULT</b> error code.
## -see-also
<a href="/previous-versions/windows/desktop/api/dvbsiparser/nn-dvbsiparser-ipbdasiparser">IPBDASiParser</a> | 33.453333 | 355 | 0.779593 | kor_Hang | 0.358765 |
b96d0d9e8ec6beaaf9803087ada7c7d4c691276e | 1,096 | md | Markdown | .github/PULL_REQUEST_TEMPLATE.md | Brainyackerz/st-device-sdk-c-ref | 78ef8367c732309cfca90817d9355a8f19178554 | [
"Apache-2.0"
] | 65 | 2019-10-31T03:36:12.000Z | 2022-03-08T01:16:33.000Z | .github/PULL_REQUEST_TEMPLATE.md | Brainyackerz/st-device-sdk-c-ref | 78ef8367c732309cfca90817d9355a8f19178554 | [
"Apache-2.0"
] | 33 | 2019-11-26T05:16:00.000Z | 2022-01-20T10:45:19.000Z | .github/PULL_REQUEST_TEMPLATE.md | Brainyackerz/st-device-sdk-c-ref | 78ef8367c732309cfca90817d9355a8f19178554 | [
"Apache-2.0"
] | 110 | 2019-11-01T04:23:50.000Z | 2022-03-28T21:05:22.000Z | <!--
Thank you for your interest in contributing to the SmartThings Device SDK(STDK for short) project.
Please read & check through marking lists before submitting pull requests.
-->
## Marking lists
- [ ] I have read the [Contributing Guidelines](https://github.com/SmartThingsCommunity/st-device-sdk-c/blob/master/CONTRIBUTING.md).
- [ ] I have read the [Samsung Individual CLA](https://github.com/SmartThingsCommunity/st-device-sdk-c/blob/master/doc/SAMSUNGCLA.docx) and agree with it
* We (SmartThings Device SDK team) may ask you to sign it for larger changes. In this case, once we receive it, we'll be able to accept your pull requests according to relevant laws.
- I submitted this PR against the correct branch:
- [ ] This pull-request is based on the latest [develop](https://github.com/SmartThingsCommunity/st-device-sdk-c-ref/tree/develop) branch.
- [ ] I have ensured local tests pass about my code changes.
## License
Your contribution will be licensed under the [Apache License Ver2.0](https://github.com/SmartThingsCommunity/st-device-sdk-c-ref/blob/master/LICENSE).
| 60.888889 | 187 | 0.763686 | eng_Latn | 0.960054 |
b96d2cc3ab3df9324599630a89922bcf98d6f7da | 164 | md | Markdown | README.md | tehistory/DLLScraper | 415142c48ac39c922dfd04fb1f1a2e1b238f702e | [
"Apache-2.0"
] | null | null | null | README.md | tehistory/DLLScraper | 415142c48ac39c922dfd04fb1f1a2e1b238f702e | [
"Apache-2.0"
] | null | null | null | README.md | tehistory/DLLScraper | 415142c48ac39c922dfd04fb1f1a2e1b238f702e | [
"Apache-2.0"
] | null | null | null | # DLLScraper
Designed to make a text file with the information needed to understand a dll and what it contains.
Still a work in progress but should be functional.
| 32.8 | 98 | 0.79878 | eng_Latn | 0.999943 |
b96e31503cd97d14c6f0702fd739379cdee39f89 | 52 | md | Markdown | content/gallery/2007-07-13-11-00-00--magnificent-condor-flight.jpg/index.md | Jaza/worldtrip | ddddb1601594daa8234405d2ff64f3406799fcea | [
"Apache-2.0"
] | null | null | null | content/gallery/2007-07-13-11-00-00--magnificent-condor-flight.jpg/index.md | Jaza/worldtrip | ddddb1601594daa8234405d2ff64f3406799fcea | [
"Apache-2.0"
] | null | null | null | content/gallery/2007-07-13-11-00-00--magnificent-condor-flight.jpg/index.md | Jaza/worldtrip | ddddb1601594daa8234405d2ff64f3406799fcea | [
"Apache-2.0"
] | null | null | null |
+++
draft = false
+++
_Magnificent condor flight._
| 8.666667 | 28 | 0.673077 | eng_Latn | 0.833541 |
b96e9776a2669dbd65184f62be942cab9e37e26b | 25,760 | md | Markdown | README.md | nqtronix/git-template | f0f5123ac11fbf7952f3e9ec4d9f683b2099f705 | [
"MIT"
] | null | null | null | README.md | nqtronix/git-template | f0f5123ac11fbf7952f3e9ec4d9f683b2099f705 | [
"MIT"
] | null | null | null | README.md | nqtronix/git-template | f0f5123ac11fbf7952f3e9ec4d9f683b2099f705 | [
"MIT"
] | 2 | 2021-01-18T09:14:08.000Z | 2021-01-29T17:47:14.000Z | <!-- banner: can be a image or a large font-->
<h1 align="center" style="font-weight: bold; margin-top: 20px; margin-bottom: 20px;">git-template</h1>
<!-- blurb: shortest possible summary (one line max) -->
<h3 align="center" style="font-weight: bold; margin-top: 20px; margin-bottom: 20px;">A simple and clean git repository template.</h3>
<!-- badges: meaningful meta information (one line max), do NOT include anything immediately visible -->
<p align="center">
<a href="#changelog"><img src="https://img.shields.io/github/release-pre/nqtronix/git-template.svg" alt="release: NA"></a>
<a href="https://github.com"><img src="https://img.shields.io/badge/platform-github.com-blue.svg" alt="platform: github.com"></a>
<a href="#status"><img src="https://img.shields.io/badge/status-maintained-green.svg" alt="status: maintained"></a>
<a href="https://github.com/nqtronix/git-template/issues"><img src="https://img.shields.io/github/issues/nqtronix/git-template.svg" alt="issues: NA"></a>
<a href="#license"><img src="https://img.shields.io/github/license/nqtronix/git-template.svg" alt="license: NA"></a>
</p>
<!-- quick links: local links (one line max) -->
<!-- Link to the (most important) h2 chapters, but do NOT link to anything visible without scrolling -->
<p align="center">
<a href="#getting-started">Getting Started</a> •
<a href="#documentation">Documentation</a> •
<a href="#under-the-hood">Under the Hood</a> •
<a href="#support">Need Help?</a> •
<a href="#about">About</a> •
<a href="#credits-and-references">Credits</a>
</p>
<!-- separate h2 chapters with white space: <br> -->
<br>
## Introduction
**Open Source is amazing.** It lets us create new things without having to re-invent the wheel every time. Well, at least in theory. Most things have been done by someone, somewhere, but only a fraction is published and documented. And that's likely because many developers don't like the overhead of writing documentation. **So, let's make it dead simple!**
**git-template** contains all the essential files to make your repository **useful _and_ pretty**. Copy templates, fill in your details and get back to do the things you love most. It's that simple, really. Check out the [documentation](#documentation) to learn about our design principles.
<br>
## Key Features
- **best of git:** embraces common design practices used in dozens of repositories
- **skim-able:** most relevant info is visible at first glance
- **pre-formatted**: the design is ready-to-use, just fill in your details
- **self documenting:** instead of placeholders, this file contains details about itself
<br>
## Usage Example
This readme is a template _and_ a usage example of itself, so technically no separate example is needed.
The screenshot below is from one of my projects, which uses this template. You can find that project and many more under [related projects](#related-projects).
<a href="https://github.com/nqtronix/fifofast"><img src="https://raw.githubusercontent.com/nqtronix/git-template/master/example.png" alt="Usage Example Screenshot"></a>
<br>
## Getting Started
You've never written a readme and want to do it _right_ straight from the start? Then just follow the steps below. If you run into problems, please [ask for clarification](#get-help).<br>
### Step 1: Software and Tools
There are countless programs that can edit markdown formatted files:
- **[markdownify][prog-markdownify] [Windows, free]**<br>
My personal favorite. The code is highlighted and converted into a live preview. The UI is intuitive and minimalistic. Local links are supported and even images from the internet (such as badges) are shown in the preview.
- **[markdown editor][prog-markdown-editor] [Web, free]**<br>
Not as good as markdownify, but available without installing anything. Its formatting closely resembles how it will look on GitHub.
- **Any text editor**<br>
You may already use Notepad++, Atom or any other editor. They all work, but may not offer a preview and therefore I wouldn't recommend them to beginners.
### Step 2: Download **git-template**
- **Copy this repository**<br>
Clone it or hit [Download][git-download] and extract the .zip file.
### Step 3: Add your details
- **Copy the files to your repo**<br>
If you don't have any of the included files, just drag + drop them into your existing repository.
- **Edit it**<br>
Open the file with the editor of your choice and tailor it to your project. Delete everything you don't need, add stuff you think is missing. It's _your_ readme after all.
<br>
## Documentation
>No one reads anything on the internet. <sup>[[link][video-people-dont-read]]
Not even your readme. Especially not if you treat it like many people and just dump a bunch of information about your project in it. So let's take a more interesting approach.
**Your readme is the landing page for your project, the first thing every visitor sees.** To convince someone to stay, you have no more [than a few seconds][article-few-seconds]. So make them count:
<br>
1. **State Your Purpose**<br>
All your creative efforts have a reason. [Start by telling _why_][video-start-with-why] your project exists and _why_ anyone should have interest in it. As humans we crave meaning and purpose more than anything else. Be short and precise.
2. **First Things First**<br>
Outline the the scope of your project. Even if visitors are inspired by your _why_, it dosen't matter if it does not fit their requirements, no matter how great your code is. And that is ok. [Badges](#--badges) are a perfect tool to visualize what your project is and what it isn't.
3. **No Clutter**<br>
Get rid of everything else. No worries, you can bring it up later, but for for now it's just distraction. When in doubt, be generous with white space. Less is More.
<br>
### Write it Skim-able
> People don't read, they **_scan_**. <sup>[[link][video-people-dont-read-scan]]
If a paragraph seems useless, they skip to the next. This results in an [F-shaped pattern][video-fshape] of attention. Naturally you should place important things at the beginning of the page. Limit your paragraphs to **one idea** and try to indicate it at its start.
<br>
Additionally you can provide **visual clues** with a good formatting:
- meaningful images
- bullet lists
- variation in typeface ([link][git-readme], **bold**, _etc_)
- code snippets
- quotes
- white space
Together these changes can increase the comprehension of your text [by up to 124%][article-read-on-the-web].
<br>
### RDD - Readme Driven Development
The term "Readme Driven Development" was coined by Tom Preston-Werners and [this blog post][article-rdd]. The key takeaway is, that you should write your readme prior to **anything else**. No code, not documentation, no use cases should be written before a readme. This allows you to clarify your thoughts and remind you of the things you need to implement. I honestly think it's a good practice to follow.
Of course, that readme will be vastly different from the readme you are reading write now. There will be almost no formatting, minimal links, no pictures and no badges.
**This doesn't mean that you have to start over to adopt this template.** Just copy & paste your notes into the chapters "Documentation" and "Under The Hood".
<br>
### Structure
The structure of your readme should follow the principles laid out in the previous two sections. Each project has some different requirements, so feel free to remove or add new chapters to the template.
These are the contents of my **ideal readme**. They are described in the next chapter in detail.
```
README.md
├───┬── Banner
│ ├── Summary
│ ├── Badges
│ └── Quick Links
├───┬── Introduction
│ ├── Key Features
│ ├── (Dependencies)
│ └── Usage Example
├── Getting Stated (Install & Configure)
├── Documentation (Usage/API/Testing)
│ ├── ...
│ └── ...
├── Under the Hood (Internals)
│ ├── ...
│ └── ...
├── Support
│ ├── FAQ
│ ├── Get Help
│ └── Contribute
├── About
│ ├── Status
│ ├── Known Issues
│ ├── Planned Features
│ ├── Changelog
│ └── Contact (The Author/Maintainer)
├── Credits and References
│ ├── Projects Used
│ ├── Related Projects
│ └── Additional Resources
└── License
```
<br>
## Under the Hood
<!-- the colon (:) behind each entry below is to distinguish it in local links: [link](#key-features) is different form [link](#key-features:) -->
### Banner
Start the readme with the name of your project in a large font. Alternatively you can create a banner or a logo to stand out. ~~If you feel like it, you can even use some ASCII art.~~ Although you can use ASCII art, github can't be conviced to center it.
### Summary
Write a _single line_ to summarize the essence of the project. It doesn't even have to be a full sentence. Expressing clearly what your goal is can be insanely hard, but is a crucial part of the introduction. If you can't tell what this is all about, who else will be?
<br>
### Badges
Metadata is best added in form of **badges** right below the summary. They help viewers to decide whether your project meets their requirements. The information is picked up intuitively: <a href="#--badgers"><img src="https://img.shields.io/badge/category-value-blue.svg" alt="category: value"></a>
The left side classifies the category, the right side the value. The background color can be customised to illustrate the value. Often they are click-able and take you to a page with more detailed information. There are even a few dynamic badges based on data from the GitHub API or external tools.
<br>
**Badges should be used to provide additional information _only_.** Meaningless badges de-valuate the important ones. [A recent study][study-badges-paper] shows that the number of downloads (and therefore the community interest) is greatest with 4 to 6 badges. If yours fit into one line, you should be generally fine, though.
For more details about which badges you should consider, check out the included [**badges.md**][git-badges] file.
<br>
### Quick Links
Many readmes have a table of contents (TOC), which adds a lot of bloat to the beginning of the readme. Most of the links won't be used anyway. So instead I suggest to add **a single line of quick links**, inspired by [markdownify][prog-markdownify]'s readme.
Each link refers to a main chapter of the readme. The first chapters "_Introduction_", "_Key Features_" and "_Getting Started_" are visible without scrolling and don't need a link. Note that the keywords don't have to match up with the chapters title. For example I prefer "_Need Help?_" instead of "_Support_" as it seems more friendly to me.
<br>
### Introduction
The introduction should be short and to the point as described in [documentation](#documentation).
Generally I'd suggest to split the introduction into **two short paragraphs**:
1. Why does your project exist? What was the problem, that had to be addressed?
2. How does your project address that problem? What does it do in a nutshell?
The second paragraph should ideally start with the projects name in bold, followed by a verb describing what it does. Limit yourself to about 5 lines per paragraph.
<br>
### Key Features
Make a bullet list of your projects best features. This is more about what aspects _you_ value, than all the great things it can do. You probably already know what you what to put there anyway.
<br>
### Usage Example
A picture, screenshot or a few lines of code say more than a thousand words. Choose a common use case and demonstrate how _intuitive and straightforward_ your project handles that situation. Link to more complex examples if you want to.
<br>
### Getting Started
Assume your viewer has a general understanding of programming, but does not know your tools or workflow well. The very first experience should work out-of-the-box, so give detailed starting instructions. Breaking it down into manageable steps can be very helpful for this. Link to all the software that has to be installed. **Make starting as trivial as you can.**
The "Getting Started" section in this readme seems ridiculous, I know, and I've definitely overdone it a bit (every programmer can edit a text file, I hope). However I think it illustrates my point quite nicely.
<br>
### Documentation
Quite often you hear documentation belongs in a separate document and that is definitely true for large project. But for the smaller projects I don't consider it required.
Your documentation should tell the reader _how to use_ the software and _not how it works_. Write about what each function does, what their arguments are, what it returns. That sort of thing. **When in doubt, give examples.**
<br>
### Under the Hood
You've done something clever and are eager to talk about it? Now you can! write about the internals of your project to your hearts content. Everyone who got this far actually cares about the details, so most of the viewers _care_ about what you have to say. Talk about how it all came to be, what problems you've face, what didn't work or teach a few cool tricks. But if you don't want to, that's fine too.
<br>
### Support
Provide help for the most common issues and error messages; a [FAQ](#faq) can be particularly useful. Offer some way of asking all questions that are not answered yet. You can use the build-in issue tracker or an external tool for this.
Although many GitHub users will know how to contribute to a project, be friendly to the new users and point them to your [CONTRIBUTING.md][git-contribute] for additional information.
<br>
### About
The about section contains any meta information about the project. Explain the current status, list major known issues, planned features, give a short changelog (but that can be a separate file, too) and offer some way of contacting you.
<br>
### Credits and References
**Say "Thanks"** to all the people, whose work somehow helped you and include a link, if applicable. You should do this even if you're not obligated by any license. A little appreciation can go a long way (and make someones day).
<br>
### License
Every project **needs** a license. If you don't, now one is allowed to do anything with your code. Considering you put all this effort into publishing it, I dont think that's what you want. **If you are unsure what license is best for you, visit [choosealicense.com][choosealicense.com]**.
<br>
The most popular license is the [MIT License][license-mit]. It is permissive and short enough to be understood without a lawyer. It is recommended by Tom Preston-Werner on his [blog][article-open-source-everything].
You might be tempted to give up all your rights and put your project int "public domain", but this simply does not work in some countries. [This answer on opensource.stackexchange.com][license-mit-vs-cc0] explains some issues quite well. If you still want to do that, the [CC0 1.0 License][license-cc0] might be the best option. It's advantage above other "public domain" licenses is it's fallback clause [to function as a license][license-cc0-fallback].
**That said, I am not a lawyer and will not take responsibility for any choice you make.**
<br>
## Support
### FAQ
- **Q: But _why_ should I use your template and not [this][readme-fvcproductions], [this][readme-fcpb], [this][readme-richardlitt], [this][readme-zalando] or [that][readme-noffle]?**<br>
A: Feel free to use whatever you like. I've read them and many more (yes, even the long blocks of text), but wasn't particularly happy with any of those option. So I made my own. You may use it, too.
- **Q: It's all too much!**<br>
A: Delete whatever you don't need: Sections, badges, formatting; nothing is set in stone. In fact for each of my projects I will copy this readme and delete a good part of it. But having a single, complete readme ensures that all derived works share the same structure.
- **Q: You love badges, don't you?**<br>
A: YES, as long as they are useful. Please do not add a bunch of them in the middle of your readme, unless you're writing about badges.
- **Q: Nobody asked these questions, right?**<br>
A: Uhhh, maybe? Look, I did need examples to fill this section. And nobody is going to notice anyway. Not this far down in the document, on the fourth question. There's no way. Have I told that I'm on instructables.com? I've still got a few pro membership codes, just tell me if you want one. I bet it takes months until someone notices this.
- **Q: What's your favorite color?**<br>
A: This is getting ridiculous. Don't you have something better to do than reading a made up FAQ?
<br>
### Get Help
**Your question or problem wasn't solved in the FAQ?** No worries! Just open up a new issue in the [GitHub issue tracker][git-issues]. Please provide all information to reproduce your problem. If you don't have a GitHub account (and can't be bothered to create one,) you can [contact](#contact) me directly.
<br>
### Contribute
**Spotted an error?** [Open an issue][git-issues] or submit a pull request.
There is no CONTRIBUTING.md yet, sorry. Contributions will inherit the [license](#license) of this project. If you have any questions, just ask.
<br>
## About
### Status
**This project is currently classified as** <a href="https://github.com/nqtronix/git-template/blob/master/badges.md#project-status"><img src="https://img.shields.io/badge/status-maintained-green.svg" alt="status: maintained"></a><br>
_The developers intend to keep the code in working condition by updating dependencies, fixing bugs and solving issues._
Without a doubt the readme is an important part of open source projects. I wanted to get it _right_ with everything I publish. This template is the result of my research. I do not consider it perfect, but "good enough" for most repositories. Major changes are not planned.
<br>
### Known Issues
- none (that are reported)
<br>
### Planned Features
- Add a CONTRIBUTING.md file
<br>
### Changelog
This project uses [**Semantic Versioning 2.0.0**][semver.org]. During initial development (0.x.x versions) any _major_ increase is substituted with a _minor_ increase (0.1.0->0.2.0 instead of 0.1.0->1.0.0).
The message of each commit contains detailed information about the changes made. The list below is a summary about all significant improvements.
- **0.1.0 (latest)**
- initial release
<br>
### Contact
If you haven't done so already, please check out [Get Help](#get-help) for the fastest possible help on your issue. Alternatively you can find my public email address on my [profile][git-profile].
<br>
## Credits and References
### Projects Used
- **[Awesome Readme][readme-matiassingers]** - _A curated list of awesome READMEs_<br>
Thanks [@matiassingers][at-matiassingers] for all the examples, hints and inspiration! This template would be quite different without you.
- [**Structured README**][readme-shaloo]<br>
Unfortunatly I found this little gem just after this readme was completed, but we share many common ideas. Thanks [@shaloo][at-shaloo]!
- **[markdownify][prog-markdownify]** - _A minimal markdown editor desktop app_<br>
A intuitive and responsive editor with all the features you could wish for. It even fetches badges from the internet and displays them! It may sound odd, but it has been quite fun to write this readme. Thanks [@amitmerchant1990][at-amitmerchant1990] for that great tool!
- **[shields.io][shields.io]** - _badges as a service_ <br>
A very clever solution to deliver custom and scalable badges. Thanks to the whole [@badges][at-badges] team!
- **[Text ASCII Art Generator][prog-ascii-art]**<br>
Get any in a variety of ASCII Art fonts. It's very simple and intuitive to use. Thanks [@patorjk][at-patorjk]!
<br>
### Related Projects
- [**fifofast**][git-repo-fifofast] - _A fast, generic fifo for MCUs._
- [**unittrace**][git-repo-unittrace] - _A simple testing and debugging tool for MCUs inspired by MinUnit._
- [**ahk-utf8-anywhere**][git-repo-ahk-utf8-anywhere] - _Turn keywords into utf8 characters anywhere you need to._
Want yours to be listed here, too? Create a merge request or [**get in touch**](#get-help).
<br>
### Additional Resources
All works referenced throughout this readme are listed below for your convenience. Thank you for sharing your thoughts and ideas with the world.
<br>
#### Human Behavior
- [**How to Write Documentation for People that Don't Read**][video-people-dont-read] by Kevin Burke
- [**How Users Read on the Web**][article-read-on-the-web] by Jakob Nielsen
- [**F-Pattern in Reading Digital Content**][video-fshape]
- [**Do You Have A 7 Second Website?**][article-few-seconds]
- [**Start with _why_**][video-start-with-why] TED Talk by Simon Sinek
- **[Study on badges on GitHub][study-badges], or as a [pdf][study-badges-paper]** - _"Adding Sparkle to Social Coding: An Empirical Study of Repository Badges in the npm Ecosystem"_
#### Thoughs about the Readme
- [**Readme Driven Development**][article-rdd] by Tom Preston-Werner, founder of GitHub ([@mojombo][at-mojombo])
- [**Sample Readme**][readme-fvcproductions] by [@fvcproductions][at-fvcproductions]
- [**Open Source Project Template**][readme-fcpb] by [@cfpb][at-cfpb]
- [**Art of README**][readme-noffle] by [@noffle][at-noffle]
- [**Standard Readme**][readme-richardlitt] by [@richardlitt][at-richardlitt]
- [**Zalando's README Template**][readme-zalando] by [@zalando][at-zalando]
#### Formatting
- [**Basic writing and formatting syntax**][markdown-git] on GitHub
- [**Markdown Cheatsheet**][markdown-cheatsheet] by [@adam-p][at-adam-p]
#### Licensing
- [**choosealicense.com**][choosealicense.com]
- [**License MIT**][license-mit]
- [**License CC0**][license-cc0]
- [**License CC0 - fallback clause**][license-cc0-fallback]
- [**How can I place software in the public domain?**][license-mit-vs-cc0] on opensource.stackexchange.com
- [**Open Source (Almost) Everything**][article-open-source-everything] by Tom Preston-Werner ([@mojombo][at-mojombo])
<br>
## License
This project is proudly licensed under the [MIT license][git-license].
The MIT license was chosen to give you the freedom to use this project in any way you want, while protecting all contributors from legal claims. Good code works, great code works for everyone. If this code has become a part of one of your projects, a link back to us would be highly appreciated. Thanks!
<!-- LINKS -->
<!-- in-line references: websites -->
[choosealicense.com]:https://choosealicense.com
[shields.io]:https://shields.io
[hackaday.io]:https://hackaday.io
[semver.org]:https://semver.org/
<!-- in-line references to people -->
[at-adam-p]:https://github.com/adam-p
[at-amitmerchant1990]:https://github.com/amitmerchant1990
[at-badges]:https://github.com/badges
[at-cfpb]:https://github.com/cfpb
[at-fvcproductions]:https://github.com/fvcproductions
[at-matiassingers]:https://github.com/matiassingers
[at-mojombo]:https://github.com/mojombo
[at-noffle]:https://github.com/noffle
[at-patorjk]:https://github.com/patorjk
[at-richardlitt]:https://github.com/richardlitt
[at-shaloo]:https://github.com/shaloo
[at-zalando]:https://github.com/zalando
<!-- in-line references to github -->
[git-profile]:https://github.com/nqtronix
[git-download]:https://github.com/nqtronix/git-template/archive/master.zip
[git-issues]:https://github.com/nqtronix/git-template/issues
[git-readme]:README.md
[git-license]:LICENSE.md
[git-contribute]:CONTRIBUTING.md
[git-badges]:badges.md
[git-repo-unittrace]:https://github.com/nqtronix/unittrace
[git-repo-fifofast]:https://github.com/nqtronix/fifofast
[git-repo-ahk-utf8-anywhere]:https://github.com/nqtronix/ahk-utf8-anywhere
<!-- in-line references by tag -->
[prog-markdownify]:https://github.com/amitmerchant1990/electron-markdownify
[prog-markdown-editor]:https://jbt.github.io/markdown-editor/
[prog-ascii-art]: http://patorjk.com/software/taag
[readme-matiassingers]:https://github.com/matiassingers/awesome-readme
[readme-fvcproductions]:https://gist.github.com/fvcproductions/1bfc2d4aecb01a834b46
[readme-fcpb]:https://github.com/cfpb/open-source-project-template
[readme-noffle]:https://github.com/noffle/art-of-readme
[readme-richardlitt]:https://github.com/richardlitt/standard-readme
[readme-zalando]:https://github.com/zalando/zalando-howto-open-source/blob/master/READMEtemplate.md
[readme-shaloo]:https://github.com/shaloo/structuredreadme
[markdown-cheatsheet]:https://github.com/adam-p/markdown-here/wiki/Markdown-Cheatsheet
[markdown-git]:https://help.github.com/articles/basic-writing-and-formatting-syntax
[article-rdd]:http://tom.preston-werner.com/2010/08/23/readme-driven-development.html
[article-open-source-everything]:http://tom.preston-werner.com/2011/11/22/open-source-everything.html
[article-read-on-the-web]:https://www.nngroup.com/articles/how-users-read-on-the-web
[article-few-seconds]:https://www.hallme.com/blog/do-you-have-a-7-second-website
[study-badges]:https://cmustrudel.github.io/projects/badges/
[study-badges-paper]:https://cmustrudel.github.io/papers/icse18badges.pdf
[license-mit]:https://opensource.org/licenses/MIT
[license-mit-vs-cc0]:https://opensource.stackexchange.com/questions/1371/how-can-i-place-software-in-the-public-domain/1381#1381
[license-cc0]:https://creativecommons.org/publicdomain/zero/1.0/
[license-cc0-fallback]:https://wiki.creativecommons.org/wiki/CC0_FAQ#How_does_it_work.3F
[video-people-dont-read]:https://youtu.be/sQP_hUNCrcE?t=68
[video-people-dont-read-scan]:https://youtu.be/sQP_hUNCrcE?t=90
[video-fshape]:https://www.youtube.com/watch?v=XU1-Rz2Q7-E
[video-start-with-why]:https://www.youtube.com/watch?v=u4ZoJKF_VuA
| 51.212724 | 455 | 0.742585 | eng_Latn | 0.989901 |
b96ea89121382a8a2d97394ba58bdd1240166744 | 1,798 | md | Markdown | README.md | Thomas-George-T/HackerRank-Python-Challenges-Solutions | fd04cb95e0ed78bc91cba2b628596f4e1c305ee2 | [
"MIT"
] | null | null | null | README.md | Thomas-George-T/HackerRank-Python-Challenges-Solutions | fd04cb95e0ed78bc91cba2b628596f4e1c305ee2 | [
"MIT"
] | null | null | null | README.md | Thomas-George-T/HackerRank-Python-Challenges-Solutions | fd04cb95e0ed78bc91cba2b628596f4e1c305ee2 | [
"MIT"
] | null | null | null | 
<p align="center">
<br>
<a href="https://www.hackerrank.com/Thomas_George_T">
<img height=100 src="https://hrcdn.net/community-frontend/assets/brand/logo-new-white-green-a5cb16e0ae.svg">
</a>
<br>
<br>
</p>
## Description
The solutions of all my HackerRank Python challenges for all the subdomains in python3
## Subdomains
### Introduction
| Number | Challenges | Solutions |
|:------:|------------|:---------:|
| 1 | [Say "Hello, World!" With Python](https://www.hackerrank.com/challenges/py-hello-world/problem) | [.py](https://github.com/Thomas-George-T/HackerRank-Python-Challenges-Solutions/blob/main/Introduction/Say%20'Hello,%20World!'%20With%20Python.py) |
| 2 | [Python If-Else](https://www.hackerrank.com/challenges/py-if-else/problem) | [.py]() |
| 3 | [Arithmetic Operators](https://www.hackerrank.com/challenges/python-arithmetic-operators/problem) | [.py]() |
| 4 | [Python: Division](https://www.hackerrank.com/challenges/python-division/problem) | [.py]() |
| 5 | [Loops](https://www.hackerrank.com/challenges/python-loops/problem) | [.py]() |
| 6 | [Write a function](https://www.hackerrank.com/challenges/write-a-function/problem) | [.py]() |
| 7 | [Print Function](https://www.hackerrank.com/challenges/python-print/problem) | [.py]() | | 59.933333 | 252 | 0.719132 | yue_Hant | 0.352184 |
b96f5a309155f306d9d2193880f3c967388c1b4f | 15,374 | md | Markdown | articles/backup/backup-mabs-sql-azure-stack.md | mtaheij/azure-docs.nl-nl | 6447611648064a057aae926a62fe8b6d854e3ea6 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/backup/backup-mabs-sql-azure-stack.md | mtaheij/azure-docs.nl-nl | 6447611648064a057aae926a62fe8b6d854e3ea6 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/backup/backup-mabs-sql-azure-stack.md | mtaheij/azure-docs.nl-nl | 6447611648064a057aae926a62fe8b6d854e3ea6 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Back-ups maken van SQL Server werk belastingen op Azure Stack
description: In dit artikel vindt u informatie over het configureren van Microsoft Azure Backup Server (MABS) om SQL Server-data bases op Azure Stack te beveiligen.
ms.topic: conceptual
ms.date: 06/08/2018
ms.openlocfilehash: 80de7913b010fca69c3703e423109f2ede653590
ms.sourcegitcommit: 32c521a2ef396d121e71ba682e098092ac673b30
ms.translationtype: MT
ms.contentlocale: nl-NL
ms.lasthandoff: 09/25/2020
ms.locfileid: "91332811"
---
# <a name="back-up-sql-server-on-azure-stack"></a>Back-up maken van SQL Server op Azure Stack
Gebruik dit artikel om Microsoft Azure Backup Server (MABS) te configureren om SQL Server-data bases op Azure Stack te beveiligen.
Het beheer van SQL Server database back-up naar Azure en het herstel van Azure bestaat uit drie stappen:
1. Een back-upbeleid maken om SQL Server-data bases te beveiligen
2. Back-ups op aanvraag maken
3. De data base herstellen vanaf schijven en Azure
## <a name="prerequisites-and-limitations"></a>Vereisten en beperkingen
* Als u een database met bestanden op een externe bestandsshare hebt, mislukt de beveiliging met fout-id 104. MABS biedt geen ondersteuning voor de beveiliging van SQL Server gegevens op een externe bestands share.
* MABS kan geen data bases beveiligen die zijn opgeslagen op externe SMB-shares.
* Zorg ervoor dat de replica's van de [beschikbaarheids groep zijn geconfigureerd als alleen-lezen](/sql/database-engine/availability-groups/windows/configure-read-only-access-on-an-availability-replica-sql-server).
* U moet de systeem account **NTAuthority\System** expliciet toevoegen aan de groep Sysadmin op SQL Server.
* Wanneer u een herstel bewerking op een andere locatie uitvoert voor een gedeeltelijk Inge sloten data base, moet u ervoor zorgen dat de functie [Inge sloten data bases](/sql/relational-databases/databases/migrate-to-a-partially-contained-database#enable) is ingeschakeld voor het SQL-doel exemplaar.
* Wanneer u een herstel bewerking op een andere locatie uitvoert voor een bestands stroom database, moet u ervoor zorgen dat de functie [Bestands stroom database](/sql/relational-databases/blob/enable-and-configure-filestream) is ingeschakeld voor het SQL-doel exemplaar.
* Beveiliging voor SQL Server AlwaysOn:
* MABS detecteert beschikbaarheids groepen bij het uitvoeren van een query bij het maken van de beveiligings groep.
* MABS detecteert een failover en gaat verder met de beveiliging van de data base.
* MABS ondersteunt configuraties met meerdere site clusters voor een exemplaar van SQL Server.
* Wanneer u data bases beveiligt die de functie AlwaysOn gebruiken, heeft MABS de volgende beperkingen:
* MABS zal het back-upbeleid voor beschikbaarheids groepen dat is ingesteld in SQL Server, op basis van de voor keuren voor back-ups, als volgt door:
* Voorkeur voor secundaire: back-ups moeten op een secundaire replica plaatsvinden, behalve wanneer de primaire replica de enige replica online is. Als er meerdere secundaire replica's beschikbaar zijn, wordt het knoop punt met de hoogste back-upprioriteit geselecteerd voor back-up. Als alleen de primaire replica beschikbaar is, moet de back-up op de primaire replica worden uitgevoerd.
* Alleen secundaire: back-up mag niet op de primaire replica worden uitgevoerd. Als de primaire replica de enige online replica is, mag de back-up niet plaatsvinden.
* Primaire: back-ups moeten altijd op de primaire replica plaatsvinden.
* Iedere replica: back-ups kunnen op alle beschikbare replica's in de beschikbaarheidsgroep plaatsvinden. Het knooppunt waarvan een back-up moet worden gemaakt, zal gebaseerd zijn op de back-upprioriteiten voor elk van de knooppunten.
* Houd rekening met het volgende:
* U kunt back-ups maken van elke Lees bare replica, dat wil zeggen primair, synchroon secundair, asynchroon secundair.
* Als een replica wordt uitgesloten van de back-up, bijvoorbeeld als **replica uitsluiten** is ingeschakeld of als niet leesbaar is gemarkeerd, wordt die replica niet geselecteerd voor back-up onder een van de opties.
* Als er meerdere replica's beschikbaar en leesbaar zijn, wordt het knoop punt met de hoogste back-upprioriteit geselecteerd voor back-up.
* Als de back-up mislukt op het geselecteerde knoop punt, mislukt de back-upbewerking.
* Herstel naar de oorspronkelijke locatie wordt niet ondersteund.
* Back-upproblemen SQL Server 2014 of hoger:
* SQL Server 2014 heeft een nieuwe functie toegevoegd voor het maken van een [Data Base voor on-premises SQL Server in Windows Azure Blob-opslag](/sql/relational-databases/databases/sql-server-data-files-in-microsoft-azure). MABS kan niet worden gebruikt om deze configuratie te beveiligen.
* Er zijn enkele bekende problemen met de voor keur voor secundaire back-upvoorkeur voor de SQL AlwaysOn-optie. MABS maakt altijd een back-up van secundair. Als er geen secundair kan worden gevonden, mislukt de back-up.
## <a name="before-you-start"></a>Voordat u begint
[Azure backup server installeren en voorbereiden](backup-mabs-install-azure-stack.md).
## <a name="create-a-backup-policy-to-protect-sql-server-databases-to-azure"></a>Een back-upbeleid maken om SQL Server data bases te beveiligen in azure
1. Selecteer de werk ruimte **beveiliging** op de Azure backup server gebruikers interface.
2. Op het lint met hulp middelen selecteert u **Nieuw** om een nieuwe beveiligings groep te maken.
Azure Backup Server start de wizard beveiligings groep, die u helpt bij het maken van een **beveiligings groep**. Selecteer **Next**.
3. Selecteer in het scherm **type beveiligings groep selecteren** de optie **servers**.
4. In het scherm **groeps leden selecteren** worden de verschillende gegevens bronnen weer gegeven in de lijst met beschik bare leden. Selecteer **+** om een map uit te vouwen en de submappen weer te geven. Schakel het selectie vakje in om een item te selecteren.
Alle geselecteerde items worden weer gegeven in de lijst geselecteerde leden. Selecteer **volgende**na het selecteren van de servers of data bases die u wilt beveiligen.
5. Geef in het scherm **methode voor gegevens beveiliging selecteren** een naam op voor de beveiligings groep en schakel het selectie vakje **Ik wil online beveiliging** in.
6. In het scherm doelen voor de **korte termijn opgeven** , neemt u de benodigde invoer op voor het maken van back-uppunten op schijf en selecteert u **volgende**.
In het voor beeld is de **Bewaar** termijn **5 dagen**, de **synchronisatie frequentie** is elke **15 minuten**, wat de back-upfrequentie is. **Snelle volledige back-up** is ingesteld op **8:00 P. M**.
> [!NOTE]
> In het voor beeld dat wordt weer gegeven, om 8:00 uur elke dag een back-uppunt wordt gemaakt door de gewijzigde gegevens van de vorige dag van het 8:00 PM-back-uppunt te verplaatsen. Dit proces heet **snelle volledige back-up**. Transactie logboeken worden elke 15 minuten gesynchroniseerd. Als u de Data Base op 9:00 uur moet herstellen, wordt het punt gemaakt op basis van de logboeken van het laatste snelle volledige back-uppunt (8 P.M. in dit geval).
>
>
7. Controleer op het scherm **schijf toewijzing controleren** de totale beschik bare opslag ruimte en de mogelijke schijf ruimte. Selecteer **Next**.
8. Kies in de methode voor het maken van een **replica kiezen**hoe u uw eerste herstel punt maakt. U kunt de eerste back-up hand matig overdragen (uit het netwerk) om te voor komen dat er band breedte overbelast of via het netwerk. Als u wilt wachten op het overdragen van de eerste back-up, kunt u de tijd voor de eerste overdracht opgeven. Selecteer **Next**.
Voor de eerste back-upkopie moet de volledige gegevens bron (SQL Server-Data Base) van de productie server (SQL Server computer) naar Azure Backup Server worden overgedragen. Deze gegevens zijn mogelijk erg groot en het overdragen van de gegevens via het netwerk kan de band breedte overschrijden. Daarom kunt u ervoor kiezen om de eerste back-up te verplaatsen: **hand matig** (met behulp van Verwissel bare media) om te voor komen dat er band breedte overbelast wordt of **automatisch via het netwerk** (op een bepaald moment).
Zodra de eerste back-up is voltooid, zijn de rest van de back-ups incrementele back-ups op de eerste back-upkopie. Incrementele back-ups zijn vaak klein en kunnen eenvoudig via het netwerk worden overgedragen.
9. Kies wanneer u wilt dat de consistentie controle wordt uitgevoerd en selecteer **volgende**.
Azure Backup Server voert een consistentie controle uit op de integriteit van het back-uppunt. Azure Backup Server berekent de controlesom van het back-upbestand op de productie server (SQL Server computer in dit scenario) en de gegevens van de back-up voor dat bestand. Als er een conflict optreedt, wordt ervan uitgegaan dat het back-upbestand op Azure Backup Server is beschadigd. Azure Backup Server verholpen de back-upgegevens door de blokken te verzenden die overeenkomen met de controlesom komen niet overeen. Omdat consistentie controles prestaties vergen, kunt u de consistentie controle plannen of automatisch uitvoeren.
10. Als u de online beveiliging van de gegevens bronnen wilt opgeven, selecteert u de data bases die moeten worden beveiligd met Azure en selecteert u **volgende**.
11. Kies een back-upschema en bewaar beleid dat aan het organisatie beleid voldoet.
In dit voor beeld worden back-ups eenmaal per dag om 12:00 uur en 8 uur (onderste deel van het scherm) gemaakt.
> [!NOTE]
> Het is een goed idee om een aantal herstel punten voor de korte termijn te hebben op de schijf, voor snel herstel. Deze herstel punten worden gebruikt voor operationeel herstel. Azure fungeert als een goede externe locatie met hogere Sla's en gegarandeerde Beschik baarheid.
>
>
**Aanbevolen procedure**: als u back-ups naar Azure plant om te starten nadat de back-ups van de lokale schijf zijn voltooid, worden de meest recente schijf back-ups altijd naar Azure gekopieerd.
12. Kies het schema voor het Bewaar beleid. De details over de manier waarop het Bewaar beleid werkt, vindt u in [gebruik Azure backup om uw tape-infrastructuur artikel te vervangen](backup-azure-backup-cloud-as-tape.md).
In dit voorbeeld geldt het volgende:
* Back-ups worden eenmaal per dag om 12:00 uur en 8 uur (onderste deel van het scherm) gemaakt en blijven 180 dagen bewaard.
* De back-up op zaterdag om 12:00 uur wordt 104 weken bewaard
* De back-up op de laatste zaterdag om 12:00 uur wordt gedurende 60 maanden bewaard
* De back-up op de laatste zaterdag van maart om 12:00 uur wordt gedurende tien jaar bewaard
13. Selecteer **volgende** en selecteer de juiste optie voor het overdragen van de eerste back-up naar Azure. U kunt **automatisch selecteren via het netwerk**
14. Wanneer u de details van het beleid in het scherm **samen vatting** hebt bekeken, selecteert u **groep maken** om de werk stroom te volt ooien. U kunt **sluiten** en de voortgang van de taak in de werk ruimte bewaking bewaken selecteren.
## <a name="on-demand-backup-of-a-sql-server-database"></a>Back-ups op aanvraag van een SQL Server Data Base
Terwijl de vorige stappen een back-upbeleid hebben gemaakt, wordt er alleen een ' herstel punt ' gemaakt wanneer de eerste back-up wordt uitgevoerd. In plaats van te wachten tot de scheduler wordt gestart, activeren de volgende stappen om hand matig een herstel punt te maken.
1. Wacht totdat de status van de beveiligings groep op **OK** staat voor de Data Base voordat u het herstel punt maakt.
2. Klik met de rechter muisknop op de data base en selecteer **herstel punt maken**.
3. Kies **online beveiliging** in de vervolg keuzelijst en selecteer **OK** om te beginnen met het maken van een herstel punt in Azure.
4. Bekijk de voortgang van de taak in de werk ruimte **bewaking** .
## <a name="recover-a-sql-server-database-from-azure"></a>Een SQL Server-Data Base herstellen vanuit Azure
De volgende stappen zijn vereist om een beveiligde entiteit (SQL Server-Data Base) te herstellen vanuit Azure.
1. Open de Azure Backup Server-beheer console. Ga naar de **herstel** werkruimte waar u de beveiligde servers kunt zien. Blader door de vereiste data base (in dit geval Report Server $ MSDPM2012). Selecteer een **herstel** tijd die is opgegeven als een **online** punt.
2. Klik met de rechter muisknop op de naam van de data base en selecteer **herstellen**.
3. MABS toont de details van het herstel punt. Selecteer **Next**. Als u de Data Base wilt overschrijven, selecteert u het herstel type **herstellen naar het oorspronkelijke exemplaar van SQL Server**. Selecteer **Next**.
In dit voor beeld herstelt MABS de Data Base naar een andere SQL Server-instantie of naar een zelfstandige netwerkmap.
4. In het scherm **herstel opties opgeven** kunt u de herstel opties zoals netwerk bandbreedte gebruiken selecteren om de band breedte te beperken die wordt gebruikt voor herstel. Selecteer **Next**.
5. In het scherm **samen vatting** ziet u alle beschik bare herstel configuraties tot nu toe. Selecteer **herstellen**.
De herstel status toont de data base die wordt hersteld. U kunt **sluiten** selecteren om de wizard te sluiten en de voortgang in de werk ruimte **bewaking** weer te geven.
Wanneer het herstel is voltooid, is de herstelde data base toepassings consistent.
## <a name="next-steps"></a>Volgende stappen
Raadpleeg de [back-upbestanden en het toepassings](backup-mabs-files-applications-azure-stack.md) artikel.
Zie het artikel [back-upSharePoint on Azure stack](backup-mabs-sharepoint-azure-stack.md) .
| 82.655914 | 635 | 0.778262 | nld_Latn | 0.999545 |
533d2663d3ef7bc978bcf99fc22d03e4dc3dee40 | 806 | md | Markdown | src/posts/2022-03-15-diary.md | makenowjust/diary | 83a09435b6dec23eadf876c016ec65be55117215 | [
"MIT"
] | null | null | null | src/posts/2022-03-15-diary.md | makenowjust/diary | 83a09435b6dec23eadf876c016ec65be55117215 | [
"MIT"
] | null | null | null | src/posts/2022-03-15-diary.md | makenowjust/diary | 83a09435b6dec23eadf876c016ec65be55117215 | [
"MIT"
] | null | null | null | ---
title: 仮面ライダーエグゼイドを観た
---
# やったこと
## 正規表現
なんとなく Go 言語の正規表現実装みたいなの (Thompson VM) を DFA 的に実行できるようにするのを実装してみた。
適当に作ったけど正しく動いていると思う。
少なくとも `Nfa` の `exec` の動作と `toDfa` してから `exec` したときの動作が厳密に一致するのは実装から明らかだと思われる。
<https://scastie.scala-lang.org/7Cj8iOc7SHu2SKLUUJ8BYg>
そしてちょっと調子に乗って、SFA 的なアプローチで並列化するようにしてみた。
一応実装はできたのだけど、別にあまり早くない。
というか、そもそもの実装があまり早くないのが問題な気がする。
アロケーションを意識するのが Scala だとしんどい。Rust にするべきか‥‥。
コードは気が向いたら公開するかもしれないし、しないかもしれない。
今のままだとしない気がする‥‥。
## エグゼイド
Prime Video で公開されていたので仮面ライダーエグゼイドを最後まで観た。
エグゼイドは宝条永夢ゥ！ のイメージしかなかったけど、観てみると普通に面白かったな、という感じ。
30話辺りまでのストーリー (ポッピーが戻ってくるあたりまで) はほんとよくできてなぁ、と思う。
逆にそこから先の展開は行き当たりばったりというか、敵がつよすぎれば味方もつよすぎて、何ができて何ができないのかよく分かんなくなってしまった気がする。
でも44話のポッピーが消滅するところで、最後に檀黎斗のところに行ったのは良かった。
自分の創った存在に報われて良かったというか、最後の戦いに檀黎斗がすっと出てこれたのはあのシーンがあったからだろうと思える。
映画は気が向いたら見よう。
| 24.424242 | 77 | 0.843672 | jpn_Jpan | 0.992636 |
533d4c396f0b527be1ad32ca5edc8732e3d9443c | 5,440 | md | Markdown | courgette/description.md | zealoussnow/chromium | fd8a8914ca0183f0add65ae55f04e287543c7d4a | [
"BSD-3-Clause-No-Nuclear-License-2014",
"BSD-3-Clause"
] | 14,668 | 2015-01-01T01:57:10.000Z | 2022-03-31T23:33:32.000Z | courgette/description.md | zealoussnow/chromium | fd8a8914ca0183f0add65ae55f04e287543c7d4a | [
"BSD-3-Clause-No-Nuclear-License-2014",
"BSD-3-Clause"
] | 113 | 2015-05-04T09:58:14.000Z | 2022-01-31T19:35:03.000Z | courgette/description.md | zealoussnow/chromium | fd8a8914ca0183f0add65ae55f04e287543c7d4a | [
"BSD-3-Clause-No-Nuclear-License-2014",
"BSD-3-Clause"
] | 5,941 | 2015-01-02T11:32:21.000Z | 2022-03-31T16:35:46.000Z | Courgette Internals
===================
Patch Generation
----------------
- courgette\_tool.cc:GenerateEnsemblePatch kicks off the patch
generation by calling ensemble\_create.cc:GenerateEnsemblePatch
- The files are read in by in courgette:SourceStream objects
- ensemble\_create.cc:GenerateEnsemblePatch uses FindGenerators, which
uses MakeGenerator to create
patch\_generator\_x86\_32.h:PatchGeneratorX86\_32 classes.
- PatchGeneratorX86\_32's Transform method transforms the input file
using Courgette's core techniques that make the bsdiff delta
smaller. The steps it takes are the following:
- _disassemble_ the old and new binaries into AssemblyProgram
objects,
- _adjust_ the new AssemblyProgram object, and
- _encode_ the AssemblyProgram object back into raw bytes.
### Disassemble
- The input is a pointer to a buffer containing the raw bytes of the
input file.
- Disassembly converts certain machine instructions that reference
addresses to Courgette instructions. It is not actually
disassembly, but this is the term the code-base uses. Specifically,
it detects instructions that use absolute addresses given by the
binary file's relocation table, and relative addresses used in
relative branches.
- Done by disassemble:ParseDetectedExecutable, which selects the
appropriate Disassembler subclass by looking at the binary file's
headers.
- disassembler\_win32\_x86.h defines the PE/COFF x86 disassembler
- disassembler\_elf\_32\_x86.h defines the ELF 32-bit x86 disassembler
- The Disassembler replaces the relocation table with a Courgette
instruction that can regenerate the relocation table.
- The Disassembler builds a list of addresses referenced by the
machine code, numbering each one.
- The Disassembler replaces and address used in machine instructions
with its index number.
- The output is an assembly\_program.h:AssemblyProgram class, which
contains a list of instructions, machine or Courgette, and a mapping
of indices to actual addresses.
### Adjust
- This step takes the AssemblyProgram for the old file and reassigns
the indices that map to actual addresses. It is performed by
adjustment_method.cc:Adjust().
- The goal is the match the indices from the old program to the new
program as closely as possible.
- When matched correctly, machine instructions that jump to the
function in both the new and old binary will look the same to
bsdiff, even the function is located in a different part of the
binary.
### Encode
- This step takes an AssemblyProgram object and encodes both the
instructions and the mapping of indices to addresses as byte
vectors. This format can be written to a file directly, and is also
more appropriate for bsdiffing. It is done by
AssemblyProgram.Encode().
- encoded_program.h:EncodedProgram defines the binary format and a
WriteTo method that writes to a file.
### bsdiff
- simple_delta.c:GenerateSimpleDelta
Patch Application
-----------------
- courgette\_tool.cc:ApplyEnsemblePatch kicks off the patch generation
by calling ensemble\_apply.cc:ApplyEnsemblePatch
- ensemble\_create.cc:ApplyEnsemblePatch, reads and verifies the
patch's header, then calls the overloaded version of
ensemble\_create.cc:ApplyEnsemblePatch.
- The patch is read into an ensemble_apply.cc:EnsemblePatchApplication
object, which generates a set of patcher_x86_32.h:PatcherX86_32
objects for the sections in the patch.
- The original file is disassembled and encoded via a call
EnsemblePatchApplication.TransformUp, which in turn call
patcher_x86_32.h:PatcherX86_32.Transform.
- The transformed file is then bspatched via
EnsemblePatchApplication.SubpatchTransformedElements, which calls
EnsemblePatchApplication.SubpatchStreamSets, which calls
simple_delta.cc:ApplySimpleDelta, Courgette's built-in
implementation of bspatch.
- Finally, EnsemblePatchApplication.TransformDown assembles, i.e.,
reverses the encoding and disassembly, on the patched binary data.
This is done by calling PatcherX86_32.Reform, which in turn calls
the global function encoded_program.cc:Assemble, which calls
EncodedProgram.AssembleTo.
Glossary
--------
**Adjust**: Reassign address indices in the new program to match more
closely those from the old.
**Assembly program**: The output of _disassembly_. Contains a list of
_Courgette instructions_ and an index of branch target addresses.
**Assemble**: Convert an _assembly program_ back into an object file
by evaluating the _Courgette instructions_ and leaving the machine
instructions in place.
**Courgette instruction**: Replaces machine instructions in the
program. Courgette instructions replace branches with an index to
the target addresses and replace part of the relocation table.
**Disassembler**: Takes a binary file and produces an _assembly
program_.
**Encode**: Convert an _assembly program_ into an _encoded program_ by
serializing its data structures into byte vectors more appropriate
for storage in a file.
**Encoded Program**: The output of encoding.
**Ensemble**: A Courgette-style patch containing sections for the list
of branch addresses, the encoded program. It supports patching
multiple object files at once.
**Opcode**: The number corresponding to either a machine or _Courgette
instruction_.
| 34.871795 | 72 | 0.784559 | eng_Latn | 0.996823 |
533d81063e393518cafea71de2dedd5e853aae0e | 4,831 | md | Markdown | README.md | mk12/spa | f38d1e52ff7d721f58e207b11e802414d32080cd | [
"MIT"
] | 2 | 2016-04-08T10:00:16.000Z | 2017-12-22T03:11:51.000Z | README.md | mk12/spa | f38d1e52ff7d721f58e207b11e802414d32080cd | [
"MIT"
] | 2 | 2015-09-05T19:13:34.000Z | 2015-09-05T19:17:42.000Z | README.md | mk12/spa | f38d1e52ff7d721f58e207b11e802414d32080cd | [
"MIT"
] | null | null | null | # SPA
SPA is a Simple Proof Assistant. It can help you prove basic theorems about sets and numbers.
## Usage
Build the project with `./build.sh` and then run `./dist/spa` to enter the interactive console. If all goes well, it should greet you with a friendly banner:
```
_____ _____ _____
| ___| | _ | | _ | | Simple Proof Assisant
| |___ | |_| | | |_| | | (c) 2015 Mitchell Kember
|___ | | ___| | _ | | Version 0.1
___| | | | | | | | |
|_____| |_| |_| |_| | Type "help" to get started
```
Enter `help` to see the commands that are available.
## Proving a theorem
You start by entering your theorem. Here's a convoluted example:
```
prove (forall x in ZZ (iff (and (= x (+ 1 1)) (sub {x} ZZ)) (exists a (= a a))))
```
Theorems are written in prefix notation, similar to Lisp. At any time, you can enter `stat` to see the current status of the proof. In this case, we want to decompose the theorem using `dec`.
After decomposing a few times and then entering `tree`, you'll see the power of SPA: it breaks down the theorem into managable pieces (goals), keeps track of your givens, and lets you navigate the tree until you've proved the original theorem. If you enter `ded`, SPA will automatically derive givens from your current knowledge. When you get to a simple goal such as `(= 1 1)`, you can enter `triv` to let SPA know that it's trivial to prove. You can also enter `just` and provide a sentence of justification.
After proving that theorem, the tree looks like this:
```
_______________A
/
_______B
/
___C___
/ \
_D _E
/ /
F G
/ \
H I
[A] (forall x (=> (in x ZZ) (iff (and (= x (+ 1 1)) (sub {x} ZZ)) (exists a (= a a)))))
[B] (=> (in x ZZ) (iff (and (= x (+ 1 1)) (sub {x} ZZ)) (exists a (= a a))))
[C] (iff (and (= x (+ 1 1)) (sub {x} ZZ)) (exists a (= a a)))
[D] (=> (and (= x (+ 1 1)) (sub {x} ZZ)) (exists a (= a a)))
[E] (=> (exists a (= a a)) (and (= x (+ 1 1)) (sub {x} ZZ)))
[F] (exists a (= a a))
[G] (and (= x (+ 1 1)) (sub {x} ZZ))
[H] (= x (+ 1 1))
[I] (sub {x} ZZ)
```
## Objects
There are three types of mathematical objects in SPA:
- Numbers
- Concrete numbers: 1, -1, 99, etc.
- Compound numbers: sum, difference, or product.
- Sets
- Concrete sets: {0}, {0, 42}, etc.
- Compound sets: union, intersection, or difference.
- Special sets: empty set, naturals, integers, set of sets.
- Symbols
- A single character that refers to another object: _x_, _y_, etc.
## Sentences
There are three types of mathematical sentences in SPA:
- Logical (all binary except `not`)
- Boolean algebra: `and`, `or`, `not`, `=>` (implies), or `iff` (if and only if).
- Relation (all binary)
- `=`, `!=`, `<`, `>`, `<=`, `>=`, `s=` (set equality), `sub` (proper subset), `sube` (subset), `in` (belongs to), `div` (divides).
- Quantified
- Existential: `(exists a (> a 5))`.
- Universal: `(forall a (= a a))`.
There is a short form for quantified sentences:
- `(forall x in NN (!= x -1))` is equivalent to `(forall x (=> (in x NN) (!= x -1)))`.
- `(exists x in ZZ (= x -1))` is equivalent to `(exists x (and (in x ZZ) (= x -1)))`.
## Usefulness
In the future SPA may become intelligent enought to prove basic theorems on its own. For now, it just manages mechanical steps of theorem-proving: the current goal, the tree of goals it fits into, the list of givens, the rules of decomposition, and the rules of deduction.
This is useful for some theorems you might see in Algebra class. In the real world, though, theorems are hard to prove not because they are long or have deeply nested trees — in fact, many difficult theorems consist of a single quantified implication — but because they involve a very difficult step. For example, SPA will never be able to help you prove the existence of an object.
All that being said, I enjoyed writing SPA and I hope others have fun playing around with it.
## Contributions
Contributions are welcome! Take a look at the current issues to see what needs to be worked on. Please create a pull request if you have anything to contribute.
## License
© 2015 Mitchell Kember
SPA is available under the MIT License; see [LICENSE](LICENSE.md) for details.
| 45.575472 | 510 | 0.56717 | eng_Latn | 0.997986 |
533db735e49fbcaf6a28d4d32e642b792e02a2aa | 2,500 | md | Markdown | docs/extensibility/vsct-xml-schema-conditional-attributes.md | HiDeoo/visualstudio-docs.fr-fr | db4174a3cd6d03edc8bbf5744c3f917e4b582cb3 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/extensibility/vsct-xml-schema-conditional-attributes.md | HiDeoo/visualstudio-docs.fr-fr | db4174a3cd6d03edc8bbf5744c3f917e4b582cb3 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/extensibility/vsct-xml-schema-conditional-attributes.md | HiDeoo/visualstudio-docs.fr-fr | db4174a3cd6d03edc8bbf5744c3f917e4b582cb3 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Attributs conditionnels de schéma XML VSCT | Microsoft Docs
ms.date: 11/04/2016
ms.topic: conceptual
helpviewer_keywords:
- VSCT XML schema elements, conditional attributes
- conditional attributes (VSCT XML schema)
ms.assetid: 754d4f32-319b-44c9-915f-f7c60e53222e
author: acangialosi
ms.author: anthc
manager: jillfra
ms.workload:
- vssdk
ms.openlocfilehash: f2b1fb3ee1b2cd396f25ec5591a585f8d87648d0
ms.sourcegitcommit: 6cfffa72af599a9d667249caaaa411bb28ea69fd
ms.translationtype: MT
ms.contentlocale: fr-FR
ms.lasthandoff: 09/02/2020
ms.locfileid: "80697948"
---
# <a name="vsct-xml-schema-conditional-attributes"></a>Attributs conditionnels du schéma XML VSCT
Vous pouvez appliquer des attributs conditionnels à toutes les listes et éléments. Les opérateurs logiques et les expressions d’expansion de symboles prennent la valeur true ou false. Si la valeur est true, la liste ou l’élément associé est inclus dans la sortie obtenue.
Vous pouvez tester les expansions de jeton par rapport à d’autres constantes ou expansions de jeton. La fonction `Defined()` teste si un nom particulier a été défini, même s’il n’a pas de valeur.
Lorsqu’un attribut condition est appliqué à une liste, la condition est appliquée à chaque élément enfant de la liste. Si un élément enfant lui-même contient un attribut condition, sa condition est combinée avec l’expression parente par une opération AND.
Les valeurs 1, « 1 » et « true » sont évaluées comme vraies, et 0, « 0 » et « false » sont évalués comme faux.
## <a name="operators"></a>Opérateurs
Utilisez les opérateurs suivants pour évaluer des expressions conditionnelles.
|Opérateur|Définition|
|--------------|----------------|
|(,)|Regroupement|
|!|Opérateur NOT logique|
|\<, >, \<=, >=, ==, !=|Opérateurs relationnels et opérateurs d'égalité|
|et|Boolean|
|ou|Boolean|
## <a name="examples"></a>Exemples
```xml
<Menu Condition="Defined(DEBUG)" ...
</Menu>
<Menu Condition="%(SKU_MODE) = 'Demo'" ...
</Menu>
<Menus Condition="Defined(DEBUG)">
<Menu ...
</Menu>
</Menus>
<Menus Condition="Defined(DEMO_SKU)">
<Menus Condition="!Defined(DEBUG)">
<Menu ...
</Menu>
</Menus>
<Menu ...
</Menu>
</Menus>
<Menus Condition="(Defined(DEMO_SKU) or Defined(SAMPLE_SKU))
and !Defined(DEBUG)">
<Menu ...
</Menu>
</Menus>
```
## <a name="see-also"></a>Voir aussi
- [Table de commandes Visual Studio (. Fichiers vsct)](../extensibility/internals/visual-studio-command-table-dot-vsct-files.md)
| 33.783784 | 271 | 0.7252 | fra_Latn | 0.861738 |
533dd5cfde99cfb08db26dae494605ea7d8d0337 | 906 | md | Markdown | README.md | mqt2999/Team-Profile-Generator | 1d29dd33bba9a657b096c689be7d9b71b48f625b | [
"MIT"
] | null | null | null | README.md | mqt2999/Team-Profile-Generator | 1d29dd33bba9a657b096c689be7d9b71b48f625b | [
"MIT"
] | null | null | null | README.md | mqt2999/Team-Profile-Generator | 1d29dd33bba9a657b096c689be7d9b71b48f625b | [
"MIT"
] | null | null | null | # Team-Profile-Generator [](https://shields.io/)
## Description
The motivation for this project is to create web page that displays a roster cards for an employer who enters their answers using a terminal. Also to test my knowladge in node and test driven programing
## Table of Contents
- [Installation](#installation)
- [Usage](#usage)
- [Credits](#credits)
- [License](#license)
## Installation
* node and a terminal are needed
## Usage
* 1. open the terminal in the right directory
* 2. Type "node index.js" press enter
* 3. answer the prompts and then open "index.html" and view results
## Credit
* none
## License
* MIT
* <a href="https://opensource.org/licenses/MIT"> MIT License </a>
## Test
* 1. open the terminal and type "npm run test" press enter.
## Questions
* Github: Mqt2999
* Email: [email protected] | 29.225806 | 202 | 0.715232 | eng_Latn | 0.912943 |
533e81829318cc5226fabf3427dc7e69fe2e32ab | 2,674 | md | Markdown | README.md | minterciso/cuda_snippets | 77dd3a24df8132b1282e7496e220ceae06cf5895 | [
"MIT"
] | null | null | null | README.md | minterciso/cuda_snippets | 77dd3a24df8132b1282e7496e220ceae06cf5895 | [
"MIT"
] | null | null | null | README.md | minterciso/cuda_snippets | 77dd3a24df8132b1282e7496e220ceae06cf5895 | [
"MIT"
] | null | null | null | # Introduction
In this repository you'll find some snippets of common CUDA operations. I'll always try to make them as pure C/C++ as possible (ie: trying to avoid using STL or 3rd party libraries).
## curand_dev
Shows how to create a lot of numbers on the device, then add them on some pre-specified "bins". This is usefull to check the probability of hitting some number.
I focused on 2 main distributions: Uniform and Normal
### Compilation
Use nvcc and just add the -lcurand library:
$ nvcc -o curand_dev curand_dev.cu -lcurand
### Usage
Usage: ./curand_dev options
-h --help This help message
-d type --distribution type Distribution type (valid values: 'uniform', 'normal')
-s value --scale value Scale value for the Normal distribution.
-S value --shift value Shift value for the Normal distribution.
-m value --min value Minimum value
-M value --max value Maximum value
-o file --output file Output CSV file (required)
-g --gnuplot Write a gnuplot file for showing the output data
#### Distribution type
There are 2 main distribution presented here: uniform and normal.
The Uniform distribution simply generates a number using a uniform distribution, and *caps* the number between \[min,max\[. The amount of capped numbers is the probability of each number to show using this distribution. The graph of the probabilities should be pretty standard.
The Normal distribution on the other hand returns a number between \[0,1.0\[, and we then scale it to an int between \[min,max\[. The normal distribution uses mean 0.0 and standar deviation of 1.0. It's also possible to adjus the *scale* (or spread) of the probabilities and the *shift* of the distribution via the parameters -s and -S. For instance:
./curand_dev -o output.csv -d normal -s 10 -S 50
Would give numbers between \[0,100\[ with a scale of 10 and shift of 50 would result in a graph that is centered on the middle and spreads values trough all bins. If for instace we change the -s value, the spread size would be much smaller. I recommend trying it.
There's also a thir hidden option that, if you pass anything else then "normal" or "uniform", it'll try to create both graphs, and output the result of both on the same file. This is VERY usefull for seeing the differences between the distributions.
As an example:
| 66.85 | 350 | 0.693717 | eng_Latn | 0.998111 |
533ee914e9e3dca6bb596248f331f50fe2f2f515 | 1,958 | md | Markdown | docs/extensibility/debugger/reference/idebugdefaultport2-getportnotify.md | klmnden/visualstudio-docs.tr-tr | 82aa1370dab4ae413f5f924dad3e392ecbad0d02 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-09-01T20:45:52.000Z | 2020-09-01T20:45:52.000Z | docs/extensibility/debugger/reference/idebugdefaultport2-getportnotify.md | klmnden/visualstudio-docs.tr-tr | 82aa1370dab4ae413f5f924dad3e392ecbad0d02 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/extensibility/debugger/reference/idebugdefaultport2-getportnotify.md | klmnden/visualstudio-docs.tr-tr | 82aa1370dab4ae413f5f924dad3e392ecbad0d02 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: IDebugDefaultPort2::GetPortNotify | Microsoft Docs
ms.date: 11/04/2016
ms.topic: reference
f1_keywords:
- IDebugDefaultPort2::GetPortNotify
helpviewer_keywords:
- IDebugDefaultPort2::GetPortNotify
ms.assetid: 3ae715ee-9886-4694-a52b-59bb3b27467a
author: madskristensen
ms.author: madsk
manager: jillfra
ms.workload:
- vssdk
dev_langs:
- CPP
- CSharp
ms.openlocfilehash: fd85f76ab0c882656ca79fe02296f30bdb83f523
ms.sourcegitcommit: 40d612240dc5bea418cd27fdacdf85ea177e2df3
ms.translationtype: MT
ms.contentlocale: tr-TR
ms.lasthandoff: 05/29/2019
ms.locfileid: "66351771"
---
# <a name="idebugdefaultport2getportnotify"></a>IDebugDefaultPort2::GetPortNotify
Bu yöntem alır bir [IDebugPortNotify2](../../../extensibility/debugger/reference/idebugportnotify2.md) Bu bağlantı noktası için arabirim.
## <a name="syntax"></a>Sözdizimi
```cpp
HRESULT GetPortNotify(
IDebugPortNotify2** ppPortNotify
);
```
```csharp
int GetPortNotify(
out IDebugPortNotify2 ppPortNotify
);
```
## <a name="parameters"></a>Parametreler
`ppPortNotify`\
[out] Bir [IDebugPortNotify2](../../../extensibility/debugger/reference/idebugportnotify2.md) nesne.
## <a name="return-value"></a>Dönüş Değeri
Başarılı olursa döndürür `S_OK`; Aksi takdirde bir hata kodu döndürür.
## <a name="remarks"></a>Açıklamalar
Normalde, `QueryInterface` yöntemi, uygulama nesnesi üzerinde çağrıldığında [IDebugPort2](../../../extensibility/debugger/reference/idebugport2.md) arabirimi almak için bir [IDebugPortNotify2](../../../extensibility/debugger/reference/idebugportnotify2.md) arabirimi. Ancak, istendiği arayüz farklı bir nesne üzerinde uygulanmadı koşullar vardır. Bu yöntem bu koşullarda gizler ve döndürür `IDebugPortNotify2` en uygun nesnesinden arabirimi.
## <a name="see-also"></a>Ayrıca bkz.
- [IDebugDefaultPort2](../../../extensibility/debugger/reference/idebugdefaultport2.md)
- [IDebugPortNotify2](../../../extensibility/debugger/reference/idebugportnotify2.md) | 36.259259 | 442 | 0.782942 | tur_Latn | 0.542014 |
533f1ca997cd46cdd742aed6e6822e0755b338cf | 411 | md | Markdown | Contact.md | oberron/frenchtouch | 753e1a4622fa94be53ff2cc614d0ed499b284314 | [
"MIT"
] | null | null | null | Contact.md | oberron/frenchtouch | 753e1a4622fa94be53ff2cc614d0ed499b284314 | [
"MIT"
] | 1 | 2019-11-15T07:08:40.000Z | 2019-11-30T10:21:06.000Z | Contact.md | oberron/frenchtouch | 753e1a4622fa94be53ff2cc614d0ed499b284314 | [
"MIT"
] | null | null | null | ---
layout: page
title: Contact
author: Oberron
---
## Sebas
* Civil State: Sebastien Perez Vasseur
> if it is Turing complete, let's port python onto it.
## Oberron
* Civil State: Marius Chevrier
> impossible is an illusion, non-obviousness is a fact | 21.631579 | 82 | 0.73236 | eng_Latn | 0.348551 |
533f5ee7431dddefdcf6c04c4bc93b9084cef0df | 13,706 | md | Markdown | README_en_US.md | MingGH/solo | c9ef32508d6b2c59c923749a567fc912333c00bb | [
"MulanPSL-1.0"
] | 1,537 | 2016-04-12T01:01:31.000Z | 2022-03-30T09:06:40.000Z | README_en_US.md | MingGH/solo | c9ef32508d6b2c59c923749a567fc912333c00bb | [
"MulanPSL-1.0"
] | 224 | 2019-11-29T07:56:49.000Z | 2022-03-31T08:14:20.000Z | README_en_US.md | MingGH/solo | c9ef32508d6b2c59c923749a567fc912333c00bb | [
"MulanPSL-1.0"
] | 473 | 2016-01-11T14:01:43.000Z | 2022-03-25T13:37:34.000Z | <p align = "center">
<img alt="Solo" src="https://b3log.org/images/brand/solo-128.png">
<br><br>
Small and beautiful blog system, designed for programmers
<br><br>
<a title="Build Status" target="_blank" href="https://travis-ci.org/88250/solo"><img src="https://img.shields.io/travis/88250/solo.svg?style=flat-square"></a>
<a title="Docker Image CI" target="_blank" href="https://github.com/88250/solo/actions"><img src="https://img.shields.io/github/workflow/status/88250/solo/Docker%20Image%20CI?color=blue&label=Actions&logo=github&style=flat-square"></a>
<a title="Coverage Status" target="_blank" href="https://coveralls.io/github/88250/solo"><img src="https://img.shields.io/coveralls/github/88250/solo.svg?style=flat-square&color=CC9933"></a>
<a title="Code Size" target="_blank" href="https://github.com/88250/solo"><img src="https://img.shields.io/github/languages/code-size/88250/solo.svg?style=flat-square&color=6699FF"></a>
<a title="MulanPSL2" target="_blank" href="https://license.coscl.org.cn/MulanPSL2"><img src="http://img.shields.io/badge/license-MulanPSL2-orange.svg?style=flat-square"></a>
<br>
<a title="Releases" target="_blank" href="https://github.com/88250/solo/releases"><img src="https://img.shields.io/github/release/88250/solo.svg?style=flat-square&color=CC6666"></a>
<a title="Release Date" target="_blank" href="https://github.com/88250/solo/releases"><img src="https://img.shields.io/github/release-date/88250/solo.svg?style=flat-square&color=99CCFF"></a>
<a title="Downloads" target="_blank" href="https://github.com/88250/solo/releases"><img src="https://img.shields.io/github/downloads/88250/solo/total.svg?style=flat-square&color=99CC99"></a>
<a title="Docker Pulls" target="_blank" href="https://hub.docker.com/r/b3log/solo"><img src="https://img.shields.io/docker/pulls/b3log/solo.svg?style=flat-square&color=blueviolet"></a>
<br>
<a title="GitHub Commits" target="_blank" href="https://github.com/88250/solo/commits/master"><img src="https://img.shields.io/github/commit-activity/m/88250/solo.svg?style=flat-square"></a>
<a title="Last Commit" target="_blank" href="https://github.com/88250/solo/commits/master"><img src="https://img.shields.io/github/last-commit/88250/solo.svg?style=flat-square&color=FF9900"></a>
<a title="GitHub Pull Requests" target="_blank" href="https://github.com/88250/solo/pulls"><img src="https://img.shields.io/github/issues-pr-closed/88250/solo.svg?style=flat-square&color=FF9966"></a>
<a title="Hits" target="_blank" href="https://github.com/88250/hits"><img src="https://hits.b3log.org/88250/solo.svg"></a>
<br><br>
<a title="GitHub Watchers" target="_blank" href="https://github.com/88250/solo/watchers"><img src="https://img.shields.io/github/watchers/88250/solo.svg?label=Watchers&style=social"></a>
<a title="GitHub Stars" target="_blank" href="https://github.com/88250/solo/stargazers"><img src="https://img.shields.io/github/stars/88250/solo.svg?label=Stars&style=social"></a>
<a title="GitHub Forks" target="_blank" href="https://github.com/88250/solo/network/members"><img src="https://img.shields.io/github/forks/88250/solo.svg?label=Forks&style=social"></a>
<a title="Author GitHub Followers" target="_blank" href="https://github.com/88250"><img src="https://img.shields.io/github/followers/88250.svg?label=Followers&style=social"></a>
</p>
<p align="center">
<a href="https://github.com/88250/solo/blob/master/README.md">中文</a>
</p>
## 💡 Introduction
[Solo](https://b3log.org/solo) is a small and beautiful open source blog system, designed for programmers. Solo has a very active [community](https://ld246.com), which can push articles as posts to the community, and replies from the community will be linked as blog comments (for details, please visit [B3log Ideas - Distributed Community Network](https://ld246.com/article/1546941897596)).
> This is a brand new online community experience, so that you who love recording and sharing no longer feel lonely!
Welcome to [Solo Official Discussion Forum](https://ld246.com/tag/solo) to learn more.
## 🗃 Showcases
https://ld246.com/top/solo
## ✨ Features
* [Markdown Editor](https://github.com/Vanessa219/vditor) supports three editing modes: WYSIWYG/Instant Rendering/Split View
* [Tag aggregation classification](https://ld246.com/article/1558320086126)
* Custom navigation links
* Random articles / Related articles / Pin articles / Update reminder
* Custom article permanent link / Signature column
* Configure site SEO parameters / Announcement / Footer
* Code syntax highlighting / Mathematical formulas / Flow charts / Staves
* [Multi-skin, multi-end adaptation](https://b3log.org/solo/#themes)
* Multilingual / International
* Friendly Link Management
* Multi-user writing, team blog
* [Hexo / Jekyll / Markdown import](https://ld246.com/article/1498490209748)
* SQL / JSON / Markdown export
* Atom / RSS / Sitemap
* CDN static resource separation, configurable jsDelivr CDN distribution
* [Pull GitHub repository and automatic backup](https://ld246.com/article/1557238327458)
* [Built-in HTTPS + CDN file storage](https://ld246.com/article/1559928188793)
* [Support to generate and export static sites](https://ld246.com/article/1579053576274) for publishing GitHub Pages
## 🎨 Screenshots
### Start
### Console
### Post
### Skin
### Front
## 🍱 Skins
The current built-in skins are as follows, you can click to preview:
* [Bubble](https://88250.b3log.org/?skin=Bubble)
* [Casper](https://88250.b3log.org/?skin=Casper)
* [Pinghsu](https://88250.b3log.org/?skin=Pinghsu)
* [Jane](https://88250.b3log.org/?skin=Jane)
* [nijigen](https://88250.b3log.org/?skin=nijigen)
* [Medium](https://88250.b3log.org/?skin=Medium)
* [9IPHP](https://88250.b3log.org/?skin=9IPHP)
* [Andrea](https://88250.b3log.org/?skin=Andrea)
* [Bruce](https://88250.b3log.org/?skin=Bruce)
* [Community](https://88250.b3log.org/?skin=Community)
* [favourite](https://88250.b3log.org/?skin=favourite)
* [Finding](https://88250.b3log.org/?skin=Finding)
* [i-nove](https://88250.b3log.org/?skin=i-nove)
* [metro-hot](https://88250.b3log.org/?skin=metro-hot)
* [NeoEase](https://88250.b3log.org/?skin=NeoEase)
* [next](https://88250.b3log.org/?skin=next)
* [owmx-3.0](https://88250.b3log.org/?skin=owmx-3.0)
* [timeline](https://88250.b3log.org/?skin=timeline)
* [tree-house](https://88250.b3log.org/?skin=tree-house)
* [yilia](https://88250.b3log.org/?skin=yilia)
Welcome to [here](https://github.com/88250/solo/issues/2) recommend good-looking skin, we will try to make it.
## 🛠️ Setup
Solo supports "dynamic and static":
* Dynamic blog: built on the server, the process runs in resident memory, and is used online
* Static blog: run on local computer, generate and export static site after writing
### Video demo tutorial
* [Run on localhost](https://www.bilibili.com/video/BV1tK411n7R3)
* [Run via IntelliJ IDEA](https://www.bilibili.com/video/BV1jD4y1S7Ez)
* [Run via Docker on server](https://www.bilibili.com/video/BV1Yk4y1q7rV)
More video tutorials are being produced successively, welcome to follow me on Bilibili: [Scrap Programmer D](https://space.bilibili.com/526767010).
### Run locally
Local operation is mainly used for trial or static site generation, please refer to [here](https://ld246.com/article/1579053576274) for usage of static site generation.
(Video demo tutorial please see [here](https://www.bilibili.com/video/BV1tK411n7R3))
[Download](https://github.com/88250/solo/releases) and unzip the latest Solo package, enter the decompression directory and execute:
* Windows: `java -cp "lib/*;." org.b3log.solo.Server`
* Unix-like: `java -cp "lib/*:." org.b3log.solo.Server`
If you have a Java development environment, you can refer to [here](https://ld246.com/article/1493822943172) to build and run through the source code (Video demo tutorial please see [here](https://www.bilibili.com/video/BV1jD4y1S7Ez)).
### Docker
Docker deployment is a dynamic blog usage, mainly used to deploy dynamic blogs on the server.
(Video demo tutorial please see [here](https://www.bilibili.com/video/BV1Yk4y1q7rV))
#### Get the latest image
```shell
docker pull b3log/solo
```
#### Start the container
* Use MySQL
Create database schema manually (schema name `solo`, character set use` utf8mb4`, sorting rule `utf8mb4_general_ci`):
```sql
create database solo default character set utf8mb4 collate utf8mb4_general_ci;
create user 'root'@'127.0.0.1' identified by '123456';
grant all privileges on *.* to 'root'@'127.0.0.1';
flush privileges;
```
Start container:
```shell
docker run --detach --name solo --network=host \
--env RUNTIME_DB="MYSQL" \
--env JDBC_USERNAME="root" \
--env JDBC_PASSWORD="123456" \
--env JDBC_DRIVER="com.mysql.cj.jdbc.Driver" \
--env JDBC_URL="jdbc:mysql://127.0.0.1:3306/solo?useUnicode=yes&characterEncoding=UTF-8&useSSL=false&serverTimezone=UTC&allowPublicKeyRetrieval=true" \
b3log/solo --listen_port=8080 --server_scheme=http --server_host=localhost --server_port=
```
For simplicity, the host network mode is used to connect to MySQL on the host.
* Use H2 Database
```shell
docker run --detach --name solo --volume ~/solo_h2/:/opt/solo/h2/ --publish 8080:8080 \
--env RUNTIME_DB="H2" \
--env JDBC_USERNAME="root" \
--env JDBC_PASSWORD="123456" \
--env JDBC_DRIVER="org.h2.Driver" \
--env JDBC_URL="jdbc:h2:/opt/solo/h2/db;MODE=MYSQL" \
b3log/solo --listen_port=8080 --server_scheme=http --server_host=localhost --server_port=
```
Start command line arguments description:
* `--listen_port`: the process listen port
* `--server_scheme`: the protocol for the final visiting, if the anti-generation service is enabled with HTTPS, it also needs to be changed to `https`
* `--server_host`: the domain name or public IP for the final visiting, do not bring port
* `--server_port`: the port for the final visiting, use the default 80 or 443 of the browser to leave the value blank
The description of the complete startup arguments can be viewed using `-h`.
#### Logging configuration
By default, logs are printed to the standard output stream through log4j2, which can be viewed through `docker logs solo`. If you need to override the log4j configuration, you can mount the file to achieve:
```shell
--volume ~/log4j2.xml:/opt/solo/log4j2.xml
```
#### Skin configuration
If you want to use other skins, you can mount the directory skins (it needs to contain all the skins you want to use):
```shell
--volume ~/skins/:/opt/solo/skins/
```
#### Version upgrade
1. Pull the latest image
2. Restart the container
You can refer to [here](https://github.com/88250/solo/blob/master/scripts/docker-restart.sh) to write a restart script and run it through crontab every morning to achieve automatic update.
#### Docker Compose
Please refer to [here](https://github.com/liumapp/solo-in-docker), thanks to [@liumapp](https://github.com/liumapp) for providing it.
### NGINX reverse proxy
```nginx
upstream backend {
server localhost:8080; # Solo listen port
}
server {
listen 80;
server_name 88250.b3log.org; # blog domain
access_log off;
location / {
proxy_pass http://backend$request_uri;
proxy_set_header Host $http_host;
proxy_set_header X-Real-IP $remote_addr;
client_max_body_size 10m;
}
}
```
**Be sure to configure**:
```nginx
proxy_set_header Host $http_host;
proxy_set_header X-Real-IP $remote_addr;
```
Otherwise, "Latke configuration error" or abnormal style may appear on the access page; the function of counting online visitors will be abnormal.
## 📜 Documentation
* [Install Solo Blog from scratch](https://ld246.com/article/1565021959471) (thanks @InkDP for sharing)
* [Solo User Guide](https://ld246.com/article/1492881378588)
* [Solo from design to implementation](https://ld246.com/article/1537690756242)
* [Solo Skin Development Guide](https://ld246.com/article/1493814851007)
* [Plugin development](https://docs.google.com/document/pub?id=15H7Q3EBo-44v61Xp_epiYY7vK_gPJLkQaT7T1gkE64w&pli=1)
## 🏘️ Community
* [Forum](https://ld246.com/tag/solo)
* [Issues](https://github.com/88250/solo/issues/new/choose)
## 📄 License
Solo uses the [Mulan Permissive Software License，Version 2](http://license.coscl.org.cn/MulanPSL2) open source license.
## 🙏 Acknowledgement
* [jQuery](https://github.com/jquery/jquery): Front-end JavaScript tool library
* [Vditor](https://github.com/88250/vditor): In-browser Markdown editor
* [Highlight.js](https://github.com/isagalaev/highlight.js): Front-end code syntax highlighting library
* [pjax](https://github.com/defunkt/jquery-pjax): pushState + AJAX = pjax
* [jsoup](https://github.com/jhy/jsoup): Java HTML parser
* [flexmark](https://github.com/vsch/flexmark-java): Java Markdown processor
* [Apache Commons](http://commons.apache.org): Java commons library
* [Latke](https://github.com/88250/latke): Java Web framework based on JSON
| 46.461017 | 391 | 0.735444 | eng_Latn | 0.23174 |
533ffdbac76204315b92b27dafcabfd867a88744 | 2,496 | md | Markdown | userdocs/diagnostics/function-builder-methods.md | ApolloZhu/swift | ec1892a8f0178bc7bf7b3b9cbedd14c6802af6f4 | [
"Apache-2.0"
] | 2 | 2020-04-24T03:06:52.000Z | 2020-04-24T03:06:58.000Z | userdocs/diagnostics/function-builder-methods.md | ApolloZhu/swift | ec1892a8f0178bc7bf7b3b9cbedd14c6802af6f4 | [
"Apache-2.0"
] | null | null | null | userdocs/diagnostics/function-builder-methods.md | ApolloZhu/swift | ec1892a8f0178bc7bf7b3b9cbedd14c6802af6f4 | [
"Apache-2.0"
] | 1 | 2018-03-13T12:56:35.000Z | 2018-03-13T12:56:35.000Z | # Function Builder Methods
To be useful as a function builder, a function builder type must provide a
sufficient subset of function-building methods that enable the transformation of
various statement kinds (`if`, `switch`, `for`..`in`, etc.). The following
example function builder illustrates the various function-building methods one
can define:
```swift
@_functionBuilder
struct ExampleFunctionBuilder {
/// The type of individual statement expressions in the transformed function,
/// which defaults to Component if buildExpression() is not provided.
typealias Expression = ...
/// The type of a partial result, which will be carried through all of the
/// build functions.
typealias Component = ...
/// The type of the final returned result, which defaults to Component if
/// buildFinalResult() is not provided.
typealias Result = ...
/// Required by every function builder to build combined results from
/// statement blocks.
static func buildBlock(_ components: Component...) -> Component { ... }
/// If declared, provides contextual type information for statement
/// expressions to translate them into partial results.
static func buildExpression(_ expression: Expression) -> Component { ... }
/// Enables support for `if` statements that do not have an `else`.
static func buildOptional(_ component: Component?) -> Component { ... }
/// With buildEither(second:), enables support for 'if-else' and 'switch'
/// statements by folding conditional results into a single result.
static func buildEither(first component: Component) -> Component { ... }
/// With buildEither(first:), enables support for 'if-else' and 'switch'
/// statements by folding conditional results into a single result.
static func buildEither(second component: Component) -> Component { ... }
/// Enables support for..in loops in a function builder by combining the
/// results of all iterations into a single result.
static func buildArray(_ components: [Component]) -> Component { ... }
/// If declared, this will be called on the partial result of an 'if
/// #available' block to allow the function builder to erase type
/// information.
static func buildLimitedAvailability(_ component: Component) -> Component { ... }
/// If declared, this will be called on the partial result from the outermost
/// block statement to produce the final returned result.
static func buildFinalResult(_ component: Component) -> Result { ... }
}
```
| 43.789474 | 83 | 0.728766 | eng_Latn | 0.994462 |
534052161c8c6477e9f5bccfc78f20e95a556b59 | 2,248 | md | Markdown | README.md | WairimuThuku/wildlife-reporter | f76b0707a86412b35c51e5d52d5b78f704b3f6fd | [
"MIT"
] | null | null | null | README.md | WairimuThuku/wildlife-reporter | f76b0707a86412b35c51e5d52d5b78f704b3f6fd | [
"MIT"
] | null | null | null | README.md | WairimuThuku/wildlife-reporter | f76b0707a86412b35c51e5d52d5b78f704b3f6fd | [
"MIT"
] | null | null | null | # Wildlife Tracker
Wildlife Tracker is an app that allows one to record sightings of various animal,It allows one to create rangers,locations,animals and
sightings. It also allows you to view rangers locations sightings and animals. One can also view sightings a ranger has made and
locations with the sightings that have occured in them
## Author
- [Lulu Thuku](https://github.com/WairimuThuku)
## Setup/Installation Requirements
* Fork this repo
* Clone this repo
* Open terminal
* Navigate to appropriate directory using the cd command
* type in the command git clone and paste the url of clone and then press enter
## Setup Requirements for Database
* In PSQL:
* CREATE DATABASE wildlife_tracker;
* \c wildlife_tracker
* CREATE TABLE animals (id serial PRIMARY KEY, name varchar,type VARCHAR,health VARCHAR,age VARCHAR);
* CREATE TABLE locations (id serial PRIMARY KEY,name VARCHAR);
* CREATE TABLE locations_sightings (id serial PRIMARY KEY,location_id INT,sighting_id INT);
* CREATE TABLE rangers (id serial PRIMARY KEY,name VARCHAR,badge_number VARCHAR);
* CREATE TABLE rangers_sightings (id serial PRIMARY KEY,ranger_id INT,sighting_id INT);
* CREATE TABLE sightings (id serial PRIMARY KEY,animal_id INT,ranger_id INT,location_id INT,time TIMESTAMP);
* CREATE DATABASE wildlife_tracker_test WITH TEMPLATE wildlife_tracker;
## In order to run locally
* Go to DB.class in main/java folder and make necessary changes
* Go to DatabaseRule in test/java folder and make necessary changes
## Technologies Used
* Java for backend
* Heroku for deployment
* CSS for styling
* VTL
* JavaScrpt
## Support and contact details
If you come across any problems you can reach me at: [email protected]
### License
*This project is licensed under the terms of the MIT license.*
Copyright (c) 2022 **Lulu Thuku**
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
| 44.078431 | 135 | 0.790925 | eng_Latn | 0.974669 |
5340d822e0e38da0fdcc68cf901020c18c8ad92f | 6,307 | md | Markdown | aspnet/web-forms/overview/deployment/visual-studio-web-deployment/setting-folder-permissions.md | yliu138/Docs | 99935146241613c6eb4b24bbcd775c8318677bc3 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2019-05-08T19:48:25.000Z | 2019-05-08T19:48:25.000Z | aspnet/web-forms/overview/deployment/visual-studio-web-deployment/setting-folder-permissions.md | yliu138/Docs | 99935146241613c6eb4b24bbcd775c8318677bc3 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | aspnet/web-forms/overview/deployment/visual-studio-web-deployment/setting-folder-permissions.md | yliu138/Docs | 99935146241613c6eb4b24bbcd775c8318677bc3 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
uid: web-forms/overview/deployment/visual-studio-web-deployment/setting-folder-permissions
title: "ASP.NET Web Deployment using Visual Studio: Setting Folder Permissions | Microsoft Docs"
author: tdykstra
description: "This tutorial series shows you how to deploy (publish) an ASP.NET web application to Azure App Service Web Apps or to a third-party hosting provider, by usin..."
ms.author: aspnetcontent
ms.date: 02/15/2013
ms.assetid: 9715a121-fa55-4f1b-a5d2-fb3f6cd8be8f
msc.legacyurl: /web-forms/overview/deployment/visual-studio-web-deployment/setting-folder-permissions
msc.type: authoredcontent
---
ASP.NET Web Deployment using Visual Studio: Setting Folder Permissions
====================
by [Tom Dykstra](https://github.com/tdykstra)
[Download Starter Project](http://go.microsoft.com/fwlink/p/?LinkId=282627)
> This tutorial series shows you how to deploy (publish) an ASP.NET web application to Azure App Service Web Apps or to a third-party hosting provider, by using Visual Studio 2012 or Visual Studio 2010. For information about the series, see [the first tutorial in the series](introduction.md).
## Overview
In this tutorial, you set folder permissions for the *Elmah* folder in the deployed web site so that the application can create log files in that folder.
When you test a web application in Visual Studio using the Visual Studio Development Server (Cassini) or IIS Express, the application runs under your identity. You are most likely an administrator on your development computer and have full authority to do anything to any file in any folder. But when an application runs under IIS, it runs under the identity defined for the application pool that the site is assigned to. This is typically a system-defined account that has limited permissions. By default it has read and execute permissions on your web application's files and folders, but it doesn't have write access.
This becomes an issue if your application creates or updates files, which is a common need in web applications. In the Contoso University application, Elmah creates XML files in the *Elmah* folder in order to save details about errors. Even if you don't use something like Elmah, your site might let users upload files or perform other tasks that write data to a folder in your site.
Reminder: If you get an error message or something doesn't work as you go through the tutorial, be sure to check the [troubleshooting page](troubleshooting.md).
## Test error logging and reporting
To see how the application doesn't work correctly in IIS (although it did when you tested it in Visual Studio), you can cause an error that would normally be logged by Elmah, and then open the Elmah error log to see the details. If Elmah was unable to create an XML file and store the error details, you see an empty error report.
Open a browser and go to `http://localhost/ContosoUniversity`, and then request an invalid URL like *Studentsxxx.aspx*. You see a system-generated error page instead of the *GenericErrorPage.aspx* page because the `customErrors` setting in the Web.config file is "RemoteOnly" and you are running IIS locally:
Now run *Elmah.axd* to see the error report. After you log in with the administrator account credentials ("admin" and "devpwd"), you see an empty error log page because Elmah was unable to create an XML file in the *Elmah* folder:
## Set write permission on the Elmah folder
You can set folder permissions manually or you can make it an automatic part of the deployment process. Making it automatic requires complex MSBuild code, and since you only have to do this the first time you deploy, the following steps how to do it manually. (For information about how to make this part of the deployment process, see [Setting Folder Permissions on Web Publish](http://sedodream.com/2011/11/08/SettingFolderPermissionsOnWebPublish.aspx) on Sayed Hashimi's blog.)
1. In **File Explorer**, navigate to *C:\inetpub\wwwroot\ContosoUniversity*. Right-click the *Elmah* folder, select **Properties**, and then select the **Security** tab.
2. Click **Edit**.
3. In the **Permissions for Elmah** dialog box, select **DefaultAppPool**, and then select the **Write** check box in the **Allow** column.
(If you don't see **DefaultAppPool** in the **Group or user names** list, you probably used some other method than the one specified in this tutorial to set up IIS and ASP.NET 4 on your computer. In that case, find out what identity is used by the application pool assigned to the Contoso University application, and grant write permission to that identity. See the links about application pool identities at the end of this tutorial.) Click **OK** in both dialog boxes.
## Retest error logging and reporting
Test by causing an error again in the same way (request a bad URL) and run the **Error Log** page. This time the error appears on the page.
## Summary
You have now completed all of the tasks necessary to get Contoso University working correctly in IIS on your local computer. In the next tutorial, you will make the site publicly available by deploying it to Azure.
## More information
In this example, the reason why Elmah was unable to save log files was fairly obvious. You can use IIS tracing in cases where the cause of the problem is not so obvious; see [Troubleshooting Failed Requests Using Tracing in IIS 7](https://www.iis.net/learn/troubleshoot/using-failed-request-tracing/troubleshooting-failed-requests-using-tracing-in-iis) on the IIS.net site.
For more information about how to grant permissions to application pool identities, see [Application Pool Identities](https://www.iis.net/learn/manage/configuring-security/application-pool-identities) and [Secure Content in IIS Through File System ACLs](https://www.iis.net/learn/get-started/planning-for-security/secure-content-in-iis-through-file-system-acls) on the IIS.net site.
> [!div class="step-by-step"]
> [Previous](deploying-to-iis.md)
> [Next](deploying-to-production.md)
| 85.22973 | 620 | 0.784367 | eng_Latn | 0.992938 |
5340e693e39f9ca00896105be2ac561eaaca2e40 | 44 | md | Markdown | README.md | vadimLBN/Nauka-Gita | 7b4285e8484b0c43e09a014be37e0c42149d8f2d | [
"Apache-2.0"
] | null | null | null | README.md | vadimLBN/Nauka-Gita | 7b4285e8484b0c43e09a014be37e0c42149d8f2d | [
"Apache-2.0"
] | null | null | null | README.md | vadimLBN/Nauka-Gita | 7b4285e8484b0c43e09a014be37e0c42149d8f2d | [
"Apache-2.0"
] | null | null | null | # Nauka-Gita
Moje pierwsze repozytorium GIT
| 14.666667 | 30 | 0.818182 | pol_Latn | 0.993253 |
5340fe5b13fca864249cfe7a1374155f0435552a | 7,974 | md | Markdown | docs/framework/wpf/controls/tooltip-overview.md | Athosone/docs.fr-fr | 83c2fd74def907edf5da4a31fee2d08133851d2f | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/wpf/controls/tooltip-overview.md | Athosone/docs.fr-fr | 83c2fd74def907edf5da4a31fee2d08133851d2f | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/wpf/controls/tooltip-overview.md | Athosone/docs.fr-fr | 83c2fd74def907edf5da4a31fee2d08133851d2f | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Vue d'ensemble de l'info-bulle
ms.date: 03/30/2017
dev_langs:
- csharp
- vb
helpviewer_keywords:
- ToolTip control [WPF], about ToolTip control
- controls [WPF], ToolTip
ms.assetid: f06c1603-e9cb-4809-8a62-234607fc52f7
ms.openlocfilehash: 08b30d8be83ef9d814d17c5d4ec0c95a26bacdad
ms.sourcegitcommit: 9b552addadfb57fab0b9e7852ed4f1f1b8a42f8e
ms.translationtype: HT
ms.contentlocale: fr-FR
ms.lasthandoff: 04/23/2019
ms.locfileid: "61790726"
---
# <a name="tooltip-overview"></a>Vue d'ensemble de l'info-bulle
Une info-bulle est une petite fenêtre contextuelle qui s’affiche lorsqu’un utilisateur place le pointeur de la souris au-dessus d’un élément, tel qu’un <xref:System.Windows.Controls.Button>. Cette rubrique présente l’info-bulle et explique comment créer et personnaliser son contenu.
<a name="what_is_a_tooltip"></a>
## <a name="what-is-a-tooltip"></a>Qu’est-ce qu’une info-bulle ?
Lorsqu’un utilisateur déplace le pointeur de la souris sur un élément qui contient une info-bulle, une fenêtre qui renferme le contenu de l’info-bulle (par exemple, le contenu texte qui décrit la fonction d’un contrôle) apparaît pendant un laps de temps spécifié. Si l’utilisateur éloigne le pointeur de la souris du contrôle, la fenêtre disparaît car le contenu de l’info-bulle ne peut pas recevoir le focus.
Une info-bulle peut contenir une ou plusieurs lignes de texte, des images, des formes ou un autre contenu visuel. Pour définir une info-bulle pour un contrôle, vous devez définir l’une des propriétés suivantes pour le contenu de l’info-bulle.
- <xref:System.Windows.FrameworkContentElement.ToolTip%2A?displayProperty=nameWithType>
- <xref:System.Windows.FrameworkElement.ToolTip%2A?displayProperty=nameWithType>
Propriété que vous utilisez varie selon que le contrôle qui définit l’info-bulle hérite le <xref:System.Windows.FrameworkContentElement> ou <xref:System.Windows.FrameworkElement> classe.
<a name="create_tooltip"></a>
## <a name="creating-a-tooltip"></a>Création d’une info-bulle
L’exemple suivant montre comment créer une info-bulle simple en définissant le <xref:System.Windows.FrameworkElement.ToolTip%2A> propriété pour un <xref:System.Windows.Controls.Button> contrôle à une chaîne de texte.
[!code-xaml[GroupBoxSnippet#ToolTipString](~/samples/snippets/csharp/VS_Snippets_Wpf/GroupBoxSnippet/CS/Window1.xaml#tooltipstring)]
Vous pouvez également définir une info-bulle comme un <xref:System.Windows.Controls.ToolTip> objet. L’exemple suivant utilise [!INCLUDE[TLA2#tla_xaml](../../../../includes/tla2sharptla-xaml-md.md)] pour spécifier un <xref:System.Windows.Controls.ToolTip> objet en tant que l’info-bulle d’un <xref:System.Windows.Controls.TextBox> élément. Notez que l’exemple spécifie le <xref:System.Windows.Controls.ToolTip> en définissant le <xref:System.Windows.FrameworkElement.ToolTip%2A?displayProperty=nameWithType> propriété.
[!code-xaml[ToolTipSimple#ToolTip](~/samples/snippets/csharp/VS_Snippets_Wpf/ToolTipSimple/CSharp/Pane1.xaml#tooltip)]
L’exemple suivant utilise le code pour générer un <xref:System.Windows.Controls.ToolTip> objet. L’exemple crée un <xref:System.Windows.Controls.ToolTip> (`tt`) et l’associe un <xref:System.Windows.Controls.Button>.
[!code-csharp[ToolTipSimple#2](~/samples/snippets/csharp/VS_Snippets_Wpf/ToolTipSimple/CSharp/Pane1.xaml.cs#2)]
[!code-vb[ToolTipSimple#2](~/samples/snippets/visualbasic/VS_Snippets_Wpf/ToolTipSimple/VisualBasic/Window1.xaml.vb#2)]
Vous pouvez également créer le contenu d’info-bulle qui n’est pas défini comme un <xref:System.Windows.Controls.ToolTip> objet en plaçant le contenu de l’info-bulle dans un élément de disposition, comme un <xref:System.Windows.Controls.DockPanel>. L’exemple suivant montre comment définir le <xref:System.Windows.FrameworkElement.ToolTip%2A> propriété d’un <xref:System.Windows.Controls.TextBox> au contenu qui est inclu dans un <xref:System.Windows.Controls.DockPanel> contrôle.
[!code-xaml[GroupBoxSnippet#ToolTipDockPanel](~/samples/snippets/csharp/VS_Snippets_Wpf/GroupBoxSnippet/CS/Window1.xaml#tooltipdockpanel)]
<a name="Using_the_ToolTip_and_ToolTipService_Properties"></a>
## <a name="using-the-properties-of-the-tooltip-and-tooltipservice-classes"></a>Utilisation des propriétés de l’info-bulle et des classes ToolTipService
Vous pouvez personnaliser le contenu de l’info-bulle en définissant des propriétés visuelles et en appliquant des styles. Si vous définissez l’info-bulle contenu comme un <xref:System.Windows.Controls.ToolTip> de l’objet, vous pouvez définir les propriétés visuelles de la <xref:System.Windows.Controls.ToolTip> objet. Sinon, vous devez définir des propriétés jointes équivalentes sur la <xref:System.Windows.Controls.ToolTipService> classe.
Pour obtenir un exemple montrant comment définir des propriétés pour spécifier la position du contenu de l’info-bulle à l’aide de la <xref:System.Windows.Controls.ToolTip> et <xref:System.Windows.Controls.ToolTipService> propriétés, consultez [positionner une info-bulle](how-to-position-a-tooltip.md).
<a name="StylingToolTip"></a>
## <a name="styling-a-tooltip"></a>Application d’un style à une info-bulle
Vous pouvez appliquer un style un <xref:System.Windows.Controls.ToolTip> en définissant un personnalisé <xref:System.Windows.Style>. L’exemple suivant définit un <xref:System.Windows.Style> appelé `Simple` qui montre comment décaler le positionnement de la <xref:System.Windows.Controls.ToolTip> et modifier son apparence en définissant le <xref:System.Windows.Controls.Control.Background%2A>, <xref:System.Windows.Controls.Control.Foreground%2A>, <xref:System.Windows.Controls.Control.FontSize%2A>, et <xref:System.Windows.Controls.Control.FontWeight%2A>.
[!code-xaml[ToolTipSimple#Style](~/samples/snippets/csharp/VS_Snippets_Wpf/ToolTipSimple/CSharp/Pane1.xaml#style)]
<a name="UsingtheToolTipServiceTimeIntervalProperties"></a>
## <a name="using-the-time-interval-properties-of-tooltipservice"></a>Utilisation des propriétés d’intervalle de temps de ToolTipService
Le <xref:System.Windows.Controls.ToolTipService> classe fournit les propriétés suivantes pour vous permettent de définir des info-bulle affichent des heures : <xref:System.Windows.Controls.ToolTipService.InitialShowDelay%2A>, <xref:System.Windows.Controls.ToolTipService.BetweenShowDelay%2A>, et <xref:System.Windows.Controls.ToolTipService.ShowDuration%2A>.
Utilisez le <xref:System.Windows.Controls.ToolTipService.InitialShowDelay%2A> et <xref:System.Windows.Controls.ToolTipService.ShowDuration%2A> propriétés pour spécifier un délai, généralement bref, avant qu’un <xref:System.Windows.Controls.ToolTip> s’affiche et également de spécifier la durée pendant laquelle un <xref:System.Windows.Controls.ToolTip> reste visible. Pour plus d'informations, voir [Procédure : Différer l’affichage d’une info-bulle](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/ms747264(v=vs.90)).
Le <xref:System.Windows.Controls.ToolTipService.BetweenShowDelay%2A> propriété détermine si les info-bulles des différents contrôles apparaissent sans délai initial lorsque vous déplacez rapidement le pointeur de la souris entre eux. Pour plus d’informations sur la <xref:System.Windows.Controls.ToolTipService.BetweenShowDelay%2A> propriété, consultez [utiliser la propriété BetweenShowDelay](how-to-use-the-betweenshowdelay-property.md).
L’exemple suivant montre comment définir ces propriétés pour une info-bulle.
[!code-xaml[ToolTipService#ToolTip](~/samples/snippets/csharp/VS_Snippets_Wpf/ToolTipService/CSharp/Pane1.xaml#tooltip)]
## <a name="see-also"></a>Voir aussi
- <xref:System.Windows.Controls.ToolTipService>
- <xref:System.Windows.Controls.ToolTip>
- <xref:System.Windows.Controls.ToolTipEventArgs>
- <xref:System.Windows.Controls.ToolTipEventHandler>
- [Rubriques de guide pratique](tooltip-how-to-topics.md)
| 96.072289 | 559 | 0.795586 | fra_Latn | 0.682537 |
53414ce645818c287f2bb9faf1a91ddf9dc89265 | 13,492 | md | Markdown | documents/benchmark_write_read.md | RapidsAtHKUST/EngineRace | 6d19ebc5f26a7ef0fc655953d7597a94003ca920 | [
"MIT"
] | null | null | null | documents/benchmark_write_read.md | RapidsAtHKUST/EngineRace | 6d19ebc5f26a7ef0fc655953d7597a94003ca920 | [
"MIT"
] | null | null | null | documents/benchmark_write_read.md | RapidsAtHKUST/EngineRace | 6d19ebc5f26a7ef0fc655953d7597a94003ca920 | [
"MIT"
] | null | null | null | # 思路
## test-device-write: Code Updated Unitl 11/07 (From 11/04).
控制变量 | 范围
--- | ---
order | 顺序写，随机写(random shuffle)
buffer-size | `{1,2,4,8,16}` `*` `4KB`
* 顺序 vs 随机写 value no-fallocate (2018-11-05_11-40-testwrite-vary-buffsize-seq-rand, not-o-direct)
```
11:16:30 156:[0m Close the database.
11:16:30 412:[0m Close file..
11:16:30 426:[0m 0
11:18:26 352:[0m Step one File exists, 508,500, 116.089
11:18:26 426:[0m 1
11:20:21 352:[0m Step one File exists, 506,536, 114.852
11:20:21 426:[0m 2
11:22:15 352:[0m Step one File exists, 508,584, 114.419
11:22:15 426:[0m 3
11:24:10 352:[0m Step one File exists, 510,688, 114.930
11:24:10 426:[0m 4
11:26:06 352:[0m Step one File exists, 510,824, 115.395
11:26:06 436:[0m Close file end..
11:26:06 457:[0m 0
11:28:02 352:[0m Step one File exists, 513,432, 116.023
11:28:02 457:[0m 1
11:29:57 352:[0m Step one File exists, 513,432, 114.868
11:29:57 457:[0m 2
11:31:51 352:[0m Step one File exists, 513,432, 114.491
11:31:51 457:[0m 3
11:33:46 352:[0m Step one File exists, 513,432, 114.862
11:33:46 457:[0m 4
11:35:41 352:[0m Step one File exists, 513,432, 115.382
11:35:41 185:[0m Close the database successfully.
```
* 顺序写 no-fallocate (2018-11-07_17-55-write-kv-no-fallocate)
```
17:34:27 180:[0m Close the database.
17:34:27 480:[0m Close file..
17:34:27 494:[0m 0
17:34:27 355:[0m rm -r test_directory/*
17:38:26 414:[0m Step one File exists, 508,592, 238.938
17:38:26 426:[0m Step one File exists, 508,592, 238.992 end.
17:40:16 458:[0m Step two File exists, 508,592, 109.900
17:40:16 494:[0m 1
17:40:16 355:[0m rm -r test_directory/*
17:42:12 414:[0m Step one File exists, 506,752, 115.441
17:42:12 426:[0m Step one File exists, 506,752, 115.443 end.
17:44:02 458:[0m Step two File exists, 506,936, 109.898
17:44:02 494:[0m 2
17:44:02 355:[0m rm -r test_directory/*
17:45:56 414:[0m Step one File exists, 506,936, 114.264
17:45:56 426:[0m Step one File exists, 506,936, 114.273 end.
17:47:42 458:[0m Step two File exists, 506,936, 105.959
17:47:42 494:[0m 3
17:47:42 355:[0m rm -r test_directory/*
17:49:37 414:[0m Step one File exists, 506,980, 114.714
17:49:37 426:[0m Step one File exists, 506,980, 114.724 end.
17:51:18 458:[0m Step two File exists, 507,132, 100.984
17:51:18 494:[0m 4
17:51:18 355:[0m rm -r test_directory/*
17:53:14 414:[0m Step one File exists, 507,344, 115.299
17:53:14 426:[0m Step one File exists, 507,344, 115.305 end.
17:54:52 458:[0m Step two File exists, 508,928, 98.516
17:54:52 215:[0m Close the database successfully.
```
* 顺序写 fallocate (2018-11-07_20-15-write-kv-fallocate)
```
20:02:05 180:[0m Close the database.
20:02:05 483:[0m Close file..
20:02:05 497:[0m 0
20:02:05 355:[0m rm -r test_directory/*
20:02:05 377:[0m Release File exists, 508,420, 0.263
20:04:15 417:[0m Step one File exists, 508,576, 130.198
20:04:16 429:[0m Step one File exists, 508,576, 130.241 end.
20:04:16 497:[0m 1
20:04:16 355:[0m rm -r test_directory/*
20:04:16 377:[0m Release File exists, 506,844, 0.183
20:06:10 417:[0m Step one File exists, 507,132, 114.513
20:06:10 429:[0m Step one File exists, 507,132, 114.551 end.
20:06:10 497:[0m 2
20:06:10 355:[0m rm -r test_directory/*
20:06:11 377:[0m Release File exists, 507,148, 0.247
20:08:05 417:[0m Step one File exists, 507,260, 113.964
20:08:05 429:[0m Step one File exists, 507,260, 113.971 end.
20:08:05 497:[0m 3
20:08:05 355:[0m rm -r test_directory/*
20:08:05 377:[0m Release File exists, 507,420, 0.209
20:10:00 417:[0m Step one File exists, 507,668, 114.389
20:10:00 429:[0m Step one File exists, 507,668, 114.393 end.
20:10:00 497:[0m 4
20:10:00 355:[0m rm -r test_directory/*
20:10:00 377:[0m Release File exists, 507,864, 0.268
20:11:55 417:[0m Step one File exists, 508,156, 114.736
20:11:55 429:[0m Step one File exists, 508,156, 114.744 end.
20:11:55 215:[0m Close the database successfully.
```
* 随机和顺序读写 (2018-11-07_01-35-write-odirect-also)
```
00:53:54 :159:[0m Close the database.
00:53:54 :431:[0m Close file..
00:53:54 :445:[0m 0
00:55:49 :368:[0m Step one File exists, 508,516, 115.656
00:55:49 :377:[0m Step one File exists, 508,516, 115.657 end.
00:57:39 :409:[0m Step two File exists, 508,580, 109.911
00:57:39 :445:[0m 1
00:59:34 :368:[0m Step one File exists, 514,656, 114.454
00:59:34 :377:[0m Step one File exists, 514,656, 114.455 end.
01:01:23 :409:[0m Step two File exists, 515,016, 109.804
01:01:23 :445:[0m 2
01:03:18 :368:[0m Step one File exists, 515,016, 114.241
01:03:18 :377:[0m Step one File exists, 515,016, 114.242 end.
01:05:04 :409:[0m Step two File exists, 515,016, 106.102
01:05:04 :445:[0m 3
01:06:58 :368:[0m Step one File exists, 515,036, 114.576
01:06:58 :377:[0m Step one File exists, 515,036, 114.577 end.
01:08:39 :409:[0m Step two File exists, 515,192, 101.067
01:08:39 :445:[0m 4
01:10:35 :368:[0m Step one File exists, 515,308, 115.066
01:10:35 :377:[0m Step one File exists, 515,308, 115.066 end.
01:12:13 :409:[0m Step two File exists, 517,124, 98.652
01:12:13 :455:[0m Close file end..
01:12:13 :476:[0m 0
01:14:09 :368:[0m Step one File exists, 518,108, 115.630
01:14:09 :377:[0m Step one File exists, 518,108, 115.630 end.
01:15:59 :409:[0m Step two File exists, 518,108, 109.734
01:15:59 :476:[0m 1
01:17:53 :368:[0m Step one File exists, 518,108, 114.688
01:17:53 :377:[0m Step one File exists, 518,108, 114.688 end.
01:19:43 :409:[0m Step two File exists, 518,108, 110.020
01:19:43 :476:[0m 2
01:21:38 :368:[0m Step one File exists, 518,108, 114.349
01:21:38 :377:[0m Step one File exists, 518,108, 114.349 end.
01:23:24 :409:[0m Step two File exists, 518,108, 105.950
01:23:24 :476:[0m 3
01:25:18 :368:[0m Step one File exists, 518,108, 114.743
01:25:18 :377:[0m Step one File exists, 518,108, 114.743 end.
01:27:00 :409:[0m Step two File exists, 518,108, 101.057
01:27:00 :476:[0m 4
01:28:55 :368:[0m Step one File exists, 518,108, 115.197
01:28:55 :377:[0m Step one File exists, 518,108, 115.197 end.
01:30:33 :409:[0m Step two File exists, 518,108, 98.599
01:30:33 :194:[0m Close the database successfully.
```
* 随机和顺序总结
* buffer-size足够大随机和顺序的读写性能相近
* 顺序和随机对read影响更大, 对write影响相对较小
* write-benchmark总结
* 16KB buffer写入最好
* fallocate与否总时间差别不大 (加上`0.263s` fallocate time), `4KB` no fallocate very bad, `8KB` no fallocte ok
* read-benchmark总结
* read `block size / buffer size` 一次较大更好
### test-device-write-aio: Code Updated Unitl 11/14 (From 11/12).
答辩中不讲。在写入中用处不大。
* Write-Only
变量 | 经验
--- | ---
thread# | 32 ok, at least `4` (better than `2`)
QueueDepth | 32 ok
io_getevents block threshold | `4`, busy waiting cost too much cpu
### Others
small queue-depth is ok for write. (199064, 2018-11-14_11-36)
8 thread per round is ok because in a no-dependency implementation.
```
14:46:40 396: Write Stat of tid 56, mem usage: 576,520 KB, elapsed time: 14.337 s, ts: 1542091600.226 s
14:46:40 396: Write Stat of tid 57, mem usage: 576,768 KB, elapsed time: 14.337 s, ts: 1542091600.227 s
14:46:40 396: Write Stat of tid 58, mem usage: 577,012 KB, elapsed time: 14.337 s, ts: 1542091600.227 s
14:46:40 396: Write Stat of tid 63, mem usage: 577,256 KB, elapsed time: 14.337 s, ts: 1542091600.227 s
14:46:40 396: Write Stat of tid 60, mem usage: 577,500 KB, elapsed time: 14.337 s, ts: 1542091600.227 s
14:46:40 396: Write Stat of tid 59, mem usage: 577,744 KB, elapsed time: 14.338 s, ts: 1542091600.227 s
14:46:40 396: Write Stat of tid 61, mem usage: 577,988 KB, elapsed time: 14.338 s, ts: 1542091600.228 s
14:46:40 396: Write Stat of tid 62, mem usage: 577,988 KB, elapsed time: 14.338 s, ts: 1542091600.228 s
14:46:54 396: Write Stat of tid 53, mem usage: 576,508 KB, elapsed time: 28.705 s, ts: 1542091614.593 s
14:46:54 396: Write Stat of tid 51, mem usage: 576,548 KB, elapsed time: 28.706 s, ts: 1542091614.594 s
14:46:54 396: Write Stat of tid 48, mem usage: 576,800 KB, elapsed time: 28.707 s, ts: 1542091614.595 s
14:46:54 396: Write Stat of tid 54, mem usage: 577,052 KB, elapsed time: 28.707 s, ts: 1542091614.595 s
14:46:54 396: Write Stat of tid 50, mem usage: 577,304 KB, elapsed time: 28.707 s, ts: 1542091614.595 s
14:46:54 396: Write Stat of tid 52, mem usage: 577,556 KB, elapsed time: 28.707 s, ts: 1542091614.595 s
14:46:54 396: Write Stat of tid 49, mem usage: 577,808 KB, elapsed time: 28.707 s, ts: 1542091614.595 s
14:46:54 396: Write Stat of tid 55, mem usage: 578,060 KB, elapsed time: 28.707 s, ts: 1542091614.596 s
14:47:08 396: Write Stat of tid 42, mem usage: 580,068 KB, elapsed time: 43.079 s, ts: 1542091628.965 s
14:47:08 396: Write Stat of tid 45, mem usage: 580,068 KB, elapsed time: 43.079 s, ts: 1542091628.966 s
14:47:08 396: Write Stat of tid 43, mem usage: 580,108 KB, elapsed time: 43.080 s, ts: 1542091628.966 s
14:47:08 396: Write Stat of tid 41, mem usage: 580,108 KB, elapsed time: 43.081 s, ts: 1542091628.967 s
14:47:08 396: Write Stat of tid 44, mem usage: 580,108 KB, elapsed time: 43.080 s, ts: 1542091628.967 s
14:47:08 396: Write Stat of tid 40, mem usage: 580,108 KB, elapsed time: 43.082 s, ts: 1542091628.968 s
14:47:08 396: Write Stat of tid 47, mem usage: 580,108 KB, elapsed time: 43.082 s, ts: 1542091628.970 s
14:47:08 396: Write Stat of tid 46, mem usage: 580,108 KB, elapsed time: 43.088 s, ts: 1542091628.975 s
14:47:23 396: Write Stat of tid 33, mem usage: 578,084 KB, elapsed time: 57.386 s, ts: 1542091643.269 s
14:47:23 396: Write Stat of tid 32, mem usage: 578,336 KB, elapsed time: 57.387 s, ts: 1542091643.270 s
14:47:23 396: Write Stat of tid 34, mem usage: 578,588 KB, elapsed time: 57.387 s, ts: 1542091643.271 s
14:47:23 396: Write Stat of tid 38, mem usage: 578,840 KB, elapsed time: 57.388 s, ts: 1542091643.274 s
14:47:23 396: Write Stat of tid 35, mem usage: 579,092 KB, elapsed time: 57.390 s, ts: 1542091643.275 s
14:47:23 396: Write Stat of tid 36, mem usage: 579,336 KB, elapsed time: 57.390 s, ts: 1542091643.276 s
14:47:23 396: Write Stat of tid 37, mem usage: 579,588 KB, elapsed time: 57.394 s, ts: 1542091643.279 s
14:47:23 396: Write Stat of tid 39, mem usage: 579,840 KB, elapsed time: 57.395 s, ts: 1542091643.281 s
14:47:37 396: Write Stat of tid 27, mem usage: 578,068 KB, elapsed time: 71.688 s, ts: 1542091657.570 s
14:47:37 396: Write Stat of tid 30, mem usage: 578,320 KB, elapsed time: 71.688 s, ts: 1542091657.570 s
14:47:37 396: Write Stat of tid 28, mem usage: 578,572 KB, elapsed time: 71.689 s, ts: 1542091657.571 s
14:47:37 396: Write Stat of tid 25, mem usage: 578,824 KB, elapsed time: 71.690 s, ts: 1542091657.571 s
14:47:37 396: Write Stat of tid 26, mem usage: 579,076 KB, elapsed time: 71.690 s, ts: 1542091657.572 s
14:47:37 396: Write Stat of tid 29, mem usage: 579,328 KB, elapsed time: 71.691 s, ts: 1542091657.574 s
14:47:37 396: Write Stat of tid 24, mem usage: 579,580 KB, elapsed time: 71.693 s, ts: 1542091657.575 s
14:47:37 396: Write Stat of tid 31, mem usage: 579,832 KB, elapsed time: 71.694 s, ts: 1542091657.577 s
14:47:51 396: Write Stat of tid 18, mem usage: 580,084 KB, elapsed time: 85.986 s, ts: 1542091671.863 s
14:47:51 396: Write Stat of tid 17, mem usage: 580,336 KB, elapsed time: 85.988 s, ts: 1542091671.864 s
14:47:51 396: Write Stat of tid 16, mem usage: 580,588 KB, elapsed time: 85.989 s, ts: 1542091671.864 s
14:47:51 396: Write Stat of tid 22, mem usage: 580,840 KB, elapsed time: 85.985 s, ts: 1542091671.865 s
14:47:51 396: Write Stat of tid 20, mem usage: 581,092 KB, elapsed time: 85.986 s, ts: 1542091671.866 s
14:47:51 396: Write Stat of tid 21, mem usage: 581,344 KB, elapsed time: 85.986 s, ts: 1542091671.866 s
14:47:51 396: Write Stat of tid 19, mem usage: 581,596 KB, elapsed time: 85.989 s, ts: 1542091671.867 s
14:47:51 396: Write Stat of tid 23, mem usage: 581,848 KB, elapsed time: 85.988 s, ts: 1542091671.869 s
14:48:06 396: Write Stat of tid 14, mem usage: 582,100 KB, elapsed time: 100.284 s, ts: 1542091686.158 s
14:48:06 396: Write Stat of tid 15, mem usage: 582,352 KB, elapsed time: 100.286 s, ts: 1542091686.161 s
14:48:06 396: Write Stat of tid 12, mem usage: 582,604 KB, elapsed time: 100.291 s, ts: 1542091686.165 s
14:48:06 396: Write Stat of tid 13, mem usage: 582,856 KB, elapsed time: 100.291 s, ts: 1542091686.165 s
14:48:06 396: Write Stat of tid 10, mem usage: 582,856 KB, elapsed time: 100.296 s, ts: 1542091686.165 s
14:48:06 396: Write Stat of tid 11, mem usage: 583,140 KB, elapsed time: 100.297 s, ts: 1542091686.166 s
14:48:06 396: Write Stat of tid 9, mem usage: 583,180 KB, elapsed time: 100.298 s, ts: 1542091686.166 s
14:48:06 396: Write Stat of tid 8, mem usage: 583,220 KB, elapsed time: 100.299 s, ts: 1542091686.166 s
14:48:20 396: Write Stat of tid 7, mem usage: 581,236 KB, elapsed time: 114.592 s, ts: 1542091700.458 s
14:48:20 396: Write Stat of tid 6, mem usage: 581,276 KB, elapsed time: 114.592 s, ts: 1542091700.458 s
14:48:20 396: Write Stat of tid 0, mem usage: 581,316 KB, elapsed time: 114.617 s, ts: 1542091700.472 s
14:48:20 396: Write Stat of tid 4, mem usage: 581,356 KB, elapsed time: 114.608 s, ts: 1542091700.472 s
14:48:20 396: Write Stat of tid 1, mem usage: 581,396 KB, elapsed time: 114.616 s, ts: 1542091700.472 s
14:48:20 396: Write Stat of tid 3, mem usage: 581,428 KB, elapsed time: 114.612 s, ts: 1542091700.473 s
14:48:20 396: Write Stat of tid 2, mem usage: 581,468 KB, elapsed time: 114.617 s, ts: 1542091700.476 s
14:48:20 396: Write Stat of tid 5, mem usage: 581,508 KB, elapsed time: 114.614 s, ts: 1542091700.478 s
``` | 54.403226 | 104 | 0.695894 | yue_Hant | 0.152543 |
53417716319f69a10427667d7eb9014e42570a92 | 9,640 | md | Markdown | docs/xamarin-forms/creating-mobile-apps-xamarin-forms/summaries/chapter25.md | mattcartwright/xamarin-docs | b448d629ee81ab411f04eb7e12f630c0997fa42f | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/xamarin-forms/creating-mobile-apps-xamarin-forms/summaries/chapter25.md | mattcartwright/xamarin-docs | b448d629ee81ab411f04eb7e12f630c0997fa42f | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/xamarin-forms/creating-mobile-apps-xamarin-forms/summaries/chapter25.md | mattcartwright/xamarin-docs | b448d629ee81ab411f04eb7e12f630c0997fa42f | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-07-18T03:40:46.000Z | 2020-07-18T03:40:46.000Z | ---
title: "Summary of Chapter 25. Page varieties"
description: "Creating Mobile Apps with Xamarin.Forms: Summary of Chapter 25. Page varieties"
ms.prod: xamarin
ms.technology: xamarin-forms
ms.assetid: D1D348F2-6A44-4781-ADCE-A0B7BB9AEF89
author: davidbritch
ms.author: dabritch
ms.date: 11/07/2017
---
# Summary of Chapter 25. Page varieties
So far you've seen two classes that derive from `Page`: `ContentPage` and `NavigationPage`. This chapter presents two others:
- [`MasterDetailPage`](xref:Xamarin.Forms.MasterDetailPage) manages two pages, a master and a detail
- [`TabbedPage`](xref:Xamarin.Forms.TabbedPage) manages multiple child pages accessed through tabs
These page types provide more sophisticated navigation options than the
`NavagationPage` discussed in [Chapter 24. Page Navigation](~/xamarin-forms/creating-mobile-apps-xamarin-forms/summaries/chapter24.md).
## Master and Detail
The [`MasterDetailPage`](xref:Xamarin.Forms.MasterDetailPage) defines two properties of type `Page`: [`Master`](xref:Xamarin.Forms.MasterDetailPage.Master) and [`Detail`](xref:Xamarin.Forms.MasterDetailPage.Detail). Generally you set each of these properties to a `ContentPage`. The `MasterDetailPage` displays and switches between these two pages.
There are two fundamental ways to switch between these two pages:
- *split* where the master and detail are side by side
- *popover* where the detail page covers or partially covers the master page
There are several variations of the *popover* approach (*slide*, *overlap*, and *swap*), but these are generally platform dependent. You can set the [`MasterDetailBehavior`](xref:Xamarin.Forms.MasterDetailPage.MasterBehavior) property of `MasterDetailPage` to a member of the [`MasterBehavior`](xref:Xamarin.Forms.MasterBehavior) enumeration:
- [`Default`](xref:Xamarin.Forms.MasterBehavior.Default)
- [`Split`](xref:Xamarin.Forms.MasterBehavior.Split)
- [`SplitOnLandscape`](xref:Xamarin.Forms.MasterBehavior.SplitOnLandscape)
- [`SplitOnPortrait`](xref:Xamarin.Forms.MasterBehavior.SplitOnPortrait)
- [`Popover`](xref:Xamarin.Forms.MasterBehavior.Popover)
However, this property has no effect on phones. Phones always have a popover behavior. Only tablets and desktop windows can have a split behavior.
### Exploring the Behaviors
The [**MasterDetailBehaviors**](https://github.com/xamarin/xamarin-forms-book-samples/tree/master/Chapter25/MasterDetailBehaviors) sample allows you to experiment with the default behavior on different devices. The program contains two separate `ContentPage` derivatives for the master and detail (with a `Title` property set on both), and another class that derives from `MasterDetailPage` that combines them. The detail page is enclosed in a `NavigationPage` because the UWP program wouldn't work without it.
The Windows 8.1 and Windows Phone 8.1 platforms require that a bitmap be set to the `Icon` property of the master page.
### Back to School
The
[**SchoolAndDetail**](https://github.com/xamarin/xamarin-forms-book-samples/tree/master/Chapter25/SchoolAndDetail) sample takes a somewhat different approach to constructing the program to display students from the [**SchoolOfFineArt**](https://github.com/xamarin/xamarin-forms-book-samples/tree/master/Libraries/SchoolOfFineArt) library.
The `Master` and `Detail` properties are defined with visual trees in the [SchoolAndDetailPage.xaml](https://github.com/xamarin/xamarin-forms-book-samples/blob/master/Chapter25/SchoolAndDetail/SchoolAndDetail/SchoolAndDetail/SchoolAndDetailPage.xaml) file, which derives from `MasterDetailPage`. This arrangement allows data bindings to be set between the master and detail pages.
That XAML file also sets the [`IsPresented`](xref:Xamarin.Forms.MasterDetailPage.IsPresented) property of `MasterDetailPage` to `True`. This causes the master page to be displayed at startup; by default the detail page is displayed. The [SchoolAndDetailPage.xaml.cs](https://github.com/xamarin/xamarin-forms-book-samples/blob/master/Chapter25/SchoolAndDetail/SchoolAndDetail/SchoolAndDetail/SchoolAndDetailPage.xaml.cs) file sets `IsPresented` to `false` when an item is selected from the `ListView` in the master page. The detail page is then displayed:
[](images/ch25fg09-large.png#lightbox "Detail Page from a MasterDetailPage")
### Your own user interface
Although Xamarin.Forms provides a user interface for switching between the master and detail views, you can supply your own. To do so:
- Set the [`IsGestureEnabled`](xref:Xamarin.Forms.MasterDetailPage.IsGestureEnabled) property to `false` to disable swiping
- Override the [`ShouldShowToolbarButton`](xref:Xamarin.Forms.MasterDetailPage.ShouldShowToolbarButton) method and return `false` to hide the toolbar buttons on Windows 8.1 and Windows Phone 8.1.
You must then provide a means to switch between the master and detail pages, such as demonstrated by the
[**ColorsDetail**](https://github.com/xamarin/xamarin-forms-book-samples/tree/master/Chapter25/ColorsDetails) sample.
The [**MasterDetailTaps**](https://github.com/xamarin/xamarin-forms-book-samples/tree/master/Chapter25/MasterDetailTaps) sample demonstrates another approach using a `TapGestureRecognizer` on the master and detail pages.
## TabbedPage
The [`TabbedPage`](xref:Xamarin.Forms.TabbedPage) is a collection of pages that you can switch among using tabs. It derives from `MultiPage<Page>` and defines no public properties or methods of its own. [`MultiPage<T>`](xref:Xamarin.Forms.MultiPage`1), however, does define a property:
- [`Children`](xref:Xamarin.Forms.MultiPage`1.Children) property of type `IList<T>`
You fill this `Children` collection with page objects.
Another approach allows you to define the `TabbedPage` children much like a `ListView` using these two properties that generate the tabbed pages automatically:
- [`ItemsSource`](xref:Xamarin.Forms.MultiPage`1.ItemsSource) of type `IEnumerable`
- [`ItemTemplate`](xref:Xamarin.Forms.MultiPage`1.ItemTemplate) of type `DataTemplate`
However, this approach does not work well on iOS when the collection contains more than a few items.
`MultiPage<T>` defines two more properties that let you keep track of which page is currently viewed:
- [`CurrentPage`](xref:Xamarin.Forms.MultiPage`1.CurrentPage) of type `T`, referring to the page
- [`SelectedItem`](xref:Xamarin.Forms.MultiPage`1.SelectedItem) of type `Object`, referring to the object in the `ItemsSource` collection
`MultiPage<T>` also defines two events:
- [`PagesChanged`](xref:Xamarin.Forms.MultiPage`1.PagesChanged) when the `ItemsSource` collection changes
- [`CurrentPageChanged`](xref:Xamarin.Forms.MultiPage`1.CurrentPageChanged) when the viewed page changes
### Discrete tab pages
The [**DiscreteTabbedColors**](https://github.com/xamarin/xamarin-forms-book-samples/tree/master/Chapter25/DiscreteTabbedColors) sample consists of three tabbed pages that display colors in three different ways. Each tab is a `ContentPage` derivative, and then the `TabbedPage` derivative [DiscreteTabbedColorsPage.xaml](https://github.com/xamarin/xamarin-forms-book-samples/blob/master/Chapter25/DiscreteTabbedColors/DiscreteTabbedColors/DiscreteTabbedColors/DiscreteTabbedColorsPage.xaml) combines the three pages.
For each page that appears in a `TabbedPage`, the `Title` property is required to specify the text in the tab, and the Apple Store requires that an icon be used as well, so the `Icon` property is set for iOS:
[](images/ch25fg13-large.png#lightbox "TabbedPage")
The [**StudentNotes**](https://github.com/xamarin/xamarin-forms-book-samples/tree/master/Chapter25/StudentNotes) sample has a home page that lists all the students. When a student is tapped, this navigates to a `TabbedPage` derivative, [`StudentNotesDataPage`](https://github.com/xamarin/xamarin-forms-book-samples/blob/master/Chapter25/StudentNotes/StudentNotes/StudentNotes/StudentNotesDataPage.xaml), that incorporates three `ContentPage` objects in its visual tree, one of which allows entering some notes for that student.
### Using an ItemTemplate
The [**MultiTabbedColor**](https://github.com/xamarin/xamarin-forms-book-samples/tree/master/Chapter25/MultiTabbedColors) sample uses the [`NamedColor`](https://github.com/xamarin/xamarin-forms-book-samples/blob/master/Libraries/Xamarin.FormsBook.Toolkit/Xamarin.FormsBook.Toolkit/NamedColor.cs) class in the [**Xamarin.FormsBook.Toolkit**](https://github.com/xamarin/xamarin-forms-book-samples/tree/master/Libraries/Xamarin.FormsBook.Toolkit) library. The [MultiTabbedColorsPage.xaml](https://github.com/xamarin/xamarin-forms-book-samples/blob/master/Chapter25/MultiTabbedColors/MultiTabbedColors/MultiTabbedColors/MultiTabbedColorsPage.xaml) file sets the `DataTemplate` property of `TabbedPage` to a visual tree beginning with `ContentPage` that contains bindings to properties of `NamedColor` (including a binding to the `Title` property).
However, this is problematic on iOS. Only a few of the items can be displayed, and there is no good way to give them icons.
## Related links
- [Chapter 25 full text (PDF)](https://download.xamarin.com/developer/xamarin-forms-book/XamarinFormsBook-Ch25-Apr2016.pdf)
- [Chapter 25 samples](https://github.com/xamarin/xamarin-forms-book-samples/tree/master/Chapter25)
- [Master-Detail Page](~/xamarin-forms/app-fundamentals/navigation/master-detail-page.md)
- [Tabbed Page](~/xamarin-forms/app-fundamentals/navigation/tabbed-page.md)
| 81.008403 | 843 | 0.799793 | eng_Latn | 0.865278 |
53418988be19eec79625bfb3460a0d475d67f97a | 1,611 | md | Markdown | articles/vmware-cloudsimple/cloudsimple-account.md | brentnewbury/azure-docs | 52da5a910db122fc92c877a6f62c54c32c7f3b31 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2019-08-27T01:30:49.000Z | 2019-08-27T01:30:49.000Z | articles/vmware-cloudsimple/cloudsimple-account.md | brentnewbury/azure-docs | 52da5a910db122fc92c877a6f62c54c32c7f3b31 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/vmware-cloudsimple/cloudsimple-account.md | brentnewbury/azure-docs | 52da5a910db122fc92c877a6f62c54c32c7f3b31 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2019-11-08T10:14:07.000Z | 2019-11-08T10:14:07.000Z | ---
title: CloudSimple account management - Azure
description: Learn about managing CloudSimple accounts
author: sharaths-cs
ms.author: dikamath
ms.date: 04/10/2019
ms.topic: article
ms.service: vmware
ms.reviewer: cynthn
manager: dikamath
---
# Account management overview
When you create your CloudSimple service, it creates an account on CloudSimple. The account is associated with your Azure subscription where the service is located. All users with **owner** and **contributor** roles in the subscription have access to the CloudSimple Portal. The Azure subscription ID and tenant ID associated with the CloudSimple service are found on the [Accounts page](https://docs.azure.cloudsimple.com/account/).
## Additional alert emails
You can configure email IDs in CloudSimple to receive alerts:
* Related to your service
* For automatic processing
## CloudSimple operator access
You can control access to the CloudSimple Portal for service operations personnel. Service operations personnel sign in to the portal when you submit a support ticket. Service operations will fix any problems reported and the actions taken are available in audit logs.
## Users
All users who have **owner** and **contributor** role in the subscription have access to the CloudSimple Portal. When you access the portal, the user is created on the CloudSimple account. You can disable access to the CloudSimple Portal for specific users from the Accounts page.
## Next steps
* [View account summary](https://docs.azure.cloudsimple.com/account/)
* [View user list](https://docs.azure.cloudsimple.com/users/) | 47.382353 | 436 | 0.785847 | eng_Latn | 0.984549 |
53424bed2779f5c9d73add2fffcc971a553f341e | 77 | md | Markdown | scripts/features/NNscore/README.md | sc8668/ml_pose_prediction | 14efc5e03a5cf35aa43dac624910393055c26f52 | [
"MIT"
] | 2 | 2021-10-20T06:07:16.000Z | 2022-02-23T02:25:45.000Z | scripts/features/NNscore/README.md | sc8668/ml_pose_prediction | 14efc5e03a5cf35aa43dac624910393055c26f52 | [
"MIT"
] | null | null | null | scripts/features/NNscore/README.md | sc8668/ml_pose_prediction | 14efc5e03a5cf35aa43dac624910393055c26f52 | [
"MIT"
] | 1 | 2021-12-15T08:30:39.000Z | 2021-12-15T08:30:39.000Z | #### the demo to calculate the features from NNscore.
see NNscore2.0_ref.sh
| 19.25 | 53 | 0.753247 | eng_Latn | 0.998523 |
5342884e591af82bb4d6d0bccdf6edbc5e872e39 | 67 | md | Markdown | HISTORY.md | paulradzkov-forks/docpad-plugin-opengraph | d68453d3566dd491963126c382a9b923f602ea73 | [
"MIT"
] | null | null | null | HISTORY.md | paulradzkov-forks/docpad-plugin-opengraph | d68453d3566dd491963126c382a9b923f602ea73 | [
"MIT"
] | null | null | null | HISTORY.md | paulradzkov-forks/docpad-plugin-opengraph | d68453d3566dd491963126c382a9b923f602ea73 | [
"MIT"
] | null | null | null | # History
- v2.0.0-alpha.1 January 19th, 2014
- Initial release
| 13.4 | 35 | 0.686567 | eng_Latn | 0.671316 |
5342bea801b8eb14d2a0234c442ee6650f48d45d | 1,940 | md | Markdown | data/issues/ZF-9725.md | zendframework/zf3-web | 5852ab5bfd47285e6b46f9e7b13250629b3e372e | [
"BSD-3-Clause"
] | 40 | 2016-06-23T17:52:49.000Z | 2021-03-27T20:02:40.000Z | data/issues/ZF-9725.md | zendframework/zf3-web | 5852ab5bfd47285e6b46f9e7b13250629b3e372e | [
"BSD-3-Clause"
] | 80 | 2016-06-24T13:39:11.000Z | 2019-08-08T06:37:19.000Z | data/issues/ZF-9725.md | zendframework/zf3-web | 5852ab5bfd47285e6b46f9e7b13250629b3e372e | [
"BSD-3-Clause"
] | 52 | 2016-06-24T22:21:49.000Z | 2022-02-24T18:14:03.000Z | ---
layout: issue
title: "Problem to load PDF File"
id: ZF-9725
---
ZF-9725: Problem to load PDF File
---------------------------------
Issue Type: Bug Created: 2010-04-21T06:38:54.000+0000 Last Updated: 2010-10-21T02:01:03.000+0000 Status: Resolved Fix version(s):
Reporter: ZEMZEMI (mimosa803) Assignee: Alexander Veremyev (alexander) Tags: - Zend\_Pdf
Related issues: - [ZF-9101](/issues/browse/ZF-9101)
Attachments: - [EDT\_INFO2-Sem2-22032010.pdf](/issues/secure/attachment/13027/EDT_INFO2-Sem2-22032010.pdf)
- [test2.pdf](/issues/secure/attachment/13026/test2.pdf)
### Description
Hi,
I'm using Zend\_pdf framework to retrieve metadata from pdf file. But I have an error when I try to load my file. In deed, I tested my program with two files but it doesn't work with all pdf I think.
This is my code and the error message is "Outline childs load error"
require\_once('C:\\xampp\\php\\PEAR\\Zend\\Pdf.php');
$pdfPath="test2.pdf";
$pdf = Zend_Pdf::load($pdfPath,1);
echo count($pdf->properties);
foreach ($pdf->properties as $cle=>$valeur) {
echo $cle.''.$valeur;
}
### Comments
Posted by Shaun Farrell (farrelley) on 2010-05-18T03:32:42.000+0000
I am unable to reproduce this issue.
$pdfPath= APPLICATION\_PATH . "/../public/EDT\_INFO2-Sem2-22032010.pdf"; $pdf = Zend\_Pdf::load($pdfPath, 1); echo "# of Props: " . count($pdf->properties) . "
"; foreach ($pdf->properties as $cle => $valeur) { echo $cle . ': ' . $valeur . "
"; }
Gives me the following data. (needs to be converted but I get data back)
of Props: 3
===========
Creator: þÿ�C�a�l�c Producer: þÿ�O�p�e�n�O�f�f�i�c�e�.�o�r�g� �2�.�4 CreationDate: D:20100322123632+01'00'
Posted by Shaun Farrell (farrelley) on 2010-05-20T03:56:51.000+0000
unable to reproduce this error.
| 28.115942 | 199 | 0.626289 | eng_Latn | 0.358055 |
5342d9710b6a279476cec44d3581ba71ad947b99 | 34 | md | Markdown | README.md | 99sbr/Predictive-Customer-Analytics | 15d6afa6da914657e676d21e3f5f42ea7f1b57ef | [
"MIT"
] | 3 | 2021-08-10T11:48:24.000Z | 2022-01-05T12:03:48.000Z | README.md | 99sbr/Predictive-Customer-Analytics | 15d6afa6da914657e676d21e3f5f42ea7f1b57ef | [
"MIT"
] | null | null | null | README.md | 99sbr/Predictive-Customer-Analytics | 15d6afa6da914657e676d21e3f5f42ea7f1b57ef | [
"MIT"
] | 1 | 2022-01-23T22:06:11.000Z | 2022-01-23T22:06:11.000Z | # Predictive-Customer-Analytics
| 11.333333 | 31 | 0.794118 | deu_Latn | 0.295697 |
534333a72baeff0423a159badd788b15e6ad511a | 2,465 | md | Markdown | docs/integrations/sources/mixpanel.md | Dwellers/airbyte | fb902dcc2e6584891a8b4c3e0f8526847ec6a9c1 | [
"MIT"
] | 2 | 2021-08-04T03:17:38.000Z | 2021-11-15T10:16:08.000Z | docs/integrations/sources/mixpanel.md | Dwellers/airbyte | fb902dcc2e6584891a8b4c3e0f8526847ec6a9c1 | [
"MIT"
] | 52 | 2021-06-11T12:39:05.000Z | 2022-03-30T04:59:35.000Z | docs/integrations/sources/mixpanel.md | Dwellers/airbyte | fb902dcc2e6584891a8b4c3e0f8526847ec6a9c1 | [
"MIT"
] | 1 | 2021-08-04T03:25:02.000Z | 2021-08-04T03:25:02.000Z | # Mixpanel
## Overview
The Mixpanel source supports both Full Refresh and Incremental syncs. You can choose if this connector will copy only the new or updated data, or all rows in the tables and columns you set up for replication, every time a sync is run.
This Source Connector is based on a [Airbyte CDK](https://docs.airbyte.io/contributing-to-airbyte/python).
### Output schema
Several output streams are available from this source:
* [Export](https://developer.mixpanel.com/docs/exporting-raw-data#section-export-api-reference) \(Incremental\)
* [Engage](https://developer.mixpanel.com/docs/data-export-api#section-engage) \(Full table\)
* [Funnels](https://developer.mixpanel.com/docs/data-export-api#section-funnels) \(Incremental\)
* [Revenue](https://developer.mixpanel.com/docs/data-export-api#section-hr-span-style-font-family-courier-revenue-span) \(Incremental\)
* [Annotations](https://developer.mixpanel.com/docs/data-export-api#section-annotations) \(Full table\)
* [Cohorts](https://developer.mixpanel.com/docs/cohorts#section-list-cohorts) \(Full table\)
* [Cohort Members](https://developer.mixpanel.com/docs/data-export-api#section-engage) \(Full table\)
If there are more endpoints you'd like Airbyte to support, please [create an issue.](https://github.com/airbytehq/airbyte/issues/new/choose)
### Features
| Feature | Supported? |
| :--- | :--- |
| Full Refresh Sync | Yes |
| Incremental - Append Sync | Yes |
| Replicate Incremental Deletes | Coming soon |
| SSL connection | Yes |
| Namespaces | No |
Please note, that incremental sync could return duplicated (old records) for the state date due to API filter limitation, which is granular to the whole day only.
### Performance considerations
The Mixpanel connector should not run into Mixpanel API limitations under normal usage. Please [create an issue](https://github.com/airbytehq/airbyte/issues) if you see any rate limit issues that are not automatically retried successfully.
* Export stream - 60 reqs per hour
* All streams - 400 reqs per hour
## Getting started
### Requirements
* Mixpanel API Secret
### Setup guide
Please read [Find API Secret](https://help.mixpanel.com/hc/en-us/articles/115004502806-Find-Project-Token-).
## CHANGELOG
| Version | Date | Pull Request | Subject |
| :------ | :-------- | :----- | :------ |
| `0.1.0` | 2021-07-06 | [3698](https://github.com/airbytehq/airbyte/issues/3698) | created CDK native mixpanel connector |
| 43.245614 | 239 | 0.737525 | eng_Latn | 0.822866 |
534438552a62680c6698fd2c41a8b8ea364bc12d | 1,264 | markdown | Markdown | _posts/2009-3-22-barcamp-antwerpen-bca.markdown | atog/atog.github.com | 636eaf8fc398187fd97ed0f3078725178583211b | [
"MIT"
] | 1 | 2016-05-09T06:57:41.000Z | 2016-05-09T06:57:41.000Z | _posts/2009-3-22-barcamp-antwerpen-bca.markdown | atog/atog.github.com | 636eaf8fc398187fd97ed0f3078725178583211b | [
"MIT"
] | null | null | null | _posts/2009-3-22-barcamp-antwerpen-bca.markdown | atog/atog.github.com | 636eaf8fc398187fd97ed0f3078725178583211b | [
"MIT"
] | null | null | null | ---
layout: post
title: Barcamp Antwerpen #bca
---
Gisteren vond de allereerste [Barcamp Antwerpen](http://www.barcampantwerpen.org/) plaats, in euh, [Berchem, Antwerpen](http://www.almpoint.be/index.html). [Wiki hier](http://barcampantwerpen.pbwiki.com/).
Het was mijn 4de barcamp maar de eerste waar ik zelf niets gepresenteerd heb. _Shame on me_. Het was dan volgens mij ook wel de *beste* barcamp ooit. [Eindelijk eens van die parking af](http://www.facebook.com/group.php?gid=32344007255) ;)
Veel nieuwe mensen. Veel geïnteresseerde mensen. Veel interessante mensen. Mooi weer, daar hebben we toch nog van kunnen genieten door een terraske maar bovenal vond ik dat het er vol met _gemotiveerde mensen_ rondliep. Dat is bewezen door de actieve feedback sessie op het laatste. Op naar de volgende!
Het enige minpuntje was de koffie: [Nespresso](http://www.nespresso.com/), die was veel te goed. Nu moet ik me ook zo'n machine aanschaffen. Het _moet_ gewoon.
Ook een dikke merci aan [nucleus](http://nucleus.be/), [the parkinklot](http://theparkinglot.be/), [Devia](http://www.devia.be/), [Chocolateque](http://www.chocolateque.com/) en natuurlijk niet te vergeten [Topanga](http://twitter.com/topanga) aka [Anne Verberckmoes](http://www.tenderfeelings.be/). | 97.230769 | 303 | 0.763449 | nld_Latn | 0.997742 |
534442472ab5ba62908449b34b16f523dd4bd2da | 16,585 | md | Markdown | ce/customerengagement/on-premises/customize/sub-grid-properties-legacy.md | eddybreezy/dynamics-365-customer-engagement | d4186cb92cc23a532d225d9dbf6a187601fb322b | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ce/customerengagement/on-premises/customize/sub-grid-properties-legacy.md | eddybreezy/dynamics-365-customer-engagement | d4186cb92cc23a532d225d9dbf6a187601fb322b | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ce/customerengagement/on-premises/customize/sub-grid-properties-legacy.md | eddybreezy/dynamics-365-customer-engagement | d4186cb92cc23a532d225d9dbf6a187601fb322b | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Sub-Grid properties for main forms | MicrosoftDocs
description: Understand the Sub-Grid properties for main forms
Keywords: Main form; Sub-Grid properties; Dynamics 365 for Customer Engagement
author: Mattp123
applies_to:
- Dynamics 365 for Customer Engagement (online)
- powerapps
ms.author: matp
manager: kvivek
ms.date: 01/09/2019
ms.service: crm-online
ms.topic: article
ms.assetid: 82892cd3-3436-4677-b96b-f2ccd0a4f078
search.audienceType:
- customizer
---
# Sub-Grid properties overview
You can configure a sub-grid on a form to display a list of records or a chart. Select **Show Chart Only** on the **Display** tab to show a chart instead of a list.
You can access **Sub-Grid properties** in solution explorer. Under **Components**, expand **Entities**, expand the entity you want, and then select **Forms**. In the list of forms, open the form of type **Main**. Then on the **Insert** tab, select **Sub-Grid** to view sub-grid properties.
| Tab | Property | Description |
|----------------|-------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| **Display** | **Name** | **Required**: The unique name for the sub-grid that is used when referencing it in scripts. The name can contain only alphanumeric characters and underscores. |
| | **Label** | **Required**: The localizable label for the sub-grid visible to users. |
| | **Display label on the Form** | Whether the label should be displayed on the form. This is required if you enable **Display Search Box**. You can also choose to have the panel header color. |
| | **Records** | Choose from two options:<br /><br /> - **Only Related Records**: Sub-grid will display only records related to the current record.<br />- **All Record Types**: Sub-grid will display records filtered only by the default view or, if the view selector is enabled, any views the user chooses.<br /><br /> The option you choose will affect the behavior of the show list control. [!INCLUDE[proc_more_information](../includes/proc-more-information.md)] [Show list behavior](#show-list-behavior) |
| | **Entity** | Depending on the option you choose for **Records**, this list displays either:<br /><br /> - **Only Related Records**: A list of entities that are related to this entity with the name of the lookup field on that entity which defines the relationship in parentheses.<br />- **All Record Types**: A list of all entities. |
| | **Default View** | Choose the view that will be applied by default. If you do not enable any other views using the **View Selector** property. This will be the only view.<br /><br /> Use the **Edit** button to open the default view for editing. Use the **New** button to create a new view to use for this sub-grid. |
| | **Display Search Box** | Display the search box. When this option is chosen the **Display Label on the Form** option is required. |
| | **Display Index** | Only forms using the [Classic forms](main-form-presentations.md#classic-forms) support display index.<br /><br /> Select this check box if you want the alphabetical index to be available with the list. This lets you jump to records starting with a particular letter or number. |
| | **View Selector** | You have three options:<br /><br /> - **Off**: Only the default view can be used.<br />- **Show All Views**: Allow people to choose any view.<br />- **Show Selected Views**: Use the Ctrl key with your cursor to select which of the available views to show. |
| | **Default Chart** | Select which chart to show if **Show Chart Only** is selected. |
| | **Show Chart Only** | Rather than a list of records a chart will be displayed. |
| | **Display Chart Selection** | If **Show Chart Only** is selected, allow people to choose different charts. |
| | **Availability** | Specify whether the section should be available on phone. |
| **Formatting** | **Layout** | **Select the number of columns the control occupies**.<br /><br /> When the section containing the sub-grid has more than one column you can set the field to occupy up to the number of columns that the section has. |
| | **Row Layout** | **Number of Rows** will determine how many records are shown on a page of a sub-grid.<br /><br /> If **Automatically expand to use available space** is chosen the form will allow space for two records and will expand the space as the number of records increases. If the number exceeds the **Number of Rows**, people can navigate to additional pages to view the records.<br /><br /> If **Automatically expand to use available space** is not chosen the form will provide space for the number of records defined by **Number of Rows** and people can navigate to additional pages to view any additional records. |
| **Controls** | **Controls** | Choose to add controls and select the radio button to have them for Web, Phone or Tablet. |
In forms using the [Classic forms](main-form-presentations.md#classic-forms), actions performed on a sub-grid were available in the ribbon. Developers can customize the behavior of these actions or add additional actions by customizing the ribbon.
In forms using the [Updated forms](main-form-presentations.md#updated-forms) actions for sub-grids are placed near the sub-grid, making them easier to access. However the command bar does not allow for custom actions to be added. Developers can edit the ribbon to modify the actions for the remaining three actions: show list, add record, and delete record.
## Show list behavior
When displaying a list in forms with the [Updated forms](main-form-presentations.md#updated-forms), each sub-grid displays the **Open View** button  in the top right corner when the entity is also displayed as one of the entities included in the navigation area of the form editor. Choosing this button will open the view. The behavior will change depending on the option chosen for the **Records** property.
When you select **Only Related Records** the view will open using one of the associated views in the same window. To return to the form, use the back button or choose the current record primary name value in the navigation bar.
When you select **All Record Types** the view will open in a new window.
## Add record behavior
When displaying a list in forms with the [Updated forms](main-form-presentations.md#updated-forms), each sub-grid displays the **Add record** button  in the top right side of the sub-grid. Choosing this button will allow you to add a record. This behavior will change depending on the option chosen for the **Records** property and if the lookup is for activity records.
When you select **Only Related Records** the default behavior is the behavior to add existing records. People see an in-line lookup to search for an existing record first. This helps prevent creating duplicate records. If they can’t find an existing record, they can choose the **New** option. When a new record is created any of the field mappings defined in the relationship will be applied. [!INCLUDE[proc_more_information](../includes/proc-more-information.md)] [Map entity fields](map-entity-fields.md)
When you select **All Record Types** the default behavior is to add a new record. The quick create form will be shown if the target entity has one. If not, the default entity main form is shown.
If the sub-grid displays activities, people will first need to choose the type of activity and then they will see the “add new record” behavior.
## Delete record behavior
When you select a record in a sub-grid the **Delete** button  appears on the right side of the row. The behavior of this delete action is different depending on the type of relationship with the current entity.
When the sub-grid uses a 1:N (one-to-many) relationship, the normal record delete behavior is to show a confirmation dialog before deleting the record.
When the sub-grid uses a N:N (many-to-many) relationship, the record in the relationship (or intersect) entity relating to two records is deleted without a confirmation and the record will no longer be displayed in the sub-grid. But the record that was displayed is not deleted.
## See also
[Use the Main form and its components](../customize/use-main-form-and-components.md)
[!INCLUDE[footer-include](../../../includes/footer-banner.md)] | 202.256098 | 659 | 0.384383 | eng_Latn | 0.996479 |
53447750f98dcc37e0f421bdc0998b4dafdddca9 | 28,472 | md | Markdown | articles/app-service/configure-custom-container.md | Tanksta/azure-docs.de-de | 3fade99b63ec5fb175e7b72d9f49c28a25a183cc | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/app-service/configure-custom-container.md | Tanksta/azure-docs.de-de | 3fade99b63ec5fb175e7b72d9f49c28a25a183cc | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/app-service/configure-custom-container.md | Tanksta/azure-docs.de-de | 3fade99b63ec5fb175e7b72d9f49c28a25a183cc | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Konfigurieren eines benutzerdefinierten Containers
description: Erfahren Sie, wie Sie einen benutzerdefinierten Container in Azure App Service konfigurieren. In diesem Artikel werden die gängigsten Konfigurationsaufgaben vorgestellt.
ms.topic: article
ms.date: 02/23/2021
ms.custom: devx-track-azurepowershell
zone_pivot_groups: app-service-containers-windows-linux
ms.openlocfilehash: 48d2eeec1bdb1b9b4a393b4116092f043716077c
ms.sourcegitcommit: 3c460886f53a84ae104d8a09d94acb3444a23cdc
ms.translationtype: HT
ms.contentlocale: de-DE
ms.lasthandoff: 04/21/2021
ms.locfileid: "107832031"
---
# <a name="configure-a-custom-container-for-azure-app-service"></a>Konfigurieren eines benutzerdefinierten Containers für Azure App Service
In diesem Artikel erfahren Sie, wie Sie einen benutzerdefinierten Container für die Ausführung unter Azure App Service konfigurieren.
::: zone pivot="container-windows"
Dieser Leitfaden enthält die wichtigsten Konzepte und Anweisungen für die Containerstellung von Windows-Apps in App Service. Wenn Sie Azure App Service noch nie verwendet haben, befolgen Sie zunächst den [Schnellstart zu benutzerdefinierten Containern](quickstart-custom-container.md) und das [Tutorial](tutorial-custom-container.md).
::: zone-end
::: zone pivot="container-linux"
Dieser Leitfaden enthält die wichtigsten Konzepte und Anweisungen für die Containerstellung von Linux-Apps in App Service. Wenn Sie Azure App Service noch nie verwendet haben, befolgen Sie zunächst den [Schnellstart zu benutzerdefinierten Containern](quickstart-custom-container.md) und das [Tutorial](tutorial-custom-container.md). Es gibt auch eine Schnellstartanleitung für [Apps mit mehreren Containern](quickstart-multi-container.md) und ein [Tutorial](tutorial-multi-container-app.md).
::: zone-end
::: zone pivot="container-windows"
## <a name="supported-parent-images"></a>Unterstützte übergeordnete Images
Für Ihr benutzerdefiniertes Windows-Image müssen Sie das passende [übergeordnete Image (Basisimage)](https://docs.docker.com/develop/develop-images/baseimages/) für das gewünschte Framework auswählen:
- Verwenden Sie zum Bereitstellen von .NET Framework-Apps ein übergeordnetes Image, das auf dem [LTSC](/windows-server/get-started-19/servicing-channels-19#long-term-servicing-channel-ltsc)-Release (Long-Term Servicing Channel, langfristiger Wartungskanal) von Windows Server Core basiert.
- Verwenden Sie zum Bereitstellen von .NET Core-Apps ein übergeordnetes Image, das auf dem Release [Semi-Annual Servicing Channel (SAC)](/windows-server/get-started-19/servicing-channels-19#semi-annual-channel) von Windows Server Nano basiert.
Während des App-Starts dauert das Herunterladen eines übergeordneten Images eine Weile. Sie können die Startzeit jedoch reduzieren, indem Sie eins der folgenden übergeordneten Images verwenden, die bereits in Azure App Service zwischengespeichert sind:
- [mcr.microsoft.com/windows/servercore](https://hub.docker.com/_/microsoft-windows-servercore):2004
- [mcr.microsoft.com/windows/servercore](https://hub.docker.com/_/microsoft-windows-servercore):ltsc2019
- [mcr.microsoft.com/dotnet/framework/aspnet](https://hub.docker.com/_/microsoft-dotnet-framework-aspnet/):4.8-windowsservercore-2004
- [mcr.microsoft.com/dotnet/framework/aspnet](https://hub.docker.com/_/microsoft-dotnet-framework-aspnet/):4.8-windowsservercore-ltsc2019
- [mcr.microsoft.com/dotnet/core/runtime](https://hub.docker.com/_/microsoft-dotnet-core-runtime/):3.1-nanoserver-2004
- [mcr.microsoft.com/dotnet/core/runtime](https://hub.docker.com/_/microsoft-dotnet-core-runtime/):3.1-nanoserver-1909
- [mcr.microsoft.com/dotnet/core/runtime](https://hub.docker.com/_/microsoft-dotnet-core-runtime/):3.1-nanoserver-1903
- [mcr.microsoft.com/dotnet/core/runtime](https://hub.docker.com/_/microsoft-dotnet-core-runtime/):3.1-nanoserver-1809
- [mcr.microsoft.com/dotnet/core/aspnet](https://hub.docker.com/_/microsoft-dotnet-core-aspnet/):3.1-nanoserver-2004
- [mcr.microsoft.com/dotnet/core/aspnet](https://hub.docker.com/_/microsoft-dotnet-core-aspnet/):3.1-nanoserver-1909
- [mcr.microsoft.com/dotnet/core/aspnet](https://hub.docker.com/_/microsoft-dotnet-core-aspnet/):3.1-nanoserver-1903
- [mcr.microsoft.com/dotnet/core/aspnet](https://hub.docker.com/_/microsoft-dotnet-core-aspnet/):3.1-nanoserver-1809
::: zone-end
## <a name="change-the-docker-image-of-a-custom-container"></a>Ändern des Docker-Images eines benutzerdefinierten Containers
Wenn Sie eine vorhandene benutzerdefinierte Container-App vom aktuellen Docker-Image auf ein neues Image umstellen möchten, verwenden Sie den folgenden Befehl:
```azurecli-interactive
az webapp config container set --name <app-name> --resource-group <group-name> --docker-custom-image-name <docker-hub-repo>/<image>
```
## <a name="use-an-image-from-a-private-registry"></a>Verwenden eines Images aus einer privaten Registrierung
Führen Sie den folgenden Befehl aus, um ein Image aus einer privaten Registrierung wie Azure Container Registry zu verwenden:
```azurecli-interactive
az webapp config container set --name <app-name> --resource-group <group-name> --docker-custom-image-name <image-name> --docker-registry-server-url <private-repo-url> --docker-registry-server-user <username> --docker-registry-server-password <password>
```
Geben Sie für *\<username>* und *\<password>* die Anmeldeinformationen für das Konto Ihrer privaten Registrierung an.
## <a name="i-dont-see-the-updated-container"></a>Ich kann den aktualisierten Container nicht sehen
Wenn Sie Ihre Docker-Containereinstellungen so ändern, dass sie auf einen neuen Container verweisen, kann es ein paar Minuten dauern, bis die App HTTP-Anforderungen aus dem neuen Container verarbeitet. Während der neue Container abgerufen und gestartet wird, bedient App Service weiterhin Anforderungen aus dem alten Container. Nur wenn der neue Container gestartet wird und zum Empfangen von Anforderungen bereit ist, beginnt App Service mit dem Senden von Anforderungen an ihn.
## <a name="how-container-images-are-stored"></a>Speichern von Containerimages
Wenn Sie ein benutzerdefiniertes Docker-Image zum ersten Mal in App Service ausführen, führt App Service ein `docker pull` aus und ruft alle Imageebenen ab. Diese Ebenen werden auf dem Datenträger gespeichert, so als ob Sie Docker lokal verwendeten. Bei jedem Neustart der App führt App Service ein `docker pull` aus, ruft aber nur Schichten ab, die sich geändert haben. Wenn keine Änderungen vorliegen, verwendet App Service vorhandene Ebenen auf dem lokalen Datenträger.
Wenn die App Compute-Instanzen aus irgendeinem Grund ändert (z. B. durch zentrales Hoch- oder Herunterskalieren der Tarife), muss App Service alle Ebenen erneut abrufen. Dasselbe trifft zu, wenn Sie eine Aufskalierung durchführen, um zusätzliche Instanzen hinzuzufügen. Es gibt auch seltene Fälle, in denen sich App-Instanzen ohne einen Skalierungsvorgang ändern können.
## <a name="configure-port-number"></a>Konfigurieren der Portnummer
App Service geht standardmäßig davon aus, dass der benutzerdefinierte Container an Port 80 lauscht. Wenn Ihr Container an einem anderen Port lauscht, legen Sie die App-Einstellung `WEBSITES_PORT` in Ihrer App Service-App fest. Sie können sie über die [Cloud Shell](https://shell.azure.com) festlegen. In Bash:
```azurecli-interactive
az webapp config appsettings set --resource-group <group-name> --name <app-name> --settings WEBSITES_PORT=8000
```
PowerShell:
```azurepowershell-interactive
Set-AzWebApp -ResourceGroupName <group-name> -Name <app-name> -AppSettings @{"WEBSITES_PORT"="8000"}
```
App Service ermöglicht es Ihrem Container zurzeit, nur einen Port für HTTP-Anforderungen verfügbar zu machen.
## <a name="configure-environment-variables"></a>Konfigurieren von Umgebungsvariablen
Ihr benutzerdefinierter Container kann Umgebungsvariablen verwenden, die extern bereitgestellt werden müssen. Sie können sie über die [Cloud Shell](https://shell.azure.com) übergeben. In Bash:
```azurecli-interactive
az webapp config appsettings set --resource-group <group-name> --name <app-name> --settings DB_HOST="myownserver.mysql.database.azure.com"
```
PowerShell:
```azurepowershell-interactive
Set-AzWebApp -ResourceGroupName <group-name> -Name <app-name> -AppSettings @{"DB_HOST"="myownserver.mysql.database.azure.com"}
```
Wenn Ihre App ausgeführt wird, werden die Einstellungen der App Service-App automatisch als Umgebungsvariablen in den Prozess eingefügt. Sie können Containerumgebungsvariablen mit der URL `https://<app-name>.scm.azurewebsites.net/Env)` überprüfen.
Wenn Ihre App Images aus einer privaten Registrierung oder von Docker Hub verwendet, werden die Anmeldeinformationen für den Zugriff auf das Repository in den Umgebungsvariablen `DOCKER_REGISTRY_SERVER_URL`, `DOCKER_REGISTRY_SERVER_USERNAME` und `DOCKER_REGISTRY_SERVER_PASSWORD` gespeichert. Aufgrund von Sicherheitsrisiken wird keiner dieser reservierten Variablennamen in der Anwendung verfügbar gemacht.
::: zone pivot="container-windows"
Für Container, die auf IIS oder .NET Framework (4.0 oder höher) basieren, werden sie von App Service automatisch als .NET-App-Einstellungen und -Verbindungszeichenfolgen in `System.ConfigurationManager` eingefügt. Für alle anderen Sprachen oder Frameworks werden sie als Umgebungsvariablen für den Prozess bereitgestellt, wobei eines der folgenden entsprechenden Präfixe verwendet wird:
- `APPSETTING_`
- `SQLCONTR_`
- `MYSQLCONTR_`
- `SQLAZURECOSTR_`
- `POSTGRESQLCONTR_`
- `CUSTOMCONNSTR_`
::: zone-end
::: zone pivot="container-linux"
Diese Methode funktioniert sowohl für Apps mit einem einzelnen Container als auch für Apps mit mehreren Containern, wobei die Umgebungsvariablen in der Datei *docker-compose.yml* angegeben sind.
::: zone-end
## <a name="use-persistent-shared-storage"></a>Verwenden von beständig freigegebenem Speicher
::: zone pivot="container-windows"
Sie können das Verzeichnis *C:\home* im Dateisystem Ihrer App verwenden, damit Dateien auch nach einem Neustart erhalten bleiben und instanzübergreifend freigegeben werden können. Das `C:\home` wird in Ihrer App bereitgestellt, damit Ihre Container-App auf den beständigen Speicher zugreifen kann.
Wenn der beständige Speicher deaktiviert ist, bleiben Schreibvorgänge in das Verzeichnis `C:\home` nicht erhalten. [Docker-Hostprotokolle und -Containerprotokolle](#access-diagnostic-logs) werden in einem standardmäßigen permanenten freigegebenen Speicher gespeichert, der nicht an den Container angefügt ist. Wenn der beständige Speicher aktiviert ist, bleiben alle Schreibvorgänge in das Verzeichnis `C:\home` erhalten, alle Instanzen einer horizontal skalierten App können darauf zugreifen, und das Protokoll ist unter `C:\home\LogFiles` verfügbar.
::: zone-end
::: zone pivot="container-linux"
Sie können das Verzeichnis */home* im Dateisystem Ihrer App verwenden, damit Dateien auch nach einem Neustart erhalten bleiben und instanzübergreifend freigegeben werden können. Das `/home` wird in Ihrer App bereitgestellt, damit Ihre Container-App auf den beständigen Speicher zugreifen kann.
Wenn der beständige Speicher deaktiviert ist, bleiben Schreibvorgänge in das Verzeichnis `/home` nicht über App-Neustarts oder mehrere Instanzen hinweg erhalten. Die einzige Ausnahme ist das Verzeichnis `/home/LogFiles`, das zum Speichern der Docker- und Containerprotokolle verwendet wird. Wenn der beständige Speicher aktiviert ist, bleiben alle Schreibvorgänge in das Verzeichnis `/home` erhalten und können von allen Instanzen einer horizontal skalierten App aufgerufen werden.
::: zone-end
Standardmäßig ist der beständige Speicher deaktiviert, und die Einstellung wird in den App-Einstellungen nicht verfügbar gemacht. Um ihn zu aktivieren, legen Sie die App-Einstellung `WEBSITES_ENABLE_APP_SERVICE_STORAGE` über die [Cloud Shell](https://shell.azure.com) fest. In Bash:
```azurecli-interactive
az webapp config appsettings set --resource-group <group-name> --name <app-name> --settings WEBSITES_ENABLE_APP_SERVICE_STORAGE=true
```
PowerShell:
```azurepowershell-interactive
Set-AzWebApp -ResourceGroupName <group-name> -Name <app-name> -AppSettings @{"WEBSITES_ENABLE_APP_SERVICE_STORAGE"=true}
```
> [!NOTE]
> Sie können auch [Ihren eigenen beständigen Speicher konfigurieren](configure-connect-to-azure-storage.md).
## <a name="detect-https-session"></a>Erkennen einer HTTPS-Sitzung
App Service beendet TLS/SSL auf den Front-Ends. Dies bedeutet, dass TLS/SSL-Anforderungen nie bis zu Ihrer App gelangen. Sie müssen und sollten keine Unterstützung für TLS/SSL in Ihrer App implementieren.
Die Front-Ends befinden sich in Azure-Rechenzentren. Wenn Sie TLS/SSL mit ihrer App verwenden, wird Ihr Datenverkehr über das Internet immer sicher verschlüsselt.
::: zone pivot="container-windows"
## <a name="customize-aspnet-machine-key-injection"></a>Anpassen des Einfügens des ASP.NET-Computerschlüssels
Während des Containerstarts werden automatisch generierte Schlüssel als Computerschlüssel für ASP.NET-Kryptografieroutinen in den Container eingefügt. Sie können [diese Schlüssel in Ihrem Container finden](#connect-to-the-container), indem Sie nach den folgenden Umgebungsvariablen suchen: `MACHINEKEY_Decryption`, `MACHINEKEY_DecryptionKey`, `MACHINEKEY_ValidationKey`, `MACHINEKEY_Validation`.
Die neuen Schlüssel können bei jedem Neustart die ASP.NET-Formularauthentifizierung und den Ansichtszustand zurücksetzen, wenn Ihre App von ihnen abhängig ist. Um die automatische Neugenerierung von Schlüsseln zu verhindern, [legen Sie sie manuell als App Service-App-Einstellungen](#configure-environment-variables) fest.
## <a name="connect-to-the-container"></a>Herstellen einer Verbindung mit dem Container
Sie können eine direkte Verbindung mit Ihrem Windows-Container für Diagnoseaufgaben herstellen, indem Sie zu `https://<app-name>.scm.azurewebsites.net/DebugConsole` navigieren. Funktionsweise:
- Mit der Debugkonsole können Sie interaktive Befehle ausführen, z. B. das Starten von PowerShell-Sitzungen, das Untersuchen von Registrierungsschlüsseln und das Navigieren im gesamten Containerdateisystem.
- Sie funktioniert gesondert vom darüber angesiedelten grafischen Browser, in dem nur die Dateien in Ihrem [freigegebenen Speicher](#use-persistent-shared-storage) angezeigt werden.
- In einer horizontal skalierten App ist die Debugkonsole mit einer der Containerinstanzen verbunden. Sie können eine andere Instanz aus dem Dropdown **Instanz** im obersten Menü auswählen.
- Jede Änderung, die Sie an dem Container innerhalb der Konsole vornehmen, bleibt *nicht* erhalten, wenn Ihre App neu gestartet wird (mit Ausnahme von Änderungen im freigegebenen Speicher), weil sie nicht Teil des Docker-Images ist. Um Ihre Änderungen beizubehalten, wie z. B. Registrierungseinstellungen und Softwareinstallation, machen Sie sie zu einem Teil der Dockerfile-Datei.
## <a name="access-diagnostic-logs"></a>Zugreifen auf Diagnoseprotokolle
App Service protokolliert Aktionen des Docker-Hosts sowie aus dem Container stammende Aktivitäten. Protokolle vom Docker-Host (Plattformprotokolle) werden standardmäßig ausgeliefert, aber Anwendungsprotokolle oder Webserverprotokolle aus dem Container müssen manuell aktiviert werden. Weitere Informationen finden Sie unter [Aktivieren der Diagnoseprotokollierung](troubleshoot-diagnostic-logs.md#enable-application-logging-linuxcontainer) und [Aktivieren der Webserverprotokollierung](troubleshoot-diagnostic-logs.md#enable-web-server-logging).
Es gibt verschiedene Möglichkeiten, um auf Docker-Protokolle zuzugreifen:
- [Im Azure-Portal](#in-azure-portal)
- [In der Kudu-Konsole](#from-the-kudu-console)
- [Mit der Kudu-API](#with-the-kudu-api)
- [Senden von Protokollen an Azure Monitor](troubleshoot-diagnostic-logs.md#send-logs-to-azure-monitor-preview)
### <a name="in-azure-portal"></a>Im Azure-Portal
Docker-Protokolle werden im Portal auf der Seite **Containereinstellungen** Ihrer App angezeigt. Die Protokolle werden abgeschnitten, aber Sie können alle Protokolle herunterladen, indem Sie auf **Herunterladen** klicken.
### <a name="from-the-kudu-console"></a>In der Kudu-Konsole
Navigieren Sie zu `https://<app-name>.scm.azurewebsites.net/DebugConsole`, und klicken Sie auf den Ordner **LogFiles**, um die einzelnen Protokolldateien anzuzeigen. Um das gesamte Verzeichnis **LogFiles** herunterzuladen, klicken Sie auf das Symbol **Herunterladen** links neben dem Verzeichnisnamen. Sie können auch über einen FTP-Client auf diesen Ordner zugreifen.
Im Konsolenterminal können Sie nicht standardmäßig auf den Ordner `C:\home\LogFiles` zugreifen, da der persistente freigegebene Speicher nicht aktiviert ist. Um dieses Verhalten im Konsolenterminal zu aktivieren, [aktivieren Sie den persistenten freigegebenen Speicher](#use-persistent-shared-storage).
Wenn Sie versuchen, das Docker-Protokoll, das zurzeit verwendet wird, mithilfe eines FTP-Clients herunterzuladen, erhalten Sie möglicherweise einen Fehler aufgrund einer Dateisperre.
### <a name="with-the-kudu-api"></a>Mit der Kudu-API
Navigieren Sie direkt zu `https://<app-name>.scm.azurewebsites.net/api/logs/docker`, um die Metadaten für die Docker-Protokolle anzuzeigen. Möglicherweise wird mehr als eine Protokolldatei aufgelistet, und mithilfe der `href`-Eigenschaft können Sie die Protokolldatei direkt herunterladen.
Um alle Protokolle zusammen in einer ZIP-Datei herunterzuladen, greifen Sie auf `https://<app-name>.scm.azurewebsites.net/api/logs/docker/zip` zu.
## <a name="customize-container-memory"></a>Anpassen des Containerarbeitsspeichers
Standardmäßig sind alle in Azure App Service bereitgestellten Windows-Container auf 1 GB RAM beschränkt. Sie können diesen Wert ändern, indem Sie die App-Einstellung `WEBSITE_MEMORY_LIMIT_MB` über die [Cloud Shell](https://shell.azure.com) bereitstellen. In Bash:
```azurecli-interactive
az webapp config appsettings set --resource-group <group-name> --name <app-name> --settings WEBSITE_MEMORY_LIMIT_MB=2000
```
PowerShell:
```azurepowershell-interactive
Set-AzWebApp -ResourceGroupName <group-name> -Name <app-name> -AppSettings @{"WEBSITE_MEMORY_LIMIT_MB"=2000}
```
Der Wert wird in MB definiert und muss kleiner oder gleich dem gesamten physischen Arbeitsspeicher des Hosts sein. Beispielsweise darf in einem App Service-Plan mit 8 GB RAM der kumulative Gesamtwert von `WEBSITE_MEMORY_LIMIT_MB` für alle Apps 8 GB nicht überschreiten. Informationen dazu, wie viel Arbeitsspeicher für den jeweiligen Tarif verfügbar ist, finden Sie unter [App Service-Preise](https://azure.microsoft.com/pricing/details/app-service/windows/) im Abschnitt **Windows Container Premium-Tarif**.
## <a name="customize-the-number-of-compute-cores"></a>Anpassen der Anzahl der Compute-Kerne
Standardmäßig wird ein Windows-Container mit allen verfügbaren Kernen für Ihren ausgewählten Tarif ausgeführt. Sie können z. B. die Anzahl der Kerne verringern, die ihr Stagingslot verwendet. Um die Anzahl der von einem Container verwendeten Kerne zu verringern, legen Sie die App-Einstellung `WEBSITE_CPU_CORES_LIMIT` auf die bevorzugte Anzahl von Kernen fest. Sie können sie über die [Cloud Shell](https://shell.azure.com) festlegen. In Bash:
```azurecli-interactive
az webapp config appsettings set --resource-group <group-name> --name <app-name> --slot staging --settings WEBSITE_CPU_CORES_LIMIT=1
```
PowerShell:
```azurepowershell-interactive
Set-AzWebApp -ResourceGroupName <group-name> -Name <app-name> -AppSettings @{"WEBSITE_CPU_CORES_LIMIT"=1}
```
> [!NOTE]
> Durch Aktualisieren der App-Einstellung wird ein automatischer Neustart ausgelöst, was zu minimalen Ausfallzeiten führt. Bei einer Produktions-App sollten Sie erwägen, sie in einen Stagingslot zu wechseln, die App-Einstellung im Stagingslot zu ändern, und die App dann wieder zurück in die Produktion zu wechseln.
Überprüfen Sie Ihre angepasste Anzahl, indem Sie zur Kudu-Konsole wechseln (`https://<app-name>.scm.azurewebsites.net`) und die folgenden Befehle mithilfe von PowerShell eingeben. Jeder Befehl gibt eine Zahl aus.
```PowerShell
Get-ComputerInfo | ft CsNumberOfLogicalProcessors # Total number of enabled logical processors. Disabled processors are excluded.
Get-ComputerInfo | ft CsNumberOfProcessors # Number of physical processors.
```
Bei den Prozessoren kann es sich um Mehrkern- oder Hyperthreading-Prozessoren handeln. Informationen dazu, wie viele Kerne für den jeweiligen Tarif verfügbar sind, finden Sie unter [App Service-Preise](https://azure.microsoft.com/pricing/details/app-service/windows/) im Abschnitt **Windows Container Premium-Tarif**.
## <a name="customize-health-ping-behavior"></a>Anpassen des Integritäts-Ping-Verhaltens
In App Service wird ein Container als erfolgreich gestartet betrachtet, wenn der Container gestartet wird und auf einen HTTP-Ping antwortet. Die Integritäts-Ping-Anforderung enthält den Header `User-Agent= "App Service Hyper-V Container Availability Check"`. Wenn der Container gestartet wird, aber nach einem bestimmten Zeitraum nicht auf einen Ping antwortet, protokolliert App Service ein Ereignis im Docker-Protokoll, das besagt, dass der Container nicht gestartet wurde.
Wenn Ihre Anwendung ressourcenintensiv ist, antwortet der Container möglicherweise nicht rechtzeitig auf den HTTP-Ping. Um die Aktionen zu kontrollieren, wenn HTTP-Pings fehlschlagen, legen Sie die App-Einstellung `CONTAINER_AVAILABILITY_CHECK_MODE` fest. Sie können sie über die [Cloud Shell](https://shell.azure.com) festlegen. In Bash:
```azurecli-interactive
az webapp config appsettings set --resource-group <group-name> --name <app-name> --settings CONTAINER_AVAILABILITY_CHECK_MODE="ReportOnly"
```
PowerShell:
```azurepowershell-interactive
Set-AzWebApp -ResourceGroupName <group-name> -Name <app-name> -AppSettings @{"CONTAINER_AVAILABILITY_CHECK_MODE"="ReportOnly"}
```
In der folgenden Tabelle sind die möglichen Werte aufgeführt:
| Wert | Beschreibungen |
| - | - |
| **Repair** | Neustarten des Containers nach drei aufeinanderfolgenden Verfügbarkeitsprüfungen |
| **ReportOnly** | Der Standardwert. Den Container nicht neu starte, aber den Container nach drei aufeinanderfolgenden Verfügbarkeitsprüfungen in den Docker-Protokollen protokollieren. |
| **Deaktiviert** | Keine Verfügbarkeitsprüfung durchführen. |
## <a name="support-for-group-managed-service-accounts"></a>Unterstützung für gruppenverwaltete Dienstkonten
Gruppenverwaltete Dienstkonten (Group Managed Service Accounts, gMSAs) werden zurzeit in Windows-Containern in App Service nicht unterstützt.
::: zone-end
::: zone pivot="container-linux"
## <a name="enable-ssh"></a>Aktivieren von SSH
SSH ermöglicht die sichere Kommunikation zwischen einem Container und einem Client. Damit ein benutzerdefinierter Container SSH unterstützt, müssen Sie ihn dem Docker-Image selbst hinzufügen.
> [!TIP]
> In allen integrierten Linux-Containern in App Service wurden die SSH-Anweisungen in ihren Imagerepositorys hinzugefügt. Sie können die folgenden Anweisungen mit dem [Node.js 10.14-Repository](https://github.com/Azure-App-Service/node/blob/master/10.14) durchgehen, um zu prüfen, wie es dort aktiviert ist. Die Konfiguration im integrierten Node.js-Image unterscheidet sich geringfügig, ist jedoch im Wesentlichen identisch.
- Fügen Sie dem Repository [die Datei „sshd_config“](https://man.openbsd.org/sshd_config) hinzu, wie im folgenden Beispiel gezeigt.
```
Port 2222
ListenAddress 0.0.0.0
LoginGraceTime 180
X11Forwarding yes
Ciphers aes128-cbc,3des-cbc,aes256-cbc,aes128-ctr,aes192-ctr,aes256-ctr
MACs hmac-sha1,hmac-sha1-96
StrictModes yes
SyslogFacility DAEMON
PasswordAuthentication yes
PermitEmptyPasswords no
PermitRootLogin yes
Subsystem sftp internal-sftp
```
> [!NOTE]
> Diese Datei konfiguriert OpenSSH und muss die folgenden Elemente enthalten:
> - `Port` muss auf 2222 festgelegt werden.
> - `Ciphers` muss mindestens ein Element aus dieser Liste enthalten: `aes128-cbc,3des-cbc,aes256-cbc`.
> - `MACs` muss mindestens ein Element aus dieser Liste enthalten: `hmac-sha1,hmac-sha1-96`.
- Fügen Sie im Dockerfile die folgenden Befehle hinzu:
```Dockerfile
# Install OpenSSH and set the password for root to "Docker!". In this example, "apk add" is the install instruction for an Alpine Linux-based image.
RUN apk add openssh \
&& echo "root:Docker!" | chpasswd
# Copy the sshd_config file to the /etc/ssh/ directory
COPY sshd_config /etc/ssh/
# Open port 2222 for SSH access
EXPOSE 80 2222
```
Diese Konfiguration erlaubt keine externen Verbindungen zum Container. Auf Port 2222 des Containers kann nur im Brückennetzwerk eines privaten virtuellen Netzwerks zugegriffen werden, und Angreifer im Internet haben keinen Zugriff auf diesen Port.
- Starten Sie im Startskript für Ihren Container den SSH-Server.
```bash
/usr/sbin/sshd
```
## <a name="access-diagnostic-logs"></a>Zugreifen auf Diagnoseprotokolle
[!INCLUDE [Access diagnostic logs](../../includes/app-service-web-logs-access-linux-no-h.md)]
## <a name="configure-multi-container-apps"></a>Konfigurieren von Apps mit mehreren Containern
- [Verwenden von beständigem Speicher in Docker Compose](#use-persistent-storage-in-docker-compose)
- [Einschränkungen der Vorschau](#preview-limitations)
- [Optionen von Docker Compose](#docker-compose-options)
### <a name="use-persistent-storage-in-docker-compose"></a>Verwenden von beständigem Speicher in Docker Compose
Apps mit mehreren Containern wie WordPress benötigen einen beständigen Speicher, um ordnungsgemäß zu funktionieren. Um dies zu ermöglichen, muss Ihre Docker Compose-Konfiguration auf einen Speicherort *außerhalb* Ihres Containers verweisen. Speicherorte in Ihrem Container bleiben nach dem Neustart der App nicht mehr unverändert.
Aktivieren Sie den beständigen Speicher, indem Sie die App-Einstellung `WEBSITES_ENABLE_APP_SERVICE_STORAGE` mit dem Befehl [az webapp config appsettings set](/cli/azure/webapp/config/appsettings#az_webapp_config_appsettings_set) in der [Cloud Shell](https://shell.azure.com) festlegen.
```azurecli-interactive
az webapp config appsettings set --resource-group <group-name> --name <app-name> --settings WEBSITES_ENABLE_APP_SERVICE_STORAGE=TRUE
```
Ordnen Sie in Ihrer Datei *docker-compose.yml* die `volumes`-Option zu `${WEBAPP_STORAGE_HOME}` zu.
`WEBAPP_STORAGE_HOME` ist eine Umgebungsvariable in App Service, die dem beständigen Speicher für Ihre App zugeordnet wird. Beispiel:
```yaml
wordpress:
image: wordpress:latest
volumes:
- ${WEBAPP_STORAGE_HOME}/site/wwwroot:/var/www/html
- ${WEBAPP_STORAGE_HOME}/phpmyadmin:/var/www/phpmyadmin
- ${WEBAPP_STORAGE_HOME}/LogFiles:/var/log
```
### <a name="preview-limitations"></a>Einschränkungen der Vorschau
Apps mit mehreren Containern befinden sich derzeit in der Vorschauphase. Die folgenden Features der App Service-Plattform werden nicht unterstützt:
- Authentifizierung/Autorisierung
- Verwaltete Identitäten
- CORS
### <a name="docker-compose-options"></a>Optionen von Docker Compose
In den folgenden Listen werden unterstützte und nicht unterstützte Docker Compose-Konfigurationsoptionen angezeigt:
#### <a name="supported-options"></a>Unterstützte Optionen
- command
- entrypoint
- Environment
- image
- ports
- restart
- services
- volumes
#### <a name="unsupported-options"></a>Nicht unterstützte Optionen
- build (unzulässig)
- depends_on (ignoriert)
- networks (ignoriert)
- secrets (ignoriert)
- andere Ports als 80 und 8080 (ignoriert)
> [!NOTE]
> Alle weiteren Optionen, die nicht ausdrücklich aufgeführt sind, werden in der Public Preview ignoriert.
[!INCLUDE [robots933456](../../includes/app-service-web-configure-robots933456.md)]
::: zone-end
## <a name="next-steps"></a>Nächste Schritte
> [!div class="nextstepaction"]
> [Tutorial: Migrieren benutzerdefinierter Software zu Azure App Service mithilfe eines benutzerdefinierten Containers](tutorial-custom-container.md)
::: zone pivot="container-linux"
> [!div class="nextstepaction"]
> [Tutorial: WordPress-App mit mehreren Containern](tutorial-multi-container-app.md)
::: zone-end
Oder siehe in zusätzlichen Ressourcen:
[Laden eines Zertifikats in Windows-/Linux-Containern](configure-ssl-certificate-in-code.md#load-certificate-in-linuxwindows-containers)
| 65.603687 | 551 | 0.796923 | deu_Latn | 0.975464 |
534558471849ef936c176487ffa9e11a8851de49 | 4,249 | md | Markdown | _posts/2019-03-11-linux-perf-context-switch.md | lightfish-zhang/lightfish-zhang.github.io | 18ed4c2bc6465efe0d05304fdafde71383f72058 | [
"MIT"
] | 1 | 2019-06-20T10:17:51.000Z | 2019-06-20T10:17:51.000Z | _posts/2019-03-11-linux-perf-context-switch.md | lightfish-zhang/lightfish-zhang.github.io | 18ed4c2bc6465efe0d05304fdafde71383f72058 | [
"MIT"
] | 55 | 2019-01-20T07:09:51.000Z | 2021-10-01T07:11:15.000Z | _posts/2019-03-11-linux-perf-context-switch.md | lightfish-zhang/lightfish-zhang.github.io | 18ed4c2bc6465efe0d05304fdafde71383f72058 | [
"MIT"
] | 1 | 2021-02-28T05:38:41.000Z | 2021-02-28T05:38:41.000Z | ---
layout: post
title: Linux 进程性能问题——CPU 上下文切换 Context Switches
date: 2019-03-08 20:30:00 +0800
category: Linux
tag: [perf]
thumbnail: https://cdn.jsdelivr.net/gh/lightfish-zhang/media-library/image/201903/switch-icon.png
icon: note
---
* content
{:toc}
## 前言
Linux 是一个多任务操作系统，当比较多数量的进程抢夺 CPU 时，上下文切换的损耗会显得比较大，本文讲述如何衡量 Linux 系统的上下文切换的性能指标，以及上下文切换的基础知识。
## 什么是 CPU 上下文切换
简单理解，CPU 上下文切换是更新了 CPU 寄存器的值，或者硬件触发信号，调用中断处理程序。
根据任务不同，有不同场景的上下文切换，有 **特权模式切换**，**进程上下文切换**，**线程上下文切换**，**中断上下文切换**
### 特权模式切换(系统调用)
特权模式切换是指系统调用过程，在同一个进程中进行“用户态－内核态－用户态”的切换过程，一次系统调用，会发生两次 CPU 上下文切换。这过程中，先保存 CPU 寄存器里原来用户态的指令位置，接下来要执行内核态代码，CPU 寄存器更新为内核态指令的位置，最后跳转到内核态运行内核任务。
与进程上下文切换不同的是，系统调用过程中，不会涉及到虚拟内存等进程用户态的资源，也不会切换进程。
了解更多 Linux Protection Rings 特权保护级别，看下图
不同级别可以访问的资源级别不一样，如最里层的内核空间 Ring 0 可以直接访问所有资源，最外层的用户空间 Ring 3 只能访问受限资源，不能直接访问内存等硬件设备，必须通过系统调用陷入内核中，才能访问特权资源。
### 进程上下文切换
进程上下文切换，是指从一个进程切换到另一个进程。进程是由内核来管理和调度的，进程的切换只能发生在内核态。
#### 进程的上下文有什么？
进程的上下文有虚拟内存、栈、全局变量等用户空间的资源，还包括内核堆栈、寄存器等内核空间的状态。
于是，切换进程的过程比系统调用过程要多一步，在保存内核状态与 CPU 寄存器之前，需要把进程的虚拟内存、栈等保存下来；等加载下一个进程的内核态后，需要更新下一个进程的虚拟内存、栈等。
#### CPU 上下文切换耗时
引用测试报告 [How long does it take to make a context switch?](https://blog.tsunanet.net/2010/11/how-long-does-it-take-to-make-context.html)，每次上下文切换都需要几十纳秒到数微秒的 CPU 时间。这个时间还是相当可观的，特别是在进程上下文切换次数较多的情况下，很容易导致 CPU 将大量时间耗费在寄存器、内核栈以及虚拟内存等资源的保存和恢复上，进而大大缩短了真正运行进程的时间。
#### 切换进程对内存访问性能的影响
Linux 通过 TLB（Translation Lookaside Buffer）来管理虚拟内存到物理内存的映射关系。当虚拟内存更新后，TLB 也需要刷新，内存的访问也会随之变慢。特别是在多处理器系统上，缓存是被多个处理器共享的，刷新缓存不仅会影响当前处理器的进程，还会影响共享缓存的其他处理器的进程。
#### Linux 如何进行进程调度
- 首先，为了公平调度，CPU 时间被划分为一段段的时间片，这些时间片再被轮流分配给各个进程。
- 第二，进程在系统资源不足（比如内存不足）时，要等到资源满足后才可以运行，这个时候进程也会被挂起，并由系统调度其他进程运行。
- 第三，当进程通过睡眠函数 sleep 这样的方法将自己主动挂起时，自然也会重新调度。
- 第四，当有优先级更高的进程运行时，为了保证高优先级进程的运行，当前进程会被挂起，由高优先级进程来运行。
- 最后，发生硬件中断时(比如网卡硬盘键盘等)，CPU 上的进程会被中断挂起，转而执行内核中的中断服务程序。
### 线程上下文切换
我们这里讨论同一个进程下多个线程的上下文切换。
线程是调度的基本单位，而进程则是资源拥有的基本单位。于是，内核中的任务调度，实际上的调度对象是线程；而进程只是给线程提供了虚拟内存、全局变量等资源。
由于同一个进程下，多个线程共享虚拟内存等资源，所以线程的上下文切换，只需切换线程的私有数据、寄存器等不共享的数据。
### 中断上下文切换
中断是什么？
中断其实是一种异步的事件处理机制，可以提高系统的并发处理能力。中断分为两种，硬中断与软中断。
**硬中断**：比如网卡接收数据后，需要通知 Linux 内核有新的数据到了，通过硬件中断的方式发送电信号给内核，内核此时调用中断处理程序来响应下。这一步需要快速响应，防止时间过长影响系统的并发处理能力。于是，内核把网卡的数据读到内存中，更新一下硬件寄存器的状态，表示数据已经读好了。再发送一个软中断信号给用户程序，结束中断处理程序。
**软中断**：用户程序需要上面网卡接收的数据，正处于 read 或者 epoll 的系统调用的 Sleep 状态中。系统如何通知用户程序收数据呢？每个 CPU 都对应一个软中断内核线程，名 `ksoftirqd/$CPU_NUM`，它被软中断信号唤醒，从内存中找到网络数据，按照网络协议栈，对数据进行逐层解析和处理，再发到用户程序上（唤醒用户程序）
为了快速响应硬件的事件，中断处理会打断进程的正常调度和执行，转而调用中断处理程序，响应设备事件。而在打断其他进程时，就需要将进程当前的状态保存下来，这样在中断结束后，进程仍然可以从原来的状态恢复运行。
对同一个 CPU 来说，中断处理比进程拥有更高的优先级，所以中断上下文切换并不会与进程上下文切换同时发生。同样道理，由于中断会打断正常进程的调度和执行，所以**大部分中断处理程序都短小精悍**，以便尽可能快的执行结束。
跟进程上下文不同，中断上下文切换并不涉及到进程的用户态。所以，即便中断过程打断了一个正处在用户态的进程，也不需要保存和恢复这个进程的虚拟内存、全局变量等用户态资源。**中断上下文，其实只包括内核态中断服务程序执行所必需的状态，包括 CPU 寄存器、内核堆栈、硬件中断参数等。**
另外，跟进程上下文切换一样，中断上下文切换也需要消耗 CPU，切换次数过多也会耗费大量的 CPU，甚至严重降低系统的整体性能。所以，当你发现中断次数过多时，就需要注意去排查它是否会给你的系统带来严重的性能问题。
## 上下文切换频繁的性能问题
过多的上下文切换，会把 CPU 时间消耗在寄存器、内核栈以及虚拟内存等数据的保存和恢复上，缩短进程真正运行的时间，成了系统性能大幅下降的一个元凶。
### 从性能角度看待上下文切换
- **自愿上下文切换**，是指进程无法获取所需资源，导致的上下文切换。比如说， I/O、内存等系统资源不足时，就会发生自愿上下文切换。
- **非自愿上下文切换**，则是指进程由于时间片已到等原因，被系统强制调度，进而发生的上下文切换。比如说，大量进程都在争抢 CPU 时，就容易发生非自愿上下文切换。
## 模拟场景与测量工具
使用 `sysbench` 命令行工具可以模拟系统多线程调度的瓶颈，它可以造成大量的线程线程，造成频率大的非自愿上下文切换
```
# 以 10 个线程运行 5 分钟的基准测试，模拟多线程切换的问题
sysbench --threads=10 --max-time=300 threads run
```
测量工具： `vmstat`, `pidstat`
- 命令 `vmstat 5`， 每 5 秒输出 1 组数据，指标有：
+ cs（context switch）是每秒上下文切换的次数。
+ in（interrupt）则是每秒中断的次数。
+ r（Running or Runnable）是就绪队列的长度，也就是正在运行和等待 CPU 的进程数。
+ b（Blocked）则是处于不可中断睡眠状态的进程数。
- 命令 `pidstat -wt 1` 每隔 1 秒输出 1 组数据，`-w` 表示输出进程切换指标，`-u`表示输出 CPU 使用指标，`-wt`表示输出线程的上下文切换指标
- `watch -d cat /proc/interrupts` 查看 `/proc` 这个虚拟文件目录下，Linux 的中断使用情况，值得注意的指标有：
+ `RES` 重调度中断，这个中断类型表示，唤醒空闲状态的 CPU 来调度新的任务运行，也称为处理器间中断（Inter-Processor Interrupts，IPI）
## Reference
- [Preemptive Priority-Based Scheduling](http://www.embeddedlinux.org.cn/rtconforembsys/5107final/LiB0024.html)
- [Linux 特权级别 wiki](https://en.wikipedia.org/wiki/Protection_ring)
- [Linux 概念，中断与中断处理](https://zhuanlan.zhihu.com/p/53640307) | 32.189394 | 253 | 0.800894 | yue_Hant | 0.655647 |
53461d08d7ab98b7110377348853131b1c3156e6 | 10,924 | md | Markdown | android/start.md | kaustavghosh06/docs | 98d51c400d95a3c734f3e095df7c1777b24271bc | [
"Apache-2.0"
] | null | null | null | android/start.md | kaustavghosh06/docs | 98d51c400d95a3c734f3e095df7c1777b24271bc | [
"Apache-2.0"
] | null | null | null | android/start.md | kaustavghosh06/docs | 98d51c400d95a3c734f3e095df7c1777b24271bc | [
"Apache-2.0"
] | null | null | null | ---
title: Getting Started
---
# Getting Started
Build an Android app using the AWS Amplify CLI and the AWS SDK for Android. The Amplify CLI lets you quickly add backend features to your application so that you can focus on your application code. This page guides you through setting up an initial backend and integration into your app.
## Prerequisites
[Install and configure the Amplify CLI](..)
[Install Android Studio](https://developer.android.com/studio/index.html#downloads) version 3.1 or higher. Install Android SDK for API level 28 (Android 9.0).
## Step 1: Create a new app
Follow [these steps](https://developer.android.com/training/basics/firstapp/creating-project) to create an Android Studio application using Java. Modify your `project/build.gradle` with the following build dependency:
```groovy
classpath 'com.amazonaws:aws-android-sdk-appsync-gradle-plugin:2.9.+'
```
Next, add dependencies to your `app/build.gradle`, and then choose Sync Now on the upper-right side of Android Studio.
```groovy
apply plugin: 'com.amazonaws.appsync'
dependencies {
//Base SDK
implementation 'com.amazonaws:aws-android-sdk-core:2.13.+'
//AppSync SDK
implementation 'com.amazonaws:aws-android-sdk-appsync:2.8.+'
implementation 'org.eclipse.paho:org.eclipse.paho.client.mqttv3:1.2.0'
implementation 'org.eclipse.paho:org.eclipse.paho.android.service:1.1.1'
}
```
Finally, update your AndroidManifest.xml with the following:
```xml
<uses-permission android:name="android.permission.INTERNET"/>
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE"/>
<uses-permission android:name="android.permission.WAKE_LOCK" />
<uses-permission android:name="android.permission.READ_PHONE_STATE" />
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>
<uses-permission android:name="android.permission.READ_EXTERNAL_STORAGE"/>
<!--other code-->
<application
android:allowBackup="true"
android:icon="@mipmap/ic_launcher"
android:label="@string/app_name"
android:roundIcon="@mipmap/ic_launcher_round"
android:supportsRtl="true"
android:theme="@style/AppTheme">
<service android:name="org.eclipse.paho.android.service.MqttService" />
<!--other code-->
</application>
```
**Build your Android Studio project**.
## Step 2: Set Up Your Backend
Create new AWS backend resources and pull the AWS services configuration into the app. In a terminal window, navigate to your project folder (the folder that typically contains your project level `build.gradle`), and run the following command (for this app, accepting all defaults is OK):
```bash
$ cd ./YOUR_PROJECT_FOLDER
$ amplify init #accept defaults
$ amplify push #creates configuration file
```
An `awsconfiguration.json` file will be created with your configuration and updated as features get added to your project by the Amplify CLI. The file is placed in the `./app/src/main/res/raw` directory of your Android Studio project and automatically used by the SDKs at runtime.
## Step 3: How it Works
Rather than configuring each service through a constructor or constants file, the AWS SDKs for Android support configuration through a centralized file called `awsconfiguration.json` which defines all the regions and service endpoints to communicate. Whenever you run `amplify push`, this file is automatically created allowing you to focus on your application code. On Android projects the `awsconfiguration.json` will be placed into the `./app/src/main/res/raw` directory.
To verify that the CLI is set up for your app, run the following command.
```bash
$ amplify status
| Category | Resource name | Operation | Provider plugin |
| -------- | ------------- | --------- | --------------- |
```
The CLI displays a status table with no resources listed. As you add feature categories to your app and run `amplify push`, backend resources created for your app are listed in this table.
## Step 4: Add API and Database
Add a GraphQL API to your app and automatically provision a database with the following command (accepting all defaults is OK):
```bash
$ amplify add api #select GraphQL, API Key
```
The `add api` flow above will ask you some questions, like if you already have an annotated GraphQL schema. If this is your first time using the CLI select **No** and let it guide you through the default project **"Single object with fields (e.g., “Todo” with ID, name, description)"** as it will be used in the code generation examples below. Later on you can always change it. This process creates an AWS AppSync API and connects it to an Amazon DynamoDB database.
Create required backend resources for your configured api with the following command:
```bash
$ amplify push
```
Since you added an API the `amplify push` process will automatically enter the codegen process and prompt you for configuration. Accept the defaults which generate a `./app/src/main/graphql` folder structure with your statements. Run a **Gradle Sync** and **Build** your app, at which point the generated packages are automatically added to your project.
## Step 5: Integrate into your app
Initialize the AppSync client inside your application code, such as the `onCreate()` lifecycle method of your activity class:
```java
private AWSAppSyncClient mAWSAppSyncClient;
@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_main);
mAWSAppSyncClient = AWSAppSyncClient.builder()
.context(getApplicationContext())
.awsConfiguration(new AWSConfiguration(getApplicationContext()))
.build();
}
```
You can now add data to your database with a mutation:
```java
public void runMutation(){
CreateTodoInput createTodoInput = CreateTodoInput.builder().
name("Use AppSync").
description("Realtime and Offline").
build();
mAWSAppSyncClient.mutate(CreateTodoMutation.builder().input(createTodoInput).build())
.enqueue(mutationCallback);
}
private GraphQLCall.Callback<CreateTodoMutation.Data> mutationCallback = new GraphQLCall.Callback<CreateTodoMutation.Data>() {
@Override
public void onResponse(@Nonnull Response<CreateTodoMutation.Data> response) {
Log.i("Results", "Added Todo");
}
@Override
public void onFailure(@Nonnull ApolloException e) {
Log.e("Error", e.toString());
}
};
```
Next, query the data:
```java
public void runQuery(){
mAWSAppSyncClient.query(ListTodosQuery.builder().build())
.responseFetcher(AppSyncResponseFetchers.CACHE_AND_NETWORK)
.enqueue(todosCallback);
}
private GraphQLCall.Callback<ListTodosQuery.Data> todosCallback = new GraphQLCall.Callback<ListTodosQuery.Data>() {
@Override
public void onResponse(@Nonnull Response<ListTodosQuery.Data> response) {
Log.i("Results", response.data().listTodos().items().toString());
}
@Override
public void onFailure(@Nonnull ApolloException e) {
Log.e("ERROR", e.toString());
}
};
```
You can also setup realtime subscriptions to data:
```java
private AppSyncSubscriptionCall subscriptionWatcher;
private void subscribe(){
OnCreateTodoSubscription subscription = OnCreateTodoSubscription.builder().build();
subscriptionWatcher = mAWSAppSyncClient.subscribe(subscription);
subscriptionWatcher.execute(subCallback);
}
private AppSyncSubscriptionCall.Callback subCallback = new AppSyncSubscriptionCall.Callback() {
@Override
public void onResponse(@Nonnull Response response) {
Log.i("Response", response.data().toString());
}
@Override
public void onFailure(@Nonnull ApolloException e) {
Log.e("Error", e.toString());
}
@Override
public void onCompleted() {
Log.i("Completed", "Subscription completed");
}
};
```
Call the `runMutation()`, `runQuery()`, and `subscribe()` methods from your app code, such as from a button click or when your app starts in `onCreate()`. You will see data being stored and retrieved in your backend from the Android Studio console. At any time you can open the AWS console for your new API directly by running the following command:
```terminal
$ amplify console api
> GraphQL ##Select GraphQL
```
This will open the AWS AppSync console for you to run Queries, Mutations, or Subscriptions at the server and see the changes in your client app.
## Next Steps
🎉 Congratulations! Your app is built, with a realtime backend using AWS AppSync.
What next? Here are some things to add to your app:
* [Authentication](./authentication)
* [Storage](./storage)
* [Serverless APIs](./api)
* [Analytics](./analytics)
* [Push Notification](./push-notifications)
* [Messaging](./messaging)
**Existing AWS Resources**
If you want to use your existing AWS resources with your app you will need to **manually configure** your app with an `awsconfiguration.json` file in your code. For example, if you were using Amazon Cognito Identity, Cognito User Pools, AWS AppSync, or Amazon S3:
```xml
{
"CredentialsProvider": {
"CognitoIdentity": {
"Default": {
"PoolId": "XX-XXXX-X:XXXXXXXX-XXXX-1234-abcd-1234567890ab",
"Region": "XX-XXXX-X"
}
}
},
"CognitoUserPool": {
"Default": {
"PoolId": "XX-XXXX-X_abcd1234",
"AppClientId": "XXXXXXXX",
"AppClientSecret": "XXXXXXXXX",
"Region": "XX-XXXX-X"
}
},
"AppSync": {
"Default": {
"ApiUrl": "https://XXXXXX.appsync-api.XX-XXXX-X.amazonaws.com/graphql",
"Region": "XX-XXXX-X",
"AuthMode": "AMAZON_COGNITO_USER_POOLS"
}
},
"S3TransferUtility": {
"Default": {
"Bucket": "BUCKET_NAME",
"Region": "XX-XXXX-X"
}
}
}
```
In the configuration above, you would need to set the appropriate values such as `Region`, `Bucket`, etc.
**AWS SDK Interfaces**
For working with other AWS services you can use service interface objects directly via the generated SDK clients.
To work with service interface objects, your Amazon Cognito users' [IAM role](https://docs.aws.amazon.com/cognito/latest/developerguide/iam-roles.html) must have the appropriate permissions to call the requested services.
{: .callout .callout--warning}
You can call methods on any AWS Service interface object supported by the AWS Android SDK by passing your credentials from the AWSMobileClient to the service call constructor. See [Manual SDK Setup](./manualsetup) for more information.
| 39.57971 | 474 | 0.704962 | eng_Latn | 0.889677 |
53466af0dbfd03fe4525b887011e423e8ed196e8 | 163 | md | Markdown | clojure/leiningen.md | fgui/fgui.github.io | 69f01fc39d833b0f9c11840c491d0dd69f662e77 | [
"MIT"
] | null | null | null | clojure/leiningen.md | fgui/fgui.github.io | 69f01fc39d833b0f9c11840c491d0dd69f662e77 | [
"MIT"
] | null | null | null | clojure/leiningen.md | fgui/fgui.github.io | 69f01fc39d833b0f9c11840c491d0dd69f662e77 | [
"MIT"
] | null | null | null | ---
layout: page
title: clj> lein
---
```
lein help
lein tutorial
lein sample
```
in the web:
[leiningen at github](https://github.com/technomancy/leiningen)
| 9.588235 | 63 | 0.680982 | eng_Latn | 0.296778 |
5346ccb2e07936302fd4d6174c3249d4c72030f1 | 3,430 | md | Markdown | content/post/2020/hacker-news-why-arent-we-more-serious.md | RubenSchade/rubenerd-com | c31a535a0e2949a360be1211b5413bac6d37c2cb | [
"BSD-3-Clause"
] | 7 | 2016-08-25T17:47:57.000Z | 2020-07-13T12:19:53.000Z | content/post/2020/hacker-news-why-arent-we-more-serious.md | RubenSchade/rubenerd-com | c31a535a0e2949a360be1211b5413bac6d37c2cb | [
"BSD-3-Clause"
] | null | null | null | content/post/2020/hacker-news-why-arent-we-more-serious.md | RubenSchade/rubenerd-com | c31a535a0e2949a360be1211b5413bac6d37c2cb | [
"BSD-3-Clause"
] | 3 | 2020-07-13T12:20:10.000Z | 2021-01-04T09:34:13.000Z | ---
title: "Hacker News: Why aren’t we all more serious?"
date: "2020-09-27T10:18:38+10:00"
abstract: "Feedback from the post in HN, including talk about the site mascot."
year: "2020"
category: Internet
tag:
- comments
- feedback
- hacker-news
location: Sydney
---
Another post of mine [appeared on Hacker News](https://news.ycombinator.com/item?id=24537147) last week, this time thanks to [luu](https://news.ycombinator.com/user?id=luu). It was one I wrote back in July responding to the charge that my [blog isn't serious enough](https://rubenerd.com/why-arent-you-more-serious/), a touchy-feely topic I didn't expect given HN tends to appeal to hard computer science and engineering types. I was also surprised at the number of positive comments.
The biggest takeaway I took were an affirmation that not everything needs to be a hussle, or justified in the context of money. tayo42 had my favourite comment:
> I really wish we didn't put so much pressure to be professional and serious all the time. Working takes up 1/3 of my life currently and I can't actually be my self. Another third is sleeping. So for only 1/3 of my time I can actually act like my self. I hate that there is a pressure to talk a certain, act a certain way, express my self a certain way. I think we really need more of a emphasis on being human, less "circle back" and "work streams", more jokes, more smiling and experimenting.
KaiserPro also raised a point I hadn't considered: being too serious could also *limit* the reach of your work in unexpected ways:
> They couldn't seem to grasp that if I'd have written [his sweary post in] a dry, clean style, not only would they have not read it, but they wouldn't have understood my point. [..] Humour, irreverence and swearing are all tools to convey a meaning, point or story. Used well (I am fully willing to admit that I have not been masterful in my use) they can create a mental image far stronger than any other metaphor.
There's also the angle that simply fewer people are writing online these days, or are confining themselves to social networks. There are so many reasons why this is sad, not least because they're surrendering control, propping up invasive business models, and relegating their important ideas to ephemeral social posts. But just as important is the lack of personality: I miss seeing people's personal sites in the 1990s, and how people presented their blogs in the 2000s.
Curiously, the few negative comments had to do with my [site mascot Rubi](https://rubenerd.com/about/#mascot), which I'll admit didn't surprise me. Once people on mobile found her—she only appears in the desktop theme—a few proceeded to discuss her appropriateness. One specifically called out her "hiked-up skirt" (since deleted) which amused Clara who drew her, and who often cosplays in similar getup. It was a good thing they didn't see Rubi in her summer swimsuit and shorts for that brief month a few years ago!
I've always had a small anime badge somewhere on my sites since at least 2006, back when it was SOS-Dan to demonstrate my allegiance to Haruhi. Before then it was Star Trek insignia. I love stumbling on another personal site and seeing a different aspect of someone's personality shine through. That's what makes the web fun. If I lose a few readers from doing that, they probably weren't the kind of people I wanted to spend mental energy on in the first place.
| 118.275862 | 529 | 0.7793 | eng_Latn | 0.999856 |
5346ee21364468443e8dc11a0a83d1d731d03ea2 | 11,671 | md | Markdown | examples.md | anthonymark33/cache | 12b87469d4aa0628b98933dd469bf6fb329fb293 | [
"MIT"
] | 1 | 2021-07-16T03:28:03.000Z | 2021-07-16T03:28:03.000Z | examples.md | anthonymark33/cache | 12b87469d4aa0628b98933dd469bf6fb329fb293 | [
"MIT"
] | 6 | 2020-04-05T04:57:31.000Z | 2020-04-10T17:18:30.000Z | examples.md | anthonymark33/cache | 12b87469d4aa0628b98933dd469bf6fb329fb293 | [
"MIT"
] | 2 | 2020-05-03T01:35:26.000Z | 2021-03-03T11:40:02.000Z | # Examples
- [Examples](#examples)
- [C# - NuGet](#c---nuget)
- [Elixir - Mix](#elixir---mix)
- [Go - Modules](#go---modules)
- [Haskell - Cabal](#haskell---cabal)
- [Java - Gradle](#java---gradle)
- [Java - Maven](#java---maven)
- [Node - npm](#node---npm)
- [macOS and Ubuntu](#macos-and-ubuntu)
- [Windows](#windows)
- [Using multiple systems and `npm config`](#using-multiple-systems-and-npm-config)
- [Node - Lerna](#node---lerna)
- [Node - Yarn](#node---yarn)
- [OCaml/Reason - esy](#ocamlreason---esy)
- [PHP - Composer](#php---composer)
- [Python - pip](#python---pip)
- [Simple example](#simple-example)
- [Multiple OS's in a workflow](#multiple-oss-in-a-workflow)
- [Using a script to get cache location](#using-a-script-to-get-cache-location)
- [R - renv](#r---renv)
- [Simple example](#simple-example-1)
- [Multiple OS's in a workflow](#multiple-oss-in-a-workflow-1)
- [Ruby - Bundler](#ruby---bundler)
- [Rust - Cargo](#rust---cargo)
- [Scala - SBT](#scala---sbt)
- [Swift, Objective-C - Carthage](#swift-objective-c---carthage)
- [Swift, Objective-C - CocoaPods](#swift-objective-c---cocoapods)
- [Swift - Swift Package Manager](#swift---swift-package-manager)
## C# - NuGet
Using [NuGet lock files](https://docs.microsoft.com/nuget/consume-packages/package-references-in-project-files#locking-dependencies):
```yaml
- uses: actions/cache@v1
with:
path: ~/.nuget/packages
key: ${{ runner.os }}-nuget-${{ hashFiles('**/packages.lock.json') }}
restore-keys: |
${{ runner.os }}-nuget-
```
Depending on the environment, huge packages might be pre-installed in the global cache folder.
If you do not want to include them, consider to move the cache folder like below.
>Note: This workflow does not work for projects that require files to be placed in user profile package folder
```yaml
env:
NUGET_PACKAGES: ${{ github.workspace }}/.nuget/packages
steps:
- uses: actions/cache@v1
with:
path: ${{ github.workspace }}/.nuget/packages
key: ${{ runner.os }}-nuget-${{ hashFiles('**/packages.lock.json') }}
restore-keys: |
${{ runner.os }}-nuget-
```
## Elixir - Mix
```yaml
- uses: actions/cache@v1
with:
path: deps
key: ${{ runner.os }}-mix-${{ hashFiles(format('{0}{1}', github.workspace, '/mix.lock')) }}
restore-keys: |
${{ runner.os }}-mix-
```
## Go - Modules
```yaml
- uses: actions/cache@v1
with:
path: ~/go/pkg/mod
key: ${{ runner.os }}-go-${{ hashFiles('**/go.sum') }}
restore-keys: |
${{ runner.os }}-go-
```
## Haskell - Cabal
We cache the elements of the Cabal store separately, as the entirety of `~/.cabal` can grow very large for projects with many dependencies.
```yaml
- uses: actions/cache@v1
name: Cache ~/.cabal/packages
with:
path: ~/.cabal/packages
key: ${{ runner.os }}-${{ matrix.ghc }}-cabal-packages
- uses: actions/cache@v1
name: Cache ~/.cabal/store
with:
path: ~/.cabal/store
key: ${{ runner.os }}-${{ matrix.ghc }}-cabal-store
- uses: actions/cache@v1
name: Cache dist-newstyle
with:
path: dist-newstyle
key: ${{ runner.os }}-${{ matrix.ghc }}-dist-newstyle
```
## Java - Gradle
```yaml
- uses: actions/cache@v1
with:
path: ~/.gradle/caches
key: ${{ runner.os }}-gradle-${{ hashFiles('**/*.gradle*') }}
restore-keys: |
${{ runner.os }}-gradle-
```
## Java - Maven
```yaml
- uses: actions/cache@v1
with:
path: ~/.m2/repository
key: ${{ runner.os }}-maven-${{ hashFiles('**/pom.xml') }}
restore-keys: |
${{ runner.os }}-maven-
```
## Node - npm
For npm, cache files are stored in `~/.npm` on Posix, or `%AppData%/npm-cache` on Windows. See https://docs.npmjs.com/cli/cache#cache
>Note: It is not recommended to cache `node_modules`, as it can break across Node versions and won't work with `npm ci`
### macOS and Ubuntu
```yaml
- uses: actions/cache@v1
with:
path: ~/.npm
key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') }}
restore-keys: |
${{ runner.os }}-node-
```
### Windows
```yaml
- name: Get npm cache directory
id: npm-cache
run: |
echo "::set-output name=dir::$(npm config get cache)"
- uses: actions/cache@v1
with:
path: ${{ steps.npm-cache.outputs.dir }}
key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') }}
restore-keys: |
${{ runner.os }}-node-
```
### Using multiple systems and `npm config`
```yaml
- name: Get npm cache directory
id: npm-cache
run: |
echo "::set-output name=dir::$(npm config get cache)"
- uses: actions/cache@v1
with:
path: ${{ steps.npm-cache.outputs.dir }}
key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') }}
restore-keys: |
${{ runner.os }}-node-
```
## Node - Lerna
>Note this example uses the new multi-paths feature and is only available at `master`
```yaml
- name: restore lerna
uses: actions/cache@master
with:
path: |
node_modules
*/*/node_modules
key: ${{ runner.os }}-${{ hashFiles('**/yarn.lock') }}
```
## Node - Yarn
The yarn cache directory will depend on your operating system and version of `yarn`. See https://yarnpkg.com/lang/en/docs/cli/cache/ for more info.
```yaml
- name: Get yarn cache directory path
id: yarn-cache-dir-path
run: echo "::set-output name=dir::$(yarn cache dir)"
- uses: actions/cache@v1
id: yarn-cache # use this to check for `cache-hit` (`steps.yarn-cache.outputs.cache-hit != 'true'`)
with:
path: ${{ steps.yarn-cache-dir-path.outputs.dir }}
key: ${{ runner.os }}-yarn-${{ hashFiles('**/yarn.lock') }}
restore-keys: |
${{ runner.os }}-yarn-
```
## OCaml/Reason - esy
Esy allows you to export built dependencies and import pre-built dependencies.
```yaml
- name: Restore Cache
id: restore-cache
uses: actions/cache@v1
with:
path: _export
key: ${{ runner.os }}-esy-${{ hashFiles('esy.lock/index.json') }}
restore-keys: |
${{ runner.os }}-esy-
- name: Esy install
run: 'esy install'
- name: Import Cache
run: |
esy import-dependencies _export
rm -rf _export
...(Build job)...
# Re-export dependencies if anything has changed or if it is the first time
- name: Setting dependency cache
run: |
esy export-dependencies
if: steps.restore-cache.outputs.cache-hit != 'true'
```
## PHP - Composer
```yaml
- name: Get Composer Cache Directory
id: composer-cache
run: |
echo "::set-output name=dir::$(composer config cache-files-dir)"
- uses: actions/cache@v1
with:
path: ${{ steps.composer-cache.outputs.dir }}
key: ${{ runner.os }}-composer-${{ hashFiles('**/composer.lock') }}
restore-keys: |
${{ runner.os }}-composer-
```
## Python - pip
For pip, the cache directory will vary by OS. See https://pip.pypa.io/en/stable/reference/pip_install/#caching
Locations:
- Ubuntu: `~/.cache/pip`
- Windows: `~\AppData\Local\pip\Cache`
- macOS: `~/Library/Caches/pip`
### Simple example
```yaml
- uses: actions/cache@v1
with:
path: ~/.cache/pip
key: ${{ runner.os }}-pip-${{ hashFiles('**/requirements.txt') }}
restore-keys: |
${{ runner.os }}-pip-
```
Replace `~/.cache/pip` with the correct `path` if not using Ubuntu.
### Multiple OS's in a workflow
```yaml
- uses: actions/cache@v1
if: startsWith(runner.os, 'Linux')
with:
path: ~/.cache/pip
key: ${{ runner.os }}-pip-${{ hashFiles('**/requirements.txt') }}
restore-keys: |
${{ runner.os }}-pip-
- uses: actions/cache@v1
if: startsWith(runner.os, 'macOS')
with:
path: ~/Library/Caches/pip
key: ${{ runner.os }}-pip-${{ hashFiles('**/requirements.txt') }}
restore-keys: |
${{ runner.os }}-pip-
- uses: actions/cache@v1
if: startsWith(runner.os, 'Windows')
with:
path: ~\AppData\Local\pip\Cache
key: ${{ runner.os }}-pip-${{ hashFiles('**/requirements.txt') }}
restore-keys: |
${{ runner.os }}-pip-
```
### Using a script to get cache location
> Note: This uses an internal pip API and may not always work
```yaml
- name: Get pip cache
id: pip-cache
run: |
python -c "from pip._internal.locations import USER_CACHE_DIR; print('::set-output name=dir::' + USER_CACHE_DIR)"
- uses: actions/cache@v1
with:
path: ${{ steps.pip-cache.outputs.dir }}
key: ${{ runner.os }}-pip-${{ hashFiles('**/requirements.txt') }}
restore-keys: |
${{ runner.os }}-pip-
```
## R - renv
For renv, the cache directory will vary by OS. Look at https://rstudio.github.io/renv/articles/renv.html#cache
Locations:
- Ubuntu: `~/.local/share/renv`
- macOS: `~/Library/Application Support/renv`
- Windows: `%LOCALAPPDATA%/renv`
### Simple example
```yaml
- uses: actions/cache@v1
with:
path: ~/.local/share/renv
key: ${{ runner.os }}-renv-${{ hashFiles('**/renv.lock') }}
restore-keys: |
${{ runner.os }}-renv-
```
Replace `~/.local/share/renv` with the correct `path` if not using Ubuntu.
### Multiple OS's in a workflow
```yaml
- uses: actions/cache@v1
if: startsWith(runner.os, 'Linux')
with:
path: ~/.local/share/renv
key: ${{ runner.os }}-renv-${{ hashFiles('**/renv.lock') }}
restore-keys: |
${{ runner.os }}-renv-
- uses: actions/cache@v1
if: startsWith(runner.os, 'macOS')
with:
path: ~/Library/Application Support/renv
key: ${{ runner.os }}-renv-${{ hashFiles('**/renv.lock') }}
restore-keys: |
${{ runner.os }}-renv-
- uses: actions/cache@v1
if: startsWith(runner.os, 'Windows')
with:
path: ~\AppData\Local\renv
key: ${{ runner.os }}-renv-${{ hashFiles('**/renv.lock') }}
restore-keys: |
${{ runner.os }}-renv-
```
## Ruby - Bundler
```yaml
- uses: actions/cache@v1
with:
path: vendor/bundle
key: ${{ runner.os }}-gems-${{ hashFiles('**/Gemfile.lock') }}
restore-keys: |
${{ runner.os }}-gems-
```
When dependencies are installed later in the workflow, we must specify the same path for the bundler.
```yaml
- name: Bundle install
run: |
bundle config path vendor/bundle
bundle install --jobs 4 --retry 3
```
## Rust - Cargo
```yaml
- name: Cache cargo registry
uses: actions/cache@v1
with:
path: ~/.cargo/registry
key: ${{ runner.os }}-cargo-registry-${{ hashFiles('**/Cargo.lock') }}
- name: Cache cargo index
uses: actions/cache@v1
with:
path: ~/.cargo/git
key: ${{ runner.os }}-cargo-index-${{ hashFiles('**/Cargo.lock') }}
- name: Cache cargo build
uses: actions/cache@v1
with:
path: target
key: ${{ runner.os }}-cargo-build-target-${{ hashFiles('**/Cargo.lock') }}
```
## Scala - SBT
```yaml
- name: Cache SBT ivy cache
uses: actions/cache@v1
with:
path: ~/.ivy2/cache
key: ${{ runner.os }}-sbt-ivy-cache-${{ hashFiles('**/build.sbt') }}
- name: Cache SBT
uses: actions/cache@v1
with:
path: ~/.sbt
key: ${{ runner.os }}-sbt-${{ hashFiles('**/build.sbt') }}
```
## Swift, Objective-C - Carthage
```yaml
- uses: actions/cache@v1
with:
path: Carthage
key: ${{ runner.os }}-carthage-${{ hashFiles('**/Cartfile.resolved') }}
restore-keys: |
${{ runner.os }}-carthage-
```
## Swift, Objective-C - CocoaPods
```yaml
- uses: actions/cache@v1
with:
path: Pods
key: ${{ runner.os }}-pods-${{ hashFiles('**/Podfile.lock') }}
restore-keys: |
${{ runner.os }}-pods-
```
## Swift - Swift Package Manager
```yaml
- uses: actions/cache@v1
with:
path: .build
key: ${{ runner.os }}-spm-${{ hashFiles('**/Package.resolved') }}
restore-keys: |
${{ runner.os }}-spm-
```
| 26.226966 | 147 | 0.60766 | eng_Latn | 0.611409 |
5347982d8d8e96606decea3551658a2e00f3f63a | 8,738 | md | Markdown | docs/framework/winforms/controls/how-to-display-option-buttons-in-a-menustrip-windows-forms.md | emrekas/docs.tr-tr | 027bd2c6c93900a75cac7ac42531c89085f87888 | [
"CC-BY-4.0",
"MIT"
] | 1 | 2020-01-06T07:30:24.000Z | 2020-01-06T07:30:24.000Z | docs/framework/winforms/controls/how-to-display-option-buttons-in-a-menustrip-windows-forms.md | emrekas/docs.tr-tr | 027bd2c6c93900a75cac7ac42531c89085f87888 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/winforms/controls/how-to-display-option-buttons-in-a-menustrip-windows-forms.md | emrekas/docs.tr-tr | 027bd2c6c93900a75cac7ac42531c89085f87888 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: "Nasıl yapılır: Bir MenuStrip 'te seçenek düğmelerini görüntüleme (Windows Forms)"
ms.date: 03/30/2017
dev_langs:
- csharp
- vb
helpviewer_keywords:
- MenuStrip [Windows Forms], displaying option buttons
- displaying option buttons [Windows Forms], MenuStrip [Windows Forms]
- option buttons [Windows Forms], displaying in MenuStrip
ms.assetid: 8b596af2-9ff8-4f7b-93d7-cba830e167f4
ms.openlocfilehash: 94d683369edd6583ad8b01c2ce3f393567a5ed75
ms.sourcegitcommit: a97ecb94437362b21fffc5eb3c38b6c0b4368999
ms.translationtype: MT
ms.contentlocale: tr-TR
ms.lasthandoff: 08/13/2019
ms.locfileid: "68971932"
---
# <a name="how-to-display-option-buttons-in-a-menustrip-windows-forms"></a>Nasıl yapılır: Bir MenuStrip 'te seçenek düğmelerini görüntüleme (Windows Forms)
Radyo düğmeleri olarak da bilinen seçenek düğmeleri, kullanıcılar tek seferde yalnızca bir tane seçim yapmak dışında onay kutularına benzerdir. Varsayılan olarak, <xref:System.Windows.Forms.ToolStripMenuItem> sınıfı seçenek düğmesi davranışı sağlamıyorsa, bir <xref:System.Windows.Forms.MenuStrip> denetimdeki menü öğeleri için seçenek düğmesi davranışını uygulamak üzere özelleştirebileceğiniz onay kutusu davranışı sağlar.
Bir menü öğesinin özelliği olduğunda `true`, kullanıcılar bir onay işaretinin görüntülenmesini değiştirmek için öğeye tıklabilirler. <xref:System.Windows.Forms.ToolStripMenuItem.CheckOnClick%2A> <xref:System.Windows.Forms.ToolStripMenuItem.Checked%2A> Özelliği, öğenin geçerli durumunu gösterir. Temel seçenek düğmesi davranışını uygulamak için, bir öğe seçildiğinde, daha önce seçilen öğenin <xref:System.Windows.Forms.ToolStripMenuItem.Checked%2A> özelliğini olarak `false`ayarlamış olmanız gerekir.
Aşağıdaki yordamlar, <xref:System.Windows.Forms.ToolStripMenuItem> sınıfını devralan bir sınıfta bu ve ek işlevselliğin nasıl uygulanacağını açıklamaktadır. Sınıfı, seçenek düğmelerinin seçim davranışını <xref:System.Windows.Forms.ToolStripMenuItem.OnCheckedChanged%2A> ve <xref:System.Windows.Forms.ToolStripMenuItem.OnPaint%2A> görünümünü sağlamak için ve gibi üyeleri geçersiz kılar. `ToolStripRadioButtonMenuItem` Ayrıca, bu sınıf, üst <xref:System.Windows.Forms.ToolStripMenuItem.Enabled%2A> öğe seçilmediği takdirde alt menüdeki seçeneklerin devre dışı bırakılması için özelliği geçersiz kılar.
## <a name="to-implement-option-button-selection-behavior"></a>Seçenek düğmesi seçimi davranışını uygulamak için
1. Öğe seçimini etkinleştirmek için `true` özelliğini'ebaşlatın.<xref:System.Windows.Forms.ToolStripMenuItem.CheckOnClick%2A>
[!code-csharp[ToolStripRadioButtonMenuItem#110](~/samples/snippets/csharp/VS_Snippets_Winforms/ToolStripRadioButtonMenuItem/cs/ToolStripRadioButtonMenuItem.cs#110)]
[!code-vb[ToolStripRadioButtonMenuItem#110](~/samples/snippets/visualbasic/VS_Snippets_Winforms/ToolStripRadioButtonMenuItem/vb/ToolStripRadioButtonMenuItem.vb#110)]
2. Yeni bir <xref:System.Windows.Forms.ToolStripMenuItem.OnCheckedChanged%2A> öğe seçildiğinde, daha önce seçilen öğenin seçimini temizlemek için yöntemini geçersiz kılın.
[!code-csharp[ToolStripRadioButtonMenuItem#120](~/samples/snippets/csharp/VS_Snippets_Winforms/ToolStripRadioButtonMenuItem/cs/ToolStripRadioButtonMenuItem.cs#120)]
[!code-vb[ToolStripRadioButtonMenuItem#120](~/samples/snippets/visualbasic/VS_Snippets_Winforms/ToolStripRadioButtonMenuItem/vb/ToolStripRadioButtonMenuItem.vb#120)]
3. Daha önce seçilmiş olan bir öğeye tıklanmanın seçimi temizlemez olduğundan emin olmak için yönteminigeçersizkılın.<xref:System.Windows.Forms.ToolStripMenuItem.OnClick%2A>
[!code-csharp[ToolStripRadioButtonMenuItem#130](~/samples/snippets/csharp/VS_Snippets_Winforms/ToolStripRadioButtonMenuItem/cs/ToolStripRadioButtonMenuItem.cs#130)]
[!code-vb[ToolStripRadioButtonMenuItem#130](~/samples/snippets/visualbasic/VS_Snippets_Winforms/ToolStripRadioButtonMenuItem/vb/ToolStripRadioButtonMenuItem.vb#130)]
## <a name="to-modify-the-appearance-of-the-option-button-items"></a>Seçenek düğmesi öğelerinin görünüşünü değiştirmek için
1. Sınıfını kullanarak varsayılan onay işaretini bir seçenek düğmesiyle değiştirmek için yönteminigeçersizkılın.<xref:System.Windows.Forms.ToolStripMenuItem.OnPaint%2A> <xref:System.Windows.Forms.RadioButtonRenderer>
[!code-csharp[ToolStripRadioButtonMenuItem#140](~/samples/snippets/csharp/VS_Snippets_Winforms/ToolStripRadioButtonMenuItem/cs/ToolStripRadioButtonMenuItem.cs#140)]
[!code-vb[ToolStripRadioButtonMenuItem#140](~/samples/snippets/visualbasic/VS_Snippets_Winforms/ToolStripRadioButtonMenuItem/vb/ToolStripRadioButtonMenuItem.vb#140)]
2. <xref:System.Windows.Forms.ToolStripMenuItem.OnMouseLeave%2A> <xref:System.Windows.Forms.ToolStripMenuItem.OnMouseUp%2A> Farenin durumunu izlemek<xref:System.Windows.Forms.ToolStripMenuItem.OnMouseDown%2A>için,, ve yöntemlerini geçersiz kılın ve yöntemindoğruseçenekdüğmesidurumunuboyaytığınızdaneminolun.<xref:System.Windows.Forms.ToolStripMenuItem.OnPaint%2A> <xref:System.Windows.Forms.ToolStripMenuItem.OnMouseEnter%2A>
[!code-csharp[ToolStripRadioButtonMenuItem#150](~/samples/snippets/csharp/VS_Snippets_Winforms/ToolStripRadioButtonMenuItem/cs/ToolStripRadioButtonMenuItem.cs#150)]
[!code-vb[ToolStripRadioButtonMenuItem#150](~/samples/snippets/visualbasic/VS_Snippets_Winforms/ToolStripRadioButtonMenuItem/vb/ToolStripRadioButtonMenuItem.vb#150)]
## <a name="to-disable-options-on-a-submenu-when-the-parent-item-is-not-selected"></a>Üst öğe seçilmediğinden bir alt menüdeki seçenekleri devre dışı bırakmak için
1. <xref:System.Windows.Forms.ToolStripMenuItem.Enabled%2A> Öğesinin hem`true` değeri hem de değeri`false`olanbir üst öğesi olduğunda öğenin devre dışı bırakılması için özelliği geçersiz kılın. <xref:System.Windows.Forms.ToolStripMenuItem.Checked%2A> <xref:System.Windows.Forms.ToolStripMenuItem.CheckOnClick%2A>
[!code-csharp[ToolStripRadioButtonMenuItem#160](~/samples/snippets/csharp/VS_Snippets_Winforms/ToolStripRadioButtonMenuItem/cs/ToolStripRadioButtonMenuItem.cs#160)]
[!code-vb[ToolStripRadioButtonMenuItem#160](~/samples/snippets/visualbasic/VS_Snippets_Winforms/ToolStripRadioButtonMenuItem/vb/ToolStripRadioButtonMenuItem.vb#160)]
2. Üst öğenin <xref:System.Windows.Forms.ToolStripMenuItem.CheckedChanged> olayına abone olmak için yönteminigeçersizkılın.<xref:System.Windows.Forms.ToolStripMenuItem.OnOwnerChanged%2A>
[!code-csharp[ToolStripRadioButtonMenuItem#170](~/samples/snippets/csharp/VS_Snippets_Winforms/ToolStripRadioButtonMenuItem/cs/ToolStripRadioButtonMenuItem.cs#170)]
[!code-vb[ToolStripRadioButtonMenuItem#170](~/samples/snippets/visualbasic/VS_Snippets_Winforms/ToolStripRadioButtonMenuItem/vb/ToolStripRadioButtonMenuItem.vb#170)]
3. Üst öğe <xref:System.Windows.Forms.ToolStripMenuItem.CheckedChanged> olayının işleyicisinde, ekranı yeni etkin durumuyla güncelleştirmek için öğeyi geçersiz kılar.
[!code-csharp[ToolStripRadioButtonMenuItem#180](~/samples/snippets/csharp/VS_Snippets_Winforms/ToolStripRadioButtonMenuItem/cs/ToolStripRadioButtonMenuItem.cs#180)]
[!code-vb[ToolStripRadioButtonMenuItem#180](~/samples/snippets/visualbasic/VS_Snippets_Winforms/ToolStripRadioButtonMenuItem/vb/ToolStripRadioButtonMenuItem.vb#180)]
## <a name="example"></a>Örnek
Aşağıdaki kod örneği, tam `ToolStripRadioButtonMenuItem` sınıfı ve seçenek düğmesi davranışını göstermek için bir `Program` <xref:System.Windows.Forms.Form> sınıfı ve sınıfı sağlar.
[!code-csharp[ToolStripRadioButtonMenuItem#000](~/samples/snippets/csharp/VS_Snippets_Winforms/ToolStripRadioButtonMenuItem/cs/ToolStripRadioButtonMenuItem.cs#000)]
[!code-vb[ToolStripRadioButtonMenuItem#000](~/samples/snippets/visualbasic/VS_Snippets_Winforms/ToolStripRadioButtonMenuItem/vb/ToolStripRadioButtonMenuItem.vb#000)]
## <a name="compiling-the-code"></a>Kod Derleniyor
Bu örnek şunları gerektirir:
- System, System. Drawing ve System. Windows. Forms derlemelerine başvurular.
## <a name="see-also"></a>Ayrıca bkz.
- <xref:System.Windows.Forms.MenuStrip>
- <xref:System.Windows.Forms.ToolStripMenuItem>
- <xref:System.Windows.Forms.ToolStripMenuItem.CheckOnClick%2A?displayProperty=nameWithType>
- <xref:System.Windows.Forms.ToolStripMenuItem.Checked%2A?displayProperty=nameWithType>
- <xref:System.Windows.Forms.ToolStripMenuItem.OnCheckedChanged%2A?displayProperty=nameWithType>
- <xref:System.Windows.Forms.ToolStripMenuItem.OnPaint%2A?displayProperty=nameWithType>
- <xref:System.Windows.Forms.ToolStripMenuItem.Enabled%2A?displayProperty=nameWithType>
- <xref:System.Windows.Forms.RadioButtonRenderer>
- [MenuStrip Denetimi](menustrip-control-windows-forms.md)
- [Nasıl yapılır: Özel bir ToolStripRenderer uygulama](how-to-implement-a-custom-toolstriprenderer.md)
| 89.163265 | 600 | 0.83875 | tur_Latn | 0.837445 |
53479b901683da08a8bc8d2313e5423293aa3780 | 2,415 | md | Markdown | .github/CONTRIBUTING.md | CameronJHall/flottbot | b3cdf4a54c47de3034b106e35d5de681d80f987c | [
"Apache-2.0"
] | 2 | 2019-06-03T20:51:05.000Z | 2019-06-04T18:55:51.000Z | .github/CONTRIBUTING.md | CameronJHall/flottbot | b3cdf4a54c47de3034b106e35d5de681d80f987c | [
"Apache-2.0"
] | null | null | null | .github/CONTRIBUTING.md | CameronJHall/flottbot | b3cdf4a54c47de3034b106e35d5de681d80f987c | [
"Apache-2.0"
] | null | null | null | ## Contributing
To ensure that all developers follow the same guidelines for development, we have laid out the following procedure.
### Prerequisites
- [Golang](https://golang.org/dl/) - the source code is written in Go.
- [dep](https://github.com/golang/dep) - our Go dependency management tool.
- Slack API token - obtain a Slack API token for development by creating a bot integration.
### Development Process
- Clone this repository to your Go workspace:
```sh
# Make sure your go paths are set if they aren't already
export GOPATH=$HOME/go
export PATH=$PATH:$GOPATH/bin
# Clone the project
git clone [email protected]:target/flottbot.git $GOPATH/src/github.com/target/flottbot
```
- Build the project dependencies using [dep](https://github.com/golang/dep):
```sh
# Change into the project directory
cd $GOPATH/src/github.com/target/flottbot
# Run dep
dep ensure
```
- Write your code and ensure all tests pass.
```sh
# Checkout a branch for your work
git checkout -b name_of_your_branch
# Code away!
```
- Build the project and run locally:
```sh
# Export your Slack API token (the token below is redacted)
export SLACK_TOKEN=xoxb-xxxxxxxxxxxx-xxxxxxxxxxxxxxxxxxxxxxxx
# Build the binary and run flottbot
go build -o ./flottbot cmd/flottbot/main.go && ./flottbot
```
- If you followed the above steps correctly, you should see output similar to this:
```sh
DEBU[0000] Registering bot...
DEBU[0000] Bot 'flottbot' registered!
DEBU[0000] Searching for rules directory...
DEBU[0000] Fetching all rule files...
DEBU[0000] Reading and parsing rule files...
DEBU[0000] Successfully created rules
DEBU[0000] Registering flottbot to Slack...
DEBU[0000] Found channels!
DEBU[0000] Registering CLI support for flottbot...
Enter CLI mode: hit <Enter>. <Ctrl-C> to exit.
DEBU[0001] Connection established!
```
- You should now see your bot online in your Slack Workspace where you can manually test your changes.
- Satisfied with your contribution? Record your changes in the [changelog](https://github.com/target/flottbot/blob/master/CHANGELOG.md).
- Submit a PR for your changes.
- After the Travis build passes and you have an approved review, we will merge your PR.
- We will tag a release for flottbot when the desired functionality is present and stable.
- Production images of your changes will be published to Docker Hub and new binaries will be built and made available via Github Releases
| 30.56962 | 139 | 0.758178 | eng_Latn | 0.978728 |
5347bf692bcdc07e6efe40a0375161c18528fd6f | 11,565 | md | Markdown | BibWord_FAQ.md | ydhondt/BibWord | 236bb99e65c0d7297f9257aeb6543f7f7cfc67fc | [
"MIT"
] | 1 | 2021-04-06T18:04:08.000Z | 2021-04-06T18:04:08.000Z | BibWord_FAQ.md | ydhondt/BibWord | 236bb99e65c0d7297f9257aeb6543f7f7cfc67fc | [
"MIT"
] | null | null | null | BibWord_FAQ.md | ydhondt/BibWord | 236bb99e65c0d7297f9257aeb6543f7f7cfc67fc | [
"MIT"
] | null | null | null | ## Frequently Asked Questions for BibWord Styles
This pages contains answers regarding questions about the styles published through this project. For questions regarding the citations and bibliography tool in general, check the [developer FAQ](FAQ).
* [Why is a new style not showing up in Word when I add it to the Style directory?](#Q1)
* [In Word 2008, new styles are only added for citations. How can I use the new styles for bibliographies?](#Q2)
* [Why does it take Word so long to show the dropdown list with style names the first time?](#Q3)
* [Why do I get 'BO' instead of a number when using certain styles?](#Q4)
* [Why do certain styles have a * at the end of their name?](#Q5)
* [Can I request to get a certain style?](#Q6)
* [Can I (not) link my in-text citations to their bibliography entries?](#Q7)
* [Can I change the surrounding brackets for in-text citations?](#Q8)
* [How do I get my in-text citations in superscript?](#Q9)
* [How do I convert all my in-text citations to static text in one go?](#Q10)
* [Is there an easy way to get rid of sources which are not cited in the text?](#Q11)
* [How do I set the indentation of my bibliography?](#Q12)
* [Is it possible to group several citations? Currently I have something like (1)(2) and I want (1,2).](#Q13)
* [Only the name of the first author is displayed correctly, all other author names are abbreviated. Is this a bug?](#Q14)
* [When using a numbered style (e.g. IEEE), the number is wrapped over multiple lines. Is this a bug?](#Q15)
* [My in-text citations are displayed in bold. How do I change this?](#Q16)
<a name="Q1"></a>
_**Q:**_ Why is a new style not showing up in Word when I add it to the Style directory?
_**A:** The list of available reference styles gets loaded only once. So when you add a new style to the style directory, you need to restart Word._
<a name="Q2"></a>
_**Q:**_ In Word 2008, new styles are only added for citations. How can I use the new styles for bibliographies?
_**A:** Add the bibliography using one of the four predefined styles. Then go to the citation toolbox and select the style you want. This will update all the citations and bibliographies in your text to the new style._
<a name="Q3"></a>
_**Q:**_ Why does it take Word so long to show the dropdown list with style names the first time?
_**A:** Word has to retrieve the style names of every XSL in the style directory the first time. Hence, the more styles you put in the directory, the more time Word needs to fill the drop down list._
<a name="Q4"></a>
_**Q:**_ Why do I get 'BO' instead of a number when using certain styles?
_**A:** 'BO' is often printed when the BibOrder number is not available. Use the [BibWord Extender](BibWord-Extender) tool on the document to add the missing numbers._
<a name="Q5"></a>
_**Q:**_ Why do certain styles have a **{"**"}** at the end of their name?
_**A:** Although the usage of a **{"**"}** is not mandatory, it often indicates that part of the functionality of the style can only be used in combination with the [BibWord Extender](BibWord-Extender) tool._
<a name="Q6"></a>
_**Q:**_ Can I request to get a certain style?
_**A:** **No.** Using [BibWord](BibWord), you really should try to create the style yourself. Keep in mind that even if you find someone prepared to create the style for you that you will have to provide him/her with detailed information about the formatting guidelines for your style. Messages containing "I need style x." will most likely be ignored._
<a name="Q7"></a>
_**Q:**_ Can I (not) link my in-text citations to their bibliography entries?
_**A:** Yes. Set the value of **{"citation_as_link"}** to 'yes' if you want in-text citations to link to their specific bibliography entry, or to any other value if you do not._
<a name="Q8"></a>
_**Q:**_ Can I change the surrounding brackets for in-text citations?
_**A:** Yes. You can change the surrounding brackets by changing the values of **{"openbracket"}** and **{"closebracket"}**_
```xml
<openbracket>(</openbracket>
<closebracket>)</closebracket>
```
<a name="Q9"></a>
_**Q:**_ How do I get my in-text citations in superscript?
_**A:** In-text citations inherit the style of their surroundings. Only limited formatting (bold, underline, italic) can be applied to them through the reference style. For any further formatting, such as superscript, a character style has to be applied to all CITATION fields._
_The following macro creates a character style called **In-Text Citation** if it does not yet exist. When the style is newly created, it sets the font to superscript. Then the style is applied to all CITATION fields in the document. By changing/updating the style **In-Text Citation** you can then update the formatting of all citations_
```vbscript
Sub ApplyCitationStyle()
Dim stylename As String
Dim exists As Boolean
Dim s As Style
Dim fld As Field
stylename = "In-Text Citation"
' Check if the style already exists.
exists = False
For Each s In ActiveDocument.Styles
If s.NameLocal = stylename Then
exists = True
Exit For
End If
Next
' If the style did not exist yet, create it.
If exists = False Then
Set s = ActiveDocument.Styles.Add(stylename, wdStyleTypeCharacter)
s.BaseStyle = ActiveDocument.Styles(wdStyleDefaultParagraphFont).BaseStyle
s.Font.Superscript = True
End If
' Now that the style really exists, select it.
Set s = ActiveDocument.Styles(stylename)
' Apply the style to all in-text citations.
For Each fld In ActiveDocument.Fields
If fld.Type = wdFieldCitation Then
fld.Select
Selection.Style = s
End If
Next
End Sub
```
<a name="Q10"></a>
_**Q:**_ How do I convert all my in-text citations to static text in one go?
_**A:** You can use the following macro to convert all in-text citations:_
```vbscript
Sub CitationsToStaticText()
Dim fld As Field
' Go over all stories, including main, footnotes, ...
For Each sr In ActiveDocument.StoryRanges
' Find all citation fields and convert them to static text.
For Each fld In sr.Fields
If fld.Type = wdFieldCitation Then
fld.Select
WordBasic.BibliographyCitationToText
End If
Next
Next
End Sub
```
<a name="Q11"></a>
_**Q:**_ Is there an easy way to get rid of sources which are not cited in the text?
_**A:** You can use the following macro to remove all uncited sources from a document:_
```vbscript
Sub RemoveUnusedCitations()
' Get the number of sources.
idx = ActiveDocument.Bibliography.Sources.Count
' Remmove unused sources starting from the last one.
Do While (idx > 0)
If ActiveDocument.Bibliography.Sources(idx).Cited = False Then
ActiveDocument.Bibliography.Sources(idx).Delete
End If
idx = idx - 1
Loop
End Sub
```
<a name="Q12"></a>
_**Q:**_ How do I set the indentation of my bibliography?
_**A:** Add a bibliography to your document. Open the 'Styles' pane {"(CTRL+ALT+SHIFT+S)"} and look for a style called 'Bibliography' (or a localized translation of the word 'Bibliography'). Change the indentation settings there. That way, whenever your bibliography gets updated, the indentation will remain correct._
<a name="Q13"></a>
_**Q:**_ Is it possible to group several citations? Currently I have something like (1)(2) and I want (1,2).
_**A:** Yes. You can add a second source to a citation by using the '\m' switch and the tag of the source you want to add. In Word 2007, if you want to add a source with tag 'Bee99' to an existing citation, right click the citation and select 'Edit Field...'. It will show you something like 'CITATION Gup97 \l 2060'. To add the extra source, change it to 'CITATION Gup97 \l 2060 \m Bee99'. For more information, also see the Microsoft Office online help topic on the [CITATION](http://office.microsoft.com/en-us/word/HA102157071033.aspx) field code._
_Alternatively, you can put your cursor inside any in-text citation, then go to 'References' tab in the ribbon and click 'Insert Citation'._
_To change the separator between two grouped in-text citations, BibWord uses the **separator** element._
<a name="Q14"></a>
_**Q:**_ Only the name of the first author is displayed correctly, all other author names are abbreviated. Is this a bug?
_**A:** No. You probably made a mistake when entering the different author names. You should enter them one by one in the dialog that comes up when clicking the "Edit..." button next to the author field. That way you will not make a mistake._
_If you really want to enter them as a string, then be aware that the correct format is "Last1, First1 Middle1; Last2, First2 Middle2; ...". So the names are separated by a ";" while name parts are separated by a ","._
_Note that there is a bug in Word where sometimes the name conversion goes wrong. For more info, see [release:here](27834)._
<a name="Q15"></a>
_**Q:**_ When using a numbered style (e.g. IEEE), the number is wrapped over multiple lines. Is this a bug?
_**A:** No. Numbered styles are mostly represented using a 2 column table where the first column contains the number and the second column contains the text. The text wrap you see is caused by the first column not being wide enough. You can simple solve this by positioning your cursor on the the table border between the first and second column and drag it to the right._
_This can also be used to add extra white space after the number if you set the halign element to left of the first column._
<a name="Q16"></a>
_**Q:**_ My in-text citations are displayed in bold. How do I change this?
_**A:** If you link your in-text citation to your bibliography, Word formats the link using the 'Heading 2 Character style'. So if that style is configured to use bold, so will the in-text citation. Assuming you cannot or do not want to change that style, there are two possible solutions:_
* _Disable linking between in-text citations and bibliographies. This can be done easily be setting the value of **citation_as_link** to 'no' in the xsl file._
* _Format each in-text citation with another character style. This way you will be able to keep using the links between in-text citations and bibliographies. To ease this job, you could use the following macro which you can run every time you insert an in-text citation or once at the end._
```vbscript
Sub ApplyCitationStyle()
Dim stylename As String
Dim exists As Boolean
Dim s As Style
Dim fld As Field
stylename = "In-Text Citation"
' Check if the style already exists.
exists = False
For Each s In ActiveDocument.Styles
If s.NameLocal = stylename Then
exists = True
Exit For
End If
Next
' If the style did not exist yet, create it.
If exists = False Then
Set s = ActiveDocument.Styles.Add(stylename, wdStyleTypeCharacter)
s.BaseStyle = ActiveDocument.Styles(wdStyleDefaultParagraphFont).BaseStyle
s.Font.Bold = False
End If
' Now that the style really exists, select it.
Set s = ActiveDocument.Styles(stylename)
' Apply the style to all in-text citations.
For Each fld In ActiveDocument.Fields
If fld.Type = wdFieldCitation Then
fld.Select
Selection.Style = s
End If
Next
End Sub
```
| 50.282609 | 551 | 0.709555 | eng_Latn | 0.997062 |
5348097b19c940a923a2045702cc295c38769bef | 2,524 | md | Markdown | README.md | jrsinclair/js-circle-chart | 8379059a7d0a25771ed00c18484843997f3fc812 | [
"MIT"
] | 12 | 2015-06-12T15:53:11.000Z | 2021-06-04T08:40:18.000Z | README.md | v1ckxy/js-circle-chart | 8379059a7d0a25771ed00c18484843997f3fc812 | [
"MIT"
] | 2 | 2015-12-16T21:54:36.000Z | 2018-12-16T19:04:23.000Z | README.md | v1ckxy/js-circle-chart | 8379059a7d0a25771ed00c18484843997f3fc812 | [
"MIT"
] | 6 | 2015-07-17T01:11:07.000Z | 2018-12-07T18:02:47.000Z | # Circle Chart
A very simple (responsive) circular chart/dial using Raphäel.
To use, include Raphäel, then pass an element with a number in it to the constructor. What you do with the CSS is up to you.
To give an example, you might do something like the following:
```html
<!doctype html>
<html lang="en">
<head>
<meta charset="UTF-8">
<title>Circle Chart</title>
<style>
.circle-chart { width: 25%; position: relative; }
.circle-chart__text { position: absolute; width: 100%; height: 100%; text-align: center; left: 0; top: 0; line-height: 4; font-family: sans-serif; }
</style>
</head>
<body>
<!-- Number goes inside a HTML element -->
<div class="circle-chart">
85%
</div>
<!-- Load the required libraries -->
<script src="//cdnjs.cloudflare.com/ajax/libs/raphael/2.1.2/raphael-min.js"></script>
<script src="js/circle-chart.js"></script>
<!-- Create the chart -->
<script>
var el = document.querySelector('.circle-chart');
new CircleChart(el);
</script>
</body>
</html>
```
## Options
You can pass an options object as a second parameter to the constructor. The defaults are something like the following:
```javascript
{
stroke: 20, // Width of the circle (in pixels)
maxVal: 100, // Maximum value for the chart
colour: '#56b7d6', // Colour of the circle (yes, with British spelling)
animationSpeed: 1000, // Time in ms for animations,
edgeWidth: 0, // Width of the border (zero means no border)
edgeGap: undefined, // Gap between border and chart. Defaults to edgeWidth.
edgeColour: '#56b7d6', // Colour of the border.
trackColour: 'transparent', // Colour of the track beneath the chart.
edgeClass: 'edge', // class name for the edge
trackClass: 'track', // class name for the track
pathClass: 'path', // class name for the path
pathEasing: 'ease-in-out' // follows the naming convention of Raphael.easing_formulas
}
```
Released under the [MIT License](http://opensource.org/licenses/MIT). | 38.830769 | 170 | 0.669176 | eng_Latn | 0.920054 |
53484b7f39663e10f6909ba618477ca804abb6e7 | 5,562 | md | Markdown | articles/virtual-machine-scale-sets/virtual-machine-scale-sets-manage-powershell.md | jkudo/azure-docs.ja-jp | 91f0b0c63c4e01743cd750160d36fdb3a9d7c6a7 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/virtual-machine-scale-sets/virtual-machine-scale-sets-manage-powershell.md | jkudo/azure-docs.ja-jp | 91f0b0c63c4e01743cd750160d36fdb3a9d7c6a7 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | articles/virtual-machine-scale-sets/virtual-machine-scale-sets-manage-powershell.md | jkudo/azure-docs.ja-jp | 91f0b0c63c4e01743cd750160d36fdb3a9d7c6a7 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Azure PowerShell を使用して仮想マシン スケール セットを管理する
description: 仮想マシン スケール セットを管理するための一般的な Azure PowerShell コマンドレット (インスタンスを起動および停止したり、スケール セットの容量を変更したりする方法など)。
author: cynthn
tags: azure-resource-manager
ms.assetid: d35fa77a-de96-4ccd-a332-eb181d1f4273
ms.service: virtual-machine-scale-sets
ms.topic: conceptual
ms.date: 05/29/2018
ms.author: cynthn
ms.openlocfilehash: cc83c8b73c73b2aa70bc36bad175e5c19c1ab700
ms.sourcegitcommit: 5397b08426da7f05d8aa2e5f465b71b97a75550b
ms.translationtype: HT
ms.contentlocale: ja-JP
ms.lasthandoff: 01/19/2020
ms.locfileid: "76275711"
---
# <a name="manage-a-virtual-machine-scale-set-with-azure-powershell"></a>Azure PowerShell を使用して仮想マシン スケール セットを管理する
仮想マシン スケール セットのライフサイクルを通して、1 つ以上の管理タスクを実行することが必要になる場合があります。 さらに、各種ライフサイクルのタスクを自動化するスクリプトを作成するほうが便利な場合もあります。 この記事では、これらのタスクを実行するために使用できる一般的な Azure PowerShell コマンドレットのいくつかについて詳細に説明します。
仮想マシン スケール セットを作成する必要がある場合は、[Azure PowerShell でスケール セットを作成](quick-create-powershell.md)できます。
[!INCLUDE [updated-for-az.md](../../includes/updated-for-az.md)]
## <a name="view-information-about-a-scale-set"></a>スケール セットに関する情報を表示する
スケール セットに関する全体的な情報を表示するには、[Get-AzVmss](/powershell/module/az.compute/get-azvmss) を使用します。 次の例では、*myResourceGroup* リソース グループ内の *myScaleSet* という名前のスケール セットに関する情報を取得します。 独自の名前を次のように入力します。
```powershell
Get-AzVmss -ResourceGroupName "myResourceGroup" -VMScaleSetName "myScaleSet"
```
## <a name="view-vms-in-a-scale-set"></a>スケール セットの VM を表示する
スケール セット内の VM インスタンスの一覧を表示するには、[Get-AzVmssVM](/powershell/module/az.compute/get-azvmssvm) を使用します。 次の例では、*myScaleSet* という名前のスケール セットおよび *myResourceGroup* リソース グループ内のすべての VM インスタンスを一覧表示します。 これらの名前には独自の値を指定します。
```powershell
Get-AzVmssVM -ResourceGroupName "myResourceGroup" -VMScaleSetName "myScaleSet"
```
特定の VM インスタンスに関する追加情報を表示するには、[Get-AzVmssVM](/powershell/module/az.compute/get-azvmssvm) に `-InstanceId` パラメーターを追加し、表示するインスタンスを指定します。 次の例では、*myScaleSet* という名前のスケール セットおよび *myResourceGroup* リソース グループ内の VM インスタンス *0* に関する情報を表示します。 独自の名前を次のように入力します。
```powershell
Get-AzVmssVM -ResourceGroupName "myResourceGroup" -VMScaleSetName "myScaleSet" -InstanceId "0"
```
## <a name="change-the-capacity-of-a-scale-set"></a>スケール セットの容量を変更する
前のコマンドでは、スケール セットと VM インスタンスに関する情報を表示しました。 スケール セット内のインスタンスの数を増やすか、または減らすために、その容量を変更できます。 スケール セットは、必要な数の VM を自動的に作成または削除した後、アプリケーション トラフィックを受信するようにそれらの VM を構成します。
最初に、[Get-AzVmss](/powershell/module/az.compute/get-azvmss) を使用してスケール セット オブジェクトを作成し、次に `sku.capacity` に新しい値を指定します。 容量の変更を適用するには、[Update-AzVmss](/powershell/module/az.compute/update-azvmss) を使用します。 次の例では、*myResourceGroup* リソース グループ内の *myScaleSet* を *5* インスタンスの容量に更新します。 独自の値を次のように指定します。
```powershell
# Get current scale set
$vmss = Get-AzVmss -ResourceGroupName "myResourceGroup" -VMScaleSetName "myScaleSet"
# Set and update the capacity of your scale set
$vmss.sku.capacity = 5
Update-AzVmss -ResourceGroupName "myResourceGroup" -Name "myScaleSet" -VirtualMachineScaleSet $vmss
```
スケール セットの容量を更新するには数分かかります。 スケール セットの容量を減らした場合は、最も大きなインスタンス ID を持つ VM が最初に削除されます。
## <a name="stop-and-start-vms-in-a-scale-set"></a>スケール セット内の VM を停止および起動する
スケール セット内の 1 つ以上の VM を停止するには、[Stop-AzVmss](/powershell/module/az.compute/stop-azvmss) を使用します。 `-InstanceId` パラメーターでは、停止する VM を 1 つ以上指定できます。 インスタンス ID を指定しない場合は、スケール セット内のすべての VM が停止されます。 複数の VM を停止するには、各インスタンス ID をコンマで区切ります。
次の例では、*myScaleSet* という名前のスケール セットおよび *myResourceGroup* リソース グループ内のインスタンス *0* を停止します。 独自の値を次のように指定します。
```powershell
Stop-AzVmss -ResourceGroupName "myResourceGroup" -VMScaleSetName "myScaleSet" -InstanceId "0"
```
既定では、停止された VM は割り当て解除されるため、コンピューティング料金は発生しません。 停止されたときに VM をプロビジョニングされた状態のままにする場合は、前のコマンドに `-StayProvisioned` パラメーターを追加します。 停止された VM がプロビジョニングされたままになる場合は、通常のコンピューティング料金が発生します。
### <a name="start-vms-in-a-scale-set"></a>スケール セット内の VM を起動する
スケール セット内の 1 つ以上の VM を起動するには、[Start-AzVmss](/powershell/module/az.compute/start-azvmss) を使用します。 `-InstanceId` パラメーターでは、起動する VM を 1 つ以上指定できます。 インスタンス ID を指定しない場合は、スケール セット内のすべての VM が起動されます。 複数の VM を起動するには、各インスタンス ID をコンマで区切ります。
次の例では、*myScaleSet* という名前のスケール セットおよび *myResourceGroup* リソース グループ内のインスタンス *0* を起動します。 独自の値を次のように指定します。
```powershell
Start-AzVmss -ResourceGroupName "myResourceGroup" -VMScaleSetName "myScaleSet" -InstanceId "0"
```
## <a name="restart-vms-in-a-scale-set"></a>スケール セット内の VM を再起動する
スケール セット内の 1 つ以上の VM を再起動するには、[Restart-AzVmss](/powershell/module/az.compute/restart-azvmss) を使用します。 `-InstanceId` パラメーターでは、再起動する VM を 1 つ以上指定できます。 インスタンス ID を指定しない場合は、スケール セット内のすべての VM が再起動されます。 複数の VM を再起動するには、各インスタンス ID をコンマで区切ります。
次の例では、*myScaleSet* という名前のスケール セットおよび *myResourceGroup* リソース グループ内のインスタンス *0* を再起動します。 独自の値を次のように指定します。
```powershell
Restart-AzVmss -ResourceGroupName "myResourceGroup" -VMScaleSetName "myScaleSet" -InstanceId "0"
```
## <a name="remove-vms-from-a-scale-set"></a>スケール セットから VM を削除する
スケール セット内の 1 つ以上の VM を削除するには、[Remove-AzVmss](/powershell/module/az.compute/remove-azvmss) を使用します。 `-InstanceId` パラメーターでは、削除する VM を 1 つ以上指定できます。 インスタンス ID を指定しない場合は、スケール セット内のすべての VM が削除されます。 複数の VM を削除するには、各インスタンス ID をコンマで区切ります。
次の例では、*myScaleSet* という名前のスケール セットおよび *myResourceGroup* リソース グループ内のインスタンス *0* を削除します。 独自の値を次のように指定します。
```powershell
Remove-AzVmss -ResourceGroupName "myResourceGroup" -VMScaleSetName "myScaleSet" -InstanceId "0"
```
## <a name="next-steps"></a>次のステップ
スケール セットに対する他の一般的なタスクとして、[アプリケーションのデプロイ](virtual-machine-scale-sets-deploy-app.md)や [VM インスタンスのアップグレード](virtual-machine-scale-sets-upgrade-scale-set.md)があります。 また、Azure PowerShell を使用して、[自動スケールの規則を構成する](virtual-machine-scale-sets-autoscale-overview.md)こともできます。
| 51.027523 | 285 | 0.800431 | yue_Hant | 0.891788 |
53499a34d0f32ca21e07dbb3e0997baff3dbf4dd | 1,047 | md | Markdown | posts/cambodia-2019-1.md | jerrielu/sporule | b2df31ae055223709936db939514d2d31401934d | [
"MIT"
] | null | null | null | posts/cambodia-2019-1.md | jerrielu/sporule | b2df31ae055223709936db939514d2d31401934d | [
"MIT"
] | null | null | null | posts/cambodia-2019-1.md | jerrielu/sporule | b2df31ae055223709936db939514d2d31401934d | [
"MIT"
] | null | null | null | ---
title: "高棉热浪 1/4"
author: "九姨"
date: "2020-07-05"
categories: "游记"
tags: "柬埔寨,暹粒"
coverImage: "images/P1040665.jpg"
---
>旅游狂热爱好者九姨的东南亚第一站是柬埔寨暹粒。而对我来说这次更加新奇的体验是——跟团游！
## 行程总览
## 吴哥时代酒店
>到达暹粒时已接近傍晚。街上朴素又如繁星一般的霓虹灯深得我心。在马路上稳占C位的突突车，提醒着大家此刻正身处东南亚。
>酒店离市区大约需要15-20分钟车程，但是宽敞古朴，还有一个露天大泳池。
>酒店大堂有柬埔寨传统乐器的现场表演。
>房间宽敞整洁。
>洗手间干湿分离。
>次日一早，来到酒店餐厅用自助早餐。
## 女王宫
>早餐后来到位于荔枝山附近的女王宫，又称班迭斯雷。
>女王宫始建于公元十世纪，大规模地使用了红色砂岩，建筑上满是精致的浮雕，被誉为“吴哥艺术宝石”。
>女王宫最具辨识度当属其精致的砂岩楣石和山形墙。巨大的山形墙上雕刻的是印度史诗中的故事，跨立在门框之上，显得气势磅礴。
>女王宫坐西向东，共有三层红色砂岩围墙。
>石门内有三座钟形寺塔。据说，中间最高的寺塔里供奉的是湿婆神，其南是梵天神，其北则是毗湿奴神。
>团餐和购物点就不一一赘述了。下期景点密集预警，真是叫人期待呢！ | 16.359375 | 59 | 0.754537 | yue_Hant | 0.119269 |
5349d4afdcb43b6d1f794494c43997bc3d4e378a | 1,683 | md | Markdown | docs/framework/data/adonet/sql/linq/inheritance-support.md | TomekLesniak/docs.pl-pl | 3373130e51ecb862641a40c5c38ef91af847fe04 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/data/adonet/sql/linq/inheritance-support.md | TomekLesniak/docs.pl-pl | 3373130e51ecb862641a40c5c38ef91af847fe04 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/framework/data/adonet/sql/linq/inheritance-support.md | TomekLesniak/docs.pl-pl | 3373130e51ecb862641a40c5c38ef91af847fe04 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: Obsługa dziedziczenia
ms.date: 03/30/2017
ms.assetid: 19bb2794-b4e7-402e-8307-1d1517381a08
ms.openlocfilehash: 7673e69458d5c1af854747c43ba463332a9cd588
ms.sourcegitcommit: 5b475c1855b32cf78d2d1bbb4295e4c236f39464
ms.translationtype: MT
ms.contentlocale: pl-PL
ms.lasthandoff: 09/24/2020
ms.locfileid: "91158256"
---
# <a name="inheritance-support"></a>Obsługa dziedziczenia
[!INCLUDE[vbtecdlinq](../../../../../../includes/vbtecdlinq-md.md)] obsługuje *Mapowanie pojedynczej tabeli*. Innymi słowy, pełna Hierarchia dziedziczenia jest przechowywana w pojedynczej tabeli bazy danych. Tabela zawiera spłaszczoną Unię wszystkich możliwych kolumn danych dla całej hierarchii. (Unia jest wynikiem łączenia dwóch tabel w jedną tabelę, w której znajdują się wiersze, które znajdowały się w jednej z oryginalnych tabel). Każdy wiersz ma wartości null w kolumnach, które nie mają zastosowania do typu wystąpienia reprezentowanego przez wiersz.
Strategia mapowania jednej tabeli jest najprostszą reprezentacją dziedziczenia i zapewnia dobrą charakterystykę wydajności dla wielu różnych kategorii zapytań.
Aby zaimplementować to mapowanie w programie [!INCLUDE[vbtecdlinq](../../../../../../includes/vbtecdlinq-md.md)] , należy określić atrybuty i właściwości atrybutów w klasie głównej hierarchii dziedziczenia. Aby uzyskać więcej informacji, zobacz [How to: map dziedziczenia hierarchii](how-to-map-inheritance-hierarchies.md).
Deweloperzy korzystający z programu Visual Studio mogą również używać Object Relational Designer do mapowania hierarchii dziedziczenia.
## <a name="see-also"></a>Zobacz też
- [Informacje uzupełniające](background-information.md)
| 67.32 | 561 | 0.801545 | pol_Latn | 0.999869 |
5349fbf3c0744c5e56b984eacf03c784d9328c85 | 1,753 | md | Markdown | _posts/2022-04-02-Sobre_mim.md | Gleynner/gleynner.github.io | d4fd3e812c3e6ccdccdb95ab1e96a8796bbb567c | [
"MIT"
] | null | null | null | _posts/2022-04-02-Sobre_mim.md | Gleynner/gleynner.github.io | d4fd3e812c3e6ccdccdb95ab1e96a8796bbb567c | [
"MIT"
] | null | null | null | _posts/2022-04-02-Sobre_mim.md | Gleynner/gleynner.github.io | d4fd3e812c3e6ccdccdb95ab1e96a8796bbb567c | [
"MIT"
] | null | null | null | ---
layout: page
title: 'Sobre mim'
gh-repo: daattali/beautiful-jekyll
gh-badge:
- star
- fork
- follow
tags: null
---
<style> body {text-align: justify} </style>
Graduado em Engenharia de Produção e mestre em Estatística Aplicada e Biometria pela Universidade Federal de Viçosa. Atualmente, sou colaborador no Laboratório de Análises e Pesquisas em Estatística Aplicada (LAPEA), onde desempenho atividades de pesquisa e análise de dados. Durante minha jornada neste laboratório tive a oportunidade atuar como coordenador de RH e auxiliar na tomada de decisões, junto à coordenação geral, além de ministrar curso de capacitação (tanto para membros quanto para estudantes de graduação), atuar no planejamento de reuniões e organização de eventos.
Minha formação me proporcionou uma base teórica sólida em campos como inferência estatística, probabilidade e matemática, além de uma visão sistemática e lógica de negócios. Aliado à minha paixão por análise de dados, isto me ajudou a desenvolver e a buscar novos conhecimentos em programação. Tenho experiência com a linguagem R e, atualmente, desenvolvendo habilidades em Python. Por meio de tais realizações, tornou-se possível a aplicação de meus conhecimentos em problemas do mundo real, auxiliando na tomada de decisão por meio de técnicas, como, análise exploratória, visualização de dados, estatística inferencial e algoritmos de aprendizado de máquina e inteligência artificial.
<br>
**Nome:** Gleynner Ghiotto Lima de Menezes <br>
**Endereço:** Viçosa - Minas Gerais <br>
**Telefone/Whatsapp:** (31) 99498-1925 <br>
**E-mail:** [email protected] / [email protected] <br>
**LinkedIn:** https://www.linkedin.com/in/gleynner-ghiotto-558b2914b/ <br>
| 70.12 | 687 | 0.782088 | por_Latn | 0.999888 |
534a35eba92837871f344e572afa6fc5297c98ab | 112 | md | Markdown | services/censor/ChangeLog.md | zhaoxiangchun/jdcloud-sdk-go | abade87e78106bc9ce437cf871c6a1ce8c42242d | [
"Apache-2.0"
] | null | null | null | services/censor/ChangeLog.md | zhaoxiangchun/jdcloud-sdk-go | abade87e78106bc9ce437cf871c6a1ce8c42242d | [
"Apache-2.0"
] | null | null | null | services/censor/ChangeLog.md | zhaoxiangchun/jdcloud-sdk-go | abade87e78106bc9ce437cf871c6a1ce8c42242d | [
"Apache-2.0"
] | null | null | null | # 更新历史 #
API版本：1.0.1
|发布时间|版本号|更新|说明|
|---|---|---|---|
|2020-10-10|1.0.1|支持音视频异步检测||
|2019-09-20|1.0.0|初始版本||
| 14 | 29 | 0.517857 | yue_Hant | 0.201826 |
534b72132d09550049ce68a97d5c2dbdbe208474 | 1,562 | md | Markdown | 05.Being_Diplomatic.md | AleksandrKugushev/EmailCorespondenceTips | b9b269b9289686711d2a9aa89460620e6abfc585 | [
"MIT"
] | 1 | 2016-11-18T14:01:08.000Z | 2016-11-18T14:01:08.000Z | 05.Being_Diplomatic.md | AleksandrKugushev/EmailCorespondenceTips | b9b269b9289686711d2a9aa89460620e6abfc585 | [
"MIT"
] | null | null | null | 05.Being_Diplomatic.md | AleksandrKugushev/EmailCorespondenceTips | b9b269b9289686711d2a9aa89460620e6abfc585 | [
"MIT"
] | null | null | null | Being Diplomatic
================
##### Language tools:
1. modals: would, could, might, may
- We need to ... - We might need to ...
- We’ll miss the deadline - We may miss the deadline
- Email that report me - Could/Would you email that report to me?
2. qualifiers: slight, a bit, rather, a few
- We have a problem - We have a slight problem
- We are expecting a delay - We are expecting a short delay
- I was disappointed to ...- I was rather disappointed to ...
- We have found a serious bug - We have found a rather serious bug
3. softeners: I’m afraid, to be honest, with respect, just,
unfortunately, it seems, there seems to be, it appears
4. passive forms: it was assumed, it was considered
- I consider ...-ing ... - It was considered to ...
- We assumed that ... - It was assumed that ...
5. continuous forms: I was wondering, we are aiming
6. words and phrases with less negative meaning
- A problem - An issue
- No - Not really
- I haven’t done/finished - I haven’t been able to do/finish
- I can’t do/won’t do - I am unable to do/I am not able to do/ I
am not in a position to do
- Reject - Unable to accept
- Unhappy - Not entirely/totally/completely happy
7. restrictive phrases: at the moment, at this stage, at this point, so
far, just, yet
8. ’yes... but... ’ statements
- I understand your concern, but I am not in a position to ...
- I see your point, but our budget it too limited to ...
| 26.033333 | 72 | 0.628681 | eng_Latn | 0.999831 |
534b94749d7d127ba287fa3a7ba386b64bb53ada | 484 | md | Markdown | README.md | ElotlMX/ccoss-2020-esquite | 468694ddef202dde17060a32fe6628543d960404 | [
"CC-BY-4.0"
] | null | null | null | README.md | ElotlMX/ccoss-2020-esquite | 468694ddef202dde17060a32fe6628543d960404 | [
"CC-BY-4.0"
] | null | null | null | README.md | ElotlMX/ccoss-2020-esquite | 468694ddef202dde17060a32fe6628543d960404 | [
"CC-BY-4.0"
] | null | null | null | # Sobre el desarrollo de tecnologías libres para lenguas mexicanas. Caso: Esquite
Presentación mostrada en el CCOSS 2020 sobre Esquite
<a rel="license" href="http://creativecommons.org/licenses/by/4.0/"><img alt="Licencia Creative Commons" style="border-width:0" src="https://i.creativecommons.org/l/by/4.0/80x15.png" /></a><br />Esta obra está bajo una <a rel="license" href="http://creativecommons.org/licenses/by/4.0/">Licencia Creative Commons Atribución 4.0 Internacional</a>.
| 80.666667 | 346 | 0.758264 | spa_Latn | 0.58906 |
534bcfcb29b14e6c1e95eee851513c0d50e1b8cf | 875 | md | Markdown | blog/react-native/release/index.md | HwangTaehyun/HwangTaehyun.github.io | a69d1e2474a619507079075b71f2a74213e67d08 | [
"MIT"
] | 1 | 2022-03-26T17:54:38.000Z | 2022-03-26T17:54:38.000Z | blog/react-native/release/index.md | HwangTaehyun/HwangTaehyun.github.io | a69d1e2474a619507079075b71f2a74213e67d08 | [
"MIT"
] | null | null | null | blog/react-native/release/index.md | HwangTaehyun/HwangTaehyun.github.io | a69d1e2474a619507079075b71f2a74213e67d08 | [
"MIT"
] | null | null | null | ---
layout: post
title: "react native release build error"
subtitle: "Error: Duplicate resources"
type: "Year in Review"
blog: true
text: true
author: "Taehyun"
post-header: true
order: 9
---
# ❎ 에러 발생
아래의 명령어로 react-native js를 bundling 한 다음,
{% highlight js %}
$ react-native bundle --platform android --dev false --entry-file index.js --bundle-output android/app/src/main/assets/index.android.bundle --assets-dest android/app/src/main/res
{% endhighlight %}
android 폴더에 들어가서 아래와 같이 빌드 명령어를 치면 안드로이드 앱을 빌드할 수 있다.
{% highlight js %}
$ ./gradlew assembleRelease
{% endhighlight %}
종종 리소스 중복 에러를 만날 수 있는데, 아래 해결법에서와 같이 중복된 resource를 지워주면 해결된다!
{% highlight js %}
* What went wrong:
Execution failed for task ':app:mergeReleaseResources'.
{% endhighlight %}
# 🌟 해결
에러 문구 그대로 resource가 겹쳐서 생긴 문제인데
/android/app/src/main/res 폴더에 들어가서 drawable 폴더를 삭제하고 다시 실행하면 문제가 해결된다.
| 22.435897 | 178 | 0.722286 | kor_Hang | 0.998926 |
534c83b75204fa8c461bb74bfbcf751a109307df | 13,694 | md | Markdown | desktop-src/WinAuto/uiauto-supporttextcontroltype.md | weijiechai/win32 | 6b707eecd167607ce836a92096c337def7a5b43a | [
"CC-BY-4.0",
"MIT"
] | 552 | 2019-08-20T00:08:40.000Z | 2022-03-30T18:25:35.000Z | desktop-src/WinAuto/uiauto-supporttextcontroltype.md | weijiechai/win32 | 6b707eecd167607ce836a92096c337def7a5b43a | [
"CC-BY-4.0",
"MIT"
] | 1,143 | 2019-08-21T20:17:47.000Z | 2022-03-31T20:24:39.000Z | desktop-src/WinAuto/uiauto-supporttextcontroltype.md | weijiechai/win32 | 6b707eecd167607ce836a92096c337def7a5b43a | [
"CC-BY-4.0",
"MIT"
] | 1,287 | 2019-08-20T05:37:48.000Z | 2022-03-31T20:22:06.000Z | ---
title: Text Control Type
description: This topic provides information about Microsoft UI Automation support for the Text control type.
ms.assetid: 69a3b243-8ee5-48e4-a01e-c7ad69b9a3aa
keywords:
- UI Automation,support for Text control type
- UI Automation,Text control type
- UI Automation,tree structure for Text control type
- UI Automation,properties for Text control type
- UI Automation,control patterns for Text control type
- UI Automation,events for Text control type
- tree structures,Text control type
- properties,Text control type
- control patterns,Text control type
- events,Text control type
- support for Text control type
- Text control type
- control types,tree structure for Text control type
- control types,control patterns for Text control type
- control types,support for Text
- control types,Text
ms.topic: article
ms.date: 05/31/2018
---
# Text Control Type
This topic provides information about Microsoft UI Automation support for the **Text** control type.
A text control is a basic user interface item that represents a piece of text on the screen.
The following sections define the required UI Automation tree structure, properties, control patterns, and events for the **Text** control type. The UI Automation requirements apply to all tree controls where the UI framework/platform integrates UI Automation support for control types and control patterns.
This topic contains the following sections.
- [Typical Tree Structure](#typical-tree-structure)
- [Relevant Properties](#relevant-properties)
- [Required Control Patterns](#required-control-patterns)
- [Required Events](#required-events)
- [Related topics](#related-topics)
## Typical Tree Structure
The following table depicts a typical control and content view of the UI Automation tree that pertains to text controls and describes what can be contained in each view. For more information about the UI Automation tree, see [UI Automation Tree Overview](uiauto-treeoverview.md).
| Control View | Content View |
|--------------|--------------|
| <ul><li>Text</li></ul> | <ul><li>Text (if content)</li></ul> |
A text control can be used alone as a label or as static text on a form. It can also be contained within the structure of one of the following items:
- [DataItem](uiauto-supportdataitemcontroltype.md)
- [ListItem](uiauto-supportlistitemcontroltype.md)
- [TreeItem](uiauto-supporttreeitemcontroltype.md)
Text controls might not appear in the content view of the UI Automation tree because text is often displayed through the **Name** property of another control. For example, the text used to label a combo box control is exposed through the control's **Name** property. Because the combo box control is in the content view of the UI Automation tree, the text control need not be there. Text controls may have children in the content view if there is an embedded object such as a hyperlink.
## Relevant Properties
The following table lists the UI Automation properties whose value or definition is especially relevant to the text controls. For more information about UI Automation properties, see [Retrieving Properties from UI Automation Elements](uiauto-propertiesforclients.md).
| UI Automation Property | Value | Notes |
|---------------------------------------------------------------------------------------------------------------------|------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| [**UIA\_AutomationIdPropertyId**](uiauto-automation-element-propids.md) | See notes. | The value of this property must be unique among all peer elements in the raw view of the UI Automation tree. |
| [**UIA\_BoundingRectanglePropertyId**](uiauto-automation-element-propids.md) | See notes. | The outermost rectangle that contains the whole control. |
| [**UIA\_ClickablePointPropertyId**](uiauto-automation-element-propids.md) | See notes. | Supported if there is a bounding rectangle. If not every point within the bounding rectangle is clickable, and the element performs specialized hit testing, override and provide a clickable point. |
| [**UIA\_ControlTypePropertyId**](uiauto-automation-element-propids.md) | **Text** | |
| [**UIA\_IsContentElementPropertyId**](uiauto-automation-element-propids.md) | Depends | The text control is content if it contains information not exposed in another control's Name property. |
| [**UIA\_IsControlElementPropertyId**](uiauto-automation-element-propids.md) | TRUE | The text control must always be a control. |
| [**UIA\_IsKeyboardFocusablePropertyId**](uiauto-automation-element-propids.md) | See notes. | If the control can receive keyboard focus, it must support this property. |
| [**UIA\_LabeledByPropertyId**](uiauto-automation-element-propids.md) | NULL | Text controls do not have a static text label. |
| [**UIA\_LocalizedControlTypePropertyId**](uiauto-automation-element-propids.md) | See notes. | Localized string corresponding to the **Text** control type. The default value is "text" for en-US or English (United States). |
| [**UIA\_NamePropertyId**](uiauto-automation-element-propids.md) | See notes. | The name of a text control can be the text that it displays. However, if the control also supports the [Text](uiauto-implementingtextandtextrange.md) pattern, and the text is extensive, don't use the full text content as the **Name** value. Instead, provide a **Name** value that is shorter, derived from other properties of your control. |
## Required Control Patterns
The following table lists the UI Automation control patterns required to be supported by text controls. For more information on control patterns, see [UI Automation Control Patterns Overview](uiauto-controlpatternsoverview.md).
| Control Pattern | Support | Notes |
|---------------------------------------------------------|---------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| [**IGridItemProvider**](/windows/desktop/api/UIAutomationCore/nn-uiautomationcore-igriditemprovider) | Depends | If the text control is contained within a table control, the [GridItem](uiauto-implementinggriditem.md) control pattern must be supported. |
| [**ITableItemProvider**](/windows/desktop/api/UIAutomationCore/nn-uiautomationcore-itableitemprovider) | Depends | If the text control is contained within a table control, the [TableItem](uiauto-implementingtableitem.md) control pattern must be supported. |
| [**ITextProvider**](/windows/desktop/api/UIAutomationCore/nn-uiautomationcore-itextprovider) | Depends | Text should support the [Text](uiauto-implementingtextandtextrange.md) control pattern for better accessibility; however, it is not required. The Text control pattern is useful when the text has rich style and attributes (for example, color, bold, and italics). |
| [**IValueProvider**](/windows/desktop/api/UIAutomationCore/nn-uiautomationcore-ivalueprovider) | Never | A text control never supports the [Value](uiauto-implementingvalue.md) control pattern. If the text is editable, it is the [Edit](uiauto-supporteditcontroltype.md) control type. |
## Required Events
The following table lists the UI Automation events that text controls are required to support. For more information on events, see [UI Automation Events Overview](uiauto-eventsoverview.md).
| UI Automation Event | Notes |
|---------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------|
| [**UIA\_AutomationFocusChangedEventId**](uiauto-event-ids.md) | |
| [**UIA\_BoundingRectanglePropertyId**](uiauto-automation-element-propids.md) property-changed event. | |
| [**UIA\_IsEnabledPropertyId**](uiauto-automation-element-propids.md) property-changed event. | If the control supports the [**IsEnabled**](uiauto-automation-element-propids.md) property, it must support this event. |
| [**UIA\_IsOffscreenPropertyId**](uiauto-automation-element-propids.md) property-changed event. | If the control supports the [**IsOffscreen**](uiauto-automation-element-propids.md) property, it must support this event. |
| [**UIA\_NamePropertyId**](uiauto-automation-element-propids.md) property-changed event. | |
| [**UIA\_StructureChangedEventId**](uiauto-event-ids.md) | |
| [**UIA\_Text\_TextChangedEventId**](uiauto-event-ids.md) | If the control supports the [Text](uiauto-implementingtextandtextrange.md) control pattern, it must support this event. |
## Related topics
<dl> <dt>
**Conceptual**
</dt> <dt>
[UI Automation Control Types Overview](uiauto-controltypesoverview.md)
</dt> <dt>
[UI Automation Overview](uiauto-uiautomationoverview.md)
</dt> </dl>
| 93.794521 | 486 | 0.462027 | eng_Latn | 0.884667 |
534d059c7a764e796d8e03dd372c4415b379547c | 3,649 | md | Markdown | README.md | dmdhrumilmistry/TermuxScripts | decec7841f25cd5f6fb37f44e30cf58323f1fd78 | [
"MIT"
] | null | null | null | README.md | dmdhrumilmistry/TermuxScripts | decec7841f25cd5f6fb37f44e30cf58323f1fd78 | [
"MIT"
] | null | null | null | README.md | dmdhrumilmistry/TermuxScripts | decec7841f25cd5f6fb37f44e30cf58323f1fd78 | [
"MIT"
] | null | null | null | # TermuxScripts
```bash
===============================
___ ___ __
| |__ |__) |\/| | | \_/
| |___ | \ | | \__/ / \
__ __ __ __ ___ __
/__` / ` |__) | |__) | /__`
.__/ \__, | \ | | | .__/
______________________________
Project by
dmdhrumilmistry
______________________________
```
## Scripts
- Installation Scripts
|Script Name|Description|
|:---------:|:----------|
|[Beef](https://github.com/dmdhrumilmistry/TermuxScripts/blob/main/Installation/Beef/beef-installer.sh)|Installs Beef Framework on Termux|
|[cryptography](https://github.com/dmdhrumilmistry/TermuxScripts/blob/main/Installation/cryptography.sh)|Helps to install cryptography python package|
|<details><summary>[Install Linux Distros](https://github.com/dmdhrumilmistry/TermuxScripts/tree/main/Installation/linux_distros)</summary><br>[Ubuntu](https://github.com/dmdhrumilmistry/TermuxScripts/blob/main/Installation/linux_distros/ubuntu.sh)</details>|Installation Scripts to install linux distros in Termux without Root|
|[TOR WebServer](https://github.com/dmdhrumilmistry/TermuxScripts/blob/main/Installation/tor_webserver.sh)|Installs and configures apache2 webserver to host a website on TOR network|
|[Ngrok](https://github.com/dmdhrumilmistry/TermuxScripts/blob/main/Installation/ngrok_installation.sh)|Installs ngrok on Termux|
|[GooglePhish](https://github.com/dmdhrumilmistry/TermuxScripts/blob/main/Installation/GooglePhish.sh)|Installs Google Phishing Page Project on Termux|
## Installation
- Install **TermuxScripts** project
```bash
bash -c "$(curl -fsSL https://github.com/dmdhrumilmistry/TermuxScripts/blob/main/installer.sh?raw=True)"
```
- Provide `termux-scripts.py` permission for execution if missing
```bash
chmod +x TermuxScripts/termux-scripts.py
```
## Usage
- Start UI using
```bash
python termux-scripts.py
```
_OR_
```bash
./termux-scripts.py
```
- Use help menu for options
```
>> help
+---------+----------------------------------------------+
| Command | Description |
+---------+----------------------------------------------+
| help | prints commands along with description |
| exit | exits TermuxScripts console |
| clear | clears console |
| show | print options in current directory |
| select | selects a directory, eg. select Installation |
| back | move one directory back |
| run | runs a script eg. run GooglePhish.sh |
+---------+----------------------------------------------+
```
- To run `GooglePhish.sh` scripts from `Installation` scripts use:
```bash
>> show
+--------------+-----------------------+---------------+
| Dir | Files | Dirs |
+--------------+-----------------------+---------------+
| . | installer.sh | .git |
| | | Installation |
| Installation | GooglePhish.sh | Beef |
| | cryptography.sh | linux_distros |
| | ngrok_installation.sh | |
| | tor_webserver.sh | |
+--------------+-----------------------+---------------+
>> select Installation
>> run GooglePhish.sh
```
## License
[MIT License](https://github.com/dmdhrumilmistry/TermuxScripts/blob/main/LICENSE)
## Contributions
- Fork this project
- Update project
- Create Pull Request
- PR will be merged after reviewing the commits
| 35.427184 | 330 | 0.555221 | yue_Hant | 0.406961 |
534d7706a5df125e341a8b2326f4ddb67214b6dd | 79 | md | Markdown | _pages/team.md | auAIforum/auAIforum.github.io | 6c6a5f0e2dcadfed2559113140c8cf63e1475c1e | [
"MIT"
] | null | null | null | _pages/team.md | auAIforum/auAIforum.github.io | 6c6a5f0e2dcadfed2559113140c8cf63e1475c1e | [
"MIT"
] | null | null | null | _pages/team.md | auAIforum/auAIforum.github.io | 6c6a5f0e2dcadfed2559113140c8cf63e1475c1e | [
"MIT"
] | null | null | null | ---
title: "AI Team"
layout: splash
permalink: /team/
---
### It's coming soon
| 11.285714 | 20 | 0.620253 | eng_Latn | 0.724908 |
534e5c630a3486d49534e1a48db37d603d640412 | 826 | md | Markdown | VBA/Outlook-VBA/articles/namespace-accounts-property-outlook.md | oloier/VBA-content | 6b3cb5769808b7e18e3aff55a26363ebe78e4578 | [
"CC-BY-4.0",
"MIT"
] | 584 | 2015-09-01T10:09:09.000Z | 2022-03-30T15:47:20.000Z | VBA/Outlook-VBA/articles/namespace-accounts-property-outlook.md | oloier/VBA-content | 6b3cb5769808b7e18e3aff55a26363ebe78e4578 | [
"CC-BY-4.0",
"MIT"
] | 585 | 2015-08-28T20:20:03.000Z | 2018-08-31T03:09:51.000Z | VBA/Outlook-VBA/articles/namespace-accounts-property-outlook.md | oloier/VBA-content | 6b3cb5769808b7e18e3aff55a26363ebe78e4578 | [
"CC-BY-4.0",
"MIT"
] | 590 | 2015-09-01T10:09:09.000Z | 2021-09-27T08:02:27.000Z | ---
title: NameSpace.Accounts Property (Outlook)
keywords: vbaol11.chm778
f1_keywords:
- vbaol11.chm778
ms.prod: outlook
api_name:
- Outlook.NameSpace.Accounts
ms.assetid: 80e969ea-d2cc-966d-5fe4-68d59951b5c9
ms.date: 06/08/2017
---
# NameSpace.Accounts Property (Outlook)
Returns an **[Accounts](accounts-object-outlook.md)** collection object that represents all the **[Account](account-object-outlook.md)** objects in the current profile. Read-only.
## Syntax
_expression_ . **Accounts**
_expression_ A variable that represents a **NameSpace** object.
## Remarks
If Outlook is running in sessionless mode, **Accounts** returns an **Accounts** collection with **[Accounts.Count](accounts-count-property-outlook.md)** equal to 0.
## See also
#### Concepts
[NameSpace Object](namespace-object-outlook.md)
| 21.179487 | 180 | 0.745763 | eng_Latn | 0.589411 |
534e662d808edf869507bddbda49af983e8637f1 | 400 | md | Markdown | _captures/TLP2_20190730.md | Meteoros-Floripa/meteoros.floripa.br | 7d296fb8d630a4e5fec9ab1a3fb6050420fc0dad | [
"MIT"
] | 5 | 2020-01-22T17:44:06.000Z | 2020-01-26T17:57:58.000Z | _captures/TLP2_20190730.md | Meteoros-Floripa/site | 764cf471d85a6b498873610e4f3b30efd1fd9fae | [
"MIT"
] | null | null | null | _captures/TLP2_20190730.md | Meteoros-Floripa/site | 764cf471d85a6b498873610e4f3b30efd1fd9fae | [
"MIT"
] | 2 | 2020-05-19T17:06:27.000Z | 2020-09-04T00:00:43.000Z | ---
layout: capture
label: 20190730
station: TLP2
date: 2019-07-30 21:32:36
preview: TLP2/2019/201907/20190730/stack.jpg
capturas:
- imagem: TLP2/2019/201907/20190730/M20190730_213236_TLP_2P.jpg
- imagem: TLP2/2019/201907/20190730/M20190731_045018_TLP_2P.jpg
- imagem: TLP2/2019/201907/20190730/M20190731_045800_TLP_2P.jpg
- imagem: TLP2/2019/201907/20190730/M20190731_050035_TLP_2P.jpg
---
| 30.769231 | 65 | 0.79 | yue_Hant | 0.066794 |
534ebb7b07c0bbd70a1047ed4f16ee7f4067f450 | 121 | md | Markdown | README.md | DavidWhitlock/PortlandStateAndroid | 6ba7541a5a9227b24f25bcca9a71248321ebb9e2 | [
"Apache-2.0"
] | null | null | null | README.md | DavidWhitlock/PortlandStateAndroid | 6ba7541a5a9227b24f25bcca9a71248321ebb9e2 | [
"Apache-2.0"
] | 1 | 2020-08-13T04:06:31.000Z | 2020-08-13T04:23:03.000Z | README.md | DavidWhitlock/PortlandStateAndroid | 6ba7541a5a9227b24f25bcca9a71248321ebb9e2 | [
"Apache-2.0"
] | null | null | null | # PortlandStateAndroid
Android source code and examples for Advanced Programming with Java at Portland State University.
| 40.333333 | 97 | 0.85124 | eng_Latn | 0.905479 |
534eca83f41bf9c1e5858a0ff3b14124fa7a4666 | 10,971 | md | Markdown | README.md | MunDeuksoo/mediadevices | 5a1bd11087c4172b1ff873fdb30db68d6b1ea4f5 | [
"MIT"
] | 361 | 2019-12-15T06:06:12.000Z | 2022-03-31T13:14:33.000Z | README.md | MunDeuksoo/mediadevices | 5a1bd11087c4172b1ff873fdb30db68d6b1ea4f5 | [
"MIT"
] | 270 | 2019-12-05T05:50:18.000Z | 2022-03-31T10:34:40.000Z | README.md | MunDeuksoo/mediadevices | 5a1bd11087c4172b1ff873fdb30db68d6b1ea4f5 | [
"MIT"
] | 60 | 2020-02-19T09:57:05.000Z | 2022-03-31T10:16:59.000Z | <h1 align="center">
<br>
Pion MediaDevices
<br>
</h1>
<h4 align="center">Go implementation of the <a href="https://developer.mozilla.org/en-US/docs/Web/API/MediaDevices">MediaDevices</a> API</h4>
<p align="center">
<a href="https://pion.ly/slack"><img src="https://img.shields.io/badge/join-us%20on%20slack-gray.svg?longCache=true&logo=slack&colorB=brightgreen" alt="Slack Widget"></a>
<a href="https://github.com/pion/mediadevices/actions"><img src="https://github.com/pion/mediadevices/workflows/CI/badge.svg?branch=master" alt="Build status"></a>
<a href="https://pkg.go.dev/github.com/pion/mediadevices"><img src="https://godoc.org/github.com/pion/mediadevices?status.svg" alt="GoDoc"></a>
<a href="https://codecov.io/gh/pion/mediadevices"><img src="https://codecov.io/gh/pion/mediadevices/branch/master/graph/badge.svg" alt="Coverage Status"></a>
<a href="LICENSE"><img src="https://img.shields.io/badge/License-MIT-yellow.svg" alt="License: MIT"></a>
</p>
<br>
`mediadevices` provides access to media input devices like cameras, microphones, and screen capture. It can also be used to encode your video/audio stream to various codec selections. `mediadevices` abstracts away the complexities of interacting with things like hardware and codecs allowing you to focus on building appilcations, interacting only with an amazingly simple, easy, and elegant API!
## Install
`go get -u github.com/pion/mediadevices`
## Usage
The following snippet shows how to capture a camera stream and store a frame as a jpeg image:
```go
package main
import (
"image/jpeg"
"os"
"github.com/pion/mediadevices"
"github.com/pion/mediadevices/pkg/prop"
// This is required to register camera adapter
_ "github.com/pion/mediadevices/pkg/driver/camera"
// Note: If you don't have a camera or your adapters are not supported,
// you can always swap your adapters with our dummy adapters below.
// _ "github.com/pion/mediadevices/pkg/driver/videotest"
)
func main() {
stream, _ := mediadevices.GetUserMedia(mediadevices.MediaStreamConstraints{
Video: func(constraint *mediadevices.MediaTrackConstraints) {
// Query for ideal resolutions
constraint.Width = prop.Int(600)
constraint.Height = prop.Int(400)
},
})
// Since track can represent audio as well, we need to cast it to
// *mediadevices.VideoTrack to get video specific functionalities
track := stream.GetVideoTracks()[0]
videoTrack := track.(*mediadevices.VideoTrack)
defer videoTrack.Close()
// Create a new video reader to get the decoded frames. Release is used
// to return the buffer to hold frame back to the source so that the buffer
// can be reused for the next frames.
videoReader := videoTrack.NewReader(false)
frame, release, _ := videoReader.Read()
defer release()
// Since frame is the standard image.Image, it's compatible with Go standard
// library. For example, capturing the first frame and store it as a jpeg image.
output, _ := os.Create("frame.jpg")
jpeg.Encode(output, frame, nil)
}
```
## More Examples
* [Webrtc](/examples/webrtc) - Use Webrtc to create a realtime peer-to-peer video call
* [Face Detection](/examples/facedetection) - Use a machine learning algorithm to detect faces in a camera stream
* [RTP Stream](examples/rtp) - Capture camera stream, encode it in H264/VP8/VP9, and send it to a RTP server
* [HTTP Broadcast](/examples/http) - Broadcast camera stream through HTTP with MJPEG
* [Archive](/examples/archive) - Archive H264 encoded video stream from a camera
## Available Media Inputs
| Input | Linux | Mac | Windows |
| :--------: | :---: | :-: | :-----: |
| Camera | ✔️ | ✔️ | ✔️ |
| Microphone | ✔️ | ✔️ | ✔️ |
| Screen | ✔️ | ✔️ | ✔️ |
By default, there's no media input registered. This decision was made to allow you to play only what you need. Therefore, you need to import the associated packages for the media inputs. For example, if you want to use a camera, you need to import the camera package as a side effect:
```go
import (
...
_ "github.com/pion/mediadevices/pkg/driver/camera"
)
```
## Available Codecs
In order to encode your video/audio, `mediadevices` needs to know what codecs that you want to use and their parameters. To do this, you need to import the associated packages for the codecs, and add them to the codec selector that you'll pass to `GetUserMedia`:
```go
package main
import (
"github.com/pion/mediadevices"
"github.com/pion/mediadevices/pkg/codec/x264" // This is required to use H264 video encoder
_ "github.com/pion/mediadevices/pkg/driver/camera" // This is required to register camera adapter
)
func main() {
// configure codec specific parameters
x264Params, _ := x264.NewParams()
x264Params.Preset = x264.PresetMedium
x264Params.BitRate = 1_000_000 // 1mbps
codecSelector := mediadevices.NewCodecSelector(
mediadevices.WithVideoEncoders(&x264Params),
)
mediaStream, _ := mediadevices.GetUserMedia(mediadevices.MediaStreamConstraints{
Video: func(c *mediadevices.MediaTrackConstraints) {},
Codec: codecSelector, // let GetUsermedia know available codecs
})
}
```
Since `mediadevices` doesn't implement the video/audio codecs, it needs to call the codec libraries from the system through cgo. Therefore, you're required to install the codec libraries before you can use them in `mediadevices`. In the next section, it shows a list of available codecs, where the packages are defined (documentation linked), and installation instructions.
Note: we do not provide recommendations on choosing one codec or another as it is very complex and can be subjective.
### Video Codecs
#### x264
A free software library and application for encoding video streams into the H.264/MPEG-4 AVC compression format.
* Package: [github.com/pion/mediadevices/pkg/codec/x264](https://pkg.go.dev/github.com/pion/mediadevices/pkg/codec/x264)
* Installation:
* Mac: `brew install x264`
* Ubuntu: `apt install libx264-dev`
#### mmal
A framework to enable H264 hardware encoding for Raspberry Pi or boards that use VideoCore GPUs.
* Package: [github.com/pion/mediadevices/pkg/codec/mmal](https://pkg.go.dev/github.com/pion/mediadevices/pkg/codec/mmal)
* Installation: no installation needed, mmal should come built in Raspberry Pi devices
#### openh264
A codec library which supports H.264 encoding and decoding. It is suitable for use in real time applications.
* Package: [github.com/pion/mediadevices/pkg/codec/openh264](https://pkg.go.dev/github.com/pion/mediadevices/pkg/codec/openh264)
* Installation: no installation needed, included as a static binary
#### vpx
A free software video codec library from Google and the Alliance for Open Media that implements VP8/VP9 video coding formats.
* Package: [github.com/pion/mediadevices/pkg/codec/vpx](https://pkg.go.dev/github.com/pion/mediadevices/pkg/codec/vpx)
* Installation:
* Mac: `brew install libvpx`
* Ubuntu: `apt install libvpx-dev`
#### vaapi
An open source API that allows applications such as VLC media player or GStreamer to use hardware video acceleration capabilities (currently support VP8/VP9).
* Package: [github.com/pion/mediadevices/pkg/codec/vaapi](https://pkg.go.dev/github.com/pion/mediadevices/pkg/codec/vaapi)
* Installation:
* Ubuntu: `apt install libva-dev`
### Audio Codecs
#### opus
A totally open, royalty-free, highly versatile audio codec.
* Package: [github.com/pion/mediadevices/pkg/codec/opus](https://pkg.go.dev/github.com/pion/mediadevices/pkg/codec/opus)
* Installation:
* Mac: `brew install opus`
* Ubuntu: `apt install libopus-dev`
## Benchmark
Result as of Nov 4, 2020 with Go 1.14 on a Raspberry pi 3, `mediadevices` can produce video, encode, send across network, and decode at **720p, 30 fps with < 500 ms latency**.
The test was taken by capturing a camera stream, decoding the raw frames, encoding the video stream with mmal, and sending the stream through Webrtc.
## FAQ
### Failed to find the best driver that fits the constraints
`mediadevices` provides an automated driver discovery through `GetUserMedia` and `GetDisplayMedia`. The driver discover algorithm works something like:
1. Open all registered drivers
2. Get all properties (property describes what a driver is capable of, e.g. resolution, frame rate, etc.) from opened drivers
3. Find the best property that meets the criteria
So, when `mediadevices` returns `failed to find the best driver that fits the constraints` error, one of the following conditions might have occured:
* Driver was not imported as a side effect in your program, e.g. `import _ github.com/pion/mediadevices/pkg/driver/camera`
* Your constraint is too strict that there's no driver can fullfil your requirements. In this case, you can try to turn up the debug level by specifying the following environment variable: `export PION_LOG_DEBUG=all` to see what was too strict and tune that.
* Your driver is not supported/implemented. In this case, you can either let us know (file an issue) and wait for the maintainers to implement it. Or, you can implement it yourself and register it through `RegisterDriverAdapter`
### Failed to find vpx/x264/mmal/opus codecs
Since `mediadevices` uses cgo to access video/audio codecs, it needs to find these libraries from the system. To accomplish this, [pkg-config](https://www.freedesktop.org/wiki/Software/pkg-config/) is used for library discovery.
If you see the following error message at compile time:
```
# pkg-config --cflags -- vpx
Package vpx was not found in the pkg-config search path.
Perhaps you should add the directory containing `vpx.pc'
to the PKG_CONFIG_PATH environment variable
No package 'vpx' found
pkg-config: exit status 1
```
There are 2 common problems:
* The required codec library is not installed (vpx in this example). In this case, please refer to the [available codecs](#available-codecs).
* Pkg-config fails to find the `.pc` files for this codec ([reference](https://people.freedesktop.org/~dbn/pkg-config-guide.html#using)). In this case, you need to find where the codec library's `.pc` is stored, and let pkg-config knows with: `export PKG_CONFIG_PATH=/path/to/directory`.
## Community
Pion has an active community on the [Slack](https://pion.ly/slack).
Follow the [Pion Twitter](https://twitter.com/_pion) for project updates and important WebRTC news.
We are always looking to support **your projects**. Please reach out if you have something to build!
If you need commercial support or don't want to use public methods you can contact us at [[email protected]](mailto:[email protected])
## Contributing
Check out the **[contributing wiki](https://github.com/pion/webrtc/wiki/Contributing)** to join the group of amazing people making this project possible:
* [Lukas Herman](https://github.com/lherman-cs) - _Original Author_
* [Atsushi Watanabe](https://github.com/at-wat) - _VP8, Screencast, etc._
## License
MIT License - see [LICENSE](LICENSE) for full text
| 46.096639 | 396 | 0.748701 | eng_Latn | 0.959749 |
534ed513d39a293abd5a2737a522571a9a210ca9 | 964 | md | Markdown | _posts/2015-10-01-Diane-Harbridge-Autumnwinter-2015-Diane-Harbridge-Trixie.md | eudanceyou/eudanceyou.github.io | 9d81bccab5dd52c95c99495c5800da809ea32ed7 | [
"MIT"
] | null | null | null | _posts/2015-10-01-Diane-Harbridge-Autumnwinter-2015-Diane-Harbridge-Trixie.md | eudanceyou/eudanceyou.github.io | 9d81bccab5dd52c95c99495c5800da809ea32ed7 | [
"MIT"
] | null | null | null | _posts/2015-10-01-Diane-Harbridge-Autumnwinter-2015-Diane-Harbridge-Trixie.md | eudanceyou/eudanceyou.github.io | 9d81bccab5dd52c95c99495c5800da809ea32ed7 | [
"MIT"
] | null | null | null | ---
layout: post
date: '2015-10-01'
title: "Diane Harbridge Autumnwinter 2015 Diane Harbridge Trixie"
category: Diane Harbridge Autumnwinter 2015
tags: [Diane Harbridge Autumnwinter 2015]
---
### Diane Harbridge Autumnwinter 2015 Diane Harbridge Trixie
Just **$389.99**
###
<a href="https://www.antebrands.com/en/diane-harbridge-autumnwinter-2015/64133-diane-harbridge-trixie.html"><img src="//static.msromantic.com/148212/diane-harbridge-trixie.jpg" alt="Diane Harbridge Trixie" style="width:100%;" /></a>
<!-- break --><a href="https://www.antebrands.com/en/diane-harbridge-autumnwinter-2015/64133-diane-harbridge-trixie.html"><img src="//static.msromantic.com/148211/diane-harbridge-trixie.jpg" alt="Diane Harbridge Trixie" style="width:100%;" /></a>
Buy it: [https://www.antebrands.com/en/diane-harbridge-autumnwinter-2015/64133-diane-harbridge-trixie.html](https://www.antebrands.com/en/diane-harbridge-autumnwinter-2015/64133-diane-harbridge-trixie.html)
| 60.25 | 246 | 0.76556 | yue_Hant | 0.076281 |
534ee8a479a9bb7f38b0cf032d5d81b2c812cecd | 3,270 | md | Markdown | docs/atl/reference/iquickactivateimpl-class.md | psimn/cpp-docs.zh-cn | 0f8c59315e1753eb94b113dac7c38b3b70486ad7 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/atl/reference/iquickactivateimpl-class.md | psimn/cpp-docs.zh-cn | 0f8c59315e1753eb94b113dac7c38b3b70486ad7 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/atl/reference/iquickactivateimpl-class.md | psimn/cpp-docs.zh-cn | 0f8c59315e1753eb94b113dac7c38b3b70486ad7 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: IQuickActivateImpl 类
ms.date: 11/04/2016
f1_keywords:
- IQuickActivateImpl
- ATLCTL/ATL::IQuickActivateImpl
- ATLCTL/ATL::IQuickActivateImpl::GetContentExtent
- ATLCTL/ATL::IQuickActivateImpl::QuickActivate
- ATLCTL/ATL::IQuickActivateImpl::SetContentExtent
helpviewer_keywords:
- activating ATL controls
- controls [ATL], activating
- IQuickActivateImpl class
- IQuickActivate ATL implementation
ms.assetid: aa80c056-1041-494e-b21d-2acca7dc27ea
ms.openlocfilehash: 2169686ebbf756c5caf9232f5031532c62ac8265
ms.sourcegitcommit: fcb48824f9ca24b1f8bd37d647a4d592de1cc925
ms.translationtype: MT
ms.contentlocale: zh-CN
ms.lasthandoff: 08/15/2019
ms.locfileid: "69495508"
---
# <a name="iquickactivateimpl-class"></a>IQuickActivateImpl 类
此类将容器的控件初始化组合为单个调用。
> [!IMPORTANT]
> 此类及其成员不能用于在 Windows 运行时中执行的应用程序。
## <a name="syntax"></a>语法
```
template <class T>
class ATL_NO_VTABLE IQuickActivateImpl : public IQuickActivate
```
#### <a name="parameters"></a>参数
*T*<br/>
派生自`IQuickActivateImpl`的类。
## <a name="members"></a>成员
### <a name="public-methods"></a>公共方法
|名称|描述|
|----------|-----------------|
|[IQuickActivateImpl::GetContentExtent](#getcontentextent)|检索正在运行的控件的当前显示大小。|
|[IQuickActivateImpl::QuickActivate](#quickactivate)|快速初始化正在加载的控件。|
|[IQuickActivateImpl::SetContentExtent](#setcontentextent)|通知控制容器分配给它的显示空间量。|
## <a name="remarks"></a>备注
在单个调用中组合初始化时， [IQuickActivate](/windows/win32/api/ocidl/nn-ocidl-iquickactivate)接口可帮助容器避免延迟加载控件。 `QuickActivate`方法允许容器传递指向 [QACONTAINER](/windows/win32/api/ocidl/ns-ocidl-qacontainer) 结构的指针，该结构保存指向控件所需的所有接口的指针。 返回时，控件向后传递一个指向[QACONTROL](/windows/win32/api/ocidl/ns-ocidl-qacontrol)结构的指针，该结构包含指向其自己的接口的指针，这些接口由容器使用。 类`IQuickActivateImpl`提供的`IQuickActivate`默认实现，并通过`IUnknown`在调试版本中将信息发送到转储设备来实现。
**相关文章**[Atl 教程](../../atl/active-template-library-atl-tutorial.md)，[创建 atl 项目](../../atl/reference/creating-an-atl-project.md)
## <a name="inheritance-hierarchy"></a>继承层次结构
`IQuickActivate`
`IQuickActivateImpl`
## <a name="requirements"></a>要求
**标头：** atlctl
## <a name="getcontentextent"></a>IQuickActivateImpl::GetContentExtent
检索正在运行的控件的当前显示大小。
```
STDMETHOD(GetContentExtent)(LPSIZEL pSize);
```
### <a name="remarks"></a>备注
该大小用于控件的完全呈现，并且是在 HIMETRIC 单元中指定的。
请参阅 Windows SDK 中的[IQuickActivate：： GetContentExtent](/windows/win32/api/ocidl/nf-ocidl-iquickactivate-getcontentextent) 。
## <a name="quickactivate"></a>IQuickActivateImpl::QuickActivate
快速初始化正在加载的控件。
```
STDMETHOD(QuickActivate)(
QACONTAINER* pQACont,
QACONTROL* pQACtrl);
```
### <a name="remarks"></a>备注
结构包含指向控件所需的接口的指针以及某些环境属性的值。 返回后，控件将传递一个指向[QACONTROL](/windows/win32/api/ocidl/ns-ocidl-qacontrol)结构的指针，该结构包含指向其自己的容器所需接口的指针以及其他状态信息。
请参阅 Windows SDK 中的[IQuickActivate：： QuickActivate](/windows/win32/api/ocidl/nf-ocidl-iquickactivate-quickactivate) 。
## <a name="setcontentextent"></a>IQuickActivateImpl::SetContentExtent
通知控制容器分配给它的显示空间量。
```
STDMETHOD(SetContentExtent)(LPSIZEL pSize);
```
### <a name="remarks"></a>备注
大小是在 HIMETRIC 单位中指定的。
请参阅 Windows SDK 中的[IQuickActivate：： SetContentExtent](/windows/win32/api/ocidl/nf-ocidl-iquickactivate-setcontentextent) 。
## <a name="see-also"></a>请参阅
[CComControl 类](../../atl/reference/ccomcontrol-class.md)<br/>
[类概述](../../atl/atl-class-overview.md)
| 28.189655 | 393 | 0.761162 | yue_Hant | 0.747675 |
534ef88506c2c7595285c5ec2a2a177c3cb8d8c3 | 3,678 | md | Markdown | packages/icon/README.md | jhlav/react-md | b083f715d2d6ce2b2d116196f36ec2df141535fd | [
"MIT"
] | null | null | null | packages/icon/README.md | jhlav/react-md | b083f715d2d6ce2b2d116196f36ec2df141535fd | [
"MIT"
] | null | null | null | packages/icon/README.md | jhlav/react-md | b083f715d2d6ce2b2d116196f36ec2df141535fd | [
"MIT"
] | null | null | null | # @react-md/icon
Create icons using a font-icon library like material-icons or font-awesome or
plain old accessible SVG icons. There are also a few additional helpers to
creating animating rotating icons and separating text from an icon.
## Installation
```sh
$ npm install --save @react-md/icon
```
It is also recommended to install the other packages if you have not done so:
```sh
$ npm install --save @react-md/theme @react-md/typography
```
## Pre-made material icons
If you would like to have access to all material icons as existing components
instead of having to manually remember the correct `children` to provide or the
correct `path`, you can install the `@react-md/material-icons` package. This
will include **all** material icons as font and SVGs.
<!-- DOCS_REMOVE -->
## Documentation
You should check out the
[full documentation](https://react-md.dev/packages/icon) for live examples and
more customization information, but an example usage is shown below.
<!-- DOCS_REMOVE_END -->
## Usage
Even though the `FontIcon` and `SVGIcon` components are the "main" exports for
this package, they are more utility components and probably won't be used much
once you set up your own icon system. The _real_ exports are going to be the
`TextIconSpacing` and `IconRotator` components.
The `TextIconSpacing` component is used to add spacing between an icon and some
"text" where the text can be any renderable element. The `IconRotator` is used
to animate an icon rotation such as expander or collapse icons.
```tsx
import React, { Fragment } from "react";
import { render } from "react-dom";
import { FontIcon, TextIconSpacing } from "@react-md/icon";
import { Text } from "@react-md/typography";
// the Text component is optional, it'll just add better typography
// than normal text.
const App = () => (
<Fragment>
// creates an icon spaced before the "Go Home" text
<TextIconSpacing icon={<FontIcon>home</FontIcon>}>
<Text>Go Home</Text>
</TextIconSpacing>
// creates an icon spaced after the "Go Home" text
<TextIconSpacing icon={<FontIcon>home</FontIcon>} iconAfter>
<Text>Go Home</Text>
</TextIconSpacing>
// it can also be combined
<TextIconSpacing icon={<FontIcon>arrow_back</FontIcon>}>
<TextIconSpacing icon={<FontIcon>home</FontIcon>} iconAfter>
<Text>Go Home</Text>
</TextIconSpacing>
</TextIconSpacing>
</Fragment>
);
render(<App />, document.getElementById("root"));
```
This package's icon component usage is really only helpful when generating icon
components through an external script or using font icons. However, here are a
few examples of using the `FontIcon` and `SVGIcon` components:
```tsx
import React, { Fragment } from "react";
import { render } from "react-dom";
import { FontIcon, SVGIcon } from "@react-md/icon";
// When using font icons, you'll need to make sure they icon fonts have been
// correctly included in your app. Check out the documentation site for more
// info
const App = () => (
<Fragment>
<FontIcon>home</FontIcon>
<FontIcon iconClassName="fa fa-github" aria-label="Github" />
<SVGIcon title="Face">
<path d="M9 11.75c-.69 0-1.25.56-1.25 1.25s.56 1.25 1.25 1.25 1.25-.56 1.25-1.25-.56-1.25-1.25-1.25zm6 0c-.69 0-1.25.56-1.25 1.25s.56 1.25 1.25 1.25 1.25-.56 1.25-1.25-.56-1.25-1.25-1.25zM12 2C6.48 2 2 6.48 2 12s4.48 10 10 10 10-4.48 10-10S17.52 2 12 2zm0 18c-4.41 0-8-3.59-8-8 0-.29.02-.58.05-.86 2.36-1.05 4.23-2.98 5.21-5.37C11.07 8.33 14.05 10 17.42 10c.78 0 1.53-.09 2.25-.26.21.71.33 1.47.33 2.26 0 4.41-3.59 8-8 8z" />
</SVGIcon>
</Fragment>
);
render(<App />, document.getElementById("root"));
```
| 36.058824 | 431 | 0.708809 | eng_Latn | 0.956412 |
534fca02a2640f2e6658fee71365b3aa20994899 | 936 | md | Markdown | C/G0LD/README.md | DevHedronYT/GameDev | 96b7bc2e9090eafdd8f04a0e0142c8c61f27456d | [
"CC0-1.0"
] | 18 | 2020-10-24T05:05:09.000Z | 2022-03-27T13:57:56.000Z | C/G0LD/README.md | DevHedronYT/GameDev | 96b7bc2e9090eafdd8f04a0e0142c8c61f27456d | [
"CC0-1.0"
] | null | null | null | C/G0LD/README.md | DevHedronYT/GameDev | 96b7bc2e9090eafdd8f04a0e0142c8c61f27456d | [
"CC0-1.0"
] | 3 | 2021-03-13T05:48:05.000Z | 2021-05-03T13:14:24.000Z | ## About the Game:
This is another small test platformer, made using SDL2 & C99.
## Downloading the Game:
Clone the repo, and then change directory to this folder
## Getting the Requirements:
Download SDL2, from the website or by using homebrew or something. Don't forget to have a compiler as well. I would suggest using Emscripten to compile as that might work
and let you play the game in web. Also have make installed. To make it easier to run in the web, install Python as well.
## Running the Game:
For an executable
```
make game
./Game
```
For a web build
```
make game.html
if you have Python installed:
python -m http.server 910 or python3 -m http.server 910
open your browser, and go to localhost:910
otherwise:
emrun index.html
```
## Playing the Game:
It is literally nothing except for a character you can move around by using your arrow keys and thats it
## 3rd Party Assets Used in the Game:
- None
| 27.529412 | 170 | 0.741453 | eng_Latn | 0.999165 |
53518c53ac0a9c8de546cffe13bd672704e3dcc9 | 3,741 | markdown | Markdown | _posts/2016-8-23-h5-spa-framwork.markdown | mainpage/mainpage.github.io | 3fbc85316ceaf4cb772ffe2d6fcbe9534a5f155b | [
"Apache-2.0"
] | null | null | null | _posts/2016-8-23-h5-spa-framwork.markdown | mainpage/mainpage.github.io | 3fbc85316ceaf4cb772ffe2d6fcbe9534a5f155b | [
"Apache-2.0"
] | null | null | null | _posts/2016-8-23-h5-spa-framwork.markdown | mainpage/mainpage.github.io | 3fbc85316ceaf4cb772ffe2d6fcbe9534a5f155b | [
"Apache-2.0"
] | null | null | null | ---
layout: keynote
title: "移动端单页框架简单调研"
subtitle: ""
show: "true"
iframe: "/2016/08/23/h5-spa-framwork-slide/"
date: 2015-08-23
author: "sch"
header-img: ""
catalog: true
tags:
- 前端开发
- 移动端
---
当前移动互联网应用的开发模式主要有三种：Native、Webapp和Hybrid，关于它们的区别和优劣，相信大家已经比较熟悉了。对于web前端来说，与我们相关的是webapp和hybrid app这两种应用形态，其中又以hybrid应用更为广泛。随着近年来前端技术的发展，基于web技术的移动端应用的体验逐步向原生靠近，涌现出一批优秀的移动端web开发框架。本文结合自己在mini项目中的调研和实践，对移动端web开发的一些代表性框架做一个简单的介绍。
#移动端开发模式
Native、Webapp和Hybrid
## 单页应用(SPA)
对于移动端web应用来说，为了达到媲美原生应用的效果，单页架构几乎是不可或缺的。传统的多页面的应用在页面跳转时需要从服务器加载html并重新渲染，会出现明显的“白屏”现象，对于一个移动端“应用”来说这是不可忍受的。因此，大部分移动端框架选择或支持了单页的开发方式。那么，单页应用都有哪些优点呢？
## 单页应用的优势
* 页面无刷新切换
* 页面切换速度快，体验流畅
* 动画转场效果
* 前后端分离
## 单页应用必须具备的功能
* 能够管理页面状态的路由系统
* 子页面调度模块
* 数据管理模块
* 页面切换的转场效果
## 具有代表性的移动端单页框架
* Angular.js
* React Native
* Vue.js
* MobileBone.js
## Angular.js
* 大而全的MVC框架
* $routeProvider提供前端路由支持
* controller实现模块调度
* ng-view进行局部渲染
* ngAnimate创建动画效果
## demo
`html`
```
<body ng-app="myApp">
<div class="header">header</div>
<div ng-view></div>
<div class="footer">footer</span>
</body>
```
`js`
```
angular.module('myApp', ['ngRoute'])
.config(function($routeProvider) {
$routeProvider
.when('/', {
templateUrl: 'views/main.html',
controller: 'MainCtrl'
})
.when('/detail/:id', {
templateUrl: 'views/detail.html',
controller: 'DayCtrl'
})
.otherwise({
redirectTo: '/'
});
})
```
## 优缺点
优点：
* 功能完善，提供了一整套解决方案
* 数据绑定、依赖注入、单页路由、自定义指令
* MVC架构，分层清晰
缺点：
* 框架过重，对移动端而言体积过大
* “脏检查”效率低下
* 没有明确的组件化概念
* 动画转场效果实现较为困难
## React Native
* 基于React.js的组件化机制
* js编写的React组件渲染为原生组件
* Navigator组件实现页面导航和路由
* 路由模块通过实例化不同组件实现模块调度
* Flux架构的数据和状态管理
* 基于原生UI的动画效果
## demo
```
// 主模块
class MainView extends Component {
// ...
render() {
return (
<Navigator
//样式
style={{flex:1}}
//初始化路由
initialRoute={{component: FirstPage}}
//配置场景动画
configureScene={this.configureScene}
//根据路由渲染组件
renderScene={this.renderScene}
/>
);
}
}
//renderScene方法
renderScene(route, navigator) {
if (route.name == 'Home') {
return <Home navigator={navigator} {...route.passProps}/>
} else if (route.name == 'Detail') {
return <Detail navigator={navigator} {...route.passProps}/>
}
...
}
```
## 优缺点
优点
* 完善的组件化机制
* 基于Virtual Dom的数据绑定效率很高
* javascript组件最终渲染为原生组件
* 可以达到接近原生应用的体验
* learn once，write anywhere
缺点：
* 依赖原生组件暴露出来的组件和方法
* 一定程度上牺牲了web的灵活性和扩展性
## Vue.js
* 新兴的轻量级MVVM框架
* vue-router提供路由支持
* 路由模块通过实例化不同组件实现模块调度
* Flux架构的数据和状态管理
* 基于transition特性的CSS/动画过渡系统
## demo
`demo.vue`
```
//模板
<template>
<nav>
<li><a v-link="/home">首页</a></li>
<li><a v-link="/detail">详情</a></li>
</nav>
<div class="container">
<router-view></router-view>
</div>
</div>
</template>
<script>
...
//路由
const router = new VueRouter()
router.map({
'/home': {
component: Home
},
'/detail': {
component: Detail
}
})
router.redirect({
'*': '/home'
})
</script>
```
## 优缺点
优点：
* 完善的组件化机制
* 轻量，~24kb min+gzip
* 高效，基于defineProperty的数据绑定
* 快速，异步批量DOM更新
缺点：
* 新兴框架，资料较少
* 社区规模较小，影响力有限
* 框架不够成熟
## MobileBone.js
* 轻量webapp单页切换骨架
* 基于hash、H5 history API 和锚点定位的路由
* 通过子页面的id匹配对应路由
* 通过子页面进入和离开时的回调来调度模块
* 可定制的动画转场效果
## demo
作者提供的demos：
[http://rawgit.com/zhangxinxu/mobilebone/master/test/index.html](http://rawgit.com/zhangxinxu/mobilebone/master/test/index.html)
## 优点和缺点：
优点：
* 轻量级，插件级别的框架
* 可智能识别页面切换方向
* 动画效果可自定义
缺点
* 页面切换不支持传参
* 仅提供了切换骨架，应用的管理完全需要手动
* 代码组织不够优雅 | 15.207317 | 226 | 0.633253 | yue_Hant | 0.568752 |
53519145fe9f9ec37b7029a96375850b6f62c192 | 2,056 | md | Markdown | articles/sql-database/sql-database-develop-ruby-simple.md | VinceSmith/azure-docs | 550bda5c2baf01ff16b9d109549388ffddddc1fd | [
"CC-BY-3.0"
] | null | null | null | articles/sql-database/sql-database-develop-ruby-simple.md | VinceSmith/azure-docs | 550bda5c2baf01ff16b9d109549388ffddddc1fd | [
"CC-BY-3.0"
] | null | null | null | articles/sql-database/sql-database-develop-ruby-simple.md | VinceSmith/azure-docs | 550bda5c2baf01ff16b9d109549388ffddddc1fd | [
"CC-BY-3.0"
] | 2 | 2017-02-18T05:45:54.000Z | 2019-12-21T21:23:13.000Z | ---
title: Connect to SQL Database by using Ruby | Microsoft Docs
description: Give a Ruby code sample you can run to connect to Azure SQL Database.
services: sql-database
documentationcenter: ''
author: ajlam
manager: jhubbard
editor: ''
ms.assetid: 94fec528-58ba-4352-ba0d-25ae4b273e90
ms.service: sql-database
ms.custom: development
ms.workload: drivers
ms.tgt_pltfrm: na
ms.devlang: ruby
ms.topic: article
ms.date: 10/03/2016
ms.author: andrela
---
# Connect to SQL Database by using Ruby
[!INCLUDE [sql-database-develop-includes-selector-language-platform-depth](../../includes/sql-database-develop-includes-selector-language-platform-depth.md)]
This topic shows how to connect and query an Azure SQL Database using Ruby. You can run this sample from Windows, Ubuntu Linux, or Mac platforms.
## Step 1: Configure Development Environment
[Prerequisites for using the TinyTDS Ruby Driver for SQL Server](https://msdn.microsoft.com/library/mt711041.aspx)
## Step 2: Create a SQL database
See the [getting started page](sql-database-get-started.md) to learn how to create a sample database. It is important you follow the guide to create an **AdventureWorks database template**. The samples shown below only work with the **AdventureWorks schema**.
## Step 3: Get Connection Details
[!INCLUDE [sql-database-include-connection-string-details-20-portalshots](../../includes/sql-database-include-connection-string-details-20-portalshots.md)]
## Step 4: Run sample code
[Proof of Concept connecting to SQL using Ruby](http://msdn.microsoft.com/library/mt715797.aspx)
## Next Steps
* Review the [SQL Database Development Overview](sql-database-develop-overview.md)
* More information on the [Microsoft Ruby Driver for SQL Server](https://msdn.microsoft.com/library/mt691981.aspx)
## Additional resources
* [Design Patterns for Multi-tenant SaaS Applications with Azure SQL Database](sql-database-design-patterns-multi-tenancy-saas-applications.md)
* Explore all the [capabilities of SQL Database](https://azure.microsoft.com/services/sql-database/)
| 44.695652 | 260 | 0.784047 | eng_Latn | 0.748734 |
5352c28a74a7c7f24302c26dad0a68145b1dd55d | 6,016 | md | Markdown | docs/relational-databases/system-stored-procedures/managed-backup-sp-backup-config-basic-transact-sql.md | taiyaki32lp64/sql-docs.ja-jp | 5e7aa5e72daf73d7997c26baf0b1edd90fb0c681 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/relational-databases/system-stored-procedures/managed-backup-sp-backup-config-basic-transact-sql.md | taiyaki32lp64/sql-docs.ja-jp | 5e7aa5e72daf73d7997c26baf0b1edd90fb0c681 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | docs/relational-databases/system-stored-procedures/managed-backup-sp-backup-config-basic-transact-sql.md | taiyaki32lp64/sql-docs.ja-jp | 5e7aa5e72daf73d7997c26baf0b1edd90fb0c681 | [
"CC-BY-4.0",
"MIT"
] | null | null | null | ---
title: managed_backup.sp_backup_config_basic (TRANSACT-SQL) |Microsoft Docs
ms.custom: ''
ms.date: 10/03/2016
ms.prod: sql
ms.prod_service: database-engine
ms.reviewer: ''
ms.technology: system-objects
ms.topic: language-reference
f1_keywords:
- sp_backup_config_basic_TSQL
- sp_backup_config_basic
- managed_backup.sp_backup_config_basic
- managed_backup.sp_backup_config_basic_TSQL
dev_langs:
- TSQL
helpviewer_keywords:
- managed_backup.sp_backup_config_basic
- sp_backup_config_basic
ms.assetid: 3ad73051-ae9a-4e41-a889-166146e5508f
author: MikeRayMSFT
ms.author: mikeray
manager: craigg
ms.openlocfilehash: f3345e2b27a14285f3b9a3bfffd1ec95549ef124
ms.sourcegitcommit: 6443f9a281904af93f0f5b78760b1c68901b7b8d
ms.translationtype: MT
ms.contentlocale: ja-JP
ms.lasthandoff: 12/11/2018
ms.locfileid: "53201821"
---
# <a name="managedbackupspbackupconfigbasic-transact-sql"></a>managed_backup.sp_backup_config_basic (TRANSACT-SQL)
[!INCLUDE[tsql-appliesto-ss2016-xxxx-xxxx-xxx-md](../../includes/tsql-appliesto-ss2016-xxxx-xxxx-xxx-md.md)]
構成、 [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)] またはのインスタンスの特定のデータベースの基本設定 [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]です。
> [!NOTE]
> この手順呼び出せるで基本的なマネージド バックアップの構成を作成するための独自です。 ただし、高度な機能またはカスタム スケジュールを追加する場合は、まずこれらの設定を使用して[managed_backup.sp_backup_config_advanced (TRANSACT-SQL) ](../../relational-databases/system-stored-procedures/managed-backup-sp-backup-config-advanced-transact-sql.md)と[managed_backup.sp_backup_config_schedule (TRANSACT-SQL) ](../../relational-databases/system-stored-procedures/managed-backup-sp-backup-config-schedule-transact-sql.md)からこの手順でマネージ バックアップを有効にします。
 [Transact-SQL 構文表記規則](../../t-sql/language-elements/transact-sql-syntax-conventions-transact-sql.md)
## <a name="syntax"></a>構文
```Transact-SQL
EXEC managed_backup.sp_backup_config_basic
[@enable_backup = ] { 0 | 1} ,[@database_name = ] 'database_name' ,[@container_url = ] 'Azure_Storage_blob_container
,[@retention_days = ] 'retention_period_in_days' ,[@credential_name = ] 'sql_credential_name'
```
## <a name="Arguments"></a> 引数
@enable_backup
指定したデータベースに対して [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)]を有効または無効にします。 @enable_backupは **ビット** します。 パラメーターを構成するときに必要な[!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)]の最初のインスタンスの[!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]します。 変更する場合は、既存 [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)] 構成では、このパラメーターは省略可能です。 その場合は、指定されていないすべての構成値は、既存の値を保持します。
@database_name
有効にするためのデータベース名は、特定のデータベースでのバックアップを管理します。
@container_url
バックアップの場所を示す URL です。 ときに@credential_nameが null の場合、この URL は、Azure Storage に blob コンテナーに shared access signature (SAS) URL と、バックアップは、ブロック blob の機能に新しいバックアップを使用します。 詳細についてを参照してください[について SAS](https://azure.microsoft.com/documentation/articles/storage-dotnet-shared-access-signature-part-1/)します。 ときに@credential_nameこれは、ストレージ アカウントの URL と、バックアップ ページ blob の機能を非推奨のバックアップを使用して、指定します。
> [!NOTE]
> SAS URL のみがこの時点でこのパラメーターのサポートします。
@retention_days
バックアップ ファイルの保有期間 (日数)。 @storage_urlは INT です。 構成するときにこのパラメーターが必要なパラメーター[!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)]のインスタンスで初めて[!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]します。 変更中に、 [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)] 構成では、このパラメーターは省略可能です。 指定しない場合は、既存の構成値が保持されます。
@credential_name
Windows Azure ストレージ アカウントへの認証に使用する SQL 資格情報の名前。 @credentail_name **SYSNAME**します。 指定した場合、バックアップは、ページ blob に格納されます。 このパラメーターが NULL の場合、バックアップは、ブロック blob として格納されます。 ページ blob へのバックアップには非推奨とされているので、新しいブロック blob のバックアップ機能を使用することをお勧めします。 [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)] の構成を変更するために使用する場合、このパラメーターは省略可能です。 指定しない場合、既存の構成値は保持されます。
> [!WARNING]
> **@credential_name**パラメーターは、この時点ではサポートされていません。 ブロック blob のみのバックアップはサポートされて、このパラメーターを NULL にする必要があります。
## <a name="return-code-value"></a>リターン コード値
0 (成功) または 1 (失敗)
## <a name="security"></a>セキュリティ
### <a name="permissions"></a>アクセス許可
メンバーシップが必要です**db_backupoperator**データベース ロール、 **ALTER ANY CREDENTIAL**アクセス許可、および**EXECUTE**に対する**sp_deletebackuphistory**ストアド プロシージャ。
## <a name="examples"></a>使用例
ストレージ アカウントのコンテナーと SAS URL の両方を作成するには、最新の Azure PowerShell のコマンドを使用します。 次の例では、mystorageaccount のストレージ アカウントに、mycontainer、新しいコンテナーを作成しに完全なアクセス許可と SAS URL を取得します。
```powershell
$context = New-AzureStorageContext -StorageAccountName mystorageaccount -StorageAccountKey (Get-AzureStorageKey -StorageAccountName mystorageaccount).Primary
New-AzureStorageContainer -Name mycontainer -Context $context
New-AzureStorageContainerSASToken -Name mycontainer -Permission rwdl -FullUri -Context $context
```
次の例では、 [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)] ～ 30 日で、実行された SQL Server のインスタンスが、保有ポリシーを設定するの送信先を 'mycontainer' でストレージ アカウント"mystorageaccount"をという名前をという名前のコンテナーに設定します。
```Transact-SQL
Use msdb;
Go
EXEC managed_backup.sp_backup_config_basic
@enable_backup=1
,@container_url = 'https://mystorageaccount.blob.core.windows.net/mycontainer'
,@retention_days=30;
GO
```
次に、実行されている SQL Server インスタンスに対して [!INCLUDE[ss_smartbackup](../../includes/ss-smartbackup-md.md)] を無効にする例を示します。
```Transact-SQL
Use msdb;
Go
EXEC managed_backup.sp_backup_config_basic
@enable_backup=0;
GO
```
## <a name="see-also"></a>参照
[managed_backup.sp_backup_config_advanced (TRANSACT-SQL)](../../relational-databases/system-stored-procedures/managed-backup-sp-backup-config-advanced-transact-sql.md)
[managed_backup.sp_backup_config_schedule (Transact-SQL)](../../relational-databases/system-stored-procedures/managed-backup-sp-backup-config-schedule-transact-sql.md)
| 51.418803 | 472 | 0.759973 | yue_Hant | 0.376977 |
5352c6a376b3b00fcc84c02df49ef1a7acc8fe1e | 1,145 | md | Markdown | pytorch/README.md | behnam-samadi/dgcnn | 363fc991ef28f576d09b652a78e035056afa68d0 | [
"MIT"
] | 1,156 | 2018-02-11T07:54:01.000Z | 2022-03-31T20:59:21.000Z | pytorch/README.md | behnam-samadi/dgcnn | 363fc991ef28f576d09b652a78e035056afa68d0 | [
"MIT"
] | 77 | 2018-03-18T16:19:39.000Z | 2022-03-24T09:24:57.000Z | pytorch/README.md | behnam-samadi/dgcnn | 363fc991ef28f576d09b652a78e035056afa68d0 | [
"MIT"
] | 391 | 2018-03-02T05:18:49.000Z | 2022-03-31T14:22:23.000Z | # Dynamic Graph CNN for Learning on Point Clouds (PyTorch)
## Point Cloud Classification
* Run the training script:
``` 1024 points
python main.py --exp_name=dgcnn_1024 --model=dgcnn --num_points=1024 --k=20 --use_sgd=True
```
``` 2048 points
python main.py --exp_name=dgcnn_2048 --model=dgcnn --num_points=2048 --k=40 --use_sgd=True
```
* Run the evaluation script after training finished:
``` 1024 points
python main.py --exp_name=dgcnn_1024_eval --model=dgcnn --num_points=1024 --k=20 --use_sgd=True --eval=True --model_path=checkpoints/dgcnn_1024/models/model.t7
```
``` 2048 points
python main.py --exp_name=dgcnn_2048_eval --model=dgcnn --num_points=2048 --k=40 --use_sgd=True --eval=True --model_path=checkpoints/dgcnn_2048/models/model.t7
```
* Run the evaluation script with pretrained models:
``` 1024 points
python main.py --exp_name=dgcnn_1024_eval --model=dgcnn --num_points=1024 --k=20 --use_sgd=True --eval=True --model_path=pretrained/model.1024.t7
```
``` 2048 points
python main.py --exp_name=dgcnn_2048_eval --model=dgcnn --num_points=2048 --k=40 --use_sgd=True --eval=True --model_path=pretrained/model.2048.t7
```
| 33.676471 | 159 | 0.737991 | eng_Latn | 0.335386 |
535386ab6d17f6c75478a3c04c38e989a5769e72 | 2,357 | md | Markdown | README.md | JeffersonQin/remote-lamp-switch | 062c9ef7ff046b7f4f50d70b08f83b7d93f56a0b | [
"MIT"
] | 3 | 2022-01-06T14:45:53.000Z | 2022-01-12T05:57:22.000Z | README.md | JeffersonQin/remote-lamp-switch | 062c9ef7ff046b7f4f50d70b08f83b7d93f56a0b | [
"MIT"
] | null | null | null | README.md | JeffersonQin/remote-lamp-switch | 062c9ef7ff046b7f4f50d70b08f83b7d93f56a0b | [
"MIT"
] | null | null | null | 
# Remote Lamp Switch 远程开灯
Panasonic 松下 HH-LT0608 台灯远程开关的解决方案。写这个的原因是想要躺床上开关书桌上的台灯（因为是黄光，床头灯是白光晚上眼睛难受）。
手上有闲置的 Arduino，所以花了一个下午实现一下。
电灯图 (图源苏宁)：
<div align="center">
<img src="assets/HH-LT0608.jpg" width=300>
</div>
## 文件结构
```
.
├─ arduino/lamp-controller # arduino 的代码
├─ diagram # 电路
├─ LampSwitch # app 代码
├─ model # 场景模型
└─ server # 服务器代码
```
## 电路原理
猜测开关是有一个检测电容变化的电路，但也没办法验证（没有破拆）。经过实验，发现与人体绝缘的情况下把接地（有的时候不接地也行，很怪）的导体放在开关上会触发，所以这里用步进电机实现这个操作。
* 电机型号：28BYJ-48
* 驱动板：ULN2003APG
* Arduino Uno (Rev 3)
<div align="center">
<img src="assets/motor.svg" width=650>
</div>
电路文件 `diagram/motor.fzz` 可以用 fritzing 查看
## 机械结构
由于家里工具简陋，没有电钻，没有金属件，没有线锯，没有锉刀，所以设计得简单粗暴。但是没有关系，照样可以通过一些办法搞定（雾。
用到的工具：
* 美工刀
* 螺丝钉（用来打洞）
* 螺丝刀
* 一次性筷子
* 砂纸
* 各种胶带
原理示意图：
<div align="center">
<img src="assets/model.png" width=650>
</div>
<div align="center">
<img src="assets/trace.png" width=650>
</div>
侧视图：
<div align="center">
<img src="assets/model-side.png" width=650>
</div>
注意的点：
* 由于没有编码器，所有就拿四根棍子（筷子剪的）做了限位，伤点就就伤吧，反正一天不会转几次（暴论）
* 我加了配重是因为转两次那根棍子就会往上翘...看情况吧，能动就行
模型文件在 `model/model.dn`。~~我不会建模，是随便找了个 adobe 全家桶里的东西画的。~~
<div align="center">
<img src="assets/stick.jpg" width=300>
</div>
图为加工的轴的照片
## 通信原理
由于台灯在电脑旁边，所以我直接用串口进行通信。在电脑端建立 http server，数据通过发包获取。数据流向：
```
Arduino <==Serial==> PC / Http server <==> Mobile
```
注意事项：
* 需要统一波特率，默认为 9600 Hz
## Arduino
配置：
```c++
int loopcount = 48; # 用于调节电机每次转动的时间
```
## Server
配置：
```python
run_host = "0.0.0.0" # server host
run_port = 7884 # server port
max_level = 3 # 灯调节的档数，直接开关为 1
current_level = 0 # 服务启动时处于的档数
current_position = 0 # 当前轴所在的位置（0为左，1为右）
api_token = "test-token" # 用于验证请求的 token
serial_post = "COM5" # 串口名称
baudrate = 9600 # 波特率
delay_time = 0.8 # 两次请求移动间隔时间
```
注意：串口通信用的库是 `pyserial`，不是 `serial`
## App
<div align="center">
<img src="assets/screenshot.jpg" width=300>
</div>
用 Xamarin 开发，大部分代码抽取自我的项目 [YuzuMarker](https://github.com/JeffersonQin/YuzuMarker)
Nuget Dependency:
* Newtonsoft.Json
### Knwon Issues
* 设置的持久化还没写，static class 的 two-way binding 有点问题，bug 还没修
## UWP App Loopback
由于 UWP 对于本地回环网络的限制，所以如果控制服务器在本机则会产生问题。可以使用 Fiddler 之类的工具解除限制。关键词：UWP Loopback exemption
| 16.716312 | 93 | 0.664404 | yue_Hant | 0.376438 |
535392f1545d93dd8c24cab769371a2cdaa11f87 | 3,020 | md | Markdown | README.md | biubiu12314/IDEAtest | 580728b01d06cb54155809ebe7885ef36d03f410 | [
"Apache-2.0"
] | null | null | null | README.md | biubiu12314/IDEAtest | 580728b01d06cb54155809ebe7885ef36d03f410 | [
"Apache-2.0"
] | 6 | 2020-11-16T20:41:52.000Z | 2022-02-01T01:03:38.000Z | README.md | biubiu12314/IDEAtest | 580728b01d06cb54155809ebe7885ef36d03f410 | [
"Apache-2.0"
] | 1 | 2021-08-28T07:27:17.000Z | 2021-08-28T07:27:17.000Z | #4.0.0之后基于SpringBoot最新版本,启动类修改为SpringBoot的org.springrain.SpringrainApplication类进行启动.
项目名为springrain[春雨]我的个人博客是 http://www.weicms.net QQ群是:238904840 </br>
# 文档
https://git.oschina.net/chunanyong/springrain/tree/master/doc </br>
# 代码生成器
http://git.oschina.net/chunanyong/springrain/tree/master/gencode </br>
# sql脚本
http://git.oschina.net/chunanyong/springrain/tree/master/sql </br>
springrain是spring/springboot的极简封装,spring/springboot一站式开发的范例.
springrain本身就是一个完整的eclipse项目,spring/springboot一站式开发的范例,包含spring core,spring jdbc,spring mvc.可以认为就是一个spring/springboot的demo.
springrain 自带一个代码生成器,能够生成对表的增删改查的逻辑代码,以及前台页面样式和js文件
spring良好的扩展性,集成度,IOC,AOP事务,已经是项目的基础条件.
项目只依赖spring,没有hibernate,struts,ibatis.
使用shiro权限控制到按钮级
结合shiro,redis实现了天然的分布式session共享
hibernate太过复杂,运用不好就会造成很大影响,ibatis的优势就是把sql写入xml文件,利于数据库调优和sql语句管理.数据库调优可以使用druid直接输出比较慢的sql,比分析xml中的语句更直观,关于sql管理,springrain所有的sql语句都使用Finder封装,只要查看Finder在项目中的引用,就能查看项目中所有的sql语句,就此,ibatis的优势就很小了.
struts 和 spring mvc 相比,个人感觉还是有点差距的.
一些测试案例：
```java
//就极简而言,一个数据库只需要一个Service,就可以管理这个数据库的任意一张表
//@Test 查询基本类型
public void testObject() throws Exception{
// Finder finder=new Finder("select id from t_user where 1=1 ");
Finder finder=Finder.getSelectFinder(User.class,"id").append(" WHERE 1=1 ");
finder.append("and id=:userId ").setParam("userId", "admin");
String id = baseDemoService.queryForObject(finder, String.class);
System.out.println(id);
}
//@Test 查询一个对象
public void testObjectUser() throws Exception{
//Finder finder=new Finder("select * from t_user where id=:userId order by id");
Finder finder=Finder.getSelectFinder(User.class).append(" WHERE id=:userId order by id desc ");
finder.setParam("userId", "admin");
User u = baseDemoService.queryForObject(finder, User.class);
System.out.println(u.getName());
}
//@Test 查询分页
public void testMsSql() throws Exception{
//Finder finder=new Finder("select * from t_user order by id");
Finder finder=Finder.getSelectFinder(User.class).append(" order by id desc ");
Listlist = baseDemoService.queryForList(finder, User.class, new Page(2));
System.out.println(list.size());
for(User s:list){
System.out.println(s.getName());
}
}
//@Test 调用数据库存储过程
public void testProc() throws Exception{
Finder finder=new Finder();
finder.setParam("unitId", 0);
finder.setProcName("proc_up");
Map queryObjectByProc = (Map) baseDemoService.queryObjectByProc(finder);
System.out.println(queryObjectByProc.get("#update-count-10"));
}
//@Test 调用数据库函数
public void testFunction() throws Exception{
Finder finder=new Finder();
finder.setFunName("fun_userId");
finder.setParam("userId", "admin");
String userName= baseDemoService.queryForObjectByByFunction(finder,String.class);
System.out.println(userName);
}
``` | 34.712644 | 196 | 0.708278 | yue_Hant | 0.330367 |
5353af333fc1917e20b742215f5b0839d4d5ae5f | 81 | md | Markdown | README.md | IANSUCH/IAN | 283f85040d590802f2be67a22701289771af1272 | [
"CC0-1.0"
] | null | null | null | README.md | IANSUCH/IAN | 283f85040d590802f2be67a22701289771af1272 | [
"CC0-1.0"
] | null | null | null | README.md | IANSUCH/IAN | 283f85040d590802f2be67a22701289771af1272 | [
"CC0-1.0"
] | null | null | null | # IAN
Designer and Builder of CLT Passive House Building, PV and battery System
| 27 | 74 | 0.790123 | eng_Latn | 0.901202 |
53541d2245ab5c7a18ff9ecac86af9e133449140 | 275 | md | Markdown | Devices/Gateways/GatewayService/Hardware.md | lcacciatore/connectthedots | ec2efd440bcdf1b6ec0115a22009f09017b73bbe | [
"MIT"
] | 1 | 2015-06-18T11:08:32.000Z | 2015-06-18T11:08:32.000Z | Devices/Gateways/GatewayService/Hardware.md | ashumeow/connect-the-copy-dots | f8a12326259bf351805e04a410e7573643cf149c | [
"MIT"
] | 1 | 2021-01-17T01:57:31.000Z | 2021-01-17T01:57:31.000Z | Devices/Gateways/GatewayService/Hardware.md | ashumeow/connect-the-copy-dots | f8a12326259bf351805e04a410e7573643cf149c | [
"MIT"
] | null | null | null | To set up a Raspberry Pi as a simple gateway for connecting Arduino or other sensors to Azure you will need to procure:
1. [Raspberry Pi B/B+](http://www.raspberrypi.org/products/model-b-plus/)
2. Power supply
3. Case (optional)
Note: Only the model above has been tested. | 39.285714 | 119 | 0.756364 | eng_Latn | 0.973227 |
53542a63d85711589113e13babd394eb5c7dfabb | 20,342 | md | Markdown | public/bower_components/oclazyload/CHANGELOG.md | Hrachya777/social-blog | bce67a20c5e4951fa2afee44df4e6025c673f4d7 | [
"MIT"
] | null | null | null | public/bower_components/oclazyload/CHANGELOG.md | Hrachya777/social-blog | bce67a20c5e4951fa2afee44df4e6025c673f4d7 | [
"MIT"
] | null | null | null | public/bower_components/oclazyload/CHANGELOG.md | Hrachya777/social-blog | bce67a20c5e4951fa2afee44df4e6025c673f4d7 | [
"MIT"
] | null | null | null | <a name="1.0.4"></a>
# 1.0.4 (2015-07-30)
## Bug Fixes
- don't let unmet dependencies slip through (thank you unit tests!)
([23eb666d](https://github.com/ocombe/ocLazyLoad/commit/23eb666d6627416e40aaa97783b9e81ec7153fe9))
- don't try to call angular.module on config names
([52219f92](https://github.com/ocombe/ocLazyLoad/commit/52219f923319e0856da47a6bce064b6ffb361641),
[#217](https://github.com/ocombe/ocLazyLoad/issues/217), [#218](https://github.com/ocombe/ocLazyLoad/issues/218))
<a name="1.0.3"></a>
# 1.0.3 (2015-07-24)
## Bug Fixes
- check for config names when needed
([023e4bb1](https://github.com/ocombe/ocLazyLoad/commit/023e4bb1e43a922ac4b9a4ef09ff475f1fec867a),
[#214](https://github.com/ocombe/ocLazyLoad/issues/214), [#198](https://github.com/ocombe/ocLazyLoad/issues/198))
<a name="1.0.2"></a>
# 1.0.2 (2015-07-10)
## Bug Fixes
- add extra condition to improve karma testing
([f0c33aae](https://github.com/ocombe/ocLazyLoad/commit/f0c33aaea84511a276dd946dd48bfe2cb20d1e73))
## Features
- add interoperability with CommonJS
([b0536ad4](https://github.com/ocombe/ocLazyLoad/commit/b0536ad4104467922c36bcf55a8a072343d102bc))
<a name="1.0.1"></a>
# 1.0.1 (2015-06-01)
## Bug Fixes
- don't remove filecache for files that were successfully loaded
([e2ed37c0](https://github.com/ocombe/ocLazyLoad/commit/e2ed37c0eff32d34419af6851bfc355e7fb6f3ad))
<a name="1.0.0"></a>
# 1.0.0 (2015-05-29)
## Bug Fixes
- use parent element instead of head to insert files in native loaded
([ad4276a3](https://github.com/ocombe/ocLazyLoad/commit/ad4276a39cddf8ebfd8f247690e98fc306c2d3bb),
[#164](https://github.com/ocombe/ocLazyLoad/issues/164))
- don't compile text nodes in the directive
([8900e493](https://github.com/ocombe/ocLazyLoad/commit/8900e493b8245084f4871d129250ffc54e565639),
[#168](https://github.com/ocombe/ocLazyLoad/issues/168))
- files cache should be cleaned upon resolution of the promise
([9a186c93](https://github.com/ocombe/ocLazyLoad/commit/9a186c93ccb72c63a45e40c6c1e86319d9d004fa),
[#189](https://github.com/ocombe/ocLazyLoad/issues/189))
- reject promise when calling 'load' instead of 'inject'
([31595472](https://github.com/ocombe/ocLazyLoad/commit/315954729aaa609d43aa7eb7750e8804cff9bf70),
[#147](https://github.com/ocombe/ocLazyLoad/issues/147))
- make inject work as a standalone function when no params are given
([499bd72d](https://github.com/ocombe/ocLazyLoad/commit/499bd72ddaf6addbf2c649a48776bd2b6ff35227),
[#171](https://github.com/ocombe/ocLazyLoad/issues/171))
- guard against null-refs when parsing Safari user-agents
([818aa5d0](https://github.com/ocombe/ocLazyLoad/commit/818aa5d0ddaa3909109d42b38f8921e9d4b18cda),
[#188](https://github.com/ocombe/ocLazyLoad/issues/188))
- checking if we're not registering a component with a reserved name (such at `toString`)
([7362ca49](https://github.com/ocombe/ocLazyLoad/commit/7362ca493384c5b14e203b9c013085cbcab980f8 ),
[#184](https://github.com/ocombe/ocLazyLoad/issues/184))
<a name="1.0.0-beta.2"></a>
# 1.0.0-beta.2 (2015-04-20)
## Bug Fixes
- Die infinite loops! You are not fun anymore (with param serie:true)
([dab34c0a](https://github.com/ocombe/ocLazyLoad/commit/dab34c0a3513061665850f68d983c1f2729f5f5a),
[#166](https://github.com/ocombe/ocLazyLoad/issues/166))
<a name="1.0.0-beta.1"></a>
# 1.0.0-beta.1 (2015-04-16)
## Bug Fixes
- use document.querySelector for insertBefore when jQuery isn't available
([6e8fa8c3](https://github.com/ocombe/ocLazyLoad/commit/6e8fa8c37f4305c50241288db7fddc5ecae0ab8f),
[#164](https://github.com/ocombe/ocLazyLoad/issues/164))
## Documentation
- adding a plunkr for issues
([2f408d27](https://github.com/ocombe/ocLazyLoad/commit/2f408d2729eaf3df9cc8434375611a5b26181c0b))
<a name="1.0.0-alpha.3"></a>
# 1.0.0-alpha.3 (2015-04-09)
## Bug Fixes
- components can be registered as object maps now
([08ed860e](https://github.com/ocombe/ocLazyLoad/commit/08ed860e7051f1f0dd132d760b958c5be1114177),
[#156](https://github.com/ocombe/ocLazyLoad/issues/156))
- make a real copy of the params
([6a5d3d4c](https://github.com/ocombe/ocLazyLoad/commit/6a5d3d4ca3fca1e90468aed10ef96f06669cd7f9),
[#160](https://github.com/ocombe/ocLazyLoad/issues/160))
## Features
- ES6fy all the things!
([9cae48c8](https://github.com/ocombe/ocLazyLoad/commit/9cae48c828665e58132950d6db138d082f6bf2a2))
<a name="1.0.0-alpha2"></a>
# 1.0.0-alpha2 (2015-03-23)
## Bug Fixes
- hash shouldn't prevent file type detection
([9e1d0894](https://github.com/ocombe/ocLazyLoad/commit/9e1d089413e09b14b7b46d5ff5de4612613be5e9),
[#153](https://github.com/ocombe/ocLazyLoad/issues/153))
<a name="1.0.0-alpha1"></a>
# 1.0.0-alpha1 (2015-03-19)
## Features
- ocLazyLoad is now modular and (partially) written in ES6! It should be easier to write new loaders (or even extensions), and you can cherry picks the parts that you like. For example, you can use the injector without the loaders. Also, all of the internal functions are available (preceded by an underscore, and undocumented), use them at your own risk (in fact you shouldn't need them unless you're writing an extension).
## Bug Fixes
- the directive should append the content and not add it after
- only the modules added via angular.bootstrap should be considered "already loaded"
[#147](https://github.com/ocombe/ocLazyLoad/issues/147)
## TODO before the release
- try to remove most of the promises for perfs/tests
- use moaaar ES6
- clean up the code
<a name="0.6.3"></a>
# 0.6.3 (2015-03-09)
## Bug Fixes
- detect file type when path contains url parameters
([57e1801d](https://github.com/ocombe/ocLazyLoad/commit/57e1801d933f978060954bd8707f586b51544906),
[#137](https://github.com/ocombe/ocLazyLoad/issues/137))
- rejected promise should be returned immediately
([887a67c4](https://github.com/ocombe/ocLazyLoad/commit/887a67c4196fa4bbd65c34f6eba1d8b2bca9fed3))
<a name="0.6.2"></a>
# 0.6.2 (2015-03-05)
## Features
- first step on supporting systemjs & import
([cb8dd62e](https://github.com/ocombe/ocLazyLoad/commit/cb8dd62ed9052995cbaf132d94092d1d103dd74d))
<a name="0.6.1"></a>
# 0.6.1 (2015-03-05)
## Bug Fixes
- karma hack isn't needed anymore
([3108296e](https://github.com/ocombe/ocLazyLoad/commit/3108296e9d78da822e58333f2f7d674531ae937b))
- angular.bootstrap now adds modules to init, not replace them
([bdc03dd9](https://github.com/ocombe/ocLazyLoad/commit/bdc03dd9128eca7fca2421317b9f7b103c9b419c))
- fixed TypeError: Converting circular structure to JSON
([11da36d9](https://github.com/ocombe/ocLazyLoad/commit/11da36d90bc5bae588fa3770430d371d5f935aae))
- don't watch for angular.module calls when you're not lazy loading
([35f7eb5b](https://github.com/ocombe/ocLazyLoad/commit/35f7eb5be57f7753a20d7460c5a380f44e3ac175))
## Performance Improvements
- hash the signature to optimize memory consumption
([1cd9676e](https://github.com/ocombe/ocLazyLoad/commit/1cd9676e8799cff03458f7d2d4d144f624da9cfa))
<a name="0.6.0"></a>
# 0.6.0 (2015-02-27)
## Bug Fixes
- staged lines missing from last commit
([dd24bcdd](https://github.com/ocombe/ocLazyLoad/commit/dd24bcdd573821ce7def60c173a15cbee2540de7))
- don't throw for karma
([633bec8b](https://github.com/ocombe/ocLazyLoad/commit/633bec8b38635e7d78aaa0e4ea8f1a8cdb85050e),
[#129](https://github.com/ocombe/ocLazyLoad/issues/129))
- RequireJS should be able to load js files with no extension (default behavior)
([4f60d05d](https://github.com/ocombe/ocLazyLoad/commit/4f60d05d02039b700908545b60b71c3e2ca9bbf6))
- null constants should work
([83d416f9](https://github.com/ocombe/ocLazyLoad/commit/83d416f97d357d148efe97bafbaf2836ed7b3a3d),
[#111](https://github.com/ocombe/ocLazyLoad/issues/111))
- keep track of components signatures instead of just the names
([6bbaed97](https://github.com/ocombe/ocLazyLoad/commit/6bbaed971cf2d23bb35a6ba5f29c6e6162edc5b5),
[#120](https://github.com/ocombe/ocLazyLoad/issues/120))
- improve bootstrap & added compatibility with karma
([ff6afcf5](https://github.com/ocombe/ocLazyLoad/commit/ff6afcf5d3ef00e8e931fd548051f3103225cea8),
[#111](https://github.com/ocombe/ocLazyLoad/issues/111))
## Features
- you don't need to specify the name of the lazy loaded modules anymore!!
([6634cbee](https://github.com/ocombe/ocLazyLoad/commit/6634cbee6c5ce84363be84ae5529a61a633585b5))
- added support for specifying the type of a file.
([a3549eea](https://github.com/ocombe/ocLazyLoad/commit/a3549eea93c67cfc4881ebe9d44c73c220790461))
## Documentation
- adding a table of contents
([98aad141](https://github.com/ocombe/ocLazyLoad/commit/98aad14141e2eae1d04f9fc1fe09d85cd4b14713))
<a name="0.5.2"></a>
# 0.5.2 (2014-12-30)
## Bug Fixes
- use init for bootstrapped apps & removed the need for loadedModules
([01936cd6](https://github.com/ocombe/ocLazyLoad/commit/01936cd6fe0e0f89a203408ee0bbb927f5b44d07),
[#84](https://github.com/ocombe/ocLazyLoad/issues/84), [#102](https://github.com/ocombe/ocLazyLoad/issues/102), [#109](https://github.com/ocombe/ocLazyLoad/issues/109))
## Documentation
- added a link to a new lesson from egghead.io
([ef8d2871](https://github.com/ocombe/ocLazyLoad/commit/ef8d2871a445b29588f779a27cb3b702d0da6a13))
<a name="0.5.1"></a>
# 0.5.1 (2014-11-20)
## Bug Fixes
- don't use async when you load files in serie
([9af93ed3](https://github.com/ocombe/ocLazyLoad/commit/9af93ed30cf05c6c64594d206dc9bf36a318f46e),
[#95](https://github.com/ocombe/ocLazyLoad/issues/95))
- avoid errors thrown on empty template files
([768b9d75](https://github.com/ocombe/ocLazyLoad/commit/768b9d751a613a0a10cb476d5c3eac5fdf44f627))
- compatibility with jasmine
([d4985e1d](https://github.com/ocombe/ocLazyLoad/commit/d4985e1d7ce98315ca64a72730d8c10524929d58),
[#94](https://github.com/ocombe/ocLazyLoad/issues/94))
<a name="0.5.0"></a>
# 0.5.0 (2014-11-11)
## Features
- added a new param `insertBefore`
([c4f10385](https://github.com/ocombe/ocLazyLoad/commit/c4f10385cb6a9122c3a03d28b1bb6837710cc3f7),
[#91](https://github.com/ocombe/ocLazyLoad/issues/91))
- started unit tests
([dcc4ff63](https://github.com/ocombe/ocLazyLoad/commit/dcc4ff639df23a1b934899b020a483e47e6ab290))
## Documentation
- updated loaders signatures
([ba022894](https://github.com/ocombe/ocLazyLoad/commit/ba022894841222989cf699f07fe21f04f7ad3307))
<a name="0.4.2"></a>
# 0.4.2 (2014-11-10)
## Bug Fixes
- extend config to params for the register method
([31157941](https://github.com/ocombe/ocLazyLoad/commit/31157941ccabfa8f8c55edc00dc2b5758bf073b2),
[#89](https://github.com/ocombe/ocLazyLoad/issues/89))
<a name="0.4.1"></a>
# 0.4.1 (2014-11-09)
## Bug Fixes
- keep global params pristine when loading files
([6b2306b7](https://github.com/ocombe/ocLazyLoad/commit/6b2306b71543542c9b592766644c7bba1297bae4),
[#89](https://github.com/ocombe/ocLazyLoad/issues/89))
- defining new run blocks will replace previous ones
([af2627b5](https://github.com/ocombe/ocLazyLoad/commit/af2627b5e627b2b4d83cdd043eff68b1c1430740),
[#89](https://github.com/ocombe/ocLazyLoad/issues/89))
<a name="0.4.0"></a>
# 0.4.0 (2014-11-09)
## Features
- new parameter `serie` to load files in serie
([4ae7a3f3](https://github.com/ocombe/ocLazyLoad/commit/4ae7a3f3de6ad4de74baa6cc771aee556bce812e),
[#47](https://github.com/ocombe/ocLazyLoad/issues/47), [#86](https://github.com/ocombe/ocLazyLoad/issues/86))
- new parameter `rerun` to rerun the run blocks
([26a64a38](https://github.com/ocombe/ocLazyLoad/commit/26a64a38b0c21b6ca28cfa7e512b0b290fdca619),
[#89](https://github.com/ocombe/ocLazyLoad/issues/89))
- new function: `isLoaded` to check if a module has been loaded
([364c9e9f](https://github.com/ocombe/ocLazyLoad/commit/364c9e9ffd8350e5ca46a708bd3846ea6de9421c),
[#79](https://github.com/ocombe/ocLazyLoad/issues/79))
<a name="0.3.10"></a>
# 0.3.10 (2014-11-09)
## Bug Fixes
- fix for error:[$compile:multidir] Multiple directives
([61fd4dd3](https://github.com/ocombe/ocLazyLoad/commit/61fd4dd3b8131245d33eb2314dcf37a9188a6728),
[#84](https://github.com/ocombe/ocLazyLoad/issues/84),
[#78](https://github.com/ocombe/ocLazyLoad/issues/78),
[#73](https://github.com/ocombe/ocLazyLoad/issues/73),
[#58](https://github.com/ocombe/ocLazyLoad/issues/58))
- css onload patch for some old browsers
([14ce3406](https://github.com/ocombe/ocLazyLoad/commit/14ce34066e0e865c8fa86f663d38e046f7a32abb))
- content inside the oc-lazy-load directive is now compiled on load
([9962e2ef](https://github.com/ocombe/ocLazyLoad/commit/9962e2ef163e9449e295dd3297f6019267a0e0e1),
[#80](https://github.com/ocombe/ocLazyLoad/issues/80))
<a name="0.3.9"></a>
# 0.3.9 (2014-11-02)
## Bug Fixes
- allow components with the same name from different types/modules
([f981c337](https://github.com/ocombe/ocLazyLoad/commit/f981c33749e4e61fa4dfd7c3c41df9beffcbf734),
[#67](https://github.com/ocombe/ocLazyLoad/issues/67))
- initial modules not registered
([bcf50004](https://github.com/ocombe/ocLazyLoad/commit/bcf50004b8a1172aff4c769746fdcb9e5d5d9cba),
[#58](https://github.com/ocombe/ocLazyLoad/issues/58), [#71](https://github.com/ocombe/ocLazyLoad/issues/71), [#73](https://github.com/ocombe/ocLazyLoad/issues/73), [#77](https://github.com/ocombe/ocLazyLoad/issues/77))
- add support for angular 1.3 in bower
([bda921b6](https://github.com/ocombe/ocLazyLoad/commit/bda921b68ce30645d992982325adc4eebfdcd361),
[#76](https://github.com/ocombe/ocLazyLoad/issues/76))
## Features
- broadcast for componentLoaded event provides more info (module name and type)
([d41b9f53](https://github.com/ocombe/ocLazyLoad/commit/d41b9f53a46ff8c97b780d4c24f6f64e16017b89))
- example1 now uses ui-grid instead of ng-grid
([e7cf1e83](https://github.com/ocombe/ocLazyLoad/commit/e7cf1e83ff1453ee5adb8112052d393f9dc09e27))
## Documentation
- added link to a new article by @kbdaitch
([cc6b41db](https://github.com/ocombe/ocLazyLoad/commit/cc6b41db5e0dbcfe68754df325bf9f09e5709bf2))
- added a link to a new lesson from egghead.io
([e231f3cb](https://github.com/ocombe/ocLazyLoad/commit/e231f3cbfd6fb3338479a5f4d8a9ce00d374646e))
- added a link to a new lesson from egghead.io
([9b3c48e4](https://github.com/ocombe/ocLazyLoad/commit/9b3c48e49800dd3ed6a01dad7c1d958f8625eddb))
<a name="0.3.8"></a>
# 0.3.8 (2014-09-25)
## Bug Fixes
- reject on load error
([d83f52b5](https://github.com/ocombe/ocLazyLoad/commit/d83f52b56a77a5cdb230260c497ee2db7283e077),
[#66](https://github.com/ocombe/ocLazyLoad/issues/66))
<a name="0.3.7"></a>
# 0.3.7 (2014-09-10)
## Bug Fixes
- don't reload a dependency that was just loaded
([6752bb94](https://github.com/ocombe/ocLazyLoad/commit/6752bb948093f196311572530d814231dc2dcd3a),
[#64](https://github.com/ocombe/ocLazyLoad/issues/64))
## Features
- new event ocLazyLoad.moduleReloaded
([5010d144](https://github.com/ocombe/ocLazyLoad/commit/5010d144d1b250424be2bcfa98faf50c6782bf96))
<a name="0.3.6"></a>
# 0.3.6 (2014-09-02)
## Bug Fixes
- concurrency lazy loads (thanks @BenBlazely)
([4899ea1a](https://github.com/ocombe/ocLazyLoad/commit/4899ea1a09bee145f70aec3dd964f885060422d8),
[#44](https://github.com/ocombe/ocLazyLoad/issues/44))
## Documentation
- added a few links to other examples
<a name="0.3.5"></a>
# 0.3.5 (2014-08-26)
## Bug Fixes
- fixed cases where the config block would not be called
([1e29c9d4](https://github.com/ocombe/ocLazyLoad/commit/1e29c9d438d494cd053cd7533921e02e3fe5e5d0),
[#5](https://github.com/ocombe/ocLazyLoad/issues/5)).
The config block would not be called if:
- defined multiple times (only the first 1 would be invoked)
- defined with an auto injected module: ['...', function() {}]
- defined after another component: angular.module().controler().config()
<a name="0.3.4"></a>
# 0.3.4 (2014-08-26)
## Bug Fixes
- make sure reconfig:true always run all invoke blocks
([361ae6b7](https://github.com/ocombe/ocLazyLoad/commit/361ae6b7d319cb5ada1ab022a6761d4a67a31b58),
[#54](https://github.com/ocombe/ocLazyLoad/issues/54))
- the config/run blocks were not invoked without reconfig: true
([300882a0](https://github.com/ocombe/ocLazyLoad/commit/300882a016e4f9d538e322be9718f21740048296),
[#5](https://github.com/ocombe/ocLazyLoad/issues/5))
- indexOf polyfill for IE8
([5f71c09c](https://github.com/ocombe/ocLazyLoad/commit/5f71c09cad4255932e84c760b07d16a4a2b016d9),
[#52](https://github.com/ocombe/ocLazyLoad/issues/52))
## Features
- more log messages for debug
([bcbca814](https://github.com/ocombe/ocLazyLoad/commit/bcbca814049863b4dd7a6c5c1071efd760094966))
<a name="0.3.3"></a>
# 0.3.3 (2014-07-23)
## Bug Fixes
- don't execute config blocks multiple times by default
([e2fec59e](https://github.com/ocombe/ocLazyLoad/commit/e2fec59ee7ff1e95e7e78ef8397c4fe500d8e7c0),
[#43](https://github.com/ocombe/ocLazyLoad/issues/43), [#41](https://github.com/ocombe/ocLazyLoad/issues/41))
- don't test for .js in path because of requirejs
([6045214b](https://github.com/ocombe/ocLazyLoad/commit/6045214b6a4cc2d9dee1c1f2f89946687d963828))
- test order
([8412cb43](https://github.com/ocombe/ocLazyLoad/commit/8412cb431bfc742f2c4151e5b089f3313a70035e))
<a name="0.3.2"></a>
# 0.3.2 (2014-07-23)
## Bug Fixes
- allow $ocLazyLoadProvider.config to be called multiple times
([c590579c](https://github.com/ocombe/ocLazyLoad/commit/c590579c9512e0dd3fae2c33c0aefc0bb0f7ca7e),
[#43](https://github.com/ocombe/ocLazyLoad/issues/43))
- prevent duplicate loadings
([12bc6b2b](https://github.com/ocombe/ocLazyLoad/commit/12bc6b2b2d1561517d56c14c56c15c332d578344),
[#35](https://github.com/ocombe/ocLazyLoad/issues/35),
[#38](https://github.com/ocombe/ocLazyLoad/issues/38))
<a name="0.3.1"></a>
# 0.3.1 (2014-07-14)
## Bug Fixes
- don't reject file load with custom file loaders such as requirejs
([91ed522f](https://github.com/ocombe/ocLazyLoad/commit/91ed522f724c3d384146053623bbd1e7c2c86751),
[#33](https://github.com/ocombe/ocLazyLoad/issues/33))
## Features
- auto changelog from commits msg
([c089e085](https://github.com/ocombe/ocLazyLoad/commit/c089e085431d9f1a968e94c78f3c5ac5af71fa72))
- prevent duplicate loadings & add a cache busting param
([5a5d7f10](https://github.com/ocombe/ocLazyLoad/commit/5a5d7f108578fe31c5ca1f7c8dfc2d3bccfd1106),
[#38](https://github.com/ocombe/ocLazyLoad/issues/38))
# 0.3.0 (17 June 2014)
## Features
- $ocLazyLoad will now reject promises on errors
- Use the parameter `debug` to show log messages in the console
- JS / CSS / Template loaders are available by default in $ocLazyLoad but you can overwrite them with the config
- Better doc (finally! \o/)
- Example1 is now much better !
- Events broadcasted on module / component / file load (#21)
# 0.2.0 (20 May 2014)
* Added support for $animateProvider #19
* Added support for CSS Loading (And perhaps other file types in the future) #19
* Added loadAll function for use when a state requires resolve on more than one asset. #19
* FIX: Angular JS 1.3.0-beta.8 changed the way config blocks are handled (now invoked last) #19
* Adopted the MIT license as requested in #20
* Added a gulpfile to build dist files (and, in the future, to do tests before the build). Run `npm install` to install the new dependencies and `npm build` to build the dist files.
* **Breaking change** moved the src files to /src and the dist files to /dist. Installations via bower will only see the dist folder
* Moved the examples to /examples
# 0.1.3 (30 April 2014)
* Fix for bug #18: merged files and incorrect module loading
# 0.1.2 (14 April 2014)
* Fix for bug #16: config blocks didn't work for module dependencies
# 0.1.1 (08 April 2014)
* Fix for bug #8: runBlocks can now load new modules (thanks to @rolandzwaga)
* Added an example that makes use of requirejs and uses ngGrid as a lazy loaded module (thanks to @rolandzwaga)
# 0.1.0 (04 April 2014)
* Added a changelog !
* Added ```loadTemplateFile``` function.
* Merge pull request #6 from BenBlazely/master (Extension of lazy loading to the angular.module DI block, refactored to use promises for tracking progress.)
* Merge pull request #7 from rolandzwaga/master (Added some improvements for apps using angular.boostrap & for duplicated modules)
* Fixed a bug with run blocks not working when they used unloaded modules. Not a complete fix though, more to come when bug #8 is fixed
| 36.26025 | 424 | 0.760643 | yue_Hant | 0.419669 |
535466906f709da186b417fc989a042236c05c6e | 5,581 | md | Markdown | content/posts/zotero.md | yanboyang713/yanboyang713.github.io | 109edc6247d6a20e9a18fec2ff591a3a120741c2 | [
"MIT"
] | null | null | null | content/posts/zotero.md | yanboyang713/yanboyang713.github.io | 109edc6247d6a20e9a18fec2ff591a3a120741c2 | [
"MIT"
] | null | null | null | content/posts/zotero.md | yanboyang713/yanboyang713.github.io | 109edc6247d6a20e9a18fec2ff591a3a120741c2 | [
"MIT"
] | null | null | null | ---
title: "Getting Started with Zotero"
date: 2021-12-07T12:46:00+08:00
tags: ["zotero"]
categories: ["Research"]
draft: false
summary: "Set-up Zotero with Better Bibtex, zotfile and Scite."
---
## Introduction {#introduction}
## Why Use Zotero? {#why-use-zotero}
- Be Organized: Keep all of your research and citations in one place
- Save time: Format fewer citations by hand
- Collaborate: Work with anyone in the world, anytime
- It's Free: No cost even after you
## Zotero Installation {#zotero-installation}
```bash
yay -S zotero
```
## Launch Zotero :zotero-sync: {#launch-zotero-zotero-sync}
### Create a Zotero Account {#create-a-zotero-account}
If you haven’t already created a Zotero account, please take a few moments to register now [ **Here** ](https://www.zotero.org/user/register). It’s a free way to sync and access your library from anywhere, and it lets you join groups and back up all your attached files.
### Set up Zotero syncing {#set-up-zotero-syncing}
You can now set up Zotero syncing to sync your data across multiple computers, access your library online, or collaborate in group libraries. Follow these steps to get started.
1. Open the Sync pane of the Zotero preferences
Goto "Edit" and click "Preferences"
{{< figure src="https://res.cloudinary.com/dkvj6mo4c/image/upload/v1618958146/zotero/Wed%5FApr%5F21%5F08%5F33%5F25%5FAM%5FAEST%5F2021%5Fyoifbp.png" >}}
1. Enter your username and password
Enter your username and password into the Sync preferences and click “Set Up Syncing”. Zotero will now automatically sync your data as you make changes.
{{< figure src="https://res.cloudinary.com/dkvj6mo4c/image/upload/v1618958273/zotero/Wed%5FApr%5F21%5F08%5F37%5F31%5FAM%5FAEST%5F2021%5Fon28w2.png" >}}
## Zotero Connector {#zotero-connector}
Go to this [link](https://chrome.google.com/webstore/detail/zotero-connector/ekhagklcjbdpajgpjgmbionohlpdbjgc).
## Better Bibtex :better-bibtex: {#better-bibtex-better-bibtex}
### Instaliion {#instaliion}
Install by downloading the [latest release](https://github.com/retorquere/zotero-better-bibtex/releases/tag/v5.4.29) and save the XPI file, just clicking it and then in Zotero:
1. In the main menu go to Tools > Add-ons
2. Select ‘Extensions’
3. Click on the gear in the top-right corner and choose ‘Install Add-on From File…’
4. Choose .xpi that you’ve just downloaded, click ‘Install’
5. Restart Zotero
### Settings {#settings}
1. Go to Edit -> Preferences -> Better BibTex
#### citation key format {#citation-key-format}
You can set key format gengeration the same format key with Google scholar
```file
[auth:lower][year][veryshorttitle:lower]
```
Zotero:
Google Scholar:
```file
@article{jordan2015machine,
title={Machine learning: Trends, perspectives, and prospects},
author={Jordan, Michael I and Mitchell, Tom M},
journal={Science},
volume={349},
number={6245},
pages={255--260},
year={2015},
publisher={American Association for the Advancement of Science}
}
```
### Export {#export}
1. In the main menu go to File > Export Library
2. Format you can choose Better BibTex.
****Inportance Note****: Don't forget choose ****keep updated****
1. Choose folder
{{< figure src="https://res.cloudinary.com/dkvj6mo4c/image/upload/v1631527595/zotero/exportFile%5Frtlngo.png" >}}
1. There is a example:
```console
[yanboyang713@Boyang-PC ~]$ head reference.bib
@misc{ActionCommandsBasler,
title = {Action {{Commands}} | {{Basler}}},
howpublished = {https://docs.baslerweb.com/action-commands\#action-group-mask},
file = {/home/yanboyang713/Zotero/storage/NKXFFZRJ/action-commands.html}
}
@misc{ActionCommandsBaslera,
title = {Action {{Commands}} | {{Basler}}},
howpublished = {https://docs.baslerweb.com/action-commands},
```
## Zotfile {#zotfile}
Install by downloading the [latest release](https://github.com/jlegewie/zotfile/releases/) and save the XPI file, just clicking it – and then in Zotero:
1. In the main menu go to Tools > Add-ons
2. Select ‘Extensions’
3. Click on the gear in the top-right corner and choose ‘Install Add-on From File…’
4. Choose .xpi that you’ve just downloaded, click ‘Install’
5. Restart Zotero
### Settings {#settings}
1. In the main menu go to Tools -> ZotFile Preferences
#### Location of Files {#location-of-files}
1. Set ****Custom Location****. For example: /home/yanboyang713/papers
2. Use subfolder defined by ****/%a****, mean author name.
#### Renaming Rules {#renaming-rules}
1. Set **Format for all Item Types except Patents**: {%b}
This will rename file same with your Citation Key.
1. Set **Maximum number of authors** choose 1
2. Uncheck **Add suffix when authors are omitted**
## Scite {#scite}
Install by downloading the [latest release](https://github.com/scitedotai/scite-zotero-plugin/releases) and save the XPI file, just clicking it – and then in Zotero:
1. In the main menu go to Tools > Add-ons
2. Select ‘Extensions’
3. Click on the gear in the top-right corner and choose ‘Install Add-on From File…’
4. Choose .xpi that you’ve just downloaded, click ‘Install’
5. Restart Zotero
## Reference List {#reference-list}
1. <http://zotfile.com/>
2. <https://github.com/scitedotai/scite-zotero-plugin>
3. <https://retorque.re/zotero-better-bibtex/>
| 30.834254 | 270 | 0.719763 | eng_Latn | 0.753804 |
5354e78a4bcfa37055b65efce7079049eb2ff52b | 11,739 | md | Markdown | 7_4.md | pupenasan/hmibook | 90716e55275da229b6b9bd57953935210a03f75f | [
"MIT"
] | 1 | 2022-03-27T17:02:26.000Z | 2022-03-27T17:02:26.000Z | 7_4.md | pupenasan/hmibook | 90716e55275da229b6b9bd57953935210a03f75f | [
"MIT"
] | 1 | 2022-03-17T16:06:34.000Z | 2022-03-17T16:06:34.000Z | 7_4.md | pupenasan/hmibook | 90716e55275da229b6b9bd57953935210a03f75f | [
"MIT"
] | null | null | null | [Головна](README.md) > [7.Розроблення підсистеми трендів](7.md)
# 7.4. Підсистема трендів в SCADA Citect
У SCADA Citect збереженням (реєстрацією) даних на диску з можливістю їх перегляду у вигляді тренду займається ***трендовий сервер*** (Trend Server). Окрім збереження, трендовий сервер також обслуговує запити від клієнтів (наприклад, від Process Analyst) на читання архівних даних. Оскільки у Citect підтримується розподілена кластерна структура (див. параграф 9.1.6), трендовий сервер може запускатися окремим процесом на окремому ПК. Тому в проекті для Trend Server явно конфігурується ім’я, адреса ПК, на якому планується запускати сервер, TCP-порт та кластер. Для standalone рішень ці настройки залишаються за замовчуванням, оскільки усі компоненти запускаються на тому самому ПК.
Слід зазначити, що, окрім трендового сервера, збиранням та збереженням даних для їх аналізу та формування звітів займається окремий програмний пакет – Historian. Враховуючи, що Schneider Electric забезпечує інтеграцію продуктів Citect та Historian, деякі налаштування стосуються означення доступу до Historian.
Значення, які необхідно зберігати в тренді, означуються через ***теги трендів***, в яких вказується вся необхідна для записування в трендові файли інформація. Ці об’єкти в якості джерела даних беруть значення з інших тегів, у тому числі зі змінних тегів (рис. 7.2), хоч в якості значення можна записувати результат виразу з комбінацією будь-яких об’єктів. Таким чином, трендовий сервер слідкує за тим, коли необхідно зробити розрахунок виразу і коли треба зробити запис у файлі. Також до його завдань входить формування відповіді на запитування архівних даних. Безпосередніми клієнтами для трендового серверу можуть бути:
- графічні об’єкти для перегляду трендів: Trend та Process Analyst;
- спеціальна Cicode-функція "TrnGetTable" для отримання даних у вигляді масиву;
- функції Cicode для експорту даних: у буфер – "TrnExportClip", в файл CSV – "TrnExportCSV", або у файл DBF – "TrnExportDBF".
Для перегляду даних у вигляді трендів у графічній підсистемі використовуються два типи об’єктів "Тренд" (Trend) та "Аналізатор процесів" (Process Analyst). Графічний об’єкт "Тренд" може відображати тільки архівні дані з тегів тренду. Аналізатор процесів, окрім архівних даних, що означені в тегах трендів, може відображати дані реального часу.
*Рис. 7.2*.Принципи роботи трендової підсистеми в Citect
Форму налаштування тегу тренду показано на рис. 7.3. Для тегу тренду означується назва, яка може збігатися з назвою змінних тегів або тегів тривог. У полі "Выражение" вказується Cicode вираз, що повертає якесь числове значення. Це може бути як змінна, як це показано на рис. 7.3, так і вираз або функція, наприклад "(LOOP_1_PV + LOOP_2_PV)/2".
Трендовий сервер розраховує значення вказаного виразу з періодичністю, зазначеною в полі "Интервал опроса". Якщо в цьому полі з'являється десяткове число, то воно буде інтерпретуватися як секунди. Періодичність можна також задати у форматі "hh:mm:ss". Поле "Интервал опроса" є опціональним, за замовченням приймається 10 с. Слід звернути увагу, що при зміні цього значення треба видалити раніше створені архівні файли для даного трендового тегу, щоб зміни вступили в силу.
<a href="media7/7_3.png" target="_blank"><img src="media7/7_3.png"/></a>
*Рис. 7.3.* Налаштування тегу тренда
У Citect доступні три способи ініціювання записування, які вказуються в полі "Тип". ***Періодичний тренд*** (тип TRN_PERIODIC) записує дані постійно із зазначеним періодом. Можна також вказати ***тригер*** (поле "Триггер"), який буде активувати або деактивувати ведення записування. Запис в архів проводиться тоді, коли тригер = TRUE або не вказаний (рис. 7.4).
*Рис. 7.4.* Періодичний тренд (тип TRN_PERIODIC)
***Подієвий тренд*** (тип TRN_EVENT) записує дані тільки в момент зміни значення тригера з FALSE в TRUE. Між точками запису проводиться інтерполяція (рис. 7.5).
*Рис.7.5.* Подієвий тренд (тип TRN_EVENT)
***Періодично-подієвий тренд*** (тип TRN_PERIODIC_EVENT), як і попередній, записує дані тільки в момент зміни значення тригера з FALSE в TRUE. Але цей тип тренду не робить інтерполяцію між точками запису (рис. 7.6.)
*Рис. 7.6.* Періодично-подієвий тренд (тип TRN_PERIODIC_EVENT)
У полі "Имя файла" можна вказати шлях та ім’я файлу (без розширення) для тегу тренду. Наприклад, "[data]:loop1pv" вказує, що архівні файли будуть розміщуватися в папці, означеній параметром "DATA" з назвою "loop1pv". Якщо ім’я файлу не вказане, воно береться з імені тегу тренду, а шлях папки – зі значення параметру "DATA".
Глибина збереження архіву та кількість архівних файлів для кожного тегу тренду означується значеннями полів "Число файлов", "Время" та "Периодичность". Властивість "Число файлов" вказує на кількість архівних файлів (за замовченням береться 2). Файли синхронізовані відносно часу, вказаного в полі "Время", а кожен файл буде зберігати дані відповідно до вказаної періодичності. При першому запуску системи виконання будуть створені усі необхідні файли для ведення історії. Під час роботи системи дані будуть зберігатися в кожному з цих файлів, поступово переходячи від одного файлу до іншого з вказаною періодичністю (значення "Периодичность"). Коли закінчується час записування в останній файл, система знову переходить до 1-го файлу, затираючи старі архівні значення. Розглянемо це на прикладі, де означено кількість файлів рівною 10, періодичність 24:00:00, а час синхронізації ("Время") – 00:00:00.
1. При першому запуску системи будуть створені усі 10 файлів із зазначеним ім'ям та з розширеннями ".000"… ".009" та один файл із розширенням ".HST". Спочатку Citect пише архівні дані у файл з розширенням ".000".
2. Опівночі, наступного дня, дані будуть записуватися у файл з розширенням ".001".
3. Опівночі, третього дня, дані будуть записуватися у файл з розширенням ".002" і т. д.
4. Після 10-ти днів система почне переписувати перший файл, тобто ".000".
Слід звернути увагу, що при зміні будь-яких значень кількості або періодичності історичних файлів треба видалити раніше створені архівні файли для даного тегу тренда, щоб зміни вступили в силу.
Властивість "Метод сохранения" вказує на спосіб і величину збереження числових даних. Якщо не потрібна велика точність, варто використовувати "Scaled (2-byte samples)". Одиниці вимірювання і формат вказуються для відображення їх на осі, курсорі Аналітика процесів та на інших числових полях. Така необхідність спричинена можливістю використання кількох змінних у формуванні значення трендового тегу. Зона і привілеї налаштовуються для обмеження доступу (див. параграф 8.7.6).
У нових версіях Citect з’явилися додаткові можливості і відповідно налаштування. Зокрема масштаб задається для формування масштабу відображення за замовчуванням. Властивість "Собрать статистику" (Historize) вказує на автоматичне формування історичного тегу в спеціалізованому продукті Schneider Electric's Historian.
Клієнтська частина підсистеми трендів представлена графічними об’єктами переглядачів трендів, які можна розміщувати в будь-якій кількості на будь якій дисплейній сторінці, а також функціями Cicode.
Об’єкт "***Тренд***" – переглядач трендів Citect, який був доступний ще з ранніх версій. Він дає можливість відобразити до 8-ми архівних значень тегів тренду. Для кожного пера (кривої) вказується назва тегу тренду та колір (рис. 7.7). Властивість "Число выборок данных" вказує на кількість записів у файлі історії, які будуть відображатися для кожного тегу тренду. За допомогою властивості "Пикселов на выборку" вказуються проміжки між двома точками одного пера на графіку. Ширина об’єкта "Тренд" пов’язана з цими властивостями:
```
Ширина = "Пикселов на выборку" x Число выборок данных" (7.1)
```
Указати діапазон значень у часових розмірах можна за допомогою Cicode функції, наприклад TrendSetSpan.
Об’єкт "Тренд" має дуже мало можливостей налаштування в середовищі розроблення. Усі можливості навігації по історії, відображенню значень, налаштуванню області відображення та багато іншого реалізовуються через функції Cicode. Для спрощення використання трендів на базі об’єкта "Тренд" у включених проектах Citect є спеціальні сторінки, джини та суперджини. Тим не менше, більш функціональнішим у використанні трендів є об’єкт "Аналізатор процесів".
*Рис. 7.7.* Об’єкт "Тренд"
***Аналізатор процесів*** (Process Analyst) дає можливість відображати в часі значення тегів трендів, змінних тегів а також тегів тривог. Аналізатор процесів має такі можливості:
- налаштування всіх параметрів відображення як у середовищі розроблення, так і в середовищі виконання;
- добавлення і відображення на одному елементі тренду кількох панелей (умовно незалежних трендових елементів) це дає можливість:
- групувати криві разом за певною ознакою;
- порівнювати тренди;
- здійснювати відносний зсув панелей за часом;
- відображення на панелі об’єктів:
- трендів у реальному часі зі змінних тегів;
- архівних трендів з трендового серверу;
- зміни стану тривог у часі з тривогового сервера;
- архівних трендів та трендів реального часу з Historian;
- добавлення на тренд (конкретну панель) кривих реального часу та за архіву:
- числових змінних;
- дискретних змінних;
- стану тривог;
- відображення кривих (пер, pen) тренду у вигляді (рис. 7.8):
- ліній різного кольору, товщини та формату: неперервної, штрихової, пунктирної і т.п.;
- різного типу ліній залежно від якості (достовірності) та наявності даних;
- точок даних у форматі різних фігур;
- відображення та налаштування по осях X та Y для кожної кривої (рис. 7.9):
- сітки і поділок;
- діапазону, можливості автомасштабування;
- можливості прокручування (див.рис. 7.10);
- відображення шкали для вибраної кривої;
- у режимі виконання використання кнопок перемотування (див. рис. 7.10)
- "<" – на половину інтервалу назад;
- " <<" – на один інтервал назад;
- " >" – на половину інтервалу вперед;
- " >>" – на один інтервал уперед;
- у режимі виконання для кривих
- зціплювати криві разом;
- синхронізувати з плинним часом;
- виведення легенди з можливістю:
- швидкої зміни основних властивостей кривих;
- відображенням числового значення трендів у потрібній точці часу через курсор;
- збереження відображених даних у форматі XLS або TXT;
- збереження заданих налаштувань (представлення) у файл "*.PAV" з указаним ім’ям для можливості відкриття налаштувань звичайним вибором;
- керування та налаштування з Cicode функцій та VBA.
<a href="media7/7_8.png" target="_blank"><img src="media7/7_8.png"/></a>
*Рис.7.*8. Налаштування кривої тренду
<a href="media7/7_9.png" target="_blank"><img src="media7/7_9.png"/></a>
*Рис. 7.9.* Налаштування координатних ліній та осей
<a href="media7/7_10.png" target="_blank"><img src="media7/7_10.png"/></a>
*Рис. 7.10.* Загальний вигляд Аналітика процесів у середовищі виконання
Окремо варто зупинитися на функції відображення на панелі трендів стану тривог (рис. 7.11).
<a href="media7/7_11.png" target="_blank"><img src="media7/7_11.png"/></a>
*Рис. 7.11.* Загальний вигляд Аналітика процесів в середовищі виконання
Кожен стан тривог (неактивна 4, активна непідтверджена 1, активна підтверджена (3), неактивна непідтверджена 2) відображається на панелі трендів у вигляді прямокутника певної висоти і контуру. Для аналогових тривог можна також змінювати колір для різної мітки.
Окрім трендів, Citect має можливість з використанням спеціальних функцій відображати залежності у форматі графіку X від Y.
[<-- 7.3. Відображення трендових даних ](7_3.md)
[--> 7.5. Підсистема трендів в SCADA zenon](7_5.md) | 64.147541 | 901 | 0.782094 | ukr_Cyrl | 0.999994 |
53552abf7177eb99b2209a4c46e2065be21a1bd0 | 1,031 | md | Markdown | additional-material/translations/moving-a-commit-to-a-different-branch.ko.md | dqiuwq/first-contributions | 5fa4b1e0052a58f7f4763c82d18d41e5b7cf8401 | [
"MIT"
] | null | null | null | additional-material/translations/moving-a-commit-to-a-different-branch.ko.md | dqiuwq/first-contributions | 5fa4b1e0052a58f7f4763c82d18d41e5b7cf8401 | [
"MIT"
] | null | null | null | additional-material/translations/moving-a-commit-to-a-different-branch.ko.md | dqiuwq/first-contributions | 5fa4b1e0052a58f7f4763c82d18d41e5b7cf8401 | [
"MIT"
] | null | null | null | ## 커밋을 다른 브랜치로 옮기기
What if you commit a change, and then realize that you committed to a different branch?
How can you change that? This is what this tutorial covers.
만일 변경사항을 반영했는데 전혀 다른 브랜치에 커밋한 사실을 알았다면 어떻게할까요?
이걸 어떻게 바로잡을 수 있을까요? 바로 이 장에서 다룰 내용입니다.
### 가장 최근 커밋들을 기존에 있는 브랜치로 이동시키기
사용예:
```git reset HEAD~ --soft``` - 마지막 커밋을 되돌립니다. 물론 수정한 내용은 그대로 남아있습니다.
```git stash``` - 현재까지 수정한 모든 작업내용들의 상태를 저장합니다.
```git checkout name-of-the-correct-branch``` - 실제 반영하고자하는 브랜치를 체크아웃합니다.
```git stash pop``` - 마지막으로 저장한(stash) 변경내역들을 현재 브랜치에 반영하고 저장한 내역에서 삭제합니다.
```git add .``` - 또는 커밋에 반영할 변경내역들을 개별적으로 추가합니다.
```git commit -m "your message here"``` - 저장하고 변경내역을 커밋합니다.
자 이제 변경사항이 올바른 브랜치에 반영되었습니다.
### 가장 최근 커밋들을 신규 브랜치를 생성하여 이동시키기
사용예:
```git branch newbranch``` - 신규 브랜치를 생성하고 모든 커밋들을 저장합니다.
```git reset --hard HEAD~#``` - master 브랜치의 #번째 커밋을 되돌립니다. 되돌린 커밋들은 master에서 완전히 삭제되므로 주의하세요.
```git checkout newbranch``` - 생성한 브랜치로 이동합니다. 모든 커밋들을 가지고 있을겁니다.
주의: 커밋하지 않은 변경사항들은 사라집니다.
| 35.551724 | 96 | 0.661494 | kor_Hang | 1.00001 |
535583db966b03b26d1f5ab4716e0fc37fe4973f | 111 | md | Markdown | buildkite/tools/pipeline_generator/README.md | aehlig/continuous-integration | 42f00da5f989b7dc93cb058f26f4383f879ac512 | [
"Apache-2.0"
] | null | null | null | buildkite/tools/pipeline_generator/README.md | aehlig/continuous-integration | 42f00da5f989b7dc93cb058f26f4383f879ac512 | [
"Apache-2.0"
] | null | null | null | buildkite/tools/pipeline_generator/README.md | aehlig/continuous-integration | 42f00da5f989b7dc93cb058f26f4383f879ac512 | [
"Apache-2.0"
] | null | null | null | go get gopkg.in/yaml.v2
go get github.com/buildkite/go-buildkite/buildkite
go get github.com/machinebox/graphql | 37 | 50 | 0.828829 | pcm_Latn | 0.170659 |
5355e01785f37a4c00a4bd74e609074dff18fc45 | 13,286 | md | Markdown | doc/CONFIGURE.md | timja/ssh-slaves-plugin | 22ddf7b40c50d263bcc410e1a4253337de6cc1e0 | [
"MIT"
] | null | null | null | doc/CONFIGURE.md | timja/ssh-slaves-plugin | 22ddf7b40c50d263bcc410e1a4253337de6cc1e0 | [
"MIT"
] | null | null | null | doc/CONFIGURE.md | timja/ssh-slaves-plugin | 22ddf7b40c50d263bcc410e1a4253337de6cc1e0 | [
"MIT"
] | null | null | null | # Configuring the SSH Build Agents plugin
This plugin allows you to manage an agent running on \*nix machines over SSH. It adds a new type of agent launch method.
This launch method will
* Open an SSH connection to the specified host as the specified username.
* Check the default version of java for that user.
* Copy the latest remoting.jar via SFTP (falling back to scp if SFTP is not available)
* Start the remoting process.
## Prerequisites
Before you start to use the the plugin with your agents, you need to prepare your agents to run the remoting process.
This means that **you have to install a JDK/JRE 8 on your agent** in order to run the *remoting.jar* process.
The agent should have **enough memory** to run the remoting process and the builds.
**The agent needs to be reachable from the master**,
You have to be ensure that your Jenkins instance can connect through SSH port to your agent; you can check it from the command line.
You will have to supply an account that can log in on the target machine. No root privileges are required.
Finally the agent should have **permissions to read and write on the work directory**, and **enough disk space** to store *remoting.jar* (~1MB),
logs (~10MB should be enough), and your build workspaces (it depends on your builds, probably a few GB).
## Configure a Node to use the SSH Build Agents plugin
### Create a Node
First of all, we have to create a node. Go to `Manage Jenkins/Manage Nodes`.
Then click on the `New Node` button and configure the name and Node type.
After creating the new node, you have to configure the node settings.
* **Name:** Name that uniquely identifies an agent within this Jenkins installation.
* **Description:** Optional human-readable description for this agent.
* **\# of Executors:** The maximum number of concurrent builds that Jenkins may perform on this agent.
* **Remote root directory:** An agent needs to have a directory dedicated to Jenkins.
Specify the path to this directory on the agent. It is best to use an absolute path,
such as /var/jenkins or c:\jenkins. This should be a path local to the agent machine.
* **Labels:** Labels (or tags) are used to group multiple agents into one logical group.
You will use them to select it as agent for a build. Multiple labels must be separated by a space.
* **Usage:** Controls how Jenkins schedules builds on this node.
* **Use this node as much as possible:** This is the default setting. In this mode, Jenkins uses this node freely.
Whenever there is a build that can be done by using this node, Jenkins will use it.
* **Only build jobs with label expressions matching this node:**
In this mode, Jenkins will only build a project on this node when that project is restricted to certain nodes using a label expression
and that expression matches this node's name and/or labels.
This allows a node to be reserved for certain kinds of jobs. For example, if you have jobs that run performance tests,
you may want them to only run on a specially configured machine, while preventing all other jobs from using that machine.
To do so, you would restrict where the test jobs may run by giving them a label expression matching that machine.
Furthermore, if you set the # of executors value to 1, you can ensure that only one performance test will execute at
any given time on that machine; no other builds will interfere.
* **Launch method:** Select *Launch agents via SSH* Starts a agent by sending commands over a secure SSH connection.
### Configure Launch agents via SSH
Once you selected the **Launch method** to **Launch agents via SSH**, you can configure your SSH agent settings.
#### Required settings
* **Host:** Hostname or IP of the agent, it should be resolvable and reachable from the Jenkins instance.
* **Credentials:** Select the credentials to be used for logging in to the remote host. See [Integration with SSH Credentials Plugin](#integration-with-ssh-credentials-plugin)
* **Host Key Verification Strategy:** Controls how Jenkins verifies the SSH key presented by the remote host whilst connecting. See [Host Key Verification Strategy](#host-key-verification-strategy)
#### Advanced settings
* **Port:** The TCP port on which the agent's SSH daemon is listening, usually 22.
* **JavaPath** This Java path will be used to start the JVM. (/mycustomjdkpath/bin/java) If empty Jenkins will search Java command in the agent.
* **JVM Options** Additional arguments for the JVM such as min and max heap size, garbage collector options, and other tuning settings.
* **Prefix Start Agent Command** What you enter here will be prepended to the launch command.
* **Suffix Start Agent Command** What you enter here will be appended to the launch command.
* **Connection Timeout in Seconds** Set the timeout value for ssh agent launch in seconds.
If empty, it will be reset to default value (210 seconds). This will only set the timeout for agent launching; once launched,
the timeout will not apply.
* **Maximum Number of Retries** Set the number of times the SSH connection will be retried if the initial connection results in an error.
If empty, it will be reset to default value (10). If the value is 0, the retries would disabled.
* **Seconds To Wait Between Retries** Set the number of seconds to wait between retry attempts of the initial SSH connection. The default value is 15 seconds.
* **Use TCP_NODELAY flag on the SSH connection** Enable/Disables the TCP_NODELAY flag on the SSH connection.
If set, disable the Nagle algorithm. This means that segments are always sent as soon as possible,
even if there is only a small amount of data. When not set, data is buffered until there is a sufficient amount to send out,
thereby avoiding the frequent sending of small packets, which results in poor utilization of the network.
* **Remoting work directory** The remoting work directory is an internal data storage, which may be used by Remoting to store caches,
logs and other metadata. For more details see [Remoting Work directory](https://github.com/jenkinsci/remoting/blob/master/docs/workDir.md#remoting-work-directory)
If remoting parameter "-workDir PATH" is set in Suffix Start Agent Command this field will be ignored.
If empty, the **Remote root directory** is used as **Remoting Work directory**
### Host Key Verification Strategy
Controls how Jenkins verifies the SSH key presented by the remote host whilst connecting.
#### Known hosts file Verification Strategy
Checks the known_hosts file (~/.ssh/known_hosts) for the user Jenkins is executing under
to see if an entry exists that matches the current connection. It is possibel to change the default file by setting
the Java property `-Dhudson.plugins.sshslaves.verifiers.KnownHostsFileKeyVerificationStrategy.known_hosts_file=PATH_TO_FILE`
This method does not make any updates to the Known Hosts file, instead using the file as a read-only source and expecting
someone with suitable access to the appropriate user account on the Jenkins master to update the file as required,
potentially using the ssh hostname command to initiate a connection and update the file appropriately.
#### Manually provided key Verification Strategy
Checks the key provided by the remote host matches the key set by the user who configured this connection.
The SSH key expected for this connection. This key should be in the form `algorithm value`
where algorithm is one of ssh-rsa or ssh-dss, and value is the Base 64 encoded content of the key. The keys should be placed in /etc/ssh/<key_name>.pub
#### Manually trusted key Verification Strategy
Checks the remote key matches the key currently marked as trusted for this host.
Depending on configuration, the key will be automatically trusted for the first connection,
or an authorised user will be asked to approve the key.
An authorised user will be required to approve any new key that gets presented by the remote host.
Require a user with Computer.CONFIGURE permission to authorise the key presented during the first connection to
this host before the connection will be allowed to be established.
If this option is not enabled then the key presented on first connection for this host will be automatically trusted
and allowed for all subsequent connections without any manual intervention.
#### Non verifying Verification Strategy
Does not perform any verification of the SSH key presented by the remote host, allowing all connections regardless of the key they present.
### Availability
#### Keep this agent online as much as possible
In this mode, Jenkins will keep this agent online as much as possible.
If the agent goes offline, e.g. due to a temporary network failure, Jenkins will periodically attempt to restart it.
#### Take this agent online and offline at specific times
In this mode, Jenkins will bring this agent online at the scheduled time(s), remaining online for a specified amount of time.
If the agent goes offline while it is scheduled to be online, Jenkins will periodically attempt to restart it.
After this agent has been online for the number of minutes specified in the Scheduled Uptime field, it will be taken offline.
If Keep online while builds are running is checked, and the agent is scheduled to be taken offline,
Jenkins will wait for any any builds that may be in progress to complete.
#### Take this agent online when in demand, and offline when idle
In this mode, Jenkins will bring this agent online if there is demand, i.e. there are queued builds which meet the following criteria:
* They have been in the queue for at least the specified *In demand delay time period*
* They can be executed by this agent (e.g. have a matching label expression)
This agent will be taken offline if:
* There are no active builds running on this agent
* This agent has been idle for at least the specified *Idle delay time period*
### Integration with SSH Credentials Plugin
This plugin is now integrated with the [SSH Credentials Plugin](https://plugins.jenkins.io/ssh-credentials).
This changes how agents are configured.
The Node configuration is simplified, e.g. you now just have a Credentials drop down listing all the "Global" and
"System" scoped credentials.
If you are upgrading from a previous 0.23 version, the plugin should try to inject any required SSH credentials in the
[Credentials Plugin](https://plugins.jenkins.io/credentials) using the credentials that were previously stored in each node's definition.
To define credentials to use when connecting agents you need to go to the `Jenkins/Manage Jenkins/Manage Credentials` screen.
Once on this screen you can add **SSH credentials**, either using a *Username & Password* or using a *Username & Private Key*.
Credential scope controls where the credentials can be used:
* System scope is only available for the root Jenkins instance (in other words Jenkins can use it to connect build nodes, but the credentials are not available to build jobs)
* Global scope is available for the root Jenkins instance and any child items (in other words Jenkins can use it to connect build nodes, build jobs can use it for other SSH Credentials enabled plugins)
When you have a lot of different credentials it can be useful to put those credentials into credential domains, e.g.
The drop-down for selecting credentials will construct a specification that includes the URI Scheme of ssh
and the specified hostname and port, so where you have created the appropriate credential domains the choice of credentials
will be restricted to those outside of any credential domain and those from matching credential domains.
This can help differentiate between multiple keys/password associated with the same username.
### Using Cygwin
See [SSH Build Agents and Cygwin](https://wiki.jenkins.io/display/JENKINS/SSH+slaves+and+Cygwin) for the discussion of how to use this plugin to talk to Cygwin SSHD server.
[Remoting documentation](https://github.com/jenkinsci/remoting/tree/master/docs)
### Launch Windows agents using Microsoft OpenSSH
The current version of the plugin does not run directly on PowerShell, you have to use prefix and suffix settings to trick the command and make it works, Windows 10 machines can run as SSH agents with the Microsoft OpenSSH server by using:
**Prefix Start Agent Command**
```
powershell -Command "cd C:\J\S ; C:\J\S\jdk\bin\java.exe -jar remoting.jar" ; exit 0 ; rem '
```
**Suffix Start Agent Command**
```
'
```
[see this Mark Waite's comment](https://issues.jenkins-ci.org/browse/JENKINS-42856?focusedCommentId=355486&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-355486)
| 59.048889 | 239 | 0.777209 | eng_Latn | 0.99883 |
53562482bd60974ae2e6a823bbb976ef60e6edbd | 877 | md | Markdown | Project-Arcade Game Clone/README.md | nickhaynes/Udacity-FEND | 7d0ce0b34ab3628b7049ef6bde6bb8f82e2de824 | [
"MIT"
] | null | null | null | Project-Arcade Game Clone/README.md | nickhaynes/Udacity-FEND | 7d0ce0b34ab3628b7049ef6bde6bb8f82e2de824 | [
"MIT"
] | null | null | null | Project-Arcade Game Clone/README.md | nickhaynes/Udacity-FEND | 7d0ce0b34ab3628b7049ef6bde6bb8f82e2de824 | [
"MIT"
] | null | null | null | RIVER RUNNER--The New Frogger
===============================
It's a beautiful day for a swim--if only it weren't for all these bugs! Bugs keep any person from enjoying a good swim in the river, so how do you get the chance for a dip? Easy--RUN!
## How to Play the Game
Use your keypad. Up is up, down is down, left...you get the idea.
AVOID THE BUG(S)! If you hit a bug, you get sent home, and have to recover from the bugbites and try again.
Don't leave the screen. You can go side to side--that's just smart strategy--but you can't leave the field. Nobody wins by running away--set your goal, and run through the field, not to another field.
## How Do I Win?
Open the file--in this case, the index HTML file. Count the bugs. Time the bugs. Run. Get to the river. Then swim in the river. Not too long, though--then it's off to find another river to swim in!
| 58.466667 | 203 | 0.696693 | eng_Latn | 0.999053 |
535631a5f6a7f2092903972ab37f3076b8f36f4a | 1,191 | md | Markdown | docs/_functions/global/DOMAIN_ELSEWHERE_AUTO.md | dangeroustech/dnscontrol | c33c5956a9fd3d662ac4e5fa3063bdf656531b2f | [
"MIT"
] | 2,269 | 2017-03-14T19:18:36.000Z | 2022-03-31T09:58:25.000Z | docs/_functions/global/DOMAIN_ELSEWHERE_AUTO.md | dangeroustech/dnscontrol | c33c5956a9fd3d662ac4e5fa3063bdf656531b2f | [
"MIT"
] | 974 | 2017-03-14T21:42:10.000Z | 2022-03-31T16:55:51.000Z | docs/_functions/global/DOMAIN_ELSEWHERE_AUTO.md | jauderho/dnscontrol | 21b2a7a5333e8fa2efc6b5a37b632e90cbef3082 | [
"MIT"
] | 363 | 2017-03-14T20:34:15.000Z | 2022-03-30T21:59:22.000Z | ---
name: DOMAIN_ELSEWHERE_AUTO
parameters:
- registrar
- list of Dns Providers
---
`DOMAIN_ELSEWHERE_AUTO()` is similar to `DOMAIN_ELSEWHERE()` but instead of
a hardcoded list of nameservers, a DnsProvider() is queried.
`DOMAIN_ELSEWHERE_AUTO` is useful when you control a domain's registrar but the
DNS zones are managed by another system. Luckily you have enough access to that
other system that you can query it to determine the zone's nameservers.
For example, suppose you own a domain but the DNS servers for it are in Azure.
Further suppose that something in Azure maintains the zones (automatic or
human). Azure picks the nameservers for the domains automatically, and that
list may change occasionally. `DOMAIN_ELSEWHERE_AUTO` allows you to easily
query Azure to determine the domain's delegations so that you do not need to
hard-code them in your dnsconfig.js file.
For example these two statements are equivalent:
```
DOMAIN_ELSEWHERE_AUTO("example.com", REG_NAMEDOTCOM, DSP_AZURE);
# ...is equivalent to...
D("example.com", REG_NAMEDOTCOM,
NO_PURGE,
DnsProvider(DSP_AZURE)
);
```
NOTE: The `NO_PURGE` is used to prevent DNSControl from changing the records.
| 33.083333 | 79 | 0.777498 | eng_Latn | 0.996841 |
5357d10a49e49be883c44598f998f45b5b8061ad | 141 | md | Markdown | _posts_tmp/2020-11-30-linux-tar.md | dongb0/donb0.github.io | 6582defef0fa4472aceeaac3ee3565d6fee1d3bc | [
"Apache-2.0"
] | 1 | 2022-01-16T02:30:16.000Z | 2022-01-16T02:30:16.000Z | _posts_tmp/2020-11-30-linux-tar.md | dongb0/donb0.github.io | 6582defef0fa4472aceeaac3ee3565d6fee1d3bc | [
"Apache-2.0"
] | 1 | 2022-03-10T11:42:22.000Z | 2022-03-10T11:42:23.000Z | _posts/Linux notes/Linux cmd/2020-11-30-linux-tar.md | dongb0/dongb0.github.io | 4aa0722a3239c6381cedceea5d54fd12c4916db1 | [
"Apache-2.0"
] | null | null | null | ---
layout: post
title: "Linux Command (4) -- tar"
subtitle:
author: "Dongbo"
header-style: text
hidden: true
tags:
- linux
- cmd
---
| 10.071429 | 33 | 0.624113 | eng_Latn | 0.563122 |
Subsets and Splits
No saved queries yet
Save your SQL queries to embed, download, and access them later. Queries will appear here once saved.